Database Info

[Q] Samsung Galaxy S2 Skyrocket - Bootloop

Hi,
So my SGS2 Skyrocket is stuck in a boot loop. I've have the Sky Icecream Sandwich ROM installed for a few months now, and haven't changed anything recently.
What is happening is my phone with vibrate every 2-3 seconds with a blank screen. When I take out the battery/power source, and put it back in, the phone shows the Samsung splash (not the Android splash) for a few seconds, then goes blank and does the vibrating again.
I've tried plugging it into the computer, but the power it gets from USB turns it on and into the boot loop, so I can't get it into any kind of recovery mode. I also tried the Vol+Home+Power key combo, with nothing.
Any idea what could cause this/what the course of action should be? Thanks!

Turn phone on and wait 2 hours. If it wont work do what you use to do when you booting recovery mode. (home screen i guess). But hold it longer.
Good luck

nathan-96, do you have any idea what caused this? Because what's concerning me is that it's not getting past the Samsung icon (before android starts actually booting).
When you say turn it on, do you mean just put in the battery? Because the loop starts right when I put the battery in, it doesn't wait for me to press anything.

No, I meant turning it on. Hold centre button and put battery in. Just hold it for a moment. Hopefully you will reach recovery.
Sent from my GT-S5660 using xda premium

Can you access download mode instead of recovery? If so you could try re flashing something with Odin...
Definitely try getting the battery out for a few minutes and boot the phone while maintaining the combination to enter recovery
Sent from my GT-I9100 using xda premium

boot loop samsung galaxy s2 skyrocket
nathan-96 said:
Turn phone on and wait 2 hours. If it wont work do what you use to do when you booting recovery mode. (home screen i guess). But hold it longer.
Good luck
Click to expand...
Click to collapse
so i have a question, im having the same problem (obviously) but my cwm wont work and says something about md5 check sum and verfication? i dont know what the problem is but if the 2 hour thing doesnt work i at least need cmw to work so i can then at least install my custom rom to have my phone working. can you help? thanks

Possible a bad download...
You have CWM on your phone? Have you visited the forum for your device?
http://forum.xda-developers.com/forumdisplay.php?f=1399
technologic337 said:
so i have a question, im having the same problem (obviously) but my cwm wont work and says something about md5 check sum and verfication? i dont know what the problem is but if the 2 hour thing doesnt work i at least need cmw to work so i can then at least install my custom rom to have my phone working. can you help? thanks
Click to expand...
Click to collapse

AT&T Skyrocket BOOT LOOP Cyanongenmod 10
Hi ,
I´am playing with my Skyrocket to run the Cyanogenmod 10 and always I got stuck at Boot Loop .
This is what I have and did :
- Running AT&T Stock ICS 4.0.4 UCFL6 rooted ( I have a back up of this)
- CWM 6.0.1
- Cyanogenmod 10 Nightly Dec 07 , but I also tried with Cyanogenmod 10 Stable
- Gapps
- Factory Reset / wipe cache
- Wipe dalvik
- Mount/storage format system
- install using CWM Cyanogenmod
- install using CWM gapps
- Mount/ storage format cache
- reboot
I also tried to wipe twice as other threads say.
So I´am still with the boot loop
I returned my backup to the ICS ...
Thanks in advance !!!

Skyrocket Bootloop
Whats happening is the power button acts as if its being pressed. Thats why you have the bootloop and the phone turns on as soon as you put the battery in.
Try repeating pressing the power button or hold the power button without the battery for a few seconds. :fingers-crossed:

[Q] strange boot behavior

I had the Photon Q with the SIM mod and CM 9 working for 2 mouth. But yesterday, I were using the cellphone when it reboot itself and get freeze on the unlocked bootloader warning. I try to power it of but y could not, the I let it there until batery drain (about 4 hours)
Now when I boot the cellphone it has an strange behavior. Some times it freeze on the unlocked bootloader warning, other time make a loop boot (show the warning and restart). Also some times it display strange colors on the screen when try to boot and many times it display a randomly sorted grey vertical lines and very few times (one of every 50 times) it boot the ROM but when i touch the screen it goes black.
i can not conect to phone by adb and can not enter recovery, but i can access to the fastboot (in fact the fast boot is working but do not display anything on the screen, i suppouse that the same happend with the recovery. but i can not use it if the screen is black)
I used the fastboot and RSD to flash the stock firmware, the phone return fail on every 4.0.4 ROM but it work with the 4.1.2. After the flash some times thes phone display the morotola and sprint logo and then start the handfree configuration, but when I touch the screen it goes to black again.
I do not know if it is bricked, I think that if i have access to the fastboot i can resurrect the phone. but is very strange the random behavior.
Do you have any idea what should I do?
Thanks.
PS: sorry for my bad english

Re-Strange behaviour
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.

schmandroid said:
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
Click to expand...
Click to collapse
I tried it, but do not work.
I flash the stock ROM from fastboot and also flash several recoverys, but never boot any ROM and I think that i access to the recoverys but the screen is black then is very dificult to use it. Is strange beacouse some times screen displays perfect the unlocked bootloader warning, but never display anything on the fastboot or the recovery.
Witch part of the software have the video drivers that are used on the recovery and fastboot? I think that maybe is corrupted. how can i flash it again?
Thanks.

[Q] Need help galaxy s2 i9100 boot loop and freezing

Hello I am searching for help. The problem is that my galaxy s2 i9100 stopped working properly. It started like this maybe I took out the battery or something I don't remember and then I turned it on the phone wouldn't boot. I thought maybe my android operation system got bricked so I decided to re flash it but as I can remember the phone wouldn't go in to download mode but some how I managed to reflash the firmware but then phone booted it just froze and then I pressed lock button the phone screen would go black and reboot. After installing cyanogen mode 11 the phone would boot and it could be used again until pressed the lock button it would go black and reboot so I have been reading forums and found problems like boot loop corrupted mmc or something else corrupted and I don't know what the real problem is because the symptoms are like boot loop or corrupted mmc or soft brick. I have already tried other kernels other android versions clock work mode

migimantas said:
Hello I am searching for help. The problem is that my galaxy s2 i9100 stopped working properly. It started like this maybe I took out the battery or something I don't remember and then I turned it on the phone wouldn't boot. I thought maybe my android operation system got bricked so I decided to re flash it but as I can remember the phone wouldn't go in to download mode but some how I managed to reflash the firmware but then phone booted it just froze and then I pressed lock button the phone screen would go black and reboot. After installing cyanogen mode 11 the phone would boot and it could be used again until pressed the lock button it would go black and reboot so I have been reading forums and found problems like boot loop corrupted mmc or something else corrupted and I don't know what the real problem is because the symptoms are like boot loop or corrupted mmc or soft brick. I have already tried other kernels other android versions clock work mode
Click to expand...
Click to collapse
I have found that my emmc has the insane chip bug. The phone boots normally with cyanogen mode 11 but then it goes to sleep mode or I press the power button the screen goes black and the phone restarts. I have tried siyah kernel to try dual boot but then I flash siyah I cant get into recovery.

I think you should flash latest STOCK ROM with Odin, and then follow available custom rom instructions on xda...
Test if the stock rom will work for you, boot your phone etc... Try to use it a few days. If everything is OK, proceed with
further procedures...

twinsen.net said:
I think you should flash latest STOCK ROM with Odin, and then follow available custom rom instructions on xda...
Test if the stock rom will work for you, boot your phone etc... Try to use it a few days. If everything is OK, proceed with
further procedures...
Click to expand...
Click to collapse
I have already tried this but with the stock rom phone boots but at the section where I have to chose language I jus freezes stops working

So I think it is a hardware problem. Phone on stock rom shouldn't freeze on language selection. Something is wrong. If you are on warranty, let them fix it for you, if you are not, try to fix it in some phone repair point. I'm sure you can stop your attempts. It will not be better for now.

twinsen.net said:
So I think it is a hardware problem. Phone on stock rom shouldn't freeze on language selection. Something is wrong. If you are on warranty, let them fix it for you, if you are not, try to fix it in some phone repair point. I'm sure you can stop your attempts. It will not be better for now.
Click to expand...
Click to collapse
Take it straight away to the official service centre

[Q] I have problems with updating lollipop 5.0 in my Nexus 4.

So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help

vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?

vigneshkumargv said:
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Also i have tried using power + volume up and it doesn't help . Please help
Click to expand...
Click to collapse
with wugfresh nexus root toolkit click on the button "soft-bricked"(flash stock + unroot) or something like that to restore the phone. After that try another time to unlock and root with a custom recovery (for example twrp).
When nexus root toolkit installing the original lollipop rom, look the "dos window" to see if the software shows errors, because sometimes the process ends without a real restore.
If you have other problems, please post a screenshot.

Fenix46 said:
As you've upgraded to lollipop ?? You came from a custom rom ?? Enters the bootloader?
Click to expand...
Click to collapse
Yes I was using a custom rom, but I not even reached the step where a was supposed to use the rom, I was steel still cleaning the divece.
Here is a photo from the screen I'm stuck in:
eeee.... I'll find a wint to send the photo to this forum ^^" wait

[Q] N5 dead? multiboot issues?

Hi, my Nexus 5 was just powered off as i clicked the power button to browse the web. I tried to boot it but it just went to multiboot and restarted after 2 seconds.
It kept restarting like it was bricked but shut off after a few times. Then i booted into bootloader but the screen went off after 2 secs. I removed the battery and put it on the charger but it just boot loops the google logo.
I am on Xtrasmooth v9.0 if you want to know but i dont think that this has any importance since my phone doesnt stay in the bootloader which has nothing to do with my rom (i think):good:
But maybe it has to do with multiboot? I have to say that my phone kept randomly restarting over the last week.

AkaHantz said:
Hi, my Nexus 5 was just powered off as i clicked the power button to browse the web. I tried to boot it but it just went to multiboot and restarted after 2 seconds.
It kept restarting like it was bricked but shut off after a few times. Then i booted into bootloader but the screen went off after 2 secs. I removed the battery and put it on the charger but it just boot loops the google logo.
I am on Xtrasmooth v9.0 if you want to know but i dont think that this has any importance since my phone doesnt stay in the bootloader which has nothing to do with my rom (i think):good:
But maybe it has to do with multiboot? I have to say that my phone kept randomly restarting over the last week.
Click to expand...
Click to collapse
Have you tried restoring to 100% stock with a factory image?

_MetalHead_ said:
Have you tried restoring to 100% stock with a factory image?
Click to expand...
Click to collapse
Heya, I found out that my power button was broken so i had to remove it from the board and started the device with a screw driver :victory: