Database Info

[Q] Lost 4G after flashing another Stock

Hello guys.
I have a xperia Z3 from VIVO and flashed a rom from OI, everything went well on flashing the rom but after it finished i noticed that i lost my 4G. When i search for network there have a TIM BRASIL LTE but it won't let me register on it.
Do anyone know how to solve that?
Thanks!

Input the correct apn settings from your carrier

LitoNi said:
Input the correct apn settings from your carrier
Click to expand...
Click to collapse
Lito, do you think that would help?
Because the problem is that I am not able to register to the LTE network, it's not related to the ability of using internet.
Actually, this is exactly what happens, after i flash the firmware i have 4G but after a few minutes (Between 5 and 10 minutes) i completelly lose connection to the LTE network, even if it's available in the networks list.

Info
DiegoManBR said:
Lito, do you think that would help?
Because the problem is that I am not able to register to the LTE network, it's not related to the ability of using internet.
Actually, this is exactly what happens, after i flash the firmware i have 4G but after a few minutes (Between 5 and 10 minutes) i completelly lose connection to the LTE network, even if it's available in the networks list.
Click to expand...
Click to collapse
just test firmware of another region
(UK firmware for example)
:good:

DiegoManBR said:
Lito, do you think that would help?
Because the problem is that I am not able to register to the LTE network, it's not related to the ability of using internet.
Actually, this is exactly what happens, after i flash the firmware i have 4G but after a few minutes (Between 5 and 10 minutes) i completelly lose connection to the LTE network, even if it's available in the networks list.
Click to expand...
Click to collapse
Maybe if you explained a bit better that would?
Like mentioned before this post, try to flash only the baseband from another region, hopefully that will solve it.

Geeks Empire said:
just test firmware of another region
(UK firmware for example)
:good:
Click to expand...
Click to collapse
Geeks, there have no other region for my version of the Z3, also i am trying to flash many other rooms from my region and all of them results in a error during the flash... Blank error, no description.

LitoNi said:
Maybe if you explained a bit better that would?
Like mentioned before this post, try to flash only the baseband from another region, hopefully that will solve it.
Click to expand...
Click to collapse
Lito, thanks for the sugestion, i flashed the baseband for the Customized PT and after flash i got the 4G signal for about 30 minutes, but when i rebooted the phone, i completelly lost 4G again, and now in the network lists there is no LTE from TIM. Could it be because i installed an european baseband on a mobile here in brazil?
Thanks agian.

DiegoManBR said:
Lito, thanks for the sugestion, i flashed the baseband for the Customized PT and after flash i got the 4G signal for about 30 minutes, but when i rebooted the phone, i completelly lost 4G again, and now in the network lists there is no LTE from TIM. Could it be because i installed an european baseband on a mobile here in brazil?
Thanks agian.
Click to expand...
Click to collapse
thats weird... are you sure you have the correct APN settings inputted? Also, i would assume youve tried flashing the VIVO's baseband or any other USA roms?
Try the following if you have already done all those: go to dial pad and input *#*#4636#*#* > phone info > menu top right > select radio band > try Australia or USA or what ever pops up > scroll down and make sure LTE/GSM auto is selected or try out the other ones > scroll back up and hit the "run ping test"
if all these doesnt work, i would advise you to go back to the original rom.
just curious, which model number is your Z3?

LitoNi said:
thats weird... are you sure you have the correct APN settings inputted? Also, i would assume youve tried flashing the VIVO's baseband or any other USA roms?
Try the following if you have already done all those: go to dial pad and input *#*#4636#*#* > phone info > menu top right > select radio band > try Australia or USA or what ever pops up > scroll down and make sure LTE/GSM auto is selected or try out the other ones > scroll back up and hit the "run ping test"
if all these doesnt work, i would advise you to go back to the original rom.
just curious, which model number is your Z3?
Click to expand...
Click to collapse
Lito, now i will complicate a little bit more then. First, the model number of my mobile is D6646 from Brazil with DTV.
Also, i tried to flash the Vivo Baseband and it was worse, i did not install any baseband from USA, just from Portugal.
I tried that on the keyboard, but when i chose USA band i just can't even register on any TIM network.
Also, i tried to flash the original rom, but i can't flash any other firmware apart from Oi. I get a blank error line on flashtool for every other rom i tried to install, so it's even worse
Feel the challenge.
Thanks again for all your help.

flash back to the original ROM if you can, also, how did you flash to the new rom? through recovery or Flashtool? if you see a blank space or what ever, you might not have the correct drivers installed on your computer, especially if youre running Windows 8.
that being said, i dont see D6646 in Xperifirm, i cant tell you what to flash and what not to flash. Without that, i wouldnt advise you to flash anything but the original rom that it came with, you dont want to soft/hard brick the device.

LitoNi said:
flash back to the original ROM if you can, also, how did you flash to the new rom? through recovery or Flashtool? if you see a blank space or what ever, you might not have the correct drivers installed on your computer, especially if youre running Windows 8.
that being said, i dont see D6646 in Xperifirm, i cant tell you what to flash and what not to flash. Without that, i wouldnt advise you to flash anything but the original rom that it came with, you dont want to soft/hard brick the device.
Click to expand...
Click to collapse
Lito, I tryied to flash the original room, I am using XperiaFirm to download the firmware and flashtool to flash. I can flash the Oi room, but i can't flash the vivo BR, the Claro Argentina, or the Customized PT, all of them results in a blank error, it's not drivers problems, since i can install the Oi firmware and also i disabled the signature on windows in order to install.
Anyway, i solved the problem in order to show another problem. Here is the situation:
I created another APN to use when i don't want to use internet because even with data package disabled my mobile send data to the carrier that charges me, when i deleted that APN the 4G worked perfectly, but now my carrier is charging me the data . Any idea how to block this data comsumption?
Thanks again.

DiegoManBR said:
Lito, I tryied to flash the original room, I am using XperiaFirm to download the firmware and flashtool to flash. I can flash the Oi room, but i can't flash the vivo BR, the Claro Argentina, or the Customized PT, all of them results in a blank error, it's not drivers problems, since i can install the Oi firmware and also i disabled the signature on windows in order to install.
Anyway, i solved the problem in order to show another problem. Here is the situation:
I created another APN to use when i don't want to use internet because even with data package disabled my mobile send data to the carrier that charges me, when i deleted that APN the 4G worked perfectly, but now my carrier is charging me the data . Any idea how to block this data comsumption?
Thanks again.
Click to expand...
Click to collapse
that is extremely weird, never had such issues with any of my android phones. make sure data roaming is not on, the carrier shouldnt be able to charge you if you disabled data
Also, make sure the FTF files youve made with xperifirm and flashtool are correct, like not including the TA files etc..., i would advise you redownload those FTF files and try again, also make sure you have the latest flashtool available.
at this point, you are probably better seeking for a developer or someone who can read codes, make a logcat and see if the flashtool thread is available and ask there. Aside from the FTF files, you are better off asking the carrier why they are still able to charge you in such way. Sorry man, this is as far I can aid you in this matter. GL bud!

[ODIN] Stock Nougat Firmware [SM-G935T] S7 Edge to use it on 935v

Here is the link to the tmobile original thread
[ODIN] Stock Nougat Firmware [SM-G935T] S7 Edge
Instuctions provided by jrkruse (original post)
1. You need to be on Verizon Beta Nougat 2
2. In developer options turn on OEM unlock
3. Reboot to download mode
4. Load the files you downloaded in the corresponding slots in odin BL,AP CP, CSC the files are labeled this way
you dont use the G935TUVU4BQB1_Boot_Recovery_Image.tar.md5 until later
5. Install with odin the phone will reboot to recovery to finish the csc install
6. If the csc install in recovery fails reboot to bootloader in stock recovery
7. In odin reflash the CSC file in the CSC slot in odin. The phone will reboot to recovery again and install the csc files
8. Once the phone is done installing and wiping in recovery try and catch the phone as it reboots and reboot back to
download mode (PWR+Home+Vol Down )
9. Use odin Install G935TUVU4BQB1_Boot_Recovery_Image.tar.md5 in the AP slot
10. Let phone reboot and go through setup
11. During Setup you may have trouble typing info in the setup boxes the keyboard has some bugs in setup. I recommend skipping
adding any accounts and do it after your through setup. Or use the alternative method to find your google account
12. Once through setup download 4G LTE Switch and use to Change Network to LTE/CDMA auto (PRL)
13. I recommend downloading Package Disabler Pro (It Works now) and disable all Tmobile Apps
I found samsung pay wasnt working I found that the tmb bootloaders and persist.img needed to also be flashed I made a new odin flashable package and install instructions. All seems to work now except of course volte and wifi calling.
Explanation why you need to be on nougat beta 2
Download:
TMOBILE_NOUGAT_VZW.ZIP
ODIN v3.12.3.zip
Possible Issues and solutions :
Q: after flashing the bootloaders and persist.img, it broke all data and calls and texts again.
A: they need to be all flashed at same time. Maybe Wipe data and it might work
Q: The Google "email or phone" text input box still only accepts one letter and any extra letters overwrite the previous letter typed.
A: The samsung keyboard will work fine if you just goto settings on the keyboard to language and types and change to US english.
Q: So the question is..... this worth flashing or wait for vzw?
A: Other than no volte this definitely the best running Rom so far. It is much better than beta
Q: 13. I recommend downloading Package Disabler Pro (It Works now) and disable all Tmobile Apps
Care to share your list?
A: List of Tmo apps to disable
Q: Except MMS isn't working, for me anyways. VoLTE isn`t working.
A: I got volte working and video calling maybe this will help mms for you
Download App shortcut maker from playstore
Select all activities find IMS Settings and create shortcut
Open the ims settings from the created shortcut
Choose Ims service switch
Click on MMTEL switch
Click on RCS switch
Under MMTEL section I enabled all the options
Q: Cant get this thing to flash CSC...just keep getting the dm-verity error 0x02.
A: 1:Flash all 4 files in zip.
2:let reboot and see if you get dm verity error.
3:if you get the error than reboot to bootloader and reflash all 4 again.
4:after it reboots again it will say error.
5:reboot to bootloader and flash the csc again.
Q: in 4g lte switch, i dont see the option for lte/cdma auto. could this stuff be because csc didnt flash correctly?
A: if you have the verizon data icons you know the 4g lte then it flashed correctly. If you see data icons that ate not verizon then it didnt flash correctly.
When every one is starting over are you flashing a pit file when going pack to ph1. If not you need too.
P.S. All credits goes to jrkruze. :good:

You mentioned to install Nougat beta first before installing t mobile firmware. Is that necessary? Also, any link for Verizon apn?
Sent from my SM-G935V using Tapatalk

junear said:
You mentioned to install Nougat beta first before installing t mobile firmware. Is that necessary? Also, any link for Verizon apn?
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Look at you apn settings and just copy it. I didn't mention about to install nougat beta, I mentioned that it was installed successfully on nougat beta and that you must be on latest bootloader.

Okay so I have T-Mobile Nougat installed on my device, and I've changed my VPN over to VZWINTERNET, and I can't seem to get anything working (calls or data).
I'll continue to toy around with things though.

FoxyDrew said:
Okay so I have T-Mobile Nougat installed on my device, and I've changed my VPN over to VZWINTERNET, and I can't seem to get anything working (calls or data).
I'll continue to toy around with things though.
Click to expand...
Click to collapse
Same here

is there maybe a need to change to verizon csc?

j3ffm1ll said:
is there maybe a need to change to verizon csc?
Click to expand...
Click to collapse
are you meaning swap the pi3 csc to odin vice the csc that came with the firmware. I guess we can try that. worst thing no load, flash back stock.

justinsch03 said:
are you meaning swap the pi3 csc to odin vice the csc that came with the firmware. I guess we can try that. worst thing no load, flash back stock.
Click to expand...
Click to collapse
just a thought I would try it but I am at work and have to have use of my phone while I am here lol

FoxyDrew, radelon from what firmware did you flashed ?

spiderkr said:
FoxyDrew, radelon from what firmware did you flashed ?
Click to expand...
Click to collapse
The T-Mo one you posted. Odin with ap,bl,cp and csc selected.

After toying with tons of things on the Tmo firmware, I tried booting into Odin, and flashing the Verizon pi3 CSC. That gave me a bootloop. I then tried reflashing the entire Tmo Nougat with Odin, but replacing the CSC again with Verizons, same bootloop. So now my phone is being flashed back to the trusty U MM.
I can only assume now that running the Tmo firmware on VZW will require root to make CSC edits. But Verizon will release our own Nougat before we get root.
Now I guess it's just a race between Verizon releasing 7.0, and the G935U getting it.
$50 on Verizon.
Edit: After flashing the G935U firmware again, after the first boot I was greeted with a message saying "your device must update to use new features from your SIM card." And I booted to a weird all blue screen with a big SIM card on it. I've never seen anything like that. I'm not sure if the Tmo firmware messed with stuff, so I'm going to fully flash the G935V firmware, THEN reflash the G935U firmware, just in case the G935T firmware messed something up.

they also did something to disable all package disabler apps even if you go back to MM they dont work. They screwed us goood on this

so @spiderkr were you able to get it working or just going off of other reports?

radelon said:
The T-Mo one you posted. Odin with ap,bl,cp and csc selected.
Click to expand...
Click to collapse
i mean at what firmware where you before you flash t-mo nougat?

spiderkr said:
i mean at what firmware where you before you flash t-mo nougat?
Click to expand...
Click to collapse
Beta 2 Verizon Nougat

Unable to select network
Under "Network Operators" I selected Verizon Wireless, waited 5 minutes, and now got Unable to select network. Then, maybe a minute or so later, it says "Unable to connect. Try again later." Is there a way around this?

jrkruse said:
they also did something to disable all package disabler apps even if you go back to MM they dont work. They screwed us goood on this
Click to expand...
Click to collapse
I noticed this too, thought I was going crazy lol. That was the only think keeping me from rooting, and considering how horrible root is on this phone, I'm going to Verizon tomorrow to get a Pixel.

Im messing with it I got lte can make and receive phone call receive text but cant send

jrkruse said:
Im messing with it I got lte can make and receive phone call receive text but cant send
Click to expand...
Click to collapse
awesome!! getting closer...

jrkruse said:
Im messing with it I got lte can make and receive phone call receive text but cant send
Click to expand...
Click to collapse
How'd you manage to do that? Still can't get anything to work on my end...

VoLTE T-Mobile USA Working on H8324 Xperia XZ2 Compact Dual Stock

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.

Question Help - In need of T-mobile unlock app

Hi.
In short I am asking someone who was the T-mobile firmware if they can extract the T-mobile unlock app. I am hoping I can use the unlock app without the need to reflash my phone to the T-mobile firmware.
Long story.
I thought my wife's phone was unlocked succesfully and flashed the unlocked firmware over the T-mobile firmware. Weeks later come to find out it's not actually unlocked we were just using a MVNO that is on T-mobile antenna... which I should have known. Really want to avoid making my wife setup a bunch of stuff again, even after backing up and restoring so looking for some help.
Is anyone able to extract the unlock app, or have a better way of backing up and restoring without the need for root?
TIA

just make Okey gooogle bro,
Device Unlock 1.2.33 (arm) APK Download by T-Mobile USA - APKMirror
Device Unlock 1.2.33 (arm) APK Download by T-Mobile USA - APKMirror Free and safe Android APK downloads
www.apkmirror.com

malikin said:
just make Okey gooogle bro,
Device Unlock 1.2.33 (arm) APK Download by T-Mobile USA - APKMirror
Device Unlock 1.2.33 (arm) APK Download by T-Mobile USA - APKMirror Free and safe Android APK downloads
www.apkmirror.com
Click to expand...
Click to collapse
Thanks for the response, but installing all the ones I found online say that my device is incompatible.
Which makes sense, the ones online are all ancient.
I.E "Target: Android 7.0"

moku160 said:
Thanks for the response, but installing all the ones I found online say that my device is incompatible.
Which makes sense, the ones online are all ancient.
I.E "Target: Android 7.0"
Click to expand...
Click to collapse
What message are you receiving when you insert Non TMobile or MVNO sim?
AFAIK, you will need TMobile firmware for unlock to work. Newer TMobile phones don't have a dedicated unlock app. It is baked in connection settings.

dadmi said:
What message are you receiving when you insert Non TMobile or MVNO sim?
AFAIK, you will need TMobile firmware for unlock to work. Newer TMobile phones don't have a dedicated unlock app. It is baked in connection settings.
Click to expand...
Click to collapse
Was afraid of that. It asks for an unlock code. Will probably have to just bite the bullet and flash back to the TMobile firmware.
Maybe flashing with Home_CSC will work and still allow me to keep my wifes settings intact.

moku160 said:
Was afraid of that. It asks for an unlock code. Will probably have to just bite the bullet and flash back to the TMobile firmware.
Maybe flashing with Home_CSC will work and still allow me to keep my wifes settings intact.
Click to expand...
Click to collapse
Worth giving a shot with Home_CSC. Also Samsung backup works very well except Samsung Pay/Google Pay which you have to set again.

dadmi said:
Worth giving a shot with Home_CSC. Also Samsung backup works very well except Samsung Pay/Google Pay which you have to set again.
Click to expand...
Click to collapse
Ill probably try it tonight. As far as Samsung backup, did you mean smart switch? All the apps, contacts, photos come over but many apps still require setting up again Regardless thanks for the comments!

New T-Mobile devices don't use the unlock app anymore. Device unlock requests are done through connection settings.

Ended up flashing back to T-mobile firmware using Home_CSC instead of CSC and I was able to successfully unlock as well as keep my wifes settings...
But i tried flashing back to unlocked firmware using Home_CSC and couldn't boot. Said user data was corrupt. I tried 4 times without any difference. Luckily I was able to flash back to T-mobile firmware again with Home_CSC and it worked fine
This may be common knowledge I wasnt aware of but it appears:
Unlocked firmware + Home_CSC -> Carrier Firmware is ok
BUT carrier firmware + Home_CSC -> Unlocked Firmware is not
Thanks to anyone to commented and read.

It's contract there I believe

Question Which version of the March update should I patch and update with?

I bought my now rooted 6A via Aliexpress, and I live in Canada.
Current version is TQ1A.230205.002.
Looking through past updates, this is the first time they've singled out "Canada" for a specific update... Which version should I be patching/flashing, given that my phone came from overseas (but has the NA bands)?
13.0.0 (TQ2A.230305.008.E1, Mar 2023)
OR
13.0.0 (TQ2A.230305.008.F1, Mar 2023, WINDTRE/Canada)

From what I can see, Windtre is a specific carrier. I would go with The standard version for unlocked phones. If that's wrong then the process should abort itself before making any changes

The specific versions seem to be based on carriers. Wind Tre looks like an Italian carrier, so I'd guess the "Canada" applies for use with all Canadian carriers. Or, it may be based on some regulatory difference. Google sucks at transparency. But, the specific versions come and go, so I'd guess they're all about something which didn't get integrated into the mainline code in time, so they had to create a special version.
I would go with the WINDTRE/Canada version. You're rooted, so you could always switch if you have trouble.

azthemansays said:
I bought my now rooted 6A via Aliexpress, and I live in Canada.
Current version is TQ1A.230205.002.
Looking through past updates, this is the first time they've singled out "Canada" for a specific update... Which version should I be patching/flashing, given that my phone came from overseas (but has the NA bands)?
13.0.0 (TQ2A.230305.008.E1, Mar 2023)
OR
13.0.0 (TQ2A.230305.008.F1, Mar 2023, WINDTRE/Canada)
Click to expand...
Click to collapse
Or if it is the wrong one you can just flash right over it with the Canadian one. But I really think that is for a French or Italian Canadian carrier that you don't subscribe to.

motolio said:
From what I can see, Windtre is a specific French Canadian carrier.
Click to expand...
Click to collapse
Really, where'd you find that? I just found links to an Italian carrier. Windtre isn't listed in Wikipedia's list.
motolio said:
Italian Canadian
Click to expand...
Click to collapse
That's a new one.

mike.s said:
The specific versions seem to be based on carriers. Wind Tre looks like an Italian carrier, so I'd guess the "Canada" applies for use with all Canadian carriers. Or, it may be based on some regulatory difference. Google sucks at transparency. But, the specific versions come and go, so I'd guess they're all about something which didn't get integrated into the mainline code in time, so they had to create a special version.
I would go with the WINDTRE/Canada version. You're rooted, so you could always switch if you have trouble.
Click to expand...
Click to collapse
motolio said:
Or if it is the wrong one you can just flash right over it with the Canadian one. But I really think that is for a French or Italian Canadian carrier that you don't subscribe to.
Click to expand...
Click to collapse
Okay I'll patch both of them first, then I'll see what sticks, thanks!
Follow up question: how do you do a nandroid backup?
I went to find TWRP and apparently boot.img is now part of the recovery partition so it won't work?
Can I just boot to TWRP using adb/fastboot from my computer to make the backup?
Just got this phone recently, so I haven't had the need to backup + update until now... Plus the whole "patching the security exploit" thing.

Dude, I would not start with the Windtre one. Sounds like it could just be a striped down/limited version. It looks like that rom might specifically limit access to specific bands that Windtre doesn't allow their customers to access.
I found this on Reddit about the pixel 7:
Google "even limited the band bandwidth on NR, like 20mhz for N3
It isn't a huge problem, unless some operator add/remove bandwidth on a certain NR band
This is the case with WINDTRE (Italy, 222-88): they recently added 20mhz to their N78 spectrum (before it was max 40mhz on some regions, others 20mhz, now every region is 60mhz) and now you can't use their N78 at all
Why?
Because on their carrier policy, WindTre SIMs can use only 40mhz, 20mhz and 40+20mhz on N78 (last case is NR CA, not 60mhz)
It's really great to have a 900€ phone (Pixel 7 Pro) that can't connect to N78 thanks to Google "
Good luck. Let us know how it goes!

mike.s said:
Really, where'd you find that? I just found links to an Italian carrier. Windtre isn't listed in Wikipedia's list.
That's a new one.
Click to expand...
Click to collapse
Lol. Word

azthemansays said:
Okay I'll patch both of them first, then I'll see what sticks, thanks!
Follow up question: how do you do a nandroid backup?
I went to find TWRP and apparently boot.img is now part of the recovery partition so it won't work?
Can I just boot to TWRP using adb/fastboot from my computer to make the backup?
Just got this phone recently, so I haven't had the need to backup + update until now... Plus the whole "patching the security exploit" thing.
Click to expand...
Click to collapse
If you find a good back up process, lemme know. I need a good recovery option, too.
I did find this elaborate process on Reddit: I HAVE NEVER TRIED IT.
https://www.reddit.com/r/GooglePixel/comments/ovlnbj/_/h7akg6l

motolio said:
Good luck. Let us know how it goes!
Click to expand...
Click to collapse
You guys had me worried, and couldn't even get the phone to get the update notification (to check the version of the update).
But when I was looking at downloading the two versions on Google's ROM depository I noticed that you can directly update the phone through Chrome on my desktop???
Man, has tech changed since my last phone (Mi A1 on Oreo)...
It ended up flashing the Global ROM, so the Italian/Canadian one wouldn't have worked.
Gave up on backing up my phone, so I just exported/uploaded the settings for my launcher + AOSP mods + a couple of others then just went for it.
Thanks again for the assistance!

azthemansays said:
I noticed that you can directly update the phone through Chrome on my desktop???
Click to expand...
Click to collapse
Hope does this work? I've never encountered that option

motolio said:
Hope does this work? I've never encountered that option
Click to expand...
Click to collapse
Android flash tool: https://developers.google.com/android/images
Just scroll down to the image you want and click "flash" next to it
It'll give you instructions, as well as help you with the drivers if Chrome can't detect the phone, then will reboot it into bootloader, then recovery, then back to normal boot into an updated phone.
Make sure to check that the drivers for recovery/bootloader modes are already installed by booting into them beforehand... Otherwise you'll have a small panic as I did and have to boot your phone again manually by holding the power + volume down keys for 30ish seconds (until it reboots) due to Chrome not detecting your phone.
I'd also suggest using a back USB port on your mobo rather than plugging it into any of the front USB headers.
*screen shots below are from my phone

azthemansays said:
Android flash tool: https://developers.google.com/android/images
Just scroll down to the image you want and click "flash" next to it
It'll give you instructions, as well as help you with the drivers if Chrome can't detect the phone, then will reboot it into bootloader, then recovery, then back to normal boot into an updated phone.
Make sure to check that the drivers for recovery/bootloader modes are already installed by booting into them beforehand... Otherwise you'll have a small panic as I did and have to boot your phone again manually by holding the power + volume down keys for 30ish seconds (until it reboots) due to Chrome not detecting your phone.
I'd also suggest using a back USB port on your mobo rather than plugging it into any of the front USB headers.
*screen shots below are from my phone
Click to expand...
Click to collapse
Oh wow. Thanks! I had no idea about this. I'll give it a try next time I have time to phone out!
Thanks again

azthemansays said:
It ended up flashing the Global ROM, so the Italian/Canadian one wouldn't have worked.
Click to expand...
Click to collapse
??? The flash tool should install whichever image you choose. I've never tried picking a completely wrong one, but I suspect it does have a simple check that at least you're flashing for the correct platform (e.g. Pixel 6a).
The carrier versions are what gets sent as an OTA update via the particular carrier(s). It's not clear how you determined that the carrier specific one "wouldn't have worked." I suspect either would boot and "work", although the incorrect one may not take full advantage of the carrier's capabilities or may experience minor issues. Google has never provided guidance on exactly what types of differences there are.

mike.s said:
??? The flash tool should install whichever image you choose. I've never tried picking a completely wrong one, but I suspect it does have a simple check that at least you're flashing for the correct platform (e.g. Pixel 6a).
The carrier versions are what gets sent as an OTA update via the particular carrier(s). It's not clear how you determined that the carrier specific one "wouldn't have worked." I suspect either would boot and "work", although the incorrect one may not take full advantage of the carrier's capabilities or may experience minor issues. Google has never provided guidance on exactly what types of differences there are.
Click to expand...
Click to collapse
All I know is that I didn't get a warning, the global ROM's bands are working with my carrier's (Public Mobile - a subsidiary of Telus) after being flashed, and as you've stated Google hasn't been open with the differences... so I'm going to err on the side of caution (and international compatibility) and stick with what works.
I may revisit it if I travel inter-provincially and discover issues with coverage, but the US bands are what are compatible with what's used in Ontario.