Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black. (adb doesn't work because (i think) usb debugging was not enabled.)
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens with every option.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
I have no idea what to do. Help would be appreciated.
Sounds like the stock ROM is corrupted.
Are you really XT1003? What version of Lollipop did you upgrade to?
i updated moto g. When i change bright screen was Black
SoberDogs said:
Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black. (adb doesn't work because (i think) usb debugging was not enabled.)
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens with every option.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
I have no idea what to do. Help would be appreciated.
Click to expand...
Click to collapse
Download the lollipop ota update from internet (check about phone for information and use it for searching update on google ) then flash it from the bootloader..
instinctblade said:
Download the lollipop ota update from internet (check about phone for information and use it for searching update on google ) then flash it from the bootloader..
Click to expand...
Click to collapse
Or he can get SIGNED factory images for lolipop and flash that if the ota does not work.
Related
Well, I finished a phone call last night, and when I hung up, the screen froze. I've had this type of behavior from my phone before, so I pulled the battery and restarted. Problem is, the screen will not turn on. I can try booting normally, which hangs as soon as logcat mentions the screen size. I can boot into recovery, but no screen image is displayed (adb access is there,) and I can boot into the bootloader (fastboot commands all work,) but again, no screen.
Is this a hardware problem? I've tried manually restoring some nandroids via fastboot to no avail.
Thanks
I have the same problem
I have successfully flashed the original rom (blind), but it still does not work ...
Preven said:
I have the same problem
I have successfully flashed the original rom (blind), but it still does not work ...
Click to expand...
Click to collapse
I notice you're not on TMobile, but they offered to replace mine. I did a bit of poking around and it does in fact look like the display hardware fails to initialize. See if your carrier can replace it for you. How did you flash the stock rom with no screen (Are there CWM shell commands I don't know about)? I want to flash mine to stock before I send it in to TMO.
Hi guys,
My girlfriend bought a new Moto G yesterday. When she connected to WiFi during the setup, the device immediately said an update to 4.4.2 was available. She downloaded and applied the update but now her phone only shows the blue Motorola orb and then a black screen for 10 seconds. This loops until the battery runs out.
I can access the bootloader (flashed both the EU 4.4.2 firmware and the GB one and both don't give any errors but don't resolve the issue).
I can't access the recovery (it just seems to reboot the phone) or factory reset it from the bootloader.
Any idea what might be happening and how I can resolve this?
eddiemerckx said:
Hi guys,
My girlfriend bought a new Moto G yesterday. When she connected to WiFi during the setup, the device immediately said an update to 4.4.2 was available. She downloaded and applied the update but now her phone only shows the blue Motorola orb and then a black screen for 10 seconds. This loops until the battery runs out.
I can access the bootloader (flashed both the EU 4.4.2 firmware and the GB one and both don't give any errors but don't resolve the issue).
I can't access the recovery (it just seems to reboot the phone) or factory reset it from the bootloader.
Any idea what might be happening and how I can resolve this?
Click to expand...
Click to collapse
i also have same problem...
i cant find solution for my moto g.....
jayrocky11 said:
i also have same problem...
i cant find solution for my moto g.....
Click to expand...
Click to collapse
I didn't find any other solution other than sending it back, so it's on its way to get replaced.
I have a Moto G (from Republic Wireless) and started having the Boot loop problem.
When I try to go for fastboot, then volume up to select recovery, the motorola logo appears, but no android logo after. Then the boot loop starts again. Anyone help me please?
Did you flash an older android version?
Same same but different
I have the same issue. Although I actually get as far as to getting to the lock screen and unlock that and then I get about 3 seconds then I get the 'Powering Off' message and the phone turns itself off.
I have enough time to go in and put it in debug mode but the phone never recognises the computer once in bootloader, I think it most likely have something to do with the driver for 'Fastboot falcon s' not working. Can't install a new one or in any way make my phone communicate with my computer. Have all the latest Moto device manager stuff installed too. I also think I have the wrong firmware installed (US and not AUS version) along with a heavily corrupted (or even completely missing) recovery image.
Have tried flashing a new recovery image but I keep getting either a blank response from 'adb devices' or 'fastboot devices' and whenever I try and issue a command that would hopefully result in anything other than the **** I am currently stuck in I get a 'waiting for device'.
All this because I tried to go from Unlocked Bootloader and CM11 (that wouldn't let me use mobile data or kept crashing on me, like 24/7) to stock Android and Relock the Bootloader.
I am pretty much losing my **** here, just happy it was only a $250 device though.
Does anyone have anything on this?
oh well, giving up on this. Contacted Republic Wireless and and they're sending me a replacement.
Just wanting some advice (if any) to a white line issue I'm having with this tablet. I bought this tablet with Lollipop 5.0.1 already installed. I managed to get it downgraded, rooted, and currently have TWRP installed as well as CM12.1 nightly. The problem I have is that as soon as I install ANY custom recovery (TWRP or CWM recovery) it boots normally at first giving me the LG logo. Then, instead of getting the AT&T logo (or the CM custom boot animation), it gives me a series of white lines spamming from top to bottom of the screen. I know for a fact it has to be software related as when I return to stock KK everything boots fine, giving me the LG logo followed by the AT&T logo. I did NOT use the ADB method. Instead I downgraded using the LG Flash Tool, and a test KDZ file, which allowed me to install Flashify, then TWRP. My problem ONLY begins once I install ANY custom recovery. This process did not unlock my bootloader, however. Could this be my culprit, or would it be something else? Any help is greatly appreciated, and thanks in advance for any help/tips. More information is completely available upon request.
P.S. The white lines eventually disappear when the screen goes to sleep on it's own. I can then press the power button to wake the device which gives me the lock screen as normal. I just want to know if I can get the boot animation working. Everything else works fine.
You found cwm?
Hey guys, I've got a Kyocera Brigadier and I decided to change the runtime from Dalvik to ART. Now the phone is stuck on loadscreen and I don't know how to fix it. The phone is rooted using the KingRoot app, but I don't know if that would help in any way.
Please help me guys!
Similar Issue
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Ornias Abezethibou said:
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Click to expand...
Click to collapse
I have the same problem. I bought a new a Brigadier that was on 4.4.2. I rooted with Kingroot ran update and now my phone will not boot past Kyocera screen. It goes black with the back light on. Did factory wipe and still nothing. I am shocked that KK has killed yet another phone of mine. I very much dislike KK ROM. What did you find out?