Device Info:
VZW Moto G (1st Gen)
Android 4.4.4. KitKat (Stock)
No root, bootloader locked, never tampered with
Problem:
I set my phone down on the kitchen table and left it there a while. When I came back the notification light was blinking so I tried to turn on the screen, but nothing happened. Eventually I hard reset the device (held down the power button until the device started to reboot). The phone showed the white boot up screen with the planet Motorola logo, but rather than continuing with the boot animation, it hung there for a while before going to a black screen. I have left it for hours, it never progresses past this point. Sometimes it will reboot itself and try again to no avail. I was not installing any updates when this took place.
Attempted Solutions:
I held down the power and volume down buttons and went to bootloader. The battery was listed as low. I let the battery charge overnight and tried the bootloader again. The battery is now listed as OK, but the phone still won't boot. To be extra sure it isn't a battery issue I tried different chargers, outlets, and laptop USB ports for long periods of time. I am convinced this is not the usually "phone will not charge when turned off" problem. I also attempted to hold the power button down for long periods while on and off the charger. No results.
Resigned to take drastic measures, I tried first recovery and then factory reset from the bootloader screen. Each time I am returned to the white screen and then the black and nothing happens. I do not get the distressed android logo at all. I tried to unlock the bootloader to install a custom or factory image, but this is not allowed for the Verizon version of the Moto G.
I am out of ideas, having tried everything I've read on other posts with similar issues. What can I do?
Related
This is the first time this has happened. Basically the screen will just turn black randomly and the Google image pops up for a couple seconds before staying off. The first 3 times it happened I was able to turn it back on by just holding the power button. After that, however, it got stuck in a boot cycle until I plugged it into a charger and tried. So far with the charger plugged in it hasn't turned off yet.
I've attached a screenshot of my battery status. It seems the battery disappeared for a few hours?
Does your battery smell like sulphur?
Sounds like a stuck power button unfortunately. Quite common.
I'd say try flashing stock firmware again with fastboot.... But if it reboots while flashing, you'll be in more trouble.
Let it sit in bootloader mode awhile... See if it reboots or anything. If not, you could try flashing stock firmware. But hopefully it doesn't shutdown mid-install.... That wouldn't be good.
So my friend gave me her old Motorola Moto G 1st generation and it was fine for a few months, then a couple of days ago it wouldn't turn on. So I plugged it in and held down the power button then the down volume, and went into flash boot mode. (i think its called that). And did normal startup and everything worked fine. The next day it did the same thing and i tried to do normal startup, but it froze on the blue M screen, so i did it again but tried with recovery mode, the results was blue M screen then a black screen with the back light on. I have tried doing that many times but all i get is blue M screen, vibration, then the black screen. I have let the battery drain and charged it, to see what it would do. No progress. The battery is dead right now. Please Help.
Hello XDA!
So yesterday I decided to charge my Moto G (xt1033) after dying earlier today. After it charged to around 75% I unplugged it, I held the power button until I saw it showed the "Warning Bootloader Unlocked" screen and I put the phone in my pocket. After dinner, I noticed that my phone was running hot in my pocket and when I pulled it out, it was still on the "warning Bootloader Unlocked" Screen. I tried rebooting and all I got was a quick vibrate.
I've tried searching this problem. I've tried sideloading CM12.1, wiping both caches and I tried to do a factory reset (which froze halfway through). I can still access fastboot and CWM, but that's as far as I can get.
I'm stuck. I have no idea what is wrong. I've tried everything I've seen around and my only guess is my phone is totally bricked.
If anyone has had this problem or they have any idea how to fix it, feel free to reply. I'm open to everything.
Soft brick.
Try flashing from fastboot your favorite version, maybe it's a partition-related issue.
My Moto G 4G won't boot up. Last night I forgot to charge my XT1045 and woke up to it bricked. Plugged it in and went back to sleep. A few hours later, I turned it on and it worked fine. Later, the screen froze and I turned it off by holding power until it turned off. Now, for whatever reason, it won't turn on again. I've had it plugged in for nearly 12 hours and have tried the "power + vol down for 120 seconds" suggestion to no avail.
What's interesting is that when I plug it into my computer, I can hear it being removed/recognized at around the 120 second mark but it doesn't go into the bootloader -- the screen stays black. It also doesn't show up with adb devices, which isn't surprising since it doesn't actually show up as recognized, the audio notification is all I can go off of. Am I completely screwed? Any ideas? It's rooted running the optimized stock 5.1 and stock recovery. Thanks!
well, hello everyone here, yes, as the title says, my moto g is just stuck on the motorola logo and that's it, i bought this phone to a friend who told me it was the motherboard that was f****d up, but when i got home y just pressed vol - and power just because of instinct (i actually don't know much about this phone or motorola phones itself) and it enteredinto fastboot, so i was like: 'ok..... i've just bought a treasure' and everything relatively ok, i browsed through the menu options to see what was available, i pressed Recovery and the phone just turned off because it was low in battery (before all of the fastboot and stuff when i press power, the white led just blinked and that was it, it wont even boot into Motorola logo). Ok after seeing that the phone was low battery i disarmed it and charged the battery with two cables from and or usb i peeld just for this situation. After leaving it for like two hours i put the battery again and was stuckd into the Motorola logo... nothing hard, but what is pissing me off is that now i CAN'T BE ABLE TO BOOT INTO FASTBOOT and it's just stuck booting o trying to (when i connected the battery the phone turned itself on). Now i don't know what to do, i'm desperated, please, help me
duvaldavidr said:
well, hello everyone here, yes, as the title says, my moto g is just stuck on the motorola logo and that's it, i bought this phone to a friend who told me it was the motherboard that was f****d up, but when i got home y just pressed vol - and power just because of instinct (i actually don't know much about this phone or motorola phones itself) and it enteredinto fastboot, so i was like: 'ok..... i've just bought a treasure' and everything relatively ok, i browsed through the menu options to see what was available, i pressed Recovery and the phone just turned off because it was low in battery (before all of the fastboot and stuff when i press power, the white led just blinked and that was it, it wont even boot into Motorola logo). Ok after seeing that the phone was low battery i disarmed it and charged the battery with two cables from and or usb i peeld just for this situation. After leaving it for like two hours i put the battery again and was stuckd into the Motorola logo... nothing hard, but what is pissing me off is that now i CAN'T BE ABLE TO BOOT INTO FASTBOOT and it's just stuck booting o trying to (when i connected the battery the phone turned itself on). Now i don't know what to do, i'm desperated, please, help me
Click to expand...
Click to collapse
I have exactly the same problem. My moto g doesn't stop trying to start uo even if i am not pressing the power button. When I connect it to the charguer screen turns on and says o% battery, then it tries to turn on itself. Have you solved this problem???
@duvaldavidr @jorgearnaiz998 Any of you had any luck?