Quote:
Originally Posted by szaszg
Thanks a lot, but...
|
If people are fond of Magisk then it should be made clear what the problem is and have it addressed.
So far, this has not been done.
Is it that Magisk'ed images refuse to boot at all?
In such a case the first step is to make a new Android image with a single cosmetic change to see if that can boot.
I've dived pretty deep into the abl but I haven't seen this problem myself.
I don't use Magisk, but I do use custom Android images (at least on recovery).
Slot switching might be possible in EDL.
You could switch the GPT type GUIDs around.
Whether this will run into problems with the slot metadata is another question.
I've never relied on slots since mostly there aren't two "real" slots anyway and the mechanics gets too complicated.
Things being pathologically slow are usually visible in logcat.