Database Info

Att oreo on my tmobile s7

https://www.xda-developers.com/how-...-att-samsung-galaxy-s7-s7-edge/#disqus_thread
Can I flash this with flasfire if so how

SIGMAxB said:
https://www.xda-developers.com/how-...-att-samsung-galaxy-s7-s7-edge/#disqus_thread
Can I flash this with flasfire if so how
Click to expand...
Click to collapse
Won't flash on T-Mobile - it expects AT&T firmware (SM-G930A) - not anything else. I tried it (SM-G930T) and got error 7 in second stage with that exact reference (expected SM-G930A; got SM-G930T). This would have to be edited to take that second-stage reference out to work.)

You can flash if you flash the latest att firmware but the fluidity of the u firmware and battery have me staying put till the official release

Death Cookie Firmware in Non-DeathStar Phones - Yes; However
SIGMAxB said:
You can flash if you flash the latest att firmware but the fluidity of the u firmware and battery have me staying put till the official release
Click to expand...
Click to collapse
Then use A firmware (not U). You can even stick your T-Mobile nano-SIM back in the phone once the firmware is installed (just not DURING the install). I've just finished the install, have my UnCarrier nano-SIM back in the phone, and am currently charging it while restoring all my apps (yes - including the T-Mobile apps). The only loss (which isn't one in my situation) is VoLTE/VoWifi (two features I never use). The rather cute part is that I have more access to e-mail accounts with the AT&T firmware than I did with either UnCarrier firmware or VZW firmware (and with fewer apps, no less). Still, if you DO use VoLTE or VoWifi, this firmware is not an option. You have to reboot a second time (apparently the first reboot post-install doesn't completely flush - which is why the Wi-fi doesn't work; the second boot fixes that). The same should be true with any other carrier (VZW, Sprint, Cricket Wireless, Virgin Mobile, etc.); your only loss will be carrier-specific features.

PGHammer said:
Then use A firmware (not U). You can even stick your T-Mobile nano-SIM back in the phone once the firmware is installed (just not DURING the install). I've just finished the install, have my UnCarrier nano-SIM back in the phone, and am currently charging it while restoring all my apps (yes - including the T-Mobile apps). The only loss (which isn't one in my situation) is VoLTE/VoWifi (two features I never use). The rather cute part is that I have more access to e-mail accounts with the AT&T firmware than I did with either UnCarrier firmware or VZW firmware (and with fewer apps, no less). Still, if you DO use VoLTE or VoWifi, this firmware is not an option. You have to reboot a second time (apparently the first reboot post-install doesn't completely flush - which is why the Wi-fi doesn't work; the second boot fixes that). The same should be true with any other carrier (VZW, Sprint, Cricket Wireless, Virgin Mobile, etc.); your only loss will be carrier-specific features.
Click to expand...
Click to collapse
Which version of att firmware did you flash ? Is it worth flashing the Oreo update

SIGMAxB said:
Which version of att firmware did you flash ? Is it worth flashing the Oreo update
Click to expand...
Click to collapse
The same version in the AT&T Mobility thread (same subject) - the hard part (for me) was that I had to update by dong the updates manually to get to the right version to apply the beta (from an earlier version) - seven updates I had to apply via SDcard - THAT was the real pain, not the application of the beta firmware itself, which was rather painless. I'm still there and have absolutely zero interest in going back to any version of Nougat (stock or L, for that matter), and I came from Project L V.4. In other words, I'm using this as my daily driver.
I DO have one warning (and it's one that makes sense when using firmware from another carrier); take your T-Mobile SIM out before you start the firmware changeover, and don't put in your proper SIM until you start the new-customer steps, as some firmware doesn't take kindly to using a carrier other than the one intended (in the case of what I call "Darth Cookie", AT&T Mobility); remember, we're on T-Mobile - not exactly the "proper" carrier for this firmware. (I was wary on the move to T-Mobile firmware, because the handset itself is VZW-branded - and I was worried about gotchas merely there; amazingly - or more amusingly - because it IS locked firmware - changing carriers is depressingly easy despite the firmware locks.)

Beginning of Round Two - CRB6
PGHammer said:
The same version in the AT&T Mobility thread (same subject) - the hard part (for me) was that I had to update by dong the updates manually to get to the right version to apply the beta (from an earlier version) - seven updates I had to apply via SDcard - THAT was the real pain, not the application of the beta firmware itself, which was rather painless. I'm still there and have absolutely zero interest in going back to any version of Nougat (stock or L, for that matter), and I came from Project L V.4. In other words, I'm using this as my daily driver.
I DO have one warning (and it's one that makes sense when using firmware from another carrier); take your T-Mobile SIM out before you start the firmware changeover, and don't put in your proper SIM until you start the new-customer steps, as some firmware doesn't take kindly to using a carrier other than the one intended (in the case of what I call "Darth Cookie", AT&T Mobility); remember, we're on T-Mobile - not exactly the "proper" carrier for this firmware. (I was wary on the move to T-Mobile firmware, because the handset itself is VZW-branded - and I was worried about gotchas merely there; amazingly - or more amusingly - because it IS locked firmware - changing carriers is depressingly easy despite the firmware locks.)
Click to expand...
Click to collapse
I reset the phone, and kicked off testing of CRB6, and I did one thing differently; I left the SIM in the phone. I had a purpose for that - I was looking for bugbears that apply to non-AT&T carriers (T-Mobile, VZW, Sprint, et. al.) Amusingly, there aren't any. I did the flush (U Firmware version of BRA1) then applied the AT&T version of BQL1 (back-to-back via ODIN). Then came the ADB via SD card single-file updates (recovery mode for these) and there are only two - BQL1 to BRA1 (from Round One) and the new CRB6 update (courtesy of Samsung Firmware Science) labeled update_2.zip. It replaces update.zip, and is not opened or extracted - apply it as-is. After this update applies, follow the new-customer steps as you did for Round One - no changes here.

If anyone needs the newest G930A firmware before this Oreo leak, I have a Google drive Link. PM me.
And that's an Odin friendly

bkup said:
If anyone needs the newest G930A firmware before this Oreo leak, I have a Google drive Link. PM me.
And that's an Odin friendly
Click to expand...
Click to collapse
Can I get a copy please

Why I Did It The Way I Did
SIGMAxB said:
Can I get a copy please
Click to expand...
Click to collapse
When someone gets a proper copy, link it to the thread - the very reason I did NOT do it that way was because a proper copy of AT&T BRA1 didn't exist. (You can't get it from SamMobile or UPDATO either - much to my frustration; the latest ODINable AT&T firmware was BQL1.)

SM-G930P to SM-G930U

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 ?

G970U and G970U1 Firmware Links Here

For those who don't know, G970U is the model number of all of the US carrier versions of the Galaxy S10e. The G970U1 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. 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 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 pay for a subscription to a site that gets the official releases (usually) before they hit SamFirm/Frija, so that's where my files come from. However, I don't have unlimited bandwidth on the site, and it's also quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single Sx and Note x 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 SamFirm/Frija.
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, 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=290639
U1 firmware: https://www.androidfilehost.com/?w=files&flid=290640
(Quebec tends to be the fastest download mirror, if it gives you that option)
Notes:
- I compress extra small for space and bandwith savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- I remove the .md5 from each file solely for faster flashing (Odin won't check the file integrity without it). Rest assured, the files are perfectly fine and safe - Odin has a million safechecks built in.
- My naming method for folders 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. Any zips with "wipe" in the title do not have a HOME CSC included.
NOTE: With initial release, HOME CSC was not included by default, so I created it myself. Should flash fine, but until noted by someone in the thread, it has not been tested.
- I have identical threads for the S10 and S10+ as well
- 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 SamFirm/Frija:
AIO = Cricket (not available via SamFirm/Frija)
ATT = AT&T (not available via SamFirm/Frija)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via SamFirm/Frija, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
- the correct procedure for switching from one carrier's firmware to another is:
1. Flash full U1 firmware package including non HOME CSC
2. Upon boot, insert a SIM of the carrier whose firmware you want
3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want

Just a quick question will you be hosting FW for models G973U, G973U1, G975U, G975U1? Don't know if XDA will have separate forums for the s10e and s10+ models. Supposedly there will be a 5G S10+ coming during Mid 2019 which would have a separate FW section I assume.

equake said:
Just a quick question will you be hosting FW for models G973U, G973U1, G975U, G975U1? Don't know if XDA will have separate forums for the s10e and s10+ models. Supposedly there will be a 5G S10+ coming during Mid 2019 which would have a separate FW section I assume.
Click to expand...
Click to collapse
Read the OP

Nice plan! Kudos

Build SBA added.
SPR is the only USERDATA for this build so far - not sure if it will stay a Sprint-exclusive release, or be more widely pushed out. But like with any other build, it can be flashed to any S10e, regardless of which carrier it originally came from.
EDIT: Xfinity and Verizon USERDATAs added

I have the tmobile variant. Trying to flash and keeps failing for some reason. Trying to flash the U1 . Came with G970USQU1ASAT

matteosaeed said:
I have the tmobile variant. Trying to flash and keeps failing for some reason. Trying to flash the U1 . Came with G970USQU1ASAT
Click to expand...
Click to collapse
Can we get more details on that?

iBowToAndroid said:
MODS: Please move appropriately if the S10e is ever given its own forum
(For those who don't know, G970U is the model number of all of the US carrier versions of the Galaxy S10e. The G970U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among any of those models.)
As of the moment of posting, these cannot yet be obtained from SamFirm, and are not yet on SamMobile, but I thought some of you might like to get early access
I have no idea if existing patched Odin can be used to flash them, since I don't have a device to try it on. Maybe one of the blog sites can give it a try for us, on one of their review units. But at minimum, devs can peek into the partitions if they want, or casual users can keep the files on hand for converting firmware, once they get their device.
The large files will be your 4 part firmware and then grab your desired USERDATA as well. I'll continue to add more versions and more USERDATAs over time.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=290639
U1 firmware: https://www.androidfilehost.com/?w=files&flid=290640
Notes:
- I compress extra small for space and bandwith savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- I remove the .md5 from each file solely for faster flashing (Odin won't check the file integrity without it). Rest assured, the files are perfectly fine and safe - Odin has a million safechecks built in.
- My naming method for folders 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. Any zips with "wipe" in the title do not have a HOME CSC included.
NOTE: With initial release, HOME CSC was not included by default, so I created it myself. Should flash fine, but until noted by someone in the thread, it has not been tested.
- SamFirm still works, if you want to download them yourself. I pay for a subscription to a site that gets beta builds and also gets the official releases before they hit SamFirm, so that's where my files come from
NOTE: As of the moment of posting, these are not available via SamFirm. I'll remove this note once they become available for download (probably at/after device launch)
- I have identical threads for the S10 and S10+ as well
- You can get USERDATAs from SamFirm for everything but AT&T - those files will never be on SamFirm. So in addition to the 5 piece firmware, I'll try to always upload one USERDATA per bootloader increment for AT&T
- For USERDATAS (all the others are self explanatory):
ACG = C-Spire
AIO = Cricket
LRA = Bluegrass Cellular
CCT = Xfinity Mobile (Comcast)
CHA - Spectrum Mobile (Charter)
TMK = Metro PCS
Click to expand...
Click to collapse
Hope u can get the att.. i want the video call and advanced messaging that is missing from u1

iBowToAndroid said:
Can we get more details on that?
Click to expand...
Click to collapse
What would you like to know? I didn't get error codes or anything. Just failed. I used the csc and not the home one though.

blkghost22 said:
Hope u can get the att.. i want the video call and advanced messaging that is missing from u1
Click to expand...
Click to collapse
1. Don't quote the OP
2. What do you mean by "get the att"? There is an AT&T USERDATA for the U firmware
matteosaeed said:
What would you like to know? I didn't get error codes or anything. Just failed. I used the csc and not the home one though.
Click to expand...
Click to collapse
There might not be "codes" per se, but there's always a specific error that either shows up in Odin, or on the phone itself

iBowToAndroid said:
1. Don't quote the OP
2. What do you mean by "get the att"? There is an AT&T USERDATA for the U firmware
There might not be "codes" per se, but there's always a specific error that either shows up in Odin, or on the phone itself
Click to expand...
Click to collapse
Yeah, I remember on earlier phones there were errors showing. I didn't see anything except failed only on Odin. I'll try again later. I tried both the patched by raymond and regular Odin.

matteosaeed said:
Yeah, I remember on earlier phones there were errors showing. I didn't see anything except failed only on Odin. I'll try again later. I tried both the patched by raymond and regular Odin.
Click to expand...
Click to collapse
The only Odin that might work is the 3.13 patched (3B). But as stated in the OP, I have no idea if that Odin will work, or if a new one is needed.
If Odin fails, then we need to know on which step it fails, and what the message is. Probably best to just post a picture of it, or paste the log

Just to be clear, nobody has been able to flash U1 firmware to a U s10 device?
Considering ordering an s10e, but hoped that I could flash the U1 firmware to pass the provisioning check for tethering.

@iBowToAndroid
By any chance is there an AT&T userdata for the new SBA firmware? Sorry to bother
Nvm i just didnt check userdata and it worked

iBowToAndroid said:
The only Odin that might work is the 3.13 patched (3B). But as stated in the OP, I have no idea if that Odin will work, or if a new one is needed.
If Odin fails, then we need to know on which step it fails, and what the message is. Probably best to just post a picture of it, or paste the log
Click to expand...
Click to collapse
After i updated t-mobile firmware, i was able to flash with home csc. Stuck in starting android but will do a factory reset and will work fine. Will report back.
freddie813 said:
Just to be clear, nobody has been able to flash U1 firmware to a U s10 device?
Considering ordering an s10e, but hoped that I could flash the U1 firmware to pass the provisioning check for tethering.
Click to expand...
Click to collapse
Should work. I usually use pdanet vs the native tethering because tmobile can detect native tethering and throttle (happened on my pixel) .
---------- Post added at 11:59 PM ---------- Previous post was at 11:46 PM ----------
Flash successfully and working now. Will test if anything is broken

So all 4 main files are the same and there is no difference in T-Mobile's modem file versus ATT's? If I grab USERDATA file for TMB, it will flash all T-Mobile's bloatware.
As I remember flashing S7, S8 with a firmware that had TMB wording, where I could distinguish the firmware files. I mainly flashed 4 files on aforementioned models and skipped USERDATA and my unlocked U1 model became TMO and had all the features.
Soon T-Mobile is releasing firmware updates, will see how different they are.

So ive flashed the U1 firmware and it takes but the user data refuses to take and my phone is stil saying vzw/vzw/vzw
---------- Post added at 12:05 PM ---------- Previous post was at 12:05 PM ----------
Thinking im going to need a pulled pit file from someone actual tmobile s10e
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
if i use the regular U firmware with tmobile it goes back to factory of verizon and logo comes back

matteosaeed said:
After i updated t-mobile firmware, i was able to flash with home csc. Stuck in starting android but will do a factory reset and will work fine. Will report back.
---------- Post added at 11:59 PM ---------- Previous post was at 11:46 PM ----------
[/COLOR]Flash successfully and working now. Will test if anything is broken
Click to expand...
Click to collapse
Could you clarify the exact actions you took, step by step? And which odin?

Here's the procedure that worked best on the S9s, to convert firmware on a U model:
1. Wipe in recovery -->reboot bootloader-->flash U1 firmware
2. Upon boot, watch for the popup that says "your device will restart to apply new carrier settings", and do it. Make sure your desired SIM is inserted for this step.
3. After that finishes, power off, boot to download, and flash desired U firmware with non HOME CSC and desired U USERDATA. That should give you all the desired carrier settings - and bloatware.
Also, G973U and G973U1 firmware is now live and downloadable in SamFirm. Getting U1 (at least for now) requires manual entry - Auto will not work. U firmware is up for these carriers:
Xfinity Mobile
Spectrum Mobile
Sprint
T-Mobile
Metro
US Cellular
Verizon (have to use Manual entry - Auto will not work)
So going forward, I'll only be adding full builds if I can get them before they hit SamFirm, and only if there isn't build for that month already (eg. I won't add any more February builds since SBA is already up.). I will try to stay up to date on USERDATAs for AT&T and Cricket, since AT&T won't let their firmware be put on SamFirm.

I have an G975U1 and I attempted to flash the U1 firmware using 3.13 out of curiosity.
The first time it failed.
When the device steps through the necessary steps for Verified Boot, it failed.
VBMETA was referenced as was the partition table. So I can only surmise that the new VBMETA.IMG information doesn't match that which is stored within the device's partition tables.
I, unfortunately, didn't capture the the log nor the screenshot.
When I put the device back into 'Download Mode' and tried again, it passed.
I am going to try a CSC change from G975U1 to G975W using Odin 3.13B but I doubt it will work.
.....
And my attempt to change G975U1 to G975W using the Bell combination files failed. It provided the same error messages regarding VBMETA. See attached logs and screenshot.

General G996U and G996U1 Firmware Links and Flashing Discussion Here

For those who aren't already aware, G996U is the model number of all of the US carrier versions of the S21+. The G996U1 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 pay for a subscription to a site that gets the official releases (usually) before they hit the 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=322091
U1 firmware: https://www.androidfilehost.com/?w=files&flid=322092
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 to an S21, 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 Sx and Note x 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
SPR = Sprint
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
- the correct procedure for switching from one carrier's firmware to another is:
1. Flash full U1 firmware package including non HOME CSC
2. Upon boot, insert a SIM of the carrier whose firmware you want
3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want

Initial U firmware and AT&T USERDATA are posted, along with U1 firmware. U firmware is not yet accessible in the firmware download tools like SamFirm and Frija, but if anyone wants a different carrier's USERDATA (for flashing bloatware to a U1 device or for converting a U device from one carrier's bloatware to a different one), let me know and I'll get it for you

Are the firmware in OP compatible for the S21 (Non-plus)?

craznazn said:
Are the firmware in OP compatible for the S21 (Non-plus)?
Click to expand...
Click to collapse
This thread is in the S21+ forum, not the S21 forum.
This thread is for model numbers G996U and G996U1, not G991U or G991U1.
If you're looking for S21 firmware, that will be found in the S21 forum

I agree with you

Does the firmware control the SIM lock? So, can you flash the U1-XAA firmware and use say a phone purchased from AT&T on another carrier? Or do you need to do the SIM unlock before flashing?

3BeersKen said:
Does the firmware control the SIM lock? So, can you flash the U1-XAA firmware and use say a phone purchased from AT&T on another carrier? Or do you need to do the SIM unlock before flashing?
Click to expand...
Click to collapse
SIM unlock always goes much deeper than firmware. Flashing U1 will never automatically unlock any model - the unlock has to be done separately. If desired, I can provide a recommendation for a professional 3rd party business to do the unlocking, for any interested users who may not meet the carrier's unlock requirement(s).

Thanks. That's what I figured, but wanted to make sure. I like to get off of the AT&T firmware as quickly as possible as you can't get their updates unless you have an active SIM in the phone.

3BeersKen said:
You can't get their updates unless you have an active SIM in the phone.
Click to expand...
Click to collapse
Correct. They're A-holes like that haha

iBowToAndroid said:
Correct. They're A-holes like that haha
Click to expand...
Click to collapse
I got TMobile s21+ and want flash to u1,do you know which odin should I use, thanks

yijinsa said:
I got TMobile s21+ and want flash to u1,do you know which odin should I use, thanks
Click to expand...
Click to collapse
3.14.1 patched

I don't have my S21+ yet but it will be here soon. I ordered from Samsung and selected the Verizon version as unlocked was considerably more expensive.
Does anyone know what Verizon specific bloatware the S21+ has?
Are there certain apps which can be uninstalled with the U1 version but not the Verizon U version?
Are there any potential speed benefits on the 5G network that would be lost using the U1 version, or features like tethering that won't work?
For updates in the future, would they arrive faster on the U1 version, slower, or the same?
My main purpose in flashing from U to U1 is to free up the maximum amount of space of the 128 GB while still retaining 100% of the speed and features I would have with the Verizon version.
Thank you for educating me! It's been a couple years since I flashed my Note 8.

I order a unlocked S21+ U1 version straight from Samsung and didn't have to put in any VZW info.
There is a buttload of Samsung bloatware but no VZW except fot MyVZX

Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB

x1tymez said:
Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB
Click to expand...
Click to collapse
Yes, that seems to be a common issue with T-Mobile S21s - all 3 models

iBowToAndroid said:
Yes, that seems to be a common issue with T-Mobile S21s - all 3 models
Click to expand...
Click to collapse
You think there will be a fix for this? It's weird that dialer codes also don't work.

x1tymez said:
Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB
Click to expand...
Click to collapse
I've got a T-Mobile locked that I was able to get flashed over to U1 without much trouble. Shows mode number SM-G996U1 now, build number shows same.
edit: Nevermind, I see the TMB/TMB/TMB

krisology said:
You think there will be a fix for this? It's weird that dialer codes also don't work.
Click to expand...
Click to collapse
Dialer codes don't work? On which firmware?

iBowToAndroid said:
Dialer codes don't work? On which firmware?
Click to expand...
Click to collapse
XAA U1, VZW U1, stock TMB U, and I've tried the TLI U1 above and couldn't get it to work. Using google dialer, I input the codes like *#*#27262826#*#* and as soon as I type the last star it just disappears and nothing pops up. I tried with T-Mobile and Verizon sim.

krisology said:
XAA U1, VZW U1, stock TMB U, and I've tried the TLI U1 above and couldn't get it to work. Using google dialer, I input the codes like *#*#27262826#*#* and as soon as I type the last star it just disappears and nothing pops up. I tried with T-Mobile and Verizon sim.
Click to expand...
Click to collapse
Dialer codes usually don't work on VZW firmware, whether U or U1. But they almost always work on TMB and all others.
Have you tried *#06# ?

How To Guide F711U and F711U1 Firmware Links and Flashing Discussion Here

(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