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.
Related
Hi again everyone, title pretty much says it all. I'm not too great with rooting, so I was wondering if I can keep twrp, magisk and root from 9.5.3 and download and install the new 9.5.6 OTA update for the GM21AA OP7 Pro, or if I'll have to do separate steps to be able to keep root. The update is 178MB
Don't do like me. I updated to 9.5.6, rebooted and update went ok, but I lost root. Thought there would be a patched boot image already but havent found one.
update: go here
go to Post #299
dy2592 said:
Don't do like me. I updated to 9.5.6, rebooted and update went ok, but I lost root. Thought there would be a patched boot image already but havent found one.
Click to expand...
Click to collapse
Just open the downloaded ota, rip the boot.img from that file. Patch manually in magisk that boot.img. Then install the update, and reboot afterwards to fastboot mode. Flash the patched img and you are done.
Lucifer6 said:
Hi again everyone, title pretty much says it all. I'm not too great with rooting, so I was wondering if I can keep twrp, magisk and root from 9.5.3 and download and install the new 9.5.6 OTA update for the GM21AA OP7 Pro, or if I'll have to do separate steps to be able to keep root. The update is 178MB
Click to expand...
Click to collapse
Post 6 in this thread is how I did it and retained root, but I lost TWRP (I knew I would before doing it) I used the steps used for the OnePlus 6t for rooted users, knowing I would lose TWRP.
https://forum.xda-developers.com/oneplus-7-pro/help/t-mobile-converted-to-9-5-4-received-t3934761
These are the steps for the 6t for TWRP users but I know TWRP is having decryption issues so I'm not sure if the below will work.
1. Boot into TWRP and Flash the Latest Magisk Uninstaller
2. Flash the latest Full Oxygen OS Zip
3. Flash the TWRP installer Zip
4. Reboot to RECOVERY to make sure TWRP stays and continue to root.
5. Flash the Latest Magisk to maintain root
6. Reboot System and Enjoy the latest firmware without any data loss
Lucifer6 said:
Hi again everyone, title pretty much says it all. I'm not too great with rooting, so I was wondering if I can keep twrp, magisk and root from 9.5.3 and download and install the new 9.5.6 OTA update for the GM21AA OP7 Pro, or if I'll have to do separate steps to be able to keep root. The update is 178MB
Click to expand...
Click to collapse
A partial ota with unlocked bootloader will brick your phone. Download the full zip and update in TWRP if you have it. If bootloader locked, install as normal, wait for it to finish and ask to reboot, don't reboot and open magisk manager and install to inactive slot. Reboot. That process will cause you to lose TWRP if you have it. If you have TWRP, flash full ROM in TWRP, flash TWRP.zip, reboot recovery and flash magisk.zip.
This way is easy and painless.
Yep performed the system update as well. It saw I was rooted and proceeded to download the full OTA. I let it update, did not reboot. Went to Magisk and Install to Inactive Slot(After OTA) and all is well. Im still rooted.
Posted by another user and the way I just did 9.5.6. Yes you will lose TWRP as usual if installed.
schmeggy929 said:
This way is easy and painless.
Yep performed the system update as well. It saw I was rooted and proceeded to download the full OTA. I let it update, did not reboot. Went to Magisk and Install to Inactive Slot(After OTA) and all is well. Im still rooted.
Posted by another user and the way I just did 9.5.6. Yes you will lose TWRP as usual if installed.
Click to expand...
Click to collapse
So dumb question here since I'm sorta new with this device (I've had Samsung and other devices that I've rooted so I'm aware of the basics).
Where do I download the entire fastboot zip files for say 9.5.6.GM31CB (TMobile variant)? I can't find it on OnePlus or T-Mobile. Also side question, do we still need to use Chinese certain of TWRP to get decryption working for internal storage? Thank you for whatever info you can provide.
I wonder, is there a patch for 9.5.6 yet? Let's say I have a locked bootloader now and stock on 9.5.6, how would I go about rooting my device? Or will I have to wait for the patched boot.img?
Lucifer6 said:
I wonder, is there a patch for 9.5.6 yet? Let's say I have a locked bootloader now and stock on 9.5.6, how would I go about rooting my device? Or will I have to wait for the patched boot.img?
Click to expand...
Click to collapse
Not if you unlock it, install magisk and patch the boot image within the app. I'd suggest looking for full zip of 9.5.6 just to use in case.
Which TWRP are you guys using? I see there is a Chinese version with decrypt working. Is that one safe?
photolarry said:
So dumb question here since I'm sorta new with this device (I've had Samsung and other devices that I've rooted so I'm aware of the basics).
Where do I download the entire fastboot zip files for say 9.5.6.GM31CB (TMobile variant)? I can't find it on OnePlus or T-Mobile. Also side question, do we still need to use Chinese certain of TWRP to get decryption working for internal storage? Thank you for whatever info you can provide.
Click to expand...
Click to collapse
There doesn't seem to be any fastboot ROM for the T-Mobile variant nor any Full OTA zips yet. Just have to keep looking in the PRO Guides, News and Discussion section. Personally I would not use that version of TWRP. Im waiting for the other TWRP by Maurinofrio to get Decrypt working.
schmeggy929 said:
There doesn't seem to be any fastboot ROM for the T-Mobile variant nor any Full OTA zips yet. Just have to keep looking in the PRO Guides, News and Discussion section. Personally I would not use that version of TWRP. Im waiting for the other TWRP by Maurinofrio to get Decrypt working.
Click to expand...
Click to collapse
So weird they claim they are as friendly to developers as pixel yet I don't see links to firmware. Not sure if I'm going to even bother rooting without backup of a full zip with all images inside. I guess I could get 9.5.3 and then do a few upgrades to get back to 9.5.6 but I'd rather have full file for 9.5.6.GM31CB
photolarry said:
So weird they claim they are as friendly to developers as pixel yet I don't see links to firmware. Not sure if I'm going to even bother rooting without backup of a full zip with all images inside. I guess I could get 9.5.3 and then do a few upgrades to get back to 9.5.6 but I'd rather have full file for 9.5.6.GM31CB
Click to expand...
Click to collapse
They are as developer-friendly as Pixel phones, (when you buy unlocked directly from OnePlus) not the T-Mobile version. Buy a Pixel from Google it OEM unlock to unlock the bootloader, buy a 7 Pro from OnePlus it's OEM unlock to unlock the bootloader.
In addition about you going to 9.5.3 and then upgrading to get back to 9.5.6
The 9.5.6 you're currently running on the T-Mobile version is not the same as 9.5.6 on the unlocked version. The unlocked version is a few builds newer.
If I were you I'd wait till the MSM tool that works with the T-Mobile version is released.
bp328i said:
They are as developer-friendly as Pixel phones, (when you buy unlocked directly from OnePlus) not the T-Mobile version.
In addition about you going to 9.5.3 and then upgrading to get back to 9.5.6
The 9.5.6 you're currently running on the T-Mobile version is not the same as 9.5.6 on the unlocked version. The unlocked version is a few builds newer.
If I were you I'd wait till the MSM tool that works with the T-Mobile version is released.
Click to expand...
Click to collapse
Msm tool? I'll get an unlock token Friday. Why would I need that? Newer than 9.5.6.GM31CB? I don't think so. This includes April security patch. I'm guessing the only big difference is the radio image is different for TMobile. Again I'm new to this mfgr so I'm trying. They aren't making it easy for me. I have an unlock phone. So shouldn't matter if I got it from T-Mobile. I can OEM unlock. So I can manipulate at will. Trouble is I'm scared I'll break the phone since I don't know this line of Android devices. I considered changing this to international but afterwards in worried it'll not work well in T-Mobile
photolarry said:
Msm tool? I'll get an unlock token Friday. Why would I need that? Newer than 9.5.6.GM31CB? I don't think so. This includes April security patch. I'm guessing the only big difference is the radio image is different for TMobile. Again I'm new to this mfgr so I'm trying. They aren't making it easy for me. I have an unlock phone. So shouldn't matter if I got it from T-Mobile. I can OEM unlock. So I can manipulate at will. Trouble is I'm scared I'll break the phone since I don't know this line of Android devices. I considered changing this to international but afterwards in worried it'll not work well in T-Mobile
Click to expand...
Click to collapse
There are a lot more changes in the international 9.5.6 GM21AA then that. they optimized double tap to wake and ambient display, fixed Bluetooth headset delays, camera updates, and other things.
The T-Mobile version will always be behind on software verse the international version.
bp328i said:
There are a lot more changes in the international 9.5.6 GM21AA then that. they optimized double tap to wake and ambient display, fixed Bluetooth headset delays, camera updates, and other things.
The T-Mobile version will always be behind on software verse the international version.
Click to expand...
Click to collapse
So are you saying I should update to AA? Even if I'm on T-Mobile network?? Will that not mess with the radio?
photolarry said:
So are you saying I should update to AA? Even if I'm on T-Mobile network?? Will that not mess with the radio?
Click to expand...
Click to collapse
That's the main reason everyone with the T-Mobile version is trying to unlock their bootloader, so they can run the international software. T-Mobile's software will always be behind the unlocked version. 9.5.3 for the unlocked version had the April security patch, that was three versions ago.
I owned the T-Mobile version of the 6t and the unlocked version of the 6t, the reception was the same.
My T-Mobile 7 Pro is unlocked running the international GM21AA software on T-Mobiles network. I uninstalled the Renovate Ice ROM for the screenshot so you can see I have the same model number as you running GM21AA.
But currently if you mess up a T-Mobile version there's no way to get it back because the MSM tool for it is not available yet. If something goes wrong you might be stuck with a phone that doesn't work until it's released.
bp328i said:
That's the main reason everyone with the T-Mobile version is trying to unlock their bootloader, so they can run the international software. T-Mobile's software will always be behind the unlocked version. 9.5.3 for the unlocked version had the April security patch, that was two versions ago.
I owned the T-Mobile version of the 6t and the unlocked version of the 6t, the reception was the same.
My T-Mobile 7 Pro is unlocked running the international GM21AA software on T-Mobile. I uninstalled the Renovate Ice ROM for the screenshot so you can see I have the same model number as you running GM21AA.
But currently if you mess up a T-Mobile version there's no way to get it back because the MSM tool for it is not available yet.
Click to expand...
Click to collapse
Thank you for your feedback. It's helpful to me. I am guessing an msm tool is something that puts stock firmware onto the device fresh in case you brick it. Couldn't I just fastboot flash 9.5.3 full package which I think is downloadable within OnePlus support?
photolarry said:
Thank you for your feedback. It's helpful to me. I am guessing an msm tool is something that puts stock firmware onto the device fresh in case you brick it. Couldn't I just fastboot flash 9.5.3 full package which I think is downloadable within OnePlus support?
Click to expand...
Click to collapse
Correct about the tool, returns the phone to 100% stock out of the box. Not 100% sure about whether or not the fastboot flash would fix a soft bricked device. That could possibly work.
But I know currently it's impossible to go back to T-Mobile software without the tool.
has anyone contact oneplus support either via email and chat and requested full ROM download links?
theyre pretty helpful like that.
Hi there, I have the GM1925 (Sprint) model of the OnePlus 7 Pro 5G.
I'm running stock OOS 10.0.3GM25CC, rooted with Magisk, substratum, and an unlocked bootloader.
It's been years since I've run a stock ROM, so I really have no concept of how OTA updates work (I've always just flashed updates via TWRP). A couple days ago I got a system update notification for a 199MB download, and I'm wondering if it's "safe" to apply it, or if I need to do anything special first.
From what I've read online here and in the OnePlus forums, the recommendation is to do a "full" local update (something like a 2GB download), however the sprint firmware for the GM1925 doesn't have such an option in the system updates settings.
Can I apply this update safely without losing any of my data? Is there a guide somewhere for how to apply and survive OTA updates?
Update: I'm now getting notifications from Google Play Services saying "Couldn't install update" despite the fact that I haven't *tried* to install it.
Any advice? Is it safe to install? I don't want to wind up with a brick that I'll have to reflash and set up again.
Narwhal73 said:
Update: I'm now getting notifications from Google Play Services saying "Couldn't install update" despite the fact that I haven't *tried* to install it.
Any advice? Is it safe to install? I don't want to wind up with a brick that I'll have to reflash and set up again.
Click to expand...
Click to collapse
From my experience from last incremental updates(onePlus7pro5g) I've just had to boot to recovery and flash twrp and magisk again..
You said you rooted and unlocked bootloader, just wondering if you could lmk how you did it, I have the same device and have been struggling.
Shooter7889 said:
From my experience from last incremental updates(onePlus7pro5g) I've just had to boot to recovery and flash twrp and magisk again..
Click to expand...
Click to collapse
When you say reboot to recovery and flash twrp again, do you mean reboot to the bootloader?
Did you do anything before applying the OTA, like disabling magisk mods?
EDIT: Also, do you have the Sprint model & firmware?
Cody719 said:
You said you rooted and unlocked bootloader, just wondering if you could lmk how you did it, I have the same device and have been struggling.
Click to expand...
Click to collapse
This is a bit off-topic I guess, but info to unlock the bootloader is here:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
You'll need a Windows computer to use the MSMTool in that thread. Also, pro-tip: uncheck the automatic reboot option in the MSMTool GUI to make your life easier when you have to reboot to the bootloader to run the fastboot commands.
If all goes well, you'll be running Android 9. Surprisingly that OS version claimed my phone was SIM-locked -- but applying the Android 10 OTA update fixed this issue. Then I rebooted to the bootloader, flashed TWRP, rebooted to recovery and flashed Magisk to root the phone.
Narwhal73 said:
When you say reboot to recovery and flash twrp again, do you mean reboot to the bootloader?
Did you do anything before applying the OTA, like disabling magisk mods?
EDIT: Also, do you have the Sprint model & firmware?
Click to expand...
Click to collapse
In developer settings I turn on advanced reboot options, so I can easily hold the power button and it shows all the options(power off, reboot, recovery, bootloader, screenshot). If u have twrp fully installed u can just click recovery and then reflash twrp and magisk and reboot. About disabling magisk mods, yeh I always disabled rice and all others that may cause problems. But on this latest 10.4 update, I had apparently done something where I cldnt even get my system updates to download it. So I just ended up msm'ing my phone and then BL unlocking, updating to 10.4,then doing magisk and mods..?
There's a great telegram group with all the info for gm1925/1920 onePlus7pro 5g, should def go check it out, alot of help there.
Shooter7889 said:
There's a great telegram group with all the info for gm1925/1920 onePlus7pro 5g, should def go check it out, alot of help there.
Click to expand...
Click to collapse
What's the name of that Telegram group? The only one I can find for the 5G version is the McLaren 7 Pro.
I've also got the Sprint oneplus 7g Pro 5G/gm1925, and I am getting the notification for the update but am not able to install it. There is no option for the full download in order to use the methods described for other models. Would really like to get this resolved without having to do a full rewipe and flash, that's for sure.
I'm still holding off on applying this OTA until I can get some more info. I also couldn't find the aforementioned telegram group
Bumping this thread because there still doesn't seem to be a good guide for stock OTA updates on the GM1925.
I'm interested in doing this aswell. I have OP7Pro Sprint too. Just bootloader unlocked and magisk nothing else.
Though I have software version NoLimits IDK if that can be OTA'd.
Narwhal73 said:
Hi there, I have the GM1925 (Sprint) model of the OnePlus 7 Pro 5G.
I'm running stock OOS 10.0.3GM25CC, rooted with Magisk, substratum, and an unlocked bootloader.
It's been years since I've run a stock ROM, so I really have no concept of how OTA updates work (I've always just flashed updates via TWRP). A couple days ago I got a system update notification for a 199MB download, and I'm wondering if it's "safe" to apply it, or if I need to do anything special
Can I apply this update safely without losing any of my data? Is there a guide somewhere for how to apply and survive OTA updates?
Click to expand...
Click to collapse
Basically you need to back up all your data and your storage card area off the phone. Then you have to relock the bootloader to apply the update.( Relocking bootloader will wipe the phone. )
After applying update, unlocked bootloader again root and restore your data and files.
you will have to do this everytime sprint/t-mobile releases update. If you want to stay up to date. And you will get the Google nag at least once weekly until you do
schn1tt3r said:
I'm interested in doing this aswell. I have OP7Pro Sprint too. Just bootloader unlocked and magisk nothing else.
Though I have software version NoLimits IDK if that can be OTA'd.
Click to expand...
Click to collapse
Same here, but what I want to do instead of waiting for the OTA update from Sprint it's to flash the original ROM from OnePlus but I'm not sure which version could be compatible.
I received a Oneplus 8t (Cyberpunk Edition). The phone was supposed to have HydrogenOS as it is a Chinese phone. However, the vendor installed Global OxygenOS (KB05AA). After OTA updates, the phone wouldn't reboot and would get stuck on the Cyberpunk boot animation.
________________________________________
OxygenOS
I tried updating/restoring OxygenOS using the the MSM download tools here:
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Pros: Google Apps and a Global ROM.
Cons: No OTA updates and no original Cyberpunk theme.
Best case scenario for OxygenOS users would be for Oneplus to fix the OTA updates for Cyberpunk phones. This would stop the bootloop problem people are having.
________________________________________
HydrogenOS
I have made a guide on how to restore HydrogenOS and add Google Apps:
Oneplus 8T (Cyberpunk Edition) - HydrogenOS (Google Apps, Theme, OTA Updates!)
Originality/HydrogenOS If you have a Chinese Cyberpunk Edition phone with OxygenOS, you'll notice that the Cyberpunk theme/assets are missing, and OTA updates lead to a boot loop. This guide will tell you how to restore the phone to its original...
forum.xda-developers.com
Pros: Working OTA updates, the original Cyberpunk theme, and Google Apps!
Cons: A little bit of time and maintenance.
________________________________________
Overall I would highly recommend trying the HydrogenOS solution I've linked above. It works excellent for me, so I won't be pursuing a solution for OxygenOS unless things change. The guide I wrote and linked above should get anyone with a Cyberpunk phone on to HydrogenOS (with OTA updates, original theme, and Google Apps).
________________________________________
Bounty: Claimed by @Steve0007
Up to @Arr6 if he still wants to match my donation for the HydrogenOS solution.
Hi,
so even if we flash full OTA zip file of 11.0.5.6KB05AA version (or EU version) from the HydrogenOS, for future update we will not be able to use phone OTA?
Thanks,
shadww said:
Hi,
so even if we flash full OTA zip file of 11.0.5.6KB05AA version (or EU version) from the HydrogenOS, for future update we will not be able to use phone OTA?
Thanks,
Click to expand...
Click to collapse
Your results may vary, but OxygenOS' (KB05AA) OTA updates aren't currently meant for the Cyberpunk phone. Many people have gotten the bootloop issue on OTA updates.
OniAraAra said:
Your results may vary, but OxygenOS' (KB05AA) OTA updates aren't currently meant for the Cyberpunk phone. Many people have gotten the bootloop issue on OTA updates.
Click to expand...
Click to collapse
Ok, so I have tried updating using EU version "Oxygen_15.E.21_OTA_0210" ==> resulted in bootloop. I wiped the phone and back to hydrogenOS.
Now I will see if I can flash the Global version and update this reply.
Edit:
flashing global full OTA "15.O.20_OTA_0200" also resulted in bootloop. I wiped and back to hydrogenOS.
only thing is confusing me is... how did the vendor install global oxygenOS and sell to people.
I've tried to contact their support team, so far 5 days no answer - I'm as confused as you @shadww... I'm currently just using it as a regular 8T, I've never had the phone in Hydrogen OS tho - build is Oxygen OS 11.KB05AA and update is to Oxygen OS 11.0.5.6.KB05AA...
shadww said:
only thing is confusing me is... how did the vendor install global oxygenOS and sell to people.
Click to expand...
Click to collapse
I was thinking the same thing
Nables said:
I've tried to contact their support team, so far 5 days no answer - I'm as confused as you @shadww... I'm currently just using it as a regular 8T, I've never had the phone in Hydrogen OS tho - build is Oxygen OS 11.KB05AA and update is to Oxygen OS 11.0.5.6.KB05AA...
Click to expand...
Click to collapse
Have you tried to do the OTA update?
I also have the 8T Cyberpunk edition running on 11.0.4.5.KB05AA right now, i have SOME Cyberpunk things (theme as well as always on display clock (no wallpapers) i have tried to install newest update with Full zip and gets me to bootloop, ill be in touch in case i am able to achieve anything.
I have already said they hacked the phones. I wouldn't be surprised if the Chinese sellers have a half decent working TWRP that they aren't sharing
g96818 said:
I have already said they hacked the phones. I wouldn't be surprised if the Chinese sellers have a half decent working TWRP that they aren't sharing
Click to expand...
Click to collapse
Hacked, how so? It seems like all they did was obtain/install the KB05AA ahead of schedule. I guess it's all hearsay, either way.
I received my 8T Cyberpunk 3 days ago. I've requested the Seller to ship it off with HydrogenOS as stock so I can still have the original themes. They've also taken the liberty to install GApps on my HydrogenOS as well. So right now I can use Google Services and GPay. They have deleted all the Chinese Bloatware (But still kept Market, Wallet, Browser).
Running: Hydrogen OS 11.0.5.6.KB05
PRO:
GoogleApps (Playstore, Play Protect, Google Pay)
Original CyberPunk Theme with HydrogenOS
OTA HydrogenOS Update with no problems
CON:
AndroidAuto does not work.
Google BackUp does not work (Only Google Photo backup works)
Google Assistant can be dodgy.
Where did you buy please?
Arr6 said:
Have you tried to do the OTA update?
Click to expand...
Click to collapse
Yep - results in bootloop so I stopped trying and waiting for a solution or response from Oneplus. Currently using my phone as a regular 8T (with no cyberpunk theme)
Hmm I just ordered the Cyberpunk edition and now I'm worried we won't be able to update. Maybe the next update will resolve the issue?
Hi,
So I have some good news (I think).
I was trying to flash OxygenOS (Global and EU) on my HydrogenOS (11.0.4.5) Cyberpunk8T. It ended me bricking my device. (Yes, I was fooling around with fastbootd >_<)
I went to this thread: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
and used the MSM tool @OniAraAra linked: https://androidfilehost.com/?w=files&flid=320230
I was able to get back to HOS (11.0.1.2). So this even downgraded my version, and I had all cyberpunk elements.
Then it hit me. I was trying to figure out how did the sellers flash the global OOS.... and most of xda members here state that their device came on "11.0.4.5.KB05AA ", and it had " SOME Cyberpunk things ".
So I went and did an MSM restore on my Cyberpunk8T HOS (11.0.1.2) to EU OOS 11.0.4.5 (from unbrick-tool thread above). Guess what it worked. I was able to boot to EU OOS 11.0.4.5.
Then right away, I did a local OTA upgrade using full package EU OOS 11.0.5.6 (https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/).
I booted to EU OOS 11.0.5.6, have cyberpunk boot animation, wallpapers, theme, icon pack, and sounds (basically everything, let me know if I should check something specific).
ps: I also heard that local upgrade is not available on Global or India OOS, thats why I tried it on EU. Not sure if one does EU MSM, then flash Global Full OTA locally if that might work or not.
Edit:
Uploading some videos (higher quality might some time to process)
shadww said:
Hi,
So I have some good news (I think).
I was trying to flash OxygenOS (Global and EU) on my HydrogenOS (11.0.4.5) Cyberpunk8T. It ended me bricking my device. (Yes, I was fooling around with fastbootd >_<)
I went to this thread: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
and used the MSM tool @OniAraAra linked: https://androidfilehost.com/?w=files&flid=320230
I was able to get back to HOS (11.0.1.2). So this even downgraded my version, and I had all cyberpunk elements.
Then it hit me. I was trying to figure out how did the sellers flash the global OOS.... and most of xda members here state that their device came on "11.0.4.5.KB05AA ", and it had " SOME Cyberpunk things ".
So I went and did an MSM restore on my Cyberpunk8T HOS (11.0.1.2) to EU OOS 11.0.4.5 (from unbrick-tool thread above). Guess what it worked. I was able to boot to EU OOS 11.0.4.5.
Then right away, I did a local OTA upgrade using full package EU OOS 11.0.5.6 (https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/).
I booted to EU OOS 11.0.5.6, have cyberpunk boot animation, wallpapers, theme, icon pack, and sounds (basically everything, let me know if I should check something specific).
ps: I also heard that local upgrade is not available on Global or India OOS, thats why I tried it on EU. Not sure if one does EU MSM, then flash Global Full OTA locally if that might work or not.
Edit:
Uploading some videos (higher quality might some time to process)
Click to expand...
Click to collapse
That is interesting. I wonder if there's just a problem with the international OTA file?
lexcyn said:
That is interesting. I wonder if there's just a problem with the international OTA file?
Click to expand...
Click to collapse
Not really sure. I did try previously local OTA to full EU OOS, but had the bootloop issue similar to international/global OTA.
There is also always the possibility that seller did not do proper global MSM revert? or that going to HOS and then again to OOS might do the trick? (not really sure here, I am just stating random possibilities)
Good thing is one can easily test using MSM tool to revert back.
shadww said:
Hi,
So I have some good news (I think).
I was trying to flash OxygenOS (Global and EU) on my HydrogenOS (11.0.4.5) Cyberpunk8T. It ended me bricking my device. (Yes, I was fooling around with fastbootd >_<)
I went to this thread: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
and used the MSM tool @OniAraAra linked: https://androidfilehost.com/?w=files&flid=320230
I was able to get back to HOS (11.0.1.2). So this even downgraded my version, and I had all cyberpunk elements.
Then it hit me. I was trying to figure out how did the sellers flash the global OOS.... and most of xda members here state that their device came on "11.0.4.5.KB05AA ", and it had " SOME Cyberpunk things ".
So I went and did an MSM restore on my Cyberpunk8T HOS (11.0.1.2) to EU OOS 11.0.4.5 (from unbrick-tool thread above). Guess what it worked. I was able to boot to EU OOS 11.0.4.5.
Then right away, I did a local OTA upgrade using full package EU OOS 11.0.5.6 (https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/).
I booted to EU OOS 11.0.5.6, have cyberpunk boot animation, wallpapers, theme, icon pack, and sounds (basically everything, let me know if I should check something specific).
ps: I also heard that local upgrade is not available on Global or India OOS, thats why I tried it on EU. Not sure if one does EU MSM, then flash Global Full OTA locally if that might work or not.
Edit:
Uploading some videos (higher quality might some time to process)
Click to expand...
Click to collapse
That is pretty much what I am looking for! Cyberpunk theme with Oxygen OS and OTA updates. It seems from your method you can do the OTA updates. I assume this method will reset the whole phone correct?
Regarding version, does it matter If I use Global or EU? I am in US and everything has been working with phone service with the global OS, just no cyberpunk themes or OTA updates
Arr6 said:
That is pretty much what I am looking for! Cyberpunk theme with Oxygen OS and OTA updates. It seems from your method you can do the OTA updates. I assume this method will reset the whole phone correct?
Regarding version, does it matter If I use Global or EU? I am in US and everything has been working with phone service with the global OS, just no cyberpunk themes or OTA updates
Click to expand...
Click to collapse
1) So, it looks like fine to update through full OTA (EU) for me. I wonder if in the future I will have to wait for full OTA updates or can do incremental ones too (won't know until tested in the future).
2) Yes, this method will reset/wipe the phone. (see: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/ )
3) Regarding EU vs Global, I think there might be difference in some apps. However, I believe that bands information are stored seperate to the ROM, so EU or Global OOS should work fine from operation stand point. Also, I am not sure about 5G though, as I heard US has different standard or something. Not sure if that is also affected by OOS verison (I think it should be hardware thing though).
shadww said:
1) So, it looks like fine to update through full OTA (EU) for me. I wonder if in the future I will have to wait for full OTA updates or can do incremental ones too (won't know until tested in the future).
2) Yes, this method will reset/wipe the phone. (see: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/ )
3) Regarding EU vs Global, I think there might be difference in some apps. However, I believe that bands information are stored seperate to the ROM, so EU or Global OOS should work fine from operation stand point. Also, I am not sure about 5G though, as I heard US has different standard or something. Not sure if that is also affected by OOS verison (I think it should be hardware thing though).
Click to expand...
Click to collapse
When doing full OTA, does that wipe your phone? just wondering because im worried ill have to wipe everytime o get an update. regardless i will be testing your trick later on today !
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.
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