Database Info

Manually updating to Oreo

Hi.
I have a G955U Galaxy S8+ AT&T Factory Unlocked on Android 7.0
Baseband Version: G955USQU1AQD9
Android Security Patch Level - April 1, 2017
I no longer live in the US, and currently in the Philippines. Phone works great and the signal is too and all, but I cannot get OTA updates.
Can I just download the firmware file in this thread and flash straight through ODIN, or do I need to follow another guide?
Thanks in advance

You can, however there are specific sequences to follow, so you have to update in firmware released order.
I encountered the same problem so I downloaded odin that worked for Nougat and loaded all version to BRB1 I think it is and then went to Oreo. Currently on CRC5.
Another note, when you are about to hit Oreo you will need to download the odin that works for Oreo. It can be found in the CRC5 thread.
Happy Updating

onedonrazor said:
You can, however there are specific sequences to follow, so you have to update in firmware released order.
I encountered the same problem so I downloaded odin that worked for Nougat and loaded all version to BRB1 I think it is and then went to Oreo. Currently on CRC5.
Another note, when you are about to hit Oreo you will need to download the odin that works for Oreo. It can be found in the CRC5 thread.
Happy Updating
Click to expand...
Click to collapse
Is this really necessary?
I want to update to Oreo as well but since I'm AT&T unlocked and not currently using AT&T network I'm stuck in the June software update so I'll have to flash like 7-8 firmware updates and each one being about 2-3 GB to download.
Also, is there any stock Samsung firmware I can download so I can avoid having to manually flash every software update? Or am I just stuck with the AT&T firmware?
Thanks in advance.

I'm also having this problem. Need to flash the updates through ODIN but I can't find every single stock file leading up to BR9 on this site. Do I really have flash them all? Or is there another way?

flashing official firmware through odin stops secure folder from working?

Hello,
I'm in a bit of a confusing situation. When nougat released for s6 last year i think, i flashed it through odin and after that samsung launched/introduced secure folder for nougat and i tried it. It wasn't working because my device status wasn't "official" anymore.
So now I'm thinking again to flash uk firmware (from sammobile) for galaxy s7 sm-g930f(not rooted & device status is OFFICIAL) via odin would this problem happen again if i flash it?
Thanks if anyone's interested to answer my query..!

If you flash the correct firmware from a trusted firmware website, you shouldn't have any issues.
But flashing the wrong firmware (e.g. for the wrong SoC) or flashing firmware from a random blog site might get you in trouble, as they can end up being phone dumps instead of the actual official package.
If you use the files from updato, sammobile, or one of the firmware tools (I think this works despite ceasing development https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647) I'd say you'd be safe.

Chances are if your device was Custom, then you have rooted it at some point / flashed custom, in that case KNOX will be tripped (0x1) and if secure folder relies on KNOX being valid (0x0) as a lot of Samsung stock apps do, it will not work any longer

Beanvee7 said:
If you flash the correct firmware from a trusted firmware website, you shouldn't have any issues.
But flashing the wrong firmware (e.g. for the wrong SoC) or flashing firmware from a random blog site might get you in trouble, as they can end up being phone dumps instead of the actual official package.
If you use the files from updato, sammobile, or one of the firmware tools (I think this works despite ceasing development https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647) I'd say you'd be safe.
Click to expand...
Click to collapse
I've always downloaded firmwares from sammobile.

AT&T Galaxy S8+ OTA software update not working / alternative way. SOLVED

What I want to do: I was trying to OTA update my phone software to the latest, but it seems I am behind on many updates. On the AT&T website, I saw that I need the previous updates installed first, in order to get the latest ones. I have to go in order.
Problem: Every-time I try to do a software update from the settings, it says “Current software is up to date.” It’s been saying that for over a year now. I can’t even get the updates from last year.
So is there a way I can flash one of the stock firmware updates from last year on to my phone with Odin and see if it will fix the ‘over the air’ updates? Or can I just skip to the most recent firmware and flash that one.
By the way, I have never done anything like this to my phone before, so I am a bit nervous, but I want to get this problem fixed so I would love if someone helped me out. I did see some articles online about flashing stock firmware, that’s how I learned about Odin.
If this is doable, can someone please link me to a thorough tutorial on this process? If it isn’t, can you guys recommend another way of getting to the latest 8.0 stock firmware?
My phone:
Galaxy S8 plus (AT&T)
Model#: SM-G955U
Android version: 7.0
Baseband version: G955USQS1AQF7
Android security patch level: June 1, 2017
Kernel version: 4.4.16-11449429
My phone isn't unlocked.

Zendrop said:
What I want to do: I was trying to OTA update my phone software to the latest, but it seems I am behind on many updates. On the AT&T website, I saw that I need the previous updates installed first, in order to get the latest ones. I have to go in order.
Problem: Every-time I try to do a software update from the settings, it says “Current software is up to date.” It’s been saying that for over a year now. I can’t even get the updates from last year.
So is there a way I can flash one of the stock firmware updates from last year on to my phone with Odin and see if it will fix the ‘over the air’ updates? Or can I just skip to the most recent firmware and flash that one.
By the way, I have never done anything like this to my phone before, so I am a bit nervous, but I want to get this problem fixed so I would love if someone helped me out. I did see some articles online about flashing stock firmware, that’s how I learned about Odin.
If this is doable, can someone please link me to a thorough tutorial on this process? If it isn’t, can you guys recommend another way of getting to the latest 8.0 stock firmware?
My phone:
Galaxy S8 plus (AT&T)
Model#: SM-G955U
Android version: 7.0
Baseband version: G955USQS1AQF7
Android security patch level: June 1, 2017
Kernel version: 4.4.16-11449429
My phone isn't unlocked.
Click to expand...
Click to collapse
You can Odin flash CRG3 and the next OTA should be CRHI, so once you go thru settings, check for updates it should want to go to CRHI. And then you should be in the Update path to receive OTA's automatically

Josephigloe said:
You can Odin flash CRG3 and the next OTA should be CRHI, so once you go thru settings, check for updates it should want to go to CRHI. And then you should be in the Update path to receive OTA's automatically
Click to expand...
Click to collapse
Thanks, so is it okay to flash it with the latest version of Odin? Also, do you mind linking me with an up to date / reliable tutorial on this? This is my first time attempting to do something like this.
One more thing, on Sammobile, there is only one firmware available for at&t, and it's the oldest one.
https://www.sammobile.com/firmwares/galaxy-s8-plus/SM-G955U/ATT/

Zendrop said:
Thanks, so is it okay to flash it with the latest version of Odin? Also, do you mind linking me with an up to date / reliable tutorial on this? This is my first time attempting to do something like this.
Click to expand...
Click to collapse
https://drive.google.com/folderview?id=1okPBAupxRljTcSPI70ZVv7KqrccKNqwU
This is a patched odin.
Odin instructions.
https://www.xda-developers.com/update-firmware-any-samsung-phone/

Josephigloe said:
https://drive.google.com/folderview?id=1okPBAupxRljTcSPI70ZVv7KqrccKNqwU
This is a patched odin.
Odin instructions.
https://www.xda-developers.com/update-firmware-any-samsung-phone/
Click to expand...
Click to collapse
Okay, and is it okay if I flash from a firmware from May 2018? It's about 4 months old. Would I be able to OTA update from there on? Also, what is AT&T userdata? I came across it in this thread and I was wondering. https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-att-stock-odin-files-firmware-t3769140

Zendrop said:
Okay, and is it okay if I flash from a firmware from May 2018? It's about 4 months old. Would I be able to OTA update from there on? Also, what is AT&T userdata? I came across it in this thread and I was wondering. https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-att-stock-odin-files-firmware-t3769140
Click to expand...
Click to collapse
Yes you can use this firmware and start to receive updates, User data I'm not 100% sure but I think its supposed to flash your data so you wont have to reinstall everything but I heard it dosent work for At&t it will still do a complete wipe before install.

Josephigloe said:
Yes you can use this firmware and start to receive updates, User data I'm not 100% sure but I think its supposed to flash your data so you wont have to reinstall everything but I heard it dosent work for At&t it will still do a complete wipe before install.
Click to expand...
Click to collapse
I flashed it and it works great so far. Thanks for all the help! The OTA update also seems to be working!

[Resolved] #Solved# Any Possible Solution to Downgrade Back to Nougat?

Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:

tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Softwarehttps://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.

spawnlives said:
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.
Click to expand...
Click to collapse
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:

tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

spawnlives said:
tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse

tsam19 said:
spawnlives said:
tsam19 said:
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

spawnlives said:
tsam19 said:
spawnlives said:
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Have rooted the device no problem with magisk and patching the original boot img file. Then flashing patched boot img via odin. Causing device verification to need to reformat the device, resulting in correct root.
Once a device , this device is rooted, no official updates can be installed anyway. When you try to uodate software, a pop up shows as the device recognises the software has been modified.
As for TWRP there ISN'T any version of TWRP available for the Samsung Galaxy Active Tab2 (SM-T395). I have even emailed the makers , developers of TWRP why there isn't one in their device inventory list on their webpage.
So no TWRP, and NO custom roms either for this model.
My concern , was all about finding a valid , safe way to downgrade back to original Nougat 7.1. And until someone can produce a working image with a BL with binary 4. Then there's only one optiin and that is to buy another untampered device with Nougat 7.1 out of the box and leave it un updated. :good:
Thanks for replying.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
To answer your question of how is downgrading such a big problem, it is due to security reasons, to keep your device as secure as possible with the newest available software and the latest security updates.
Sent from my SM-S767VL using Tapatalk

[SOLVED] Samsung S10+ not scanning for OTA updates despite having relocked bootloader using download mode and flashed stock ROM using Odin.

[Repost from Samsung Galaxy S10+ forum]
I rooted my phone last October 2020 and installed a custom ROM. Enjoyed it for a while but today I decided I want to revert to stock.
- Flashed stock ROM from Frija (wasn't able to backup data and settings when I first rooted my phone) (the stock firmware is the May 2021 security firmware update, it's the only one available from both SamFirm and Frija based on the region and carrier where my phone came from) using the HOME CSC file instead of the CSC (not sure if it's important to point that out but i'm just gonna bring it up just in case)
- Re-locked bootloader using download mode. Verified by searching for Netflix on the Play Store and thankfully, it showed up.
However, I tried making the phone search for an OTA update by going to Settings > Software updates > Download and install, but after checking for updates, it says my software is "up to date". I'm not entirely what the latest software version in my region is but I really want to get OTA updates back. I don't care about tripping Knox or what not, I just need the OTA updates.
EDIT: Solved by hainguyenthao