I have a stock GN, not rooted yet. Today my phone automatically shut off and now it starts back up, google logo shows up and all those colors come on for couple of seconds and then the phone reboots itself.
I can press both volume up+volume down + power button and get into a menu which gives me the options of Start, Restart bootloader, recovery mode, and power off. I choose recovery mode but then it goes on to an android sign with exclamation mark. After that I can't seem to get anywhere. I have tried volume up +power, volume down+power, and volume up+down+power but nothing seems to work. It just keeps on rebooting it self.
Any solutions to this problem??
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
....
FredFS456 said:
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
Click to expand...
Click to collapse
So, I did the above method and after flashing the factory stock rom it won't start up anymore. It doesn't respond to anything at all. It seems I've bricked it
Is there any way to unrbick it now? I'm assuming I can't send it in for warranty either now if it's semi bricked. Unless it's been completely bricked which means there is still a chance of getting a replacement phone.
I have the same prob on rooted SGN
This morning I switched off the airplane mode to be available, system crashed and restarted. And then still the same again - booting / android logo / restart again.. /./. I am using Android Revolution HD 2.1.5, for last month with no problems.
I tried to boot into recovery, then wipe the cache and reflash rom and radio from sd, it is still the same. I can see all the files on my int. sd with no probs.
Please help.
I'm thinking it might be a hardware issue, but I'll wait for another member's opinion before confirming.
Solved!!!
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
630263 said:
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
Click to expand...
Click to collapse
Was your phone rooted or bootloader unlocked before the problem occurred?
Anyways I've sent in my phone for warranty, hopefully samsung will fix it.
So my phone company called me today and apparently Samsung told them that it's corrosion(?) problem. When I asked exactly what does that mean they said it's moisture damage or physical damage that probably caused it. But I'm confused how could my phone possibly get moisture damage inside an otter box. I know how delegate these devices are and I know how to take care of them.
Anyhow it'll be $90 to fix it. I had no other option so I asked them to go ahead with the repairs. So frustrated with Samsung to be honest. I never dropped my phone once, never had any water damage, phone was always inside the defender case. And I still have to pay them for fixing my phone even though it's not my fault.
That's quite worrying, I just started having boot loop problems today. I've had the phone since Feb 29th and not had a problem with it yet, but today it started boot looping. I went into recovery and did a factory reset, was alright for a couple of hours then it crashed, started bootlooping again. Running stock 4.0.2 unrooted, I'm wondering if flashing 4.0.4 might help.
I'm in the same boat.... unrooting stock 4.0.1 firmware - canadian version from Negri.
April 23rd my phone crashed and started boot looping. Google logo - reboot - Google logo - reboot
Factory reset worked. I installed less apps than I had before figuring perhaps an app was corrupting something.
Yesterday - it happened again. Phone crashed. Boot loop. Factory Reset worked. Installed even fewer apps.
We'll see what happens this time around. I am hoping it is just a software thing. Hoping 4.0.4 gets pushed soon too.....
I've been having the same issue, plus sometimes my home screen it would lock up and wouldn't let me do anything, so I did a battery pull and it would boot loop for a half hour.
After the 3rd time I just took it to my Verizon wireless store, and showed them the situation and they couldn't figure it out, so their sending me a replacement, which I'm not looking forward too, don't want a semi-used phone....
Via Galaxy Nexus [LTE]
Rebooting Issue Solved.
I was also a troubled Samsung Galaxy Nexus user and my phone kept restarting more than half a dozen times everyday. Most of the times when I switched between two or more applications, or when it was simply idle on my desk.
However, I found a solution (at least in my case). All I did was root my phone, install cwm recovery, and flash a custom rom after wiping cache and factory resetting the phone, It's been about 5 to 6 hours now since I flashed the custom rom and I haven't had a single reboot or hang since.
Others who face this problem, please give it a shot, who knows? You might save your Galaxy Nexus instead of sending it back to get a replacement or spend some money on it for repairs which aren't even required in the first place.
I also had this problem unrooted. I had to give it to Samsung for the warranty
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
2stardiver said:
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
Click to expand...
Click to collapse
I could be wrong, but have you tried to clean the pin on the battery? Seems like battery and the phone isn't contracting too well
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Little update, phone did continue rebooting with original 1750mAh battery also.
I did also reset with recovery mode, and after that it did also reboot one time.
like it uses all memory/cpu and when nothing to do reboot (like windows )
I also did flash stock rom with toolkit but no help.
I will test rooting phone and flash another rom, or is it useless ?
after using couple days, not yet rooted.
Phone works and wont reboot even in heavy stress. but sometimes it just reboots by own not a single program in task list.
might reboot right after previous reboot or take hours to reboot.
stupid phone
I have been done some research.
I did one more time reflash google stock with rootkit, and forgot lock phone, it was almost 3 hours by own in wifi, no reboots at all.
when I noticed that I forgot to lock it I rooted whole phone and installed paranoid android 2.13 with CWM.
Now Ive been using 2 hours without any reboot, installing software, setting things up and using apps.
I dont understand at all:silly:
edit: noup, yesterday evening one almost reboot, paranoid android did reset itself but didnt even reset uptime. so I didnt count that normal reboot.
but after wake up this morning, it did reboot once when I put in my pocket, another just lying on table, once activating bluetooth in my car.
going to send it back to seller.
I have a similar issue, although not quite the same. Last night my phone started boot looping - it managed to boot up to the lock screen, and I can use it for about a minute before it dies and then reboots. This continues again and again (I have to pull the battery to quit it).
I have stock JB on my GSM GN, but rooted with an unlocked bootloader / CWM. I restored my old CWM backup, and had the same issue. I also wiped the cache and the dalvik just to see if that helped, but I had the same issue. I then tried to do a factory reset in CWM, but after I did that the boot loop just got to the nexus logo and died, entering a new (slightly shorter) boot loop. I went back into recovery and reflashed my CWM backup, and that at least got me back to booting into android.
I can't understand what's going on - could it be a hardware issue if it will happily stay alive in recovery, but dies after 1-2mins of android?
Thanks for your help. If it is hardware then I hope I can reflash the stock recovery / bootloader and unroot through recovery... the phone doesn't stay on long enough to do it when it's booted into full android!
Got a HTC One X a while back and decided to keep it stock as long as I dont find a stable recovery. So my HOX was completely stock. Had no issuses with it for the time I have used it which should be around 15days. I did experience some random reboots. Overheating was a problem too.
Last night was using gameboid to play while watching soccer. After match, I tried to use inbuilt browser but it could not be launched. Everytime I started it, a menu opened with sending a report or not. Then tried google play store to download another browser, but that failed too. Even apps did not upadate. got a error. Dont remember exactly but most probably that was error 492.
Then i decided to reboot. After the HTC quietly brilliant screen, came the HTC ONE screen with some sound, and then hung up there. Tried a hard reboot but same thing happened but this time onwards sound vanished.
So what should I do?
Thought of going to bootloader and then factory reset but I have some important data in HOX and then doing factory reset might not solve the problem.
What should I do?
Just to tell you, Now when I went to bootloader and turned off and back on while plugged to laptop, its still on the same screen but this time its charging.
It does not charge while turned off.
Again,
Im unrooted - completely stock and not unlocked via htcdev.
Edit: The phone is charging now with the power adapter.
Edit2: Just did a factory reset via bootloader , back to normal now.
When still completely on stock and haven`t done anything.
I would say return it..
There would be answers and suggestions but why void warranty.
while my phone hangs up at htc one screen, is there any way the data can be restored? Im assuming running ruu erases everything since its virtual sd card.
Girlfriends device has had multiple problems with rebooting constantly.
Originally when the problem occurred the device was rooted, no custom rom or anything, just root access. It died and just would not turn on. Sent it in, the work order said they replaced the soft key and main battery.
After a few weeks to the phone would just randomly reboot and continue to reboot basically until the battery died. This time it was not rooted at all, they had done a software update that removed it. Thought maybe it was apps, uninstalled everything, did an ota update. Still reboots. Sent it in again, this time all they replaced was the soft key, again. Came back today, less than two hours later while trying to update core apps through Google play and the device froze. Now we are unable to get the device to boot up properly any more again. Sits on the HTC splash screen when it decides it actually wants to turn on, and that's about it. Can't get it to connect the the computer or anything.
Still a warranty case, solve it there ....messing with it here will not help. My guess it needs a new mainboard
here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
ender127 said:
here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
Click to expand...
Click to collapse
there was an ota update a bit ago, 4.3...um, is it under warranty or does she have insurance, if so, go to the sprint techs and have them look at it, if not, what you can do/try for it is to completely flash the 4.3 ota update again using odin and download mode...you can do this by clicking on the 2nd link in my signature and see what happens, fixed my phone like this after 4.3 and myself messed it up lol and it's the exact same thing the sprint techs would do for it if you brought it in
so there's your options man...good luck, any questions just post up but the guide is very simple and straight fwd to follow and I provided all that is needed in my download bundle from my dropbox account
edit...if you can't boot up to enable the usb debugging mode, it should still work but it's recommended to do but again, shouldn't really matter, as long as it boots into download mode you should be ready to go
ender127 said:
here's the background: galaxy s3, nonrooted, stock firmware, no physical damage that i'm aware of.
my friend's gs3 is constantly rebooting. essentially, it even reboots at boot up at any of the various splash screens during boot up and does not even boot up fully at all before it'll decide to crap out again. i figured that it may possibly be related to some rogue app so i told her to load up in safe mode but even then, the phone would reboot and attempt to restart again to ultimately fail and repeat. it did manage to boot up for a minute or two under safe mode yet it would restart again. i actually spoke to her last night but when she woke up, her phone wouldn't even stay on. after she had hung up, all she did was charge her phone and found it in it's current condition. we've attempted to remove the battery for a minute or so but the problem persists. the only other assumption was that there might have been an ota update that went bad. unfortunately i have a rooted gs4 so i'm not sure if there was an ota update for the gs3 that i wasn't aware of.
does anyone else have an idea on how to fix this or what may be the problem?
Click to expand...
Click to collapse
This isn't an uncommon problem with the S3. I just recently went through this. In my case, and in many other cases, it's a faulty motherboard. Nothing you can do to fix it other than get Sprint to replace the handset.
For me, if I left it completely off for a long time, when I turned it back in it was stable for a couple of hours. Not sure if it was a coincidence, happened a couple of times that way.
My Galaxy S3 keeps shutting off during boot. I encountered this problem while running Cmod 11. Was using poweramp playing music off my 64gb exFat microsd card, and suddenly Poweramp encounters "Error too many files" and promptly shuts the phone down. (Poweramp has been giving me strange problems before this, like that error just mentioned, and scanning for changes when there are none, but this is the first time the error caused the phone to shut down).
After rebooting it, The S3 gets to the boot screen and upon opening an app, promptly shuts down again. Further attempts result in the phone shutting off during the boot animation, and finally now the phone simply shuts down right before the boot animation. (note: it doesn't reboot. It turns itself off).
I thought it might be a problem with Cmod, so I wiped everything and using CWM, installed slimkat. Same problem. so I went and installed stock android using Odin, and now I'm back to stock. STILL same problem.
When I have the phone plugged into a computer, it seems to get further than the boot animation before shutting down (sometimes it gets to the lockscreen before shutting down again).
Any idea what's causing this problem? I have no problems with erratic shutdowns during recovery and download mode.
How old is your battery? Might be time to replace it.
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
cheezyphil said:
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
Click to expand...
Click to collapse
They're not as heavy to load.
Was any modification done to your phone (software) about when that started happening?
The s3's been on and off custom roms for a year now
cheezyphil said:
The s3's been on and off custom roms for a year now
Click to expand...
Click to collapse
I mean before it started happening. Or were you on the same ROM/version of that ROM for a while when it happened.
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
cheezyphil said:
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
Click to expand...
Click to collapse
Well if you can get in recovery, I would suggest doing a clean flash. But chances are that it's your battery giving out.
If you want to test, borrow a battery from another S3. I know with T-Mobile you can go to a store and they usually have a device on hand that you can borrow one from to test it out before spending money on it. I imagine you can do this at AT&T stores as well.
had the same problem with my atnt galaxy s3
i have the same problem,,i am using cm12 ryt now,,i tried to put every single rom and same thing happens,,i also brought it back to its stock firmware,,and still the problem occurs... did u find any solution for it,already?
:crying: