Random Reboots GSM GN 4.1.1 All Stock - Samsung Galaxy Nexus

Hi, I have a completely stock GSM GN on 4.1.1 and just since two days ago I have been getting random reboots. Only reason I can even tell is because I have my phone encrypted (lost phone and my data is in a strangers hands? No thanks) so every time it happens it sits at the prompt for me to input the password.
I initially tried clearing the dalvik-cache and that didn't work. So, I did a complete wipe and reflashed the stock images via the GN Toolkit. That also didn't work. Finally, I went through and uninstalled all apps that were installed or updated within the last week of August and it still didn't work.
I am at wits end here. I've owned my GNexus since the beginning of July and never had a problem like this. Any suggestions would be recommended.
EDIT:
I have also noticed that while I am using the device the screen sometimes flickers black for a second and then comes back on. Its not like the CRT Off animation you get when you hit the power button, just simply the screen goes black and then a second later comes back

Just bumping because I changed the issue from a hot restart to a proper reboot since I just got it doing a full at "Google" image reboot. Once it did just do a "Nexus Logo" reboot though.

Related

Random Root Problem

So i bought my incredible the second day they were released, and rooted it when unrevoked came out with their first one-click root program (so needless to say im not exactly a "new" root user). i've ran a couple roms, and lately have run stock leaks w/ added .zips for a little customization (about the past three months or so). i've been on the latest leak for like a month ish (i think its the latest one) possibly little bit longer than that. i never had a random reboot or even really any lag up, which was really amazing. then, i tried to install a custom flat black notifications bar, and i installed the update zip through recovery but it didnt do anything.
about two weeks later, i installed that new status bar power menu thing, and started to get the occasional random reboot and bog up. no really enough to really be a problem, but tonight right before bed my phone started boot looping after a random reboot (it would boot for a min or two then reboot after a lockup). so i pulled the battery and powered back on. then it loaded to the lockscreen, but every single app that should have started at startup began to repeatedly force close, so i couldnt use the phone. i tried three times but it happened every time. im nandroiding now, im sure that'll fix the problem, but any ideas what caused this? thanks!
just happened again on ruby 2.0.0, but this time all of the apps force closed AND the "click android to start" setup screen came up. I got a random reboot (which i rarely to never have), pulled battery and powered back up, it loaded to lockscreen, then it went into a soft reboot and froze at the looping bootscreen, then once i pulled battery again and powered up, i got the crashes. any idea what it is? this time, it did happen like 15 min after i had dropped my phone from about 2 feet off the ground, i guess that could be it? idk
For what it's worth, I was running 2.3 and it wouldn't mount internal or SD. This happened even after installing other ROM's. I downloaded the latest RUU, unrooted, and started from scratch.
I reformatted the SD card too. I re-rooted, and restored my SD backup. I re-downloaded the ROM I wanted, and installed it. It fixed the weird issues I was having. You may want to consider starting over from scratch.
Sent from my Incredible using XDA App

[Q] TP2 'Align Screen' Infinite loop

I was running MightyRom for almost a year, no problems. Suddenly about a month ago my screen alignment was occasionally wacked, by a 1/4 inch or so.
But the alignment screen function no longer worked, I had to restart the phone to exit the application.
Yesterday I flashed back to the stock Sprint ROM and removed the SIM card, I'm giving the phone to my kid so I wanted to reset it to factory specs.
So the 'startup for the first time' sequence begins and the align screen application simply will not 'align'. The crosshairs just prompt me to keep pressing for alignment but I cannot get past this to get to the Home screen.
I hard reset the phone several times from the bootloader screen, even tried to re-flash the Sprint ROM again, but no avail.
Any suggestions? I've been all over google looking for solutions.
I should also mention that it's a brick since I can't make calls/text, etc.. I'm stuck on the 'align' screen.
I took it to the Sprint store, they confirm that it must be a hardware issue.
Rep ordered me a new one, says it will be in by Monday or Tuesday, just have to activate an old phone for the weekend.
0 deductible!!
I'm glad that I got that Sprint ROM back on it just in time.

[Q] GSM Galaxy Nexus force close & reboot ****storm

I have searched for this issue but couldn't find anything about it...
So I got my GSM Galaxy Nexus from Rogers 10 days ago. It has been working dandy with maybe 1 force close the whole time and no random reboots. I also unlocked the bootloader and installed 4.0.2 (yakju) keeping the radio that came with it intact.
I also installed Google Wallet on it and successfully used it. Other than that, I haven't done any tweaks, and like I said, it has been working perfectly with no problems whatsoever.
Enter today: I woke up this morning and went to check my phone. Instantly like 3 applications force closed (ones that weren't even running in the foreground too). Now for the past 3 hours hours or so, applications force close (some won't even have a chance to run for a second) and the phone reboots randomly. I think it has rebooted around 30 times in the past 3 hours. Sometimes it reboots as soon as it has booted up, sometimes it works for a few minutes before rebooting.
Every time it reboots it shows my old battery stats (I think.. from before I went to sleep), and notifies me of the same emails. I managed to install one app before it did a random reboot once, but after the reboot it was gone. (Think Groundhog Day).
I have no idea how to fix this short of doing a factory reset. Anyone have any ideas as to what may be happening or how to fix it?
Thanks.
stenzor said:
I have searched for this issue but couldn't find anything about it...
So I got my GSM Galaxy Nexus from Rogers 10 days ago. It has been working dandy with maybe 1 force close the whole time and no random reboots. I also unlocked the bootloader and installed 4.0.2 (yakju) keeping the radio that came with it intact.
I also installed Google Wallet on it and successfully used it. Other than that, I haven't done any tweaks, and like I said, it has been working perfectly with no problems whatsoever.
Enter today: I woke up this morning and went to check my phone. Instantly like 3 applications force closed (ones that weren't even running in the foreground too). Now for the past 3 hours hours or so, applications force close (some won't even have a chance to run for a second) and the phone reboots randomly. I think it has rebooted around 30 times in the past 3 hours. Sometimes it reboots as soon as it has booted up, sometimes it works for a few minutes before rebooting.
Every time it reboots it shows my old battery stats (I think.. from before I went to sleep), and notifies me of the same emails. I managed to install one app before it did a random reboot once, but after the reboot it was gone. (Think Groundhog Day).
I have no idea how to fix this short of doing a factory reset. Anyone have any ideas as to what may be happening or how to fix it?
Thanks.
Click to expand...
Click to collapse
Is it doing a full reboot or just a "warm start"?
Sent from my Galaxy Nexus using Tapatalk
What's a warm start? It seems to be doing a full reboot.. Screen goes black, then Google logo appears, then the boot animation.
It seems that I cannot do a factory reset.. selecting it in the menu brings me to the android robot on its back with a red exclamation mark, and selecting wipe data from that menu doesn't actually wipe anything even though it says it does.
Try unlocking and relocking your boot loader if you are going to factory reset anyways
Sent from my Galaxy Nexus using xda premium
It's already unlocked.. You mean locking it and unlocking again? Also, is there any way to batch reinstall all the apps tied to my account? And also, any clue how this issue could have originated? I want to avoid it in the future.
No idea.. all I can think of is an app using all of your memory as that's what causes a force close.. and sure try relocking and unlocking if a normal factory reset won't do it. If you have titanium backup you can use that to batch reinstall but if it is an all causing this issue you should install them one at a time to see of there are any adverse effects.
I don't know if it is an app but that is my best guess.
Sent from my Galaxy Nexus using xda premium
I hadn't installed any new apps prior to this.. and everything was working fine before, which is why I'm confused as to what could have caused this. Also, not just one app force closes, but like 4 at a time.. usually the Google apps for some reason. I checked the memory and the CPU and it seemed to be running at normal levels.
Have you tried an old-fashioned battery pull?
Haven't had this happen to me, but a pull usually does the trick.
Yep, and it hasn't worked.. Every time the device reboots, it will either reboot again right away, or if i don't touch it, it will idle. Then if I try to do anything, 3 or 4 apps will crash instantly, and then it will freeze and instantly restart.
If I manage to install an app, I can run it, but then it crashes and reboots again with no sign of the app. Deleting apps is also useless as they are back after reboot. Strange issue.
Guys, I really need help.. I finally had time to sit down with my phone and figure out this issue so I decided to just do a wipe. As I wrote previously, I am unable to wipe it from within the OS due to it rebooting when I do, so I decided to re-lock the bootloader.
When I typed "fastboot oem lock", it changed the lock state on my phone to locked.. as I was expecting.. however, when I rebooted the bootloader, it was unlocked again. WTF? Now I am trying to flash stock 4.0.2 to it again (which it was already), but it's been stuck on "writing 'system' ..." for half hour
Could the flash memory be corrupted somehow?
Ok, I have deduced that it is most likely corrupted flash memory.. I didn't even know that could happen, especially in 10 days.. I guess that's good ol' "Made in China" at work. Still, am I the only one who has had their flash memory fail on them?
Crossing my fingers that Rogers will replace my Galaxy Nexus even though it's rooted and bootloader unlocked :/
Hey stenzor,
I am facing same problem of rebooting...
But I haven't flashed it to yakju.
Did rogers replaced your?

It froze, went black, and now it is weird.

Hello,
This is what have happened:
I was browsing via Chrome, when phone froze. Well, no big deal. It went black, and I couldn't power it back on. I was on rehersal, so I left it on the table for an hour.
Came back to it, tried to power it on, and after 20sec or so of holding Power button, Google appeared. And it disapeared again.
And that is it.
I can access bootloader, and recovery.
From there I tried to flash fresh img, but my device is locked. Went the other way. I downloaded latest OTA and went to adb sideload, and it downloaded it all to phone, but same thing with booting. It stops.
Sometimes it even goes to those circle animations on booting, but than it freezes again, and turns off.
Any hope for my 2 years friend now
Thanks.
@Nuuq: by searching for 'brick' 'bootloop' you find for example this thread Hope, it helps.
Exact same thing happened to me this morning. I was playing Clash Royale, and it froze. Rebooted, and it just went to Google screen and nothing else. I let it sit for an hour, and it started to boot, but froze mid-boot-animation. I can get into bootloader and recovery, so I'm going to flash the Bootloop fix this afternoon and see if it fixes it.
Odd......
I thought this was a CPU bootloop issue, so I flashed the 4-core TWRP, wiped everything, and installed the stock OPR4.170623.006 system, vendor, and thne 4-core boot.img I found in the bootloop thread. I got a little farther, say 5 minutes instead of 5 seconds, but it was still crashing and bootlooping! I couldn't activate the phone, cuz it was rebooting while waiting for my 2-factor authentication text, and when I tried wiping it again, it was rebooting while in TWRP while re-flashing the system. The more I try to fix it, the worse it gets...
I may just give up on the phone, and contact Project Fi support to see if they'll give me a new one.
Same here guys...put inside the the fridge for about an hour and it started, just in time to save my photos on Google photo...but as soon as I start to use it, it freeze, turn off, no reboot. If I reboot, it freezes on circles Google animation...i can enter in bootloader and recovery too...any suggestion?
Same problem - merrily browsing -> crashed and now bootlooping - can get to the bootloader menu but can't get into recovery mode
Running Oreo 8.0
I flashed the 4-core TWRP, and it was crashing even in that. Last night, it sat for 3 hours on the activation page, and never froze, but anytime I try to use it, it freezes. It sometimes turns on, but most of the time it just crashes while booting.
I already use Google Photos, and my texts are synced through Fi hangouts, so I'm not worried about losing anything. I've wiped my phone and started over maybe a dozen times over the past year. Different ROMs, kernels, etc. I just want a working device.
I called Google, and they said nope. They want me to call LG, but my brother has had 2 bootlooping 5x, and LG didn't help with either of his. I doubt LG will help me here, cuz I bought it from the Google Store. I think I have 3 options:
1) pay to gave the CPU reflowed. If I went this route, I would want to upgrade to 3GB or 4GB of RAM at the same time. If I do this, I still have to deal with my battery only holding a 70% of it's charge, and not wanting to spend $50 on a 2 year old OEM batter.
2) Upgrade to a used Pixel. I'm sure with the Pixel 2 coming out, lots of people are going to be upgrading, and I'm sure there will be a bunch of used Pixels showing up. But, you're still buying a used phone that's been out for a year now...
3) Upgrade to the Android One Moto X4. The word "upgrade' is used loosely, as it's VERY similar to our 5Xs. Similar benchmarks, similar screens, similar primary cameras, almost the exact same dimensions, etc. It would be an upgrade with 3GB RAM, bigger storage, SD card slot, 2nd rear camera, better GPS, bigger battery, new (not used), and a few other minor tweaks. Con is that it's so new, there are no ROM/kernels for it yet
I think I just talked myself into a X4 while writing this. We'll see what the wife says.
it happen for me but me i can boot to bootloder but the phone become very slow i just escape from bootloop i turn it on and after 2 week he bootloop again now only fastboot no recovery and no system how i do
squelch41 said:
Same problem - merrily browsing -> crashed and now bootlooping - can get to the bootloader menu but can't get into recovery mode
Running Oreo 8.0
Click to expand...
Click to collapse
Hmm, putting it in the freezer gets it to boot but rapidly crashes again - looks like it is the hardware rather than software

SMT700 screen flicker & reboot issue - kinda solved

It started about 8 months ago, in retrospect, after an OTA update. I'd be looking at some app when the screen would flicker and shortly after it would either go blank, reboot or simply turn off, it was maddening and I thought the end of my little tablet. I tried a couple of different things, thinking that somehow the bootloader got corrupted I reflashed that, didn't work. I then flashed the previous version of the bootloader, that really didn't work so flashed back. I'd always kept the tablet with the stock Samsung ROM so flashed the latest Lineage ROM (great piece of work) but that didn't help and actually made it worse, when I would reboot it seemed like it would immediately flicker when things were updating, it wouldn't stay on for more than a minute. I read about the potential for cracked battery leads so changed the battery and reflowed the solder around the terminals, that didn't solve the problem either. After that I started to suspect some kind of memory/software issue so in desperation I flashed it back to the beginning of time, the original Samsung ROM and that worked. I have the TAR if anyone needs it just let me know. After you do this your back to Android 5 and you'll notice that it will notify you of OTA updates, I updated BUT I found that past the 4th update the flicker came back, this might just be an issue with my tab but just be aware. I only use this now to read the news or my Kindle books, I did notice that some apps would trigger the flicker like My Radar or Zillow so I uninstalled them.
Hope this helps.

Categories

Resources