Soft bricked my phone installing the android 10 open beta.
All good, recovered it (i have lots of experience rooting and modifying phones, but NOT with the a/b structure)
Now i have no service no my phone, but the sims are detected, as during the set up, it shows both of my numbers.
Both the imei numbers are there if i dial *#06#
Unlock was a while back using simple fastboot flashing unlock, and my previous set up was stock, with arter97 kernel & magisk.
I fastboot flashed 2 roms i could find (21BA and 21AA and neither made a difference) - so i'm factory reset too. I'm on Three UK if anyone knows how to get this sorted!
I had the same problem yesterday. Android flashed q, did not work, then returned to 9.5.11, but there was no service.
I reset my device using msm tool. Visit the Msm tool topic, my problem is solved.
manor7777 said:
I fastboot flashed 2 roms i could find (21BA and 21AA and neither made a difference) - so i'm factory reset too. I'm on Three UK if anyone knows how to get this sorted!
Click to expand...
Click to collapse
You've answered it yourself. You flashed the wrong rom with 21AA. 21BA is for Europe.
As mentioned above, the MSM tool will sort it.
hallo dare said:
You've answered it yourself. You flashed the wrong rom with 21AA. 21BA is for Europe.
As mentioned above, the MSM tool will sort it.
Click to expand...
Click to collapse
Actually, that wasn't the issue. I've had both on my device before with full functionality. The problem was, when i went back to stock it switched to slot B. was as simple as switching back to A. Now i've updated to open beta 1, i'm back on slot b and all working
Is Reliance JIO working on Oneplus 8T?
I have unlocked Tmobile OP 8T ( KB 2007) and it's not working for me.
5ud0 said:
Is Reliance JIO working on Oneplus 8T?
I have unlocked Tmobile OP 8T ( KB 2007) and it's not working for me.
Click to expand...
Click to collapse
It is working perfectly fine, although my device model number is KB2001.
You may have to flash the Indian firmware to make it work.
TheMystic said:
It is working perfectly fine, although my device model number is KB2001.
You may have to flash the Indian firmware to make it work.
Click to expand...
Click to collapse
Unfortunately nothing is working for me
Tried all 3 versions of oxygen os. It's working in my op 6t but not in op8t
5ud0 said:
Unfortunately nothing is working for me
Tried all 3 versions of oxygen os. It's working in my op 6t but not in op8t
Click to expand...
Click to collapse
I had the same problem on a Samsung S8+ (purchased abroad).
The solution was to flash the local firmware and everything worked after that.
You are probably flashing the OS. I'm saying you have to flash the FIRMWARE (which is different from the OS).
Someone who has a custom recovery installed may be able to help you.
TheMystic said:
I had the same problem on a Samsung S8+ (purchased abroad).
The solution was to flash the local firmware and everything worked after that.
You are probably flashing the OS. I'm saying you have to flash the FIRMWARE (which is different from the OS).
Someone who has a custom recovery installed may be able to help you.
Click to expand...
Click to collapse
Cool, Thanks for letting me know. I will look it up. If you have any threads that can help me, I would really appreciate that
Update: Just a clarification mate, by flashing firmware, do you mean flashing the global rom from fastboot? If so, that is how I flashed global rom on my T-Mobile. All the articles when I search for flashing firmware is pointing to the flashing from fastboot which is what I did.
5ud0 said:
Cool, Thanks for letting me know. I will look it up. If you have any threads that can help me, I would really appreciate that
Update: Just a clarification mate, by flashing firmware, do you mean flashing the global rom from fastboot? If so, that is how I flashed global rom on my T-Mobile. All the articles when I search for flashing firmware is pointing to the flashing from fastboot which is what I did.
Click to expand...
Click to collapse
8T is a very new device, and I don't think the required files are available yet. As far as I know, even TWRP isn't available yet for this device.
Once a custom recovery is available, someone who has the KB2001 model may be able to extract the required files and pack them in a flashable zip. It is these files that are primarily what distinguishes one model number from another.
This is NOT the OS/ ROM. The Firmware contains the modem and other driver files to support the telecom bands/ spectrum (among others) used in a specific region. I'm afraid you have to wait for now, as there is unlikely to be an immediate solution now.
You can try at the service centre though. They may be able to help here (although very unlikely).
TO CLARIFY THIS IS A ROOT ONLY FIXAfter gaining root install given module.
Data is now retained. Even after reboot(s).
No empty slot or waiting.
Issue is TMO variant is showing muli sim.
So props were added to make it like a conversion to single sim....
Yes module works for both models.
Install & enjoy
Extract and pull it apart if interested .
Please give amazing thanks
to @twinnfamous for building module & bringing this data/sim nightmare to an end
Can confirm this worked and solved my stupid "no sim" error after upgrading from 11.10.10 global to c44.
Worked perfectly on TMobile converted to global. With the issue of having no signal after 12 update.
Thank you @twinnfamous for making the module and thank you @Libra420T for sharing !! You both saved my A$$!
Is this the only way to get data working? I have a NA global variant that doesn't support dual SIM and seems to have the same issue. Honestly really liking ColorOS besides this... I usually don't root but if I don't have a choice, I guess that's what I'll do.
Thanks much. This worked perfectly after I figured out how to root C.62!
Libra420T said:
TO CLARIFY THIS IS A ROOT ONLY FIXAfter gaining root install given module.
Data is now retained. Even after reboot(s).
No empty slot or waiting.
Issue is TMO variant is showing muli sim.
So props were added to make it like a conversion to single sim....
Yes module works for both models.
Install & enjoy
Extract and pull it apart if interested .
Please give amazing thanks
to @twinnfamous for building module & bringing this data/sim nightmare to an end
Click to expand...
Click to collapse
thanks so much! I reflashed with msm multiple times and then kept upgrading to 12 since I thought I was doing something wrong, this fixed the SIM issue. now working great!
Hey dear my device OnePlus 9 T-Mobile
After rollback to stock T-Mobile
By unbrick msm tools
Stock T-Mobile not like first time
Sim card always disconnected and reconnected . Any solution?
This is support a Indian firmware?
badlucky said:
Hey dear my device OnePlus 9 T-Mobile
After rollback to stock T-Mobile
By unbrick msm tools
Stock T-Mobile not like first time
Sim card always disconnected and reconnected . Any solution?
Click to expand...
Click to collapse
You need to make sure that the msm tool manager is for your version that shipped with your phone, as well as the right android version number. Only then will you be able to generate a modem from your service provider.
If that doesn't work, I would try to msm to different versions of your T-Mobile vairent (LE2117). You should have rolled back to like 11.2.2 unless you have the Indian version. Idk what the first version was. my guess is that you used an msm tool that didn't include the Indian T-Mobile vairents.
Dear . I'm use msm to flash global firmware then im rollback to T-Mobile
This file sim card fix only on global firmware? Or for both (glo & India ) .
? Any new T-Mobile msm tools ?
Libra420T said:
TO CLARIFY THIS IS A ROOT ONLY FIXAfter gaining root install given module.
Data is now retained. Even after reboot(s).
No empty slot or waiting.
Issue is TMO variant is showing muli sim.
So props were added to make it like a conversion to single sim....
Yes module works for both models.
Install & enjoy
Extract and pull it apart if interested .
Please give amazing thanks
to @twinnfamous for building module & bringing this data/sim nightmare to an end
Click to expand...
Click to collapse
Hey dear . Update to a12 last version c63 with ota update or local update?
Phoenix47 said:
Will it work on coloros 13 open beta ?
Click to expand...
Click to collapse
Yes it does. Beware that you may lose VoLTE, 5G, and WiFi calling though.
Phoenix47 said:
I don't even use any of them.
Click to expand...
Click to collapse
What carrier do you have? I had to go back to OOS because no US carrier works right without VoLTE now. Couldn’t make or receive calls unless my phone was on 3G (T-Mobile). Went back to OOS and then switched to my 12 Pro Max. Waiting for the Pixel 7 Pro announcement to decide if I’m going to that or getting a 14 Pro Max and saying goodbye to Android (again - my OnePlus 9 is the first Android I had since 2017 when I switched). All I know is I’m over this device.
dual sim will work?
sim issues solved from Android 13?
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
Hello.
So basically, I have a T-Mobile OnePlus 9 (LE2117). I went through that whole ordeal of having that global conversion script brick then phone and then bring it back to life using the India 9 Pro MSM. I tried a bunch of stuff, eventually gave up and contacted OnePlus support to get to a working T-Mobile MSM tool.
When the T-Mobile MSM they used did its thing, it went back to the T-Mobile software, however there are two issues with it:
1. The pink T-Mobile splash screen doesn't show up on boot but instead a black one that just says "android" shows up (see attached image)
2. The software updates button is grayed out and cannot be hit
The original T-Mobile MSM you can find online also works now, but it still results in this same issue.
I ended up using the global conversion MSM on OOS 11 and a custom rom for a few months each, both of which worked perfectly, but this is still an issue that is here after using the T-Mobile MSM again.
Is there any good way of fixing this issue? I do have quite a few of the important partitions backed up if those are necessary.
Thanks!
BGW#10 said:
Hello.
So basically, I have a T-Mobile OnePlus 9 (LE2117). I went through that whole ordeal of having that global conversion script brick then phone and then bring it back to life using the India 9 Pro MSM. I tried a bunch of stuff, eventually gave up and contacted OnePlus support to get to a working T-Mobile MSM tool.
When the T-Mobile MSM they used did its thing, it went back to the T-Mobile software, however there are two issues with it:
1. The pink T-Mobile splash screen doesn't show up on boot but instead a black one that just says "android" shows up (see attached image)
2. The software updates button is grayed out and cannot be hit
The original T-Mobile MSM you can find online also works now, but it still results in this same issue.
I ended up using the global conversion MSM on OOS 11 and a custom rom for a few months each, both of which worked perfectly, but this is still an issue that is here after using the T-Mobile MSM again.
Is there any good way of fixing this issue? I do have quite a few of the important partitions backed up if those are necessary.
Thanks!
Click to expand...
Click to collapse
Can u use op9 to global conversion msm with any problem
rizzmughal said:
Can u use op9 to global conversion msm with any problem
Click to expand...
Click to collapse
If you are talking about the T-Mobile to Global conversion MSM, yes.
BGW#10 said:
If you are talking about the T-Mobile to Global conversion MSM, yes.
Click to expand...
Click to collapse
Did u update to oos12 were there anyproblems u face in that
rizzmughal said:
Did u update to oos12 were there anyproblems u face in that
Click to expand...
Click to collapse
The dual sim/no service bug. I am aware of the root fix, but I was looking to get the T-Mobile software working normally again.
BGW#10 said:
The dual sim/no service bug. I am aware of the root fix, but I was looking to get the T-Mobile software working normally again.
Click to expand...
Click to collapse
What is the target id for ur device is it india or tmo
rizzmughal said:
What is the target id for ur device is it india or tmo
Click to expand...
Click to collapse
I would say that it is tmo because the T-Mobile msm tools works no problem.