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.
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
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
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
angrygamer1023 said:
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Click to expand...
Click to collapse
Try another recovery / another version. Did the trick for me and you have nothing to lose
I have 2 XT925s. I bricked one to the point that I could boot to fastboot but could not even get into stock recovery. I was running stock 4.4.2.
I did the following.
I got the DROID_RAZR_HD_Utility_1.41. I used the TWRP 2.7.1.0 in that utility specifically for XT925.
I used fastboot to manually flash TWRP into the recovery partition.
DO NOT reboot past boot menu. Right after flashing, boot into recovery. That should give you TWRP.
I used TWRP to Install CM11 snapshot. I had to manually flash into the modem partition, the modem file also obtained from the above utility. You will need to flash in gapps for 4.4.2.
That recovered the bricked phone.
Of note, I was able to flash TWRP in the other phone. Backed it up. Transfered the backed up OEM ROM into the phone running CM. And get it to run stock ROM.
I now have one running CM11, and one running stock 4.4.2. I'm just comparing battery life. I've noticed CM11 has a smaller memory footprint than stock 4.4.2.
Cheers
did not work for me anywhere to be found stock 4.4.2 recovery img for 926?
I have a Boost 1031 and I unlocked bootloader and rooted with no issues. Phone was 4.4.1 and auto-updated to 4.4.4. I installed TWRP and tried flashing CM13 which indicated 1031 was compatible. Couldn't install due to outdated bootloader version so followed post saying edit text out of rom to bypass and it will update automatically. I did, and it worked, but I just got the CM13 logo bootloop. Thought maybe I could go back to stock and take it slower with a stock 5.1 or GPE but can't "downgrade" now since CM13 did successfully flash.
via command in fastboot I am on bootloader version 411A.
I have tried:
adb sideloading factory image for Boost Falcon - failed due to partition error.
adb sideloading 5.1 optimized rom, CM12 and CM13 - failed due to not able to mount anything.
extracted and via fastboot:
4.4 stock factory image - successfully installed w/initial errors relating to downgrade as warned, stuck on 'unlocked bootloader' screen
5.1 optimized rom - successfully installed, stuck on loop of sad broken android on his side.
CWM recovery
3 versions of TWRP
Is there anything else I can try? I can still get into fastboot and the custom recovery.
Thanks!
static.chaos73 said:
I have a Boost 1031 and I unlocked bootloader and rooted with no issues. Phone was 4.4.1 and auto-updated to 4.4.4. I installed TWRP and tried flashing CM13 which indicated 1031 was compatible. Couldn't install due to outdated bootloader version so followed post saying edit text out of rom to bypass and it will update automatically. I did, and it worked, but I just got the CM13 logo bootloop. Thought maybe I could go back to stock and take it slower with a stock 5.1 or GPE but can't "downgrade" now since CM13 did successfully flash.
via command in fastboot I am on bootloader version 411A.
I have tried:
adb sideloading factory image for Boost Falcon - failed due to partition error.
adb sideloading 5.1 optimized rom, CM12 and CM13 - failed due to not able to mount anything.
extracted and via fastboot:
4.4 stock factory image - successfully installed w/initial errors relating to downgrade as warned, stuck on 'unlocked bootloader' screen
5.1 optimized rom - successfully installed, stuck on loop of sad broken android on his side.
CWM recovery
3 versions of TWRP
Is there anything else I can try? I can still get into fastboot and the custom recovery.
Thanks!
Click to expand...
Click to collapse
Try to flash the 5.1 Factory Firmware Image:
http://forum.xda-developers.com/showthread.php?t=2542219
http://forum.xda-developers.com/moto...mware-t3110795
From that point you can move on to custom ROMs if you wish
satanas17 said:
Try to flash the 5.1 Factory Firmware Image:
http://forum.xda-developers.com/showthread.php?t=2542219
http://forum.xda-developers.com/moto...mware-t3110795
From that point you can move on to custom ROMs if you wish
Click to expand...
Click to collapse
Yes I have tried that. The problem is that I can't flash anything because there is no recognized system. No matter what rom it is, it can't mount sd card, data, /dev/block/platform etc. After more research I think I may need to reformat the partitions but in adb I get an error of no superuser. I'm trying to see if I can do it in fastboot instead.
static.chaos73 said:
Yes I have tried that. The problem is that I can't flash anything because there is no recognized system. No matter what rom it is, it can't mount sd card, data, /dev/block/platform etc. After more research I think I may need to reformat the partitions but in adb I get an error of no superuser. I'm trying to see if I can do it in fastboot instead.
Click to expand...
Click to collapse
OK, finally got it working! I used fastboot to partition with the gpe image of the rom I was trying to flash, then fastboot to format. Then I went into recovery and tried to mount data/system/cache. Data was still not available, so I used recovery to format data and got it mounted. I tried a few different roms and finally was able to get cyanpop marshmallow to load up and run. I'm going to try and figure out what the difference is because I want CM13 nightly eventually. I tried to downgrade back to 4.4 stock but never could get past the downgrade errors when flashing in recovery, and flashing via fastboot or adb sideload would just fail.
Anyway, thanks for your help!
You seem to be making things more complicated than necessary. You should be aware Firmware Images can only be flashed via Fastboot. Flashing the GPE firmware image formatted userdata (/data) to EXT4. Stock ROMs will not boot if you have an EXT4 /data partition. See the FAQ in my Stock ROM collection thread.
lost101 said:
You seem to be making things more complicated than necessary. You should be aware Firmware Images can only be flashed via Fastboot. Flashing the GPE firmware image formatted userdata (/data) to EXT4. Stock ROMs will not boot if you have an EXT4 /data partition. See the FAQ in my Stock ROM collection thread.
Click to expand...
Click to collapse
OK that makes sense. I will read through your FAQ before attempting to flash anything else. Thank you for the information!