Database Info

Need Help With My S6 ASAP Please.

Hello wise people of XDA,
This is my first post.
I currently use an S6 G920F United Kindom unlocked as my phone and i have been using this phone for a long time. Now its past its warranty I decided to root the phone and see what i can do with it and get rid of the bloatware. Normally i either use KingoRoot or KingRoot but both failed so I searched around on the internet and came across CF Auto Root. After seeing it was successful for others i jumped on the bandwagon. I rooted it and everything was golden until i came across a problem, it would randomly turn off. This was random and infrequent. but not it happens like 5 times a day so i decided to flash a stock rom. For some strange reason Sam mobile wont let me download a stock Rom so after poking around the internet i have download a few stock roms however they always fail in Odin. Now my phone wont even boot as it says "error occured while updating use smart switch emergency recovery feature" so i go onto the Smart switch PC app and then it doesnt recognise. After 2 days of trying i haven't had any luck so I don't know what to so. Every time I try flashing something, when it fails i get some red text on the phone which I don't understand.
Someone please help me as I cant just buy a new phone and this is the only phone i have got. Any help would be very grateful and please don't hesitate to ask any questions.
Edit:
It says on the Download Screen:
Odin Mode
Product Name: SM-G920F
Current Binary: Custom
System Status: Custom
Reactivation Lock: Off
Secure Download: Enabled
Knox Warranty Woid : 1 (0x0500)
RP SWREV: B:6 K:2 S:2
(When it fails it says) SW REV. Check Fail. Device:6 . Binary: 5
Hopefully that helped.

Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).

Bryan48765 said:
Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).
Click to expand...
Click to collapse
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.

wasim.1.wt said:
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.
Click to expand...
Click to collapse
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.

Bryan48765 said:
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.
Click to expand...
Click to collapse
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!

wasim.1.wt said:
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!
Click to expand...
Click to collapse
U6/S6, "Device:6" is in the odin log so it's already 6 and won't return to 5.

Combination Firmware A8 (2018) SW rev check fails device 3 binary 2.

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.

Sos help - nothing pass by odin

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.

[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

I can not flash any official firmware!1 PLEASE HELP ME

Hi,
I got my phone from Germany and tried to flash Nordic stock rom with Odin. enabled developer option but did not tick OEM UNLOCK!
After start ordin, I got error on my phone:
ODIN mode (AVB Fail)
product: Error validation footer
product: error verifying vbmeta image
SAMSUNG product ...
I can restart again to download mode, but it is not allowing me to flahs any firmware!!
I tried Germany android 10 , Nordic one and one from UK as a test, but it is keep saying pit_binary_flash unsupported version!!!
What does it mean, theversion is 10 and the coiuntry is the same!! i used the same CSC and the same AP ... Damn
Any help guys??????????????

mehdi.moha said:
Hi,
I got my phone from Germany and tried to flash Nordic stock rom with Odin. enabled developer option but did not tick OEM UNLOCK!
After start ordin, I got error on my phone:
ODIN mode (AVB Fail)
product: Error validation footer
product: error verifying vbmeta image
SAMSUNG product ...
I tried to hold volumegdown + power button. but it restartes to the same screen!!
please help.
It is not entering to recovery also, only volume down+power is responding
Click to expand...
Click to collapse
any helppppppppppppppppp??

please guys, any help???????????????????????????

I managed toget todownload mode, butnow I can not flash any officiam rom! for any android 10 it says :
pit_flash_binary unsupported version
I cant boot to os
any help?

mehdi.moha said:
I managed toget todownload mode, butnow I can not flash any officiam rom! for any android 10 it says :
pit_flash_binary unsupported version
I cant boot to os
any help?
Click to expand...
Click to collapse
Is there anyone here that can help me please ????

Change the Odin version.
---------- Post added at 14:39 ---------- Previous post was at 14:36 ----------
Be sure you use v3.14.4.

marselcj said:
Change the Odin version.
---------- Post added at 14:39 ---------- Previous post was at 14:36 ----------
Be sure you use v3.14.4.
Click to expand...
Click to collapse
I just got 3.4.14
It is the same

Are you sure you flash the proper firmware for SM-N975F?

marselcj said:
Are you sure you flash the proper firmware for SM-N975F?
Click to expand...
Click to collapse
I used this link:
https://www.imei.info/download-firmware/samsung/samsung-galaxy-note10plus-exynos/SM-N975F/DBT/pda/
The latest one is on the top.
I also tried to use older ones, but still it says version not supported!
Never faced to this kind of issue in my life.

Solved,
I should search for bin 2 only, shouldnt use Bin firmwares.

mehdi.moha said:
Solved,
I should search for bin 2 only, shouldnt use Bin firmwares.
Click to expand...
Click to collapse
,
Im facing same problem than you, bought in Finland samsung s10e last july tried to downgrade to Android 9 because severe battery drain after the february update, downloaded from sammobile NEE version but when start to flash in odin the phone does not do anything and end in flash error.
Tried to test without luck also BTU uk version but same problem.
The error code is this one
SW REV CHECK FAIL
device:4
binary:3
pit flash binary unsupported version .
Any help will be very good.
thanks in advance.

gusmas said:
,
Im facing same problem than you, bought in Finland samsung s10e last july tried to downgrade to Android 9 because severe battery drain after the february update, downloaded from sammobile NEE version but when start to flash in odin the phone does not do anything and end in flash error.
Tried to test without luck also BTU uk version but same problem.
The error code is this one
SW REV CHECK FAIL
device:4
binary:3
pit flash binary unsupported version .
Any help will be very good.
thanks in advance.
Click to expand...
Click to collapse
aha, that is because the downgrade is not allowed. there is no way to downgrade your phone,
The only solution is to flash android 10 again on your phone.
for example,take a look at here:
https://www.samfw.com/firmware/SM-N975F/NEE
there is a Tab named Bit, for me the problem was i tried to use Bit 1 while my phone is Bit 2. for the same reason I got error: device:2 binary:1
So I think it means using Bin 1 is incorrect
So I flashed Bin 2 and worked.
Hope it solve your problem since it toke 3 days froms me to find the solution.
Please reply here if did not work:good:

mehdi.moha said:
aha, that is because the downgrade is not allowed. there is no way to downgrade your phone,
The only solution is to flash android 10 again on your phone.
for example,take a look at here:
https://www.samfw.com/firmware/SM-N975F/NEE
there is a Tab named Bit, for me the problem was i tried to use Bit 1 while my phone is Bit 2. for the same reason I got error: device:2 binary:1
So I think it means using Bin 1 is incorrect
So I flashed Bin 2 and worked.
Hope it solve your problem since it toke 3 days froms me to find the solution.
Please reply here if did not work:good:
Click to expand...
Click to collapse
Thanks for the info I will try again with the new method you suggested, best regards.

I cant get into download mode every time I try it just restart

Smartphones13 said:
I cant get into download mode every time I try it just restart
Click to expand...
Click to collapse
Turn phone off hold voulme up and down together, and then plug in USB C cable it will boot into download mode! Well that's how i boot into download mode Note 9!

gusmas said:
,
Im facing same problem than you, bought in Finland samsung s10e last july tried to downgrade to Android 9 because severe battery drain after the february update, downloaded from sammobile NEE version but when start to flash in odin the phone does not do anything and end in flash error.
Tried to test without luck also BTU uk version but same problem.
The error code is this one
SW REV CHECK FAIL
device:4
binary:3
pit flash binary unsupported version .
Any help will be very good.
thanks in advance.
Click to expand...
Click to collapse
Hi,
th error message means your phone ion a newer software version than the one you flashed on it