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.
Related
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
Here's a quick guide for rooting your Fairphone 4.
DISCLAIMER
I'm not the author of this method, merely sharing the informations that can be found on fairphone community forums.
All credit goes to hirnsushi from fairphone community forum.
I will not be held responsible for any damage caused by this operation, flashing your device always implies a risk of manufacturing your very own plastic brick.
PREREQUISITES
- Unlocked bootloader
- Computer with adb & fastboot
- Magisk app installed on your device
- FP4's official stock boot.img
HOW TO ROOT
1. Copy the boot.img file on your device's internal memory
2. Patch the boot.img file using Magisk -> Installation -> Patch a file
3. Transfer the patched boot.img back to your computer
4. Reboot to fastboot: Power + vol up from off device OR adb reboot bootloader
5. Boot from the patched img by running: fastboot boot patched_boot.img where patched_boot.img is actually replaced with the path and name of your patched file
DO NOT FLASH THE PATCHED IMG. BOOT ONLY.
6. Your device will take much much more time to boot than usual, be patient.
7. Once booted, open Magisk, run a direct Install and reboot.
You are now rooted.
This will break your ability to use Google Pay. Though a workaround is described below.
[OPTIONAL]- PASS SAFETYNET AND GPAY CERTIFICATION
1. Download and enable the following Magisk mod:
- Riru module
- Riru’s universal SafetyNet’s fix 2.1.2
- SQLLite for ARM aarch64 devices
- GPay SQLLite Fix 2.5
2. Enable Magisk hide and hide Magisk from the following packages:
- Google Play Store
- Google Pay
- Google Play Services
3. Now the part that is very important to follow otherwise it will not work :
- Put your phone in Airplane mode
- Clear all data from:
Google Play
Google Pay
Google Play Service: remember, clear ALL data, not just cache, even for this one
- Reboot
- Toggle Airplane mode off
You should now have a rooted device that can be used to pay for groceries. How cool is that.
If Pay app states device is not certified, there is high chances you did not follow exactly the described steps.
I really like a rooted phone as always. I will wait till there is a way to reinstall the standard ROM. Then it will be safe for me to try.
I'm on the latest update and not able to unlock the bootloader. I enabled OEM unlocking in developer options and rebooted to bootloader. On the first screen it says "Device status: Locked" and doesn't react on any fastboot command. When I enter recovery and start fastboot, each command will fail (command not present in this implementation). Any hints?
Finally managed to unlock the bootloader. The trick was to use an USB2.0 port on my PC.
I live in US so don't have one in my hands yet. Has anyone done a .QCN dump of the phone yet? Do you program the phone with Firehose EDL? Are there qualcomm drivers? I have so many questions.
I tried it with the latest boot.img avaliable here ('cause I have the A.094 ROM version on my phone)
Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation
code.fairphone.com
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
And that works perfectly, that's my daily driving phone, and no problems
Generally speaking I can only but encourage you to register and browse the fairphone forum as there are much much more resources, guides and activity around the fairphone 4 than on xda.
I'm using latest magisk 24.1 and todays OTA fails. I tried with Zygisk on and off. In the magisk app under install there is a install to new slot thing but I feel like that's supposed to be used if it don't fail. will I brick my phone if i click it?
edit:
found this on fp forum
Fixing OTA after rooting
Because my FP is rooted, I couldn’t install the update right away. Message: Couldn't update, installation problem The problem is that the boot partition gets modified when you root your phone and this prevents the OTA package from installing. It’s described well on Quora. This is how I was...
forum.fairphone.com
citroniais said:
I tried it with the latest boot.img avaliable here ('cause I have the A.094 ROM version on my phone)
Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation
code.fairphone.com
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
And that works perfectly, that's my daily driving phone, and no problems
Click to expand...
Click to collapse
My Build-Number say I am on:
FP4.FP3R.A.099.20220112
So it seems my Bootloader version should be A.099 but there is no file like this:
https://storage.googleapis.com/fairphone-source/FP4/A.099-boot.img
Is it okay to take a older boot img or another?
Latest seems to be
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
and before that:
https://storage.googleapis.com/fairphone-source/FP4/A.091-boot.img
yes I used 094 to root 099 yesterday, just don't flash the 094 or the modded 094.
I'm using latest magisk and safetynet-fix-v2.2.1, GPay.SQLite.Fix.v2.5, SQLite for ARM aarch64 devices.
Thomas.swe said:
yes I used 094 to root 099 yesterday, just don't flash the 094 or the modded 094.
Click to expand...
Click to collapse
okay, so you are on a magisk-boot-v-A.094? I thought Magisk, run a direct Install then is only able to patch your current running patched-A.094 boot.
Am I wrong?
I have rooted 099 with latest magisk 24.1 you only boot with the 094 versions to root the 099.
Thomas.swe said:
I have rooted 099 with latest magisk 24.1 you only boot with the 094 versions to root the 099.
Click to expand...
Click to collapse
Yes that it true, you are have root now.
But I think you are on the bootloader version A.094.
the 099 came from OTA so why whould bootloader be 094?
Thomas.swe said:
the 099 came from OTA so why whould bootloader be 094?
Click to expand...
Click to collapse
I am just thinking that you are on 094. Perhaps I am wrong.
But in step 5 you boot the patched 094 img and with this 094 boot image you run the direct magisk install on step 7. If I a not wrong magisk used the current running boot-image. So magisk patched your 094.
Perhaps I am wrong, I am not sure.
EDIT:
You are right @Thomas.swe Sorry for confusing.
See here: https://forum.fairphone.com/t/fp4-root-access-is-possible-maybe-a-bit-risky/76839/144
EDIT2:
@Eznaa does "our device will take much much more time to boot than usual, be patient." mean more than 20 minutes?
EDIT3:
No I used the wrong bootloader. Iode OS has its own bootloader-image upsi
I had root working using this method on A.116-boot.img. I then uninstalled Magisk, did an OTA (to A.128), did "Install Magisk to inactive Slot" (as I successfully did in older OTA updates), but it bootloops. If I `fastboot flash boot A.128-boot.img` it boots normally, but as expected, without root.
I tried an `adb wait-for-device shell magisk --remove-modules` to make sure no Magisk modules are causing the bootloop. I am on Magisk 25.1, btw.
Do you have any idea what could cause the Magisk-patched image to bootloop?
Hi,
Did you try to patch A.128 and boot on it ?
fastboot boot [image]
Please note : the best way to find an answer about any issue related to Fairphone is in the "Fairphone Community Forum" : forum.fairphone.com - The Fairphone users are not using that much XDA
I am thinking of buying Fairphone 4 and need magisk. Can anyone answer a question about the installation instructions above? Magisk website says to flash the magisk patched boot image but here the instruction is to first boot from the magisk patched image, not flash it, and then once booted run a direct install from the magisk app. What is the reason for this extra step?
Just a heads up. Root/Unlock voids FairPhone warranty unfortunately. Only reason I haven't bought this phone.
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.
I am trying to Unlock my bootloader, Install TWRP then install Magisk for the customizations. I connected my Mi Account on my phone, and I have to wait 5 more days from the 7 days wait period. Meanwhile I was wondering If there were any simple tutorials for Installing TWRP out here, or any specific channel/video you guys would recommend for my phone. which I can watch and prepare myself, while I wait.
I checked YouTube, there are a few good tutorials there, but they each do a slightly different method, or they mention that all the Xiaomi phones will have the same method but go on to mention that "for this specific X phone you will have to do slightly differently" and that's where It gets confusing.
I don't want to end up bricking my phone in the process, that's why I was looking to ask directly in the forums so I can get more relevant suggestions, rather than just watching a YouTube follow along video which the channel owner doesn't check comments on.
Any suggestions, recommendations welcome
Suggestion before flashing the ROM you need to read the whole page of the ROM because it's the number one thing that people missed up and bricking their phone because they don't read the whole post. Also backup your data.
percharnel said:
Suggestion before flashing the ROM you need to read the whole page of the ROM because it's the number one thing that people missed up and bricking their phone because they don't read the whole post. Also backup your data.
Click to expand...
Click to collapse
I'm just tryna install Magisk as the end goal. No plans for ROM currently. But thanks for the suggestion nontheless. Something to keep in mind in case I change my mind later
My advice for you is as follows:
Let TWRP go and don't use OpenGApps.
Use the things that are working flawlessly.
Take LOS Recovery instead of mighty, but outdated TWRP,
Take MindTheGApps instead of highly customizable OpenGApps.
(Think about LOS as your custom ROM).
I used to use both together with my Mi 8. But installing LOS, the recovery and GApps on my Poco F3 was possible within round about an hour. All this went well, while I watched Netflix and cuddled a beautiful woman on her Sofa. By the way - I had to install ADB and divers on her Surface Laptop at first.
Hi,
You could check out My Beginners guide post:
Also a Very important Note, "NEVER RE-LOCK YOUR BOOLOADER" with a custom recovery or Custom Rom installed, as this will BRICK your device and you will have to pay to get it unbricked.
The Re-lock could happen when you use the MIFlash Tool and select "Clean all and Lock".
.
SDK Platform Tools (ADB & Fastboot): https://developer.android.com/tools/releases/platform-tools
Xiaomi USB Driver: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
(link source: https://developer.android.com/studio/run/oem-usb)
OrangeFox Recovery: https://orangefox.download/device/alioth
Notes:
-During BL-Unlock, your phone will auto. factory reset.
-Unlike on many AOSP-ROMs, using a Custom Recovery on MIUI will cause OTAs to not work anymore as the MIUI Update relies on MIUI Recovery. Instead you have to manually flash each MIUI-update in your Custom Recovery.
-I'm suggesting OrangeFox Recovery, because it never failed me personally, and because it's simply much more modern than TWRP.
-On MIUI, Magisk (by default) will cause you to fail Google SafetyNet, which means Banking Apps, Netflix, and many other apps won't work. You will have to spoof Attestation to "Basic" by using a Magisk Module that changes the fingerprint. And you'll have to hide Magisk from Play Services (.gms and .gms.unstable specifically) and user-apps that check for Magisk/Root.
Boot to Fastboot Mode (Power + Vol Down),
extract "recovery.img" from OrangeFox.zip,
Open Terminal inside Platform-Tools folder and do "fastboot boot <path_to_recovery.img>"
To install OrangeFox, go to its Menu and tap "Install current Recovery" (something along those lines)
To install Magisk, you can rename Magisk.apk to Magisk.zip and flash it in Custom Recovery (only TWRP or OrangeFox!, other recoveries may not be able to install anything other than the ROM ZIP file). It's the easy method of getting Magisk, however flashing Magisk.zip in Recovery isn't supported anymore by TopJohnWu.
Recommended way is to obtain the boot.img and patch it with the Magisk App. I personally do a Boot Backup with OrangeFox Recovery, patch the backup file, and restore the magisk-patched Boot file with OFox.
My break is over, so I'll have to cut here, but I think I have my socials linked in my profile. if you need more help you can message me privately on TG
cyanGalaxy said:
SDK Platform Tools (ADB & Fastboot): https://developer.android.com/tools/releases/platform-tools
Xiaomi USB Driver: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
(link source: https://developer.android.com/studio/run/oem-usb)
OrangeFox Recovery: https://orangefox.download/device/alioth
Notes:
-During BL-Unlock, your phone will auto. factory reset.
-Unlike on many AOSP-ROMs, using a Custom Recovery on MIUI will cause OTAs to not work anymore as the MIUI Update relies on MIUI Recovery. Instead you have to manually flash each MIUI-update in your Custom Recovery.
-I'm suggesting OrangeFox Recovery, because it never failed me personally, and because it's simply much more modern than TWRP.
-On MIUI, Magisk (by default) will cause you to fail Google SafetyNet, which means Banking Apps, Netflix, and many other apps won't work. You will have to spoof Attestation to "Basic" by using a Magisk Module that changes the fingerprint. And you'll have to hide Magisk from Play Services (.gms and .gms.unstable specifically) and user-apps that check for Magisk/Root.
Boot to Fastboot Mode (Power + Vol Down),
extract "recovery.img" from OrangeFox.zip,
Open Terminal inside Platform-Tools folder and do "fastboot boot <path_to_recovery.img>"
To install OrangeFox, go to its Menu and tap "Install current Recovery" (something along those lines)
To install Magisk, you can rename Magisk.apk to Magisk.zip and flash it in Custom Recovery (only TWRP or OrangeFox!, other recoveries may not be able to install anything other than the ROM ZIP file). It's the easy method of getting Magisk, however flashing Magisk.zip in Recovery isn't supported anymore by TopJohnWu.
Recommended way is to obtain the boot.img and patch it with the Magisk App. I personally do a Boot Backup with OrangeFox Recovery, patch the backup file, and restore the magisk-patched Boot file with OFox.
My break is over, so I'll have to cut here, but I think I have my socials linked in my profile. if you need more help you can message me privately on TG
Click to expand...
Click to collapse
I'm considering to switch from latest TWRP 3.7.0_9-0 to OFR R11.1_3_A12 on my old dipper. But that dosn't play a role here, because I have some general questions about it that are the same for alioth.
Just want to try it out and see, if it's really so much better than TWRP like lots of people tried to tell me in the last years...
So may I ask you some vital questions?
1. From what I understood, it should be possible to flash OFR easily through my already installed TWRP on the device, right?
2. Which decryption methods does the A12-Branch of OFR support? A12 only or A11+A12 so that it's possible to dirty flash from A11 to 12?
3. In OFR there's an inbuild (and easy to handle?) direct management of the preinstalled Apps, right? This could be avery interesting feature for me, especially with regards to the slowly dying OpenGApps-Project that was imho the best way to customize GApps over the last few years...
If you are a visual learner just watch them carefully, watch the suggestions above they work great, works perfectly on OFOX too
Hi,
When my phone automatically updated to MIUI 14, a error message appeared and then, my root was lost...
Il tryed several times to get it back patching boot.img from Magisk.. (canary version included), but when I install patched.img my phone does not start and i have to get back to boot.img
Any ideas?
Rename magisk from apk to zip, and then flash the magisk zip from recovery
Saezrfff said:
Hi,
When my phone automatically updated to MIUI 14, a error message appeared and then, my root was lost...
Il tryed several times to get it back patching boot.img from Magisk.. (canary version included), but when I install patched.img my phone does not start and i have to get back to boot.img
Any ideas?
Click to expand...
Click to collapse
Hi,
Boot your F3 into fastboot mode and connect to a PC,
Download "Temporary Recovery" and unzip, run the "RUN ME Temporary TWRP A13-Orange Fox Recovery.bat" file and choose TWRP.
Once rebooted select: Advanced from within TWRP and tap "Flash current TWRP", copy over the included Magisk files into the internal memory (I use a OTG adaptor and USB Stick), install Magisk V26.1.apk, when in recovery you can install Magisk as a .apk format.
Included are the files i use when switching between roms, included are the latest, Magisk V26.1 and Magisk Delta, it also includes the latest versions of TRWP/OrangeFox recovery and other goodies,
I hope it helps
It's possible that the MIUI 14 update may have caused compatibility issues with your previous root method. You could try using a different root method or a different version of Magisk. Additionally, make sure you are following the correct steps for patching the boot.img file and installing it. If the issue persists, you may need to wait for an updated version of Magisk or seek assistance from the Magisk community.
you can try patching Boot.img instead of flashing Magisk.zip
you can do a OrangeFox/TWRP Backup of Boot-partition and patch the resulting "boot.emmc.win" file in Magisk App, because it's actually just a normal partition-image.
then flash the magisk-patched image file.
no pc required. just a custom recovery.
you can try the new Magisk v26.1, or Magisk Alpha (not affiliated with official Magisk).
i use Magisk v26.1 Official but I'm on AOSP