Develop Bugs

Help on custom rom RR/CM13 install magisk

I try on 551ml with RR/CM13 rom (fresh install) but magisk still not able to install correctly.
Here are the steps i did
1) Using magisk modder v3.1 from xda forum (this auto patch is for original zf2 rom i think)
a) Install RR v5.7.4 rom with clean format
b) after boot into phone, install supersu from google play and full unroot
c) Unlock MM bootloader (using mogisk modder v3.1) from fastboot
d) from TWRP 3.0.2-M1 install Magisk-v6_repack_for_zf2_601.zip
e) TWRP install phh-superuser-17-magisk-x86-fix.zip
f) back to phone and install magisk apk, still shows as unroot phone only.
2) Using original magisk post v6
a) Install RR rom with clean format
b) after boot into phone, install supersu from google play and full unroot
c) from TWRP 3.0.2-M1 install Magisk-v6.zip
d) TWRP install phh-superuser-17-magisk.zip
e) back to phone and install magisk v1.2 apk, still shows as unroot phone only.
Anyone using CM13 or RR rom able to install magisk in Zf2? I only see the official rom able to install magisk, I would appreciate for help.

andychau99 said:
I try on 551ml with RR/CM13 rom (fresh install) but magisk still not able to install correctly.
Here are the steps i did
1) Using magisk modder v3.1 from xda forum (this auto patch is for original zf2 rom i think)
a) Install RR v5.7.4 rom with clean format
b) after boot into phone, install supersu from google play and full unroot
c) Unlock MM bootloader (using mogisk modder v3.1) from fastboot
d) from TWRP 3.0.2-M1 install Magisk-v6_repack_for_zf2_601.zip
e) TWRP install phh-superuser-17-magisk-x86-fix.zip
f) back to phone and install magisk apk, still shows as unroot phone only.
2) Using original magisk post v6
a) Install RR rom with clean format
b) after boot into phone, install supersu from google play and full unroot
c) from TWRP 3.0.2-M1 install Magisk-v6.zip
d) TWRP install phh-superuser-17-magisk.zip
e) back to phone and install magisk v1.2 apk, still shows as unroot phone only.
Anyone using CM13 or RR rom able to install magisk in Zf2? I only see the official rom able to install magisk, I would appreciate for help.
Click to expand...
Click to collapse
Lol, ZE55xML_Modder*
RR isn't supported I think. I have AICP 11.0 with MM blobs and magisk works fine. If you have any question related to the tool, you can ask me, i'm the dev of that.
Inviato dal mio ASUS_Z00A utilizzando Tapatalk

andychau99 said:
I try on 551ml with RR/CM13 rom (fresh install) but magisk still not able to install correctly.
Here are the steps i did
1) Using magisk modder v3.1 from xda forum (this auto patch is for original zf2 rom i think)
a) Install RR v5.7.4 rom with clean format
b) after boot into phone, install supersu from google play and full unroot
c) Unlock MM bootloader (using mogisk modder v3.1) from fastboot
d) from TWRP 3.0.2-M1 install Magisk-v6_repack_for_zf2_601.zip
e) TWRP install phh-superuser-17-magisk-x86-fix.zip
f) back to phone and install magisk apk, still shows as unroot phone only.
2) Using original magisk post v6
a) Install RR rom with clean format
b) after boot into phone, install supersu from google play and full unroot
c) from TWRP 3.0.2-M1 install Magisk-v6.zip
d) TWRP install phh-superuser-17-magisk.zip
e) back to phone and install magisk v1.2 apk, still shows as unroot phone only.
Anyone using CM13 or RR rom able to install magisk in Zf2? I only see the official rom able to install magisk, I would appreciate for help.
Click to expand...
Click to collapse
1 install Magisk-v6_repack_for_zf2_601.zip
2 install supersu v.2.7.6 magisk.zip
3 install phh-superuser-17-magisk-x86-fix.zip
Back to phone and install magisk apk, superuser.apk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Chuckskullz said:
1 install Magisk-v6_repack_for_zf2_601.zip
2 install supersu v.2.7.6 magisk.zip
3 install phh-superuser-17-magisk-x86-fix.zip
Back to phone and install magisk apk, superuser.apk
Click to expand...
Click to collapse
Is it necessary to flash two superuser apps? Only flash either SuperSU or phh's Superuser.
Sent from my ASUS_Z00AD using XDA Labs

Cm 13 has its own su. You would need to find out how to remove that before you did any of this!
Sent from my ASUS_Z00AD using Tapatalk

krasCGQ said:
Is it necessary to flash two superuser apps? Only flash either SuperSU or phh's Superuser.
Sent from my ASUS_Z00AD using XDA Labs
Click to expand...
Click to collapse
Yes , flash two superuser
---------- Post added at 05:35 AM ---------- Previous post was at 05:19 AM ----------
I'm flash
1.magisk v6 repack
2.supersu.magisk 2.76
Reboot
Twrp mout check system delete su /system/xbin
Terminal command
echo BINDSYSTEMXBIN=true"> /data/.supersu
echo SYSTEMLESS=true"> /data/.supersu
3.install supersu- v.2.78SR in systemless
4.suhide 0.53
Reboot
If bootloop recovery flash magisk v6 repack
Check magisk manager 1.2 toggle not work you must flash phh supersu and install app Enable toggle
You can flash xposed-systemless v.86.2 x86
# sorry i'm Eng bad

I can update to Magisk v.7

Full Unroot ?
Chuckskullz said:
Yes , flash two superuser
---------- Post added at 05:35 AM ---------- Previous post was at 05:19 AM ----------
I'm flash
1.magisk v6 repack
2.supersu.magisk 2.76
Reboot
Twrp mout check system delete su /system/xbin
Terminal command
echo BINDSYSTEMXBIN=true"> /data/.supersu
echo SYSTEMLESS=true"> /data/.supersu
3.install supersu- v.2.78SR in systemless
4.suhide 0.53
Reboot
If bootloop recovery flash magisk v6 repack
Check magisk manager 1.2 toggle not work you must flash phh supersu and install app Enable toggle
You can flash xposed-systemless v.86.2 x86
# sorry i'm Eng bad
Click to expand...
Click to collapse
Do you need to make a Full unroot before ?

pashise said:
Do you need to make a Full unroot before ?
Click to expand...
Click to collapse
No.

Rooting the Pixel XL with Magisk

So I just got a Pixel XL and have unlocked the bootloader, but now I'm trying to root and I'm very confused. I have a few questions:
Should I be using TWRP RC1 or RC2? I'm currently on 3.1.0-0RC2 but I hear RC2 has weird issues with restoring/making Nandroids but I can't tell if that refers to the RC2 of a different build or what... The other issue is the TWRP page for Marlin only lists RC2 for v3.1.0, there is no RC1
Is it possible to get MagiskSU running and installed without a custom kernel - if possible I'd like to stick to the stock kernel
Can I use Magisk Modules or am I stuck in Core Only mode?
Any help would be appreciated, thanks!

CarteNoir said:
So I just got a Pixel XL and have unlocked the bootloader, but now I'm trying to root and I'm very confused. I have a few questions:
Should I be using TWRP RC1 or RC2? I'm currently on 3.1.0-0RC2 but I hear RC2 has weird issues with restoring/making Nandroids but I can't tell if that refers to the RC2 of a different build or what... The other issue is the TWRP page for Marlin only lists RC2 for v3.1.0, there is no RC1
Is it possible to get MagiskSU running and installed without a custom kernel - if possible I'd like to stick to the stock kernel
Can I use Magisk Modules or am I stuck in Core Only mode?
Any help would be appreciated, thanks!
Click to expand...
Click to collapse
Go here and search for Installation Instructions: [Unofficial] Google Pixel family support by goodwin_c
Go here for the latest Magisk/Magisk Manager Pixel/Pixel XL files.

Homeboy76 said:
Go here and search for Installation Instructions: [Unofficial] Google Pixel family support by goodwin_c
Go here for the latest Magisk/Magisk Manager Pixel/Pixel XL files.
Click to expand...
Click to collapse
Hi there, I went to that thread but it has no instructions, just discussion. I had a look for instructions but could only find other threads. I followed what they said (fastboot boot twrp.img => flash twrp.zip => reboot recovery => flash magisk.zip => flash twrp.zip => reboot system) but the root doesn't work (despite all recovery logs saying everything worked properly), and I get this when I open MagiskManager:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

CarteNoir said:
Hi there, I went to that thread but it has no instructions, just discussion. I had a look for instructions but could only find other threads. I followed what they said (fastboot boot twrp.img => flash twrp.zip => reboot recovery => flash magisk.zip => flash twrp.zip => reboot system) but the root doesn't work (despite all recovery logs saying everything worked properly), and I get this when I open MagiskManager:
Click to expand...
Click to collapse
have you done a 2nd reboot? sometimes that's the charm...

Captain Hindsight said:
have you done a 2nd reboot? sometimes that's the charm...
Click to expand...
Click to collapse
I've done multiple reboots sadly. Still nothing.

@CarteNoir working for me on PA. I always flash magisk last. Twrp is working fine for me. perhaps twrp is flashing over magisk?

tdct12 said:
@CarteNoir working for me on PA. I always flash magisk last. Twrp is working fine for me. perhaps twrp is flashing over magisk?
Click to expand...
Click to collapse
I think that might be the case but I don't know how to stop it. I tried flashing Magisk after TWRP but still no dice. I tried flashing the ElementalX kernel as per the guides and it finally works, but I really don't want to have to use a custom kernel, I'd much rather just stick to the stock kernel. Is there any way I can get this working with the stock kernel?

tdct12 said:
@CarteNoir working for me on PA. I always flash magisk last. Twrp is working fine for me. perhaps twrp is flashing over magisk?
Click to expand...
Click to collapse
TWRP does not flash over magisk, never has and isn't now.
---------- Post added at 07:40 AM ---------- Previous post was at 07:38 AM ----------
CarteNoir said:
I think that might be the case but I don't know how to stop it. I tried flashing Magisk after TWRP but still no dice. I tried flashing the ElementalX kernel as per the guides and it finally works, but I really don't want to have to use a custom kernel, I'd much rather just stick to the stock kernel. Is there any way I can get this working with the stock kernel?
Click to expand...
Click to collapse
So the modified kernel hides your unlocked bootloader status, running the stock kernel means you will fail safetynet and thus negate using magisk to begin with. There is a patched stock kernel you can fastboot that patches the bootloader check but it needs to be fastbooted to the device. Thats if you can get magisk working with it.

pcriz said:
TWRP does not flash over magisk, never has and isn't now.
---------- Post added at 07:40 AM ---------- Previous post was at 07:38 AM ----------
So the modified kernel hides your unlocked bootloader status, running the stock kernel means you will fail safetynet and thus negate using magisk to begin with. There is a patched stock kernel you can fastboot that patches the bootloader check but it needs to be fastbooted to the device. Thats if you can get magisk working with it.
Click to expand...
Click to collapse

pcriz said:
TWRP does not flash over magisk, never has and isn't now.
So the modified kernel hides your unlocked bootloader status, running the stock kernel means you will fail safetynet and thus negate using magisk to begin with. There is a patched stock kernel you can fastboot that patches the bootloader check but it needs to be fastbooted to the device. Thats if you can get magisk working with it.
Click to expand...
Click to collapse
Hey there, took a look at that patched stock kernel but unfortunately couldn't get it to work. I tried following the standard installation steps up until the point where you're supposed to flash the ElementalX kernel, at which point I booted back to bootloader and used fastboot flash kernel to flash the patched stock kernel file, then I returned to recovery to flash TWRP again as per the flow of the instructions, however that didn't work and Magisk still shows as not installed/no root.
I then tried flashing stock images/uninstalling Magisk, then following the standard instructions all the way through, installing the ElementalX kernel along the way. I then rebooted, confirmed Magisk installed and was working correctly, then went back into the bootloader and used fastboot flash kernel to flash the patched stock kernel file. However again on rebooting to system I found that Magisk said no root/not installed.
Is ElementalX doing something other than removing the androidboot.verifiedbootstate flag in regards to making Magisk work? Or is there perhaps anywhere where I can find a TWRP flashable package version of the patched stock kernel?

CarteNoir said:
Hey there, took a look at that patched stock kernel but unfortunately couldn't get it to work. I tried following the standard installation steps up until the point where you're supposed to flash the ElementalX kernel, at which point I booted back to bootloader and used fastboot flash kernel to flash the patched stock kernel file, then I returned to recovery to flash TWRP again as per the flow of the instructions, however that didn't work and Magisk still shows as not installed/no root.
I then tried flashing stock images/uninstalling Magisk, then following the standard instructions all the way through, installing the ElementalX kernel along the way. I then rebooted, confirmed Magisk installed and was working correctly, then went back into the bootloader and used fastboot flash kernel to flash the patched stock kernel file. However again on rebooting to system I found that Magisk said no root/not installed.
Is ElementalX doing something other than removing the androidboot.verifiedbootstate flag in regards to making Magisk work? Or is there perhaps anywhere where I can find a TWRP flashable package version of the patched stock kernel?
Click to expand...
Click to collapse
So I think you would want to fastboot the stock boot.IMG. flash the kernel, then turn around and flash twrp, reboot, install magisk.
If Elemental is doing something more to make this work I don't know what it is, but essentially every custom kernel or kernel that comes packaged with a custom rom does the same thing.

[GUIDE][Android 11] How to ROOT OnePlus 7T

Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect.​
1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA
2-ENABLE USB DEBUGGING IN DEVELOPER OPTIONS
3-INSTALL 15 seconds ADB Installer v1.4.3 AND OnePlus_USB_Drivers_Setup.exe
4-CONNECT YOUR ONEPLUS 7T TO PC AND ALLOW USB DEBUGGING REQUEST
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UNLOCK BOOTLOADER (THIS PROCESS WILL ERASE ALL YOUR DATA)​GO TO C:\adb AND OPEN A Windows PowerShell (SHIFT+Right-Click)
Code:
adb devices
adb reboot bootloader
Code:
fastboot oem unlock
INSTALL MAGISK AND PATH boot.img​1-INSTALL Magisk-66e30a77(22006).apk
2-DOWNLOAD AND UNZIP boot.img
boot.img (GLOBAL) FROM OnePlus7TOxygen_14.O.25_OTA_0250_all_2103170010_42034d7f PAYLOAD.BIN
boot.img (EUROPE) FROM OnePlus7TOxygen_14.E.25_OTA_0250_all_2103162336_da326df80dc PAYLOAD.BIN
boot.img (INDIA) FROM OnePlus7TOxygen_14.I.25_OTA_0250_all_2103170010_f57745e564 PAYLOAD.BIN
3-PASTE boot.img IN THE ONEPLUS 7T ROOT DIRECTORY
4-Open Magisk
5-In "Magisk" select "Install"
"SELECT AND PATCH A FILE"
NOW SELECT boot.img FILE FROM OP7T ROOT DIRECTORY and "LET´S GO"
PATCHED boot.img = magisk_patched.zip (GLOBAL VARIANT, I DON'T KNOW IF IT WORKS WITH THE OTHER VARIANTS)
FLASH PATH BOOT.IMG​1-COPY PATCHED BOOT.IMG ("magisk_patched.img") FROM DOWNLOAD DIRECTORY and paste it on C:\adb
2-ENABLE USB DEBUGGING IN DEVELOPER OPTIONS AGAIN
3-CONNECT YOUR ONEPLUS 7T TO PC AND ALLOW USB DEBUGGING REQUEST
GO TO C:\adb AND OPEN A Windows PowerShell (SHIFT+Right-Click)
Code:
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
NOW JUST GO INTO MAGISK AND INSTALL THE APP
That's all!​

You don't need to flash, you just need to boot, then install it from magical again, then reboot

HydraMaZ said:
You don't need to flash, you just need to boot, then install it from magical again, then reboot
Click to expand...
Click to collapse
In my case, when I tried just boot, my phone froze in "Fastboot Mode" screen.

Hi there!
I am having absolutely no luck. I can get root but whichever patched image I use, my SIMs stop working.
My phone is HD1903 (European variant) and I am running OOS 11 Stable AA (Global ROM).
I have tried this:
-Guide provided here, using image and Magisk app (not patched image provided)
-With working stock boot image (ril included), boot patched (the one with link here) open magisk, direct install -> not working ril
-With working ril, using magisk app, patch image, grab image and flash it from fastboot. Tried with stable and canary apk. When I flash any of them, still no working ril.
-Reflash OOS11 to other slot, with chinese TWRP, backup boot image, flash from there Magisk zip. No luck, root but no SIMs
-Using that image backupped, patch from Magisk app, boot it, no SIM, flash it no SIM.
I have never had problems rooting this phone, but this is going really really strange, then Idk what to do really, the SIM thing is driving me crazy. Any idea is appreciated
Could it somewhat be related to the european variant + global ROM combo?
Thanks!

Success in installing Magisk and patched img for EU also successful. But always fail on Safetynet. Any suggestions?
Nevermind. Figured it out. Someone already helped. Forgot about the Magisk hide feature inside settings.

miguelang611 said:
Hi there!
I am having absolutely no luck. I can get root but whichever patched image I use, my SIMs stop working.
My phone is HD1903 (European variant) and I am running OOS 11 Stable AA (Global ROM).
I have tried this:
-Guide provided here, using image and Magisk app (not patched image provided)
-With working stock boot image (ril included), boot patched (the one with link here) open magisk, direct install -> not working ril
-With working ril, using magisk app, patch image, grab image and flash it from fastboot. Tried with stable and canary apk. When I flash any of them, still no working ril.
-Reflash OOS11 to other slot, with chinese TWRP, backup boot image, flash from there Magisk zip. No luck, root but no SIMs
-Using that image backupped, patch from Magisk app, boot it, no SIM, flash it no SIM.
I have never had problems rooting this phone, but this is going really really strange, then Idk what to do really, the SIM thing is driving me crazy. Any idea is appreciated
Could it somewhat be related to the european variant + global ROM combo?
Thanks!
Click to expand...
Click to collapse
miguelang611 said:
Hi there!
I am having absolutely no luck. I can get root but whichever patched image I use, my SIMs stop working.
My phone is HD1903 (European variant) and I am running OOS 11 Stable AA (Global ROM).
I have tried this:
-Guide provided here, using image and Magisk app (not patched image provided)
-With working stock boot image (ril included), boot patched (the one with link here) open magisk, direct install -> not working ril
-With working ril, using magisk app, patch image, grab image and flash it from fastboot. Tried with stable and canary apk. When I flash any of them, still no working ril.
-Reflash OOS11 to other slot, with chinese TWRP, backup boot image, flash from there Magisk zip. No luck, root but no SIMs
-Using that image backupped, patch from Magisk app, boot it, no SIM, flash it no SIM.
I have never had problems rooting this phone, but this is going really really strange, then Idk what to do really, the SIM thing is driving me crazy. Any idea is appreciated
Could it somewhat be related to the european variant + global ROM combo?
Thanks!
Click to expand...
Click to collapse
Actually, I have been flashing Global on my 7T HD1903 since I purchased it. But recently, I have been having problems with the Global rom Android 11. Camera freezing on other modes aside from Photo. So I downgraded to 10.0.16. The took the plunge of flashing the EU rom Android 11. And hey, nicely flashed with no known errors or issues.
Then try this rooting process. And it all worked fine. MaYBE e you should try EU rom too.

zer0se7en said:
Actually, I have been flashing Global on my 7T HD1903 since I purchased it. But recently, I have been having problems with the Global rom Android 11. Camera freezing on other modes aside from Photo. So I downgraded to 10.0.16. The took the plunge of flashing the EU rom Android 11. And hey, nicely flashed with no known errors or issues.
Then tried this rooting process. And it all worked fine.Maybe you should try WU rom too.
Click to expand...
Click to collapse
My issue was caused by a Magisk module, which strangely enough made android phone to fail, the process I was doing was right, except I didn't uninstall all modules before A11 update

I'm relatively new to payload dumpers and patching boot.img's so decided to sideload the Magisk.apk (22000) via fastbooted twrp instead, it worked a charm and all rooted.
Only issue was I forgot to install the magisk app before hand so had to install it to get it on the app drawer, other than that, no issues.

miguelang611 said:
My issue was caused by a Magisk module, which strangely enough made android phone to fail, the process I was doing was right, except I didn't uninstall all modules before A11 update
Click to expand...
Click to collapse
I do recall having this problem, it was already a bother ten months ago. I never found the actual problem, I just used several files until I got the right one working fine. Up until now I was using a rooted Oxygen OS 10.0.5 with magisk and it seemed to do the trick for me, but I got an automatic update a week ago and I got to root back my phone, might aswell update it.
But I fear that if I update to the 11 OS and try to root it, the exact problem will appear, I will wait for any fix in the future.
Update :
I did it following a few tutorial from everywhere.
There's a lot of ways to do it but ultimately, you should have magisk on canary then patch your own boot.img (either see how to extract the payload file or get the correct boot.img version )
Then follow this :
[SOLVED] Magisk patched boot.img for Android 11?
Hi there, I managed to patch the boot.img with Magisk 20.4 (20400). Then I replaced the patched boot.img and updated to Android 11 with "flash_all.bat" method. However, the phone did not boot until I flashed stock original boot.img from Android...
forum.xda-developers.com

So this process seems to have gotten me farther than anything else has so far. Been trying to root my 7T. Unfortunately, it also seems to have bricked my phone. Any advice?

Hi, I'm Android 10 root. I guess I shouldn't update OTA if I want to keep root right? The usual process would fail?

When I boot from the patched boot.img and even when I'm booting from stock boot.img the phone starts woth boot animation and finally the screen just turns black. Sometimes when I press Power + Volume up/down in no specific order, I get a kind of "menu" where I can restart or lock the screen but it's almost unresponsive and it seems to not react to touch inputs. Did anyone had similar problems? Up to Oxygen 10.x I had never any problems with fastboot boot boot.img
Unfortunately with Oxygen 11 it seems more complicated now.

I've tried everything and cant get Android 11 rooted successfully. Patched boot img myself, used other boot imgs from the forums, newest Magisk, older Magisk, Canary builds, everything I can think of... None of the patched boot imgs will boot...just stuck on boot screen (boot loop). I'm using a converted Tmobile model on Global firmware.
Odd that some people seem to have no trouble just rooting like normal but some of us cant get 11 to root.
Any ideas or tips that I could try?

Hey Guys I just rooted my phone and my wifi isn't turning on and my phone is taking 10-15 mins to reboot any fix for this? (Indian Variant One Plus 7t)

Has anyone managed to root a European 7T running stock Android 11?

BritSwedeGuy said:
Has anyone managed to root a European 7T running stock Android 11?
Click to expand...
Click to collapse
Yes. it was few weeks ago now but I think I used the 'Chinese' TWRP. However, I think that there are a few other options. What have you tried?.

mikefnz said:
Yes. it was few weeks ago now but I think I used the 'Chinese' TWRP. However, I think that there are a few other options. What have you tried?.
Click to expand...
Click to collapse
I've cracked it by extracting and patching the boot.img myself.
The files are here...
File folder on MEGA
mega.nz

I just use magisk canary and flash via Chinese twrp and rooted oos10, oos11, any custom ROMs easily

HueyT said:
I just use magisk canary and flash via Chinese twrp and rooted oos10, oos11, any custom ROMs easily
Click to expand...
Click to collapse
I am on rooted Android 10. How do i flash Chinese TWRP?

jesrani said:
I am on rooted Android 10. How do i flash Chinese TWRP?
Click to expand...
Click to collapse
Put such file in your adb folder in PC, rename img file to twrp.img, and type "fastboot flash recovery twrp.img" while phone is in bootloader mode

Question Bootloop after magisk on 12.5.3.0.RKHEUXM

Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you

suloku said:
Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you
Click to expand...
Click to collapse
Try flashing the older patched boot.img on the new stock firmware.

On the 12.5.3.0 ill patched boot.img from 12.5.1.0 and all right.

Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended

i have the same issue of auto updated and lost my root access.
Which boot.img I should Magish'd to get the root access again?
Currently installing my twrp
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
if Flash Current TWRP fails, go to Backup > Refresh Sizes and try Flash Current TWRP again
Click to expand...
Click to collapse
Currently at the Resizing stage
Edit 1: failed, I have the error bootctrl error that prevent me from installing after resizing.
I have flashed the twrp3.5.2 directly to boot resulting in bootloop and needed to install the Boot.img from the 12.5.1 from the previous bulit
Edit: actually I can ignore that error.
Magisk installed but safety checked failed even I have the "universal safety check module installed "
Also the app thoax isn't working

I'd try removing all magisk modules, installing stock 12.5.3, then using magisk apk to create patched boot.img and flash it with fastboot (fastboot flash boot magisk_boot_patched.img)
Also, maybe try flashing bot boot_a and boot_b? I had a problem were my active boot partition changed and phone became even more broken.

suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
Might wanna also uncheck Automatic system updates in the Developer settings to be safe.

suloku said:
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
There is a setting in the Xiaomi system updater that had by default checked auto-update. That setting need to be disabled/unchecked as well.
Since you have root with Magisk, can also Force stop or debloat the updater app, so the system will not update itself.

suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
I had the same issue on Redmi Note 9 Pro (joyuse). Based on your tip I've removed some modules from `data/adb/modules` and my device is finally booting normally. Thanks!

[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img

OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img
Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g
Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc
Note: DISABLE ALL MAGISK MODULES BEFORE EXECUTING OTA UPGRADE

I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk. I have Canary version installed. There was an Update to Magisk which I accidentally by OTA instead of full and now my phone is not booting. It goes into original recovery mode or fastboot only. How can I recover from this? I tried to flash the magisk patched image and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!

jesrani said:
I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk. I have Canary version installed. There was an Update to Magisk which I accidentally by OTA instead of full and now my phone is not booting. It goes into original recovery mode or fastboot only. How can I recover from this? I tried to flash the magisk patched image and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!
Click to expand...
Click to collapse
flash original (stock) boot.Img above to unroot

HueyT said:
flash original (stock) boot.Img above to unroot
Click to expand...
Click to collapse
Thanks. Would that work for Indian version also? And would that wipe data?
I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.

jesrani said:
Thanks. Would that work for Indian version also? And would that wipe data?
I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
Click to expand...
Click to collapse
All variants share same boot, data fine

HueyT said:
flash original (stock) boot.Img above to unroot
Click to expand...
Click to collapse
jesrani said:
I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk. I have Canary version installed. There was an Update to Magisk which I accidentally by OTA instead of full and now my phone is not booting. It goes into original recovery mode or fastboot only. How can I recover from this? I tried to flash the magisk patched image and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!
Click to expand...
Click to collapse
In such situation always remember, flashing original boot.img may not work best is change the partition. so if you are in a go to b and boot. Use temp TWRP custom recovery to change partition if you cannot change via command line. and once you are able to boot, flash magisk properly on both partition.

This isn't really working for me, I try to flash it with 'fastboot flash boot magisk_patched-23000.img' but it does say this on command but it doesn't boot into root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: I have Magisk ver. 25.2

RRRb50 said:
This isn't really working for me, I try to flash it with 'fastboot flash boot magisk_patched-23000.img' but it does say this on command but it doesn't boot into root
View attachment 5716169
Edit: I have Magisk ver. 25.2
Click to expand...
Click to collapse
did you install magisk25 apk?

thexile said:
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img
المخزون: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g
Magisk v23.0 مصححة: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc
ملاحظة: قم بتعطيل كافة وحدات MAGISK قبل تنفيذ ترقية OTA
Click to expand...
Click to collapse

I am on OOs 11.0.9.1. my device went into bootloop after i updated some magisk modules.
After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.

I installed twrp on partition a and now I am having root. I was not able to install Magisk25.2.apk but was able to install some other version, I think Canary release. So most things seem to work. However when I click Add Systemless Host, nothing seems to be happening. AdAway is not working. How can I get this to work again.
HDFC banking app is also detecting root even though I have installed HideMyApplist and configured DevOptsHide and HideMyApplist in LsPosed. Not sure what is the mistake. Can anyone advice?