I've got a sprint GS3 that is rooted and has the clockwork recovery mod on it, but was otherwise running stock OS. It had been acting up, hanging, that kind of thing so I decided to go ahead and accept the download new software prompt I've had for the last year or so. When it went to the bootimage(?) menu it asked if I wanted to install this untrusted image. That gave me pause, so I selected no. The little android icon got a red X-ish thing on it's chest and it rebooted. And sat at the samsung galaxy s3 screen for about a half an hour. I pulled the power and it kept going between hanging at that screen, or hanging at random points (app 6, 8, 9, 11) of an "upgrading android" screen I have never seen before. I tried going into the recovery mode but when I follow the instructions (up vol, home and power, when it vibrates for power release the power button) but that doesn't work at all. It just sits there. I'm 100% certain it's not a button/physical issue. I decided to try the download option and can get to a screen that warns me about custom rom. I've tried both installing (let it go for over an hour, gave up) and hitting cancel, to no avail. Before I take this as a sign from the android gods that it's time to go get a GS5, does anyone have any ideas/advice? TIA.
Wrong section.. Report it yourself and adj a mod to move it to correct section..
Sent from my GT-I9300 using xda app-developers app
Have you tried to plug the phone in with the USB cable into the computer?
Related
Flashed a new kernel with aokp jb with the lastest update, and when I went to fix permission it look an accessive amount of time so I waited and waited until I restarted the phone. Now the phone just boot loops, as soon as it hits the aokp animation. Held down the menu and volume button on boot and it brought me to an area where if I press the volume up button I can "install a customer os" then it brings me to "ODIN MODE" and has the andriod dude pic and says downloading do not turn off target..... however it just hangs there and hasn't done anything past that point.. Any ideas?
You need to hold menu and vol+
Sent from my SGH-I747 using xda premium
Steve_Maio said:
Flashed a new kernel with aokp jb with the lastest update, and when I went to fix permission it look an accessive amount of time so I waited and waited until I restarted the phone. Now the phone just boot loops, as soon as it hits the aokp animation. Held down the menu and volume button on boot and it brought me to an area where if I press the volume up button I can "install a customer os" then it brings me to "ODIN MODE" and has the andriod dude pic and says downloading do not turn off target..... however it just hangs there and hasn't done anything past that point.. Any ideas?
Click to expand...
Click to collapse
vol + and menu for recovery mode
vol - and menu for download mode
if fixing the permissions don't fix the problem, check if you pick a kernel for ICS or JB. If you have the right kernel, perform a full wipe and flash your rom again and see if it boots.
Reinstall aokp and full wipe. Let it boot once before installing a custom kernel. Its a common occurrence and a known "problem." Just let it boot once as stock aokp and you should be fine.
partial boot, power off
I have a similar problem, I have an At&t samsung galaxy s3 I had flashed a Rom that I didn't like and was restoring from previous back up, I didnt want to re load all the apps and data I had on that restore as I was running low on device memory so I went to "advanced restore" and there were 4 options to choose, I chose the top option. I don't recall what it is because I cant get into recovery now doing the menu volume+ or using the jig I have to get into Download mode and start over completely. When I power on it flashed Samsung, then Samsung galaxy s3 then screen goes black and powers off. I am assuming when I chose the 1st option I restored the OS but not the bootloaders. I have read previously how to load them from the sd card but can't find that post. Any help would be greatly appreciated.
I rooted my phone to a stock root on my Jelly Bean Galaxy S3. I then installed ClockworkMod through ROM Manager, then CM10. It installed OK, now stuck in a boot loop. No big deal, I'll reinstall to my Kies backup. Doesn't work, I can't seem to get into recovery mode. I hold the buttons, it vibrates, and the screen stays black until I let go at which point it boots to that horrendous boot loop. I really need my phone back!
P.S. Please explain as if I am five years old.
Flightfreak said:
I rooted my phone to a stock root on my Jelly Bean Galaxy S3. I then installed ClockworkMod through ROM Manager, then CM10. It installed OK, now stuck in a boot loop. No big deal, I'll reinstall to my Kies backup. Doesn't work, I can't seem to get into recovery mode. I hold the buttons, it vibrates, and the screen stays black until I let go at which point it boots to that horrendous boot loop. I really need my phone back!
P.S. Please explain as if I am five years old.
Click to expand...
Click to collapse
Download mode couldnt get any simpler bud
Edit: just incase if you dont know its down home power button to get to it, find your galaxy s3 firnware (ATT/Bell etc...) and your back stock nonrooted. And then you can root againif you wanna
While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.
mrhaley30705 said:
While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.
Click to expand...
Click to collapse
Did you read the question bro.. he said he CAN'T go to recovery mode only other option is download mode
No, the option is to boot into recovery and perform a factory reset (which may fix his problem). IF that doesn't fix his problem, he can flash a different ROM from recovery, provided he had custom recovery.
The only difference in getting to download as opposed to recovery is which volume button you use. Chances are if he can't 3 button into recovery, download will be the same result.
Thanks
Got it fixed guys, thanks for the help, now I'm back at Stock Rooted 4.1.1, but am still on the quest for a deodexed rom!
Excellent suggestion - it worked for me
mrhaley30705 said:
While in a boot loop, hold the buttons. The phone will power off and stay off as long as you hold them down. Let go of all three, then immediately press all 3 again. When you see a little blue line of letters on the top left of your screen, let go again. Should boot into recovery from there.
Click to expand...
Click to collapse
I got a Galaxy S III on 23rd Dec 2012 with Ice Cream Sandwich installed. A couple of weeks later it updated itself with a little help from me to the latest Jelly Bean. Since then it's gone into the reboot loop 3 times without any provocation; i.e. I get it out of my pocket and it's in a reboot loop but it had been fine the last time I used it. I tried pressing various buttons alone and in combination and eventually it came out of the loop. At no time did I have to remove the battery. The only mod I've made to it is the addition of a 64GByte SD card, apart from the upgrade to Jelly Bean. I've seen many posts on this problem but yours is the first that confirms my solution for getting out of it. It's obviously a common problem so somewhere there must be a description of what causes it and, hopefully, how to prevent it as it's a real nuisance when you want to use your phone and it's in a reboot loop. If and when I find a definitive article I'll post here again.
Thanks MrHaley.
Hey everyone,
My phone won't boot, go into recovery or go into download mode. I was on FrostyJB but was going to change to a 4.2 ROM, so I was going through my normal backup process. I set Titanium Backup to backup all apps and then left it for a while. When I came back later to pick up my phone I checked the lock screen for the time but did not unlock it. About 10 minutes after this I attempted to wake my phone, but it would not respond. I pulled the battery and attempted to reboot it. The soft keys lit up but the screen stayed black. When I try to put it into download mode it just vibrates occasionally. I was switching ROMs also due to the fact that my phone was filled up with "system data" and I needed the storage for my trip to Colorado in approximately 6 hours now. Any help is greatly appreciated and if its not too much trouble please respond quickly because I'd like to have a working phone during my trip.
Thanks in advance!
Ok, so I've managed to connect it to Odin by pressing the buttons blindly (the screen never lit up). I flashed a new recovery and rebooted it but no cigar. I assume my screen is broken somehow. I guess I'll take it to a Tmo store when I get back from vacation, it's a shame I won't have it for the trip >.<
Did you try pressing volume up + power + home key to get into recovery? Also if the soft keys lit up while trying to get into download mode then it may still be in download mode even though the screen is black. That can happen due to various things. To be sure I would connect it to a pc and see if Odin can identify it. If so then you can try flashing it back to stock and see if that makes any difference.
Sent from my SGH-T999 using xda premium
I just had very similar situation backing up system on TWRP (fell asleep and phone completely discharged while in recovery).
1)Open ODIN on PC,
2)Pull battery out of phone.
3)Connect phone to pc w/ usb
4) Put battery in
5) hold down volume, home button and power button
6) Took me immediately into download mode
..good luck
Sent from my SGH-T999 using xda app-developers app
So, my Galaxy S3 suddenly shut off on me, so I tried to reboot it, and it would just say "Galaxy s3" then nothing would show. So I figured it was a software brick and I can just restore a backup. When I tried to access Recovery Mode, it would show that its trying to boot into Recovery, but nothing would happen. So I figured I can just go into Download Mode and restore it through ODIN to get all the partitions working again. It would go to Download Mode for a few seconds, and then just shut off on me before I can even do anything. Everytime I take out the battery and put it back in, it tries to auto boot, but it never gets passed the Samsung s3 logo. Do you think this is a software or hardware brick? And would any of you know how I should go about fixing this?
Thanks a bunch
neim81094 said:
So, my Galaxy S3 suddenly shut off on me, so I tried to reboot it, and it would just say "Galaxy s3" then nothing would show. So I figured it was a software brick and I can just restore a backup. When I tried to access Recovery Mode, it would show that its trying to boot into Recovery, but nothing would happen. So I figured I can just go into Download Mode and restore it through ODIN to get all the partitions working again. It would go to Download Mode for a few seconds, and then just shut off on me before I can even do anything. Everytime I take out the battery and put it back in, it tries to auto boot, but it never gets passed the Samsung s3 logo. Do you think this is a software or hardware brick? And would any of you know how I should go about fixing this?
Thanks a bunch
Click to expand...
Click to collapse
i think the problem is on power button...
if the power button press contiues will be like that
i meet the same case like u...
sory my englis
press thanks if i help...
I agree, the only way it should turn on when you replace the battery is if power was held down. It would explain everything else you mentioned as well. Try gently knocking it back out. Or if comfortable with it, open the device to have a closer kook.
Sent from my SCH-I535 using Tapatalk 4
DocHoliday77 said:
I agree, the only way it should turn on when you replace the battery is if power was held down. It would explain everything else you mentioned as well. Try gently knocking it back out. Or if comfortable with it, open the device to have a closer kook.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
It just turned on, I guess it was the power button.
Sent from my SGH-T999 using xda app-developers app
i'm experiencing a similar issue. I can only get any result while it's plugged in. it wont boot past the second splash screen, I got it into download mode and flashed the stock package from sammobile.com with no change. the phone keeps trying to boot into recovery after flashing stock but it goes to the android with the open chest screen and reboots and tries again over and over. i've taken the phone apart and seen nothing wrong, no corrosion, no water damage and i've even replaced the battery with no success. i tried flashing clockworkmod recovery, the flash was successful but it still wont even boot to recovery. the power button isnt stuck, i can manipulate it when i have the bare motherboard in my hands and still it's fine. would replacing the power switch have any affect? please any thoughts would be appreciated
edit: since flashing stock, plugging the phone into the computer with oem cable causes it to vibrate intermittently. holding power causes it to try recovery mode. running windows 7 with samsung drivers properly installed and adb recognizes my galaxy s2 and captivate no problems. someone mentioned on a post i read about using a 3 part stock rom, modem, pda and phone to flash instead of the all in one tar file, any thoughts?
another edit. this phone has never to my knowledge been rooted or had any kernel/rom flashed onto it. as far as i know it's stock from Wind mobile, 3 months past warranty
I've dug around trying to find a similar problem here and on google, so my apologies if this has already been addressed.
The problem originally began when the game pad stopped being responsive (or at times took multiple presses to get a response) and after no luck troubleshooting it, I tried to reset from clockwork recovery.
Ever since my phone no longer boots. It just sits on the LUPUS wolf logo (I do not recall exactly which rom I am running, but I hope this helps) and at first I thought it was your normal "this can take a bit" first boot, but I've let it eat the whole battery and it never gets anywhere. I've tried to prompt the phone to boot into both custom recovery and d/l mode and neither get me anywhere. Any suggestions?
Sacrifusion said:
I've dug around trying to find a similar problem here and on google, so my apologies if this has already been addressed.
The problem originally began when the game pad stopped being responsive (or at times took multiple presses to get a response) and after no luck troubleshooting it, I tried to reset from clockwork recovery.
Ever since my phone no longer boots. It just sits on the LUPUS wolf logo (I do not recall exactly which rom I am running, but I hope this helps) and at first I thought it was your normal "this can take a bit" first boot, but I've let it eat the whole battery and it never gets anywhere. I've tried to prompt the phone to boot into both custom recovery and d/l mode and neither get me anywhere. Any suggestions?
Click to expand...
Click to collapse
IMHO, it looks like faulty slider flex cable (exact same situation i had, but i was able to enter recovery after 2 minutes of logo on screen)
Try to power on phone with slider open.
If you can enter in recovery mode with "volume -" (if it light blue led or vibrate) and see is d-pad is working.
Sorry for the delayed reply. The notification went into my spam folder :/
Alright, I followed your steps in two ways. I opened the slider and held both the power and the volume down till I got the buzz buzz and the LED blinked green once and continued to hold volume down till I got the LUPUS logo. No luck. I did mostly the same thing the second time but I held the volume down for 3 minutes with the same result. I still have yet to make it back into recovery.
Sacrifusion said:
Sorry for the delayed reply. The notification went into my spam folder :/
Alright, I followed your steps in two ways. I opened the slider and held both the power and the volume down till I got the buzz buzz and the LED blinked green once and continued to hold volume down till I got the LUPUS logo. No luck. I did mostly the same thing the second time but I held the volume down for 3 minutes with the same result. I still have yet to make it back into recovery.
Click to expand...
Click to collapse
To be able to enter recovery, it is not "holding volume-" while powering on phone or keeping it pressed.
Press power button (and it should vibrate), and release it.
When blue led is on press and release vol- button many times untill you enter recovery (don't keep it pressed all time)
Ah, you are absolutely right. I've never entered recovery like that on another Android before. I loaded up the "near perfect" rom and my game pad seems to be working for now, so it appears I am back in business.
How problematic is it if my slider flex cable is going bad? Will it permanently fail eventually?