Database Users

Hong Kong 16GB Note 3 SM-N9005 softbrick

Hi
Got a Hong Kong 16GB Note 3 SM-N9005 which someone has attempted to flash with N9005XXUBMJ3_N9005OXABMJ3_N9005XXUBMJ2_HOME.tar.md5 in ODIN which obviously failed because of different region, now it's stuck in download mode. Trying to flash back to the only stock ZHU Hong Kong firmware available N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME.tar fails in ODIN, Kies firmware recovery fails as well.
any suggestions?
ODIN:
<ID:0/033> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/033> Odin v.3 engine (ID:33)..
<ID:0/033> File analysis..
<ID:0/033> SetupConnection..
<ID:0/033> Initialzation..
<ID:0/033> Get PIT for mapping..
<ID:0/033> Firmware update start..
<ID:0/033> SingleDownload.
<ID:0/033> NON-HLOS.bin
<ID:0/033> NAND Write Start!!
<ID:0/033> aboot.mbn
<ID:0/033> FAIL! (Auth)
<ID:0/033>
<ID:0/033> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On Phone when flashing with ODIN or Kies
SW REV CHECK FAIL : [abort]Fused 2 > Binary 1

etoko said:
Hi
Got a Hong Kong 16GB Note 3 SM-N9005 which someone has attempted to flash with N9005XXUBMJ3_N9005OXABMJ3_N9005XXUBMJ2_HOME.tar.md5 in ODIN which obviously failed because of different region, now it's stuck in download mode. Trying to flash back to the only stock ZHU Hong Kong firmware available N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME.tar fails in ODIN, Kies firmware recovery fails as well.
any suggestions?
ODIN:
<ID:0/033> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/033> Odin v.3 engine (ID:33)..
<ID:0/033> File analysis..
<ID:0/033> SetupConnection..
<ID:0/033> Initialzation..
<ID:0/033> Get PIT for mapping..
<ID:0/033> Firmware update start..
<ID:0/033> SingleDownload.
<ID:0/033> NON-HLOS.bin
<ID:0/033> NAND Write Start!!
<ID:0/033> aboot.mbn
<ID:0/033> FAIL! (Auth)
<ID:0/033>
<ID:0/033> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On Phone when flashing with ODIN or Kies
SW REV CHECK FAIL : [abort]Fused 2 > Binary 1
Click to expand...
Click to collapse
i am currently having the same phone model and same problem with you at the moment. Stuck at the Odin mode screen. I've been working on it in the last 5 - 6 hours but still cant file the solution. Please anyone help?

blackj30 said:
i am currently having the same phone model and same problem with you at the moment. Stuck at the Odin mode screen. I've been working on it in the last 5 - 6 hours but still cant file the solution. Please anyone help?
Click to expand...
Click to collapse
I had a silmarly issue with my N9005 but UK version. I flashed ITV (Italy) firmware and was stuck on Download Mode.
I have now managed to restore my phone back to UK (BTU) factory firmware.
1) Boot in Recovery Mode (Power Off, Vol+ & Home + Power On)
- Wipe Date/Factory Reset
- Wipe Cache
2) Boot into Download Mode (aka ODIN MODE) (Power Off, Vol- & Home + Power On)
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE
Note: REACTIVIATION LOCK: OFF - This must be off or you can not perform a restore.
3) Using Odin to flash your stock firmware - ODIN flash will fail
4) Using Kies 3 beta go to 'Tools -> Firmware Upgrade and Initalisation' (Follow the instructions on the screen, your will need your S/N of the phone) - You should now be back to factory firmware.

toker_X1 said:
I had a silmarly issue with my N9005 but UK version. I flashed ITV (Italy) firmware and was stuck on Download Mode.
I have now managed to restore my phone back to UK (BTU) factory firmware.
1) Boot in Recovery Mode (Power Off, Vol+ & Home + Power On)
- Wipe Date/Factory Reset
- Wipe Cache
2) Boot into Download Mode (aka ODIN MODE) (Power Off, Vol- & Home + Power On)
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE
Note: REACTIVIATION LOCK: OFF - This must be off or you can not perform a restore.
3) Using Odin to flash your stock firmware - ODIN flash will fail
4) Using Kies 3 beta go to 'Tools -> Firmware Upgrade and Initalisation' (Follow the instructions on the screen, your will need your S/N of the phone) - You should now be back to factory firmware.
Click to expand...
Click to collapse
Hi, i can't go in to stock recovery. And when i did Firmware upgrade, downloaded the firmware, then went to emergency recovery, after a while, it fail again.

blackj30 said:
Hi, i can't go in to stock recovery. And when i did Firmware upgrade, downloaded the firmware, then went to emergency recovery, after a while, it fail again.
Click to expand...
Click to collapse
same problem here :crying:
after i put my s/n its says its not good

ARIEL80 said:
same problem here :crying:
after i put my s/n its says its not good
Click to expand...
Click to collapse
One final try would be to use Odin and flash the Kernel and CSC files for your stock firmware if this fails then you probably need to take it Samsung Repair Center.

toker_X1 said:
One final try would be to use Odin and flash the Kernel and CSC files for your stock firmware if this fails then you probably need to take it Samsung Repair Center.
Click to expand...
Click to collapse
now its ok with the keis, but when its start to upgrad with the keis' its fail..
i try what you say now

If I'm not mistaken, attempting to flash MJ3 has upgraded the bootloader thefore the MI7 firmware will not flash because it has old bootloader? (aboot.mbn(?)
but there is currently no Hong Kong firmware higher than MI7, therefore its ****ed (Kies emergency recovery tries to flash MI7.
No other region firmware flashing.
No firmware downgrading.
What a joke Samsung.

etoko said:
If I'm not mistaken, attempting to flash MJ3 has upgraded the bootloader thefore the MI7 firmware will not flash because it has old bootloader? (aboot.mbn(?)
but there is currently no Hong Kong firmware higher than MI7, therefore its ****ed (Kies emergency recovery tries to flash MI7.
No other region firmware flashing.
No firmware downgrading.
What a joke Samsung.
Click to expand...
Click to collapse
Yup. So if I flash the stock bootloader together with stock rom it should work?

no.

NISIM2337 said:
no.
Click to expand...
Click to collapse
No it didn't work!!! What should i do now?
From Odin:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005ZHUBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N9005ZHUBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005ZHUBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N9005XXUBMI5_REV03_CL1252918.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ZZH_N9005ZZHBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Yeah the aboot.mbn fail.
On the device, it said "SW REV CHECK FAIL: [aboot]Fused 2 > Binary 1"
Please help. Or I have to use new BL with stock AP, CSC, CP? I think it will hard brick the phone?? hehe

blackj30 said:
No it didn't work!!! What should i do now?
From Odin:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005ZHUBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N9005ZHUBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005ZHUBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N9005XXUBMI5_REV03_CL1252918.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ZZH_N9005ZZHBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Yeah the aboot.mbn fail.
On the device, it said "SW REV CHECK FAIL: [aboot]Fused 2 > Binary 1"
Please help. Or I have to use new BL with stock AP, CSC, CP? I think it will hard brick the phone?? hehe
Click to expand...
Click to collapse
You have a brick until the stock firmware is updated with the new bootloader.

ultramag69 said:
You have a brick until the stock firmware is updated with the new bootloader.
Click to expand...
Click to collapse
true hehe it's one of the ways to keep my phone brandnew

blackj30 said:
true hehe it's one of the ways to keep my phone brandnew
Click to expand...
Click to collapse
You simply have to flash the firmware MJ3 UK and you're done.
It 'happened to me, I resolved as I told you.

frilli said:
You simply have to flash the firmware MJ3 UK and you're done.
It 'happened to me, I resolved as I told you.
Click to expand...
Click to collapse
i've done that to get to my current situation. Now basically i get the same error message on both phone and odin if i flash any kind of rom:
aboot.mbn fail
sw rev check fail
any other thing that i can do or i really have to wait for my stock rom update to launch?
pathetic that you have a new good phone but cant use

blackj30 said:
i've done that to get to my current situation. Now basically i get the same error message on both phone and odin if i flash any kind of rom:
aboot.mbn fail
sw rev check fail
any other thing that i can do or i really have to wait for my stock rom update to launch?
pathetic that you have a new good phone but cant use
Click to expand...
Click to collapse
You have 3 options:
1) Take to Samsung Repaire Center - They will charge you (in the UK its £29.99 for software faults)
2) Wait until HK Firmware gets upgraded to MJ3 (as Samsung doesnt allow downupgrade of Bootloaders)
3) Flash CWM or TWRP and install a custom rom (this will volid warranty)

toker_X1 said:
You have 3 options:
1) Take to Samsung Repaire Center - They will charge you (in the UK its £29.99 for software faults)
2) Wait until HK Firmware gets upgraded to MJ3 (as Samsung doesnt allow downupgrade of Bootloaders)
3) Flash CWM or TWRP and install a custom rom (this will volid warranty)
Click to expand...
Click to collapse
"3) Flash CWM or TWRP and install a custom rom (this will volid warranty)"-THAT OPTION DONT WORK

Have you tried flashing back to the stock HONG KONG ODIN tar file?
that should make it work again.

AllGamer said:
Have you tried flashing back to the stock HONG KONG ODIN tar file?
that should make it work again.
Click to expand...
Click to collapse
I did try flash HK TGY firmware back in many ways, but still not working. I think I will wait for TGY firmware to be upgraded. It will take forever.

blackj30 said:
I did try flash HK TGY firmware back in many ways, but still not working. I think I will wait for TGY firmware to be upgraded. It will take forever.
Click to expand...
Click to collapse
did you try flash the full firmware,not 1 file,that should be 5 files,including the bootloader and pit file.download from the chinese address.

Is my phone permanently bricked?

I was updating my samsung galaxy grand prime duos (SM-G531H) with kies, not knowing my cable was broken while the updating the phone disconnected and i ended up with a screen saying "firmware upgrade encountered an issue. please select recovery mode in kies and try again" i changed the cable and decided to flash the update with odin... process went through and the phone booted up normal with the new update installed... now i decided to factory reset so i went into the stock recovery and did but it came up with a bunch of errors which i didn't take note of... i flashed twrp and repaired the file system, wiped system and then i flashed the the firmware together with the pit file on odin once more... the phone booted up normal and i was using it and eveything when i put it to charge and came back 10 mins later the phone was off.... when i powered it on it just stays on the "samsung galaxy grand prime" screen and doesn't boot... it doesn't go into recovery anymore it just hangs whe're it says "recovery is not seandroid enforcing" i tried flashing the firmware with odin again but every single time i tried it keeps failing at...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Removed!!
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried the repair firmware together with the pit file and it gets stuck at
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
it's been like that for over an hour now... any help would be much appreciated guys.

No
Try with orignal firmware

nihu.46 said:
Try with orignal firmware
Click to expand...
Click to collapse
I tried everything and nothing seems to work

I also get this problem. Does anyone know how to fix it?

Ghettovybz said:
I tried everything and nothing seems to work
Click to expand...
Click to collapse
Remove kies. Reinstall samsung drivers.
Find and flash TWRP 3.0.0 with odin ( on recovery is not SEAndroid enforcing hold volume up and home for 5-10 seconds. Also flash the Custom Kernel by eyeless95 on the forum, its sepermissive.

u0aol said:
Remove kies. Reinstall samsung drivers.
Find and flash TWRP 3.0.0 with odin ( on recovery is not SEAndroid enforcing hold volume up and home for 5-10 seconds. Also flash the Custom Kernel by eyeless95 on the forum, its sepermissive.
Click to expand...
Click to collapse
What about for SM-G530H?
Do u have the link for the kernel?
After installing kernel what should I do then?

Two ways. Find stock rom in Sammobile and install via Odin (newest). Or try once again install it via Kies. You sould can restore it with Kies, but dont plug phone to computer. Write down S/N or something like that (it's under battery) and model, and Kies will download system

argounaut said:
What about for SM-G530H?
Do u have the link for the kernel?
After installing kernel what should I do then?
Click to expand...
Click to collapse
I have a g531h so I'm not sure. I'm below ten posts so i cant post links.
There are kernels and recoverys in the development section that work fine for your phone .

[AT&T S7] Please help if you can. ODIN flashing stock error

EDIT: I HAVE SOLVED THE ISSUE. I am not sure how but I got into a different download mode and the flash worked. I also used different SM-930A Files and it worked but system status is still custom.
I want to put my phone back to stock after I have installed a custom ROM. I have an AT&T S7. I get this error while flashing the firmware using Odin
----------------------------------------------------------------------------------------------------------
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
------------------------------------------------------------------------------------------------------
On the phone it says the following
"SW REV CHECK FAIL : [system]Fused 3 > Binary 1"
If you could tell me how to flash my phone back to stock without getting this error it would be very much appreciated.

I got the same error a while back. For me, it was because I was using Odin 3.11.1. Once I updated to Odin 3.12.3, the restore went smoothly. Someone correct me if that's not the way to fix this issue, but that is what worked for me.

lukemarcondes said:
I got the same error a while back. For me, it was because I was using Odin 3.11.1. Once I updated to Odin 3.12.3, the restore went smoothly. Someone correct me if that's not the way to fix this issue, but that is what worked for me.
Click to expand...
Click to collapse
I have resolved the issue. I have been trying for almost a month now to fix the phone and I finally did it. The device still says custom although I have flashed the official firmware on. Somehow I got into an alternative download mode that accepted the flash. I have no clue how I got it into the mode but it only said "downloading" and showed nothing in the top right corner. No white text.

ColbyTrip1 said:
I have resolved the issue. I have been trying for almost a month now to fix the phone and I finally did it. The device still says custom although I have flashed the official firmware on. Somehow I got into an alternative download mode that accepted the flash. I have no clue how I got it into the mode but it only said "downloading" and showed nothing in the top right corner. No white text.
Click to expand...
Click to collapse
I see. Glad you were able to fix it!

Trying to install stock fw using Odin - can't get it working

Hello,
I've been on a custom ROM for a few weeks and wanted to go back to Stock now that Oreo has been released.
I'm having difficulty to install stock using Odin 3.1.2 using latest stock firmware.
This is my log from Odin:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
The boxes doesn't show any progression or FAIL.

ME TOO ...Anybody knows Why?... in the past I used Odin several times and ever works fine.. So now I reinstall the drivers, change the PC, USB Cable, etc... and nothing...
I just flash only the BL and this is the result:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin.lz4
Please help us...

coiae said:
ME TOO ...Anybody knows Why?... in the past I used Odin several times and ever works fine.. So now I reinstall the drivers, change the PC, USB Cable, etc... and nothing...
I just flash only the BL and this is the result:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin.lz4
Please help us...
Click to expand...
Click to collapse
Are you using the latest version of Odin?

for me, if i don't flash my personal branded firmware (oreo or nougat) it fails. i must flash only my ITV (italy nobrand). if i try to flash TIM branded ita, it fails

Thanx adj998. You have all reason. My version of ODIN was 3.12.3 and this version don't work with the latest firmware of Samsung S8.
I am looking on Internet.... and that's it... I find a new version of ODIN 3.13.. See attachment
All working perfect. (This link have the last version)
https://www.theandroidsoul.com/download-odin/
adj998 said:
Are you using the latest version of Odin?
Click to expand...
Click to collapse

coiae said:
Thanx adj998. You have all reason. My version of ODIN was 3.12.3 and this version don't work with the latest firmware of Samsung S8.
I am looking on Internet.... and that's it... I find a new version of ODIN 3.13.. See attachment
All working perfect. (This link have the last version)
https://www.theandroidsoul.com/download-odin/
Click to expand...
Click to collapse
Awesome glad it worked for you

Managed to go back to stock but my apps still think I am rooted. Any ideas why? Is it the firmware?

adicken said:
Managed to go back to stock but my apps still think I am rooted. Any ideas why? Is it the firmware?
Click to expand...
Click to collapse
If you've rooted a g950f/g955f, then you've tripped Knox permanently, even if you install stock firmware it will stay tripped. Because of this, any Samsung app that uses Knox such as s-health and s-pay, and so on will say you are rooted, only way to solve this issue is to flash custom rom

Samsung Galaxy S8 no OS while current binary is custom (0xe) Odin fails flashing roms

After rooting my Samsung Galaxy S8 I accidentally wiped all data including the OS. I'm completely new to this and wish for some detailed help from a professional.
Odin keeps giving a fail at param.bin using different ROMs. I've heard it might be the bootloader version that's incompatible but I'm not sure what to do and which bootloader version I have. I'm using the same firmware I've downloaded from sammobile before for my model number SM-G950F and even an extra one with Android pie on it, the same android version before this happened, but to no avail. Here is the log from Odin. Appreciate all help since I wiped the data after being stuck in the bootloader with a Samsung logo on it (alone) but after wiping everything it's the screen before it with the samsung logo AND "powered by android".
It may be relevant to note that I'd rather use Odin than an SD-card.
Edit: I checked the download screen on my s8 and found an error saying that SW REV. Failed Bootloader device 6 binary 4. I checked next to SWREV: B:6
So it apparently is a binary incompatibility for bootloader. Now my question is where can I find the suitable binary? All I see while downloading firmware is the model version and the date but not the binary.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5716 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> param.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in advance!

It worked!
So as a beginner's guide you need to check the error code given after failing in Odin in the download screen in the phone itself at the end of these codes.
My error code was as mentioned in the edit that I was trying to install a firmware with a binary version 4 whereas my device's version is 6. To find the correct firmware version you need to look for the part in the PDA code where it says U6 or U5 or U4 (binary version 6, 5 or 4 as examples respectively).
PDA code is for example: G950FXXU6DSK9 as in my case. This is different from the CSC code, you can find both in the sammobile website. You just have to compare your device's binary version found next to SWREV and identified with a B up among the codes in the download screen of your phone (after holding volume down power and bixby at the same time).
That's it. Special thanks to ZeroXO who contributed to the resolution of the issue and was very helpful ^^

Kindly share your experiences after you rooted your device. What are the pros n cons?