[Q] Moto G 2014 - boot loop, next step - G 2014 Q&A, Help & Troubleshooting

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

Related

Need help! Possible brick

Hello,
I have a really strange experience with my G1. Last July when I was trying the latest Hero ROM /I do not remember exactly which/, my phone started to act strangely. When I was playing music through the music player, the phone suddenly shut down itself /without any reason/. I turned it on, the phone booted properly, worked for around 5 minutes and died again. This time it refused to power on /nothing happened when I pushed the power button/. From this moment I told myself that my phone is a complete brick, because I tried everything CAMERA+POWER; HOME+POWER, putted on the charger;USB, there was no reaction at all.
Today I have putted the USB cable /without any reason, hope dies last / and my phone suddenly showed a red LED. I pushed the POWER button and the led turned off, blinked and turned off again, when I released the button the RED LED turned itself on again. I tried HOME+POWER without any result, then CAMERA+POWER and it entered bootloader. Then I downloaded RC29 in order to downgrade it. The phone found the image file properly but it displayed the following error: Battery voltage too low, please change battery, I tried it several times, ending with the same error. I rebooted the phone it showed T-MOBILE G1 screen for about 10 seconds and it died again without showing any signs of life.
What should I do? Can this really be caused from the battery? Or is it something else?
The phone was running DANGER-SPL with the latest radio. I have flashed many roms after the installation of DANGER-SPL. The rom previously installed on the device was CYANOGEN MOD experimental /I do not remember the version/.
Thanks!
I don't mean to be rude, but it says low voltage charge battery. Why not do that, or buy a new battery.
Seems the phone doesn't recognize the full battery, I'm having the same problem - my thread here: http://forum.xda-developers.com/showthread.php?p=5307393
The battery I think must be full when flashing otherwise something goes wrong, but it's not bricked. I'm trying a few things...

blank/black screen after boot - frozen? gulp. . help

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.

Alert and FYI!

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

[Q] Possible brick during rooting?

Hey all, thanks for taking your time to read and possibly help me out with my problem. Yesterday I've tried rooting my droid in order to put cyanogen mod on it later. The reason I was interested in doing that was because I felt as droid was not working to it full potential and constantly crashing apps on me (browser, games, weather, etc). A friend of mine suggested cyanogen as he himself owns it. Being that I've did plenty of CFW on PS2, psp, xbox and mp3s/ipods, I thought there shouldn't be a hassle with this.
I followed the procedures listed on cyanogen's wiki page in order to complete the rooting process. But on the step where it asked to instal .sbf file trough RSD lite and wait till it says "pass" I've ran into trouble.
During the unpacking of that file to the phone using RSD lite the phone was undergoing several reboots, and after finally finishing the reboots on my PC screen in the RSD Lite window it showed 100% complete "please reboot the phone manually". I had no idea how to do that manually as the phone just kept going on and off by itself. (also for some reason it kept saying "error" force close/wait/send notice. But I thought it was probably just the process. After trying to reboot the phone a couple of times nothing worked. I didn't receive any "pass" signs on the droid screen.
I've got a little worried about the whole process and decided to shut the phone off and during that close the RSD Lite on my computer. Doing that made no further improvements for me. The phone just kept going on and off like crazy while in USB and not turning on at all while not plugged into either USB or AC. I've decided to go to recovery mode and just reset everything to stock as I was running out of time and had to get some sleep before work next day. After reseting the cache/data files I rebooted the phone but the same things kept happening to it. Now it was asking me to reconnect with gmail account and all that intro stuff. But the phone would always end up locking up and shutting off somewhere in the process of reconnecting the account.
Fast forward to today I've read that its possible to complete reset everything to stock version trough .sbf file once again. But now the problem consists of the phone not having enough batter life. (I'm not sure what the screen is called where the process of dumping .sbf trough RSD lite starts) but that screen keeps saying battery is too low to do anything with it. And mind me it has been charge for a very long time now in the AC adapter.
Now it also appears as the problem has worsened. The phone does not start up at all in either USB or without connection. It only starts up in AC adapter but then it shuts off in 2 minutes and back on and off , on and off. Recovery mode can't be accessed in any way, at least any way known to me. The black .sbf screen can only be accessed while the phone is not connected to anything but still keeps saying the battery is too low. And I've noticed the phone getting extremely hot during AC charge. (another small detail that sometimes when the phone does turn on and goes to home screen opening up the landscape view does not increase the length of the top (pull down) bar in horizontal view.
I've tried taking out both battery and sdcard and putting them back but no luck. I'm really lost as to what I can do next in order to fix this problem.
If you need any further information please let me know and thank you again for trying to help me!
I don't really see how you managed to get a fc with rsdlite.
Did you reboot your phone (turn off) then boot into usb recovery (power on while holding up, for the droid)?
Sent from my Droid using XDA App
I am by no means an expert and could be just wasting your time but in the absence of expert opinions something is better than nothing right? It sounds to me like maybe you have a bad battery that as luck would have it failed during the update/rewrite. Have you tried getting into recovery with the battery pulled running straight off the ac adapter? Hopefully you made a clockwork/nandroid backup before you started?
sent from a random hobo's droid on xda's app
I'm not an expert either, but having just successfully rooted my droid and installed cyanogen I feel the need to ask: did you hold up on the d-pad while RSD rebooted the phone the first time? If not then you needed to immediately restart the process.
I think you need to use a separate battery charger (meaning that charging battery without a phone) to charge the battery.
Sometimes, battery won't hold a charge when your phone is a brick.
BTW, it appears that you are having the same issue with mine.
(I can't post a URL because I am new here, but you can take a look at my article in this section, called "[S.O.S] A rare MILESTONE brick situation". )
I had the same problem (battery won't charge and phone won't start-up), I had to purchase a separate battery charger, and then flashed another SBF, to make the phone charging normal. (Although my phone is still a brick, but not a problem with battery. )

Restart loop on Moto G xt1068

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!

Categories

Resources