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
Related
Hi
Apologies for what is quite a basic question for I'm just trying to get things straight in my head before proceeding.
I have a UK retail S7 G930F, current running stock
Build G930FXXU1DQC4
Baseband G930FXXU1DQC2
Despite the fact this build only has Android security patch level February 2017, and the latest build is from 2018, my device and Smart Switch insist I am up to date, I want to actually make this the case while remaining on stock firmware.
I have used Odin to flash Galaxy phones before but not since I had a Note 2 and Note 3 so I'm a little rusty.
I have Odin 3.13.1 and the zip download from sammobile for build G930FXXS2DRAA for the same CSC region I'm currently on which is XEU.
All the guides for Odin flashing say to only use the AP file and option in Odin. However as my BL, CP and CSC will all be older as well, and I'm simply going from stock to stock can I (or should I) also flash these parts as well?
Thanks.
I need more information. 6 mm and 7 nougat use the same BL and require no upgrade where if you were on lollipop somehow you would need the bl. Please DO NOT run off and start flashing things like BL without help from here first. I have bricked a samsung device so bad I had to replace the motherboard, so I learned the hard way.
Both current firmware and the one I intend to flash are Android 7, the new one is just a much more recent build with a more up to date security patch level.
My current firmware, as shipped (or possibly updated OTA a long time ago)
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXU1DQC4/127501/
My intended firmware that I plan to flash
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXS2DRAA/205600/
Despite the fact that sammobile says the newer one is available in Smart Switch, it doesn't show any updates when I connect my device to my PC with Smart Switch.
y2kgecko said:
Both current firmware and the one I intend to flash are Android 7, the new one is just a much more recent build with a more up to date security patch level.
My current firmware, as shipped (or possibly updated OTA a long time ago)
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXU1DQC4/127501/
My intended firmware that I plan to flash
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXS2DRAA/205600/
Despite the fact that sammobile says the newer one is available in Smart Switch, it doesn't show any updates when I connect my device to my PC with Smart Switch.
Click to expand...
Click to collapse
I get that a lot. I upgraded my s7 to latest n release today and it worked ok.
So, do I just flash AP or everything?
y2kgecko said:
So, do I just flash AP or everything?
Click to expand...
Click to collapse
You need to flash all 4 files: BL / AP / CP / CSC
I do recommend that you flash CSC* and not HOME_CSC*. That way you will reset the phone to factory defaults and it will be ready for future OTA updates.
Backup your files first that you think are important and then start from scratch to configure the phone, install your apps, update the ones on the phone.
Short question: how can I downgrade or FRP unlock a S8+ G955F that is FRP locked and on very recent firmware?
Here are the details:
I am trying to assist a family member with a Galaxy S8+ (SM-G955F) that they have just purchased online. When purchasing it they were not told that FRP lock is on (FRP LOCK: ON) and OEM lock is on (OEM LOCK: ON). It was running Bootloader v2 on very recent stock firmware. It has been successfully flashed with BL_G955FXXU2CRED and AP_G955FXXU2CRED...
It was on G955FXXU2CRED firmware. I was able to successfully able to flash the Combination ROM COMBINATION_FA70_G955FXXU2ARE1 (full name COMBINATION_FA70_G955FXXU2ARE1_CL12792727_QB18097821_REV00_user_mid_noship.tar)
With combination rom, it seemed that I could enable USB Debugging, and also follow the steps for *#0808# IME to enable the appropriate mode for adb codes to be entered. I was able to find the device with 'adb devices', and I thought that the FRP unlock codes on the command line worked. But after re-flashing to the current Stock Firmware again, FRP lock was still there.
It seems I need to downgrade to Nougat 7.0, but I am on Bootloader V2. Odin identifies it by a FAIL with binary not matched (2 vs 1). So it seems that if I could get a method to keep Bootloader V2 and install Stock Firmware for Android 7.0 Nougat, I would be halfway there to fixing the FRP problem. However, I can't find any firmware or ROMs for G955F that includes Bootloader V2. This is identified by a U2 in the firmware name, like: G955FXXU2CRED . Is there a way to keep the BL Bootloader V2 but install AP ROM from Nougat?
I have spent many hours on this so far, and I just wanted to say thank you to all you guys who are helping on XDA, I really appreciate it. I have read about 7 day waiting periods for OEM UNLOCK but I don't see how it applies, as I can't do anything aside from use Combination ROM, use Odin, or go to the FRP locked FW which seems to be a dead end?
If there was a reliable method for rooting this G955F device with this G955FXXU2CRED firmware, I would be open to trying it.
details
Another note: AP SW Rev is identified as B:2 K:1 S:1
I don't think once a phone has the boot loader CRED, that the phone can be downgraded. Hope I am wrong.
JeffDC said:
I don't think once a phone has the boot loader CRED, that the phone can be downgraded. Hope I am wrong.
Click to expand...
Click to collapse
I think you are right. The combination ROM seems to built on selinux version 7.
I think I need to root with twrp. But first I need to enable OEM unlock. I'm not sure if that will be possible with combination ROM or if I should flash latest stock and then wait 7 days??
same problem here... If an solution available pls write here
anonan said:
I think you are right. The combination ROM seems to built on selinux version 7.
I think I need to root with twrp. But first I need to enable OEM unlock. I'm not sure if that will be possible with combination ROM or if I should flash latest stock and then wait 7 days??
Click to expand...
Click to collapse
Flashing stock rom and waiting 7 days would be the safe option.
I am not exactly sure what you are trying to achieve.
https://www.samsung.com/us/support/frp/
anonan said:
I think you are right. The combination ROM seems to built on selinux version 7.
I think I need to root with twrp. But first I need to enable OEM unlock. I'm not sure if that will be possible with combination ROM or if I should flash latest stock and then wait 7 days??
Click to expand...
Click to collapse
I think I read someone on CarHDRom who flashed the rom via TWRP, and then when the phone booted into system for the first time at setting up, they changed the date to 8 days earlier, and when the phone setup was completed and booted into system, the OEM unlock was available.
Re: CRED I believe once it has been installed on a phone, you can not go back to a previous version (pre CRED).
JeffDC said:
I think I read someone on CarHDRom who flashed the rom via TWRP, and then when the phone booted into system for the first time at setting up, they changed the date to 8 days earlier,.
Click to expand...
Click to collapse
I wonder if I can do this date trick with combination FW to enable OEM unlock.
anonan said:
I wonder if I can do this date trick with combination FW to enable OEM unlock.
Click to expand...
Click to collapse
It seems there are a few solutions to frp if you can selectively restore flash files. It looks like Samsung tool Pro can do this, but is there any free adb method?
http://forum.gsmhosting.com/vbb/f453/new-solution-remove-frp-s8-plus-sm-g955f-last-security-2422242/
Especially this http://forum.gsmhosting.com/vbb/f453/g955f-rev-2-frp-100-no-box-2417931/
Hi, could you send me a link of the combination firmware please Can't find it anywhere My email address is [email protected] I currently have similar experience of yours I thought everythings gonna be okay but it was too good to be true Help
anonan said:
Short question: how can I downgrade or FRP unlock a S8+ G955F that is FRP locked and on very recent firmware?
Here are the details:
I am trying to assist a family member with a Galaxy S8+ (SM-G955F) that they have just purchased online. When purchasing it they were not told that FRP lock is on (FRP LOCK: ON) and OEM lock is on (OEM LOCK: ON). It was running Bootloader v2 on very recent stock firmware. It has been successfully flashed with BL_G955FXXU2CRED and AP_G955FXXU2CRED...
It was on G955FXXU2CRED firmware. I was able to successfully able to flash the Combination ROM COMBINATION_FA70_G955FXXU2ARE1 (full name COMBINATION_FA70_G955FXXU2ARE1_CL12792727_QB18097821_REV00_user_mid_noship.tar)
With combination rom, it seemed that I could enable USB Debugging, and also follow the steps for *#0808# IME to enable the appropriate mode for adb codes to be entered. I was able to find the device with 'adb devices', and I thought that the FRP unlock codes on the command line worked. But after re-flashing to the current Stock Firmware again, FRP lock was still there.
It seems I need to downgrade to Nougat 7.0, but I am on Bootloader V2. Odin identifies it by a FAIL with binary not matched (2 vs 1). So it seems that if I could get a method to keep Bootloader V2 and install Stock Firmware for Android 7.0 Nougat, I would be halfway there to fixing the FRP problem. However, I can't find any firmware or ROMs for G955F that includes Bootloader V2. This is identified by a U2 in the firmware name, like: G955FXXU2CRED . Is there a way to keep the BL Bootloader V2 but install AP ROM from Nougat?
I have spent many hours on this so far, and I just wanted to say thank you to all you guys who are helping on XDA, I really appreciate it. I have read about 7 day waiting periods for OEM UNLOCK but I don't see how it applies, as I can't do anything aside from use Combination ROM, use Odin, or go to the FRP locked FW which seems to be a dead end?
If there was a reliable method for rooting this G955F device with this G955FXXU2CRED firmware, I would be open to trying it.
Click to expand...
Click to collapse
anonan said:
It seems there are a few solutions to frp if you can selectively restore flash files. It looks like Samsung tool Pro can do this, but is there any free adb method?
http://forum.gsmhosting.com/vbb/f453/new-solution-remove-frp-s8-plus-sm-g955f-last-security-2422242/
Especially this http://forum.gsmhosting.com/vbb/f453/g955f-rev-2-frp-100-no-box-2417931/
Click to expand...
Click to collapse
It worked! Flashed the Comb file with Odin and do what he does in the video, then flashed the Stock G955FXXU2CRED and now its unlocked I dont know how i did this but its worked!
darknagel said:
It worked! Flashed the Comb file with Odin and do what he does in the video, then flashed the Stock G955FXXU2CRED and now its unlocked I dont know how i did this but its worked!
Click to expand...
Click to collapse
Excellent.
I still can't get this to work. Have you purchased Samsung tool Pro to do the flashing of individual boot files? What version?
Hi there. I already bypassed the frp.. If you need. Hp with android 8.0 even with the binary 2. I have some comb files and working stock roms through odin. Feel free to pm me via my email [email protected]. Thanks!
how
darknagel said:
It worked! Flashed the Comb file with Odin and do what he does in the video, then flashed the Stock G955FXXU2CRED and now its unlocked I dont know how i did this but its worked!
Click to expand...
Click to collapse
Hi
Can you let me know the steps as i am trying but i cant flash the stock firmware after the factory binary
thx
oz_ezekiel said:
Hi
Can you let me know the steps as i am trying but i cant flash the stock firmware after the factory binary
thx
Click to expand...
Click to collapse
Download latest odin and try again. I too got stuck in similar situation. Realised the issue is due to Odin. If you are using latest and encountered this error, try one version earlier.
I too can confirm that the combination-ROM works like a charm with odin. FRP kinda unlocked itself
How to downgrade a non-rooted S7 Edge from Android Oreo 8.0 to 7.0 and keeping your Knox 0x0!
So if some of you are looking for a 'how-to' guide, look no further! (I believe it works on your S7 too, but make sure you have downloaded the correct firmware)
*IMPORTANT*
-I don't take ANY responsibility if you bricked your device during the flash!
-Follow the guide below before flashing your official firmware using Odin!
On the phone
-Sign-out any accounts on settings
-Have OEM-unlock & USB Debugging ON (developer options)
-*optional task, just in case* Screenshot your device information on the settings tab (IMEI, Baseband, Software Info, Model number)
-*optional task, just in case* Backup your device using Samsung SmartSwitch software
Things to download
-For this guide I used Odin v3.13.1 https://dl.sammobile.com/Odin3-v3.13.1.zip
-You can install the Samsung driver using SmartSwitch if your Win PC can't detect your Samsung phone (it should show on Device Manager > Modem > something like Samsung Modem)
-*READ* You can't flash back to version 6.0 now because of (Android Oreo 8.0 is using different version of boot-loader) but there are some late Android 7.0 with updated boot-loader, those are using boot-loader binary v2, so binary v1 it will be conflicted and won't work upon flash.
-*NOTE* Download the correct firmware of your phone model by following the baseband, that's why I recommended to take screenshots of your phone, you can search it on here https://www.sammobile.com/firmwares/, for mine, I've searched SM-G935F and BTU is my choice, the filtered results should be your correct firmware. But in my case I used (v7.0 in March 2018) because it has the binary boot-loader v2 with it (whatever it called, it's important otherwise it will not work which I've tried)
-*optional*, if you find sammobile download speed is way too slow* You can use https://updato.com/firmware-archive-select-model?q=SM-G935F&exact=1&r=&v=Nougat%28Android+7.0%29%2COreo%28Android+8.0.0%29&rpp=100, and basically look for the correct firmware which I have mentioned above.
-Extract your firmware onto a single folder, don't mess them up! (you should see something like AP_G935blahblahblah.md5, and you will need AP_, BL_, CP_, CSC_ for downgrading)
Follow the steps:
1. Now you have the correct firmware and Odin running on Admin right
2. On Odin you can add AP_, BL_, CP_ & CSC_ onto the correct selection, for example: https://i.imgur.com/DIB2d1S.png
3. Have your phone on Download mode, google it if you don't know how (make sure you followed the On the phone step first, it's very important)
4. Find a data USB cable and plug into USB2.0 port, make sure your phone appeared on Odin (you will see something like 0:[COM5])
5. On Odin (only Auto Reboot, F. Reset Time) is needed, it should be ticked by default.
6. Now you can safely click 'Start' on Odin.
7. DO NOT TOUCH YOUR PHONE in case your USB is loose which I had experience before.
8. Wait until it shows a green PASS! like this: https://i.imgur.com/FYosmx2.png
9. When see a blue screen with Erasing text on it, please wait until it reboot and hold (Volume UP + Home Button + Power Button) boot to recovery mode
10. Wipe cache partition, and data/factory reset then reboot system now
11. Wait for it to boot into your sweet sweet Android Nougat 7.0 (Late version)
12. Disable auto-update if you wish, mine was on auto-update so I had to pause it half-way
Hope you find this guide helpful, I tried to remember the steps on my head as I typed, (*sorry for the grammar if you find it hard to understand) and if you think I've missed something here, let me know! I would update the guide if any step is missing, just in case
Thanks
I'm guessing Knox counter wouldn't have incremented?
ZionMainframe said:
Thanks
I'm guessing Knox counter wouldn't have incremented?
Click to expand...
Click to collapse
No, not at all, if you are using the official firmware! Just follow the guide closely
Please help me downgrade from G935FXXS3ERHD to G935FXXU2DRAG.
I tried nand TWRP BL restore, BL and stock firmware flash in Odin. Nothing works.
Edit:
I found a solution, see: Original post
but there are some late Android 7.0 with updated boot-loader, those are using boot-loader binary v2
can you upload the bootloader?
How to know each android 7.0 bootloader is V2?
Now with the lattest update the binary changed to 3 then i cant downgrade to Nougat
(Im spanish)
Oreo to nougat
I have a s7 edge with the Data firmware Version 2018/09/18 8.0.0
PDA: G935FXXS3ERHD
CSC: G935FITV3ERG2
is it possible to downgrade from oreo to nougat? I have the battery that you always download
I tried but doesn't work
Hello dear!
I have a S7 edge SM-G935T and I tried to flash the last version of Nougat 7, but doesn't work. Odin don't let me finish the process. Maybe you wrote this thread before my cellphone received the last update of Oreo.
Do you have any solution in this case. I really appreciate it.
King regards, _/\_
Unfortunately the bootloader was updated in last updates, now the bootloader is version 3 as the phone said to me when i tried to flash the last version of Nougat.
i have stupid question but, i have R16NW.SM-G930FXXS3ERKE (oreo) but i think im not supposed download this(G930FXXS3ERKE) if i want downgrade to nougat but rather (G930FXXS2DRC3) because the first firmware i mentioned get me oreo again.... am I right??? i don t wont screw things up....
TheLoller221 said:
Unfortunately the bootloader was updated in last updates, now the bootloader is version 3 as the phone said to me when i tried to flash the last version of Nougat.
Click to expand...
Click to collapse
YES, the Guide is NOT working ANYMORE...
Does this work still
Help with G930A
Hello um I have a Samsung Galaxy S7 on AT&T (G939A) and it's on 8.0 (G930AUCS9CSB1). I've tried to root it but after some research I've come to find out I have to downgrade it to nougat to root it. But the problem is everytime I load a firmware it fails and I did more research I think it said something about the bootloader blocking it and the only way to downgrade the bootloader is downgrading the firmware which I can't do because of that cycle. Can someone please help me all I want to do is root install a custom recovery and a custom rom I love playing around with android tweaks but I can't get it because of this. I hope someone can help me please and thank you.
freshair4552 said:
I have a Samsung Galaxy S7 on AT&T (G939A) and it's on 8.0 (G930AUCS9CSB1)...
Can someone please help me all I want to do is root install a custom recovery and a custom rom...
Click to expand...
Click to collapse
Your bootloader cannot be unlocked due to it being Snapdragon, so unfortunately there is nothing you can do. Only Exynos variants can be modified.
Hello guys,I have a problem with my galaxy s7 sm-g935f(Exynos version).Few months ago I flashed my phone from android Nougat SEE CSC(South East Europe) to UK's Oreo BTU CSC.I'm curious is there any other way to downgrade it from oreo to nougat,otherwise than Odin.I tried flashing it a few times with the latest Odin version (3.13.3) and nougat SEE CSC(South East Europe) because that's my original CSC.Odin recognizes the device normally,but when i click start,it comes to setup connection and then FAIL.The reason I'm trying to downgrade is very poor battery life and heating,and the phone is very laggy.I even tried through Samsung Smart Switch Emergency software recovery but it seems that Samsung has restricted that option...please help if anyone has/had similar problem.Thank you!
Mine is Sprint g935pvpsbcta1
Am I screwed also?
Hi, I have
SM-G935Fand I can't find any nougat firmware with baseband of: G935FXXS8ETCA.. Can I flash any country / baseband 7.0 firmware? And will it improve the SOT? I'm currently getting upto 5 hours SOT.
lovetv said:
How to downgrade a non-rooted S7 Edge from Android Oreo 8.0 to 7.0 and keeping your Knox 0x0!
So if some of you are looking for a 'how-to' guide, look no further!
(I believe it works on your S7 too, but make sure you have downloaded the correct firmware)
*IMPORTANT*
-I don't take ANY responsibility if you bricked your device during the flash!
-Follow the guide below before flashing your official firmware using Odin!
On the phone
-Sign-out any accounts on settings
-Have OEM-unlock & USB Debugging ON (developer options)
-*optional task, just in case* Screenshot your device information on the settings tab (IMEI, Baseband, Software Info, Model number)
-*optional task, just in case* Backup your device using Samsung SmartSwitch software
Things to download
-For this guide I used Odin v3.13.1 https://dl.sammobile.com/Odin3-v3.13.1.zip
-You can install the Samsung driver using SmartSwitch if your Win PC can't detect your Samsung phone (it should show on Device Manager > Modem > something like Samsung Modem)
-*READ* You can't flash back to version 6.0 now because of (Android Oreo 8.0 is using different version of boot-loader) but there are some late Android 7.0 with updated boot-loader, those are using boot-loader binary v2, so binary v1 it will be conflicted and won't work upon flash.
-*NOTE* Download the correct firmware of your phone model by following the baseband, that's why I recommended to take screenshots of your phone, you can search it on here https://www.sammobile.com/firmwares/, for mine, I've searched SM-G935F and BTU is my choice, the filtered results should be your correct firmware. But in my case I used (v7.0 in March 2018) because it has the binary boot-loader v2 with it (whatever it called, it's important otherwise it will not work which I've tried)
-*optional*, if you find sammobile download speed is way too slow* You can use https://updato.com/firmware-archive-select-model?q=SM-G935F&exact=1&r=&v=Nougat%28Android+7.0%29%2COreo%28Android+8.0.0%29&rpp=100, and basically look for the correct firmware which I have mentioned above.
-Extract your firmware onto a single folder, don't mess them up! (you should see something like AP_G935blahblahblah.md5, and you will need AP_, BL_, CP_, CSC_ for downgrading)
Follow the steps:
1. Now you have the correct firmware and Odin running on Admin right
2. On Odin you can add AP_, BL_, CP_ & CSC_ onto the correct selection, for example:
https://imgur.com/DIB2d1S
3. Have your phone on Download mode, google it if you don't know how (make sure you followed the On the phone step first, it's very important)
4. Find a data USB cable and plug into USB2.0 port, make sure your phone appeared on Odin (you will see something like 0:[COM5])
5. On Odin (only Auto Reboot, F. Reset Time) is needed, it should be ticked by default.
6. Now you can safely click 'Start' on Odin.
7. DO NOT TOUCH YOUR PHONE in case your USB is loose which I had experience before.
8. Wait until it shows a green PASS! like this:
https://imgur.com/FYosmx2
9. When see a blue screen with Erasing text on it, please wait until it reboot and hold (Volume UP + Home Button + Power Button) boot to recovery mode
10. Wipe cache partition, and data/factory reset then reboot system now
11. Wait for it to boot into your sweet sweet Android Nougat 7.0 (Late version)
12. Disable auto-update if you wish, mine was on auto-update so I had to pause it half-way
Hope you find this guide helpful, I tried to remember the steps on my head as I typed, (*sorry for the grammar if you find it hard to understand) and if you think I've missed something here, let me know! I would update the guide if any step is missing, just in case
Click to expand...
Click to collapse
I just wonder this solution will be work as well? my phone is s6 edge plus G928C.
And i want to downgrade to 5.1.1 or 6.0 because 7.0 was really terrible.
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
DeadRatGames said:
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
Click to expand...
Click to collapse
It seems that your filmware is corrupt.
Which bootloader binary are you on, binary 2 or 3, Nougat or Oreo?
Remember that if you have binary 3 you cannot downgrade to binary 2.
And don't use the combination rom anymore because you have to know what you're doing its risky.
I can advise you to do a fresh install of the official country filmware from out of the box, and after that update to the latest filmware version, and a big chance to get rid of RMM prenormal state, with oem-unlock back.
If you're on binary 2, just flash an official filmware from your country before the August security patch, after that update it again to the latest version.
solamente said:
It seems that your filmware is corrupt.
Which bootloader binary are you on, binary 2 or 3, Nougat or Oreo?
Remember that if you have binary 3 you cannot downgrade to binary 2.
And don't use the combination rom anymore because you have to know what you're doing its risky.
I can advise you to do a fresh install of the official country filmware from out of the box, and after that update to the latest filmware version, and a big chance to get rid of RMM prenormal state, with oem-unlock back.
If you're on binary 2, just flash an official filmware from your country before the August security patch, after that update it again to the latest version.
Click to expand...
Click to collapse
Thanks for responding, I'm currently on binary 3 on android Oreo August security patch.
What do you mean by a fresh install from out of the box. Like Download the latest version from updato?
I apologise if I seem a little clueless lol.
DeadRatGames said:
Thanks for responding, I'm currently on binary 3 on android Oreo August security patch.
What do you mean by a fresh install from out of the box. Like Download the latest version from updato?
I apologise if I seem a little clueless lol.
Click to expand...
Click to collapse
What I meant is the first official filmware you had when the phone was bought,and if you were on binary 2, but that doesn't matter now you're on binary 3.
Now you have to flash the official filmware from your country, it must be a binary 3 filmware because downgrading will not work.
After that you have to do jailtime for 168 hours untill oem unlock is gonna appear again.
Do not restart the phone or disconnect the network at this time.
solamente said:
What I meant is the first official filmware you had when the phone was bought,and if you were on binary 2, but that doesn't matter now you're on binary 3.
Now you have to flash the official filmware from your country, it must be a binary 3 filmware because downgrading will not work.
After that you have to do jailtime for 168 hours untill oem unlock is gonna appear again.
Do not restart the phone or disconnect the network at this time.
Click to expand...
Click to collapse
Do I really need to wait 168 hours lol?
DeadRatGames said:
Do I really need to wait 168 hours lol?
Click to expand...
Click to collapse
Unfortunately you do with the 1 august patch, if you can find a previous official filmware, for example april, may, june or juli patch you can do the trick to set back the date and time 7 days and get oem unlock back.
But this does not work anymore with the august patch or later, that means you have to wait 7 days.
solamente said:
Unfortunately you do with the 1 august patch, if you can find a previous official filmware, for example april, may, june or juli patch you can do the trick to set back the date and time 7 days and get oem unlock back.
But this does not work anymore with the august patch or later, that means you have to wait 7 days.
Click to expand...
Click to collapse
How do I downgrade though?
DeadRatGames said:
How do I downgrade though?
Click to expand...
Click to collapse
At this time its impossible to downgrade from a binary 3 towards 2 or from 2 to 1.
You can only upgrade, Samsung has blocked the downgrading from a higher to a lower binary, therefore it is useless to try it with Odin, it won't succeed.
Maybe someone else knows a way around to downgrade, but I don't.
DeadRatGames said:
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
Click to expand...
Click to collapse
1. You didn't posted in the wrong section. This one is the correct one, the one where you wanted to post is reserved to ROMs, kernels and other projects.
2. Modifying Official firmwares is a bad idea if you don't know how to do it. Seems also you downloaded the wrong firmware for your phone.
3. Flashing Combination firmware is useless since OEM Toggle is still enabled (you said you were rooted so I suppose yes). RMM flag is still stored in RPMB and doesn't gets resetted by flashing that factory fw, to set RMM back to Normal you need to flash the full stock firmware for your country and wait the classic 168h countdown.
4. The "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: x, BINARY: x" is caused because you're trying to flash a firmware with a lower rev. than the one installed in your phone. You need to flash a firmware with the same or higher rev (In this case, you need a XXU3/XXS3 or higher fw). Forget to flash a fw with a lower rev since RP fuse prevents you to do it (if you force install the bl via TWRP you get an hardbrick)
BlackMesa123 said:
1. You didn't posted in the wrong section. This one is the correct one, the one where you wanted to post is reserved to ROMs, kernels and other projects.
2. Modifying Official firmwares is a bad idea if you don't know how to do it. Seems also you downloaded the wrong firmware for your phone.
3. Flashing Combination firmware is useless since OEM Toggle is still enabled (you said you were rooted so I suppose yes). RMM flag is still stored in RPMB and doesn't gets resetted by flashing that factory fw, to set RMM back to Normal you need to flash the full stock firmware for your country and wait the classic 168h countdown.
4. The "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: x, BINARY: x" is caused because you're trying to flash a firmware with a lower rev. than the one installed in your phone. You need to flash a firmware with the same or higher rev (In this case, you need a XXU3/XXS3 or higher fw). Forget to flash a fw with a lower rev since RP fuse prevents you to do it (if you force install the bl via TWRP you get an hardbrick)
Click to expand...
Click to collapse
Thanks for responding currently I am on stock official firmware for my country and waiting 7 days,6 days left. I appreciate you all for responding. I want to ask one last thing, if I wipe internal storage through TWRP and delete the OS (blank download mode) can I not install a binary 2 boot loader?
DeadRatGames said:
Thanks for responding currently I am on stock official firmware for my country and waiting 7 days,6 days left. I appreciate you all for responding. I want to ask one last thing, if I wipe internal storage through TWRP and delete the OS (blank download mode) can I not install a binary 2 boot loader?
Click to expand...
Click to collapse
Already replied: no. First, there's no relation between bootloader and system (why should a wipe let you flash a lower rev bootloader lol). And as I already explained, Rollback Prevention fuse avoids you to do that: in Odin if you try to flash a lower rev bin it returns an error. If you try to force install it via TWRP, you'll hard brick your device and get a dead phone
BlackMesa123 said:
Already replied: no. First, there's no relation between bootloader and system (why should a wipe let you flash a lower rev bootloader lol). And as I already explained, Rollback Prevention fuse avoids you to do that: in Odin if you try to flash a lower rev bin it returns an error. If you try to force install it via TWRP, you'll hard brick your device and get a dead phone
Click to expand...
Click to collapse
When I say wipe I mean like complete wipe. Delete everything not just date like fully wipe internal storage. But anyway thanks.
Reformat system.
DeadRatGames said:
When I say wipe I mean like complete wipe. Delete everything not just date like fully wipe internal storage. But anyway thanks.
Click to expand...
Click to collapse
Don't take any risks or you will be ending up with a hard brick, like Mesa said!
Just do your time 6 days I think.
solamente said:
Don't take any risks or you will be ending up with a hard brick, like Mesa said!
Just do your time 6 days I think.
Click to expand...
Click to collapse
Ok. Thanks
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
vibespredah said:
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
Click to expand...
Click to collapse
same questions
vibespredah said:
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
Click to expand...
Click to collapse
use this technic and your problem will be solved : youtube/watch?v=WmvjDEk6w4E
amazing. youre the man. cheers.
samalderon said:
use this technic and your problem will be solved : youtube/watch?v=WmvjDEk6w4E
Click to expand...
Click to collapse
omg youre the best. thanks so much.
the phone was initially on android Nougat 7.1.1, I updated it officially to android Oreo
after that, I flashed new STOCK ROM Oreo too, by Odin for the first time for this phone after unpacking and updating it from Nougat to Oreo
now I cannot flash anything by Odin TWRP, ROOT, STOCK ROM, COMBINATION FILE .... nothing pass
I can't even flash any other stock ROM beside the one i flashed before, either it's the same android version or not
odin always fail
I Waited 190 hours (more than 7 days) of continuous up time without restarting to have access and Remove FRP Lock but no luck at all, still the same
SEE ATTACHMENTS For Photos
SM-A530F/DS
Odin3 v3.13.1
Android 8.0.0 Oreo
Country / Region : Morocco (MWD)
PDA : A530FXXS4BSB1
Product Code : MWD
CSC : A530FOJM4BSB1
Phone : A530FXXU4BRL8
COMBINATION_OXM_FA71_A530FXXU4ASB1_BoxWares.tar
Which file are you trying to flash?
If I'm not wrong you could flash any firmware with version 4 or upper. For example you could not flash A530FXXU3BSA3 (Version 3) but it should be fine with A530FXXS4BSB1 (Version 4).
emovere said:
Which file are you trying to flash?
If I'm not wrong you could flash any firmware with version 4 or upper. For example you could not flash A530FXXU3BSA3 (Version 3) but it should be fine with A530FXXS4BSB1 (Version 4).
Click to expand...
Click to collapse
It looks like your trying to down grade to a version 3 and you can't do that.
Sorry wrong person.
---------- Post added at 01:37 PM ---------- Previous post was at 01:29 PM ----------
Pro Cal said:
the phone was initially on android Nougat 7.1.1, I updated it officially to android Oreo
after that, I flashed new STOCK ROM Oreo too, by Odin for the first time for this phone after unpacking and updating it from Nougat to Oreo
now I cannot flash anything by Odin TWRP, ROOT, STOCK ROM, COMBINATION FILE .... nothing pass
I can't even flash any other stock ROM beside the one i flashed before, either it's the same android version or not
odin always fail
I Waited 190 hours (more than 7 days) of continuous up time without restarting to have access and Remove FRP Lock but no luck at all, still the same
SEE ATTACHMENTS For Photos
SM-A530F/DS
Odin3 v3.13.1
Android 8.0.0 Oreo
Country / Region : Morocco (MWD)
PDA : A530FXXS4BSB1
Product Code : MWD
CSC : A530FOJM4BSB1
Phone : A530FXXU4BRL8
COMBINATION_OXM_FA71_A530FXXU4ASB1_BoxWares.tar
Click to expand...
Click to collapse
You can't flash twrp because your in prenormal state you have to wait 168 hour no reboots.
Are you trying to down grade to 7.1?
Samsung updated the binary from Nougat to oreo. Its impossible to downgrade. Its thr same with pie, you can downgrade to oreo for now as it still has the same binary on the latest security patch.
Dantar0 said:
Samsung updated the binary from Nougat to oreo. Its impossible to downgrade. Its thr same with pie, you can downgrade to oreo for now as it still has the same binary on the latest security patch.
Click to expand...
Click to collapse
You can from Pie to Oreo some country received Oreo now so they come with BL 4
emovere said:
Which file are you trying to flash?
If I'm not wrong you could flash any firmware with version 4 or upper. For example you could not flash A530FXXU3BSA3 (Version 3) but it should be fine with A530FXXS4BSB1 (Version 4).
Click to expand...
Click to collapse
thanks a lot for the feedback, appreciated
if I understood it correctly the version number is the tow characters that comes after XX like U3 or S4 right ?
how to know the version number you mentioned exactly ?
and what about TWRP then, why even TWRP won't pass
mchlbenner said:
It looks like your trying to down grade to a version 3 and you can't do that.
Sorry wrong person.
---------- Post added at 01:37 PM ---------- Previous post was at 01:29 PM ----------
You can't flash twrp because your in prenormal state you have to wait 168 hour no reboots.
Are you trying to down grade to 7.1?
Click to expand...
Click to collapse
actually I already did waited 190 of continuous up time, then after directly tried to flash TWRP and still no pass in Odin fail
I did tried to flash stock rom for 7.1.1 but even with same current version "Oreo" nothing pass
how can I know the version you mentioned please ?
Dantar0 said:
Samsung updated the binary from Nougat to oreo. Its impossible to downgrade. Its thr same with pie, you can downgrade to oreo for now as it still has the same binary on the latest security patch.
Click to expand...
Click to collapse
how to know please the exact binary version or locate ot on the PDA File for example PDA : A530FXXS4BSB1
Pro Cal said:
how to know please the exact binary version or locate ot on the PDA File for example PDA : A530FXXS4BSB1
Click to expand...
Click to collapse
For that, the binary is 4 (after the FXXS)
https://www.sammobile.com/firmwares/galaxy-a8/SM-A530F/MWD/
As you can see, Samsung updated the binary on the latest security update for your region. Its impossible to downgrade to a previous OS due to having different binaries. You'll also find that even though it's oreo, the binary updated from the January security patch to February's. Probably to make way for android 9 One UI.
The only option is to flash oreo but with the February security patch
Dantar0 said:
For that, the binary is 4 (after the FXXS)
https://www.sammobile.com/firmwares/galaxy-a8/SM-A530F/MWD/
As you can see, Samsung updated the binary on the latest security update for your region. Its impossible to downgrade to a previous OS due to having different binaries. You'll also find that even though it's oreo, the binary updated from the January security patch to February's. Probably to make way for android 9 One UI.
The only option is to flash oreo but with the February security patch
Click to expand...
Click to collapse
many thanks for the feedback and effort
so basically it means nougat is out of the question
and tell me please why country si important, I can flash any other firmware for another country as longer it the same binary version, right ?
and what about root for this binary version or TWRP why it won't pass either ?
Pro Cal said:
many thanks for the feedback and effort
so basically it means nougat is out of the question
and tell me please why country si important, I can flash any other firmware for another country as longer it the same binary version, right ?
and what about root for this binary version or TWRP why it won't pass either ?
Click to expand...
Click to collapse
You can flash a different regions firmware as long as you download the right variation. (SM-A530F)
Sorry but I don't know much about rooting this phone though
Pro Cal said:
thanks a lot for the feedback, appreciated
if I understood it correctly the version number is the tow characters that comes after XX like U3 or S4 right ?
how to know the version number you mentioned exactly ?
and what about TWRP then, why even TWRP won't pass
Click to expand...
Click to collapse
Read post if you had read before you jump this would not have happened.
You can't flash twrp because your in prenormal state you have to wait 168 hour no reboots.
Are you trying to down grade to 7.1?
mchlbenner said:
Read post if you had read before you jump this would not have happened.
You can't flash twrp because your in prenormal state you have to wait 168 hour no reboots.
Are you trying to down grade to 7.1?
Click to expand...
Click to collapse
I did read it and did answer you but it's you who didn't read mine otherwise you wouldnt repeat the same thing
*********************
actually I already did waited 190 of continuous up time, then after directly tried to flash TWRP and still no pass in Odin fail
I did tried to flash stock ROM for 7.1.1 but even with same current version "Oreo" nothing pass
Pro Cal said:
I did read it and did answer you but it's you who didn't read mine otherwise you wouldnt repeat the same thing
*********************
actually I already did waited 190 of continuous up time, then after directly tried to flash TWRP and still no pass in Odin fail
I did tried to flash stock ROM for 7.1.1 but even with same current version "Oreo" nothing pass
Click to expand...
Click to collapse
Is your phone branded.
Post this info screenshot example .
I will see if I can figure this out.
mchlbenner said:
Is your phone branded.
Post this info screenshot example .
I will see if I can figure this out.
Click to expand...
Click to collapse
Nop i dnt think so
Pro Cal said:
Nop i dnt think so
Click to expand...
Click to collapse
That as far that you can down grade to.