I've got a sprint galaxy s4, was running 4.2.2 and I had added the hotspot mod by overwriting some files to make that happen. I was attempting to go back to stock in order to update to 4.3 via an Odin3 flash and something happened. I can only boot into the download mode, I can't get into recovery mode at all. If I try to get into recovery, I get the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
Kies will not recognize my phone. When I plug it into my computer via usb, I hear a notification. Kies attempts to connect, but never does successfully. I have no way of getting my serial number as I can't boot it and it's not listed under the battery cover. I have tried uninstalling/reinstalling drivers with no success. I have tried to uninstall Kies completely and flash via Odin3 but get a failure below
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMF9_L720SPTAMF9_L720VPUAMF9_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<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!!
Also tried again and got these messages
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMF9_L720SPTAMF9_L720VPUAMF9_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> Removed!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I hope I've provided info on what I have tried. I am not an expert by any means, but would really appreciate any help. At this point I'm looking to just get back to stock and have a usable phone. I don't care about losing any info and am willing to wipe/flash whatever I can. Thank you for any input! I'm hoping to not have to take this to the sprint store
You just have to odin the stock mf9 tar again. I would try a different version of odin, a different usb port, or a different usb cable. Odin will fix your problem, don't use kies. I used odin 3 version 3.07 but I've also had a lot of success with odin 3 ver 1.85 that is included when you download cf autoroot. Also, make sure you are running odin as administrator.
cruise350 said:
You just have to odin the stock mf9 tar again. I would try a different version of odin, a different usb port, or a different usb cable. Odin will fix your problem, don't use kies. I used odin 3 version 3.07 but I've also had a lot of success with odin 3 ver 1.85 that is included when you download cf autoroot. Also, make sure you are running odin as administrator.
Click to expand...
Click to collapse
Thanks for your reply. I am trying to flash the stock .tar but I'm not having any success. I get the error messages I listed above. Any clue what those mean or what I could be doing wrong? That looks like greek to me. I really don't know what any of it means.
i would just use the CF-autoroot odin......this has saved my ass twice !!! seems to be the " mirical odin " program
chris-allen said:
i would just use the CF-autoroot odin......this has saved my ass twice !!! seems to be the " mirical odin " program
Click to expand...
Click to collapse
wow. Finally figured it out. I tried 3 different USB ports, none of those worked. Tried a 4th on the back of my PC and viola, finally got Odin to work. THanks for your help!
Related
Hi all,
i tried to flash cyanogenmod unofficial, on the flash an error was comming, now the device dosent start...
when i boot the phone normaly, is comming: firmware upgrade encountered an issue. please select recovery mode in kies & try again.
i tryed to flash the original firmware:
(I9505XXUAMDF_I9505AUTAMD8_AUT)
I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_HOME.tar
but an error in odin is comming:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_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> Removed!!
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
please can you help me?
cutalaxy said:
Hi all,
i tried to flash cyanogenmod unofficial, on the flash an error was comming, now the device dosent start...
when i boot the phone normaly, is comming: firmware upgrade encountered an issue. please select recovery mode in kies & try again.
i tryed to flash the original firmware:
(I9505XXUAMDF_I9505AUTAMD8_AUT)
I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_HOME.tar
but an error in odin is comming:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_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> Removed!!
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
please can you help me?
Click to expand...
Click to collapse
Try flashing along with pit file
MKe sure u have the proper file for the same
Sent from my GT-I9500 using xda premium
123hiten said:
Try flashing along with pit file
MKe sure u have the proper file for the same
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
where can i find the pit file?
cutalaxy said:
where can i find the pit file?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2265477&highlight=stock+firmware
this link has it attached take the correct one u would know better
dont worry i had the same issue on my note 2 a month ago and was wrkng fine after flashing rescue firmware urs wil work too
damn, it doeset work for me
is it hard brick?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_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> 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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
cutalaxy said:
damn, it doeset work for me
is it hard brick?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDF_I9505AUTAMD8_I9505XXUAMDF_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> 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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
No its not at a hard brick dont worry dont panic thats the best wat to work around
I would say dont use pit file unless its last option and try without that only may be in other pc using other cable some below steps myte also help u
2) Install later Kies.
3) Kill al kies applications (all 4 of them).
disable antivirus or whatever you got there.) Get to Download Mode and push Vol Up.
7) Open Odin.
8) Plug the device to your laptop.
Does it see the device?
If NO:
A) Get another usb cable, are you using ?
B) Try different Odin Versions (download 3 or 4).
C) Try another USB port.
D) Still no luck? reboot the pc and start from step 3.
---------- Post added at 08:30 PM ---------- Previous post was at 08:23 PM ----------
Download 2/3 stock firmware and try installing thru ODIN it should work
Make sure u have all the drivers installed
MAke sure kies is not open or make sure its closed even in background process
okay, with odin 1.85 now has worked phu... lucky
but i'm confused... all(!) my settings and apps etc. are still installed and settet? why dat?
only root is going... i'm now flashing root again
i think i will wait for an official CWM and official Cyanogen... is to hot for me
@123hiten
thank you very much!! I thought now i have to get out 700$ again... :S
cutalaxy said:
okay, with odin 1.85 now has worked phu... lucky
but i'm confused... all(!) my settings and apps etc. are still installed and settet? why dat?
only root is going... i'm now flashing root again
i think i will wait for an official CWM and official Cyanogen... is to hot for me
@123hiten
thank you very much!! I thought now i have to get out 700$ again... :S
Click to expand...
Click to collapse
Official firmware is not a wiping one. It doesnt flash userdata, it replace system, recovery, and some other partitions.
sent from my Galaxy
cutalaxy said:
okay, with odin 1.85 now has worked phu... lucky
but i'm confused... all(!) my settings and apps etc. are still installed and settet? why dat?
only root is going... i'm now flashing root again
i think i will wait for an official CWM and official Cyanogen... is to hot for me
@123hiten
thank you very much!! I thought now i have to get out 700$ again... :S
Click to expand...
Click to collapse
Great to hear that man
If u flash stock firmware all will remain as its in ODIN but its good if u reset the device after or b4 root
Also take a EFS backup of ur device and be safe
i had root before the device bricks... so i rootet it now again, and works good...
yeah, i will backup efs (hope this <- works...)
yah, thank you again...
have a nice day..
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.
Last night I bricked my phone, trying to flash the stock modem (NAE) on mobile Odin. As of right now, it does not boot, simply being stuck at the SAMSUNG GALAXY S4 screen. It will not boot into recovery, instead rebooting to the same screen once more. Kies will not see the connection, and I have reinstalled it, the drivers, etc.
Odin does the same thing, but sees the connection. All I get is this after trying to flash the firmware (both with Auto Reboot and F. Reset Time on and off)
<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> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
And the firmware that I am using is the "L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5." I don't know what to do, and I was thinking that someone could help me here.
Were you on NG2 perhaps? If so, you cannot go back to NAE and that would explain the Odin failure.
Go to www.sammobile.com and download the NG2.tar and give that a try.
If only I had thought of that (which I couldn't have)! Thanks, this worked. I was on the NC6 version of the ROM, and have downloaded/installed this. It works like a charm except one thing; the data seems to either not be working, or extremely slow at times. That, and the messaging does not appear to work. Wifi is the same way at times.
Novorone said:
If only I had thought of that (which I couldn't have)! Thanks, this worked. I was on the NC6 version of the ROM, and have downloaded/installed this. It works like a charm except one thing; the data seems to either not be working, or extremely slow at times. That, and the messaging does not appear to work. Wifi is the same way at times.
Click to expand...
Click to collapse
If you were on NC6 you have a triband model (720T) and need NG5.tar.
this model seems difficult (gt-i9506)
i tried to root it via towelroot, then kingoroot, these failed but then now the reboot is stuck on "firmware upgrade encountered an issue"
ive tried Kies firmware recovery but the download fails after 80%,
ive tried the sammobile download the ROM this too fails, network drops out tried this 3 times
i want to try Kies emergency recovery but cant find any recovery code
im stuck i dont know what to do now been researching for 4 hours cant find solution :crying:
could anyone please help?? am going crazy over this spent 2 days researching and finding nothing
Download a complete stock rom and flash it with ODIN. You have to uninstall KIES beforehand (they are conflicting).
thanks for reply...
i took kies off and this is what Odin is giving me...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUAMHF_I9506VAUAMH3_I9506XXUAMHD_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
the device says this.....
SW REV CHECK FAIL: [aboot]Fused 1 > Binary0
does this highlight anything that could be going wrong?
Not sure... but looks like the rom is not for that device. Are you sure you have a i9506?
on samsmobile GT-I9506/VAU/ Roms (i cant post link)
well the first ROM was 4.2 android (bottom of ROM list), so then tried 4.4 (top of ROM list) android it failed again but with different Odin errors...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUCNJ1_I9506VAUCNJ1_I9506XXUCNK1_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
can anyone see the fault here...?? no error came up on the device, only on Odin this time
Did you restart after KIES de-installation? Was USB driver successfully missing (so you had to install one manually for ODIN)? If not, you probably still have drivers/files running from KIES.
Otherwise, try a different computer to double check its not the system.
If you originally updated to Android 4.4.x or later on this device, you cannot install 4.3.x or lower as Knox within the bootloader will actively prevent Odin from functioning. As to Odin, make sure you're using the original cable, are not using a hub, have Kies disabled or uninstalled, and use a different USB port. Odin sometimes is picky about the ports it uses.
If you can get the ROM issue resolved, use CF-Autoroot to root, keeping in mind that you will trip the Knox flag in doing so. Towelroot and other one-click root methods don't work on your device.
FIXED IT!!!!!!! :laugh::silly::good::cyclops:
Moved all operations to a different PC running XP with no kies on it
The error still occurred "write fail"
So instead i tried Odin 3.09 instead of 3.07 but most of all i changed usb cables, found an original cable off my mates Nokia
then boom!!! she starting writing!!!
Thankyou so much you legends, you are now my best friends forever!!!
Strangely the new flash, all my old previous data & apps are still on there??? somehow the network is not locked either which i was fearing being a vodafone ROM
still want to root it though
Flashing a ROM through Odin doesn't wipe the data partition, which is why your apps are untouched.
ok let`s start from the start, i tried to root my note 3 sm-n9005 and failed to succeed.
i used the cf auto root guide, odin said success but my phone failed to boot and went straight to recovery mode.
then, i tried using odin 3.07/09/11/185 to rewrite into the stock rom, but odins says FAIL and gives nothing in return.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBPB1_N9005EVRGBPB1_N9005XXUGBOJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
i just want get my phone back with android that above 4.4
please help :crying:
Looks like the ROM you are trying to flash is not made for your phone or the ROM is older than the ROM currently installed on the phone.
Are you using the original Samsung USB cable? Tried different USB cables and ports?
For Root note 3 use Towelroot by Chainfire.
Sent from my Limited Edition Note 3 LTE using Super Tapatalk
Download Official 5.0 ROM from Sammobile and flash it in Odin, after it try to root phone...
In dialog this looks like firmware file is damaged
The firmware doesn't look damaged, the firmware you are trying to flash has a bootloader that is older than the bootloader in the phone.
isn't chainfire's root method called cfautoroot?
download one more time...