Hi everyone,
this is my first post, so i hope i'm posting it right, following every rule.
I've got a problem with my moto g. At the moment i bought it, I unlocked the bootloader, rooted it, upgraded it into KitKat, tried out a few different roms, installed Xposed, etc. and i never had any problem ( at least not one i coudn't figure out how to resolve).
However yesterday i wanted to try out Cyanogenmod 11, with yesterday's nightly 09/04/2014. I downloaded it from this post :
http//forum.xda-developers.com/showthread.php?t=2608377
Downloaded Gapps, too. Put both of them as zip in the moto g, did the 3 wipes and installed both zip's ( first cyanogen and then gapps).
However, once it rebooted, the cyanogen arrow kept moving around, endlessly. ( i waited for around 20 min)
In case it's relevant, i'll say that at the moment of downloading the nightly i lost internet connection, however i managed to resume the download and decided to keep going.
But after seeing that i didn't manage to install the rom properly I decided to download the nightly again and push it via "adb push .... ".
I installed it again with CWM, but the cyanogen logo kept loading. Nothing happend.
I also tried to install other Roms : GPE, 4.4.2 stock version and i even tried downgrading it to 4.3 ( which had previously worked, but not this time :crying: ) .
Everytime i got the same error, the mobile stucks at the logo ( Google logo, motorola logo, cyanogen logo,... )
My bootloader is unlocked and i've already the 3 wipes, and chache & system format ( via CWM )
and if i try to install a zip via CMW i get the following error : "E: Can't mount /sdcard"
wipe dalvick cache doesn't work and there is no error displayed.
¿Can someone help me?
Thank you very much!
Best way for you right now is to flash your stock firmware back (through fastboot) and try cm11 on that.
small-mallet said:
Best way for you right now is to flash your stock firmware back (through fastboot) and try cm11 on that.
Click to expand...
Click to collapse
Yap you should do a factory flash just download the pack "Moto g back to stock script" and do a full wipe while in fast boot and then flash CW root and install r0m u wish
Hey guys, i'm having some SERIOUS problems with my 1st generation moto g XT1033.
Some days ago, i flashed stock android 5.0. Alright... So, i discovered that that were cm12 nightlies on the official cyanogenmod site and i flashed it. So, just after that i discovered that dual sim wasn't ported yet so i tried to change to stock 5.0, but my phone entered in a boot loop so i flashed stock 4.4.4, with no luck... now i flashed 5.0 but it's still not booting, i am now thinking about going back to CM12, which already have dual sim... the problem is that i dont know why, TWRP MTP isn't working, so now i just cant pass the CM12 zip to the phone because of that. please i need help i dont know what to do, if there's some way to flashing it without using TWRP's MTP. Thanks a lot and sorry about the english
pedrocarboni said:
Hey guys, i'm having some SERIOUS problems with my 1st generation moto g XT1033.
Some days ago, i flashed stock android 5.0. Alright... So, i discovered that that were cm12 nightlies on the official cyanogenmod site and i flashed it. So, just after that i discovered that dual sim wasn't ported yet so i tried to change to stock 5.0, but my phone entered in a boot loop so i flashed stock 4.4.4, with no luck... now i flashed 5.0 but it's still not booting, i am now thinking about going back to CM12, which already have dual sim... the problem is that i dont know why, TWRP MTP isn't working, so now i just cant pass the CM12 zip to the phone because of that. please i need help i dont know what to do, if there's some way to flashing it without using TWRP's MTP. Thanks a lot and sorry about the english
Click to expand...
Click to collapse
Bad idea, never try to downgrade... If you can still access fastboot you are VERY luck that your phone did not end up in a hard brick. :fingers-crossed:
Try and flash stock 5.0 from fastboot mode. And wipe everything including userdata.
Goodluck!
skyguy126 said:
Bad idea, never try to downgrade... If you can still access fastboot you are VERY luck that your phone did not end up in a hard brick. :fingers-crossed:
Try and flash stock 5.0 from fastboot mode. And wipe everything including userdata.
Goodluck!
Click to expand...
Click to collapse
Thanks for Helping!!! Just one question: How can i pass the stock zip to the phone to flash it if mtp is not working?Any suggestions? Because i think its not possible to flash 5.0 using fastboot, just on the stock recovery
update: I have just figured out that adb is working with CWM, which i have installed right now Yay!now I can push files from my computer!!
https://androidxda.net/how-to-unbrick-moto-g-1st-gen-2013-after-lollipop-5-0-android-update/ :laugh::laugh:
pedrocarboni said:
Thanks for Helping!!! Just one question: How can i pass the stock zip to the phone to flash it using if mtp is not working?Any suggestions? Because i think its not possible to flash 5.0 using fastboot, just on the stock recovery
Click to expand...
Click to collapse
If you have unlocked boot loader then go into fastboot mode and run "fastboot boot customrecovery.img" where customrecovery.img is CWM or TWRP. I recomment TWRP. From there you can adb sideload the zip. Only flash it if you know exactly what you are doing or you may end up in a hard brick.
skyguy126 said:
If you have unlocked boot loader then go into fastboot mode and run "fastboot boot customrecovery.img" where customrecovery.img is CWM or TWRP. I recomment TWRP. From there you can adb sideload the zip. Only flash it if you know exactly what you are doing or you may end up in a hard brick.
Click to expand...
Click to collapse
i used sideload flashing CM12,but i have recieved the error message "could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4 mount:failed to mount /dev/block/platform/msm_sdcc.1/byname/system: Invalid Argument
unmount of /system failed; no such volume detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and when i try mounting /system, CWM says Error mounting /system!
pedrocarboni said:
i used sideload flashing CM12,but i have recieved the error message "could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4 mount:failed to mount /dev/block/platform/msm_sdcc.1/byname/system: Invalid Argument
unmount of /system failed; no such volume detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and when i try mounting /system, CWM says Error mounting /system!
Click to expand...
Click to collapse
Do this at your own risk:
Your system partition is corrupt, you need to enter adb shell and format /system into ext4s. Search on google for the command as I do not have it on the top of my head. I believe it has something to do with make_ext4s function.
pedrocarboni said:
Hey guys, i'm having some SERIOUS problems with my 1st generation moto g XT1033.
Some days ago, i flashed stock android 5.0. Alright... So, i discovered that that were cm12 nightlies on the official cyanogenmod site and i flashed it. So, just after that i discovered that dual sim wasn't ported yet so i tried to change to stock 5.0, but my phone entered in a boot loop so i flashed stock 4.4.4, with no luck... now i flashed 5.0 but it's still not booting, i am now thinking about going back to CM12, which already have dual sim... the problem is that i dont know why, TWRP MTP isn't working, so now i just cant pass the CM12 zip to the phone because of that. please i need help i dont know what to do, if there's some way to flashing it without using TWRP's MTP. Thanks a lot and sorry about the english
Click to expand...
Click to collapse
Pedro, I have the same problem.
I can only access bootloader and recovery, but using adb sideload I can't flash any image (and version) that works.
I just get boot looping as you, and gpt.bin and motoboot.img files can't be flashed.
I've found that with Lollipop bootloader we can't install an older Android version.
My Moto G is now a paperweight, until the final stock Lollipop comes.
pedrocarboni said:
i used sideload flashing CM12,but i have recieved the error message "could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4 mount:failed to mount /dev/block/platform/msm_sdcc.1/byname/system: Invalid Argument
unmount of /system failed; no such volume detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and when i try mounting /system, CWM says Error mounting /system!
Click to expand...
Click to collapse
Hi, I experienced the same problem. Have you fixed your phone? Please give me some suggestion. Thank you.
Same problem with my Moto G 2013.
I've tried to downgrade and got problem. Now I can't flash an older motoboot.img and gpt.bin.
I'm using CyanogenMod 12, but every time when I boot, there is a line going down over the screen.
This line only disappear when I turn off and on the screen. Then everything backs to normal.
Is there a way to solve this?
This happened to me yesterday, i wento from my US Retail 4.4.4 to BR Retail 4.4.4 then via stock recovery flashing the OTA of 5.0, installed Xposed but gave me slow boots, like 5 min per boot, so i decided to downgrade, flashed 4.4.4 BR but after boot a black screen comes and doesn't go, think of flashing 4.4.2 US but the same isue, then decided to update again to 5.0 BR but stock recovery don't let me flash because an error, i flashed philz touch and do a factory reset, wipe data, cache, and everything, then flashed flashing 4.4.4 BR and then 4.4.2 US, the line down problem is nothing, only appears when you boot and, if you lock your phone for about 2-3 seconds, it dissappear (until you boot again), hope it helps, sorry for bad english
For all with bootloops, there is a major issue caused with a boot animation memory leak. Search on the forum to find the fix. You may need to delete the bootanimation binary.
skyguy126 said:
For all with bootloops, there is a major issue caused with a boot animation memory leak. Search on the forum to find the fix. You may need to delete the bootanimation binary.
Click to expand...
Click to collapse
skyguy126, I've not found any solution for this on forum.
Could you please show me a way?
For those that have problems downgrading, download this and follow this steps.
Once finished flash TWRP recovery and restore your nandroid.
Moto G not Booting, HELP
Hi everyone, I really need help with my moto G, it´s not booting into android after pressing the power button the moto logo comes up and the phone goes directly into fastboot displaying a message in pink color: version downgrade for boot
Failed to validate boot image.
I have been hours checking around for a solution and working now for the third day trying to solve the problem with no luck.
I have downloaded the original firmware for the device, tried to flash it and it doesn´t work, tried other countries firmware and they doesn´t work either.
The process will be partially ok but as it goes to flash the boot.img, recovery and system files it will give an error.
I also tried bootloader refresh, bootloader bricker and blankflash to try fix any possible bootloader issues.
The device has a locked bootloader since it is a moto g from AIO.
Please Help, It´s my only device and I cannot afford another one at this time.
There´s a few images from the flash process and device info
:crying:
You need to unlock your bootloader in order to flash various ROMs.
but in this model the bootloader cannot be unlocked it is CID 0X0010
How did this happen to your phone? What model phone do you have?
It´s a Moto G 2013, xt1032
It all begin trying to install a signed stock firmware that was supposed to be for that specific model: AIO_XT1032_4.4.2-KXB20.9-1.10-1.9_CFC_1FF.xml
During the flash process it send some error messages but the process keep running until it finishes, once the device reboot it went straight to fastboot and since then I haven´t been able to get it back working.
Are you manually flashing each partition?
Maybe try a 4.4.4 ROM.
Yes, I have. I´ve also tried other signed firmware that have a .bat file that run all by itself but neither way it worked. It comes up with the error message: Invalid signed Image and below Preflash Validation Fail
I am an android new-bie who hoped to root his phone.
I have a Moto e 2nd gen XT1506 eu(outus) 3g
while trying to root the phone i flashed TWRP img from adb after unlocking bootloader and proceeded for su zip.But when trying to boot for system it always boots to
twrp recovery(even from the option of boot to system in twrp).I tried resetting phone from stock recovery(after flashing it) which didnt work.Then i tried formatting dalvik cache,cache, (which i was unable to do as it showed that it was unable to mount /data).
Please help me turning my phone back to normal.
It seems that the problem may due to flashing twrp to boot
AP241099 said:
I am an android new-bie who hoped to root his phone.
I have a Moto e 2nd gen XT1506 eu(outus) 3g
while trying to root the phone i flashed TWRP img from adb after unlocking bootloader and proceeded for su zip.But when trying to boot for system it always boots to
twrp recovery(even from the option of boot to system in twrp).I tried resetting phone from stock recovery(after flashing it) which didnt work.Then i tried formatting dalvik cache,cache, (which i was unable to do as it showed that it was unable to mount /data).
Please help me turning my phone back to normal.
It seems that the problem may due to flashing twrp to boot
Click to expand...
Click to collapse
If i can get the stock boot.img file for my phone ,I may try flashing it to boot(i think that may solve my problem)
Hi there,
You'd be best served asking for help from the experts who own your device here:
E 2015 Q&A, Help & Troubleshooting
Before that see this guide: [GUIDE] Restore Moto E (2015) Stock Firmware
Good luck
I received a boot looped moto G from a friend and what infuriates me is that no matter what I do, nothing changes on the phone. NOTHING. Flash new recovery? Old one is still there. Flashed new modem, radio, boot images, boot logo [OKAY] and more yet it's as if the phone never budged. I wiped /data /system /cache too.
Not recognized on ADB
Recognized on mfastboot
Boots to recovery
Bootloader Unlocked
Any ideas what the issue is?
1.Which recovery have you tried ?? Before flashing new recovery have you erased the old one ("fastboot erase recovery <recovery name> " ). Have you tried twrp latest version by h2o ??
2. While flashing new rom, does recovery shows any error ??
3. Have you checked your partition ?? They may be corrupted..
Sent from my Moto G using Tapatalk
Facing the same problem here
I had dropped my Moto G in water accidentaly. After reviving it I was welcomed to CM12.1 with continuous error messages (process.com.xyz has stopped). So i decided to flash stock ROM and update my recovery while at it. But afer doing the necessary operations successfully I am greeted back to the same corrupted OS. Not 1 bit of data is changed. Please suggest a solution someone.
You can try flashing CM via TWRP again, this may cause the OS to boot correctly. However, generally emmc corruption can never be cured.
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.