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
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 even when using the
MASKROM
button on the PCB 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