Ok everyone,
I recently got a Galaxy S4 from Verizon(SCH-I545), and I was attempting to root it for the first time, using Root De La Vega (on VRUDMI1).
I connected ODIN and began to flash the .tar.md5 file, and here's what the log says:
Code:
<ID:0/006> Firmware update start..
<ID:0/006> cache.img.ext4
<ID:0/006> NAND Write Start!!
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Then I am greeted with a huge red FAIL! icon.
At this point, the only thing I can get into is download mode. Booting up, or trying to enter stock recovery leads to an error that states:
Code:
Firmware upgrade encountered an issue.
Please use Software repair assistant and try again.
The repair assistant requires the device model number, which I do not have.
Odining stock firmware returns:
Code:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I am kind of out of options here. Any suggestions?
Auth means you are using the wrong tar fille. Make sure you use the MI1 file if you took the latest update
I have a Similar Issue, but I have SafeStrap installed, and Flashed over my Origional Stock Rom on Accident -_- The Un-Rooted Rom wouldn't install, but the Rooted Rom which i found http://stockroms.net/file/GalaxyS4/SCH-i545/rooted/VRUAME7_Deodex.zip was able to be installed.
Still waiting for its first boot though, taking quite some time -_- Suck on the Verizon Logo...
My Suggestion is once you get your phone working again cause its not Bricked, you just flashed incorrectly, install SafeStrap, since it doesn't require you to unlock the bootloader, and it allows you to mess around with different ROM's while not affecting the other ROM's.
http://forum.xda-developers.com/showthread.php?t=2428226
Ablac said:
Still waiting for its first boot though, taking quite some time -_- Suck on the Verizon Logo...
http://forum.xda-developers.com/showthread.php?t=2428226
Click to expand...
Click to collapse
Did you get it to work? I made the same mistake with SafeStrap, and now I can only boot to the download screen.
I'm downloading the ROM you linked, but it will take another two hours.
EDIT:
Download finished. How do I install it? I was expecting a .tar or .md5 to use with ODIN, but the link contains a zipped .img
Did it work?
Ablac said:
I have a Similar Issue, but I have SafeStrap installed, and Flashed over my Origional Stock Rom on Accident -_- The Un-Rooted Rom wouldn't install, but the Rooted Rom which i found http://stockroms.net/file/GalaxyS4/SCH-i545/rooted/VRUAME7_Deodex.zip was able to be installed.
Still waiting for its first boot though, taking quite some time -_- Suck on the Verizon Logo...
My Suggestion is once you get your phone working again cause its not Bricked, you just flashed incorrectly, install SafeStrap, since it doesn't require you to unlock the bootloader, and it allows you to mess around with different ROM's while not affecting the other ROM's.
http://forum.xda-developers.com/showthread.php?t=2428226
Click to expand...
Click to collapse
Hello, I am also downloading this file and wondering how to install it. I cannot boot into recovery mode as I get the "firmware upgrade encountered..." message. The download page says "These are official stock ROMs that have root added and you can use CWM/TWRP to install them.", but as I said, I cannot boot there.
If this method doesn't work for my situation, is there anybody else who can point us in the right direction to the correct TAR file? At this point all I want is a working phone, I don't care if rooted or not.
Thank you everyone!
[UPDATE] I got a hold of another Galaxy S4 and I plugged it in to the computer while turned on (nothing running on either phone or computer) and when I got the [New device plugged in] notification I was asked if I wanted to install the Verizon software, I clicked on [Yes] and this began the installation of the [Software Repair Assistant]. Once it finished I unplugged the phone (as it had started to do the latest update), cancelled the update and then launched the [VZW Upgrade Assistant], switched the tab to the [Repair Assistant], plugged in the bricked phone and immediately told me that it had to repair the phone and it was so bad that it was going to wipe it entirely. Right now is "downloading software" (35%) and it will take from 60 to 90 minutes to complete.
I have to leave my house now but I will leave it running and see what happens when I come back. I will venture outside my house without a phone for the first time in over a decade... wish me luck.
[FINAL UPDATE] That did it. I have a non-rooted functional phone! Now to wait until someone comes up with a way to root it.
alexbmex1 said:
Hello, I am also downloading this file and wondering how to install it. I cannot boot into recovery mode as I get the "firmware upgrade encountered..." message. The download page says "These are official stock ROMs that have root added and you can use CWM/TWRP to install them.", but as I said, I cannot boot there.
If this method doesn't work for my situation, is there anybody else who can point us in the right direction to the correct TAR file? At this point all I want is a working phone, I don't care if rooted or not.
Thank you everyone!
[UPDATE] I got a hold of another Galaxy S4 and I plugged it in to the computer while turned on (nothing running on either phone or computer) and when I got the [New device plugged in] notification I was asked if I wanted to install the Verizon software, I clicked on [Yes] and this began the installation of the [Software Repair Assistant]. Once it finished I unplugged the phone (as it had started to do the latest update), cancelled the update and then launched the [VZW Upgrade Assistant], switched the tab to the [Repair Assistant], plugged in the bricked phone and immediately told me that it had to repair the phone and it was so bad that it was going to wipe it entirely. Right now is "downloading software" (35%) and it will take from 60 to 90 minutes to complete.
I have to leave my house now but I will leave it running and see what happens when I come back. I will venture outside my house without a phone for the first time in over a decade... wish me luck.
[FINAL UPDATE] That did it. I have a non-rooted functional phone! Now to wait until someone comes up with a way to root it.
Click to expand...
Click to collapse
Try here: http://forum.xda-developers.com/showthread.php?t=2381382
---------- Post added at 07:51 PM ---------- Previous post was at 07:44 PM ----------
dlist said:
Ok everyone,
I recently got a Galaxy S4 from Verizon(SCH-I545), and I was attempting to root it for the first time, using Root De La Vega (on VRUDMI1).
I connected ODIN and began to flash the .tar.md5 file, and here's what the log says:
Code:
<ID:0/006> Firmware update start..
<ID:0/006> cache.img.ext4
<ID:0/006> NAND Write Start!!
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Then I am greeted with a huge red FAIL! icon.
At this point, the only thing I can get into is download mode. Booting up, or trying to enter stock recovery leads to an error that states:
Code:
Firmware upgrade encountered an issue.
Please use Software repair assistant and try again.
The repair assistant requires the device model number, which I do not have.
Odining stock firmware returns:
Code:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I am kind of out of options here. Any suggestions?
Click to expand...
Click to collapse
Try the download on this thread: http://forum.xda-developers.com/showthread.php?t=2301259. I was able to use the file from to recover. There also is another thread on recovering from a soft brick.
All done
artjef said:
Try here: http://forum.xda-developers.com/showthread.php?t=2381382
---------- Post added at 07:51 PM ---------- Previous post was at 07:44 PM ----------
Try the download on this thread: http://forum.xda-developers.com/showthread.php?t=2301259. I was able to use the file from to recover. There also is another thread on recovering from a soft brick.
Click to expand...
Click to collapse
Beautiful ROOT! It is back. Thank you very much for the link. Worked like a charm.
Related
I think I really screwed up with my phone, I started off trying to root it with using a guide I found. The guide was very broad and told me to use a file called CF-Auto-Root-m0-m0xx-gti9300.tar.md5 I flashed this file using Odin 3.07. BUT I PUT IT IN THE BOOTLOADER, so that is my first major mistake, or at least I think. The phone worked, but I couldn't receive cell signal. So now I am trying to flash the factory reset that I got from sammobile. None of these seem to work. I have learned to switch to Odin 1.85, while trying to flash the different files, I get different results. When I flash CODE_19300XXEMF1_1160235_REV00_user_low_ship_tar.m d5, into the PDA it gives me the following error:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to flash the bootloader, it just says
All threads completed. (succeed 0 / failed 0)
My friend came over and tried to help me for an hour or two, but he couldn't figure out what was wrong with it. If you guys could give any help, that would be extremely appriciated right now, becuase I am on the urge of giving up.
Details about my device:
Galaxy S3, GT-I9300 international edition.
I'm on AT&T in the united states.
I'm really new to xda, and all this, but if there is any reward system for helping me, I'll be sure to make sure you are treated well.
Please Help,
AnorexicFatman
As the title states, I am currently trying to flash my phone back to stock to fix a soft brick. I was trying to get the latest update since I was on a custom ROM and couldn't get the OTA. I got the firmware from Sammobile, from what I understand to be a reputable place to get them. The flash in Odin seemed to go normally until it had the phone restart, It is now is a loop of flashing the "Galaxy Note II" screen. And I had CWM installed, but I cannot get to the recovery with it in this loop.
Yes, I have read the sticky before posting this. I am doing the only recommended thing I can find to do for this sort problem, flash it back to stock. I have the stock firmware, directly from the link in the sticky, and when I go to start it on Odin this is what I get:
<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> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there something I'm missing/doing wrong? I have installed a few ROMs before, but I am fairly new to using Odin and flashing the firmware.
I would greatly appreciate any help with this
Thank you!
Hi,
Hope you used pit file in odin along with rom file. Also, do a factory reset after successful odin.
Thanks,
Nikhil Dhand
Chat: [email protected]
Sent from my SCH-I605 using XDA Premium 4 mobile app
nikhil.kdhand said:
Hi,
Hope you used pit file in odin along with rom file. Also, do a factory reset after successful odin.
Thanks,
Nikhil Dhand
Chat: [email protected]
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, I believe that was the problem. I didn't know it needed the PIT for this.
The phone lives again, but it's strange. The flash was almost done, got to the sboot, and failed. My phone had "unsupported version" in red on the Odin screen. I rebooted the phone, it went to the android update screen, and now it is working like it did before all this.
Now the question is, why did the 4.3 firmware send it into a boot loop? Is the file on Sammobile the right one? Would it be better to just get my phone back to stock with a stock recovery, and get the update OTA?
It is possible that the usb port I used was bad, I seriously need to remember not to use the front ports for something like this...
I need to read up more on this so I don't screw it up next time.
SFBob9 said:
Now the question is, why did the 4.3 firmware send it into a boot loop? Is the file on Sammobile the right one? Would it be better to just get my phone back to stock with a stock recovery, and get the update OTA?
Click to expand...
Click to collapse
It is important to note that if you take the OTA, it WILL relock your bootloader. This means no custom recovery and no custom ROMs.
Ok so i rooted my phone a bit back but i keep getting firmware upgrade notifications so i just wanted to unroot and be vanilla firmware. well i tried with Odin and it didnt work so im stuck in Odin mode and i cant get back to using the phone. Please HELP!
Here is my guide.
http://www.androidfilehost.com/?fid=23501681358538464
This does not seem to be working...
Did you download the pdf?
Sent from my SCH-I545 using XDA Free mobile app
techguy2002 said:
Did you download the pdf?
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Yes i read at it and did what it said. Instructions werent super clear. Is that for the ME7?
not for ME7 but how to get from nc5 to mk2 and back rooted to nc5. I dont know how you would get back to ME7. I saw the post and made the comment and couldnt delete it.
@Radllik
There is no reason to open two threads on the same subject. This thread since it has replies has been moved to the Q&A section where all questions and request for assistance belong.
Your other thread will be locked, please pay attention to the rules in the future.
EFM
Have a great day!
Same, stuck in odin/download mode
I tried to upgrade via kies and it crashed at 80% (i don't know how). Now i'm stuck in download mode too. Mine is ME7. Can someone please tell me what to do, i downloaded the whole internet in the past 2 days just to get it working again the message i get from odin is the following:
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I'm pretty sure you couldn't reinstall me7 as its no longer signed? Might want to look for full wipe tars for Odin and try that.
Sent from my SCH-I545 using XDA Free mobile app
Vidanl said:
I tried to upgrade via kies and it crashed at 80% (i don't know how). Now i'm stuck in download mode too. Mine is ME7. Can someone please tell me what to do, i downloaded the whole internet in the past 2 days just to get it working again the message i get from odin is the following:
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
First, techguy2002: Please stop recommending this when you don't know what state people are in. You WILL cause people to brick their phones. I know you're trying to be helpful, but your instructions apply to MK2 only.
OK, so OP is on ME7. What did you try to flash, specifically what image? What showed up on the phone when the flash failed?
You should start with trying to flash the ME7 image from here.
Then, if that fails, post the full errors from ODIN and the phone.
k1mu said:
First, techguy2002: Please stop recommending this when you don't know what state people are in. You WILL cause people to brick their phones. I know you're trying to be helpful, but your instructions apply to MK2 only.
OK, so OP is on ME7. What did you try to flash, specifically what image? What showed up on the phone when the flash failed?
You should start with trying to flash the ME7 image from here.
Then, if that fails, post the full errors from ODIN and the phone.
Click to expand...
Click to collapse
That link does not work on the page you sent. Also i live in Michigan.
the link isn't working
k1mu said:
First, techguy2002: Please stop recommending this when you don't know what state people are in. You WILL cause people to brick their phones. I know you're trying to be helpful, but your instructions apply to MK2 only.
OK, so OP is on ME7. What did you try to flash, specifically what image? What showed up on the phone when the flash failed?
You should start with trying to flash the ME7 image from here.
Then, if that fails, post the full errors from ODIN and the phone.
Click to expand...
Click to collapse
Hey, the link isn;t working and i already tried the ME7... so it wont work. I can't get it to recovery mode also, so the only thing that works is the Download mode so please someone who had a simmilar problem, let me know how to fix this (step by step of course ) thanks
Vidanl said:
Hey, the link isn;t working and i already tried the ME7... so it wont work. I can't get it to recovery mode also, so the only thing that works is the Download mode so please someone who had a simmilar problem, let me know how to fix this (step by step of course ) thanks
Click to expand...
Click to collapse
When you say "it won't work", what do you mean? What image did you try, what errors appeared in ODIN and on the phone?
Worst case, you could try flashing a newer ROM image, for example MI1, MJ7, or MK2.
they wont pass in odin
k1mu said:
When you say "it won't work", what do you mean? What image did you try, what errors appeared in ODIN and on the phone?
Worst case, you could try flashing a newer ROM image, for example MI1, MJ7, or MK2.
Click to expand...
Click to collapse
None of those images seem to "pass" in odin. i always get the quoted message and i get binary error. :S The thing is, even the recovery mode isnt working, the only thing that works is the download mode.
Vidanl said:
None of those images seem to "pass" in odin. i always get the quoted message and i get binary error. :S The thing is, even the recovery mode isnt working, the only thing that works is the download mode.
Click to expand...
Click to collapse
We can't help you without more information. For example, the following:
1. What build was your phone on when you started?
2. What file are you trying to flash? What build is it?
3. Did you verify the MD5 of the download prior to trying to flash it?
4. What shows up in ODIN when you try to flash it?
5. What shows up ON YOUR PHONE when you try to flash it? Without knowing that, there's no way to guess what's failing.
What you're saying sounds like either you're trying to flash an incompatible image (i.e. trying to flash MDK on a ME2 phone), or you've got a bad network connection that's corrupting your downloads. Having the full set of diagnostic information will help figure out which.
got it working
k1mu said:
We can't help you without more information. For example, the following:
1. What build was your phone on when you started?
2. What file are you trying to flash? What build is it?
3. Did you verify the MD5 of the download prior to trying to flash it?
4. What shows up in ODIN when you try to flash it?
5. What shows up ON YOUR PHONE when you try to flash it? Without knowing that, there's no way to guess what's failing.
What you're saying sounds like either you're trying to flash an incompatible image (i.e. trying to flash MDK on a ME2 phone), or you've got a bad network connection that's corrupting your downloads. Having the full set of diagnostic information will help figure out which.
Click to expand...
Click to collapse
I found a pit file for 16gb version, just used the pit file in odin... then i tried to install MJ7, it didn't work, and after that all of a sudden it booted and asked me to setup my phone i really don't know how it happened. thanks for the support guys
Same exact problem!
Vidanl said:
I found a pit file for 16gb version, just used the pit file in odin... then i tried to install MJ7, it didn't work, and after that all of a sudden it booted and asked me to setup my phone i really don't know how it happened. thanks for the support guys
Click to expand...
Click to collapse
Totally softbricked my cousin's phone the exact same way. Could you post a link for that PIT file? I'd like to try the method that you tried to get this working again. Thanks.
cashmoneysalad said:
Totally softbricked my cousin's phone the exact same way. Could you post a link for that PIT file? I'd like to try the method that you tried to get this working again. Thanks.
Click to expand...
Click to collapse
Verizon S4 16Gb PIT can be downloaded from here http://www.androidfilehost.com/?fid=23269279319199111
Sent from my SCH-I545 using Tapatalk
Okay, I popped the PIT in there and tried to flash Verizon MJ7. Got a fail. Here's the details.
Odin is reading:
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.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> 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)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone reads:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
START [224, 1440]
SW REV. CHECK FAIL : fused : 6 , Binary: 5
Any ideas here, guys? I'd really like to fix this for my cousin. It's frustrating because I know it's only soft-bricked but no remedy I have tried thus far has worked.
cashmoneysalad said:
Okay, I popped the PIT in there and tried to flash Verizon MJ7. Got a fail. Here's the details.
Odin is reading:
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.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> 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)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone reads:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
START [224, 1440]
SW REV. CHECK FAIL : fused : 6 , Binary: 5
Any ideas here, guys? I'd really like to fix this for my cousin. It's frustrating because I know it's only soft-bricked but no remedy I have tried thus far has worked.
Click to expand...
Click to collapse
Fused:6 - your phone has the NC5 bootloader.
Binary:5 but you're trying to flash MJ7/MK2.
At this point you can follow Surge1223's directions to back down to MK2 then upgrade to NC5 rooted. http://forum.xda-developers.com/showthread.php?t=2726868
Or, do the same thing using techguy2002's directions: http://forum.xda-developers.com/showthread.php?t=2763834
Hello!
I'm attempting to root my S4 and eventually flash it with a custom ROM. However, I'm having a lot of trouble getting it to root. I'm using an online guide which flashes another kernel (NC5) using Odin then roots using towelroot and finally flashing back to my original kernel (NK1). The problem is that when I originally try to flash the NC5 kernel using Odin, I get an error. I've tried looking online for a solution but have found nothing so hopefully someone on here can assist me.
I'm running 4.4.2 on a SCH-I545VRUFNK1 and using Odin v3.09 but have also tried v3.04 to no avail. I've taken the battery out and waited 10 minutes, but that didn't work. Here is the output from Odin:
<ID:0/004> Added!!
<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> boot.img
<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)
<ID:0/004> Removed!!
Thank you to all in advance!
Niotic said:
Hello!
I'm attempting to root my S4 and eventually flash it with a custom ROM. However, I'm having a lot of trouble getting it to root. I'm using an online guide which flashes another kernel (NC5) using Odin then roots using towelroot and finally flashing back to my original kernel (NK1). The problem is that when I originally try to flash the NC5 kernel using Odin, I get an error. I've tried looking online for a solution but have found nothing so hopefully someone on here can assist me.
I'm running 4.4.2 on a SCH-I545VRUFNK1 and using Odin v3.09 but have also tried v3.04 to no avail. I've taken the battery out and waited 10 minutes, but that didn't work. Here is the output from Odin:
<ID:0/004> Added!!
<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> boot.img
<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)
<ID:0/004> Removed!!
Thank you to all in advance!
Click to expand...
Click to collapse
Have you tried using a different USB cable? Sometimes I have had this happen, I switched cables and it worked fine after, but this may not be your specific issue.
---------- Post added at 12:35 PM ---------- Previous post was at 12:32 PM ----------
Also, are you using the Kernel or full image? Look at file size as the Kernel is fairly small compared.
Yea, I did try that! I tried it with two different cables and two different USB ports but didn't change anything unfortunately.
Niotic said:
Yea, I did try that! I tried it with two different cables and two different USB ports but didn't change anything unfortunately.
Click to expand...
Click to collapse
I would say maybe try another PC if available.
What if there isn't another pc available?
What is the file size of the image you are trying to flash?
Flash a stock nc5 image, then use towelroot. Odin may not be liking the image... Also, sometimes the phone has to be flat. That helps me A LOT in my constant Odin Flashes.
XxD34THxX said:
Flash a stock nc5 image, then use towelroot. Odin may not be liking the image... Also, sometimes the phone has to be flat. That helps me A LOT in my constant Odin Flashes.
Click to expand...
Click to collapse
Can't flash a stock image of NC5 as he is on NK1. He CAN flash the NC5 kernel, use towelroot to root, and then flash the NK1 kernel again.
I had this same problem. I am pretty sure I had the phone flat on my table instead of on my PC... That didn't help in your case... Use Odin 3.07
The file size is 8,691 KB. And this is exactly what I am trying to do! Flash the NK1 Kernel then use towel root then flash back to my original kernel of NC5. I'll try to use Odin 3.07 and let y'all know how it goes.
I apologize for the delayed response, it's the end of the school year and things are getting pretty hectic. Please be patient with me!
Niotic said:
The file size is 8,691 KB. And this is exactly what I am trying to do! Flash the NK1 Kernel then use towel root then flash back to my original kernel of NC5. I'll try to use Odin 3.07 and let y'all know how it goes.
I apologize for the delayed response, it's the end of the school year and things are getting pretty hectic. Please be patient with me!
Click to expand...
Click to collapse
Just tried Odin 3.07 with no luck, my phone is flat and I tried two different USB ports with two different chords. What's my next option?
Niotic said:
The file size is 8,691 KB. And this is exactly what I am trying to do! Flash the NK1 Kernel then use towel root then flash back to my original kernel of NC5. I'll try to use Odin 3.07 and let y'all know how it goes.
I apologize for the delayed response, it's the end of the school year and things are getting pretty hectic. Please be patient with me!
Click to expand...
Click to collapse
Its no problem man. I actually jump on XDA when I am at work, in between selling phones and monthly renewals. I recently had the same issue and changing my cable solved it for me.
Thanks for understanding! Yea I've tried two different cables as stated before but no luck. I'm starting to get the feeling this root isn't going to work -_-
Niotic said:
Thanks for understanding! Yea I've tried two different cables as stated before but no luck. I'm starting to get the feeling this root isn't going to work -_-
Click to expand...
Click to collapse
What, if you don't mind my asking, do you use root for?
Sent from my SCH-I545 using XDA Free mobile app
Well recently my battery life has been atrocious to say the least so I was hoping on using a root to improve that further controlling the resources that some apps use even while not in use. For example facebook is constantly pulling a massive amount of resources which I believe is partially related to my bad battery life.
I also am a bit obsessed with my UI and love changing it around in order to get better funtionality as well as increasing it's visual appel. I feel that touchwiz is ugly and would like to flash something over it in order to get rid of it and allow further customization of my UI.
Have you tried unchecking Auto Reboot in Odin options?
Another way, I've got this rooting problem on my Samsung E5:
...
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Luckily I found a thread in AndroidForums (I can't post the link here because of XDA's rules). Not totally the same but I think it could help. Belong to it, maybe your reactivation lock is on. Turn it off (Menu > Settings > General > Security > Reactivation lock, uncheck) and retry.
Thanks for the suggestion zhaona; unfortunately, it did not work. Does anyone else have some suggestions?
So I was given this phone that is stuck in download mode and am having quite a few problems getting it flashed with odin.... it seems to fail every time. not sure on the original android version it was rooted on .. The only information I was given is that it was rooted at one point and then they did a factory wipe getting it stuck in download mode... Seeing as Im new to this whole scene any help would be much appriciated
Tried 3 different firmwares from a post here
and also tried to get kies to recognize the phone .. It will not ,It is stuck at connecting
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Update:
On download screen : sw rev check fail....
If i have to choose a certain version of the firmware is there anyway to check the version I need without having to turn on the phone?
Does the sw rev check fail error mention a fuse and or binary with a number next to it?
Matthew M. said:
Does the sw rev check fail error mention a fuse and or binary with a number next to it?
Click to expand...
Click to collapse
fuse 0 binary 5
So .. I got the phone working by doing a firmware upgrade or initialization in kies, So I suppose It is fixed now .. I would still like to know what the problem could be using odin? I tried 5 different firmware upgrades from oldest to newest and couldnt get it to work. It is still kinda vexxing me, im sure I was doing somthing wrong . Any extra insight would be helpful to avoid this headache in the future?
You should go back to kies and see what version it flashed. That way if this ever happens again you can download that version and flash it through odin
Deleted
Serioussamuel said:
So .. I got the phone working by doing a firmware upgrade or initialization in kies, So I suppose It is fixed now .. I would still like to know what the problem could be using odin? I tried 5 different firmware upgrades from oldest to newest and couldnt get it to work. It is still kinda vexxing me, im sure I was doing somthing wrong . Any extra insight would be helpful to avoid this headache in the future?
Click to expand...
Click to collapse
Can you explain how you did this? I am running into a similar problem and neither a firmware upgrade nor a kies initialization is working.
Same problem here, I also don't know what my phone bootloader or firmware, I'm also stock in download mode...hope someone can answer and help us...