Database Users

PLEASE HELP - Phone soft bricked after ICS LPY

Hi All,
So, I was one of those people who last night decided I needed to have clean install for my newly LPY ICS flashed through odin PC. Obviously, I had not read the warning threads only after my phone got stuck on format and then rebooted and got stuck on logo did I visit XDA and saw the new warning Anyhow, what I had flashed was a rooted version of LPY ICS. Now, I have access to download mode but when I tried to reflash through Odin PC I get a failed attempt with this message !!!
**Edit: I don't think I did use repartition...I usually never do....this all started after me trying to clean install via CWM from official rooted LPY it got stuck on formatting then rebooted and was on logo forever so I proceeded to use Odin flashing LPY failed, tried all methods posted here besides flashing kernel Abyuss note 4.2 from in PDA as someone here suggested but since I can't find one that works with Odin I just reflash LC1 rooted stock multiple times but no luck it fails and NAND Write Start which is almost at the end of flashing.
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5 is valid.
Rooted_Stock_Odex_N7000XXLC1.tar.md5 is valid.
GT-N7000-MULTI-CSC-OXALC1.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:13)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Can't open the specified file. (Line: 1876)
All threads completed. (succeed 0 / failed 1)
Can anyone please help. I have no idea what I should do I even tried flashing stock ICS LPY but at 3/4 of the way it would also fail!!!

jwais said:
Hi All,
So, I was one of those people who last night decided I needed to have clean install for my newly LPY ICS flashed through odin PC. Obviously, I had not read the warning threads only after my phone got stuck on format and then rebooted and got stuck on logo did I visit XDA and saw the new warning Anyhow, what I had flashed was a rooted version of LPY ICS. Now, I have access to download mode but when I tried to reflash through Odin PC I get a failed attempt with this message !!!
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5 is valid.
<OSM> Rooted_Stock_Odex_N7000XXLC1.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Can't open the specified file. (Line: 1876)
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone please help. I have no idea what I should do I even tried flashing stock ICS LPY but at 3/4 of the way it would also fail!!!
Click to expand...
Click to collapse
Did you backup your previous from ..if you did just go into recovery and restore it
Sent from my GT-N7000 using xda premium

You are making one huge mistake : you have the box "re-partition" selected. Uncheck that option and you should be good to go.
P_

jwais said:
Hi All,
So, I was one of those people who last night decided I needed to have clean install for my newly LPY ICS flashed through odin PC. Obviously, I had not read the warning threads only after my phone got stuck on format and then rebooted and got stuck on logo did I visit XDA and saw the new warning Anyhow, what I had flashed was a rooted version of LPY ICS. Now, I have access to download mode but when I tried to reflash through Odin PC I get a failed attempt with this message !!!
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5 is valid.
<OSM> Rooted_Stock_Odex_N7000XXLC1.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Can't open the specified file. (Line: 1876)
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone please help. I have no idea what I should do I even tried flashing stock ICS LPY but at 3/4 of the way it would also fail!!!
Click to expand...
Click to collapse
Try to flash gingerbread rom from http://forum.xda-developers.com/showthread.php?t=1535025 i would try this one "N7000XXLC1_N7000OXALC1 Open Europe (02/03/2012)" because it a full wipe.

Here is how to solve.
1.flash stck GB rom
2.wipe data/cache from stock recovery.
3.now flash stock ics.
4.then flash another rom/ root kernel
Sent from my GT-N7000 using xda premium

awesome-member said:
Here is how to solve.
1.flash stck GB rom
2.wipe data/cache from stock recovery.
3.now flash stock ics.
4.then flash another rom/ root kernel
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
That' the safest way.
Sent from my Galaxy Note

Thanks guys, I tried reflashing stock GB lc1 and it stoped on odin pc sayig failed and I did not repartition this time. Tried reflashing stock ICS LPY with no luck...it fails.
If anyone has another option please let me know...I cannot access recovery only download mode when I try to access recovery it gives me " firmware upgrade failed encountered an issue. Please select recovery mode in kies & try gain" .....

jwais said:
Thanks guys, I tried reflashing stock GB lc1 and it stoped on odin pc sayig failed and I did not repartition this time. Tried reflashing stock ICS LPY with no luck...it fails.
If anyone has another option please let me know...I cannot access recovery only download mode.....
Click to expand...
Click to collapse
Try to find the pit file and use it with repartition checked.
Sent from my GT-N7000 using XDA

just to be sure,
did u kill all kies processes?

aww
jwais said:
Hi All,
So, I was one of those people who last night decided I needed to have clean install for my newly LPY ICS flashed through odin PC. Obviously, I had not read the warning threads only after my phone got stuck on format and then rebooted and got stuck on logo did I visit XDA and saw the new warning Anyhow, what I had flashed was a rooted version of LPY ICS. Now, I have access to download mode but when I tried to reflash through Odin PC I get a failed attempt with this message !!!
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5 is valid.
<OSM> Rooted_Stock_Odex_N7000XXLC1.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Can't open the specified file. (Line: 1876)
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone please help. I have no idea what I should do I even tried flashing stock ICS LPY but at 3/4 of the way it would also fail!!!
Click to expand...
Click to collapse
idk how to i wish i could man

Kill KiesHelper.exe and KiesPDLR.exe and try to flash again

Yup killed all kies processes. Reflashing stock LC1 one last time with odin pc as suggested....pray for me

I had this similar issue. I had to completely un install Kies and then Odin worked without issue
Sent from my GT-N7000 using xda premium

i slashed my knees open, knelt with salt and lemon on the ground. i can't do this for long.... is your note ok (i hope i do not have to do some other kind of rituals for the flash procedure to work for you).

Ok guys after trying to reflash second time stock GB LC1 with odin pc this is what I get:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000XXLC1.tar.md5 is valid.
<OSM> MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.img
<ID:0/013> NAND Write Start!!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/013> Removed!!
It goes almost all the way but then somehow stops at the nand write part. Anyone has any clue?

Did you completely uninstall kies? It's worth a shot...
Sent from my GT-N7000 using xda premium

Uninstalling Kies right now...will try again flashing. Thanks!

take out your battery, restart the pc... and try another cable if possible.
make sure all firewalls and/or antivirus softwares are disabled. if it helps, run odin as administrator.
while you do that, i shall make a bonfire and prepare to dance around naked around the flame and chant the songs my great ancestors has been singing since time immemorial.

Ok, I think I found a pattern for the failed attempts during flashing...it always stalls and fails during the NAND Write Start.....anyone has any clue as to why?

Maybe it sounds stupid but what version of Odin do yo use?

[Q] Odin gets stuck while flashing

I tried to flash my Galaxy Y with Odin but it always gets stuck at 'boot.img', after which I power off the phone. The phone is working fine but even after repeating the process the same thing happens. What should I do?

entermetallica said:
I tried to flash my Galaxy Y with Odin but it always gets stuck at 'boot.img', after which I power off the phone. The phone is working fine but even after repeating the process the same thing happens. What should I do?
Click to expand...
Click to collapse
Dude this problem related with flashing kernal which kernal u hav inastalled.
Sent from my GT-S5360 using xda app-developers app

[email protected] said:
Dude this problem related with flashing kernal which kernal u hav inastalled.
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
I haven't installed any kernel.

entermetallica said:
I tried to flash my Galaxy Y with Odin but it always gets stuck at 'boot.img', after which I power off the phone. The phone is working fine but even after repeating the process the same thing happens. What should I do?
Click to expand...
Click to collapse
just simply disconnect your phone, put off your battery, put in your battery again, enter download mode, and try to flash again

May be Kies interfering
this may be due to kies interfering with the COM connection... you check by pressing Ctrl+Alt+Del and end each Kies process through task manager and try flashing again...

Catalyste said:
this may be due to kies interfering with the COM connection... you check by pressing Ctrl+Alt+Del and end each Kies process through task manager and try flashing again...
Click to expand...
Click to collapse
Also all adb connections must also be stopped
Sent from my GT-S5360 using xda premium

Similar issue here guys.. My phone was stuck at the boot image after rebooting from a custom ROM (JellyBlast 3.0), I couldn't get into recovery mode as well. In download mode Odin (1.84 and 1.85) detects the phone and while trying to flash with stock DDLF2 I get the below:
<ID:0/048> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5360DDLF2_S5360ODDLF1_S5360DDLF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/048> Odin v.3 engine (ID:48)..
<ID:0/048> File analysis..
<ID:0/048> SetupConnection..
<ID:0/048> Initialzation..
<ID:0/048> Get PIT for mapping..
<ID:0/048> Firmware update start..
<ID:0/048> sbl.bin
<ID:0/048> BcmCP.img
<ID:0/048>
<ID:0/048> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea what might be wrong - all drivers are installed and Kies is not running.

xdroid_noob said:
Similar issue here guys.. My phone was stuck at the boot image after rebooting from a custom ROM (JellyBlast 3.0), I couldn't get into recovery mode as well. In download mode Odin (1.84 and 1.85) detects the phone and while trying to flash with stock DDLF2 I get the below:
<ID:0/048> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5360DDLF2_S5360ODDLF1_S5360DDLF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/048> Odin v.3 engine (ID:48)..
<ID:0/048> File analysis..
<ID:0/048> SetupConnection..
<ID:0/048> Initialzation..
<ID:0/048> Get PIT for mapping..
<ID:0/048> Firmware update start..
<ID:0/048> sbl.bin
<ID:0/048> BcmCP.img
<ID:0/048>
<ID:0/048> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea what might be wrong - all drivers are installed and Kies is not running.
Click to expand...
Click to collapse
Issue fixed, tried another set of FW from doky77's page - the complete set with PDA, Modem and CSC files. The whole process took less than a minute. And bingo, I have unbricked my phone the first time.

Download firmware packages .again and try sometimes it will work....dont worry.......if it stucks on boot.img.......ex:in samsung logo ...remove the battery ....and start the phone in recovery mode using 3button combo.......in recovery mode use wipe data/factory reset after its completed and then wipe cache....after rebbooot system...it will surely work....i have xperienced this bug....if i helped pls tap helped
Sent from my GT-S6102 using xda app-developers app

xdroid_noob said:
Issue fixed, tried another set of FW from doky77's page - the complete set with PDA, Modem and CSC files. The whole process took less than a minute. And bingo, I have unbricked my phone the first time.
Click to expand...
Click to collapse
Hmm so I need 3 blanks filled in in order to flash my SGY?
I only have one file once extracted. Firmware for Sammobile.com

Use doky's thread for downloading firmwares not sammobile....Galaxy Y might not install the whole partition properly from a single tar file from sam mobile....
The doky's Firmwares have a higher chance of proper installation..
Sent from my GT-S5360 using xda app-developers app

I had softbrick with my galaxy Y..
what i do is to get offical firmware which got seperate file for modem,pda,csc..and also need pit file..
i flash it through ODIN and bring my phone alive back..

xdroid_noob said:
Similar issue here guys.. My phone was stuck at the boot image after rebooting from a custom ROM (JellyBlast 3.0), I couldn't get into recovery mode as well. In download mode Odin (1.84 and 1.85) detects the phone and while trying to flash with stock DDLF2 I get the below:
<ID:0/048> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5360DDLF2_S5360ODDLF1_S5360DDLF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/048> Odin v.3 engine (ID:48)..
<ID:0/048> File analysis..
<ID:0/048> SetupConnection..
<ID:0/048> Initialzation..
<ID:0/048> Get PIT for mapping..
<ID:0/048> Firmware update start..
<ID:0/048> sbl.bin
<ID:0/048> BcmCP.img
<ID:0/048>
<ID:0/048> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea what might be wrong - all drivers are installed and Kies is not running.
Click to expand...
Click to collapse
this had happened me before.
later i came to know about sgy that our sgy can't flash using a single .tar file in modem.
So you should flash it using three files in PDA, MODEM& CSC.
You will get all these files from 'doky73's thread.
Sent from my GT-S5360 using xda app-developers app

Solution: Add PIT file
abyisforyou said:
this had happened me before.
later i came to know about sgy that our sgy can't flash using a single .tar file in modem.
So you should flash it using three files in PDA, MODEM& CSC.
You will get all these files from 'doky73's thread.
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
For any of those who are reading this in the future with the same problem, add the PIT file for your device too and it should work. It worked fort me.

Catalyste said:
this may be due to kies interfering with the COM connection... you check by pressing Ctrl+Alt+Del and end each Kies process through task manager and try flashing again...
Click to expand...
Click to collapse
this worked. many thanks

Firmware upgrade encountered an issue.

So my gs4 seems to be soft bricked. I was trying to reroot my phone and it failed in the middle of rooting and now when I try to turn it on, it goes to a screen saying firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. What do I do? Do I just flash stock firmware onto the phone with odin?

xTrooge said:
So my gs4 seems to be soft bricked. I was trying to reroot my phone and it failed in the middle of rooting and now when I try to turn it on, it goes to a screen saying firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. What do I do? Do I just flash stock firmware onto the phone with odin?
Click to expand...
Click to collapse
yes your best option

Blackwolf10 said:
yes your best option
Click to expand...
Click to collapse
any links to a fast download? found one but it goes 360 kb/s max.

xTrooge said:
any links to a fast download? found one but it goes 360 kb/s max.
Click to expand...
Click to collapse
good you can think of your options while it is downloading :laugh:
no sorry i am not that familiar with this thread but on stock firmware threads usually people leave mirrors of other sites so try that

So just tried it, heres what i get from odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-L720_MDC_Stock_Nodata.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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
fml

xTrooge said:
So just tried it, heres what i get from odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-L720_MDC_Stock_Nodata.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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
fml
Click to expand...
Click to collapse
ahhhh seems your rooting has made a few problems you don't have a pit partition so odin can't do anything about it
you can try kies don't know if it will help seems you will have to service it i guess

Blackwolf10 said:
ahhhh seems your rooting has made a few problems you don't have a pit partition so odin can't do anything about it
you can try kies don't know if it will help seems you will have to service it i guess
Click to expand...
Click to collapse
where do i get the pit? kies is pretty useless seeing as how it can only recover if i backed it up

xTrooge said:
where do i get the pit? kies is pretty useless seeing as how it can only recover if i backed it up
Click to expand...
Click to collapse
pit file usually comes with the stock Rom you get 3 files from the zip right ?
but i wouldn't want to try that and i would defently read a thread about pit before doing anything
BTW what's your device model ?
the only thing i can think of is you used a wrong rooting methood for it

Blackwolf10 said:
pit file usually comes with the stock Rom you get 3 files from the zip right ?
but i wouldn't want to try that and i would defently read a thread about pit before doing anything
BTW what's your device model ?
the only thing i can think of is you used a wrong rooting methood for it
Click to expand...
Click to collapse
nvm just fixed it. i just had to use a different usb port and restart my comp.

xTrooge said:
nvm just fixed it. i just had to use a different usb port and restart my comp.
Click to expand...
Click to collapse
hah that works the best glad you didn't have to use Pit

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.

I9505 soft-bricked odin fails flashing roms

I come from an Omega ROM v19 (4.3) rooted on a Galaxy S4
I tried to flash back the stock ROM that was a 4.2.2 and ODIN came with that message
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<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> sbl2.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl3.mbn
<ID:0/008> rpm.mbn
<ID:0/008> aboot.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
In download mode after the flash fails, appears this message
Code:
START [224,1440]
SW REV. CHECK FAIL : fused : 4, Binary : 3
I cant't solve that soft-brick, i tried on different USB ports but seems that is not working, even changing ODIN version
Can you help me?
PS: Sorry for my bad english

C4scade said:
I come from an Omega ROM v19 (4.3) rooted on a Galaxy S4
I tried to flash back the stock ROM that was a 4.2.2 and ODIN came with that message
Code:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:8)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sbl2.mbn
NAND Write Start!!
sbl3.mbn
rpm.mbn
aboot.mbn
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1
In download mode after the flash fails, appears this message
Code:
START [224,1440]
SW REV. CHECK FAIL : fused : 4, Binary : 3
I cant't solve that soft-brick, i tried on different USB ports but seems that is not working, even changing ODIN version
Can you help me?
PS: Sorry for my bad english
Click to expand...
Click to collapse
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.
Edit : Did you check MD5 of your firmware?
? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?

Ricardo_Is said:
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.
Edit : Did you check MD5 of your firmware?
? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?
Click to expand...
Click to collapse
Sorry for my bad english but
i also got the same error with odin :
aboot.mbn
FAIL! (Auth)
got no sound and got a black screen when calling mic also not working
flashing custom roms wont fix it any way to install stock i9505 rom without odin or kies ?
's it fixable any ideas ??

Ricardo_Is said:
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.
Edit : Did you check MD5 of your firmware?
? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?
Click to expand...
Click to collapse
Man, i don't think that a nandroid backup can solve a binary error.. and yes, i checked the firmware md5, it's ok, it is from sammobile.com

I'd say if you've got aboot fail then your trying to flash older rom on a phone that's had newer rom on it aka Knox already.
Sent from my GT-I9505 using xda app-developers app

Flash the ''i9505 pit'' file on odin in pda. That will fix

DONE!!!
mr.biceps said:
Flash the ''i9505 pit'' file on odin in pda. That will fix
Click to expand...
Click to collapse
Hi
I like to share how I fixed my S4 using ODIN 3.09
1. I flash the ''i9505 pit'' file on odin in pda (JUST THIS ONE FILE)
2. I used CF-Auto-Root-jflte-jfltexx-gti9505.tar
3. I tried to use Firmware with 4.3 because the phone had updated android to 4.3 v. but in the ODIN program appeared FAIL!
4. So I decided to install an older Firmware (with 4.2.2 v.) and it helped
Thank you for all the advice and good work XDA TEAM!!!

mgolejnik said:
Hi
I like to share how I fixed my S4 using ODIN 3.09
1. I flash the ''i9505 pit'' file on odin in pda (JUST THIS ONE FILE)
2. I used CF-Auto-Root-jflte-jfltexx-gti9505.tar
3. I tried to use Firmware with 4.3 because the phone had updated android to 4.3 v. but in the ODIN program appeared FAIL!
4. So I decided to install an older Firmware (with 4.2.2 v.) and it helped
Thank you for all the advice and good work XDA TEAM!!!
Click to expand...
Click to collapse
Hi there,
Just out of interest, How did you manage to flash 4.2.2 firmware via Odin to a phone that had had the 4.3 firmware installed via an update??
I (and many others) are aware that 4.3/4 firmware has the KNOX enabled boot-loaders making it impossible to downgrade stock firmware
Or have I completely misunderstood your resolution/fix?

CarlM34 said:
Hi there,
Just out of interest, How did you manage to flash 4.2.2 firmware via Odin to a phone that had had the 4.3 firmware installed via an update??
I (and many others) are aware that 4.3/4 firmware has the KNOX enabled boot-loaders making it impossible to downgrade stock firmware
Or have I completely misunderstood your resolution/fix?
Click to expand...
Click to collapse
But I never wrote that I had installed version 4.3 / 4. This is the version which is installed this time: I9505XXUFNB9_I9505O2UFNA2_I9505XXUFNB9_HOME.tar after this I flash CF-Auto-Root-jflte-jfltexx-gti9505.tar and now it is rooted and it is KNOX (but not for long)
Maybe I made a mistake. If so, sorry
...
I MADE MISTAKE!!! I am so sorry for that!!!
I9505XXUFNB9_I9505O2UFNA2_I9505XXUFNB9_HOME.tar it is newest version it's 4.4.2!!! I am sorry again.

I'm Also Having a problem with my samsung s4 gt-i9505 (INS)
i was trying to flash my phone with 4 files of firmware with Odin3 v3.10.6
and while flashing i got this problem
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I9500XXUHPI1_CL9155695_QB10809785_REV00_user_low_ship.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_I9500XXUHPI1_CL9155695_QB10809785_REV00_user_low_ship.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> MODEM_I9500DDUHPE1_REV01_CL1856465_SIGNED.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_ODD_I9500ODDHOJ1_CL5979820_QB6580299_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if you have any solution please reply