Related
Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen
MAGISK modules are HERE
Magisk MANAGER is available on PLAYSTORE
BEFORE making a twrp backup... (after data format ect.)...
you may want to FIX the huawei theme manager not working problem for some of us... the FIX is HERE
Thanks to Henkate
Youll need a good file system manager...i'm using ROOT EXPLORER and theres that new FX file explorer
does it work with android 7?
tanlikar1 said:
does it work with android 7?
Click to expand...
Click to collapse
Yes. In fact, this was meant for Android 7, but it should work on Android 6 too.
Absolutely...Im on Nougat emui5
does anyone have stock rom for MLA-L12C636B340 ?
Do you mean original firmware ?
Maybe you can still get it via firmware finder...
virusdunil said:
Do you mean original firmware ?
Maybe you can still get it via firmware finder...
Click to expand...
Click to collapse
ya
Working on Nova?
Does it work in the non plus Nova as well? Any experiences?
Worked on Can-L11. Tested. No need format data, in twrp tree, i add img, that work with encrypted data.
I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?
Cooks_08 said:
I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?
Click to expand...
Click to collapse
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot
virusdunil said:
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot
Click to expand...
Click to collapse
Got the flash working. Used Garak's Twrp and now i got. Thanks.
Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.
Mezo21 said:
Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.
Click to expand...
Click to collapse
Hi there,
I have Nova 2s, carefully follow this thread's instructions, it will 100% works : https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
Thanks for the guidance, Magisk is doing very well.
Only TWRP is missing, but later.
Huawei Nova
CAN-L01C432B382
Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip
meskafonas said:
Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip
Click to expand...
Click to collapse
did you format data as f2fs? If yes, magisk doesn't go well along with it. If no, then you would get better support at magisk thread
virusdunil said:
Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen
Click to expand...
Click to collapse
Do you have this problem with fingerprint? [emoji853] https://r.tapatalk.com/shareLink?ur...share_tid=3907398&share_fid=3793&share_type=t
Enviado desde mi HUAWEI CAN-L11 mediante Tapatalk
Since you are rooted, you probably found out the OTA update won’t install.
after 3 % it crashes, and no update is installed.
So this is what I did to get the latest update:
step 1: remove root access;
- reboot and hold volume down to get into fastboot mode
- connect to pc, and load original boot.img , I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
- I connected to LMSA, to make a backup, and download the new rom.
- I went to fastboot mode again and flashed the boot by using the command “fastboot flash boot boot.img ( the “old/current” one, not the one from the downloaded new image”
“fastboot reboot”
Step 2:
so the phone booted, and I ran the update again. This time I had no issues installing it.
Step 3:
i extracted the new Boot.img from the rom downloaded by LMSA
I re patched the new boot.img with magisk, rebooted again, and and the update was complete.
this was done on the eu g8 power , for update qpe30.79.124 , but i guess this will work on all versions since the process is the same ...
for people reading this, and don’t have root / want root, just read this thread:
Confirming success with this. I downloaded the whole ZIP, extracted boot.img and used Magisk App's built-in feature to mod the boot img. Afterward, I reflashed boot partition via fastboot. Thanks, all!
Success on Sophia RETUS 80-51-5. Flashed 80-51-3 stock boot with fastboot, took update, extracted BOOT from 80-51-5, modified with Magisk and flashed the mod with fastboot. Back up and running.
I have twrp installed. Will this work?
No, I don't believe so.
3dekstron said:
I have twrp installed. Will this work?
Click to expand...
Click to collapse
As far as I know you will also have to flash the stock recovery before updating... not sure if the recovery has to match the stock rom build, like the boot.img does. You could also flash the entire latest stock rom using LMSA to update.
pjottrr said:
Since you are rooted, you probably found out the OTA update won’t install.
after 3 % it crashes, and no update is installed.
So this is what I did to get the latest update:
step 1: remove root access;
- reboot and hold volume down to get into fastboot mode
- connect to pc, and load original boot.img , I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
- I connected to LMSA, to make a backup, and download the new rom.
- I went to fastboot mode again and flashed the boot by using the command “fastboot flash boot boot.img ( the “old/current” one, not the one from the downloaded new image”
“fastboot reboot”
Click to expand...
Click to collapse
What does this mean (from above) and what results are to be expected?
I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
Click to expand...
Click to collapse
I'm guessing that a fail is expected since original boot.img is no longer installed (ie, rather the patched version is installed). Hopefully someone can elaborate
Also in the case of the Magisk systemless root method, will OTA announcements occur even though they can't be installed without first unrooting?
I wonder if there is not a few steps that could be cut off and streamlined this method, for example why isnt uninstalling magisk enough, since magisk restores the boot.img, also it backs up the original boot.img so instead of going through the whole LMSA thing it can be just copied to storage and flashed in fastboot, right?
TaZeR369 said:
I wonder if there is not a few steps that could be cut off and streamlined this method, for example why isnt uninstalling magisk enough, since magisk restores the boot.img, also it backs up the original boot.img so instead of going through the whole LMSA thing it can be just copied to storage and flashed in fastboot, right?
Click to expand...
Click to collapse
I just did that with a sofia retus phone on Android 11 for the new security update.
RPM31.Q1-54-13 to RPMS31.Q1-54-13-2.
1. Uninstall all Magisk modules and reboot
2. Uninstall Magisk and hit restore image
3. Uninstall Magisk completely and phone reboots
4. Accept OTA update (nervously)
5. Patch boot image with Magisk
6. Flash patched image with minimal adb and fastboot
7. Success!
this process does replace vanced youtube with factory youtube and youtube music, but it's easy to just replace them again in vanced manager.
I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!
I just flashed Lineage, rebooted, set up the phone, rebooted into recovery and then flashed Magisk.apk after renaming it to Magisk.zip. After a reboot I opened the Magisk app (which was automatically installed when flashing Magisk) for the first time and it prompted me to do some additional operations. It survived an OTA update so it should keep working in the future.
The firts mentioned method does not seem to work with the new Magisk 24.1
Does anyone have a solution to this?
(Never mind ..you need to uninstall the earlier version,then it will work)
sburry said:
I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!
Click to expand...
Click to collapse
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!
ldm21 said:
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!
Click to expand...
Click to collapse
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed
Rstment ^m^ said:
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed
Click to expand...
Click to collapse
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!
ldm21 said:
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!
Click to expand...
Click to collapse
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
I think this is the equivalent of flashing the apk as zip in custom recovery, which is deprecated.
I compared the official one with the first post and I think the following is missing in the first post:
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
From:
Installation
The Magic Mask for Android
topjohnwu.github.io
Poco has a vbmeta but i never executed this step. The instructions say that it is optional but they don't specify it.
I used the first post since LOS18.1 and no problems. Since LOS19.1 updates give me bootloops so after some repair tries (and failed twrp restore) I did a fresh install and did not take the updates anymore. No idea if it has something to do with magisk or patching vbmeta. Soon gonna try to update LOS with magisk disabled.
Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
Does this still apply to LOS20 and Magisk 25.2? After doing this, do I still need to extract the patched image?
Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful
[deleted]
johnr64 said:
Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful
Click to expand...
Click to collapse
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.
dangerousnerdrays said:
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.
Click to expand...
Click to collapse
lol... flashing patched image is all you need to do
Either via adb sideloading magisk.apk or manually flashing image both will suffice.
Just look at magisk app, if it doesn't say not installed then it is working
My thoughts about rooting stock MIUI on Xiaomi 11 Lite 5g NE (Lisa)
This week I'm still waiting for Bootloader, but checking about the possibilities.
Coming from Xiaomi Mi 9T (Davinci) – I owned the phone for 2+ years, used stock EEA first, then switched to Xiaomi.eu Weeklies and finally to Xiaomi.eu Stable.
Trough the time, I went from A9/MIUI 10 to A11/MIUI 12.5, and in parallel I experimented with all relevant Magisk version (Stable, Beta, Canary, Lite, Alpha and Custom Magisk) – curently I'm on Magisk Alpha 23018 (with Zygisk, DenyList, Shamiko – no more the old MagiskHide).
Through all that, I used my Davinci as daily driver, for private and business, and I never had any bigger issues. I hope for the similar experience with my new Lisa.
As you can see, I'm not a fan of custom ROMs (altough I experimented with some of them on my previous devices), hence I also plan for Lisa, at least for now, to stay on MIUI.
Stock MIUI:
1.AFAIK, there are two unofficial custom recoveries but they don't support A12 encryption on /Data and Internal memory, hence they are of limited use for rooting.
They can be used for ADB sideloading and probably with OTG stick and external SD card.
But they cannot install/flash from Internal memory, backup/restore to Internal memory, and generally they cannot backup /Data – specially, TWRP cannot be used for fixing /adb/data in case of magisk bootloops.
2.However, for the installation of Magisk, TWRP is NOT REQUIRED – although by (1), TWRP could be still used for e.g. flashing the Magisk zip from OTG stick.
3.Magisk can be alternatively installed by: installing Magisk app (no root yet), patching the extracted boot.img (in Magisk app), and flashing the patched boot img from Fastboot (therefore, by completely bypassing TWRP).
My Lisa came with EEA 12.5.7 and it was immediately updated to 12.5.8, hence I have downloaded the stock miui_LISAEEAGlobal_V12.5.8.0.RKOEUXM_700eb7116a_11.0.zip and unzipped – but unlike for e.g. Mi 9 series, the OTA package does not contain separated boot.img (192 MB).
Instead, it contains 13.2 GB payload.bin (SAR, Dynamic partitions, all in once) and when I tried, Magisk cannot patch, reporting that format is not supported.
4. There are still some other ways to install Magisk. Maybe, by backing up Boot to OTG stick / external SD card – the backed up boot.emmc.win file can be used as the boot img for patching.
Or by flashing the Magisk zip through TWR (from external SD /OTG) – but that might be risky in case of a brick, fixing may not be easy.
Xiaomi.eu:
Xiaomi.eu ROMs are essentially debloated MIUI. Usually they are even bette, specially if staying on Xiaomi.eu Stable releases (Weekly releases are essentially betas).
Since I was accustomed to Xiaomi.eu on my Davinci, I also planned to switch to Xiaomi.eu on my Lisa.
Currently, they have Stable 12.5.7 (A11), while Weeklies with MIUI 13 / A12 are around the corner (they will start once Xiaomi starts releasing MIUI 13 weekly Betas for Lisa)
5. Hence I have downloaded xiaomi.eu_multi_MI11LE_XM11Lite5GNE_V12.5.7.0.RKOCNXM_v12-11-fastboot.zip. Since there is no TWRP for Lisa, Xiaomi.eu ROM must be installed through Fastboot (unzip and run the batch script windows_fastboot_first_install_with_data_format.bat).
The zip file contains the boot.img and I just tried, Magisk (Alpha) can succesfuly patch – the patched img needs to be flashed from Fastboot to Boot (I cannot proceed for now since still waiting for BL to be unlocked).
If anything goes wrong, it will be just enough to flash the original Xiaomi.eu boot.img.
I already used the same procedure for installing Magisk to Davinci, however I used then TWRP/OF/SHRP (not Fastboot) to flash the patched boot img directly from the couche and the phone – this could even apply to Lisa, if placing the patched boot img to external SD or OTG stock.
Please correct me and/or comment about the other posssbilites about installing Magisk to MIUI on Lisa, specially with your results if you already tried.
I rooted my lisa by the patched boot.img method. Working like a charm! One thing to note is that you need to reinstall Magisk to the inactive slot soon after OTA but before rebooting since the device uses a/b partitioning. But now for some reason, the more dark mode options in the dark mode settings doesn't work anymore
varunkp said:
I rooted my lisa by the patched boot.img method. Working like a charm! One thing to note is that you need to reinstall Magisk to the inactive slot soon after OTA but before rebooting since the device uses a/b partitioning. But now for some reason, the more dark mode options in the dark mode settings doesn't work anymore
Click to expand...
Click to collapse
Which ROM are you talking please, Xiaomi.eu or the stock - if stock, please details (CN/Golobal/EEA and MIUI version like in the Settings/My Device)?
I'm asking because for EEA 12.5.8 (that I have) I don't see how can I get boot.img.
I downloaded the OTA zip but it does not contain boot.img, instead, there is 13.2 GB payload.bin inside - see my post above).
For Xiaimu.eu ni problem, their fastboot zip contains the images folder with boot img inside
zgfg said:
Which ROM are you talking please, Xiaomi.eu or the stock - if stock, please details (CN/Golobal/EEA and MIUI version like in the Settings/My Device)?
I'm asking because for EEA 12.5.8 (that I have) I don't see how can I get boot.img.
I downloaded the OTA zip but it does not contain boot.img, instead, there is 13.2 GB payload.bin inside - see my post above).
For Xiaimu.eu ni problem, their fastboot zip contains the images folder with boot img inside
Click to expand...
Click to collapse
I'm on the stock MIUI India edition. To get the boot.img, download the fastboot ROM. All the images will be in there. But you can also extract the boot.img from the payload file as well. The guide can be found here.
varunkp said:
I'm on the stock MIUI India edition. To get the boot.img, download the fastboot ROM. All the images will be in there. But you can also extract the boot.img from the payload file as well. The guide can be found here.
Click to expand...
Click to collapse
Ok, thanks, Payload_Dumper works
Since it is A/B device, should I flash to both slots?
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
zgfg said:
Ok, thanks, Payload_Dumper works
Since it is A/B device, should I flash to both slots?
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Click to expand...
Click to collapse
Just fastboot flash boot patched_boot.img should be enough. It'll flash the image to the active slot automatically.
Upon waiting the standard 168 hours, I successfully unlocked my new Lisa (Xiaomi 11 Lite 5g NE)
---
Since I had MIUI EEA 12.5.8 (A11), I downloaded the miui_LISAEEAGlobal_V12.5.8.0.RKOEUXM_700eb7116a_11.0.zip (use MIUI Downloader app from Playstore to make it easy).
Unzipped and found payload.bin inside - used Payload_Dumper (search on XDA) to extract boot.img
I installed Magisk Alpha 24001 app (the same will work for Magisk Stable or Magic Beta 2400x) and patched the boot.img.
I first tested does it boot correctly:
fastboot boot patched_boot.img
and then permanently flashed the Magisk:
fastboot flash boot patched_boot.img
New Magisk does no more support MagiskHide - use Zygisk+DenyList+Shamiko instead:
In Magisk app, enable Zygisk and reboot.
Then enable Enforce DenyList, open Configure DenyList, enable filter to show System and OS apps, find Google Play Services (GMS) and checkmark:
com.google.android.gms
com.google.android.gms.unstable
Additionally checkmark the other (like banking) apps you used to checkmark for MagiskHide in the old Magisk v23
E.g., I always checkmark Xiaomi stock Security (com.miui.securitycenter) and Safety Net checkers like YASNAC (download from Playstore - Magisk does no more include SafetyNet checker coming with the app).
Reboot again.
Since it is also good idea to hide this new Zygisk, I installed Shamiko (Magisk module) and disabled Enforce DenyList (Shamiko will read and take over from DenyList).
Reboot
Additionally, to hide init.rc, I installed InitRcHider module.
Finally to pass the SafetyNet (CTS, unlocked Bootloader), I installed USNF 2.2.1 (latest at the moment, like all the other modules I mention here).
Note: InitRcHider and Shamiko are not required for SN, but without Zygisk+DenyList+USNF you will not pass
Google Play was showing that Device is not certified - I deleted Cache and Data for Google Play Store app, rebooted and after some time Device was certified
Since Magisk does no more connect to the Modules Repo, use Fox Magisk Module Manager
---
Further, I installed AdAway hosts/root mode (don't forget to enable Systemless Hosts in Magisk, and reboot), Vanced YouTube root
By using SystemlessDebloater (find in Fox Mmm), I have debloated 40-something preinstalled system apps - attached is the config list for Debloater, if you want to keep certain apps (Facebook or so, remove those names from the list)
E.g., for Vanced YT, I first uninstalled all updates to YT and then used SystemlessDebloater to debloat the built in the system YT v17, then successfully installed Vanced YT root that requires YT v16.29.39
---
Since Riru is incompatible with Zygisk, use LSposed-Zygisk version. As LSPosed modules, I use GravityBox_R, CustoMIUIzer and HideMyApplist (HMA)
E.g. with HMA I detach (hide) YouTube and AndroidAuto (I still need to configure apps and hacks for AA - work in progress) - YT Vanced root and similarly the hacks for AA require particular old versions of YT or AA.
By detaching those apps from Playstore, I make sure that Playstore does not bother, and does not update by mistake (even mine) YT and AA
Also, banking and similar apps usually look for Magisk app, LSPosed, and LSPosed modules - if they find, they detect 'root'
You can use e.g. Oprek Detector (fromg Google Play):
- checkmark in DenyList
- use HMA to hide Magisk app, LSPosed and Lsposed modules (apps) from Oprek Detector.
As a result, Oprek Detector will no more find root
Use that as a proof of concept for hiding the root from banking apps (altough, some of them may require additional steps)
Thanks to @HimanshuRaj (his TG support and his SHRP - another thread), I have now both Magisk and permanent TWRP (more precisely, SHRP), both in the patched boot.img:
- fastboot boot to SHRP
- from SHRP, flash SHRP img to Ramdisk -Recovery
- Stay in SHRP and flash the Magisk apk renamed to zip file
Normal booting boots to Sydtem/Magisk and rebooting to Recovery boots to Magisk
Thanks a lot @zgfg for the guide!
I'm going to save this thread as in the future it's possible I will try to root my mobile following your instructions.
Now, one more successful experiment:
- Magisk Alpha notified about the update (to 24102)
- hence I updated the Magisk Alpha app and then took the Direct update for Magisk itself
It updated the boot img, but correctly keeping the previously installed permanent SHRP:
- 'normal' booting boots to System/Magisk
- rebooting to Recovery boots to SHRP
I followed your steps and it works fine, just making sure on how to get permanent SHRP
i have a fully functioning lisa now with magisk and a couple of modules, do i need to redo all of it when trying to install SHRP with your instructions?
and do i flash the patched magisk file or the default app apk?
for context: i tried installing shrp twice and performing backups with it but ended up having to clean install stock rom again, maybe it was because i was missing an sd card but i tried it using a pc and just pulling the backup to and from there
breakasteroid said:
for context: i tried installing shrp twice and performing backups with it but ended up having to clean install stock rom again, maybe it was because i was missing an sd card but i tried it using a pc and just pulling the backup to and from there
Click to expand...
Click to collapse
Permanent installation for SHRP (Lisa) was also covered (how-to) in the TG channel (link in SHRP thread, itsvOP post #1).
As said, I have permanently installed both Magisk v24.3 and SHRP v0 2 (from TG channel) into the Boot partition (since there is no Recovery partition) and I can boot into System with Magisk (normal boot) or to SHRP (boot to Recovery, with Vol+)
And in SHRP, Internal memory, USB-OTG and external SD work flawlessly
However, the SHRP supports only MIUI 12.5, (A11) not A12 (MIUI 13)
---
Anyway, more about rooting:
Just installed the Magisk module:
[MOD][Magisk][MIUI][v1.1]ALWAYS on display for Mi 10 Lite (monet)
Hi there! I made this Magisk module to enable more options to choose with the Always on display on monet and not only the annoying option of "10 seconds after tapping". Did it modifying the "AODSettings.smali" file inside an old AOD apk, where...
forum.xda-developers.com
and with that, I can finally use AOD really always (or scheduled), not only for 10 seconds as Xiaomi pushed to MiUI 12.5.8
zgfg said:
However, the SHRP supports only MIUI 12.5, (A11) not A12 (MIUI 13)
Click to expand...
Click to collapse
the question was rather if you flashed SHRP and magisk before or after installing all said modules and LSPosed but since SHRP isnt working it wont help me anymore
alright so i wont be able to use SHRP since i have A12 running the xiaomi.eu roms, thanks for the info!
breakasteroid said:
the question was rather if you flashed SHRP and magisk before or after installing all said modules and LSPosed but since SHRP isnt working it wont help me anymore
alright so i wont be able to use SHRP since i have A12 running the xiaomi.eu roms, thanks for the info!
Click to expand...
Click to collapse
Boot is /boot partition, Magisk staff (all modules, LSPosed, etc goes to /data partition
Hence the order does not matter.
Everything what is needed was explained above and in the TG channel, hence sorry I will not waste time drawing the architecture again
Anyway, when I took SHRP v0.2, and permanently flashed, I 'lost' Magisk for eg 5 minutes.
I made backup of boot partition in SHRP (it was no more stock but with SHRP), patched Magisk to the backed-up img, went back to SHRP and flashed to Boot. Since then I had back both Magisk patch and SHRP in the Boot, and when I booted back to System/Magisk I had all my 5 Magisk modules, LSPosed and it's 3 modules running
It's all about to understand what goes to different partitions Boot and Data, hence playing with Boot does not affect what was previously installed to Data
Anyway, SHRP is of no use for you (yet), but be aware that there TWRP does not support A12 yet, hence neither the derivatives like SHRP
---
And if you use patch and flash (in fastboot) method, you can install Magisk with no need for TWRP/SHRP
alright thanks, just had to make sure i didnt do stuff wrong and thats why i lost my data, thanks again for the info on TWRP and A12 not (yet) being available which was probably the reason how everything broke
anyone succeeded in rooting miui 13 Indian varient?
kindly share boot image patched
Today I updated my Xiaomi 11 lute 5g ne to MiUI 13 and my root has gone. So I have to use Magisk to patch boot.img. It created patched boot file but when I flash it to my phone and reboot, it freezes on MI logo screen. It didn't work like before. Please help me, thank you.
P/s: when I find rom I saw 2 files: boot.img & boot-gki.img. I only copied boot.img to my phone to patch.
vygavedha said:
anyone succeeded in rooting miui 13 Indian varient?
kindly share boot image patched
Click to expand...
Click to collapse
I was able to patch boot image extracted from payload bin and rooted with magisk
HUYDAY said:
Today I updated my Xiaomi 11 lute 5g ne to MiUI 13 and my root has gone. So I have to use Magisk to patch boot.img. It created patched boot file but when I flash it to my phone and reboot, it freezes on MI logo screen. It didn't work like before. Please help me, thank you.
P/s: when I find rom I saw 2 files: boot.img & boot-gki.img. I only copied boot.img to my phone to patch.
Click to expand...
Click to collapse
Were you able to figure a way out? I'm in the same situation where I've tried everything to root 13.0.3 and it gets stuck on boot logo everytime.
Hello! As written in the title, i updated my already rooted poco f3 to the latest miui 14.0.7 (european rom) and then proceded to flash magisk. I followed everything to a T (extract boot from payload, patch in magisk, check partitions) and flashed it in fastboot. The terminal said "flashed to boot_a succesfully" so i rebooted. After unlocking the phone though, just a few seconds later it starts reooting on its own and prompts me to the miui recovery. I tried flashing the patched boot image both to boot_a and boot_b after this error, but it keeps happening.
Any help? i just don't want to lose my data.
EDIT: Thankfully i made it. The error was caused by a magisk module, so in the adb shell just run magisk --remove-modules and the error should be solved. Info from https://topjohnwu.github.io/Magisk/...debugging,and automatically reboot the device.
Would it work again if i flashed the stock boot image?
Pillow fan said:
Would it work again if i flashed the stock boot image?
Click to expand...
Click to collapse
Yes, or you can reflash the ROM.zip (without data-format of course)
OrangeFox Recovery has a Magisk Module Manager built-in and lets you disable/remove individual Modules.
Otherwise, you can simply put an empty file called "disable" or "remove", into /data/adb/modules/your_module_here/
On the next boot, Magisk will take action accordingly.
Also, maybe this is easier for you, but you can simply use a TWRP / OrangeFox Backup of the boot-partition, to patch Magisk.
Then you can rename the Magisk-patched Boot.img back into "boot.emmc.win", put it into Backup folder and replace with original Boot backup file, and restore with TWRP/OF.
Doesn't require a PC.