Related
Hi guys,
just bought a new Samsung Galaxy S7 (SM-G930F).
Of course I got it with the Android 6.0.1 but I want to upgrade it to 7.
As for now, my build has no OTA updates to 7, but I saw that there's a UK build for Android 7.
Question is... if my build number is G930FXXU1BPLB, can I upgrade it to other build number, as for example to: G930FXXU1DPLT ?
And.. if I can do that... Will I get OTA updates of the future releases? It's important to note that I live in Israel, so what happens if I Install an UK build?
Will it block me to get OTA updates because I'm not from the region?
Thanks!
Everything works, except WifiCalling and VoLTE, if you switch to a british firmware.
So OTA's and the like won't be a problem. It's the same experience as if you were using your current german firmware in Israel.
For OTA's be sure to use the correct CSC file, so it get's changed aswell. DBT/BTU mix stuff won't get you OTA's
Given that i had a problem with restoring WhatsApp's chatlog when switching from 6.0 to 7.0 (which according to google and a post here, i'm the only one to have it), it's still advised to read up on app compatibility.
Also it's advised to do a factory reset after flashing, so everything is reset.
Tekkpriest said:
Everything works, except WifiCalling and VoLTE, if you switch to a british firmware.
So OTA's and the like won't be a problem. It's the same experience as if you were using your current german firmware in Israel.
For OTA's be sure to use the correct CSC file, so it get's changed aswell. DBT/BTU mix stuff won't get you OTA's
Given that i had a problem with restoring WhatsApp's chatlog when switching from 6.0 to 7.0 (which according to google and a post here, i'm the only one to have it), it's still advised to read up on app compatibility.
Also it's advised to do a factory reset after flashing, so everything is reset.
Click to expand...
Click to collapse
Thanks,
So I understand you won't any problems. And I don't really need the WiFi calling.
But about the VoLTE, do you mean that I'll loose the 4G ? Or do you something else?
About the CSC, I have to admit that I don't really know what it is. Is it a file that comes with the files that I should flash?
About the build number, I've just saw that there's a newer build of UK according to sammobile website: G930FXXU1DQB3 (released on the 06/02/2017), and the G930FXXU1DPLT (released on 16/01/2017) that I've stated in the original topic.
Is there a difference between them, should I go with the G930FXXU1DQB3 ?
Thanks again.
Semek said:
Thanks,
So I understand you won't any problems. And I don't really need the WiFi calling.
But about the VoLTE, do you mean that I'll loose the 4G ? Or do you something else?
About the CSC, I have to admit that I don't really know what it is. Is it a file that comes with the files that I should flash?
About the build number, I've just saw that there's a newer build of UK according to sammobile website: G930FXXU1DQB3 (released on the 06/02/2017), and the G930FXXU1DPLT (released on 16/01/2017) that I've stated in the original topic.
Is there a difference between them, should I go with the G930FXXU1DQB3 ?
Thanks again.
Click to expand...
Click to collapse
VoLTE is the "new" standard for calling.
Normally, when you call someone and don't use VoLTE, you fall back to the local 2G/3G network, which is slower and has lesser quality. Since many providers, atleast in my country, haven't completely switched over (for example prepaid customers still have the outdated 2G/3G calling), you should not notice much of a difference, since it's the same call quality as in 2013 for example. You will still understand people, as they will understand you.
4G / LTE data connectivity is unaffected by it and works without any problems, regardless of country etc. , unless you travel to america and use a local providers sim card there, where you might need the Snapdragon variant of the S7.
That being said, i flashed the newest firmware (DQB3) and it works flawlessly, except afromentioned WhatsApp problem. The only difference is, the update dated to the end of january is included, which fixes some stuff.
A CSC file contains country specific settings, like frequencies used, APN's and even carrier brandings are found in this file, which is why they might differ in size for different regions/carriers.
Because of that, VoLTE and wifi calling might not work, since, in this case, they use the BTU networks standard and you are not in the UK but Israel, aswell as probably not using a british provider.
Anyways back to your question:
There are 2 CSC files, the ROM`s CSC one and a HOME_CSC.
To receive OTA's, you will need to flash the normal CSC and not the HOME one. This will reset and wipe your device (backup all important stuff beforehand) and you get a device "fresh out of the box" bought in the UK.
The HOME CSC does not wipe your memory, but you won't receive OTA updates aswell, since your device hasn't changed it CSC and thus "is not an original BTU device".
So if you go down that route, which is perfectly acceptable and should not make any problems, you will have to flash updates manually via Odin.
Tekkpriest said:
VoLTE is the "new" standard for calling.
Normally, when you call someone and don't use VoLTE, you fall back to the local 2G/3G network, which is slower and has lesser quality. Since many providers, atleast in my country, haven't completely switched over (for example prepaid customers still have the outdated 2G/3G calling), you should not notice much of a difference, since it's the same call quality as in 2013 for example. You will still understand people, as they will understand you.
4G / LTE data connectivity is unaffected by it and works without any problems, regardless of country etc. , unless you travel to america and use a local providers sim card there, where you might need the Snapdragon variant of the S7.
That being said, i flashed the newest firmware (DQB3) and it works flawlessly, except afromentioned WhatsApp problem. The only difference is, the update dated to the end of january is included, which fixes some stuff.
A CSC file contains country specific settings, like frequencies used, APN's and even carrier brandings are found in this file, which is why they might differ in size for different regions/carriers.
Because of that, VoLTE and wifi calling might not work, since, in this case, they use the BTU networks standard and you are not in the UK but Israel, aswell as probably not using a british provider.
Anyways back to your question:
There are 2 CSC files, the ROM`s CSC one and a HOME_CSC.
To receive OTA's, you will need to flash the normal CSC and not the HOME one. This will reset and wipe your device (backup all important stuff beforehand) and you get a device "fresh out of the box" bought in the UK.
The HOME CSC does not wipe your memory, but you won't receive OTA updates aswell, since your device hasn't changed it CSC and thus "is not an original BTU device".
So if you go down that route, which is perfectly acceptable and should not make any problems, you will have to flash updates manually via Odin.
Click to expand...
Click to collapse
Wow, thanks for the reply!
I just want to be sure before I do it...
Are those the only options I need to check & load in Odin for flashing the new ROM?
Because I have few more files in the folder like BL and CP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So are AP and CSC enough?
Thanks!
Semek said:
Wow, thanks for the reply!
I just want to be sure before I do it...
Are those the only options I need to check & load in Odin for flashing the new ROM?
Because I have few more files in the folder like BL and CP.
So are AP and CSC enough?
Thanks!
Click to expand...
Click to collapse
Hi ahi,
I live in Israel too and flashed the UK firmware on my s7.
I install everything that was packed in the rar you download.
Nougat is awesome for our phone.
OrenGazala said:
Hi ahi,
I live in Israel too and flashed the UK firmware on my s7.
I install everything that was packed in the rar you download.
Nougat is awesome for our phone.
Click to expand...
Click to collapse
Hi Oren,
It's great to hear that everything works smoothly from someone from my country!
So, just to make sure, before I do anything stupid (or not, heh)... in Odin you selected & loaded the: BL, AP, CP and CSC?
Toda
Semek said:
Hi Oren,
It's great to hear that everything works smoothly from someone from my country!
So, just to make sure, before I do anything stupid (or not, heh)... in Odin you selected & loaded the: BL, AP, CP and CSC?
Toda
Click to expand...
Click to collapse
Select everything. Bootloader is very important for example. Otherwise you most likely will brick your phone
Anyways enjoy Nougat, i'm actually doing the same process again now, to see if i can get my WA Backup to work somehow.
Tekkpriest said:
Select everything. Bootloader is very important for example. Otherwise you most likely will brick your phone
Anyways enjoy Nougat, i'm actually doing the same process again now, to see if i can get my WA Backup to work somehow.
Click to expand...
Click to collapse
Just finished successfully the process and I'm on 7.0 now
Thank you, you've been very helpful. About the Whatsapp, looks like it restoring fine for me, or at least in the process (it's still downloading the media, the conversation were ok).
Semek said:
Just finished successfully the process and I'm on 7.0 now
Thank you, you've been very helpful. About the Whatsapp, looks like it restoring fine for me, or at least in the process (it's still downloading the media, the conversation were ok).
Click to expand...
Click to collapse
Very nice, good to know that it works for you.
Currently doing a downgrade with full wipe to 6.0.1 and then update via OTA. Let's see if that fixes it. Otherwise i have to start clean
Anyways, again enjoy Nougat. Should run very good out of the box
Semek said:
Just finished successfully the process and I'm on 7.0 now
Thank you, you've been very helpful. About the Whatsapp, looks like it restoring fine for me, or at least in the process (it's still downloading the media, the conversation were ok).
Click to expand...
Click to collapse
Hey,
I'm happy to know that everything works fine.
Enjoy!
Guys, what about Samsung Pay and Android Pay? Are they working fine? I am on XSA. Australia has Samsung pay and Android Pay working.
Sent from my SGP521 using XDA-Developers Legacy app
I was on vodafone phone with there bloatware so I flashed btu with csc not home csc once I flashes it wiped cache and reset phone then when it loaded up I got the new ota patch for nougat plus I've also got wifi calling.
---------- Post added at 07:07 PM ---------- Previous post was at 07:03 PM ----------
Just a question can some confirm if using stock Samsung browser when keyboard comes up but prodictive text don't work. But when using chrome it works?
I've got a question too. I would like to change my 6.0.1 on 7.0, also British stuff but I'm a little bit concerned about mixing XEO and BTU. Is it possible to mix 6.0.1 HOME_CSC XEO (latest) with 7.0 British BTU + PIT file from the 7.0 BTU Home (I would like to make factory reset and have my native CSC file)? Does it make difference to take PIT file from 6.0.1 or 7.0 Home file either?
venki5star said:
Guys, what about Samsung Pay and Android Pay? Are they working fine? I am on XSA. Australia has Samsung pay and Android Pay working.
Sent from my SGP521 using XDA-Developers Legacy app
Click to expand...
Click to collapse
For Samsung Pay, i can't confirm, but since Android Pay definitely works, Samsung Pay should work aswell, if you did not trigger Knox etc.
mimo2008 said:
I was on vodafone phone with there bloatware so I flashed btu with csc not home csc once I flashes it wiped cache and reset phone then when it loaded up I got the new ota patch for nougat plus I've also got wifi calling.
---------- Post added at 07:07 PM ---------- Previous post was at 07:03 PM ----------
Just a question can some confirm if using stock Samsung browser when keyboard comes up but prodictive text don't work. But when using chrome it works?
Click to expand...
Click to collapse
Just tested it, i have predictive text in either browser, or anywhere i do have a keyboard.
MalfiRaggraClan said:
I've got a question too. I would like to change my 6.0.1 on 7.0, also British stuff but I'm a little bit concerned about mixing XEO and BTU. Is it possible to mix 6.0.1 HOME_CSC XEO (latest) with 7.0 British BTU + PIT file from the 7.0 BTU Home (I would like to make factory reset and have my native CSC file)? Does it make difference to take PIT file from 6.0.1 or 7.0 Home file either?
Click to expand...
Click to collapse
You can mix it, but personally, i advice against it. Might reduce battery life, you will have to flash every update manually, since OTA does not work with a mix of XEO/BTU.
Also, since XEO and BTU share a common CSC file (they are OXA's, multipurpose CSC's) in most nougat roms around, you might need to root anyway to completely switch over, if a repartition + factory / cache reset won't work.
So to summarize, yes it's possible to use the HOME_CSC to avoid switching your CSC and wiping your phone. It's also possible to stay on a 6.0.1 CSC, but! there might be problems later.
If possible always do a fresh install and if your phone runs well currently, why not stay on Marshmallow? Depending on the current OTA release, which you might have to look up for your country, it might be better to wait a bit. Personally for me, it'd be a complete switch over, since i am too lazy to flash every update manually.
That being said, you won't need a PIT file going from 6.0.1 to 7.0, since it is included in the CSC. Pit files might be useful, if you want to downgrade and in some other cases, but not if you just want to upgrade. They include repartition infos, which are important, if you don't have a "4 file flash" (yucks, my english for explaining it better, sorry).
Personally for me, it'd be a complete switch over, since i am too lazy to flash every update manually.
Click to expand...
Click to collapse
Yeah, but that wouldn't be a problem for me, cuz I've been using custom ROMs manual flashing on my old fellow Galaxy S4, whenever update was avaiable but anyway, who doesn't want to make things easier?
So to summarize, yes it's possible to use the HOME_CSC to avoid switching your CSC and wiping your phone. It's also possible to stay on a 6.0.1 CSC, but! there might be problems later.
Click to expand...
Click to collapse
So what are the main drawbacks using BTU CSC that the XEO? Will it, paradoxically, drain more battery because of incompatibility of GSM frequencies?
If possible always do a fresh install and if your phone runs well currently, why not stay on Marshmallow?
Click to expand...
Click to collapse
Marshmallow works perfectly for my phone, especially for battery and performance but obviously, I'm curious whether Nougat would it make more perfect
Depending on the current OTA release, which you might have to look up for your country, it might be better to wait a bit.
Click to expand...
Click to collapse
Samsung consultant said to me that they EVEN DON'T KNOW when 7.0 will be relased for our country. That made me angry and I said to myself that I will take the matters into one’s own hands.
Pit files might be useful, if you want to downgrade and in some other cases, but not if you just want to upgrade. They include repartition infos, which are important, if you don't have a "4 file flash" (yucks, my english for explaining it better, sorry).
Click to expand...
Click to collapse
So, If I have only AP file, I will need to use PIT file for downgrading also, right?
And very well explained issue, it really helps me a lot in a certain level of understanding the given topic
MalfiRaggraClan said:
Yeah, but that wouldn't be a problem for me, cuz I've been using custom ROMs manual flashing on my old fellow Galaxy S4, whenever update was avaiable but anyway, who doesn't want to make things easier?
So what are the main drawbacks using BTU CSC that the XEO? Will it, paradoxically, drain more battery because of incompatibility of GSM frequencies?
Marshmallow works perfectly for my phone, especially for battery and performance but obviously, I'm curious whether Nougat would it make more perfect
Samsung consultant said to me that they EVEN DON'T KNOW when 7.0 will be relased for our country. That made me angry and I said to myself that I will take the matters into one’s own hands.
So, If I have only AP file, I will need to use PIT file for downgrading also, right?
And very well explained issue, it really helps me a lot in a certain level of understanding the given topic
Click to expand...
Click to collapse
Sorry for the late reply, work called.
Usually a BTU won't draw more battery or anything, since frequencies mostly are standard in every country. It's more like saved APN's etc. (which you can change manually via your phone's settings menu anyways). But as previously mentioned to the original poster, you can depending on where you live, loose out on VoLTE and Wifi-Calling, since those a carrier specific and usually not included in an unbranded ROM. If those are important to you, you probably want to stick with your current ROM, even if i do understand that new things are always fun. Even i did not wait for my carrier..
But having OTA updates and stuff like that is convenient, otherwise you'd have to flash every update like this one, which is why i recommend using a full BTU firmware, if you really wanna do it. Well, you don't have to flash it manually.. but it won't change since OTA updates are CSC based. So for example if Android 7.1 or another security patch will come out, you will need to wait until your XEO (Poland, i presume?) firmware get's the corresponding update, which according to you might take ages, since the original Nougat is not even out yet.
If you only have an AP file, i recommend using updato.com / samfirmware to download the current image of the BTU. Since you will need Bootloader and Modem files aswell (BL, CP respectively), aswell as the CSC file. I have checked though, your current CSC is included in the OXA (multipurpose CSC) of the BTU. So you might wanna flash a non BTU image first to change the CSC to something not included in the BTU one. Otherwise you will need root access to change it manually and this triggers Knox as we all know and thus your warranty is gone. And if you flash a non BTU image, be sure to factory reset / clear cache via recovery mode after installing and then let it boot normally, so the CSC change will take effect, afterwards flash the BTU image will all files and do the same. Be sure to backup your data beforehand, since they will get lost and do NOT use the HOME_CSC file. This one is for not changing the CSC at all and will retain your data. Use the ROM's CSC. Also always check the rom for your model, i have seen people who used a 935F (which is the edge) ROM on a flat S7 (which is 930F in europe mostly). But that's why i highlight it.
If you have further questions, i'll answer them to the best of my abilities
Oh and i almost forgot, you don't need a pit file . It's really just for more engineerical purposes as explained in ODIN. Current Marshmallow and Nougat Roms consist of 4 parts, which include the corresponding PIT.
I highly recommend not using the PIT file, if you don't know what it entails (you will need to look on the internet for it, since it will be quite lengthy if i explain). In short, as long as an update does not use a different partition layout and / or you mess up your partitions by yourself, you just don't need it. And doing afromentioned, would require extensive knowledge about Android anyways. As long as you don't root and modify your system yourself, you most likely will always be fine. And since rooting does have it's drawback (like some Apps not working due to security, Samsung warranty void etc), i'd not recommend it anyways, unless you are experienced
Sorry for the late reply, work called.
But as previously mentioned to the original poster, you can depending on where you live, loose out on VoLTE and Wifi-Calling, since those a carrier specific and usually not included in an unbranded ROM.
Click to expand...
Click to collapse
Np
Doesn't matter for me, I don't use them either, because I am on unbranded one from the very beginning
XEO (Poland, i presume?)
Click to expand...
Click to collapse
Yes, exactly.
If you only have an AP file, i recommend using updato.com / samfirmware to download the current image of the BTU.
Click to expand...
Click to collapse
No, I have 4 file package from Sammobile, but the previous question was about what could I do when I have only AP file. But I know this now
Since you will need Bootloader and Modem files aswell (BL, CP respectively), aswell as the CSC file. I have checked though, your current CSC is included in the OXA (multipurpose CSC) of the BTU. So you might wanna flash a non BTU image first to change the CSC to something not included in the BTU one.
Click to expand...
Click to collapse
For Example?? And If I want to make full switch over towards BTU, should I really need to flash something non - BTU or just pure BTU (with BTU CSC file)? And what if my carrier will release XEO 7.0 stuff... then would I need to flash the same non BTU/XEO stuff to change CSC again?
Oh and i almost forgot, you don't need a pit file . It's really just for more engineerical purposes as explained in ODIN.
Click to expand...
Click to collapse
I have used the PIT file when I was debranding, that is why I was asking about extended purposes Obviously, I haven't got extensive knowledge about android but I know just the basics (the reason why it looks like that is I am not programming anything, otherwise I would know more, much more).
And, using occasion... Since S7 ownership I was wondering how root would affect function "safe start". Would it be possible to bypass this function COMPLETELY after launch, on the rooted phone (For example: if someone could steal it and unluckily, had extensive android knowledge could bypass launch/start password, and, the worst, security lock, when my phone is fully rooted)?
Here is the link to the tmobile original thread
[ODIN] Stock Nougat Firmware [SM-G935T] S7 Edge
Instuctions provided by jrkruse (original post)
1. You need to be on Verizon Beta Nougat 2
2. In developer options turn on OEM unlock
3. Reboot to download mode
4. Load the files you downloaded in the corresponding slots in odin BL,AP CP, CSC the files are labeled this way
you dont use the G935TUVU4BQB1_Boot_Recovery_Image.tar.md5 until later
5. Install with odin the phone will reboot to recovery to finish the csc install
6. If the csc install in recovery fails reboot to bootloader in stock recovery
7. In odin reflash the CSC file in the CSC slot in odin. The phone will reboot to recovery again and install the csc files
8. Once the phone is done installing and wiping in recovery try and catch the phone as it reboots and reboot back to
download mode (PWR+Home+Vol Down )
9. Use odin Install G935TUVU4BQB1_Boot_Recovery_Image.tar.md5 in the AP slot
10. Let phone reboot and go through setup
11. During Setup you may have trouble typing info in the setup boxes the keyboard has some bugs in setup. I recommend skipping
adding any accounts and do it after your through setup. Or use the alternative method to find your google account
12. Once through setup download 4G LTE Switch and use to Change Network to LTE/CDMA auto (PRL)
13. I recommend downloading Package Disabler Pro (It Works now) and disable all Tmobile Apps
I found samsung pay wasnt working I found that the tmb bootloaders and persist.img needed to also be flashed I made a new odin flashable package and install instructions. All seems to work now except of course volte and wifi calling.
Explanation why you need to be on nougat beta 2
Download:
TMOBILE_NOUGAT_VZW.ZIP
ODIN v3.12.3.zip
Possible Issues and solutions :
Q: after flashing the bootloaders and persist.img, it broke all data and calls and texts again.
A: they need to be all flashed at same time. Maybe Wipe data and it might work
Q: The Google "email or phone" text input box still only accepts one letter and any extra letters overwrite the previous letter typed.
A: The samsung keyboard will work fine if you just goto settings on the keyboard to language and types and change to US english.
Q: So the question is..... this worth flashing or wait for vzw?
A: Other than no volte this definitely the best running Rom so far. It is much better than beta
Q: 13. I recommend downloading Package Disabler Pro (It Works now) and disable all Tmobile Apps
Care to share your list?
A: List of Tmo apps to disable
Q: Except MMS isn't working, for me anyways. VoLTE isn`t working.
A: I got volte working and video calling maybe this will help mms for you
Download App shortcut maker from playstore
Select all activities find IMS Settings and create shortcut
Open the ims settings from the created shortcut
Choose Ims service switch
Click on MMTEL switch
Click on RCS switch
Under MMTEL section I enabled all the options
Q: Cant get this thing to flash CSC...just keep getting the dm-verity error 0x02.
A: 1:Flash all 4 files in zip.
2:let reboot and see if you get dm verity error.
3:if you get the error than reboot to bootloader and reflash all 4 again.
4:after it reboots again it will say error.
5:reboot to bootloader and flash the csc again.
Q: in 4g lte switch, i dont see the option for lte/cdma auto. could this stuff be because csc didnt flash correctly?
A: if you have the verizon data icons you know the 4g lte then it flashed correctly. If you see data icons that ate not verizon then it didnt flash correctly.
When every one is starting over are you flashing a pit file when going pack to ph1. If not you need too.
P.S. All credits goes to jrkruze. :good:
You mentioned to install Nougat beta first before installing t mobile firmware. Is that necessary? Also, any link for Verizon apn?
Sent from my SM-G935V using Tapatalk
junear said:
You mentioned to install Nougat beta first before installing t mobile firmware. Is that necessary? Also, any link for Verizon apn?
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Look at you apn settings and just copy it. I didn't mention about to install nougat beta, I mentioned that it was installed successfully on nougat beta and that you must be on latest bootloader.
Okay so I have T-Mobile Nougat installed on my device, and I've changed my VPN over to VZWINTERNET, and I can't seem to get anything working (calls or data).
I'll continue to toy around with things though.
FoxyDrew said:
Okay so I have T-Mobile Nougat installed on my device, and I've changed my VPN over to VZWINTERNET, and I can't seem to get anything working (calls or data).
I'll continue to toy around with things though.
Click to expand...
Click to collapse
Same here
is there maybe a need to change to verizon csc?
j3ffm1ll said:
is there maybe a need to change to verizon csc?
Click to expand...
Click to collapse
are you meaning swap the pi3 csc to odin vice the csc that came with the firmware. I guess we can try that. worst thing no load, flash back stock.
justinsch03 said:
are you meaning swap the pi3 csc to odin vice the csc that came with the firmware. I guess we can try that. worst thing no load, flash back stock.
Click to expand...
Click to collapse
just a thought I would try it but I am at work and have to have use of my phone while I am here lol
FoxyDrew, radelon from what firmware did you flashed ?
spiderkr said:
FoxyDrew, radelon from what firmware did you flashed ?
Click to expand...
Click to collapse
The T-Mo one you posted. Odin with ap,bl,cp and csc selected.
After toying with tons of things on the Tmo firmware, I tried booting into Odin, and flashing the Verizon pi3 CSC. That gave me a bootloop. I then tried reflashing the entire Tmo Nougat with Odin, but replacing the CSC again with Verizons, same bootloop. So now my phone is being flashed back to the trusty U MM.
I can only assume now that running the Tmo firmware on VZW will require root to make CSC edits. But Verizon will release our own Nougat before we get root.
Now I guess it's just a race between Verizon releasing 7.0, and the G935U getting it.
$50 on Verizon.
Edit: After flashing the G935U firmware again, after the first boot I was greeted with a message saying "your device must update to use new features from your SIM card." And I booted to a weird all blue screen with a big SIM card on it. I've never seen anything like that. I'm not sure if the Tmo firmware messed with stuff, so I'm going to fully flash the G935V firmware, THEN reflash the G935U firmware, just in case the G935T firmware messed something up.
they also did something to disable all package disabler apps even if you go back to MM they dont work. They screwed us goood on this
so @spiderkr were you able to get it working or just going off of other reports?
radelon said:
The T-Mo one you posted. Odin with ap,bl,cp and csc selected.
Click to expand...
Click to collapse
i mean at what firmware where you before you flash t-mo nougat?
spiderkr said:
i mean at what firmware where you before you flash t-mo nougat?
Click to expand...
Click to collapse
Beta 2 Verizon Nougat
Unable to select network
Under "Network Operators" I selected Verizon Wireless, waited 5 minutes, and now got Unable to select network. Then, maybe a minute or so later, it says "Unable to connect. Try again later." Is there a way around this?
jrkruse said:
they also did something to disable all package disabler apps even if you go back to MM they dont work. They screwed us goood on this
Click to expand...
Click to collapse
I noticed this too, thought I was going crazy lol. That was the only think keeping me from rooting, and considering how horrible root is on this phone, I'm going to Verizon tomorrow to get a Pixel.
Im messing with it I got lte can make and receive phone call receive text but cant send
jrkruse said:
Im messing with it I got lte can make and receive phone call receive text but cant send
Click to expand...
Click to collapse
awesome!! getting closer...
jrkruse said:
Im messing with it I got lte can make and receive phone call receive text but cant send
Click to expand...
Click to collapse
How'd you manage to do that? Still can't get anything to work on my end...
I have the SM-G930UP baseband version G930PVPS4BQE1
I am preparing to flash the universal firmware, but with the T-Mobile modem. The goal is a phone with the U firmware and the T-Mobile modem.
Download and install Samsung USB drivers: http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Odin utility: https://odindownload.com/SamsungOdin/
Latest SM-G930U firmware files for “USA (XAS)”:
G930UUEU4BRD1_G930OUYM4BRD1_XAS
All U variants have the same baseband etc. numbers , so I assume it doesn't matter which one I use.
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/
Latest T-Mobile SM-G930T firmware files:
G930TUVS4BRC1_G930TTMB4BRC1_TMB https://www.sammobile.com/firmwares/galaxy-s7/SM-G930T/
The plan is to back up all data first, extract the all the files (Odin, drivers, and both U and T archives). Install the Samsung USB drivers.
Next steps:
Connect phone to PC.
Shut down phone: Hold Home and Volume-Down buttons while pressing the power button. Press Volume-Up when prompted to place phone in download mode (whatever it’s called).
Open Odin. Wait for Com connected prompt.
Click BL button. Select the SM-G930U BL file.
Click AP button. Select the SM-G930U AP file.
Click CP button. Select the SM-G930T CP file.
Click CSC button. Select the SM-G930U CSC (NOT HOME_CSC) file to wipe and factory reset the phone.
Click Start and wait for Odin to say “Complete.”
Any feedback? Suggestions? Anything I missed?
what baseband are you currently on?
why would you want T-mobile modem? anything wrong with U-version?
turbozapekanka said:
why would you want T-mobile modem? anything wrong with U-version?
Click to expand...
Click to collapse
In some of the reading I have done it appears advantageous to have the carrier modem of the service provider you use; I'm assuming because the carriers tweak the modem for use with their particular infrastructure.
I don't know if that's true, but I have seen a number of posts to that effect. It sounds logical and I figure it can't hurt as long as it works.
InsanePostman said:
what baseband are you currently on?
Click to expand...
Click to collapse
Mr. _Happy said:
I have the SM-G930P baseband version G930PVPS4BQE1
Click to expand...
Click to collapse
Software version is the same. G930PVPS4BQE1 it's from May 2017.
Mr._Happy said:
In some of the reading I have done it appears advantageous to have the carrier modem of the service provider you use; I'm assuming because the carriers tweak the modem for use with their particular infrastructure.
I don't know if that's true, but I have seen a number of posts to that effect. It sounds logical and I figure it can't hurt as long as it works.
Click to expand...
Click to collapse
I doubt it.
I've been using U-version (converted from SM-G930P) on T-mobile for a year and found no issues whatsoever.
I was reading the opposite, something like U-version has more LTE bands unlocked (which makes sense as it should work with all carriers)
Also someone here claimed it has extra bands for Europe. like band 7, 20
turbozapekanka said:
I doubt it.
I've been using U-version (converted from SM-G930P) on T-mobile for a year and found no issues whatsoever.
I was reading the opposite, something like U-version has more LTE bands unlocked (which makes sense as it should work with all carriers)
Also someone here claimed it has extra bands for Europe. like band 7, 20
Click to expand...
Click to collapse
Interesting. That seems logical too.
Unfortunately I may not be flashing anything as every time I have downloaded firmware from SAMOBILE and extracted it I have got an error message that the AP portion has a problem. If I "retry" it gives me the same error. If I "skip" it unpacks everything except the AP file. I have tried several times with multiple downloads. Each one took the full two hours to download, so it's been a lengthy process with no results.
When you flashed the G930U which variant did you use?
Mr._Happy said:
Interesting. That seems logical too.
Unfortunately I may not be flashing anything as every time I have downloaded firmware from SAMOBILE and extracted it I have got an error message that the AP portion has a problem. If I "retry" it gives me the same error. If I "skip" it unpacks everything except the AP file. I have tried several times with multiple downloads. Each one took the full two hours to download, so it's been a lengthy process with no results.
When you flashed the G930U which variant did you use?
Click to expand...
Click to collapse
I flashed version G930UUEU4APL2 with odin 3.12.3
It was back in January 2017. Note the number 4 in the version. This indicates bootloader version.
I believe you can no longer flash this version if your current version has 5 (or any greater number) in place of 4 because you're not allowed to downgrade the bootloader version.
Sprint is known to bump the bootloader version from 4 to 5 for (supposedly) blocking this type of conversions of their branded phones.
turbozapekanka said:
I flashed version G930UUEU4APL2 with odin 3.12.3
It was back in January 2017. Note the number 4 in the version. This indicates bootloader version.
I believe you can no longer flash this version if your current version has 5 (or any greater number) in place of 4 because you're not allowed to downgrade the bootloader version.
Sprint is known to bump the bootloader version from 4 to 5 for (supposedly) blocking this type of conversions of their branded phones.
Click to expand...
Click to collapse
Mr._Happy said:
I have the SM-G930P baseband version G930PVPS4BQE1
Click to expand...
Click to collapse
Sprint is currently on bootloader 6, actually. Crappy obstructionist commercialism specifically to block people converting.
I have been denying and rejecting the software updates since May of 2017 which is when I got that software version, so your G930UUEU4APL2 firmware from January would not work on this phone as my Sprint firmware is more recent.
I should be able to flash the most recent version of G930U, however. I just can't seem to download one that will extract the AP portion. It's really frustrating.
Try this https://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930uueu4apl2-sm-g930u-t3535230
You should be able to flash any firmware as long as the bootloader version is the same
For newer firmwares you may need to use the latest Odin version (3.13.x)
---------- Post added at 12:15 PM ---------- Previous post was at 12:07 PM ----------
I wonder why did you choose XAS version.
I also remember back in time I downloaded two versions of U-firmware (SPR and XAA) and compared the files they appeared identical.
turbozapekanka said:
I doubt it.
I've been using U-version (converted from SM-G930P) on T-mobile for a year and found no issues whatsoever.
I was reading the opposite, something like U-version has more LTE bands unlocked (which makes sense as it should work with all carriers)
Also someone here claimed it has extra bands for Europe. like band 7, 20
Click to expand...
Click to collapse
What ROM have you been running?
Looks like slim pickins for the snapdragon chipset.
I assume all Exynos ROMs would obviously not work .
I have a SM-G930VL that I flash the G930U firmware . Much better
Stock
turbozapekanka said:
You should be able to flash any firmware as long as the bootloader version is the same
Click to expand...
Click to collapse
This is what I was saying. The last Sprint update I did on the phone was May 2017. I have been dismissing the update nag since then. Which means I could flash any G930U firmware with a date later than May 2017 with the same bootloader number.
Sprint has been trying to block this: their bootloader number is currently on 6, all the other carriers are on 4.
turbozapekanka said:
For newer firmwares you may need to use the latest Odin version (3.13.x)
Click to expand...
Click to collapse
Yep. The link I used to download the latest version was in the first post of this thread. 3.13 worked just fine.
The problems I was having had to do with the my computer, but I solved them and was able to to flash the latest version of G930U.
The phone is snappy and without the annoying lag.
Call quality improved immediately. With the Sprint firmware on the T-Mobile network there was a glitch with using the voicemail icon on the dial screen - it would fail to call the voicemail and give an incomplete call error; the workaround was to call myself from contacts and enter my pin to get to my voicemail. Now the voicemail icon on the dialer takes me to voicemail without a hitch. When calling it doesn't have a 15 - 20 second wait before ringing the number (the top left of the status bar would read "Attempting"). Internet reception is also better especially in the NYC subway.
Also as soon as my phone went from Sprint to T-Mobile I could no longer send or receive pictures via text. Apparently Sprint firmware wasn't interested in sending MMS messages anymore, but with the U firmware they work just fine and regular texts go through more quickly as well.
So far battery life is about the same as far as I can tell, maybe a marginal improvement. Nothing to call home about.
But mostly I seem to get the overall desired reception improvement: it stopped dropping calls, and the call quality is solid and the undersea world that had been happening with the Sprint firmware is gone.
Also the fingerprint scanner is working better.
It's much improved.
I REALLY like how it seemlessly goes from voice on network to voice on WiFi.
Question: will this get OTA updates? Is it fantasy to think the G930U will get Oreo?
I am interested in testing the various towers, most frequent LTE bands, signal strength, and handset radios. Is there a thread for that or any apps you know of?
Mr._Happy said:
Question: will this get OTA updates? Is it fantasy to think the G930U will get Oreo?
Click to expand...
Click to collapse
Yes it will get OTA updates including Oreo. U-version lags behind branded versions in this regard though.
i'm just got the oreo update - installing right now (us cellular)
i have tmobile g930t
if i shift to U , will volte work?
because i am unable to use volte in india now
Hey guys so I am brand-new to all this but need to convert my g930p to g930u. I just want to clear this up: because my software version is Q930PVPU6CRE7, I won't be able to flash the version OP used but must find a version with a 6 in it?
I'm in the same boat with my wife's phone. Limited bands available meaning it's on 3G more often than not, and MMS won't work if connected to WiFi. Not to mention the sprint junkware... is there any way to change from G930P to a G930U firmware if the phone is currently on bootloader version 6? I don't mind rooting...
I flashed G930U on G930P but network still not working. It shows unknown network and Radio Off. Mobile can read SIM menu and Contacts but no signal. Any help please?
EDIT: Now I know that changing ROM or rooting does not network unlock.
Mr._Happy said:
I have the SM-G930UP baseband version G930PVPS4BQE1
I am preparing to flash the universal firmware, but with the T-Mobile modem. The goal is a phone with the U firmware and the T-Mobile modem.
Download and install Samsung USB drivers: http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Odin utility: https://odindownload.com/SamsungOdin/
Latest SM-G930U firmware files for “USA (XAS)”:
G930UUEU4BRD1_G930OUYM4BRD1_XAS
All U variants have the same baseband etc. numbers , so I assume it doesn't matter which one I use.
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/
Latest T-Mobile SM-G930T firmware files:
G930TUVS4BRC1_G930TTMB4BRC1_TMB https://www.sammobile.com/firmwares/galaxy-s7/SM-G930T/
The plan is to back up all data first, extract the all the files (Odin, drivers, and both U and T archives). Install the Samsung USB drivers.
Next steps:
Connect phone to PC.
Shut down phone: Hold Home and Volume-Down buttons while pressing the power button. Press Volume-Up when prompted to place phone in download mode (whatever it’s called).
Open Odin. Wait for Com connected prompt.
Click BL button. Select the SM-G930U BL file.
Click AP button. Select the SM-G930U AP file.
Click CP button. Select the SM-G930T CP file.
Click CSC button. Select the SM-G930U CSC (NOT HOME_CSC) file to wipe and factory reset the phone.
Click Start and wait for Odin to say “Complete.”
Any feedback? Suggestions? Anything I missed?
Click to expand...
Click to collapse
if i try this method to convert smg930u to smg930f will it work cuz meh need root ?
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.
(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