I already bricked my fydetab duo. Where can I find boot.img and init_boot.img for Android 15?

Fydetab Duo
1

I started tinkering with the fydetab duo and I kind of bricked it. I wanted to try installing Android and I followed this tuto : https://github.com/LinuxDroidMaster/Fydetab-Duo-DroidMaster-wiki/blob/main/Documentation/Android/Installing_AOSP.md from @DroidMaster1 :pray:

First part worked well and I was able to boot into Anroid, didn’t tried it much but it seemed to be working just fine. Then I started the second part to install Magisk, after I flashed the patched_boot.img providedon the tuto and after that I couldn’t unlock the device at all, the screen kept flickering. something was off. I expect it was because the patched_boot.img was made for Android 14, but the AOSP image I flashed was of Android 15 (it’s the one found there, despite what the page says it’s Android 15 afaict, it’s also what we see when opening the icloud link). I kind of suspected something could go wrong when I flashed but yolo-ed it anyway and of course didn’t backup the current boot partition…

then I tried to find a boot partition image I could flash to restore it to the previous state but I made some mistake and ended up flashing trash in the boot and boot_init partition.

Now Android won’t start at all, obviously. Instead the tablet is booting into Android Recovery. And I can’t put the tablet in Loader / Recovery mode anymore. It always boot into Android Recovery :man_shrugging: even when using the MASKROM button on the PCB :confused: And USB Mass Storage Mode is not reachable either.

I can get into fastboot mode so I wanted to flash the whole fydetab-android-r15.img, but it looks I can’t do that with adb or fastboot. Or at least I couldn’t find how. Then I tried flashing a GSI image (the lineage one, following this guide) but it didn’t change anything. It’s not surprising since this only overrides the system partition.

sooooo I don’t know what to do next. Maybe if I had the right boot.img and init_boot.img files it would boot again. But also the fact that the recovery mode is not working is a bit concerning. Would Compiling and Replacing U-Boot fix it? I think I can do it from adb shell but I don’t know if the partitions are still, the wiki mentions the /dev/mmcblk0p10 & /dev/mmcblk0p11 partitions but I’m not sure they are still the same:

$ ls /dev/block/by-name/ -l
total 0
lrwxrwxrwx 1 root root 20 2021-01-01 13:26 backup -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2021-01-01 13:26 baseparameter -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 2021-01-01 13:26 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2021-01-01 13:26 cache -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2021-01-01 13:26 dtbo -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2021-01-01 13:26 frp -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2021-01-01 13:26 metadata -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2021-01-01 13:26 misc -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 18 2021-01-01 13:26 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 23 2021-01-01 13:26 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 2021-01-01 13:26 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx 1 root root 20 2021-01-01 13:26 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2021-01-01 13:26 security -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2021-01-01 13:26 super -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 2021-01-01 13:26 trust -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2021-01-01 13:26 uboot -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2021-01-01 13:26 userdata -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 2021-01-01 13:26 vbmeta -> /dev/block/mmcblk0p6

so that’s where I’m at. any hint of what I could try is welcome!

thank you :bowing_man:

2

Hi! The provided patched boot.img is for the old Android image (Android 12). I recommend you flashing again the last Android image and patching it yourself instead of using the one I provide (you should have the instructions in the guide).

I didn’t try a GSI ROM from the Android 14 image but if you use DSU Loader you can try it without deleting the original system so you can check if it works or not

3

The MAKSROM button on the motherboard is a hardware-level recovery method, so it shouldn’t be impossible to enter due to being flashed.

Please try using another data cable (not the one that comes with Fydetab) to connect, and then use RKdevtool or Upgradetool to flash the FydeOS firmware.

4

I recommend you flashing again the last Android image and patching it yourself instead of using the one I provide (you should have the instructions in the guide).

@DroidMaster1 yeah, I need to get the Loader / Recovery mode working again for that though :sweat_smile:

@Archie2 thank you that’s quite reassuring, it did work once with this cable though so (using vol + & power) not sure why it wouldn’t now but I’ll try with another one anyway. And also with another computer because somehow when I press the MASKROM button it makes my laptop shutdown :man_shrugging:, so maybe that aborts the process and goes back to regular booting and back into Android Recovery…

thank you both!

5

Got it working with another cable, the first cable that I initially used to flash the tablet can’t even chargeany device now… so that was just unfortunate timing on this cable breaking when I was trying to reset the tablet. using vol+ & power was enough, no need to open it again in fact…

now trying to do install AOSP 14 + Magisk + GAPPS :crossed_fingers:

thank you!

1 Like
6

Glad it worked!
Come join our Fydetab Duo community on Discord!