View Single Post
Old 03-13-2022, 03:33 AM   #134
mergen3107
Wizard
mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.
 
mergen3107's Avatar
 
Posts: 1,520
Karma: 5000046
Join Date: Feb 2012
Location: Cape Canaveral
Device: Kindle Scribe
Quote:
Originally Posted by readandread View Post
Ok, thanks. Just let me wrap my head around this process. The whole process of pulling boot.img patching it and applying isn't something I'm used to. I apologize I'm still confused a bit.

I understand the get the update and install it part, obviously.

Do you pull the boot.img via edl from the v3.2 or after the update (from v3.2.1)?

Do you then take that boot.img as is and copy that to the root directory of the devices, open Magisk and patch it and then apply it after that?
In few words:
1) Apply update.upx as usual
2) From decrypted update.zip get boot.img
3) Put it to device, Magisk - install - patch the boot.img
4) Now flash this patched image to device via fastboot or edl.
5) Open device, Magisk - install again - but this time around use “Direct install”. This option is not available on stock boot.img, so you won’t confuse it.
6) Reboot and you should have root.
mergen3107 is offline   Reply With Quote