I recently found out I could update my captivate with Kies Mini (when I tried to update otherwise I got the "failure to communicate with server" error). I updated and everything went smoothly. Kies told me update was successful and I unplugged my captivate. It was booting up fine until it reached the Galaxy S logo. It kept going through the logo animation for about 2 minutes before it shut off. I took the battery out and tried again. Same result. How can I fix this?
Please help, thank you.
edit: I was running a One Click Lag fixed captivate with. I have a Win 7 64 bit
edit 2: okay now my soft buttons are lighted up. When I touch them It responds with a blink, but no haptic feedback. What is going on??
overkillogi said:
I recently found out I could update my captivate with Kies Mini (when I tried to update otherwise I got the "failure to communicate with server" error). I updated and everything went smoothly. Kies told me update was successful and I unplugged my captivate. It was booting up fine until it reached the Galaxy S logo. It kept going through the logo animation for about 2 minutes before it shut off. I took the battery out and tried again. Same result. How can I fix this?
Please help, thank you.
edit: I was running a One Click Lag fixed captivate with. I have a Win 7 64 bit
edit 2: okay now my soft buttons are lighted up. When I touch them It responds with a blink, but no haptic feedback. What is going on??
Click to expand...
Click to collapse
I have the same problem. Did you find a fix?
I have an unlocked HSPA+ Galaxy Nexus imported from the UK to the US. Ordered from Negri Electronics.
It's not rooted or modded in any way.. Mainly because I don't know how to. As far as I know, it's running stock ICS.
I was using it normally, (using the fb messenger app if it makes any difference) when it suddenly rebooted by itself. The Google logo comes up, then the start up animation, and sometimes the home screen will appear but is not touch sensitive (i cannot slide it to unlock), and then it 'hangs' and the screen goes black. Repeat.
I've tried to fix this by myself and there's a video on youtube (sorry, noob here. can't post links. video is by robbidwv and title is "my galaxy nexus won't boot..") of the same problem that I have, but the posted solution doesn't work for me.
So far, I have entered Coin Mode and pressed Start. Entered Fastboot mode and gone into Recovery Mode (no options appear after that. it just starts booting up and the loop begins), and I've also tried Restart Bootloader.
I've almost given up. Now all I want is to extract my SMS, if they're still on my phone. I can't access the folders on my computer because it won't boot up and connect. Is there a way that I can extract my SMS by using DOS in either Coin Mode or Fastboot mode?
Or even better, does anyone have a solution to this boot loop problem? I'll contact Negri Electronics tomorrow and hopefully they can send me a replacement.
Please help!! Thanks
that problem just started happening with me an hour ago!!
i hate this!!
we need a solution please!
Hey guys, sorry about the issue.the major problem I see here is you wanting to retrieve your txt messages, which might be possible with a little Modding, but if yourwilling to lose them to get a working phone back, then this is what your going to have to do. Make sure your phone is completely off. Hold the 2 volume buttons and the power button together. You will get into a mode with an android Guy. Press the volume button up or down until it says reboot recovery at the top. Press the power button. It will rebootand come to a screen with an android. Hold volume up,down and power at the same time. A menu will come up. Go down to wipe data. Click it, and after it is done reboot. Your phone should work now.
If this helped you, or you simply appreciate me taking the time to write this out then please press the thanks button
Hey!
Thanks. Yeah I 'fixed' it already. I was just about to post something similar. After a while I just gave up on trying to recover my data. Good thing that Google syncs everything so the only issue would be recovering my messages, which I decided weren't worth sending it in for a repair which would probably not be able to recover anything anyway.
The thing I didn't know about was to press power + volume up WHILE on the recovery screen. I thought navigating to the recovery screen was it!
Still, this kind of sucks. I love my GNex, but I can't help but be slightly pissed seeing that my crappy iPhone 3GS never did this in the 2 years I had it. Oh well, hope it doesn't happen again!
hey guys! i also did a complete wipe on my phone and got it working again!
but i wonder why this happened in the first place?
last application i installed before the crash was double twist, i dunno why but i feel that it was the reason behind the boot loop!
Sorry for reviving this thread, but I just had this happen to me TWICE!
It happened to me first last Monday, the 23rd - the phone crashed when trying to send an email with an attachment - and went into a boot loop - Google logo would appear, no make it to the animation, and reboot....
I performed a full reset and things worked again. I didn't install all the apps I had before - figuring it must have been due to some app messing with the OS.
Well, it happened again to me yesterday! I was connecting to my bluetooth headset when the phone crashed and went into the boot loop. Full reset worked again, and I've installed even fewer apps - essentially only those that I use on a daily basis.
My phone is still on 4.0.1 and I'm hoping once 4.0.4 is pushed this may get resolved? I have a canadian GNex from Negri. I will call them again (I called the first time, but when the full reset worked I never contacted them again).
I would like to this this is a software issues, and not hardware.
I have the same problem. If you figure it out let me know.
Today my phone also entered a boot loop: [Google logo]->[black screen]->[vibration]->[Repeat]
I tried Recovery Mode, but this is what happens: (sorry for the link but I am not trusted with powerful tools such as outside links apparently, as I have not yet reached the maturity of a person with eight posts... )
dl(dot)dropbox(dot)com/u/53568097/Android.jpg
This is what I see when I navigate to Recovery Mode
For a split second I can see an image of an Android with spinning cogs in his innards, but then this little sad fellow appears. WTF is this?
EDIT:
Oh, and I'm running Android stock 4.0.2, never rooted or unlocked, Swedish. At the time when the phone started doing this, I was using Endomondo, and was about to set off on my bike when it died on me.
Stock ROM galaxy nexus bootlooping after wiping data also.
Hi,
My GNex went into a bootloop so i searched xda and found that factory reseting would be helping my prob. But after wiping the data also its still in going through the loop . Please help .:crying:
I've rooted stock ICS for my TF101 and I've only exeperienced the random reboot once. But for some reason my tablets home button does nothing. I've pressed it and the animation plays but it doesn't do anything i have to use the back key to get to the home screen. Does anyone know why this might be? I've tried rebooting it with no luck. I haven't tried resetting to factory yet.i want to se if anyone has any insight.
Anyone knows a fix for this?
I have the same issue except mine is not rooted. I will root it later and see if that changes anything, although i do not see why it would.... Please help??
Ok well i downloaded and installed the redemption Rom on my galaxy note 10.1 .GT-N8013 and after doing so now my lock screen, the power button options and side option went i pull out the s pen and a few other things no longer work. Also wen i turn off then boot up my tablet i get a error message at the beginning saying that you are still in factory mode and there are a couple of programs not running correctly disabling wifi. If i could possibly get help on this problem i would greatly appreciate it. Thanks
Any one possibly know wits going on?
First off, my google pixel is 100% stock. Last night when I went to bed, I had no issues with my phone. I woke up in the middle of the night because the screen was on and very bright. It was the white google boot screen, but with a bunch of corrupted text sporadically over it, and it was stuck there. I held down the power button to reboot, but when it did it would get to my unlock screen, but be frozen there. After about 5 seconds on that screen, it would reboot itself, and just continue that over and over. I tried holding down the volume down button to get into the bootloader, but when I go into recover mode, it just gives me the logo of the green android guy with a red triangle exclamation point on it and it says "no command" below it. So I reboot, and the only way to stop the boot cycle is to to back into the boot loader and select shutdown, so that way it will stay off.
Any words of wisdom? I was really not looking to get a new phone at this point...
I'll add that I used the instructions here to try to apply a rescue OTA using ADB according to these instructions: https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view. It completed successfully, but didn't make any improvement on the situation.
Update #2: I ended up trying to do a factory reset from recovery mode and that also doesn't seem to have helped.
Did you try installing a more recent OTA than what you originally had?
I already had the most recent OTA so I can't get a more recent one.
Try again in a few days when the February update is released. If it still doesn't work, it's possible a memory chip got fried.
If you're in the US, look up your nearest uBreakiFix location. They handle all Pixel warranties in the US. There are a number of reports in various threads of people getting their phone repaired for free, even outside of warranty.
I am in the US, but the nearest location for me is about 1.5 hours away. I guess I could give them a call to find out if it's worth the drive.
Why do you think a new OTA update would help where an old one wouldn't?
Is there any way I can flash the full image without having previously unlocked the bootloader?
Well i am experiencing the same problem on temporary basis since 2-3 days and the problem seems to be with the power button. I get it fix when i take it out of the body cover and try to clear the dust around power button and seems to fix it but it still happens in the morning or at night at home.