Database Users

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.

[Q] Bricked - Please help

'm on the Sprint Galaxy S4 SPH-L720. I've spent about 10 hours on this - reading and following posts and trying different flashes with no luck. I was on the Pac Man Rom (with CW MOD 11): pac_jflte-dev-20140831.zip (I believe in my phone it showed KitKat 4.4.4) . I was having issues with reception, getting voicemails, and battery, so I wanted to revert to Stock Rom (I think I tried mk2), and ran into problems. I've been trying to flash NAE (and use the NAE pit file) with different versions of Odin, different USB jacks, etc but with no luck. The error messages I get in Odin are:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
And my phone says in red:
Start {224,1440}
Secure Check Fail: PIT
SV rev. check fail : fused : 5 Binary : 4
Click to expand...
Click to collapse
The NAE i'm flashing is: L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5
I really appreciate any help anyone can offer.

You aren't flashing the correct file. Did you upgrade to the latest OTA NG2 update recently?

I think you was flash wrong combination of flashable.. Maybe..
Again. Check your flashable..

daniel4653 said:
You aren't flashing the correct file. Did you upgrade to the latest OTA NG2 update recently?
Click to expand...
Click to collapse
Thank you for your replies. Daniel4653, I didn't do any OTA updates (I think because the phone was rooted, I couldn't, no?). What is the correct file to flash? I've downloaded a bunch:
SPR-L720VPUEMK2-20131212171424
SPR-L720VPUAMF9-20130626162512
SPR-L720VPUFNAE-20140224205519
L720VPUAMDC_L720SPTAMDC_SPR

I had used an older version of Philz Recovery (philz_touch_6.07.9-i9300.tar.md5) and when I tried a newer version (philz_touch_6.15.6-jflte.tar.md5), I was able to boot into Clockwork Mod. From there I was able to install a custom ROM again. Phew. Also, I know understand that a phone that has Knox installed (0x1) won't work with Odin anymore. See http://forum.xda-developers.com/showthread.php?t=2447832&page=7

After getting Cyanogenmod up and running, I realized that I have no sound, am not able to make calls and the battery drains very quickly. I found a link with someone that has a similar issue (but not on sprint) - I can't post links yet but if you google "No Sound After Updating And New Instalation Of Cm11" it's the first article.
It seems like it's an issue with my modem or boot loader (sorry I'm a noob and doing my best to understand everything - spent all day trying to get my phone working )? I tried flashing the MK2 modem only MK2-ModemOnly.tar.md5 with no luck. I get an error in ODIN.
I know it's a problem people are having with cyanogenmod. Could I install another rom like negalite wonder rom (ng2)?
Thank you.

garbage914 said:
After getting Cyanogenmod up and running, I realized that I have no sound, am not able to make calls and the battery drains very quickly. I found a link with someone that has a similar issue (but not on sprint) - I can't post links yet but if you google "No Sound After Updating And New Instalation Of Cm11" it's the first article.
It seems like it's an issue with my modem or boot loader (sorry I'm a noob and doing my best to understand everything - spent all day trying to get my phone working )? I tried flashing the MK2 modem only MK2-ModemOnly.tar.md5 with no luck. I get an error in ODIN.
I know it's a problem people are having with cyanogenmod. Could I install another rom like negalite wonder rom (ng2)?
Thank you.
Click to expand...
Click to collapse
If you can mount everything and wipe all in cwm (follow the steps) you can flashing another roms..
But make sure you can doing mount or etc..

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)

Downgrading from 5.1.1 to 5.0.1

I've recently updated to 5.1.1 thru OTA update. Running fine for a few days but now phone keeps random rebooting and frequent crashes or hangs. Suspecting it may have been due to firmware.
Had did a factory reset and wiping of cache partition but issue persists.
So over here I'm trying to downgrade my firmware. But odin shows this:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MK2_Full_Odin_Tar.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my phone, it shows:
[1]eMMC write fail: ABOOT
Please advise me what should I do? Really appreciate it because the frequent crashes are really frustrating. Thanks in advance!

jengkhit said:
I've recently updated to 5.1.1 thru OTA update. Running fine for a few days but now phone keeps random rebooting and frequent crashes or hangs. Suspecting it may have been due to firmware.
Had did a factory reset and wiping of cache partition but issue persists.
So over here I'm trying to downgrade my firmware. But odin shows this:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MK2_Full_Odin_Tar.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my phone, it shows:
[1]eMMC write fail: ABOOT
Please advise me what should I do? Really appreciate it because the frequent crashes are really frustrating. Thanks in advance!
Click to expand...
Click to collapse
if your phone is upgraded COJ5, you can not to downgrade of it. there is no way ,I am trying almost two weeks .and you can find two titles about this

mudur1998 said:
if your phone is upgraded COJ5, you can not to downgrade of it. there is no way ,I am trying almost two weeks .and you can find two titles about this
Click to expand...
Click to collapse
Then there is no other way to work around? The constant crashing and freezing is driving me nuts.

Download the official rom from samfirmware and reflash it via odin with option Nand Erase Alll

GrippingSphere said:
Download the official rom from samfirmware and reflash it via odin with option Nand Erase Alll
Click to expand...
Click to collapse
Have you ever done this or heard of anyone doing it successfully? Everything I've read over the past 5 years is that will make a phone FUBAR'd.

dicksteele said:
Have you ever done this or heard of anyone doing it successfully? Everything I've read over the past 5 years is that will make a phone FUBAR'd.
Click to expand...
Click to collapse
I've done it multiple times on my phone. Flashing with Nand Erase All option is just erasing everything on your internal sd card, so all your previously installed programs and scripts that may conflict with the new rom will be erased.
It will not affect your EFS or your IMEI.
You just have to save all your important files to your external sd card first.

GrippingSphere said:
I've done it multiple times on my phone. Flashing with Nand Erase All option is just erasing everything on your internal sd card, so all your previously installed programs and scripts that may conflict with the new rom will be erased.
It will not affect your EFS or your IMEI.
You just have to save all your important files to your external sd card first.
Click to expand...
Click to collapse
Interesting..... Have you done it with the COJ5 bootloader? And flashed to a 5.0.1 bootloader?
I understand what you are saying.
I've read some more about it this afternoon. Only a few articles suggested doing it. But they suggesting backing up /efs.
Not sure how /efs survives a internal sdcard erase.
I would think all partitions would be torched.

GrippingSphere said:
I've done it multiple times on my phone. Flashing with Nand Erase All option is just erasing everything on your internal sd card, so all your previously installed programs and scripts that may conflict with the new rom will be erased.
It will not affect your EFS or your IMEI.
You just have to save all your important files to your external sd card first.
Click to expand...
Click to collapse
yes,before COJ5 it could be done,did you try this method(I have tried several times and several stock roms from sammobile)after COJ5,if you did not ,I strongly advice you ,do not try it ,if your phone is still on any other firmware except COJ5

I'm sorry for the confusion. My original post is actually in response to jengkhit's post when he mentioned that he is experiencing frequent crashes after updating via OTA. I recommend flashing the official rom via odin but the same 5.1.1 rom or later, not to a lower rom version like 5.0.1. I know that one cannot flash to a lower rom version once upgraded to the latest 5.1.1.

GrippingSphere said:
I'm sorry for the confusion. My original post is actually in response to jengkhit's post when he mentioned that he is experiencing frequent crashes after updating via OTA. I recommend flashing the official rom via odin but the same 5.1.1 rom or later, not to a lower rom version like 5.0.1. I know that one cannot flash to a lower rom version once upgraded to the latest 5.1.1.
Click to expand...
Click to collapse
Hey GrippingSphere, thanks for your reply. I was busy over the weekend so no time to see this thread. I'm still facing the same issues. Now my phone often can't boot up. When it boots, often goes to Odin mode with mmc_read failed. Then I have to do soft reset multiple times before getting it to boot. I figured out the only way to prevent hanging/rebooting is to continuously run music/video player. Is this software or hardware issue?
Anyway, I tried to flash same version firmware to overwrite but also encountered the same problem in Odin. What might be the issue? And now my binary is custom although firmware is official.
My warranty already expired so I'm really praying I can fix this if it is software related.
Thanks again, anyone, who can help or encountered similar issues.

I can only think of reflashing your official rom then factory reset as the possible solutions to your phone problem. If these doesn't work then it might be a hardware problem already.

Samsung J3 - J320FN UK EE bricked?

Ok i have searched the site for an exact answer to the issue i have encountered, with not getting a specific answer to my question. If there is already a thread for my exact problem, or two to solve the two issues i have encountered, please share the link, thank you.
My Wife and I got her son a Galaxy J3 (SM-J320fn) open network, with a Giff Gaff sim, from Argos. Its his first phone and we wanted to see if he could look after it, and if so, we would get him a better model at Christmas. Now his dad wanted to put google family link on the device, and due to it being only android 5.1, this was not possible. This sparked a huge row between my wife and her ex, with him being a general ****. I have tinkered with PC's and X-box 360s before, and thought i could have a go at Rooting the device and installing a custom android 7 rom. I didn't go into this lightly, and read that XDA was the very best place to seek advice and guides. I read up on rooting the device i had, Odin,TWRP and the OS linage android 7 rom. I was comfortable, that although it was very in depth to my skill set, i felt i could do it. I followed the guide to rooting the J320fn, installing the drivers, and USB debugging, fired up ODIN as administrator and installed TWRP, from there i followed the guide to install the custom ROM after than.
all was fine. device was android 7 and google family link was installed. everybody was happy...
My step son left his phone in the school office after his football match after school the other day and the device powered down for the first time since i uploaded the custom rom. When powering up the device we got the custom binary blocked by FRP lock issue. ok... so i came back here to XDA to read a thread about that. i decided that maybe i should have looked into other parental apps instead of messing about with the phone. so i went down the root of restoring the stock firmware and to battle it out with the dad about using a different parental app. so i downloaded the stock firmware for the device, and put the device into download mode. i ran ODIN but the install failed and on the device the loading bar at the bottom was about 5mm into the download and nothing else moved... ****... ok... now what? i took out the battery, and then powered up again. "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" ... Oh man, now what. so i return back XDA to look at this. read the guide and went to KIES3 to install stock firmware, but kies doesn't seem to recognise my device model? i click the emergency firmware recovery, but lists no device to recover?
so now im searching frantically to solve this... i downloaded the stock firmware from SamMobile; J320FNXXU0ARA1_J320FNEVR0ARA1_J320FNXXU0ARA1_HOME.tar.md5 (which took like 17 hours.. meh) and that Fails in ODIN too...
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> nvitem.bin
<ID:0/003> PM_sharkl_arm7.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
then i read to try install TWRP again, which also didn't work either as that brought up the binary blocked by FRP again and Failed in ODIN.
"<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> Added!!
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
So now i really don't know what to do... is it bricked? any and all help would be much appreciated.
Thank you
Rob