Nexus reboots on its own constantly on multiple roms - Samsung Galaxy Nexus

Ok, I'm at a total loss. For some reason my gnex running liquidsmooth started rebooting randomly today. I tried wiping cache/dalvik and that didn't work, so I did a factory reset. That also didn't help, as soon I was asked to choose a wifi network the phone froze and rebooted. So I tried restoring to a previous working version of liquid. I still had the same problem. It rebooted every 5 minutes! Then, I tried wiping everything and installing a fresh copy of liquid,but I still couldn't get past choosing my wifi network w/o a reboot. So I finally tried restoring to a really old aokp backup and it STILL is rebooting. what the heck is going on? Can anybody give me any help? Is this a hardware issue? I've also tried two different batteries by the way.

Some more info. It seems to be tied to notifications. I got it running on the AOKP rom on airplane mod, but when i received a text from my wife it rebooted 3 times. I only got it to stop by putting it back into airplane mod. Could it be a radio issue? I'll try flashing some.

why dont you flash back to stock and see if that works fine. that will tell you everything.

Zepius said:
why dont you flash back to stock and see if that works fine. that will tell you everything.
Click to expand...
Click to collapse
Good point. I'll probably try flashing muzzy's rom really quick, since it's supposed to be so stable to see if that does the trick. If not I'll try going back to stock. I've never had to go back to stock with this phone, so I wouldn't mind avoiding it if I can, but anything is worth a shot at this point.
I really just need to nurse it along until the VZW one or Moto X come out. I'm holding out for those at this point.

I wouldn't recommend flashing another custom ROM. You should flash the factory images.

Related

[Q] I am absolutely stumped, please help

Hi All, I come begging for help after exhausting all of my options and searches for similar issues.
I have a CDMA Galaxy Nexus Stock 4.0.2 but rooted (I installed CWM).
I woke up to my phone stuck in the boot loading screen; it just kept looping over and over. I shut off the phone restarted it and the phone was practically unuseable, it ran very very slow. Now I haven't done anything recently or installed any apps. The only app I installed was a modified MMS app (one of the Inverted Black ones), but that was 2 weeks ago and everything was running fine since then. (However since I'm not on a deodexed Rom, I knew there could be issues).
Well I of course switched back to the stock MMS app that I had manually backed up and that did not help. Now my phone would load, it would get to my homescreen, but it would then say something along, "service is not working, wait, close, or ok?" I'd hit wait and within 2 minutes my phone would automatically reboot and then go into a a sort-of bootloop (it would just show the boot.img and loop).
I then tried to restore two Nandroid back-ups (which were basically bone stock and made months ago) and both worked, except it would say secure.img not found or something like that. I was still able to boot up and use these back ups, but then within 5 minutes I would get the same error and then the phone would reboot.
After retrying them I decided to to just go bone stock and wipe and do a factory reset. This worked and everything seemed fine until I went to turn on wi-fi.
I would wait for wi-fi to turn on and eventually it would just quit and then reboot the phone. I did this 3 times in a row to confirm that it was indeed wi-fi causing these rebooting issues.
Now here's the thing, right now my phone is working as I have purposely tried not to touch the wi-fi (I need to use my phone) . Data, voice, mms/sms all work. But I literally have no idea why wi-fi would be causing my OS to go crazy?
My last resort is to flash the stock toro.img but I was hoping you guys could help me before I get to that point.
As of right now even though I did a data wipe/factory restore my phone is still rooted (rooted apps all work) and my bootloader is still unlocked. (I renamed the secure.bootloader file as per the instructions when using fastboot to load CWM).
Please help me troubleshoot this, Thanks guys.
I don't know if you have tried but maybe try flashing a rom after a data wipe
angelino0919 said:
I don't know if you have tried but maybe try flashing a rom after a data wipe
Click to expand...
Click to collapse
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
JayBeezy802 said:
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
Click to expand...
Click to collapse
Well you can always relock the bootloader. I doubt you will have to go back to stock though

WiFi going nuts

I've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Re-Install your Rom, first.
Update your Radios.
Simple.
alexdz said:
I've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Click to expand...
Click to collapse
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
vdude8 said:
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
Click to expand...
Click to collapse
I failed to mention initially, but I did try updating the radios as well. Regardless, I'm not having the problem anymore, and it's possible that there was simply something in my Titanium backups (done while on ICS) that it didn't like. I started thinking back on the timing and realized that the issue was showing up only after I went through the batch restore process, so this time I only restored a few apps that had data I didn't want to lose, and nothing else. So far so good.
Except of course that I'm now having a new problem that may be associated with a2sd, but I'll post that in that Deck's Reloaded thread...
Thanks!
I had a lot of force closes after restoring ICS backups in GB. Don't think the backups are backwards compatable...not all the time anyway.

[Q] Phone deactivated?

I was running latest paranoid android and I wiped cache/dalvic cache after flashing Cerberus in recovery and when the phone booted up it was asking me to Activate (sprint service) my phone. I've never seen this with flashing roms and was wondering if this is a known issue with flashing roms on the S3 or something that can randomly occur from time to time.
Anyone have experience with this before? I had been running Paranoid Android for less than 24 hours but initially didn't have any problems whatsoever.
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
youdoofus said:
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
Click to expand...
Click to collapse
This didn't have anything to do with my Google account. I guess I should have been more specific, I mean that my phone is deactivated on Sprint's network as in I can't make phone calls and all the info is missing in about phone. Phone number, PRL and such. I am flashing back to stock right now and hope this fixes it. Will probably give paranoid another go but this doesn't sound like a common issue because I haven't been able to find anything by searching.
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Ahhh... could try manually flashing your modem after the install too
sent from my thumbs
billard412 said:
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Click to expand...
Click to collapse
Soon as I flashed the stock rom it tried to activate and initially failed and prompted me to reboot. Second attempt it was successful and then I immediately flashed back to PA and it is working. Going to give it another shot and keep the stock rom on my sd card this time in case I get stuck in a pinch.
I jumped the gun, phone activated fine but signal drops in and out randomly and will not connect to 3g. Just reflashed to stock again and everything seemed fine but signal was still back in and out. Checked under status and PRL read "0" tried updating to no avail so did the dialer code and it did the activation and all is right in the world again, or at least for the moment.
Just trying to figure out why when I flash Paranoid all my settings just disappear
*edit*
Just flashed back to PA this third time after fully making sure that the phone was working and had 3G data and all was right with the world (my phone). Will update if it goes South again but as of right now the phone is behaving properly. Maybe it just wasn't working right the first time and I didn't notice since I was on wifi. Only thing that keeps me from thinking that is I didn't get the Activation message until 12 hours or so after I had flashed and had been using the phone. /shrug
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
youdoofus said:
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
Click to expand...
Click to collapse
how do you flash a modem? I am new to this and this is also a problem that I am having with the same rom. I tried searching for a fix and this is where i landed.
Thank you,
and sorry if i am breaking forum rules

[Solved] Urgent, LTE issue.

Solved! ODIN'd back to stock and LTE kicked in immediately. Back to flashing =) Thanks guys!
Original Post:
============================================================================
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
RPelham said:
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
Click to expand...
Click to collapse
Running galaxymod right now and in DFW area with great LTE coverage and never had the issues you had or any for that matter. Somehow in the flashing, I'm going to get real technical here right now , something got borked that isn't affected by flashing a new ROM. We could give to several things to try but honestly flashing back to factory out of the box and starting from there is the only fail safe way to do it. probably faster too. That's I would do
hednik said:
Running galaxymod right now and in DFW area with great LTE coverage and never had the issues you had or any for that matter. Somehow in the flashing, I'm going to get real technical here right now , something got borked that isn't affected by flashing a new ROM. We could give to several things to try but honestly flashing back to factory out of the box and starting from there is the only fail safe way to do it. probably faster too. That's I would do
Click to expand...
Click to collapse
Thanks for the reply. I just downloaded root-injected stock and am flashing as we speak. If this doesn't work, I'm going to flash back to bone-stock and see how that goes. I'll report back and let everyone know =)
RPelham said:
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
Click to expand...
Click to collapse
Did you check to see if your IMEI is missing?
I had the same issue on GalaxyMod. I had to do a clean install of the ROM, apply KT's kernel, and apply the LTE fix BEFORE I rebooted. I could not tell from your post if you did a clean install of GalaxyMod. Then I checked my IMEI and it was missing, so I performed the fix found here http://forum.xda-developers.com/showthread.php?t=1801997 and repeated the steps above. Worked for me as I get LTE speeds now on GalaxyMod.
peaster3 said:
Did you check to see if your IMEI is missing?
I had the same issue on GalaxyMod. I had to do a clean install of the ROM, apply KT's kernel, and apply the LTE fix BEFORE I rebooted. I could not tell from your post if you did a clean install of GalaxyMod. Then I checked my IMEI and it was missing, so I performed the fix found here http://forum.xda-developers.com/showthread.php?t=1801997 and repeated the steps above. Worked for me as I get LTE speeds now on GalaxyMod.
Click to expand...
Click to collapse
I'm getting LTE speeds, problem is after toggling airplane mode or rebooting the phone it takes up to 10 minutes for LTE to activate. I fresh installed GalaxyMod, wiped everything possible in the wipe menu of TWRP with the exception of external SD.
I also applied the LTE fix before I booted GalaxyMod, but I did not flash KT747. I prefer to not flash that kernel because it has the updated BT/WIFI drivers and had a warning that I would need to back those drivers up if I ever wished to revert. I don't really feel like going through all of that lol.
Solved. ODIN'd back to stock =) Thanks hednik!
RPelham said:
Solved. ODIN'd back to stock =) Thanks hednik!
Click to expand...
Click to collapse
Glad it worked.... these phones are almost fool proof as you can start with a clean slate if all else fails. Glad it worked
IMEI was still intact ?
hednik said:
Glad it worked.... these phones are almost fool proof as you can start with a clean slate if all else fails. Glad it worked
IMEI was still intact ?
Click to expand...
Click to collapse
Yupp I haven't yet lost my IMEI since I got the phone back in July. Guess I'm lucky so far, see posts all the time where people lose it, and I'm a flashaholic lol.
Sent from my SGH-I747 using xda app-developers app

[Q] S3 Turning Off on its Own

I've been regularly running cyanogenmod 11 on my Bell S3 without many issues. Last going off, I believe I was running either M11 or M12 of CM11, and all was well. Then, curiosity got the best of me, and I slapped on CyanideL Lollipop beta, and while that ran pretty damn well for me for about a month, I reverted back to CM11 a few days ago due to some minor bugs and annoyances (mostly camera). Anyways, since reverting back to CM11 M12, my phone has been randomly shutting off, not rebooting, just off. It has happened while it's in my pocket not really in use, or it can happen while I'm going to check my text messages.
Thinking this was an issue maybe with M12, I updated to the latest nightly, but nope, its still the same. Some of the times that its happened in my hands, I've seen the Power Button menu pop up, and then disappear. A few seconds later, boom, off she goes. It always powers up again when I power it back on, but I would like to try to get to the bottom of what is causing this, as it is being very annoying for me.
The question is, what can I do to try and nail down this issue? When flashing back to CM11, I did the full wipe, then dalvik/cache after the flash. Is there something that happens when you go from 5.0 back to 4.4 that may cause this?
This is possibly related. I tried out an unofficial cyanogemmod 12 rom on my AT&T S3 for a while, but decided to revert due to camera not working. So I installed S3Rx ROM on the phone and had some issues. The phone would get stuck on the loading screen and never get past that. I did the standard data/factory reset, cache wipe and dalvik wipe before installing S3Rx back, but no luck. The only way I could get it to install correctly was by formatting /system, /cache, /data and /data/media in ClockworkMod recovery. But be aware that you will lose all personal data when you do that so be sure to backup.
Alright, I'll backup what I need to, and do a full wipe as you suggested. I'm pretty sure I did that when I downgraded to begin with, but no hurt in trying it again.
You could flash back to completely stock 4.4.2 using firmware from sammobile.com, depending on the bootloader on your phone.
audit13 said:
You could flash back to completely stock 4.4.2 using firmware from sammobile.com, depending on the bootloader on your phone.
Click to expand...
Click to collapse
If I do go back to Stock 4.4.2, would I be able to re-root again? Its been a couple of years since I had to mess with stock, so I don't know what has changed.
I've tried a few different things here, completely wiping everything, installing a 4.4.4 kernel, installing CM11 from scratch, restoring from TWRP, etc etc. Still having the issue.
Last thing I'll try before going to stock is to try going back to lollipop.
Update: I'm starting to think that this is just a coincidental hardware issue. It seems to have something to do with my power button, perhaps there's something stuck in it that's cause the button to be pressed. Right before it shuts off, the power menu pops up for a split second once or twice, then the phone becomes unresponsive for a second, then its off. Certainly sounds hardware related. Just attempted lollipop again, and same result.
I think you are correct in your assessment. Open up the phone and see if you can find anything that looks odd.

Categories

Resources