Develop Bugs

Issues Rooting Pixel XL with TWRP/Magisk

I'm following some guides to root my pixel xl but am running to some issues.
I tried using twrp-3.3.1-0-marlin.img to load Magisk-v19.3.zip but it gives me errors mounting system and vendor.
I then tried using twrp-3.3.0-0-marlin.img to load Magisk-v19.3.zip and it appears to succeed. I reboot, but Magisk Manager never appears. When I load it manually, it tells me that Magisk 19.3 isn't installed.
I'm not sure what I'm doing wrong. Is there some hidden step?
Thank you.

ookami007 said:
I'm following some guides to root my pixel xl but am running to some issues.
I tried using twrp-3.3.1-0-marlin.img to load Magisk-v19.3.zip but it gives me errors mounting system and vendor.
I then tried using twrp-3.3.0-0-marlin.img to load Magisk-v19.3.zip and it appears to succeed. I reboot, but Magisk Manager never appears. When I load it manually, it tells me that Magisk 19.3 isn't installed.
I'm not sure what I'm doing wrong. Is there some hidden step?
Thank you.
Click to expand...
Click to collapse
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.

Tulsadiver said:
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.
Click to expand...
Click to collapse
Need to try this soon, glad to see it's working ?
Sent from my Pixel XL using XDA Labs

Tulsadiver said:
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.
Click to expand...
Click to collapse
I've followed this along with every other guide I could find at least 10x each or more, and still haven't achieved root. Everything seems to install fine, but everytime I open Magisk Manager, it shows "Magisk is not installed". And that seems to be the only thing keeping me from getting root. There has to be a missing step or something... It's been about 5 years since I've rooted a device(HTC M8), but I don't remember ever having so much difficulty. I've wiped the phone more times than I can count, uninstalled/reinstalled Magisk(regular and Canary), tried to do this on both Android 8 and 9, tried to complete this process on both LinuxMint and Windows, etc. I'm completely out of ideas at this point.

tyler.durden said:
I've followed this along with every other guide I could find at least 10x each or more, and still haven't achieved root. Everything seems to install fine, but everytime I open Magisk Manager, it shows "Magisk is not installed". And that seems to be the only thing keeping me from getting root. There has to be a missing step or something... It's been about 5 years since I've rooted a device(HTC M8), but I don't remember ever having so much difficulty. I've wiped the phone more times than I can count, uninstalled/reinstalled Magisk(regular and Canary), tried to do this on both Android 8 and 9, tried to complete this process on both LinuxMint and Windows, etc. I'm completely out of ideas at this point.
Click to expand...
Click to collapse
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.

Tulsadiver said:
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.
Click to expand...
Click to collapse
That's definitely one that I haven't tried yet. I'm still on Android 9 for now. I downloaded the latest Platform tools just a few days ago, so that part should be up to date. It doesn't seem like there's much for Android 10 yet, so I'm waiting a bit before I switch.

tyler.durden said:
That's definitely one that I haven't tried yet. I'm still on Android 9 for now. I downloaded the latest Platform tools just a few days ago, so that part should be up to date. It doesn't seem like there's much for Android 10 yet, so I'm waiting a bit before I switch.
Click to expand...
Click to collapse
Here is the boot and patched boot from 9 August update. I typically have firmware for recent Pixel phones.
https://mega.nz/#!gRBGhYAZ!Z7mEBEHVT9V4ut0p__g5BVboS8RjLSSPWXgjurSQxbU

Tulsadiver said:
Here is the boot and patched boot from 9 August update. I typically have firmware for recent Pixel phones.
https://mega.nz/#!gRBGhYAZ!Z7mEBEHVT9V4ut0p__g5BVboS8RjLSSPWXgjurSQxbU
Click to expand...
Click to collapse
Thank you! Magisk finally installed using the boot.img patching method, and now I have root access.

Tulsadiver said:
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.
Click to expand...
Click to collapse
I am having the same issue, but with the Oct patch. How do I make one of these with Magisk Manager? I tried making it with the bootloader img from the stock factory image, but it fails at repackaging step. Anyone else having issue with Oct patch?

smithilberry said:
I am having the same issue, but with the Oct patch. How do I make one of these with Magisk Manager? I tried making it with the bootloader img from the stock factory image, but it fails at repackaging step. Anyone else having issue with Oct patch?
Click to expand...
Click to collapse
You meant boot.img, right?
Edit. You need to unzip the image zip in order to get the boot.img.

Tulsadiver said:
You meant boot.img, right?
Edit. You need to unzip the image zip in order to get the boot.img.
Click to expand...
Click to collapse
Yes, that's what I meant. I also got it working. I used TWRP 3.3.0 and it worked. Not sure what the reason would be.

Tulsadiver said:
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.
Click to expand...
Click to collapse
Sent from my marlin using XDA Labs
---------- Post added at 10:51 AM ---------- Previous post was at 10:45 AM ----------
Tulsadiver said:
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.
Click to expand...
Click to collapse
This was my dilemma. I have no PC so I am using Osmosis's static fastboot magisk mod and it works excellent but because the sdk must be an updated version it does not know the command when you flash the patched boot.img the " --slots all " it says unrecognizabled command in termux and terminal emulator but everything else will flash it's just that new --slots all that gets it. Is there any way for me to get the boot.img on both slots without using that command? Can I just fastboot the boot then reboot bootloader and repeat? Would that get it on both slots?
Is it possible to install the boot.img in one slot or will that mess things up? Guide has patched boot on both...Or just boot twrp 3300 and flash a rom? I'm weary about getting too brave because I bricked a device recently that was A/B. I been around for many years and never bricked anything till recently. ?
Sent from my marlin using XDA Labs

flash713 said:
Sent from my marlin using XDA Labs
---------- Post added at 10:51 AM ---------- Previous post was at 10:45 AM ----------
This was my dilemma. I have no PC so I am using Osmosis's static fastboot magisk mod and it works excellent but because the sdk must be an updated version it does not know the command when you flash the patched boot.img the " --slots all " it says unrecognizabled command in termux and terminal emulator but everything else will flash it's just that new --slots all that gets it. Is there any way for me to get the boot.img on both slots without using that command? Can I just fastboot the boot then reboot bootloader and repeat? Would that get it on both slots?
Is it possible to install the boot.img in one slot or will that mess things up? Guide has patched boot on both...Or just boot twrp 3300 and flash a rom? I'm weary about getting too brave because I bricked a device recently that was A/B. I been around for many years and never bricked anything till recently.
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
I personally have never flashed it to both slots. Just the current slot
fastboot flash boot magisk_patched.img

Tulsadiver said:
I personally have never flashed it to both slots. Just the current slot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
You rock! Appreciate you telling me this! I believe I understand more now that I've read about the A/B partition for a few weeks.. Pixel XL forums actually has the most detailed information of A/B that I've seen yet. Cheers.
Sent from my marlin using XDA Labs

Tulsadiver said:
I personally have never flashed it to both slots. Just the current slot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Can I fastboot vendor and bootloader, or anything instead of the entire factory image if I want to roll back to August Pie from October 10? I'm going after DU and it's an August pie build.. Thanks for the info on slots! Somehow it helped me better understand the entire partition deal... I remember you from many years ago on some Nexus device that you made various mods for.. Anyway thanks! Alot!
Sent from my marlin using XDA Labs

flash713 said:
Can I fastboot vendor and bootloader, or anything instead of the entire factory image if I want to roll back to August Pie from October 10? I'm going after DU and it's an August pie build.. Thanks for the info on slots! Somehow it helped me better understand the entire partition deal... I remember you from many years ago on some Nexus device that you made various mods for.. Anyway thanks! Alot!
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
To roll back you not only have to flash the entire image but you'll have to wipe your phone.

TWRP boot looping?
I'm trying to root a Pixel XL Android 10, purchased form Google. I'm stuck at the point of trying to boot the phone to the temporary TWRP. Using command "fastboot boot twrp.img" .
I get the "Sending, Booting, Finished OKAY" messages, but the phone then shows a never ending flash of the TWRP logo every few seconds, with no functionality.
The twrp.img I'm using is twrp-3.0.2-0-RC1-fastboot-marlin.img
Any suggestions?

SeekMocha said:
I'm trying to root a Pixel XL Android 10, purchased form Google. I'm stuck at the point of trying to boot the phone to the temporary TWRP. Using command "fastboot boot twrp.img" .
I get the "Sending, Booting, Finished OKAY" messages, but the phone then shows a never ending flash of the TWRP logo every few seconds, with no functionality.
The twrp.img I'm using is twrp-3.0.2-0-RC1-fastboot-marlin.img
Any suggestions?
Click to expand...
Click to collapse
NEVER MIND: I was using wrong version of TWRP.

SeekMocha said:
NEVER MIND: I was using wrong version of TWRP.
Click to expand...
Click to collapse
What TWRP version did you use?

Bootloop after installing magisk

hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
try to flash stock boot.img and recovery.img

sonn3 said:
try to flash stock boot.img and recovery.img
Click to expand...
Click to collapse
Same issue. So how would we go about flashing properly?

Search for recovery.img and boot.img in stock rom and flash in fastboot mode.

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
Did you select close avb 2.0 in twrp and factory reset?

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
We would need further details on which device (region) which MIUI version (number, android, region) you were on when you attempted to install Magisk. Of course we assume here you had unlocked your bootloader first, otherwise any attempt to flash anything will result in bootloop.
Many have successfully rooted on Android 9 regardless of MIUI version.
Complication often comes with Chineses devices from what I read, Global not so much so if you are on Global device consider yourself lucky
Easiest root is probably to flash LR team TWRP If you can still access fastboot mode (voloume - + power) version 09.24 or 11.04 if you are on Android 9 or version 12.10 if you are on Android 10. Note that you probably have more chances of success being on Android 9.
And use the root feature from WITHIN that TWRP to install root on your device.
You have a complete guide of the steps to reproduce here:
Guide
I have tested on Android 9, EEA device, EEA rom MIUI 11.0.2.0 and it works without an issue if you follow the guide provided above.
If you still want to manually flash Magisk from any other recovery, make sure to use version 19.04 which seems to have the higher odds of success (update afterward from Manager).
Also as mentioned by @wang1chung do not forget to close avb 2.0.
Myself I also had RM Force encrypt option used (just in case) even if not mentionned in the thread.
But unlike what was suggested in those threads I did not wipe data.
That said since I do not want to have TWRP to stick for now, I actually want it to automatically be replaced by stock recovery all went fine for me, and Magisk is there.
And when I need TWRP for something I just flash it again and do my stuff.
Hope this helps.
Good luck!

Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?

allxdadev said:
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
Click to expand...
Click to collapse
Personally I used the hassle-free method pressing the button to root directly from within the LR-TWRP (09.24, or 11.04 on Android 9 MIUI), swiped, then pressed that other provided button to close AVB 2.0, swiped and it worked on first attempt.
Of course TWRP got replaced on first reboot by system recovery, but I dont care as I do not want it to stick on my device. I just flash it again when I need it.
Magisk stayed, updated it from Manager (well manager updated first to that new ugly theme.... yurk!), then Magisk updated, no problem.
Note that I am on EU Phone running EEA MIUI 11.0.2.0. You might get a different outcome with other devices/roms.
Side note, LR-TWRP 09.24 installs Magisk 19.04 which has been reported numerous time to work on most Android 9 MIUI regional versions. LR-TWRP 11.04 howevers installs Magisk 20.0 fyi.
Hope this helps,
Regards,

regarding the thread title, i had the same problem. right when i was about to retart everything all over from 0, i was glad i was able to just go into twrp and just unroot. rebooted and it started as if nothing hsppended. now i jjust gotta find which module made me bootloop.

try this n give us the result

December firmware update!

Does anyone know where i can find the newest security December 1, 2019 update for the g7 play? i've searched online and cannot find it anywhere. My phone keeps reminding me of a failed update so i went looking for the new one. Do i re-flash the phone to stock and update it that way before re-rooting it or wait until someone post the newest update in the mirrors repository? What do you guys suggest?

dominoeflux said:
Does anyone know where i can find the newest security December 1, 2019 update for the g7 play? i've searched online and cannot find it anywhere. My phone keeps reminding me of a failed update so i went looking for the new one. Do i re-flash the phone to stock and update it that way before re-rooting it or wait until someone post the newest update in the mirrors repository? What do you guys suggest?
Click to expand...
Click to collapse
https://support.motorola.com/us/en/Solution/MS147329
Oct 2019 seems to be the latest:
https://www.theandroidsoul.com/spri...lay-moto-g6-play-with-october-security-patch/
Normally you go back to stock, patch and then re-root.
What model do you have?
I cannot get root on my XT1952-4.

mtmtumbo said:
https://support.motorola.com/us/en/Solution/MS147329
Normally you go back to stock, patch and then re-root.
What model do you have?
I cannot get root on my XT1952-4.
Click to expand...
Click to collapse
I have the same model with boost mobile...do you need help rooting it? I just followed the instructions for the boot.img magisk patch but when you patch it make sure you select beta in magisk and in advanced settings make sure all are checked especially recovery mode before you patch and lastly when you reboot, reboot to recovery every time or the root will not stick...that's something no one mentioned when i was trying to root mine. I had to research the problem of why the root wasn't sticking. When you reboot to recovery it will stay on a blank screen and then vibrate, that's normal. It does that before it boots up. Once it's booted, check to make sure you have root by opening the magisk app, you should see both green check marks and thanks for you help with how to update.

dominoeflux said:
I have the same model with boost mobile...do you need help rooting it? I just followed the instructions for the boot.img magisk patch but when you patch it make sure you select beta in magisk and in advanced settings make sure all are checked especially recovery mode before you patch and lastly when you reboot, reboot to recovery every time or the root will not stick...that's something no one mentioned when i was trying to root mine. I had to research the problem of why the root wasn't sticking. When you reboot to recovery it will stay on a blank screen and then vibrate, that's normal. It does that before it boots up. Once it's booted, check to make sure you have root by opening the magisk app, you should see both green check marks and thanks for you help with how to update.
Click to expand...
Click to collapse
thanks, I followed the instructions as well to patch boot.img and use fastboot with magisk_patched.img, but when I rebooted, I only got the xxxxxx-xxxxxx-xxxxxxx-xxxxxxx-xxxxxx code and then no vibration and nothing else - seems stuck and just looping at this point
what do you mean select beta in magisk?
what version of apk did you create the patched img from? 7.4.0?
and yes, i made sure i checked all the advanced options (including recovery) before creating the patched img file

mtmtumbo said:
thanks, I followed the instructions as well to patch boot.img and use fastboot with magisk_patched.img, but when I rebooted, I only got the xxxxxx-xxxxxx-xxxxxxx-xxxxxxx-xxxxxx code and then no vibration and nothing else - seems stuck and just looping at this point
what do you mean select beta in magisk?
what version of apk did you create the patched img from? 7.4.0?
and yes, i made sure i checked all the advanced options (including recovery) before creating the patched img file
Click to expand...
Click to collapse
when you go in the magisk manager, select the three lines at the top left and go to settings/update channel and select beta....if you don't you will loop. i used the latest magisk version which is 7.4.0 so yes you're using the correct one. your suppose to see those codes it's normal, if the phone does not vibrate, then that means that it didn't work.

dominoeflux said:
when you go in the magisk manager, select the three lines at the top left and go to settings/update channel and select beta....if you don't you will loop. i used the latest magisk version which is 7.4.0 so yes you're using the correct one. your suppose to see those codes it's normal, if the phone does not vibrate, then that means that it didn't work.
Click to expand...
Click to collapse
Thanks, I enabled beta in magisk and tried it again and it still did not vibrate after showing the codes - just rebooting in a loop as before.
What size is your magisk_patched.img and boot.img files?
Here are mine:
33,554,432 boot.img
18,103,592 magisk_patched.img
You can see after the patching that the size of the boot image drops almost in half - is that normal?
I transfer these files using adb push and pull as I heard MTP transfers could corrupt the files.
Anyhow, since we're on the same build, can you post up your boot and patched img somewhere so I can try them?

mtmtumbo said:
Thanks, I enabled beta in magisk and tried it again and it still did not vibrate after showing the codes - just rebooting in a loop as before.
What size is your magisk_patched.img and boot.img files?
Here are mine:
33,554,432 boot.img
18,103,592 magisk_patched.img
You can see after the patching that the size of the boot image drops almost in half - is that normal?
I transfer these files using adb push and pull as I heard MTP transfers could corrupt the files.
Anyhow, since we're on the same build, can you post up your boot and patched img somewhere so I can try them?
Click to expand...
Click to collapse
Did you repatch the stock boot.img before flashing again? The magisk patch is different if not on beta and the magisk recovery is not selected, that's why it's probably still not working.
also make sure that you're patching the correct boot.img from your stock firmware that you're on, it creates problems if you're not. I can't upload my .imgs for some reason and you're correct it didn't vibrate the first time i was successful, but after i have to reboot the phone i would reboot to recovery so when the phone boots the root sticks, that's when it will vibrate.

@mtmtumbo I apologize I haven't been on here in a couple of days, any update on rooting your g7 play?

dominoeflux said:
Did you repatch the stock boot.img before flashing again? The magisk patch is different if not on beta and the magisk recovery is not selected, that's why it's probably still not working.
also make sure that you're patching the correct boot.img from your stock firmware that you're on, it creates problems if you're not. I can't upload my .imgs for some reason and you're correct it didn't vibrate the first time i was successful, but after i have to reboot the phone i would reboot to recovery so when the phone boots the root sticks, that's when it will vibrate.
Click to expand...
Click to collapse
happy new year all
yes i re-patched the stock boot.img before flashing, magisk was on beta and yes the third option in advanced for recovery was selected before i patched the boot.img
after i saw the codes and it was looping, i rebooted the phone to recovery but no difference
i'm also having a problem flashing twrp without just using fastboot boot twrp.img - flashing it with fastboot flash doesn't work (using dtbo.img first to avoid the black screen)
btw you can use mega.nz to upload your img's - give it a shot and post the URL here
if it matters, this is the ROM I'm using:
XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC

mtmtumbo said:
happy new year all
yes i re-patched the stock boot.img before flashing, magisk was on beta and yes the third option in advanced for recovery was selected before i patched the boot.img
after i saw the codes and it was looping, i rebooted the phone to recovery but no difference
i'm also having a problem flashing twrp without just using fastboot boot twrp.img - flashing it with fastboot flash doesn't work (using dtbo.img first to avoid the black screen)
btw you can use mega.nz to upload your img's - give it a shot and post the URL here
if it matters, this is the ROM I'm using:
XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
Happy New Year man.....i believe i figured out why you're still boot looping, did you reboot back into the bootloader after you flashed the patched.img?
edit: when your doing twrp, you have to boot into it before installing it to the ramdisk. there's a how to in this forum here: https://forum.xda-developers.com/g7-play/how-to/how-to-successfully-install-twrp-g7-play-t3979701
the GSI's don't work for me so i'm waiting for a legit custom build before installing twrp again

Update 134-7
XT1952-2
ATTMX
https://mirrors.lolinet.com/firmwar...USMXLA_regulatory-XT1952-2-MEXICO_CFC.xml.zip
OpenMX
https://mirrors.lolinet.com/firmwar...EFAULT_regulatory-XT1952-2-MEXICO_CFC.xml.zip
RETAR
https://mirrors.lolinet.com/firmwar...ULT_regulatory-XT1952-2-ARGENTINA_CFC.xml.zip

[OP7T][Stock/Magisk] OxygenOS 11.0.2.1.HD65AA boot.img

OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://file5.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img

Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?

My computer is down so:
THANKS A MILLION!!!!!!!!!!!!!
YOU'RE SO AWESOME!!!!!!!!!!!!

Orion9k0 said:
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
Click to expand...
Click to collapse
If you are not using TWRP, follow this guide: https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/

didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on

posiblyLopsided said:
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
Click to expand...
Click to collapse
Did you switch back the default OTA active slot after flashing both?

nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
i did not flash i only booted. i have tried flashing in the past with android 11 and had the same result of eternal loading. but that was a while ago and it is possible i did smth wrong.

nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
Did you remove or at the very least disable all Magisk modules before OTA updating?

i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.

posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"

kurskoo40 said:
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
Click to expand...
Click to collapse
the issue is that when i do fastboot boot magisk.img it gets stuck on the boot animation. i have to hold the power button and volume up to force it to power off then i can boot it back to the normal version

posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.

thexile said:
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
Click to expand...
Click to collapse
how would i do that? can i use my phone file manager or do i need to use adb?

posiblyLopsided said:
how would i do that? can i use my phone file manager or do i need to use adb?
Click to expand...
Click to collapse
Since you have no root access currently, you have to do so via adb in recovery mode with adb enabled.

thexile said:
Since you no root access currently, you have to do so via adb in recovery mode with adb enabled.
Click to expand...
Click to collapse
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.

posiblyLopsided said:
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
Click to expand...
Click to collapse
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.

thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
yeah looks like i learned the hard way too. also i didnt realise they released twrp for oneplus 7t. id heard that it just didnt work with android 11 but maybe im wrong. ill try it out anyways. if the twrp works that would be amazing. also thanks for all the help.

thexile said:
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://srv-store6.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks. This worked fine. I just used local install from update, backed out without rebooting, installed magisk app and did the first reboot into bootloader, then wrote magisk modded boot image to boot a/b. It was a dirty update over the prior version.

thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
i have successfully rooted after useing twrp to remove those magisk modules.

Hi, I really need EU version of boot.img, could you please help me?
I've even looked for the full 11.0.2.1.HD65BA but with no luck.
So basically can't find anywhere both the boot.img and the full stock rom, any advice?
Thank you

Question le2125_11_c.61 OOS12 root

My phone updated to le2125_11_c.61 and I can't find a suitable boot.img to flash magisk. The OTA update has a partial boot image so that fails. Does anyone have a copy of the boot.img for this version, or is there another method I should use?

rustyshakelford2 said:
My phone updated to le2125_11_c.61 and I can't find a suitable boot.img to flash magisk. The OTA update has a partial boot image so that fails. Does anyone have a copy of the boot.img for this version, or is there another method I should use?
Click to expand...
Click to collapse
Just use the C.48 patched image, boot (don't flash), and then direct install Magisk. Should work. If it doesn't, no harm done since you didn't flash it.

EtherealRemnant said:
Just use the C.48 patched image, boot (don't flash), and then direct install Magisk. Should work. If it doesn't, no harm done since you didn't flash it.
Click to expand...
Click to collapse
That was a nice thought, but unfortunately it didn't work. The phone hangs when booting both the magisk'd and regular C.48 image.
I did fastboot boot boot.img. Is that correct? I'm a bit out of practice.

rustyshakelford2 said:
That was a nice thought, but unfortunately it didn't work. The phone hangs when booting both the magisk'd and regular C.48 image.
I did fastboot boot boot.img. Is that correct? I'm a bit out of practice.
Click to expand...
Click to collapse
Yeah that's correct. Bummer that it didn't work. Give me a few to download and patch it.

rustyshakelford2 said:
That was a nice thought, but unfortunately it didn't work. The phone hangs when booting both the magisk'd and regular C.48 image.
I did fastboot boot boot.img. Is that correct? I'm a bit out of practice.
Click to expand...
Click to collapse
Well unfortunately I have downloaded two different python scripts trying to patch the full OTA with the incremental OTA and they are both failing so I guess we will have to wait for someone else to do it because I don't have the expertise to fix this.

As long as your bootloader is unlocked, You could try booting (again not flashing) into TWRP and then try sideloading Magisk (after renaming .apk to .zip) ?

djsubterrain said:
As long as your bootloader is unlocked, You could try booting (again not flashing) into TWRP and then try sideloading Magisk (after renaming .apk to .zip) ?
Click to expand...
Click to collapse
You can't boot into TWRP because it doesn't work on OOS12. It crash dumps.
Someone who is rooted needs to install the OTA and pull the image unless there is a tool I haven't come across that works better for incremental OTA extraction.

The incremental C.61 OTA (downloaded thru Oxygen Updater) ins't getting installed.
The oxygen updater app isn't listing the file and the About device Local Install is throwing Verification failed.
Any idea to fix this ?
LE2121
Thanks

observingi said:
The incremental C.61 OTA (downloaded thru Oxygen Updater) ins't getting installed.
The oxygen updater app isn't listing the file and the About device Local Install is throwing Verification failed.
Any idea to fix this ?
LE2121
Thanks
Click to expand...
Click to collapse
I am also facing the same problem..

rustyshakelford2 said:
My phone updated to le2125_11_c.61 and I can't find a suitable boot.img to flash magisk. The OTA update has a partial boot image so that fails. Does anyone have a copy of the boot.img for this version, or is there another method I should use?
Click to expand...
Click to collapse
Try using the MSM tool for your device, press F8, then select boot_a or boot_b depending on what slot you're in. To check your slot, reboot to fastboot and issue the command fastboot getvar current-slot.
You should be able to then patch the boot.img and flash it normally.

razercortex said:
Try using the MSM tool for your device, press F8, then select boot_a or boot_b depending on what slot you're in. To check your slot, reboot to fastboot and issue the command fastboot getvar current-slot.
You should be able to then patch the boot.img and flash it normally.
Click to expand...
Click to collapse
Getting this phone to actually boot into MSM mode is a nightmare. I either end up in fastboot or it boots up normally. I got it to show up exactly once, but it timed out and booted up before I got the readback going.

rustyshakelford2 said:
Getting this phone to actually boot into MSM mode is a nightmare. I either end up in fastboot or it boots up normally. I got it to show up exactly once, but it timed out and booted up before I got the readback going.
Click to expand...
Click to collapse
Enable USB debugging in settings, then type adb reboot edl.

razercortex said:
Enable USB debugging in settings, then type adb reboot edl.
Click to expand...
Click to collapse
I got it! I managed to readback boot_b using the password "oneplus". I can't seem to find where it saved the file though.

It's in C:\ aka your root drive

razercortex said:
Try using the MSM tool for your device, press F8, then select boot_a or boot_b depending on what slot you're in. To check your slot, reboot to fastboot and issue the command fastboot getvar current-slot.
You should be able to then patch the boot.img and flash it normally.
Click to expand...
Click to collapse
That's a cool trick. I didn't know about that one.

Successfully rooted! Huge thanks to razercortex and others in this thread who helped.
Here is a download of both the unmodified and magisk patched boot.img for e2125_11_c.61 global.
https://www.dropbox.com/s/bpoe31lt022rigj/e2125_11_c.61%20global%20boot.img.zip?dl=1
I booted the patched image via fastboot and then did a magisk direct install. After updating the safetynet fix module and running props I am passing safeteynet. I had to restore props to defaults and then apply the android 11 fingerprint for this phone, otherwise it would fail CTS.

rustyshakelford2 said:
Successfully rooted! Huge thanks to razercortex and others in this thread who helped.
Here is a download of both the unmodified and magisk patched boot.img for e2125_11_c.61 global.
https://www.dropbox.com/s/bpoe31lt022rigj/e2125_11_c.61%20global%20boot.img.zip?dl=1
I booted the patched image via fastboot and then did a magisk direct install. After updating the safetynet fix module and running props I am passing safeteynet. I had to restore props to defaults and then apply the android 11 fingerprint for this phone, otherwise it would fail CTS.
Click to expand...
Click to collapse
Can you please share the steps to get the boot.img
I have to get it from LE2121

gulshanstrider said:
Can you please share the steps to get the boot.img
I have to get it from LE2121
Click to expand...
Click to collapse
You should be able to just boot (don't flash) the 2125 rooted image they posted and then use Magisk to direct install.

EtherealRemnant said:
You should be able to just boot (don't flash) the 2125 rooted image they posted and then use Magisk to direct install.
Click to expand...
Click to collapse
I have an LE2125 on 11_C.61 and when I fastboot the posted patched boot.img file I get Magisk Installed: N/A in Magisk Manager. I even patched the posted boot.img myself in Magisk and get Magisk Installed: N/A when fastbooting that patched boot.img. Any ideas?

TornSack said:
I have an LE2125 on 11_C.61 and when I fastboot the posted patched boot.img file I get Magisk Installed: N/A in Magisk Manager. I even patched the posted boot.img myself in Magisk and get Magisk Installed: N/A when fastbooting that patched boot.img. Any ideas?
Click to expand...
Click to collapse
Did you go to try to direct install? I haven't actually tried C.61 yet, I've got stuff to do this weekend and can't have my phone in an experimental state when I'm trying to call and Uber to get around, so I can't test it myself.