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?

Stuck on Console Mode

I am stuck in console mode!
Is there a hackable way to turn off console mode?
Like an adb call or a config file I could change or something like this?
On Shield Tablet FW v. 4.0.1 (MM) I went into console mode, but the System UI crashes constantly right from the start for whatever reason. Therefore I can't tab anything on the screen except for the crash dialog.
The dialog to disable console mode shows up, but I can't interact with it.
Several reboots did not help. I just can't leave this mode and am stuck with no interaction possible.
On earlier versions the tablet returned to normal mode automatically after reboot, but not this time. I am rooted and unlocked with TWRP. So I am still able to work in the file system or adb/fastboot.
So does anyone know what I have to configure manually to turn console mode off?

You could try clearing the cache on the device

Thanks for the contribution.
I already tried that, though.
I even reflashed the system image without wiping the data and nothing changed.
So it must be somewhere on the data partition or even sdcard.

I am stuck in this now, stock 4.2 rooted. I see a few posts on this but nobody ever bothers to post their resolution.
Is wiping data the only fix?
edit-
So for me, I wiped data and all was well. what a pain in the ass. So I need to make a backup every time I want to try and use console mode?
mirror mode has worked fine, just wanted to try with screen off.

Yeah, unfortunately I ended up wiping data as well. I tried even to just install the system without wiping first, but did not help.
So I took this opportunity and updated to the latest version as well.

Yeah, unfortunately I ended up wiping data as well. I tried even to just install the system without wiping first, but did not help.
So I took this opportunity and updated to the latest version as well.

I have had the same problem and could not fix it so now I use an app called second screen instead of console mode. Not only can you eliminate black bars on side of screen, but you can manually change resolution as well as turn off the backlight while connected to a display. Just look up the app on play store. BTW, you will still have to clear data first.
Sent from my 306SH using XDA-Developers mobile app

Marshmallow problems with spontaneous launching of Google Now, taking over device.

My phone has been misbehaving since it upgraded the OS to Marshmallow. It was primarily occurring with the Google Now app and it would take over the phone and flash up and off the screen and whilst this was going on, the phone is busy vibrating, the screen became unresponsive and generally I couldn't do anything with it during these episodes. I stopped it sending to the screen and then it was the Google app that kept flashing up, starting with a round circle coming from the app drawer icon. It has got worse over the last few days to the point that it might take me ten minutes before I could get access to the caller to make a call and even trying to shut down the device was near impossible because the confirmation box never stayed on the screen long enough to answer the question and then it didn't come back. Yesterday, after many tries to restart, it finally restarted in safe mode. If it was related to an app that I downloaded, it should have stopped then but it didn't. When I was able to get into settings, I then went to apps and then disabled google app as this was the one starting up and flashing the screen non stop. I was then asked if I wanted to replace it with a factory version which I did but I also left it disabled. The problem has continued but not as ferociously with the screen becoming unresponsive at times while the buzzing from the vibrate still occurring. I have looked up various forums but haven't found any that have similar problems described. I checked the screen overlay settings and they are enabled and that seems to be the main problem with marshmallow. I'm looking for some advice but realise that this might be too basic for this forum? Vodafone Smart ultra 6, Android version 6.0.1 Kernel version 3.10.49

Stoksie said:
My phone has been misbehaving since it upgraded the OS to Marshmallow. It was primarily occurring with the Google Now app and it would take over the phone and flash up and off the screen and whilst this was going on, the phone is busy vibrating, the screen became unresponsive and generally I couldn't do anything with it during these episodes. I stopped it sending to the screen and then it was the Google app that kept flashing up, starting with a round circle coming from the app drawer icon. It has got worse over the last few days to the point that it might take me ten minutes before I could get access to the caller to make a call and even trying to shut down the device was near impossible because the confirmation box never stayed on the screen long enough to answer the question and then it didn't come back. Yesterday, after many tries to restart, it finally restarted in safe mode. If it was related to an app that I downloaded, it should have stopped then but it didn't. When I was able to get into settings, I then went to apps and then disabled google app as this was the one starting up and flashing the screen non stop. I was then asked if I wanted to replace it with a factory version which I did but I also left it disabled. The problem has continued but not as ferociously with the screen becoming unresponsive at times while the buzzing from the vibrate still occurring. I have looked up various forums but haven't found any that have similar problems described. I checked the screen overlay settings and they are enabled and that seems to be the main problem with marshmallow. I'm looking for some advice but realise that this might be to basic for this forum? Vodafone Smart ultra 6, Android version 6.0.1 Kernel version 3.10.49
Click to expand...
Click to collapse
When you updated to Nougat, what method did you use to update? Did you update via OTA? We're you rooted when you did it?
Have you tried booting to recovery and factory resetting and wiping cache then rebooting?
Sent from my SM-S903VL using Tapatalk

Droidriven said:
When you updated to Nougat, what method did you use to update? Did you update via OTA? We're you rooted when you did it?
Have you tried booting to recovery and factory resetting and wiping cache then rebooting?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
It was an update that appeared on my notifications and I thought it was a small bug fix update and didn't realize that it would replace the entire OS. I just allowed the update and then realized what had happened. I think it is Marshmallow that it updated to but originally the app drawer was paginated and accessed by side swipes whereas the system now is a long page of apps moved up and down. I don't know if it was rooted and I assume that that means it wasn't.
I was trying to avoid a factory reset but I did wipe the cache and rebooting. When google apps is disabled, the interruptions are less often and not for as long but it still went into a complete meltdown of a screen appearing and disappearing at such a rate that nothing can be done with it. It won't show a video because of the interruptions.

Stoksie said:
It was an update that appeared on my notifications and I thought it was a small bug fix update and didn't realize that it would replace the entire OS. I just allowed the update and then realized what had happened. I think it is Marshmallow that it updated to but originally the app drawer was paginated and accessed by side swipes whereas the system now is a long page of apps moved up and down. I don't know if it was rooted and I assume that that means it wasn't.
I was trying to avoid a factory reset but I did wipe the cache and rebooting. When google apps is disabled, the interruptions are less often and not for as long but it still went into a complete meltdown of a screen appearing and disappearing at such a rate that nothing can be done with it. It won't show a video because of the interruptions.
Click to expand...
Click to collapse
Unfortunately, I think you're gonna have to factory reset in stock recovery because there's obviously a conflict with something you already had on the device and it isn't playing nice with something that was in the update.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Unfortunately, I think you're gonna have to factory reset in stock recovery because there's obviously a conflict with something you already had on the device and it isn't playing nice with something that was in the update.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thanks for taking the time to respond. I have resigned myself to that although it does not seem to be anything that I downloaded to the phone as it occurred in safe mode too. I was just hoping that there was a fix out there but obviously it is not a widespread occurrence.

Stoksie said:
Thanks for taking the time to respond. I have resigned myself to that although it does not seem to be anything that I downloaded to the phone as it occurred in safe mode too. I was just hoping that there was a fix out there but obviously it is not a widespread occurrence.
Click to expand...
Click to collapse
It could have been something in system that got changed during the update but the data from before the change is still there and conflicting with whatever changes were made. Some kind of saved system data that can only be wiped by factory reset or reflashing.
Sent from my SM-S903VL using Tapatalk

I did a factory reset, lost a lot of photos that had started being saved on the phone and not the sdcard after the upgrade to Marshmallow. Have had to accept that but unfortunately the bizarre behavior did not stop and it continues on and off, sometimes so bad that I cannot dial a number on it and other times it happens but I can get in between the action and dial or send a text etc. I have gradually been stopping things like notifications from google apps and traffic reports from google maps (this may have had a good effect) and anything that might be doing constant checks. It seems to have quietened down over the last day or so and I even got to play a game on it but the next option is to send it away to an engineer. I just thought that I would let you know the outcome of the factory reset.

Why does my Google Pixel randomly reboot?

Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?

marf3 said:
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
Click to expand...
Click to collapse
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update

pradctgign said:
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
Click to expand...
Click to collapse
I noticed problems with my ear speaker as well. And i cant make phone calls. The phone doent respond anymore when i try to.

Same problem after android 8.0 update

If you have installed the latest Google phone/dialer app, that is likely the problem, was for me.
Find the app in settings and uninstall,it will roll back to a previous version and hopefully fix your issues.
Sent from my Pixel using Tapatalk

My pixel does the same thing, ever since I updated to 8.0, have you tried doing a factory reset? I haven't done it yet, I have been uninstalling apps for the last couple of days, when it is in safe mode it works good, but when it's not, it freezes and restarts. I'm going to try uninstalling the latest version on google dialer to see if it helps.

I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.

droid4lif3 said:
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
Click to expand...
Click to collapse
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.

wrong place sry

Had this on my pixel xl. I was on the 8.1 beta.
factory reset, rolled back to 8.0
8.1 ota official
haven't had a reboot in over a week now

Murrzeak said:
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
Click to expand...
Click to collapse
Yea, the issue is back, has been for about 2 weeks. This phone is really starting to be a pain in the ass, I can't believe that it happens so often. Did you do a warranty fix?

That's a pity. Yes, I did. Got the device roughly two and a half weeks ago. Flashed 8.0 and then sideloaded 8.1 right away. Knock on wood, all good. But there's still a report every other day in Buganiser of a phone even on 8.1 doing this.

Got mine at release. November 16. Google won't replace it either. I have a one pixel brick

I have the same problem. However, it is not frequent enough on Android P beta. But as soon as I go back to the stable build, it starts to do the same thing. Did you guys have any luck resolving this or should I send it back to the vendor I bought it from. They won't replace the device in Pakistan but may be will fix it in some manner.

Stock Pixel 2 bootloop

Just recently got this phone direct from Google in the UK. Now back in Japan, so a return is not too easy....
I noticed my phone vibrate a couple of times in my pocket, and then saw it was rebooting. It's now stuck in a bootloop with these screens:
(First it says "com.android.phone has stopped", then reboots)
View attachment 4386691
View attachment 4386692
I can also get to this screen...
View attachment 4386693
Before I try 'Factory data reset' is there anything else I can do? I'd really like to save installed apps, logins etc. cos that all takes ages to setup. As it's all stock I have no backup :/
Many thanks if you can help!

same problem there
details https://android.stackexchange.com/questions/188957/how-to-get-my-data-on-encrypted-and-not-booting-pixel-2
looks like decrypting keys not updated properly after updating...

that doesn't sound great. My phone is stock though - could it be the same thing?

Anything else I can try before wiping?

You can try flash factory image without -w key, if device unlocked

Not good sign. It's locked

According to the photos the device state is locked. And as you know (but the OP may not) unlocking will wipe the device anyway.

Thanks all. Realised that 'locked'status meant I was pretty much fcked, so I wiped and all's well - just a hassle logging back into every single service and downloading every app.
Any idea wtf might have caused it? I mean, this time it was an annoyance, but if it happened up a mountain it could be a major drag.