Quote:
Originally Posted by Renate
Usually Magisk doesn't worry about vbmeta, but you might clear it and try.
(Or you can use a patched vbmeta.img)
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
|
Thanks for the hint. Will look more deeply into this problematic. So far I do not know how to do it.
Problem is that Palma does not accept probably any fastboot command. Example:
Code:
fastboot --disable-verity --disable-verification flash vbmeta partitions/vbmeta_b.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (64 KB) OKAY [ 0.007s]
Writing 'vbmeta' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Also tried to modify vbmeta with
this patcher. Then updating vbmeta with edl
Code:
edl --loader=palma2pro.bin --memory=ufs w vbmeta_b partitions/vbmeta_b_patched.img
edl --loader=palma2pro.bin --memory=ufs w vbmeta_system_b partitions/vbmeta_system_b_patched.img
Did not help to convince Palma to boot.
Quote:
Originally Posted by Renate
Me? I'd try to avoid swapping slots. Just flash the boot image to the current slot.
|
Yes, I would like to skip this too. But Palma does not boot when I jut put back stock boot image. Only way I did find is swapping activeboot back and forth.
There is probably some better way. But since I don't know any better, I use this randomly discovered method so far.
Quote:
Originally Posted by Renate
Did you extract system_a already from super? Is it in erofs? Is it in ext4?
|
Thanks again! Yes it is erofs. I just did not know thing like erofs exists so far :-D