Database Info

Question Oneplus 9 LE2117 root process(T-Mobile)

With the differences between the EU, Global variants, and software versions listed in the threads I've gone through, I am having trouble finding a guide that I am sure would be applicable to root my Oneplus 9 LE2117 11.2.5.5-LE54CB. (T-Mobile)(US)
My device is SIM unlocked, and the bootloader is unlocked, but I am unsure of the best method to root.
Could anyone point me in the right direction?

Follow the steps to install magisk.

Superguy said:
Follow the steps to install magisk.
Click to expand...
Click to collapse
Thanks for the response. I believe that's the last step I have to complete to be done, but that is where I seem to be getting lost. I can't find a boot image for the specific model and software numbers I have. From the threads I have read I think I could use the boot image for software version 11.2.2.2 but I am uncertain.

I went ahead and used the boot.img for 11.2.2.2 and it looks like it worked.

captain_howdy said:
With the differences between the EU, Global variants, and software versions listed in the threads I've gone through, I am having trouble finding a guide that I am sure would be applicable to root my Oneplus 9 LE2117 11.2.5.5-LE54CB. (T-Mobile)(US)
My device is SIM unlocked, and the bootloader is unlocked, but I am unsure of the best method to root.
Could anyone point me in the right direction?
Click to expand...
Click to collapse
You need 11.2.5.5 boot.img from any region. Then follow the instructions install magisk.

just use the AA image for tmobile. patch the image with magisk the file will go to your download file then fastboot boot the img file from the one get from magisk after patching and you will gain temp root. direct install with magisk and reboot. if you get into a bootloop. reset devices from recovery and you will still retain root after the reset. i have installed empty slot ota and direct install. bootlooped on ota empty slot but reset from recover fixed problem instantly and retained root. direct install no bootloop retained root.

Does anyone care to comment with insights or experiences in regards
to Rooting with Magisk which will allow for the installation on a Custom ROM at a later time -
that is, when a stable Lineage OS for example is available for the OP-9 (t-Mobile) ?
Thank You in Advance !

I doubt it but anything is possible. with the process to convert to different variants being fairly simple and accessible there will be very little focus on that particular software. It is compatible with gloabal pathched boot image to gain root and from there your pretty much able to customize to do what ever your heart desires.

Superguy said:
Follow the steps to install magisk.
Click to expand...
Click to collapse
Can you direct me where to find that ?
I'm having difficulties getting anything to work...
If you are on the latest Tmobile update,you can use 11.2.8.8.img from either AA,BA or DA. the boot.img are all the same.
Click to expand...
Click to collapse
I'm on 11.2.6.6.LE54CB - and I thought the end two letters were Important ?

avid_droid said:
Negative. Letters don't matter. The latest update from T-Mobile normally correlates with the latest of AA,BA,DA. If you are on the 11.2.6.6 it's 11.2.8.8. any of the boot.img will work.
Click to expand...
Click to collapse
See, the thing is, I was so accustomed to having an Un-Locked device from t-Mo, I didn't realize that the Awesome Dude who un-locks the SIM, does not actually un-lock the Phone. So Much Bull**** from t-Mo...
ANy-Hoo... I just applied thru the OP site to get my 9 completely un-locked.
Thank You for Your Time and Response!

avid_droid said:
Negative. Letters don't matter. The latest update from T-Mobile normally correlates with the latest of AA,BA,DA. If you are on the 11.2.6.6 it's 11.2.8.8. any of the boot.img will work.
Click to expand...
Click to collapse
Quick little bump, but I'm on 11.2.7.7.LE54CB. Has anything still changed or would I still be good to go to use the 11.2.8.8. boot.img to root or the latest 11.2.9.9.LE25AA from OnePlus's site directly?

I have managed to install the Eurepean 11.2.9.9.LE15BA for the 9 PRO le2117
I have the tmobile 9 5g version not the pro. camera doesnt pull up but otherwise runs fine

Need help here! I forgot to backup my oneplus 9 pro LE2127 when I tried to root my phone using TWRP，and I installed TWRP in my phone's boot partition which wiped out all data in that partition. I used TWRP side loaded Global ROM to recover my phone but the phone doesn't have any signal with sim card in. Used MSM tool backe to T-Mobile 11.2.5.5 and still same problem, sim card can be read but no signal. Flashed T-Mobile modem but modem b failed, it says no such partition.
Bought this phone from third party. Any suggestion is appreciated.

Question Phone Hard Bricked in EDL mode

Hey!
Soooooo, I tried to update my OS to the most recent while rooted, but I accidentally locked my boot loader, bricked the software, tried to unbrick it, then later got hard bricked in EDL mode. I have tried using the MSM tool for the global version of the Oneplus 9 but it always ended up saying that the image didn't match or something (IDK the thing was in F’ing Chinese). This hard brick has gotten so bad that I cant even hold Vol up + Power to hard restart it. The screen just doesn't come on any more but is still recognized by my computer as a Qualcomm device. Does anyone know of a fix that doesn't include installing the Indian loader?
Model # LE2115 (OP9 Global)

I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for you.

chinbags said:
I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for you.
Click to expand...
Click to collapse
I had to do the same thing. I am using a LE2113 and managed to brick my phone in a way where only EDL could save it. I came from the latest OOS (colorOS) firmware and tried to flash LineageOS when everything went south. I tried to use the Oneplus 9 EU MSM tool but this one did not work for me. Since there is no official EU MSM for the LE2113 the only way I could repair it was by using the EU OnePlus 9 pro msm firmware. It only worked with the "use lite firehose" option for me. After that was done I unlocked the bootloader once again and flashed OOS (Android 11) for OnePlus 9 again. This was the way I got the original firmware back on my device although I do not think it would've been possible to relock the bootloader at this point.
Straight after that I once again flashed lineage and everything is working fine now. Certainly a shady approach but it is the end result that counts I'd say.

Nullifii said:
Hey!
Soooooo, I tried to update my OS to the most recent while rooted, but I accidentally locked my boot loader, bricked the software, tried to unbrick it, then later got hard bricked in EDL mode. I have tried using the MSM tool for the global version of the Oneplus 9 but it always ended up saying that the image didn't match or something (IDK the thing was in F’ing Chinese). This hard brick has gotten so bad that I cant even hold Vol up + Power to hard restart it. The screen just doesn't come on any more but is still recognized by my computer as a Qualcomm device. Does anyone know of a fix that doesn't include installing the Indian loader?
Model # LE2115 (OP9 Global)
Click to expand...
Click to collapse
That's not Chinese version m8 le2110 is, I bricked mine , I flashed it with global version , now it says it le2115 lol after OTA update to android 12 ??

jab5555 said:
That's not Chinese version m8 le2110 is, I bricked mine , I flashed it with global version , now it says it le2115 lol after OTA update to android 12 ??
Click to expand...
Click to collapse
That's the thing though. I had the LE2115 MSM tool but it was in Chinese for some reason I have a LE2115 phone as well but it said that the files didn't match up. Maybe they uploaded the wrong variant to the website? None of the tools that I had downloaded were in English, all in Chinese.

chinbags said:
I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for y
Click to expand...
Click to collapse

File folder on MEGA
mega.nz
This what I used m8, got it off OP when they tried to remote flash my phone , couldn't do it on AMD Ryzen, done on my old pc, driver issue lol, good luck m8

Question T-mobile oneplus 9 (LE2117) has an unlocked bootloader now?

Hello all, after lurking here for a while, I found something that's making me post.
I have a carrier locked OP9. I just received the update to Android 12, and it has broken critical features. (Particularly not being able to stop apps from being closed accidentally!)
I have looked at Lineage OS in the past, and the process to get the LE2117's bootloader unlocked was... complicated.
However, while trying to fix other problems, rooting around in the developer options, I noticed that "unlock bootloader" was actually toggleable!
I think I have an unlocked bootloader now, but it's on android 12, and all the guides for rooting and installing a custom MOD for this phone say you must revert to android 11 before anything else.
So what now? Am I waiting for lineageOS 19 to come out, because that's the one based on android 12? I'm new to custom roms, and don't get the coding side of how all this works. (But I'm pretty determined to figure this out.)
Thanks for any help or advice you've got!

each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!

Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.

dark_sable said:
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
Click to expand...
Click to collapse
I am pretty sure there is root for 12. All you need to do is dump the payload from the 12 update OnePlus let's loose, and patch it with magisk and flash it via fastboot. Via bootloader it is easy I am using a TMobile OnePlus 9. All you need to do is revert back to 11 via a msm tool. There is a post here for that. After downgrading to unlock your bootloader is easy only takes time. There is a post for it I don't remember all the details but all you have to do is get you imei code and email OnePlus. Soon they will sent you a code to fastboot flash to unlock the bootloader. After that most of these 12 work for us on our model phone. I am using evolution x. It tells me every day I can go to 12 .

funkybear34 said:
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Click to expand...
Click to collapse
Yes yes they do.

I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.

JimmyL216 said:
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
Click to expand...
Click to collapse
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.

EtherealRemnant said:
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
Click to expand...
Click to collapse
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode

JimmyL216 said:
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
Click to expand...
Click to collapse
What worked for me was shutting the phone off, removing my case, holding both volume up and down, then plugging the phone in. The screen won't show anything, you have to look at the MSM Tool and see that it's connected to know you did it right. Both times I tried it worked perfectly.
You can also use adb reboot edl if you can get the thing to boot and have USB debugging turned on.

Question Stuck on Oneplus 9 Pro Indian firmware

I attempted to convert my t-mobile oneplus 9 to international firmware by first flashing the Indian firmware.
I mistakenly downloaded the oneplus 9 PRO Indian msm.
I didn't realize this as the file has a very similar name. Lemonade_22.I.07_210412 vs Lemonadep_22_I.07_210412
I've tried everything since then, with no success. I tried to flash the correct oneplus 9 indian msm but it says incorrect device.
So I'm stuck with the oneplus 9 pro Indian firmware and can't get back to indian oneplus 9 firmware....

I have been developing and flashing android devices since the early days of Cyanogenmod... dozens of devices. And guess what? I did EXACTLY the same thing as you.
The link I downloaded from said it was Oneplus 9 firmware, and given the filenames being virtually identical, I never noticed it was the Oneplus 9 PRO firmware.
So don't feel too bad. Even experienced people can make mistakes when trying to flash phones!
I am working on a solution, but so far no luck because:
1. Msm Tool will not flash the Oneplus 9 firmware as it thinks it is the incorrect device (why did it let us flash the incorrect device firmware before???)
2. The bootloader is re-locked and the OEM Unlocking feature is greyed out in Developer options, therefore fastboot can't be used to re-flash the correct firmware.
3. The System Update "local upgrade" feature does not find ZIP files in the root folder and will not allow us to browse to the correct file.
So for now, we are stuck. I think solving #3 will be the solution. If we can make the "local upgrade" work, we should be able to flash the stock firmware ZIP.

@Derek6091 @mightysween did you fix it yet? I had my device screw up so bad today that the only MSM I could use on my global unit was the Indian 9 Pro firmware and I have gotten my device mostly working.
You can see my drama with it and how I finally got it working here.
[SOLVED] Can anyone help me unbrick? I have tried lite firehose, MSM for global, MSM for Indian 9 Pro, none work
I modded the global MSM so that it will flash to this frankenphone. https://forum.xda-developers.com/t/all-of-those-stuck-on-indian-firmware-rejoice-i-modded-the-global-msm.4442473/ EDIT: For anyone else trying this and getting unsupported...
forum.xda-developers.com
I can get it working with 11.2.10.10 but not OOS 12, in OOS 12 the touchscreen doesn't work and it shows dual SIM icons so it's still doing something that makes it think it's a foreign variant. I ended up just going back to StagOS where I was before everything got mucked up.
Unfortunately the MSMs still see it as an Indian variant so I can only flash the Indian OP9P firmware to it, tried all the other MSMs and none work. I have been reading threads here and people claim they got it back to global but I tried all of the suggestions and none of them restored the device enough to where the global MSM Tool didn't see it as an Indian model and refuse to flash so I think we are stuck with this frankendevice.

@EtherealRemnant Yes I had to do oem unlock while on the Indian firmware. If your phone has the oem unlock greyed out, there's a guide on how to fix that with a simple command line.
Then I unlocked bootloader, flashed lineage recovery then a custom ROM. Haven't tried to get back to stock rom, and I don't think we can.... But I love this rom I'm currently on which is stagos.
Feel free to message me for any questions you may have!
[ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonade][FINAL][08/09/2022]
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might...
forum.xda-developers.com

@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms

EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Nice glad you figured it out.

go17lyonjon said:
Nice glad you figured it out.
Click to expand...
Click to collapse
haha yeah I was a dog with a bone, wasn't gonna drop it lol.

EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Excellent. How did you do it? I would like to try with the T-Mobile MSM

Derek6091 said:
@EtherealRemnant Yes I had to do oem unlock while on the Indian firmware. If your phone has the oem unlock greyed out, there's a guide on how to fix that with a simple command line.
Then I unlocked bootloader, flashed lineage recovery then a custom ROM. Haven't tried to get back to stock rom, and I don't think we can.... But I love this rom I'm currently on which is stagos.
Feel free to message me for any questions you may have!
[ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonade][FINAL][08/09/2022]
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might...
forum.xda-developers.com
Click to expand...
Click to collapse
I can't find a working command line fix for the greyed out OEM unlock... which one did you use?

mightysween said:
I can't find a working command line fix for the greyed out OEM unlock... which one did you use?
Click to expand...
Click to collapse
Go to your home screen on your phone and connect to computer with usb debugging and run this command in cmd,
adb shell pm disable-user com.qualcomm.qti.uim
Then go to developer options and oem unlock should be able to toggle.

mightysween said:
Excellent. How did you do it? I would like to try with the T-Mobile MSM
Click to expand...
Click to collapse
You have to use the Oppo Decrypter tools. Decrypt the OPS file and open settings.xml. At the bottom of it there's a Target area. I just edited that to IN instead of O2 and re-packed it.

Derek6091 said:
Go to your home screen on your phone and connect to computer with usb debugging and run this command in cmd,
adb shell pm disable-user com.qualcomm.qti.uim
Then go to developer options and oem unlock should be able to toggle.
Click to expand...
Click to collapse
Perfect... thanks.

EtherealRemnant said:
You have to use the Oppo Decrypter tools. Decrypt the OPS file and open settings.xml. At the bottom of it there's a Target area. I just edited that to IN instead of O2 and re-packed it.
Click to expand...
Click to collapse
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.

mightysween said:
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
Click to expand...
Click to collapse
Manually flashing partitions in Fastboot does work, FYI. So it is possible to go back to stock that way once the bootoader is re-unlocked.
I wonder where the "target" data is stored on the actual device. If it is simply a numerical/text value in an accessible partition, seems like it would be pretty easy to make a TWRP flashable that can change it.

mightysween said:
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
Click to expand...
Click to collapse
Strange that it didn't work for you. That was indeed all I changed. Did you change it to what the unsupported target message said your device was? I was comparing the settings between India and global and besides the change of target ID, the target number on India was 3 instead of 1. No idea if that makes a difference though because I didn't try it.
You made sure to re-encrypt and replace the OPS, right?
Also yeah you can flash with fastboot, it doesn't fix that flag though and when I tried to go back to OOS 12 with the messed up flag it thought my device was a dual SIM device so there was no signal and the touchscreen didn't work. Happened twice. With the modified MSM I went back to global and am running OOS 12 right now.

EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Do you still have this file ? I flashed the OnePlus 9 pro indian firmware in msm since it's the only thing that worked and I want to go back to global

taintsx said:
Do you still have this file ? I flashed the OnePlus 9 pro indian firmware in msm since it's the only thing that worked and I want to go back to global
Click to expand...
Click to collapse
All you have to do to go back to global is download the full OTA for your device and flash it with the system updater.

EtherealRemnant said:
All you have to do to go back to global is download the full OTA for your device and flash it with the system updater.
Click to expand...
Click to collapse
Yea I tried that and had touchscreen not responding issues

taintsx said:
Yea I tried that and had touchscreen not responding issues
Click to expand...
Click to collapse
Then use the downgrade package. It will wipe your phone again but I will get you back to full OOS11 firmware and that issue won't happen.

EtherealRemnant said:
Then use the downgrade package. It will wipe your phone again but I will get you back to full OOS11 firmware and that issue won't happen.
Click to expand...
Click to collapse
Yea i tried that with
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
downgrade indian version 11.2.5.5 , unfortunately it just tells me it cannot read the file when i attempt to sideload

Question Using wrong boot .image?

Booted up a oneplus 9 pro boot image, it fixed my phone being stuck in fastboot because I didn't have stock image.
Now updates don't work.
Oneplus 9 T-Mobile, stock rom, pro boot image, unlocked bootloader, unlocked sim - Any help would be appreciated.
Was thinking MSM tool but unsure what one to use.

I'm in a similar situation but I can't get out of fastboot. What OnePlus Pro boot image did you flash to your phone and what firmware are you on?

I gave the pro boot.img a try and it worked!
I grabbed it from this post: https://forum.xda-developers.com/t/...t-keep-root-oos-12-c-48.4252373/post-87096189
I want to back a few things up before tinkering anymore but will report back on how I try to fix it.
Thinking ahead, did Oxygen Updater not allow you to change your device back to a OnePlus 9, download the software update, flash and revert back?

Glad you could get your phone fixed...
I wish my system updates worked though lol ugh

Harley1979 said:
Glad you could get your phone fixed...
I wish my system updates worked though lol ugh
Click to expand...
Click to collapse
Are you using Oxygen Updater or the native update tool?
If the latter I would try the former.
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com

No I'm on a t-mobile oneplus 9 with android 12.

Soooo have you tried Oxygen Updater?

No it doesn't work for my version of this phone.
Thanks though

I wish I had a copy of the original boot image of my phone, T-Mobile variant boot.imge I'm guessing and for the non-pro version. I'm assuming that may fix my issue with the T-Mobile system updates and my incompatibility app issues with Google Play...

Harley1979 said:
I wish I had a copy of the original boot image of my phone, T-Mobile variant boot.imge I'm guessing and for the non-pro version. I'm assuming that may fix my issue with the T-Mobile system updates and my incompatibility app issues with Google Play...
Click to expand...
Click to collapse
If your bootloader is unlocked and Google Play is telling you that your device is not supported, it's because of the unlocked bootloader most likely. Are you successfully passing both basic and CTS safetynet profiles?

Not sure sry... Only few apps are incompatible.
This is what the OnePlus updater shows.

Harley1979 said:
Not sure sry... Only few apps are incompatible.
This is what the OnePlus updater shows.
Click to expand...
Click to collapse
I think your problem is that your bootloader is unlocked and it needs to be locked in order to pass safeynet. More and more apps are not allowing for detected unlocked bootloaders in which makes safetynet fail.

Wish I knew how to relock it... Little reluctant to use a random site's information... Xda probably has information on relocking it, wish I had a link to a good post.

Could it possibly brick my phone if I'm using a pro boot image an try to lock bootloader?
Any advice or help would be much appreciated thanks for your time.

I will follow-up more later as I'm walking out the door. I'm not convinced that we are on a different or should I say, incompatible boot.img. When I get home I need to do some research to see what is actually different in the boot.img when being compared each other (C.61 boot.img on OP9 and OP9 Pro).
Back history for anyone following along... I was unlocked, rooted, Google Play certified and on C.48. I upgraded via OTA, no reboot and chose an inactive slot. It did not work and soft bricked slot a. I lost root, was on C.48 still but on slot B. I successfully upgraded to C.61 but didn't have root. I could not find a good boot.img or patched_boot.img. I tried a stock OP9 Pro image and that got me working. That same user provided a patch img too so I tried that and obtained root as well.
Soooo what is the difference between the boot images on C.61 pro and non-pro OP9 models?
Stay tuned....!

Thanks I'll keep checking back on this

Unfortunately the difference is that the pro version is available to tinker with and the non pro version isn't. Sorry to state the obvious.

My phone so far is working fine on the OP9 Pro kernel. C.61 is rooted and Google Play is certified. All my previous Magisk config is there as well and modules. I'm not sure what the difference between the kernels are at this point but also not a kernel expert either.
Once the next full release comes out for OP9, I will swap it out.
@Harley1979 I got your PM and will follow-up with you there.