Develop Bugs

[ROOT][UB][LP] Easy way to Root your ZL with Lollipop!

ROOT Xperia ZL - 5.0.2
NOTE: For now it's only for UNLOCKED BOOTLOADER!
Come on with me, mate! Let's root that damn thing in some easy steps!
Requirements:
Download Advenced Custom Kernel .292 by Gustavo RD78
Download my Kernel Only.ftf (don't metter if it's for C6506 or 02 its the same thing)
Download SuperSu.zip
Note: Extract the boot.img from Gustavo RD78's zip.
Note: If you've been prompted to update binaries in SuperSU app, flash this file. It is an beta updated version of SuperSU that might works!
For root:
Unlock your BL
Flash extracted boot.img from the Gustavo's zip through Fastboot Mode in Flash Tool
Reboot into recovery (reboot and press Volume + repetivelly)
Flash SuperSu.zip
Power options (in recovery) -> Power off
Flash my Kernel Only.ftf from here through flash mode!
Power on, you're rooted!
Relock your bootloader, be happy! (Optionally)
For recovery:
I don't flash xzdualrecovery, it got me into bootloop.
My tip is for you to download TWRP.img and flash it with RASHR APP (download from Google Play).

didnt work for me, i flashed as mentioned above but on booting supersu shows needs to be updated and fails
apps like tb show root fail only works through kingroot then but cant get recovery to work through that root access

I was able to get full root with this guide except for the SuperSU zip, it asked me to update the binaries and you know, you can't because you don't have recovery and that version isn't working on Lollipop... BUT
This one works perfectly, do the same but use THIS one
BETA SuperSU 2.4.8
And don't forget to flash the stock kernel!
{
"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"
}

Oliver94 said:
It asked me to update the binaries
Click to expand...
Click to collapse
Really? It doesn't asked me... Well, I'll add this link to the OP for the ones that have been prompted to update binaries. Thanks for repoting this to me!

Abadeer said:
For recovery:
I don't flash xzdualrecovery, it got me into bootloop.
My tip is for you to download TWRP.img and flash it with RASHR APP (download from Google Play).
Click to expand...
Click to collapse
Hi, which twrp.img did you mentioned? Download in Rashr app or somewhere, as Rashr said it will flash the recovery into the FOTAkernel partition. Will this work with stock rom?
Sent from my C6503

khangozzy said:
Hi, which twrp.img did you mentioned? Download in Rashr app or somewhere, as Rashr said it will flash the recovery into the FOTAkernel partition. Will this work with stock rom?
Sent from my C6503
Click to expand...
Click to collapse
That recovery didn't work for me.

khangozzy said:
Hi, which twrp.img did you mentioned? Download in Rashr app or somewhere, as Rashr said it will flash the recovery into the FOTAkernel partition. Will this work with stock rom?
Sent from my C6503
Click to expand...
Click to collapse
didnt work for me .. doubt stock kernel supports it

not working
got me into bootloop flashing the "gustavo's" kernel

may i ask what happen if not unlock bootloader yet? got bootloop?

greetings, be so kind as to better explain the three from step 2 to 5 , thanks

Abadeer said:
ROOT Xperia ZL - 5.0.2
NOTE: For now it's only for UNLOCKED BOOTLOADER!
Come on with me, mate! Let's root that damn thing in some easy steps!
Requirements:
Download Advenced Custom Kernel .292 by Gustavo RD78
Download my Kernel Only.ftf (don't metter if it's for C6506 or 02 its the same thing)
Download SuperSu.zip
Note: Extract the boot.img from Gustavo RD78's zip.
Note: If you've been prompted to update binaries in SuperSU app, flash this file. It is an beta updated version of SuperSU that might works!
For root:
Unlock your BL
Flash extracted boot.img from the Gustavo's zip through Fastboot Mode in Flash Tool
Reboot into recovery (reboot and press Volume + repetivelly)
Flash SuperSu.zip
Power options (in recovery) -> Power off
Flash my Kernel Only.ftf from here through flash mode!
Power on, you're rooted!
Relock your bootloader, be happy! (Optionally)
For recovery:
I don't flash xzdualrecovery, it got me into bootloop.
My tip is for you to download TWRP.img and flash it with RASHR APP (download from Google Play).
Click to expand...
Click to collapse
I download Rashr and flash TWRP.imp but can't enter Recovery. I root my phone success by use PRF Creator (choose 10.6.A.0.454 Rom and SuperSu 2.4.8 only, not choose ZL-dualrecovery).

THANKS
Abadeer said:
ROOT Xperia ZL - 5.0.2
NOTE: For now it's only for UNLOCKED BOOTLOADER!
Come on with me, mate! Let's root that damn thing in some easy steps!
Requirements:
Download Advenced Custom Kernel .292 by Gustavo RD78
Download my Kernel Only.ftf (don't metter if it's for C6506 or 02 its the same thing)
Download SuperSu.zip
Note: Extract the boot.img from Gustavo RD78's zip.
Note: If you've been prompted to update binaries in SuperSU app, flash this file. It is an beta updated version of SuperSU that might works!
For root:
Unlock your BL
Flash extracted boot.img from the Gustavo's zip through Fastboot Mode in Flash Tool
Reboot into recovery (reboot and press Volume + repetivelly)
Flash SuperSu.zip
Power options (in recovery) -> Power off
Flash my Kernel Only.ftf from here through flash mode!
Power on, you're rooted!
Relock your bootloader, be happy! (Optionally)
For recovery:
I don't flash xzdualrecovery, it got me into bootloop.
My tip is for you to download TWRP.img and flash it with RASHR APP (download from Google Play).
Click to expand...
Click to collapse
You sir is a life saver!

Thank you for this guide. I successfully install lollipop and got root with BETA SuperSU 2.4.8 on my C6503. I would know if is possible flash a recovery without going in bootloop, because I would install xposed framework.
I already tried to flash the recovery TWRP from Rashr app, but it seems that the recovery wasn't installed and it's impossible boot in recovery mode.

How can I recover from a Bootloop?
I flashed boot.img with fastboot but then realized i didn't have SuperSU on my SDCard. So I Flashed your KernelOnly.ftf to get back into my system and get SuperSU on my SDCard, but now I'm in bootloop.
EDIT: I flashed my ROM again (C6503_10.6.A.0.454_Customized_BR) to recover from Bootloop. But now I'm guessing that you Kernel Only file doesn't work with my ROM. Will I get bootloop again if I successfully root my phone?

fabioascoelho said:
How can I recover from a Bootloop?
I flashed boot.img with fastboot but then realized i didn't have SuperSU on my SDCard. So I Flashed your KernelOnly.ftf to get back into my system and get SuperSU on my SDCard, but now I'm in bootloop.
EDIT: I flashed my ROM again (C6503_10.6.A.0.454_Customized_BR) to recover from Bootloop. But now I'm guessing that you Kernel Only file doesn't work with my ROM. Will I get bootloop again if I successfully root my phone?
Click to expand...
Click to collapse
Check here if your ROM is correct. I went in bootloop several times before have root and working ROM. Take attention to step 5. Don't reboot your system, but power off or you'll go in bootloop. Good Luck!
P.S. I used Beta SuperSU and not SuperSU. I don't know if it changes something.

drakon091 said:
Check here if your ROM is correct. I went in bootloop several times before have root and working ROM. Take attention to step 5. Don't reboot your system, but power off or you'll go in bootloop. Good Luck!
P.S. I used Beta SuperSU and not SuperSU. I don't know if it changes something.
Click to expand...
Click to collapse
I'm using the last Firmware available for C6503 (1270-5681 10.6.A.0.454 R3E), but the OP Kernel is for C6502. I thought it would be compatible.
What I did:
1. Flashed boot.img in fastboot mode;
2. Booted into recovery mode;
3. Realized I didn't had Beta SuperSU on my phone, just on my PC :crying:
4. Went to Power Menu and Power Off on recovery mode;
5. Flashed the Kernel offered by the OP, Kernel Only from a C6502 phone;
6. Tried to boot but I got a bootloop.
7. Re-flashed my C6503 Lollipop ROM.
Now I want to retry the process, but can someone confirm that the Kernel from C6502 phone is compatible with a C6503 or should I wait for someone to post a Kernel Only ftf for my phone version?

fabioascoelho said:
I'm using the last Firmware available for C6503 (1270-5681 10.6.A.0.454 R3E), but the OP Kernel is for C6502. I thought it would be compatible.
What I did:
1. Flashed boot.img in fastboot mode;
2. Booted into recovery mode;
3. Realized I didn't had Beta SuperSU on my phone, just on my PC :crying:
4. Went to Power Menu and Power Off on recovery mode;
5. Flashed the Kernel offered by the OP, Kernel Only from a C6502 phone;
6. Tried to boot but I got a bootloop.
7. Re-flashed my C6503 Lollipop ROM.
Now I want to retry the process, but can someone confirm that the Kernel from C6502 phone is compatible with a C6503 or should I wait for someone to post a Kernel Only ftf for my phone version?
Click to expand...
Click to collapse
All steps seem correct and I guarantee that custom kernel is compatible with C6503 (I flashed it on mine C6503). Try to install Beta SuperSU, it should work! Kernel Only ftf is compatible too!

i´ve already done this - worked like a charm! but i got another question now:
i want to install xposed fw - so if i flash the boot.img from gustavo´s kernel to get a custom recovery again, install the xposed fw stuff, and then flash the only-kernel from lollipop again, will i lose my data on phone or better said, do i´ve to setup everything again? or can i work with the phone as it was before flashing gustavo´s boot.img?

I would know if there is another way to get a recovery without reflash gustavo's kernel and then kernel only ftf. It's annoying do this for every installation...

yup, thats true, but, not atm! we´ve to wait until somebody does the job!
i tried to flash the kernel of xzdualrecovery for 10.6.A.0.454 which can be made on their site, but doesnt work either - bootloop

How do you install Magisk on Oneplus 3 OOS 4.1.3

I tried to install magisk v12 zip but it always fails but says to install supersu soon after. I did that but when i installed magisk manager it said there's no MagiskSU installed and Safety net did not pass as well! Then i tried to uninstall supersu and magisk and flash magisk v12 again but same result again. I tried find how to install MagiskSU online but i can't find any thread about this issue. My aim of installing Magisk is to use MagiskHide for snapchat. Can someone help me pls.:crying:

Are you on SuperSU at the moment?
You will need to unroot using the SuperSU app (That's what I did) before flashing magisk zip.
Secondly, I had trouble with SuperSU + Magisk so I used phh superuser to get it working. I also needed magisk to hide root from snapchat and another banking app and I am able to do so easily.
So, in short,
1. Uninstall SuperSU
2. Flash magisk zip in recovery
3. Flash phh superuser in recovery (People say its optional but I do it anyway)
4. Reboot and benefit

Can you send me a link to download the phh superuser file you used please. When you say uninstall do you mean full unroot? What did you use to uninstall supersu? https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459

Magisk v12 will auto install root when no root is detected, so u can just clean flash ur rom and install magisk v12 after it, it will auto root

@mharis05 nowadays Phh's Superuser is not "optional": it's unsupported and replaced by the integrated MagiskSU since Magisk v10: look at the official thread, it's declared obsolete.
It would get device in trouble, even if MagiskSU is disabled.
 @Bradl79 neither the clean flash is a right way, because:
1) If you're intending a system wipe, it's not resolutive because Magisk is OTA-survival.
2) If you're intending a data wipe, it's an useless waste of time... and data!
You have to run the following zip files: Magisk official uninstaller and UnSU to be sure you've not rooted device in any way.
Then to stay quiet, do a Cache and Dalvik/ART wipe.
At this point, try to reflash Magisk.

I tried that but time and time again when i try to uninstall that SUPERSU it says to flash default boot.img to complete the process. AND Installation "FAILED" Flash Supersu immediately. I did that but still no magiskSU.

At this point try to wipe system and cache/ART, then reflash OOS.
After doing that, go with Magisk.

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.

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.

[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?