Bought an unlocked S8 from Samsung I use AT&T for service. I wouldn't be opposed to flashing/odin'ing AT&T firmware. Currently on build NRD90M.G950U1UEU1AQH3 and the August 1st security patch. I'm unsure of the best path to get to an AT&T firmware.
Go to the att section. Find the qf7 firmware and flash it with Odin.
Go to the adb update from server thread. Download all the firmwares (starting with qf7 to whatever it is) and put them on your external storage. While on qf7 reboot into recovery and select install update from storage. Flash each one, after the last one wipe data/factory reset and reboot.
So to be clear, flash AQF7 in Odin. This will get me onto an AT&T specific SM-G950U (<-- Not U1) ROM that I can then sideload the updates onto? Is sideloading the ADB updates just to speed things up vs waiting for OTAs once I'm on the correct ROM?
I flashed my at&t version to AHQ3 thinking I would be getting faster support. I am also surprised that the Unlocked AHQ3 is still on the August security patch. I really expected this version to get patched much faster or am I missing something?
msk said:
I flashed my at&t version to AHQ3 thinking I would be getting faster support. I am also surprised that the Unlocked AHQ3 is still on the August security patch. I really expected this version to get patched much faster or am I missing something?
Click to expand...
Click to collapse
The US unlocked version is the red headed stepchild of the S8 world, it really is slower for updates.
I am running AQK3 on an ATT version, think I got it from sammobile, just got one I think it was the VZW version but don't remember, didn't change the AT&T bloatware... since I did not pawn/root it in my current setup. Patch level is oct not nov...
You should have received the November security patch update last night or should be getting it sooner than later. If anything try running the manual software update on WiFi when you get a chance.
Related
As Verizon users know a new OTA was pushed yesterday 02/16/17 the update is safe to take if you have a unlocked bootloader you will need to reflash TWRP and root you will lose both after updating
Haven't seen a new OTA on Verizon.
@Shiftydogit, build no. anything?
I'm guessing it is not showing on anyone who manually upgraded with the latest Google OTA files. Not sure about the regular Google update files, but probably checks the system version ether way for 7.1.1, NOF26V and the latest (February) security version.
sliding_billy said:
I'm guessing it is not showing on anyone who manually upgraded with the latest Google OTA files. Not sure about the regular Google update files, but probably checks the system version ether way for 7.1.1, NOF26V and the latest (February) security version.
Click to expand...
Click to collapse
Its all determined by the IMEI and ICCID. The images from Google and VZW are now identical. I got the OTA push and Im on the latest Google OTAs. They simply don't roll out OTAs to everyone at the same time .
Newer than February security patch 7.1.1 NOF26V? What's the build number? I'm 100% stock on NOF26V and can't pull an OTA at this time.
Shiftydogit said:
As Verizon users know a new OTA was pushed yesterday 02/16/17 the update is safe to take if you have a unlocked bootloader you will need to reflash TWRP and root you will lose both after updating
Click to expand...
Click to collapse
Have you rerooted? Idk if I have much reason to, since I rooted mostly for tethering, but I'm curious about the reliability in that
Soccerdude588 said:
Have you rerooted? Idk if I have much reason to, since I rooted mostly for tethering, but I'm curious about the reliability in that
Click to expand...
Click to collapse
Not at the moment been to lazy to reflash TWRP lol
farfromovin said:
Newer than February security patch 7.1.1 NOF26V? What's the build number? I'm 100% stock on NOF26V and can't pull an OTA at this time.
Click to expand...
Click to collapse
NOF26V is the newest OTA. NOF26W is for Rogers. NOF26V was pushed a few weeks ago and includes the February Security patches. I'm assuming those getting it on 2/17 were either late, or part of the 7.1.2 beta program.
I just bought a refurbished AT&T Galaxy S7 Edge and is on the May security update build G930AUCU4BQD4. I looked online and the latest build for the August security update is G930AUCU4BQG1. I go to check for updates and it tells me its up to date. Does anyone know how can I force the cell to download the update. I tried looking for an OTA file to use and flash from recovery, but no luck.
Thank you.
My first question is did you buy an Edge which is a 935 or the S7(Flat) which is the 930. Depending on that the next question is who is your carrier. If it is ATT then you should be able to OTA with no needed tinkering. If it is not ATT then you would have to sideload the ota zips via recovery. Plenty of links and descriptions on XDA for how to do that, but we need to know which phone it is first.
twizt3d said:
My first question is did you buy an Edge which is a 935 or the S7(Flat) which is the 930. Depending on that the next question is who is your carrier. If it is ATT then you should be able to OTA with no needed tinkering. If it is not ATT then you would have to sideload the ota zips via recovery. Plenty of links and descriptions on XDA for how to do that, but we need to know which phone it is first.
Click to expand...
Click to collapse
It's the 935 edge att, but not getting ota's. I did find the files to update, but I am not sure if it will delete restore the phone to factory.
https://forum.xda-developers.com/att-s7-edge/how-to/updates-g935a-servers-adb-sideloads-t3583165
Danny1976 said:
It's the 935 edge att, but not getting ota's. I did find the files to update, but I am not sure if it will delete restore the phone to factory.
https://forum.xda-developers.com/att-s7-edge/how-to/updates-g935a-servers-adb-sideloads-t3583165
Click to expand...
Click to collapse
Sideloading WILL wipe the phone. I still am not clear on whether this is a 935a or a 935v with a fw. Also is your provider att. The only reason I am aware you would not get it's is of you flashed a leaked or beta fw that has no upgrade path. Try to Odin the full fw.
This has to be a complete newb question but how come when I search on sammobile or updato there isn't an AT&T firmware under SM-G950U, but rather it's always under SM-G950U1?
Example - SamMobile for U1 -- lists AT&T firmware
But SamMobile for SM-G950U, although it lists several carriers, does not have AT&T.
Background: My wife and I both got AT&T branded S8s. I got mine through Samsung.com, she got hers through Best Buy. Mine had no problems receiving OTAs. Hers is still stuck with software from April and will not receive OTA updates nor will it update via SmartSwitch, so I was just going to flash latest AT&T via odin, but only seeing software under 950U1, I just wanted to make sure I was downloading the right one (currently this one, I believe)
@mhh84,
You can download the .zip files for AT&T updates from here, and ADB sideload them > https://forum.xda-developers.com/att-galaxy-s8/how-to/adb-sideload-servers-t3647117
Thanks but I'm not sure that answered my question or helped me. Her phone is on April security patch. The page you linked seemed to have incremental updates but doesn't go back to April.
mhh84 said:
Thanks but I'm not sure that answered my question or helped me. Her phone is on April security patch. The page you linked seemed to have incremental updates but doesn't go back to April.
Click to expand...
Click to collapse
You can download AQF7 from this thread (post #5), then follow the step by step incremental updates from the first post that I linked. > https://forum.xda-developers.com/att-galaxy-s8/how-to/att-software-update-g950usqs1aqf7-t3625728
OK, thanks @cam30era. I'm still a little unclear about my initial question though. Is the answer that AT&T firmwares aren't available or that for some reason they all just are classified under U1? I guess I want to know why it's better to do 5 incremental updates like this rather than just grabbing the August AT&T firmware from updato/sammobile. That was my original plan. I just got confused why the AT&T showed up under U1 rather than U.
mhh84 said:
OK, thanks @cam30era. I'm still a little unclear about my initial question though. Is the answer that AT&T firmwares aren't available or that for some reason they all just are classified under U1? I guess I want to know why it's better to do 5 incremental updates like this rather than just grabbing the August AT&T firmware from updato/sammobile. That was my original plan. I just got confused why the AT&T showed up under U1 rather than U.
Click to expand...
Click to collapse
I can't tell you the "why", but from observation I can tell you that there are no Odin download links for AT&T firmware updates after April. Using @norbarb thread for ADB sideload appears to be the only way to update if you're not getting OTAs.
So I have what was originally a VZW 955U, flashed soon after I got it, to the unlocked 955U1 firmware using Prince's Odin and have been happy so far. Now with all the Oreo updates released except for the unlocked one, I'm wondering if I can just use prince's odin again to load the latest TMB Oreo firmware or need to do the whole engboot thing first? My current software is latest Nougat build for 955U1 and shows up as TMB//VZW.
Any thoughts?
No one? I remember reading on some of the earlier threads that if you flashed U1 first, you could then flash to the other carriers versions without the other steps but want to confirm. Don't want to deal with bootloops or softbricks.
I think you need the eng file ..but there is not oreo eng file..
Tried a lot of things, flashing tmobile oreo directly using modified and unmodified odin, trying to flash the latest Nougat builds from Tmobile using Prince Odin (the Dec one almost took and showed up as TMB/TMB/VZW but ultimately would not get updates) and then flashing back to the unlocked version but nothing worked, will likely have to do a full erase and reload the unlocked version. The eng boot file no longer works far as I can tell. Will just have to wait for the unlocked version to get updated. Sucks as this is a corporate phone and my firm has been pushing to get Oreo on all devices.
If someone has a recent guide on carrier switching the S8 , would appreciate it. Most guides here are from May of 2017 and I'm betting those files are too old to be compatible if you're on the latest Dec build for 950U1/955U1. At least doing a full reset and reflash of the 955U1 brought Wifi Calling which wasn't quite working right since I had just flashed over the 955U1 software over the stock verizon last year.
I think I'll just wait a few more weeks for the 955U1 Oreo to drop. Has to happen eventually right? Lol.
Deleted
Maybe because the Sprint Oreo will be using BLv6 so its 2 numbers behind everyone else? lol ... anyone have any thoughts about what the BL-version could possibly be for the Sprint Oreo? ... could they or would they use a BLv4 like everyone else?
that was the Sprint answer
SprintBama said:
Maybe because the Sprint Oreo will be using BLv6 so its 2 numbers behind everyone else? lol ... anyone have any thoughts about what the BL-version could possibly be for the Sprint Oreo? ... could they or would they use a BLv4 like everyone else?
Click to expand...
Click to collapse
If anything, they would change it to v7. Maybe they are waiting for a merger, which could happen next week
I checked for update today and got 1627.64mb g930pvpu6cre7 Samsung experience 9.0 with oreo.
I haven't gotten an update from Sprint on my S7 since December 2016. I am still on some random Nougat beta version.
I thought a brand new firmware update to Oreo would reset whatever bug was in there causing this, but it looks like one person in my house got the Oreo update and mine is still saying I am up to date when I check manually.
Is there no longer an ODIN for macOS? I thought there was one, but I used it on another Mac maybe 4 years ago when I was on my S3 and rooting it. Doesn't seem to exist anymore.
Just received oreo on my s7 for boost. So far I'm not impressed. I was really hoping for Dolby on this but guess not. The build number is SMG930PVPU6CRE7
kalala said:
I haven't gotten an update from Sprint on my S7 since December 2016. I am still on some random Nougat beta version.
I thought a brand new firmware update to Oreo would reset whatever bug was in there causing this, but it looks like one person in my house got the Oreo update and mine is still saying I am up to date when I check manually.
Is there no longer an ODIN for macOS? I thought there was one, but I used it on another Mac maybe 4 years ago when I was on my S3 and rooting it. Doesn't seem to exist anymore.
Click to expand...
Click to collapse
On Mac you can use Heimdall to flash the latest Nougat firmware then update through OTA to Oreo. Because there isn't any firmware file yet on Updato or Sammobile.
i manfully updated @ 4:15. they sent it @ 1627.64 mb. still downloading. when I got my att update I tried all the batch root methods for my 935a. saving magisk for last bc I didn't have the boot.img for the cre4 update.
I I only had the "att beta" update from March. long story short it won't boot with the nougat eng.boot. I gave it an hour. I cleared the cache, factory reset, tried to add flash all of the earlier img files I had for oreo, nothing worked. had to flash it back to nougat bra1. I immediately requested the update again. they approved. the next day I attempted to flash magisk 16.4. w/ the modified odin 3.1.3 version. it wouldn't flash. with the cre4 boot.tar in hand, I tried every method on gods green earth to gain some sort of r/w access. it was late, I was tired, I flashed the eng boot. once again it was stuck at the Samsung boot logo. it wouldn't allow me into recovery to push the cre4 update zip. once again I'm back to bra1 nougat. I booted into recovery & updated it from the sd card. when it booted I noticed it wasn't anywhere as clean & polished as the ota I had twice. I've flashed back to brd1 ten times, & requested the ota. after smart switch, I used all the avail windows software I could acquire & kept trying, they won't send it. but they did provide me with a new picture for my samsung account. I'll post it later. gotta check out this 930p oreo.
razor001_ said:
On Mac you can use Heimdall to flash the latest Nougat firmware then update through OTA to Oreo. Because there isn't any firmware file yet on Updato or Sammobile.
Click to expand...
Click to collapse
I don't think Heimdall works on High Sierra or even Sierra anymore.
I'm wanting to move to a SM-930U version of stock android on my 930P. But in struggling to do so for the past couple of weeks I finally figured out that sprint as updated the bootloader to version 5 and most of the firmware images for 930U are version 4 (android 7 nugut). (PU4 vs PU5) which results in a Odin fuse error.
The phone is currently nagging me to go from PU5BQL1 to BU6BRD2. If I understand the nameing convention that would move me to version 6 of the bootloader.
What are the odds I can move to oreo for 930U and avoid the bootloader fuse issue? I think I also understand that as of this posting date a 930U oreo firmware has not been released?
schmism said:
I'm wanting to move to a SM-930U version of stock android on my 930P. But in struggling to do so for the past couple of weeks I finally figured out that sprint as updated the bootloader to version 5 and most of the firmware images for 930U are version 4 (android 7 nugut). (PU4 vs PU5) which results in a Odin fuse error.
The phone is currently nagging me to go from PU5BQL1 to BU6BRD2. If I understand the nameing convention that would move me to version 6 of the bootloader.
What are the odds I can move to oreo for 930U and avoid the bootloader fuse issue? I think I also understand that as of this posting date a 930U oreo firmware has not been released?
Click to expand...
Click to collapse
almost zero... asuming that Oreo for "U" Variants step up with BL on this month maybe next one, is something pausible but stepping up two versions in any short time is questionable... but who knows. The best you can do is wait this or the next month for BL update on U variants.
To be clear I'm still on version 5. I will continue to put off the upgrade to 6.