When the phone is off and you plug in the usb cable to charge, before it used to go to the coffee mug screen on. Now it just stays on the Essentials logo screen, I can manually boot it by holding the power button down a few seconds, or boot it normally with the USB cable out. I'm not sure if this is because of the Pie update and Essentials broke it by accident, or it's due to Magisk/unlocked bootloader, or bad RTS flashing. Other than that, the phone is fine. Is anyone else experiencing this?
I am able to replicate this on my phone running the latest version of Pie. I first discovered it when I plugged my phone into the stock charged and attempted to power it off. Instead of powering off and showing the charge screen, the phone acted like it was going through a reboot process. It would display the unlocked bootloader warning and initial splash screen and it gets stuck on this screen. It requires me to power cycle the phone by holding the power button for several seconds. Prior to updating the phone to Pie I know I was able to power it off while the charger was connected without experiencing this behavior. I bought two of these phones so I will try it out on the other one when my girlfriend gets home tonight.
This is the same thing i'm experiencing so at least that should rule out bad flashing. Were you able to check the other phone to see if it also happens on it and is it stock? If it's stock and does the same thing then i'll send an email to essentials to ask if they are planning to fix it.
winggndm1 said:
This is the same thing i'm experiencing so at least that should rule out bad flashing. Were you able to check the other phone to see if it also happens on it and is it stock? If it's stock and does the same thing then i'll send an email to essentials to ask if they are planning to fix it.
Click to expand...
Click to collapse
I did test the other phone and it behaved the same as mine. I tried using both of our adapters as well as my S8 adapter with the same results. I tried to power it off while it was plugged in via recovery but it begins to reboot then gets stuck on the "Powered by Android" screen. I'd appreciate you letting me know their response to the issue.
So restoring the stock boot image fixes the issue. I reflash twrp, the stock boot image and installed the zip, and back to the same behavior. So magisk must be modifying the image incorrectly and breaking it. I'll report this on the magisk thread.
https://forum.xda-developers.com/showpost.php?p=77402354&postcount=6560
it seems that using 16.6 works. Something broke in 16.7 and affects also Pixel users.
winggndm1 said:
When the phone is off and you plug in the usb cable to charge, before it used to go to the coffee mug screen on. Now it just stays on the Essentials logo screen, I can manually boot it by holding the power button down a few seconds, or boot it normally with the USB cable out. I'm not sure if this is because of the Pie update and Essentials broke it by accident, or it's due to Magisk/unlocked bootloader, or bad RTS flashing. Other than that, the phone is fine. Is anyone else experiencing this?
Click to expand...
Click to collapse
I'm experiencing this too. Any updates?
I just downgraded to Magisk 16.6 and the charging icon is back. I can confirm that it is working. Thank you for the headsup!!
Same exact issue here.
Now on Magisk 17.1, Pie Oct, Stock Kernel, permanent TWRP.
Was happening on 16.7 as well prior to permanent TWRP.
I never used Magisk below 16.7 so I can't comment on that.
Also noticed that the phone gets pretty hot when charging while off, with the "stuck" Essential logo screen.
Anyone else's phone get pretty hot while charging "off"?
ultrasuper said:
Same exact issue here.
Now on Magisk 17.1, Pie Oct, Stock Kernel, permanent TWRP.
Was happening on 16.7 as well prior to permanent TWRP.
I never used Magisk below 16.7 so I can't comment on that.
Also noticed that the phone gets pretty hot when charging while off, with the "stuck" Essential logo screen.
Anyone else's phone get pretty hot while charging "off"?
Click to expand...
Click to collapse
Update magisk to the canary build
rignfool said:
Update magisk to the canary build
Click to expand...
Click to collapse
I'd rather wait for the stable release to come in.
This issue seems to be only a cosmetic issue (I hope).
Maybe it's real, maybe it's coincidence, but my Pixel XL was having the same issue. Once night, I turned of the phone, the issue occurred, and the next morning my screen would not turn on. The LED at the top would light, but no screen. I took it to be repaired per Google, and was told they tried 3 screens and none would work. They believed it was something with the motherboard. Coincidence or fact? I do not know, you be the judge.
Related
Ok, so here's the problem:
I plugged my limited edition white Nexus 4 into the wall charger, and it locked normally, even the lock animation came. (Didn't power off, just locked.).
I just pressed the power button as I normally would, but it did not ask me for the unlock pattern. In fact, all I could see was a dim LED backlight.
So I searched on Google and then on xda, and found a thread which instructed me to hold down the volume up and power buttons for 20-30 seconds, and then to hold down the power button. I did this, and it made my phone boot up normally. But when I unlocked my phone, I noticed that the screen was flickering. Not black and white or whatever, but between the different brightnesses. I then locked the phone (Not power off).
After turning it back on, there were no problems, in fact, I just rebooted the phone, and it seems to be working fine.
I want to know how I can prevent this problem from happening again, and what to do if this happens again.
I haven't rooted, custom ROMmed or unlocked bootloader, and do not plan to do so. All I have done yet is update my phone to Android 4.3, using an official Google .zip file I found on DroidLife. It is an official file, not a leaked build. I do not think that is relevant, but I thought I should tell you anyway. Also, this may have something to do with the charger, because the phone turned off as soon as I plugged it in, or the timing was just ridiculously good.
Please read this carefully, every line is important. Nexus 4 specs have been given in signature.
poop happens. you cant provide any logs at the moment, so we cant see what happened. just a fyi, stock, official roms, also are buggy occasionally. my guess is that it had a derp somewhere to begin with, it happens. a reboot, or a forced reboot usually resolves the situation. with root, theres a bit more troubleshooting/action that can be taken in a situation like this, maybe even some preventative action like a dalvik wipe.
simms22 said:
poop happens. you cant provide any logs at the moment, so we cant see what happened. just a fyi, stock, official roms, also are buggy occasionally. my guess is that it had a derp somewhere to begin with, it happens. a reboot, or a forced reboot usually resolves the situation. with root, theres a bit more troubleshooting/action that can be taken in a situation like this, maybe even some preventative action like a dalvik wipe.
Click to expand...
Click to collapse
Thanks for the reply
If I root the Nexus 4, will i be able to install OTA?? Even installing through adb sideload is fine with me. Basically, is it possible to root and still get updates? If it is possible, what is the method to install updates? What is the most reliable method to root for Nexus 4? Can I root without installing a custom recovery? I'm not gonna install custom ROMs on the Nexus until it is outdated. Sorry about all the questions, as I am very curious.
So I'm not sure what the **** happened, but my 6p decided to brick itself after the latest update. It's essentially in a perpetual bootloop. When it does manage to boot up, it bootloops again a few seconds later. I tried reflashing 7.1.1 and 7.0 multiple times. Nothing worked. It's running completely stock software, so I'm not sure what exactly could be the problem. Has anyone else experienced this problem? Either way, I haven't had good luck this year with tech... Galaxy Note 7, EVGA GTX 1080, and now a bricked 6p... I think I may have a curse or something.
Call Huawei and they will fix your phone at no cost. Don't even try to fix it !
Try Wugs first to go back to full stock.......fully automated......Let it try to fix the problem.....
Kind of sounds like you didn't update your vendor files......
http://forum.xda-developers.com/showthread.php?t=3258493
Sent from my Pixel XL using XDA Premium HD app
This is a known bug. Happened to me a month ago. I decided to ditch the Nexus 6p and get an LG V20. I called Huawei and they were going to do an RMA at no cost but the fact that I opened my phone to check if the power button wasn't the cause of the bootloop they said the warranty was voided. They wouldn't let me pay cash for any repairs.
Let me tell you my story and somehow my Nexus is working again. I'm now one my 1+3 though. So I was enrolled in the beta program. Bootloader unlocked, stock recovery. When I updated to dp2, twice my device rebooted and got stock at the Google logo. No access to recovery only bootloader. Then the next day literally, the OTA for final 7.1.1 was released. I decided to sideload the OTA. Magically, my Nexus came back to life. This would be short lived. About 48 hrs later. I was in the camera, and bamm, it froze then boot loop from hell. My Nexus was in the same pickle as dp2. After researching online, no fix. I was on my new phone and figured it was a goner. I left it charging constantly and would never turn on. Then the full image came out. Figured I'd try it out. Flashed it to no avail. Still stuck. Again I wrote it off upset but life goes on. 2 nights ago when I could not sleep, I had a strange idea. Lemme flash back to 7.0. so I downloaded the image from Google and flashed it. Same result. I then had an appifany, now your mileage may vary, I realized I had been charging my Nexus with my 1+3 dash charger. I switched it to the stock brick I have plugged in elsewhere. It was still bootlooping but I left it plugged in. Yesterday morning when I awoke, I noticed something different, my Nexus was on the charging screen when the unit is turned off, hence showing the battery logo @ 100%. I then held my power button and lo and behold, it turned on and greeted me to 7.0 setup. I nearly **** the bed. I skipped most the setup as I didn't care. Set up my wifi, and it went to the home screen. Instantly popped up with an OTA to final 7.1.1. So I proceeded to download it. Now I didn't recheck my phone untill I got back from work, but when I did, my phone was still on, OTA downloaded and ready for install, a little over 600 meg update. Before going to bed, I hit restart and upgrade. It when through the update without a hitch. My phone has been. Working for 24hrs, no crashs or bootloops. Fingers crossed this does not reoccur but my Nexus thus far is fully running with no reoccurrence. I wonder if this issue has something to do with what it's plugged into. I have no explanation as to why or how but that's what I'm pointing my finger at as not every USB c power brick and cable is made equal. Maybe a fluke, it may rebrick itself , but for now it's back in action sitting on the sideline. I will update if it rebricks itself.
Sent from my ONEPLUS A3000 using Tapatalk
icedmayhem said:
Let me tell you my story and somehow my Nexus is working again. I'm now one my 1+3 though. So I was enrolled in the beta program. Bootloader unlocked, stock recovery. When I updated to dp2, twice my device rebooted and got stock at the Google logo. No access to recovery only bootloader. Then the next day literally, the OTA for final 7.1.1 was released. I decided to sideload the OTA. Magically, my Nexus came back to life. This would be short lived. About 48 hrs later. I was in the camera, and bamm, it froze then boot loop from hell. My Nexus was in the same pickle as dp2. After researching online, no fix. I was on my new phone and figured it was a goner. I left it charging constantly and would never turn on. Then the full image came out. Figured I'd try it out. Flashed it to no avail. Still stuck. Again I wrote it off upset but life goes on. 2 nights ago when I could not sleep, I had a strange idea. Lemme flash back to 7.0. so I downloaded the image from Google and flashed it. Same result. I then had an appifany, now your mileage may vary, I realized I had been charging my Nexus with my 1+3 dash charger. I switched it to the stock brick I have plugged in elsewhere. It was still bootlooping but I left it plugged in. Yesterday morning when I awoke, I noticed something different, my Nexus was on the charging screen when the unit is turned off, hence showing the battery logo @ 100%. I then held my power button and lo and behold, it turned on and greeted me to 7.0 setup. I nearly **** the bed. I skipped most the setup as I didn't care. Set up my wifi, and it went to the home screen. Instantly popped up with an OTA to final 7.1.1. So I proceeded to download it. Now I didn't recheck my phone untill I got back from work, but when I did, my phone was still on, OTA downloaded and ready for install, a little over 600 meg update. Before going to bed, I hit restart and upgrade. It when through the update without a hitch. My phone has been. Working for 24hrs, no crashs or bootloops. Fingers crossed this does not reoccur but my Nexus thus far is fully running with no reoccurrence. I wonder if this issue has something to do with what it's plugged into. I have no explanation as to why or how but that's what I'm pointing my finger at as not every USB c power brick and cable is made equal. Maybe a fluke, it may rebrick itself , but for now it's back in action sitting on the sideline. I will update if it rebricks itself.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Dude this is really interesting. I am therefore holding off of updating to 7.1.1 and still using 6.0.1. Although 7.1.1 is very tempting to me. Keep us posted regarding your Nexus 6p's bootloop and workings on this thread please
Wow alot of people are having issue with the 6p... Google need to fix things asap
icedmayhem said:
Let me tell you my story and somehow my Nexus is working again. I'm now one my 1+3 though. So I was enrolled in the beta program. Bootloader unlocked, stock recovery. When I updated to dp2, twice my device rebooted and got stock at the Google logo. No access to recovery only bootloader. Then the next day literally, the OTA for final 7.1.1 was released. I decided to sideload the OTA. Magically, my Nexus came back to life. This would be short lived. About 48 hrs later. I was in the camera, and bamm, it froze then boot loop from hell. My Nexus was in the same pickle as dp2. After researching online, no fix. I was on my new phone and figured it was a goner. I left it charging constantly and would never turn on. Then the full image came out. Figured I'd try it out. Flashed it to no avail. Still stuck. Again I wrote it off upset but life goes on. 2 nights ago when I could not sleep, I had a strange idea. Lemme flash back to 7.0. so I downloaded the image from Google and flashed it. Same result. I then had an appifany, now your mileage may vary, I realized I had been charging my Nexus with my 1+3 dash charger. I switched it to the stock brick I have plugged in elsewhere. It was still bootlooping but I left it plugged in. Yesterday morning when I awoke, I noticed something different, my Nexus was on the charging screen when the unit is turned off, hence showing the battery logo @ 100%. I then held my power button and lo and behold, it turned on and greeted me to 7.0 setup. I nearly **** the bed. I skipped most the setup as I didn't care. Set up my wifi, and it went to the home screen. Instantly popped up with an OTA to final 7.1.1. So I proceeded to download it. Now I didn't recheck my phone untill I got back from work, but when I did, my phone was still on, OTA downloaded and ready for install, a little over 600 meg update. Before going to bed, I hit restart and upgrade. It when through the update without a hitch. My phone has been. Working for 24hrs, no crashs or bootloops. Fingers crossed this does not reoccur but my Nexus thus far is fully running with no reoccurrence. I wonder if this issue has something to do with what it's plugged into. I have no explanation as to why or how but that's what I'm pointing my finger at as not every USB c power brick and cable is made equal. Maybe a fluke, it may rebrick itself , but for now it's back in action sitting on the sideline. I will update if it rebricks itself.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Update:. 12/28. 0212 hrs. Even though I'm using my 1+3 as my daily driver, my 6p still works. No bootloops, random reboots, or freezing in os. Tested with calling, SMS, camera, downloads, etc. Haven't modified or flashed anything since, but then again I prefer stock nowadays. Can't say I'm not surprised although.
Sent from my ONEPLUS A3000 using Tapatalk
so many people encountering issues and bricks by updating from stock M i guess? to Nougat.
i have never once had an issue downgrading back to MM and upgrading back to Nougat, because of custom roms i guess?
i am not a stock'ish guy.
but i know there are many who just want the phone as it is, no mods etc.
I have a S8 Exynos version running stock Oreo - No root.
Yesterday I enabled FaceRecognition, just for trying it out, along with Gravityscreen since I wanted an unlocked phone the moment I picked it up. However, It didnt work as expected. I think there is some issue with Gravity screen turning off the screen and back ON.
anyway, the thing is, at one point my phone got stuck beyond redemption. I'm attaching a video, in 7z file, of what was happenning. I couldn't operate the phone at all - couldn't turn it OFF either. I let the battery drain and even upon restart, the problem didnt go away!! Not sure suddenly what triggered the problem! and what the solution is! I should've tried booting to Recovery. But have given the phone to the service center.
Anyone face this?
Try pressing the power off key and volume up for 3 seconds and see if it works bro.
I applied the 4core fix for my N6P back in September of last year, and stopped using it around December because of the battery life. Around July/August I purchased a battery and installed it and things were going well. Now my phone is freezing and booting to the Google Logo and... Crash again. No Nexus animation; Google, crash. Sometimes it will attempt to boot and bootloop and sometimes it turns on and works fine. Sometimes if it turns back on it freezes and boom. Google logo.
I guess the remaining 4 cores in this phone are done completely from the looks of it? I know the patch wasn't meant to be permanen, only temporary because the remaining 4cores would eventually die.
snappycg1996 said:
I applied the 4core fix for my N6P back in September of last year, and stopped using it around December because of the battery life. Around July/August I purchased a battery and installed it and things were going well. Now my phone is freezing and booting to the Google Logo and... Crash again. No Nexus animation; Google, crash. Sometimes it will attempt to boot and bootloop and sometimes it turns on and works fine. Sometimes if it turns back on it freezes and boom. Google logo.
I guess the remaining 4 cores in this phone are done completely from the looks of it? I know the patch wasn't meant to be permanen, only temporary because the remaining 4cores would eventually die.
Click to expand...
Click to collapse
My 6p also started bootlooping again today and this time fix didn't help me. I think it's gone for good.
maxguncel said:
My 6p also started bootlooping again today and this time fix didn't help me. I think it's gone for good.
Click to expand...
Click to collapse
Is yours booting to the Google logo and crashing? Or simply bootlooping? Mine goes to the logo, crashes about 10-15 times and then eventually attempts to boot.
It's a shame, got a baby on the way and simply can't afford another phone right now
snappycg1996 said:
Is yours booting to the Google logo and crashing? Or simply bootlooping? Mine goes to the logo, crashes about 10-15 times and then eventually attempts to boot.
It's a shame, got a baby on the way and simply can't afford another phone right now
Click to expand...
Click to collapse
Displays Google logo about 20-30 sec and restarts. Before I could see the animation but this time no luck.
Congratulations! I also have a newborn, we'll see what the future holds
maxguncel said:
Displays Google logo about 20-30 sec and restarts. Before I could see the animation but this time no luck.
Congratulations! I also have a newborn, we'll see what the future holds
Click to expand...
Click to collapse
Thank you You too! Day of Thanksgiving he is supposed to get here, but my wife isn't doing too well lol do you know of any way for us to pull data? Adb is failing to see my device when it's in the bootloader, fastboot is working though. I tried once more to flash twrp 4 core and boot it with no luck. Those small cores gave out I guess. I left my phone on overnight bootlooping with no luck. I got most things off, just my actual camera fder I couldn't get and apps which aren't a huge deal.
Sadly this morning I had the same problem. Bootlooping, I even cannot enter into Recovery. Then, suddently, it restarted, but I wasn't home, so I hadn't the chance to save the data. Then, about 3 hours later, it restarted bootlooping and, since then, it's stucked into this bootloop. Even reflashing the modified boot won't work.
Anybody knows how to at least recover the data inside? Even if I have to break the phone (I'm going to buy onther one soon)
hey guys, me too. but you know something? my initial assessment was that it was a result of an update. Now looking here annd seeing so many others with the same problem at the SAME TIME?? mine happened out of the blue on about October 4th or 5th. Ive had this phone for two years and never had aproblem with it at all. right out of the blue (in the morning) i get the bootloop. I cleared the cache and it booted up again. it was just fine for two days and now it is down black and out. When i push the power button i get a red light. one blink. if i hold down pwr and vol i get 8 blinks. tried on stock charger and other charger. like was previously mentioned when i tried it on a different charger it worked. the first time. now its dead. any solutions?
Marxmellow said:
hey guys, me too. but you know something? my initial assessment was that it was a result of an update. Now looking here annd seeing so many others with the same problem at the SAME TIME?? mine happened out of the blue on about October 4th or 5th. Ive had this phone for two years and never had aproblem with it at all. right out of the blue (in the morning) i get the bootloop. I cleared the cache and it booted up again. it was just fine for two days and now it is down black and out. When i push the power button i get a red light. one blink. if i hold down pwr and vol i get 8 blinks. tried on stock charger and other charger. like was previously mentioned when i tried it on a different charger it worked. the first time. now its dead. any solutions?
Click to expand...
Click to collapse
It simply means that the battery is fully discharged. Keep it connected to the current and maybe it restarts working.
I'm in the same situation since yesterday, hoping that at some point it returns working for some time, just to backup some data. I have like 10GB of photos not backupped in it.
When I replaced my battery I reinstalled factory. Start from scratch.
I had the same issue and that's all I did. Booted fine after that. I used the ifixit battery tho, cause if you got a lower cost one it could be the battery itself too
This is a Nexus 6P (32GB) I rooted shortly after getting it (new) in September 2016, and updated to stock 7.1.2 in August 2017, but I otherwise haven't modified it from its out-of-the-box state.
Until recently, I'd never experienced any issues - no random reboots, battery was still pretty good, etc. Then last week, the phone rebooted suddenly, and appeared to "boot loop". I hadn't yet heard about the issues the 6P has with this so I powered it down, left it alone for a while, then turned it back on later, booted without incident, and forgot about it.
Last night it happened again, at which point I searched and learned of the dreaded "boot loop of death" the 6P specifically has had issues with. Hoping that wasn't the issue, I again powered down and tried it this morning, and it only stayed awake for about 5 minutes before going into boot loop. At this point I looked up and applied the fix described in this thread, but to my dismay it had no (visible) effect - I still see the initial "bootloader is unlocked" screen, then the google + open lock icon, repeat ad nauseum.
About all I can do with the phone right now is load into fastboot. The phone has data on it I'd really like to recover, is there a way I can do that from there? If not, is there any way to connect with ADB without getting through a full boot? Are there alternative boot loop fixes, alternative steps to the fix described? I've read several threads here and can't tell if any apply to me, and can't find any answers to the above.
I've accepted that the phone is probably never going to be the same again but I need to get my data off there and do a few quick things before I consign this one to paperweight duty. Thanks in advance
chmmr said:
This is a Nexus 6P (32GB) I rooted shortly after getting it (new) in September 2016, and updated to stock 7.1.2 in August 2017, but I otherwise haven't modified it from its out-of-the-box state.
Until recently, I'd never experienced any issues - no random reboots, battery was still pretty good, etc. Then last week, the phone rebooted suddenly, and appeared to "boot loop". I hadn't yet heard about the issues the 6P has with this so I powered it down, left it alone for a while, then turned it back on later, booted without incident, and forgot about it.
Last night it happened again, at which point I searched and learned of the dreaded "boot loop of death" the 6P specifically has had issues with. Hoping that wasn't the issue, I again powered down and tried it this morning, and it only stayed awake for about 5 minutes before going into boot loop. At this point I looked up and applied the fix described in this thread, but to my dismay it had no (visible) effect - I still see the initial "bootloader is unlocked" screen, then the google + open lock icon, repeat ad nauseum.
About all I can do with the phone right now is load into fastboot. The phone has data on it I'd really like to recover, is there a way I can do that from there? If not, is there any way to connect with ADB without getting through a full boot? Are there alternative boot loop fixes, alternative steps to the fix described? I've read several threads here and can't tell if any apply to me, and can't find any answers to the above.
I've accepted that the phone is probably never going to be the same again but I need to get my data off there and do a few quick things before I consign this one to paperweight duty. Thanks in advance
Click to expand...
Click to collapse
I have the exact same issue. I run the same version operating system as you have an unlocked bootloader otherwise have not modified the typical system install. I did already have the fix applied from an earlier incident but now it is boot looping and won't stop. I have red threads here and there that have advised to apply heat to the phone and that might get it to boot at least to get your data off. Myself I have had no such luck with this technique but perhaps it will work for you otherwise I have since moved on to the OnePlus 6t. A very awesome replacement not to mention at a decent price for more horsepower and storage
Sent from my ONEPLUS A6013 using Tapatalk
Just in case it helps anyone with this phone and issue, I was able to get a couple more boots out of it, enough to rescue some data, by doing the "15 minutes in the freezer in a ziploc bag" trick.
RIP Nexus 6P, shame about the BLOD!