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.
Related
I am getting my Sony "U.S" Version just because of its warranty, is there a way i can Enable the fingerprint. Please help
currently all you could do is flash the International firmware. I haven't really looked into anything though personally. I'm not sure how they disabled it, maybe changing a 0 to 1 somewhere but I doubt it.
Yes I got the US version from Amazon and just flashed the CE1 firmware and fingerprint works after flashing that firmware
Sent from my G8142 using Tapatalk
Buy it from the UK. Same warranty. No need to flash anything. Save about $100.00
NO BRAINER!
jaseman said:
Buy it from the UK. Same warranty. No need to flash anything. Save about $100.00
NO BRAINER!
Click to expand...
Click to collapse
It doesn't have US warranty, probably you have to send it back to UK. Personally I don't care about warranties, never had to use for any of my many phones until now partly because don't keep the phone that long. The other advantage buying from Amazon US is ease of return in case you don't like the phone. If you played with it before and 100% sure you like the phone and will definitely keeping it, then yeah better to buy from clove and save the extra $150 or change.
kirdroid said:
Yes I got the US version from Amazon and just flashed the CE1 firmware and fingerprint works after flashing that firmware
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
Can you post a simple guide to do this with some links on where to get all the tools firmware, flashy oil etc... Also I think there are some alternatives for the firmware such as the US and European version any differences between them?
samurayx89 said:
Can you post a simple guide to do this with some links on where to get all the tools firmware, flashy oil etc... Also I think there are some alternatives for the firmware such as the US and European version any differences between them?
Click to expand...
Click to collapse
I used the newflasher tool in the below link. Personally this is my first Xperia device in a long time and haven't used the Xperia flashing tools before.
https://forum.xda-developers.com/showthread.php?t=3619426
1. Make sure you have the right drivers installed. I installed Xperia companion tool since someone mentioned that should install all the drivers. I also installed the flash tool and fastboot drivers from Xperia flash tool since I had issues putting my phone in flash mode. If you are using Windows 10 you have disable verify driver signing in boot before installing the flash tool drivers.
2. Download the firmware of your choice, I chose CE1 (Central Europe) firmware over other Asian firmware.
3. Then follow the instructions in the thread to flash.
Main issue I had was putting my phone in flash mode. But apparently flash mode doesn't have any screen like recovery etc. You just have to turn off your phone then while holding the volume button down connect your phone via USB. That should put in flash mode even though you don't get any screen to say it's in flash mode.
Once I put in flash mode everything went fine by following instructions in the thread.
Thanks,
So when you downloaded the files with XperiFirm and used NewFlasher did you delete any of the files or just drop newflasher into the created directory and flashed everything.
samurayx89 said:
Thanks,
So when you downloaded the files with XperiFirm and used NewFlasher did you delete any of the files or just drop newflasher into the created directory and flashed everything.
Click to expand...
Click to collapse
Just dropped all newflasher files into the created firmware directory and just ran the newflasher application from that directory. It flashed everything in there.
I know the thread says if you want you can remove specific things from the firmware directory if you don't want to flash certain things. But I didn't see any reason to do that and I never care about wiping my device since all my info is backed up in the cloud and takes around 30 minutes to restore and be up and running again. Just to be safe I flashed everything so that it doesn't screw up anything. I haven't used the Xperia flash tools before so kept it simple.
kirdroid said:
Just dropped all newflasher files into the created firmware directory and just ran the newflasher application from that directory. It flashed everything in there.
I know the thread says if you want you can remove specific things from the firmware directory if you don't want to flash certain things. But I didn't see any reason to do that and I never care about wiping my device since all my info is backed up in the cloud and takes around 30 minutes to restore and be up and running again. Just to be safe I flashed everything so that it doesn't screw up anything. I haven't used the Xperia flash tools before so kept it simple.
Click to expand...
Click to collapse
Does Google Assistant work for you on the CE1 firmware? It's not popping up for me at all.
Yadiel2007 said:
Does Google Assistant work for you on the CE1 firmware? It's not popping up for me at all.
Click to expand...
Click to collapse
Yeah working fine no issues here (long press home button to bring up assistant) ... Even ok Google works fine as well when screen is on.
kirdroid said:
Just dropped all newflasher files into the created firmware directory and just ran the newflasher application from that directory. It flashed everything in there.
I know the thread says if you want you can remove specific things from the firmware directory if you don't want to flash certain things. But I didn't see any reason to do that and I never care about wiping my device since all my info is backed up in the cloud and takes around 30 minutes to restore and be up and running again. Just to be safe I flashed everything so that it doesn't screw up anything. I haven't used the Xperia flash tools before so kept it simple.
Click to expand...
Click to collapse
Do you still have Volte working after flashing the CE firmware?
tdgillihan said:
Do you still have Volte working after flashing the CE firmware?
Click to expand...
Click to collapse
Also curious about volte, I bought mine from Best Buy yesterday and it doesn't have Volte on T-Mobile in the us. I'm hoping flashing the CE firmware enables it.
HigherSensation said:
Also curious about volte, I bought mine from Best Buy yesterday and it doesn't have Volte on T-Mobile in the us. I'm hoping flashing the CE firmware enables it.
Click to expand...
Click to collapse
Hmmm, that's weird. My understanding was that it was enabled on the US version but not on the international. Are you sure you don't have it?
tdgillihan said:
Hmmm, that's weird. My understanding was that it was enabled on the US version but not on the international. Are you sure you don't have it?
Click to expand...
Click to collapse
I'm pretty sure it's the US model because the fingerprint sensor is disable.
there is no VOLTE on this phone, no menu options for advanced calling like wifi calling either.
tdgillihan said:
Hmmm, that's weird. My understanding was that it was enabled on the US version but not on the international. Are you sure you don't have it?
Click to expand...
Click to collapse
HigherSensation said:
I'm pretty sure it's the US model because the fingerprint sensor is disable.
Click to expand...
Click to collapse
afuller42 said:
there is no VOLTE on this phone, no menu options for advanced calling like wifi calling either.
Click to expand...
Click to collapse
Sorry, my bad, mixed up my forums. Comments deleted.
afuller42 said:
there is no VOLTE on this phone, no menu options for advanced calling like wifi calling either.
Click to expand...
Click to collapse
Must be an Branding/Software issue i guess.
On the unbranded EU version, both is available.
wifi calling: Settings -> Wireless&Networks -> Wi-Fi Calling
VoLTE: Settings -> Wireless&Networks -> Mobile Networks -> Enable VoLTE
Tuerkay said:
Must be an Branding/Software issue i guess.
On the unbranded EU version, both is available.
wifi calling: Settings -> Wireless&Networks -> Wi-Fi Calling
VoLTE: Settings -> Wireless&Networks -> Mobile Networks -> Enable VoLTE
Click to expand...
Click to collapse
Are you sure it has nothing to do with your service provider?
I bought mine from the UK (not sure if it is the same as the unbranded EU version you mention) and when I look for those same settings they do not exist.
I am in the US running on AT&T as an unlocked go phone customer.
afuller42 said:
there is no VOLTE on this phone, no menu options for advanced calling like wifi calling either.
Click to expand...
Click to collapse
jaseman said:
Are you sure it has nothing to do with your service provider?
I bought mine from the UK (not sure if it is the same as the unbranded EU version you mention) and when I look for those same settings they do not exist.
I am in the US running on AT&T as an unlocked go phone customer.
Click to expand...
Click to collapse
Could be that the settings are not available unless your carrier/plan supports them. Pretty sure anyone slipping a T Mobile sim in has those services.
I've been searching for days now, yet can't find what I'm looking for. I have the S7 Edge International vatient SM-G935F and have recently upgraded it to Oreo on the Superman Rom. I'm loving my phone again, yet I have yet to find a solution to enable WIFi calling and VOLTE for the S7 International on TMB. Can anyone assist? I'm sure there are a ton of other folks in my situation, yet everything I've found only works on Nougat or is only for newer model phones.
I'd greatly appreciate any guidance to get this final piece of the puzzle solved.
Thanks in advance!
Flash Home_CSC for your carrier over top of the ROM, CSC is what controls your carrier specific features like VoWiFi and VoLTE
Edit: Although since you're using T-Mobile, isn't that US based? Make sure you only flash the firmware appropriate to your device. US model S7's use a different SoC so you can't flash it over an international phone
It's the international version that I'm using on a US carrier. There is no firmware from the carrier directly due to the difference in SoC on the phones that were sold in the US.
This being said I was able to use the CSC selection tool with Nougat, yet the tool hasn't been updated for the S7 running Oreo.
My hope is someone has created a compatible tool or flashable fix. I've found several for the s8, yet nothing for my S7.
You could do a full TWRP backup, try the Nougat CSC tool or the S8 one and see how it runs, and if any issues you can restore the backup or dirty flash the ROM
You can try this: https://forum.xda-developers.com/showpost.php?p=69864872&postcount=5484
using this: https://forum.xda-developers.com/s7-edge/development/utility-flashable-csc-selection-30-t3392957
which is a recommended step when doing this: https://forum.xda-developers.com/galaxy-s7/development/rom-s7-rom-v1-0-t3356197
So, it might just work for you.
Edited after re-reading your initial post:
Also, I've not done this yet, but I am possibly about to install the Superman Oreo ROM too (I have the sm-g930f), and you mentioned you find only tools for Nougat. The second link I provided is the 2.5.0 CSC selection tool for MM or Nougat, and no version listed for Oreo, yet that CSC selection 2.5.0 version is linked to from the Superman Oreo developer in one of the steps, for flashing CSC after flashing the ROM......
So, my question to you is: have you tried that CSC selection tool for Nougat already just after flashing Superman Oreo, and it doesn't work? One of my main reasons for going with the Superman ROM is to have the proper CSC installed for my international (exynos) variant on US T-Mobile, and I'm not even gonna start if the CSC won't install.
Thx!
Yes, I've tried the Nougat 2.5.0 version as well as the s8 version, neither of which seem to work for my phone on Oreo.
Beanvee7 said:
You could do a full TWRP backup, try the Nougat CSC tool or the S8 one and see how it runs, and if any issues you can restore the backup or dirty flash the ROM
Click to expand...
Click to collapse
Tried both of the tools already (csc select 2.5.0 for Nougat and the Oreo version for the s8). S8 version says, nope, this is an S7 and won't install, the S7 version installs yet ends up in a boot loop. So, no dice as of yet.
I've asked for info from the dev on his forums with no response as of yet. Crossing my finger that he releases a new version or someone else can work some magic.
sirebral123 said:
Tried both of the tools already (csc select 2.5.0 for Nougat and the Oreo version for the s8). S8 version says, nope, this is an S7 and won't install, the S7 version installs yet ends up in a boot loop. So, no dice as of yet.
I've asked for info from the dev on his forums with no response as of yet. Crossing my finger that he releases a new version or someone else can work some magic.
Click to expand...
Click to collapse
I just installed Superman Oreo last night then installed csc from the Nougat 2.5.0 csc selection tool immediately afterward. I got it all working, including volte. What boot loop issue did you have? How far did it boot and what did you see before the reboot?
gruuvin said:
I just installed Superman Oreo last night then installed csc from the Nougat 2.5.0 csc selection tool immediately afterward. I got it all working, including volte. What boot loop issue did you have? How far did it boot and what did you see before the reboot?
Click to expand...
Click to collapse
After android booted the system said it was rebooting to complete the configuration for new SIM functionality. It then rebooted itself to TWRP. From TWRP I selected boot system and then it would start the same process over. I had no control while the message displayed. I also noted random crashes at the same time while Android was booted.
I cleared cache and tried again with no change. Really happy you got it working, can you detail your progress?
Thanks!
sirebral123 said:
After android booted the system said it was rebooting to complete the configuration for new SIM functionality. It then rebooted itself to TWRP. From TWRP I selected boot system and then it would start the same process over. I had no control while the message displayed. I also noted random crashes at the same time while Android was booted.
I cleared cache and tried again with no change. Really happy you got it working, can you detail your progress?
Thanks!
Click to expand...
Click to collapse
Ya, that's the same issue I had.
I just typed it up in another response on the Superman Rom for g930f thread:
https://forum.xda-developers.com/showpost.php?p=77640954&postcount=13063
basically, when at the point you were at, you could pull the sim card (you won't get the error when you have no sim in the device) and keep on going with the setup, until you have the device rooted (recommend magisk) and then connect to your device and disable the package that's giving you a problem, using the adb shell and "su; pm disable com.sec.android.AutoPreconfig"
I was able to get the phone to stop rebooting with the sim installed by disabling the preconfig service, yet I'm still left with weirdness. I am getting two crashes that appear to be associated with Samsung Messages (SMS program). Copy code and messages are continually crashing.
Also, I am able to see the wifi calling in the pulldown, yet it doesn't appear in the actual configuration menu. Things are still very wonky with the Nougat CSC.
Any ideas?
I was able to get past the sim card issue, yet then experienced several FCs from "Messages", "Floating text" and "Copy text".
I tried clearing cache, a dirty install of Superman, clearing messages data, no dice, same errors. Also, as mentioned the wifi calling still doesn't show up in the other network settings, although volte does show up and the icon for wifi calling shows in the pulldown config, yet I can't open details.
Note, I also saw a note from the developer of CSC Selection that said nougat CSCs had the potential to causes FCs, not sure where I saw it, yet probably on these forums or on his website.
I haven't tried a clean install yet, but that's my last option as it entails a day of work.
Still hoping someone has the answers.
sirebral123 said:
I was able to get the phone to stop rebooting with the sim installed by disabling the preconfig service, yet I'm still left with weirdness. I am getting two crashes that appear to be associated with Samsung Messages (SMS program). Copy code and messages are continually crashing.
Also, I am able to see the wifi calling in the pulldown, yet it doesn't appear in the actual configuration menu. Things are still very wonky with the Nougat CSC.
Any ideas?
Click to expand...
Click to collapse
Not really, except that my approach, when encountering issues like this, is often to start at the beginning and fully work through it again. When I had this issue, I was not satisfied to have let the system boot multiple times, so I actually shut down, uninstalled the sim, reformatted /data, fully wiped, installed SuperStock kernel with the ROM, did not ever let it install bootloader and modem (stayed with what samsung pushed with the initial Oreo update, ERG2), i DID let the aroma installer install the default btu csc, then when rom install completed, I installed the tzo csc, booted once to the spanish "Hola" screen, immediately rebooted to recovery, installed tmb csc, rebooted again, did the initial android wifi and google setup, rebooted, installed magisk, rebooted and adb shell disable that package, shut down, install sim, reboot and went to steps 7,8,9 from here https://forum.xda-developers.com/showpost.php?p=69864872&postcount=5484 I honestly have NO IDEA why that link had me install the brazilian csc right after rom install, boot then install the tmobile US csc... that seems weird, but I did it, and it worked (?) At any rate, since I had fought with it for a few hours prior to that, I kinda knew how I should properly sequence the setup for best chance at success, starting from the beginning. I have a g930f.... is yours a g935f? not sure that would make a difference, but if you have the same hardware, then you must be able to reproduce the successful results.
I should also add that wifi calling is not something that I've actually done... I haven't needed it yet. But I do have the selection in Connections > Mobile Networks > VoLTE calls, and I use LTE Discovery app to show me that my phone connects to LTE band 12 now. I also now have a working "Wi-Fi Calling" toggle in my toggles pulldown menu, and while it is on, I made a phone call while connected to my home wifi. I haven't yet figured out how to verify it's working. I suppose if I really want to test this, I could tin-foil the house so I can't get cell signal, then see if I can make a phone call while I'm on wifi!
---------- Post added at 08:42 PM ---------- Previous post was at 08:05 PM ----------
sirebral123 said:
I was able to get past the sim card issue, yet then experienced several FCs from "Messages", "Floating text" and "Copy text".
I tried clearing cache, a dirty install of Superman, clearing messages data, no dice, same errors. Also, as mentioned the wifi calling still doesn't show up in the other network settings, although volte does show up and the icon for wifi calling shows in the pulldown config, yet I can't open details.
Note, I also saw a note from the developer of CSC Selection that said nougat CSCs had the potential to causes FCs, not sure where I saw it, yet probably on these forums or on his website.
I haven't tried a clean install yet, but that's my last option as it entails a day of work.
Still hoping someone has the answers.
Click to expand...
Click to collapse
What kernel did you install?
Yeah, I dug a little deeper, and I may not have wifi calling working, as it is not something that shows up in Settings, and if there is a toggle, I should be able to find it in settings. .... same as you, I have the wifi calling toggle, and VoLTE in settings, but not wifi calling in settings. weird that my toggle doesn't seem to have an issue turning on and off... I'll need to figure out how to test this.
No force closing though. It all seems quite stable, actually. But, yeah, it takes forever to setup all the apps..... about 50 of em!
Good luck!
Thanks for your diligence, I'll continue to hack away at it as well and perhaps we can put this to rest together. I did find one other CSC that does seem to work until it tries to register the WIFI calling. Perhaps this will help us. I'll attach it in the next message. (Need to post it from my phone).
Here's the TMO version that I was able to install without issues. I think it's Europian, yet it does show VoLTE and WIFI calling enabled. The issue is when it tries to register on the TMB servers (probably pointing to Germany). My hope with posting this is that someone with more skill than I can assist with the setting(s) that need to be changed to have it register on the TMB servers.
https://mega.nz/#!LeAVxQ6T!6WnCmQ0N5kFbGW83AAf_qyLmhM5g-3UNCnS6wIl5boc
sirebral123 said:
Here's the TMO version that I was able to install without issues. I think it's Europian, yet it does show VoLTE and WIFI calling enabled. The issue is when it tries to register on the TMB servers (probably pointing to Germany). My hope with posting this is that someone with more skill than I can assist with the setting(s) that need to be changed to have it register on the TMB servers.
https://mega.nz/#!LeAVxQ6T!6WnCmQ0N5kFbGW83AAf_qyLmhM5g-3UNCnS6wIl5boc
Click to expand...
Click to collapse
I read this morning, the suggestions from the selection tool thread, to install the tekhd csc from here that's for the S8, so I wouldn't take the chance, but since you did, kudos!
I downloaded and opened the package you linked, and I'm looking at the xml to see if there is a european server.... and looking also at the tmb csc from tkkg's package in source here: https://github.com/GrifoDev/CSC/blob/Nougat/aroma/csc/XAA/system/csc/TMB/system/csc/customer.xml
In that customer.xml file there is the closest thing I found to a tmobile url with respect to wifi, which is "wlan.mnc260.mcc310.3gppnetwork.org" and that url is the same url found in tekhd tmb crc
btw, in your csc package there is others.xml, and in there is: "<CscFeature_Setting_SupportWifiCall>TRUE</CscFeature_Setting_SupportWifiCall>"
I am very tempted to add that line in the tmb csc inside Tkkg's 2.5.0 selection tool, and flash it to my phone to see if that exposes the wifi call setting with my setup..... My pessimism tells me that things are never that easy!
Also, Tkkg announced this morning in one of his SupermanRom threads that he will be updating the csc selection tool for Oreo soon.... keeping fingers crossed that will be sooner rather than later.
Edited:
The csc you linked to is T-Mobile US.... check out the customers.xml file <CustomerData> <GeneralInfo> <Country> USA
The csc you linked to is T-Mobile US.... check out the customers.xml file <CustomerData> <GeneralInfo> <Country> USA[/QUOTE]
So.. it seems the one I uploaded is for the s8 as well. It does seem to work until wifi calling enabled, then it fails to register.
sirebral123 said:
The csc you linked to is T-Mobile US.... check out the customers.xml file <CustomerData> <GeneralInfo> <Country> USA
Click to expand...
Click to collapse
So.. it seems the one I uploaded is for the s8 as well. It does seem to work until wifi calling enabled, then it fails to register.[/QUOTE]
Have you had any luck? I've been able to recreate everything so far in this thread and taking some advice from this one: https://forum.xda-developers.com/s7-edge/development/utility-flashable-csc-selection-30-t3392957. WiFi calling is still a no go for TMB.
Nope, nothing as of yet. ?
Tkkg locked that thread as soon as he posted the updated CSCs for Oreo. The tmb csc in that update doesn't work for me at all. Phone just crashes. Nothing tested and no way to discuss what does and doesn't work. 3.0.0 csc tool can not be taken seriously, unfortunately.
I spent quite a bit of time figuring out how to make the VoLTE work on Airtel and Jio in India on a USA edition H8314 phone.
Sony for some reason doesn't bundle all operators VoLTE configuration in all images, not sure why, typically not the case with other high end phones. And they have region specific bundles or OEM customization.
I solved the problem by taking parts of the regular dual sim ZX2 firmware H8296_Customized IN_1314-9934_52.0.A.3.202_R4B, which has the VoLTE configuration for Airtel and Reliance, and flashing it on my phone. VoLTE works! No issues noticed so far (will update if I notice anything).
Here are the steps:
1. Install XperiFirm
2. download the Indian version of firmware for XZ2 dual, in my case H8296_Customized IN_1314-9934_52.0.A.3.202_R4B
3. download and install newflasher
4. From the downloaded and extracted set of files in XperiFirm download directory, copy the following to another directory
oem_other_X-FLASH-CUST-B6B5.sin
oem_X-FLASH-CUST-B6B5.sin
5. Copy the newflasher also to the same directory, now this directory should have 3 files
6. turn off the phone,
8. enter flashmode (vol down + connect USB cable to PC)
9. run the newflasher, in the directory you prepaired in step 4 and 5
10. Unplug from USB after the flashing is done and restart your phone, it should work with VoLTE on airtel as well as Jio. On airtel it may take a few minutes before the calls actually start going on VoLTE but it works perfectly fine.
This doesn't require bootloader unlock so all phone function would remain good. Feel Free to ask questions, the version of firmware on my XZ2C is 52.0.A.3.163 USA generic.
So this works good with Indian and US networks ?
ahzam said:
I spent quite a bit of time figuring out how to make the VoLTE work on Airtel and Jio in India on a USA edition H8314 phone.
Sony for some reason doesn't bundle all operators VoLTE configuration in all images, not sure why, typically not the case with other high end phones. And they have region specific bundles or OEM customization.
I solved the problem by taking parts of the regular dual sim ZX2 firmware H8296_Customized IN_1314-9934_52.0.A.3.202_R4B, which has the VoLTE configuration for Airtel and Reliance, and flashing it on my phone. VoLTE works! No issues noticed so far (will update if I notice anything).
Here are the steps:
1. Install XperiFirm
2. download the Indian version of firmware for XZ2 dual, in my case H8296_Customized IN_1314-9934_52.0.A.3.202_R4B
3. download and install newflasher
4. From the downloaded and extracted set of files in XperiFirm download directory, copy the following to another directory
oem_other_X-FLASH-CUST-B6B5.sin
oem_X-FLASH-CUST-B6B5.sin
5. Copy the newflasher also to the same directory, now this directory should have 3 files
6. turn off the phone,
8. enter flashmode (vol down + connect USB cable to PC)
9. run the newflasher, in the directory you prepaired in step 4 and 5
10. Unplug from USB after the flashing is done and restart your phone, it should work with VoLTE on airtel as well as Jio. On airtel it may take a few minutes before the calls actually start going on VoLTE but it works perfectly fine.
This doesn't require bootloader unlock so all phone function would remain good. Feel Free to ask questions, the version of firmware on my XZ2C is 52.0.A.3.163 USA generic.
Click to expand...
Click to collapse
beastonprowl said:
So this works good with Indian and US networks ?
Click to expand...
Click to collapse
I haven't traveled to USA since, but I do not see why it won't work.
thanks ahzam for sharing this. My XZ2 is on Customized Version CE1 and VoLTE didn't work with o2 Germany. I downloaded the DE firmware with xperifirm and flashed the 2 files you mentioned via newflasher v13. Reboot and everything is working fine now!
Thanks again,
drewster
Hi ahzam,
I have bought H8296 unlocked international version from USA.
I am also not able to use the VoLTE in India on airtel idea or jio.
Will this firmware help me to get the VoLTE.
After doing so, will I be getting future official Sony updates or it will be rooted device and Xperia support will end?
Can you please help?
Regards
Akhilesh
FantasticBeast007 said:
Will this firmware help me to get the VoLTE.
Click to expand...
Click to collapse
Yes, this should work.
FantasticBeast007 said:
After doing so, will I be getting future official Sony updates or it will be rooted device and Xperia support will end?
Click to expand...
Click to collapse
For me updates still work.
Your device will not be rooted after that. So in my opinion you will not loose your warranty.
Greetz
Thank you for confirming
I will try this and keep you posted if this works
Thank you Guys
It worked and now I get VoLTE on both Airtel and Jio.
However for Airtel it takes some extra 10 seconds to get VoLTE.
One problem I have noticed after this. I received an official xperia update but got an error "Could not Install" while installing this update.
Do you know how to resolve this issue?
Regards
Akhilesh
FantasticBeast007 said:
One problem I have noticed after this. I received an official xperia update but got an error "Could not Install" while installing this update.
Do you know how to resolve this issue?
Regards
Akhilesh
Click to expand...
Click to collapse
For me all updates worked so far without any error. I think i've read somewhere, that the update can be done via Sony companion. (But for me companion never worked in any way^^)
ahzam said:
I spent quite a bit of time figuring out how to make the VoLTE work on Airtel and Jio in India on a USA edition H8314 phone.
Sony for some reason doesn't bundle all operators VoLTE configuration in all images, not sure why, typically not the case with other high end phones. And they have region specific bundles or OEM customization.
I solved the problem by taking parts of the regular dual sim ZX2 firmware H8296_Customized IN_1314-9934_52.0.A.3.202_R4B, which has the VoLTE configuration for Airtel and Reliance, and flashing it on my phone. VoLTE works! No issues noticed so far (will update if I notice anything).
Here are the steps:
1. Install XperiFirm
2. download the Indian version of firmware for XZ2 dual, in my case H8296_Customized IN_1314-9934_52.0.A.3.202_R4B
3. download and install newflasher
4. From the downloaded and extracted set of files in XperiFirm download directory, copy the following to another directory
oem_other_X-FLASH-CUST-B6B5.sin
oem_X-FLASH-CUST-B6B5.sin
5. Copy the newflasher also to the same directory, now this directory should have 3 files
6. turn off the phone,
8. enter flashmode (vol down + connect USB cable to PC)
9. run the newflasher, in the directory you prepaired in step 4 and 5
10. Unplug from USB after the flashing is done and restart your phone, it should work with VoLTE on airtel as well as Jio. On airtel it may take a few minutes before the calls actually start going on VoLTE but it works perfectly fine.
This doesn't require bootloader unlock so all phone function would remain good. Feel Free to ask questions, the version of firmware on my XZ2C is 52.0.A.3.163 USA generic.
Click to expand...
Click to collapse
Can we get VoLTE for any region with these configurations? Like EMEA etc.
nos1609 said:
Can we get VoLTE for any region with these configurations? Like EMEA etc.
Click to expand...
Click to collapse
you should be able to get VoLTE for any region by following this process, you need to extract the files from right version of the bundle for that region.
hi, actually I'm using xz2 premium (H8166) which isn't supported by the jio sim and airtel volte so can I try this method? Thanks.
updated : actually, it's working for xz2 premium so no problem in Volte... so rite now Im using airtel and jio both working fine... but mobile restarts for network optimization while changing mobile data from sim1 to sim2 or sim2 to sim1. Anyways thanks Alot for this awesome tip man.. I really felt bad for my xz2 premium now I'm really happy. You saved my money. Thanks again.
drewsterAndi said:
For me all updates worked so far without any error. I think i've read somewhere, that the update can be done via Sony companion. (But for me companion never worked in any way^^)
Click to expand...
Click to collapse
It also did not worked via xperia companion.
However I ran software repair using xperia companion and it worked, Now I have Volte + All the Sony Security updates
---------- Post added at 03:48 AM ---------- Previous post was at 03:44 AM ----------
ganesh_84s said:
hi, actually I'm using xz2 premium (H8166) which isn't supported by the jio sim and airtel volte so can I try this method? Thanks.
updated : actually, it's working for xz2 premium so no problem in Volte... so rite now Im using airtel and jio both working fine... but mobile restarts for network optimization while changing mobile data from sim1 to sim2 or sim2 to sim1. Anyways thanks Alot for this awesome tip man.. I really felt bad for my xz2 premium now I'm really happy. You saved my money. Thanks again.
Click to expand...
Click to collapse
Yes the restarting is known issue and Sony does is intentionally. I have XZ2 and planning to buy XZ2 Premium also in coming months.
ganesh_84s said:
hi, actually I'm using xz2 premium (H8166) which isn't supported by the jio sim and airtel volte so can I try this method? Thanks.
updated : actually, it's working for xz2 premium so no problem in Volte... so rite now Im using airtel and jio both working fine... but mobile restarts for network optimization while changing mobile data from sim1 to sim2 or sim2 to sim1. Anyways thanks Alot for this awesome tip man.. I really felt bad for my xz2 premium now I'm really happy. You saved my money. Thanks again.
Click to expand...
Click to collapse
First of all, I would like to say Big thanks who share this Procedure, Now I am able to use Volte Functionality
Now I have the same problem while changing sim1 to sim2 to and vice versa but before did volte procedure it was working fine in both sim, so as per my opinion this problem related somewhere Volte functional
I bought this Cell from the Middle East, So in Middle east it was working fine while changing Sim1 & Sim2 Procedure and even in India it was working
So if someone does R&D than might be it is a curable issue, I don't know why Sony did a big mistake nowadays even Oops, Vivo, all Chinese implements successfully these things, even sony dosnt implement Auto Hide status bar in Compact Series Cell
sunnymodh said:
First of all, I would like to say Big thanks who share this Procedure, Now I am able to use Volte Functionality
Now I have the same problem while changing sim1 to sim2 to and vice versa but before did volte procedure it was working fine in both sim, so as per my opinion this problem related somewhere Volte functional
I bought this Cell from the Middle East, So in Middle east it was working fine while changing Sim1 & Sim2 Procedure and even in India it was working
So if someone does R&D than might be it is a curable issue, I don't know why Sony did a big mistake nowadays even Oops, Vivo, all Chinese implements successfully these things, even sony dosnt implement Auto Hide status bar in Compact Series Cell
Click to expand...
Click to collapse
yes, same point before volte its working fine but now restarting issue and I can't update to latest security update too... but I think it's not big issue.. let me flash it anyway restart issue is seriously curable.
sunnymodh said:
First of all, I would like to say Big thanks who share this Procedure, Now I am able to use Volte Functionality
Now I have the same problem while changing sim1 to sim2 to and vice versa but before did volte procedure it was working fine in both sim, so as per my opinion this problem related somewhere Volte functional
I bought this Cell from the Middle East, So in Middle east it was working fine while changing Sim1 & Sim2 Procedure and even in India it was working
So if someone does R&D than might be it is a curable issue, I don't know why Sony did a big mistake nowadays even Oops, Vivo, all Chinese implements successfully these things, even sony doesn't implement Auto Hide status bar in Compact Series Cell
Click to expand...
Click to collapse
Today I discovered 3 more problems
1)After Install Volte Firmware, Because in India no Official launched XZ2C , after install we can not get Firmware Update
2)If you Switch Mobile data between two sims, Cell will restart automatically
3)In Setting->Display you can not get Super Vivid Mode or Professional Mode for better color reproduction
So if anyone tells me XZ2C officially launched which country with Volte Function, if we get an answer than we can solve all the issue
Fact. reset
sunnymodh said:
Today I discovered 3 more problems
1)After Install Volte Firmware, Because in India no Official launched XZ2C , after install we can not get Firmware Update
2)If you Switch Mobile data between two sims, Cell will restart automatically
3)In Setting->Display you can not get Super Vivid Mode or Professional Mode for better color reproduction
To get back this, just factory re-set and will get this options. Anyway It is not working any VoLTE (it's just showing the LTE symbol and option in seeting, in reality your call is routed on 3g/2g. ) you can verify this by selecting 4g only and try calling.
So if anyone tells me XZ2C officially launched which country with Volte Function, if we get an answer than we can solve all the issue
Click to expand...
Click to collapse
>>> 1)After Install Volte Firmware, Because in India no Official launched XZ2C , after install we can not get Firmware Update
How did you find this? As far as I see there is no new firmware came in this recent times. Correct me if I am wrong.
>>>3)In Setting->Display you can not get Super Vivid Mode or Professional Mode for better color reproduction
To get back this, just factory re-set and will get this options. Anyway It is not working on any VoLTE (it's just showing the LTE symbol and option in settings, in reality your call is routed on 3g/2g. ) you can verify this by selecting 4g only and try calling.
tvk73 said:
>>> 1)After Install Volte Firmware, Because in India no Official launched XZ2C , after install we can not get Firmware Update
How did you find this? As far as I see there is no new firmware came in this recent times. Correct me if I am wrong.
>>>3)In Setting->Display you can not get Super Vivid Mode or Professional Mode for better color reproduction
To get back this, just factory re-set and will get this options. Anyway It is not working on any VoLTE (it's just showing the LTE symbol and option in settings, in reality your call is routed on 3g/2g. ) you can verify this by selecting 4g only and try calling.
Click to expand...
Click to collapse
For Latest Software Update Just Use Software Xperifirm, you will get all country latest Software Info and also you can download
Germany, India, Russia you will get Volte Services, Right now I am using Volte Function in Sony XZ2C
FantasticBeast007 said:
It also did not worked via xperia companion.
However I ran software repair using xperia companion and it worked, Now I have Volte + All the Sony Security updates
---------- Post added at 03:48 AM ---------- Previous post was at 03:44 AM ----------
Yes the restarting is known issue and Sony does is intentionally. I have XZ2 and planning to buy XZ2 Premium also in coming months.
Click to expand...
Click to collapse
Can you tell me which Firmware you are using, because I am not able to get any OTA Update
https://xpericheck.com/device/H8296
Current build is 52.0.A.11.3
I Present The Galaxy A71_5G Guide for Flashing Unlocked Firmware.
Here are some useful reminders:
All download links are at the bottom of this post.
Make sure you follow the "Prerequisites For Anything You decide To Do In This Guide" section.
Don't copy quotation marks, unless I tell you to in this guide.
You will need a Windows computer in order to utilize the software provided.
This is an A71_5G guide, not an A71_5GUW guide.
WARNING: Anything you do in this guide will erase your phone completely. It's recommended that you back up before you do anything and that you remove your google account from your phone (so you don't have to go through FRP).
Disclaimer:
I am NOT responsible for any damage done to your device if you decide to use this guide.
Prerequisites for anything you decide to do in this guide (Required):
Standard Odin
Samsung Drivers
Steps:
1) Uninstall Samsung Switch and/or Samsung Kies, if present on your computer. This helps removes any conflicts with Odin.
2) Extract the Samsung Driver zip and the Odin zip to somewhere safe on your computer.
3) Double click on the extracted "SAMSUNG_USB_Driver_for_Mobile_Phones" executable (SAMSUNG_USB_Driver_for_Mobile_Phones.exe) and complete the installation wizard.
3) Navigate to your extracted Odin folder and double click on the Odin3 v3.14.1_3B_PatcheD.exe.
All About Bootloaders (Required Reading):
As Wikipedia puts it, “A boot loader is a computer program that loads an operating system or some other system software for the computer after completion of the power-on self-tests.” In other words, a bootloader is what loads you operating system. In most Samsung phones (including the S8 and S8+), there’s an e-fuse that prevents downgrading of the bootloader. This means any firmware or firmware update containing a lower Bootloader version than the one you have, will FAIL to be applied. There is really no way to circumvent this.
I’ll be explaining how to properly identify your current Bootloader version.
How to identify Bootloader version:
Steps:
1) Open “Settings” on your phone.
2) Scroll down to “About Phone”.
3a) If you are on a standard, carrier firmware, under “Baseband version” you should see something similar to this: “G950UXXXXXXXX”.
3b) If you are on an unlocked firmware, under “Baseband version” you should see something similar to this: “G950U1XXXXXXXX”.
4) No matter which firmware you're on, the fourth “X” would be either a “1” or a “2”, which means you will have either Bootloader version 1 or Bootloader version 2, respectively.
Note: As stated in the last section attempting to flash firmware that contains Bootloader v1 onto a phone that already has Bootloader v2, will fail. You can update a phone on Bootloader v1 to a firmware that has Bootloader v2, however.
Flashing Unlocked Firmware:
NOTE: The unlocked firmware does NOT unlock your phone for use on other carriers, it only removes bloatware. Some carrier specific features, such as Wi-Fi Calling and VOLTE will not work with the Unlocked Firmware.
Prerequisites: What's listed in the "Prerequisites for anything you decide to do in this guide" section
Odin3 v3.14.1_3B_PatcheD.exe.zip
Unlocked Firmware from site listed below.
Steps:
1) Extract the Odin3 v3.14.1_3B_PatcheD.exe and the Unlocked Firmware you downloaded from below.
2) Turn off your A71_5G.
3) Once off, hold the Power button while holding the Volume Down button, and the Volume Up button until you feel a vibration then let go of the power button.
4) Press the Volume Up key to enter Download Mode.
5) On your PC, navigate to your extracted Odin3 v3.14.1_3B_PatcheD.exe folder.
6) Double click on the "Odin3 v3.14.1_3B_PatcheD.exe" executable.
7) Connect your phone to your PC with your USB cable.
8) You should see Odin3 v3.14.1_3B_PatcheD output "Added!!" in the "Log" tab and underneath the "ID:COM" section, you should see an empty box turn blue.
9) Now it's time to add your firmware files that were extracted earlier. Individually add an appropriate firmware file for each box on the right. The "BL" box will require a firmware file that starts with "BL", the "AP" box will require a firmware file that starts with "AP", the "CP" box will require a firmware file that starts with "CP", and the "CSC" box will require a firmware file that starts with "CSC" (DO NOT USE THE "HOME_CSC" file for the "CSC" box).
10) Go to the "Options" tab and make sure that only the "Auto Reboot" and "F. Reset Time" checkboxes are ticked.
11) Go back to the "Log" tab.
12) Click the "Start" button on bottom right.
13) Sit back and relax for a while. Odin will output what is being flashed in the "Log" and on a box in the top left.
14) The box in the top left will become green and in black letters say "PASS" once the flash was successful.
15) Once the flash finished, disconnect your phone from your computer.
16) Your phone will do an erase at this point, so don't mess with your phone until you reach the setup screen.
17) Continue with the setup on your phone and enjoy!
DOWNLOADS:
Standard Odin/Patched Odin: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Samsung Drivers: http://developer.samsung.com/galaxy/...er-for-windows
Google Platform-Tools (ADB): https://developer.android.com/studio/releases/platform-tools
Unlocked Firmware (Bootloader v1): https://samfw.com/firmware/SM-A716U1/XAA
CREDITS
Credit goes to each respective site/developer for the tools required to complete this.
If you would like to be added to the credits and are one of the developers or owners of the tools used please feel free to Private Messege Me!!!
This Will Be Updated To The Latest Firmware When The U1 Varient Gets Updates
Do you know where i can find the carrier firmware ??? I'm looking for the AT&T one ..... Thank you
cubano2031 said:
Do you know where i can find the carrier firmware ??? I'm looking for the AT&T one ..... Thank you
Click to expand...
Click to collapse
you should be able to find it using sammobile.com or frija https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
C.tig45 said:
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
Click to expand...
Click to collapse
Does 5G still work for you? I had read somewhere that it wouldn't function if you didn't have the T-mobile firmware.
C.tig45 said:
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
Click to expand...
Click to collapse
Original XAA user here...we're still on the June security patch which apparently does not support Chat in Samsung's message app (though does still work in Google's). Looks like TMobile is one of the carriers that actually cooperates with Samsung Messages which makes me think switching to the unlocked firmware (at least the current version) will break Chat. I actually considered flashing from XAA to TMB just to get this feature but I'm on Verizon and I figure the basebands won't match up.
I read (down a rabbit hole) somewhere that the July security patch enables support for Chat. The June update came out about a week before July, so here's hoping it won't be much longer till there's a July update for XAA
andrewNY said:
Does 5G still work for you? I had read somewhere that it wouldn't function if you didn't have the T-mobile firmware.
Click to expand...
Click to collapse
5G works just fine. pretty much everything works minus the chat features in samsung messages.
---------- Post added at 11:03 PM ---------- Previous post was at 10:49 PM ----------
SmileyMorgue said:
Original XAA user here...we're still on the June security patch which apparently does not support Chat in Samsung's message app (though does still work in Google's). Looks like TMobile is one of the carriers that actually cooperates with Samsung Messages which makes me think switching to the unlocked firmware (at least the current version) will break Chat. I actually considered flashing from XAA to TMB just to get this feature but I'm on Verizon and I figure the basebands won't match up.
I read (down a rabbit hole) somewhere that the July security patch enables support for Chat. The June update came out about a week before July, so here's hoping it won't be much longer till there's a July update for XAA
Click to expand...
Click to collapse
That's great to hear! I look forward to the patch. Yes, from the digging I did, chat features were not included in the XAA version, but they were working when I was using TMB before switching.
Update to ATH3 Available on phone still a U1 Bootloader.
For those that wish to download full firmware here is the link to it https://samfw.com/firmware/SM-A716U1/XAA/A716U1UEU1ATH3
allenjthomsen said:
Update to ATH3 Available on phone still a U1 Bootloader.
Click to expand...
Click to collapse
Wow, build date was only 2 weeks prior to release. Recently came from a Moto Z4 where we were lucky to have 6 month old security updates.
Unfortunately still can't get the chat feature working; maybe it'll take some time to register the update.
C.tig45 said:
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
Click to expand...
Click to collapse
Can you still access "network unlock" (device sim unlock) with the "unlocked firmware"?
This is my only concern as I haven't sim unlock the phone yet and these T-Mobile phones requires that app to unlock the sim.
whatsitsnamenow said:
Can you still access "network unlock" (device sim unlock) with the "unlocked firmware"?
This is my only concern as I haven't sim unlock the phone yet and these T-Mobile phones requires that app to unlock the sim.
Click to expand...
Click to collapse
If its like previous Samsung phones, you'll need to be on the carrier specific firmware to run the unlock. Once unlocked you can flash back to the unbranded/unlocked firmware.
Anyone tired these firmwares with AT&T
so there is no unlocked version firmware for bootloader V2 right now?
Is anyone else able to access the firmware file on the link? It mentions something about the download under construction.
If I unlock the bootloader, can I Edit the Access Points or APN Settings ?
No unlock needed
foamhead said:
If I unlock the bootloader, can I Edit the Access Points or APN Settings ?
Click to expand...
Click to collapse
You don't need to unlock bootloader, you will not be able to delete the default but you can add another apn. I (on att) added nxtgen apn to get faster cell speeds.
Rwmega said:
You don't need to unlock bootloader, you will not be able to delete the default but you can add another apn. I (on att) added nxtgen apn to get faster cell speeds.
Click to expand...
Click to collapse
Thanks for the reply. I added another APN. Your right cant delete the defaults ones. Im with sprint was trying to do the ,dun to get my hotspot to work. I have it on 3 other phones.
I have a Sprint version.
If I flash the T-Mobile software will it open up all of the T mobile bands?
It could already have them, but have not been able to find specific s on the bands on the sprint version of the phone to see.
Phone looks to be manufactured before the merger?
whatsitsnamenow said:
Can you still access "network unlock" (device sim unlock) with the "unlocked firmware"?
This is my only concern as I haven't sim unlock the phone yet and these T-Mobile phones requires that app to unlock the sim.
Click to expand...
Click to collapse
I haven't sim unlocked the phone yet since it's not paid off so couldn't tell u if I can still access that feature.
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.