is there any way to install this update? every time i try i get an error message that only says "Installation Problem".
eisawi99 said:
is there any way to install this update? every time i try i get an error message that only says "Installation Problem".
Click to expand...
Click to collapse
You can't install updates while rooted. You would need to use MSM tool to go back to stock and then upgrade, afterwards you can root again. T mobile disables the local update option in system update and also only sends out the ota package and not the full system firmware. Just make sure you backup your persist partition before using MSM (recommend using the readback feature F8 of the MSM tool to back it up and then restore persist using fastbootd if it breaks fingerprint).
jeffsga88 said:
You can't install updates while rooted. You would need to use MSM tool to go back to stock and then upgrade, afterwards you can root again. T mobile disables the local update option in system update and also only sends out the ota package and not the full system firmware. Just make sure you backup your persist partition before using MSM (recommend using the readback feature F8 of the MSM tool to back it up and then restore persist using fastbootd if it breaks fingerprint).
Click to expand...
Click to collapse
Is there a guide for doing this using the MSM tool? I'm sure I could figure it out eventually but I'd probably also break something in the process lol.
eisawi99 said:
Is there a guide for doing this using the MSM tool? I'm sure I could figure it out eventually but I'd probably also break something in the process lol.
Click to expand...
Click to collapse
Here's the link to MSM tool:
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
It has a guide in the OP of how to use it. Again, I highly recommend backing up your persist partition using the tool first. Just open tool, press F8, select persist, password is oneplus, connect phone in edl mode, click readback. It will copy your persist to root of your hard drive. Disconnect phone, close and reopen MSM, reconnect phone in edl mode and run MSM tool. Completely restores phone. Update to newest 10.5.17, then if you lost fingerprint, unlock bootloader, then from fastboot type:
Code:
fastboot reboot fastboot
Brings you to a screen with Chinese and English on it, type the following:
Code:
fastboot flash persist persist.img
Replace persist.img with location of your backed up persist. Then you can boot or install TWRP and flash magisk for root.
I had rooted my op8 and wanted the update so did exactly the above, used MSM, lost fingerprint so flashed my backed up persist and everything works great.
jeffsga88 said:
Here's the link to MSM tool:
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
It has a guide in the OP of how to use it. Again, I highly recommend backing up your persist partition using the tool first. Just open tool, press F8, select persist, password is oneplus, connect phone in edl mode, click readback. It will copy your persist to root of your hard drive. Disconnect phone, close and reopen MSM, reconnect phone in edl mode and run MSM tool. Completely restores phone. Update to newest 10.5.17, then if you lost fingerprint, unlock bootloader, then from fastboot type:
Code:
fastboot reboot fastboot
Brings you to a screen with Chinese and English on it, type the following:
Code:
fastboot flash persist persist.img
Replace persist.img with location of your backed up persist. Then you can boot or install TWRP and flash magisk for root.
I had rooted my op8 and wanted the update so did exactly the above, used MSM, lost fingerprint so flashed my backed up persist and everything works great.
Click to expand...
Click to collapse
By completely restores phone, you mean I'll lose all my data? If so it's fine but is there an easy way to back up and restore the data?
eisawi99 said:
By completely restores phone, you mean I'll lose all my data? If so it's fine but is there an easy way to back up and restore the data?
Click to expand...
Click to collapse
Sorry, meant to put that on that reply before. It completely erases your phone. They have the OnePlus switch app, not sure how it is as I've never used it. I use Swift backup from the play store, but it's not completely free (i.e. batch backup and restore isn't free), also know others use titanium backup as well.
Got my update so far pretty unimpressed. Maybe I don't know what I'm doing should it show NR or 5G? Cell mapper will show NR at times, but my phone says 5G. Coverage might have improved some, but not much Decent download speeds, but upload is horrible almost always, sometimes it just errors out,
Christobal34 said:
Got my update so far pretty unimpressed. Maybe I don't know what I'm doing should it show NR or 5G? Cell mapper will show NR at times, but my phone says 5G. Coverage might have improved some, but not much Decent download speeds, but upload is horrible almost always, sometimes it just errors out,
Click to expand...
Click to collapse
Overall, it will not put you on SA (NR only) mode by default. The network will still keep you on NSA (LTE + NR) at most times. Generally, your speeds on NSA will be faster than on SA. The benefit of SA is that you don't need to have good LTE signal to connect to 5G. The issue, current 5G phones can't do calls over NR (VoNR) which means if you force SA mode, you won't be able to make our receive calls. Next year's phones will have VoNR, so SA will matter more then. By the way, cell mapper won't show you much information, the only useful thing to look for on cell mapper regarding 5g right now is the:
Code:
5G State: Connected
If it says that, you're Connected to 5g. If you're Connected to 5g and it gives you no LTE cell information, you should be on SA. There's only 1 app that correctly shows everything for 5g and it's Network Signal Guru, but it requires root and to see 5g info requires the beta version and a license. By the way, phone will show 5g. Another way to tell if on SA, pull down the quick settings and it will say TMO instead of T-Mobile and you can go to the phone dialer and type the following:
Code:
*#*#4636#*#*
Click on phone information and see what it says for data network and voice network, it will say NR if on SA or say LTE if on NSA. You can also force it to NR only with that menu, but again you won't be able to make or receive calls if you do that.
jeffsga88 said:
Overall, it will not put you on SA (NR only) mode by default. The network will still keep you on NSA (LTE + NR) at most times. Generally, your speeds on NSA will be faster than on SA. The benefit of SA is that you don't need to have good LTE signal to connect to 5G. The issue, current 5G phones can't do calls over NR (VoNR) which means if you force SA mode, you won't be able to make our receive calls. Next year's phones will have VoNR, so SA will matter more then. By the way, cell mapper won't show you much information, the only useful thing to look for on cell mapper regarding 5g right now is the:
Code:
5G State: Connected
If it says that, you're Connected to 5g. If you're Connected to 5g and it gives you no LTE cell information, you should be on SA. There's only 1 app that correctly shows everything for 5g and it's Network Signal Guru, but it requires root and to see 5g info requires the beta version and a license. By the way, phone will show 5g. Another way to tell if on SA, pull down the quick settings and it will say TMO instead of T-Mobile and you can go to the phone dialer and type the following:
Code:
*#*#4636#*#*
Click on phone information and see what it says for data network and voice network, it will say NR if on SA or say LTE if on NSA. You can also force it to NR only with that menu, but again you won't be able to make or receive calls if you do that.
Click to expand...
Click to collapse
Thanks for the info. I did force it to NR to test. I personally don't care about speed, but was hoping for better coverage. So do you need the x60 modem to use VoNR?
Christobal34 said:
Thanks for the info. I did force it to NR to test. I personally don't care about speed, but was hoping for better coverage. So do you need the x60 modem to use VoNR?
Click to expand...
Click to collapse
Yeah unfortunately still need to wait for x60 for VoNR (at least that's my understanding is that x50 and x55 don't support VoNR). I wouldn't be surprised if OnePlus patched the modem in the future so even if you force NR that it still detects when you place a call or get a call to drop to LTE for phone call. Samsung appears to have done this with the s20s.
Related
Hello guys,
As I have stated on my Q&A thread I was going to be posting a tutorial in order to bring LTE back for those who had lost it. I will give you some background in order for you to know how I lost it and then I will explain how did I get it back:
How did I lost it:
I had bought a Xiaomi Mi A1, and had given my previous Redmi Note 5 SD636 to my wife, for reasons that don't care at this time haha. So, I get it and I am on carrier Tigo Colombia, which uses band 4 AWS-1 . Everything was working as expected, I had my 4G LTE as a regular user. I had installed the gcam, unlocking bootloader and then relocking it, flawless. Everything was working perfect.
The issue came, when I decided that was time to try one of the AOSP Pie roms. I decided to try Simplix Blue, which called my attention due to not being available on RN5 the device that I used to own. I am pretty sure, that has nothing to do with the rom, for reasons that I will explain later on, but more fault of the SD625, boot.img and modem of the device. So I flashed the rom, as I usually do, following instructions, installing TWRP, changing slot, bla bla bla.. you already know this. So I booted up the rom, and it was on 3g, seemed strange, but on the initial set up I thought myself it was more of configuration on the network side. So, as soon as I finished the set up, I went into settings and selected LTE/WCDMA, did not work. Selected only LTE, did not work. Dialed #*#*4636*#*#, choose LTE network, did not work. So I said, this is more of a ROM problem then. Installed Arrow OS, same issue. Started getting strange, so I said, maybe it is a stock rom problem on my device, so I downloaded Stock ROM and flashed. Surprisingly, did not work either.
So I started to look around for solutions, wrote on telegram group and got ignored, as usually happens on that group, and I posted a Q&A thread here, which you can find here:
https://forum.xda-developers.com/mi-a1/help/lost-lte-pie-t3852725
Got no response at first, and then I saw some similar threads with same issue but no resolution. So I started looking for myself. Lasted 2 days looking for a solution as I was completely sure it was not a Hardware issue as I had it before. So, I will explain how I get it back after combining a tutorial with some personal knowledge.
I need to give credits to: @kirtikhurana, he does not even know I used his tutorial for Lenovo P2 haha, but it is worth it thanking him as his thread helped me a lot.
What we need:
QPST
QXDM (You can find this two programs on this thread, 3rd post https://forum.xda-developers.com/lenovo-p2/how-to/enabled-4g-ca-p2-t3707584) Once again, thanks to the creator of the thread for this.
Minimal ADB and Fastboot
LTE Band Calulator app(Which you can find on play store)
Network signal guru app (Which you can find on play store too)
Stock rom (Then you can change it and flash whatever rom you want)
First thing, is have the stock rom rooted, with magisk or whatever method you choose to root it. We will connect the phone to our PC and turn on the USB debugging. For the ADB and fastboot, let's make sure we open the CMD with administrator rights.
I will assume you had already installed QPST and QXDM. We will open a CMD where we have ADB and Fastboot and type:
Code:
adb shell
and then:
Code:
su
We will grant adb shell superuser rights on our phone. As soon as superuser rights are granted, we need to enter on DIAG mode, for that, we will type on the CMD:
Code:
setprop sys.usb.config rndis,diag,adb
On the original thread, it is stated that you can also dial *#*#717717#*#* to enter directly in diagnostic mode (Use this option if QPST does not detect your phone on following steps and reboot).
Now, we will go to QPST>bin folder and open QPST Config, with administrator rights. Check whether your phone is connected or not on diagnostic mode. I will clarify something here:
On the second tab of the QPST Config, you will see an option to add ports, by default, you can select COM1, which is usually not the port where we connect the USB. If that happens and does not detect your device, go to device administrator in the control panel, and make sure your android phone is detected as Diagnostic device, you can check that on USB and ports, where you will also find COM1 as another device. As soon as you make sure drivers and everything is ok, but still does not detect the phone, do the step previously mentioned of: *#*#717717#*#* and reboot.
Now, assuming that your phone is showing there, you will now go to QXDM>bin and open on the tools bar, options and click on communications: You will see your device and the type of model of the processor, in this case, should be MSM8986 or similar. Check below and you will see an option called target port, check on drop down list and choose the com port where you have your device. Now you can close that window.
Now, we will go to view and pick NV Browser, then look for the filter LTE. Then we will select the first option (if this and the other option if grayed out means it has not taken the connection of your phone).
On that first option, you will see two fields below. We will choose the first one and click on read. As soon as we do that, it will autopopulate a number, that number are the bands that you have enabled.
Let's go now to our phone and open LTE band calculator, and let's pick up the bands we need to have (if you write a random number on the app, it will show you which bands will be selected with that number).
Having that number, we will, in QXDM, double click on the input field and write the number that the app has given us and then click on write. As soon as we do that, we need to reboot the phone.
Now, when the phone is already rebooted, we will open network signal guru, provide corresponding permissions and now, click on the three dots at the top right corner and click on lock bands, select LTE. Now, you will see that the band that you were missing, for you to get LTE is there! So what you need to do is select it and click accept. Your phone will freeze for a bit and then reboot itself.
As soon as the phone is rebooted, you will see that you have your LTE back!!
This was the way I was able to get it.
I said it was not a rom, because if you flash stock rom again, with miFlash, you may loose LTE again and need to repeat the process as it happened to me. However, if you are on stock and decide to flash another rom, oreo or pie, you will not lose it.
Hopefully is clear enough for you guys who are facing this issue.
Regards
I lost also band 20 after flashing LOS and after that latest stock
So if i install LOS 15.1 after this method, band 20 will stay unlocked?
Thanks
trance89 said:
I lost also band 20 after flashing LOS and after that latest stock
So if i install LOS 15.1 after this method, band 20 will stay unlocked?
Thanks
Click to expand...
Click to collapse
Yes sir it will! You can do it with no issues whatsoever.
And if i root my system with patched boot.img + magisk method and after this mod i just revert back the untouched boot.img then can i relock bootloader?
ota updates or factory reset won't destroy it?
Thank you
trance89 said:
And if i root my system with patched boot.img + magisk method and after this mod i just revert back the untouched boot.img then can i relock bootloader?
ota updates or factory reset won't destroy it?
Thank you
Click to expand...
Click to collapse
You can do all your stuff. Only thing is if you flash again via MiFlash stock rom, then it may break and you may need to redo the process. But besides that, you can root, unroot, install custom, everything you want to do and you will not loose your band.
Please help! I can't seem to get the device into diagnostic mode or the damn windows drivers don't work. I've installed minimal ADB and drivers from xiaomi. as soon as I enter setprop sys.usb.config rndis,diag,adb no vibrate or anything on my device and in my windows device manager the Android device changes to an ADB interface and a Android device with a yellow exclamation mark. Dialing *#*#717717#*#* doesn't do a thing. I'm on LOS 15.1. Of course no com1 ports to connect to Any ideas?
saski4711 said:
Please help! I can't seem to get the device into diagnostic mode or the damn windows drivers don't work. I've installed minimal ADB and drivers from xiaomi. as soon as I enter setprop sys.usb.config rndis,diag,adb no vibrate or anything on my device and in my windows device manager the Android device changes to an ADB interface and a Android device with a yellow exclamation mark. Dialing *#*#717717#*#* doesn't do a thing. I'm on LOS 15.1. Of course no com1 ports to connect to Any ideas?
Click to expand...
Click to collapse
use google usb driver, it works with all devices: https://developer.android.com/studio/run/win-usb
Jemec26 thanks for the step by step instructions, i got back my lost band
saski4711 said:
Please help! I can't seem to get the device into diagnostic mode or the damn windows drivers don't work. I've installed minimal ADB and drivers from xiaomi. as soon as I enter setprop sys.usb.config rndis,diag,adb no vibrate or anything on my device and in my windows device manager the Android device changes to an ADB interface and a Android device with a yellow exclamation mark. Dialing *#*#717717#*#* doesn't do a thing. I'm on LOS 15.1. Of course no com1 ports to connect to Any ideas?
Click to expand...
Click to collapse
Go with stock rom first. It is not mandatory, but on other roms it may not work.
trance89 said:
use google usb driver, it works with all devices: https://developer.android.com/studio/run/win-usb
Jemec26 thanks for the step by step instructions, i got back my lost band
Click to expand...
Click to collapse
Glad it helped you!
saski4711 said:
Please help! I can't seem to get the device into diagnostic mode or the damn windows drivers don't work. I've installed minimal ADB and drivers from xiaomi. as soon as I enter setprop sys.usb.config rndis,diag,adb no vibrate or anything on my device and in my windows device manager the Android device changes to an ADB interface and a Android device with a yellow exclamation mark. Dialing *#*#717717#*#* doesn't do a thing. I'm on LOS 15.1. Of course no com1 ports to connect to Any ideas?
Click to expand...
Click to collapse
to make use of qualcomm diagnostic mode you must use qualcomm driver, take a look here https://forum.xda-developers.com/mi-a1/how-to/tool-low-level-backup-restore-unbrick-t3790307 in faqs section.
and here an explanation https://forum.hovatek.com/thread-22399.html
Main branch of los and aosp has network issue it needs to be fixed from scratch.
Ok finally I've managed to work through this and it now shows that band 20 is finally back enabled! However there is still no LTE band 20 reception (only band 3 in the city) and yes LTE band 20 signal strength is good when checking with other devices.
Anyway thanks so much for this tutorial but I guess my MiA1 is defective or bricked beyond repair. ;(
saski4711 said:
Ok finally I've managed to work through this and it now shows that band 20 is finally back enabled! However there is still no LTE band 20 reception (only band 3 in the city) and yes LTE band 20 signal strength is good when checking with other devices.
Anyway thanks so much for this tutorial but I guess my MiA1 is defective or bricked beyond repair. ;(
Click to expand...
Click to collapse
Weird. Please upload a pic when you can of the lock bands on the network signal guru app. Also, check with the *#*#4636#*#* the network mode that you are currently running. If your band 20 is already enabled, you should get it. Have you tried different sim?
Jemec26 said:
Weird. Please upload a pic when you can of the lock bands on the network signal guru app. Also, check with the *#*#4636#*#* the network mode that you are currently running. If your band 20 is already enabled, you should get it. Have you tried different sim?
Click to expand...
Click to collapse
Can't upload a screenshot since I'm at work now. LTE discovery shows only Band 3 LTE in the city and no LTE at all only 2G/3G in rural areas (where LTE Band 20 is availble!). Already switched SIMs they work fine (Telefonica Germany).
Signal Guru shows the following locked LTE bands:
B1:2100
B3:1800+
B5:850
B7:2600
B8:900 GSM
B20: 800DD (this one is new since I've unlocked it!)
B34: TDD 2000
B38: TDD 2600
B39: TDD 1900+
B40 TDD 2300
#*#*4636#*#* Shows Radio Band Automatic. Will Check all my steps again. could it be that I need to disable some bands in order to get band 20 working? Got my hand on a working MiA1 and it shows less LTE bands than the faulty one.
saski4711 said:
Can't upload a screenshot since I'm at work now. LTE discovery shows only Band 3 LTE in the city and no LTE at all only 2G/3G in rural areas (where LTE Band 20 is availble!). Already switched SIMs they work fine (Telefonica Germany).
Signal Guru shows the following locked LTE bands:
B1:2100
B3:1800+
B5:850
B7:2600
B8:900 GSM
B20: 800DD (this one is new since I've unlocked it!)
B34: TDD 2000
B38: TDD 2600
B39: TDD 1900+
B40 TDD 2300
#*#*4636#*#* Shows Radio Band Automatic. Will Check all my steps again. could it be that I need to disable some bands in order to get band 20 working? Got my hand on a working MiA1 and it shows less LTE bands than the faulty one.
Click to expand...
Click to collapse
Hmm I did not have to disable other bands but you can try and let us know, it won't damage anything and you can always make a backup. Try disabling bands that you know are not in use.
Tried everything disabled bands - nothing helped. Last Idea was to use the low level backup tool https://forum.xda-developers.com/mi-a1/how-to/tool-low-level-backup-restore-unbrick-t3790307 to backup all partitions from a functioning device with LOS installed and restore it to the one with LTE issues. Now the IMEI is gone. Reflashed August 2017 ROM with miflash to get the damn thing into diagnostic mode again (doesn't that work with LOS?) restored my IMEI, triggered OTA and got a boot loop. I'm afraid I've bricked my device beyond repair
update: I cannot mount my system_a partition in TWRP anymore. flashing stock fails with:
target reported max download size of 536870912 bytes
sending sparse 'system_a' (516697 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 4.295s
"Flash system_a error"
Any ideas? system_a cannot be 516697 KB in size no way!
saski4711 said:
Tried everything disabled bands - nothing helped. Last Idea was to use the low level backup tool https://forum.xda-developers.com/mi-a1/how-to/tool-low-level-backup-restore-unbrick-t3790307 to backup all partitions from a functioning device with LOS installed and restore it to the one with LTE issues. Now the IMEI is gone. Reflashed August 2017 ROM with miflash to get the damn thing into diagnostic mode again (doesn't that work with LOS?) restored my IMEI, triggered OTA and got a boot loop. I'm afraid I've bricked my device beyond repair
update: I cannot mount my system_a partition in TWRP anymore. flashing stock fails with:
target reported max download size of 536870912 bytes
sending sparse 'system_a' (516697 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 4.295s
"Flash system_a error"
Any ideas? system_a cannot be 516697 KB in size no way!
Click to expand...
Click to collapse
Whoa bro. I stated on the thread that you need to have stock rom. LOS may not work, after that you could install it. Now, for the prob that you have, try downloading a different image, try to even downgrade it to 7 and see if it works to restore partitions. I would suggest july firmware, some of the fw are not full, some do not even touch partitions, I know that july does, reason why I am suggesting it
Will this work for this problem? https://forum.xda-developers.com/mi-a1/help/4g-update-to-pie-t3877027 It's quite similar.... but with stock beta pie....
arc4d14n said:
Will this work for this problem? https://forum.xda-developers.com/mi-a1/help/4g-update-to-pie-t3877027 It's quite similar.... but with stock beta pie....
Click to expand...
Click to collapse
Yes, it will work. But i suggest you to wait the official fix.
jack_21 said:
Yes, it will work. But i suggest you to wait the official fix.
Click to expand...
Click to collapse
Thank you, I'll wait for a couple of patches before trying this, I just wanted to now all the alternatives
I managed to get VoLTE working on the xz2cd (H8324) with T-Mobile USA using the xz3 (H8416) USA firmware oem-*.sin files.
Thank you to all the others that figured out the process details so all I had to do was try every combination - see the other VoLTE threads in this forum to guide you on the actual steps. Also thanks to Androxyde and Igoreisberg for the flash & download tools!
I have this working with the H8324_Customized NOBA_1313-6167_52.0.A.8.25_R5B firmware, I happen to choose, replacing only the oem-*.sin files from the XZ3 H8416_Customized US_1316-4522_52.0.A.8.25_R10B firmware. When you set both lines to "LTE (preferred)" and you'll be able to make LTE calls on both lines, however it may only show [HD] calling on the line you configured last I think but it'll be VoLTE on both.
Enjoy and thanks again to all the other threads that guided me through this long but worthwhile trial process. I wish the carriers didn't make LTE VoLTE provisioning difficult, why didn't they just make it universal like 3G.
Note: I was able to separately get Wifi-Calling to appear using the H8276_Freedom CA_1313-8876_52.0.A.8.25_R3B oem-*.sin files but it wasn't functional on T-Mobile USA - I think someone with a little bit more knowledge might be able to get this to work, unless you can point me in the right direction.
Someone please make an open firmware thin/light/compact dual SIM phone with Wifi-Calling/VoLTE (removable battery a bonus)!
Do you think the files would be the same on the H8314 US edition? i'm assuming you need to be rooted for this to work?
Hey Mike, Can you please share(download link) OEM*.sin files of USA firmware for Volte Settings
Im wondering if we can flash the OEM files from the US XZ1 Compact to get T-Mobile VOLTE and Wifi calling? I would try it myself but I cant find one of these phones at a reasonable price. If I do I will try and report back if anyone cares. I am glad at least VOLTE seems to work with this workaround.
VoLTE provisioned on XZ2 but calls are still made over 3G
I’ve done the same for my XZ2 (not compact, H8266). The VoLTE button is now active, but calls are still making over 3G. Any suggestion?
I just talked to a T-mobile specialist, and he confirmed that my phone should work and no need to register or do anything if it supports all bands!!! As he told me "only check for compatibility" and mine is compatible! ?
Were you ever able to get this working? New XZ2 owner and of course I bought this within a week is the announcement about all non VoLTE devices being kicked off in January..
Is there anyway to get volte working for tmobile on the h8314?
XZ2C H8314 VoLTE working on T-Mobile USA
colonelcack said:
Is there anyway to get volte working for tmobile on the h8314?
Click to expand...
Click to collapse
Yes VoLTE works but no VoWIFI with the following method:
Download USA Customized for XZ2C (H8314) and use only the two oem...sin files from XZ3 (H8416) USA Customized. (overwrite the two files in the XZ2C stack)
Use newflasher tool. (I deleted all .ta files and userdata file to avoid losing existing data)
To put the phone into flash mode, power off, hold the vol down button and plug in your usb cable while holding the button until you get a dim green light.
The device will show up in device manager under USB and you can run newflasher as administrator. Please search for a tutorial - there are many that are very good with screenshots of the files you want to move into the newflasher folder.
Some hangups I ran into when setting up and flashing -
Installing flashtool drivers required disabling driver signature enforcement on win10 (Flash device did not show up in usb in device manager until this was done)
For safety, after the flashtool driver install, I performed a repair on xperia companion app in case of any driver conflicts.
Running newflasher again, I got an error: Unable to open ./boot/Apollo_XBootConfig_MiscTA.ta! after multiple system files had been flashed.
But not to worry, the command window said the phone exited flash mode, but got error 933 - unable to sync. - No worries though, just make sure the command window states the phone is out of flash mode somewhere, disconnect your cable and power up your phone.
Then you will get an android message saying your carrier settings will update after reboot and the phone may reboot.
Once rebooted, enter *#*#4636#*#* in your phone dialer app (Takes 30 seconds after fresh boot for the menu to come up) , select phone information, and select LTE only (Note: VoLTE Provisioned will have the slider set to the right, but grayed out - Before the re-flash, the slider was set to the left and grayed out), reboot again. (If you click the 3 dots and look at IMS Status, you will see IMS status Registered, VoLTE Available and UT interface Available - Before the re-flash status was not registered and not available)
Now when you make a call, it will say "HD" in your dialer while on a call and your signal indicator will no longer say 3G when calling.
VoWIFI does not work, but you can use whatapp or something else like googleFi if its a must have, but in my case, I did not want to have to buy a new phone in January when they turn off 3G - Phones are too darn big now anyways and I love the display on this phone.
Notices will go out starting AUG 4th if your phone is marked as not supported using T-Mobile IMEI BYOD online tool - Their tool said my phone does not support VoLTE (Not fully true - It just does not have Band 71 for Long Range VoLTE but will use Band 4(66) just fine, I cannot confirm band 12 even though the phone spec supports it. It appears only Short range VoLTE is working on the phone unless someone else can confirm with this method, My Band 12 tower is behind a hill and i am 20 miles from it) T-mobile currently does not have a whitelist like AT&T, so If the UE (User Equipment - ie. phone) is configured properly, the network will handle the rest. I hope this practice does not change.
The advantage to using this method, is you are using completely stock USA files - My bootloader is locked and i am not rooted BTW. My XZ2C is only carrier unlocked.
The build number of both Roms I used was the same 52.1.A.3.49 XXX - Good Luck.
BTW - Some people were asking what modem config is working with VoLTE on T-mobile USA - to get the modem setting type *#*#7378423#*#* and in the service menu select software info, under Current modem config the value reads:
row/tmobile/vl/us
XZ1 oem files on XZ2 for VOLTE and VOWIFI calls.
nicogu said:
Im wondering if we can flash the OEM files from the US XZ1 Compact to get T-Mobile VOLTE and Wifi calling? I would try it myself but I cant find one of these phones at a reasonable price. If I do I will try and report back if anyone cares. I am glad at least VOLTE seems to work with this workaround.
Click to expand...
Click to collapse
You will need to try this. I was not so brave. The reason is the difference in the build IDs and oem.sin file names between the XZ1 (Old) and XZ2 (Current as of July USA Customized builds).
Mixing and matching files is easier when you are doing so off the same build ID. Thats why V0LTE worked on my XZ2 using XZ3 oem.sin files, they were from the same build ID and had the same names even though the sizes were slightly different.
It may work if the format of the oem.sin file did not change between the XZ1 builds and XZ2 Builds. The more different the builds, the higher the risk of something going wrong.
---------- Post added at 01:31 AM ---------- Previous post was at 01:28 AM ----------
gigili said:
I’ve done the same for my XZ2 (not compact, H8266). The VoLTE button is now active, but calls are still making over 3G. Any suggestion?
Click to expand...
Click to collapse
Enter *#*#4636#*#* in your phone dialer app, select phone information, and select LTE only - Reboot, if you cant make calls after that something else is wrong.
---------- Post added at 01:33 AM ---------- Previous post was at 01:31 AM ----------
hitemup92 said:
Were you ever able to get this working? New XZ2 owner and of course I bought this within a week is the announcement about all non VoLTE devices being kicked off in January..
Click to expand...
Click to collapse
Got this to work, no VoWIFI though - look further down the thread.
depsilon said:
Yes VoLTE works but no VoWIFI with the following method:
Download USA Customized for XZ2C (H8314) and use only the two oem...sin files from XZ3 (H8416) USA Customized. (overwrite the two files in the XZ2C stack)
Use newflasher tool. (I deleted all .ta files and userdata file to avoid losing existing data)
To put the phone into flash mode, power off, hold the vol down button and plug in your usb cable while holding the button until you get a dim green light.
The device will show up in device manager under USB and you can run newflasher as administrator. Please search for a tutorial - there are many that are very good with screenshots of the files you want to move into the newflasher folder.
Some hangups I ran into when setting up and flashing -
Installing flashtool drivers required disabling driver signature enforcement on win10 (Flash device did not show up in usb in device manager until this was done)
For safety, after the flashtool driver install, I performed a repair on xperia companion app in case of any driver conflicts.
Running newflasher again, I got an error: Unable to open ./boot/Apollo_XBootConfig_MiscTA.ta! after multiple system files had been flashed.
But not to worry, the command window said the phone exited flash mode, but got error 933 - unable to sync. - No worries though, just make sure the command window states the phone is out of flash mode somewhere, disconnect your cable and power up your phone.
Then you will get an android message saying your carrier settings will update after reboot and the phone may reboot.
Once rebooted, enter *#*#4636#*#* in your phone dialer app (Takes 30 seconds after fresh boot for the menu to come up) , select phone information, and select LTE only (Note: VoLTE Provisioned will have the slider set to the right, but grayed out - Before the re-flash, the slider was set to the left and grayed out), reboot again. (If you click the 3 dots and look at IMS Status, you will see IMS status Registered, VoLTE Available and UT interface Available - Before the re-flash status was not registered and not available)
Now when you make a call, it will say "HD" in your dialer while on a call and your signal indicator will no longer say 3G when calling.
VoWIFI does not work, but you can use whatapp or something else like googleFi if its a must have, but in my case, I did not want to have to buy a new phone in January when they turn off 3G - Phones are too darn big now anyways and I love the display on this phone.
Notices will go out starting AUG 4th if your phone is marked as not supported using T-Mobile IMEI BYOD online tool - Their tool said my phone does not support VoLTE (Not fully true - It just does not have Band 71 for Long Range VoLTE but will use Band 12 just fine) T-mobile currently does not have a whitelist like AT&T, so If the UE (User Equipment - ie. phone) is configured properly, the network will handle the rest. I hope this practice does not change.
I made the mistake of calling sony and t-mobile for support and they both kept blaming each other, the reason they don't know why VoLTE does not work on some phones is they really don't know enough about their network or the basebands in the phone or the software build process and details about android sin files - as they should not either cause if the network engineers, device manufacturers and software developers all do their job and stick to industry standard practices, it will just work anyway.
The advantage to using this method, is you are using completely stock USA files - My bootloader is locked and i am not rooted BTW. My XZ2C is only carrier unlocked.
The build number of both Roms I used was the same 52.1.A.3.49 XXX - Good Luck.
BTW - Some people were asking what modem config is working with VoLTE on T-mobile USA - to get the modem setting type *#*#7378423#*#* and in the service menu select software info, under Current modem config the value reads:
row/tmobile/vl/us
Click to expand...
Click to collapse
Thank you so much for the detailed instructions! Only one question... Where do I download these files from? And the tool? Can you link me...
Sorry it's been a long time since I've done any xda stuff
H8314 Flash tools
colonelcack said:
Thank you so much for the detailed instructions! Only one question... Where do I download these files from? And the tool? Can you link me...
Sorry it's been a long time since I've done any xda stuff
Click to expand...
Click to collapse
I dont have direct links, but here is an excellent walkthrough that calls out all the tools -
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Search for flashtool on XDA there should be links for that, but you only install the drivers from it, not the tool.
You also need the xperia companion software download from sony website for any missing drivers from flashtool.
Search XDA for newflasher, thats what you will actually flash with - https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
the firmware download utility is xperifirm software - https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
depsilon said:
H8314 Flash tools
I dont have direct links, but here is an excellent walkthrough that calls out all the tools -
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Search for flashtool on XDA there should be links for that, but you only install the drivers from it, not the tool.
You also need the xperia companion software download from sony website for any missing drivers from flashtool.
Search XDA for newflasher, thats what you will actually flash with - https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
the firmware download utility is xperifirm software - https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Click to expand...
Click to collapse
It's been a while but wanted to thank you for taking the time to write out these steps. I finally took a shot with the incoming shutdown of 3g for my XZ2, but unfortunately it did not work. Similar to what gigili said, while VoLTE appears to be provisioned the calls are dropping to 3g/HSPA like they originally were. After setting to "LTE Preferred" and rebooting, calls would not be made at all. I also saw "Unknown" under the Modem Config, and from what you said it should reference T-Mobile after flashing the OEM sin files.
I tried this using the latest firmware available on XperiFirm for the XZ2 (Customized US H8266 - my device is H8276) and the XZ3, which I used to grab the two OEM sin files. The firmware is 52.1.A.3.137.
Using UnSin, I unpacked both "oem_X-FLASH-CUST-B6B5.sin" files in both firmwares, and under modem-config there are a bunch of folders, and each one seems to have a conf files pointing to "mcfg_sw/generic/row/tmobile/vl/us/mcfg_sw.mbn."
I read in another thread that T-Mobile maybe has some way of blocking this workaround now, but I'm not entirely sure if that is true? Totally understand if you've moved on from the device as it's been a while, but am admittedly curious if there's a specific firmware version that this works on I could try to salvage the device.
Volte xz2/xz2 p/xz3 solved
Samir solanki said:
Volte xz2/xz2 p/xz3 solved
Click to expand...
Click to collapse
Details on exactly how?
I will create complete guide thread for the same
Samir solanki said:
I will create complete guide thread for the same
Click to expand...
Click to collapse
Thanks I'll watch for it
I am working to bring support for T-Mobile VoLTE on the xz2c to LineageOS 18.1. As of this writing, official LineageOS builds for this device do not support VoLTE unless it was already enabled and working in the stock firmware.
I have submitted some patches which may resolve the issue for TMO and probably other carriers as well. They work for me, but testing has been limited. If you are interested in using LineageOS instead of the stock ROM, and you are willing and able to build LOS yourself on linux, consider giving my patchset a try. Please read the patch description fully before attempting a build: you will need to obtain and mount some additional files first. The LineageOS wiki has additional instructions for creating a build environment.
EDIT: My patch is part of official LOS 18.1 starting with nightly 20220401. There is no need to build it yourself.
cbs228 said:
---
Click to expand...
Click to collapse
You are a saint for working on this. I bought a H8324 XZ2c recently and was super disappointed it didn't work, so I am back to my XZ1c. Super frustrated. If you ever get a pre-compiled ROM, I would love to try. In the meantime I will try to compile it myself in the coming days despite my technical illiteracy.
If that doesn't end up working, what stock firmware is available with T-Mobile VoLTE enabled and working, so I could step up from that to Lineage? Considering how old the other solutions for trying to get VoLTE working, I am hesitant to try any especially funny business of switching old firmware files from other phones around.
xperiaperson42069 said:
If that doesn't end up working, what stock firmware is available with T-Mobile VoLTE enabled and working, so I could step up from that to Lineage?
Click to expand...
Click to collapse
As far as I am aware there isn't any stock firmware that works "out of the box." The xz2c is listed as "unsupported" by t-mobile, which probably means there isn't any sort of stock ROM out there that works. Sometimes carriers do release "branded" ROMs, but there's nothing like that for this device AFAIK.
LinageOS is designed to be installed "on top" of an existing stock ROM. If you attempt to install it after you have flashed another distro (like an AOSP build), you will likely just make a brick. If you do end up bricking your device, do not despair. You can use Emma to restore your device to factory condition. Emma is available on the Sony Developer World website, and there are many guides available for it.
So I've been reading and just trying to verify if I'm using the T-Mobile version of oneplus 8i can't install the betas? If I'm wrong can someone point me to the correct version to install? We just got beta 3
goast said:
So I've been reading and just trying to verify if I'm using the T-Mobile version of oneplus 8i can't install the betas? If I'm wrong can someone point me to the correct version to install? We just got beta 3
Click to expand...
Click to collapse
The T-Mobile software removes the ability to install update from local storage. You would have to convert to Global to be able to install the betas. I am running a T-Mobile OP8, converted to Global, running beta 3 no issues.
Global Version
stompysan said:
The T-Mobile software removes the ability to install update from local storage. You would have to convert to Global to be able to install the betas. I am running a T-Mobile OP8, converted to Global, running beta 3 no issues.
Click to expand...
Click to collapse
Do you have a link as to where i can get Global version or steps for getting it ?
j1232 said:
Do you have a link as to where i can get Global version or steps for getting it ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8/how-to/guide-convert-to-global-t4105885
Make sure to read everything on the thread. Pull an image of your persist and your modem before flashing global. Some people lose network and/or FP, though having those two files can typically repair them pretty easily. If something bad happens during the conversion, you can use MSM to go back to T-Mobile firmware, but that doesn't fix your FP reader. That's why grabbing the persist is most important. You can do both from booting TWRP. Back up the modem directly in TWRP, and use adb shell along with "dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img" to make an image of the persist. Once on global, you can simply install the update through the local upgrade process and go from there. From what I have read, you do lose 5G SA. I don't know if this is still valid on the latest beta or not, but it is something to note.
stompysan said:
https://forum.xda-developers.com/oneplus-8/how-to/guide-convert-to-global-t4105885
Make sure to read everything on the thread. Pull an image of your persist and your modem before flashing global. Some people lose network and/or FP, though having those two files can typically repair them pretty easily. If something bad happens during the conversion, you can use MSM to go back to T-Mobile firmware, but that doesn't fix your FP reader. That's why grabbing the persist is most important. You can do both from booting TWRP. Back up the modem directly in TWRP, and use adb shell along with "dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img" to make an image of the persist. Once on global, you can simply install the update through the local upgrade process and go from there. From what I have read, you do lose 5G SA. I don't know if this is still valid on the latest beta or not, but it is something to note.
Click to expand...
Click to collapse
How can one tell of phone is using 5g SA on OB3?
crazynapkinman said:
How can one tell of phone is using 5g SA on OB3?
Click to expand...
Click to collapse
Using a program like LTE Discovery will tell you. In my case, it indicates I am connected to NR NSA 5G. I have not ever seen my phone go to SA 5G since converting, and I do live in an SA location and have connected while on T-Mobile software. See screenshot.
Mine says 5G NR
crazynapkinman said:
Mine says 5G NR
Click to expand...
Click to collapse
I have noticed it takes some fiddling with WiFi to get it to display network type. The 5G detection is still a WIP. There are probably other apps that may work better, but I am just used to using LTE Discovery over the years.
I'm also on a tmobile converted to global phone. Using Beta 3 and getting random errors with the sim card where phone says "no sim". Happens 1-2 times per day. Only way to fix is to reboot or eject the sim and reinsert. Either way, back to full bars for a few hours. I backed up modem and persist, but I don't think the Android 10 modem will work on Android 11. Also, can't flash because TWRP doesn't work on Android 11 yet. Very frustrating, looks like lots of reports of this happening on Oneplus 8 phones (Tmobile and unlocked) on here and oneplus forums. No solution found!
xxBrun0xx said:
I'm also on a tmobile converted to global phone. Using Beta 3 and getting random errors with the sim card where phone says "no sim". Happens 1-2 times per day. Only way to fix is to reboot or eject the sim and reinsert. Either way, back to full bars for a few hours. I backed up modem and persist, but I don't think the Android 10 modem will work on Android 11. Also, can't flash because TWRP doesn't work on Android 11 yet. Very frustrating, looks like lots of reports of this happening on Oneplus 8 phones (Tmobile and unlocked) on here and oneplus forums. No solution found!
Click to expand...
Click to collapse
I have Sprint sim and this is not happening.
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
Hey guys.... I'm using pro 7 in an unsupported county and I was able through guides to enable all the missing features expect the 5g...can anyone help me?
So do i, looking forward for this. Sim provider support 5g but Google not provide it. Any tips will be appreciated
Same here. I had found a temporary fix on pixel 6 that worked for people but not for me. Let's see if a wizard here can help
You can activate the 5G in the supported countries with magisk
I have follow the guides here....I successfully enable call screening, wifi calling etc.....but 0 luck with 5g....I don't understand what I'm missing
G_Vasi said:
I have follow the guides here....I successfully enable call screening, wifi calling etc.....but 0 luck with 5g....I don't understand what I'm missing
Click to expand...
Click to collapse
Any luck with vowifi or direct my call?
Yeah I have manage to enable all the features expect 5g
G_Vasi said:
Yeah I have manage to enable all the features expect 5g
Click to expand...
Click to collapse
I read about volte zip magisk modul need to flash,did you flash it?
As I said....I have manage to enable all the features such us volte etc.... everything work except 5g...and yes I have 5g in my area
Have you gone into the Phone Information screen and enabled NR?
*#*#4636#*#*, choose Phone Information. Under preferred network type, change it to NR/LTE.
If that doesn't work, your carrier could be blocking it or it could need a special network configuration that the Pixel doesn't have being an unsupported device. Either way, you may be out of luck.
EtherealRemnant said:
Have you gone into the Phone Information screen and enabled NR?
*#*#4636#*#*, choose Phone Information. Under preferred network type, change it to NR/LTE.
If that doesn't work, your carrier could be blocking it or it could need a special network configuration that the Pixel doesn't have being an unsupported device. Either way, you may be out of luck.
Click to expand...
Click to collapse
I can't get into phone information with that code . I got messageroblem with network or unsupported MMi code.
I'm not rooted yet and didn't unlocked bootloader. Anyone successfully get 5G in unsupported country?
My network provider support 5G
Josh said:
I can't get into phone information with that code . I got messageroblem with network or unsupported MMi code.
I'm not rooted yet and didn't unlocked bootloader. Anyone successfully get 5G in unsupported country?
My network provider support 5G
Click to expand...
Click to collapse
Sounds like your SIM is disabling the menu.
Download this app and it will bypass that.
Force LTE Only (4G/5G) - Apps on Google Play
This app will help You change network to 5G/4G/3G/2G and stay in chosen network
play.google.com
Set up the app and use Method 2 to get that menu pulled up.
I was able to use that app to force my OnePlus 9 to use 5G when I flashed the Chinese firmware that didn't actually support US carriers and also blocked dialer access to the menu so it's worth a shot.
EtherealRemnant said:
Sounds like your SIM is disabling the menu.
Download this app and it will bypass that.
Force LTE Only (4G/5G) - Apps on Google Play
This app will help You change network to 5G/4G/3G/2G and stay in chosen network
play.google.com
Set up the app and use Method 2 to get that menu pulled up.
I was able to use that app to force my OnePlus 9 to use 5G when I flashed the Chinese firmware that didn't actually support US carriers and also blocked dialer access to the menu so it's worth a shot.
Click to expand...
Click to collapse
No luck, only just unlock bootloader and root with Magisk and flash modul VOLTE to force 5G but only what makes me bad is that data must be wiped and must again activated bank app and that is procedure. Any solution to avoid vipe data when I unlock bootloader? I think that there is not
Josh said:
No luck, only just unlock bootloader and root with Magisk and flash modul VOLTE to force 5G but only what makes me bad is that data must be wiped and must again activated bank app and that is procedure. Any solution to avoid vipe data when I unlock bootloader? I think that there is not
Click to expand...
Click to collapse
Yeah with you being stuck on EDGE, I don't have high hopes that you're able to fix this without root (and even then, you may not).
There is no way to unlock the bootloader and preserve data as the wipe is a security precaution.
G_Vasi said:
Hey guys.... I'm using pro 7 in an unsupported county and I was able through guides to enable all the missing features expect the 5g...can anyone help me?
Click to expand...
Click to collapse
Which carrier?
Vodafone GR
If you are rooted, did u try the network signal guru method?