I get `boot.img` from decrypting ozip from `RMX2076PU_11_OTA_0250` then patch it with magisk manager then flash the patch_boot.img but got wrong boot/recovery.
If anyone can run the 2075-2076 with magisk please share in this thread.
thx.:angel:
Related
I was on 9.5.5 with TWRP and Magisk
I deleted the guest account and remove the island in "Island" to be able to create a full backup in TWRP recovery (Had error 255 before I removed the two other users)
Downloaded the 9.5.7 using oxygen updater
Uninstalled magisk ("Restore images")
Installed 9.5.7 using settings/local update
Went back into Magisk Manager and installed Magisk to inactive slot and rebooted - everything went great and I'm now on 9.5.7 with Magisk ??
Now I'd like to install TWRP recovery using the TWRP app but I'm unsure if I should select the zip file or img file?
evalu8t0r said:
I was on 9.5.5 with TWRP and Magisk
I deleted the guest account and remove the island in "Island" to be able to create a full backup in TWRP recovery (Had error 255 before I removed the two other users)
Downloaded the 9.5.7 using oxygen updater
Uninstalled magisk ("Restore images")
Installed 9.5.7 using settings/local update
Went back into Magisk Manager and installed Magisk to inactive slot and rebooted - everything went great and I'm now on 9.5.7 with Magisk
Now I'd like to install TWRP recovery using the TWRP app but I'm unsure if I should select the zip file or img file?
Click to expand...
Click to collapse
Id download the zip and flash it in magisk.
2nd vote for zip.
Know for sure that the zip will install on both slots. Don't know for sure whether img does.
Therefore, zip.
Not sure how to flash it from Magisk but I'll try the zip from the TWRP app later ?
Thanks for the response ?
...so... the "Flash" button in TWRP does absolutely nothing but download the file (?)
Going to Magisk/Modules and selecting the zip file does the magic ?
EDIT: No, I did not RTFM as I could not find the f**ing manual...
There was a note saying "you are now unrooted" so I went back to Magisk and pressed "Install (Direct)" before rebooting and everything worked as expected ? now on 9.5.7 with Magisk and TWRP ?
Zip. Img doesn't quite install right and disappears on boot.
JhinCuatro said:
Zip. Img doesn't quite install right and disappears on boot.
Click to expand...
Click to collapse
Flash Magisk right after flashing the zip (don't reboot), and see if TWRP "sticks".
I'm using the canary version of Magisk for the Q beta 6. Yesterday I tried to install a self made module to get rid of screenshot sounds (the one on the rep isn't working because Google changed the path. But as I installed it, I can only remember that the last line was "Magisk manager will be removed and your device will reboot in a moment" or something like that
Well, the manager is still installed, but Magisk itself got uninstalled. Besides the fact that I have no clue why that happened, now I can't install it. TWRP doesn't support Q. So I got the Q image from Google, extracted the boot.img and let Magisk Manager patch it (with preserve force encryption and Preserve AVB 2.0/dm-verity turned on) and flash it through Fastboot (fastboot flash boot magisk-boot.img) but it's still not installed. And without TWRP of course I can't flash the uninstaller zip (no clue what was actually removed).
Is there a way through adb or fastboot to find out what's left of the Magisk installation and remove that? Or any other solution I didn't think of?
Ok, via adb is not an option since both /data and /cache refuse permissions so I can't even get logs to find out what happened.
Does anyone have a working pre-patched boot.img? I don't know if that Manual method isn't working because patching isn't really working or because the Magisk files are still present and the module is still conflicting with Magisk. And I don't want to do a factory reset
Nevermind. It was a faulty Magisk database, I had to uninstall and reinstall it to solve the problem
As title implies, how to do it?
Thanks
I see the magisk method but it require boot.img, something that lineageos doesn't have. Any clue?
Thanks.
BWRainbow said:
I see the magisk method but it require boot.img, something that lineageos doesn't have. Any clue?
Thanks.
Click to expand...
Click to collapse
With lineage, the 'recovery' image is the boot.img. It's just the boot image with lineage recovery 'injected' into it. You can use it and inject magisk.
I think the better way to do that though is to adb sideload the magisk apk, but you first have to rename the 'magiskxxx.apk' to 'magiskxxx.zip'. Doing it that way will also add a needed script file to the lineage system, so that when u do a lineage update, magisk and it's modules will be in the updated slot.
cheers
As in the subject, I have a problem with the magisk on the Mi 10 Lite 5G.
I downloaded room miui_MONETGlobal_V13.0.2.0.SJIMIXM_f2b661bdf6_12.0
Due to the fact that on android 12 there is no TWRP working yet, I uploaded magisk 24.3, patched the boot.img file and uploaded via FASTBOOT, everything is loaded, I have root access but the application does not work as it should. When he wants to hide an application under the name of settings installed he gets the message: "Restore application magisk, this application cannot run as root has been lost. Please restore it to its original state." and here I have install at the bottom. after installing the application from scratch, I get another message "Your device requires additional configuration for the magisk to work properly" I click ok and I have the message "configuration failed."
I tried multiple times to patch boot.img and upload it via Fastboot but I have the same problem every time.
Anyone know the solution to this problem ???
I'm still on MIUI 12/A10, I haven't tried this out.
But - since the flash-script is just a fastboot script, you can do it a bit backwards.
Install any pre-A12-rom, after that, boot in to TWRP. Flash boot.img from the A12-rom. Then flash magisk.
Now you edit the fastboot.bat or fastboot.sh-script. Remove the line with fastboot flash boot images\boot.img. Boot in to the bootloader. Then run the script.
You should now have a fully working A12-rom with magisk.