Guys,
I tried to install the free wifi that QBKING had in his youtube channel. I was on MJA. What happened was I got stuck at the sprint screen.
Now I tried to Unroot the phone through downloading the tar file from QBKings website for sprint L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5
I checked the MD5 of the zip file once it was downloaded and it matched.
However, Now I don't have a dam phone because It keeps on failing in odin. I checked a few different usb ports.
With the message
SW REV. CHECK FAIL : fused : 4 , Binary : 1
Can someone please help me!
First of all, you need to know what you are doing before you use old videos to update your phone. The latest software which was MJA, but is now MK2, you can't go back to older firmwares. MDC was the original firmware that was released with the phone when it came out in May. The best thing to do at this point is to download the MJA full tar file from sammobile.com or from the development section here. Odin it to your phone, you may need to do a factory reset afterward to get it to boot. Once your phone is on MJA you cannot odin any firmware that is older than MJA or you will end up bricked again. After that, you can reroot your phone using cf-autoroot and install a custom recovery. Then, find the MJA odexed hotspot mod here: http://forum.xda-developers.com/showthread.php?t=2256950 and flash that in recovery. Then you will be where you wanted to be.
cruise350 said:
First of all, you need to know what you are doing before you use old videos to update your phone. The latest software which was MJA, but is now MK2, you can't go back to older firmwares. MDC was the original firmware that was released with the phone when it came out in May. The best thing to do at this point is to download the MJA full tar file from sammobile.com or from the development section here. Odin it to your phone, you may need to do a factory reset afterward to get it to boot. Once your phone is on MJA you cannot odin any firmware that is older than MJA or you will end up bricked again. After that, you can reroot your phone using cf-autoroot and install a custom recovery. Then, find the MJA odexed hotspot mod here: http://forum.xda-developers.com/showthread.php?t=2256950 and flash that in recovery. Then you will be where you wanted to be.
Click to expand...
Click to collapse
Thanks for the reply,
As far as the Wifi hotspot. I just followed his advice on his website but instead downloaded the system files from the MJA Odexed zip found on his website here. :http://qbking77.com/development/how-to-get-free-native-wifi-hotspot-on-the-sprint-samsung-galaxy-s4/
I didn't think I would mess up my phone this bad
Is this the correct file for sprint?. The file I am trying to flash in odin. is Sprint Galaxy S4 SPH-L720 VPUAMDC (Android 4.2.2) – Download found on QBkings website http://qbking77.com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4/.
But my phone keeps on failing in odin with the message I reported in my Original post.
So I should download the MJA file not the MK2 update? I really don't want to mess up my phone anymore then it already is. Could you please provide a direct link to the correct file to download in odin.
All I know is the tar file that Qbking is providing isn't working and keep on failing in odin.
Thanks again!
Modmyppc said:
Thanks for the reply,
As far as the Wifi hotspot. I just followed his advice on his website but instead downloaded the system files from the MJA Odexed zip found on his website here. :http://qbking77.com/development/how-to-get-free-native-wifi-hotspot-on-the-sprint-samsung-galaxy-s4/
I didn't think I would mess up my phone this bad
Is this the correct file for sprint?. The file I am trying to flash in odin. is Sprint Galaxy S4 SPH-L720 VPUAMDC (Android 4.2.2) – Download found on QBkings website http://qbking77.com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4/.
But my phone keeps on failing in odin with the message I reported in my Original post.
So I should download the MJA file not the MK2 update? I really don't want to mess up my phone anymore then it already is. Could you please provide a direct link to the correct file to download in odin.
All I know is the tar file that Qbking is providing isn't working and keep on failing in odin.
Thanks again!
Click to expand...
Click to collapse
It sounds like you downloaded the correct hotspot mod in the first place so it shouldn't have failed. Very often, the odexed and deodexed files get mixed up and that is why it is best to download the file from the original post here on XDA.
As far as the tar file, yes you have to download the MJA tar file and odin it. The MK2 file is only an update file and must be applied after the MJA tar is odined. After downloading the tar file extract the zip and then use a newer version of odin. I believe odin 3 ver 3.07 works best. Put your phone in download mode and connect it to your computer and verify that the com port shows up in odin. Run odin as administrator in windows and load the file in the PDA spot. Uncheck all the check boxes except for reboot and it should work. If you need the MJA file I can send you a link to my dropbox via PM.
cruise350 said:
It sounds like you downloaded the correct hotspot mod in the first place so it shouldn't have failed. Very often, the odexed and deodexed files get mixed up and that is why it is best to download the file from the original post here on XDA.
As far as the tar file, yes you have to download the MJA tar file and odin it. The MK2 file is only an update file and must be applied after the MJA tar is odined. After downloading the tar file extract the zip and then use a newer version of odin. I believe odin 3 ver 3.07 works best. Put your phone in download mode and connect it to your computer and verify that the com port shows up in odin. Run odin as administrator in windows and load the file in the PDA spot. Uncheck all the check boxes except for reboot and it should work. If you need the MJA file I can send you a link to my dropbox via PM.
Click to expand...
Click to collapse
Could it be something Im doing?
I downloaded Odin V 3.07 tried the Tar file again and still failed.
Here is what odin said.
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Does that tell you anything?
Could this tar file just be faulty? I would really like to try and download another tar file if you can pm me your link I would really appreciate it.
Thanks
Modmyppc said:
Could it be something Im doing?
I downloaded Odin V 3.07 tried the Tar file again and still failed.
Here is what odin said.
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Does that tell you anything?
Could this tar file just be faulty? I would really like to try and download another tar file if you can pm me your link I would really appreciate it.
Thanks
Click to expand...
Click to collapse
It looks like you are trying to install an old MDC tar, when you need to install the MJA tar, you can download it from here http://www.yourfavoritepainter.com/MJA_HOME.tar.zip
or you can go to http://sammobile.com/firmwares/ and find the latest version
Modmyppc said:
Could it be something Im doing?
I downloaded Odin V 3.07 tried the Tar file again and still failed.
Here is what odin said.
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Does that tell you anything?
Could this tar file just be faulty? I would really like to try and download another tar file if you can pm me your link I would really appreciate it.
Thanks
Click to expand...
Click to collapse
It's still trying to install the MDC tar, I will pm you the link to the MJA tar.
Please forgive the ignorance
I'm stuck as well, I keep seeing "Odin this to your phone" but the file is a .zip file. How can I use Odin with a zip?
Bageland2000 said:
I'm stuck as well, I keep seeing "Odin this to your phone" but the file is a .zip file. How can I use Odin with a zip?
Click to expand...
Click to collapse
It likely needs to be extracted. Or maybe it's a one click?
Sent from my SGH-L720 using Tapatalk
k2buckley said:
It likely needs to be extracted. Or maybe it's a one click?
Sent from my SGH-L720 using Tapatalk
Click to expand...
Click to collapse
OK, I now believe Odin referred to "Odin one click." I used TWRP to flash the zip and everything is working fine...
cruise350 said:
It's still trying to install the MDC tar, I will pm you the link to the MJA tar.
Click to expand...
Click to collapse
I am also having this problem, if i could have the link that would be greatly appreciated. I guess this QBking seems to be a hit for new rooters. Also i am downloading the MJA tar file that the other person posted on this thread. Is that a good idea or not?
My Sprint Samsung Galaxy s4 Stuck on Yellow Screen!!!!
HEY I DID THE EXACT Thing!!! Now I'm Stuck on the Sprint yellow Screen it won't boot pass THAT.
Can anyone HELP.... Thanks in Advance
thereal14life said:
HEY I DID THE EXACT Thing!!! Now I'm Stuck on the Sprint yellow Screen it won't boot pass THAT.
Can anyone HELP.... Thanks in Advance
Click to expand...
Click to collapse
As in the OP? Be more specific.
Sent from my SPH-L720 using Tapatalk
thereal14life said:
HEY I DID THE EXACT Thing!!! Now I'm Stuck on the Sprint yellow Screen it won't boot pass THAT.
Can anyone HELP.... Thanks in Advance
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2626871
this is a thread from where I had the exact same problem. Follow this and it should get you going again. it worked for me. I was on MK2...it was on my phone when i got it.
I received a fail message as well along with this
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUEMJA_L720SPTEMJA_L720VPUEMJA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
TaKaVp said:
I received a fail message as well along with this
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUEMJA_L720SPTEMJA_L720VPUEMJA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If you have already installed kit kat aka 4.4.2 or NAE, you cannot Odin an older version. Since the MJA software you are trying to Odin is failing with an Auth error, that tells me you are already on NAE and must use the NAE full tar file to restore your phone. Look for it in the development section in a thread from Random45. His links have great download speeds.
Sent from my icrap 2 using Tapatalk HD
Related
Hi Everyone
I've bricked my S4 stupidly by trying to install CF Auto Root without having USB Debugging enabled.
No my phone starts up telling me there was an incomplete upgrade and to continue it but kies can't seem to find anything.
I've tried reflashing the stock firmware but I keep receiving a error saying it can't find the PIT file for mapping.
Does anyone have one for the S4 I9505 INTL (UK) Variant.
Thanks
sandeepsb said:
Hi Everyone
I've bricked my S4 stupidly by trying to install CF Auto Root without having USB Debugging enabled.
No my phone starts up telling me there was an incomplete upgrade and to continue it but kies can't seem to find anything.
I've tried reflashing the stock firmware but I keep receiving a error saying it can't find the PIT file for mapping.
Does anyone have one for the S4 I9505 INTL (UK) Variant.
Thanks
Click to expand...
Click to collapse
usb debugging
see my signature for flashing with pit :good:
samersh72 said:
usb debugging
see my signature for flashing with pit :good:
Click to expand...
Click to collapse
I've just downloaded your pit file. The problem here is I can't get back into my phone and I can only go into download mode. Initially I set USB Debugging as off and tried flashing. So now I'm stuck with a bricked phone.
sandeepsb said:
I've just downloaded your pit file. The problem here is I can't get back into my phone and I can only go into download mode. Initially I set USB Debugging as off and tried flashing. So now I'm stuck with a bricked phone.
Click to expand...
Click to collapse
NO need to enable usb debugging to flash with odin, just put pit file and the firmware in odin and flash
sandeepsb said:
I've just downloaded your pit file. The problem here is I can't get back into my phone and I can only go into download mode. Initially I set USB Debugging as off and tried flashing. So now I'm stuck with a bricked phone.
Click to expand...
Click to collapse
Do not start panicking so soon all this happens while we tinker with device follow what samersh72 saying u ll have ur device working
Its not bricked at all
Sent from my GT-I9500 using xda premium
samersh72 said:
usb debugging
see my signature for flashing with pit :good:
Click to expand...
Click to collapse
samersh72 said:
NO need to enable usb debugging to flash with odin, just put pit file and the firmware in odin and flash
Click to expand...
Click to collapse
I've tried it and I'm getting a Failed message:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
I've attached a screenshot.
sandeepsb said:
I've tried it and I'm getting a Failed message:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
I've attached a screenshot.
Click to expand...
Click to collapse
Just tried again and I'm receiving this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
sandeepsb said:
Just tried again and I'm receiving this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try using ODIN 3.07 version
also make sure u have no kies programme running , try using diff usb port
it should work
sandeepsb said:
I've tried it and I'm getting a Failed message:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
I've attached a screenshot.
Click to expand...
Click to collapse
remove pit file from folder and put it on desktop and the firmware and odin
use odin 3.07 or 1.85
change usb port and use original cable
if you can go in recovery (i doubt)make a wipe)
retry
samersh72 said:
remove pit file from folder and put it on desktop and the firmware and odin
use odin 3.07 or 1.85
change usb port and use original cable
if you can go in recovery (i doubt)make a wipe)
retry
Click to expand...
Click to collapse
Crisis averted just flashed the PIT without anything in the PDA section and I've managed to boot back into my phone.
Thanks for the help and the PIT file.
sandeepsb said:
Crisis averted just flashed the PIT without anything in the PDA section and I've managed to boot back into my phone.
Thanks for the help and the PIT file.
Click to expand...
Click to collapse
glad to hear that, but usually it is flashed with the firmware if you would try again you will succeed......any way you make it :good:
Same happened with me, no matter how many times I tried flashing the PIT with the firmware, it just wouldn't have it at all.
When I flashed the PIT on it's own, it flashed fine, said reset, then booted back into android.
Glad you got it sorted though! It's scary when you see FAIL in big letters when flashing stuff! haha.
Read more, Learn more.....
---------- Post added at 07:45 PM ---------- Previous post was at 07:35 PM ----------
but in some cases where there is a serious firmware issue, pit file will work only with flashing firmware
Please help, I need the PIT file for M919 (T-mobile), anyone have it? Pleaseeeeee.
T-Mo GS4 Pit File
xs2k said:
Please help, I need the PIT file for M919 (T-mobile), anyone have it? Pleaseeeeee.
Click to expand...
Click to collapse
I too Also need this file as well, I can only seem to find the international GS4 pit files.
samersh72 said:
NO need to enable usb debugging to flash with odin, just put pit file and the firmware in odin and flash
Click to expand...
Click to collapse
samersh72 said:
remove pit file from folder and put it on desktop and the firmware and odin
use odin 3.07 or 1.85
change usb port and use original cable
if you can go in recovery (i doubt)make a wipe)
retry
Click to expand...
Click to collapse
I cant find the PIT partition file anywhere on your sig
I dunno if im looking in the wrong place. Can you give me a hint on where it is?
Im having problems with my phone and it wont load past the boot animation.
Chris
scientificharmony said:
I cant find the PIT partition file anywhere on your sig
I dunno if im looking in the wrong place. Can you give me a hint on where it is?
Im having problems with my phone and it wont load past the boot animation.
Chris
Click to expand...
Click to collapse
Attached here in first post http://forum.xda-developers.com/showthread.php?t=2265477
Sent from my Galaxy
samersh72 said:
Attached here in first post http://forum.xda-developers.com/showthread.php?t=2265477
Sent from my Galaxy
Click to expand...
Click to collapse
Hi, Thanks for that info. The device has now boot, but i seem to have error messages in recovery cannot mount E:\ etc etc
how the hell do i fix that lol
scientificharmony said:
Hi, Thanks for that info. The device has now boot, but i seem to have error messages in recovery cannot mount E:\ etc etc
how the hell do i fix that lol
Click to expand...
Click to collapse
reflash with i9505-cwm-recovery-6.0.3.2-4
wipe all
reflash with pit CSB_signed_Fusion3_EUR_0325_V2 and pda I9505XXUAME2_I9505OLBAMDM_I9505DXUAME2_HOME.tar
Just a word from me guys.
Please don't underestimate power of changing USB port and/or USB cable. I've just been sitting on soft-bricked s4, nothing seemed to work, ODIN 3.x or 1.8, original firmware or third party ROM/recovery etc, PIT file, nothing could be overwritten. I restarted PC and instal/reinstall drivers.. nothing.
I've changed the cable and USB port to the rear one et voila, all worked as a charm.
good luck.
Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html
frliran said:
Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html
Click to expand...
Click to collapse
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.
Here is the log from odin
radicalisto said:
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.
Click to expand...
Click to collapse
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...
frliran said:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...
Click to expand...
Click to collapse
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )
Here is the log of the first file
radicalisto said:
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )
Click to expand...
Click to collapse
The previous log was from the new file I downloaded today.
This is the log from "Odin3 v3.07" using the first file I rooted my phone with:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE...Can you please help me to re-root my phone.
(And if you can, please send me a link to download root for the KitKat version so that I can re-root it when the update will rollout in my country.)
Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?
yes
radicalisto said:
Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?
Click to expand...
Click to collapse
Yes I am.
But in odin 3.9 there is AP and not PDA.
But I tried both in both odin versions: 3.7 and 3.9.
In odin 3.7 I am using PDA, and in odin 3.9 I am using AP.
Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.
)-;
radicalisto said:
Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.
Click to expand...
Click to collapse
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country
frliran said:
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country
Click to expand...
Click to collapse
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**
hmmm
radicalisto said:
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**
Click to expand...
Click to collapse
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...
Solved it (-:
frliran said:
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...
Click to expand...
Click to collapse
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem
It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.
Thank you very much for your help
radicalisto said:
It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.
Click to expand...
Click to collapse
Yes (-:
Thanl you very much for your help and consideration
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.
Hello,
My brother has a 32gb Verizon Note 3 4.4.2. He managed to root his device and used safestrap, but somehow removed his stock rom and wound up in download mode to try to attempt to completely wipe it and install the original firmware. When following the steps in ODIN, there is a failed error. It reads:
Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_lo w_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> aboot.mbn
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone have any clue what the best route is to just completely wipe the phone and somehow get it working again? I'd really appreciate it.
Try the nc2 or nc4 firmware those are the 4.4.2 kitkat ones. Mi9 is 4.3 jellybean, it wont let you odin back to mi9
joe187xx said:
What firmware Were you on mi9 or mje?
Click to expand...
Click to collapse
Sorry, I'm not familiar with the difference, how could I find out? I know it was updated to 4.4.2
http://forum.xda-developers.com/showthread.php?t=2524572
It says MI9 in the firmware package. You downloaded the wrong one.
arizonakye said:
Sorry, I'm not familiar with the difference, how could I find out? I know it was updated to 4.4.2
Click to expand...
Click to collapse
Yes you were on NC2 or NC4 kit kat and you tried to put a Jellybean stock MI9 rom on that will not work you have to find the NC4 tar file and flash in odin the letter n numbers that we refer to are the the last 3 of the actual tar stock file ex MI9 - MJ7 - MJE are jellybean stock/ NC2 - NC4 are Kit kat stock. You need to NC4 stock tar file…
I have been searching threads for 6 hours, but haven't found anything conclusive.
I rooted my phone a while back, but today I decided to install a new custom ROM. I backed up the ROM to my external SD and installed the new one through safestrap. However, when I tried to reboot, I just got stuck on a screen that says samsung and has an open lock.
I am able to get into download mode, but not into recovery. After I boot into download mode, it says write protection:enabled (not sure that is normal, but I thought I would mention it). I open up Odin and the drivers seem to load fine. I have tried a a few versions of ODIN and two different Stock ROMs, but it fails every time. On my phone, after it fails, I get a message that says SW Rev. Check Fail: fused 2, binary: 1.
In ODIN, I get the following:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? I'm getting kind of desperate.
Have you tried another USB cable?.
I have actually. The original cable and just another one I had. Also, tried it on 3 computers.
Should I be loading a PIT file? some places say to do it and others say not to.
marcymtz92 said:
Should I be loading a PIT file? some places say to do it and others say not to.
Click to expand...
Click to collapse
The problem is you're trying to flash mdl firmware and you're not on that version. It looks like you're on mf3. There is no Odin flashable mf3 firmware so I'd suggest you flash the nb1 tar file. See the general forum for the file. http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
You are freaking amazing. That file totally worked. Thanks so much.
marcymtz92 said:
You are freaking amazing. That file totally worked. Thanks so much.
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 5 using XDA Free mobile app