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.
Related
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...
I have the SM-G930UP baseband version G930PVPS4BQE1
I am preparing to flash the universal firmware, but with the T-Mobile modem. The goal is a phone with the U firmware and the T-Mobile modem.
Download and install Samsung USB drivers: http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Odin utility: https://odindownload.com/SamsungOdin/
Latest SM-G930U firmware files for “USA (XAS)”:
G930UUEU4BRD1_G930OUYM4BRD1_XAS
All U variants have the same baseband etc. numbers , so I assume it doesn't matter which one I use.
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/
Latest T-Mobile SM-G930T firmware files:
G930TUVS4BRC1_G930TTMB4BRC1_TMB https://www.sammobile.com/firmwares/galaxy-s7/SM-G930T/
The plan is to back up all data first, extract the all the files (Odin, drivers, and both U and T archives). Install the Samsung USB drivers.
Next steps:
Connect phone to PC.
Shut down phone: Hold Home and Volume-Down buttons while pressing the power button. Press Volume-Up when prompted to place phone in download mode (whatever it’s called).
Open Odin. Wait for Com connected prompt.
Click BL button. Select the SM-G930U BL file.
Click AP button. Select the SM-G930U AP file.
Click CP button. Select the SM-G930T CP file.
Click CSC button. Select the SM-G930U CSC (NOT HOME_CSC) file to wipe and factory reset the phone.
Click Start and wait for Odin to say “Complete.”
Any feedback? Suggestions? Anything I missed?
what baseband are you currently on?
why would you want T-mobile modem? anything wrong with U-version?
turbozapekanka said:
why would you want T-mobile modem? anything wrong with U-version?
Click to expand...
Click to collapse
In some of the reading I have done it appears advantageous to have the carrier modem of the service provider you use; I'm assuming because the carriers tweak the modem for use with their particular infrastructure.
I don't know if that's true, but I have seen a number of posts to that effect. It sounds logical and I figure it can't hurt as long as it works.
InsanePostman said:
what baseband are you currently on?
Click to expand...
Click to collapse
Mr. _Happy said:
I have the SM-G930P baseband version G930PVPS4BQE1
Click to expand...
Click to collapse
Software version is the same. G930PVPS4BQE1 it's from May 2017.
Mr._Happy said:
In some of the reading I have done it appears advantageous to have the carrier modem of the service provider you use; I'm assuming because the carriers tweak the modem for use with their particular infrastructure.
I don't know if that's true, but I have seen a number of posts to that effect. It sounds logical and I figure it can't hurt as long as it works.
Click to expand...
Click to collapse
I doubt it.
I've been using U-version (converted from SM-G930P) on T-mobile for a year and found no issues whatsoever.
I was reading the opposite, something like U-version has more LTE bands unlocked (which makes sense as it should work with all carriers)
Also someone here claimed it has extra bands for Europe. like band 7, 20
turbozapekanka said:
I doubt it.
I've been using U-version (converted from SM-G930P) on T-mobile for a year and found no issues whatsoever.
I was reading the opposite, something like U-version has more LTE bands unlocked (which makes sense as it should work with all carriers)
Also someone here claimed it has extra bands for Europe. like band 7, 20
Click to expand...
Click to collapse
Interesting. That seems logical too.
Unfortunately I may not be flashing anything as every time I have downloaded firmware from SAMOBILE and extracted it I have got an error message that the AP portion has a problem. If I "retry" it gives me the same error. If I "skip" it unpacks everything except the AP file. I have tried several times with multiple downloads. Each one took the full two hours to download, so it's been a lengthy process with no results.
When you flashed the G930U which variant did you use?
Mr._Happy said:
Interesting. That seems logical too.
Unfortunately I may not be flashing anything as every time I have downloaded firmware from SAMOBILE and extracted it I have got an error message that the AP portion has a problem. If I "retry" it gives me the same error. If I "skip" it unpacks everything except the AP file. I have tried several times with multiple downloads. Each one took the full two hours to download, so it's been a lengthy process with no results.
When you flashed the G930U which variant did you use?
Click to expand...
Click to collapse
I flashed version G930UUEU4APL2 with odin 3.12.3
It was back in January 2017. Note the number 4 in the version. This indicates bootloader version.
I believe you can no longer flash this version if your current version has 5 (or any greater number) in place of 4 because you're not allowed to downgrade the bootloader version.
Sprint is known to bump the bootloader version from 4 to 5 for (supposedly) blocking this type of conversions of their branded phones.
turbozapekanka said:
I flashed version G930UUEU4APL2 with odin 3.12.3
It was back in January 2017. Note the number 4 in the version. This indicates bootloader version.
I believe you can no longer flash this version if your current version has 5 (or any greater number) in place of 4 because you're not allowed to downgrade the bootloader version.
Sprint is known to bump the bootloader version from 4 to 5 for (supposedly) blocking this type of conversions of their branded phones.
Click to expand...
Click to collapse
Mr._Happy said:
I have the SM-G930P baseband version G930PVPS4BQE1
Click to expand...
Click to collapse
Sprint is currently on bootloader 6, actually. Crappy obstructionist commercialism specifically to block people converting.
I have been denying and rejecting the software updates since May of 2017 which is when I got that software version, so your G930UUEU4APL2 firmware from January would not work on this phone as my Sprint firmware is more recent.
I should be able to flash the most recent version of G930U, however. I just can't seem to download one that will extract the AP portion. It's really frustrating.
Try this https://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930uueu4apl2-sm-g930u-t3535230
You should be able to flash any firmware as long as the bootloader version is the same
For newer firmwares you may need to use the latest Odin version (3.13.x)
---------- Post added at 12:15 PM ---------- Previous post was at 12:07 PM ----------
I wonder why did you choose XAS version.
I also remember back in time I downloaded two versions of U-firmware (SPR and XAA) and compared the files they appeared identical.
turbozapekanka said:
I doubt it.
I've been using U-version (converted from SM-G930P) on T-mobile for a year and found no issues whatsoever.
I was reading the opposite, something like U-version has more LTE bands unlocked (which makes sense as it should work with all carriers)
Also someone here claimed it has extra bands for Europe. like band 7, 20
Click to expand...
Click to collapse
What ROM have you been running?
Looks like slim pickins for the snapdragon chipset.
I assume all Exynos ROMs would obviously not work .
I have a SM-G930VL that I flash the G930U firmware . Much better
Stock
turbozapekanka said:
You should be able to flash any firmware as long as the bootloader version is the same
Click to expand...
Click to collapse
This is what I was saying. The last Sprint update I did on the phone was May 2017. I have been dismissing the update nag since then. Which means I could flash any G930U firmware with a date later than May 2017 with the same bootloader number.
Sprint has been trying to block this: their bootloader number is currently on 6, all the other carriers are on 4.
turbozapekanka said:
For newer firmwares you may need to use the latest Odin version (3.13.x)
Click to expand...
Click to collapse
Yep. The link I used to download the latest version was in the first post of this thread. 3.13 worked just fine.
The problems I was having had to do with the my computer, but I solved them and was able to to flash the latest version of G930U.
The phone is snappy and without the annoying lag.
Call quality improved immediately. With the Sprint firmware on the T-Mobile network there was a glitch with using the voicemail icon on the dial screen - it would fail to call the voicemail and give an incomplete call error; the workaround was to call myself from contacts and enter my pin to get to my voicemail. Now the voicemail icon on the dialer takes me to voicemail without a hitch. When calling it doesn't have a 15 - 20 second wait before ringing the number (the top left of the status bar would read "Attempting"). Internet reception is also better especially in the NYC subway.
Also as soon as my phone went from Sprint to T-Mobile I could no longer send or receive pictures via text. Apparently Sprint firmware wasn't interested in sending MMS messages anymore, but with the U firmware they work just fine and regular texts go through more quickly as well.
So far battery life is about the same as far as I can tell, maybe a marginal improvement. Nothing to call home about.
But mostly I seem to get the overall desired reception improvement: it stopped dropping calls, and the call quality is solid and the undersea world that had been happening with the Sprint firmware is gone.
Also the fingerprint scanner is working better.
It's much improved.
I REALLY like how it seemlessly goes from voice on network to voice on WiFi.
Question: will this get OTA updates? Is it fantasy to think the G930U will get Oreo?
I am interested in testing the various towers, most frequent LTE bands, signal strength, and handset radios. Is there a thread for that or any apps you know of?
Mr._Happy said:
Question: will this get OTA updates? Is it fantasy to think the G930U will get Oreo?
Click to expand...
Click to collapse
Yes it will get OTA updates including Oreo. U-version lags behind branded versions in this regard though.
i'm just got the oreo update - installing right now (us cellular)
i have tmobile g930t
if i shift to U , will volte work?
because i am unable to use volte in india now
Hey guys so I am brand-new to all this but need to convert my g930p to g930u. I just want to clear this up: because my software version is Q930PVPU6CRE7, I won't be able to flash the version OP used but must find a version with a 6 in it?
I'm in the same boat with my wife's phone. Limited bands available meaning it's on 3G more often than not, and MMS won't work if connected to WiFi. Not to mention the sprint junkware... is there any way to change from G930P to a G930U firmware if the phone is currently on bootloader version 6? I don't mind rooting...
I flashed G930U on G930P but network still not working. It shows unknown network and Radio Off. Mobile can read SIM menu and Contacts but no signal. Any help please?
EDIT: Now I know that changing ROM or rooting does not network unlock.
Mr._Happy said:
I have the SM-G930UP baseband version G930PVPS4BQE1
I am preparing to flash the universal firmware, but with the T-Mobile modem. The goal is a phone with the U firmware and the T-Mobile modem.
Download and install Samsung USB drivers: http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Odin utility: https://odindownload.com/SamsungOdin/
Latest SM-G930U firmware files for “USA (XAS)”:
G930UUEU4BRD1_G930OUYM4BRD1_XAS
All U variants have the same baseband etc. numbers , so I assume it doesn't matter which one I use.
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/
Latest T-Mobile SM-G930T firmware files:
G930TUVS4BRC1_G930TTMB4BRC1_TMB https://www.sammobile.com/firmwares/galaxy-s7/SM-G930T/
The plan is to back up all data first, extract the all the files (Odin, drivers, and both U and T archives). Install the Samsung USB drivers.
Next steps:
Connect phone to PC.
Shut down phone: Hold Home and Volume-Down buttons while pressing the power button. Press Volume-Up when prompted to place phone in download mode (whatever it’s called).
Open Odin. Wait for Com connected prompt.
Click BL button. Select the SM-G930U BL file.
Click AP button. Select the SM-G930U AP file.
Click CP button. Select the SM-G930T CP file.
Click CSC button. Select the SM-G930U CSC (NOT HOME_CSC) file to wipe and factory reset the phone.
Click Start and wait for Odin to say “Complete.”
Any feedback? Suggestions? Anything I missed?
Click to expand...
Click to collapse
if i try this method to convert smg930u to smg930f will it work cuz meh need root ?
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.
Let's Get Started by saying: I'm not resoponsible for brick, loss or any damage to your phone. So backup!
Pre Requirements:
a. A Windows PC with internet connection.
b. Odin Patched Here
c. HOME CSC file of Indian / Thailand / Vietnam Region. You can get firmware of your phone from samfw.com or any other website.
Make sure that the bootloader version on your phone and the one you download are same. For example, A515FXXU4CTJ1 has bootloader version 4 (that's fifth digit from the right). So you have to download a firmware which has same bootloader version.
P.S. We don't need full firmware, Only the file name beginning by "HOME_CSC" is needed.
Working:
1. Eject the SIM Card(s)
2. Go to Settings -> Apps -> Calendar -> Storage -> Clear Data.
3. Put your phone into download mode.
4. Run the Odin....exe (downloaded in step b) as administrator
5. Click CSC and select the HOME_CSC file obtained from step c in Pre-Req.
6. Click "Start".
7. When phone reboots, Repeat step 2.
All done. You can insert SIM Card(s) and use Call Recording.
Notes:
You'll be ondifferent region's CSC after this.
Phone will not factory reset and you won't lose any data after this.
You might not be able to get system updates after this. In order to get them you'd have to flash your region's CSC, then update, then flash custom CSC again.
Tested working on:
Samsung A51 (Android 10)
Samsung A50 (Android 10)
Samsung M21 (Android 11)
You tell
zubair1836 said:
Let's Get Started by saying: I'm not resoponsible for brick, loss or any damage to your phone. So backup!
Click to expand...
Click to collapse
Hi I tried your message but I got an error on my phone along the lines of : secure check fail cache (1). I tried with the odin version you linked and I was thinking about trying a version v3.14 patched that I found here on XDA. Any ideas?
My phone is fine it does seem to restart to a thing with the cyan download background saying "An error has occured..." but I can restart and then hit volume key saying 'reset phone' which just boots the phone normally.
n4noAbyss said:
Hi I tried your message but I got an error on my phone along the lines of : secure check fail cache (1). I tried with the odin version you linked and a version v3.14 patched that I found here on XDA. Any ideas?
My phone is fine it does seem to restart to a thing with the cyan download background saying "An error has occured..." but I can restart and then hit volume key saying 'reset phone' which just boots the phone normally.
Click to expand...
Click to collapse
This happens when you use a non Patched odin. Make sure you're using the one from link in OP. BTW, which phone is it?
zubair1836 said:
This happens when you use a non Patched odin. Make sure you're using the one from link in OP. BTW, which phone is it?
Click to expand...
Click to collapse
It's G991U1, with 1ATLI so I downloaded 1AUB8 (THL) to try to flash the HOME_CSC, I'm 100% sure I tried with the odin you linked (also your one has same CRC SHA-1 as the the one linked in the XDA thread). Maybe I need to try with the updated patcheD odin (v3.14.1_3B) I didn't do that yet.
n4noAbyss said:
It's G991U1, with 1ATLI so I downloaded 1AUB8 (THL) to try to flash the HOME_CSC, I'm 100% sure I tried with the odin you linked (also your one has same CRC SHA-1 as the the one linked in the XDA thread). Maybe I need to try with the updated patcheD odin (v3.14.1_3B) I didn't do that yet.
Click to expand...
Click to collapse
I believe everything's right then. Can't identify the issue though.
I guess, trying updated version might help.
Good luck!
If problem persists after trying updated version. Please share screen when phone is in download mode.
I had kept this thread in my bookmarks since I was buying the A52 4G on Amazon.ca and absolutely wanted Call Recordings (officially we shouldn't be able to get the A52 4G in Canada, only the 5G version is officially here, so it's an import).
But as luck would have it, it's the SM-A525M and already has Call Recording enabled in it. So that saves me some trouble. But thanks for this guide! I may not have needed it in the end, but would've totally relied on it otherwise.
If I'm understanding this right, my firmware is A525MUBS1AUD1. Brazil's ? It's Android so it has every languages built-in regardless and there's no carrier specific apps in it either, so that's great.
tried on A52 4G all flashed fine
but the csc did not changed and no call recorder
tridi001 said:
tried on A52 4G all flashed fine
but the csc did not changed and no call recorder
Click to expand...
Click to collapse
Well, That's unlucky then; it's unavailable on certain devices.
(WIP, files are currently processing and uploading)
For those who aren't already aware, F711U is the model number of all of the US carrier versions of the Z Flip3. The F711U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via the various firmware download tools posted here on XDA like SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I have access to an internal Samsung firmware download tool that usually gets new versions before they hit the public firmware download tools, so that's where my files come from.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=327752
U1 firmware: https://www.androidfilehost.com/?w=files&flid=327753
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- it's quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single flagship model, so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit the firmware download tools.
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T (and Cricket, if they get this model). I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
DSH = Dish Network
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via firmware download tools, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
nwb_sam said:
Flashed a physical T-Mobile F711U to a F711U1 XAA firmware using Odin(Can't stand the bright pink boot up animations).
Flash worked perfectly. But, when I tried to test doing an update from Google settings it failed every time with "Registration Failed". I flashed the device back to the T-Mobile F711U firmware and was able to update without issue.
Not sure if you ran into this issue, but it's worth noting you might not be able to update the phone if the carriers are checking the Firmware.
Edit: Also forgot to mention, had to use the patched Odin due to the Firmware Model mismatch. Phone does work properly though.
Click to expand...
Click to collapse
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
iBowToAndroid said:
What do you mean by "doing an update from Google settings"?
What type of update? What "Google settings" exactly?
Click to expand...
Click to collapse
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
nwb_sam said:
From "Settings" App > "Software Update" > "Download and Install" and pressing the "Download and Installing.
I get "Connecting to server" and then immediately "Registration Failed" I've attempted over Wi-Fi and with that option toggled off.
This could also be the phone is new and T-Mobile doesn't have the F711U1 XAA firmware at their carrier level, but the registration failed annoys me. On F711U (official T-Mobile firmware) I simply get a notification that the device is up to date.
Click to expand...
Click to collapse
Which F711U1 version did you flash?
iBowToAndroid said:
Which F711U1 version did you flash?
Click to expand...
Click to collapse
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
nwb_sam said:
I flashed my phone using the F711U1OYM1AUG7 (F711U1 XAA) firmware from sammobile.
I flashed it back to the T-Mobile firmware, (F711UOYN1AUGB (F711U TMB) and the issue went away.
I did flash it again to the XAA to confirm the problem this evening. Never retained data during the process. Factory reset and removed my account information (Google and Samsung) before updating the firmware each time.
I've done this on a few phones in the past. If I'm making a blunder in the process causing this then I'm truly sorry for wasting anyone's time.
Edit: Typo
Click to expand...
Click to collapse
Well UG7 is the latest that's available. So yes, I would expect you to get an error.
Once an update is available, if the phone is still giving the same error, then you can worry about it
Hello, well from my understanding Xfinity is bootloader unlockable after 60days and fully played for. I am wondering if anyone is planning on making a thread for Xfinity specifically. Or want too work with me on One. Sorry too spam or thread. But if u are familiar with how rom building, and flashing was with any other recent samsung model/Xfinity/bootloader unlock. It would be highly appreciated too know your experience.
jokono421 said:
Hello, well from my understanding Xfinity is bootloader unlockable
Click to expand...
Click to collapse
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
iBowToAndroid said:
Incorrect. No US models of any Samsung device have been user-unlockable for years now, dating back to the S7
Click to expand...
Click to collapse
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
twistedumbrella said:
I think network unlock got mixed up with bootloader unlock. You can unlock the phones for use with another carrier after X days and completed payment.
Click to expand...
Click to collapse
Probably so
Can someone locate the thom browne fimware please?
blkghost22 said:
Can someone locate the thom browne fimware please?
Click to expand...
Click to collapse
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
iBowToAndroid said:
Well normally I would say that you can get it yourself from the various firmware download tools like SamFirm or Frija. But it looks like Samsung changed something over the weekend, as the current versions of the tools are failing to pull any firmware
So I can grab it for you
Click to expand...
Click to collapse
Thank you and always the best.
blkghost22 said:
Thank you and always the best.
Click to expand...
Click to collapse
Added, UGC build
iBowToAndroid said:
Added, UGC build
Click to expand...
Click to collapse
Guess its taking time to upload? Dont see the files just yet..
Edit:
Nvm i see the files now... again thank you so much
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
blkghost22 said:
I know long time ago it didnt work but just wanted to throw it out there... if i flash the u1 or thom browne am i able to flash the att userdata to get the advance msging and video calls?
Click to expand...
Click to collapse
1. Thom Browne *is* U1 firmware
2. USERDATA belongs to U firmware, not U1. So I have absolutely no idea. You'll have to try it and see what happens
Have successfully flashed F711U1 to F711W. Everything working fine. Used Odin 3.14, CSC_OMC_OYV, and working on Telus with all available features working.
Please note that AFTER the flash, you will be prompted to reset the device to stock. Reason being is that it needs to install the appropriate CSC linked to the inserted SIM card.
Can anyone confirm if cross flashing different build firmwares that it will unlock the unlock bootloader option?
Currently on carrier firmware for TMobile and I'm wondering if this is possible or if the u1 firmware has the unlock bootloader option available