Develop Bugs

December update breaks magisk?

Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.

Works fine for me.

Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions

Working fine for me as well.

I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app

You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.

mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!

RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.

RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1

Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.

Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018

I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse

[GUIDE] How to Root OnePlus 7T without TWRP

So today with some testers i managed to make root on OnePlus 7T, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator). For now you should use only Magisk Canary files
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
Third Root Guide:
Guide by @gpz1100
TIPS:
Actually you should use only Magisk canary files Magisk 20.3
You can get the stock boot images from the fastboot rom: https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
Actually i'm using magisk manager canary and magisk canary debug to patch the boot.img, I don't recommend updating magisk, if you don't want to see the updates install the normal magisk manager
Magisk 20.3 fully support OnePlus 7T and 7T Pro
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images: https://www.androidfilehost.com/?w=files&flid=300177
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
@RohanAJoshi

Flashed and working flawless.
Really thanks for this.
Awesome work bro.

Can you please upload the patched boot.img please? I dont see it in the above folder at all.

nick_22 said:
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
Click to expand...
Click to collapse
Done, i uploaded them using ftp and i forgot to move the files in the right folder

Working, thanks a lot @mauronofrio

I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.

jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
See OP, its clearly mentioned there. You have to flash this via fastboot and not any custom recovery. Firstly setup adb on your PC and then check the commands. Its very easy. Do some googling and still if its difficult for you, come back and ask.

jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
Welcome to the android scene, reminds me of the old psx scene

I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.

@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?

nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
Get your stock boot.img from 1st post.
Reboot to bootloader.
And do this command
fastboot flash boot boot.img
fastboot reboot
Device will boot unrooted.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
jesrani;80464121 [user=4712355 said:
@mauronofrio[/user], thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.

RohanAJoshi said:
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
Click to expand...
Click to collapse
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?

jesrani said:
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
In older devices like OP5T it happens like this, not in newer devices. OP7T has seamless updates, its installs while device is turned on in second partition.

nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
jesrani said:
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)

mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?

jesrani said:
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
Canary debug, don't update it

Help please. I have returned to Android after 5years with OnePlus 7t and trying to root it. I am trying this method but not being able to successfully root it. Steps I have tried
Went to fastboot mode by restarting the phone but I don't get an option to install the patched image file. And even boatloader is locked. Do I need to unlock the bootloader. And I unlock will I loose my data. Sorry for silly question I have completely forgot about Android.

Thanks, rooted successfully

?
To be honest need video tutorial asap?

mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Ok. Got it. So, I have already booted back to unrooted mode now. And I cant wipe my data again. Thanks for your response.

Stuck after flashing patched magisk bootloader img

So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????

after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result

krolla03 said:
So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????
Click to expand...
Click to collapse
krolla03 said:
after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result
Click to expand...
Click to collapse
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.

I previously dealt with similar symptoms. You can read about it here -- https://forum.xda-developers.com/showpost.php?p=81102855&postcount=33

Badger50 said:
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.
Click to expand...
Click to collapse
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?

krolla03 said:
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?
Click to expand...
Click to collapse
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:

Badger50 said:
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:
Click to expand...
Click to collapse
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.

krolla03 said:
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.
Click to expand...
Click to collapse
Yep. It'll just be temporary :good:

Badger50 said:
Yep. It'll just be temporary :good:
Click to expand...
Click to collapse
Thanks man. I got it all working again!!!

Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?

dark_heroo said:
Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?
Click to expand...
Click to collapse
Not sure what your starting point is but:
After installing you fastboot factory image
you can either temporarily or permanently install TWRP (temp TWRP= fastboot twrp.img, install magisk, reboot OR perm TWRP = fastboot twrp.img, install TWRP.zip from witin TWRP)
then you just flash/install magisk in TWRP
In my sig is a link to a detailed step by step guide for all this.
Good luck!

Question [Latest OOS C.44 EU] Rooting via Magisk/fastboot not working

Hello all,
yesterday I've updated to latest OOS LE2123_11.C.44_1440_202201182111 (Android 12). I was previously on root, so I've updated the phone via full 4GB OTA through the system updater.
Everything was fine until I've tried to root by following these steps:
ATTENTION: if you're a Googler and willing to root the OPO 9 Pro, don't use the steps below, because they lead to a soft-bricked phone! (at least, for me)
Download the full OTA via Oxygen Updater
Extract the boot.img (192MB) via Payload Dumper (and I was confused, because the previous Android 11 boot.img was exactly the half in size)
Let the phone update itself
Throw the boot.img inside Magisk and create a patched boot.img
Flash the pathed boot image via fastboot with "fastboot flash boot Magisk_patched_blabla.img"
The phone was refusing to boot, as it was automatically booting in Fastboot mode.
So I've reflashed the patched IMG file, and the phone switched to Qualcomm Crashdump mode
Then, don't ask me how, I've managed to get it back to fastboot mode. Searched XDA for a clean and tested boot.img, understood that the boot contains 2 slots A/B, set the active boot slot to A, flashed the boot.img downloaded before, and the phone turned back to life.
So...what am I doing wrong? Maybe everything?
What are the correct steps to root the phone?
Thank you in advance

you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/

OS Update with install to inactive slot in magisk works too.

nicoilboss said:
you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/
Click to expand...
Click to collapse
I follow those steps I can get the boot and install alpha apk after it's install completed to reboot, phone gets bricked and stuck in fastboot.

Wait for the new Magisk, it's going to support Android 12.
https://twitter.com/topjohnwu/with_replies

djsubterrain said:
Wait for the new Magisk, it's going to support Android 12.
https://twitter.com/topjohnwu/with_replies
Click to expand...
Click to collapse
Missed this one...
How come some people is actually running on the rooted OOS C.44 EU? Are they using a particular version of a patched boot.img that's floating underground?

l_mike said:
OS Update with install to inactive slot in magisk works too.
Click to expand...
Click to collapse
I've clickbaited like a moron on the UPDATE/REBOOT button after OTA, and I've missed the opportunity to do it *before* rebooting the phone... then followed the steps I've posted and knocked out of the door...

xmff00 said:
Missed this one...
How come some people is actually running on the rooted OOS C.44 EU? Are they using a particular version of a patched boot.img that's floating underground?
Click to expand...
Click to collapse
Your post doesn't specify which version of magisk you're using, unless I overlooked it. If you're not using alpha already, use alpha. And make sure you also patch the boot.img with alpha and not a different version than you're trying to install. A couple of people have said canary works now (at least for C40), but I can't confirm whether it still works on C44. Stable doesn't work (yet).

terlynn4 said:
Your post doesn't specify which version of magisk you're using, unless I overlooked it. If you're not using alpha already, use alpha. And make sure you also patch the boot.img with alpha and not a different version than you're trying to install. A couple of people have said canary works now (at least for C40), but I can't confirm whether it still works on C44. Stable doesn't work (yet).
Click to expand...
Click to collapse
New stable V24 is released. Works great

nicoilboss said:
you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/
Click to expand...
Click to collapse

I've tried to use this method but when I try to flash using the 'fastboot boot magisk_boot.img' I get the error "failed - command boot not recognized"
ADB shows the 'sending' command but then nothing happens other than error mentioned above. I've tried to use both the patched and unpatched images but same error. No idea how to proceed from here

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.