Build number won't change? - Samsung Galaxy S7 Edge Questions and Answers

Want OTA back on my S7 Edge and I'm not particularly bothered about VOLTE so I have just tried to flash it with G935FXXU1DQB1.
The build number is still NRD90M.G935FXXU1DPLT which is Beta 1 Nougat?
Have I done something wrong in ODIN?

Sorted. Flashed back to BTU 6.0.1

Related

Factory image question MM

Im looking to downgrade back to marshmallow from android N. Im looking at the factory images and not sure what the difference is between them. There is 6.0.1 (MTC20L) there all the same but have different letters at the end of them does that matter? Just looking for the latest version of MM . Thanks
They are listed sequentially from oldest to the newest. If you were going to flash MM, MTC20L would be the newest. Keep in mind you will not have any of the security updates issued after that ROM was released, and you will be nagged to update to the latest 7.1.1 release.

Firmware Change to Tmobile After Repaired by Samsung

Before I send it to Samsung to repaired my S8+, the phone has the unlock version g955u1, but when I got it back, it is g955u with tmobile on it. Is it possible to change it back ? I have android 8.0 right now with January 2018 security patch. Most of the firmware I found are 7.0. I am new to android I might need some extra help here.
I believe you should be able to flash Nougut fw with odin (not 100% sure but should be able to) . Just make sure that the bootloader versions are the same.
Nevermind, I miss understood your question. You'll have to wait until the oreo fw is released before you can change from u to u1 or vise versa

Android 8 Oreo Update

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.

AT&T CRD6 OREO on 930U and CANT revert back to BRA1, BQE1, BRD1 in Odin

Literally no matter what I do. I cannot flash ANYTHING in Odin to either revert back to 7.0 or stock 8.0. Its not flashing any version of 7 or 8 and its not flashing any U firmware or AT&T firmware.
What am I doing wrong. I flashed 8.0 with the intent to be able to revert back to stock 7.0 once official Oreo rolled out and I literally cant do anything in Odin. I've tried odin 3.13 and 3.12 prince version. HALP
update: flashed G930UUEU4BRD1 using odin 3.12 successfully. phew
As far as I know, the newest Oreo version of AT&T is CRE4, not BRD6 as you say
SKv.DinDin said:
As far as I know, the newest Oreo version of AT&T is CRE4, not BRD6 as you say
Click to expand...
Click to collapse
You may be speaking about where I said CRD6, that is a version of Oreo that doesn't have much difference than the latest version of Oreo CRE4. Most of them after release have been minor changes. I was not flashing back to BRA1 to constantly flash the newest update of Oreo. I have an unlocked s7 so I can flash any carrier but eventually when the official oreo firmware comes out for either tmobile or the unlocked 930 varient i will be switching back to OTA updates
aarongotgame said:
You may be speaking about where I said CRD6, that is a version of Oreo that doesn't have much difference than the latest version of Oreo CRE4. Most of them after release have been minor changes. I was not flashing back to BRA1 to constantly flash the newest update of Oreo. I have an unlocked s7 so I can flash any carrier but eventually when the official oreo firmware comes out for either tmobile or the unlocked 930 varient i will be switching back to OTA updates
Click to expand...
Click to collapse
You tried with patched odin? Odin v3.13.1 3B.
anarasgarli said:
You tried with patched odin? Odin v3.13.1 3B.
Click to expand...
Click to collapse
The issue was probably that I needed to put home file in csc and exclude the csc file and then factory reset and clear caches. I probably ended up factory reset before Odin and didn't activate USB debug or the files I was using were corrupt. Since then I've just flashed TMobile Oreo that came out a few days ago and I'm gonna just use official ota for future updates
aarongotgame said:
The issue was probably that I needed to put home file in csc and exclude the csc file and then factory reset and clear caches. I probably ended up factory reset before Odin and didn't activate USB debug or the files I was using were corrupt. Since then I've just flashed TMobile Oreo that came out a few days ago and I'm gonna just use official ota for future updates
Click to expand...
Click to collapse
Looks like same problem with Galaxy S8, just search Stuck 32% error at Galaxy s8.
Reverting back from Oreo to either Nougat or Marshmallow
I am a newbie here.. Recently my ATT Galaxy S7 received Oreo upgrade and I am not at all liking it.
Can someone please guide me if it's possible to go back to Nougat or even marshmallow (preferable). If yes, what would steps for same..
My device is SM-G930A. Originally ATT device and now it's unlocked by ATT.
My device is currently NOT rooted , I am OK with rooting it.. I would appreciate if someone can help me with steps for same as well..
Thanks in advance..

Older G935V to newer G935U?

Ok so I rooted my Verizon phone 2 years ago and I'm still running 6.0.1 with G935VVRU2APE1, the security patch level is from June 1, 2016, yes I'm wayyy behind. I'd like to go to Nougat or Oreo if possible with a fresh start/data wipe. Not concerned with root atm.
Where do I start? I've read through a lot of forum pages but no one has a build as old as mine it seems. According to updato.com/firmware-archive-select-model?q=SM-G935v (can't post proper link) the latest build for 6.0.1 is G935VVRU4API3. Can I go from APE1 to API3 without issue following "{GUIDE} Flashing the SM-935U firmware onto your Verizon S7 Edge and Rooting" or does it have to be a certain prior version?
From there will an OTA update or an official stock odin file get me to Nougat/Oreo? Thank you in advance!
I did upgrade my 6.0.1 V to 7.0 U. From there I got the OTA updates/upgrades to Oreo. You can get them faster if you use SmartSwitch on PC and phone.
SoNic67 said:
I did upgrade my 6.0.1 V to 7.0 U. From there I got the OTA updates/upgrades to Oreo. You can get them faster if you use SmartSwitch on PC and phone.
Click to expand...
Click to collapse
Thanks for the reply. So do I go from my current build to the latest 6.0.1 (API3) or just go straight to the latest 7.0?
I would say you have to go to an official one first, using Odin.

Categories

Resources