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..

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.

[HELP] Galaxy S4 GT-I9506 Bootloop

I just recently unrooted my device and tried to make a fresh new start
I came into Recovery , wiped cache and after that wiped user data (Factory Reset)
i tried to reboot it , still via recovery, but now it's stuck on boot. (Samsung logo with the little circles just being there...)
Since I'm total noob at this , what can i do to finally boot my device ?
Thanks

Reflash official stock rom using odin. This will erase everything and you will need to start from scratch. PM me for help using odin
Sent from my MotoG3 using XDA-Developers mobile app
---------- Post added at 05:28 PM ---------- Previous post was at 05:27 PM ----------
You could also only reflash the boot partition using adb...
Sent from my MotoG3 using XDA-Developers mobile app

It's really a dumb question ,but i'll ask anyway. I recently damaged my usb cable , it doesn't work now. I charge my mobile with these Samsung chargers , where you can't pull out the usb cable
So is there a way to do it without connecting my device to PC ??

.kyon said:
It's really a dumb question ,but i'll ask anyway. I recently damaged my usb cable , it doesn't work now. I charge my mobile with these Samsung chargers , where you can't pull out the usb cable
So is there a way to do it without connecting my device to PC ??
Click to expand...
Click to collapse
Unless you manage to boot the phone, no.

GDReaper said:
Unless you manage to boot the phone, no.
Click to expand...
Click to collapse
I have managed to finally obtain a USB cable, but i really can't find a STOCK ROM for my device. I have been reading.. I have found that you need special stock rom due to your carrier so you can call etc.
Is it true ? If so -- i would have to search for "Samsung Galaxy S4 GT-I9506 Czech Republic T-Mobile Stock rom" ?
Thanks.. (i can't find it..)

.kyon said:
I have managed to finally obtain a USB cable, but i really can't find a STOCK ROM for my device. I have been reading.. I have found that you need special stock rom due to your carrier so you can call etc.
Is it true ? If so -- i would have to search for "Samsung Galaxy S4 GT-I9506 Czech Republic T-Mobile Stock rom" ?
Thanks.. (i can't find it..)
Click to expand...
Click to collapse
Only if it is carrier locked

GDReaper said:
Only if it is carrier locked
Click to expand...
Click to collapse
How can i check that ?

.kyon said:
How can i check that ?
Click to expand...
Click to collapse
Does it work with other Sim cards?

GDReaper said:
Does it work with other Sim cards?
Click to expand...
Click to collapse
Oh i get it now.. stupid me.
I just downloaded a stock rom, so im going to try it.

GDReaper said:
Does it work with other Sim cards?
Click to expand...
Click to collapse
Im flashing the rom quite some time (over 3hours)
and it seems to be stuck in odin..
here is the actual log :
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUDOK1_I9506OXXDOK1_I9506XXUDOJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<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> 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

.kyon said:
Im flashing the rom quite some time (over 3hours)
and it seems to be stuck in odin..
here is the actual log :
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUDOK1_I9506OXXDOK1_I9506XXUDOJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<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> 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
Click to expand...
Click to collapse
Make sure the connection between the phone and the PC is stable.
Playing around with the phone might briefly disconnect it.
It could also be caused by the cable. Odin is sensitive in this sense and it is possible to not work unless you use an original Samsung cable.

GDReaper said:
Make sure the connection between the phone and the PC is stable.
Playing around with the phone might briefly disconnect it.
It could also be caused by the cable. Odin is sensitive in this sense and it is possible to not work unless you use an original Samsung cable.
Click to expand...
Click to collapse
I tried it several times over the course of 2 days , leaving the phone and PC alone , while in school , while i sleep and everytime it just FAILs
i noticed a SS_DL.dll in my rar with the stock rom (from sammobile)
Could it be my problem ? If it isn't the problem (the .dll)
i'll post exactly how i try to flash it, so you can help me - if i am doing anything wrong..
Thanks

.kyon said:
I tried it several times over the course of 2 days , leaving the phone and PC alone , while in school , while i sleep and everytime it just FAILs
i noticed a SS_DL.dll in my rar with the stock rom (from sammobile)
Could it be my problem ? If it isn't the problem (the .dll)
i'll post exactly how i try to flash it, so you can help me - if i am doing anything wrong..
Thanks
Click to expand...
Click to collapse
I told you, Odin is very sensitive.
It can fail because of the cable.
It can fail because of the USB ports.
It can fail because of Windows version.
And it can fail because of Odin version.

GDReaper said:
I told you, Odin is very sensitive.
It can fail because of the cable.
It can fail because of the USB ports.
It can fail because of Windows version.
And it can fail because of Odin version.
Click to expand...
Click to collapse
Ok thanks for the advice, but what about the .dll part ? Is it neccessary or it is in the .rar just "because" ?

.kyon said:
Ok thanks for the advice, but what about the .dll part ? Is it neccessary or it is in the .rar just "because" ?
Click to expand...
Click to collapse
You're supposed to have a .tar files, not rar file.

GDReaper said:
You're supposed to have a .tar files, not rar file.
Click to expand...
Click to collapse
I downloaded a .rar package from sammobile.com
EXTRACTED the .rar to my desktop
the rar contained these 2 files :
I9506XXUDOK1_I9506OXXDOK1_I9506XXUDOJ2_HOME.tar.md5
&
SS_DL.dll
The file i put in ODIN (The AP box) is the .tar one

.kyon said:
I downloaded a .rar package from sammobile.com
EXTRACTED the .rar to my desktop
the rar contained these 2 files :
I9506XXUDOK1_I9506OXXDOK1_I9506XXUDOJ2_HOME.tar.md5
&
SS_DL.dll
The file i put in ODIN (The AP box) is the .tar one
Click to expand...
Click to collapse
Any ideas about .dll ? Or explanation what it is doing there ? Thanks

.kyon said:
Any ideas about .dll ? Or explanation what it is doing there ? Thanks
Click to expand...
Click to collapse
Why are you so obsessed about that dll file?
There's nothing you can do with it, Odin can flash ONLY tar files.
I told you the most common reasons Odin fails, and none of them are a dll file.

GDReaper said:
Why are you so obsessed about that dll file?
There's nothing you can do with it, Odin can flash ONLY tar files.
I told you the most common reasons Odin fails, and none of them are a dll file.
Click to expand...
Click to collapse
Obsessed, well yea thats true I just thought it may be reason why it fails
Let me try it few more times.

Hi, I have this exact same problem. I came from a custom rom (Aurora) and tried to flash stock but whichever stock I use via Odin (which succeeds and reboots etc) I just end up back at the Samsung screen with blue sparks. I've left it there for 15-20 minutes and it just stays. Very sad Look forward to seeing if you find a fix

Samsung S4 (i9505) bricked. Recovery doesn't work, only download mode.

Hi.
So what I recently did was I plug phone in downlaod mode to pc and install stock firmware (the same that was installed already 5.0.1) using odin. Unfortunetly phone still bricked, recovery doesnt't work. Then i was flash twrp recovery from odin and now phone show me:
recovery is not seandroid enforcing set warranty bit recovery alert. Now I'm thinking about do re-partition and install stock rom again, but i want to save my files.
Maby I'm doing something wrong, please help me.
Sorry for my english ;_;

What is the model # in download mode? Did you use the stock ROM from sammobile.com? Any errors when flashing with Odin?

audit13 said:
What is the model # in download mode? Did you use the stock ROM from sammobile.com? Any errors when flashing with Odin?
Click to expand...
Click to collapse
No errors with flashing, I downloaded rom from stockroms.net, because sammobile download speed is frustrating and...
Model #? I do not understand what you mean. I see only GT-I9505, system status, knox etc.

I would try a firmware from samsung-updates.com or sammobile.com.

audit13 said:
I would try a firmware from samsung-updates.com or sammobile.com.
Click to expand...
Click to collapse
Ok, now i downloaded rom from sammobile.com (goo_gl/os9avL) and flash faild!
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUHPK2_I9505XEOHPL1_I9505XXUHPK2_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> SingleDownload.
<ID:0/003> aboot.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> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
What should I do now?

Now i was tried with odin 3.11v and faild again. Previously i used 3.09v.
Code:
<OSM> Enter CS for MD5..
[...]
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!

Was the phone dropped? What happened that needed you to reflash there stock ROM?
Can you flash twrp using Odin?

audit13 said:
Was the phone dropped? What happened that needed you to reflash there stock ROM?
Can you flash twrp using Odin?
Click to expand...
Click to collapse
I need to flash to stock, because phone start restarting itself and sometimes gets bootloop. When I tried enter to recovery mode phone instantly reboot, after few tries recover stop working.

Maybe flash twrp to see if you can get into recovery?

audit13 said:
Maybe flash twrp to see if you can get into recovery?
Click to expand...
Click to collapse
When I flash twrp and enter recovery mode I have this alert:
Code:
recovery is not seandroid enforcing set warranty bit recovery

So the phone stays on that message or something else happens?

audit13 said:
So the phone stays on that message or something else happens?
Click to expand...
Click to collapse
Phon stay on that message and nothing else happeneds. Any tips?

Sounds like there could be a problem with the phone's internal memory chip. You could take it to a cell repair shop to see if they can flash the firmware using a jtag cable or octopus box.

audit13 said:
Sounds like there could be a problem with the phone's internal memory chip. You could take it to a cell repair shop to see if they can flash the firmware using a jtag cable or octopus box.
Click to expand...
Click to collapse
Hmmm. What you think about flashing system with re-partition option? It make sense?

You can try flashing with a pit file. Make sure you get a pit file that matches the phone's internal memory size.

audit13 said:
You can try flashing with a pit file. Make sure you get a pit file that matches the phone's internal memory size.
Click to expand...
Click to collapse
OK, when I do this, there is no way to save my files? Do you think, service can keep my internal data?

It's going to be very expensive to try and recover data, especially if the internal memory chip is damaged.