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..
Related
As stated in the title, I've managed to bypass the locked bootloader and flash pc8 firmware from pd8 firmware. It didn't seem I had any restrictions to what I flashed in Odin. Just looking for suggestions before I post how.
Bought the phone with pd8 firmware, downgraded to bl, ap,csc to pc8 firmware
Got ahead of myself
Moderator can delete this thread
MOD EDIT: THREAD CLOSED
So we're you able to downgrade or not? I been having issues with the July update and wanted to go back to may.
Awhile ago I tried flashing back to I guess to feb update and kept getting errors.
Try the odin modified version that comes with the rooting package for s7 qualcomm USA version.
It's all over the net.
hackitinc said:
Try the odin modified version that comes with the rooting package for s7 qualcomm USA version.
It's all over the net.
Click to expand...
Click to collapse
Thanks for the idea, but it didn't work sadly. Same error [aboot] 3 > 2 failed.
Oh well, I am hoping the unlocked firmware thats out will be updated to v3 bootloader soon.
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.
According to GSM Arena, T-Mobile just released official android 8 for s7/s7 edge! Finally. Now which firmware should I be on because I have an unlocked phone and I want to flash TMobile firmware since I have TMobile sim card.
https://www.gsmarena.com/tmobile_starts_rolling_out_samsung_galaxy_s7_oreo_update-news-31959.php
I'm pretty sure I can just use SamFirm to flash the official firmware since SamFirm has all the official firmware for samsung phones. I will check to see if SamFirm has updated to Android 8 on the Tmobile s7/s7 edge.
Update: Yup, SamFirm has the official version for Download if you aren't getting the OTA update. (see attachment below)
Can confirm. Just completed the OTA update.
888Appraisal said:
Can confirm. Just completed the OTA update.
Click to expand...
Click to collapse
How is it running for you?
Smooth install. no freezes or crashes as of today. I did do a shutdown right after install. Rebooted just fine. I plan on doing cache wipe after a day or two.
overall responsiveness seems no worse than 7.
Running smooth after factory reset, but the secure folder icon doesn't change with icon packs. Just wondering if anyone else has noticed any bugs like this.
I upgraded to this build and I don't like it. Can I odin back to 7.0 and be ok?
HTCMDA said:
I upgraded to this build and I don't like it. Can I odin back to 7.0 and be ok?
Click to expand...
Click to collapse
Yea
Hey I need help installing this. I have an At&t SIM card, my s7 flat is on stang5litre right now. Do I'll have to install the att nougat and then update?? Or Do I have to go back to t mobile nougat and update and hope it is rooted still
iim baby jesus said:
Hey I need help installing this. I have an At&t SIM card, my s7 flat is on stang5litre right now. Do I'll have to install the att nougat and then update?? Or Do I have to go back to t mobile nougat and update and hope it is rooted still
Click to expand...
Click to collapse
Oreo isn't rooted period because of the locked bootloader on the us variants. If you have an atnt phone and an atnt sim, why not just flash the official atnt Oreo. Or the official atnt nougat bra1 and then just use the ota updates to get to official atnt oreo
aarongotgame said:
Oreo isn't rooted period because of the locked bootloader on the us variants. If you have an atnt phone and an atnt sim, why not just flash the official atnt Oreo. Or the official atnt nougat bra1 and then just use the ota updates to get to official atnt oreo
Click to expand...
Click to collapse
Yea sorry I meant for it to be unlocked still on Oreo if installed the t mobile Oreo. Should I just use sammobile and download the art nougat use odin then do the ota through the phone?
iim baby jesus said:
Yea sorry I meant for it to be unlocked still on Oreo if installed the t mobile Oreo. Should I just use sammobile and download the art nougat use odin then do the ota through the phone?
Click to expand...
Click to collapse
I have an unlocked s7. We can use any carriers firmware. If you want the atnt firmware, you can go to the atnt s7 forums and they have the nougat and the Oreo firmware. They have the stock atnt Oreo firmware that you should be able to flash directly. If that doesn't work, you can flash atnt nougat bra1 and then just continuously ota until the Oreo update comes up, I think atnt is currently on Oreo CRE4 if they haven't had an update. Also, if your phone is unlocked and you've had the 930U firmware before, I'm actually gonna switch over to the unlocked Oreo once it is officially released since the U firmware doesn't have all the carrier bloat. Right now the U firmware is only on BRD1 nougat I believe.
If you want tmobiles Oreo, just flash the files I provided. If it doesn't work then revert back to atnt nougat bra1 or unlocked bra1 and then you can flash this TMobile Oreo
aarongotgame said:
I have an unlocked s7. We can use any carriers firmware. If you want the atnt firmware, you can go to the atnt s7 forums and they have the nougat and the Oreo firmware. They have the stock atnt Oreo firmware that you should be able to flash directly. If that doesn't work, you can flash atnt nougat bra1 and then just continuously ota until the Oreo update comes up, I think atnt is currently on Oreo CRE4 if they haven't had an update. Also, if your phone is unlocked and you've had the 930U firmware before, I'm actually gonna switch over to the unlocked Oreo once it is officially released since the U firmware doesn't have all the carrier bloat. Right now the U firmware is only on BRD1 nougat I believe.
If you want tmobiles Oreo, just flash the files I provided. If it doesn't work then revert back to atnt nougat bra1 or unlocked bra1 and then you can flash this TMobile Oreo
Click to expand...
Click to collapse
As of now do you believe Oreo is worth it, or should I wait till it it is more stable
iim baby jesus said:
As of now do you believe Oreo is worth it, or should I wait till it it is more stable
Click to expand...
Click to collapse
Oreo is worth it and it's stable. It's been out for a while, it's just now hitting older devices. Currently Android P is the newest Android. Which is Android 9
aarongotgame said:
Oreo is worth it and it's stable. It's been out for a while, it's just now hitting older devices. Currently Android P is the newest Android. Which is Android 9
Click to expand...
Click to collapse
Thank you sir? hopefully there is root on the way
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.