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.
Related
I was just getting over the initial buyers remorse phase for my galaxy (or in my case, flashers remorse, even though I run stock JPY and it's fine, I have this urge to re-exchange it for a SLOWER stock Vodaphone Australia 2.2 version that's probably more buggy, but at least truly stock), when I drained my battery to 1% to test battery life, and shut it off manually.
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) left right and center then went straight back into default first-boot menu, like the very day I received the phone, or after a hard reset. The funny thing was, instead of having default values selected, it had the ones I had already put in. I thought it would be fine after that. Wrong.
I tried rebooting it again to see if it fixed itself, and it does the same with the forced closes. I uninstall my background and re-install it, and save some settings. When it boots it restores the live background back to it's stock settings (the live wallpaper I chose is still there, but the settings for it are not).
At this point I'm scratching my head so I uninstall all apps. This time on boot it doesn't throw up "force close" errors, but instead force-closes a single app or service for me on boot, with the one buzz, then three quick buzzes. Sigh... I have to factory reset my phone. One thing that particularly annoyed me was the fact I moved all my apps (AngryBirds ) to my external SD card, yet miraculously, after the reset my phone doesn't seem to think it's there anymore! Another thing I'm pondering is that if I didn't reset my phone like this, would this still have occurred?
Runs perfectly fine after the factory reset, with no errors or anything on boot as of yet. I have been compulsively rebooting it ever since just to find out, LOL!
Is this a 'normal' sort of thing to happen on the SGS, or is just through shear coincidence the combination of me restarting the phone in it's booting phase + the low battery life screwed up some boot settings while the phone was writing to it, or is it some hardware error? I can see this as particularly annoying if it were to happen every month or so. Coming from an old brick phone with something like 8000 messages on it, it'd be inconvenient to say the least to start deleting everything periodically... I guess I can use apps to back-up data when this occurs, but some apps don't even work after it's been erroring out on me. *Pulls hair out*
TL;DR:
Reset my phone while it was booting (still on the GT-I9000 screen) on a low (1%) battery and it broke my phone settings. Forced closes unknown app/service on boot with no 3rd party apps installed, but still boots to home. Force closes 3rd party apps frequently if they're installed. Factory Reset/Wipe. Problem Solved. Annoyed. RAGE.
next time something like this happens use adb logcat to figure out what is actually going wrong
exclamationmark said:
...
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) ...
Click to expand...
Click to collapse
you are not alone . after draining battery , starting it accidently up (drained) in middle of booting , killed it for me, well not killed but wouldnt boot for me and I had to the the factory reset. oh and since the nice bzz ... bzz bzz bzz I hear more often I would like to ( here was I ignored crying about it http://forum.xda-developers.com/showthread.php?t=937938 )
Yeah I'll definitely boot up logcat if it happens again. I'm just hoping this isn't a regular occurrence . As long as I don't do anything stupid like this again, I'm thinking it should be fine.
The third time this happens, it's going back to the service center, so it's got two chances left! Another thing I failed to mention was that it was chewing up like 200mb~ ram with level 1+2 ram cleared, without loading back into the homescreen, before the factory reset. Probably the stupid forced close app/service leaking >.>
Pagot, if that were me and continual factory resets were the only way to fix it (or didn't fix it) I'd flash it back to stock (or just remove root) and return it to the service center if that's an option. Sounds like something got corrupted or didn't get flashed properly. Either way I'd let THEM waste their time sorting it out because no amount of flashing is going to solve a hardware issue if it turns out to be one.
exclamationmark:
(had stock, so just root removing) but I know how our service centers work (and I would have to bring it even to our carrier) they wouldnt even talk to me if I didnt do the factory reset and the first thing they would do "reflash and factory reset"
right now I am not playing on the phone so much anymore. no lust or time so no idae if my apps are still fcing so often . And I installed speedmod and made a backup so I can revert back if something happens. So will see.
Wanted to just write about the battery down +(or) not full boot = corruption
Long time lurker, first time poster.
I woke up today to see my captivate screen showing blank screen (active black screen with buttons lighted up) being unresponsive. It was on it's charger from the night.
I pulled the battery to shut it down. It rebooted. I thought nothing about it until I tried to use it about an hour later.
I have had it on stock Froyo, with no root. Never have flashed any other ROM besides updates through kies.
Problems and things I've noticed so far:
No puzzle lock screen. Can't find it under "set screen lock". Only None, Pattern, PIN, Password available.
Home button and search button do not function(they light up like they are pressed, but not action occurs in any apps or home screen).
No data. Usually i'd see edge or 3g, but I have no data connection.
Text messages wiped. None available through "Messages"(though call log shows history of messages).
Keyboard was on stock android rather than swype(since changed back to swype).
Holding power button only shows "Power off" option. Before there was at least Airplane mode.
GPS was on(I hardly ever use it).
Location settings seemed to be default("use wireless networks" was unclicked)
Most other settings/app data seems fine.
About phone info:
Model Number: SAMSUNG-SGH-i897
Firmware version: 2.2
Baseband version: I897UCKB1
Kerner version: 2.6.32.9
Build number: FROYO.UCKB1
Click to expand...
Click to collapse
Other related things:
Day or two before I received a text message from AT&T to download Kies and use Froyo(Don't remember exact wording, lost the text message, but something to the effect it looked like a mass mailing text to update to Froyo using Kies). I was already on Froyo(flashed as soon as I found out it was available few months back).
I also got a text message about downloading their at&t app to manage my minutes and pay my bill(also already had that app).
My Captivate would randomly freeze/unresponsive a few times, but I didn't think much of it.
Google Music app seemed to randomly start playing the audio file i paused(just in my pocket, or once when i put headphones in to make a call).
Searching the forums, haven't found too much related.
One thread suggested using "home switcher", which I have tried(both Froyo and regular versions, though can't press home button for Froyo version). Neither seems to know what my default Home App is, but it only sees TwLaucher(I only have TouchWiz).
Tried installing an alternative launcher(ADW,LauncherPro), still no home/search button.
I'm without my computer for the weekend, so I can't backup my files and reset to factory just yet.
Anyone have any thoughts to fix this or know what may have went wrong?
I might finally make the jump to a Custom ROM if it'll fix this.
Yes, you should either flash a custom rom or do a factory reset. I will say an event similar to this, also involving text messaging, is what made me make the leap to Assonance, and then Serendipity, and I haven't looked back.
Sent from a state of Serendipity
At the least, try a master reset.
You're not alone....
Two Saturdays ago, I woke up, grabbed my phone to see what time it was and my phone was going haywire. It as blinking, flickering and rebooted on its own a couple of times...without me touching it.
When I DID manage to access the phone after a reboot there was no connection. I couldn't call, send/receive texts, nor could I access most of the features (during one of the haywire moments, the phone popped open my "Gallery" folder and started running a slideshow and then shut down. Again, all without me touching it!) There was a distinct blue circle with a slash where the 3G bars used to be on the top right corner of the phone.
I did a factory reset and didn't help. Wiped everything off the phone, but the device was still going nuts.
I got the phone in mid-December and have absolutely pampered that thing. Never dropped, never scratched, never abused. So I was surprised when I took it into the AT&T replacement center that the lady told me that my battery was wet! Not the phone, but the battery. Those two white-that-turn-pink indicators are so close to each other on the phone that I can't see how one gets wet while the other doesn't.
So they give me a new phone. One thing I noticed right away was that my data usage went WAY UP with the new device. To put it in perspective, I used 100 mb of data in 29 days and 64mb IN ONE DAY with my new phone. I thought it may be a one-time fluke, but it's not. I am only 10 days into my new month and am already at 164mb out of 200mb in my plan. I have NEVER used 164 mb in the 6 months previous, let alone in 10 days.
Fun's not over yet. I noticed a lot of crashes and "Force Closes" with the new phone too. I didn't even have any apps downloaded yet and things were still crashing. Last night I pull my phone out to take a picture and...nope. Screen was all kinds of whacked out and it crashed. And still does now every time I open the camera function. I managed to get in camera mode fast enough to do a reset, but didn't work. The screen is fine otherwise. So looks like I'm back to A&T tomorrow for another round.
I'm glad you posted this, cause the same morning all this happened -- literally, within 10 mins of me waking up -- my computer (brand new - 2 days old) went berserk and shut off and my stereo started flipping channels, turning the volume, treble, bass up and down..BY ITSELF without me touching ANYTHING! It was pretty freaky. I wondered if I was struck by lightning the night before.http://media.xda-developers.com/images/smilies/eek.gif
I was finally able to get back home today and do a factory reset. This (somewhat) solved the problem. Everything is mostly back to normal(home button and search button work on home screen, lock screen is there).
Lost a couple of game saves as I had no method to pull a save file(was doing adb pull on some known file locations).
I did run adb logcat before resetting, and home button and search button seemed to trigger something, just not follow through(Search button did work in a card game as a forward button and home button worked in the kies app to exit, just never as a return to home button in apps).
I'll be looking to root and flash a custom ROM, especially root so I can do a proper backup in case anything like this happens again.
I just want to say thank you posting in q&a and doing research before and after your flashing started. Then searched after your problem. You're a new member of a breed that are few and far between. I will hit your thanks when I get on my computer, app doesn't have it. You will go far here.
Okay, I have been having a serious issue with my D3 lately. One time, my phone just randomly rebooted, and then it would get stuck at the red "Droid Eye" screen, where it would be laggy and such after a while. Eventually the screen would time out in like 2 minutes. After it turned off, I could not get it to turn back on. Basically dead, except I could still get notifications and even a phone call. But I could not act on any of them. it's like the phone's heart is still beating, but I can't turn the screen on. I pull the battery and reboot and it does it again. SOMETIMES if I keep touching the red eye screen I can get to get to the lock screen, but the wallpaper won't load and it's basically frozen. I even tried booting into safe mode and that didn't help. I took it to Verizon, they said they've a couple other people with a similar issue on the forums. They did a factory reset, and that has been the only solution to the issue. I have had it 3 times now, and this time I'm sticking with the Blur launcher and keeping only the essential apps installed. I'm assuming this is a software issue, and I'm currently trying to figure out if it is related to a certain app that was installed. Hoping they will fix this with an update! ANYBODY ELSE HAVING THIS ISSUE? if so, any leads on another fix or what it could be?
sounds like a software issue. a factory reset doesn't do anything other than change the software.
I had a similar issue on my droid 1. it was rooted and when I installed a gingerbread from I forgot who, it got stuck at the eye, kept rebooting, and occasionally, i'd get calls and it still wouldn't work. I look forward to root.
out of curiousity, did you have to take it to the store to factory reset or is there an option for it in the bootloader(I know its locked but I have no idea to what degree)
The first time I took it to the store they did it for me, but yeah there's an option in the bootloader. Just took my back to Verizon cuz this was the 4th time it's done it, they're sending me a new one! It's okay, cuz my nice screen open 'click' sound was gone on the keyboard lol
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. ?
I've been banging my head against the wall with this issue for months and finally have decided to reach out and see if I can get some additional insight.
My wife had upgraded from her 2013 motox about a year and a half ago and it has been just sitting in a drawer until a few months ago. I pulled it out a while back thinking of using it as a music player for the kids, well I booted it up and it will literally force close random apps constantly, to where the moment I click away another pops up, lots of Gapps crashes but everything from alarm clock to youtube, system apps and downloaded apps, if I am fast (and lucky) enough I can navigate through the phone like a snail in molasses... Well, this is just the beginning, in addition to the FC issue, any changes I make to anything on the phone will not stay changed... I have uninstalled just about every downloaded app and disabled just about every system app and they all come back or become enabled again. Even managed to delete a few gigs of photos off it while connected to my pc and... after a reboot, they are back.:crying:
I don't recall using rockmymoto or anything on her phone (Its on 4.4.4), I am still using my moto x and I did all that on mine but never hers... Yet I am unable to reboot to recovery, just fastboot also her phone doesn't load the adb drivers and only shows as a MTP usb device while my MotoX shows as XT1058 and the ABD interface.
I have tried flashing stock firmware via RSD Lite and manually thru Fastboot, I've done 4.4.4 and 5.1.x and each time I have no issue flashing the entirety of the packages but when it reboots its still has all her data and all the force closes... Also tried the in phone factory reset (in regular mode and safe mode) and I can click the "Erase everything" button but it doesn't proceed.
It's driving me freaking insane! When she stopped using it, it was fine, no issues whatsoever and I am incredibly confused at how it got this way while just sitting in a cupboard drawer. I have had over a dozen Android phones, all rooted and flashed, I consider myself a pretty competent user, i've baked my own roms and compiled cm(7) from source and even unbricked a few devices here and there for friends and family but this is literally got me stumped.
Really hoping someone out there sees this, has had a similar issue and maybe has some good new for me.
Thanks in advance
Raff