Related
Hello, All!
I have a G930V (Verizon S7) Non-EDGE, and I wan't to convert it to a G930U Unbranded (Or at least bloat free).
## BY THE WAY ##
Yes, I have seen other threads on this topic. Doesn't answer my confusions though.
Threads by:
tvm2487 (G930U Firmware)
James.Markham0757 (Can someone send me in the right direction...)
DeathAngel66669 (Using SamFirm to download SM-G930U-G930UUEU2APG9...)
## BY THE WAY ##
So anyways here are my questions.
##
1. Looking through Sammobile or Updato I see that a the newest version is
(G930UUEU2APEH) on (XAA), Would that work for the VZW Variant if not, What can i use?
2. Regarding my phone's below details would i be able to convert it to any of the 'U' Firmwares?
3. I don't wan't to trip any security features or mess with KNOX, really don't want to root.
Really just wan't to keep my warranty. Granted I will probably lose that by not using VZW firmware.
4. I thought flashing firmwares not similar to your phone will brick it permenantly. Why does the 'U' firmware run on the 'V'?
5. If i can flash the firmware (Odin?), What should i tick in the boxes for it to flash perfectly fine without errors?
Given this would be my first Samsung Tweaking.
6. Besides the Verizon bloat, What other cons are in the 'U' firmware that I should know about before doing the procedure?
7. Chances of bricking the phone? Would it be reversible?
##
My current S7 VZW Details:
Model: SM-G930V
Ver: 6.0.1
Patch Level: October, 1, 2016
Baseband Ver: G930VVRU4API3
I appreciate the help and your time. Thanks !
1. Looking through Sammobile or Updato I see that a the newest version is
(G930UUEU2APEH) on (XAA), Would that work for the VZW Variant if not, What can i use?
I don’t think it would flash as it is bootloader 2(5th character from right) latest firmware is 4!
2. Regarding my phone's below details would i be able to convert it to any of the 'U' Firmwares?
From what I understand all the USA variants of the Galaxy S7's are the same hardware
3. I don't wan't to trip any security features or mess with KNOX, really don't want to root.
Really just wan't to keep my warranty. Granted I will probably lose that by not using VZW firmware.
I have an AT&T branded S7 SM-G930A and have flashed the U firmware and used it for a while. I have now switched carriers to T-Mobile used the U firmware without issues and now flashed the T-Mobile firmware and it works fine. KNOW IS NOT TRIPPED.
4. I thought flashing firmwares not similar to your phone will brick it permenantly. Why does the 'U' firmware run on the 'V'?
Not sure, Odin may just fail to complete install?
5. If i can flash the firmware (Odin?), What should i tick in the boxes for it to flash perfectly fine without errors?
Given this would be my first Samsung Tweaking.
I never had luck flashing the HOME-CSC file, had to use straight CSC.
6. Besides the Verizon bloat, What other cons are in the 'U' firmware that I should know about before doing the procedure?
One thing I did notice is the visual voicemail app tends to work better when using the specific carrier firmware(both AT&T & T-Mobile).
I'm using T-Mobile and I don't see a need to go back to U at this time as their is not much bloat on the T-Mobile firmware.
7. Chances of bricking the phone? Would it be reversible?
##
I just installed T-Mobile Nougat on my phone and got the error on phone and it was stuck on “You will need to use Smart Switch Recovery” to fix phone! SCARY!!! I managed to finally get firmware installed and running!
Understood.
When I get home today I'll try to install a newer version from SamMobile.
Updato has older versions. Sammobile has the latest which is.
G930U with code (VZW) on
G930UOYM4APL2
(https://www.sammobile.com/firmwares/download/118975/G930UUEU4APL2_G930UOYM4APL2_VZW/)
Would this be compatible?
G930UUEU4APL2 is the latest U-firmware. Everything flashes correctly, it won't trip KNOX, and it is super easy to go back to G930V firmware if you decide you want to send it back for warranty. You can't brick the phone by flashing signed files with Odin. The bootloader won't allow Odin to flash anything that could brick it.
I had already started replying before you posted above me. I'd recommend using my link to the firmware, as Sammobile downloads take FOREVER.
I see, I'm glad.
So, What would i need to make sure to do and not do in Odin 3.11.1?
AP/BL/CP/CSC from your zip? Just flash everything or only certain things?
Re-partition tick box? yes or no?
Flash all four of those files and DON'T CHANGE ANY Odin settings.
Okay. I just flashed it and now my phone repeatedly keeps booting into recovery.
The recovery logs and the red text at the bottom says:
dm-verity verification failed
Need to check DRK first...
Any ideas?
##PREVIOUS##
I think it might have to be because I used HOME_CSC rather than CSC.
What's the difference between both? Can i revert later?
##PREVIOUS##
@CVertigo1
I reflashed with the CSC file rather than the HOME_CSC file as according to your instructions in your thread (Latest G930U Firmware) and it worked perfectly fine!
KNOX is still at 0x0 and warranty void is fine.
( https://forum.xda-developers.com/verizon-galaxy-s7/how-to/g930u-firmware-pl2-g930v-success-t3558214 )
No bloat, amazingly fast, and some features i like are present. I'll report back to your thread on the battery life when i get more time with it.
I appreciate your patience.
(Will post screenshots later).
Home_CSC doesn't wipe user data, which causes issues when swapping firmware. That's what caused your bootloop.
Followed this, today, was sick and tired of the damn Verizon bloat slowing the phone down.
The phone runs faster - notably faster.
After installing the SIM, the phone returns, "Your device will restart to configure features supported by the new SIM card."
And then" It's useless. If I hard-power reset it, and take out the SIM, it's viable - it's just useless otherwise.
Phone is a G930V, flashed to G930U.
Any Suggestions? The phone is *NOT* rooted, so I can't easily take out or rename the AutoPreconfig.apk package.. Argh.
Will I get the android nougat update on this ROM?
Just converted G930V to G930U, all 100% working here in the UK. Fully debranded and no verizon warning about sim change. perfect
Mind telling me what thread you used to find the latest firmware? This forum for the phone is so rarely used anymore, it's hard to tell what info to go even go on anymore.
Is PL2 the latest for 930U? I'm VZW but US, not UK
Has anyone had success using the U modem with the newer firmware on a carrier outside of Sprint?
There is an article here about it and you can disable any warning messages with a package disabler.
Since the U firmware doesn't work, just wondering if anyone has tried this.
I have one I am willing to sacrifice if you want me to test something out. I'd like to try and flash it to Verizon for a friend.
If doesn't have the latest firmware, I wouldn't even bother because you can just put the offical u or verzion firmware on it.
Here is the process in a nutshell:
1. Odin a dec/Jan firmware...like QJ3. But replace the cp slot with the file from the latest u firmware. This is the modem file.
2. When your phone starts, you will receive a pop up message, just hit cancel.
3. Install a package disabler like sabs, bk, adhell2. Disable securitylogagent . This should remove the annoying message. Sabs takes a little effort to setup, but you may need it for the disabler part. Restart after disabling.
4. Pop in verizon sim. See if the additional bands are unlocked.
If you fail, you can always just odin back to a v5 sprint firmware. But don't try it unless you are stuck on the current firmware and your phone is doing nothing. It won't brick your phone.
While the firmware is not downloadable, modem files can downgrade one major update.
This worked for me, but I only have sprint and haven't tried it elsewhere.
Thanks for the info. I just screwed up and updated to the latest firmware. So with that said the sacrificial lamb still stands...
V3racious said:
Thanks for the info. I just screwed up and updated to the latest firmware. So with that said the sacrificial lamb still stands...
Click to expand...
Click to collapse
Like I said, I see the additional bands, but have no idea if they are useable since sprint doesn't use them.
lvpre said:
If doesn't have the latest firmware, I wouldn't even bother because you can just put the offical u or verzion firmware on it.
Here is the process in a nutshell:
1. Odin a dec/Jan firmware...like QJ3. But replace the cp slot with the file from the latest u firmware. This is the modem file.
2. When your phone starts, you will receive a pop up message, just hit cancel.
3. Install a package disabler like sabs, bk, adhell2. Disable securitylogagent . This should remove the annoying message. Sabs takes a little effort to setup, but you may need it for the disabler part. Restart after disabling.
4. Pop in verizon sim. See if the additional bands are unlocked.
If you fail, you can always just odin back to a v5 sprint firmware. But don't try it unless you are stuck on the current firmware and your phone is doing nothing. It won't brick your phone.
While the firmware is not downloadable, modem files can downgrade one major update.
This worked for me, but I only have sprint and haven't tried it elsewhere.
Click to expand...
Click to collapse
Can I do this if I am on the latest firmware?
V3racious said:
Can I do this if I am on the latest firmware?
Click to expand...
Click to collapse
Yes, you are just changing the modem [ap slot]. It worked for me and the bands show up for me as options, but no way of knowing they actually work. I have sprint, so testing a carrier with different bands is the only way.
1. Thanks to @FP_XDA and GSMZambia for the great directions found here
2. The other stuff and ideas:
The above method does put the U firmware on your phone. I had trouble getting it to connect to the network. I did try different combinations of files in the AP tar; CP; and CSC, but it would either not connect after a factory data reset or loop with the message about my SIM has changed, please restart.
I tried just flashing the following combinations through flashfire, but maybe this is a Sprint SIM issue and it works on other SIM cards; however, I have Sprint.
The U firmware seemed to work fine on the software. Including boot.img in flashfire would take away the eng_boot and root. I just had trouble connecting to the Sprint network.
Do you need to use the v5 combo file and flash a certain CP/CSC before going through the rooting steps? The U firmware CSC file is different in size, so is it a partition (PIT) issue since that will write the cache.img.ext4 file and those vary in size from stock to the U? Is there a certain order to flash in flashfire to get it to work properly?
Anyway, I downloaded several U CSC firmwares (XAA, XAS, SPR (last two are sprint)), but ran into some network issue every time. The operating system seemed stable, but the lack of connection and some random entries under settings make it so close, but yet so far.
I don't mind the Sprint firmware, but can you unlock additional LTE bands if you use the stock sprint firmware on another carrier?
Thanks for any help!
Here is more info about the Settings submenu options:
Here is some more detailed info:
The submenus under settings give me options like K twophoneservice; T roaming; Giga LTE. I think it is CSC related as those carriers are Korean based. I think this may be my issue along with a few others I've seen on reddit. Just wondering why it says that though. I used the G930U version, so not sure why this would appear.
Any help or suggestions?
Thanks
Bootloop
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Aggiedude said:
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Click to expand...
Click to collapse
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
lvpre said:
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
Click to expand...
Click to collapse
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
XMayhem2099 said:
7. Disable the following packages via bk or adhell
Chameleon
Sprint OMADM
Sprint OMADM Phone Interface
MDMApp
SecurityLogAgent
Security Policy Updates
Security Storage
Click to expand...
Click to collapse
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
elesbb said:
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
Click to expand...
Click to collapse
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
lvpre said:
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
Click to expand...
Click to collapse
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed?
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
elesbb said:
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD.
Click to expand...
Click to collapse
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
Click to expand...
Click to collapse
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed? .
Click to expand...
Click to collapse
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
Click to expand...
Click to collapse
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
lvpre said:
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
Click to expand...
Click to collapse
Yeah I am currently rooted with the U firmware BL4. I want to upgrade to Oreo, hoping for performance improvements, better battery, etc. But I guess since the Oreo U firmware is still BL4, I can just downgrade if I can't get root back.
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
Click to expand...
Click to collapse
I never mentioned a bootloop? Is this about something else? The point I am trying to address is the loss of Sprint connectivity after flashing eng boot. This is because of the packages that need to be disabled.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
Click to expand...
Click to collapse
So you flash everything, eng boot, and are currently rooted. You then flash the provided file via flash fire, factory reset, and now you no longer are able to connect to Sprint network? When you say "can't connect to Sprint network", are you referring to data or to Sprint network entirely? If you go under your "about phone" section, what does your IMEI and phone number display? Don't actually type it here, but it should be something comprehensible. It shouldn't say "unknown" or a bunch of zeros, etc. [/quote]
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
Click to expand...
Click to collapse
True..
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
Click to expand...
Click to collapse
I do. A lot of people want to be back to BL4. There is NO difference in the newer bootloaders EXCEPT a special "key" type of thing that prevents downgrading. That is the only thing different. This is why the U firmware is still on BL4 despite having an Oreo update. Sprint changes the BL version just so people like us have extra hurdles to overcome when we want something different. Its very stupid tbh.
But, I would like to help you guys out, however, I AM NOT upgrading to the BL5/6. Noway nohow.
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
lvpre said:
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
Click to expand...
Click to collapse
Hmm. That's weird. What does your about phone section say for IMEI and phone number? Everything good? I wonder if something is affecting the PRL. Try updating that via settings menu before you flash the firmware and factory reset. The CSC shouldn't really affect that part. I have changed mine multiple times to just eff around and see what/if anything changed. Its more for the phone to know what menu options are available and such. For instance, call recording shows up when its not a US branded carrier.
Sadly I will never flash the newer BL. But I will definitely keep trying via the thread and if you would like to discord or something similar I would be down. School starts in about 2 weeks so I'm basically free till then
sim boot loop
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Aggiedude said:
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Click to expand...
Click to collapse
Thanks for posting this!!! I'm glad that I wasn't the only having this issue. I tried it again using a different method and still got the SIM boot loop. This method probably works great if you have anything other than Sprint or Sprint MVNO, but something is conflicting like it does during a typical root of the G930P. Anyway, hopefully, someone else will be able to figure this out.
I know these are much tougher to find - can't be obtained from SamFirm or SamMobile. So I'll be uploading one for each bootloader version. Firmware is universal on U models so you can use the other 4 files from any other matching collection. Can probably even mix and match builds, if you can't find files for the exact same build. Can't mix and match bootloaders though, so the other 4 files have to at least be from the same bootloader.
USERDATAs for any other CSCs can be gotten from SamFirm - for the latest version. If you need an old USERDATA for a CSC that's not commonly found on SamMobile (ACG, LRA, TFN, etc), let me know and I can probably get it.
https://www.androidfilehost.com/?w=files&flid=283206
Can I use the userdata file for G55USQU5CRF5 with the other four files being from the build G55USQS5CRF5? I'm not sure what the difference between SQU and SQS is, and if it is significant. Thank you!
zeiguy17 said:
Can I use the userdata file for G55USQU5CRF5 with the other four files being from the build G55USQS5CRF5? I'm not sure what the difference between SQU and SQS is, and if it is significant. Thank you!
Click to expand...
Click to collapse
Yes, you can. There basically is no difference
I'm begging someone to help me. I flashed my AT&T S8+ to the G955U1 unlocked firmware, then got accepted into the beta and installed it via OTA update. I now want to go back to a AT&T rom so I can have stuff like Wi-fi calling and VOLTE back. I've tried so many different roms with ATT userdata and they all fail with ODIN. I'm guessing its something to do with bootloader version. Is there any way I can get back to a AT&T ROM from the G955U1 Pie beta firmware.
sean8102 said:
I'm begging someone to help me. I flashed my AT&T S8+ to the G955U1 unlocked firmware, then got accepted into the beta and installed it via OTA update. I now want to go back to a AT&T rom so I can have stuff like Wi-fi calling and VOLTE back. I've tried so many different roms with ATT userdata and they all fail with ODIN. I'm guessing its something to do with bootloader version. Is there any way I can get back to a AT&T ROM from the G955U1 Pie beta firmware.
Click to expand...
Click to collapse
Well the beta has to still be Bootloader 5, so just flash any 5 build
iBowToAndroid said:
Well the beta has to still be Bootloader 5, so just flash any 5 build
Click to expand...
Click to collapse
I finally managed to get Odin to flash a ROM. All of them I tried were bootloader 5. But now the problem is I cant get OTA updates. My phone is back to being a AT&T one with the AT&T boot screen and wi-fi calling etc etc. But everytime I check for updates it says its up to date even though I have CRL1 and the latest AT&T firmware is U5CSA4. I would update form SD card but that wipes the phone every time. I had to do that 4 or 5 times just to get to CRL1 because it kept saying my phone is up to date.
sean8102 said:
I finally managed to get Odin to flash a ROM. All of them I tried were bootloader 5. But now the problem is I cant get OTA updates. My phone is back to being a AT&T one with the AT&T boot screen and wi-fi calling etc etc. But everytime I check for updates it says its up to date even though I have CRL1 and the latest AT&T firmware is U5CSA4. I would update form SD card but that wipes the phone every time. I had to do that 4 or 5 times just to get to CRL1 because it kept saying my phone is up to date.
Click to expand...
Click to collapse
1. AT&T phones don't OTA if you're using a carrier other than AT&T - even their own MVNOs
2. If you are using AT&T, OTA rollouts are staged. It just came out less than a week ago, so your phone might not have been green-lit yet
3. Both 1 and 2 are really irrelevant anyways, because you can just Odin flash any update you want. Using HOME CSC will ensure data isn't wiped
iBowToAndroid said:
1. AT&T phones don't OTA if you're using a carrier other than AT&T - even their own MVNOs
2. If you are using AT&T, OTA rollouts are staged. It just came out less than a week ago, so your phone might not have been green-lit yet
3. Both 1 and 2 are really irrelevant anyways, because you can just Odin flash any update you want. Using HOME CSC will ensure data isn't wiped
Click to expand...
Click to collapse
I am using AT&T. I know rollouts are staged but I've never had it tell me my phone is up to date when it is 7 versions behind which it was because I had to start at CRF5 since that is the newest AT&T Userdata file I could find. I checked after doing the update from SD card method each time, making sure to put the date on my phone forward since AT&T only lets you manually check once a day. No matter what it said I was up to date despite being several versions behind.
I'm gonna try using Odin to flash one more time because not being able to do OTA update is a HUGE PIA. Dose it matter that the user data is called "ATT_G955USQU5CRF5" despite the firmware being USQS because I couldn't find a USQUCRF5 and besides AT&T's update history shows USQSCRF5 anyways. What I did was downloaded a verizon G955USQS5CRF5 ODIN file (because for some reason AT&T odin files are really hard to find) and replaced the Verizon user data with the AT&T one.
Also if I flash say CSA4 verizon with the verizon user data the put my AT&T sim card in it dose it not download all the the carrier bloatware and what not? dose that basically turn it back into a AT&T phone? or could I take that CSA4 and flash it with the CRF5 AT&T user data?
sean8102 said:
I am using AT&T. I know rollouts are staged but I've never had it tell me my phone is up to date when it is 7 versions behind which it was because I had to start at CRF5 since that is the newest AT&T Userdata file I could find. I checked after doing the update from SD card method each time, making sure to put the date on my phone forward since AT&T only lets you manually check once a day. No matter what it said I was up to date despite being several versions behind.
I'm gonna try using Odin to flash one more time because not being able to do OTA update is a HUGE PIA. Dose it matter that the user data is called "ATT_G955USQU5CRF5" despite the firmware being USQS because I couldn't find a USQSCRF5 and besides AT&T's update history shows USQSCRF5 anyways. What I did was downloaded a verizon G955USQS5CRF5 ODIN file and replaced the Verizon user data with the AT&T one.
Also if I flash say CSA4 verizon with the verizon user data the put my AT&T sim card in it dose it not download all the the carrier bloatware and what not? dose that basically turn it back into a AT&T phone? or could I take that CSA4 and flash it with the CRF5 AT&T user data?
Click to expand...
Click to collapse
1. I have no idea what the difference is between SQS and SQU. Even on the same network, it seems to be completely random as to which one gets assigned to each new update. I don't think it matters
2. Don't flash userdata if you're going to Odin flash a different carrier's version. Just do the normal 4 files
Sorry for the late reply. But just wanted to say that this method of getting from a G955U1 (US Unlocked) firmware back to AT&T branded firmware did end up working. I did eventually start getting OTA updates after using the method I mentioned (flashing Verizon USQS5CRF5 ROM files with AT&T G955USQS5CRF5 USERDATA file using ODIN Odin3 v3.13.1 3B Patched). Then updating to the then latest version using the update.zip method using files from the "Firmware Science" site (I think that's the name). Then about two days after AT&T released a new update I actually got it OTA. However after it installed successfully my chrome app became broken. Opening it and hitting the ... button in the top right would open the menu but all the options just said "chrome". Tried clearing the cache and files of Chrome but then it just crashed when launched. Had to do a reset (not a big deal since I had a Samsung SmartSwitch backup on my SD Card). Just hope that dose not happen every OTA, but guessing it was a weird fluke.
sean8102 said:
Sorry for the late reply. But just wanted to say that this method of getting from a G955U1 (US Unlocked) firmware back to AT&T branded firmware did end up working. I did eventually start getting OTA updates after using the method I mentioned (flashing Verizon USQS5CRF5 ROM files with AT&T G955USQS5CRF5 USERDATA file using ODIN Odin3 v3.13.1 3B Patched). Then updating to the then latest version using the update.zip method using files from the "Firmware Science" site (I think that's the name). Then about two days after AT&T released a new update I actually got it OTA. However after it installed successfully my chrome app became broken. Opening it and hitting the ... button in the top right would open the menu but all the options just said "chrome". Tried clearing the cache and files of Chrome but then it just crashed when launched. Had to do a reset (not a big deal since I had a Samsung SmartSwitch backup on my SD Card). Just hope that dose not happen every OTA, but guessing it was a weird fluke.
Click to expand...
Click to collapse
Hey I am in the same boat. Can you please help pointing to the files you used to ODIN to get back to ATT version.
SC1 USERDATA was added a few days ago, for anyone wanting to jump to Pie
USERDATA added for bootloader 6
USERDATA added for bootloader 7
Ive been researching and reading most of the day about returning to stock on an att 955u. The only download i can find that wont take 6 hours is from samfirm and is G955USQS7DSL2. Can i use this and the userdata from your link to return this back to stock?
jetracer said:
Ive been researching and reading most of the day about returning to stock on an att 955u. The only download i can find that wont take 6 hours is from samfirm and is G955USQS7DSL2. Can i use this and the userdata from your link to return this back to stock?
Click to expand...
Click to collapse
Since the USERDATA is TA5, I would recommend using a build that's closer to that one. You can get TA3 from SamFirm under regions/CSCs ACG, CCT, LRA, SPR, TFN, or VZW.
When you say "returning to stock", what firmware is currently on the device?
iBowToAndroid said:
Since the USERDATA is TA5, I would recommend using a build that's closer to that one. You can get TA3 from SamFirm under regions/CSCs ACG, CCT, LRA, SPR, TFN, or VZW.
When you say "returning to stock", what firmware is currently on the device?
Click to expand...
Click to collapse
I was on a verizon build. I ended up returning to stock with G955USQS6DSG4, got one update and now says no firmware. Currently shows G955USQU6DSH8.
SamMobile actually had pretty decent speed.
jetracer said:
I was on a verizon build. I ended up returning to stock with G955USQS6DSG4, got one update and now says no firmware. Currently shows G955USQU6DSH8.
SamMobile actually had pretty decent speed.
Click to expand...
Click to collapse
Do you have all of AT&T's apps and bloatware now? If so, it should be updating at least to SJ3, if not up to TA5. You would need an active AT&T SIM inserted in order to pull the update though
iBowToAndroid said:
Do you have all of AT&T's apps and bloatware now? If so, it should be updating at least to SJ3, if not up to TA5. You would need an active AT&T SIM inserted in order to pull the update though
Click to expand...
Click to collapse
Yea just uninstalled and disabled a bunch of att and samsung bloat. I am currently running an att sim. Should i possible download the v7 files and try again? Shouldn't matter that the firmware was from "tmobile" right its the userdata that counts iirc.
jetracer said:
Yea just uninstalled and disabled a bunch of att and samsung bloat. I am currently running an att sim. Should i possible download the v7 files and try again? Shouldn't matter that the firmware was from "tmobile" right its the userdata that counts iirc.
Click to expand...
Click to collapse
What do the 3 service provider codes show as, under Software Information?
I have a TracFone S8+. I recently flashed it with the Verizon combination and stock firmware. Now, whenever I'm trying to flash it to anything, I either
get stuck at SetupConnection for a while before getting "All threads completed success 0 / failed 1", or
get the Complete(Write) error
I tried the method where I click the start button before immediately entering download mode. That did nothing. I also tried flashing it again with both Verizon and Tracfone files. Neither succeeded. I used different versions of Odin, as well as the Prince and the new patched editions. My phone is working fine, but I'm worried that problems may arise by not having the original carrier's firmware, esp. when I still have TracFone as my carrier.
gladiatorland said:
I have a TracFone S8+. I recently flashed it with the Verizon combination and stock firmware. Now, whenever I'm trying to flash it to anything, I either
get stuck at SetupConnection for a while before getting "All threads completed success 0 / failed 1", or
get the Complete(Write) error
I tried the method where I click the start button before immediately entering download mode. That did nothing. I also tried flashing it again with both Verizon and Tracfone files. Neither succeeded. I used different versions of Odin, as well as the Prince and the new patched editions. My phone is working fine, but I'm worried that problems may arise by not having the original carrier's firmware, esp. when I still have TracFone as my carrier.
Click to expand...
Click to collapse
Nothing bad should happen service wise. A lot of tracphone uses Verizon towers. As long as you download the TracFone apps.
Ok first off.
The combination is a multi carrier firmware. It is test firmware from Samsung not the carrier. So when you flashed that and then switched to Verizon that set Verizon as the CSC.
What you are looking for is a TracFone CSC from your current firmware version 5th digit back from far end is a 1 through 5. That determines the revision. This could cause a Odin failure. If it's lower than current.
So now that's some what explained.
If you can find that revision of firmware's CSC file you can flash that in Odin with your tracfones sim installed and it should revert back to TracFone if you think it's nessicary. If your on the newer 8.0 firmwares you need that modded Odin 3.12b I think. Those firmware are in a different file type. Not .tar files. So that will cause a fail too.
I'm always around if all those check out we can go from there:good:
There is also a dialer code to select csc but I think hidden menus are disabled on Verizon.
Lss all the firmwares are identical for all the us models. They all have identical hardware.
Pretty much what determines anything is the csc file
Thank you for your help! It's invaluable.
Okay, so I found Verizon's firmware to be G955UOYN2CRB9. However, Tracfone's is G955USQU5CRL2. If the number before the C is indeed the bootloader version, then that means I'm trying to upgrade from 2 to 5. Is that possible?
gladiatorland said:
Thank you for your help! It's invaluable.
Okay, so I found Verizon's firmware to be G955UOYN2CRB9. However, Tracfone's is G955USQU5CRL2. If the number before the C is indeed the bootloader version, then that means I'm trying to upgrade from 2 to 5. Is that possible?
Click to expand...
Click to collapse
Yes. You just can't go back to the revision 2 firmware after. You can upgrade just not downgrade
TheMadScientist said:
Yes. You just can't go back to the revision 2 firmware after. You can upgrade just not downgrade
Click to expand...
Click to collapse
Okay, now I'm seriously boggled. When I go to Software Update section in settings, it tells me that the current version is indeed G955USQU5CRL2/G955UOYN5CRL2/G955USQU5CRL2. Even though the last successful flash was Verizon. Do you know what could've happened here!? And why I still get an error when I flash the phone with TracFone firmware?
I have a Verizon phone with Verizon firmware and the 5th digit from the right is a 5. It appears you have Verizon firmware flashed on your phone
Sent from my SM-G950U using Tapatalk
djm1947 said:
I have a Verizon phone with Verizon firmware and the 5th digit from the right is a 5. It appears you have Verizon firmware flashed on your phone
Sent from my SM-G950U using Tapatalk
Click to expand...
Click to collapse
Interesting. When I visited SamMobile's page for G955U, I found that PDA associated with TracFone as well.