Database Info

[Q] HELP! I need to flash a modem if anyone can help?

Ok well, I got my replacement Moto G and everything was working ok on 4.3. Then I decided to manually flash Kitkat through adb after unlocking the boot-loader, and now I'm getting no service at all. lol. Um, yea So I have flashed the same firmware on the original Moto G that I had and had no problems flashing it. I don't know why I'm not getting any service on this one? I forgot to mention that I twent back to 4.3 through adb seeing that might of helped and did the kitkat upgrade after, and nada!
Baseband Version: MSM8626BP_1032.340.63.00b
System Version: 172.44.4.falcon_umts.Retail.en.US
Build number: KXB20.9-1.8-1.4
Under status I'm getting Unknown Network, Mobile Network type Unknown, Service State: Radio off, Mobile network state, disconnected, Bluetooth address unavailable. That is what is missing under those sections. I'm assuming it has something to do with the radio/modem. If anyone has one they can let me flash for the Retail US version, I would highly appreciated. :good: Thank you for your help!

maybe a solution
asheehanjr said:
Ok well, I got my replacement Moto G and everything was working ok on 4.3. Then I decided to manually flash Kitkat through adb after unlocking the boot-loader, and now I'm getting no service at all. lol. Um, yea So I have flashed the same firmware on the original Moto G that I had and had no problems flashing it. I don't know why I'm not getting any service on this one? I forgot to mention that I twent back to 4.3 through adb seeing that might of helped and did the kitkat upgrade after, and nada!
Baseband Version: MSM8626BP_1032.340.63.00b
System Version: 172.44.4.falcon_umts.Retail.en.US
Build number: KXB20.9-1.8-1.4
Under status I'm getting Unknown Network, Mobile Network type Unknown, Service State: Radio off, Mobile network state, disconnected, Bluetooth address unavailable. That is what is missing under those sections. I'm assuming it has something to do with the radio/modem. If anyone has one they can let me flash for the Retail US version, I would highly appreciated. :good: Thank you for your help!
Click to expand...
Click to collapse
try this:
1. open dialer
2. type this: *#*#4636#*#*
3. open Phone information
4. scroll down and tap "Turn on radio"
if nothing happened, try reboot... is it working?

2hipso said:
try this:
1. open dialer
2. type this: *#*#4636#*#*
3. open Phone information
4. scroll down and tap "Turn on radio"
then reboot... is it working?
Click to expand...
Click to collapse
I did try it and it didn't work for me but, I re downloaded the Android 4.4.2 Blur_Version.172.44.4.falcon_umts.AWSRetail.en.US and flashed it via adb and, I switched the msfastboot modem 1 and 2 did that before flashing the modem NON-HLOS.bin and have everything working now. Phew. lol. Thanks for your help dude. Will note your method for future use. Thanks again! :good:

i dont know what are you talking about but
asheehanjr said:
I did try it and it didn't work for me but, I re downloaded the Android 4.4.2 Blur_Version.172.44.4.falcon_umts.AWSRetail.en.US and flashed it via adb and, I switched the msfastboot modem 1 and 2 did that before flashing the modem NON-HLOS.bin and have everything working now. Phew. lol. Thanks for your help dude. Will note your method for future use. Thanks again! :good:
Click to expand...
Click to collapse
you're welcome

asheehanjr said:
I did try it and it didn't work for me but, I re downloaded the Android 4.4.2 Blur_Version.172.44.4.falcon_umts.AWSRetail.en.US and flashed it via adb and, I switched the msfastboot modem 1 and 2 did that before flashing the modem NON-HLOS.bin and have everything working now. Phew. lol. Thanks for your help dude. Will note your method for future use. Thanks again! :good:
Click to expand...
Click to collapse
So you reflashed everything and what lines did you use or changed in fastboot?

Need Help. I cant turn on my WIFI !!!!
Hello. I have issue with my WiFi connection in my Moto G. I flashed 2 times 4.4.2 stock roms and nothing. I also downgrade to JB and always cant turn the WiFi button to ON in settings. PLZ HELP ME !!!
---------- Post added at 10:58 AM ---------- Previous post was at 10:46 AM ----------
How you do that. I have identical issue with my Moto G . PLZ HELPPPPPP !!!!!
:crying::crying::crying::crying:

;(
Sharwin said:
Hello. I have issue with my WiFi connection in my Moto G. I flashed 2 times 4.4.2 stock roms and nothing. I also downgrade to JB and always cant turn the WiFi button to ON in settings. PLZ HELP ME !!!
Please. Anybody can help me, which lines I must change. I work on this phone yesterday more than 10 hours and nothing. I need help !!!!!!1 :crying:
Click to expand...
Click to collapse

Read here

Same issue as OP Help.
I am having the same issue as the OP. I tried to install modem 2 before 1 the way OP stated. But I still cant get any service on my phone. I also have the 1034 version of the device suited for T-Mobile. I tried to flash the stock radio as well but Im not getting any service. If someone knows what the issue is please help.
By the way my wifi is working just fine. Its the network I cant connect to. I tried my sim card and it work in another phone.
Thank you for any help.

I'm also having the same problem. I have a US global model XT-1032 Moto G. No matter what the heck I try to do the radio always stays off on the phone. It worked fine prior to the 4.4.2 OTA update.
I've tried flashing just the modem from the 4.4.2 and 4.3 US firmwares for both the XT-1032 and XT-1034 versions and neither of them work, it always shows the network as unknown and the radio being turned off.
I have even tried erasing the modemst2 then modemst1 in that order and then flashing the modem with the non-hlos.bin file hoping that if I did it in reverse to the normal order it would fix the issue.
The sad thing is that since I unlocked the damn bootloader to do this, now I can't get any kind of warranty repair done on it by Motorola.

doctor_evil said:
I'm also having the same problem. I have a US global model XT-1032 Moto G. No matter what the heck I try to do the radio always stays off on the phone. It worked fine prior to the 4.4.2 OTA update.
I've tried flashing just the modem from the 4.4.2 and 4.3 US firmwares for both the XT-1032 and XT-1034 versions and neither of them work, it always shows the network as unknown and the radio being turned off.
I have even tried erasing the modemst2 then modemst1 in that order and then flashing the modem with the non-hlos.bin file hoping that if I did it in reverse to the normal order it would fix the issue.
The sad thing is that since I unlocked the damn bootloader to do this, now I can't get any kind of warranty repair done on it by Motorola.
Click to expand...
Click to collapse
I wanted to report that I fixed my problem with my moto-G, it turned out to be a XT-1034 instead of a XT-1032. I posted a blog post with a link for downloading the file that I used to fix the problem. Basically what I had to do was flash the 4.4.2 modem for a Retail GB model moto-G. This fixed the problem. here is the link http://doctorevil30564.blogspot.com/2014/06/how-to-fix-motorola-moto-g-xt-1034-that.html
UPDATE: the Retail US 4.4.3 factory image from here Blur_Version.210.12.32.falcon_umts.AWSRetail.en.US fixed the radio on my XT-1034 so no need to use the previous method if you are having the same issue, just try flashing that version on your XT-1034

hi Guys ... i am having this same issue ....
I am on Android 4.4.2
Baseband version : MSM8626BP_1032.340.63.00R
System Version: 174.44.9.falcon_utms.TescoSL.en.GB
Build number: KLB20.9-1.10-1.9
In Status I have
Network : unknown
Mobile network type : unknown
service status : out of service
I've tried flashing stock 4.4.2 over adb but nothing happened

doctor_evil said:
I wanted to report that I fixed my problem with my moto-G, it turned out to be a XT-1034 instead of a XT-1032. I posted a blog post with a link for downloading the file that I used to fix the problem. Basically what I had to do was flash the 4.4.2 modem for a Retail GB model moto-G. This fixed the problem. here is the link http://doctorevil30564.blogspot.com/2014/06/how-to-fix-motorola-moto-g-xt-1034-that.html
UPDATE: the Retail US 4.4.3 factory image from here Blur_Version.210.12.32.falcon_umts.AWSRetail.en.US fixed the radio on my XT-1034 so no need to use the previous method if you are having the same issue, just try flashing that version on your XT-1034
Click to expand...
Click to collapse
hi Guys ... i am having this same issue ....
I am on Android 4.4.2
Baseband version : MSM8626BP_1032.340.63.00R
System Version: 174.44.9.falcon_utms.TescoSL.en.GB
Build number: KLB20.9-1.10-1.9
In Status I have
Network : unknown
Mobile network type : unknown
service status : out of service
I've tried flashing stock 4.4.2 over adb but nothing happened

Moto G 2015 XT1548 Radio Firmware - SIM Not Detected

Alright, having flashed CM13 and gotten my phone mostly working again, I'm running into issues with the phone not detecting the SIM card. Most of the information I can find indicates that I need to update the radio firmware, but I can't actually find any that works with my phone! Does anyone have any suggestions?

groverXIII said:
Alright, having flashed CM13 and gotten my phone mostly working again, I'm running into issues with the phone not detecting the SIM card. Most of the information I can find indicates that I need to update the radio firmware, but I can't actually find any that works with my phone! Does anyone have any suggestions?
Click to expand...
Click to collapse
Download the latest factory image for your device, and flash the following files:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse

acejavelin said:
Download the latest factory image for your device, and flash the following files:
Click to expand...
Click to collapse
Any idea which image I should use? Mine is the Virgin Mobile variant and i haven't been able to locate one specific to them. If I use the Sprint version, is that going to cause problems?

groverXIII said:
Any idea which image I should use? Mine is the Virgin Mobile variant and i haven't been able to locate one specific to them. If I use the Sprint version, is that going to cause problems?
Click to expand...
Click to collapse
Should be the same... Virgin Mobile IS Sprint

acejavelin said:
Should be the same... Virgin Mobile IS Sprint
Click to expand...
Click to collapse
Okay, thanks! I'll try this in the morning when I get home from work and see if it works!

acejavelin said:
Should be the same... Virgin Mobile IS Sprint
Click to expand...
Click to collapse
Alright, so I flashed the listed files and got the phone to recognize my SIM card, but now after it boots up and connects, 30 seconds to 2 minutes later it reboots on me. Any ideas?
Edit: I tried the 5.1.1 firmware and that actually seems to have done the trick, for the most part. It shows Sprint as my network, though, and I'm not sure if that's going to cause any issues further down the line.
Edit 2: Actually, after a reboot it's showing the correct network again and everything has been stable.

Sprint version unlocked work T-Mobile WiFi calling?

I have been offered a great deal to buy a Sprint Essential version that has been unlocked. Does anybody have the Sprint unlocked version and verify TMobile WiFi calling works?

mexicandroid said:
I have been a great deal to buy a Sprint Essential version that has been unlocked. Does anybody have the Sprint unlocked version and verify TMobile WiFi calling works?
Click to expand...
Click to collapse
Yes.my essential is a Sprint one, that is unlocked and on t mobile network. WiFi calling works great

jacksummers said:
Yes.my essential is a Sprint one, that is unlocked and on t mobile network. WiFi calling works great
Click to expand...
Click to collapse
A million thanks, it's been hard trying to find a clear option on Google. Most carrier unlocked phone won't work with other carriers WiFi calling due to the firmware. To bad there isn't a Essential phone 2 planned anymore
So those APN's pertain to the WiFi calling? Never new that lol

mexicandroid said:
A million thanks, it's been hard trying to find a clear option on Google. Most carrier unlocked phone won't work with other carriers WiFi calling due to the firmware. To bad there isn't a Essential phone 2 planned anymore
So those APN's pertain to the WiFi calling? Never new that lol
Click to expand...
Click to collapse
No the apn is just the one I use here in Ohio. To enable the feature you need to flash an open market firmware. Go to the essential site and install the P update, it's super easy to sideload. Or if u want Oreo, the July Oreo open market firmware works and has WiFi calling. I got my essential from sprint and it was there soon as I flashed a open market firmware.all that means is it's the non carrier specific firmware that has all features

Is there a version of Android P with open market Firmware?
Hey just out of curiosity do you know if the phone is carrier locked, will flashing the open market Firmware, will it unlock it?

mexicandroid said:
Is there a version of Android P with open market Firmware?
Hey just out of curiosity do you know if the phone is carrier locked, will flashing the open market Firmware, will it unlock it?
Click to expand...
Click to collapse
Yes the one on there is open market.and yes,flashing the open market firmware will carrier unlock it. Not all phones, just with essential.it was a "loose" Carrier lock

The one I'm getting is already carrier unlocked, for $200 in mint condition with the 360 camera is too good too pass up
But good to know

jacksummers said:
Yes the one on there is open market.and yes,flashing the open market firmware will carrier unlock it. Not all phones, just with essential.it was a "loose" Carrier lock
Click to expand...
Click to collapse
https://www.essential.com/developer/current-builds
On the download page there only one download link. Does it detect which version the phone has while installing? I'm going to download the fast boot and try to install it. See how it goes
Update
I installed the Pie Sprint/ Open Market fastboot file but when I try to turn on WiFi calling the UI closed and takes me to lockscreen. I'm going to download the March 2018 fastboot file since it only has an option for Open Market only and then try to update over the air to Pie

jacksummers said:
Yes.my essential is a Sprint one, that is unlocked and on t mobile network. WiFi calling works great
Click to expand...
Click to collapse
I've been playing with the firmware and no luck yet but I have been keeping everything stock and no luck activating TMobile WiFi calling. Are you stock or custom rom?

mexicandroid said:
I've been playing with the firmware and no luck yet but I have been keeping everything stock and no luck activating TMobile WiFi calling. Are you stock or custom rom?
Click to expand...
Click to collapse
Stock,is your bootloader unlocked?

I have the same issue, original Sprint phone, payed it off, switched to TMobile, wifi calling works on Oreo, but won't turn on with Pie, causes a crash

jacksummers said:
Stock,is your bootloader unlocked?
Click to expand...
Click to collapse
Yes, I typed "fastboot flashing unlock" and it promoted me on the phone to unlock it. After I downloaded the Pie fastboot file and typed "flashall.bat" and it took a few minutes to install. Actually my TMobile still card was working and after trying different build it Sim locked it.
After it Sim locked I unlocked the bootloader and tried to flash different builds and letting it boot with the bootloader locked and unlocked and no lock. I just wanted the TMobile WiFi calling lol
The guy I bought the phone from contacted Sprint and sent a unlock request. I hope it unlockes it. I guess it is carrier locked through the bootloader and not the firmware. However that works

PixelatedVision said:
I have the same issue, original Sprint phone, payed it off, switched to TMobile, wifi calling works on Oreo, but won't turn on with Pie, causes a crash
Click to expand...
Click to collapse
Before I tried flashing different builds same thing was happening on Pie when trying to activate WiFi calling but not sure if was an issue with Pie because the firmware is a Sprint Variant or because something because just a bug that hadn't been worked out yet

mexicandroid said:
Before I tried flashing different builds same thing was happening on Pie when trying to activate WiFi calling but not sure if was an issue with Pie because the firmware is a Sprint Variant or because something because just a bug that hadn't been worked out yet
Click to expand...
Click to collapse
It unlocks it if u put in your t Mobile SIM before updating it.that unlocked mine. Then flash the updated firmware. Everything has worked flawlessly on Oreo or p. I have had only Oreo on it for a minute here in there when testing treble roms. When I needed to go back to stock before flashing p. For some reason when I would flash a treble gsi, then go back to p without flashing Oreo in between I would lose WiFi and Bluetooth. Make sure to do a fastboot -w before flashing.

jacksummers said:
It unlocks it if u put in your t Mobile SIM before updating it.that unlocked mine. Then flash the updated firmware. Everything has worked flawlessly on Oreo or p. I have had only Oreo on it for a minute here in there when testing treble roms. When I needed to go back to stock before flashing p. For some reason when I would flash a treble gsi, then go back to p without flashing Oreo in between I would lose WiFi and Bluetooth. Make sure to do a fastboot -w before flashing.
Click to expand...
Click to collapse
When I was playing with it after it had sim locked, went back to nougat just to see if the TMobile WiFi worked but after a minute or two it Sim locked and wouldn't even let open the lockscreen. After that I had gone back to either Oreo out Pie but not sure and it had sim unlocked. But after that I tried flashing different firmwares just to try to see if the TMobile WiFi would work but it Sim locked it again and couldn't get it to unlock it after.
What you mean fastboot -w before flashing?
You think I should flash a Oreo firmware first with my sim in it, let it boot then flash Pie or
Flash Oreo firmware, not let it boot then flash, Pie firmware?
Or should I flash the Oreo firmware that update to Pie through OTA file through ADB?

Finally got my phone unlocked. I'm on Pie but when I try to turn WiFi calling the app closes. Has anybody had any luck with it?

mexicandroid said:
Finally got my phone unlocked. I'm on Pie but when I try to turn WiFi calling the app closes. Has anybody had any luck with it?
Click to expand...
Click to collapse
Good happy to hear. Mine works fine. Same thing as you...was Sprint phone, t mobile sim did nothing and still showed Sprint prl lock. stuck my t mobile sim in, allowed it to update to P beta via adb sideload..when it booted up was t mobile. WiFi calling and all. Been sideloading new updates and customizing for 3 months now.love it!.

jacksummers said:
Good happy to hear. Mine works fine. Same thing as you...was Sprint phone, t mobile sim did nothing and still showed Sprint prl lock. stuck my t mobile sim in, allowed it to update to P beta via adb sideload..when it booted up was t mobile. WiFi calling and all. Been sideloading new updates and customizing for 3 months now.love it!.
Click to expand...
Click to collapse
Your Pie correct with WiFi calling working correctly? I read on Reddit users had luck by installing the open market firmware, setting up the phone and WiFi calling, then installing the OTA to Pie and got it working
I tried so many combinations to unlock but no luck. Luckily the guy I bought it from let have his old Sim card. Left it there for an hour. Changed the APN settings to global then inserted my Sim card and it unlocked

SOLUTION:
Well I finally got TMobile WiFi calling to work. Had to install Oreo open market firmware, setup TMobile WiFi calling and then update to Pie through OTA and now it works on Pie.
I saw a thread on Reddit where some people had luck by just resetting WiFi/Bluetooth/Network settings and then activating WiFi calling.
Also read that doing hard reset will cause you to lose WiFi calling for other companies other than Sprint. Good luck everybody

How To Guide Tips on converting T-Mobile OnePlus 9 to Global

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

How To Guide [TMO To Global] [No Dual-SIM Bug]

Requirements:-
* Unlock Token
* T-Mobile MSM Tool
* OOS 11.2.10.10 and OOS 12 C.48 Global
* Fastboot Enhance
Click to expand...
Click to collapse
Instructions:-
1) MSM back to TMobile OOS11 and unlock bootloader through unlock token
2) Extract the payload file from OOS11.2.10.10 update zip to FastbootEnhance folder
3) Now reboot your phone to fastboot mode and open the FastbootEnhance tool on PC
4) Click on the Reboot To FastbootD option and flash the payload file in fastbootd.
5) After it is done, reboot to recovery and format data
6) Then reboot to system and do local update to OOS 12 C.48
7) No more dual sim problem on global OOS12 and you can also relock bootloader

Phoenix47 said:
Requirements:-
Instructions:-
Note:-
Click to expand...
Click to collapse
Does this msm support the devices which r stuck with target id india

Phoenix47 said:
Requirements:-
Instructions:-
Note:-
Click to expand...
Click to collapse
Can i update it to c.63 will still be there no dual sim bug

rizzmughal said:
Can i update it to c.63 will still be there no dual sim bug
Click to expand...
Click to collapse
If you do incremental ota to c.63 , it will be just like updating to OOS13. You will get a null imei 2. SIM will work without any problem.

Phoenix47 said:
If you do incremental ota to c.63 , it will be just like updating to OOS13. You will get a null imei 2. SIM will work without any problem.
Click to expand...
Click to collapse
When i did before it was same but mobile data wont work

rizzmughal said:
When i did before it was same but mobile data wont work
Click to expand...
Click to collapse
If you used msm conversion package, then thats totally different. Second IMEI is not NULL if you use msm conversion method and there is NO SIM error. I know what you are talking about. If you use the new method, everything works.

Phoenix47 said:
If you used msm conversion package, then thats totally different. Second IMEI is not NULL if you use msm conversion method and there is NO SIM error. I know what you are talking about. If you use the new method, everything works.
Click to expand...
Click to collapse
Then i m going for it

rizzmughal said:
Then i m going for it
Click to expand...
Click to collapse
Phoenix47 said:
If you used msm conversion package, then thats totally different. Second IMEI is not NULL if you use msm conversion method and there is NO SIM error. I know what you are talking about. If you use the new method, everything works.
Click to expand...
Click to collapse
Tried ur way its the same 2nd imei is null and mobile data aint working

rizzmughal said:
Tried ur way its the same 2nd imei is null and mobile data aint working
Click to expand...
Click to collapse
Data is working fine for me on OOS13. Don't think the two methods have same outcome, because you don't have to wait everytime after reboot for loading sim.

Phoenix47 said:
Data is working fine for me on OOS13. Try rebooting phone.
Click to expand...
Click to collapse
I did reboot i m on c.63 data aint working will try updating oos13

Still no data on oos13

I guess the problem here is no matter how we flash we have flash tmo msm India mod and we r stuck with target is of India no matter what we do to convert we get dual sim bug we have to find a way to change target Id back to tmo

rizzmughal said:
I guess the problem here is no matter how we flash we have flash tmo msm India mod and we r stuck with target is of India no matter what we do to convert we get dual sim bug we have to find a way to change target Id back to tmo
Click to expand...
Click to collapse
Data is a different story. Atleast NO SIM bug is fixed.

Phoenix47 said:
Data is a different story. Atleast NO SIM bug is fixed.
Click to expand...
Click to collapse
There was never no sim bug for was always no data bug using oos 13 with magisk module fix

Also on ething i noticed till c.48 in settings about device model number is 2117 but after c.63 or oos13 when dual sim bug appears model number is 2115 may be this has something to do with this dual sim bug

If you have a connection it will be an APN issue.

rizzmughal said:
There was never no sim bug for was always no data bug using oos 13 with magisk module fix
Click to expand...
Click to collapse
If you convert through msm method and update to oos13, you will have weird sim bugs. If you reboot phone, your sim will not load for atleast a minute or two. That problem is gone with new conversion method.

Phoenix47 said:
If you convert through msm method and update to oos13, you will have weird sim bugs. If you reboot phone, your sim will not load for atleast a minute or two. That problem is gone with new conversion method.
Click to expand...
Click to collapse
For me i wanted to say

Mmcx125 said:
If you have a connection it will be an APN issue.
Click to expand...
Click to collapse
No its not apn related problem

rizzmughal said:
Also on ething i noticed till c.48 in settings about device model number is 2117 but after c.63 or oos13 when dual sim bug appears model number is 2115 may be this has something to do with this dual sim bug
Click to expand...
Click to collapse
My phone model was LE2115 even on C.48