Im trying to do some tests to try and find out why the phone crashes with a modified boot img
Im a noob in the android environment so my reasons can seem naive.
Since we are getting ramdumps at crash i thought the problem was the ramdisk in the boot.img
So i've created a boot img with 1.5.3.fix kernel and boot and 1.5.2 ramdisk, but the device still crashes
If it's not a corrupted boot.img problem, maybe it's the system checking if everything's fine and noticing a modified environment throws a crash.
So it's the system's fault.
Does anyone know a way to check what background services there are and if one of them is the culprit? How can we check what makes the phone crash?
Also what if the problem is magisk itself? if factory resets seems to fix the issue for many, maybe updating from .2 to .3 brings magisk to keep some old keys and values that when used/accessed crash the phone
I do not know if anyone tested this, but totally uninstalling magisk and deleting all data of it and installing it brand new could fix the issue...?
Im a noob in the android environment so my reasons can seem naive.
Since we are getting ramdumps at crash i thought the problem was the ramdisk in the boot.img
So i've created a boot img with 1.5.3.fix kernel and boot and 1.5.2 ramdisk, but the device still crashes
If it's not a corrupted boot.img problem, maybe it's the system checking if everything's fine and noticing a modified environment throws a crash.
So it's the system's fault.
Does anyone know a way to check what background services there are and if one of them is the culprit? How can we check what makes the phone crash?
Also what if the problem is magisk itself? if factory resets seems to fix the issue for many, maybe updating from .2 to .3 brings magisk to keep some old keys and values that when used/accessed crash the phone
I do not know if anyone tested this, but totally uninstalling magisk and deleting all data of it and installing it brand new could fix the issue...?
Last edited: