Apatch on an already modified boot.img (Samsung) #621
Unanswered
dazzleworth
asked this question in
Q&A
Replies: 1 comment 1 reply
-
|
Greetings, in my case I restored the modified boot.img several times without any problem. Were you able to apply apatch without problems? Samsungs are awesome. In my case, apply apatch and I get boot loop? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Yes! I had to flash a custom kernel, in this case I picked HariKernel (the only one compatible with Exynos 2100 devices) for OneUi (stock rom) then I could patch boot.img with Apatch without bootloop |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a Samsung device with an already unlocked bootloader and used chimeratool to perform a Knoxguard removed. I can tell that chimeratool modified the boot img with an red warning text upon boot that phone is not running official firmware (after bootloader unlocked) warning. No bootloop and phone boots up fine. No root access also. I'm able to obtain the current modified boot image state using DSU loader and plan to use apatch to patch that. Can I restore modified boot.img before apatch (on Odin or TWRP) if I encounter bootloop? I don't want to restore stock firmware. Thanks.
System info:
Beta Was this translation helpful? Give feedback.
All reactions