Database Info

[Q] Nexus 5 has repeated force closes on newly installed stock firmware

Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.

slixzen said:
Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.
Click to expand...
Click to collapse
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.

_MetalHead_ said:
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.
Click to expand...
Click to collapse
I know this is a very late response.
The initial way that I installed the stock firmware was using fastboot, and installing each .img file separately.
I just re-flashed the factory image again (except for the recovery image), and am waiting for the phone to boot up (it seems like it takes ages for the phone to actually go from fresh install to fully booted), it has been over a 5 minutes now.
But once that is done, I will see what happens. Is there a way to check for bad hardware (I am specifically thinking flash storage)? Maybe that is causing the problem?

Galaxy S6 Active Ultra Power Save (Brick) Mode

To start, I have lost access to the reaction video of my wife's first pregnancy announcement. So I would even be willing to make a donation to someone who can help me. (If that is against the rules, let me know)
I used an app from the Play store called Package Disabler Pro to disable some of the bloatware on my phone. In doing so, I disabled something necessary for Ultra Power Save Mode to function. (perhaps Touchwiz) I use Nova Launcher. I tried to show UPSM to a friend yesterday and was met with a black screen. The phone was still running, as I could get the notification window to drop down from swiping. But I had no option to leave UPSM in the settings. The settings that were listed were very limited. I tried everything and ended up soft restarting the phone. It booted back up into UPSM with black screen (no launcher). I finally started tinkering around with Recovery and cleared the cache. At some point, I don't know if it was caused by the cleared cache, it stopped booting fully. I now get stuck at the finished ATT boot animation.
I'm at a loss as to the next step. AFAIK there are no custom recoveries for Galaxy S6 Active yet. So pulling data from ADB in recovery is out. The only other option I have seen is a 'dirty' stock rom flash. But I don't even know if that is possible or will work. If there is anyone out there that has any clue what I should be doing, please help me. I need help. :crying:
Thank you.

Saafir said:
I'd say give the stock a try. The stock tars for our regular S6 dont wipe data. Let this be a learning experience to backup important items to the cloud or thumb drive
Click to expand...
Click to collapse
Is there a distinction between using Stock Recovery to flash stock and using Odin? Stock Recovery warns that user data will be formatted. So I'm assuming that it wipes the user data partition. All that aside, does anyone even know how to get ahold of S6 Active tars?

Ah! I have this same problem right now. Note5. Haven't dug myself that far into the hole yet, and I somehow got out of nova launcher and into TouchWiz (safe mode boot probably), but im stuck in grayscale and can't do anything other than the limited settings options or make phone calls. No texting, internet, full settings access, quicksettings, or really any apps but contacts and phone.

tip...
drapelyk said:
To start, I have lost access to the reaction video of my wife's first pregnancy announcement. So I would even be willing to make a donation to someone who can help me. (If that is against the rules, let me know)
I used an app from the Play store called Package Disabler Pro to disable some of the bloatware on my phone. In doing so, I disabled something necessary for Ultra Power Save Mode to function. (perhaps Touchwiz) I use Nova Launcher. I tried to show UPSM to a friend yesterday and was met with a black screen. The phone was still running, as I could get the notification window to drop down from swiping. But I had no option to leave UPSM in the settings. The settings that were listed were very limited. I tried everything and ended up soft restarting the phone. It booted back up into UPSM with black screen (no launcher). I finally started tinkering around with Recovery and cleared the cache. At some point, I don't know if it was caused by the cleared cache, it stopped booting fully. I now get stuck at the finished ATT boot animation.
I'm at a loss as to the next step. AFAIK there are no custom recoveries for Galaxy S6 Active yet. So pulling data from ADB in recovery is out. The only other option I have seen is a 'dirty' stock rom flash. But I don't even know if that is possible or will work. If there is anyone out there that has any clue what I should be doing, please help me. I need help. :crying:
Thank you.
Click to expand...
Click to collapse
Have tried starting the phone in Safe Mode? Thats what I'd try.

Try what sd_N suggested.
Turn your phone on by holding power button + volume down
When you get the samsung logo, release the power button but keep holding volume down all the way until you get lock screen.
If you are able to boot to safe mode then there's most likely something you have downloaded / something running during your regular boot that crashes / malfunctions.
- Renolz

I found a Solution for those who are still Stuck in Ultra Power Saving Mode.
Send an SMS to your number with Text "google.com"
Notification will appear.
Open the SMS and click the google.com link
Browser will open
Search for a Package DIsabler Software apk -ez disabler or package disabler pro etc.(You should pay the developer later)
Download and Install the app.
You will get Open Option right after Installation is finished.
Enable Emergency Launcher.
Press Home.
Voila, You can now exit UPSM without Factory Reset

Moto G - Won't turn on after Cache partition reset / factory reset (?)

To start off, recently out of the blue, whenever I would open any app and had other apps already open, the current app I would be on would close. For example, after trying to open the Google Play Music app and having it close seven times after opening it, it'll finally let me open the app and then listen to music. I click the change song button and then the app crashes with a notification saying this or just crashes without one. I read also this had to do with the Google Play Services app. I disabled it and enabled it twice. No difference at all.
This is for all applications and drove me insane. I eventually decided to research it and came up with the answer of resetting the cache partition. I did so but then was stuck in boot loop. I wasn't really sure what to do at this point. Perhaps this was a mistake but, I decided to factory reset my phone. Now, the boot loop only vibrates and goes to the light-green Motorola symbol. Nothing else for hours.
The previous times I've had to reset this phone (about four now) the device would show the commands it's doing and then you would see it finish. It didn't do it this time, simply saying resetting cache and reformatting.
I'm lost at this point.
Perhaps someone will have knowledge about this?

Try to reinstall rom from fastboot.

The phone does not wake up properly after flashing Oreo?

Hi there, your comments would be greatly appreciated.
To keep data, I flash the whole 8.0 stock firmware after removing -w.
After using days, the phone can't be easily unlocked, even by power key or by FPR. Sometimes, I need to wait a more long time for the phone waking up.
Sometimes the incoming call can't even wake it up, I can't answer the call.
Have reflashed the firmware with -w available then restore all my app via titanium backup. the issue persists.
Please help! How to tell which app prevent the phone from waking

Try factory reset and not restoring data with titanium rather Google backup
Sent from my Pixel using Tapatalk

Thanks. have tried clean install. everything is fine before restoring data with titanium.
So there must be some app which prevent phone from waking. Is there any chance of find this app.
PunishedSnake said:
Try factory reset and not restoring data with titanium rather Google backup
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse

I'd say just start over....
I'd say it's titanium backup restore itself
Sent from my Pixel using Tapatalk

thank you dude, will take a try.

If the issue persists you could give a list of the apps you install if you don't mind.. maybe we can figure out which one affects the unlocking. :highfive:
Sent from my Pixel using XDA Labs

I'm having a similar issue, but in my case I'm having trouble waking up the phone after it's been unplugged from the charger. If I use my phone all day after a full charge (and after rebooting), it's silky smooth, but the second I plug it in, the issue starts until I reboot again.

It might be extreme, but I've done this multiple times on previous phones. I restore half my apps, say the ones starting with A through M. If there's no problem, then I install half of what's left, say N through S, etc. Keep doing this as a process of elimination. Yes it's tedious but eventually you can narrow down the problem app and/or app data. You could also try restoring all of your apps without data, and if there's no problem then restore the data for half of the apps, etc.
Otherwise, as @PunishedSnake said, don't restore data (or even apps) at all with Titanium Backup. It sucks but we all occasionally have to do that.

I've since factory reset my phone with minimal app installation (no Google restoring of apps), but am still experiencing this frustrating glitch, even with/without unplugging the charger and rebooting.
Debating whether or not I should root (and downgrade).

Safe Mode fixed the problem. I will try to find the apps which prevents the phone from waking up.
How can I do this.
boojay said:
I've since factory reset my phone with minimal app installation (no Google restoring of apps), but am still experiencing this frustrating glitch, even with/without unplugging the charger and rebooting.
Debating whether or not I should root (and downgrade).
Click to expand...
Click to collapse

bush911 said:
Safe Mode fixed the problem. I will try to find the apps which prevents the phone from waking up.
How can I do this.
Click to expand...
Click to collapse
I think I've found the problematic app in my case. I've been using immersive mode through Custom Navigation Bar and after disabling it, my phone has become responsive again. After double checking the app's description in the Play Store, it seems the dev hasn't updated it for Oreo yet.
#FirstWorldFragmentationProblems
Edited: In order to fix this problem, simply use Tasker to disable Custom Navigation Bar's Immersive mode whenever you turn off the screen, and re-enabling it either when you unlock the phone, or only for specific apps (which is what I do).

Yes. try to enable immersive mode via this command
adb shell settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
now everything is fine.
boojay said:
I think I've found the problematic app in my case. I've been using immersive mode through Custom Navigation Bar and after disabling it, my phone has become responsive again. After double checking the app's description in the Play Store, it seems the dev hasn't updated it for Oreo yet.
#FirstWorldFragmentationProblems
Click to expand...
Click to collapse

bush911 said:
Yes. try to enable immersive mode via this command
adb shell settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
now everything is fine.
Click to expand...
Click to collapse
Glad to hear you were able to resolve your problem. In my case, I actually don't want immersive mode activated all the time so I may still have to root in order to selectively choose which apps I apply this command to.
Edited: In order to fix this problem, simply use Tasker to disable Custom Navigation Bar's Immersive mode whenever you turn off the screen, and re-enabling it either when you unlock the phone, or only for specific apps (which is what I do).

Data recovery/Phone recovery on bootlooping pixel?

My phone died last Wednesday and has continuously proceeded to boot loop ever since. Not sure if this is due to mother board issues, a recent update, lack of space on device, or malfunctioning apps?
I don't think its a motherboard issue though. I was pretty much at capacity 29gb usable of 32gb. I recently downloaded instagram and every time I used it the the system UI send a warning message and proceeded to crash every time, but the phone never boot-looped? I had recently updated to 8.1.0 and after looking at the android loading screen over 1000x now, I can tell that the animation is a little different from before.
The bootloop that I am experiencing isn't a load then restart loop it's just an endless load. With the the google 'G' and an endless loading bar beneath swaying side to side for hours on end.
Unfortunately I haven't backed up my phone in more than 5 months. I was wondering if there was anything I can do to get my data back (i.e. media, numbers, texts etc.) or potentially get my phone working again with the data intact?
I can boot into recovery mode perfectly. In the past google had a "clear system cache feature" on V7.1 I think? but that was phased out with more recent updates leaving me with the option of only factory resetting the phone. My phone is not rooted. I was wondering if there was anything I could do in the recovery screen that could mimic the clear system cache feature? Like writing some sort of command line or something? Or anything else that I could do to get my data back and my phone working again?
What are my options?

buttface12 said:
My phone died last Wednesday and has continuously proceeded to boot loop ever since. Not sure if this is due to mother board issues, a recent update, lack of space on device, or malfunctioning apps?
I don't think its a motherboard issue though. I was pretty much at capacity 29gb usable of 32gb. I recently downloaded instagram and every time I used it the the system UI send a warning message and proceeded to crash every time, but the phone never boot-looped? I had recently updated to 8.1.0 and after looking at the android loading screen over 1000x now, I can tell that the animation is a little different from before.
The bootloop that I am experiencing isn't a load then restart loop it's just an endless load. With the the google 'G' and an endless loading bar beneath swaying side to side for hours on end.
Unfortunately I haven't backed up my phone in more than 5 months. I was wondering if there was anything I can do to get my data back (i.e. media, numbers, texts etc.) or potentially get my phone working again with the data intact?
I can boot into recovery mode perfectly. In the past google had a "clear system cache feature" on V7.1 I think? but that was phased out with more recent updates leaving me with the option of only factory resetting the phone. My phone is not rooted. I was wondering if there was anything I could do in the recovery screen that could mimic the clear system cache feature? Like writing some sort of command line or something? Or anything else that I could do to get my data back and my phone working again?
What are my options?
Click to expand...
Click to collapse
I think you can clear cache in fastboot. Not sure why you would continue to use an app that is crashing system.

lafester said:
I think you can clear cache in fastboot. Not sure why you would continue to use an app that is crashing system.
Click to expand...
Click to collapse
That feature was taken out of the boot-loader by google in the past few updates. I'm currently on 8.1.0.
I was wondering if there was an alternative method that I could take in fast boot/recovery mode that could possibly give me the same cache clearing result? Possibly some sort of adb method or something? Also unfortunately my boot loader is locked. So If I can't clear the cache, I was wondering what my current options are as far as backing up the device before I inevitably have to do a factory reset are?