Odin Failing When Using CF Auto Root - Galaxy S 5 Q&A, Help & Troubleshooting

Accidentally posted this in the TMO S5 board, my bad.
I've followed the super easy instructions on how to use CF Auto Root but still cannot make it all the way through the first part of the root process. It starts running fine and then stops at NAND Write Start. At one point it got past that but failed at again.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Earlier it said something about the PIT partition, but I can't seem to find a 32GB pit file for the Sprint S5 - and it's not saying that any more. I am kind of at a loss here, and now my phone won't boot at all. What else can I do?
Thanks!

Could you first please confirm is Kies installed?
Secondly could you try to change the cable and try a different USB port?
Have you booted your phone into the bootloader? Home + volume down when powering on. Take the battery out and leave it for 10 seconds and then try to boot into bootloader mode.

Related

Softbricked my GS4 (i337m), any help would be appreciated!

Hey everyone,
I believe I just softbricked my phone, I tried to restore it back to stock via ODIN but it wont work,
Here is the error message from ODIN
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And it stuck on the screen that shows "firmware upgrade encountered an issue please select recovery mode in kies and try again"
WHAT DO I DO? :crying::crying::crying::crying::crying::crying:
Try flashing this http://forum.xda-developers.com/showthread.php?p=46943588 via Odin forI337MF3......cuz the one u used is for I337MDL ....
Swyped from BlueICESense_JBE
take a look at Jamison's guide just to see if you did some steps wrong
it is mdl so don't use the fw but the steps may be similar
http://www.infamousdevelopment.com/index.php?topic=115.msg890#msg890)*

I need help!!!!!!!!!

I recently was attempting to downgrade my kernal so I could root my S5. I knew to this and I'm not sure where I messed up. My phone is stuck in a bootloop. I've tried multiple times to reset through ODIN to stack firmware. This is what it reads. Please help if you can.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1ANCG_G900VVZW1ANCG_G900VVRU1ANCG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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)
Download odin for your device, and a official samsu rom md5 for your device.
Put the original rom to your device with odin, but first enter in Download mode ( volume - with home button and power pressed in same time.)
necromisty said:
Download odin for your device, and a official samsu rom md5 for your device.
Put the original rom to your device with odin, but first enter in Download mode ( volume - with home button and power pressed in same time.)
Click to expand...
Click to collapse
I've done that, I've tried three versions of Odin and Five different versions of ROM.
Bootloader is locked, search the forum for tutorials for your model S5 (Verizon?)

Samsung SMT330NU - Odin3 issue

Looks like I could use some experienced help here. So I went to root using Odin3. I loaded up my file and everything seemed to go as expected. That is until it reset at the end. At that point it seemed to be stuck in a boot loop. I let it go for a while, but still just rebooting over and over (just Samsung splash screen). So at that point I double check things. Looks like I loaded the MD5 file for the SMT330 not smt330nu. So Is started over with the correct file and it progresses almost all the way and I get an error. Looks like this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-milletwifiue-milletwifiue-smt330nu.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried several times and I only get this far. Any alternatives here?
Murph77 said:
Looks like I could use some experienced help here.
So I went to root using Odin3. I loaded up my file and everything seemed to go as expected. That is until it reset at the end. At that point it seemed to be stuck in a boot loop. I let it go for a while, but still just rebooting over and over (just Samsung splash screen). So at that point I double check things. Looks like I loaded the MD5 file for the SMT330 not smt330nu. So Is started over with the correct file and it progresses almost all the way and I get an error. Looks like this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-milletwifiue-milletwifiue-smt330nu.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried several times and I only get this far. Any alternatives here?
Click to expand...
Click to collapse
Don't use cfauto root it gets deprecated all the time. Use this method instead (simply stated, install trwrp with Odin and immediately boot into twrp to install the latest beta SuperSU zip): http://forum.xda-developers.com/showpost.php?p=61421937&postcount=4

Cricket sgh-i337z custom recovery error

My device is already rooted from Kingoroot which worked easily and had no problems.
Now I'm trying to install custom recovery, I downloaded the newest IMG that TWRP has for my device, convert it to tar.md5, then I boot my phone into download mode and try to push the rom to my phone via Odin, and after about 3-4 seconds it says fail at the top, here is the output the Odin gives:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> twrp-2.8.4.0-jfltecri.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> twrp-2.8.4.0-jfltecri.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
It doesn't cause any errors or anything on my phone when it fails, I just restart my phone and it works just fine.
Thanks for the help, I couldn't find a similar error to mine with a solution posted previously for my device.
Try using different USB cables and USB ports.
OP resolved the issue. Thread closed.

G900F Won't boot to ROM or Recovery

This all started when I tried to flash Clockwork recovery on my stock G900F. I used Odin to successfully load the recovery, but as soon as it booted it would get stuck at "Set warranty bit: recovery" and restart itself into the ROM. So then I tried TWRP and Philz Touch and got the same thing. Then I tried to flash CF-Auto Root to see if I could use root permissions to restart into recovery via the CWM app, but that too gave me the same error. I tried both with and without Auto-Reboot on to see if maybe the stock ROM was overwriting the recovery but that didn't fix it either. This entire time USB debugging was enabled so that's not it.
Since the point of me doing this was to install CM 14.1 anyways, I decided to try flashing a stock ROM. I tried a whole bunch of different rips and none of them worked. The ones that were compressed into .tar would give the following error in Odin:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The one that was broken into four separate files gives this error:
Code:
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
For both types of rips I had both Auto-Boot and F. Reset Time on. I did once attempt to use the .pit file provided with the latter rip and attempt to re-format, but that didn't do anything except prevent my stock ROM from booting (it's now stuck at the Samsung logo). I can still boot into download mode.
What are my options from here? I'm a little disheartened that my stock phone was unable to load any of the recovery tools that I tried, but maybe I'm missing something.
I tried using the firmware linked in this thread. I tried flashing with both T-flash and repartition as well as just T-flash and it doesn't work.
I get about halfway through the download before it fails. This is the output from Odin:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> T Flash...
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> userdata.img.ext4
<ID:0/004> FAIL! (Erase)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can still boot into download mode and successfully flash any recovery I try, but I also still can't boot into recovery. Any help is greatly appreciated.
Turns out this was as simple as not having the version of the phone I thought I had.
Amazon told me it was a G900F when I bought it. The box says G900F. The sticker beneath the battery says G900F. The phone itself says G9006V.
When I searched to see if this has happened to anyone else, I saw more than a few confused and frustrated people learning this same thing the hard way as I did.
The lesson here is to trust what you see in download mode and disregard everything else. It's a bit slimy, but that's the world we live in.

Categories

Resources