View Single Post
Old Yesterday, 11:27 PM   #13
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 4,193
Karma: 19000001
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
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
Me? I'd try to avoid swapping slots. Just flash the boot image to the current slot.

Did you extract system_a already from super? Is it in erofs? Is it in ext4?

If you PM me a link to the stock recovery I might find time to make a custom recovery.
There are still no updates for this device.
Renate is online now   Reply With Quote