Hey guys, my gnex has just been stricken (for the second time) by the boot loop. Managed to fix it last time with a flash of the google image, but this time it isnt working.
Same as usual, mine features the greyed out wifi toggle as well, and reboots every time the screen goes off (which makes sense that I've been noticing it go off every 2 minutes).
I have found that the device will not reboot if it is plugged in and set in the dev options to "stay awake" while charging. This seems to keep it running, same if I set the time-out to longer. My theory has to do with the distribution of power...I think that something is telling the phone it doesn't have enough power to function.
Like everyone else I've done endless factory resets, flashed the goog image and such and such to no avail. Currently stock but I left my bootloader unlocked atm. I can still boot into recov and everything and even flash other roms.
Has anyone else noticed this, or could someone who is also having the problem confirm the screen thing?
I think last time I posted I was on winmo, missed this forum.
Bump? Anyone else having this issue?
Just send it in for warranty. I sent mine in and Samsung exchanged the phone
I havent been paying attention, are many people having this issue? It sounds scary. Were you on a custom rom when this started?
My Nexus has been stuck on "Turning WiFi on.." since I've had it. It would also constantly boot loop itself whenever the screen went off. I flashed the new AOKP build to avoid this issue, however, the WiFi still does not work If I'm ever on stock again, I'll give stay awake a shot.
I live in the U.S. with the GSM GNex, so warranty is out of the question unfortunately.
Fixed the loop by flashing aopk again with franco's kernel. Brilliant but my Wifi is still messed up. I flashed a new baseband XXKL1 and no improvements. I'm gonna just wait it out for a bit because I've seen some threads elsewhere where that has actually worked, but who knows. I'll probably cave and send it out soon.
RogerPodacter said:
I havent been paying attention, are many people having this issue? It sounds scary. Were you on a custom rom when this started?
Click to expand...
Click to collapse
Yes and no. It happened twice and the second time I fixed it by going FROM stock to AOPK with included kernel. Now it happened on THAT setup so I went back to stock and no dice. Its a very weird problem....
I got exactly the same problem. Wifi didn't work (grey toggle) so I tried to bring the warranty conditions back, but got an endless boot each time screen goes off.
mastergrifis said:
I got exactly the same problem. Wifi didn't work (grey toggle) so I tried to bring the warranty conditions back, but got an endless boot each time screen goes off.
Click to expand...
Click to collapse
Try booting into the bootloader and using the gnex toolkit to go back to stock and relock. Good luck. Logcat isnt even logging my wifi issues, its like my wifi adapter was removed entirely.
ShatteredAxe said:
Try booting into the bootloader and using the gnex toolkit to go back to stock and relock. Good luck. Logcat isnt even logging my wifi issues, its like my wifi adapter was removed entirely.
Click to expand...
Click to collapse
That's what I did, I used the toolkit to go back to stock and after that I got those annoying reboot. Of course wifi doesn't work anyway... That's really frustrating
mastergrifis said:
That's what I did, I used the toolkit to go back to stock and after that I got those annoying reboot. Of course wifi doesn't work anyway... That's really frustrating
Click to expand...
Click to collapse
You and I are in the EXACT same boat my friend. I just cant afford being without this phone, my job depends on social media and email. DAMN YOU SAMSUNG!!!!!
ShatteredAxe said:
You and I are in the EXACT same boat my friend. I just cant afford being without this phone, my job depends on social media and email. DAMN YOU SAMSUNG!!!!!
Click to expand...
Click to collapse
I have a Desire Z by my side, but of course I want my Gnex back as new. The only thing that scares me is the warranty. I'm not sure if it's still valid. I mean, apparently there's no sign of root/bootloaderunlocked, but how can I explain that suddenly my phone has started rebooting itself without any reasons?
Yeah, only option is to just try and see what happens.
Related
Hi everyone,
It's been a while since I've been active here, but I've recently discovered a weird problem with my phone - I can't get it to turn *off*.
I rarely try to turn it off, so I have no idea how long it's been doing this, but I was on a plane recently and discovered that whenever I try to power it off, it'll pop right back on as soon as it shuts down.
I'm on CM7.1.0, but it's the same when I go back to my nandroid backups of 7.0.3, 7.0.2, and even stock 2.2! I have then eng-hboot (0.76.2000), radio is 26.08.04.16_M, recovery is CWM 5.0.2.0, but the same thing happened on 3.0.2.4. I can provide more info if needed.
Can anyone help?
Just... take the battery out?
martonikaj said:
Just... take the battery out?
Click to expand...
Click to collapse
Thats not really a permanent solution is it ?
bombadier said:
Thats not really a permanent solution is it ?
Click to expand...
Click to collapse
But I mean how long is he going to keep his phone off for? If you're keeping the phone off for a long time, you shouldn't store it with the battery inside anyways.
chinly43 said:
Hi everyone,
It's been a while since I've been active here, but I've recently discovered a weird problem with my phone - I can't get it to turn *off*.
I rarely try to turn it off, so I have no idea how long it's been doing this, but I was on a plane recently and discovered that whenever I try to power it off, it'll pop right back on as soon as it shuts down.
I'm on CM7.1.0, but it's the same when I go back to my nandroid backups of 7.0.3, 7.0.2, and even stock 2.2! I have then eng-hboot (0.76.2000), radio is 26.08.04.16_M, recovery is CWM 5.0.2.0, but the same thing happened on 3.0.2.4. I can provide more info if needed.
Can anyone help?
Click to expand...
Click to collapse
Does this only happen when the device is plugged into the charger/connected via USB?
Sent from my HTC Vision using XDA App
1) Yes, pulling the battery works of course, but there should be a way to turn it off without doing that. And it comes on instantly when the battery is reinserted.
2) It happens regardless of whether it's plugged in or not.
Maybe I should try re-installing the engineering fastboot? Or try a different radio?
This was happening to a lot of CM Nightly users a few months ago (myself included), and it fixed itself a few days after it started. I still have no idea what caused it.
Sent from my Transformer TF101 using xda premium
This happened to me just the other night. I needed to power off for a short while - I pulled the battery. I don't think it happens every time, but I was able to pull the battery and then reinsert it without the phone rebooting immediately.
It happens to me form times to times but i think its nothing serious so i just take the battery out
An update - I tried turning it off while plugged into my computer and watching the log in DDMS; it *CAN* turn off when it's plugged in! Still nothing when it's unplugged, though.
Anyone have any ideas how to fix this? Like others have said, it's not like this is a major problem - I can always just pull the battery if I need the power to be off for some reason. And it's not like phones really need to be off for air travel, so I can't even think of a reason I would need it off, but still - this is obviously a flaw in something, and I can't stand knowing that it's not working exactly right. I think I'm going to flash a different radio, see if it makes a difference, but if anyone has any ideas how/why this is happening, I'd really appreciate you sharing them.
ETA: updating the radio didn't change anything.
same problem--- keeps turning back on
IOn my Desire Z running MIUI, i turn it off and it shuts down to turn itself back on! Very annoying, particulary when on a plane. Taking the battery off, OBVIOULSY fixes it. But not a very practical solution.
Similar to post above, it stays off when connected to USB. Go figure!
I think I read somewhere that this was a clwm issue with the most recent recovery, have you tried flashing a different one? Older or maybe try 4ext?
PS just reread your first post sorry, it seems you already tried a different recovery.
For the OP, since you tried reflashing, and I'm sure you wiped, then I would imagine it isn't a issue with the ROM, the radio didn't help so maybe bootloader or recovery.
OP here, sorry I hadn't checked in for a while. For unknown reasons, the problem's gone. No big changes to my phone, so the issue vanished as mysteriously as it appeared.
Alright so ive used the search and couldnt find anything. I have a rooted s2 running eagles blood v1.1 and last night i flashed over lite'ing theme and now my phone screen will shut off and wont allow me to turn it back on, i have to hold the power button and it restarts. Ive reflashed eagleblood even recovered back to stock with just root and it continues to do it.
Any help would be much appriciated :/
Sent from my SGH-T989 using XDA App
Probably best to post this in the rom developer's thread. Any number of things can cause this behavior.
I would but my post count is low and i am unable to post there, so for now i am seeking help here.
ive tried un-rooting the phone, flashing the stock rom and no root, but have the same issue.
Did you wipe the caches in recovery?
treo...not! said:
Did you wipe the caches in recovery?
Click to expand...
Click to collapse
sure did, every time i reflashed/flashed i wiped everything
still contines, ive wiped everything, unrooted with factory resets, tried stock rom, eagles blood rom, reflashed multiple times.
screen shuts off and will not turn back on, have to hold power button and phone reboots.
IProbablyDidit said:
still contines, ive wiped everything, unrooted with factory resets, tried stock rom, eagles blood rom, reflashed multiple times.
screen shuts off and will not turn back on, have to hold power button and phone reboots.
Click to expand...
Click to collapse
Are you using SetCPU? I had this problem from a screen off profile where I could get calls or have my alarm go off yet not able to wake the screen unless I manually powered it off and on.
Sent from my EagleBlood-infused SGSII or my GTab 10.1 now "In Paris"
bhowanidin said:
Are you using SetCPU? I had this problem from a screen off profile where I could get calls or have my alarm go off yet not able to wake the screen unless I manually powered it off and on.
Sent from my EagleBlood-infused SGSII or my GTab 10.1 now "In Paris"
Click to expand...
Click to collapse
setcpu ? youll have to bare with me a little bit as i dont know probably all i should
odin back to stock with zedomax file! that usually fixes all probs
GRAB THIS STUFF :http://forum.xda-developers.com/showthread.php?t=1323878
Enjoy and also make sure u have the proper samsung drivers
movieaddict said:
odin back to stock with zedomax file! that usually fixes all probs
GRAB THIS STUFF :http://forum.xda-developers.com/showthread.php?t=1323878
Enjoy and also make sure u have the proper samsung drivers
Click to expand...
Click to collapse
i have tried this already, does not work :/
I'm having the same problem on rooted stock rom. It's getting more and more frequent. The phone just refuses to come back on after going to sleep. If I plug in the power/usb cable, it actually makes the connected noise as if it's actually awake but the screen stays off.
I've uninstalled all cpu and memory tweaking apps and am still experiencing the issue.
KaneHusky said:
I'm having the same problem on rooted stock rom. It's getting more and more frequent. The phone just refuses to come back on after going to sleep. If I plug in the power/usb cable, it actually makes the connected noise as if it's actually awake but the screen stays off.
I've uninstalled all cpu and memory tweaking apps and am still experiencing the issue.
Click to expand...
Click to collapse
ive tried everything, flashed over and over, un rooted, different roms etc nothing has worked so i just used zedomax's stock rom to restore the phone ( problem still continues) called tmobile and will have my replacement within a day or so, nothing else i can do i suppose.
though my problem did seem to start right when i flashed lite'ing theme for eaglesblood (not saying that caused it )
IProbablyDidit said:
ive tried everything, flashed over and over, un rooted, different roms etc nothing has worked so i just used zedomax's stock rom to restore the phone ( problem still continues) called tmobile and will have my replacement within a day or so, nothing else i can do i suppose.
though my problem did seem to start right when i flashed lite'ing theme for eaglesblood (not saying that caused it )
Click to expand...
Click to collapse
i had the same problem with the phone when i got it , i think its gotta be something with the phone.if mine continues then im sending it back also
tigerz0202 said:
i had the same problem with the phone when i got it , i think its gotta be something with the phone.if mine continues then im sending it back also
Click to expand...
Click to collapse
im starting to think it is a phone issue myself, going to find out Tuesday when my new one arrives though i am hoping it was an error on my part because this phone has the chance to be fantastic.
I was having random shutdowns with my 1st phone, the thing is I never did have stock long enough (rooted after 45min of gettjng) to see if it was the phone or root/rom(s).
My second phone is working great without any random shutdowns, but I'm still stock(running on second day of testing).
Gonna root and flash tomorrow and hope everything remains the same if not back it goes before my remorse period ends.
I really think it's phone related rather then a rom because I've never had this problem with previous phones.
So I would suggest on exchanging it.
Sent from my SGH-T989 using xda premium
htc2364 said:
I was having random shutdowns with my 1st phone, the thing is I never did have stock long enough (rooted after 45min of gettjng) to see if it was the phone or root/rom(s).
My second phone is working great without any random shutdowns, but I'm still stock(running on second day of testing).
Gonna root and flash tomorrow and hope everything remains the same if not back it goes before my remorse period ends.
I really think it's phone related rather then a rom because I've never had this problem with previous phones.
So I would suggest on exchanging it.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
i do appreciate the feed back, and from everyone who did give it. after lots of research and back and fourth between stock and custom roms i definitely wanted it to be the rom so it was fixable but im about 96% sure its the actual phone its self.
Alright, so here is what's going on.
I had my alarm go off earlier today, got up, unplugged my phone like normal. I swiped off the notifications I didn't care about like a tapatalk message etc. I noticed that Google Current's automatically updated. I'm sure that's no huge deal.
I locked the screen and went about my day. I tried to swipe to unlock, and the phone freezes and reboots. The phone is responsive until you unlock it, then it just freezes and reboots.
Tried safe mode once, and it worked fine. I then turned it off, and tried normally booting again, same freezing and rebooting. So I went to go back to safe mode, and now safe mode is doing the same thing, which means that a factory reset is now out of the question.
What the hell man.
Specs:
- Samsung Galaxy Nexus
- All stock apps except added Facebook and Tapatalk
- Jellybean 4.2.2 software I believe. I'd double check if I could.
- Still locked and unrooted
Any ideas on where to go from here? No warranty, so any ideas would help
It turns on, goes to lock screen. Then freezes when I try to get anywhere from that lock screen. Even on safe mode.
Then it will reboot automatically after about 30 seconds.
I should note I received a text in this time, and thought maybe just pulling the notification bar down and going straight to the text would work. The notification bar works, but when I hit the text, it froze the same way.
This must be some sort of self check or some Android process crashing. But I can't utilize safe mode to fix it.
Any ideas on what to do? I know there are threads with this problem, but this involves an unrooted phone, of which I have seen no threads, or threads with answers. I am not experienced with getting too far into Android, so just a direction to go, or something to try when I get home would be awesome. (At work currently)
The only options I have right now are the options upon booting with the volume down, which are Start - Restart bootloader - Recovery Mode and Turn off. In this screen, here is my info:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro 16GB
HW VERSION - 9
BOOTLOADER VERSION - PRIMELA03
BASEBAND VERSION I9250UGLL1
CARRIER INFO - NONE
SERIAL NUMBER - xxxxxxx
SIGNING - production
LOCK STATE - LOCKED
In recovery mode, I see a dead android guy with a red triangle and an exclamation mark in it.
I realize you guys probably get a lot of dumb questions so I tried unloading all the information I could. My replies will be 5 minutes apart, as I'm new and I see that's a restriction on being here.
Thanks in advance
You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.
Daedalus93 said:
You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.
Click to expand...
Click to collapse
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.
slipstreamconversion said:
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.
Click to expand...
Click to collapse
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme
Daedalus93 said:
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme
Click to expand...
Click to collapse
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again
slipstreamconversion said:
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again
Click to expand...
Click to collapse
Yes. My phone recently was stuck on a bootloop and I've already sent it for repair. Yeah drops are never good
No problem
Hello everyone! I own a Galaxy Nexus that's running one of the Cyanogenmod 4.4 snapshots. While watching a youtube video my phone froze up and shut itself off. I rebooted and after a few moments the same thing happened. When I power up my phone one of two things happen. It either reboots while booting and automatically attempts to boot again or it manages to turn on for a short while and then turns itself off.
I believed the issue was a battery or hardware one at first but after leaving my phone booted in recovery for half an hour with no ill effects I think something else might be up. What do you guys think is the best course of action? The only thing I've done is a factory reset that has done nothing.
Anyone?
Stryking said:
Anyone?
Click to expand...
Click to collapse
Factory Reset and reflash the rom. If that doesn't work try flashing another rom like Vanir. If your phone still shuts off...well unfortunately this may be a hardware related issue, nothing you can do if that's the case. Unless it's your battery which I highly doubt.
I think it's the same thing that happened to me a year ago, check this out:
http://forum.xda-developers.com/galaxy-nexus/help/bricked-phone-t2306672
for me it was a hw related problem, i had to send the phone back to assistance and have it repaired (it was still under warranty).
Good luck :good:
Thank you all for your ideas. I'll report back my findings later today.
Same problem over here. Tried a lot of roms (custom and stock from Google page), took it to assistance (no warranty though) was told is a hardware issue. Since replacing the mainboard its the same price as a new phone... well you know.
But a curios thing happened: tried to flash the Ubuntu Touch rom, same problem (reboots at Ubuntu start screen) and the Firefox-OS, that one worked (considering it's limitations obviously)!
So i have had my zenfone for awhile now. i unlocked the bootloader and was able to root it with a temp CWM. it was going fine for a long time.
Then one day my phone started to act up. wouldn't read texts right, false notifications, and app crashing. i thought maybe i had a virus so i ran a cleaning app (Clean Master and Lookout) but they found nothing. so i thought why not restarting the phone? seems to work for some.... *sigh*
Upon restarting the phone i am now stuck on the ZenPhone flip case thing... with the info on the circle. i thought maybe i dropped my phone sometime or somewhere and the case got stuck. okay simple fix, i tried using a magnet to open the case... and it did nothing.
Then I tired going into recovery mode by going through fast boot. but selecting anything in fast boot causes the phone to "freeze" and endlessly vibrate. It can't even detect when its plugged into the computer so i cant do commands on it from fast boot. i cant even do it from the OS as i think when its in the flip thing it doesn't allow PC access (at least i think). but the strange part about being on the OS, is that when phone goes to sleep (screen turns off), it "freezes".
What i'm asking here is there a way to fix this or is this phone lost. i made this account just for this... please help!
Good luck, I wish I had never bought this phone. I've sent it back to A-Sucks two damn times and it's still nothing more than a phone that always has some kind of an issue.
Chocketbear said:
Good luck, I wish I had never bought this phone. I've sent it back to A-Sucks two damn times and it's still nothing more than a phone that always has some kind of an issue.
Click to expand...
Click to collapse
Well i'm not one for giving up so easily. tho i am stumped on this, i would like it if i didnt have to send this back to asus... plus i think i voided my warranty.
Sonrio224 said:
Well i'm not one for giving up so easily. tho i am stumped on this, i would like it if i didnt have to send this back to asus... plus i think i voided my warranty.
Click to expand...
Click to collapse
You have a different issue, yeah don't send it back.
Maybe you can try twrp manager app to flash recovery if you can boot the system
titou4488 said:
Maybe you can try twrp manager app to flash recovery if you can boot the system
Click to expand...
Click to collapse
I tried that. my computer, or any other computer i tried, doesn't detect its connected when in fast boot nor in the OS.
when trying to use the normal recovery on the phone. it gets stuck in an endless vibration until i turn it off.
Booting into anything (i.e. Normal boot, recovery) from fast boot causes the vibration hang
Sonrio224 said:
I tried that. my computer, or any other computer i tried, doesn't detect its connected when in fast boot nor in the OS.
when trying to use the normal recovery on the phone. it gets stuck in an endless vibration until i turn it off.
Booting into anything (i.e. Normal boot, recovery) from fast boot causes the vibration hang
Click to expand...
Click to collapse
Re-read that, nothing was said about the PC...
ultramag69 said:
Re-read that, nothing was said about the PC...
Click to expand...
Click to collapse
my bad... either way, i still cant get into the OS as its stuck on the ZenPhone flip case thing as i stated above. it wont let me do anything from there.
if the phone cannot be saved. i might as well sell it for parts.
Before that, have you tried totally discharging the battery, leaving for a day or 2 to get rid of any last traces of power from the RAM then recharging and starting up again?
Might be something screwy going on with the phones hardware but these things are literally PC's and sometimes they need to have a good shutdown to get rid of all the quirks stuck in ram.
If you don't want to wait, you could just open up and disconnect the battery. You were only going to sell as parts anyway....
ultramag69 said:
Before that, have you tried totally discharging the battery, leaving for a day or 2 to get rid of any last traces of power from the RAM then recharging and starting up again?
Might be something screwy going on with the phones hardware but these things are literally PC's and sometimes they need to have a good shutdown to get rid of all the quirks stuck in ram.
If you don't want to wait, you could just open up and disconnect the battery. You were only going to sell as parts anyway....
Click to expand...
Click to collapse
haven't tried that. ill fully drain the battery and see where i get
Okay so good news. that actually worked... i think. i took the battery out for a bit and let it sit, then i put it back in and it booted up just fine!
but now i have a new issue, i can no longer talk on phone calls. speaker isn't working for some reason. might have put it back together wrong.
all things considered, thank you so much for the help!
No worries, good luck on the speaker issue...