So I tried to flash a rom today. Well, I tried to update it. I know I shouldn't have, but I aborted the process because it got hung up on the same thing for 10 minutes. Surprise, everything's screwed up. But don't worry, I fixed it. I literally re-constructed the system image through adb (the system folder was just deleted for some reason) and got the phone to boot again. But then the network wasn't working anymore, so I flashed the rom again and nope still not working. So then I flashed it AGAIN and my phone was low on battery and I was in class and it flashed fine, but then it shut off during boot. And now it's constantly turning on and booting over and over, and the battery is super low, and I can't access recovery. Or the bootloader. No combinations work, nothing. So here I am, completely at my own fault and stupidity. Ideas?
Here's the symptoms:
I plugged it in after class, 0% charge. Oops. Not supposed to do that.
Waited. Waited. Got to bootloader, tried to enter recovery. Not enough battery, waited.
Got to recovery, tried to boot normally, and now it gets the the "powered by android" screen for a couple of seconds, shuts down, and restarts the process.
My theory:
The phone is so low on battery it can't continue booting, so it shuts off. It uses what little battery it has to put the screen brightness on full and boot, repeat.
PDATE:
It's been a good hour or so, and the phone still shows 0% charge and wont boot. It's really hot.
Hey guys,
I've got a M7 that is stuck bootlooping. It's fully stock, absolutely untouched and of course out of guarantee time
The phone started the behavior after running out of battery.
The phone does start automatically when connected to power source and shows the htc logo and then vibrates and the cycle begins. The touch buttons do not light up.
I can get into boot menu, though I'm unable to select any of the options as the phone quickly reboots again. The led is neither alight nor blinking when connected to power.
The phone doesn't show reaction to any button/light combination when not connected to power. I've tried the following combinations:
power+up 2min
power+down 2min
power+up+down+light 15sec
So anything else i can try?
Hi!,
Today I was using my Moto g 2014 LTE XT1072 and suddenly it crashed and it got stuck in a bootloop. Im running cyanpop 6.0.1 and TWRP as recovery. Now I get the unlocked bootloader warning, the fibration and than it goes black. Sometimes it get to see a small portion of the cyanpop boot animation, but it stil goes black after that. I can't get into recovery. If I hold the power and volume down button the bootloop stops for 20 secs. After that it begins again. My PC does not spot the phone when I plug it in with Motorola Device Manager installed.
I really do not know what to do anymore. Do I have to buy a new phone? Please save me from the suffering. If you need any more information please ask.
EDIT: Good news everyone! After the battery drained and leaving it alone for 24 houres the phone booted normally. Thanks guys for the help!
have you tried to enter in fastboot mode?
Zagomah said:
have you tried to enter in fastboot mode?
Click to expand...
Click to collapse
Well I can't get into it from recovery, because I can't get excase it. My Pc did start seeing it when its in 'charge mode' (not sure what the real name is), but when I type 'adb devices' in minimal ADB and Fastboot it just says 'list of devices attached'. And when I try 'fastboot devices' it does nothing. Not sure what to know.
Captain_Bacon said:
If I hold the power and volume down button the bootloop stops for 20 secs.
Click to expand...
Click to collapse
While powered off and no cables connected
hold power + vol-down 3/4 seconds (screen stay black) then release the power and keep vol-down pushed (bootloader screen is visible now) release vol-down, .
Not working ? are you sure ?
dr.nic said:
While powered off and no cables connected
hold power + vol-down 3/4 seconds (screen stay black) then release the power and keep vol-down pushed (bootloader screen is visible now) release vol-down, .
Not working ? are you sure ?
Click to expand...
Click to collapse
Will try this at home!
Nope, still the same thing. The loop stops for 20 secs and just continues after
Captain_Bacon said:
Hi!,
Today I was using my Moto g 2014 LTE XT1072 and suddenly it crashed and it got stuck in a bootloop. Im running cyanpop 6.0.1 and TWRP as recovery. Now I get the unlocked bootloader warning, the fibration and than it goes black. Sometimes it get to see a small portion of the cyanpop boot animation, but it stil goes black after that. I can't get into recovery. If I hold the power and volume down button the bootloop stops for 20 secs. After that it begins again. My PC does not spot the phone when I plug it in with Motorola Device Manager installed.
I really do not know what to do anymore. Do I have to buy a new phone? Please save me from the suffering. If you need any more information please ask.
EDIT: Good news everyone! After the battery drained and leaving it alone for 24 houres the phone booted normally. Thanks guys for the help!
Click to expand...
Click to collapse
Nice to know. Moto G family phones tend to suffer from battery-motherboard problems, usually related to current issues. Is your charger at least 1.0A? My Thea's battery drained at school, I tried to connect it to a generic charger and the phone misbehaved and became trapped in a 0% screen loop, and did not appear to grab some charge. I thought to myself "Oh no! My expensive phone is now ruined forever and my warranty is void! What I'm gonna do?" But I walked home, connected it to my old reliable Samsung charger to see what happens and voila! The phone started charging and I could turn it on again.
benjausen said:
Nice to know. Moto G family phones tend to suffer from battery-motherboard problems, usually related to current issues. Is your charger at least 1.0A? My Thea's battery drained at school, I tried to connect it to a generic charger and the phone misbehaved and became trapped in a 0% screen loop, and did not appear to grab some charge. I thought to myself "Oh no! My expensive phone is now ruined forever and my warranty is void! What I'm gonna do?" But I walked home, connected it to my old reliable Samsung charger to see what happens and voila! The phone started charging and I could turn it on again.
Click to expand...
Click to collapse
I used my Nvidia Shield Tablet charger, which is pretty beafy. I experienced somewhat the same thing. Did yours keep trying to boot aswhile?
Captain_Bacon said:
I used my Nvidia Shield Tablet charger, which is pretty beafy. I experienced somewhat the same thing. Did yours keep trying to boot aswhile?
Click to expand...
Click to collapse
Kind of. The phone would not respond nor turn it's LED on. When connected into any charger the phone screen would turn on in the 0% battery screen. If I touched anything, the phone turned off and the 0% screen appeared again. Also sometimes it would just appear again like crazy, like if I killed the bootloader or something alike. After connecting to the Samsung charger, the 0% screen appeared again and the screen turned off. I didn't touch anything out of fear. After three minutes, the Bootloader Unlocked message appeared and finally the phone booted to TWRP's charging screen. I let it charge to 4% and tried to start the phone. The phone booted into CM12.1 and problem solved. I hope these issues never happen to us again. It would mean motherboard degeneration/wearing out/side effect from bootloader unlock and flashing or something alike. Thanks for the answer.
benjausen said:
Kind of. The phone would not respond nor turn it's LED on. When connected into any charger the phone screen would turn on in the 0% battery screen. If I touched anything, the phone turned off and the 0% screen appeared again. Also sometimes it would just appear again like crazy, like if I killed the bootloader or something alike. After connecting to the Samsung charger, the 0% screen appeared again and the screen turned off. I didn't touch anything out of fear. After three minutes, the Bootloader Unlocked message appeared and finally the phone booted to TWRP's charging screen. I let it charge to 4% and tried to start the phone. The phone booted into CM12.1 and problem solved. I hope these issues never happen to us again. It would mean motherboard degeneration/wearing out/side effect from bootloader unlock and flashing or something alike. Thanks for the answer.
Click to expand...
Click to collapse
No probs my friend and I wish you the same. Let the moto gods protect us.
Hello fine people at XDA! I've been a lurker for some time and did some great things with this site!
I have a friend at work that has the Moto G xt1068. She has no clue about rooting or anything of the sort. Since last night she's having this problem. She was trying to take a picture, the camera wouldnt take the picture (although the rest of the functions of the phone were working properly). She tried turning off the phone and it never turned back on! The Motorola logo shows up but the phone immediately turns off. If it's plugged in, it shows that the battery has 0% charge, then the Motorola logo and then it starts looping on that every few seconds/minutes (not sure on this one). I entered fast boot (VOL DOWN + PWR) and with any of the options to boot the phone (Factory, Recovery, Normal boot, etc) it does the same, none of them boot. I was thinking maybe a battery problem but since the fast boot screen works fine with the phone unplugged I have my doubts. Is there any solution for this rather than taking the phone to tech and not having it for a couple of days?
Thanks and regards!
Hello!
I have a XT1097 (that has some battery issues - shutting down at 15%). When I started it while charging it would sometimes enter in bootloop.
Recently I was using it (the battery was low, almost 15%) when it shut down. It entered in bootloop and I couldn't access recovery mode. After the TWRP logo screen it restarts.
After some attempts and after full charges and discharges, I was able to access the TWRP menu. Everything works fine from there.
Yesterday this happened again. I tried a full charge and discharge but nothing happens: still bootloop and I couldn't acccess the TWRP menu.
Have you ever seen anything like that? I wonder if there's any other form of accessing the TWRP menu (via PC or something).
I'm using Lineage OS rom and I didn't notice anything different or strange before this happened.
I've had this happen for over a year now. It's not every time my phone dies, maybe 1 in 100. I've learned how to extract my texts messages then factory reset and start over.
Are you saying if you get to twrp, and click restart from there it'll start properly?!?
You can get out of the bootloop and into bootloader by pressing vol down and power for 20 seconds ish. Sometimes you need to do it multiple times.