Database Users

[Q] ODIN fails i337m - bricked - HELP

Hello,
Hello,
Samsung S4 from Canada - Provider Bell - Model SGH-I337M
Phone was functional, new in box, with latest November firmware.
Soft Bricked it when Odin failed (auth) to downgrade from latest frimware to 4.22 (reason for downgrade: unlock codes not working; USB unlock not working due to new security features in latest update).
Tried steps in http://forum.xda-developers.com/showthread.php?t=2261153 using Kies and that also fails with - PC failed to recognise the mobile phone
Now trying to upload latest firmware using Odin 3.09, i get FAILED:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On Phone, looks like 2% done (blue bar)
Is this phone garbage????
Thanks !!

Hey have you tried re-flashing the original bell rom? Or did you have a backup? I haven't bricked my s4 but I bricked my S3 multiple times and I ended up bringing it back with a basic ATT rom before getting the rom I wanted to work.
So first try flashing your original stock rom (if you have it or go to your backup)
Next step try an ATT stock rom.
If that doesn't fix it, someone more experienced will have to chime in.
mfreeman3769 said:
Hello,
Hello,
Samsung S4 from Canada - Provider Bell - Model SGH-I337M
Phone was functional, new in box, with latest November firmware.
Soft Bricked it when Odin failed (auth) to downgrade from latest frimware to 4.22 (reason for downgrade: unlock codes not working; USB unlock not working due to new security features in latest update).
Tried steps in http://forum.xda-developers.com/showthread.php?t=2261153 using Kies and that also fails with - PC failed to recognise the mobile phone
Now trying to upload latest firmware using Odin 3.09, i get FAILED:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On Phone, looks like 2% done (blue bar)
Is this phone garbage????
Thanks !!
Click to expand...
Click to collapse

Odin fails due to the firmware
Hello,
Finally I found the issue. The File at Sam Mobile version 4.2.2 for Bell is the cause. It fails at 2% upload. The 4.3 file restored the phone, but had to root using CF-AUTO-ROOT in order to get the /data folder back (phone stuck in a loop in boot animation).
The other file available there, an older 4.2.2 is corrupt once downloaded (tried 3 times).
Reason I was flashing back to 4.2.2 is because with the new Bell 4.3 firmware, network unlock codes no longer work (changed??) and neither does USB unlocking (new security feature).
It is conceivable that the new 4.3 frimware from this provide is the cause of the Odin failure at 2% for 4.2.2 ?
Any other good reliable sources for a 4.2.2 firmware version pre ME1 ?
Samsung S4 i337m for Bell (Canada) ??
Thanks!

Try this: launch Samsung Kies and go to Tools -> Firmware Upgrade and Initialization.
I tied it (my phone work now) but i have always the same trouble with ODIN (nothing can't put in except CF-AUTO-ROOT don't tell me fail)

mfreeman3769 said:
Hello,
Finally I found the issue. The File at Sam Mobile version 4.2.2 for Bell is the cause. It fails at 2% upload. The 4.3 file restored the phone, but had to root using CF-AUTO-ROOT in order to get the /data folder back (phone stuck in a loop in boot animation).
The other file available there, an older 4.2.2 is corrupt once downloaded (tried 3 times).
Reason I was flashing back to 4.2.2 is because with the new Bell 4.3 firmware, network unlock codes no longer work (changed??) and neither does USB unlocking (new security feature).
It is conceivable that the new 4.3 frimware from this provide is the cause of the Odin failure at 2% for 4.2.2 ?
Any other good reliable sources for a 4.2.2 firmware version pre ME1 ?
Samsung S4 i337m for Bell (Canada) ??
Thanks!
Click to expand...
Click to collapse
You might want to check which bootloader you are on, you can do this through terminal on the the phone (instructions burried somewhere in one of the threads) or download Phone INFO from the play store, it will display which bootloader you are on. Once you know that, see if you can find a thread (search) on downgrading from 4.3 to 4.2

Note 3 SM-N9005 Firmware Issue & Device Recognised As 'Samsung GT-S5690'

Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John

Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Click to expand...
Click to collapse
hello. have you tried another version of odin? im sure someone can help you revive your phone

Mine did the same thing,put it into download mode and flash cwm recovery and it'll come to life..

hypnodaz said:
Mine did the same thing,put it into download mode and flash cwm recovery and it'll come to life..
Click to expand...
Click to collapse
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?

Mamba25 said:
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Click to expand...
Click to collapse
You will have to flash stock firmware 4.4 before your phone will work again. Simply flashing cwm will get you to cwm recovery but not a working phone.
---------- Post added at 09:37 AM ---------- Previous post was at 09:31 AM ----------
Mamba25 said:
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Click to expand...
Click to collapse
Have you tried using Odin V3.09 to flash 4.4?

hey_joe said:
You will have to flash stock firmware 4.4 before your phone will work again. Simply flashing cwm will get you to cwm recovery but not a working phone.
Click to expand...
Click to collapse
Hi, I have found a tutorial on flashing ClockworkMod Recovery v6.0.4.5 but it states:
"Must enable USB Debugging first" and also "Must let Reactivation lock off first", is this absolutely necessary as I can't access my phone, let alone its settings? Can I still proceed with installing ClockworkMod Recovery?

Mamba25 said:
Hi, I have found a tutorial on flashing ClockworkMod Recovery v6.0.4.5 but it states:
"Must enable USB Debugging first" and also "Must let Reactivation lock off first", is this absolutely necessary as I can't access my phone, let alone its settings? Can I still proceed with installing ClockworkMod Recovery?
Click to expand...
Click to collapse
Don't follow that one.
Go here and download the right file for your phone's model, put phone in download mode and flash using odin in ap/pda slot.
Btw, have you tried flashing 4.4 using odin v3.09?

When odin gives you the fail message technically you've already flashed the stock, but for some reason odin doesn't recognise it as a pass. .leave your phone plugged in, reset odin, put your phone into download phone and then flash recovery. . Hey presto your phone will wake up..

hypnodaz said:
When odin gives you the fail message technically you've already flashed the stock, but for some reason odin doesn't recognise it as a pass. .leave your phone plugged in, reset odin, put your phone into download phone and then flash recovery. . Hey presto your phone will wake up..
Click to expand...
Click to collapse
I don't think this is the case because when I first tried flashing from 4.3 to 4.4.2 it tried for a few seconds then failed and been stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“ despite resetting Odin and going back into download mode, tried reflashing but keep getting the 'FAIL' (logs posted in original first post).
Is there any reason why my phone is being detected as 'Samsung GT-S5690' in MobileGo? I'm thinking if Kies could detect it as the Note 3 again my problems would be solved.
I haven't tried Odin v3.09 because to be honest I thought the firmware file once extracted as a RAR file could only be read by Odin v3.07 is that not the case?
Soz everyone

Mamba25 said:
I haven't tried Odin v3.09 because to be honest I thought the firmware file once extracted as a RAR file could only be read by Odin v3.07 is that not the case?
Soz everyone
Click to expand...
Click to collapse
No it's not.

Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Click to expand...
Click to collapse
looks like u r trying to flash 4.3 & 4.4 one after one, now dont try 4.3 at all, make sure kies is not running in baground, disable antivirus if any.

I had the the same issue with kies myself, tried every trick in the book before I tried the method I mention above.. maybe it's an issue with the phone itself, or a certain batch of phones?

Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
...
Click to expand...
Click to collapse
The writing of stock 4.3 fails since your bootloader was updated by your failed attempt. You will probably never be able to write a 4.3 stock image.
The writing of 4.4 NB1 fails since probably it is for a slightly different region with a slightly different partitioning scheme. Ideally install the 4.4 for your specific model/region. If that fails you might need to write some 4.4 with repartition - there are some threads around (I think also the Hong-Kong version had serious problems with 4.4 because of that).

xclub_101 said:
The writing of 4.4 NB1 fails since probably it is for a slightly different region with a slightly different partitioning scheme. Ideally install the 4.4 for your specific model/region. If that fails you might need to write some 4.4 with repartition - there are some threads around (I think also the Hong-Kong version had serious problems with 4.4 because of that).
Click to expand...
Click to collapse
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks

Mamba25 said:
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Click to expand...
Click to collapse
There is AP in 3.09 in place of PDA.

Mamba25 said:
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Click to expand...
Click to collapse
I don't think there is an easy way to see what the original version was as long as you can no longer boot the phone. I think the EU model is generally listed as N9005ZWE while the HK is N9005ZKA and that might be written somewhere on the box. Also it might be a different partitioning model even if it is not a Hong-Kong model.

xclub_101 said:
I don't think there is an easy way to see what the original version was as long as you can no longer boot the phone. I think the EU model is generally listed as N9005ZWE while the HK is N9005ZKA and that might be written somewhere on the box. Also it might be a different partitioning model even if it is not a Hong-Kong model.
Click to expand...
Click to collapse
Could you please let me know if the update be completed successfully. I have the same problem so want to know the steps of the
same. Please help me.

madsus said:
Could you please let me know if the update be completed successfully. I have the same problem so want to know the steps of the
same. Please help me.
Click to expand...
Click to collapse
I've taken the phone to a repair shop recommended by Samsung themselves, they've had it a week now and I rang yesterday and they said it is the first Hong Kong Note 3 they've received and are waiting to hear from Samsung as to how to repair it. BIG YAWN!
Will keep you posted - miss my phone

Note 3 SM-N9005 firmware upgarade issue
Hi , i am having the same problem in my Note 3 i upgraded phronesis rom and after the phone was not detected in computer. so tried to flash custom kitkat rom again then it got disconnected and then showing error as firmware upgrade issue,
tried to download firmware and update by Odin, tired cmw recovery and tried many firmwares, Odin shows Failure and Kies dosent shown code or phone in emergency recovery , all ways failed, is it possible to make the phone work normal.

[HOW TO] Fix (system rev. check fail device: 2 binary 1) In 5.1.1 G920F

How to fix system rev. check fail device: 2 binary 1 error when flashing a custom 5.1.1 ROM
If this error has appeared after flashing the new Bootloader and Modem for BOFJ
Download this: https://mega.co.nz/#!E05hTYaS!_vad3fvvKCwWiMmgWGrGgc69KYdgYRa1wFCmxYzwH3s
(Stock 5.1.1)
Once installed and passed with ODIN (Flash as AP)
Power off the phone and boot into download mode
Once in download mode flash the latest TWRP 2.8.7.1
http://forum.xda-developers.com/showpost.php?p=61548356&postcount=570
After flashed you'll be able to boot into recovery and flash your custom ROM ​

Thanks
Just fixed my baby s6

I get error..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Reflash with stock 5.1.1 via odin.
ROMs for G920F:
http://www.sammobile.com/firmwares/database/SM-G920F/

Is there a 920T version of this?

Here you go:
http://www.sammobile.com/firmwares/database/SM-G920T/

G920I version?
Is there a 920I version as well?
Found it.
http://www.sammobile.com/firmwares/database/SM-G920I/

Criticalstriker said:
I get error..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
>>>>>>>>>>>>>First of all thank you very much to the OP!! <<<<<<<<<<<<<<<
I got the same error and solved it.
I think the reason was that I tried flashing a 502 stock when I had already flashed the 511 bootloader and modem. In my case I have a Brazilian SM-G920I GS6 and the 511 stock rom is/was not readily available for it. So I tried downloading the latest available official stock version (502) and it resulted in the error you mentioned.
So I dowloaded the India 511 version (region INU) for 920I and it finally worked.
I used samfirm to download it (http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647).
You need to input the exact model name (for me it was literally SM-G920I) and the region code for your phone. Then download it, DON'T close samfirm software, then click on Decrypt and you will finally have a ZIP from which you can extract the stock rom. And to find out your region code, you can go to www.sammobile.com and click on Firmware in the main menu at the top. Then you enter the model number and after that you will get to a screen with a dropdown menu for all available regions and their codes (for instance, region codes for Brazil are ZTO, ZTA..).
You can also download the stock roms from sammobile diretcly but it is too slow (takes a day or so).
Good luck!
:fingers-crossed:

gamekill said:
>>>>>>>>>>>>>First of all thank you very much to the OP!! <<<<<<<<<<<<<<<
I got the same error and solved it.
I think the reason was that I tried flashing a 502 stock when I had already flashed the 511 bootloader and modem. In my case I have a Brazilian SM-G920I GS6 and the 511 stock rom is/was not readily available for it. So I tried downloading the latest available official stock version (502) and it resulted in the error you mentioned.
So I dowloaded the India 511 version (region INU) for 920I and it finally worked.
I used samfirm to download it (http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647).
You need to input the exact model name (for me it was literally SM-G920I) and the region code for your phone. Then download it, DON'T close samfirm software, then click on Decrypt and you will finally have a ZIP from which you can extract the stock rom. And to find out your region code, you can go to www.sammobile.com and click on Firmware in the main menu at the top. Then you enter the model number and after that you will get to a screen with a dropdown menu for all available regions and their codes (for instance, region codes for Brazil are ZTO, ZTA..).
You can also download the stock roms from sammobile diretcly but it is too slow (takes a day or so).
Good luck!
:fingers-crossed:
Click to expand...
Click to collapse
Ok, now I'm stuck.
I've downloaded the same version as you (INU 5.1.1 for G920I) and flashed. Used for some days and now I have to take my SGS6 to service to check if they can give me a new one because I´m having some trouble with the radio of my network (the problm was before flashing any ROM). Any way, I've tried to flash stock 5.0.2 and Odin still giving the same error. In my case I tried many of 5.0.2 stocks ROMs for the G920I and none of them worked, even the stock from Claro (my carrier) doesn't work.
This is the log in Odin, after reflashing INU 5.1.1, wiping and apply download mode.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920IDVU1AOD1_G920IUWA1AOD6_G920IDVU1AOD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1005)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't know what to do. I can't downgrade

andifds said:
Ok, now I'm stuck.
I've downloaded the same version as you (INU 5.1.1 for G920I) and flashed. Used for some days and now I have to take my SGS6 to service to check if they can give me a new one because I´m having some trouble with the radio of my network (the problm was before flashing any ROM). Any way, I've tried to flash stock 5.0.2 and Odin still giving the same error. In my case I tried many of 5.0.2 stocks ROMs for the G920I and none of them worked, even the stock from Claro (my carrier) doesn't work.
This is the log in Odin, after reflashing INU 5.1.1, wiping and apply download mode.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920IDVU1AOD1_G920IUWA1AOD6_G920IDVU1AOD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1005)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't know what to do. I can't downgrade
Click to expand...
Click to collapse
It's not possible to downgrade to 5.0.1 if your bootloader is on 5.1.1.

Downloading now. So like all the other Odin roms it passed but does it pass in download mode on the phone that then blocks the download ?

hello!
This works on any 5.1.1?
i mean can i download any 5.1.1. for 920F and it will be fixed or i have to use exactly the rom that is posted on OP?

Once in download mode flash the latest TWRP 2.8.7.1
[url said:
http://forum.xda-developers.com/showpost.php?p=61548356&postcount=570[/url]
After flashed you'll be able to boot into recovery and flash your custom ROM [/COLOR][/SIZE]
[/CENTER]
Click to expand...
Click to collapse
hi! can someone help me to flash this recovery.img ?
thanxx in advance.

Thank you so much for this topic, Rossyyy! :good::good::good::good::good::good::good:!!!!!!!!!
Edit; The only thing is that i still get a message (top left) in really small red letters every time i boot. For a few seconds and than boot proceeds by itself....

Rossyyy said:
How to fix system rev. check fail device: 2 binary 1 error when flashing a custom 5.1.1 ROM
If this error has appeared after flashing the new Bootloader and Modem for BOFJ
Download this: https://mega.co.nz/#!E05hTYaS!_vad3fvvKCwWiMmgWGrGgc69KYdgYRa1wFCmxYzwH3s
(Stock 5.1.1)
Once installed and passed with ODIN (Flash as AP)
Power off the phone and boot into download mode
Once in download mode flash the latest TWRP 2.8.7.1
http://forum.xda-developers.com/showpost.php?p=61548356&postcount=570
After flashed you'll be able to boot into recovery and flash your custom ROM ​
Click to expand...
Click to collapse
Hey, once I am facing the "system rev. check fail device: 2 binary 1 error", I don't think I can power off the phone completely. I can just reboot the phone into the download mode. If I try to reboot into recovery it will say "recovery is not seandroid enforcing"...
How do I power off the phone completely or how do I reboot into recovery?

aeroxy said:
How do I power off the phone completely or how do I reboot into recovery?
Click to expand...
Click to collapse
Volume up, home and power button.

richajax said:
Volume up, home and power button.
Click to expand...
Click to collapse
Oh yes, I have tried this. It will reboot and says "recovery is not seandroid enforcing"...

I think you will find your answer in one of these topics?
http://forum.xda-developers.com/search.php?searchid=379334690

Thanks, fixed the soft brick on my 920i. Used the Indian 5.1.1 version but it takes an age to download. Here is an alternate link.
https://mega.co.nz/#!VZcARCrC!-Zj8gwLGkqmlEnSBemyfqsTrr4C_ilf3koUOS6_w2pE

brettule said:
Thanks, fixed the soft brick on my 920i. Used the Indian 5.1.1 version but it takes an age to download. Here is an alternate link.
https://mega.co.nz/#!VZcARCrC!-Zj8gwLGkqmlEnSBemyfqsTrr4C_ilf3koUOS6_w2pE
Click to expand...
Click to collapse
Thanks for the link. I panicked when this happened, glad i was able to find this topic through google
---------- Post added at 02:46 PM ---------- Previous post was at 02:39 PM ----------
Okay, so it failed. Now what?
I'm starting to panic lol.
<OSM> Please wait..
<OSM> G920IDVU2COF8_G920IODD2COF8_G920IDVU2COF8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Can't open the specified file. (Line: 2012)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
**EDIT**
for anyone else that may ever encounter this.. .make sure your "re-partition" option is unchecked in odin.

i brick my samsung s4 sgh i337

hello everyone i am new here.
i have come here because i was trying to install a new recovery twrp to be exact. while i was installing it apeared a messge it said: the recovery has been installed correctly would you like to restart your mobile? and i restared my mobile and then it shown a message it said: system software not authorized by at&t has been found on your phone. at that time i had installed android lollipop 5.0.1 and it was rooted and i just wanted to re-install lollipop again by odin but knox and bootloader was enable so i cant reinstall the rom again and it seem like i have bricked my mobile..
help me please.

SGH-i337 is an AT&T phone which has a locked bootloader. If you have old bootloader like MDL you could use the loki exploit when you install the TWRP. What is your bootloader version?
I do not think there is a odin flashable lollipop full firmware exist. The last full firmware released for i337 is NB1 (kitkat). After that there is only incremental OTA upgrade to lollipop.

can i downgrade to kikkat?
i dont know what kind of bootloader i have. but odin is always fail when i try to apply the firmware... let me post a screemcapture!
can i dowgrade via ota... because i have tried to intall lollipop by ota but there is always an error! unpacking the package!

either samsung kies doesnt detect my mobile and i cant not enter to recovery mode because it says that firmware upgrade encountered an issue. please select recovery mode in kies and try again.

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

The ROM you are trying to flash has a bootloader that is older than the bootloader on the phone. This is evidenced by the fact that Odin stops after trying to flash aboot.mbn.
Look here for a possible solution: http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642

my mobile was running lollipop 5.0.1 and how can i get the latest version?

thank you it works hehe i am so thankful with you...
arigatou..

FAIL! SHA256 is Invalid error trying to Root

I, along with several other users, have been getting a SHA256 is invalid error when trying to do the root from this thread:
http://forum.xda-developers.com/att-note-7/how-to/root-complete-stock-ph1-setup-root-t3463187
The fail comes in at the step when trying to flash the Sprint userdebug firmware in the AP slot.
I tried using different computers, cables, and ODIN and all that happened was I managed to brick my phone (but then fix it by flashing the stock ATT files thankfully)
One thing I noticed is that the firmware is downloaded as an MD5 instead of a TAR file, but I assume this has no bearing on the error.
Does anyone have any solution to this problem? It seems there are many people who have been able to acquire root, so there must be some solution available.
Any help is greatly appreciated as root access will be incredibly beneficial!
This is what the log looks like in the Odin version provided in the post:
<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.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)

Luigiman765 said:
I, along with several other users, have been getting a SHA256 is invalid error when trying to do the root from this thread:
http://forum.xda-developers.com/att-note-7/how-to/root-complete-stock-ph1-setup-root-t3463187
The fail comes in at the step when trying to flash the Sprint userdebug firmware in the AP slot.
I tried using different computers, cables, and ODIN and all that happened was I managed to brick my phone (but then fix it by flashing the stock ATT files thankfully)
One thing I noticed is that the firmware is downloaded as an MD5 instead of a TAR file, but I assume this has no bearing on the error.
Does anyone have any solution to this problem? It seems there are many people who have been able to acquire root, so there must be some solution available.
Any help is greatly appreciated as root access will be incredibly beneficial!
This is what the log looks like in the Odin version provided in the post:
<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.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You have the wrong version of Odin. I replied to your comment in another thread with the link. But it's someone who uploaded a copy of the fixed Odin from one of the root threads.
It was post #168 or #186. I'm away from that tab now.
I know you have the latest version, but you need the other version that's cooked to work with this spirit root package

grmcrkrs said:
You have the wrong version of Odin. I replied to your comment in another thread with the link. But it's someone who uploaded a copy of the fixed Odin from one of the root threads.
It was post #168 or #186. I'm away from that tab now.
I know you have the latest version, but you need the other version that's cooked to work with this spirit root package
Click to expand...
Click to collapse
Well, this did in fact move me past the SHA256 Invalid error but I was presented with a new error:
<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..
<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> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
[1]eMMC write fail: aboot
Then, my phone bricked. Again. Luckily I already fixed this once and I fixed it again.
At this point I assume I just have some unrootable version of the phone and can live with it I suppose.
Bricking a phone this expensive isn't fun despite the fact that I have fixed it.

they slipped a new bootloader in with the "green battery" icon update. this new updated bootloader checks and will not allow a downgrade in version. root method #patched
i took the update on my defective device, just to test this. you are lucky, i am unable to get my device back to ATT stock, i am bricked.

cordell12 said:
they slipped a new bootloader in with the "green battery" icon update. this new updated bootloader checks and will not allow a downgrade in version. root method #patched
i took the update on my defective device, just to test this. you are lucky, i am unable to get my device back to ATT stock, i am bricked.
Click to expand...
Click to collapse
Guess I'm bricked too.. same issues.. if a new update comes out, will that get loaded and allow the device to start working again? I thought bricked was the device not even turning on.
Mine turns on and everything works find except i have no cell reception at all - circle w/line through it. can seem to get it rooted and this all happened just after the last update but not sure if it was related. Samsung thinks I rooted the phone but I've never done that in my life so not I have no choice but to try in order to get a working phone back... but that doesn't seem to be working either.. ugh. $800 for a phone that worked for 8 months...

Same as you. Everything works but cell service
MellowJoe said:
Guess I'm bricked too.. same issues.. if a new update comes out, will that get loaded and allow the device to start working again? I thought bricked was the device not even turning on.
Mine turns on and everything works find except i have no cell reception at all - circle w/line through it. can seem to get it rooted and this all happened just after the last update but not sure if it was related. Samsung thinks I rooted the phone but I've never done that in my life so not I have no choice but to try in order to get a working phone back... but that doesn't seem to be working either.. ugh. $800 for a phone that worked for 8 months...
Click to expand...
Click to collapse
hAVE YOU BEEN ABLE TO DO ANYTHING

Luigiman765 said:
Well, this did in fact move me past the SHA256 Invalid error but I was presented with a new error:
<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..
<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> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
[1]eMMC write fail: aboot
Then, my phone bricked. Again. Luckily I already fixed this once and I fixed it again.
At this point I assume I just have some unrootable version of the phone and can live with it I suppose.
Bricking a phone this expensive isn't fun despite the fact that I have fixed it.
Click to expand...
Click to collapse
But see, it failed at the aboot part.
Try flashing the combination file for your current bootloader version. Once that is installed try again.
Combination Files always ship with the revision 1 aboot for that binary version. And they are signed. So you can downgrade to a revision A aboot file by using the Combination files.
This might help. PrinceComsy's version of ODIN or Jester's version of ODIN are the ones usually used for AT&T devices with checksum errors.
(i.e When you see a build like 3CQB2 or 5BPK1 or something like that. The first digit on the build is the bootloader revision or binary version of the firmware. That second digit is the aboot revision. The last 3 digits are the time the build was created and its revision number.
When I had my AT&T Note 5, I had updated to Binary 3 aka Marshmallow. I couldn't go back to the binary 2, LP 5.1.1 builds to root anymore. Using the combination file for binary 3 I was able to flash a binary 2 AP file overtop of the rest of the binary 3 combination firmware. And it booted up just fine! I was able to downgrade and root because of the combination file.