Quote:
Originally Posted by Renate
First, determine if you are on _a or _b.
_b is bigger and everything bloats so that I presume _b is newer and current.
Check that you can write _b to _b and it boots to stock recovery.
Make a copy of _b (not the trimmed one).
Modify it in a non-destructive way and flash it.
See if that will boot or if you are getting bit by AVB.
Code:
modfile copy_b.img 600 /a Hello
That puts the word "Hello" in the unused space of the extended command line. |
I would assume I'm on _b also, I tried to reflash _a then _b at 2 different time to isolate the issue, and the bootloop was only fixed after I reflash _b.
Can you elaborate on the modifying part of the recovery img? I mean what tool to use?
Thanks