Database Users

[Q] Bricked ET4G, unable to Odin back to life

Well, it seems I may have stepped in some deep doo doo, and would appreciate any help. I walked into a movie theater, my SG2 was running Calkulin's final ICS ROM. Other than the yellow triangle on the initial Samsung logo screen (early launch days rooting method), the phone was working fine. It had plenty of juice, I checked messages, silenced it, and put it in my pocket. When I took the phone out after the flick, it had powered down. I don't know why. I took it home and plugged it in, but it still had plenty of juice (the power off charging screen with the animated battery works fine). Since then, powering up freezes at the initial start-up screen (Samsung logo/triangle), never making it to the boot animation.
I cannot boot into recovery (power + volume up), but I can get into Download/Odin mode (volume down). I tried to Odin One Click back to EL29. Odin found the phone and a COM Port, and I clicked Start. Odin set up the connection, got the PIT, initialized, got through "<ID:0/012>Firmware update start..", then froze at "<ID0/012> recovery.bin", and has been stuck there ever since, at least half an hour. I don't want to disconnect in the middle of an Odin session for fear of permanently bricking the phone, though at this point it may already be a done deal.
Can anyone please offer any suggestions, help, or [insert trumpet fanfare here] even a solution? Hopeful thanks in advance.

uminchu said:
Well, it seems I may have stepped in some deep doo doo, and would appreciate any help. I walked into a movie theater, my SG2 was running Calkulin's final ICS ROM. Other than the yellow triangle on the initial Samsung logo screen (early launch days rooting method), the phone was working fine. It had plenty of juice, I checked messages, silenced it, and put it in my pocket. When I took the phone out after the flick, it had powered down. I don't know why. I took it home and plugged it in, but it still had plenty of juice (the power off charging screen with the animated battery works fine). Since then, powering up freezes at the initial start-up screen (Samsung logo/triangle), never making it to the boot animation.
I cannot boot into recovery (power + volume up), but I can get into Download/Odin mode (volume down). I tried to Odin One Click back to EL29. Odin found the phone and a COM Port, and I clicked Start. Odin set up the connection, got the PIT, initialized, got through "<ID:0/012>Firmware update start..", then froze at "<ID0/012> recovery.bin", and has been stuck there ever since, at least half an hour. I don't want to disconnect in the middle of an Odin session for fear of permanently bricking the phone, though at this point it may already be a done deal.
Can anyone please offer any suggestions, help, or [insert trumpet fanfare here] even a solution? Hopeful thanks in advance.
Click to expand...
Click to collapse
You got the S4 forum by mistake. But it is ok to pull the phone. I would pull the battery and let it sit for about an hour. Replace the USB cable, even if it has worked 1000 times. Power it back into download mode after an hour and try to Odin again.

crawrj said:
You got the S4 forum by mistake. But it is ok to pull the phone. I would pull the battery and let it sit for about an hour. Replace the USB cable, even if it has worked 1000 times. Power it back into download mode after an hour and try to Odin again.
Click to expand...
Click to collapse
Sorry about the forum goof, hopefully a mod will move this thread to the ET4G forum. Thank you for the suggestion, will try it verbatim.

premium

crawrj said:
You got the S4 forum by mistake. But it is ok to pull the phone. I would pull the battery and let it sit for about an hour. Replace the USB cable, even if it has worked 1000 times. Power it back into download mode after an hour and try to Odin again.
Click to expand...
Click to collapse
Swapped the cable, same result.
McLelle said:
premium
Click to expand...
Click to collapse
Pardon?

uminchu said:
Swapped the cable, same result.
Pardon?
Click to expand...
Click to collapse
Only other thing I can think of is to varify the md5 on the file you have to make sure it isn't corrupt. And to either reinstall the drivers or try a different computer.

Two possible solutions:
1. Odin the full firmware. Obviously you would lose data, but at least your phone wouldn't be a paperweight. GB27 was the latest i think.
2. Get an S4. You already posted in the forum, might as well just get the phone now. HAH!

ACoolGuy said:
Two possible solutions:
1. Odin the full firmware. Obviously you would lose data, but at least your phone wouldn't be a paperweight. GB27 was the latest i think.
2. Get an S4. You already posted in the forum, might as well just get the phone now. HAH!
Click to expand...
Click to collapse
Good call, hopefully, both 1 and 2 apply.
I'm still trying to restore the GS2, if nothing else for the learning experience. If I'm able to restore it, should someone else happen to fall into (or is that out of?) the same boat, maybe I can help out. Then maybe sell, loan or donate it down the line.
I wasn't eligible for an upgrade until mid-July. After several failed attempts to restore the phone, I called customer care and explained (omitting anything about rooting or custom ROMs) that I had a dead phone and was pretty much up a tree. Sprint was pretty cool about resetting my date 2 months early without nailing me with a prorated ETF. I picked up an S4, now running Force 1.0. Other than a couple of WTF aspects, I like the phone. IMO, Sprint really needs to sell a 32 or 64gb option. 16gb only gets you 9~gb useable space for apps and pics with no apps2SD capability. Here's hoping the devs can work something out for that in ROMs to come.
Thanks for your suggestion. My hopes are somewhat diminished at this point, but sure, why not give it a go.

crawrj said:
Only other thing I can think of is to varify the md5 on the file you have to make sure it isn't corrupt. And to either reinstall the drivers or try a different computer.
Click to expand...
Click to collapse
Verified md5s, they match. Reinstalled drivers. Switched to a laptop. Same behavior and results each time.
Odin logs:
EL29:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> recovery.bin
GB27:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> boot.bin
In each case, following the last entry, everything hangs. There is no further movement in Odin's log or the progress bar. The phone continues to heat up, and not just the battery. The upper half of the glass and the rear case heat up also, but nothing tangible happens on the phone or the PC from that point on. Eventually, when I finally I unplug, Odin displays the red FAIL! flag, I have to pull the battery, let it cool, and it still won't boot into anything but download mode. All attempts to boot into recovery or system hang indefinitely at the initial Samsung logo screen.
Can this be salvaged or have I run myself out of options? If so, I understand that rooting and flashing my phone carried a risk, I chose to do it, stuff happens, it's all on me, and I accept all that. I'm not complaining, but I am very curious: has anyone else experienced or observed a phone suddenly and spontaneously brick itself while asleep in a pocket?

uminchu said:
Verified md5s, they match. Reinstalled drivers. Switched to a laptop. Same behavior and results each time.
Odin logs:
EL29:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> recovery.bin
GB27:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> boot.bin
In each case, following the last entry, everything hangs. There is no further movement in Odin's log or the progress bar. The phone continues to heat up, and not just the battery. The upper half of the glass and the rear case heat up also, but nothing tangible happens on the phone or the PC from that point on. Eventually, when I finally I unplug, Odin displays the red FAIL! flag, I have to pull the battery, let it cool, and it still won't boot into anything but download mode. All attempts to boot into recovery or system hang indefinitely at the initial Samsung logo screen.
Can this be salvaged or have I run myself out of options? If so, I understand that rooting and flashing my phone carried a risk, I chose to do it, stuff happens, it's all on me, and I accept all that. I'm not complaining, but I am very curious: has anyone else experienced or observed a phone suddenly and spontaneously brick itself while asleep in a pocket?
Click to expand...
Click to collapse
I don't understand how something like this could have happened from just sitting in your pocket? Which version of Odin are you using? You only have auto reboot checked right? And you are putting it in PDA?

crawrj said:
I don't understand how something like this could have happened from just sitting in your pocket? Which version of Odin are you using? You only have auto reboot checked right? And you are putting it in PDA?
Click to expand...
Click to collapse
Me either. I walked into a theater, sat down, grabbed the phone, checked mail, silenced it and put it back in my pocket. It had plenty of juice, somewhere in the 80s. The phone buzzed once during the flick. Afterward, when I took the phone out it was shut down and woudn't reboot; just hung at the logo. True story.
One Click Odins, v1.81, from the ET4G Q&A, Help & Troubleshooting forums:
http://forum.xda-developers.com/showthread.php?t=1903252

uminchu said:
One Click Odins, v1.81, from the ET4G Q&A, Help & Troubleshooting forums:
http://forum.xda-developers.com/showthread.php?t=1903252
Click to expand...
Click to collapse
I am at a loss. You can't get into recovery and Odin won't work. I only have one more thing to try. Turn the phone on and let it sit for a while and then plug it into the computer. Follow this guide and see what happens. http://forum.xda-developers.com/showpost.php?p=30996963&postcount=2
Just thought of one other possible chance. Download kies and run through the emergency firmware reload or whatever it is called.

crawrj said:
I am at a loss. You can't get into recovery and Odin won't work. I only have one more thing to try. Turn the phone on and let it sit for a while and then plug it into the computer. Follow this guide and see what happens. http://forum.xda-developers.com/showpost.php?p=30996963&postcount=2
Click to expand...
Click to collapse
Can't do it this sec, just on the way out, but will follow the guide verbatim asap and keep you posted. Thanks a mil for all your help. Whether or not I can restore this thing, please know that I am truly grateful for all your time and effort.

crawrj said:
Just thought of one other possible chance. Download kies and run through the emergency firmware reload or whatever it is called.
Click to expand...
Click to collapse
Good call, will try that as well when I get back, or possibly tomorrow am.

crawrj said:
I am at a loss. You can't get into recovery and Odin won't work. I only have one more thing to try. Turn the phone on and let it sit for a while and then plug it into the computer. Follow this guide and see what happens. http://forum.xda-developers.com/showpost.php?p=30996963&postcount=2
Click to expand...
Click to collapse
Sorry if this is a dumb question, but step 4 of your guide calls for booting into CWM, before ADBing anything. How do I push the images and start a shell if I can't get into recovery?

uminchu said:
Sorry if this is a dumb question, but step 4 of your guide calls for booting into CWM, before ADBing anything. How do I push the images and start a shell if I can't get into recovery?
Click to expand...
Click to collapse
Just skip the CWM part. I am hoping your phone comes up enough to be able to hit adb. But honestly I doubt it will work. Kies is about your only real hope at this point I would say.

Stuck in Android System Recovery (3e). Newbie needs help!

Hello. I recently switched from the iPhone to android and I rooted using the motochopper.zip. After I was done, I pressed the power button and then pressed it again to see the facial recognition lock. Then, it just froze. I pressed and held the power button and it has been stuck on the android recovery loop. I tried putting it into "download mode" as people have recommended and download this "custom OS", but it's stuck downloading. I've tried searching it up, but people are saying to "flash the ROM" or using "Odin". Since I am a new android user, I have no idea what they're talking about.
I know that there's some threads about this, but they're not on my device and they're outdated.
Your help is greatly appreciated. Thanks!

What phone do you have?
Sent from my Nokia 5120. Rocking it oldschool

bhp090808 said:
What phone do you have?
Sent from my Nokia 5120. Rocking it oldschool
Click to expand...
Click to collapse
Galaxy S4 AT&T

Same thing here
I'm having the exact same problem. I can't even get into download mode to try and restore. I'm not new to android and have had several Galaxy phones in the past. I think the internal SD is either corrupt or the OS has simply been wiped from it somehow. The phone boots and shows the Samsung logo with the "Custom" unlock icon then reboots and boots into stock recovery. Once in stock recovery, if I try to wipe cache it says "Wipe error" and goes back to the main menu. My phone is rooted with Motochopper since the release of the exploit. With the bootloader still locked, I haven't even attempted any other mods or flashes. My phone was fine all day yesterday but my battery completely died last night while I was out. I plugged it in and let it charge all night, the phone is fully charged. Removed SIM, external SD, still nothing. I'm going to continue to try and get to download mode but I've just about tried everything I can. Anything this awesome community can help with would be great, luckily I still have my Nexus so it'll do until I can call AT&T on Monday. Its a corporate account so a retail store won't touch it.

You guys try the vol down home button power button combo?
ATT S4 Rooted. Beastin.
4.2.2

There ya go.
http://forum.xda-developers.com/showthread.php?p=40976805
You should not lose any data.
As to how this happened I would suspect you guys were playing with Xposed framework and Cydia. That's how a lot of people are getting stuck in this recovery menu.
Sent from my SAMSUNG-SGH-I337 using xda premium

Odin restore worked..
I was trying the wrong button combination to get into download mode. I forgot I had installed and messed around with Cydia. Thanks for the help, this is why I love this place.

Android System Recovery
Hi,
I accidentally dropped my Galaxy S I and whenever I turn it on, there is a message that says:
Android system recovery <3e>
Enter: OK Key, Select : Vol UP/ Vol down
Reboot system now
apply update from sdcard
wipe data/ factory reset
wipe cache partition
"Reboot system now" is highlighted and I can't select other options for some reason. I took out the battery and the sd card, pressed every single button but it doesn't seem to work. I have no idea what I'm supposed to do!
Your help is really appreciated. Thank you

europ99 said:
Hi,
I accidentally dropped my Galaxy S I and whenever I turn it on, there is a message that says:
Android system recovery <3e>
Enter: OK Key, Select : Vol UP/ Vol down
Reboot system now
apply update from sdcard
wipe data/ factory reset
wipe cache partition
"Reboot system now" is highlighted and I can't select other options for some reason. I took out the battery and the sd card, pressed every single button but it doesn't seem to work. I have no idea what I'm supposed to do!
Your help is really appreciated. Thank you
Click to expand...
Click to collapse
A. You brought back a resolved thread from MAY????????????
B. You dropped your phone.....replace it. Warranty or insurance is your best bet. If warranty won't cover it or if you have no insurance on it, you could try to get Samsung to repair it for less than buying a new one (usually).
Please don't bring back any more OLD and RESOLVED threads.

unable to root and install cmw recovery on my Samsung galaxy grand duos gt 19082
Hi....
I am having Samsung galaxy grand duos gt 19082
having andriod 4.2.2
I want to root and install clockwork mod recovery
but I am not able to do this
please help
please
when I went to download mode
Then my phone goes to android system recovery <3e>
And when flash any zip file or rom
then it says E:signature verification failed
after this it auto reboot s
I also tried to do this with all versions of odin
but in this recovery mode odin is unable to detect my port or mobile
so please help me
please help
help me
help me
please

This is a s4 thread.. Perhaps why its not working?
mf3 rooted SHOstock 2.3

Cant get into download mode on 4.4.2
scott14719 said:
A. You brought back a resolved thread from MAY????????????
B. You dropped your phone.....replace it. Warranty or insurance is your best bet. If warranty won't cover it or if you have no insurance on it, you could try to get Samsung to repair it for less than buying a new one (usually).
Please don't bring back any more OLD and RESOLVED threads.
Click to expand...
Click to collapse
You are wrong this thread isn't resolved. I have the same problem with my Tmobile S4 (M919). When the phone boots without me pressing any buttons, it goes to
Android system recovery <3e>
KOT49h.m919UVUFNB4
and when I HOLD VOLUME DOWN + HOME + POWER it boots as it should. I can't go into download mode. I'm not sure but I think it has something to do with KNOX.
Please help if you have a way to get into DOWNLOAD MODE. I have tried button combination and adb (reboot download) methods.

Help
Hi,
I've just got a Note 3 but it's status is Custom. I don't think it's rooted, I certainly haven't done it.
Basically I want the Kit Kat update but it tells me I can't update OTA as it's modified and through Kies it says it's up to date which isn't true. I'm on 4.3.
I tried rebooting into recovery but it errors when I try and doesn't tell me any information about KNOX lock etc.
Anyway If I can do the update with Odin I'd be happy but could you help me:
Firstly what version of Odin should I use. I can see a 3.07. It seems old but is that OK ?
Secondly I can't work out what firmware I need to download for it. I have done *#1234# and this is what it tells me the following:
AP: N9005XXUBMJ3
CP: N9005XXUBMJ1
CSC:N9005DBTBMJ3
Any ideas what it is and which I'd need to download for it ? When I got it the phone was set to German by default but I'm not sure if that means it is German or not.
Any help would be greatly appreciated!!
Daniel

You might want to try asking in the Note3 forum. You will get better answers.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Thanks for the tip
Your tip on booting in safe mode helped me get out of recovery mode. Thanks.
stevehkim said:
You guys try the vol down home button power button combo?
ATT S4 Rooted. Beastin.
4.2.2
Click to expand...
Click to collapse

ANDROID SYSTEM RECOVERY (3e) Gallaxy S4
ZPaul2Fresh8 said:
There ya go.
http://forum.xda-developers.com/showthread.php?p=40976805
You should not lose any data.
As to how this happened I would suspect you guys were playing with Xposed framework and Cydia. That's how a lot of people are getting stuck in this recovery menu.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I am new to this website so forgive me if this has already been addressed. My daughter's phone has the Android System Restore (3e) message. I am trying to figure out a way to save her pictures and contacts without having to do a factory reset. Will the above file allow us to correc this problem and keep the contacts and pictures? She has pictures on her phone she needs to pass a class so she can graduate. Any and all helpl would be appreciated. If someone is able to walk me through this - I would appreciate it

So i followed the Odin post as it was, and i'm still stuck and seems no way out.
when i click "start" to flash and resetup the factory FW, i get the following.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/009> Removed!!
<ID:0/009> Added!!
<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> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
what am i doing wrong that i cant flash back to stock so i can flash PACMAN on my S4?

Your device was running a firmware newer than amdl. You will need to flash the mf3 or mk2 tar file in Odin. They are linked in the general section.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Red_81 said:
Your device was running a firmware newer than amdl. You will need to flash the mf3 or mk2 tar file in Odin. They are linked in the general section.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
is this post the one i need Red? when looking it was one of the first i seen with the info you gave me.

AndriodVamps said:
is this post the one i need Red? when looking it was one of the first i seen with the info you gave me.
Click to expand...
Click to collapse
Yes, use the all in one tar file. It's mk2
Sent from my Nexus 5

Urgent help needed, Travelling and Phone crashed

I'm hoping someone can help me. I'm stuck travelling and my phone just crapped out. I'm not sure if it something to do with the ROM, but I was recording video and then all of a sudden the phone just rebooted and got stuck on the first screen. When I would normally reboot, i'd see a lock and it'd boot into the OS, but now it just says Samsung Galaxy s5 and its stuck.
I'm hoping someone can point me to the first step I need to do to recover it. I can't even get into recovery mode using the home key, power and volumen button. It just says Recovery Booting... and is just sitting there.

So I was able to get into Maintenace Mode. Not sure what to do from here to to recover or do a fresh install.
I REALLLLYY appreciate any help you guys can provide!!
Not sure if it matters, but i'm on the latest MOAR ROM (OC4)

If it's really that urgent, you might have to take it to the Verizon store #shudder#

Verizon won't do anything..I bought this off of craigslist.
So I've been successful at getting to the 'Downloading...' screen to make Odin work. I've so far flashed the NK2 Kernel successfully, but when I try to flash the NK2.tar I consistently fail:
<OSM> ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I can't get past it, even after trying to flash different NXX .tars. I've tried two different computers, and different cables. I've tried Odin 3.10, 3.09 and 3.07
Suggestions please????

flashhsalf said:
Verizon won't do anything..I bought this off of craigslist.
Click to expand...
Click to collapse
That doesn't matter, if your service is through them, they can fix it.
I get the impression that it wasn't as urgent as you led to believe, since your initial post was days ago. You REALLY just wanted people to help you immediately...

ldeveraux said:
That doesn't matter, if your service is through them, they can fix it.
I get the impression that it wasn't as urgent as you led to believe, since your initial post was days ago. You REALLY just wanted people to help you immediately...
Click to expand...
Click to collapse
It was urgent at the time when I asked for help, but I got by using email to contact people that I needed because I had no choice.
I wasn't trying to dupe anyone to help me, I was in panic because I had no idea where to start while waiting for my flight. I didn't sit on my ass waiting for help either. I went and scoured the web for instructions on how to restore the phone and the last post is as far as I've gotten.
Thanks for your help btw.

flashhsalf said:
It was urgent at the time when I asked for help, but I got by using email to contact people that I needed because I had no choice.
I wasn't trying to dupe anyone to help me, I was in panic because I had no idea where to start while waiting for my flight. I didn't sit on my ass waiting for help either. I went and scoured the web for instructions on how to restore the phone and the last post is as far as I've gotten.
Thanks for your help btw.
Click to expand...
Click to collapse
Can you get to download mode to ODIN a ROM?

ldeveraux said:
Can you get to download mode to ODIN a ROM?
Click to expand...
Click to collapse
Yes, that is what i've been trying with Power+Vol Down+Home Key, I leave everything default and then add the .tar in the AP field. Few posts about other Samsung phones mention that i need to add some files in the BL, CP, CSC, field, but not sure if that applies to our S5.??
i've downloaded almost all of the Stock_Restore.tar files from this thread: (http://forum.xda-developers.com/showthread.php?t=2784880) and I've also tried the Stock_Retail.tar but they all fail at with the error in ODIN. After the error, I reboot but I can't get to the Samsung S5 screen. I get bootlooped into the ODIN screen saying firmware got corrupted, so with another attempts to reset, battery pull etc, I get to the normal ODIN screen and If I flash a Firmware, only then do I get to the Samsung S5 screen, but then nothing.
What I am not clear about is do I need to install the Retail Firmware or the Modem or the Kernel individually? Or do I just flash the Stock_Restore.tar as it has all of those files in it already.
Few times I was able to get ODIN to flash the rom tar without any errors not sure what changes I made, but it would then just sit on the Samsung Galaxy screen and not do anything.
Second time, I got Recovery Booting on the top left of the screen and then it'd just sit there. I tried to get into the Recovery Menu, but nothing would happen.
So I've just been trying to flash differnt combination of Firmware and stock Rom.tar files hoping something would stick, but i feel like i'm running in circles.
I've tried to get Kies 3 to work, but why samsung doesn't list the serial number on the S5 and then ask for it in their software is beyond me. I've tried Smart Switch, but it doesn't support our phone and i get stuck with the same are where I need the Serial Number. :/

You're in over your head, and for some reason, you refuse to go to the source to get this fixed. If you won't listen to advice on where to get help, I'm afraid I can't help you.

Which build were you running before the phone crashed? This may be applicable to you but you must have been on a build before BOC4.
Flash this. Unzip the file and you'll find a large file that ends in tar.md5
Open Odin (Doesn't matter which verion as long as it's higher than 3.09)
Click the button that says 'AP' and flash it.
Wait for the com-slot to go first blue then green and eventually say "PASS!!".
You should now have Stock NCG KitKat running on your SM-G900V

Quigly said:
Which build were you running before the phone crashed? This may be applicable to you but you must have been on a build before BOC4.
Flash this. Unzip the file and you'll find a large file that ends in tar.md5
Open Odin (Doesn't matter which verion as long as it's higher than 3.09)
Click the button that says 'AP' and flash it.
Wait for the com-slot to go first blue then green and eventually say "PASS!!".
You should now have Stock NCG KitKat running on your SM-G900V
Click to expand...
Click to collapse
I was on MOAR's OC4 ROM and i've tried what you have suggested and after I get the 'PASS!" and the system reboots, it never leaves the 'Samsung S5' screen. It'll stay there for hours. I then try to enter Recovery and I'll get the Recovery Booting on the top left of the screen in blue ..... and then it'll just stay there as well. I think something got corrupted and can't be overwritten with ODIN.
Where is the recover image located? In the bootloader? The menu which you see after you hit the Power + Vol UP+ Home?
Thanks for your suggestions, i do appreciate you trying.

ldeveraux said:
You're in over your head, and for some reason, you refuse to go to the source to get this fixed. If you won't listen to advice on where to get help, I'm afraid I can't help you.
Click to expand...
Click to collapse
Isn't everyone in over their head when they try to fix their phone for the first time with so much information scattered all over web forums and then multitude of exception about which rom and which firmware to install? Needless to say I took your advice and went to the Verizon store and they said what I excepted, Its not their problem, I need to take it to Samsung. I then found a Samsung support place at Best Buy and he pretty much said, because it said System Status: Custom , he can't plug it into his computer. So yea, not much help there, but thanks for your suggestions.

flashhsalf said:
Where is the recover image located? In the bootloader? The menu which you see after you hit the Power + Vol UP+ Home?
Thanks for your suggestions, i do appreciate you trying.
Click to expand...
Click to collapse
The recovery and boot.img files are in the ROM and/or tar.md5 package when you flash them.
Have you tried flashing the stock OC4 roms or just the firmware maybe?
When you flash a full tar.md5 with the MULTI CERT (bootloader FW) that should take care of your problem because that should overwrite any file system in place.

flashhsalf said:
I was on MOAR's OC4 ROM and i've tried what you have suggested and after I get the 'PASS!" and the system reboots, it never leaves the 'Samsung S5' screen. It'll stay there for hours. I then try to enter Recovery and I'll get the Recovery Booting on the top left of the screen in blue ..... and then it'll just stay there as well. I think something got corrupted and can't be overwritten with ODIN.
Where is the recover image located? In the bootloader? The menu which you see after you hit the Power + Vol UP+ Home?
Thanks for your suggestions, i do appreciate you trying.
Click to expand...
Click to collapse
Have you been able to resolve this issue or are you still stuck? I posted again to your questions just above this post. Basically what I'm saying is that you have a corrupt file that you're trying to flash or you have the incomplete version of the one you really need. This post http://forum.xda-developers.com/showthread.php?t=2784880 should steer you in the right direction if you still have quetions or you just PM me.

Make sure you're not trying to downgrade the bootloader. If you had BOE1 or later, an attempted flash of anything earlier than that will always fail because the bootloader was irrevocably locked.
You do not need to flash all of the components (modem, etc) in any combination. Just grab a full stock recovery image, and it contains everything you need. You can tweak with different modem versions later, but for right now focus on getting your phone working.
Make sure you're checking the md5 of the image you downloaded. A corrupted download will always fail to flash.
After successfully flashing with Odin, boot into stock recovery and clear the cache. If that doesn't work, boot back into stock recovery and also do "factory reset" to wipe out any remnants. (I wouldn't think this would do anything since flashing is supposed to wipe out everything, but it's worked for me on several occasions when stuck on the logo screen).
Read this to get yourself up to speed: http://forum.xda-developers.com/verizon-galaxy-s5/general/guide-painiacs-essential-guide-to-t3319848

Problem with Samsung Galaxy S4 - Help please

Hello,
I have a Samsung S4 locked to the T-Mobile/EE network in the UK.
The phone has suddenly stopped working.
When I do manage to switch it on, the phone vibrates and then the Samsung logo comes up but the background screen is all jumbled up, like its scrambled. I have tried getting the phone into Safe Mode, but it didn't work. I have also tried recovery mode, but some blue text comes on the top left of the screen and it just stays there.
I got these details from the stick in the back of the Phone if it helps.
MODEL: GT-I9505
FCC ID: A3LGTI9505
SSN:I9505GSMH
I hope somebody here can help me.
I am not that technically minded, but if steps are shown I can work it out, if there is a fix.
Thank you.

You may have to reflash the Samsung rom using Odin.
You can download the stock rom from sammobile.com.

boom247 said:
Hello,
I have a Samsung S4 locked to the T-Mobile/EE network in the UK.
The phone has suddenly stopped working.
When I do manage to switch it on, the phone vibrates and then the Samsung logo comes up but the background screen is all jumbled up, like its scrambled. I have tried getting the phone into Safe Mode, but it didn't work. I have also tried recovery mode, but some blue text comes on the top left of the screen and it just stays there.
I got these details from the stick in the back of the Phone if it helps.
MODEL: GT-I9505
FCC ID: A3LGTI9505
SSN:I9505GSMH
I hope somebody here can help me.
I am not that technically minded, but if steps are shown I can work it out, if there is a fix.
Thank you.
Click to expand...
Click to collapse
Hey there,
Unfortunately those stickers don't always represent the reality, because the sticker can be changed.
For the time being you will have to try and flash a stock rom.
Head over to sammobile.com, input your phone model, choose your country and carrier then download the latest firmware. Beware of very slow download speeds. You might want to give SamFirm tool a shot.
Afterwards get Odin (3.09 always worked well for me). Make sure you have the Samsung drivers installed.
Extract the firmware zip/rar you got and you should end up with a tar file.
Put the phone into download mode (volume down + power button), run odin, connect the phone to the PC (odin should display added!)
Put the tar file into the the AP slot (I think), uncheck every option in Odin except F.Reset time and hit start. Wait for it to complete.

GDReaper said:
Hey there,
Unfortunately those stickers don't always represent the reality, because the sticker can be changed.
For the time being you will have to try and flash a stock rom.
Head over to sammobile.com, input your phone model, choose your country and carrier then download the latest firmware. Beware of very slow download speeds. You might want to give SamFirm tool a shot.
Afterwards get Odin (3.09 always worked well for me). Make sure you have the Samsung drivers installed.
Extract the firmware zip/rar you got and you should end up with a tar file.
Put the phone into download mode (volume down + power button), run odin, connect the phone to the PC (odin should display added!)
Put the tar file into the the AP slot (I think), uncheck every option in Odin except F.Reset time and hit start. Wait for it to complete.
Click to expand...
Click to collapse
Thanks I will try that. File is downloading as I type.

GDReaper said:
Hey there,
Unfortunately those stickers don't always represent the reality, because the sticker can be changed.
For the time being you will have to try and flash a stock rom.
Head over to sammobile.com, input your phone model, choose your country and carrier then download the latest firmware. Beware of very slow download speeds. You might want to give SamFirm tool a shot.
Afterwards get Odin (3.09 always worked well for me). Make sure you have the Samsung drivers installed.
Extract the firmware zip/rar you got and you should end up with a tar file.
Put the phone into download mode (volume down + power button), run odin, connect the phone to the PC (odin should display added!)
Put the tar file into the the AP slot (I think), uncheck every option in Odin except F.Reset time and hit start. Wait for it to complete.
Click to expand...
Click to collapse
I done that, it shows a green coloured PASS in the top left square.
The phone is still showing Downloading.... Do not turn off.
This is what was shown in the message screen
What do I do now with the phone?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUHOD7_I9505EVRHOD1_I9505XXUHOD7_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> 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> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse

boom247 said:
I done that, it shows a green coloured PASS in the top left square.
The phone is still showing Downloading.... Do not turn off.
This is what was shown in the message screen
What do I do now with the phone?
Click to expand...
Click to collapse
You turn the phone off and unplug it. Then power it on. Hopefully it will boot. If not, try booting into recovery and then doing a factory reset. Reboot.

GDReaper said:
You turn the phone off and unplug it. Then power it on. Hopefully it will boot. If not, try booting into recovery and then doing a factory reset. Reboot.
Click to expand...
Click to collapse
ok. it doesn't turn on now. oh boy...

boom247 said:
ok. it doesn't turn on now. oh boy...
Click to expand...
Click to collapse
Then jump start it by plugging it in.

GDReaper said:
Then jump start it by plugging it in.
Click to expand...
Click to collapse
I've already tried that. It's not turning on at all.

boom247 said:
I've already tried that. It's not turning on at all.
Click to expand...
Click to collapse
Try a different battery.

GDReaper said:
Try a different battery.
Click to expand...
Click to collapse
Ok, so after leaving it for a few hours with the battery out. I managed to turn it on. plugged in the charger and it came up with the following message
Firmware upgrade encountered an issue. please select recovery mode in kies and try again.
(tried keis and its rubbish)

boom247 said:
Ok, so after leaving it for a few hours with the battery out. I managed to turn it on. plugged in the charger and it came up with the following message
Firmware upgrade encountered an issue. please select recovery mode in kies and try again.
(tried keis and its rubbish)
Click to expand...
Click to collapse
It may be possible that it did not flash right. For now I'd say to flash the firmware once more and hopefully it won't die again.

Problem with Samsung Galaxy S4 - Help please - UPDATE
Hello,
Ok, so after numerious times flashing, turning on off, etc etc. My Samsung S4 is still not working.
I've managed to take some photos of what I saw when I was flashing the phone using odin.
As you will see the screen does scamble sometimes, but when I tap it slightly it clears up again.
If anyone can help me, let me know, would like some experienced users for their suggestions.

Did you get any errors when flashing in Odin?
If the screen clears up when you touch it in download/Odin mode, sounds like there may be hardware damage.

audit13 said:
Did you get any errors when flashing in Odin?
If the screen clears up when you touch it in download/Odin mode, sounds like there may be hardware damage.
Click to expand...
Click to collapse
When I found the correct OS to flash I didn't get any errors. So, No, no errors.
I think it might be hardware failure.
But the recovery to flash the phone works. However anything else doesn't.
When I turn it on, it just hangs on the logo screen.

Are you performing a factory wipe in stock recovery right after flashing and before booting the phone for the first time?

audit13 said:
Are you performing a factory wipe in stock recovery right after flashing and before booting the phone for the first time?
Click to expand...
Click to collapse
To be honest, I am following instructions I found on-line. These are instructions on how to flash with ODIN
I remember I showed my phone to a IT guy at work, who wiped the cache, but after that Ive never been able to go into that menu again.
I would appreciate any further help and suggestions.
Thank you for your reply

To get into recovery, are you holding down the home button, volume up, and power?

audit13 said:
To get into recovery, are you holding down the home button, volume up, and power?
Click to expand...
Click to collapse
Yes I did try that. It comes up with the blue recovery text on the top left of the screen and just stays there

Try this: open Odin, uncheck auto reboot, flash the phone with the stock ROM, when you see the word reset in the status window, remove the USB cable from the phone, remove battery, replace battery, press and hold all three buttons. It may take a while but keep holding the buttons to see what happens.

In dire need of help with a soft-bricked S4 (GT-i9505), tried almost everything

Greetings to you all,
Long time lurker first time poster.
I made an account because nothing seems to be working and I'm in need of some professional insight regarding a particular problem.
So the problem is that one day, while chatting on whatsapp having edited no settings at all, on a completely stock (non-rooted, no customization of any kind) international version (I'm in Germany, bought it carrier-independent) of the S4 (GT-i9505), the phone shut off and was stuck in a bootloop.
I thought I can go into recovery mode and maybe wipe the dalvik cache since it may have gotten corrupted, but recovery mode wasn't working as it was getting stuck/not booting.
Luckily, download mode is available. Here's what I've tried so far to no avail:
1. I tried flashing the stock firmware using odin, but it didn't work.
2. Tried using the very helpful thread about kies emergency recovery found here on the site, but kies doesn't recognize the phone (but odin does) even though I have all the needed Samsung drivers.
3. I thought of flashing TWRP and using that to flash the tar file via the sd card, but TWRP wasn't flashing either. But I used an older version of Odin and it worked. However, once it boots normally or boots into recovery, it says at the top of the screen "Recovery is not SE-enforcing. Set warranty bit: recovery" and gets stuck again. Download mode is still somewhat accessible but gets stuck halfway into booting about every time. To elaborate, If I want to get into download mode, if don't hold the Volume Up button anymore the phone shuts off, and if I keep the buttons pressed, it's essentially stuck.
I'm honestly at a loss right now. Being lucky enough to get into download mode to flash anything with Odin gets stuck in "setupconnection" in the Odin log most of the time or just fails. Have any of you had a similar problem? How did you resolve it? Any tips or advice from the pros? I have some important files I didn't have time to backup, much to my disappointment. Any help is very much welcome.
Could the hardware be dying? The internal storage/NAND maybe?
Also, the phone was running out of space, but as far as I know the partition for the OS should be stable/constant and shouldn't affect the flashing of a firmware package.

Did you get Odin errors when trying to flash stock ROM? What were the error messages? You used the latest stock ROM from sammobile.com? You used an original Samsung USB cable to flash with Odin? Tried other USB cables and USB ports with Odin?

audit13 said:
Did you get Odin errors when trying to flash stock ROM? What were the error messages? You used the latest stock ROM from sammobile.com? You used an original Samsung USB cable to flash with Odin? Tried other USB cables and USB ports with Odin?
Click to expand...
Click to collapse
Thanks for the concern. The following is the log I got on Odin (latest version) when I tried to flash the stock ROM:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
And the following is the Odin (latest version) log I got when trying to flash TWRP the first time:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<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> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The second attempt (using an older version of Odin (v3.07)) was a success with the following log being outputted:
<ID:0/003> Added!!
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
My main problem now is that download mode gets stuck. And, even though flashing the proper TWRP image was a success, it gets stuck when I attempt to boot into recovery mode. In fact, after successfully flashing TWRP, the boot-screen gives the message "Recovery is not SE-enforcing. Set warranty bit: recovery" at the top-left of the screen.
Yes, the latest version of the stock ROM from sammobile.com was attempted to be flashed with no success.
I did suspect the cable to be faulty and bought a new one with the same result of failure.
I did not attempt different ports; would the port cause these problems?
I don't know what I can do. I've never encountered such persistent and seemingly-random problems.
Also, I also tried to boot the system (knowing it would fail to do so) and tried to use ADB to flash TWRP, but it also failed, as the device did not reach the point at which ADB can perhaps make some use of it, following the instructions set here: xda-university[dot]com/as-a-user/how-to-recover-from-a-bootloop
Should I try flashing CWM instead of TWRP?

ThePrick said:
I did not attempt different ports; would the port cause these problems?
Click to expand...
Click to collapse
You already know the solution for 99% of Odin errors. Try all the ports on your pc.

@ThePrick
I believe it is some kind of hardware failure.
A device shutting down all of a sudden (without any modifications having been done to it) is not normal.
Getting stuck in recovery and download is also not a good sign.
You could take it to a service and have the Jtag it.

Lennyz1988 said:
You already know the solution for 99% of Odin errors. Try all the ports on your pc.
Click to expand...
Click to collapse
I shall try different ports when download mode works again. When trying to get into download mode, if I take my fingers off the buttons I've pressed, the phone shuts off. And I need to take them off in order to select the 'yes' option in order to proceed to download mode... which shuts off the phone. Really at a loss. Is it hard-bricked now? Why would download mode be giving this random problem?
GDReaper said:
@ThePrick
I believe it is some kind of hardware failure.
A device shutting down all of a sudden (without any modifications having been done to it) is not normal.
Getting stuck in recovery and download is also not a good sign.
You could take it to a service and have the Jtag it.
Click to expand...
Click to collapse
I agree. The thing is, once the phone reaches anywhere between 5-20% charge, it sometimes shut down randomly. Maybe it just corrupted the system because of an impromptu shut-down. I got a new battery. Still, it should have been a very straightforward process, i.e. just flash the firmware and if that doesn't work, flash twrp and flash the firmware from the sd. Maybe this could have worked at first if I used different ports. Unfortunately download mode is not working.
When I try the Volume Up + Home + Power button combo, it does enter download mode. I then need to select an option (yes/no option to proceed) so it actually boots to download mode. However if I take any of my fingers off any of the buttons, the phone shuts off.
I'll definitely try different ports once this is sorted.
If I take it to a shop I'd need to explain what I've done to the phone and I'm afraid they'll either be confused or refuse or tell me it's broken after a while.

ThePrick said:
I shall try different ports when download mode works again. When trying to get into download mode, if I take my fingers off the buttons I've pressed, the phone shuts off. And I need to take them off in order to select the 'yes' option in order to proceed to download mode... which shuts off the phone. Really at a loss. Is it hard-bricked now? Why would download mode be giving this random problem?
I agree. The thing is, once the phone reaches anywhere between 5-20% charge, it sometimes shut down randomly. Maybe it just corrupted the system because of an impromptu shut-down. I got a new battery. Still, it should have been a very straightforward process, i.e. just flash the firmware and if that doesn't work, flash twrp and flash the firmware from the sd. Maybe this could have worked at first if I used different ports. Unfortunately download mode is not working.
When I try the Volume Up + Home + Power button combo, it does enter download mode. I then need to select an option (yes/no option to proceed) so it actually boots to download mode. However if I take any of my fingers off any of the buttons, the phone shuts off.
I'll definitely try different ports once this is sorted.
If I take it to a shop I'd need to explain what I've done to the phone and I'm afraid they'll either be confused or refuse or tell me it's broken after a while.
Click to expand...
Click to collapse
Try to wiggle your power button. It may be a little bit stuck.

Try to use another data cable, I had the similar issue before having a new (better ?) data cable.
Or may be try flashing the pit again if you had ever tried Marshmallow before.

Lennyz1988 said:
Try to wiggle your power button. It may be a little bit stuck.
Click to expand...
Click to collapse
Thank you. It was indeed the power button. Although that doesn't fully explain the situation, I'm glad it wasn't anything more serious. After a couple of days I retried and after a couple of tries it could boot into download mode without freezing. Still wouldn't boot the system; flashed the firmware and it worked this time. Reboots every 20 minutes or so but I got most of my data back. Currently on an Galaxy S5.
Thanks for all the advice everyone!
Now my girlfriend's phone has a similar problem, only it's an HTC Desire 820.. The phone freezes during boot and it started off with the power button working only intermittently. Probably the power button leading to the freeze during boot. No removable battery so I can't remove the battery to restart. This is one of the reasons why removable batteries are important! She's going to take it to a repair shop though so that's that.
Thanks again for all the insightful advice and invaluable information!