My wife works in a hospital and we used wifi calling because reception was poor.
It's still poor with Tmobile but no wifi calling. When we moved from At&t the wifi
option was greyed out. Tmobile states that it works fine on their network.
Is there any way to get a samsung s7 g930a and a samsung j7-j727a to use wifi calling
on the Tmobile network?
I'm sure it will probably involve something over my pay grade but I am willing to try
anything needed to get this feature to work
JohnAtlas said:
My wife works in a hospital and we used wifi calling because reception was poor.
It's still poor with Tmobile but no wifi calling. When we moved from At&t the wifi
option was greyed out. Tmobile states that it works fine on their network.
Is there any way to get a samsung s7 g930a and a samsung j7-j727a to use wifi calling
on the Tmobile network?
I'm sure it will probably involve something over my pay grade but I am willing to try
anything needed to get this feature to work
Click to expand...
Click to collapse
If your current firmware has WiFi calling (Volte) You can only use Volte if the network supports it. There are however many apps you can use for WiFi calling look on the play store.
Not sure what volte is, I have had some other issues with the
service that I thought might be resolved by installing a
different rom
Tell me if i'm wrong
Thanks
JohnAtlas said:
Not sure what volte is, I have had some other issues with the
service that I thought might be resolved by installing a
different rom
Tell me if i'm wrong
Thanks
Click to expand...
Click to collapse
Volte is wi fi calling over a network which the network operator supports without the need for a specific app.
Please tell me exactly what you are trying to do
What network are both phones using?
Which networks were the phones on initially?
Have you modified the phones in any way? Root? or TWRP?
What firmware are both phones currently using? Go to Settings>about phone>software information>baseband version G930A????
Sorry for not getting back sooner
Both phones are currently on Tmobile network
Both phones were originally on At&t network
No modification
Samsung s7 g930a baseband version G930AUCS8CRL1
Samsung j7-j727a baseband version J727AUCS4BRL1
Note: Wifi calling was available on original at&t network but is now greyed out on tmobile network
JohnAtlas said:
Sorry for not getting back sooner
Both phones are currently on Tmobile network
Both phones were originally on At&t network
No modification
Samsung s7 g930a baseband version G930AUCS8CRL1
Samsung j7-j727a baseband version J727AUCS4BRL1
Note: Wifi calling was available on original at&t network but is now greyed out on tmobile network
Click to expand...
Click to collapse
Ok since wi fi calling is network specific (some have it some don't) you either need to have unbranded firmware on your phone so it works no matter which network is providing it, or you need to now flash T Mobile firmware for it to work again on your phone.
US networks are a nightmare when it comes to this sort of thing and it's a right pain in the a** to solve it. So what you need to search for now on here is how to flash different firmware on AT&T S7. You should always try to flash unbranded firmware so everything works easily, if not it will have to be T Mobile Oreo.
cooltt said:
Ok since wi fi calling is network specific (some have it some don't) you either need to have unbranded firmware on your phone so it works no matter which network is providing it, or you need to now flash T Mobile firmware for it to work again on your phone.
US networks are a nightmare when it comes to this sort of thing and it's a right pain in the a** to solve it. So what you need to search for now on here is how to flash different firmware on AT&T S7. You should always try to flash unbranded firmware so everything works easily, if not it will have to be T Mobile Oreo.
Click to expand...
Click to collapse
Ok, If you think unbranded is the best way to go can you point me in the right direction
updato.com and sammobile.com both host firmware and have flash guides. SamFirmTool also is good for downloading firmware, but only lets you download the latest version and isn't as user friendly.
For unbranded you'll want to look for G930U firmware.
For best compatibility you flash all 4 files using (AP,BL,CP,CSC) this will wipe the phone clean. Otherwise you can try Home_CSC instead of CSC (So AP, BL, CP, Home_CSC) , which keeps your data but may not fully resolve your issues.
Beanvee7 said:
updato.com and sammobile.com both host firmware and have flash guides. SamFirmTool also is good for downloading firmware, but only lets you download the latest version and isn't as user friendly.
For unbranded you'll want to look for G930U firmware.
For best compatibility you flash all 4 files using (AP,BL,CP,CSC) this will wipe the phone clean. Otherwise you can try Home_CSC instead of CSC (So AP, BL, CP, Home_CSC) , which keeps your data but may not fully resolve your issues.
Click to expand...
Click to collapse
What beanvee has said but I think it's worth mentioning I find Sam Firm tool pretty straight forward to use and you'll always get the firmware in separate parts which can be useful.
I found a link for the G930A here
I'm not really understanding the differences in firmware. How is flashing with this firmware
any different than what's on the phone right now?
I am just trying to get the wifi calling to work, How is flashing it with at&t version firmware going
to help me on the tmobile network.
I guess I don't know what I need, stock, unbranded, official or custom rom.
I checked all sites listed and there is no firmware for the J727a, alternative?
I would rather someone more knowledgeable guess what I need to do, if that is what is
necessary because the phones are no good to me without that feature. Any suggestions
would be appreciated.
Each carrier deploys their own CSC file, which contains carrier specific configurations, and its this file that determines if VoLTE or VoWIFI is enabled and how it connects.
AT&T may have different VoWIFI settings to TMobile, which is why using AT&T firmware it doesn't work. Some carriers outright disable it since they don't offer it.
Your best bet would be G930T firmware https://updato.com/firmware-archive-select-model?q=SM-G930T&rpp=15&order=date&dir=desc&exact=1
However unbranded G930U should also work because the unbranded firmware is meant to work on all cariers. G930A would likely get you no where since it'll be AT&T specific
The phones in the USA are all identical hardware under the hood, the only difference is the carrier branding and firmware.
But that's only for the S7, I'm not familiar with the J7.
And it's not through lack of knowledge @JohnAtlas, US phones are a nightmare to do anything with. There are several options available but it's difficult to explain what to do and how to do if you are not familiar with how the software works.
There are many guides on how to unlock the software on all US networks, and depending on the network can include multiple steps to complete, you just have to search and read.
Ok, I was able to find the latest firmware for the G930 phone
I installed odin and have the files, BL, AP, CP, and CSC or Home CSC
My question is, Do I load all files and then start or do one file at a time in odin
I tried all files the first time and got failed error and dismatch
Thanks
JohnAtlas said:
Ok, I was able to find the latest firmware for the G930 phone
I installed odin and have the files, BL, AP, CP, and CSC or Home CSC
My question is, Do I load all files and then start or do one file at a time in odin
I tried all files the first time and got failed error and dismatch
Thanks
Click to expand...
Click to collapse
All files in correct slots and use this Odin https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Put all files in and used patched odin via link
Received fail and screen that said, "An error has occurred while updating the device software"
After reading more, tried to install twrp and received secure check fail : recovery
Rebooted phone and this is the screen right now, not sure what to do next
Thanks
https://drive.google.com/file/d/1QRvaTNb067u49lW1s4UZdRZivK936C2Y/view?usp=sharing
JohnAtlas said:
Put all files in and used patched odin via link
Received fail and screen that said, "An error has occurred while updating the device software"
After reading more, tried to install twrp and received secure check fail : recovery
Rebooted phone and this is the screen right now, not sure what to do next
Thanks
https://drive.google.com/file/d/1QRvaTNb067u49lW1s4UZdRZivK936C2Y/view?usp=sharing
Click to expand...
Click to collapse
That is the system recovery and when you flash with Odin you need to put your phone in download mode first press volume down+home+power. The phone should not go to that screen you have posted either before or after Odin, its a completely different recovery mode.
Get your firmware from updato. Com or sammobile
G930U, filter by USA and choose the latest XAA or USC and use the modified version of Odin. We know this works because thousands of people have used it to do what you are trying to do.
Thanks for info, I used G930U TMK version since we are on Tmobile carrier
It seems to be working fine and wifi calling is available
There is no TMK version for the J727U but will try the XAA for the other phone
The way I understand it is that the U means unlocked and the XAA is generic and not carrier specific
Please advise if I'm not on the right track
Thanks for your help
JohnAtlas said:
Thanks for info, I used G930U TMK version since we are on Tmobile carrier
It seems to be working fine and wifi calling is available
There is no TMK version for the J727U but will try the XAA for the other phone
The way I understand it is that the U means unlocked and the XAA is generic and not carrier specific
Please advise if I'm not on the right track
Thanks for your help
Click to expand...
Click to collapse
That's brilliant , glad your up and running.
So the letter "U"after the "G930" denotes the region of the world the device is build to operate in, the Americas just happens to be U. The unbranded firmware is the one that has a region but no network assigned to it, so a 3 letter code is used instead, in your case its USC, or XAA.
Europe is G930"F" or "FD" and the 3 letter code for unbranded is BTU & XEA.
Anyway if your phone is running great on T Mobile then don't update it anymore, turn auto update off. The advantage of keeping it T Mobile is you have the wifi calling, the unbranded firmware needs more fiddling around with the get the wifi calling working on the network your using, so best to stick with what works.
I will have a look for firmware for the J7 you have to see if i can recommend doing something with it to get the wifi calling working.
*update*
So it seems the J727 is the same as the J7 in terms of the internal components, everything is the same in both models so that's great news. I think the "27" bit is just a marketing thing.
In theory you should be able to flash the latest T Mobile Oreo to your device from this link https://www.sammobile.com/firmwares/galaxy-j7-pop/SM-J727T/TMB/download/J727TUVS4BRK1/249137/
Now before we start please check / do the following to avoid further problems.
1. Save everything you need from the phone to your pc.
2. Check that you have OEM unlocked in "developer settings" and "USB debug" enabled.
3. developer setting menu is, settings>about phone>software and information>build number>tap 7 or 8 times, developer menu should now appear. (Sometimes it's somewhere else but build number is what you want to find and tap on 7-8 times).
4. To avoid any issues with device FRP lock, delete your google account off the phone., settings>accounts>google. delete it. When successfully flashed you just add the account again when the phone starts for the first time by signing in.
5. Use the same version of Odin you used to flash your S7.
you can also use updato.com (i think it's slightly faster than sammobile.)
Let me know how you get on.
Remember J727T (TMB) is the firmware you want.
Related
I just unboxed my G955FD and put my cricket SIM in and have no response from the network other than pushing an APN and my phone number. I tried manually selecting carrier networks and it listed 5 different "cricket" to attempt to connect to. At one point it showed signal bars in the status area, but no network connectivity. When I automatically connect to the network it responds saying I am registered but no signal bars in status and no activity. I appreciate the help.
Can anyone offer some tips before I call it a lost cause? The phone is out of its return period and probably broken since it will now receive a cricket badge and bars and LTE service but will not make calls or go online
Hey, are you on stock ROM. My 955F works just fine on Cricket, though compared to my daughters AT&T setup, her data is much faster. just discovered this today, and tomorrow will visit Cricket and AT&T to find out why...
Jan 9, 2108 update. I discovered Cricket is limited to about 5-6 Mps. I'm now on AT&T, for a few dollars more for two lines, and can get up to about 40-60 Mps in town.
What region CSC are you using?
---------- Post added at 07:59 AM ---------- Previous post was at 07:35 AM ----------
Here are my apn settings
Name: any but I input Internet or Cricket, I think it will work with whatever you like.
APN: ndo
MMSC: http://mmsc.aiowireless.net
MMSC proxy: proxy.aiowireless.net
multimedia message port: 80
mcc: 310
mnc: 150
apn type: default,mms,fota,hipri,supl
I know when I've setup APs on other phones there have been times that I will first do a 'reset' of my network settings on the phone, then reboot. Sometimes that will help. After that I will enter new APN settings and reboot.
On this 955F, with a viable CSC my phone just finds Cricket and works. With a bad CSC, it may list/show the cricket or AT&T networks, and will not register, no matter what I do, and for how long.
For example, my phone initially had a stock F ROM and a Panama region for the CSC. It worked with Cricket straight away. I changed the CSC to XAA using AT&T, and would find the towers, but would absolutely not register/work.
I ended up installing CarHDROM - a Note 8 OS ported for the 8+, and It took me a bit to find a CSC package that was meant for the ROM (Note 8) I was using, meaning I had to use a Note 8 CSC, even though my phone was an 8+ 955. Once that installed, Cricket started right away.
The CSC that came with CarHDROM I don't think worked straight out, but I can't recall for sure. I did end up using a XAA CSC, for the Note 8, non-AT&Tand that solved my connection issue after I had installed the CarHDROM.
CSC and phone wise, the ROM takes precedent, and the CSC must match the ROM (model). Seems that way to me, anyway.
Hope his helps.
There is another post about a FD phone that won't connect up, as well.
https://forum.xda-developers.com/galaxy-s8+/help/original-firmware-t3725472
I am on stock ROM. I guess I will root today and change CSC and hopefully that fixes whatever issue is going on. I have seen the cricket badge and LTE bars recently but no registration on network. If not, the eBay seller said they will take the phone back I'd it's indeed broken.
Ok so far no luck changing the CSC on stock ROM. I am going to try a couple different ROM and CSC combos tonight. Once again I am showing bars and cricket badge but not connecting data or voice on the phone, after root, and changing CSCs. I feel like Im so close and passed up my last day to return to eBay seller so I hope it truly is software and not hardware related. Im thinking of going by AT&T to act like a potential customer and see if its cricket messing up. Any other suggestions to try before I go crazy and use this phone for target practice?
Is it possible this is a region lock issue? My phone is a Tawain version and it was brand new out of the box. There is no sticker on it mentioning region lock. Does anyone have any insight into region locking for outside EU devices?
ChikhaiBardo said:
Is it possible this is a region lock issue? My phone is a Tawain version and it was brand new out of the box. There is no sticker on it mentioning region lock. Does anyone have any insight into region locking for outside EU devices?
Click to expand...
Click to collapse
Good question. I have a 930S Chinese region and it pulled in ATT/Cricket/TMobile just fine. I did have problems when I flashed a custom ROM, and flashed the CSC that came with the ROM. Later I flashed back the OEM CSC for the region (China) and it worked perfectly, again.
If you do flash a custom ROM, make sure you get a CSC package that is meant for that ROM (model). Not the exact model of your original phone. If you can find an XAA CSC that is meant for the new ROM, should be perfect.
JeffDC said:
Good question. I have a 930S Chinese region and it pulled in ATT/Cricket/TMobile just fine. I did have problems when I flashed a custom ROM, and flashed the CSC that came with the ROM. Later I flashed back the OEM CSC for the region (China) and it worked perfectly, again.
If you do flash a custom ROM, make sure you get a CSC package that is meant for that ROM (model). Not the exact model of your original phone. If you can find an XAA CSC that is meant for the new ROM, should be perfect.
Click to expand...
Click to collapse
Ok I have been changing CSC through TWRP with the CSCSelection Utility. Is that what you are referring to with flashing CSC? Is there a more effective way to do this through Odin? I think tomorrow morning I am going to flash back to stock firmware and start over. Am I able to flash any stock firmware for the SM-G955FD through Odin or do I need the original firmware for my region, which is (BRI) I believe I remembered reading I can flash everything for that model, but not any North American firmware meant for the SM-g955U
ChikhaiBardo said:
Ok I have been changing CSC through TWRP with the CSCSelection Utility. Is that what you are referring to with flashing CSC?
Yes
Is there a more effective way to do this through Odin? I think tomorrow morning I am going to flash back to stock firmware and start over. Am I able to flash any stock firmware for the SM-G955FD through Odin or do I need the original firmware for my region, which is (BRI) I believe I remembered reading I can flash everything for that model, but not any North American firmware meant for the SM-g955U
Click to expand...
Click to collapse
Just flash the CSC that comes 'stock'/with the rest of the full, stock firmware set, Odin will work. Have the SIM in the phone before you reboot, as for me it seems to help.
I haven't found a difference, for me yet, just flashing the exact CSC through Odin or TWRP. As I'm now on a custom ROM, I'm usually flashing via TWRP with a CSC that is supplied by an Aroma setup. Aroma is very handy.
Yes, flash your full stock via Odin. If you have TWRP you will lose it. You can re-flash TWRP from Odin. I typically flash TWRP all by itself, but I don't think that is really necessary. Maybe someone will come along and let us know.
As an aside I always keep a copy of zips/installs of TWRP, re-verity and SU on my SD card.
So after the stock full flash, I reboot into download mode and Odin flash TWRP, and follow that by a direct 3 key reboot into recovery, and TWRP will load. If you are going to root then flash re-verity, then SU/Magisk. You could then flash your CSC, but with the issues you've been having, I'd then boot to system, do the initial setup of the phone, and then boot back to recovery/TWRP, backup the phone.
Then TWRP flash the CSC Aroma package, making sure you have the SIM in the phone and reboot to system. I've been using XAA as my CSC with my custom ROM, within that is AT&T, T-Mobile, etc for US phones. I select the main XAA CSC from Aroma. Next I select the unbranded XAA as my more specific/local package, instead of AT&T, for example.
My 955F, stock worked just fine on it's 'stock' CSC (China region). I only had to change the CSC when I flashed a custom ROM, and that ROM did not have the ROM's (model) of XAA, so I had to find a CSC, which had XAA, that 'matched' the ROM I had flashed. I had flashed a Note 8 ROM, CarHDROM,v8 initially. Again, that ROM was largely meant for Europe and Exynos phones, so I had to be pointed to a Note 8 CSC that was compatible with the Note 8 custom ROM.
Yes, Odin is where you would flash stock firmware/stock CSC (not in an Aroma package) for your SM-G955FD. It is my understanding that all non-US phones, eg the G955's, are mechanically the same, so flashing 'any' Exynos ROM, G955FD ROM should work via Odin. You can also flash CSC packages via Odin as well, but there is no Aroma process, to my knowledge/experience. So have the specific and correct CSC to flash via Odin, if you go that route. It sounds like you are aware your phone is Exynos? A non-US phone?
I specifically bought my G955 (8+) as non-US so it could take root smoothly/easily, and work great world wide, including working great here in the US. Sometimes the U.S. does not seem a part of the world.
As I've been messing about with S7's/8s, there have been times that the phone did not grab onto AT&T, for example, and i would then 'reset' the network and reboot, with the SIM in the phone, then do a search for phone networks/services. That usually solved it, but when it did not, and I know I have the right CSC, I would then input/create a new APN, with AT&T, Cricket, Sprint, or what-ever service I needed, then reboot.
The only times I've not gotten the phone/s to grab the networks after that is when I've had the incorrect CSC.
Again, on my stock what-ever country G955F, stock G930S, etc, all Exynos, with the same stock (non-US) CSC that come in the firmware package, the phones have grabbed AT&T/T-Mobile just fine. If it would not, I would have reset the network, rebooted and entered the APN, and then rebooted (with the SIM in the phone). Done a network search after that, if necessary.
Hope this helps.
So today I stopped by TMOBILE and the store clerk popped a SIM card in and it fired up 4G LTE immediately and made calls. I then decided to stop by AT&T and it showed bars but refused to register or do anything even with the APN settings being pushed through from AT&T and Cricket. I am finally happy to realize that my phone is not defective (which I had feared before) and that it must be this service area and the bands on the G955FD. I have wanted to switch to TMOBILE for awhile now anyway so this is my chance to have an excuse to do it. Any input on why it won't access AT&T through an AT&T or Cricket SIM? I'm curious now more than anything. It must be missing a band that this area uses correct? The phone is clearly unlocked and functioning correctly.
What local CSC r u using?
Did you have AT&T check the APN?
T-Mobile and AT&T work on S8+ just fine, but need appropriate APNs.
Head back to the AT&T, if you want AT&T, and see if they will reset and or reinstall AT&T CSC/OS on your phone. XAA/ATT will have the AT&T boot logo. XAA/XAA (generic US use, ATT/T-Mobile compatible) will not.
One ringy dingy, two ringy dingy's...
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'm currently running the firmware from this thread: https://forum.xda-developers.com/verizon-galaxy-s7/development/easyroot-unroot-t3859755. I'd like to try out the latest v4 bootloader 930U firmware but I need to have the Verizon "Advanced Calling" on my phone because of my home in a VZW blackhole. 200 feet in every direction and signal picks up. Anyway, I need to be able to do Wi-Fi Calling. Does anybody know what apk's I need to grab from the 930V firmware? Or is it much more involved than that?
Generally things like that are part of the CSC firmware, as that's what holds carrier apk's and firmware configs. You could try downloading the G930V firmware and flashing just the Home_CSC file, which doesn't data wipe.
However in previous threads I've seen on the topic, people had to use the CSC file to finally get it working, which causes a device wipe.
I'm not quite sure I follow you. I'm currently already on Oreo PDA G930VVRS4CRI1 and CSC G930VVZW4CRI1. I want to switch to Oreo G930UUES4CRH2 or Nougat G930UUEU4BRD1 and somehow get VZW's Advanced Calling.
royta said:
I'm not quite sure I follow you. I'm currently already on Oreo PDA G930VVRS4CRI1 and CSC G930VVZW4CRI1. I want to switch to Oreo G930UUES4CRH2 or Nougat G930UUEU4BRD1 and somehow get VZW's Advanced Calling.
Click to expand...
Click to collapse
The wifi calling or "advanced" as you call it, is already enabled on the U firmware.
What Beanvee is trying to explain is when you unzip the firmware files ready for Odin, you can use the Verizon Home_CSC instead of the one which comes with the G930U firmware. This would mean you need to download both firmwares G930U & G930V.
cooltt said:
The wifi calling or "advanced" as you call it, is already enabled on the U firmware.
What Beanvee is trying to explain is when you unzip the firmware files ready for Odin, you can use the Verizon Home_CSC instead of the one which comes with the G930U firmware. This would mean you need to download both firmwares G930U & G930V.
Click to expand...
Click to collapse
Thanks. The "Advanced Calling" includes the Video Calling and HD Calling along with Wi-Fi Calling. I would like all of those features.
cooltt said:
The wifi calling or "advanced" as you call it, is already enabled on the U firmware.
What Beanvee is trying to explain is when you unzip the firmware files ready for Odin, you can use the Verizon Home_CSC instead of the one which comes with the G930U firmware. This would mean you need to download both firmwares G930U & G930V.
Click to expand...
Click to collapse
royta said:
Thanks. The "Advanced Calling" includes the Video Calling and HD Calling along with Wi-Fi Calling. I would like all of those features.
Click to expand...
Click to collapse
you two are basically speaking two different languages. @cooltt what the previous replies are saying is that your phone already has the apps youre looking for, theyre just not installed because the non-verizon specific versions of the firmware for your phone (which is what youre running) doesnt automatically install it. The CSC is the file inside of the firmwares tar.md5 file that tells it which version youre trying to use. Its kinda like how windows 10 ISOs have every version of windows inside of the ISO, the serial tells it what features to install.
What theyre telling you to try is to take the verizon tar.md5, decompress it in something like winzip, winrar or whatever you prefer, extract the file titled "HOME_CSC", put the phone in download mode and flash just the HOME_CSC file in its spot in Odin. That has the potential of telling the phone to look in the firmware for those features's apks and install them.
Think of flashing a VZW specific CSC as having windows home premium and going in and replacing that serial with a windows pro serial. Very similar concept.
the S7 is the last phone that used the single file in Odin method whereas the S8 and after uses 4. The 4 files are all inside the compressed tar.md5 file and always have been there, but the methodology of deploying the files changed starting with the S8, which coincided with the biggest form factor change in the galaxy lineup in years.
I never did get around to trying this out on my S7. I bought a Verizon S10 on Sunday and am now trying to do the same thing with it. Use unbranded firmware but still have the Advanced Calling. I'm hoping somebody over here might know what to do.
https://forum.xda-developers.com/galaxy-s10/help/install-verizon-advanced-calling-g973u1-t4064831
Hey Everyone,
I have unlocked SM-N986U1 with the latest update installed (Updated with latest June update). I wanted to change my CSC to TMB (T-Mobile) so as to enable ESeim support. I tried using Samkey, wasted 1 credit too. It said CSC updated but nothing happened, my carrier still shows XAA.
Can anyone please guide me on how can I change CSC to TMB?
Thanks.
dawinner said:
Hey Everyone,
I have unlocked SM-N986U1 with the latest update installed (Updated with latest June update). I wanted to change my CSC to TMB (T-Mobile) so as to enable ESeim support. I tried using Samkey, wasted 1 credit too. It said CSC updated but nothing happened, my carrier still shows XAA.
Can anyone please guide me on how can I change CSC to TMB?
Thanks.
Click to expand...
Click to collapse
These links'could help. I think you have to flash the TMB Rom which enables and support the eSim on the phone. It would help to have a Tmobile Sim around during this process but I have heard others say it is not needed.
Note 20 Ultra eSIM update is here!! (T-mobile USA)
Guys, FINALLY!!! Woohoo! We have eSIM support on Note 20 Ultra US Snapdragon version for T-mobile. There is an OTA you can download and then convert your physical SIM to eSIM :)
forum.xda-developers.com
[Guide] - eSim Firmware Flash/ Odin Upgrade/ Flashing and N986U to N986U1 & Vice Versa
Instructions are updated to get eSIM INTRODUCTION - Firstly sorry for posting this as this is common knowledge for many. I still see so many people asking the same questions again and again and i do want to help so decided to write a guide. If...
forum.xda-developers.com
Mbetu said:
These links'could help. I think you have to flash the TMB Rom which enables and support the eSim on the phone. It would help to have a Tmobile Sim around during this process but I have heard others say it is not needed.
Note 20 Ultra eSIM update is here!! (T-mobile USA)
Guys, FINALLY!!! Woohoo! We have eSIM support on Note 20 Ultra US Snapdragon version for T-mobile. There is an OTA you can download and then convert your physical SIM to eSIM :)
forum.xda-developers.com
[Guide] - eSim Firmware Flash/ Odin Upgrade/ Flashing and N986U to N986U1 & Vice Versa
Instructions are updated to get eSIM INTRODUCTION - Firstly sorry for posting this as this is common knowledge for many. I still see so many people asking the same questions again and again and i do want to help so decided to write a guide. If...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the link to guide. I was going through it and there is a warning on the top saying if you have Bootloader 2 you won't be able to flash U firmware on U1. I believe as I have all the latest updates I wont be be able to flash it.
Thanks for your help.
dawinner said:
Thanks for the link to guide. I was going through it and there is a warning on the top saying if you have Bootloader 2 you won't be able to flash U firmware on U1. I believe as I have all the latest updates I wont be be able to flash it.
Thanks for your help.
Click to expand...
Click to collapse
Yes you can. My device is from Xfinity and I have done the switch to any Carrier I choose on bootloader 2. U1 to U and back is doable. The key is to use the modified Odin as specified in the guide.
"
2. Download Patched Odin here
3. Unpack/Unzip what you downloaded in Step 2 (Odin Compatible ROm) and put in a folder. Lets call the folder "Flash"
4. Run Odin, click on BL, Browse to the "Flash" folder, add BL file from there, Do the same for AP (click on AP, Add AP file, this will take some time), Same for CP (click on CP, Add CP file)
5. Do the same for CSC (click on CSC, Add the file with the name starting with Home_CSC). If you use Home_CSC your phone will not get formatted and data will remain Intact
USERDATA Stays empty.
6. Now connect USB cable to your laptop (Only laptop and not the phone)>> Turn off your phone >> Press volume up and volume down keep them pressed and plug in the USB type C into your phone.
7. You should be in download mode now, press volume up. In Odin you will see that phone is added.
8. Press start in Odin. Wait for it to finish and let the phone restart (it will happen On its own).
9. Done
Mbetu said:
Yes you can. My device is from Xfinity and I have done the switch to any Carrier I choose on bootloader 2. U1 to U and back is doable. The key is to use the modified Odin as specified in the guide.
"
2. Download Patched Odin here
3. Unpack/Unzip what you downloaded in Step 2 (Odin Compatible ROm) and put in a folder. Lets call the folder "Flash"
4. Run Odin, click on BL, Browse to the "Flash" folder, add BL file from there, Do the same for AP (click on AP, Add AP file, this will take some time), Same for CP (click on CP, Add CP file)
5. Do the same for CSC (click on CSC, Add the file with the name starting with Home_CSC). If you use Home_CSC your phone will not get formatted and data will remain Intact
USERDATA Stays empty.
6. Now connect USB cable to your laptop (Only laptop and not the phone)>> Turn off your phone >> Press volume up and volume down keep them pressed and plug in the USB type C into your phone.
7. You should be in download mode now, press volume up. In Odin you will see that phone is added.
8. Press start in Odin. Wait for it to finish and let the phone restart (it will happen On its own).
9. Done
Click to expand...
Click to collapse
Thanks for the steps. Couple of Quick Questions:
1) I used frija to download the firmware (I typed CSC: TMB in frija, as its the first time I am using it, is it the right way)
2) I also checked the version in frija with the CSC: XAA, the version is same. How can I make sure that I have downloaded the correct TMB firmware.
Thanks.
dawinner said:
Thanks for the steps. Couple of Quick Questions:
1) I used frija to download the firmware (I typed CSC: TMB in frija, as its the first time I am using it, is it the right way)
2) I also checked the version in frija with the CSC: XAA, the version is same. How can I make sure that I have downloaded the correct TMB firmware.
Thanks.
Click to expand...
Click to collapse
You might want to extract the files and check for differences. The Frija tool has been kind of good to me.
Mbetu said:
You might want to extract the files and check for differences. The Frija tool has been kind of good to me.
Click to expand...
Click to collapse
Thanks for all the help, one last question, and I dont know if you will know about this:
To enable ESIM (Only T-Mobile version has E-SIM), do I need to flash U version of T-Mobile of U1 version of T-Mobile will also provide me with the same ESIM functionality?
dawinner said:
Thanks for all the help, one last question, and I dont know if you will know about this:
To enable ESIM (Only T-Mobile version has E-SIM), do I need to flash U version of T-Mobile of U1 version of T-Mobile will also provide me with the same ESIM functionality?
Click to expand...
Click to collapse
I think I flashed the U version of Tmobile but it does not hurt to try both. This is what my device info says after converting my Xfiniti to Tmobile
Mbetu said:
I think I flashed the U version of Tmobile but it does not hurt to try both. This is what my device info says after converting my Xfiniti to Tmobile
Click to expand...
Click to collapse
Thanks!!!!
Mbetu said:
I think I flashed the U version of Tmobile but it does not hurt to try both. This is what my device info says after converting my Xfiniti to Tmobile
Click to expand...
Click to collapse
I flashed the complete U firmware except the USER DATA file. But my Service Provider Software version is still stuck at XAA, its not changing to TMB. Though the phone model has changed to what you have in your screenshot.
Any idea what to do?
dawinner said:
I flashed the complete U firmware except the USER DATA file. But my Service Provider Software version is still stuck at XAA, its not changing to TMB. Though the phone model has changed to what you have in your screenshot.
Any idea what to do?
Click to expand...
Click to collapse
So the Model is 986U/DS ? And is eSim enabled ?. That is the state you would want to be in. I understand the last XXX in the service provider software can't be changed. Mine didn't change and stayed CCT which is for xfinity but the as you can see, I have TMB/TMB, TMB/CCT. Esim is enabled and my Mint mobile (Tmobile) number is on it and I have a foreign physical Sim which is roaming on AT&T on the physical slot.
You might be close.
Mbetu said:
So the Model is 986U/DS ? And is eSim enabled ?. That is the state you would want to be in. I understand the last XXX in the service provider software can't be changed. Mine didn't change and stayed CCT which is for xfinity but the as you can see, I have TMB/TMB, TMB/CCT. Esim is enabled and my Mint mobile (Tmobile) number is on it and I have a foreign physical Sim which is roaming on AT&T on the physical slot.
You might be close.
Click to expand...
Click to collapse
Also picked this nugget up from another thread
"You have to flash full tmb firmware. Not xaa tmb but 986u tmb firmware. The esim is in the user data section you'll flash"
Others have suggested you have to do a factory reset or flash the actual CSC file not the Home CSC which means you will loose DATA. I was doing this on a phone I had not setup yet so didn't mind loosing DATA. I am also assuming you have a TMB sim card in the phone because I understand that is needed so the phone can connect to Tmobile and download the carrier data files that actually changes the CSC after a clean flash.
These are just some of the things I picked up from here when doing my conversion.
Mbetu said:
Also picked this nugget up from another thread
"You have to flash full tmb firmware. Not xaa tmb but 986u tmb firmware. The esim is in the user data section you'll flash"
Others have suggested you have to do a factory reset or flash the actual CSC file not the Home CSC which means you will loose DATA. I was doing this on a phone I had not setup yet so didn't mind loosing DATA. I am also assuming you have a TMB sim card in the phone because I understand that is needed so the phone can connect to Tmobile and download the carrier data files that actually changes the CSC after a clean flash.
These are just some of the things I picked up from here when doing my conversion.
Click to expand...
Click to collapse
Yup I used the TMB version only. The model Number changed to 986U/DS. In About phone, it shows me the IMEI of the Esim, but its greyed out.
The only thing I dont have is the T-Mobile Sim. I think thats whats causing the issue. I will arrange a t-Mobile sim and try it tomorrow.
Thanks for all the help.
Mbetu said:
Also picked this nugget up from another thread
"You have to flash full tmb firmware. Not xaa tmb but 986u tmb firmware. The esim is in the user data section you'll flash"
Others have suggested you have to do a factory reset or flash the actual CSC file not the Home CSC which means you will loose DATA. I was doing this on a phone I had not setup yet so didn't mind loosing DATA. I am also assuming you have a TMB sim card in the phone because I understand that is needed so the phone can connect to Tmobile and download the carrier data files that actually changes the CSC after a clean flash.
These are just some of the things I picked up from here when doing my conversion.
Click to expand...
Click to collapse
QQ: Does it has to be a T-Mobile Sim? or Mint mobile or anyother T-Mobile based MVNO should work?
dawinner said:
QQ: Does it has to be a T-Mobile Sim? or Mint mobile or anyother T-Mobile based MVNO should work?
Click to expand...
Click to collapse
Has to be a Tmobile Sim. I tried a Mint Sim it didn't work. If you are seeing the esim but greyed out, then you are close. Restart with a Tmobile Sim and you might be in business
Mbetu said:
Has to be a Tmobile Sim. I tried a Mint Sim it didn't work. If you are seeing the esim but greyed out, then you are close. Restart with a Tmobile Sim and you might be in business
Click to expand...
Click to collapse
Thanks that helps. I just have to figure a way to get a tmobile sim. I dont have it. Lol. Will try again once I get my hands on a Tmobile sim.
Thanks for the help.
dawinner said:
Thanks that helps. I just have to figure a way to get a tmobile sim. I dont have it. Lol. Will try again once I get my hands on a Tmobile sim.
Thanks for the help.
Click to expand...
Click to collapse
Anytime. FYI, dois not have to be an active TMB sim. Used ones are on ebay for about 2 bucks.
Mbetu said:
Anytime. FYI, dois not have to be an active TMB sim. Used ones are on ebay for about 2 bucks.
Click to expand...
Click to collapse
Thanks. Let me try those.
Since the OP looks like problem solved, and not wanting to waste new thread, i have similar issues, can you help?
I have an S10e I recently broke (amazon renewed w/U1 FW), so I got another S10e from amazon, renewed which appears to also be U1 FW.
Except the latest, the replacement phone, the one I have now, NOONE can hear me, like all the time!!!!!!! Dead spots everywhere! Its so annoying. Its like i have a bad Mic? Or something...
This didn't happen with my identical phone, the one I had prior to this one, using identical sim.
I'm on Mint mobile, which is a TMO MVNO and currently have XAA/XAG FW running on the new S10e, the new one w/bad Mic or FW problem
It appears I am on U1 Unlocked USA firmware on latest phone ( i may have flashed FW Odin when I got this new one-to be safe- i forgot)
ALSO: BOTH renewed S10e's I've Purchased from Amazon, when lookup the IMEI, it shows as the AT&T Model. Which i understand the U/U1 FW can be swapped, BUT, both phones were advertised as U1 Models for the Hardware, so they sold me U models but they flashed with U1 FW probably to make more money. (this may seem trivial, but Samsung specifically has stated TWICE, that I couldn't Beta Test their last to major android FW's, because my phone shows as At&t on their end, and not the truly unlocked U1 model, for which the beta tests were for. And i was told when i purchased it was fully unlocked U1 ver. The phone itself even says its 970u1 in settings etc.)
Are there ANY hardware (including frequency bands) differences between U and U1 Models???
Is it somehow possible that my CSC, or FW on my phone is affecting my phone so badly that people cant hear me like 88% of all calls? Like should i flash different FW, or reflash or use different CSC??
Is it possible that if I went with a locked TMO FW (or another) that I could possibly, maybe get better reception so folks can hear me better? Or hear me more often or more frequently?
How often do mics go bad or get dirty on these? Can a mic be cleaned?
I have been in the other Note 20 flashing thread but I am stuck. Tried so many ways but can't get the TMB csc to stick, always shows only XAA. I have TMO sim card too. Not sure if they blocked it on the newer releases of the phone
Has anyone tried Samkey to do this? Heard it only takes 1 credit but smallest amount of credits to purchase on ebay is 10 and I dont feel like investing more money into this effort
(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