Develop Bugs

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

h815_usu twrp bootloop problem

i unlock my device using usu mode and using with custom roms. one day i installed ressurection remix 7.01 and supersu after some use i decide to only factory reset for clean start on twrp. after this my device stucked on twrp loop. no matter how try other options and roms booting only twrp.(tried offical latest 3.6.0)
i can use bootloader and download mode and tried unlock again with usu mode but no luck.
here my salt options can i do anything or my device gone forever? device model was H815TR
{
"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"
}

theartanis said:
i unlock my device using usu mode and using with custom roms. one day i installed ressurection remix 7.01 and supersu after some use i decide to only factory reset for clean start on twrp. after this my device stucked on twrp loop. no matter how try other options and roms booting only twrp.(tried offical latest 3.6.0)
i can use bootloader and download mode and tried unlock again with usu mode but no luck.
here my salt options can i do anything or my device gone forever? device model was H815TR
View attachment 5490901
Click to expand...
Click to collapse
Boot to fastboot and exec
fastboot format userdata
Then boot

steadfasterX said:
Boot to fastboot and exec
fastboot format userdata
Then boot
Click to expand...
Click to collapse
booted on twrp and nothing in device. twrp says rom successfully flashed after rebooting device is empity. so twrp wiping auto everything after reboot?

theartanis said:
booted on twrp and nothing in device. twrp says rom successfully flashed after rebooting device is empity. so twrp wiping auto everything after reboot?
Click to expand...
Click to collapse
I told you that you should boot Android after that command and not TWRP. So does Android boot now or not?

i retry and booting to only twrp

theartanis said:
i retry and booting to only twrp
Click to expand...
Click to collapse
Please flash the latest Preview(!) TWRP and not the official one. The official one is only valid for Oreo and does not contain the latest fixes

now i tried with twrp 3.5.2_9 preview-275 same thing happens

theartanis said:
now i tried with twrp 3.5.2_9 preview-275 same thing happens
Click to expand...
Click to collapse
Choose wipe -> advanced format userdata snd reboot.
If that does not fix it doe the above fastboot command again and try to boot

no luck i think main problem is twrp says everytime rom flashing succesfully but device is empity nothing installed

theartanis said:
no luck i think main problem is twrp says everytime rom flashing succesfully but device is empity nothing installed
Click to expand...
Click to collapse
What ROM do you flash? Pls flash a UsU rom.
Also after flashing get the recovery log. See my signature how

i flashing your lineageos 14.1_usu rom
https://bpa.st/IOQA > This log is after flashing rom without reboot system
https://bpa.st/AJQQ > this is after reboot

theartanis said:
i flashing your lineageos 14.1_usu rom
https://bpa.st/IOQA > This log is after flashing rom without reboot system
https://bpa.st/AJQQ > this is after reboot
Click to expand...
Click to collapse
Hm ok all went fine but when flash a nougat based ROM use the nougat(!) preview TWRP . Not sure if that helps but if you wanna use such an old ROM it might be needed anyways.

wow at last 14.1 lineage os booted after installed with N twrp-3.4.0-PREVIEW-230 but it have a error failed to mount /firmware (no such device) after wipe or install its not important right?

theartanis said:
wow at last 14.1 lineage os booted after installed with N twrp-3.4.0-PREVIEW-230 but it have a error failed to mount /firmware (no such device) after wipe or install its not important right?
Click to expand...
Click to collapse
I guess with "it" you meant TWRP has that issue ? As long as you stay on on UsU roms it shouldn't be an issue

thank you for everything now i using your last version of twrp and installed android 9.0 rom

General LE2123_11.C.61 Update in Germany

LE2123_11.C.61_ 1610_202206141855
Finally made it to my device in Hamburg
{
"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"
}

My device is showing the update too, but I did not install yet. How did you maintain root after upgrading?

I am wondering the same. The normal way doesn't work for me. Magisk tells me there is not stock backup.

If anyone knows how to update with root let us know,seems like even using the oxygen updater isn't working too

Deinstall magisk and restore original boot image, update (download incremental via oxygen updater) via oneplus updater app (you'll find it via Google, don't use the integrated updater) and install magisk to inactive slot and reboot. That's it, worked for me

If you have a rooted device and want to keep root you should install it via that local updater apk.
That c61 file you guys have downloaded, is this incremental or full?

I would like the patched boot img for this ROM....
Oxygen 61......
Please

Anonymouze said:
Deinstall magisk and restore original boot image, update (download incremental via oxygen updater) via oneplus updater app (you'll find it via Google, don't use the integrated updater) and install magisk to inactive slot and reboot. That's it, worked for me
Click to expand...
Click to collapse
Unfortunately, that is not working for me. I am getting installation error. I wonder if it could be because the local update app version?

Might be a reason but I don't think so , I attached the version I've used. Do you restore the boot image when deinstalling magisk?

Anonymouze said:
Might be a reason but I don't think so , I attached the version I've used. Do you restore the boot image when deinstalling magisk?
Click to expand...
Click to collapse
Hi, thanks for providing the app. Yes, I restore images, but still get installation error.. I have this issue since c48. I think it's because it is incremental update and my bootloader is unlocked, but I see some people manage to install it. I was hoping OP will releace full zip this time, but it seems I have ti wait.

My bootloader is also unlocked. Do you have oos12 already installed on your inactive boot slot? If not that might be a problem when flashing incremental updates

Anonymouze said:
My bootloader is also unlocked. Do you have oos12 already installed on your inactive boot slot? If not that might be a problem when flashing incremental updates
Click to expand...
Click to collapse
I am on OOS12 c47, but I am not sure what I have on the inactive slot. I had an issue and I had to reset the device after thet I tried c48, but it was the same.

I'm sure there is a way to change/switch the active/inactive slot with adb or fastboot. If so you can check what's going on on the inactive slot

Anonymouze said:
I'm sure there is a way to change/switch the active/inactive slot with adb or fastboot. If so you can check what's going on on the inactive slot
Click to expand...
Click to collapse
Thanks, I will check

I managed to get root on c61...after having updated from 48.
It wasn't straight forward. I couldn't do it the usual way of uninstalling Magisk...and then updating....and then installing Magisk to another slot. So.... This is what I did do.
In Magisk. Uninstall Magisk. Complete Uninstall.
Get into fastboot.
Flash the boot.img file from the pinned post about rooting.
Reboot and update as normal.
Now...go to the rooting post...and root again.

I updated from C47 with this method:
I first updated magisk to 25.1 and downloaded the module universal safteynet fix 2.3.1
I disabled all modules in magisk and did a reboot
In magisk manager I uninstalled magisk and restored the boot image
I installed the C61 update in system settings (no oxygen updater or local update)
After installing I did NOT reboot but reinstalled magisk to inactive slot. Then I did a reboot
After the reboot I reactivated my modules

rumaroma said:
I updated from C47 with this method:
I first updated magisk to 25.1 and downloaded the module universal safteynet fix 2.3.1
I disabled all modules in magisk and did a reboot
In magisk manager I uninstalled magisk and restored the boot image
I installed the C61 update in system settings (no oxygen updater or local update)
After installing I did NOT reboot but reinstalled magisk to inactive slot. Then I did a reboot
After the reboot I reactivated my modules
Click to expand...
Click to collapse
I couldn't restore my boot image. I had used the Alpha version ....which doesn't backup the boot image. So I had to do it the way I did. Your way is the usual way on a\b phones.

Hi guys!
Can I get boot.img for C61???? Please

rumaroma said:
I updated from C47 with this method:
I first updated magisk to 25.1 and downloaded the module universal safteynet fix 2.3.1
I disabled all modules in magisk and did a reboot
In magisk manager I uninstalled magisk and restored the boot image
I installed the C61 update in system settings (no oxygen updater or local update)
After installing I did NOT reboot but reinstalled magisk to inactive slot. Then I did a reboot
After the reboot I reactivated my modules
Click to expand...
Click to collapse
Unfortunately for me, nothing worked. I am also on c47. I tried complete magisk uninstall, re-flashed the full c47 zip (which worked via local update), manually restored boot images on both slots, when tried to update to c48 had the same issue even after factory reset. I am still getting installation problem. Maybe will be waiting for full zip, try to relock the bootloader or just switch to custom ROM

sshriss said:
Unfortunately for me, nothing worked. I am also on c47. I tried complete magisk uninstall, re-flashed the full c47 zip (which worked via local update), manually restored boot images on both slots, when tried to update to c48 had the same issue even after factory reset. I am still getting installation problem. Maybe will be waiting for full zip, try to relock the bootloader or just switch to custom ROM
Click to expand...
Click to collapse
Finally OP released C62 as full zip and I flashed it without issues. I have no major complains. All seem to be working as before.

Question After flashing TWRP the root is gone

Hello,
After flashing TWRP from advanced options (flash current TWRP) on Xiaomi 12X, Miui 14), it removes the magisk root. When I patch the boot image with magisk again, the root is back but stock recovery is restored. I tried the option to prevent TWRP being replaced by the stock recovery in the advanced options but it did not work. Is there any way to keep BOTH TWRP and root on this device? Thank you.

Wojtek1971 said:
Hello,
After flashing TWRP from advanced options (flash current TWRP) on Xiaomi 12X, Miui 14), it removes the magisk root. When I patch the boot image with magisk again, the root is back but stock recovery is restored. I tried the option to prevent TWRP being replaced by the stock recovery in the advanced options but it did not work. Is there any way to keep BOTH TWRP and root on this device? Thank you.
Click to expand...
Click to collapse
Have you tried with the REC version?
https://forum.xda-developers.com/t/shared-recovery-psyche-twrp-by-skkk.4461461/post-88081701

NOSS8 said:
Have you tried with the REC version?
https://forum.xda-developers.com/t/shared-recovery-psyche-twrp-by-skkk.4461461/post-88081701
Click to expand...
Click to collapse
Does not work, either.

Wojtek1971 said:
Does not work, either.
Click to expand...
Click to collapse
Did you do it like this?
1/root
2/Twrp

NOSS8 said:
Did you do it like this?
1/root
2/Twrp
Click to expand...
Click to collapse
How do I flash TWRP, i.e. what is the actual fastboot command? Also, does it matter which version of TWRP I should flash since there are quite a few of them?

In TWRP go to advanced. There you can choose to install TWRP directly.

Wojtek1971 said:
How do I flash TWRP, i.e. what is the actual fastboot command? Also, does it matter which version of TWRP I should flash since there are quite a few of them?
Click to expand...
Click to collapse
Same method
https://forum.xda-developers.com/t/shared-twrp-by-skkk.4479573/

NOSS8 said:
Same method
https://forum.xda-developers.com/t/shared-twrp-by-skkk.4479573/
Click to expand...
Click to collapse
The cmd fastboot flash recovery_ab twrp.img command fails. After booting to twrp using the fastboot boot twrp.img command and using the option flash current recovery upon rebooting system I'm back in twrp. The only way to get out of the bootloop is to flash magisk patched boot image to both partitions, which restores the stock recovery.

Wojtek1971 said:
The cmd fastboot flash recovery_ab twrp.img command fails. After booting to twrp using the fastboot boot twrp.img command and using the option flash current recovery upon rebooting system I'm back in twrp. The only way to get out of the bootloop is to flash magisk patched boot image to both partitions, which restores the stock recovery.
Click to expand...
Click to collapse
Do you use this rom.V14.0.1.0.TLDEUXM?
What Twrp have you tried (full name)?
Edit:
My bad,No rec version for this device.
After flashing the patched boot did you do that?
{
"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"
}

NOSS8 said:
Do you use this rom.V14.0.1.0.TLDEUXM?
What Twrp have you tried (full name)?
Edit:
My bad,No rec version for this device.
After flashing the patched boot did you do that?
View attachment 5843407​
Click to expand...
Click to collapse
I used this one: [BOOT]3.7.0_12-Mi12X_v7.1_A13-psyche-skkk. I did use the direct install method with magisk. I also tried to install TWRP to recovery ramdisk - it apparently went okay but on rebooting to recovery I'm back to stock one. I also tried flashing orangefox but with the same result . Yes, I'm on the latest miui version.

I've finally worked it out. This is what I did:
1. I rebooted to fastboot
2. In adb I entered "fastboot boot name of the twrp.img
3. Once in twrp I flashed the recovery version of my rom (Miui 14) downloaded from xiaomifirmwareupdater.com
4. I went to advanced options and used install recovery ramdisk
5. In advanced options again I entered "Use magisk to patch boot"
6. I rebooted the system: no bootloop and the root working perfectly.
It is crucial to install twrp first and only then patch the boot from twrp , not the other way round.

P.S.
In this procedure the twrp recovery is not overwritten by stock one.