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!
Related
Howdy,
So I flashed my phone to cm4.2 last weekend and everything has been quite dandy. But I now I have a problem, and I kind of doubt its from the cmod because that was a week ago and this problem happened yesterday...
Yesterday I was talking on the phone until the battery died. Then I rushed to my charger and plugged it in. I tried to turn it back on but it would not. It goes to the G1 screen then to the CM boot animation screen then the screen turns BLACK! IT will not stop doing this. I have to keep pulling out the battery. Last night I even pulled out the SIM and battery for a few minutes. Then put them back and tried again. Same result. I charged it fully last night (while off) thinking that might help. This morning after the LED light was green I tried again to reboot the phone.. Also sometimes the phone will do this reboot sequence after I plug the charger in, but it still goes to the blank/black screen... awww..
I am really hoping I do not have to wipe the phone and start over again with my apps and stuff because I have not really found a great free backuper and have not backed up within the last few days. I can use home+end call button to get to the bootloader (right name?) screen. However I am REALLY hoping I do not have to wipe.
Any solutions? I tried searching but could not find an answer..
THANKS!! This is basically terrible timing too because I leave on vacation tomorrow morning and will be needing my phone.
My phone (which is currently running Incubus26Jc's Android 2.2 FroYo RLS10 NAND) rebooted at around 12:30 AM. I noticed that it reboots, randomly, about twice a day. Not sure of the cause, haven't looked in to it, but normally it comes back to the desktop, like a fresh boot of the phone. So I thought nothing of it.
Last night, however, during the reboot, SOMETHING happened, and it seemed to have gotten stuck in an infinite loop. It would show the boot animation for a while, then lose power... then it would notice the power cable was plugged in, and try to automatically boot up.
If you notice, plugging the power cable in forces the phone to boot all the way into the Android OS. There seems to be no "charge while off" feature, at least for me.
Anyway, this endless loop caused the phone to reboot over and over and over, until the point where the battery was so far drained, that this "hand off" between the boot screen and the actual OS (somewhere during the boot animation) where the phone had to run on battery for a split second, was long enough to cause the phone to power off completely.
I couldn't flash back to Windows (I thought) because the phone didn't have enough of a charge to stay in bootloader mode while flashing the phone. Which was mostly true.
FYI (how I fixed my problem): should something similar happen to you, put the phone in true BOOTLOADER mode (hold the camera button when you press the power button, see the colored bars across the screen), even though the indicator doesn't light up, the phone DOES charge when in this mode and plugged in to a wall charger (and probably while plugged in to USB).
As far as I know, you are required to maintain a certain level of charge to run the RUU because the USB cable cannot charge the phone WHILE FLASHING, but while waiting in bootloader mode, the battery will charge. I was able to let the phone sit at the bootloader for about an hour then started up my phone and had over 70% charge according to Android. Working again!
thank for the 411. i had a similar issue with rls10. went to 10.5 and rls11 and flashed a new kernel, no further issue since
Hi, got a Moto G 2014, bought from new in October
Always had minor problems with it, especially including touchscreen going fuzzy/unusable when used with a particular charger, at low battery levels (although this isn't the one it was being used with most recently).
Recently apps have been crashing a bit more etc, quite annoying. Cleaned all caches etc today. Thought that there's a decent amount of space on the phone now so should download an app to make more of the phone - downloaded Fifa 15 which is a 1GB install.
Fell asleep during the install, woke up, and the phone was on boot loop. Didn't have a clue what was going on so I just tried to turn it on and off. Vaguely remembered something about power button and volume down, got to fast boot (I think it's called) with the normal boot, recovery etc options, tried both of those and they didn't work.
Put it on a different charger, somehow miraculously it turns up as '15%' charge stage, after a while, which it never did before. Charging now and it's reached 45%, in fairly normal time.
What's my next step? Turn it on? Or is there some way of recovering the files on the phone memory without turning it on?
edit: I mean is there some way of recovering phone files without attempting to turn it on, andd see it go into bootloop again, possibly
okay so turned it on when it had reached 100% battery, and it basically just goes back to boot loop ffs
I bought a XT1068 last year and have had no problems with it until this month. I used an anker power pack and almost immediately couldn't turn it on. I was assisted by a member of this forum and had no problems afterwards. However, yesterday I left it charging with the same charger and couldn't turn it on. The problem is that the Motorola logo shows for a few seconds (the flat one that shows at the end of a boot up) and then the phone turns off. So I went into fastboot (power + volume down) and tried to access recovery, the same thing happened. The same happened when I tried to factory reset it. It sometimes will not turn after I try one of these and stays on the Motorola screen indefinitely, for no apparent reason. Throughout this the battery slowly dies, having to be charged twice in 24 hours. And when I try to bootup from fastboot I get stuck on the Motorola screen. I am at loss of what to do and wondered if any of you had an idea?
Adb works from fastboot, but forcing a reboot from the command line produces the same results.
My bootloader is locked, I am running stock 4.4.4 and I am not rooted.
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.