I can confirm using the link below in a forum in the m9 section, I've been able to unlock bands 2,3,4,7,12 and 17 lte for a verizon build phone that is using tmobile service now. There are also instructions for other bands for other provides in the op. Used DFS tool, diag adb commands to enable diag.
http://forum.xda-developers.com/one-m9/general/how-to-change-network-bands-gsm-devices-t3135401
can you help me out with adding band 40 lte 2300mhz for indian gsm network
Casetheace said:
I can confirm using the link below in a forum in the m9 section, I've been able to unlock bands 2,3,4,7,12 and 17 lte for a verizon build phone that is using tmobile service now. There are also instructions for other bands for other provides in the op. Used DFS tool, diag adb commands to enable diag.
http://forum.xda-developers.com/one-m9/general/how-to-change-network-bands-gsm-devices-t3135401
Click to expand...
Click to collapse
hi i have been using Verizon htc one m8 in india on gsm network for an year now. As the 4g Lte services are launched in my country i got to know my phone does not support the required band. I just want to know the process to add Lte band 40 2300MHz to verizon htc one m8. my htc m8 is S-0ff on SD V10.1 rom thanks in advance.
I would believe that it would work using those links and the guide in it. Concern would be is the author of it clearly States enabling extra bands may break phone to point of RUU won't fix it. I can tell you on my Verizon m8 when I first used the DFS tool I had 4 Lt bands enabled, believe is was 2,4, 12 and maybe one more. So 3 or 4. I have it on T-Mobile sim, so. Was enabling 6 bands, at least 2 more then before. My first try I accidentally hit band 40 also so I was turning all T-Mobile bands on and a extra one. Now that didnt fry my radios. Noticed it on the first text to check if it worked. I'll write why I did, I think enabling just that one band won't kill it. Also if a band is active and you don't use it, maybe turn that off and 40 on. Okay heres my step by step guide it did.:
1. Downloaded DFS TOOl , free version is fine just takes extra time that's all.
2. Using command prompt., did the adb shell, then su, phone will ask for approval for supersu access. Then enter the code to turn hdiag on. You want to use the one for m8, first codes are for m9 , the m8 is clearly said in bold. Once entered to turn in on. Plug in your phone. Now run DFS with administrative rights, can't remember what the exact steps for the next things but just follow the guide. In DFS tool you should see your phone connect , not in usb mode, but cm 8 port, cm 7port. Now for the computer to read the phone in DIAG you need the driver, its in the m8 HTC sync manager thing. So if that's installed you have it already. Now if it's installed and you don't see it recognised in diag mode using device manager option your PC (by the way I'm running WIN 10 on my PC) I had read that I'm windows 8 it would not accept drivers without signatures. There is a guide in there explaining how to install under that. My phone was not picked up in DIAG mode, had sync manager , driver installed from DFS tool, then used a zip I'm authors guide. Unzipped folder and it was broken into folders. Have to find folder with exe to run it. After all this still no dice. Then went to device manager , went to phone where it stated driver missing. Douple clicked on it. Chose option to update driver, selected in there a option that will show you all the drivers installed on the device. Chose the HTCDIAGDRIVER. It installed it and had to reboot comp.
3. Now go back to DFS TOOL., follow the authors guide to the T in this process. You pick the last tab , LTE , I believe. Following guide, I let it read all my lte bands, wrote down all the current ones in case I needed to change it in time. Then chose to read again and write down LTE bands using authors guide, of the selection in bottom right of screen u need to chose. In guide it States the name of it, and to choose that and read. In that option In bottom right, there is another selection next to it, 3 of 4 same words can't remember the word but its in Authors guide. Now your gonna want to have what bands are currently enabled, in authors guide is what LTE bands should be choose by manufacturers default. I then choose the bands it had listed that should be, and deselected any bands that where not being used on current provider. Now you want to hit write after choosing your bands. Now after that you want to write the bands in next mode that author says to change just in case. OK, now you can't do both writes at same time. If you do, first write won't stick and only second. I tried and can tell you that. So write , reboot, write, reboot. Now after that, reconnect phone to PC and read both things you just changed to make sure they stuck.
4. Using command prompt on PC, adb shell, su , then code to turn the hdiag mode off. If you don't PC won't recognize the phone as prober driver and a DIAG mode. Make sure to do this.
That's what I did. I would advise to read all ten pages of former questions, lost of newer information that will only help you understand it more.
I'm far from a expert, I just know the adb commamd process, how to flash ROMs, mostly basic things. 4 Years ago I knew nothing. So I'm sure u can do it. Author will answer questions, mostly every question you can think of has been asked in those ten oahes and you will learn it from there. So i would read all posts so you have a good feel of it. Anything I can help you with write back. Havent been on in two weeks. Stock market has my attention 18hrs a day
Related
I just got my RAZR HD XT926, and I thought I would see f I can up it to Kitkat, or maybe even to Jellybean. No big deal, but it has been a while and I forgot the unlock thingie. There is currently no SIM inserted.
Current ROM: 9.1.41.xt926.verizon.en.us
Here is what I have done:
- Set the phone to USB debug
- Downloaded 4.4.2
- Downloaded RSDLite 6.1.x
RSD lite started fine, I already had my drivers installed, everything seems fine. However, I forgot to unlock it. The phone is in CMD mode, telling me the Device is Locked:status code: 0.
So I went to the Motorola unlocking service (I can google, I try to do a decent effort before posting for help) so I am in the process of doing just that, following the Moto instructions, but there is one thing I do not get with those. First it want to download a vast amount of updates, which I allow with default selection, then:
- Motorola tells me to place my CMD prompt at the SDK tools and type $ fastboot oem get_unlock_data . Where is that, in which folder of the SDK?
- Will it even work with phone in that mode?
Update. I managed to access the device ID and submit to Motorola. This device can not be unlocked by Motorola method.
So, can it be unlocked at all?
Update 2. Got out of boot mode by reversing the button controls while starting.
Might as well keep posting about my progress
I got the 4.4.2 Verizon (VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF) stock working with the help of www_phonearena.com/news/root-comes-to-the-motorola-droid-razr-hd-razr-m-and-atrix-hd_id35615 Motofail2go who emulated the root boot thingie that i failed to accomplish otherwise. In the phone it now says System version 183.46.10.xt926.Verizon.en.US, Android version 4.4.2.
After inserting a SIM card (Swedish 3, www_tre_se) calling works.
Upgrade to Kitkat, and calling outside of US = works. As described in this and above post.
It seems there is no need to unlock it at all. For my purposes as of yet.
Very werd, it seems to accept some SIM cards but not others, depending on provider.
As I posted above it worked with a 3 SIM card, but today testing with a Telia SIM card it claims that it is from an unrecognized source. After some googleing this could both be an issue, and not, depending on circumstances. The easiest check might be to make sure I have a 4G SIM card for the Telia subscription.
It found an update, an official one.
I just hit "Yes" and "Download" and "Install" so tight now its doing that. Could it be KitKat? :fingers-crossed:
/Edit: after update: 183.46.15.XT926.Verizon.en.us. It was not KitKat, still at 4.4.2
One would think it should detect it is not at home anymore...
XT925: www_gsmarena.com/motorola_razr_hd_xt925-4970.php
XT926 : www_gsmarena.com/motorola_droid_razr_hd-4971.php
Make note of the difference between LTE support. 925 is the one you want.
This explains part of my issues, I am returning the 926 and placed an order on 925.
(bloody URL blocker!)
Hi,
I am sorry that I post this message in the wrong place, I believe it belongs to this thread
I have just return from US and I got a LG Leon from MetroPCS to sty connected while there. Now that I am back I unlocked the phone via unlock app. My surprise came when I put me Spanish SIM card (Jazztel) and the phone only gets 2g connection. I have been searching the net and I found some threads on the topic but I can not make any of them work on my phone. First I tried changing the radio to Europe mode through *#*#4636#*#*, and I enter the test page but when I click the phone info button I get a message that states that I can not run that application on this device. I thought it was because I wasn't root so I rooted it. But before I could root I had to downgrade by flashing an older firmware. No way, I get the same message. I tried the hidden menu to see if I could find an entry to change the radio mode, or any type of LTE configuration. Hidden menu on my phone though 277634#*#. I also tried the anycut option, but I do not get any facility called LTE configuration or similar.
I am desperate and I do not know how to proceed. Any help is welcome
Thanks in advance
@sd_shadow
Went to the Verizon store to get my droid unlocked only to have the tech people there input different codes that did not work and the security feature unexplained. I went to try the sim and within a few tries it was locked.
Tech support has given me the sim network code that goes with the phone now that it is subsidy locked. I have looked at the steps on Sd Shadow's site about flashing and rooting the phone and have gone so far as to download and install the motorola drivers (signed by microsoft?). The device now shows in device manager as an ADA interface.
I have tried flashing with rsd lite, only to hear several sounds as if the device is reconnecting and see flash failure at 6/18 partition.
Am I using an incomplete .Xml?
The Fast boot version is 0A.53 and the xml downloaded from http...........://......................motofirmware.center/files/ was
VRZ_XT862_5.5.1_84_D3G-55_1FF_01.xml.zip
Haven't seen anyone trying to unblock for use with Pure Talkusa. I don't know if it makes any difference what third-party carrier i decide to go with.
I have used three different cords for the flashing, one of them does not "wiggle" in the ports like the others, but it is an older cord.
I am using Windows 7
Shakbazian said:
Went to the Verizon store to get my droid unlocked only to have the tech people there input different codes that did not work and the security feature unexplained. I went to try the sim and within a few tries it was locked.
Tech support has given me the sim network code that goes with the phone now that it is subsidy locked. I have looked at the steps on Sd Shadow's site about flashing and rooting the phone and have gone so far as to download and install the motorola drivers (signed by microsoft?). The device now shows in device manager as an ADA interface.
I have tried flashing with rsd lite, only to hear several sounds as if the device is reconnecting and see flash failure at 6/18 partition.
Am I using an incomplete .Xml?
The Fast boot version is 0A.53 and the xml downloaded from http...........://......................motofirmware.center/files/ was
VRZ_XT862_5.5.1_84_D3G-55_1FF_01.xml.zip
Haven't seen anyone trying to unblock for use with Pure Talkusa. I don't know if it makes any difference what third-party carrier i decide to go with.
I have used three different cords for the flashing, one of them does not "wiggle" in the ports like the others, but it is an older cord.
I am using Windows 7
Click to expand...
Click to collapse
The member you mentioned (sd_shadow) has replied to you in his thread
http://forum.xda-developers.com/showpost.php?p=64183133&postcount=2
Post further questions and discussions in that thread to get further help (that is the correct section to post)
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.