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!
I was using my phone earlier today and was attempting to extract an archived file with OfficeSuite 7. I had merely 400-500 of free space available at this point. After a few attempts and cancellations due to failure to extract I decided to restart my phone. Upon restarting it continuously will vibrate, show the Samsung logo for a moment, the screen will flicker off and it loops through that process all over again indefinitely. I can access download mode and recovery mode. I tried clearing the cache through recovery and removing the battery as well as smacking around the power button but it did not fix the problem.
I'm using stock TouchWiz Android 4.1.1 partly debloated, rooted, and stock recovery (because this ROM reflashes the stock recovery after a reset if a non stock recovery is installed).
I figure a factory reset might be the fix but I would need to extract my apps, settings, and SMS/all other data and I'm not sure how to do this with the phone in this condition and without an external SD card. Maybe I could flash ClockWorkMod, do a nandroid backup, and than extract this data with Titanium Backup? Can Titanium Backup do all that I am asking (I've barely used it)? Does anyone have an idea as to what the cause of the problem is to have this suddenly happen? I'm thinking it's the power button malfunctioning. The day prior twice my phone turned itself off.
Twrp has built in file manager. Copy to sd, then to computer?
Otherwise look into ADB.
what is happening
strange I am have the same issues . from working great to now FC and rebooting . almost like it the power button malfunctioning but it is not. Its something more. I was running DocHoliday 4.3 and was great . then I tried Aamir Mod V2 UVDMD5 4.3 same great . but this morning noticed it kept rebooting for no reason . wiped reset, nothing . looped and looped . wipe/reset and re-flashed and it will only stay on for a mintue . and if sleeps will not turn it F/C as soon as I touch power button.. crazy ???
anyone having the same problems with any 4.3 ROMs ??
I'm having the problem on my S3, but I'm not on 4.3 yet....
I already had this issue once 2 weeks ago and I factory wiped and started over. Fast forward two weeks forward and it started again today. WTF?
Qverse said:
strange I am have the same issues . from working great to now FC and rebooting . almost like it the power button malfunctioning but it is not. Its something more. I was running DocHoliday 4.3 and was great . then I tried Aamir Mod V2 UVDMD5 4.3 same great . but this morning noticed it kept rebooting for no reason . wiped reset, nothing . looped and looped . wipe/reset and re-flashed and it will only stay on for a mintue . and if sleeps will not turn it F/C as soon as I touch power button.. crazy ???
anyone having the same problems with any 4.3 ROMs ??
Click to expand...
Click to collapse
insaneoctane said:
I'm having the problem on my S3, but I'm not on 4.3 yet....
I already had this issue once 2 weeks ago and I factory wiped and started over. Fast forward two weeks forward and it started again today. WTF?
Click to expand...
Click to collapse
Are you using TWRP? I had a similar issue, upgraded to newest TWRP 2.6.3.1 and it was fixed. Before this I tried everything, factory reset/modem upgrade/different roms.. and it wasn't working..other than a rooted touchwiz rom.
Give it a shot.. might work..
As per Perseus71:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash.
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
atlJE said:
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
Click to expand...
Click to collapse
I have the same issue. I suspect the person I let use it tried to use the options menu to reset the phone back to factory specs, which I was warned on here that would brick it, so mine is stuck in the round and round boot screen for CM. I think you're supposed to use the factory reset in CWM to delete personal stuff. I'm trying to figure out how to fix it and if I come up with something I'll let you know.
flash back to stock rom
atlJE said:
Long story short, I had recently installed the cyanogenmod to my phone, don't like it, tried to flash it back to the stock rom and the rom couldn't install. The installation wizard restarted the phone, now it's stuck on the cyanogenmod boot screen and the notification light lit as if im charging the phone, but it's not plugged up. The bad part about all of this is that the battery isn't removable so now I have to wait for phone to die I guess but is my phone now bricked? Once it dies can I recover from this by booting it up thru recovery mode?
Click to expand...
Click to collapse
Good thing is you are not "hard bricked" just "soft bricked." Press the power button and volume up and hold till your phone reboots then immediately press the volume button and power down button to enter recovery.Then do a complete wipe, factory reset, then and only then reflash your stock CWM backup of your stock Rom . Just guessing mind you ,because I do not know every single thing you did before trying to return to stock but you should always do a full Wipe or factory reset before flashing between different roms. If your trying to flash a stock image, not a CWM backup, of your firmware you'll need to first reflash your stock recovery and relock your boot loader.
Is your phone a single SIM or dual SIM? Dual SIM phones have allot more issues on Cyanogenmod . If yours is dual SIM I'd stick to stock Rom or sense based custom roms made for our device. By the way what didn't you like about CM if your on a single SIM phone? It had a few issues but with a few tweaks you can get it working great and it's alot less bloated than stock lollipop. I'm on unofficial 12.1 CM with the a5_chl single SIM and it's fine. Having said that I had to tweak several things and I exempt dual SIM versions from my reasons for me liking this Rom. I get that it's sadly alot buggier for those phones . Let me know how things go in fixing your issue and best of luck.
---------- Post added at 10:43 PM ---------- Previous post was at 10:02 PM ----------
Ddreth said:
I have the same issue. I suspect the person I let use it tried to use the options menu to reset the phone back to factory specs, which I was warned on here that would brick it, so mine is stuck in the round and round boot screen for CM. I think you're supposed to use the factory reset in CWM to delete personal stuff. I'm trying to figure out how to fix it and if I come up with something I'll let you know.
Click to expand...
Click to collapse
First thing, some friendly advice and I truly do mean friendly, not accusing, but you should never let anyone else touch your device when it's in custom recovery. They can seriously mess it up not just"soft brick" it like yours is now.
2nd thing is the factory reset in your custom recovery doesn't have anything to do with your personal files. It's to clean your system and its data so that you can do a fresh install of a different Rom. It's called a "clean flash." A dirty flash is when your upgrading the same custom Rom and you just flash it over the previous version without wiping then clear your Dalvik cache and reboot. These wipes leave your personal files on your internal and external SD card intact unless you specifically wipe then in your custom recovery . They just call it factory reset to make it familiar to the stock Roms use of the term in my opinion. When you have this"soft brick" you can press your power button and volume up to reboot then quickly press power button and volume down to enter recovery. Then factory reset or wipe Dalvik cache if not wanting to reset and reboot one or the other should get you back into your rom.
Hope this helps and good luck plus let me know if this works to resolve your issue. Be happy to help in any way because I have been there myself in the past. Bootloops, soft bricks,etc etc................... If you can name it, I've messed it up.
Well i start getting this problems 2 day ago.
I was on OB3 perfectly with theOne5TOs but i try the new Ob4 for the 8.1 android with audax rom. I didn't like so i went back to the same rom i always do a clean flash ( wipe everything but internal ) then i flash the Rom, no verity and then magisk.
But after i setup everything i start getting this reboots! The phone just freeze and then in like 15 seconds it restarts.
I try everything at that moment i did a factory reset and nothing then i try another kernel (newkernel) and nothing.
Then i went extreme and backup everything i flash stock 5.0.4 stock recovery and lock the bootloader after that i unlocked again and install just magisk( can't live without ) and i got a reset ): i don't know what else to do. I found a 5Trepair.zip that oneplus sent to an user on the oneplus forums for this issue so i flash it and then clear cache it's been like 30 min and no reboots but let's see.
I hope there's something else to do ):
1. Turn phone on, wait (even days) till batery turns dead
2. Pack phone, send it to where you buoght it from and force them to reinstall system.
Same problem for my 5T. This started to happen after installing the last beta A5010_43_181218.