Hi Guys,
I have my galaxy nexus and suddenly after restart my was is not booting,
I do get Google LOGO and then after my screen goes blank
I tried factory reset from recover mode still no help
I did root my phone with fastboot please some one help me to get my phone back to life
HELP!!!! HELP!!!!
Call 911? Resuscitate it? Give it to me?
Sent from my Galaxy Nexus using xda premium
Do you have an image to flash?
Sent from my Galaxy Nexus using xda premium
thanks mate, i just flushed new Image
i was try to resolve market issue where when i try to guy any app on market i got error,
an error occurred while creating your order" even after new image i have same issue... i don't know how to fix that
My Galaxy \Nexus won't boot....Perpetual flash screen
I got a notice of several (around 16) apps with updates this afternoon. They were very slow to update (I think the AT&T bandwidth was horrible) My phone rebooted -- which it has about 5-6 times in the past two weeks since I got it.
On immediate reboot, I was getting System UI stopped, report ?
After about 2-3 reboots like that, I am now on the tiled flash screen after the Google intro after reboot.
I've removed the battery several times. I've tried with and without the SIM card. I've tried with a power connector connected...nothing.
This has been going on for over an hour.
I'm very frustrated.
I had the same issue, i have relocked the boot loader and I'm going to take it back tomorrow for an exchange. I was getting to the google logo and then it just reboots back to the google logo even time. I tried a nandroid restore, didn't work, i tried to wipe every thing it still wouldn't boot. Now it just stays with the google logo on screen.
I also had the System UI stopped a lot around 8 times a day.
Hmmmm
Hi Folks,
I was setting up my "old", rooted and S-Off Incredible for our son to play games when travelling, etc. - it's no longer registered on Verizon's network, but is fine for wireless and downloaded apps.
After charging the battery and installing about 47 app updates today (i.e., it hasn't been booted in awhile), I was tinkering around with adding some apps from Play and it suddenly rebooted. Then, it kept booting at the white HTC logo screen.
So, I pulled the battery and decided to go back to Verizon stock, using the image from here:
http://dinc.does-it.net/Stock_Images/4.08.605.15/
Essentially, I booted into HBOOT, went into CWM Recovery, wiped appropriate storage, then rebooted back into HBOOT after putting the above image onto the root of my SD card. Maybe I don't need to wipe storage for a RUU, but it's habit by now.
HBOOT installed the RUU image after it prompted for a Yes/No and the Incredible booted with that old, "DROID!!" startup (gosh, didn't miss that) and showed the initial lock screen.
I pulled down the lock and started only a few seconds into phone initialization when it rebooted.
Now, it reboots as early as the HTC logo screen or gets to the lockscreen and reboots on its own after a second or two.
Seems like a boot loop, but I just installed a new RUU - so . . . I'm wondering if this is a deeper issue.
Ideas on how to go about fixing this rebooting problem are welcome, please. Is it possible that my half-completed Play install - i.e., just before it began this symptom - crunched a file system that needs to be fixed up?
Thanks,
- ooofest
Do you get any kind of errors wiping data or cache from recovery? The play install wouldn't have botched up the filesystem but the reboot could have led to corruption in /data. The cause of reboot I wouldn't know without logs. Try pulling the logcat during the boot loop which may or may not work on stock. I seem to doubt it as stock doesn't have USB debugging on by default.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Do you get any kind of errors wiping data or cache from recovery? The play install wouldn't have botched up the filesystem but the reboot could have led to corruption in /data. The cause of reboot I wouldn't know without logs. Try pulling the logcat during the boot loop which may or may not work on stock. I seem to doubt it as stock doesn't have USB debugging on by default.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi tiny4579, I had no errors wiping data or cache within CWM that were visible to me. I agree that USB debugging is not likely enabled by default.
If we assume there's a /data corruption as one angle to go with, should I try wiping and reinstalling the RUU again? I could attempt to put on a custom ROM instead, particularly one with USB debugging enabled (if that exists). HBOOT currently shows Locked and S-Off.
Thanks,
- ooofest
ooofest said:
Hi tiny4579, I had no errors wiping data or cache within CWM that were visible to me. I agree that USB debugging is not likely enabled by default.
If we assume there's a /data corruption as one angle to go with, should I try wiping and reinstalling the RUU again? I could attempt to put on a custom ROM instead, particularly one with USB debugging enabled (if that exists). HBOOT currently shows Locked and S-Off.
Thanks,
- ooofest
Click to expand...
Click to collapse
If data wipe was fine I'm not sure. To test USB debugging flash something like cm7. I think it uses an insecure boot.img meaning USB debugging aka adb should be on by default.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
If data wipe was fine I'm not sure. To test USB debugging flash something like cm7. I think it uses an insecure boot.img meaning USB debugging aka adb should be on by default.
Click to expand...
Click to collapse
Using HBOOT 0.92
Installed CWM 5.0.2 via PB31IMG.zip route
Wiped all available storage areas/paths - no errors shown
Installed cyanogenmod 7.2 from the SD card
On bootup, I saw the CM 7.2 boot screen (i.e., a circling arrow) for about one minute, then it rebooted. And rebooted. And rebooted. So, I'm back to rebooting at the HTC logo screen.
Consider me baffled - this phone was working great yesterday until after updating 47 apps (got a "low space" message at one point, started deleting apps while others were still installing) trying to install another app from Play store. Ideas, perhaps?
- ooofest
ooofest said:
Using HBOOT 0.92
Installed CWM 5.0.2 via PB31IMG.zip route
Wiped all available storage areas/paths - no errors shown
Installed cyanogenmod 7.2 from the SD card
On bootup, I saw the CM 7.2 boot screen (i.e., a circling arrow) for about one minute, then it rebooted. And rebooted. And rebooted. So, I'm back to rebooting at the HTC logo screen.
Consider me baffled - this phone was working great yesterday until after updating 47 apps (got a "low space" message at one point, started deleting apps while others were still installing) trying to install another app from Play store. Ideas, perhaps?
- ooofest
Click to expand...
Click to collapse
Phone might be dying. Does it even get past the HTC screen?
Try reinstalling the ROM.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Phone might be dying. Does it even get past the HTC screen?
Try reinstalling the ROM.
Click to expand...
Click to collapse
Yeah, it tends to get beyond the HTC logo screen after a new ROM install, but usually reboots as soon as I see the notification for "preparing internal storage".
Afterwards, it tends to reboot at varying times - sometimes at the HTC logo, other times it gets past OS startup and reboots after a few seconds.
. . .
EDIT: I just rebooted and . . . now it suddenly booted into CM and is working normally. What the heck?!
I'm not a CM person and would like to install another ROM to see what happens after that - do you think the phone EMMC is starting to go, perhaps?
- ooofest
You might want to format the internal emmc and sdcard as the reboots could be related to filesystem. Grab /proc/last_kmsg if you want me to check.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
You might want to format the internal emmc and sdcard as the reboots could be related to filesystem. Grab /proc/last_kmsg if you want me to check.
Click to expand...
Click to collapse
Thanks, I couldn't find a last_kmsg to pull, but I wiped all storage available (including emmc and sdcard), then reinstalled the latest RUU for a test.
Bootup went OK until it rebooted again soon after getting to the Gingerbread lockscreen. Oh well.
I decided to try going back to CM7 since it actually booted after a time, so reapplied CWM 5.0.2 and then started to format storage again. When trying to format /system I got a 5 vibrate error.
I've gone through various combinations of reapplying the RUU, adding CWM, trying to wipe storage, etc. and I keep hitting the 5 vibrate shutdown at various points. I couldn't wipe /system without getting the 5 vibrate issue twice, then it worked the third time, etc.
Just now, I was in CWM and merely navigating the menu to go into "mounts . . ." and it 5 vibrated again. Ow.
My suspicion above keeps coming back to me: is my hardware potentially going?
- ooofest
ooofest said:
Thanks, I couldn't find a last_kmsg to pull, but I wiped all storage available (including emmc and sdcard), then reinstalled the latest RUU for a test.
Bootup went OK until it rebooted again soon after getting to the Gingerbread lockscreen. Oh well.
I decided to try going back to CM7 since it actually booted after a time, so reapplied CWM 5.0.2 and then started to format storage again. When trying to format /system I got a 5 vibrate error.
I've gone through various combinations of reapplying the RUU, adding CWM, trying to wipe storage, etc. and I keep hitting the 5 vibrate shutdown at various points. I couldn't wipe /system without getting the 5 vibrate issue twice, then it worked the third time, etc.
Just now, I was in CWM and merely navigating the menu to go into "mounts . . ." and it 5 vibrated again. Ow.
My suspicion above keeps coming back to me: is my hardware potentially going?
- ooofest
Click to expand...
Click to collapse
Could be the battery going bad. Do you have another battery you could try? Mabey once things start loading it pulls to much power and reboots.
cmlusco said:
Could be the battery going bad. Do you have another battery you could try? Mabey once things start loading it pulls to much power and reboots.
Click to expand...
Click to collapse
Yeah, I started charging again to see if that might help, and I've been booting up with it plugged in, too.
Could a battery still be the problem, even plugged in? That is, would a short of some kind be limiting how much could be drawn from the plug?
Wish I did, but don't have another battery on hand.
- ooofest
ooofest said:
Yeah, I started charging again to see if that might help, and I've been booting up with it plugged in, too.
Could a battery still be the problem, even plugged in? That is, would a short of some kind be limiting how much could be drawn from the plug?
Wish I did, but don't have another battery on hand.
- ooofest
Click to expand...
Click to collapse
Even when plugged in the power is going thru the battery, so it could still be the problem. Just a sugestion, may have nothing to do with it at all.
cmlusco said:
Even when plugged in the power is going thru the battery, so it could still be the problem. Just a sugestion, may have nothing to do with it at all.
Click to expand...
Click to collapse
Interestingly, I let it "cool down" for a bit and charge from the wall instead of USB, then was able to wipe all storage, install CM7 and it booted up fine.
So, I let it sit for a bit longer, wiped again and installed the latest stock RUU. This time, it took longer to boot and came up fine - I now have a relatively stock (except for S-Off) Incredible, again.
From your suggestion, I'll shop for another battery and see if a new one helps to keep the sudden reboots at bay.
Thanks.
- ooofest
Hi Folks,
After working this for some days, my Droid Incredible with AMOLED display still gets into a reboot or boot-loop condition after a random amount of time of continuous use. Almost as if it heats up or something in its memory mgmt is flaky.
It can take new ROMs, recoveries, HBOOTs, radios, etc. - but, regular use just brings up the boot condition too easily, so I can't give it to my kid as a simple gaming device. I tried a new battery in case that might be the issue, but the condition still persists. Pulling the battery and waiting 10+ minutes usually allows it to work again, until the next reboot cycle starts up.
This phone is running the latest RUU and is also S-Off.
So, I'd like to give it away to the first person who requests it.
I'm not offering a trade or purchase, but if someone wants this phone to use/test/etc. with, just PM me and we can plan on a quick dropoff in NY/NJ/CT area or I'll send it to your continental USA address with both batteries and no explicit or implied warranties, guaranties, liabilities or claims of operating performance, etc.
- ooofest
OK guys so I started a new thread because the situation has changed with my problems. OK so I originally posted a thread about the accelerometer, I thought maybe restoring to stock might fix it. So I flashed the zv7 on the irc with the lgnpst on the irc. And every time its the same problem, the phone hangs at the 4glte section of the stock boot animation. Also i cannot get into the boot loader. I can still get into download mode though. Any ideas?
Sent from my Galaxy Nexus using xda app-developers app
Look here. http://forum.xda-developers.com/showthread.php?p=38887359
It should get you set
Sent from my LG-LS970 using xda premium
Just factory reset in stock recovery.
What is Optimus Prime's full name?
Optimus G. Prime
I can't get into recovery either using adb or hardware keys
Sent from my Galaxy Nexus using xda app-developers app
nvm I got it thanks guys. its running but restoring to stock still didn't fix the problems back to a doner phone I guess.
Chyrio said:
OK guys so I started a new thread because the situation has changed with my problems. OK so I originally posted a thread about the accelerometer, I thought maybe restoring to stock might fix it. So I flashed the zv7 on the irc with the lgnpst on the irc. And every time its the same problem, the phone hangs at the 4glte section of the stock boot animation. Also i cannot get into the boot loader. I can still get into download mode though. Any ideas?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Not sure if it's the same issue or not, but it sounds fairly close. When I powered off the LG logo would show with screen grayed not black as a power out should be.
Try this. Unplug the phone and hit the power button until the phone goes black, not gray, black, hold the power button for say a count of 40 or longer. This should stop the LG logo cycling. leave the phone alone for about twenty minutes. Do not plug it in to a power sources as that will start the cycling again.
After about twenty minutes hit the power button once.
I'm not saying this will resolve your issue, but I had the issue you're describing, and tried everything I could think of to get into recovery. Like you I was able to get into download mode, which made me certain I should be able to get into recovery with the right set of button pushes. Tried it for hours before resigning myself to LGNPST, when I did the above though it booted right up with no problem.
Discovered completely by accident. I was in the process of starting the LGNPST process receiving some help on IRC when I I hit the power button after the delay off and it all worked out. Didn't have to go through the process. The help I got was the twenty minute delay. The folks over on IRC deserve a lot of credit for the help they give btw.
The problem started after I flashed the ZVB rooted rom zip. Since then If I try to power down while it's plugged in, or not, the same thing happens. Rebooting is not problematic, but powering down is. It's not a big deal now though since the fix is easy enough for me.
Give it a try can't hurt.
same issues...
I had same issues, I flashed back to original root back from which i started from, then flashed the stock rooted zip, then the radio update, even though ur told to do the opposite way, the reason i did was cause the radio update flashes the new bootloader, just make sure after u flash the radio update wipe the cache and dalvick casche also. I did that and it booted right away,
So tonight out of the blue, my Rogers Galaxy S3 restarted itself. This isn't totally unusual, as sometimes this will happen once or twice a day, but never has it been too bad.
First off, I've been running Cyanogenmod 10.0, and again, has been relatively problem free. The first major issue I had was a week or so ago when I woke up to my phone having seemingly restored it's default settings on its own. Apps and all my other data were intact, but widgets, app settings, etc, were all cleared.
Now tonight, my phone can rarely boot into CM, and when it does, the power menu will appear shortly thereafter before restarting itself once again. If the phone is plugged in, I can't get anything other than the charge indicator to come on the screen for more than a second. The phone also does this when trying to boot into recovery mode or download mode.
I'm at a total loss as to what to do here, so I'm going to be leaving the phone off with the battery out over night. Appreciate any feedback in the meantime.
Also having a similar problem: phone boots up, will barely enter the bootloader/TWRP/boot animation for hyperdrive ROM. Also with rogers. I believe it might be SDS but I need to re install the stock firmware and can barely boot into the bootloader without the phone dying (battery is charged though). Any help greatly appreciated!
EDIT: managed to boot up for long enough to install "eMMC check" and apparently I have a 'sane chip'.
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well, after pulling most of my hair out, that does seem to be the issue. Would explain why the power menu would come up the few times it did manage to boot. I managed to get it working for a while, but the button seems to be really delicate since picking my phone up and barely touching it reset it again.
I guess now I need a solution to the power button sticking, but at least it doesn't seem to be SDS.
Okay, that makes sense. When I leave the phone completely stable it's fine.
However, I have tried unrooting and reinstalling stock firmware. However, my system status in bootloader is still custom, when I boot up the rom I still have superuser installed. I tried installing two different stock firmwares for Rogers and the same problem. Any help would be great, I really want to send this in for warranty ASAP.
EDIT: After using ODIN to install stock rom, I still had Superuser. I installed SuperSU and then preformed it'sfull unroot. After that i cleared data and cache from stock recovery and the phone is now at original status and seems to not be randomly rebooting/dying. Weird.
Dear XDA,
I have tried all I can to fix this problem. Let me explain how it all started.
I was using my phone normally, running the same custom rom ive been running for the past 6 months. I went to turn on wifi then turned off the screen. Later when i went to check my phone the screen would not turn on, so i performed a battery pull. After that i saw the normal google boot screen and then the custom rom boot screen. It stayed on that screen for a few seconds and then went back to the google boot screen. It then did this over and over, ive left it on for an hour once and it kept doing the same thing. Only way to stop this is with battery pull.
So what can i do with the phone:
I can access fastboot
I can access download mode
What have i tried:
I tried the following methods:
1) Flashing a Back Up
2) Wiping data, flashing a rom and gapps
3) fastboot adb http://rootzwiki.com/topic/13819-how-tovzw-return-to-factory-state-unroot-and-relock/
4) ODIN http://rootzwiki.com/topic/27050-vzwodin-files-needed-for-odin-winstructions/
The same issue continues even after successfully completing these methods. Im now down to my last strand and hoping the great xda community can help me.
seanrobot said:
Dear XDA,
I have tried all I can to fix this problem. Let me explain how it all started.
I was using my phone normally, running the same custom rom ive been running for the past 6 months. I went to turn on wifi then turned off the screen. Later when i went to check my phone the screen would not turn on, so i performed a battery pull. After that i saw the normal google boot screen and then the custom rom boot screen. It stayed on that screen for a few seconds and then went back to the google boot screen. It then did this over and over, ive left it on for an hour once and it kept doing the same thing. Only way to stop this is with battery pull.
So what can i do with the phone:
I can access fastboot
I can access download mode
What have i tried:
I tried the following methods:
1) Flashing a Back Up
2) Wiping data, flashing a rom and gapps
3) fastboot adb http://rootzwiki.com/topic/13819-how-tovzw-return-to-factory-state-unroot-and-relock/
4) ODIN http://rootzwiki.com/topic/27050-vzwodin-files-needed-for-odin-winstructions/
The same issue continues even after successfully completing these methods. Im now down to my last strand and hoping the great xda community can help me.
Click to expand...
Click to collapse
Fastboot seems the best solution to me. What exactly went wrong? Also you could try a OMAP flash.
Sent from my Galaxy Nexus using XDA Premium HD app
To be honest I have no idea what happened. It happened out of no where didn't flash a new rom or anything. OMAP flash? Never heard of it but I'll definitely look into it and try it. I've tried fastboot method and still got the same problem sadly
Really hoping this isn't a hardware issue
I just tried an OMAP Flash and still have the same problem. Ive moved on to a new phone but I still want to get this one working. Any other ideas to fix this problem?
Got into the same problem as yours. I googled around, and most people fix this problem by flashing stock image. Basically wipe your phone clean, e.g system,data,cache etc. and then flash in the stock image u downloaded from google website throught fastboot mode. I tried that method, but my phone is still stuck in bootloop. You can give it a try and see if it works