Thread: Max 3 Rooted
View Single Post
Old 04-01-2020, 01:54 PM   #49
diabl0w
Connoisseur
diabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enough
 
Posts: 87
Karma: 527
Join Date: Sep 2019
Device: Max3
Quote:
Originally Posted by shunf4 View Post
Thanks for your work! I wonder how you extracted the recovery.img of 2.2.2 update provided EDL mode is no longer available.

Did you boot into a patched old version's recovery and run dd to dump it out? If so, we should expect each update in the future to be compatible with the patched recovery from the previous version. Is it true?
I've had magisk installed since the original firmware, and I've been able to use root capabilities to intercept the encrypted update in an unencrypted form for each new update. then I get extract the zip and grab the new recovery.img and patch it. that being said, I am not sure if the recovery.img has even changed between firmwares. so you may be right. I dont really care to investigate it for the time being, since patching the new one is easy.

I will actually probably start patching the boot.img instead, because I have recently found that we can do that with our devices and it makes things more straightforward. The current method in OP actually patches the boot.img anyway once you hit "install" in magisk manager. Whether you originally "fastboot boot" with a patched recovery or patched boot is sort of irrelevant at the moment.

all these things can change if onyx pushes updates to the bootloader or kernel or recovery. so for your last statement I would say the answer is usually yes, but not necesarily. but I will always be able to provide a patched version for the latest update so its a non issue
diabl0w is offline   Reply With Quote