UniSoC Tablet SC7731 stuck on bootloop due to vbmeta flash via fastbootd
UniSoC Tablet SC7731 stuck on bootloop due to vbmeta flash via fastbootd
ubuntu@ubuntu:~/Downloads/modified_fastboot$ ./fastboot flash vbmeta vbmeta-sign-custom6.img
2yesaraw0x10000000target reported max download size of 268435456 bytes
sending 'vbmeta_a' (1024 KB)...
OKAY [ 0.038s]
writing 'vbmeta_a'...
Flashing succeededOKAY [ 0.261s]
finished. total time: 0.300s
(21-06-2024, 01:03 AM)alee_ ..Any help would be appreciated! Thanks in advance! (Ironic, the brand is called "Advance".)
(21-06-2024, 09:40 AM)hovatek(21-06-2024, 01:03 AM)alee_ ..Any help would be appreciated! Thanks in advance! (Ironic, the brand is called "Advance".)
You'll need the firmware as things stand. It was risky enough flashing a GSI without the pac file but you should've stopped there since you already had root then done a full dump using DD commands so you at least have a dump (though not in .pac format).
Provide the full model name for reference
(22-07-2024, 04:35 AM)sabahlclinton i'm on the EXACTLY SAME SITUATION with moto e13 after flash vbmeta with disable verity through fastbootd (because fastboot was frozening) now my phone just restarts on bootlogo every timemy phone is dead?
(02-09-2024, 10:40 PM)alee_ ..."bump"/"update" on the "progress" I made with this problem. So if anyone here could help me I would appreciate it a lot. Thanks for reading!
(07-09-2024, 04:00 PM)hovatekHow would I enter Diag Mode then? All my attempts to connect even for a second are ruined because of that verify thing. I still keep the imgs on my PC. What should I do then? Which programs should I use? Although I can't afford any of them. Fastboot or adb alone don't do anything, device manager shows the thing for a few seconds though. What should I do?(02-09-2024, 10:40 PM)alee_ ..."bump"/"update" on the "progress" I made with this problem. So if anyone here could help me I would appreciate it a lot. Thanks for reading!
One approach would be to dump the firmware (in its bricked state) in diag mode, grab vbmeta_b.img, create a vbmeta correctly using its info then flash to vbmeta_a partition or just flash vbmeta_b.img
(30-10-2024, 07:12 PM)alee_You'll need a box or dongle for that(07-09-2024, 04:00 PM)hovatekHow would I enter Diag Mode then? All my attempts to connect even for a second are ruined because of that verify thing. I still keep the imgs on my PC. What should I do then? Which programs should I use? Although I can't afford any of them. Fastboot or adb alone don't do anything, device manager shows the thing for a few seconds though. What should I do?(02-09-2024, 10:40 PM)alee_ ..."bump"/"update" on the "progress" I made with this problem. So if anyone here could help me I would appreciate it a lot. Thanks for reading!
One approach would be to dump the firmware (in its bricked state) in diag mode, grab vbmeta_b.img, create a vbmeta correctly using its info then flash to vbmeta_a partition or just flash vbmeta_b.img