Database Info

[IMPORTANT] For Those Updating to D80020y OTA firmware

You may want to wait on updating to D80020y. Here's why;
In my experience, the update has corrupted the System UI process causing
*crashes on lockscreen/boot
*crashes to home while attempting to use an app
*apps to restart infinitely and drain battery.
*break lock screen and standby functions (KnockOn and power button) causing you to be unable to wake or enter passwords to your phone without force shutting off phone.
*There is a 50% chance of this bug happening to you on/after boot. If your phone is not experiencing these crashes; do NOT shut it off!
*Safe Mode will NOT prevent these crashes, System UI may still crash.
*My firmware before the update was STOCK rom before I updated on 9/7
TEMPORARY WORKAROUND: If you are able to access home screen, let the phone sit for a few minutes after booting and "warm up" after this period of time; apps will stop restarting and allow the UI to become stable.

I've been using 20y since getting the update, no issue at all.
Were you on stock or custom ROM?

votinh said:
I've been using 20y since getting the update, no issue at all.
Were you on stock or custom ROM?
Click to expand...
Click to collapse
No, I was always on stock AT&T rom. Never rooted either. If I remember correctly, the problems didn't appear until I rebooted the phone a few hours after updating. Maybe it is just me

Try factory reset and see if it gets any better.

Still Reboots in Marshmallow

Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.

Treizez34 said:
Has anybody been running into their phone rebooting with Marshmallow? Mine is still doing it. Already tried re flashing and clearing cache.
Click to expand...
Click to collapse
I am having the same issue. Random reboots.
I already install the 6.0 three times. one sideload and two fresh installs (full wipe + factory images). I even tried to roll back to lollipop and then update again.... same problem =(
device:
Nexus 5 - 32gb international + moto360

Sorry for my English.
I have the same problem with the Nexus 5 32GB D820.
Marshmallow clean installation ran smoothly yesterday, today began to randomly reboot.
I tried to make a factory reset and left in a bootloop.
I had to re-flash the factory image.
Let's see if it happens again.

Likely defective power button

My nexus 5 32gb is also randomly rebooting on android 6.0

The same problem with D821 16 Gb. 4 times clean installation. 1 time step-by-step installation for each part of factory image - no result. Random reboots.

There is no random reboot software bug, only faulty key

GR0S said:
There is no random reboot software bug, only faulty key
Click to expand...
Click to collapse
What do you mean with faulty key? Faulty like hardware or faulty like software? Cause I have my Nexus for 1,5 years and had never problems with power button at all. The problem comes only with Marshmallow.
---------- Post added at 07:22 AM ---------- Previous post was at 06:47 AM ----------
So, there is no full restart. If you press the power button for 10 seconds, the phone will restart and you'll hear a little vibration and see "Google" logo, after that Marshmallow animation appears. Faulty key can only cause full restart effect. But in Marshmallow I have only the shell restarts, i.e. the phone restarts with Marshmallow animation (not with vibration and "Google" logo) and this lasts 3-5 seconds. This is definitely software bug.

Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk

beekay201 said:
Are we talking about M, flashed with fastboot, and almost no user apps installed and no mods (root, custom kernel, etc)?
Because if we are, there are no random reboots.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Exactly. Flashed with fastboot, no mods, no root, no any customs. Only user apps. But you are right. I'm testing all my apps and I've found 2 weather apps. They probably caused the reboots. I'm not sure about it, cause I'm looking into all my apps.

its not a defective power button.
I roll back to lollipop and the random reboot stopped.
I did another try with marshmallow, this time with sideload installation and full wipe after. At the beginning i get two random reboots, but now it seems to be ok. no more random reboots.

SOLVED. The problem was caused by Weather Live application (https://play.google.com/store/apps/details?id=com.apalon.weatherlive). With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.

dr_stevens said:
SOLVED. The problem was caused by Weather Live application. With first installation of Android M I noticed that the app shows error message. Now, when I know cause and effect, I read feedbacks in Play Market and see other people reports crashes in Marshmallow with this app. So, if you have random restarts in Android M and Weather Live app installed, then try to delete it and wait if system will be stable.
Click to expand...
Click to collapse
I found the same issue. I'm a registered user of Weather Live, but I've found that the app is causing numerous crashes after I upgraded my Nexus 5 to Android 6 ( Marshmallow). I ran a bug report and searched it for 'FATAL EXCEPTION:', I can see that everytime there is a crash, one of the threads affected belongs to Weather Live. What I then get is a restart of the User Interface, so it goes into the 'android' animation you normally see on boot. The phone stays up because the System Uptime is not reset.
I've uninstalled the app for the moment to see if that cures the issue.

i am experiencing random reboots with my Spice Dream Uno and ended up in this forum while searching for my cause. first i thought its my device got hardware issue but it never happened before in lollipop or kitkat. it seems just like a possible hardware fault too and phone will be in bootloop , then cant even power on the display(backlight flluctuates,with black screen). when i pull the battery and reinsert after few minutes the phone starts normally. seems like Marshmallow has critical campatibility issues with some applicationsThe crash never happens in same application for me.And i have no roots ,customs etc..Came to 6.0 via OTA from lollipop.
My device dont have any issues upto now(its been an year).

I've been noticing it with a very minimal base of packages. Seems to only happen shortly after waking from deep sleep so I highly suspect doze. The phone will be fine... you set it aside... it enters doze deep sleep... phone wakes, you unlock... then bam, reboots, and enters boot loop at the Google splash screen. I've already done a factory reset, will be attempting a fastboot reflash with the new November system image today.

Wi-Fi stuck, it doesn't activate.

Hi, i recently installed the Resurrection REMIX rom for the shield k1, and it's impossible to connect to wi-fi as the activate-deactivate button is locked (gray) and it does not work even after a reboot, i can bring the wi-fi list in the notifications bar but if i try to deactivate it, it activates again.
is anyone facing a similar issue? how can i fix it? this wasn't a thing when i had the stock ROM with android 6.0.1 and i'm truly annoyed by this.

update: tried reinstalling the custom rom, now i can't complete the setup, and using power + volume down will not bring recovery mode to restore the stock ROM, now i'm left with an unusable device, what a nice day.

how to remove gltools (r9 plus brick) help needed

I installed GLtools and after completing, the screen stuck and it is always on (never sleeps or dims display). None of the buttons work. I waited till it used up all battery and then charged to 5% to turn on again. When I turn on, I see my launcher still the same (and the phone launcher desktopsetup pretty intact), but after a few seconds, screen stuck again, buttons not working again.
Is there a way to remove/uninstall GLtools through PC or whatever means to fix this?
Please help.

Did you flash it in stock recovery or TWRP?
Also next time you need to forcibly switch the phone off, do it by either holding the power button for 10secs, or all three button for 10secs (not sure which it is on the R9+), it's a lot quicker than trying to flatten the battery!

Lum_UK said:
Did you flash it in stock recovery or TWRP?
Also next time you need to forcibly switch the phone off, do it by either holding the power button for 10secs, or all three button for 10secs (not sure which it is on the R9+), it's a lot quicker than trying to flatten the battery!
Click to expand...
Click to collapse
I did not flash anything. It was in stock rom. Is there still a way to fix this (remove GLtools)? Is the GLtools running in background that's why I was still able to unlock my phone and use my phone for a few secs before screen hang again?
EDIT:
I got it to work long enough to uninstall GLtools but there is this loading bar that appears even after I had removed GLtools,
http://i.imgur.com/dN4HaZW.jpg
Is this from the phone? or from my root app?
My phone screen still hungs now. I think it's not GLtools issue.

That bar is a ColorOS thing that it does while your system is updating.
Can you re-flash the stock ROM?

Lum_UK said:
That bar is a ColorOS thing that it does while your system is updating.
Can you re-flash the stock ROM?
Click to expand...
Click to collapse
So I learned how to force close the phone from you (hold power button for 10 secs), then I turned it on normally, it worked fine as normal. I tried rooting with KingRoot and it rooted, tried to install Xposed Framework thru a method found in youtube because I don't have TWRP (method uses BusyBox Pro, Terminal Emulator to flash the zip). But Xposed modules download button don't download (button goes back to idle when I tap "download").
I also tried Lucky Patcher and other similar apps to convert or move user app to system app, after reboot, the converted app is gone (deleted). This bar also keeps appearing after I did this.
That bar keeps appearing and freezes the screen (whatever the screen is currently showing) both during and after the progress bar finishes. Tried to force close and turn it on again. Stuck on Oppo screen for 8+ hours (left it as is, I went to sleep). Decided to flash the stock rom (power + vol down) without wiping data. Worked and returned to normal desktop launcher setup but phone goes back to unrooted. Xposed Framework is gone too.
Is this bar meant to check if I am doing changes to the system like root, Xposed, converting user app to system app and prevent me from doing those? I really need those things on my phone! :crying:

the bar is just when ColorOS is updating itself or generally making changes. Presumably it doesn't like something you did.
I'd probably leave off GLTools and just go with KingRoot and Xposed. They both worked on my old R9. I think the latest version of the Xposed APK has the ability to install the framework itself, so maybe try that method?
ColorOS is heavily modified from stock android, so a lot of mods for it simply don't work, unfortunately.

Lum_UK said:
the bar is just when ColorOS is updating itself or generally making changes. Presumably it doesn't like something you did.
I'd probably leave off GLTools and just go with KingRoot and Xposed. They both worked on my old R9. I think the latest version of the Xposed APK has the ability to install the framework itself, so maybe try that method?
ColorOS is heavily modified from stock android, so a lot of mods for it simply don't work, unfortunately.
Click to expand...
Click to collapse
why did the download button of Xposed not work when I tap on it? it does nothing for me.
Which Xposed should I get? I saw 2 APKs, a 3.0 and 3.1.1 alpha 4.
I was actually rebooting after I checked XMultiWindow module in Xposed when it got into bootloop

Get 3.11a4

bootloop after weeks of normal usage

bootloader unlocked
MIUI 9.5.19 global ROM installed
Magisk 16.4
Have been using the phone for 2 weeks now it's the second time that the phone shut down because of battery to low. OK so far but it then only is booting into TWRP. Also deleting DALVIK and CACHE i can see it booting and then the black screen with the navigation arrows are visible for a second. It's seems that there is something preventing the system to come up properly. After 5 short attempts with black screen and navigationbar visible it boots into TWRP.
Also re-flashing Magisk is not solving it.
OK I could now re-flash the Global ROM again but it won't fix the general issue why the phone get's stuck once it shuts off because of empty battery and again I would loose all my data.
Anyone with ideas how to fix it or what could be the root cause?

EDIT: It seems that there is really a problem with the system itself. If I instantly hold the power button once booted until the black screen I could keep it running and I see the restart, shutdown, airplane buttons but nothing more.
In Windows I would say it's not starting the explorer.exe
anyone who had something similar?

Have you tried re-flashing with MiFlash?

Bootloop after weeks of normal use is pretty misleading considering that you are using a custom recovery that isn't even official plus Magisk and possibly other mods. You should flash the official stable ROM with the MI Flash Tool and then run the phone without any mods to see if you still experience the same problem. And if you decide to use TWRP again you are better off using it through fastboot so the stock recovery remains installed on the phone.

THx for your replies... I think I've figured it out:
It seems that the alternative launcher is the root cause. I've been using Microsoft Launcher since moths across all my devices (light+fast+sexy). Without it (replaced by Nova now) it seems that the problems are fixed