I currntly have a samsung galaxy s5 sm-g900i. And want to root it. I have followed the guides on these forums using odin and the appropriate md5 file. I have installed kies After rebooting my phone into download mode, connect to odin 3.07 and attempting to start it and get the following error.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-klte-kltedv-smg900i.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Related
Hello,
I'm trying to flash stock rom for my Galaxy S4 through Odin v3.07, but whenever I try to flash it I get the following error:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Can anybody help me or tell me what I'm doing wrong.
Thanks in advance!
<ID:0/006> 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/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> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I have tried with ODIN versions: 3.07, 3.09, 3.04 - i have red several guides. I have rooted many phones starting from iPhone 3G to several samsungs. It seems that it has some kind of write protection.
Android version: 4.4.2
Baseband N9005XXUENC2
Build number KOT49H:N9005XXUEND3
SE for Andoird status SEPF_SM-n9005_4.4.2_001
Any ideas?
I had this problem once.. I tried other stock rom with proper csc pda and modem in different files
Sent from my GT-I9300 using XDA Premium 4 mobile app
estrooter said:
<ID:0/006> 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/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> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I have tried with ODIN versions: 3.07, 3.09, 3.04 - i have red several guides. I have rooted many phones starting from iPhone 3G to several samsungs. It seems that it has some kind of write protection.
Android version: 4.4.2
Baseband N9005XXUENC2
Build number KOT49H:N9005XXUEND3
SE for Andoird status SEPF_SM-n9005_4.4.2_001
Any ideas?
Click to expand...
Click to collapse
Have you tried flashing with the official firmwares on SamMobile? http://www.sammobile.com/firmwares/
This may be a bad firmware file.
hello
my problem is when i flash a stock rom by odin it's stack on sboot.bin
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUGNH2_I9500OJVFNG1_I9500XXUGNF6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> __XmitData_Read ..
<ID:0/006> XmitData Fail..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
i tried many roms and many odin and i try to use another pc but it's the same problem
so what i will do now
my phone is galaxy s4 i9500 i'm using a custom rom miui v5
---------------------------------------
| finally it's solved ) thank u |
---------------------------------------
how fixed??
but how?? was that because of secure boot????
Hi, I have a galaxy S4 telus i337m, and back over a year ago I flashed a new ROM which worked fine. I decided I wanted to upgrade to 4.4.2 stock firmware so I downloaded the following firmware: http://www.sammobile.com/firmwares/download/36274/I337MVLUFNI2_I337MOYAFNI2_TLS.zip/
I downloaded Odin and tried to flash this stock firmware but Odin always gives me a partition error, and now I cant even boot my phone back up to its old firmware. Any help?
This is my error as it sits now:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUFNI2_I337MOYAFNI2_I337MVLUFNI2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
Solved my issue if anyone has the same problem. Use USB 2.0 ports not 3.0
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.