Can't get past CM boot screen. - T-Mobile Samsung Galaxy S II SGH-T989

So tonight I rooted my phone and decided to download CyanogenMod to it. I created a backup of my phones current install, wiped/reformatted, and installed the latest stable release of CyanogenMod from their website (version 10.2.0). I followed the instructions on CyanogenMod's website for installing from recovery since Heimdall isn't supporting right now. Everything went great, said my radio was recent enough, installed with no issues. I go to reboot and I just got the spinning arrow for ages, won't load. Any ideas? Thanks in advance.

Grrr.. and now, when I try to restore my backup, my phone won't boot. It either crashes on the boot screen and turns off, or I get stuck in a "boot loop" where it just reboots over and over and over but never gets past the splash screen. Ideas?

IntoxicatingToxin said:
Grrr.. and now, when I try to restore my backup, my phone won't boot. It either crashes on the boot screen and turns off, or I get stuck in a "boot loop" where it just reboots over and over and over but never gets past the splash screen. Ideas?
Click to expand...
Click to collapse
I and a bunch people are going through the same. We're waiting for someone who comes up with a solution.

tpag02 said:
I and a bunch people are going through the same. We're waiting for someone who comes up with a solution.
Click to expand...
Click to collapse
Well, it's good to know I'm not alone I suppose, but this is frustrating - I don't have a backup phone. :/ Going through an alternate method to try and restore my phone to stock settings - stock is way better than no phone. Lol.

If it vibrates and restarts over and over until you remove the battery. It's a bad power button. I had it happen to me. I unsoldered the button off for now. It stays on now i have a touch recovery and use volume to wake and a tile to sleep.

xj0nx said:
If it vibrates and restarts over and over until you remove the battery. It's a bad power button. I had it happen to me. I unsoldered the button off for now. It stays on now i have a touch recovery and use volume to wake and a tile to sleep.
Click to expand...
Click to collapse
It's only a bad power button when I try to flash CyanogenMod, then. I found a way to revert back to stock and my phone is fine.

IntoxicatingToxin said:
It's only a bad power button when I try to flash CyanogenMod, then. I found a way to revert back to stock and my phone is fine.
Click to expand...
Click to collapse
That makes no sense. It definitely isn't a bad power button because it works just fine with stock.

Related

Galaxy Nexus in reboot cycle

Hi
My Galaxy Nexus has just started into a constant reboot cycle. The Google logo comes up and the the multi coloured animation thing like normal and then it goes back to beginning.
I never get to enter my pin or anything.
Has this happened anybody else?
It also gets quite hot after been in reboot phase for 20-30 mins.
Thanks
Brian
Need more details: what ROM/kernel you're using? Do you have ClockWork Recovery installed? What did you do to your phone before this happened?
Sent from my Galaxy Nexus using xda premium
MS. said:
Need more details: what ROM/kernel you're using? Do you have ClockWork Recovery installed? What did you do to your phone before this happened?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Im not sure on exact details other than its as it was when I bought it apart from 4.0.2 is installed
I didnt root it or change radio etc
I was just using it as normal, was going in to check battery level I think
ClockWork isnt installed
If I hold down power button and volume button and go into recovery options reocovery mode doesnt work, restart bootloader doesnt help either
Only other options I have are Start and Power off
When I try and go back into those options again all I get is a screen with green Android and Start > Downloading > Do not turn off target
It can stay in this screen for 5 mins or more and go nowhere
This happened earlier on as well so I just turned it off
I tried the same procedure again and I got the recovery menu again but it still didnt work and then tried it again and I just got the Downloading message again
Not sure if any of that helps, I cant check the kernel version anywhere right now.
Oh and its the GSM release of the Nexus
bmulvany said:
Im not sure on exact details other than its as it was when I bought it apart from 4.0.2 is installed
I didnt root it or change radio etc
I was just using it as normal, was going in to check battery level I think
ClockWork isnt installed
If I hold down power button and volume button and go into recovery options reocovery mode doesnt work, restart bootloader doesnt help either
Only other options I have are Start and Power off
When I try and go back into those options again all I get is a screen with green Android and Start > Downloading > Do not turn off target
It can stay in this screen for 5 mins or more and go nowhere
This happened earlier on as well so I just turned it off
I tried the same procedure again and I got the recovery menu again but it still didnt work and then tried it again and I just got the Downloading message again
Not sure if any of that helps, I cant check the kernel version anywhere right now.
Oh and its the GSM release of the Nexus
Click to expand...
Click to collapse
Try removing the battery and then turn it on, works for me; have you installed some new apps before this happened?
quiro91 said:
Try removing the battery and then turn it on, works for me; have you installed some new apps before this happened?
Click to expand...
Click to collapse
have tried that several times
installed nothing new in last few days but even if I did I have no way of getting in to uninstall it if thats what was causing the issue
bmulvany said:
have tried that several times
installed nothing new in last few days but even if I did I have no way of getting in to uninstall it if thats what was causing the issue
Click to expand...
Click to collapse
and you can't remove the battery and then boot in recovery mode? are you sure?
quiro91 said:
and you can't remove the battery and then boot in recovery mode? are you sure?
Click to expand...
Click to collapse
I choose recovery mode and the phone restarts, Google logo comes up and it then goes to a picture of android robot with a red excamation mark over it
It just stays there on that screen for about 2-3 minutes and then retarts
After restarting it goes through sme sequence as before constantly going from Google Logo to multi coloured animation and then restarts again. At no stage do I get to login screen.
Only other option I get when I hold down power button and volume button is to restart bootloader, start and power off.
bmulvany said:
I choose recovery mode and the phone restarts, Google logo comes up and it then goes to a picture of android robot with a red excamation mark over it
It just stays there on that screen for about 2-3 minutes and then retarts
After restarting it goes through sme sequence as before constantly going from Google Logo to multi coloured animation and then restarts again. At no stage do I get to login screen.
Only other option I get when I hold down power button and volume button is to restart bootloader, start and power off.
Click to expand...
Click to collapse
try this, from step 4:
http://forum.xda-developers.com/showthread.php?t=1366806
it should work
quiro91 said:
try this, from step 4:
http://forum.xda-developers.com/showthread.php?t=1366806
it should work
Click to expand...
Click to collapse
that worked thanks
the hardest part was getting my laptop to pick up my phone in bootloader mode but my laptop is getting old and on its last legs, the usb ports are dodgy for everything
Just to warn you, there's a good chance it will happen again eventually. A few days ago it happened to me for the second time (completely stock).
I decided this time to root it and install a custom rom seeing as how I'd have to flash stock again anyway. I'm hoping that whatever bug that caused it has been fixed in 4.0.3.
case0 said:
Just to warn you, there's a good chance it will happen again eventually. A few days ago it happened to me for the second time (completely stock).
I decided this time to root it and install a custom rom seeing as how I'd have to flash stock again anyway. I'm hoping that whatever bug that caused it has been fixed in 4.0.3.
Click to expand...
Click to collapse
how often has this happened to you where the phone goes into reboot cycle?
are you on 4.0.2 as well I assume its the gsm phone as well?
its handy to sort but a pain in the whole having to install all the apps again
bmulvany said:
how often has this happened to you where the phone goes into reboot cycle?
are you on 4.0.2 as well I assume its the gsm phone as well?
its handy to sort but a pain in the whole having to install all the apps again
Click to expand...
Click to collapse
The first time it happened was the 11th Jan, on 4.0.1, and the second time was the 29th Feb, on 4.0.2. And yeh it's GSM.
Yeh exactly, sucks having to install apps again etc. Now I'm rooted I've got a nandroid backup just in case it happens again.

CM10 Boot Loop? Help!

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.

SGH-I747 Won't Boot After 4.3 Update

I've been looking on multiple other threads for the last few days now but haven't found a fix. I updated my S3 from 4.1.2 to 4.3 through the phone(AT&T recommended update) and it worked for 4 days but was very glitchy. Then it shut off one day with 50% battery and wouldn't turn back on. I tried pulling the battery and turning it on but it would generally fail after it reached the galaxy s3 logo. Can't stay in download mode or recovery mode without it crashing. I sometimes I found that if I leave the battery out for an over 4-5 hours, it can get it to boot and reach my home screen but it soon crashes. Any help would be greatly appreciated since I have been without a phone for about a week. Thank you.
Can you do a factory reset in recovery mode? Not sure if you phone will stay on long enough.
audit13 said:
Can you do a factory reset in recovery mode? Not sure if you phone will stay on long enough.
Click to expand...
Click to collapse
Unfortunately no, the phone doesn't stay on long enough. And I've tried with and without the phone plugged into a charger or my computer but neither really help.
Any warranty left on your phone? If not, you could try flashing a custom recovery in Odin if the phone will stay in download mode, then wipe data, cache from the custom recovery.
audit13 said:
Any warranty left on your phone? If not, you could try flashing a custom recovery in Odin if the phone will stay in download mode, then wipe data, cache from the custom recovery.
Click to expand...
Click to collapse
No I'm pretty sure the warranty is ended since I've had the phone for about a year and 3 months and don't have any insurance through AT&T. How would I go about flashing a custom recovery? Is there a link to a tutorial you could refer me to? Just in case I could get the phone to stay in download mode long enough. Thanks for all your help by the way. I really appreciate it.
Okay. Download the tar version of Philz Touch Recovery from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Install it using Odin by selecting pda and browsing to where you saved the CWM file. Flash it, go into recovery, and wipe.
Good luck. Let me know how it goes.
audit13 said:
Okay. Download the tar version of Philz Touch Recovery from here: url
Install it using Odin by selecting pda and browsing to where you saved the CWM file. Flash it, go into recovery, and wipe.
Good luck. Let me know how it goes.
Click to expand...
Click to collapse
The flash worked and now my phone is staying in recovery. It got into recovery mode and did a factory reset. Now I started up and I started setting up my phone (wifi, google account..) but it crashed multiple times during that setup time. I haven't reached the home screen yet. Occasionally it will boot loop once or twice before reaching the setup again......
So I finally got to the home screen and it crashed (after about 7-8 crashes and reboots). Could it be 4.3 or maybe a hardware problem?
Could be either but let's assume it is an OS issue. Did you flash a custom rom?
audit13 said:
Could be either but let's assume it is an OS issue. Did you flash a custom rom?
Click to expand...
Click to collapse
No I didn't, I don't know of one that I should flash? Recommendations?
Also, my phone was just on for about 8 minutes and was working. I noticed that my power/lock button was extremely touchy and i would barely have to touch(not press it) to lock it. If I press it (like I use to to lock it, it pulls up the power off/options and if I don't do anything about it, it will shut off and restart(boot loop) until i pull the battery and turn it on myself. So I think it might be a problem with the power button being too touchy that it just turns off. Do you know if there is a way to disable the power button?
I run Cyanfox on my brother's S3 and it's pretty stable: http://forum.xda-developers.com/showthread.php?t=2480007
Yes, the power button could be causing the problem. Sounds like the power connection and/or board may be defective.
audit13 said:
I run Cyanfox on my brother's S3 and it's pretty stable:url
Yes, the power button could be causing the problem. Sounds like the power connection and/or board may be defective.
Click to expand...
Click to collapse
Alright I will try to see if I can get that to work. Now the phone is rarely making it to the home screen and if it does, it only stays for at most a minute. Generally it's back to it only getting to the initial Samsung logo.
Is this with the stock ROM?
audit13 said:
Is this with the stock ROM?
Click to expand...
Click to collapse
Yeah it is. All stock.The only change that I made recently was the firmware update to 4.3.
Okay, definitely try Cyanfox to see what happens.
audit13 said:
Okay, definitely try Cyanfox to see what happens.
Click to expand...
Click to collapse
Okay, I'm reading instructions and it says the one of the prerequisites is to have the phone rooted. Is that really the case?
No need to be rooted. You can just flash it in recovery.
audit13 said:
No need to be rooted. You can just flash it in recovery.
Click to expand...
Click to collapse
Alright well it worked right off the bat for about 15 minutes and then crashed. Now it is doing the same sort of thing it was before. It will rarely make it to the home screen but typically just crashes before it gets there. It will crash and then only sometimes turn on when I press the power button. Other times I have to pull the battery and occasionally it will boot loop once or twice.
I think the power button is now the issue.

[Q] S3 (I747) Powering off During Boot

Started two days ago. Phone would randomly power off and boot back up. Finally it shut off and would not power back on. I had Cm11 installed with CWM 4.0.4.6. The phone powers on after inserting the battery. The Samsung logo flashes and then it shows the "Galaxy S3" logo with the CM logo below it. The phone the powers off. I have done a factory reset, cleared both caches, formatted the system folder, flashed SlimKat from recovery and tried another known good battery. At this point I figured I would reflash CWM but if I put the phone into download mode, it powers off after just a few seconds as well.
If I boot the phone into CWM, the phone stays on as long as I want it to so it makes me think this might be fixable. Just need some help.
Except for recovery working, it sounds like the power button sticking. If you remove/replace the battery does it power on automatically? If so its definitely the power button.
Otherwise, let us know what firmware you are currently running on. Maybe reflashing in recovery could help.
DocHoliday77 said:
Except for recovery working, it sounds like the power button sticking. If you remove/replace the battery does it power on automatically? If so its definitely the power button.
Otherwise, let us know what firmware you are currently running on. Maybe reflashing in recovery could help.
Click to expand...
Click to collapse
It does power on automatically. Makes perfect sense that it is the power button. Is this repairable or replaceable? I start Googling around for power button issues.
Im currently running CWM 6.0.4.6 and SlimKat. SlimKat was only installed cause I thought CM 11 was the issue. At this point I would just like to get the phone to a point where I could sell it.
kylelever said:
It does power on automatically. Makes perfect sense that it is the power button. Is this repairable or replaceable? I start Googling around for power button issues.
Im currently running CWM 6.0.4.6 and SlimKat. SlimKat was only installed cause I thought CM 11 was the issue. At this point I would just like to get the phone to a point where I could sell it.
Click to expand...
Click to collapse
It can be replaced fairly easily, just look it up on youtube.
You can buy the part off Ebay (or any other site you might prefer) for fairly cheap.

CM 13 stuck at Reboot animation. Help please!

It's been stuck at this loading screen for hours. Are there any ways out of this? I cant power off nor can I connect it to my PC. It always rebooted perfectly until I flashed the 5.0 version of ElementalX. Then this happened. Hope to hear some input asap as I'm trying my best not to panic. No other kernels are on here except for micro gapp and CM 13. I would remove the battery pack, but might as well get a new phone at that point. I would post a picture but I'm a new user so I'm restricted. Thanks!
legitbeans said:
It's been stuck at this loading screen for hours. Are there any ways out of this? I cant power off nor can I connect it to my PC.
would remove the battery pack, but might as well get a new phone at that point.
Click to expand...
Click to collapse
No need to do a battery pull on this phone, as you know is not really feasible. HTC has already thought that out, and built-in a hardwired button combo that does the same thing. Hold power button+ vol up until the phone reboots (may take a minute or so in the current condition). The moment the screen goes dark to reboot, slide your finger from vol up, to vol down (no need to keep holding power button at this point) and don't let go until the bootloader screen appears. From there, you can boot recovery, connect fastboot, etc.
If the button sequence above fails, its virtually always due to getting the timing wrong, either not pressing vol down soon enough, or letting go too early. Either of which, will result in trying to boot normally (not bootloader) which in your case puts you back stuck on the loading screen. Just repeat until you get it right.
Although, at this point, your battery may have just run out. In which case, you should be able to charge, and just hold power+vol down to boot directly into bootloader.
legitbeans said:
It always rebooted perfectly until I flashed the 5.0 version of ElementalX.
Click to expand...
Click to collapse
Here was your mistake. ElementalX is only for Sense and GPE ROMs, it doesn't work on AOSP ROMs like CM13.
Once you get booted into recovery, you should be able to dirty flash CM13 to re-install the CM kernel, then reboot. Or at the worst, wipe, flash CM13 and gapps again.

Categories

Resources