MobileRead Forums - View Single Post

Renate · 10-28-2021, 01:50 PM

If you want to play it safe, you can do as I do.
Get your Magisk image made but don't even install it in the boot partition.

Code:

C:\>adb reboot bootloader
C:\>fastboot boot magisk-whatever-1234567

A full reboot will bring you back to stock (in case you screwed something up).
The whole point of Magisk is to leave the system partition as stock so that incremental patches will work.
The only bad part of this is that if you are in the forest and have to reboot you will have to reboot to stock since you don't have fastboot away from your desk.

I've done some more experiments to determine how picky the system is with screwing around with framework-res.apk
It seems that deleting those two JSON breaks things.
The only thing that I've found yet that works was what I originally did, that is, changing the name in the zip local & global headers for the two files = 4 places.

There's another gotcha. If you screw up with the Magisk module it won't complete the boot and you won't have ADB. With stock (i.e. unrooted) you won't have access to the location where the Magisk module is to fix it.
I have another boot image that I made before Magisk that is "insecure", you can simply setuid to be root. This is not a good idea while running normally, especially with strange apps or WiFi on. Then I can access the bad Magisk module and fix it, then reboot to Magisk.

I don't know if it's cache or oat or what that makes the system so picky to changes. I'll have to figure it out so that I can do more patching. I need a good recovery too.

@arooni Hey, how about giving me that cat /proc/cpuinfo?

10-28-2021, 01:50 PM	#33
Renate Onyx-maniac Posts: 4,005 Karma: 18026955 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	If you want to play it safe, you can do as I do. Get your Magisk image made but don't even install it in the boot partition. Code: C:\>adb reboot bootloader C:\>fastboot boot magisk-whatever-1234567 A full reboot will bring you back to stock (in case you screwed something up). The whole point of Magisk is to leave the system partition as stock so that incremental patches will work. The only bad part of this is that if you are in the forest and have to reboot you will have to reboot to stock since you don't have fastboot away from your desk. I've done some more experiments to determine how picky the system is with screwing around with framework-res.apk It seems that deleting those two JSON breaks things. The only thing that I've found yet that works was what I originally did, that is, changing the name in the zip local & global headers for the two files = 4 places. There's another gotcha. If you screw up with the Magisk module it won't complete the boot and you won't have ADB. With stock (i.e. unrooted) you won't have access to the location where the Magisk module is to fix it. I have another boot image that I made before Magisk that is "insecure", you can simply setuid to be root. This is not a good idea while running normally, especially with strange apps or WiFi on. Then I can access the bad Magisk module and fix it, then reboot to Magisk. I don't know if it's cache or oat or what that makes the system so picky to changes. I'll have to figure it out so that I can do more patching. I need a good recovery too. @arooni Hey, how about giving me that cat /proc/cpuinfo?