I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.
GreenMunky said:
I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.
Click to expand...
Click to collapse
If a factory reset does not fix the issue, all I can suggest is find the thread "Return to Stock" and follow the instructions to flash the entire stock SBF for your carrier. This should fix any corrupted files, if present. Either option WILL erase everything, so backup anything you need first.
Good Luck
Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?
KJ said:
Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?
Click to expand...
Click to collapse
Nope, phone had been off the charger only a few hours, still had 85% or so. I actually tried plugging the phone in while it was booting up to see if an extra jolt of juice would somehow help it to fully boot up... made no difference. After 6-8 failed boot attempts, it finally booted up and has been running fine since... although I have yet to try to manually reboot it.
Well, if it acts up anymore...I'd consider a full wipe and return to stock. Same android version you're on now of course.
Otherwise...probably a fluke. ?
Related
Any help would be greatly appreciated.
I have a launch day Nexus One running CM5.0.5.3, the OC/UV kernel, and the EPE54B radio.
It has all been running great until today. I took it out of my pocket and it was warm (not hot) to the touch. I noticed the screen was blank but the buttons along the bottom were illuminated. I tried resetting it (power+volume down+trackball) and that didn't do anything, so I pulled the battery. When I rebooted it, it seemed to take a longer than usual time at the initial boot screen, and then went to the animated screen. It stayed on the animated screen for quite a while and then froze. It's stuck on the X mid-formation.
I then booted into the bootloader (which reacts like normal) and went into recovery. I re-flashed CM5.0.5.3, no effect. I wiped cache and system and re-flashed. Nothing. I did it again, and it finally booted up but I could only select things with the scrollball. The volume rocker worked fine, but the touchscreen is completely non responsive.
If I let it sit at the boot screen for a while it will go black eventually and time out.
I'm at a loss. I'm in the process of downloading a stock ROM and am going to flash it next. Anyone have any suggestions? My bootloader is (obviously) unlocked, so I'm worried about warranty work
Update: Just got it to boot (with the stock ROM) and I've got a warning screen saying:
Sorry!
Process system is not
responding.
[Force close] [Wait]
Any ideas?
Reflash CM 5.0.5.3 and then post back
Ok, re-downloading now.
Just flash in recovery?
Flashed in recovery (after wiping)
The phone stays on the stationary initial boot screen (four bars) for about a minute and a half and then goes to the animated cyan X. It stays there booting for probably two minutes before stopping mid-animation. If you let it sit there for a while the screen will time-out, which you can bring back with the power button. Sometimes when you hit the volume rocker you can hear the beep beep but nothing shows on the screen.
What the hell is wrong with my phone?
After an obscenely long time I got it to boot up.
Touchscreen is not responding, trackball is not responding, I have a question mark on the battery indicator, and no service.
I can't unlock the screen because of the non-functioning touchscreen. Live wallpaper is running great, it makes the sound when USB debugging is connected, it just won't react to any input.
I can, however, establish an ADB connection. It shows up on the device list and a remount succeeded.
Would reflashing the radio be of any benefit?
Dang the touch screen is unresponsive? I'm not an expert, but i'll try to give you some ideas.
I had some trouble once and I used settings-privacy then erased everything from within the OS. Then I reported to the screen just before going into recover and hit clear storage. Then went into recovery and wiped everything that I could. After that, flash the Rom that you want.
I've done a full wipe to no avail.
I'd bite the bullet and call htc, don't mention that you have rooted, it may be a hardware thing.
Scaaaary!! But hey, it happens. I would also try wiping for EXT on the SD card if you have been using apps2sd.....May not hurt, mights well try everything.....
Wiped everything, reflashed radio, flashed to stock. Nothing. This is exactly what I was worried about when I unlocked it.
Oh, well.
liam.lah said:
I'd bite the bullet and call htc, don't mention that you have rooted, it may be a hardware thing.
Click to expand...
Click to collapse
Yeah, I'll do that tomorrow. I guess I'll flash everything back to shipping and hope they don't notice.
mortzz said:
Wiped everything, reflashed radio, flashed to stock. Nothing. This is exactly what I was worried about when I unlocked it.
Oh, well.
Yeah, I'll do that tomorrow. I guess I'll flash everything back to shipping and hope they don't notice.
Click to expand...
Click to collapse
Many people have posted that they got a replacement even with an unlocked bootloader. One guy I heard said they charged him $55.
Either way, you can probably get a replacement.
Hi everyone,
while using my Note earlier today, it suddenly shut off (with about 75% battery) so I assumed it was just a crash. However after rebooting I could only reach the homescreen and after a few seconds it shut off again. This happened 2 more times.
After that I couldn't boot intro Android at all anymore. After displaying the Samsung splash for about 1 second, the phone shuts off. I tried things like removing the battery for some time etc..
I can boot into CWM where I tried to make a backup. After confirming the start of the backup, the screen image distorts for half a second and the phone shuts off. Then after connecting the charger, creating a backup was successful. Trying to boot into Android still didn't work though.
I did a full wipe and tried another ROM without success. The phone shuts off either after the Samsung splash screen or 1 second after displaying the boot animation of the ROM.
Is it a battery issue or could it be something else?
augenleet said:
Is it a battery issue or could it be something else?
Click to expand...
Click to collapse
Why don't you verify the first part of your question yourself? After that the second one would make sense.
So: new battery first.
ThaiDai said:
Why don't you verify the first part of your question yourself? After that the second one would make sense.
So: new battery first.
Click to expand...
Click to collapse
I've ordered it, it'll take a few days to arrive.
Just in case anyone else runs into this issue. I found that my Galaxy Note was doing exactly the same thing and it was a dodgy or dying battery.
I could run CWM or Android Recovery or Philz Recovery and I could also flash the stock roms with ODIN but after the flashing, the phone would boot to various stages (N7000 splash screen, SAMSUNG splash screen, "Updating Android" screen and then turn off. After flashing a dozen times I worked out it was the battery. Replaced it and all sorted.
I ran into a same kind of problem once. Factory resetting the phone fixed the problem for me.
I've never seen this issue before, and now I've run into it twice since updating to Kit Kat, rooting, and setting up my VZ Moto X.
Honestly, I don't have much info to share. I had just gotten done setting up my phone. Froze some VZ apps (this might be it, maybe) though nothing crazy..Navigator for one, then rebooted. No problems.
Did some more updating, installed Delayed Lock and GSAM Battery monitor (which is broken in 4.4 for now, I know) and rebooted again. One final time before I planned to do a full backup of all apps using Titanium.
It boots up fine, boot animations (both Moto globe and VZ logo) and then goes black. Now it's sitting on my desk, screen flashing every 15 seconds or so. The time is accurate and updating. Battery icon comes and goes, but it's not dead. Network shows no bars. It's basically just the status bar and the bottom nav icons. Adb isn't recognized, though it does show up under fastboot.
The worst part is that this happened to me last night. I was at the Pats game. Battery was running low and I was trying to record the last play of the game. Battery ran out and the phone shut down. I tried to start it back up and it died on me again. After getting home and charging it to full, it did what I described above.
I really hope it's not time to do a full reset via fastboot as that's what I had to do this morning. Any ideas? I tried clearing cache via fastboot too. No luck. Anyone ever see this before?
******EDIT******
I've discovered what causes this issue, for me at least. It is the combination of "improper" shutdown methods in use by some apps (Titanium Backup, Quick Reboot, SafeStrap, and others I'm sure) and the use of Delayed Lock. Basically, Delayed Lock takes control of certain system files in order to disable the pin/password/pattern lock. If the system shuts down correctly, it hands control back to system. If the phone doesn't hand over control (the phone cuts out without proper notification due to the battery dying or caused by the way an app handles rebooting), the phone hangs up on the next boot. I made a video and uploaded it here.
http://youtu.be/CRtmUAv3PLk
Also of note, rebooting using the Advanced Power Menu option within Gravitybox (the Xposed Framework module) works just fine. All of the options except for "Soft Reboot".
See more in the Delayed Lock support thread (starting at post 654):
http://forum.xda-developers.com/showthread.php?t=955092&page=66
mercado79 said:
I've never seen this issue before, and now I've run into it twice since updating to Kit Kat, rooting, and setting up my VZ Moto X.
Honestly, I don't have much info to share. I had just gotten done setting up my phone. Froze some VZ apps (this might be it, maybe) though nothing crazy..Navigator for one, then rebooted. No problems.
Did some more updating, installed Delayed Lock and GSAM Battery monitor (which is broken in 4.4 for now, I know) and rebooted again. One final time before I planned to do a full backup of all apps using Titanium.
It boots up fine, boot animations (both Moto globe and VZ logo) and then goes black. Now it's sitting on my desk, screen flashing every 15 seconds or so. The time is accurate and updating. Battery icon comes and goes, but it's not dead. Network shows no bars. It's basically just the status bar and the bottom nav icons. Adb isn't recognized, though it does show up under fastboot.
The worst part is that this happened to me last night. I was at the Pats game. Battery was running low and I was trying to record the last play of the game. Battery ran out and the phone shut down. I tried to start it back up and it died on me again. After getting home and charging it to full, it did what I described above.
I really hope it's not time to do a full reset via fastboot as that's what I had to do this morning. Any ideas? I tried clearing cache via fastboot too. No luck. Anyone ever see this before?
Click to expand...
Click to collapse
Bad system file, you may want to rsdlite and yes userdata needs to be erased. Moto is finicky, I've never had any other device soft brick on me, never. 3 times now with the moto 2 after flashing a ROM, 1 from restoring a nandroid
Sent on my Moto X
flashallthetime said:
Bad system file, you may want to rsdlite and yes userdata needs to be erased. Moto is finicky, I've never had any other device soft brick on me, never. 3 times now with the moto 2 after flashing a ROM, 1 from restoring a nandroid
Sent on my Moto X
Click to expand...
Click to collapse
i figured you'd say that. i'm just trying to figure out how to stop this from happening again. so unbelievably inconvenient.
Added some more info to the OP about what turned out to be the cause.
Two nights ago I was on my way to the airport and my phone froze then shut off. No big deal, it does that sometimes. However, when I turned it back on, it would load up the LG "Life's Good" screen and then restart, over and over.
I loaded into recovery mode and did a factory reset, and cleared the cache. After that, it would go past the LG screen to the "Android is updating Apps" screen and count up the apps until a certain point (9/45 usually) then shut off completely.
I didn't have access to a computer for the past two days so I couldn't try anything else. This morning I used LGUP to upgrade the phone to ZVB (what I was already running). The update went through successfully, at least on the computer, but now the phone is stuck on the "Life's Good" screen again, this time it isn't rebooting, just stuck on that screen with the blue LED going on and off repeatedly.
Any ideas what might be wrong? Did I screw something up by factory resetting, or by using LGUP? Please help.
Level1engineer said:
Two nights ago I was on my way to the airport and my phone froze then shut off. No big deal, it does that sometimes. However, when I turned it back on, it would load up the LG "Life's Good" screen and then restart, over and over.
I loaded into recovery mode and did a factory reset, and cleared the cache. After that, it would go past the LG screen to the "Android is updating Apps" screen and count up the apps until a certain point (9/45 usually) then shut off completely.
I didn't have access to a computer for the past two days so I couldn't try anything else. This morning I used LGUP to upgrade the phone to ZVB (what I was already running). The update went through successfully, at least on the computer, but now the phone is stuck on the "Life's Good" screen again, this time it isn't rebooting, just stuck on that screen with the blue LED going on and off repeatedly.
Any ideas what might be wrong? Did I screw something up by factory resetting, or by using LGUP? Please help.
Click to expand...
Click to collapse
Sounds like tbe famous boot loop issue. Its a hardware problem known issue. Theres a thread on the general section about it. Take it to sprint or call lg. Should be repaired for free.
I agree with TheMadScientist420. This is the same thing that happened to me. Was rooted on ZV5, went to unplug from charging and the screen didn't turn on. Pulled the battery and it would loop at the LG screen. Never got the upgrading apps message.
Cleared cache to no avail. Then factory reset with the same issue. I opened a call with them on 06/09. Shipped it to their Texas service center on 06/10 from PA. They received it on 06/14 and repaired it on 06/17 . It was shipped to me on 06/20 and I received it on 06/23 so you're looking at a 2 week turnaround on your phone.
The first time I got my phone was about two days ago. I got the MotoG2 from ebay at such a cheap price ($20), I won the auction and so yeah (26 bids). HOWEVER, this is what the description says from the seller:"This smart phone sells working as-is because screen is cracked, LCD has liquid damage, other components work as they are supposed to. SIM slot/cellular feature has not been tested on any networks. Customer data have been deleted from smartphone. *Battery life and performance on used electronic devices can not be guaranteed. * Entire screen is cracked; there are many scratches and scuffs on the bezels and on the back side. Smart phone sells with battery and non-OEM box.
I finally got it and shipped to my house, on'ed it and everything worked fine the camera, audio, basically it was brand new except for the front screen that is shattered. Later on, i decided to root my Android phone with KingRoot on kingroot.net and it was fast and easy. I didn't know what to do after, my friend told me about it and you can do many things with root. My phone was successfully rooted. I was browsing Google Play untill i saw an app that says "boot animations" I was like "Cool, gonna test it out" so it did install and i opened it. It has a ton of animations and i chose one to be as my boot animation. Unfortuanately, I so stupid forgot to backup the previous original (Motorola boot animation). It now takes a bit longer to boot up (idk whether it was the animation itself, or the fact that my phone is now rooted). I decided to uninstall the root, hoping the boot animation was gone(also kinda blurry). Well it did not, but i was like whatever. Phone still worked fully, and decided to stuck it up with that boot animation.
Now that my phone is unrooted, i decided to root it again since it did not work. I tried to install an app that AdAway and it did work. Ads were gone and i was happy.
Until. A motorola screen popped up saying it has a system update. I forgot what the update is about. All i remember is something do with "stabilizing and other stuff" and takes about 10 min.
So I did install it, phone off'd and on with an android logo with a progress bar. After it was complete A picture of an android lying down with an exclamation mark saying "Error". I was like wtf, what happened. I couldn't boot up my device because of this error. I off'd my phone and then on'd it again. It now says "no command." with the same android guy. I gave up and tried to "wipe data and personalized content" "THIS CANNOT BE UNDONE" so i just accepted it. I off'd my phone and boot it up. There was an infinite boot loop, and tried to do as much as i could. But it always led to this(phone on's then offs a few seconds later then on a few seconds later and a few seconds later An android guy says"Erasing..."few seconds later phone off's again. REPEAT!" It was like this and left it the entire night with a cable charged to it so it will not die. So its now unusable and i do not know wtf i should do. The same friking Android guy saying "erasing" i dont think its erasing because when i hold the (power button + Volume up) it says "data wipe complete". It was just repeating over and over and over again with the say frikin vibration everytime it turns on. Tried to Enter Factory, Recover, normal recovery, wipe data again. Basically i did everything that was reasonable that would fix this boot loop. HELP PLS!
Sorry have bad english.