Related
Please help me to root Samsung A7 2017. I need to root because I'd like to install Xposed. I found a few guides but they were confusing.
It's pretty easy:
On android 6
Install TWRP
Install superuser-r310-beta
That's it
On android 7 (last security patch)
IMPORTANT: If you have rooted previously with Magisk 14.x or Supersu, clean reinstall the ROM again through ODIN (erasing SYSTEM and DATA)
COPY MAGISK 15.1 in the external SD or in a USB
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Install MM Bootloader through ODIN, (Last Nougat has BOOTLOADER Locked, it doesn't work anymore OEM unlock. In the attachment there is one that I use)
Reboot your phone and soon enter again in Download mode
Install TWRP
https://forum.xda-developers.com/samsung-a-series-2017/development/xcc-t3591448
Reboot in recovery and FORMAT DATA
Install MAGISK 15.1 (1510)
REBOOT
This way works perfectly in NOUGAT last security patch and you won't have the issue about the delay of more than 5 sec when you unlock with PATTERN.
Hello, I would need help to root my device, if someone could bring me advice I'm taking, I own remote control software if it tempts someone to help me I'm up for it
Have you unlocked the bootloader and install TWRP first?
The bootloader is unlocked, TWRP is not installed, I had to read the forums to try to install TWRP but my phone is stuck on fastboot impossible to do anything
You can root very easily:
1. start the phone in fastboot mode
2. from a PC type command "fastboot boot twrp.img"
3. once in TWRP, install magisk.zip file (don't forget to follow new instructions for Magisk v22)
4. once Magisk has been installed, reboot to system
5. congrats, your phone is rooted now (without TWRP permanently installed)
hello
after updating to android 11, euxm version, I have problems rooting with magisk 22, I change the apk extension to zip, I install it from twrp, but on reboot it crashes and returns to twrp.
also i no longer see the internal memory folders in android - data
carabot said:
hello
after updating to android 11, euxm version, I have problems rooting with magisk 22, I change the apk extension to zip, I install it from twrp, but on reboot it crashes and returns to twrp.
also i no longer see the internal memory folders in android - data
Click to expand...
Click to collapse
You might have incompatible module installed (for example SafetyNet fix) - disable all modules temporarily, install Magisk and see if the phone starts.
I disabled all the modules before installing the recovery rom, however there is the uninstall of magisk 22.0 and safetynet fix?
carabot said:
I disabled all the modules before installing the recovery rom, however there is the uninstall of magisk 22.0 and safetynet fix?
Click to expand...
Click to collapse
Can you start the phone without Magisk installed?
yes
I solved by disabling modules from orange fox recovery,
how can i do to see the contents of the android folder, that is scoped storage?
carabot said:
yes
I solved by disabling modules from orange fox recovery,
how can i do to see the contents of the android folder, that is scoped storage?
Click to expand...
Click to collapse
You are contradicting yourself a little, you said that you disabled all modules before recovery ROM installation, now that you disabled them from Orange recovery. It might help to describe steps which you did and current status of your phone.
I had disabled them from magisk, but in the twrp they were active, and when I realized it I disabled them from twrp and I solved them.
p. s.
safetynet fix is compatible with android 11 and magisk 22?
i wouldn't ruin it again
carabot said:
I had disabled them from magisk, but in the twrp they were active, and when I realized it I disabled them from twrp and I solved them.
p. s.
safetynet fix is compatible with android 11 and magisk 22?
i wouldn't ruin it again
Click to expand...
Click to collapse
Yeah just hide magisk from all google apps and it will work fine, mine passes
Jooan92 said:
Hello, I would need help to root my device, if someone could bring me advice I'm taking, I own remote control software if it tempts someone to help me I'm up for it
Click to expand...
Click to collapse
Unlock bootloader
Flash a recovery (fastboot flash recovery nameofrecovery.img)
Reboot into recovery (fastboot reboot and hold power and volume up)
Load magisk zip on an EXTERNAL SD find it and flash
Boom
for scoped storage is there a solution?
carabot said:
I had disabled them from magisk, but in the twrp they were active, and when I realized it I disabled them from twrp and I solved them.
p. s.
safetynet fix is compatible with android 11 and magisk 22?
i wouldn't ruin it again
Click to expand...
Click to collapse
You need to reinstall safetynet fix after Android upgrade, installation script uses different files for different Android versions.
What issue exactly do you have with storage?
after the update open file manager and if I click on android - date I no longer see the folders
i tried to install safetynetfix from twrp but it gives me error
carabot said:
i tried to install safetynetfix from twrp but it gives me error
Click to expand...
Click to collapse
Install from magisk under the modules section, then install from storage
gave me mistake because i had wrong files
Just for notification. If safety net is important with you. Install latest stable xiaomi.eu rom v12.0.11.0. Safety net is passed and implement in rom. I 've installed it...Developers continue playing cat and mouse with Google
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.
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