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.
Related
Explanation:
Tuesday afternoon I was getting out of my car and dropped my phone like I have done hundreds of times but this time my N4 with the official bumper fell face-up into a small stream of running water on the side of the street. I quickly picked it up and wiped it off and tested it and everything seemed ok but I turned it off to be safe. I came home about an hour later and put it in a container of rice and let it dry overnight with a fan blowing over it. I booted it the next morning and everything was working as it was the day before.
At this point I was stock everything, no root and never been rooted.
Fast forward 2 days laters my device has been plagued with random restarts and/or turning off. At this point I had not installed any new apps or changed any settings so I'm pretty confident it was some rogue app causing this trouble. So I had planned on doing a factory reset but 4.4 was out so I decided if I was going to set everything up again I might as well try the update. I decided to try http://forum.xda-developers.com/showthread.php?t=2507021 and everything worked fine. I cleared the cache and everything, a fresh start. I had no errors trying to install CWM or the ROM and KitKat worked on my phone just beautifully but then it started rebooting/turning off again.
So I went back to stock. Erased the whole device and flashed the radio, bootloader and 4.3 hoping/thinking it was 4.4 causing the trouble but still the same thing. I don't know what else to do so I have come to you XDA!
Weird behavior I have noticed
phone will boot when charger is plugged in
sometimes can't turn on phone without the phone charging - fastboot or normal boot
When I say turn off I mean like the battery has been pulled out of it
Reboots are completely random, sometimes vary from a few minutes to couple of hours of booting up. It happens when the phone is idle and it happens when I'm using the device in more apps that I can remember.
Scenarios & Outcomes
Full boot in 4.3 - Turns off eventually
Full boot in 4.4 - Turns off eventually
Safe mode boot in 4.3 or 4.3 - Turns off eventually
boot into fastboot - Restart the first time then it works as expected
boot into stock recovery - Restarts
boot into cwm recovery 6.0.4.3 - Restarts
Turn on phone - Reboots after google logo shows and boots normally only to turn off eventually by itself
Overclocked too high? Rice blocking cooling, maybe blow compressed through it? Good luck!
Sent from my MZ601 using XDA Premium HD app
I'm not exactly sure what happened, but when I first rooted, installed safestrap, and then Jelly Beans 106 on my Note 3, my phone would start up fine but then restart constantly. I would get my home screen, then immediately get notifications that various apps had crashed, and then the phone would reboot, but not fully though, it wouldn't go directly to the Jelly Beans boot animation, not through the full boot from the beginning with the samsung logo. From start up to reboot varies, but usually whatever app i was using would crash within a minute, and my phone would crash/lockup/reboot maybe 30 seconds to a minute later. It did not matter what app i as using or what I was doing. Actually I just noticed it somehow lost all my email settings, none of the accounts are there anymore.
If I booted into the stock rom from safe strap it seemed stable, but never with Jelly Bean. I had tried clearing the caches, wiping the phone, and a bunch of other fixes and nothing worked. In a last ditch effort I tried the process again, from the very beginning, I retooted my phone, reinstalled everything, and it worked, until three days ago when it started rebooting again. I had about three months of my phone being perfect, and then it just started rebooting randomly on it's own. The only thing that I can think that I did was decline some usage rights for the my magazine samsung app, that was the last thing I did before my phone went crazy.
I can't even get the stock rom to be stable anymore, it will do the same thing, whats' going on? I don't get why my phone was so stable, and then it went all haywire again. anybody have any idea of what I can do?
Completely stock, not rooted or bootloaded.
After my KK OTA came in I wanted to try ART for a while. Enabled it and then went through the reboot. On the Android is Upgrading screen it would get to a certain app being optimized and then freeze. I'd reboot and it would cut down the number of apps that are getting optimized until it got to just 1 of 1.
Now it just stops there and freezes after 15 seconds or so of being optimized. It won't go past that, I've spent the entire day today giving it time to sit and then try again or just let it fester frozen for anywhere from a few minutes to a few hours.
Question is, what do I do in order to reset my device in a way to past it.
Well, I have no idea how it fixed itself, I went to do a hard reset, couldn't get it go into the documented recovery mode, and then it worked.
Frustration.
tl;dr at the bottom
Alright so I'm out of ideas on how to fix this phone, couple of days ago my mom came to me complaining that her S5 was giving her trouble. When she handed me the phone, it was in a bootloop of showing the Samsung Galaxy S5 screen, playing the theme and vibrating afterwards then rebooting. I took out the battery and tried to power it on, it ended up successfully booting into android. So from here, I figured there must have been some malware on the device, I downloaded Malwarebytes from the Google Play Store and ran a scan on the device. However in the middle of scanning, the device turned off it's screen and rebooted. (Malwarebytes found 2 malware on the device at that point) So now I'm convinced it's most likely malware and eventually removed all the detected malware on the device. I gave it back to my mom thinking it was fixed.
Moments later she came back saying that it's still giving issues, my first thought "wdf, it was working wasn't it?". I looked at the phone again, and tried to wake up the device using the power button. The 2 soft keys at the bottom lit up however the screen was still black. At this point, the phone was still working fine, the only issue was the screen wouldn't wake up. So I decided to do a battery pull once again to reboot it and it results in the bootloop once again. I did some googling and found various solutions to this, one of them involved wiping the cache from recovery, so it tried it. Booted into recovery and wiped the partition cache (i think that was it), after it wiped and was about to reboot, I noticed a brief "error icon" just before it rebooted. After this point I could not boot into recovery at all (it would just show a black screen and I would assume that the phone turned off) and it was still in a bootloop. It was only after trying to turn on the phone after trying to boot into recovery that the idea of the phone wasn't off and the screen was just black entered my mind. (Because usually if the phone is off, you can turn it on by holding the power button, the phone would not turn on until after a battery pull)
So at this point, it was late at night and I was tired. I left the battery out and just went to bed. The next day I tried to turn it on again and to my surprise it booted up fine but I was skeptical. I had a theory that the device would work fine as long as the screen remained on, so I set the screen timeout to 10 minutes and kept it on for probably 30 minutes while I continued to google. Since it stayed working during that period of time, I thought perhaps locking the device triggers the issue. I turned of "Power Button instantly locks device" and proceeded to turn off the screen using the power button. When I tried to turn it on, it was back to the same problem (black screen, device is working fine, soft keys lit up). I did a battery pull once again in an attempt to reboot and now it was back to problem #2 (boot loop, can't enter recovery). At this point in time, I considered doing a factory reset but since I couldn't enter recovery, I'd most likely have to re-flash the stock firmware.
Since I didn't have much experience flashing android devices (I personally only flashed 2 or 3 devices ever, all of them were successful but I still didn't really trust myself), I had it sent to a local cellphone company and had them try to fix it. Eventually I got the device back, but they were unable to fix the problem (they tried to flash a stock and custom rom). Now I'm back to square 1, the phone is still in a bootloop, no sound, no vibration this time, I don't have much experience with phones since I've only owned 2 in my life. The phone seems to be soft bricked pretty good, I've still got 1 more trick to try (full stock firmware flash) before I call it quits, any ideas?
tl;dr
- device is stuck in a bootloop (issue 1)
- i was able to enter recovery mode once, now it's not accessible
- download mode is accessible
- the device has been able to boot successfully a couple times, but then it has another issue.
- device's screen would not wake up after turning off, softkeys still worked, everything else still worked. (issue 2)
- the device was sent to a local phone repair company to fix (unsuccessful)
- currently device is stuck on issue 1
additional notes
- device has not been dropped or wet
- device has been owned for more than a year without problems
- this problem was recent (3 days)
- no sd card
- dark screen was turned off
theories
- screen could be malfunctioning or defective somehow, but then if it can show the bootscreen and download mode screen fine it seems unlikely also since it's been working fine for over a year
- it's a software issue of some sort, but has already been flashed by local phone repair to no success, then again I'm assuming they just did a basic recovery flash and called it quits
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