Can anyone tell me if there is newer software for this phone on AT&T?
Currently:
Model LM-G900UM
SW VERSION G900UM10e
Security June 1, 2020
I'm reading there is a version G out, but I'm not getting an update. I even tried a new SIM.
I have the Canadian version, same model and no we haven't had a software update here either
From my knowledge the only ones that have gotten an update are the international unlocked versions which are running the Snapdragon 845
At&t has had two security updates and they're not getting to me. No one at at&t seems to know what to do.
So, this saga has finally ended. My firmware was G900UM10e. VPN bug, and phone would not take OTA. It kept saying I had the latest firmware. To their credit, AT&T support DID try everything. The phone wouldn't even take a push from their servers. New SIM card, factory reset, nada.
So, they sent a warranty replacement with G900UM10n loaded. VPN works perfect. I NEED it for work. And, today I managed to get G900UM10o over the air.
Either the IMEI of my old phone was MAJORLY hard bricked on their update server, or there was a bug in 10e blocking OTA.
Anyhoo, just wanted to share.
mrsubway said:
So, this saga has finally ended. My firmware was G900UM10e. VPN bug, and phone would not take OTA. It kept saying I had the latest firmware. To their credit, AT&T support DID try everything. The phone wouldn't even take a push from their servers. New SIM card, factory reset, nada.
So, they sent a warranty replacement with G900UM10n loaded. VPN works perfect. I NEED it for work. And, today I managed to get G900UM10o over the air.
Either the IMEI of my old phone was MAJORLY hard bricked on their update server, or there was a bug in 10e blocking OTA.
Anyhoo, just wanted to share.
Click to expand...
Click to collapse
I haven't tried the VPN, but I would like to update to Android 11, and I am still stuck with the June 1, 2020 security patch on android 10 with the software version of G900UM10e and my model number is LM-G900UM. I got mine from the USA but am currently living in South Africa, so is there any way that I can fix this issue?
Only if you have an AT&T Sim card. You can't do an OTA update unless it's on the AT&T network.
e is the variant I got stuck on. Since I got my warranty replacement, I've gotten numerous updates, including Android 11.
mrsubway said:
Only if you have an AT&T Sim card. You can't do an OTA update unless it's on the AT&T network.
e is the variant I got stuck on. Since I got my warranty replacement, I've gotten numerous updates, including Android 11.
Click to expand...
Click to collapse
So basically, I can't ever receive updates unless I get an AT&T SIM card and are on their wireless network?
scorpawe said:
So basically, I can't ever receive updates unless I get an AT&T SIM card and are on their wireless network?
Click to expand...
Click to collapse
Correct.
Well, that sucks. Do you know of any way to bypass it, or is there a custom ROM that I can install on this variant of the LG Velvet?
I read some xda/reddit posts on this topic. It seems:
- OOS 11 is the only option to stably run kb2005 (oneplus dual sim) firmware on kb2007 (tmobile single sim). And a dual sim card tray can be used so that the second sim works for volte/vowifi (wifi calling).
- MSM Tool is the way to go to flash kb2005 firmware on a kb2007 phone to rebrand as EU version KB05BA, per this thread https://forum.xda-developers.com/t/...m-unlock-or-bootloader-unlock-needed.4188491/ . From there, kb2005 firmware can be installed with Local Update option.
- If OOS12 is installed and rollback is needed then this thread is very helpful https://forum.xda-developers.com/t/downgrade-oneplus-8t-kb2005-from-12-to-11-stable.4424381/
Does this sound about right? Or am I missing something on this issue? Thanks in advance!
Okay the device has arrived. I plan to stay on OOS11 for a while. 1) No real benefit added by OOS12; 2) VoLTE and Wifi Calling on US carriers like T-Mobile have been reported stabler on OOS11.
Below are the steps I took:
1. Use EU MSM tool; follow the instructions here (run MSM tool .exe file with administrator permission; can use adb tool to get into edl mode easily): https://forum.xda-developers.com/t/...m-unlock-or-bootloader-unlock-needed.4188491/
2. Download Oxygen Updater, from the device list, select oneplus 8T;
3. Enable advance option in Oxygen Updater; now kb2005 firmware should pop up, download it, and then follow the instructions about "local update" using this file.
oops this automatically brings me to OOS12.
Trying the OnePlus official rollback apk now...
Okay rollback apk doesn't work and quits when I click any firmware.
These are the correct steps:
0. Use carrier unlock from the setting to unlock T-Mobile carrier lock first.
1. Use EU MSM tool; follow the instructions here (run MSM tool .exe file with administrator permission; can use adb tool to get into edl mode easily): https://forum.xda-developers.com/t/...m-unlock-or-bootloader-unlock-needed.4188491/ note: after reboot I have dual VoWifi working already on KB05BA firmware.
2. Just use system update if it is showing 11.0.13.13.KB05BA.
This sticks to the EU firmware, as dual VoWifi already works on T-Mobile USA.
Hello, could you confirm that dual sim is working by following the steps above? I just received my T-Mobile 8T yesterday and found out it has only one sim slot.
Yes, it was actually just that simple. SIM unlock. MSM tool. And one system update.
You might have to be careful with the last part tho because the latest system update may bring you to OOS12 and dual SIM will break. You might need to search for Oxygen updater and find a way to update to the latest OOS11 firmware. Oh also Global is the best among all firmware versions.
jllll said:
Yes, it was actually just that simple. SIM unlock. MSM tool. And one system update.
You might have to be careful with the last part tho because the latest system update may bring you to OOS12 and dual SIM will break. You might need to search for Oxygen updater and find a way to update to the latest OOS11 firmware. Oh also Global is the best among all firmware versions.
Click to expand...
Click to collapse
Thank you so much
I followed the steps above but for some reason the Oxygen Updater still update my device to OOS12. I managed to downgrade back to OOS 11. I am still waiting for my dual sim tray from Amazon. Just to confirm, the latest OOS is 11.0.13.13.KB05AA right? Also, on the "About phone" page, the model is still KB2007, is this ok?
JerryRich said:
I followed the steps above but for some reason the Oxygen Updater still update my device to OOS12. I managed to downgrade back to OOS 11. I am still waiting for my dual sim tray from Amazon. Just to confirm, the latest OOS is 11.0.13.13.KB05AA right? Also, on the "About phone" page, the model is still KB2007, is this ok?
Click to expand...
Click to collapse
I am on 11.0.13.13.KB05BA EU firmware. On www.oneplus.com the latest stable firmware is 11.0.13.13.KB05AA for global https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1605596915581
My next update notification is for KB2003_11.C.33 which is OOS12.
About phone shows KB2007 for me as well but I have dual VoWifi on T-Mobile.
Waiting for a genius making dual SIM work again on OOS 12...
jllll said:
I am on 11.0.13.13.KB05BA EU firmware. On www.oneplus.com the latest stable firmware is 11.0.13.13.KB05AA for global https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1605596915581
My next update notification is for KB2003_11.C.33 which is OOS12.
About phone shows KB2007 for me as well but I have dual VoWifi on T-Mobile.
Waiting for a genius making dual SIM work again on OOS 12...
Click to expand...
Click to collapse
Don't know anything about dual sim on KB2007 and OOS12, but heard about dual sim on KB2007 on LOS/AOSP. But proceed with caution, as that guide was for OOS11 based LOS/AOSP.
[GUIDE] Enable Dual SIM (dsds) on your T-Mobile 8T (KB2007) with Lineage/AOSP ROM
NOT FOR OOS, If you do this on TMO OOS you will lose connectivity. So Lineage and all other AOSP based ROMs does not enable dual SIM for kebabt due to the T-Mobile modem having a hissy fit. However, you can flash the US/Global modem, retain all...
forum.xda-developers.com
JerryRich said:
Also, on the "About phone" page, the model is still KB2007, is this ok?
Click to expand...
Click to collapse
Yep.
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Phoenix47 said:
When I do msm on t-mobile variant, I get oos12 ota straight from oos 11.2.2.2 but it is not actually oos12 ota. It have 500mb size and updates phone to 11.2.8.8 version on tmo but can't get any more ota updates after that.
Click to expand...
Click to collapse
What MSM specifically? If it is the TMo one, then you won't get OTAs from 1+, they come from TMo. 11.2.8.8 is the latest from TMo
Phoenix47 said:
And the tmo to global conversion msmtool is not good. You get sim issue after updating to global oos12.
Click to expand...
Click to collapse
What SIM issues?
Phoenix47 said:
I was on TMO oos 11.2.9.9 before and got oos12 ota update with 5gb size. But now I only get ota till 11.2.8.8 on tmobile rom after using tmobile msm 11.2.2.2 available on xda.
.
.
Regarding sim issue, the global oos12 convert my single sim LE2117 to dual sim LE2115 which cause NO SIM bug.
Click to expand...
Click to collapse
Interesting, I never got 12 when I was TMo, only 11.2.8.8. Maybe different areas get different stages? It is weird the TMo ROM is so far behind though...
Did you follow step 9 of the conversion guide?
Really, all of these methods are outdated. The best way to do it is to use Fastboot Enhance.
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
After doing that, you just have to flash the Magisk fix to get back working data (because of the aforementioned dual SIM bug).
Phoenix47 said:
Step 9 is flashing modem.img from tmo rom, which also require unlocking bootloader. Actually the issue can also be fixed by a small magisk module which convert phone back to single sim on oos12. Did you flash the tmo oos11 modem.img on global oos12 ?
.
I am just saying, there is no way to fix that issue on locked bootloader after using the conversion msm.
Click to expand...
Click to collapse
Ah, I am not sure then how you'd fix the issue as I have an unlocked bootloader and root.
And I have not flashed the file yet or the Magisk fix. I have to send the phone off for screen repair, so I haven't popped a SIM in it since converting.
Phoenix47 said:
When I do msm on t-mobile variant, I get oos12 ota straight from oos 11.2.2.2 but it is not actually oos12 ota. It have 500mb size and updates phone to 11.2.8.8 version on tmo but can't get any more ota updates after that.
Click to expand...
Click to collapse
I'm also facing this issue
It's been over a week and still no updates after 11.2.8.8
My device was previously on OOS12 C.19 before i bricked it and uses the MSM tool
centifanto said:
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Click to expand...
Click to collapse
Did you run into SIM card issues after updating to C.48 using this method?
I'm just wondering if i can use the TMO-GLO MSM tool to get 11.2.2 them use the local update to 11.2.10.10 then go to C.48 to hopefully retain Cell service/SIM Card, any help on the matter would be appreciated!
Phoenix47 said:
It is weird that global rom shows dual sim on oos12. I mean there is single sim global model also.
.
And that magisk fix don't work on custom roms.
Click to expand...
Click to collapse
The T-Mobile model is actually dual SIM but with a single SIM tray from my understanding, hence the software bug.
Phoenix47 said:
Step 9 is flashing modem.img from tmo rom, which also require unlocking bootloader. Actually the issue can also be fixed by a small magisk module which convert phone back to single sim on oos12. Did you flash the tmo oos11 modem.img on global oos12 ?
.
I am just saying, there is no way to fix that issue on locked bootloader after using the conversion msm.
Click to expand...
Click to collapse
Flashing modem is only required on the 9 Pro because it has an mmWave modem.
Phoenix47 said:
So you are saying that adding dual sim tray will fix the NO SIM CARDS issue ?
Click to expand...
Click to collapse
No because it doesn't work right either.
EDIT: Looks like I misspoke anyway because it's only the LE2127.
ENABLE DUAL SIM ON TMO 9 PRO ONLY!!!
Frist off I'm not Responsible for anything that happens to your phone!!! THIS HAS BEEN TESTED AND WORKING 100% ON TMO 9PRO LE2127!!ALSO MODEM RETENTION. (THIS IT NOT FOR THE UNLOCKED 9PRO LE2125) DO THIS AT YOU OWN RISK!! THIS METHOD IS...
forum.xda-developers.com
This worked great on my le2117 That is SIM and Bootloader unlocked. I didn’t have to flash the modem at all. Interestingly, it didn’t change model to le2115 until did the local update to c.48. Then I was able to OTA to c.63.
the only thing I see is that Netflix does not work or allow me to update…anybody know the fix and are there any other apps that I should expect that behavior?
Great info on this thread…I think I’m going to try to load Nameless soon.
Does anyone have the TMO 11.2.8.8 or anything around there? I've heard of 11.2.9.9. I was on EU 11.2.10.10. it was mostly ok but I was having a few communication issues*. I want to compare to a stock TMO later-11 version. I'm currently on 11.2.3.3le5acb
I tried searching the forum but it doesn't allow searching for "11.2.8.8" type strings. Or short strings.
*Wifi stopped connecting to some of my APs. Until I toggled Mac randomization, then it was fine. It's no problem in my 7TP5G.
5G would drop off to LTE, no problem... But then, LTE would drop off into no data. SMS would sometimes get stuck until reboot. Visual voicemail worked when it wanted to. None of these were consistently happening but all more than once.
Overall it wasn't too bad really but I want to try a late-11 and see how it goes.
Thanks
EtherealRemnant said:
Really, all of these methods are outdated. The best way to do it is to use Fastboot Enhance.
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
After doing that, you just have to flash the Magisk fix to get back working data (because of the aforementioned dual SIM bug).
Click to expand...
Click to collapse
i can agree with him. i was one of the first people to try this method on the thread he created. works wonderfully. hence why his thread was stickied to the top of xda oneplus 9 page.
I did look through bunch of threads but cant seem to find an answer . . Is there a way to enable dual sim on the LE2115 and if someone has tried successfully (with or without any known issues) ?
If someone can point me to the right steps to follow ?
TIA
centifanto said:
2.10.10. I quickly downloaded that, and lo and behold the upda
Click to expand...
Click to collapse
bguzz said:
This worked great on my le2117 That is SIM and Bootloader unlocked. I didn’t have to flash the modem at all. Interestingly, it didn’t change model to le2115 until did the local update to c.48. Then I was able to OTA to c.63.
the only thing I see is that Netflix does not work or allow me to update…anybody know the fix and are there any other apps that I should expect that behavior?
Great info on this thread…I think I’m going to try to load Nameless soon.
Click to expand...
Click to collapse
how you did the local update? did you have to unlock your bootloader?
centifanto said:
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Click to expand...
Click to collapse
why when i try to install 11.2.10.10 my phone reset and keep saying is LE2117, it won't let me install LE2115_11.F.16. Pls help
After all procedure I'm on latest global A13 with December security patch but I have very strange issue, after airplane mode or restart my sim stop working and I have to eject and re-insert the sim for network service any solution