For the past couple of days, my device has been shutting down by itself and it often doesn't boot when unplugged (if it does, it is stuck in M screen bootloop). When I do plug it in, following things tend to happen:
- Stuck in bootloop with M logo screen
- Boots till "unlocked bootloader warning" screen pops up and then reboots again
- When I get in bootloader screen, I can't get past it. Can't even access recovery mode sometimes and if I do the device randomly shuts down
This feels quite random as it happens about 7 out of 10 times when I'm trying to reboot, eventually it ends up in the bootloop regardless of what I try.
My older rom was Lineage OS 14 that I flashed with TWRP. Today, somehow I managed to get into recovery mode for quite some time so I wiped the data and clean flashed superSU. The phone worked alright until I started setting up my device with accounts and all that stuff, it shut itself down again.
I had been using the rooted phone with Lineage OS for over 8 months and it was working just fine, no issues at all. The only new app that I installed recently was Blokada and the next day this started to happen. I don't really suspect Blokada, but still I don't know what is happening. It is hard to do anything because I can't access device storage on my PC when I'm just in the bootloader screen.
Can anyone please help me out with this? I will REALLY appreciate it if someone can help me solve this. Thank you in advance!
Could it be a fault with the Battery or it's internal connections?
I've got similar problems. It's the battery, read your charge amount.
Today my cell fell and shut off, then reboot with M logo. Then 6% of battery, after a couple of hours I beat the phone, turn it on, an then 81% (a more realistic percentaje)
---------- Post added at 08:31 PM ---------- Previous post was at 08:30 PM ----------
I've got similar problems. It's the battery, read your charge amount.
Today my cell fell and shut off, then reboot with M logo. Then 6% of battery, after a couple of hours I beat the phone, turn it on, an then 81% (a more realistic percentaje)
Related
I really don't know if this is possible or not.... but I might need to get some new corduroys after a case of the brown adrenalin with my new sensation.
Got it Friday as could see progress on the rooting and sure enough Revolution came up with the goods same day. Rooted it Saturday.
Fully charged it, switched it off and went back to the HD2 - flip case and car kit arriving today. Really don't wanna damage my new boy toy by pocketing it with car keys etc.
Stone me though I thought I bricked it. Wouldn't switch on this morning - just a dark flicker of the screen. Sweat pouring off my forehead. Never bricked a device and flashed my HD2 & TP2 a million times and my £450 unlocked handset is 3 days old and dead..
Long and the short of it is plugged in the charger again and a few minutes later it powers up - 3% battery.
Is it possible it could drain switched off? Or should I blame the kids for messing with it and deduct my dry cleaning bill from their pocket-money?
After I rooted, I had to do a battery pull until I was able to turn my phone on again, although this doesn't really replicate what problem you had...
The battery does not drain if the phone is turned off.
Question is, was it definitely turned off?
Even if it wasn't, there's no way a full charge is going to drain overnight... Unless you had a Satnav running...
Sent from my HTC Sensation Z710e using XDA Premium App
You're right - it SHOULDN'T... I'd rebooted no problems several times after the rooting. Some OTA update came over and didn't install successfully though.
It'd be very odd (and a warranty issue, get ready to go into rooting reverse) but for now I'm inclined to just blame the kids. Unless anyone else has has similar experiences.
I guess time with it will tell.
EDIT: Apparently it's a known issue and has been fixed with the new CWM update! See: http://forum.xda-developers.com/showthread.php?t=1192300
Ah ha, looks like it's not just me!
This just happened to me today and I had to change my pants because I thought I bricked it. I rooted it and installed InsertCoin no problems!
Today, as it jumped off my WiFi and onto the mobile network it got stuck on "Disconnecting from Morsolo's WiFi" and just sorta froze there (the phone still worked, but it wouldn't fully disconnect from WiFi, so I got no mobile data).
I turned the phone off via normal methods (40% Battery)... Then it wouldn't turn back on. The phone was a little bit hot at this point, but it does heat up so I thought nothing of it.
For a good 30 minutes, nothing happened. All that I could see happening when I attempted to turn the phone on was, the screen backlight would turn on, fade off, turn on, fade off. No boot, no recovery, nothing.
I tried charging it and it would show the indicator for 2 seconds and stop charging (but this is a known issue, apparently it continues to charge regardless).
After numerous times pulling the battery, trying to start, charging, battery, start... I finally managed to get it to boot and it said the battery was at 3%... After the phone was STONE COLD DEAD for a good 30 minutes to 1 hour.
...I just got home (with a dead battery, of course) and now that I've plugged it in again, it wont boot, again.
I think we've discovered an issue.
EDIT: Good man. Thanks for the update. Better get onto that right away.
Yup.. that's the same experience... except I'm still on stock rom with tweaks.
What do you reckon - flash back to stock and see if it still happens? Really don't want it turning into permanent paperweight with an iffy bootloader for someone at warranty to find with their JTAG.
Morsolo said:
Ah ha, looks like it's not just me!
This just happened to me today and I had to change my pants because I thought I bricked it. I rooted it and installed InsertCoin no problems!
Today, as it jumped off my WiFi and onto the mobile network it got stuck on "Disconnecting from Morsolo's WiFi" and just sorta froze there (the phone still worked, but it wouldn't fully disconnect from WiFi, so I got no mobile data).
I turned the phone off via normal methods (40% Battery)... Then it wouldn't turn back on. The phone was a little bit hot at this point, but it does heat up so I thought nothing of it.
For a good 30 minutes, nothing happened. All that I could see happening when I attempted to turn the phone on was, the screen backlight would turn on, fade off, turn on, fade off. No boot, no recovery, nothing.
I tried charging it and it would show the indicator for 2 seconds and stop charging (but this is a known issue, apparently it continues to charge regardless).
After numerous times pulling the battery, trying to start, charging, battery, start... I finally managed to get it to boot and it said the battery was at 3%... After the phone was STONE COLD DEAD for a good 30 minutes to 1 hour.
...I just got home (with a dead battery, of course) and now that I've plugged it in again, it wont boot, again.
I think we've discovered an issue.
Click to expand...
Click to collapse
Hello guys.
About an hour ago, I tried to access my WiFi configs, and realized it would take me back to the start screen. So I rebooted my phone. The thing is, it is now stuck in the big red Motorola/Intel logo, and keeps looping.
If I try to turn it off by using the Power button, it doesn't work. If I try to reset using Power + Vol Down, it just restarts the loop. I can't get into recovery mode, because it won't turn off.
I really don't know what to do. My phone is still trying to boot for the past hour, and I really need it, asap.
It is running Android 4.1.2. No root. As stock as it gets.
Any advice, guys? Please
alovose said:
Hello guys.
About an hour ago, I tried to access my WiFi configs, and realized it would take me back to the start screen. So I rebooted my phone. The thing is, it is now stuck in the big red Motorola/Intel logo, and keeps looping.
If I try to turn it off by using the Power button, it doesn't work. If I try to reset using Power + Vol Down, it just restarts the loop. I can't get into recovery mode, because it won't turn off.
I really don't know what to do. My phone is still trying to boot for the past hour, and I really need it, asap.
It is running Android 4.1.2. No root. As stock as it gets.
Any advice, guys? Please
Click to expand...
Click to collapse
I have the exact same problem.
My phone (non rooted, stock Android) has been freezing quite a lot for the past 1 or 2 weeks. Sometimes rebooting on its own, sometimes I had to force it. This afternoon it froze again and I had to force reboot, where it started freezing at the Motorola logo. I cant go any further since rebooting just makes it loop that way.
I waited for the battery to deplete so my phone eventually turned off, charged it back at around 60% and tried to go into recovery mode with power+volume up+volume down. Same results. I don't think I could have failed the recovery mode procedure because I had practiced and knew I would only get 1 chance of succeeding.
Anyone has experience with this ?
I will see if Motorola or my retailer will repair/replace it for free under warranty terms, otherwise I will try opening it up for some cleaning and maybe further attempts with control over the battery.
SuperS06 said:
I have the exact same problem.
My phone (non rooted, stock Android) has been freezing quite a lot for the past 1 or 2 weeks. Sometimes rebooting on its own, sometimes I had to force it. This afternoon it froze again and I had to force reboot, where it started freezing at the Motorola logo. I cant go any further since rebooting just makes it loop that way.
I waited for the battery to deplete so my phone eventually turned off, charged it back at around 60% and tried to go into recovery mode with power+volume up+volume down. Same results. I don't think I could have failed the recovery mode procedure because I had practiced and knew I would only get 1 chance of succeeding.
Anyone has experience with this ?
I will see if Motorola or my retailer will repair/replace it for free under warranty terms, otherwise I will try opening it up for some cleaning and maybe further attempts with control over the battery.
Click to expand...
Click to collapse
Well, Motorola did repair my phone for free, but I live in Brazil. It took them 1 day to repair. They say that part of the circuit board was damaged, but I don't know what could be the cause. Maybe overheat? I don't know about your phone, but mine would get up to 50ºC while using Skype.
Hello Folks,
I have been using cataclysm rom, april's stable release on my nexus 5 for past 2 months and it was a perfect companion.
Since yesterday though it has started to reboot, and only the google logo comes up and it again reboot's.
When I unplug the charger though the phone stops rebooting and is as good as dead. When I plugin, the reboot loop continues.
Currently I am unable to use my phone, and any help would be great.
My doubt is if the battery has gone very weak, and is unable to support the boot process, but even though I keep it charged for a significant amount of time, the same isssue happens.
Any help would be greatly appreciated.
Cheers
Sree Harsha
nanoharsha said:
Hello Folks,
I have been using cataclysm rom, april's stable release on my nexus 5 for past 2 months and it was a perfect companion.
Since yesterday though it has started to reboot, and only the google logo comes up and it again reboot's.
When I unplug the charger though the phone stops rebooting and is as good as dead. When I plugin, the reboot loop continues.
Currently I am unable to use my phone, and any help would be great.
My doubt is if the battery has gone very weak, and is unable to support the boot process, but even though I keep it charged for a significant amount of time, the same isssue happens.
Any help would be greatly appreciated.
Cheers
Sree Harsha
Click to expand...
Click to collapse
Hi,
It seems to be a power button issue. It being pressed permanently is causing the issue. Rammed the phone a lil softly on a surface on the side of power button and the phone was back to life. Need to get the issue fixed, need to see where and how.
If the phone is plugged in, it should be able to boot. Some time ago i had also a problem related to battery (so i thougth at the time). My phone was charging very slow and wasn't capable to boot if i had the phone turned on, so i had to turn off the phone and let it charge for about 30 minutes before it could boot. It turned out that was a problem with the USB connectors. So i cleaned the USB entry and everything was fine again.
Hi everyone, i know the title seems like it's just a trival matter, but trust me it's not.
The phone was bought new in August of last year (2015).
The story so far: I've been using sultanxda ROM for over 6 months without any issues, but i decided to test a different ROM, so i downloaded Darkobas rom and GAPPS, the ROM and Gapps installed fine but when i started the device and i was doing the initial configuration the phone rebooted by itself. It happened about 3/4 times and after that the phone had entered a bootloop. I tried to reflash the ROM and gapps, but the phone was restarting during the flash in TWRP. I decided to go stock Cyanogen OS, so i did a clean fastboot install of cyanogen OS. Everything went well the phone was working fine, but a few hours after installation the phone was randomly rebooting again, i decided i'll live with it and wait and see if it goes away by itself.
The phone was rebooting 2/3 times a day, during different acitivities so it was hard to pinpoint what might the issue be (even when locked in my pocket with all apps killed). After a few days of usage it just went straight to bootloop, after that i had issues to even install a rom (even via fastboot), because it would install everything fine and then it wouldn't start properly and would be in a bootloop (straight after installation).
I also tried the Bacon Root Toolkit installation as well as formatting everything and wiping everything. But even with the usage of Bacon Root Toolkit the random reboots happened.
So i installed an older TWRP recovery, i wiped everything re-formatted the phone to F2FS (was EXT 4 b4) and installed a F2FS compatible ROM (can't remember which one), after that installation everything seemed to work fine, but after a day or so the random reboots came back to haunt me again. So i reformatted the phone to EXT-4 again, installed stock cyanogenmod via fastboot (the 4.4.2 version), and updated it to 6.0.1 via OTA (during the course of a day or so, but even when the phone was on 4.4.2 i had a random reboot once), and the reboots returned ( i tried many different solutions, even the command line in TWRP "make_ext4fs /dev/block/mmcblk0p15"). I had NO IDEA what might be causing them but i thought that maybe the processor is ****ed and it's overheating, i returned to sultanxda rom (with the underclock to 1957 mHz).
After returning the phone booted correctly after a clean install via TWRP, but now it's rebooting again, and sometimes it happens 4/5 times in a ROW, sometimes it doesnt even reboot, but goes to black screen and I have to push the power button for 6 + seconds for it to reboot.
I've tried the stability test, or running antutu a few times in a row to verify if maybe it's the processor's/RAM's fault, but the phone didn't care, it rebooted randomly (sometimes 6/7 antutu runs in a row and nothing happened, sometimes rebooting in my pocket with all apps shut down). I've tried different launchers/messing with WiFi options/turning off the proximity check/turning off the trust agents nothing seems to make a difference. At this point I'm at a loss of what to do so i came here to ask for any advice. Is there any way to check if the phones internal memory is corrupted in some way ? I've tried searching for some apps but nothing turned out.
oski131 said:
Hi everyone, i know the title seems like it's just a trival matter, but trust me it's not.
The phone was bought new in August of last year (2015).
Click to expand...
Click to collapse
flash this solved my problem http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Flashed the persist.img the problem still occurs. 15 minutes after the flash the phone shutdown, black screen.
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
iPusak Gaoq� said:
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
Click to expand...
Click to collapse
Shouldn't the battery meter go crazy after reboots or something ? Well i guess i'll try this, the battery is not a costly component. Are there perhaps any bigger batteries than the original one with bigger backs ?
oski131 said:
Shouldn't the battery meter go crazy after reboots or something ? Well i guess i'll try this, the battery is not a costly component. Are there perhaps any bigger batteries than the original one with bigger backs ?
Click to expand...
Click to collapse
Nope...the battery remains like normal but random reboot will happen more regularly until bootloop....
Not sure if there is a bigger battery but there is one thread here that show one battery with 3600mAh and don't buy OP2 battery as it is not compatible with OPO...
Sent from my A0001 using Tapatalk
Ok thanks for the help, will report back with new battery.
Switched the battery, the random reboots still happen, decided to do a clean flash, after wiping the phone in TWRP during the flash of GAPPS the phone rebooted itself and is in a boot loop currently.
Ok so the reboots stopped, it was a battery issue, but now i have a problem with battery indicator it's stuck at 50 % all the time and the phone does not show when it's charging (no information, no LED color), but the battery is being charged because when i shut it down and connect the charge and battery level (which shows when the phone is off) increases.
I've tried to use it untill it shuts down then i charged it while it was off for 6 hours, but after turning it on it still showed 50 %. I've also deleted the batterystats.bin using TWRP but it still did not help. Any ideas how to make it show the correct % ?
oski131 said:
Ok so the reboots stopped, it was a battery issue, but now i have a problem with battery indicator it's stuck at 50 % all the time and the phone does not show when it's charging (no information, no LED color), but the battery is being charged because when i shut it down and connect the charge and battery level (which shows when the phone is off) increases.
I've tried to use it untill it shuts down then i charged it while it was off for 6 hours, but after turning it on it still showed 50 %. I've also deleted the batterystats.bin using TWRP but it still did not help. Any ideas how to make it show the correct % ?
Click to expand...
Click to collapse
told you it was a battery issues but look like you have another battery issues here...try disconnect the battery from the motherboard for 1 minutes before connect it again and do offline charge for atleast 30 minutes....after 30 minutes reboot the phone and look at the battery percentages...if its goes above 50% then you have solved your problems....if it doesn't then you might bought a bad battery....you need to contact the seller that sell you the battery and asked for replacement....
Well unfortunately after changing the battery for a second one (the random reboots started again on the new one) the issue still prevails, so i'm currently writing a ticket to oneplus in hopes of some help.
Thank you iPusak Gaoq™
iPusak Gaoq™ said:
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
Click to expand...
Click to collapse
You Sir iPusak Gaoq™ are amazing. I 've searched for 2 whole weeks and no one was able to zero in on the issue.
After reading your post, I changed my battery. 3 days back. Till now my phone is as good as new.
I cannot thank you enough. I tried everything from recovery to rom to stock.
Thank you Thank you thank you.
What peace of mind now !!!!!!!
You can try this it solved my problem without changing battery :-
https://forum.xda-developers.com/k5-plus/how-to/solving-random-reboots-problem-t3682037
Hello. I have a stock Axon 10 Pro (US version) that ran low on battery today, shut off, and is now stuck in a boot loop. I see the ZTE logo and then it goes to black, restarts a few times more, and then seems to shut off.
I can pull the battery, reconnect it, and boot into ZTE Recovery. I have data on here that I would very much like to save that I haven't backed up in the last two weeks. I assume the data is still there, just having an issue with the OS booting. I'm not sure where to go from here.
Does anyone have any advice on next steps to take?
Does anyone have any suggestions? My phone, for some reason, booted as far as being able to see my phone background image, froze about 5 seconds later, and restarted again. I'm not sure what this is a sign of, but it gives me a little hope that I can somehow salvage this.