Database Info

[Q] Galaxy S 4G Won't Boot

I just rooted my phone and I was trying to flash it to gingerbread and it was working fine, but clockwork mod wouldn't let me backup. A forum told me to dlete the recovery in the system and replace it and i did, but the replacement was titled "recovery - copy". i tried to reboot my phone but it is stuck at the "Galaxys S 4G - TMOBILE" screen. I can't get into recovery mode and i could never get into download mode. HELP!

How did you try to get into download mode and what rom did you flash?
Sent from my SGH-T959V using xda premium

here is a guide http://forum.xda-developers.com/showthread.php?t=1069032
pull battery and then plug in usb then hold down volume and then you should be in download mode. you should see phone on odin.

GMSonicX said:
I just rooted my phone and I was trying to flash it to gingerbread and it was working fine, but clockwork mod wouldn't let me backup. A forum told me to dlete the recovery in the system and replace it and i did, but the replacement was titled "recovery - copy". i tried to reboot my phone but it is stuck at the "Galaxys S 4G - TMOBILE" screen. I can't get into recovery mode and i could never get into download mode. HELP!
Click to expand...
Click to collapse
i have yet to see anyone say "delete" the recovery file. it is always "overwrite". regardless, put your phone into download mode. you are doing it wrong. try again until you get it right.
remove the battery. leave it off for 10 seconds. put it back in. press and hold the two volume buttons at the same time. then plug in the usb cable that is connected to your computer. odin should be running already. i would follow gb start pack from here.

i turned of the phone and held the volume down button and the power button, letting go of the power once the turn on screen came up. i was trying to flash the leaked android 2.3.5 for the galaxy s 4g

please read my previous post carefully. i never said to press the power button at all.

OKAY, dwld mode is volumes plus USB cable, never failed me, even when I failed a flash through odin/heimdall and just maybe a yellow pixel or even nothing shows up.
If it flashes it is dwld. The GS4g has absolutely no junk bootloader witthout proper download mode unlike other galaxies.
PS. Who else wants a Galaxy Nexus?
What is the tmobile warranty policy, I know if there is a problem with your phone even due to damage, the warranty covers it for replacement after paying contract price, but do they allow a change of phone eg instead of paying 99 or 139 for another gs4g, get a galaxy nexus for 199?
My phone works, but after it fell, it overheats and loses battery. I even got a free new battery, and I even went back to stock KD1 for a while, no difference.

So, I did what you said, and i got into download mode, no problem. but when i tried to flash with odin it just said fail.. any suggestions?

Although the square window might say "Fail" there's a status window in the bottom left-hand side of ODIN that should give you more information. What does that window say when you try to flash?

It said succesful 0/ failed 1. I tried to reboot my phone and now it won't turn on at all...

It sounds like your boot loaders are hosed.
Keep ODIN open & use the battery-pull method to see if it'll go into download mode (the screen might still be black, but see if ODIN recognizes it).
If it does:
Download chadster's KG4: http://forum.xda-developers.com/showthread.php?t=1183413
Put CODE_T959VUVKG4_CL138158_REV00_user_low_noship.tar.md5 in PDA
Put Hawk_Sidekick_VibrantPlus_831.pit in PIT
Put SGH-T959V-CSC-TMB-VIBRANT.tar.md5 in CSC
Put T959VUVKG4-Phone-CL1037720.tar.md5 in PHONE
Let ODIN decide what boxes need to be checked and flash. That will get you booted up on GB with the proper boot loaders.

Try the Unbrickable Mod in the dev section. Brought mine back today. I had a Bright WHITE screen. lol

NO BOOT
After flashing this kernel> sms-T959V-KJ6-antsvx.v1.1.3 my Galaxy S4G will not boot AFTER restoring my backup using CWM 5.0.2.8. My phone runs perfect with the stock rom and this kernel. ONLY after restoring does it NOT boot.
Can someone shine some light on this situation?

You need to restore using the kernel you made the back up from. You can then flash the new kernel over the restored back up.

lumin30 said:
You need to restore using the kernel you made the back up from. You can then flash the new kernel over the restored back up.
Click to expand...
Click to collapse
I can only get into download mode, what app would I use to flash the kernel ? (its saved on my pc)
---------- Post added at 05:06 PM ---------- Previous post was at 04:42 PM ----------
Thanks much Lumin30. Had to read your post sloooow and figure it out, and I got it. I flashed the stock+Voodoo-T959VKJ1 in Odin and it booted right up
then flashed the sms-T959V-KJ6-antsvx.v1.1.3 kernel in CWM. Im good to go now.
This has happened to me 2 other times can you suggest why? The other times I restored phone back to factory :crying:.

Still not booting AFTER restoring cwm backup
I always attempt to restore a backup that I have made using cwm as a test. Im trying to restore using the same kernel I made the backup with. When I proceed the full restore appears to go through (I get "restore complete" message in CWM v.5.0.2.8), but when I click on "reboot system now" my phone goes ONLY to the Samsung screen and stays there.
I have restored my phone to stock about 5 times carefully re-rooting and flashing the kernel with the stock firmware. Now, I have AntonX Barebones and Basic with a twist kernel installed, they work perfectly! But I CANNOT boot AFTER restoring a full backup, unless I use Odin. Can someone help me to address and fix the cause?
Edit> I was able to restore and boot up automatically a backup using CWM 5.0.2.8 of AntonX's Barebones Rom with bhundven's Blastoff 2.5 kernel. Dont know why it restored and booted properly this time but this is what I did:
I made a fresh backup of Barebones with Blastoff because I wanted to try Valhalla Black (nice ROM). I flashed it first using the "generic" install and checked through its features then wanted to see how the "custom" install felt. I decided I liked Barebones better and flashed the Blastoff kernel onto Valhalla Black, Then booted into CWM and restored my Barebones with Blastoff backup. Without wiping anything or fixing permissions my backup was fully restored and my phone booted properly on its own. I know this is what should happen, but it wasnt for me. And every time I attempted this I was restoring using the same kernel that the backup was made with. I restored twice since just to test it and both times my phone booted on its own. I believe my problemo is solved. It is possible I had a couple of bad downloads on my part with AntonX Basic with a twist 1.1.3
Thanks to the community (XDA)

[Utility]EZ Update Android 4.2/CWM/Root/Save Data/1 Click

Lots of people are having problems with the Android 4.2 update. They lose root or they can't get back into recovery. So BEFORE you flash 4.2 or if you already did and are having issues. Download this utility I whipped up. It will flash (or reflash) the 4.2 update (Including system, kernel and bootloader). It'll flash the latest 4.2 compatible ClockworkMod Touch Recovery. And then it'll get you all set up to re-root your N7 within the latest CWM. Instructions are included in the README file. PLEASE READ IT!
You DO NOT need to be on a stock rom to run this and it will NOT erase your data. But it is recommended when you get into CWM recovery for obvious reasons.
If anyone is having any issues and you get caught at the Google splash screen. You can use Power, Vol - to hard shut down the tablet, then Power, Vol +, Vol - to get into the bootloader. From here you can install the factory images from google. Once you're back up and running, you can run this tool to gain root and CWM back.
Updated 11/14/2012: Replaced SuperSu.apk with the latest version designed for 4.2
Updated 11/14/2012 14:41EST: This package will now contain 3 different runme files. One of them will not erase your data, one will erase your cache only and the last one will erase your data and cache. It seems people coming from some roms are having bootloops or hangs because of a lack of data wipe. You can attempt to run the one with no data wipe, but if you run into trouble, try one of the others. Some have made it through with only a cache wipe. See what works for you.
Updated 11/14/2012 16:53EST: Removed full data erase option as I forgot it will erase your SD card and therefor erase the root zip before it gets a chance to flash. There is only 1 runme file now and it will erase your cache, but leave your data alone. If you're having problems, or you want to avoid problems. Erase your data in CWM before you flash the supersu zip included in the package.
For Now - Windows ONLY, Sorry.
Linux version, on the way
Anyway:
Download and PLEASE READ the Read Me!

Saweet
Sent from my Nexus 7 using xda premium

Just trying to make it easy

im on 4.2 already ,can i use this to root?

Thanks for putting this together tucstwo, it was super helpful and easy for a lot of us here

Ok, I tried this and got stuck on the boot screen. Guess Ill try it again. I was on AOKP before.Can I just run this from there? I should I have wiped before?
edit
Ok it worked once I wiped it when it booted in CWR.
Great job. Now just have to test if it is still rooted

Im not getting something. After I press runme.bat my Nexus goes to clockwork recovery, its not touch, I have to choose from options like Start, Recovery Mode, etc. It doesnt match the instructions. Im super confused, any help?
Ugh. now my device is stuck at the google start screen, and not going anywhere. Android is too complicated sometimes for dumb people like me...

Solange82200 said:
Im not getting something. After I press runme.bat my Nexus goes to clockwork recovery, its not touch, I have to choose from options like Start, Recovery Mode, etc. It doesnt match the instructions. Im super confused, any help?
Click to expand...
Click to collapse
Its booting you in fastboot. just follow the instructions in the window that comes up when you run the runme.bat.
When it boots in fastboot just hit the space bar. It will take a couple times of hitting the spacebar before you reach the CWR stage where you flash the PlaceMeOnYourSDCardSuperSu.zip

When I click runme, it opens up the cmd window, starts the daemon, and then just sits there with a blinking cursor. Tried this few times already, nothing is happening.
EDIT: My nexus 7 is connected and has usb debugging turned on.

Hasan10 said:
When I click runme, it opens up the cmd window, starts the daemon, and then just sits there with a blinking cursor. Tried this few times already, nothing is happening.
Click to expand...
Click to collapse
Do you have ADB set up on you computer?
Did you make sure you have USB debugging selected on your nexus 7 in developer options?

trusteelfan said:
Do you have ADB set up on you computer?
Did you make sure you have USB debugging selected on your nexus 7 in developer options?
Click to expand...
Click to collapse
Figured it out. My computer recognizes the Nexus 7 as a portable device, but not recognizing it in the usb debugging mode (shows "Nexus" under Other Devices with a yellow triangle). Tried to update the driver, but it failed.

Thanks, it wasn't clear to me for some reason when I was doing it. It just kept saying after the black screen press continue, but something stopped along the way. I cant do it again because my device wont get past the Google startup screen, so I guess Im just going to flash from stock or something. Thank you for the quick help though, much appreciated!

Solange82200 said:
Thanks, it wasn't clear to me for some reason when I was doing it. It just kept saying after the black screen press continue, but something stopped along the way. I cant do it again because my device wont get past the Google startup screen, so I guess Im just going to flash from stock or something. Thank you for the quick help though, much appreciated!
Click to expand...
Click to collapse
You can run it again if it got stuck. I had to run it twice
---------- Post added at 10:04 PM ---------- Previous post was at 10:03 PM ----------
Hasan10 said:
Figured it out. My computer recognizes the Nexus 7 as a portable device, but not recognizing it in the usb debugging mode (shows "Nexus" under Other Devices with a yellow triangle). Tried to update the driver, but it failed.
Click to expand...
Click to collapse
The Nexus 7 toolkit will put the right drivers in place if you need them.

OK, I will try that.
By the way, I am currently on Android 4.1 with unlocked BL and CWM Recovery running Franco Kernel. Is this utility safe to use with this setup?
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
OK So I have finally got the drivers, and then ran the runme. It booted me into fastboot mode and now it says sending 'bootloader' <2096 KB>... and seems to be stuck on it. I havent touched anything on my nexus 7, didn't press any buttons yet.
Unplugged it and then plugged it back in. It failed to flash the bootloader and went straight to boot and system flashing. It has now booted into Android 4.2, but I am assuming it still got the older bootloader. I think I will have to re-run the whole process to ensure new bootloader gets flashed eh? Or is there a 4.2 bootloader floating around that I can just flash using CWM and save myself the trouble?

Hasan10 said:
OK, I will try that.
By the way, I am currently on Android 4.1 with unlocked BL and CWM Recovery running Franco Kernel. Is this utility safe to use with this setup?
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
OK So I have finally got the drivers, and then ran the runme. It booted me into fastboot mode and now it says sending 'bootloader' <2096 KB>... and seems to be stuck on it. I havent touched anything on my nexus 7, didn't press any buttons yet.
Unplugged it and then plugged it back in. It failed to flash the bootloader and went straight to boot and system flashing. It has now booted into Android 4.2, but I am assuming it still got the older bootloader. I think I will have to re-run the whole process to ensure new bootloader gets flashed eh?
Click to expand...
Click to collapse
It takes it a few minutes to run the process. You should have just waited

trusteelfan said:
It takes it a few minutes to run the process. You should have just waited
Click to expand...
Click to collapse
No I realized it didn't install the fastboot drivers before the process began. So it was actually not able to send the bootloader. Anyways, can you please read my edited post above and advise me with that to do?
EDIT: I went ahead and re-ran the process. Since all drivers were in place, the total process took less than 5 mins, arguably faster than an OTA. Still have all of my data and the goodness of 4.2.
Thanks a lot OP for this great utility.

trusteelfan said:
Ok, I tried this and got stuck on the boot screen. Guess Ill try it again. I was on AOKP before.Can I just run this from there? I should I have wiped before?
edit
Ok it worked once I wiped it when it booted in CWR.
Great job. Now just have to test if it is still rooted
Click to expand...
Click to collapse
What was it that you wiped? Just to make sure I do exactly what you did. I'm stuck on the glowing nexus logo.

essay708 said:
What was it that you wiped? Just to make sure I do exactly what you did. I'm stuck on the glowing nexus logo.
Click to expand...
Click to collapse
I had to wipe my data. It didnt like coming from AOKP

Nevermind, I wiped cache and dalvik cache and it worked for me too.

Everything is good over here. Rooted with twrp instead tho. Anyway something weird is going on with my battery, and yo seem pretty knowledgeable so I thought I'd run it by ya and see if you couldn't shed some light on the issue. Anyway my battery stats are showing that the device isn't awake.. When clearly it is and in the stats it says the screen is even on.. But not awake. Also the screen seems to brighten and dim at odd times idk if that has anything to do with it. But I flashed an ota update.. Bootloader and all. Kept root with supersu. You think something might have been corrupt or something? Here's a screenshot of the issue.. Hmm another issue, whenever I try to take a screenshot.. With more than one app, it takes a pic of an earlier point when I was on twrp getting ready for the 4.2 update. Some really strange things are going on..

[Q] In a Bit of a Predicament with Nexus S 4G; is it possible to fix?

So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please note I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronize me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image. Any help or suggestions would be very much appreciated.

Carbon131 said:
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please not I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronage me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image flashed. Any help or suggestions would be very much appreciated.
Click to expand...
Click to collapse
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|

polobunny said:
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
Click to expand...
Click to collapse
Hopefully someone may know what to do.

Carbon131 said:
Hopefully someone may know what to do.
Click to expand...
Click to collapse
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.

polobunny said:
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
Click to expand...
Click to collapse
Yeah I can't seem to do that.

Carbon131 said:
Yeah I can't seem to do that.
Click to expand...
Click to collapse
Make sure your cable is connected when you try to put your phone in download mode. Turn off the phone, then hold both volume + and -, and press power. Continue holding volume buttons until you see download mode.

[Q] Problem during rooting help

I was attempting to get root access to my galaxy tab 2 10.1 running android 10.2.1 (or whatever the latest Samsung update was it is 10.2 on my phone but am sure it was 10.2.1 on the tablet.
I was following this guide that someone here recommended
http://www.ibtimes.co.uk/articles/4...-p5113-android41-jellybean-android404-ics.htm
I set usb debug and made sure the drivers were on my pc and made sure KIES was completely not running
Followed the instructions to the letter but should have worried when I found the instructions to get to download were wrong - I found on videos that it was reboot using power and right volume key. That was successful
It connected to ODIN fine and the yellow box came up
I made sure the two boxes were ticked and then searched for the file
CF-Auto-Root-espresso10wifi-espresso10wifibby-gtp5113.zip and started ODIN
it seemed to be going fine until suddenly a red box came up with update failed
Now all I can get on the device is "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
No matter how I try to restart this I get the same screen and imagine I couldn't connect to kies even if I should
Can anyone help as I am worried that I have bricked my device - I was looking for a simple way to get root without flashing a whole rom - or is that what I was doing anyway?

Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:

Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again

n0is said:
Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:
Click to expand...
Click to collapse
I will take a look but so far the only thing I get is the message to connect to KIES and it wont of course connect - cant get into any other modes - you would think they would have some kind of hard boot recovery button that gets you to basic screen to download the latest firmware.
And I did start here and believe that this led from a post here - I was trying to find the least complicated method of getting root access without changing what I already had too much - the only other process that I found on here seemed to have lots of people reporting problems if it wasn't a 3g model
It is beginning to look like I may have found out what bricking is - thanks for the reply anyway

would like to do that
mjrshark said:
Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again
Click to expand...
Click to collapse
In fact the instructions do say if it doesn't work first time, to run it again with the boxes unticked - the problem is that I cant get back to download mode, or any mode other than the message to connect to kies, so have no way of doing this. So looks like it may have bricked - is there any way of unbricking a tablet?:crying:
It's going to be an expensive mistake especially as I haven't even had the £50 cash back from Samsung yet and I would have to pay full price now to replace it,

So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium

not optamistic but will try!
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I will try but I don't think it is going to work. Whenever I connect the tablet by USB I get the usb connecting sound followed immediately by the USB disconnect sound - this just continues to happen every 4 seconds or so all the time that the device is connected. At the moment I have it on charge as once the error screen comes on it doesnt seem to go off for a very long time and then it wont start unless I charge it first. After a few minutes on charge - The firmware upgrade encountered an issue message comes up. I am going to leave it a while until I am sure it is fully charged and then try what you suggest - not optamistic though since I now realise that it is not even connecting properly. I just have a bad feeling about this. I had to disconnect it from the power yesterday because the error screen stays on continuously and the device starts to get warm
Assuming that I ever manage to get a stock image installed will this mean I can go back to normal kies updates - all I really wanted was the standard samsung android O/S but with super user added.
Unfortunately I had read the linked article a while back and what made me more confident was the statement that said it was "virtually impossible to brick this device"

Since it's still going into Charging mode and spitting out error messages, it's not completely bricked. It's just in a reboot loop (a.k.a. soft brick).
Keep trying to get it into Download mode. Sometimes the timing is a little tricky if it's in a boot loop.
1. Disconnect it before trying to get it into Download Mode. If it's plugged in (charger or PC), the device will go into Charging mode instead.
2. Hold the Power button for 10 seconds to make it reboot.
3. When you see the screen turn off, let go of Power and then press and hold Power and Volume Right/Up.
4. If done correctly, it will immediately go into Download Mode. If you see the Samsung logo instead, repeat from Step 2.

some progress but still stuck - any more ideas please
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Hi well thanks -
when I connected Odin it did show up yellow and so I downloaded the P5110 stock from from the other thread - all went well and it reported all OK and re-booted - saw the animated sequence but now it has stalled on the samsung logo and still wont connect to kies
So still stuck but at least it has moved on - The instructions on the other page were a little unclear about one stage
It said if there was pit file included to set something and tick repartition - this was all in one line and so I assumed part of the pit instruction - as there was no pit file I did not tick re-partition - I wonder if I should have done?
I have just reconnected to ODIN and the ID Com is still lit up yellow so presumably I could try running it again, or should I look on here for another stock rom - I am wondering if I have somehpw scewed up the bootloader and if so how I go about restoring it
ODIN is the only thing it connects to right now

Upload Mode: MODEM CRASHED!

I was running the NKD Odexed ROM, and out of nowhere my phone just froze up and eventually went to Upload Mode where I was able to see that my Modem Crashed. When I pulled the batter and restarted my phone, I had no mobile service, and my Baseband and Software information both say Unknown. I cannot reboot into recovery, it just keeps bootlooping . I was able to flash the NK4 full restore, but when that loads up, even though it shows the LTE icon, my mobile data network status is set to disconnected. I also cannot boot to recovery from NK4 or any 4.4 bootloader to restore a backup. Any help would be incredibly appreciated. I'll be more than happy to buy some beers for anybody who can help me with this. Sprint is unable to help me on their end.
Edit: I should also note that I've tried Odin'ing the NKD modem several times when I am on android L, and the NK4 when on 4.4, neither do a thing to help.

jsmcmahon89 said:
I was running the NKD Odexed ROM, and out of nowhere my phone just froze up and eventually went to Upload Mode where I was able to see that my Modem Crashed. When I pulled the batter and restarted my phone, I had no mobile service, and my Baseband and Software information both say Unknown. I cannot reboot into recovery, it just keeps bootlooping . I was able to flash the NK4 full restore, but when that loads up, even though it shows the LTE icon, my mobile data network status is set to disconnected. I also cannot boot to recovery from NK4 or any 4.4 bootloader to restore a backup. Any help would be incredibly appreciated. I'll be more than happy to buy some beers for anybody who can help me with this. Sprint is unable to help me on their end.
Edit: I should also note that I've tried Odin'ing the NKD modem several times when I am on android L, and the NK4 when on 4.4, neither do a thing to help.
Click to expand...
Click to collapse
I had almost the same problem yesterday and was able to restore my backup this morning.
Here's the steps I took:
1. Using Odin 3.10.0
2. Make sure your phone is completely off (battery pull if necessary).
3. Go into Download Mode (Volume Down, Home, Power), then Volume UP
4. Plug phone via USB to computer, run Odin. Make sure you have a blue ID:COM light in Odin.
5. Uncheck Auto-Reboot.
6. Odin either NE5 firmware or NK4 firmware (depending on what your nanoid was).
7. Wait till Odin gives you a PASS, unplug USB and immediately go into Recovery (Volume UP, Home, Power).
8. Restore your nanoid and reboot.
This is assuming you have an extSD card and your nanoid is on it. If you don't you'll need to get one. If you don't have a nanoid, copy the rom you want to flash onto extSD and replace step 8.
Edit: FYI, the firmware files include the modem and TWRP recovery.
Edit: My reading skills are a little slow today, if you prefer the firmware with Philz, here's NE5 and NK4 firmware with Philz.

Ramer said:
I had almost the same problem yesterday and was able to restore my backup this morning.
Here's the steps I took:
1. Using Odin 3.10.0
2. Make sure your phone is completely off (battery pull if necessary).
3. Go into Download Mode (Volume Down, Home, Power), then Volume UP
4. Plug phone via USB to computer, run Odin. Make sure you have a blue ID:COM light in Odin.
5. Uncheck Auto-Reboot.
6. Odin either NE5 firmware or NK4 firmware (depending on what your nanoid was).
7. Wait till Odin gives you a PASS, unplug USB and immediately go into Recovery (Volume UP, Home, Power).
8. Restore your nanoid and reboot.
This is assuming you have an extSD card and your nanoid is on it. If you don't you'll need to get one. If you don't have a nanoid, copy the rom you want to flash onto extSD and replace step 8.
Edit: FYI, the firmware files include the modem and TWRP recovery.
Click to expand...
Click to collapse
Unfortunately, I can't count how many times I've tried this, both the firmware with TWRP, and firmware with Philz, my recovery will not boot. I get RECOVERY BOOTING.... in blue, RECOVERY IS NOT SEANDROID ENFORCING in red and Set Warranty Bit : recovery in yellow. This lasts about 30 seconds, and then it reboots to the same thing. The only way to get out of the recovery bootloop is to flash a firmware and not try to boot into recovery after, but then stuck with my modemless problem .
I can't even just go back Stock everything because I won't have service, my phone is basically a paperweight at this time.

jsmcmahon89 said:
Unfortunately, I can't count how many times I've tried this, both the firmware with TWRP, and firmware with Philz, my recovery will not boot. I get RECOVERY BOOTING.... in blue, RECOVERY IS NOT SEANDROID ENFORCING in red and Set Warranty Bit : recovery in yellow. This lasts about 30 seconds, and then it reboots to the same thing. The only way to get out of the recovery bootloop is to flash a firmware and not try to boot into recovery after, but then stuck with my modemless problem .
I can't even just go back Stock everything because I won't have service, my phone is basically a paperweight at this time.
Click to expand...
Click to collapse
Have you tried to odin the .tar version of Philz?
---------- Post added at 04:14 PM ---------- Previous post was at 04:05 PM ----------
As a last resort type thing, this is a one-click file from @rwilco12 to bring you back to stock unrooted NE5.

Ramer said:
Have you tried to odin the .tar version of Philz?
---------- Post added at 04:14 PM ---------- Previous post was at 04:05 PM ----------
As a last resort type thing, this is a one-click file from @rwilco12 to bring you back to stock unrooted NE5.
Click to expand...
Click to collapse
Yes, a previous version of Philz I can try this newer one though. I've also tried just TWRP. It's looking more and more like the weirdest brick I've ever heard of :-\.

Ramer said:
Have you tried to odin the .tar version of Philz?
---------- Post added at 04:14 PM ---------- Previous post was at 04:05 PM ----------
As a last resort type thing, this is a one-click file from @rwilco12 to bring you back to stock unrooted NE5.
Click to expand...
Click to collapse
Thanks for your attempted help , I actually ran both a NI3 and NE5 restore today . It would be safe to say I am not a noob at this stuff, I think I just got me a lemon :-\. I've been doing this for way too long now, I just don't get it.

jsmcmahon89 said:
Thanks for your attempted help , I actually ran both a NI3 and NE5 restore today . It would be safe to say I am not a noob at this stuff, I think I just got me a lemon :-\. I've been doing this for way too long now, I just don't get it.
Click to expand...
Click to collapse
It just seems to me that if you can get into Download Mode, it should be solvable. @tdunham, do you have anything to add that I didn't cover?

Try to do a phone reset with ##786# from the dialer. It's possible the phone cant authenticate with the network and that is why you're not getting signal.
I think this wipes internal storage but its worth a try to begin.
Next...
Pull the SD and the Sprint sim card.
Odin custom recovery and wipe absolutely everything including internal storage.
Power off the phone again, either from the recovery menu or battery pull.
Reinsert the sim card only, no SDcard, and do FULL factory Odin tar install, not the mini-bootloaders.
Let the rom boot fully but skip logging into Google and anything else and go straight into settings/backup and reset/factory reset.
Reboot again and see how it goes.
As a last resort you can try to re-pit (repartition) the phone but lets see how it goes from here.

tdunham said:
Try to do a phone reset with ##786# from the dialer. It's possible the phone cant authenticate with the network and that is why you're not getting signal.
I think this wipes internal storage but its worth a try to begin.
Next...
Pull the SD and the Sprint sim card.
Odin custom recovery and wipe absolutely everything including internal storage.
Power off the phone again, either from the recovery menu or battery pull.
Reinsert the sim card only, no SDcard, and do FULL factory Odin tar install, not the mini-bootloaders.
Let the rom boot fully but skip logging into Google and anything else and go straight into settings/backup and reset/factory reset.
Reboot again and see how it goes.
As a last resort you can try to re-pit (repartition) the phone but lets see how it goes from here.
Click to expand...
Click to collapse
I pulled the SD and Sim Card, and odin'd a custom recovery, but I cannot reach a custom recovery, just goes through the RECOVERY BOOTING.... boot loop explained in the OP. From there I've already done everything else close to 50 times now it just doesn't work.
When you go into settings/backup and restore/factory reset it's supposed to do something on it's own, mine just goes to recovery (ONLY IF STOCK RECOVERY IS INSTALLED OTHERWISE IT RECOVERY BOOTLOOPS) and the android guy falls over. It does not do the reset, I have to manually do it from stock recovery, but it doesn't seem to be helping.
Also, ##786# doesn't do anything. Neither does ##72786# as the Sprint rep was suggesting. My dialer (for one is lagging to all hell along with my keyboard) does not react, it just continues to show that #. This is on 100% stock too.

jsmcmahon89 said:
I pulled the SD and Sim Card, and odin'd a custom recovery, but I cannot reach a custom recovery, just goes through the RECOVERY BOOTING.... boot loop explained in the OP. From there I've already done everything else close to 50 times now it just doesn't work.
When you go into settings/backup and restore/factory reset it's supposed to do something on it's own, mine just goes to recovery (ONLY IF STOCK RECOVERY IS INSTALLED OTHERWISE IT RECOVERY BOOTLOOPS) and the android guy falls over. It does not do the reset, I have to manually do it from stock recovery, but it doesn't seem to be helping.
Also, ##786# doesn't do anything. Neither does ##72786# as the Sprint rep was suggesting. My dialer (for one is lagging to all hell along with my keyboard) does not react, it just continues to show that #. This is on 100% stock too.
Click to expand...
Click to collapse
It sounds like you corrupted your efs but I cant say for sure because I haven't seen it happen too often. You can always try to flash pit through odin and repartition. I'll attach the pit file in a zip so you can try it.

It seems like I would be more likely to have luck on Android L because at least when I flash that I have a phone that somewhat functions, I am missing a modem, and can not get one to stick at all, but I can at least connect to wifi, log into gmail accounts and do anything else. Where as on a stock 4.4 refresh I have a sick lag, it shows I have a modem but I am not provisioned for data, and sprint support is no help. They want me to bring my phone to a tech which is not something I am looking to do knowing I tripped the KNOX flag.

tdunham said:
It sounds like you corrupted your efs but I cant say for sure because I haven't seen it happen too often. You can always try to flash pit through odin and repartition. I'll attach the pit file in a zip so you can try it.
Click to expand...
Click to collapse
I odin'd that pit and tried to start fresh, no luck. I can't thank you guys enough for your continued effort
Edit: I am reading this post http://forum.xda-developers.com/showthread.php?t=2610757
I have never used the Nand Erase All or Phone EFS Clear options in Odin, but this seems like it might help?
2nd Edit: After flashing the PIT file with NE5 stock rom I achieved data. Now I have an incredibly laggy stock rom, which might just have to do for now, because I still can't get to a custom recovery.
I did not use Nand Erase All or Phone EFS Clear, but am still very interested.

Realized a new issue today. My phone will only charge when off. Still open to suggestions.

Im haveing the exact same issue you are and no clue what to do about it.

Wow I must be lucky all I did was a battery pull and my phone worked again (back when I was on moar 5.0) (i haven't encountered it on moar 6.1)
Sent from my SM-G900P

gtuansdiamm said:
Wow I must be lucky all I did was a battery pull and my phone worked again (back when I was on moar 5.0) (i haven't encountered it on moar 6.1)
Sent from my SM-G900P
Click to expand...
Click to collapse
I don't think you are haveing the same issues we are.

I had similar happen to me and the only thing that fixed it was to go back to the first stock, ND2 I think and work my way back up. It happened to me on NKD also, not sure if it was the same exact thing but sounds close. IIRC after flashing back to the first stock ROM thing started working but prior to that I Odin flashed every package that came with a pit file.

miked63017 said:
I had similar happen to me and the only thing that fixed it was to go back to the first stock, ND2 I think and work my way back up. It happened to me on NKD also, not sure if it was the same exact thing but sounds close. IIRC after flashing back to the first stock ROM thing started working but prior to that I Odin flashed every package that came with a pit file.
Click to expand...
Click to collapse
i was on nkd last i could remember but as far as know you cant downgrade the bootloader.

jackrabbit72380 said:
I don't think you are haveing the same issues we are.
Click to expand...
Click to collapse
well back when i had the issue id randomly take out my phone from my pocket and see it stuck on a screen that said upload mode modem crashed
lets hope that there isnt a second issue out there as well
back then it was a 50/50 shot doing a battery pull and getting the phone to boot
sometimes even while i had charge i would have to plug phone into a power supply and then try turning it on
but regardless i wish you guys best of luck

jackrabbit72380 said:
i was on nkd last i could remember but as far as know you cant downgrade the bootloader.
Click to expand...
Click to collapse
Downgrade on the sprint s5 is possible with Odin, no negative side effects. FWIW theres a few threads around too that back this statement.