Hi,
I've been searching the web for a few days and tried many things, but so far I haven't been able to fix my Moto G.
My device:
Moto G (XT1032)
DE distribution
single-sim 8GB variant
Stock firmware was Blur_Version.14.71.8.falcon_umts.O2.en.DE or Blur_Version.14.91.11.falcon_umts.O2.en.DE (not sure)
What preceded the problem:
Something like a week ago I turned on my Moto G for the first time, checked for updates to KitKat but no updates were found
I forced checkin several times, rebooted the device, still no updates found.
Updates were available on the web for several weeks, so I thought I would update manually.
I unlocked bootloader (didn't know I didn't have to)
Downloaded KitKat rom for a single-sim variant from o2 DE distribution
Flashed firmware using motorola version of fastboot (didn't forget to clear the cache and userdata)
All went fine and I was able to boot to KitKat
When it happened:
I was tinkering with developer options, probably switched runtime to ART (not sure)
I rebooted the device (manually or when switching runtime)
Device stuck in a bootloop
What doesn't work:
Stock recovery (bootloop, 4.3 and 4.4 firmware)
CWM recovery (bootloop, both with motoboot.img for 4.3 and 4.4)
TWRP recovery (splashscreen flashing, both with motoboot.img for 4.3 and 4.4)
CM 11 (bootloop)
What works:
Philz recovery (http://forum.xda-developers.com/showthread.php?t=2639583, when this recovery is flashed, device boots straight into recovery)
ADB (in recovery)
What I've tried:
Flashing many, many firmwares. Triple checked if I didn't miss anything.
Factory resets, partition formatting (In philz recovery).
Rooting the phone
Checked whether eMMC chip is corrupted through ADB shell (dmesg | grep mmc0), seemed OK, no error messages (http://forum.xda-developers.com/showthread.php?t=1284196)
Using 4.3 motoboot.img with cyanogenmod and recoveries that doesn't work
Flash stock firmware and install OTA 4.4 update in philz recovery (seemed promisingly, took longer than flashing full firmware)
Where I may have had screwed up:
- After few initial attempts to fix my phone failed, I tried corrupting the bootloader to get to download mode as suggested here http://forum.xda-developers.com/showthread.php?t=2623587 and correct it.
I would be glad for any idea C'mon, you are some smart guys, we can do it!
Try to flash stock 4.4 firmware, do not flash any recovery after flashing the stock 4.4 and see what happens
I've experienced something like that, and after reflashing the stock many times i fixed it
sounds like my problem exactly. what did you do, return the phone?
how does flashing stock repeatedly help? which stock? which method (does it matter if you do it from fastboot or in philz or some other way?)
I have the same problem, could u solve this? plsssss HELP MEEEEE
Related
So i decided to install the CM 12 on my MotoG.I downloaded the files and followed the instructions.I wiped cache,dalvik,data and did Format System but the installation failed.So I reboot my phone only to see that it was stuck at a bootloop.I get back to TWRP and I see that there was no OS installed.I decided then to flash 4.4.4 which worked,but after rebooting i was in a bootloop with no OS once again.I installed PhilZ Touch to see what's wrong.It says that I can't mount the system and the sdcard.I've tried Sideloading,adb pushing but everything fails...Is there anything i can do?Help is much appreciated
Have you tried to flash a stock ROM via fastboot commands?
Yes nothing happened..still stuck at bootloop...
nikoschasapis said:
Yes nothing happened..still stuck at bootloop...
Click to expand...
Click to collapse
which stock rom did you try to flash using fastboot?
if it's the stock 4.4.4 it's probably going to fail, you need certain things to do (you can search around here) if you're using xt1033, you can search for (xt1033 stock) there's a guide that will get you up and going. On my moto g that has flashed stock 5.0.2 and cm12, i found out that i can't use the normal method to flash the stock 4.4.4 rom, rather i was forced to flash the 5.0.2 rom, since the fastboot command fails at almost everything, which would leave the phone unusable
oh yeah, here's the guideRESTORE TO STOCK
Nevermind.I formatted the data and it let me adb push the stock 4.4.4
ROM
Hi all. I own a Moto G xt1032 UK version. (GSM right?)
I was on 4.4.4 Epsilon ROM but I wanted to flash stock 4.4.4, so I used a tutorial I found on youtube that set me up to stock 4.4.2, then I upgraded to 4.4.4 and THEN there was another update to 5.0.1. So as you can guess, I upgraded to lollipop and that was it - bootloop. I have tried flashing other roms through fastboot and nothing worked, I get an error when I flash ''system'' that says ''image is too large'' once all is done, phone restarts and its stuck on bootloop once again. The bootlogo changes when I flash different rom etc. But I don't know what to do, any ideas? :/ I have also tried to flash a custom recovery and sideload the Epsilon ROM but I only get an error in my command line that says no device connected after I hit the command. Any suggestions guys? I appreciate any sort of help, thanks guys.
I'll also add that I think I have the 41.18 bootloader if it helps (it says so in the bootloader settings)
When flashing a ROM in fastboot, are you also flashing the gpt file?
Yeah. I flash everything there's to flash as all tutorials instruct.
To try and get your phone up and running, flash a custom recovery from fastboot. Once the recovery image has been flashed, use the phone's volume buttons to boot into recovery. If you can get into recovery, try and flash a custom ROM.
Ah, I forgot to add. When I attempt to flash anything from my storage it says some sort of error coun't mount /sdcard and others when the recovery opens up. I tried flashing other recoveries, TWRP, CWM both show the exact same errors..Can't mount SDcard etc. :/ That is why I tried the sideload method which didn't work for me either.
You're flashing recovery for the falcon?
Yes..for falcon. I've done it a bunch of times before, however I never had the unable to mount error in the recovery..
I don't have my moto g on me but I found Philz Touch (based on CWM) worked besr for me after i switched back from GPE to CM12. I was getting weird error messages in TWRP.
Hello everyone. So I was updating CM12.1 to the latest nightly (4th of July) and when it finished flashing, it rebooted mid-boot, and when booted into 5.1 it said something about "encription failed" and told me to factory reset. So I went to factory reset it, and my CWM recovery was gone. The only thing that happened when I went into recovery is that the spinning-thing Andy popped up for 0.5 seconds again and again. I tried flashing the entire firmware again (stock 5.1) but no help.
I can access the bootloader and input fastboot commands.
I would give more system information, but now I don't know what the hell this phone's running.
moto g XT1039 cid7
Was running CM12.1
Was using CWM-6.0.5.0-peregrine recovery
Thanks for the help.
EDIT: FIXED
So, in order to fix it, i had to install stock firmware one or two times until it worked. You can get your corresponding 4.4/5.1 stock firmware from here http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619 If you install it and it doesn't go past the "Bootloader unlocked" screen, try flashing the stock firmware a few more times until it works.
Hope it helps!
Hello everyone. I need help! I had 4.4.4 KK, then I converted to GPE and then flashed the 5.1 Lollipop 2-3 months ago.
Yesterday I got a notification about an update (7.6 mb), I headed on and installed it and after the installation my phone did not reach the lock screen, it just stuck at the animation and never stopped. Please, tell me what to do! I am so meesed up, I don`t know what to do. Thank you.
I have exactly the same problem and have no idea how to fix it, please help us.
Same problem,
Model : Moto G 2013 (Tesco) - Flashed with GPE Lollipop, worked fine until update.
Stuck on boot screen after update,
Problem persisted after full stock restore, I made several attempts with different stock versions, all same result.
For me these steps fixed the issues, but will FULLY WIPE everything!
1. Stock Recovery (I used XT1032_FALCON-RETGB_5.0.2_LXB22.46-28.1_1_cid7_CFC_1FF.xml)
2. Restored TWRP using fastboot (twrp-2.8.7.0.-falcon_GPE.img I like the interface of the GPE version),
3. From TWRP I noticed that the /cache and /system partitions could not be mounted correctly, repair failed from within TWRP (adb shell should show you the same things.)
4. Use fastboot to format system and cache.
5. Use adb push to get AOSP 5.1.1 ROM, SuperSu and Gapps zips onto Moto G (I don't know why sideloading doesn't work).
6. Use TWRP to flash ASOP 5.1.1 ROM, SuperSu and Gapps.
7. Cross fingers and reboot.
The partition issues may just be something broken on my phone, a stock restore might work for you.
There may be another way to fix this without wiping everything, but from based on past experience using the GPE ROM on a non GPE Moto G, the partition differences cause problems.
I hope that is of some help.
Hi,
I have a Moto G 2013 (falcon) and have installed multiple custom ROMs over the years, with the latest one being the Pixel Experience 8.1 ROM. However, I attempted to go back to the original firmware as Pixel Experience wasn't working too well, and it didn't work, and I got a recommendation to install Lineage OS 14.1 on it, at which point when attempting the install the booting up sequence took forever, and so I tried the Resurrection Remix ROM, also no luck. It appears the phone is completely unable to boot - what should I do?
Kind regards,
Marco
A similar problem, I can not install any ROMs and my stock recovery blinking
restore latest stock firware, this fixes most unfixable bootloop issues. remember by restoring stock firmware i mean "fastboot" way, not through custom recovery.
follow; https://forum.xda-developers.com/showthread.php?t=2542219
koshikas said:
restore latest stock firware, this fixes most unfixable bootloop issues. remember by restoring stock firmware i mean "fastboot" way, not through custom recovery.
follow; https://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Don't work, I believe I've damaged some partition (like System,Data, ...) and no rom can be installed, bootloader may be corrupted
My XT1033 only turn on fastboot and stock recovery blinking, other recovery like TWRP they work but I can not mount or wipe any partition
I had similar symptoms after accidentally flashing a falcon firmware to my peregrine device. This caused the screen to "fade out" or flicker, but I could get to the bootloader, albeit flickering. Flashing a correct boot.img solved the bad screen issue, at which point I used fastboot boot mode to boot TWRP and flash a more "correct" rom.
I then ran into the forever booting issue. I fixed this by flashing the relevant radio...It frustratingly booted to oobe within seconds!
Hope this helps someone