Is there anyway to start the su daemon without hijacking app-process32?
I'm trying to preroot a Samsung 5.1.1 rom that has a locked bootloader.
I can root the rom just fine, but it bootloops because I'm unable to patch the boot.img.
This is due to the modified app_process32.
If I restore app_process32 back to its original state it boots just fine, but superuser reports no SU binary installed.
According to @Chainfire the daemon can be started several ways, I. E install-recovery.sh, init.d, it can also be started via a modified ddexe.
Non of these work. Has anyone got any idea on this?
I'm trying to preroot a Samsung 5.1.1 rom that has a locked bootloader.
I can root the rom just fine, but it bootloops because I'm unable to patch the boot.img.
This is due to the modified app_process32.
If I restore app_process32 back to its original state it boots just fine, but superuser reports no SU binary installed.
According to @Chainfire the daemon can be started several ways, I. E install-recovery.sh, init.d, it can also be started via a modified ddexe.
Non of these work. Has anyone got any idea on this?
from xda-developers http://ift.tt/1PrNc2n
via IFTTT
No comments:
Post a Comment