yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] crypta:
I am on A12, upgraded from OOS11 as full OTA.

Bootloader warning is gone, magisk was installable after OTA before reboot.

Problem: the latest update is an incremental. How may I update this? A normal install failed, thx to A12, c44 ai don't have an option to upload the full update into the oos updater...

How would I upgrade without resetting my system?
[OnePlus 9 Pro] Marucins:
And that's thanks to darling OnePlus - they're the ones who changed Android 12 for the "better"!

They later came to their senses...

You have to use the app: https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk

//https://forums.oneplus.com/threads/android-12-developer-preview-program-for-oneplus-9-and-oneplus-9-pro.1437113/
[OnePlus 9 Pro] dview78:
Have you managed to recover your phone? I can reboot into fastboot mode too, was away for the weekend, so didn't have time to look for a solution.
[OnePlus 9 Pro] jmadiaga:
hi,

this guide is so comprehensive for the oneplus 9 pro

however, pity of us who have only the oneplus 9

and/or who have not access to a PC or windows laptop to extract the files from OOS C.47.

i hope the img files for the OOS C.47 can also be posted.

thank you.
[OnePlus 9 Pro] danizwam:
Hi,

i deinstalled Magisk before the update (as i always do) and updated my 9 Pro to C.47. After that, i tried the boot.img in the first post and i patched my own boot.img (extracted from the payload.bin) but i it does not work properly. I type "fastboot boot magisk_boot.img" and after a while, it shows the white and red dot. But then, it reboots and boots the original boot.img. Back in A12 i have no root and cannot install Magisk.

Any suggestions?

Edit: I also tried this method https://www.droidwin.com/root-oneplus-9-pro-9r-magisk-without-twrp/ where you have to flash boot.img vendor_boot.img and vbmeta.img but i am still in a bootloop. I reflashed the the orginial files and it boots again...

I am devastated. This would be my first Android since 2009 that is not rooted. :(

EDIT:

Nevermind, i locked and unlocked my bootloader and rooted from scratch. It now works.. I think it has been caused by my SmaliPatcher Module, which i forgot to remove before unrooting. I think magisk wanted to load it at startup and that causes the crash. Due to the lack of a working TWRP, i could not flash Magisk-Uninstall oder Magisk via recovery.
[OnePlus 9 Pro] crypta:
Do you know if it will erase everything or behave like a normal OTA, like in the times OOS was still good?
[OnePlus 9 Pro] Marucins:
This works like a regular OTA.

This is just an "overlay" on the crashed function.
[OnePlus 9 Pro] abadasstanker69:
In the directions it says the T-Mo variant is "ACB" but there are NO files labeled "ACB".

You're reporting back that "AA" worked for you but that's labeled as "Global/NA".

I'm currently bootloader unlocked on the T-Mo variant. I was looking for a patched boot img when I found this thread. I feel like I'm no closer to my goal and even more confused.

To clarify for myself and others who may be reading this, are you saying that we should use the AA files if we are on the T-Mo variant? Or do I have the MSM to Global and then use the AA files? I haven't done anything to my recovery. It's still stock. All I did was sim unlock, bootloader unlock, then come here.

Thanks for any advice or guidance anyone can provide for me!

UPDATE:

I figured it out. I took a different route but it got me the same place. I'm now rooted on stock. Thanks!
[OnePlus 9 Pro] lawyeradam:
Good to hear, and Yes, the AA files worked on my T-Mobile variant without converting it to any other region. I used the stock boot.img to return to the stock recovery (I was stuck in fastboot mode only), then fastbooted the Magisk boot.img, then patched within the Magisk app.
[OnePlus 9 Pro] abadasstanker69:
Have you tried any roms yet? Or is the modem issue keeping you from trying them out?
[OnePlus 9 Pro] percentevo:
I am global c47 and currently stuck in a fastboot loop. I can fastboot the stock boot.img from the AA or the magisk boot img and both do the same, I end up in TWRP. Regardless of which boot slot I pick, A or B, I end up back at fastboot when attempting to restart. Any help would be greatly appreciated! I have spent hours now reading through this thread but no luck.
[OnePlus 9 Pro] percentevo:
what was the different route you took? Im stuck in a fastboot loop, see above post for additional.
[OnePlus 9 Pro] percentevo:
Can you provide any steps to flashing the boot.img on both A+B partitions?
[OnePlus 9 Pro] percentevo:
Issue solved.

For anyone it might help...

-I flashed the stock rom to reset things from https://xdaforums.com/t/oneplus-9-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254587/, for me it was LE2125_11.C.47: LE2125_11.C.47_1470_202203102119.

-If Fastboot loop occurs, you can flash the original boot.img in both slots if none of the patched boot images work. Or, if they only boot once and it always reenters fastboot loop on restart or shutdown.
[OnePlus 9 Pro] vishy92:
Hey!

I followed this guide to root my phone since OOS 12 made it unuseable. However I cannot find the MagiskHide option anywhere in Magisk. Is it necesarry to hide apps? If so what other methods are recommended. Sorry this is my first time rooting. Did I botch the install or are there no available modules by default in magisk?
[OnePlus 9 Pro] mlord:
Okay, I followed the instructions here and updated to C.47, re-installed Magisk, and rebooted into the new version.

No Magisk app.

So, re-installed the Magisk app from /sdcard/, but whenever I try to open the app, it briefly flashes on the screen, and then appears to get automatically un-installed again.

I do have root access though. Just no app.

Wassup?

EDIT: Okay, I somehow tripped over the app in "recents", where it was called "Magic". Tapped on that, and from there was able to restore it and get it working normally again. I must have renamed it at some point in the past.
[OnePlus 9 Pro] mlord:
After a full 24hrs of use, OOS12/C.47 is a definite improvement for me over the OOS11 that I had been running until now. All of the various threads complaining about OOS12 issues had put me off until now, but C.47 is working fine. Fully rooted (Magisk), SafetyNet checks pass -- even the ArriveCan app works (needed for re-entry to Canada when I travel).

Android Auto via AAWireless is working without issue in my Subaru -- I had been experiencing LTE data glitches before, but those seem to now be cured. Also, no need to disable ADB for Android Auto now either -- something I've had to do with both this handset and the OnePlus5 before it.

The phone feels smoother, battery life seems unchanged, wireless charging still works, my Tasker scripts are fine, etc..

Almost a non-event.
[OnePlus 9 Pro] galaxys:
Agree, it's been running smoothly for me since C.44!
[OnePlus 9 Pro] dview78:
Is there a way to re-install OTA from the computer?

My phone is still in fastboot loop - I can boot the TWRP, but it does not support Android 12, so it won't unlock local storage. I've tried booting/restoring boot.img from the OTA file, but no luck - it results in Crashdump. I've tried to use payload_dumper.py script, but it does not support Android 12 files, had no issue with Android 11 OTA.

Since payload_dumper managed to unpack system partition and few others, I thought I'd try to flash it - no luck - fastboot told me there was no system_a partition?

Where should I go to look for help?

Kind regards.
[OnePlus 9 Pro] nickdagriff1982:
I'm having problems too. Everytime I use fastboot to boot the magisk image, everything goes good, phone reboots, but when I open the Magisk app, there is no option to direct install, the only one that appears is patch a boot image. What am I missing here? I followed OP's instructions word for word. Need some help if anyone's got any ideas.
[OnePlus 9 Pro] Z-Blade:
Have you tried using the MSM Tool to recover back to stock OOS?
[OnePlus 9 Pro] Z-Blade:
You can flash the patched boot.img directly from fastboot, no need to do it via the Magisk app.
[OnePlus 9 Pro] nickdagriff1982:
I actually tried that and for some reason the patched boot image is 102mb so it said the image was too large.
[OnePlus 9 Pro] Z-Blade:
That is weird. My boot.img is about 200mb and I had no issues flashing it via fastboot. I assume you used payload dumper to extract boot.img?
[OnePlus 9 Pro] MSC238:
Tried to do an ota but lost root. I've done it plenty of times before, but I must have missed something this go 'round. The update failed though and maybe thats the issue.

What's the best way for me to get root back without losing any data?
[OnePlus 9 Pro] Kylewolf:
How would I go about upgrading to c.47 safely if I have TWRP installed. I don't mind losing it, just don't want to brick my phone.
[OnePlus 9 Pro] spevil07:
How to enter these Groups/Channels if i am not member in this group/channel? Can someone invite me or sen Link please?
[OnePlus 9 Pro] Steve0007:
Those were for C44 OTA updates. Those are not required anymore with latest Magisk. Just follow our guide on first post
[OnePlus 9 Pro] Dan3ll1:
Hey guys,

what would be the best way to Upgrade from OOS11 to OOS12 with a patched magisk boot img.

Can i do this from OP? With the full OOS zip from Oxygen Updater?

Keep Root and OTA updates

​

Option 1: With full OTA Access (BA/DA) :

And then follow the steps provided?

Thanks for any help
[OnePlus 9 Pro] spevil07:
Not needed
[OnePlus 9 Pro] nickdagriff1982:
So, I haven't been able to find my red OnePlus factory cord for a while. Well, I finally found it last night and followed yours and the OP's instructions and had no problems at all. Fully rooted, thanks Z Blade. Didn't even have to use payload dumper. Just booted the unmagisk version and direct install was there. And it didn't say the image was too large. So guys, I know it's like the golden rule, but let me go ahead and underscore that statement. Always use the factory cable.
[OnePlus 9 Pro] AC130PL:
TWRP is not compatible with A12
[OnePlus 9 Pro] lorchmeister:
The guide worked well for me (on LE2125) using included files for temp boot w/ Magisk, up until I installed newest Magisk Canary (as instructed), which updated the v24.3 included with the OOS12 C.47 patched boot zip. In Magisk I did the Direct Install and rebooted, but it went to bootloader and now I'm in the fastboot loop.

Can you please provide more details on how you fixed this? Would the other boot included with the magisk patched boot img in the zip on OP be what I should boot now? And how do I flash both slots? Do I need to do fastboot flash boot_a boot.img and then fastboot flash boot_b boot.img ??
[OnePlus 9 Pro] percentevo:
I mostly followed the instructions from the Magisk site, installing TWRP along with it. I used the Magisk from post #633 on this thread(see below). Alberhasky has the files attached on that post. My magisk app shows im running v23015 alpha. Fair warning though, my bank app is still detecting root even though I added it to the zygisk. The app runs fine but it wont allow me to use biometric login or access a couple of things which arent that important. I wanted to try Shamiko for the hide feature but it doesnt like this version of Magisk. Im not annoyed enough yet to risk upgrading and seeing what happens.

I was able to flash to both slots using TWRP, it was an option on the flash screen. I dont know how to do it using fastboot.

I hope this helps! Ask away if youre still stuck, it might jar some memory loose for me.
[OnePlus 9 Pro] jruizdesign:
c48
[OnePlus 9 Pro] galaxys:
Yep, just saw a notify from Oxygen Updater for c48! 😎📱🌠
[OnePlus 9 Pro] Murd0c:
I just updated to C48. Here is the Magisk flashed boot.img for said version. Just boot it like previous ones and then install magisk alpha.
[OnePlus 9 Pro] pharomir:
For what version? Global/NA?
[OnePlus 9 Pro] Murd0c:
Sorry forgot to specify. NA boot image
[OnePlus 9 Pro] stayfidz:
this guide is to be updated
[OnePlus 9 Pro] AutruiP:
Hi,

I've already used this tutorial once and it worked fine, but I installed TWRP which removed root and I wanted to flash magisk again. I can't seem to make it work now...

When I use "fastboot boot magisk_boot.img" (OOS 11.2.10.10 BA), my OnePlus 9 boots fine, but when I open magisk there is only the "patch a file" option. I can't use "Direct install".

This is the full detail of what I do :

- adb reboot bootloader

- fastboot boot magisk_boot.img ((from OOS 11.2.10.10 BA zip))

- Wait for it to boot

- Open Magisk (tried Magisk Canary and Magisk 24300)

- ???

- Post here

I also tried to flash the image, but it doesn't change anything.

Can someone help me ? Thanks
[OnePlus 9 Pro] hllywd:
Don't know if this is right or just a fluke, but if your selinux is set to permissive try changing it or vice versa. You may have to do a couple reboots. Worked for me.
[OnePlus 9 Pro] AutruiP:
How can I change selinux if I do not have root on my device ? TWRP also disappeared, but I have not flashed anything else than the boot.img and magisk_boot.img from the original post

Edit :

Well, it's working now, I had the Direct install option appeared... I followed this guide https://topjohnwu.github.io/Magisk/install.html , and did the boot.img directly from the magisk app, but I already did it multiple times before following the original post from there, so I really don't understand what's different this time.
[OnePlus 9 Pro] weriwd:
Update 1:​

I have exactly the same problem as the OP.

Update: I have followed the steps in post #1 "

Phone Bricked ?

:

Option 2 - Get back the original boot.img​

If your device can go to fastboot mode:

Flash back the original boot.img (w/o magisk) and reboot

Code once in fastboot mode:

"fastboot flash Original_boot.img" (use the "Original_boot.img" from the above zip file)

Change to the exact name "Original_boot.img" of the boot that has been posted in the above zip file

"fastboot reboot""

After reboot nothing happens. I'm getting the warning message that the bootloader is unlocked. I no longer see the device when using "fastboot devices", but I do see it when I use "adb devices".

I think that I got rekt, please advise I want to use my new device :/

​

Update 2:​

I have managed to unbrick the device. Qualcomm drivers were not installed correctly. Here is what I did in order to see it as Qualcomm......* in Windows Device Manager (hopefully this will help other people with the same issues):

Since my device was bricked I was not able to execute any commands through fastboot or adb, so the only option was to use the MSM tool for my EU device (provided on the first post of this thread).

Unfortunately, I was not aware of the 'state' of the device (On or Off - which was the major problem. I was seeing the device as LE2123 in Device Manager), because there was nothing shown on the display.

So if you want to install successfully Qualcomm drivers with bricked phone do the following:

Power off the device - Power button + Volume Down for 10-15 sec

Plug the cable into the phone while holding volume up + volume down -> once you hear that the phone is connected to the PC it will be discoverable as Qualcomm.... into Windows Device Manager -> right click on it and install/update the drivers from whenever they are located on your PC.

Once drivers are installed you have to repeat the force shut down (Power button + Volume Down for 10-15 sec) -> then holding volume up + volume down, and once you hear that the phone is connected click on the 'Enum' then 'Start' on the MSM tool. (Launch the MSM tool before this step, because there is a short time window in which the device is staying discoverable in this 'EDL' state)

Update 3:​

I managed to root my LE2123 (OOS12 C.47) device.

Here is what I did in order to avoid this mysterious boot loop that happened to me.

-Updated the device to the latest version - OOS12 C.47

-Installed the latest version of Magisk

-Downloaded the stock boot.img from the first page of this thread.

-Patched the boot.img through magisk

-Flashed the boot.img through fastboot - fastboot flash boot boot.img

Now everything works smoothly and I enjoy my rooted device :)
[OnePlus 9 Pro] kkalkan:
global magisk pach img

File on MEGA

mega.nz
[OnePlus 9 Pro] AGBOHOU:
For what version? Global AA?
[OnePlus 9 Pro] kkalkan:
yes global AA.
[OnePlus 9 Pro] Akilesh.cv:
Hello, can someone point me in the direction of rooting the LE2120 version please ? Thanks.
[OnePlus 9 Pro] rolandroide:
Thank you, OP, for the great tutorials, just rooted and debloated the hell out of my EU 9, no problem thanks to your detailed instructions. Actually took longer to enable fastboot on the windows 11 laptop I used... ^_^
[OnePlus 9 Pro] Unifire:
any1 else stuck at downloading 'boot.img'... ? nvm, the second time worked
[OnePlus 9 Pro] Unifire:
i get static and no root on latest o11
[OnePlus 9 Pro] Ultraman666:
A12 is still sloppy
[OnePlus 9 Pro] AllGamer:
Looking for AA C.48 magisk

I thought I was upgrading to C.47. only to realized it went all the way to C.48

Can I still use C.47 boot with magisk in C4.8 ???

Never mind, seems like it worked. (knocks on wood)
[OnePlus 9 Pro] pgv100:
Hi mlord, trying to get ArriveCAN to work, but getting the usual device isn't safe message. Have you got any hints about getting it to work? I've already enabled the Zygotsk thing and disallowed playstore and arrivecan. But I'm not sure where to go from here. I'm fairly certain it is only because I have the unlocked bootloader that it refuses.
[OnePlus 9 Pro] mlord:
I installed the Magisk app (v24.3), installed Magisk itself, and rebooted.

Then went into the app settings and enabled Zygisk(Beta), as well as "Enforce DenyList", and rebooted again to enable those.

Then downloaded the "Universal SafetyNet Fix" module (v2.2.1) for Magisk from GitHub ( https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1 ), and installed it using the Magisk app. Rebooted again.

For the ArriveCAN app and others, I went into the Magisk app again, into settings and selected the "Configure DenyList" entry. Within there, I added checkmarks for ArriveCAN and Google Play Store.

All good after that. Passes basic Safetynet checks, and ArriveCAN works without issues.
[OnePlus 9 Pro] dview78:
I was not successful with it - as I use Linux, MSM tool didn't seem to be able to see my phone from the Windows installed inside VM.

Visiting a store that "fixed phones" did a trick though - my phone was restored to the stock OOS within minutes.
[OnePlus 9 Pro] AverageLibrarian:
hey. this might seem dumb. but is this guide fully updated for the latest stuff? im looking at grabbing a oneplus 9 pro le2125 off ebay today or tomorrow and want to make sure everything is still working. ive been out of this game for a while.
[OnePlus 9 Pro] TheGhost1951:
Not seeing anything for T-Mobile OP 9 pro.... I'm waiting on unlock token and want to Root after unlocking bootloader....
[OnePlus 9 Pro] djensen777:
Here is mine. https://drive.google.com/file/d/1MdtSsj9hUoK7Cx4gKLE8DFa2oyy7D-Ft/view?usp=sharing
[OnePlus 9 Pro] cat139lyleb:
I need to make sure if I'm correct, T-Mobile (LE2127) should be "AA" because I didn't find anywhere on this page with "ACB"?
[OnePlus 9 Pro] cat139lyleb:
Good news! Very top with AA (OP9P) and it finally work with LE2127!

But! still, a puzzle to me right after flashed it to LE2127 and itself Magisk was not able to find boot.img because of itself, Magisk thinks boot.img in Slot: _A and how we can change it to Slot: _B unless LE2127 does not have one?
[OnePlus 9 Pro] sam_htc_touch:
Hi Guys,

Many thanks for this wonderful thread that enabled me to easily root my 1 day old One Plus 9 Pro :) and get all the banking/payment apps and Netflix etc working flawlessly.

Perhaps a silly question - does anyone know what could be the reason that I am now missing Advanced Reboot option in Developer Options?

Also, the status bar has overlapping icons and even the button icons at the bottom are duplicated.

Pretty sure I would have messed up during some step which is causing these issues as I couldn't find anything about these in the quick search that I did. (Any tips on how to fix these without reinstalling WhatsApp etc would be greatly appreciated!)

Edit - Just to add, I can't seem to Boot to recovery either, even from within Magisk. Also, if it helps, I don't get that warning on booting about unlocked bootloader. Adaway etc work properly though.

Cheers
[OnePlus 9 Pro] mlord:
Reboot to (stock) recovery works for me from Magisk (LE2125).
[OnePlus 9 Pro] sieggie:
Same here. Are you on Android 12?

You can simply use an alternative launcher, like Nova launcher. Has your phone retained L1 widevine after root (you can check it with DRM Info App from playstore).
[OnePlus 9 Pro] sam_htc_touch:
I have managed to brick my phone and can't seem to revive it through MSM as well since apparently the MSM Tool linked in the first post by OP is for Android 11 / devices manufactured before Mar'21 only)

Yes, I was on 12 before managing to brick my phone y'day evening :-(

and C.47 (EU version)
[OnePlus 9 Pro] sieggie:
Have you installed the Qualcomm drivers that come with MSM tool? If you have, some people have reported that you actually need to klick the "start" button in MSM tool before you connect the phone. The restore process will then start once you connect it and cant be interrupted.
[OnePlus 9 Pro] neotion:
I had the same situation: phone updated to android 12 (C.47 - EU version)), then rooting failed, then phone fell into a fastboot loop, tried to get out of it and ended up phone not even turning on (only qualcomm mode was left). MSM restored it to the factory state with Android 11. Do everything as described, the most important thing is to upload the appropriate drivers, this is the most important thing for MSM to work.
[OnePlus 9 Pro] sam_htc_touch:
Thanks, managed to finally install all the necessary fastboot and Qualcomm drivers on my windows laptop! Believe it or not, I had been actually using my Chromebook (shell mode) to use fastboot so far!

Phone is now stuck in fastboot loop, wondering how to go to EDL Mode to use MSM Tools? Volume up and down keys while the phone is switched off doesn't seem to be doing the trick either.
[OnePlus 9 Pro] sam_htc_touch:
I seem to have the same issue now of being stuck with the fastboot loop (have tried the below commands as well:

fastboot flash boot_a boot.img

and

fastboot flash boot_b boot.img

(Am not able to go to recovery mode, was able to wipe the data though -

fastboot -w

How do I go to EDL Mode is what I am trying to figure out now :cool:
[OnePlus 9 Pro] sam_htc_touch:
Update - It seems I am able to go to EDL Mode as well now, will hopefully provide an update in an hour or so 🤞
[OnePlus 9 Pro] neotion:
If MSM doesn't want to work, it is definitely the fault of the qualcomm drivers. Don't panic then, just manually install / update the correct qualcomm drivers.
[OnePlus 9 Pro] sam_htc_touch:
Thank you, MSM worked after updating the Qualcomm Drivers ...A combination of XDA and YouTube worked :)
[OnePlus 9 Pro] Jed!Master:
how can I root a12 for tmobile? I want to root it cause all other rooms have some issues here and there and tmboile, unfortunately, has a stable from than anything out here. any way I can get the boot img of the stock mobile from
[OnePlus 9 Pro] TheGhost1951:
Where are you getting the boot image stock rom? I will need as soon as my unlock token arrives.
[OnePlus 9 Pro] TheGhost1951:
This is for Android 12 right?

What Android version were you on when you did this?
[OnePlus 9 Pro] AverageLibrarian:
i have a slight issue. after i do the adb reboot bootloader command, my device is no longer seen by adb. what am i missing?
[OnePlus 9 Pro] TheGhost1951:
If it boots to bootloader, then you are in fastboot mode not adb mode.
[OnePlus 9 Pro] ffejy462:
If you enter adb reboot bootloader command, you'll be in the bootloader which you'll then use fastboot commands.

ie

Adb devices will return a serial number of some sort while in the normal os

Fastboot devices command will return the same number in the bootloader