Database Users

[Q] Odin fails, soft bricked phone.

Hey,
A while ago I've installed CM10.1 on my S4, but I was missing a lot of samsung features. So I've installed 4.2.2 again, set the binary back to the official one so I was able to update my phone again. Now that 4.3 has came out I tried to install it but then my phone bricked. The first attempt was not with odin but official via OTA.
Now i've got a soft bricked S4, tried to install the firmware several times via Odin but Odin keeps failing. If I first try to install it it wil fail at the aboot.mbn point. When I root it with Autoroot CF and then try to install the firmware it fails at system.img.ext4 as I show down here. Has anyone an idea how to fix this? Tried many options already like installing a new recovery like CWM Recovery and TWRP. (Couldn't find a stock recovery, maybe thats the solution.)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ7_I9505PHNEMJ8_I9505XXUEMJ7_HOME.tar.md 5 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> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<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)
Currently have CM10.2 installed so I can use my phone, this works but not great. Wifi, Calling, Camera, Headphone and much other options won't work. I really want to install official Samsung 4.3 firmware and be able to update again with OTA.

chendoyen said:
Hey,
A while ago I've installed CM10.1 on my S4, but I was missing a lot of samsung features. So I've installed 4.2.2 again, set the binary back to the official one so I was able to update my phone again. Now that 4.3 has came out I tried to install it but then my phone bricked. The first attempt was not with odin but official via OTA.
Now i've got a soft bricked S4, tried to install the firmware several times via Odin but Odin keeps failing. If I first try to install it it wil fail at the aboot.mbn point. When I root it with Autoroot CF and then try to install the firmware it fails at system.img.ext4 as I show down here. Has anyone an idea how to fix this? Tried many options already like installing a new recovery like CWM Recovery and TWRP. (Couldn't find a stock recovery, maybe thats the solution.)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ7_I9505PHNEMJ8_I9505XXUEMJ7_HOME.tar.md 5 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> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<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)
Currently have CM10.2 installed so I can use my phone, this works but not great. Wifi, Calling, Camera, Headphone and much other options won't work. I really want to install official Samsung 4.3 firmware and be able to update again with OTA.
Click to expand...
Click to collapse
I thought the only way to fix a bricked phone is to have it repaired or something. But I dont understand why you would switch back to samsung ui, but thats not my business. I believe is risky to go back to the phones normal UI after installing a rom because of the update problem. Basically I would never go back to the normal phones UI even if I wanted to after installing a rom, because I feel like there will be a problem. I dont really know a solution but maybe you can give it into someone to repair it, but I believe it costs A LOT. Sorry I don't really have a good solution for you. These are the risks with installing roms and switching back.

Are you using the official cable that came with the phone
Sent from my GT-I9505 using xda app-developers app

imlgl said:
Are you using the official cable that came with the phone
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Yes, also tried another cable.
Also tried: Another Odin version, another PC and different USB ports.

Anyone?

Nobody an idea?

You could try the following things:
Re-install samsung drivers
Make sure Kies is not running in the background
Try changing ports
Try different USB cable

bAk3ry said:
You could try the following things:
Re-install samsung drivers
Make sure Kies is not running in the background
Try changing ports
Try different USB cable
Click to expand...
Click to collapse
Tried again another PC and it worked a bit, I now have stock samsung firmware 4.3 installed but still no wifi and no sound. Is there a solution for that? Already tried to install CWM and TWRP but still doesn't work. When I try to play music it says audio file not supported (.MP3 file, before problems always worked) S Voice keeps crashing... And when I try to turn Wifi on I get a security message that says:
The device detected an application attempts to perform action that are not allowed. These actions are blocked.

You need to flash one of the WiFi 'fixes' from this thread, read it to work out which file you need to flash.

MistahBungle said:
You need to flash one of the WiFi 'fixes' from this thread, read it to work out which file you need to flash.
Click to expand...
Click to collapse
Tried that but it still won't work.

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.

Help Dead S5 G900F after trying downgrade

Hello...
Please if someone could help me and guide me to rescue my brand new S5 G900F :crying:
Starting to get desperate here... as I did not backup my EFS was going to do it after rooting
Here are the steps I did to get into trouble:
Upgraded to Stock Poland G900FXXU1BNL2 Loolipop to the phone everything was fine... except some app crashes as Facebook so decided to return to 4.4
So put the phone into recovery mode did a full wipe and loaded G900FXXU1ANJ1 from poland too with odin
The phone booted and looked all ok so turned it off after first boot withouth even touching the language settings.
Put again into dowload and decided to run CF-Auto to root the phone
Here everything started and Fail! message appeared at ODIN.
So turned of the phone and now the phone auto boots with message "Firmware upgrade encounter an issue. Please select recovery mode in Kies & try again."
So put the phone in download mode and try to put again stock 4.4 G900FXXU1ANJ1 again but got fail message during system.img.ext4 writting multiple times.
Then tryed to go back to Loolipop same issue multiple times...
Then finally try with lollipop after restarting computer, changing usb port, unziping again the firmware, etc...but from off state removed battery then putting back, then connecting the usb cable so from the "Firmware upgrade issue" screen hit the start and the firmware finally succedd the process.
The phone boot normally ....but I'm such and IDIOT that I said ok why not get back to 4.4 as it worked first time...
So put the phone back into download mode and try to load 4.4 stock rom G900FXXU1ANJ1 again but FAIL! appeared again and now I cant get pass it even after trying what solved the issue before...
Please help ideas etc ???
Now if I try to load 5.0 G900FXXU1ANJ1 it fail at the begining of system.img.ext4 writting...
If I try with 4.4 G900FXXU1ANJ1 from "Firmware Upgrade issue" screen the best I could get was half of the system.img.ext4 writting once before getting FAIL message again but most time it fails at the begining too.
These is what I'm getting from Odin now every test...
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BNL2_G900FXEO1BNL1_G900FXXU1BNL2_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks a lot for your time in advance for helping me...
Let me know if you need more info or anything please.

SOLVED!
GREAT NEWS
Solved myself on the last try before heading to bed crying hehehe
What I did for the record to others...and dont actually as why it worked...but it did...
Leaved the phone without battery almost half hour, then shutdown computer, unziped the 5.0 stock rom once again to have one fresh copy, open odin loaded rom wait till md5 check, then change usb port once again, then put battery to phone, then connect cable as soon as odin recognized it hit start and pray.
WORKED...
So the phone restarted as normal etc but there was the app updating screen...after it the phone was like dumb and some poland message only displaying. So turn it of, put on recovery, did cache clear and then complete wipe and restarted, Now everything is back to normal...
Phone now on 5.0 and staying so at least I find a way to backup my efs folder and stop sacking from these time mistake. I will only downgrade if safer method available or teste or maybe updating to the new 5.0 G900FXXU1BNL7 that just get out and forgeting about the downgrade well what I wanted was to open LTE bands... maybe some day...also available on 5.0 LTE band opening
For know happy having it back working

Good that you solved it and even better that you explained how you solved it! :good:
Seems like your phone wants you to stay on 5.0, hehe.
Sent from my SM-G900F using Tapatalk

Looks like he wants 5.0 stock untouched really bad...
As today I had another episode with it... LOL
It got BNL7 over OTA yesterday after all everything went perfect... but today I try to root it using CF-Auto-Root-klte-kltexx-smg900f and Odin 3.09 after enabling USB debug, etc. just like instructions but at the end of process FAIL!
Had to put again stock BNL5 to recover it.
Don't know what to do or I should wait for update on the CF-Auto to use it. In the manual I found said it should work on BNL7 but looks like it does not.
Code:
<OSM> Please wait..
<OSM> CF-Auto-Root-klte-kltexx-smg900f.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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I bricked my Note because i didnt flash the kernel :(

Hey guys,
i tried to flash my note 4 using the openrecovery method
but i forgot to flash the kernel and now my phone is stuck in the booting at the Samsung symbol. Can someone please help? i can still get into the download mode
Thank you!!!

If you can access download mode, your phone is not bricked.
Simply download last firmware for your model from sammobile, and flash it with odin...

ok thanks, will do.
But how do I safely root the note 4 5.1.1? CF-Autoroot isnt compatible

Ok, I just finished download a stock rom for my phone (.tar.zip) but when I click start in Odin it always fails for some reason...<ID:0/003> Can't open the serial(COM) port.
Edit: tried a different port now it fails at:
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
What can I do?
Does upgrading via Kies will result in losing all data?

I'm working on this issue for hours now but I'm stuck
Using Odin it will fail at sboot.bin
And kies doesnt recognize my note 4

Here's the log:
<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> Initialzation..
<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)
On the phone: SW REV. CHECK FAIL, DEVICE 2, BINARY 1

Nixdax said:
Hey guys,
i tried to flash my note 4 using the openrecovery method
but i forgot to flash the kernel and now my phone is stuck in the booting at the Samsung symbol. Can someone please help? i can still get into the download mode
Thank you!!!
Click to expand...
Click to collapse
Restore your backup in recovery

What is your exact model, G or F, what? You download the ROM from sammobile with your exact model no., and then flash.

It's N910H
I resolved it by recovering my phone via Kies though I lost all my data
Then I tried to install Xposed framework and now it's stuck in the bootloop again ...........

Never heard about the H version before! Anyway, make sure you are flashing the correct Xposed, that is Wanam's, but Arter's, and read the installation instructions closely.

Nixdax said:
It's N910H
I resolved it by recovering my phone via Kies though I lost all my data
Then I tried to install Xposed framework and now it's stuck in the bootloop again ...........
Click to expand...
Click to collapse
Please, search before flash.

H model is with Exynos processor.
http://www.sammobile.com/firmwares/database/SM-N910H/

Marshmallow slowed my phone, so I tried flashing marshmallow again via odin and softb

Hi,
Recently my phone autoupdated to marshmalow, and since then it keeps freezing and crashing. I read somewhere that the final fix to this is to reflash the firmware, so I tried and since then odin gives me an error message and the phone wont start.
I am quite new to all this, but I followed instructions from many different youtube tutorials and other online tutorials. ODIN keeps giving me a write error.
I am using different versions of odin, different usb ports and even different cables with the same end result. ODIN flash ends with error.
My note 4 has reactivation lock off, and never been rooted before. It is a UK N910F model and usually on Three mobile.
I really hope someone can help as I have struggled with this for past 2-3 days with no luck.
Here is the details from odin.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1DPE1_N910FEVR1DPE1_N910FXXU1DPB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> modem.bin
<ID:0/006> cache.img.ext4
<ID:0/006> hidden.img.ext4
<ID:0/006> FAIL! (Ext4)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

firstly odin cache whatever is given to it first then after success it attempts to flash , so either you had a successful attempt once or you entered boot loop prior to using odin .
second what you have here can be one of two things (assuming that you are quite positive about your phone version and downloaded the right firmware to it because if you are not then this might explain why you ended up with a boot loop) , where either your phone is operator locked ( in this case the firmware must be provided by the service provider ) or the usb cable is damaged ( i know you said you tried different ones , but trust me they can all be damaged , try finding a fresh one on a friend )
cheers

Odin kept failing at the hidden.img.tar.ext4 file so i googled, and found that extracting the hidden file and then flashing that file separately in odin may work. I tried that and worked!
Phew!
night-mayor said:
firstly odin cache whatever is given to it first then after success it attempts to flash , so either you had a successful attempt once or you entered boot loop prior to using odin .
Thanks form your input and help
second what you have here can be one of two things (assuming that you are quite positive about your phone version and downloaded the right firmware to it because if you are not then this might explain why you ended up with a boot loop) , where either your phone is operator locked ( in this case the firmware must be provided by the service provider ) or the usb cable is damaged ( i know you said you tried different ones , but trust me they can all be damaged , try finding a fresh one on a friend )
cheers
Click to expand...
Click to collapse