Bootloop after last update. - Moto G Q&A, Help & Troubleshooting

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.

Related

[Q] Moto G bootloop on stock firmware (Troubleshooting)

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

Problem installing custom recovery, please help!

I have been trying for hours to install both TWRP and CWM recoveries, and my phone will not accept them.
It goes through the process, yet upon the reboot into recovery, it just starts normally.
the message on the phone is: Mismathched partition size (recovery)
I have a Canadian version of 4.4.2 stock rom on my Moto G.
It is boolader unlocked and rooted.
Any ideas how to install the recovery?
My ultimate goal is to install a rom that supports russian language.
retfeg said:
I have been trying for hours to install both TWRP and CWM recoveries, and my phone will not accept them.
It goes through the process, yet upon the reboot into recovery, it just starts normally.
the message on the phone is: Mismathched partition size (recovery)
I have a Canadian version of 4.4.2 stock rom on my Moto G.
It is boolader unlocked and rooted.
Any ideas how to install the recovery?
My ultimate goal is to install a rom that supports russian language.
Click to expand...
Click to collapse
same problem here! brand new phone, 4.4.2 o2 UK.
the mismatched partition size error is not important i know that.
have tried Philz (got it to work once, but after rebooting, had gone again. ever after letting it fix the rom rewrite on exit!). also tried stock CWM 6046 and 6047.
have tried entering recover immediately after flashing.
have tried flashing multiple times.
have tried different usb ports.
ideas please?
i've never had this much trouble with any phone (have experience over 3 years with Blade, G300, Xperia range etc.)
edit: tried using fastboot -S 0 parameter also, seems to make no difference. phone won't boot into recovery. this is slightly different to the problem i had with old phone, that one would boot Philz but not boot any ROMs. this one is booting stock ROM. if i can get Philz to "take" again i could try flashing CM, but i wanted to stay on stock, and just root it..
edit2: just started working! bizarre.. hope this doesn't jinx it. i wrote two recovery images with -S 0 and it works, not sure if because of that or something else. btw Philz won't backup the stock rom, odd - it just errors out, CWM standard works though.
hurrah! i rebooted normally, went back to fastboot and recovery still there. this is with recovery-clockwork-6.0.4.7-falcon.img
now i can hopefully root it..
wonder if my 3rd moto g will get any easier! this is a huge PITA of random non-workiness so far.

Won't boot after Lollipop downgrade

i thought, i might just do a separate topic, as it gets overseen easily in other threads...
What i did:
had b140 working fine. Wanted to Update to b312 Lollipop, worked well. Then, i had some problems with Google Play Services and such. Wanted to downgrade.
First, flashed stock recovery, worked fine.
Next, Transfer Package b300: No Problem
After that, b137 as KK Rom: Updates to 90% then doesn't move.
What i already tried:
- b127, b137, b141, b312 all won't either start update or get stuck at 90%. All tried with and without previous Transfer Package.
- boot and recovery .img from Stock 4.4 and 5.1 to no avail.
- Unpacked b137 and flashed boot, system, just and recovery. No boot, no downgrade
- flashed twrp 4.4 and 5.1 both 2.6 and 2.7. One did work, throws message about not being able to mount /emmc.
- tried flashing the one custom rom EMUI based for L09, script runs perfectly, before reboot: "No Rom Installed". Won't boot
- tried CM11: Won't flash properly.
I'm pretty much out of options now. I'll take anything workable. KK or LP or what ever, as long as i'm able to recover that phone. Any ideas guys?
OMG, got it working. After two days of flashing anything i found, o went back as far as i could.
1. Bootloader, flashed boot and recovery from 5.1
2. Transition Package for LT09 fro here :Huawei Rollback LT09 (Had to boot 3 Button method with SD-Card not Inserted, then after huawei logo push sd-card in)
3. b120SP03 fro here: Huawei b120SP03 (again, three button method with sd-card not inserted, then after huawei Logo push sd-card in)
This was the first firmware that booted for me. Now i need to setup and see if i can get OTA...
I can't tell you how happy am :laugh:
Excellent well done.
Hopefully this helps someone else too.
bricked
i have a MT7-L09 it does not boot other then a vibration showing the logo the turning off straight away any fix for this ?

[HELP] Moto G 2013 GPE Stuck at boot after update

Hello,
I updated my Moto G 2013 to GPE 5.1 a while ago using an install guide from this forum (it was non-gpe before). Today I got a notifcation that an update is available. I installed it and now my phone won't fully boot up. So I am stuck in this boot animation.
What can I do now? I also want to backup at least my files on the sd card. Or is there any way to fix my problem while preserving my data?
Thanks a lot
Are you rooted? Did you had a custom recovery installed?
I received it as well, it's a 7.6 MB file, probably a stagefright patch.
Yes, I am/was rooted and had a custom recovery. So this was the problem I think. I managed to grab my files via TWRP-Recovery. So now I have to find a way to fix the boot problem.
Edit: Well, I just re-do the tutorial for flashing GPE 5.1 which seems to work.
Same problem here. Original firmware and recovery, just rooted.
I am trying to solve the problem without losing data.
There 'something with the /data folder
i install the GPE solution in this forum on my phone too + root. But i keep the original recovery
When i try factory reset i got this error wiping /data
Formatting /data...
E: format_volume: failed to open /dev/blck/platform/msm_sdcc. 1/by-name/metadata
The /cache format is ok
I hope this can help somebody to find the solution .
At least i think android stuck on boot because it cant find that folder
please help
im having same problem .my moto g2 was rooted .i got notification that update 5.1.1 is available .but after update it is stuck in bootloop:crying:

Moto G forever booting (all ROMs)

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

Categories

Resources