Hey guys, so this has happened the last two nights -- at exactly 2:02am my Droid X locks hard. Just did it again. I have no idea what is going on here but I have to pull the battery.
Last night it was on the charger (And the screen was on) so when I picked it up this morning it said 2:02 on the lock screen. Just now I was listening to music and dead stop -- screen was off but I looked at the clock on my computer and sure enough: 2:02.
Just set the clock manually to 2:01 and started a song -- let us see what happens in one minute.
*SIGH*
My phone has been working generally well..... but then I had a strange issue last night where the phone became super unresponsive accessing the SD, so I rebooted. Then the 2:02 lockup .. and then today the battery drained really quickly. A check of CPU spy and the phone never entered deep sleep. Battery manager showed the phone never going to sleep as the "awake" bar went across the whole screen even though Screen on was less than 1 hour total.
Manual clock set to 2:01 did not result in a freeze as I let it go to 2:03... I just set it to 1:59 to see if that makes a difference.
Stock latest GB, root, debloat done myself (fresh install and debloat a couple weeks ago) .... really at my wit's end with Motorola phones. I have a Droid X2 but find that phone generally unusable due to the extremely lackluster performance including the constant audio dropouts, even with the latest GB release.
Anyone else ever seen this 2:02 thing? Or have any idea where I can even begin to look to fix it? I don't see a crontab file on here. I haven't installed any new apps other than the usual updates that seem to happen every day.
....Manual clock is now at 2:04 (from 1:59) with no freeze. So I don't know WTF is happening. I had rebooted the phone around 8pm tonight .. actually had to pull the battery. Did a "reboot" from the Terminal Emulator and the phone went black and never started rebooting.
I'm so fed up with this damn phone!!
That's not happening to mines
Hard reset your phone n back up SMS, files, etc.
Try different battery!
Sent from my DROIDX
I have my phone for almost 2 months now.
Last week I updated to latest 4.4.2 available,
using the android popup asking me if I want to.
Everything was just fine, until 3 days ago.
Every day for the last 3 days I had one random restart per day.
Day 1...unlocking the lockscreen...
lockscreen was fine after several times pressing power button,
but unlocking the phone just made black screen instead of desktop screen,
notification bar worked fine on the top and sliding it down...
After minute or so phone restarted
Day 2...while opening messages
Black screen and restart after a minute.
Day 3
I turned the screen off and wanted to turn it back on and unlock it,
nothing happened after pressing the power button
I just toke the battery out and restarted the phone,
because I already knew that this would happen after waiting a minute anyway.
I did not install any new applications or change anything on the phone for the last 3 days
I have auto update disabled.
I participate in the Facebook android beta program,
but since the aplication was not updated for more than a week,
I doubt that it causes daily crashes, if it did not before.
I still have not found a solution yet.
Phone is rebooting once a day or once in a two days...
Nobody knows what could it be?
64GB OnePlus Two running OxygenOS.
Backstory of the last time this happened:
A while back, I was on Snapchat when all the sudden my phone just froze. Didn't think it was anything special since it does that not too infrequently, but then the screen went black. Again, wasn't too concerned because it has done that before as well.
It began to reboot as normal, but right when it got to the final stage of the boot animation it froze and rebooted. This time it stopped toward the beginning the the animation and rebooted. On the third boot attempt, it showed the "optimizing apps" message like the Dalvik cache had been wiped. Again, up to this point it was nothing new (I had crazy problems with the latest OxygenOS before I rolled back to 2.2.0) so I wasn't horribly concerned.
But at about 120/160 optimized, it froze on that screen and crashed. And that's where I am right now. No matter how long I hold down any combination of buttons, the screen will not come on and it fails to otherwise respond, with two exceptions.
I tried the hard brick recovery method, but no amount of holding volume up would get it to show up in device manager.
When I went to bed last night I decided to give it one last shot. Held down the power button for a sec, and it vibrated and then powered on. Went through the whole "optimizing apps" routine and started up just fine. It was reallllly sluggish and laggy for a few minutes but now seems to work fine. Only thing I can guess is leaving it plugged in for a few hours had some effect. Oddly enough, it was at 98% to start and was plugged in doing nothing (that I could tell) for a few hours, but only showed 86% when it booted.
Well, it happened again. When it happened the last time, I rolled back from OxygenOS 2.2.1 to 2.2.0 since that seemed to be the only change I had made recently. I'd left it stock till now, but I decided I wanted root and Xposed so I flashed TWRP 3.0.2, SuperSU 3.65, and Xposed. When it rebooted after this, it froze during boot and shut off. Now it won't do anything. Holding volume up won't make it show up in device manager on my computer for the hard brick recovery, and leaving it plugged in for ~20 hours didn't help either.
Please help! I'm an extremely busy engineering student and finals are just about a week away followed by flying home. I really need to fix this ASAP.
Okay, I remembered that my phone sometimes reboots when it's dropped/set down sharply, so I rapped it a few good ones on the desk. And it booted. I'm thinking there's a loose connection inside? Should I RMA it?
Guess I spoke too soon. Froze and crashed again while booting.
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.
So, here is my problem. I've got an almost four years old Note4. I flashed some custom ROM's after i bought it but then I found an old X-note 4.4.4 based custom ROM and i was using that for more than 2 years. Yesterday around noon i noticed that if I try to use Viber, it takes seconds till it opens, and lags badly. (Before that the phone was working perfectly for years). I deleted it, reinstalled, but the problem stayed the same. After a few hours all the other apps started to do the same, the phone became really laggy. As time went by it got worse and worse, around 8pm it started to freeze, reboot, became almost completely useless. I thought maybe a factory reset and a new flash would help. I did a factory reset, and flashed a completely stock ROM on it. It started well, was working good for an hour or so, and then the same problems occured again. Lag, freeze, reboot.... And then nothing. Did not even restart. I can switch it on every now and then, (like in every 20 minutes), but it boots into odin mode. I thought maybe the battery, but that is less then 2 months old. Anyone any idea what happened? I mean the phone is almost 4 years old, so I'm not really pissed off, the only reason why I wanna keep using the Note4 cuz it's removable battery. I don't like phones with built-in battery, this is why i did not upgrade to Note8 for instance. Any help would be much appreciated. By the way, my device is an SM-N910F.
Well, things got even weirder later. I found my old battery which i replaced 2 months ago, still had some juice in it, i put it in, and the phone started!!! Worked perfectly, for about an hour and a bit, then the same problems occured again, lag freeze reboot, and now it boots itself into recovery if i can start it up at all... All the same story. Anyway, i threw it in the drawer and bought a new phone.