Related
device : chinese RN8P
rom : chinese swapped to global
hi,
tried to find another method to root the RN8P, chinese version with global rom
followed this guide to patch boot.img, extracted from global rom package 10.4.1.0 global
https://romprovider.com/2019/01/create-pre-rooted-patched-boot-img-magisk/
in the end, we should theorically root after flash patched.img in fastboot mode, and install magisk after that with magisk manager
for now patched boot.img by magisk manager with magisk20.zip make a patched img 10mb...the original file makes 60mb
any ideas from experts?
thanx
https://drive.google.com/open?id=1f3DzBwZ_xfwy6ES6YElQQJy6ZVe4CS3P
harmakhis said:
device : chinese RN8P
rom : chinese swapped to global
hi,
tried to find another method to root the RN8P, chinese version with global rom
followed this guide to patch boot.img, extracted from global rom package 10.4.1.0 global
https://romprovider.com/2019/01/create-pre-rooted-patched-boot-img-magisk/
in the end, we should theorically root after flash patched.img in fastboot mode, and install magisk after that with magisk manager
for now patched boot.img by magisk manager with magisk20.zip make a patched img 10mb...the original file makes 60mb
any ideas from experts?
thanx
https://drive.google.com/open?id=1f3DzBwZ_xfwy6ES6YElQQJy6ZVe4CS3P
Click to expand...
Click to collapse
make a backup of the patched boot.img with twrp. it will be like boot.emmc.win
rename .win by .img
i dont have twrp and you say to me to backup with twrp
You can try magisk in recovery
You can extract boot without installing twrp
Get twrp working on the phone and use command
Fastboot boot " twrp.img "
This will redirect you to twrp and you can use it without replacing the recovery of the phone and when you restart the device you will be using your phone normally
I tried to do the same thing
Fastboot boot patched_boot.img to test the img from magisk but the phone boot loop
Maybe i will try to backup boot using twrp and patch it with magisk
i dont know what they do with those phones but they were not such a pain in the ass to mod in the past
10.5.10.IN11BA (European version):
I dumped the boot.img with payload dumper from the "OnePlus8ProOxygen_15.E.19_OTA_019_all_2007021957_d0064.zip" file and patched it with magisk
Note: This is for the European variant of version 10.5.10(.IN11BA)
Download links:
boot.img: https://drive.google.com/file/d/1q9BP31PO6tELbTR-4bWD8pP19_g_VSU0/view?usp=sharing
patched boot.img: https://drive.google.com/file/d/1peDOwsvoUVIoEkp8WZ3jGoRvyqd46MOo/view?usp=sharing
You can use these files to root your OP8Pro with the following guide: https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-how-to-root-oneplus-8-pro-twrp-t4083981
10.5.10.IN11AA (global version):
I dumped the boot.img with payload dumper from the "OnePlus8ProOxygen_15.O.19_OTA_019_all_2005301411_63c531a1a94a4fc1.zip" file, you'll have to patch it yourself with magisk
Here is the boot.img file for 10.5.10.IN11AA : https://gofile.io/d/yavZRg
You can patch it using the following steps (source: Magisk github)
Copy the boot.img file to your device
Download and install the latest Magisk Manager
Press Install → Install → Select and Patch a File, and select your stock boot.img file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. (If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img)
Flash the patched boot image to your device with adb:
Code:
fastboot flash boot /path/to/magisk_patched.img
reboot
Please give me feedback if it worked or not
Hello, Thanks for this work. Just a beginner's question, I suppose you must already have an unlocked bootloader to use your files.
vigneras said:
Hello, Thanks for this work. Just a beginner's question, I suppose you must already have an unlocked bootloader to use your files.
Click to expand...
Click to collapse
Yes of course.
Is this patched with magisk 20.4,not magisk canary? And fingerprint sensor works after that?
Thanks, I would come back after unlocking the bootloader
janitor9 said:
Yes of course.
Is this patched with magisk 20.4,not magisk canary? And fingerprint sensor works after that?
Click to expand...
Click to collapse
Yes indeed, patched with 20.4 and fingerprint works fine. I recommend backing up the persist.img just to be sure
Hey brother, any chance of patching 10.5.10AA? Thank you in advance. Cheers
Sent from my IN2025 using Tapatalk
rawhide85 said:
Hey brother, any chance of patching 10.5.10AA? Thank you in advance. Cheers
Sent from my IN2025 using Tapatalk
Click to expand...
Click to collapse
Here is the boot.img file for 10.5.10.IN11AA : https://gofile.io/d/yavZRg
You can patch it using the following steps (source: Magisk github)
Copy the boot.img file to your device
Download and install the latest Magisk Manager
Press Install → Install → Select and Patch a File, and select your stock boot.img file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. (If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img)
Flash the patched boot image to your device with adb:
Code:
fastboot flash boot /path/to/magisk_patched.img
reboot
Unable to boot from patched image. Unable to boot from normal boot patched with magisk ... as a hole - no root with 10.5.10BA
Can someone suggest solution?
Lucifer4o said:
Unable to boot from patched image. Unable to boot from normal boot patched with magisk ... as a hole - no root with 10.5.10BA
Can someone suggest solution?
Click to expand...
Click to collapse
Boot the twrp and flash magisk
cultofluna said:
Boot the twrp and flash magisk
Click to expand...
Click to collapse
Same result - boot loop.
Does anyone have the stock boot.img for the Global version of 10.5.10? For the IN2017 OnePlus 8. IN21AA.
10.5.11 EU Patched pls ??
alxioa said:
10.5.11 EU Patched pls ??
Click to expand...
Click to collapse
Found it here:
https://forum.xda-developers.com/showpost.php?p=83137417&postcount=424
Flying Fox said:
Found it here:
https://forum.xda-developers.com/showpost.php?p=83137417&postcount=424
Click to expand...
Click to collapse
Thanks my friend
hi, sadly the payload unzip doesn't work on my computer. I am urgently looking for the boot.img for 10.5.10.IN21BA. Can anyone help me? i can't find it on the net.
So I' can't root my phone anymore after upgrading.
First I tried my usual method that I used on my Pixel 3a XL running the latest Android 12 image.
- Extracted the boot.img from the OTA pack using "Payload-dumper-go".
- Copied up the boot.img to phone.
- Install Magisk Canary on the phone.
- Rooted the boot.img, copied it to PC.
- Booted it from fastboot.
- Tried direct install.
Crashdump mode. So clearly, no go.
Some helpful person (Mr. Intoxicated.mad from the Telegram group) posted some instructions.
1) Have Magisk Manager installed
2) Download rooting files and extract on PC
3) Copy boot.img and vendor_boot.img to Download folder
4) Open Magisk Manager and click top Install and patch boot.img. When done, go back and repeat the process for vendor_boot.img
5) Move both patched images to adb directory on your pc along with vbmeta.img
6) Run this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
Unfortunately, this did not work either.
It flashes, the phone boots, but Magisk Manager shows up like there is no actual root.
Tried the same steps with flash boot_a and flash boot_b and also flash boot (so just everything), but no change.
So I've tried:
- Magisk Canary direct install: Root works, but Direct Install -> CrashDump soft brick
- Magisk stable (23.0) with flash -> No root
- Magisk stable (23.0) with boot via fastboot -> No root, not even temporary
I'd appreciate any tips, guides!
Maybe Canary + root both vendor_boot and boot images? I haven't tried that one yet...
Did you try https://t.me/s/magiskalpha ? It's all about OOS12 or AOSP (custom) A12 ?
felek73 said:
Did you try https://t.me/s/magiskalpha ? It's all about OOS12 or AOSP (custom) A12 ?
Click to expand...
Click to collapse
Oh this is a custom Magisk build? I'll try that, thank you!
Will report back if it worked.
I've still got to do some work calls (without call recording that'll be FUN!) and then I'll attempt this.
You can also try this solution (https://forum.xda-developers.com/t/...xyysds-root-toolbox-coloros-oxygenos.4341167/) for Open Beta 3. I am curious if it works for you.
Which region is your OP9?
felek73 said:
Did you try https://t.me/s/magiskalpha ? It's all about OOS12 or AOSP (custom) A12 ?
Click to expand...
Click to collapse
This worked great! I just grabbed the latest APK I could find from the channel, installed it via Direct Install and voila'!
Basic steps:
- Extract the ZIP, use payload-dumper-go to get boot.img
- Copy up boot.img to phone
- Install this Alpha Magisk version, open boot.img from Magisk Manager
- Copy new patched image from Downloads folder to your PC
- Use Fastboot to boot this patched image, you have root at this point (but only temporary)
- Go into Magisk Manager and go for Direct Install
h8Aramex said:
This worked great! I just grabbed the latest APK I could find from the channel, installed it via Direct Install and voila'!
Basic steps:
- Extract the ZIP, use payload-dumper-go to get boot.img
- Copy up boot.img to phone
- Install this Alpha Magisk version, open boot.img from Magisk Manager
- Copy new patched image from Downloads folder to your PC
- Use Fastboot to boot this patched image, you have root at this point (but only temporary)
- Go into Magisk Manager and go for Direct Install
Click to expand...
Click to collapse
What region is your phone?
l_mike said:
You can also try this solution (https://forum.xda-developers.com/t/...xyysds-root-toolbox-coloros-oxygenos.4341167/) for Open Beta 3. I am curious if it works for you.
Which region is your OP9?
Click to expand...
Click to collapse
I haven't tried that one yet. I saw it yesterday but today it just would not pop up today while I was looking for it.
My phone is EU (Europe) - 12GB/256GB OnePlus 9 Pro LE2123 , ordered directly from the OnePlus online store.
Could you extract your boot.img? I am also with eu, maybe i would had less steps to make
Also, does the call recording work on a12?
h8Aramex said:
This worked great! I just grabbed the latest APK I could find from the channel, installed it via Direct Install and voila'!
Basic steps:
- Extract the ZIP, use payload-dumper-go to get boot.img
- Copy up boot.img to phone
- Install this Alpha Magisk version, open boot.img from Magisk Manager
- Copy new patched image from Downloads folder to your PC
- Use Fastboot to boot this patched image, you have root at this point (but only temporary)
- Go into Magisk Manager and go for Direct Install
Click to expand...
Click to collapse
So just do normal steps but use alpha magisk instead of stable? Can I use latest canary?
Moe2003 said:
So just do normal steps but use alpha magisk instead of stable? Can I use latest canary?
Click to expand...
Click to collapse
Apparently not, see OP.
terlynn4 said:
Apparently not, see OP.
Click to expand...
Click to collapse
He linked the telegram channel for canary magisk and said he grabbed the latest that he could find there, soooo
Moe2003 said:
He linked the telegram channel for canary magisk and said he grabbed the latest that he could find there, soooo
Click to expand...
Click to collapse
The telegram channel is for alpha, not canary. The whole OP is about how canary didn't work.
I just installed alpha myself, and against my better judgment I'm about to attempt the upgrade from OB3 to stable.
terlynn4 said:
The telegram channel is for alpha, not canary. The whole OP is about how canary didn't work.
I just installed alpha myself, and against my better judgment I'm about to attempt the upgrade from OB3 to stable.
Click to expand...
Click to collapse
Ok I'm stupid I thought canary and alpha were the same haha
l_mike said:
Also, does the call recording work on a12?
Click to expand...
Click to collapse
With Skvalex Call Recording + Root, yes it does. I never used the OnePlus call recorder thing because I saw it tells the other half that they are being recorded or something. Which just makes the entire conversation hostile, awkward. People know that I record them and they love that they can just dictate all their orders and crap.
h8Aramex said:
So I' can't root my phone anymore after upgrading.
First I tried my usual method that I used on my Pixel 3a XL running the latest Android 12 image.
- Extracted the boot.img from the OTA pack using "Payload-dumper-go".
- Copied up the boot.img to phone.
- Install Magisk Canary on the phone.
- Rooted the boot.img, copied it to PC.
- Booted it from fastboot.
- Tried direct install.
Crashdump mode. So clearly, no go.
Some helpful person (Mr. Intoxicated.mad from the Telegram group) posted some instructions.
1) Have Magisk Manager installed
2) Download rooting files and extract on PC
3) Copy boot.img and vendor_boot.img to Download folder
4) Open Magisk Manager and click top Install and patch boot.img. When done, go back and repeat the process for vendor_boot.img
5) Move both patched images to adb directory on your pc along with vbmeta.img
6) Run this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
Unfortunately, this did not work either.
It flashes, the phone boots, but Magisk Manager shows up like there is no actual root.
Tried the same steps with flash boot_a and flash boot_b and also flash boot (so just everything), but no change.
So I've tried:
- Magisk Canary direct install: Root works, but Direct Install -> CrashDump soft brick
- Magisk stable (23.0) with flash -> No root
- Magisk stable (23.0) with boot via fastboot -> No root, not even temporary
I'd appreciate any tips, guides!
Maybe Canary + root both vendor_boot and boot images? I haven't tried that one yet...
Click to expand...
Click to collapse
I have always rooted my phones, right now i am rooted on OOS 11 for OnePlus 9 Pro, should I follow the tutorial provided at [GUIDE] [Magisk] [Unlock / ROOT / Keep Root] ? Not sure if it is updated for OOS 12 or not yet.
l_mike said:
Could you extract your boot.img? I am also with eu, maybe i would had less steps to make
Click to expand...
Click to collapse
It's 40MB unfortunately so I don't think XDA would let me attach it.
Also try to source most steps, files from "trusted places". Don't run these "packs" you can find in Google and whatnot. Not that I personally would ever try to harm any of our fellow XDA members, but you get the idea. The internet and people can be nasty.
You can do "payload-dumper-go.exe -p boot payloadfile" and then it only extracts the payload.
Also one thing people!
For me, something installed a C:\Android\ folder with Fastboot and ADB.
ALWAYS MAKE SURE TO USE LATEST, OFFICIAL FASTBOOT AND ADB!!!!!
I know. Lot of exclamation marks and bold font.
But I've spent SO MUCH time because of this.
Even though I've had the "platform-tools" folder added to my PATH, this other thing appeared higher in the list for Windows.
So.
1) Open CMD.
2) Type "where fastboot"
Then you can make sure if you are using the one you want.
Where to get a "good fastboot"?
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Extract it, and you can add it to Path.
How to add to Path? In Win10/11, type "Path" in Start. And "Edit system environment variables" comes up.
Then click "Environment Variables" on the bottom of the newly opened System Properties window.
Double click "Path" , "New" and then just paste in the path. Like: C:\junk\platform-tools-123\
You don't have to mess with all this though. But ALWAYS make sure you are running the adb/fastboot you want!
tazoman said:
I have always rooted my phones, right now i am rooted on OOS 11 for OnePlus 9 Pro, should I follow the tutorial provided at [GUIDE] [Magisk] [Unlock / ROOT / Keep Root] ? Not sure if it is updated for OOS 12 or not yet.
Click to expand...
Click to collapse
Thank you! Unfortunately, this does not work; but there is a solution in the thread. I've just changed the topic to say [SOLVED], I forgot about it, sorry.
h8Aramex said:
Thank you! Unfortunately, this does not work; but there is a solution in the thread. I've just changed the topic to say [SOLVED], I forgot about it, sorry.
Click to expand...
Click to collapse
Later on how would we switch to canary or beta if it works again, and did u clean flash oos 12 or just update? Any bugs?
Moe2003 said:
Later on how would we switch to canary or beta if it works again, and did u clean flash oos 12 or just update? Any bugs?
Click to expand...
Click to collapse
Well, root definitely works (tried with Call Recorder).
You can simply uninstall the Magisk Manager, grab whichever you want (stable, canary) and then patch the latest boot.img. Just like now. Nothing tricky honestly. Once you update to a new system version, your boot.img will return to stock/unrooted anyway.
Though, Canary is like... super-alpha. It's supposed to be bleeding-edge, the freshest. So it's weird Canary failed, while Alpha works fine.
I updated via OTA. I don't think OnePlus provides flashable ZIPs at all. To do a Pixel like, full fastboot "-w" wipe update. You could upgrade and then wipe. But other than that...
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.
is it available ?
extract the UL you've downloaded on Asus home page/Rog phone 6/download page to get payload.bin
Use Dumper to get original boot.img (abt 101Mb via CMD)
Use magisk manager to patch the boot.img - get patched_boot.img
Flash patched_boot.img via ADB fastboot CMD in Windows 7/10/11.
Et voila, you have root for a13.
oh just patched the boot img ? i see okay thanks man appreciated it
I'm on already A13 with CN ver - rooted to change COUNTRY code to WW and flash back to WW original stock. Now everything is perfect. CN - A13 version is sudden lagged can not touch anything and force stop. Feel crazy. )