That's great. Thanks for sharing.

@PH Ph bootloader -> /dev/block/mmcblk0p1 Maybe this is the boot.bin we are looking for? Try extracting it with Android_boot_image_editor.

Hi @Nick A, I think I'm doing something wrong, but here goes. cat /proc/partitions major minor #blocks name 1 0 8192 ram0 1 1 8192 ram1 1 2 8192 ram2 1 3 8192 ram3 1 4 8192 ram4 1 5 8192 ram5 1 6 8192 ram6 1 7 8192 ram7 1 8 8192 ram8 1 9 8192 ram9 1 10 8192 ram10 1 11 8192 ram11 1 12 8192 ram12 1 13 8192 ram13 1 14 8192 ram14 1 15 8192 ram15 254 0 745120 zram0 179 0 31166976 mmcblk0 179 1 32768 mmcblk0p1 179 2 16384 mmcblk0p2 179 3 32768 mmcblk0p3 179 4 2097152 mmcblk0p4 179 5 16384 mmcblk0p5 179 6 32768 mmcblk0p6 179 7 911360 mmcblk0p7 179 8 16384 mmcblk0p8 179 9 16384 mmcblk0p9 179 10 16384 mmcblk0p10 179 11 16384 mmcblk0p11 179 12 16384 mmcblk0p12 179 13 512 mmcblk0p13 179 14 15872 mmcblk0p14 179 15 16384 mmcblk0p15 259 0 16384 mmcblk0p16 259 1 27858432 mmcblk0p17 253 0 1241204 dm-0 253 1 146376 dm-1 253 2 113948 dm-2 ls -al /dev/block/platform/soc/sdc0/by-name/ total 0 drwxr-xr-x 2 root root 380 1969-12-31 21:00 . drwxr-xr-x 3 root root 420 1969-12-31 21:00 .. lrwxrwxrwx 1 root root 21 1969-12-31 21:00 Reserve0 -> /dev/block/mmcblk0p16 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 UDISK -> /dev/block/mmcblk0p17 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 boot -> /dev/block/mmcblk0p3 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 bootloader -> /dev/block/mmcblk0p1 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 cache -> /dev/block/mmcblk0p7 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 empty -> /dev/block/mmcblk0p14 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 env -> /dev/block/mmcblk0p2 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 frp -> /dev/block/mmcblk0p13 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 media_data -> /dev/block/mmcblk0p15 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 metadata -> /dev/block/mmcblk0p11 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 misc -> /dev/block/mmcblk0p5 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 private -> /dev/block/mmcblk0p12 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 recovery -> /dev/block/mmcblk0p6 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 super -> /dev/block/mmcblk0p4 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 vbmeta -> /dev/block/mmcblk0p8 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 vbmeta_system -> /dev/block/mmcblk0p9 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 vbmeta_vendor -> /dev/block/mmcblk0p10 I couldn't open vendor.img boot.img i do.However, I couldn't find the dts file, only fstab, initd, and a few other empty folders. I posted the images below on 4shared. boot = boot.img vbmeta_vendor = vendor.img boot.img (32.0MB) Image type: Boot image Header version: 2 Command line arguments: selinux=1 androidboot.selinux=permissive androidboot.dtbo_idx=0,1,2 buildvariant=userdebug files avp folder s-gsi.avbpubkeyq-gsi.avbpubkeyr-gsi.avbpubkey fstab.sun50iw9p1 initrd.gz If you can check, I would appreciate it; I await further instructions. !off I tried mounting the partitions by inserting the burned SD card into the PC, but it's not possible to mount them. Except for a few... The SD card made by Phoenixcard is quite interesting. Could it be that the scheme on the SD card is not the same as when installed in the internal memory? The Udisk partition, for example. It's like shared memory, expanding all remaining space on both the memory card and the datauser partition. Similar to using a formatted SD card as internal memory on cell phones with that option.

Thank you ill go look

See my recent posts in the 64gb thread. You'll need to build an image with MAE0621A-02C support. The same thread will also give you dinner hints for to make the WiFi work with aic8800.