Database Users

Only will boot into downloading mode

I've got a sprint galaxy s4, was running 4.2.2 and I had added the hotspot mod by overwriting some files to make that happen. I was attempting to go back to stock in order to update to 4.3 via an Odin3 flash and something happened. I can only boot into the download mode, I can't get into recovery mode at all. If I try to get into recovery, I get the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
Kies will not recognize my phone. When I plug it into my computer via usb, I hear a notification. Kies attempts to connect, but never does successfully. I have no way of getting my serial number as I can't boot it and it's not listed under the battery cover. I have tried uninstalling/reinstalling drivers with no success. I have tried to uninstall Kies completely and flash via Odin3 but get a failure below
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMF9_L720SPTAMF9_L720VPUAMF9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
Also tried again and got these messages
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMF9_L720SPTAMF9_L720VPUAMF9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Removed!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I hope I've provided info on what I have tried. I am not an expert by any means, but would really appreciate any help. At this point I'm looking to just get back to stock and have a usable phone. I don't care about losing any info and am willing to wipe/flash whatever I can. Thank you for any input! I'm hoping to not have to take this to the sprint store

You just have to odin the stock mf9 tar again. I would try a different version of odin, a different usb port, or a different usb cable. Odin will fix your problem, don't use kies. I used odin 3 version 3.07 but I've also had a lot of success with odin 3 ver 1.85 that is included when you download cf autoroot. Also, make sure you are running odin as administrator.

cruise350 said:
You just have to odin the stock mf9 tar again. I would try a different version of odin, a different usb port, or a different usb cable. Odin will fix your problem, don't use kies. I used odin 3 version 3.07 but I've also had a lot of success with odin 3 ver 1.85 that is included when you download cf autoroot. Also, make sure you are running odin as administrator.
Click to expand...
Click to collapse
Thanks for your reply. I am trying to flash the stock .tar but I'm not having any success. I get the error messages I listed above. Any clue what those mean or what I could be doing wrong? That looks like greek to me. I really don't know what any of it means.

i would just use the CF-autoroot odin......this has saved my ass twice !!! seems to be the " mirical odin " program

chris-allen said:
i would just use the CF-autoroot odin......this has saved my ass twice !!! seems to be the " mirical odin " program
Click to expand...
Click to collapse
wow. Finally figured it out. I tried 3 different USB ports, none of those worked. Tried a 4th on the back of my PC and viola, finally got Odin to work. THanks for your help!

[Q] Failure rooting galaxy s5 SM-G900F

Hi
Hoping someone can help me I have followed the guide to root my s5 device exactly several times and it fails everytime. USB Debugging is enabled, USB Drivers are installed and Kies isnt installed on my pc, this is guide i followed:
Step 1: Download CF-Auto-Root package and Odin v3.09. Then, extract the files to the computer.
Step 2: Boot the Galaxy S5 in Download mode by pressing and holding down the Volume Down, Home and Power buttons together. When a warning screen is displayed, press the Volume Up button to enter Download mode.
Step 3: Now, run Odin3 v3.09.exe as an Administrator and then connect the Galaxy S5 to the PC via USB cable. If connected successfully, a message showing “Added!!” will appear in Odin’s message box, if not, try another USB port. If the issue persists, try reinstalling the USB driver.
Step 4: Click on the AP button, and select the CF-Auto-Root file (a .tar.md5 file), which was extracted in Step 1.
Step 5: In Odin, make sure that the “Auto Reboot” and “F. Reset Time” options are checked while “repartition” is unchecked.
Step 6: Click on the Start button in Odin to begin the flashing process.
Step 7: After the process is complete, the Galaxy S5 will restart and a PASS message with green background will appear in the left-most box at the top of Odin.
I have tried this 5 times and it isnt working fails every time any ideas why this isnt working. I am not an expert at this so if I missed anything please let me know any help would be great
Here is log from odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-klte-kltexx-smg900f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.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)
Thanks

Try again with Odin 3.7

No, stick with Odin 3.09.
Odin is tempermental, sensitive to timing and USB configurations. Try a different USB cable and USB port. And ensure that you have temporarily turned off any firewall, antivirus or malware scanning programs. If the problem persists, try reverting to a full stock firmware to eliminate a lot of variables and have a stable OS before proceeding to root your phone.
At face value, the Odin error message implies that your recovery partition is corrupt. That could mean that you are trying to reroot a phone that has already been rooted, that your root was incomplete or that you had a bad Odin write, that Knox is interfering or any number of other causes. You could reduce the variables even more by writing the proper PIT file to your phone concurrently with a flash to stock firmware. Do try a different USB cable and USB port.
And critically, ensure that you are entering download mode by removing the phone battery, replacing it, then using the volume down + home + power sequence. If the first write attempt fails, do not close the Odin screen. Instead pull the battery again, then enter download mode again and then click write for the second attempt. Ensure that you don't close the Odin screen between the two write attempts.
.

Got this resolved turned out reactivation lock was enabled in security settings turned this off and root was successful after this, thanks for the help tho

galaxy s5 root
Hi
I installed android 5.0 lollipop on my galaxy s5 ( SM-G900F ) since there i am trying to root my phone in order to delete all pre loaded apps that i don't use
But every time i try i fail,
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-klte-kltexx-smg900f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I already reed the last few posts but i still don't understand how to root my phone

tiagooliveira95 said:
I already reed the last few posts but i still don't understand how to root my phone
Click to expand...
Click to collapse
Have you tried Towelroot? I thought that worked for all of the S5 phones...

Hi
I was having the same problem as you.
Just tried this option: http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044
Just give it a try...

hey
can u give me a link with thath problem I have it to

graemek said:
got this resolved turned out reactivation lock was enabled in security settings turned this off and root was successful after this, thanks for the help tho
Click to expand...
Click to collapse
omg you hero

Root Turkish Note 3

Hey guys, I tried rooting my Turkish Note 3 (international 32gb) SM-N9000Q. Yet, I got this exact same error in Odin http://forum.xda-developers.com/galaxy-note-3/help/sm-n900-root-stuck-cache-img-t2826737
if you don't want to click;
Hello, i have stuck in cache.img.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-ha3g-ha3gxx-smn900.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS.. <ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> cache.img
I already following few tutorial in past posts that told you to unplug the USB and try another USB Plug. i already tried all of my 3 usb plugs, even change to another laptop. still always stuck in cache.img
My steps :
Activate USB Debugging, make sure Kies is not running on my PC -> Turn on Odin3 v3.07 -> Plug my phone in Download mode -> Odin detects my device with blue box -> tick the PDA, Auto-Reboot, F. Reset Time -> Then it stucks.
After i reboot my phone, now it said i have encountered an error firmware upgrade, which means i can't get in to my phone again. But i can still enter Recovery / Download mode.
I have tried using Kies 3 to firmware recovery mode but its not detecting my device (nothing appears on the white box of emergency mode).
P.S.: My phone model is SM-N900
Click to expand...
Click to collapse
I downloaded the stock firmware and restored it thankfully using sams, however I still want/need to root my phone. How can I do it?! Any help would be awesome!

S4 GT-I9506 is stuck on Firmware upgrade encountered an issue

this model seems difficult (gt-i9506)
i tried to root it via towelroot, then kingoroot, these failed but then now the reboot is stuck on "firmware upgrade encountered an issue"
ive tried Kies firmware recovery but the download fails after 80%,
ive tried the sammobile download the ROM this too fails, network drops out tried this 3 times
i want to try Kies emergency recovery but cant find any recovery code
im stuck i dont know what to do now been researching for 4 hours cant find solution :crying:

could anyone please help?? am going crazy over this spent 2 days researching and finding nothing

Download a complete stock rom and flash it with ODIN. You have to uninstall KIES beforehand (they are conflicting).

thanks for reply...
i took kies off and this is what Odin is giving me...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUAMHF_I9506VAUAMH3_I9506XXUAMHD_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
the device says this.....
SW REV CHECK FAIL: [aboot]Fused 1 > Binary0
does this highlight anything that could be going wrong?

Not sure... but looks like the rom is not for that device. Are you sure you have a i9506?

on samsmobile GT-I9506/VAU/ Roms (i cant post link)
well the first ROM was 4.2 android (bottom of ROM list), so then tried 4.4 (top of ROM list) android it failed again but with different Odin errors...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUCNJ1_I9506VAUCNJ1_I9506XXUCNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
can anyone see the fault here...?? no error came up on the device, only on Odin this time

Did you restart after KIES de-installation? Was USB driver successfully missing (so you had to install one manually for ODIN)? If not, you probably still have drivers/files running from KIES.
Otherwise, try a different computer to double check its not the system.

If you originally updated to Android 4.4.x or later on this device, you cannot install 4.3.x or lower as Knox within the bootloader will actively prevent Odin from functioning. As to Odin, make sure you're using the original cable, are not using a hub, have Kies disabled or uninstalled, and use a different USB port. Odin sometimes is picky about the ports it uses.
If you can get the ROM issue resolved, use CF-Autoroot to root, keeping in mind that you will trip the Knox flag in doing so. Towelroot and other one-click root methods don't work on your device.

FIXED IT!!!!!!! :laugh::silly::good::cyclops:
Moved all operations to a different PC running XP with no kies on it
The error still occurred "write fail"
So instead i tried Odin 3.09 instead of 3.07 but most of all i changed usb cables, found an original cable off my mates Nokia
then boom!!! she starting writing!!!
Thankyou so much you legends, you are now my best friends forever!!!
Strangely the new flash, all my old previous data & apps are still on there??? somehow the network is not locked either which i was fearing being a vodafone ROM
still want to root it though

Flashing a ROM through Odin doesn't wipe the data partition, which is why your apps are untouched.

Asking again for some help! I've spent 30 - 40 hours on this and getting nowhere :(

I've searched the heck outta this - and tried everything. I simply don't understand why I am getting nowhere. There is some fundamental thing I must be doing wrong but I don't know what.. I am sure that minds superior to mine can fix this.... I just need someone to take pity on me....
The phone is a SM-N900W8 (Bell Canada) that was completely stock running Android 5. After a battery pull, I got Set Warranty Bit : kernel error. Or if I try to get to recovery I get Set warranty Bit : recovery. I 'should' be able to flash stock ROM and fix, correct? Well, flashing stock ROM does not work. I tried flashing a TWRP too. Nothing. I tried flashing just a recovery or a boot, even tried flashing a N900T version (I read that works on my model too). I've tried latest Odin (3.13) or earlier versions (esp. 3.09, or 3.10). Nothing. It shows a pass in ODIN, but it's still not getting past these warranty bit errors. I can not get to any recovery...
The phone remains undaunted by my feeble attempts.
I'm using the original Samsung USB cable, attached to my motherboard ports (tried different ones too) and the ODIN downloads appear to load (I get the blue bar that increases across the screen). It reboots and then we're back to the error.
I have NOT tried ticking the re-partition box - is that the way to go? Isn't there a pit file contained in the stock ROM?
Should I be trying to flash using an image on the SD card?
Help me Obi-wan....

Here's a fix to where you are
I have exact same model and was where you are
Step 1 remove battery
Step 2 hold home button power button volume button
Step 3 continue holding all 3 buttons and put battery back in voila you get to recovery

Eastcoastguido said:
I have exact same model and was where you are
Step 1 remove battery
Step 2 hold home button power button volume button
Step 3 continue holding all 3 buttons and put battery back in voila you get to recovery
Click to expand...
Click to collapse
Thanks for the reply. I have tried what you suggest - device will not boot into recovery. It says Recovery booting at top of screen followed by Set Warranty Bit: recovery....

askelly35 said:
Thanks for the reply. I have tried what you suggest - device will not boot into recovery. It says Recovery booting at top of screen followed by Set Warranty Bit: recovery....
Click to expand...
Click to collapse
Try this :
- Turn off the phone.
- Enter Download mode.
- At the first download mode screen where it says you can press Volume-down to boot normally, press volume-down to boot normally.

Does Odin show any error message ??

JJEgan said:
Does Odin show any error message ??
Click to expand...
Click to collapse
ODIN shows a pass...
<ID:0/005> 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..
<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/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 2303 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> modem.bin
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> cache.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

I have now read about a eMMC Chip failure issue... maybe this is the problem?

That tends to read in Odin as Nand Write Fail .

Did it successfully flash twrp?

audit13 said:
Did it successfully flash twrp?
Click to expand...
Click to collapse
No it did not.
I have not tried to re-partition (the box has not been ticked in ODIN) - would that be something worth trying?

No not without be 100% prepared for dead phone.
Repartition you really need to know what you are doing with PIT etc.

askelly35 said:
No it did not.
I have not tried to re-partition (the box has not been ticked in ODIN) - would that be something worth trying?
Click to expand...
Click to collapse
What is the Odin error in the log window when you try to flash Odin?
You are flashing the latest stock ROM from sammobile.com in Odin?

audit13 said:
What is the Odin error in the log window when you try to flash Odin?
You are flashing the latest stock ROM from sammobile.com in Odin?
Click to expand...
Click to collapse
There was no ODIN error - it said "pass".
I was using the latest stock ROM from sammobile.com (bell Canada version for Ontario).

Try flashing again with a pit file. Without a pit file, you won't be able to re-partition.