Database Info

SM J500H sw rev check fail fused 2 binary 1

hello can you please help me I really hate android 6.1
I flashed my j5 sm j500h with Odin installed android marshmallow downloaded it from SamMobiles
when I tried to flash back android lollipop 5.1 it gave me this error in download mode sw rev check fail fused 2 binary 1
Odin failed to flash it
please help me ASAP battery draining real fast on android 6.1

J500h same this problem after rooted my devices
:after rooted my devices odin fail auth devices screen show this message fused 2 > binary 1 please solve this problem

Wajikhan said:
:after rooted my devices odin fail auth devices screen show this message fused 2 > binary 1 please solve this problem
Click to expand...
Click to collapse
You are trying to flash something that has a lower binary than the firmware that is currently installed on your device. In other words, you cannot downgrade your firmware via Odin, the bootloader will not allow it. Find the build number for the stock firmware that is on your device, look at the 5th digit from the right end of your firmware number, then, compare that to the 5th digit from the end of the build number that you are trying to flash. If the 5th digit from the right end of the firmware that is currently installed on the device has a 2 or higher in that position, you can only flash a firmware that is binary 2 or higher, you can't go back to a firmware that is binary 1. If you have a binary 3 firmware, you can't go back to binary 2 or binary 1. If you have a binary 4 firmware, you can't go back to binary 3 or binary 2 or binary 1.
You can only flash the build number that you currently have on the device or you can flash a newer build number, you cannot flash an older build number. Samsung bootloader will not allow downgrading the binary.
What method did you use to root your device? Did you use TWRP or Magisk to root your device? I'm willing to be that you did not use TWRP or Magisk because you probably have a locked bootloader, which is why the binary is preventing Odin flashing.
Sent from my SM-S767VL using Tapatalk
---------- Post added at 11:53 AM ---------- Previous post was at 11:47 AM ----------
armando1990 said:
hello can you please help me I really hate android 6.1
I flashed my j5 sm j500h with Odin installed android marshmallow downloaded it from SamMobiles
when I tried to flash back android lollipop 5.1 it gave me this error in download mode sw rev check fail fused 2 binary 1
Odin failed to flash it
please help me ASAP battery draining real fast on android 6.1
Click to expand...
Click to collapse
Simple, you can't downgrade Samsung firmware unless the downgraded firmware has the same binary as your currently installed firmware or a higher binary, you can't flash a firmware that has a lower binary than your current firmware. In other words, you seem to have a binary 2 firmware currently installed and you're trying to flash a binary 1 firmware, the binary 2 bootloader will not allow the binary 1 firmware to flash. You can flash a binary 2 or higher firmware but not a binary 1.
Sent from my SM-S767VL using Tapatalk

Downgrade Android 8 to 7 - Binary 3?

Hello,
I am attempting to downgrade from Android 8 to 7 on Galaxy S7. When I attempt to flash the old firmware I get the error 'Device 3 - Binary 2'. Does anyone know if there is a workaround for this yet?

DannySB1 said:
Hello,
I am attempting to downgrade from Android 8 to 7 on Galaxy S7. When I attempt to flash the old firmware I get the error 'Device 3 - Binary 2'. Does anyone know if there is a workaround for this yet?
Click to expand...
Click to collapse
Odin will not let you flashback to a previous boot loader version, you have to do it through TWRP. So either flash the nougat firmware with TWRP first or any nougat based rom, then flash nougat via odin which will remove root and TWRP.

cooltt said:
Odin will not let you flashback to a previous boot loader version, you have to do it through TWRP. So either flash the nougat firmware with TWRP first or any nougat based rom, then flash nougat via odin which will remove root and TWRP.
Click to expand...
Click to collapse
Are there any instructions for this?
Will secure apps (Banking etc) work again after removing root?

I was under the impression you could via Odin if OEM unlock was enabled, without needing TWRP or root. https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-downgrade-android-oreo-8-0-t3821495
edit: As for banking, if you go root then flash back to stock you should have no issues. Even if you stay root, things like Magisk will hide root status from apps and pass safetynet. Your biggest issue would be the loss of Knox, which voids warranty and breaks some Samsung apps.

Beanvee7 said:
I was under the impression you could via Odin if OEM unlock was enabled, without needing TWRP or root. https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-downgrade-android-oreo-8-0-t3821495
Click to expand...
Click to collapse
It is not possible as per some of the replies to that thread. I spent a few hours playing TWRP yesterday and it was not possible either.

DannySB1 said:
It is not possible as per some of the replies to that thread. I spent a few hours playing TWRP yesterday and it was not possible either.
Click to expand...
Click to collapse
Ok so listen, it can be done as i said but it's not easy. The choice you have of course before attempting this is to just install a android 7 custom ROM? many nougat ROMs are just stock with the bloatware removed and the boot-loader version isn't checked during flash.
Here's another way to go back, i can't guarantee it will work though i haven't tried it on an S7.
Downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's how's it done?
Download the firmware file (.tar) which you want to downgrade to and open it with an archiver application (7zip). Extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends in .bin (e.g. sboot.bin etc.). This .tar file can now be flashed like any other firmware file via Odin and it should run through it without any problems.
Hope this helps.

plz tell me how to downgrade i upgraded my phone to oreo now there's no network i need to downgrade back to marshmellow i also installed marshmellow but it stuck on samsung bootloop plz help me

Bipnbarsha said:
plz tell me how to downgrade i upgraded my phone to oreo now there's no network i need to downgrade back to marshmellow i also installed marshmellow but it stuck on samsung bootloop plz help me
Click to expand...
Click to collapse
What device? What firmware? What Rom?

S7 edge on oreo and stock rom my network was working fine on marshmellow but after oreo update my mobile network not working unfortunatly my binary has been updated before update i back up everything with twrp but now when i restore using twrp my phone stuck on samsung logo plz help mee

downgrand note 9 N9600 ZTO
i need to downgrand my note 9 i pay for the service of someone who can help me. i'm on the last firmawre bdo android 9 and i want to downgrand to the latest firmware of android 8.1. My note 9 is the N9600 ZTO.
email
[email protected]
whatsapp and telegram
+5582994311001

cooltt said:
Ok so listen, it can be done as i said but it's not easy. The choice you have of course before attempting this is to just install a android 7 custom ROM? many nougat ROMs are just stock with the bloatware removed and the boot-loader version isn't checked during flash.
Here's another way to go back, i can't guarantee it will work though i haven't tried it on an S7.
Downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's how's it done?
Download the firmware file (.tar) which you want to downgrade to and open it with an archiver application (7zip). Extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends in .bin (e.g. sboot.bin etc.). This .tar file can now be flashed like any other firmware file via Odin and it should run through it without any problems.
Hope this helps.
Click to expand...
Click to collapse
Hey man, can you please explain this better ? Im using a galaxy s7 edge, but my firmware doesnt have a TAR file. there are 4 .md5 files (AP,BL,CP,CSC) that are flashable through odin. I want to downgrade bootloader

laurentiudll said:
Hey man, can you please explain this better ? Im using a galaxy s7 edge, but my firmware doesnt have a TAR file. there are 4 .md5 files (AP,BL,CP,CSC) that are flashable through odin. I want to downgrade bootloader
Click to expand...
Click to collapse
Hello that method no longer works, you can't downgrade anymore

cooltt said:
Hello that method no longer works, you can't downgrade anymore
Click to expand...
Click to collapse
I can downgrade to 14.1 Lineage OS.
Edit: There is no way do downgrade the official firmware

Won't boot into anything but DL mode, error SW rev check fail (bootloader) device: 5

EDIT: This problem has been resolved thanks to good advice in this thread!
I'm not sure what I've managed to do, but here are the symptoms:
I installed a custom rom and it was working, had TWRP and magisk installed, but couldn't get the s7 exynos to recognize that magisk was installed. I attempted to restore to a stock rom. At this point, it will not boot past the samsung logo. It will also not boot into recovery. I can boot into download mode. The DL mode screen reports the error SW rev check fail (bootloader) device: 5 binary: 2
No matter stock ROM what I attempt to flash via Odin, just after the process log gets to sboot.bin, the next line is FAIL! then Complete (Write) operation failed. I am attempting to flash the latest version of 8.0 from sammobile for s7 exynos (I selected BTU).

kettir said:
I'm not sure what I've managed to do, but here are the symptoms:
I installed a custom rom and it was working, had TWRP and magisk installed, but couldn't get the s7 exynos to recognize that magisk was installed. I attempted to restore to a stock rom. At this point, it will not boot past the samsung logo. It will also not boot into recovery. I can boot into download mode. The DL mode screen reports the error SW rev check fail (bootloader) device: 5 binary: 2
No matter stock ROM what I attempt to flash via Odin, just after the process log gets to sboot.bin, the next line is FAIL! then Complete (Write) operation failed. I am attempting to flash the latest version of 8.0 from sammobile for s7 exynos (I selected BTU).
Click to expand...
Click to collapse
Device 5 means boot loader version 5, binary 2 means bootloder your trying to flash is older, you cannot flash an older boot loader than version 5. This means the firmware you are trying to flash is not the latest.
Sammobile has BTU version 5, search for it and download it, follow the guide how to flash.

cooltt said:
Device 5 means boot loader version 5, binary 2 means bootloder your trying to flash is older, you cannot flash an older boot loader than version 5. This means the firmware you are trying to flash is not the latest.
Sammobile has BTU version 5, search for it and download it, follow the guide how to flash.
Click to expand...
Click to collapse
Thank you, this is invaluable advice and just what I was hoping for.
When the phone arrived I could briefly see that it was a Saudi Arabia firmware. Looking at saudi STC SFU the date is 7/1/19, that might explain this. I flashed Alexndr 8.0 over that. It was during the time I tried to get magisk to stick that I bricked the phone.
I did download and attempt (with fail) to flash G930FXXS4ESC1_G930FOXA4ERKF_BTU dated 5/12/19 on the sammobile page. So I may try United Kingdom dated 7/11/19 and see if that will flash. I can't tell which version of BTU might have a boot loader version 5 among those listed. Does this seem a reasonable attempt to you?
EDIT: I did download and flash, and it's starting to boot....huzzah! I'm now filling out the startup information. Thank you!!

kettir said:
Thank you, this is invaluable advice and just what I was hoping for.
When the phone arrived I could briefly see that it was a Saudi Arabia firmware. Looking at saudi STC SFU the date is 7/1/19, that might explain this. I flashed Alexndr 8.0 over that. It was during the time I tried to get magisk to stick that I bricked the phone.
I did download and attempt (with fail) to flash G930FXXS4ESC1_G930FOXA4ERKF_BTU dated 5/12/19 on the sammobile page. So I may try United Kingdom dated 7/11/19 and see if that will flash. I can't tell which version of BTU might have a boot loader version 5 among those listed. Does this seem a reasonable attempt to you?
EDIT: I did download and flash, and it's starting to boot....huzzah! I'm now filling out the startup information. Thank you!!
Click to expand...
Click to collapse
Great.
The boot loader version is shown in the firmware, G930FXXS4ESC1 is boot loader version 4, S4= V4.
S5 = V5 etc.
For info, version 5 (S5) was the final BTU firmware release for the S7 so no more firmware updates after that.

cooltt said:
Great.
The boot loader version is shown in the firmware, G930FXXS4ESC1 is boot loader version 4, S4= V4.
S5 = V5 etc.
For info, version 5 (S5) was the final BTU firmware release for the S7 so no more firmware updates after that.
Click to expand...
Click to collapse
Thanks for the clue, it is much appreciated!

Please help I wiped my note 9 from TWRP and Odin is stuck at recovery.img

Hi guy I am panicking here I accidentally wiped everything from my samsung note 9 and there is no OS on the phone. I tried to flash older firmware but Odin is stuck at recovery and the phone shows a red line saying "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 6, BINARY:5
PLEASE SOMEONE HELP ME

Skulper said:
Hi guy I am panicking here I accidentally wiped everything from my samsung note 9 and there is no OS on the phone. I tried to flash older firmware but Odin is stuck at recovery and the phone shows a red line saying "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 6, BINARY:5
PLEASE SOMEONE HELP ME
Click to expand...
Click to collapse
The firmware that you flashed has a lower binary than the firmware that you had on the device before you modified it. You need to flash a firmware that has the same binary as what you had before you modified the device, or you need to flash a firmware that has a higher/newer binary than what you had.
See where the error says that your device is binary 6 but the firmware that you flashed has binary 5? You need a binary 6 or higher firmware. You can identify the binary by looking at the 5th character from the right end of the firmware build number.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
The firmware that you flashed has a lower binary than the firmware that you had on the device before you modified it. You need to flash a firmware that has the same binary as what you had before you modified the device, or you need to flash a firmware that has a higher/newer binary than what you had.
See where the error says that your device is binary 6 but the firmware that you flashed has binary 5? You need a binary 6 or higher firmware. You can identify the binary by looking at the 5th character from the right end of the firmware build number.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
i think i might be in love with you,(not in a weird way) this reply here saved my ass,i was stuck on odin wondering what was wrong & just this simple explanation helped me a lot

brokboi said:
i think i might be in love with you,(not in a weird way) this reply here saved my ass,i was stuck on odin wondering what was wrong & just this simple explanation helped me a lot
Click to expand...
Click to collapse
Be aware, once you flash a firmware that upgrades your device binary to a higher binary, you can not go back to the lower binary. A lot of times, flashing a firmware that upgrades the binary also upgrades the bootloader to a more secure bootloader that can't be unlocked, this kills virtually any chance of rooting the device or flashing TWRP custom recovery and/or custom ROMs. Then you're stuck with a device that you can't modify the way you want.

Droidriven said:
Be aware, once you flash a firmware that upgrades your device binary to a higher binary, you can not go back to the lower binary. A lot of times, flashing a firmware that upgrades the binary also upgrades the bootloader to a more secure bootloader that can't be unlocked, this kills virtually any chance of rooting the device or flashing TWRP custom recovery and/or custom ROMs. Then you're stuck with a device that you can't modify the way you want.
Click to expand...
Click to collapse
Ya i had that in mind so i flashed accordingly & i have unlocked bootloader with twrp not that i needed it though, cuz i just wanted to use samsung dex

brokboi said:
Ya i had that in mind so i flashed accordingly & i have unlocked bootloader with twrp not that i needed it though, cuz i just wanted to use samsung dex
Click to expand...
Click to collapse
Have you used TWRP to create a android backup of your stock ROM after you got it fixed? If not, do so, then store a copy of the backup on a PC or USB flashdrive, external sdcard, etc.. That backup can be used to restore your device, if needed.

Combination firmware.

Hey guys and girls I'm really confused by combination firmware . I'm looking for some for a galaxy S10 lite .
Current firmware is g770fxxs4euf6
I've found some combination files but I'm not sure which one I need I read about numbers and codes having to match and don't want to get the wrong one so how do I know which is the right one please ?

hainguyenthao said:
Here it is G770FXXU4AUA1
But you will need pit token to flash it cause it is a new device model
Click to expand...
Click to collapse
Thank you appreciate it can I get that from original firmware ?

teamtatty11 said:
Hey guys and girls I'm really confused by combination firmware . I'm looking for some for a galaxy S10 lite .
Current firmware is g770fxxs4euf6
I've found some combination files but I'm not sure which one I need I read about numbers and codes having to match and don't want to get the wrong one so how do I know which is the right one please ?
Click to expand...
Click to collapse
If you look at the build number of a Samsung firmware, the 5th character from the right end of the build number is the "Binary version". In the build number of the firmware that you posted above, the 5th character from the right in that build number is a 4. This means that your firmware is a binary 4 firmware.
The binary version is important because it prevents a user from downgrading the firmware. When flashing a firmware file, if the binary version of what you are trying to flash is lower than the binary of the currently installed firmware, then you can not flash the lower binary firmware. You can only flash a firmware that has a binary version that is equal to or higher than the binary of the currently installed firmware.
In your case, you have a binary 4 firmware currently installed, this means you can not flash a binary 3, 2 or 1 firmware, you can only flash a binary 4 firmware or higher. If you ever flash a higher binary, for example, from binary 4 to binary 5, you could never go back to binary 4 and if you flash from binary 5 to binary 6, you could never go back to 5 or 4. You can never go back, you can stay where you are or go higher.

Droidriven said:
If you look at the build number of a Samsung firmware, the 5th character from the right end of the build number is the "Binary version". In the build number of the firmware that you posted above, the 5th character from the right in that build number is a 4. This means that your firmware is a binary 4 firmware.
The binary version is important because it prevents a user from downgrading the firmware. When flashing a firmware file, if the binary version of what you are trying to flash is lower than the binary of the currently installed firmware, then you can not flash the lower binary firmware. You can only flash a firmware that has a binary version that is equal to or higher than the binary of the currently installed firmware.
In your case, you have a binary 4 firmware currently installed, this means you can not flash a binary 3, 2 or 1 firmware, you can only flash a binary 4 firmware or higher. If you ever flash a higher binary, for example, from binary 4 to binary 5, you could never go back to binary 4 and if you flash. You can never go back, you can stay where you are or go higher.
Click to expand...
Click to collapse
Ahh thank you for the explanation I understand that now and have the correct firmware I believe .
Any idea how I can get a pit file ? I've got the stock firmware and tried adding .zip on the end but this didn't work for me .

teamtatty11 said:
Thank you appreciate it can I get that from original firmware ?
Click to expand...
Click to collapse
You should not need the PIT and if you do, it should be packed in the firmware file somewhere.
hainguyenthao said:
Here it is G770FXXU4AUA1
But you will need pit token to flash it cause it is a new device model
Click to expand...
Click to collapse

teamtatty11 said:
Ahh thank you for the explanation I understand that now and have the correct firmware I believe .
Any idea how I can get a pit file ? I've got the stock firmware and tried adding .zip on the end but this didn't work for me .
Click to expand...
Click to collapse
Your firmware should be in .tar format, if it isn't, you probably need to extract it until you get a .tar.md5, then flash that via Odin.

Droidriven said:
Your firmware should be in .tar format, if it isn't, you probably need to extract it until you get a .tar.md5, then flash that via Odin.
Click to expand...
Click to collapse
when i tried installing via odin it said i needed the pit file i'll keep playing and see where i can get appreciate the help .

teamtatty11 said:
when i tried installing via odin it said i needed the pit file i'll keep playing and see where i can get appreciate the help .
Click to expand...
Click to collapse
The PIT is usually packaged in the firmware file somewhere. Try extracting the files in the firmware then extract those files and keep extracting the files down, look through the extracted files until you find the PIT file.
Or
Do some Google searches for:
"PIT file for (your specific model number"
Or
If there are older versions of firmware for your model number that you can download, download one of them and extract it and keep extracting those files while looking through them until you find the PIT file.

teamtatty11 said:
when i tried installing via odin it said i needed the pit file i'll keep playing and see where i can get appreciate the help .
Click to expand...
Click to collapse
If none of that works, there is also a way to pull a PIT file from the device itself by using adb shell commands but I'm not sure if it requires rooting the device or not.
Yep, requires root.
https://www.getdroidtips.com/how-to-extract-pit-files-for-any-samsung-galaxy-device/

Droidriven said:
The PIT is usually packaged in the firmware file somewhere. Try extracting the files in the firmware then extract those files and keep extracting the files down, look through the extracted files until you find the PIT file.
Or
Do some Google searches for:
"PIT file for (your specific model number"
Or
If there are older versions of firmware for your model number that you can download, download one of them and extract it and keep extracting those files while looking through them until you find the PIT file.
Click to expand...
Click to collapse
Thank you the person above who commented said that only people with access to Samsung servers can get the pit file and it will cost 64 dollars so I'm not sure . I did try extract from firmware I got from sammobile but it was password protected and I couldn't seem to find a password anywhere . I'll keep digging though I've not got anything to lose at this point . All a learning curve . Really appreciate the help