alright here is newest beta (U2ZQKM)
, *link removed, give up trying to help*
this updates your bootloader, so you cannot roll back if you do this.
You need to odin back to AGQL (only flash AP,CP and BL if you want to keep data), ota to QJC through stock recovery with this zip (https://drive.google.com/uc?id=1clYBB5bB55rxaGBQJ0SM195wXHqgiYCC&export=download) , then use this to ota again through stock recovery. Between the odin and recovery flashes, do not go back into system. Boot from odin flash directly into stock recovery, then again from first ota back into stock recovery.
This is for tech savvy people only, and for snaodragon version only.
Thanks to @norbarb for everything she has done for this community, none of us would have oreo beta at all unofficially if it wasn't for her.
NOTES:
1.This is for an at&t S8. (Since that's mentioned nowhere and this isn't the at&t s8 section)
2.If you're on unlocked firmware and you've updated to the latest QK2 your bootloader is updated and you can't Odin back to anything sooner.
3.The wording of your instructions is awful btw
joe3681 said:
For what carrier cause those build numbers aren't unbranded G950u1 numbers.
If you've updated to the latest QK2 your bootloader is updated and you can't Odin back to anything sooner.
The wording of your instructions is awful btw
Click to expand...
Click to collapse
I took it from ATT server but it is for any Snapdragon version.
I can delete it if no one wants it. Just trying to help
It's gone. Enjoy.,
Pardon my honesty, hungover and confused AF by the wording and having to search up build numbers. That would be greatly appreciated in the att section though!
You didn't have to take your call and go home but okay ?
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.
Alright so I have a T-Mobile OP7 pro. It came with 9.5.3 GM31CB installed. Everytime I try to OTA update it I get the generic installation error. I've factory reset, reset cache, etc.
The general consensus around here seems to be to flash it to the international firmware. Is there anyway to flash it to a newer build of the T-Mobile firmware and hopefully receive OTA updates in the future with no problems? I understand the flashing process but it seems like getting the T-Mobile zip file would be the problem.
Any suggestions to make my OTA install work or to flash it to the current T-Mobile version, which I believe is 9.5.10 GM31CB, would be greatly appreciated.
So I think I found what I need in the One Plus 7 Pro MSM tool. But all the guides are for switching from TMO to international or from international back to TMO. If I am going TMO to TMO do I still need som unlock and root access?
MSM tool flashing a T-Mobile version seems to work well. I used the first MSM T-Mobile thread posted in the past and then was able to OTA update to current. The only trick is to use the MSM tool and get any OTA updates applied before modifying. It looks like there are newer T-Mobile MSM versions, but I can only vouch for the efficacy of the first such thread's version since I haven't tried the newer versions.
jhofseth said:
MSM tool flashing a T-Mobile version seems to work well. I used the first MSM T-Mobile thread posted in the past and then was able to OTA update to current. The only trick is to use the MSM tool and get any OTA updates applied before modifying. It looks like there are newer T-Mobile MSM versions, but I can only vouch for the efficacy of the first such thread's version since I haven't tried the newer versions.
Click to expand...
Click to collapse
I finally got it to work, thanks for your input. I've flashed with Odin but this was my first OP flash.
So I've got a TMobile OnePlus 9 that's been converted to the global ROM. From here what's the easiest way to get updated to stock OxygenOS Android 13? When I run the system update in settings it'll update to Android 12 but the phone says that there's no sim card in. Am I doing something wrong? I don't mind unlocking the bootloader and flaking a recovery if there's a stock rooted zip I can flash.
I've tried myself but updating anything to 12 and up my touchscreen stops working, but using the TMobile India modded MSM should work getting to the global rom "but now realizing it was cuz I used something else to recover from a brick" but here
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
th
underworld737 said:
I've tried myself but updating anything to 12 and up my touchscreen stops working, but using the TMobile India modded MSM should work getting to the global rom "but now realizing it was cuz I used something else to recover from a brick" but here
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
Click to expand...
Click to collapse
thanks I'll ck it out
this doesn't work for my device le2119 the mod fix zip throws an error unsupported device eu. I made the mistake of activating slot b. is there any way of switching back without fastboot. all I get is a black screen no matter what button combo I press. I can only get edl and I'd rather not flash the eu msm again.
paulb1977 said:
this doesn't work for my device le2119 the mod fix zip throws an error unsupported device eu. I made the mistake of activating slot b. is there any way of switching back without fastboot. all I get is a black screen no matter what button combo I press. I can only get edl and I'd rather not flash the eu msm again.
Click to expand...
Click to collapse
ive gotten the same error too, im on 11.2.10.10, but cant upgrade to OOS12/13 without the touchscreen breaking/dual sim bug, i forgot the link to the 9 pro india msm to flash it with, but ive tried flashing one that was 9 pro and kept getting "device not match image", no clue why
I just read somewhere that downgrading to 11.2.2.2 may work but only place I can find that firmware is on some Chinese site. I can flash the eu pro version all day long. but now I tried flashing an India mod firmware with no success and reflasjed eu again but phone is stuck at 0% power and all I get is a bootloop
First, I apologize if these answers are already posted elsewhere, in which case please point me in the right direction.
So I use to be able to root my phones with my eyes closed (back when HSPA was the fastest and I needed to overclock my single core processor to 1.2GHz because my phone didn't have 8 cores), but its been 2 years since I've rooted my one plus 9 and I was pretty rusty then so I'm pretty much lost now. I know that over the years there's been changes to the way things must be done depending on the phone, version, etc. I'm trying to update my phone to either android 12 or 13, and unless I'm mistaken, I can't just flash an android 13 custom rom over the rooted OOS rom that is stock with the exception of having Magisk of course. If that's incorrect, that would be very convenient. But if I am, what steps do I need to do to get this done? I have SDK platform-tools ready, but I no longer have backups of the stock boot.img, or anything for that matter. My mother is a hypochondriac of sorts, so I can't have my phone not work for more than a day, or I'll have the police at my door doing a wellness check. Thanks in advance for any help!
Model: LE2117
SW ver. 11.2.3.3LE54CB
Use MSM Tool to reset your phone to initial factory firmware, which is OOS11. You can then update through OTA all the way to the latest.
And next time you root your phone, DON'T flash the patched boot.img. Instead, temporarily boot by the command fastboot boot <your_patched_boot.img> and then from Magisk app, use Direct Install. That way, Magisk will backup your original boot.img which you can restore later if there is a new OTA.
Do you have a token? Get one if you dont.
unlock token - OnePlus (United States)
www.oneplus.com
Takes a couple days to a month to get it. Check back at that page, they will not notify you when its ready.
Once you get it, MSM to global base A11\OOS11 to debrand, and also allow for easier updates since Tmobile is stingy about pushing out A13 recently.
Get to latest OTA update, fastboot flash cust-unlock <unlock_token.bin> to unlock BL, install Magisk anyway you want.