Develop Bugs

Gnex randomly shutting off?

So... maybe someone else can help me out here. My phone started doing this really cool thing about a week ago where it will just shut off out the blue. I've been scouring Google for similar problems, but cannot find anything. Lots of people complaining about reboots or sleep of death, but not hard shut downs. I don't have to pull the battery to reboot or anything, and it's not restarting, it just shuts off.
Sometimes it will only do it once or twice a day, other times it will do it 5+ times an hour. There seems to be no pattern to it either. Sometimes I will just pick up my phone and its off. Sometimes I will be listening to music with it in my pocket and it goes out. Quite a few times I've been texting or something and watched it just shut off.
It was right around when I flashed AOKP M5, so I assumed it might be that. I tried a new kernel first, which didn't help. Today I flashed MIUI, hoping it would fix my problem, but nope. Still getting reboots. So it does not seem ROM related.
Anything else I should try before trying to get my phone replaced? Who would the warranty even be through. I bought the phone from Amazon wireless. Them? Verizon? Samsung?

go back to complete stock, then see if the problem occurs

Maybe try using the samsung stock rom, without root. If you still have the problem, I think you should contact amazon. Be sure to reset the flash counter before you send it away
Sent from my GT-9100 using ICS Remix pro AOKP

There isn't a flash counter on the GNex.

[Q] Phone stuck booting up at Galaxy S III after random shut offs

So, I had rooted my phone awhile back, but have not touched root or anything since doing the official Kies Jelly bean upgrade. Phone has been working fine since Getting Jelly Bean.
Two days ago my phone starting just shutting down, the only time it had done this before was while plugged into a car charger.
This time it was the home charger. yesterday It was working with no problems for about 12 hours, then when plugged in it shut down again.
this time it kept randomly shutting down. I started uninstalling apps running to see if one was the problem. It eventually worked for about and hour. Went to sleep, woke up phone was off. It would then turn on and stay on for about a minute. I was finall going to do a factory reset.
I did not get to start the factory reset before it shut down again. It slowly degraded until now it begins to boot, shows the samsung screen, then hangs at the Samsung Galaxy S III screen.
Is there any kind of odin one click back to stock I can do, or do I need to try and get a warranty exchange?
EDIT: Realized I had forgotten about stock recovery, tried to boot into it, and..... now phone won't power at all, I think it's beyond hope.

[Q] Galaxy Nexus Reboot/Screen of Death Issues

Hello, everyone, this is my first post here, and after doing much research on my problem, I haven't had much insight into solving my problem permanently. tl;dr version is at the last paragraph.
First off, I installed AOKP on my phone for the first time a couple months ago and I had no problems for two months for reboots or anything like that, and I believe my phone was overclocked to 1520 mhz on the SmartReflex voltage settings. I did not undervolt whatsoever. In this phase, whenever I would turn it on, I would get to the boot animation, then the animation would hang, and the screen would rise to the highest brightness, flicker, and reboot, or shut down.
Then, in my troubleshooting, being the idiot I was, I accidentally unplugged it while I was flashing back to stock using ODIN. I got the "Android triangle computer" A.K.A. the "Soft Brick" signal. If I booted it normally, into my recovery, ODIN mode, whatever, I would get the same signal.
So, I left my phone alone for a couple weeks, accepting failure. Two weeks ago, I rebooted again into Odin mode, and I saw that Odin on my PC still recognized it, so I connected it and reflashed the stock ICS rom. I re-rooted and installed AOKP, all was fine for two/three days.
After that, the reboots started to happen again, and after a week of constant rebooting, and restoring latest backups,I set the CPU back to normal with no overclocking. I also undervolted but left "Set On Boot" unchecked for everything, This seemed to work fine for normal use, but I still had the phone on "InteractiveX" as the governor. So, when I would go to sleep, I would wake up and the phone would not be on. I would have to battery pull, reboot, etc. I thought this had something to do with one of the cores being turned off when the screen is, so I changed the governor to "Interactive" and the phone would charge now the same.
Now, the problem is, yesterday, I was fiddling with some benchmarks and I OC'd to 1520 for fun, and the phone screen froze, rose to the highest brightness, and shut down. I didn't have it "set to boot" so I thought everything should be fine, so I rebooted and the same thing happened at the boot animation which happened to me when I OC'd. I restored a Nandroid Backup I had before I set it to 1520, and still, no dice.
I reflashed my recovery then, because sometimes it would just freeze at the Google logo and not boot into recovery at all. Then, I restored my Nandroid again, and it booted into Android. After a few minutes, it crashed with the same "High Brightness, Screen Flicker". I restored again, and this time, I rushed into the "Performance Tab" and set my undervolt settings. The phone worked smoothly until I turned the screen off, and then I got the "Screen of Death". Basically, the screen stayed black, but the notification light was still on, and there was no response. So I pulled my battery and tried to reboot, but at the boot animation, the Nexus logo goes into "High Brightness, Screen Flicker". So, I took the battery out, and the phone is just sitting here now for fifteen or so minutes while I typed this out.
My question is, has anyone been having these same issues with their GNex. Because at this moment, I'm thinking I caused a hardware defect for running on 1520 for so long previously and I fried some inner components. Any help?
Edit: I put the battery back in and still the same thing. Going to charge overnight and let it sit, but if anyone has any help, please come forward.

Bump

First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus

Sorry
bk201doesntexist said:
First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus
Click to expand...
Click to collapse
First post here, didn't know much about rules. Thanks for the response. My Nexus did come back, just about 5 minutes ago. I'm going to stay on AOKP for a day and if I don't encounter any problems, I'll stay on it. If I do, I'll revert back to stock.

So yeah, **** this
bk201doesntexist said:
First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus
Click to expand...
Click to collapse
It was working fine until I got 3 or 4 Sleeps of Death a day until today. It just stopped working, and I restored my backup multiple times, but it would just hang at boot or bootloop. So I'm like **** this, so I flashed the stock image for 4.2.2 through Fastboot, and it still didn't boot, even after complete data wipe through the stock recovery. So, I thought it must be 4.2.2 that is doing this, so I installed the 4.1.1 and still the same result.
I'm so done with this thing, it's a hardware issue, total crap of a phone. If it is actually meant to be tinkered with and to be a "developer's phone" this crap wouldn't happen.

[Q] [SOLVED] [Hard Brick] AOKP 7.9.2013 - SGH-I747 - Ideas?

Hi, this morning I was charging my phone, received a call, and phone shut off. It literally did a single ring and then off. I went to turn on the phone, thinking it was just overheated, noting it was cool to the touch. When I went to turn the phone on, it vibrated on boot like normal, except nothing was displayed on the screen. Further waiting (approximately 2 minutes) led to nothing. I attempted to power on again, with the same vibrate, same thing. I removed the charger, then the battery for about a minute. Replace battery, left out charger, same thing. Replace charger, same thing. I had been running AOKP fine previously. Before that I had been running stock AT&T 4.1.1 . I followed Tasks' instructions in his post, I'm not new to this process. I've been following him since the S2 (SGH-I777), never had any kind of brick at all. I've also compiled CM and AOKP myself before and am not new by any means to linux. But I have no clue what just happened here and no kind of recovery or bootloader is available from what I can see on the phone and through ADB. It simply will not power on. I don't have a multimeter to rule out the battery but it seems unlikely to me that in just under 8 months of use the battery died on me. I'm not a heavy user, and typically get 3 days use out of a single charge. Anyone heard anything on the grapevine?
EDIT: I put the wrong release date in the title when I went to look at his releases. It's the 7/9/2013 release.
EDIT #2: I pulled out the SIM card to place in a backup phone and I tried booting the phone again. It started up, got to the loading screen, shut off, and now its back where it was. Considering playing with my SIM in the phone to see if I can trigger anymore activity.
EDIT #3: Success, flipping the SIM seemed to trigger something, I was able to put the phone in Download successfully. Flashing new recovery now, stay tuned.
EDIT #4: When I was able to boot the phone after flashing Jiangyi's AIO (From tasks post). I immediately booted into recovery, flashed 7/20b and 7/14 gapps, looking good so far.

[PLEASE READ] 4.3 Update Crashes Phone!!

PLEASE TAKE THE TIME TO READ, THANK YOU.
Hello,
I am a Galaxy Nexus user, non rooted, running Android version 4.3. Yesterday I was running 4.2.2 and everything was fine and running as normal. Keep in mind I never rooted my phone, although I have to others in the past. My Nexus was running pure official 4.2.2. I had been waiting for the 4.3 update and was extremely excited when I was the notification that it was ready for my phone. I quickly downloaded it and then it rebooted the phone, as any update should. That's where everything went downhill. The phone started to lag immediately when I turned it on. It was sputtering and jerking but I just thought it was getting used to the update. Then the phone would loose its onscreen buttons and turn the page that I was looking at full screen (meaning I couldn't press home or back, because they simply just weren't there). Then the phone froze all together and after waiting 20 minutes I finally took the battery out and tried again. The EXACT same thing has been happening ever since yesterday and it has made the phone unusable because it will freeze 5 minutes into turning it on. And we then screen times out, the screen will not turn back on, as if the phone was off, when it is not. I'm very frustrated because the phone was working flawlessly before the update and now I have to use my retired G1 because the phone is that unresponsive. I was just hoping someone could please help me, or has a similar story and could make this known to Google. Thank you for reading, please if you can, help me.
Justin

holiday29 said:
PLEASE TAKE THE TIME TO READ, THANK YOU.
Hello,
I am a Galaxy Nexus user, non rooted, running Android version 4.3. Yesterday I was running 4.2.2 and everything was fine and running as normal. Keep in mind I never rooted my phone, although I have to others in the past. My Nexus was running pure official 4.2.2. I had been waiting for the 4.3 update and was extremely excited when I was the notification that it was ready for my phone. I quickly downloaded it and then it rebooted the phone, as any update should. That's where everything went downhill. The phone started to lag immediately when I turned it on. It was sputtering and jerking but I just thought it was getting used to the update. Then the phone would loose its onscreen buttons and turn the page that I was looking at full screen (meaning I couldn't press home or back, because they simply just weren't there). Then the phone froze all together and after waiting 20 minutes I finally took the battery out and tried again. The EXACT same thing has been happening ever since yesterday and it has made the phone unusable because it will freeze 5 minutes into turning it on. And we then screen times out, the screen will not turn back on, as if the phone was off, when it is not. I'm very frustrated because the phone was working flawlessly before the update and now I have to use my retired G1 because the phone is that unresponsive. I was just hoping someone could please help me, or has a similar story and could make this known to Google. Thank you for reading, please if you can, help me.
Justin
Click to expand...
Click to collapse
Did you tried a full wipe?

tatazeuz said:
Did you tried a full wipe?
Click to expand...
Click to collapse
I have not tried that, only because I hoped there would be an alternate way without me having to format anything.

holiday29 said:
PLEASE TAKE THE TIME TO READ, THANK YOU.
Hello,
I am a Galaxy Nexus user, non rooted, running Android version 4.3. Yesterday I was running 4.2.2 and everything was fine and running as normal. Keep in mind I never rooted my phone, although I have to others in the past. My Nexus was running pure official 4.2.2. I had been waiting for the 4.3 update and was extremely excited when I was the notification that it was ready for my phone. I quickly downloaded it and then it rebooted the phone, as any update should. That's where everything went downhill. The phone started to lag immediately when I turned it on. It was sputtering and jerking but I just thought it was getting used to the update. Then the phone would loose its onscreen buttons and turn the page that I was looking at full screen (meaning I couldn't press home or back, because they simply just weren't there). Then the phone froze all together and after waiting 20 minutes I finally took the battery out and tried again. The EXACT same thing has been happening ever since yesterday and it has made the phone unusable because it will freeze 5 minutes into turning it on. And we then screen times out, the screen will not turn back on, as if the phone was off, when it is not. I'm very frustrated because the phone was working flawlessly before the update and now I have to use my retired G1 because the phone is that unresponsive. I was just hoping someone could please help me, or has a similar story and could make this known to Google. Thank you for reading, please if you can, help me.
Justin
Click to expand...
Click to collapse
Hi Justin,
I'm also a Galaxy Nexus user and the exact same thing happened to me.
I guess you already did a full wipe or threw your phone in the trash since you posted this several days ago haha. I did wipe my phone cuz it appeared to be the only option left, I fastbooted 4.3 factory image that I downloaded from the Google site.
It just so happens that yesterday I reinstalled (on 4.3 already) Lightflow LED Notifications app (last version, 3.8 I think, - when all of this happened I didn't have the last version - and the curse was back on. The same thing started to happen, the freeze, the buttons dissapearing, etc. So I obviouly proceeded to uninstall the app and guess what? Problem solved.
So I was just telling you this in case you still have your issue or if anybody else comes accross with the same problem.
I cannot be absolutely sure it's a crash between the update and the app but I think, at least on my phone, it was pretty obvious.