Moto G (1st Gen) - XT1033 - Unable to flash recovery/ROM (unlocked bootloader) - Moto G Q&A, Help & Troubleshooting

Hi All,
I have Moto G 1st Gen (XT1033), India in bootloop.
I have unlocked bootloader successfully. I can access bootloader menu where I am able to run fastboot/mfastboot commands from PC,
1. Flashing customer & stock recovery,
-twrp-3.0.2-0-falcon.img
-recovery-clockwork-6.0.4.7-falcon.img
-recovery-clockwork-touch-6.0.4.7-falcon.img​
Result: Does not give error but on rebooting the phone, stock recovery comes back with dead android with red exclamation mark
target reported max download size of 536870912 bytes
sending 'recovery' (7878 KB)...
OKAY [ 0.312s]
writing 'recovery'...
OKAY [ 0.140s]
finished. total time: 0.468s​2. flashing stock ROM
- XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xml.zip
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​
Result: Does not give error but on rebooting the phone, there is no change phone is in bootloop only...
2. flashing custom ROM after booting (unable to flash but can boot) with TWRP (twrp-3.0.2-0-falcon.img)
- Android6.0.1_NX_R10.3.3_MotoG2013.zip
- cm-13.0-20160617-NIGHTLY-falcon.zip
- cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon.zip
phone is detect as MTP when booting with TWRP which allows me to copy custom ROM to phone from PC.
using TWRP, trying to install ROMs as listed above.​
Result: it gets stuck forever in patching "patching system image unconditionally"
Can anyone suggest what could be wrong and how i can fix it?
Appreciate all the suggestion in advance.

Hey you can boot into fastboot which means that your phone is not hard bricked thats is a great news.
You can try wiping the partitions in the fastboot if the bootloader is unlocked
Try this in fastboot mode:
(Use mfastboot) :- http://forum.xda-developers.com/atta...1&d=1442444179
Code:
mfastboot erase system
mfastboot erase cache
mfastboot erase userdata
mfastboot erase recovery
mfastboot erase modemst1
mfastboot erase modemst2
Then install the stock rom or flash recovery then install a custom ROM.
Hit thanks if it worked..!
Stay Crazy

Try boot Twrp image and then flash Twrp image to the phone (from inside twrp, obviously). After that, select from menu "reboot to recovery". Phone should start twrp.
Format all partitions (advanced wipe) and install some custom rom and gapps.

@wald0rf, appreciate your suggestion.
As suggested, I did boot from TWRP and flashed TWRP (from inside TWRP). after that, after rebooting to recovery, I see stock recovery only (dead android)...

Hi @jignesh_shah. I'm facing the same issue. Did you find any solution as of now ?

JanardhanTS said:
Hi @jignesh_shah. I'm facing the same issue. Did you find any solution as of now ?
Click to expand...
Click to collapse
No, I have not find any solutions yet... looks like there is none!!!

jignesh_shah said:
No, I have not find any solutions yet... looks like there is none!!!
Click to expand...
Click to collapse
These are classic symptoms of corrupt (read only) emmc. There are multiple threads on this subject. I do know of one person who managed to flash CM13 via TWRP (perhaps using mfastboot boot twrp.img) and got that ROM to boot and run successfully. I suggest you try other ROMs, including a Stock-based one such as Identity Crisis 6.
One other thing to do is the following wipe via ADB: (ADB will work in TWRP - but you may need to be running linux)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​

@lost101, I went through many posts and did almost all the different suggestions.
1. flashing anything using TWRP gets stuck in "patching system image unconditionally"
2. I tried wiping entire flash, but gives i/o error
dd if=/dev/zero of=/dev/block/mmcblk0
dd: writing '/dev/block/mmcblk0': I/O error
7169+0 records in
7168+0 records out
3670016 bytes (3.5MB) copied, 2.781263 seconds, 1.3MB/s​
3. can you please point me to Identity Crisis 6 for XT1033? I checked on http://forum.xda-developers.com/moto-g/development/rom-identity-crisis-6-t3324595 it says its for XT1063/64/68...

@lost101,
I tried using idcrisis6_ds_v1.0.zip after booting with TWRP.
this time it gave different error.
symlink: no of symlinks failed = 1
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/idcrisis6_ds_v1.0.zip'
Updating partition details...
...done

@jignesh_shah. Where did you execute 'dd' commands ? On terminal ? Because I have CWM + terminal.
Regards
Janardhan TS
sent from Mi

JanardhanTS said:
@jignesh_shah. Where did you execute 'dd' commands ? On terminal ? Because I have CWM + terminal.
Regards
Janardhan TS
sent from Mi
Click to expand...
Click to collapse
using adb shell from PC.

Can you please tell me how to execute adb shell. I'm not sure debugging mode is active on multiple mobile.
Regards
Janardhan TS
sent from Mi

JanardhanTS said:
Can you please tell me how to execute adb shell. I'm not sure debugging mode is active on multiple mobile.
Regards
Janardhan TS
sent from Mi
Click to expand...
Click to collapse
i dont remember exact steps but i guess nothing tricky - connect your phone with PC using USB and boot using TWRP (allow read/write). open command line, go to path where you have adb binary and supporting DLL files in the folder (I have attached with this message if you dont have) and run command "adb shell".
best luck.

jignesh_shah said:
i dont remember exact steps but i guess nothing tricky - connect your phone with PC using USB and boot using TWRP (allow read/write). open command line, go to path where you have adb binary and supporting DLL files in the folder (I have attached with this message if you dont have) and run command "adb shell".
best luck.
Click to expand...
Click to collapse
I don't have TWRP. i have CWM recovery. Do you know how to Execute using CWM recovery

JanardhanTS said:
I don't have TWRP. i have CWM recovery. Do you know how to Execute using CWM recovery
Click to expand...
Click to collapse
Sorry for the late response.
I did not have luck with CWM so cant say. But getting TWRP should not be issue...

I can't even change my recovery.
Regards
Janardhan TS
sent from Mi

JanardhanTS said:
I can't even change my recovery.
Regards
Janardhan TS
sent from Mi
Click to expand...
Click to collapse
to use TWRP, you need not to flash. you can boot using command mfastboot boot twrp.img
However, unable to flash recovery does not seem good sign. It may be due to corrupted flash (I am also facing same issue). Only solution I have come across is to replace motherboard, which is not easy & cheap to get!!!

Thanks. I'll try it out.
Regards
Janardhan TS
sent from Mi

Related

[Help] Moto G 4G peregrine issues

Hello,
I have followed the tutorials to unlock the bootloader of my moto G 4G : the bootloader is unlocked and I have removed the message when starting the phone with this tutorial : forum.xda-developers.com/moto-g/4g-development/logo-remove-bootloader-unlocked-warning-t2794104
Anyway, I would like now to install a recovery CWM with this tutorial :
http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-cwm-6-0-5-0-t2818161
But when I do so, I have the following message on the screen of my phone : "Mismatch partition size (recovery)"
And when I boot on the bootloader then select recovery but nothing appears, just a black screen.
The status code of my bootloader is : 3 and it says "Device is unlocked".
I can boot to CWM from the computer with : fastboot boot recovery.img
but when I type : fastboot flash recovery CWM-6.0.5.0-peregrine.img I get this error.
Can someone help me please ?
Thank you in advance.
Ferguson35000 said:
Hello,
I have followed the tutorials to unlock the bootloader of my moto G 4G : the bootloader is unlocked and I have removed the message when starting the phone with this tutorial : forum.xda-developers.com/moto-g/4g-development/logo-remove-bootloader-unlocked-warning-t2794104
Anyway, I would like now to install a recovery CWM with this tutorial :
http://forum.xda-developers.com/moto-g/4g-development/recovery-unofficial-cwm-6-0-5-0-t2818161
But when I do so, I have the following message on the screen of my phone : "Mismatch partition size (recovery)"
And when I boot on the bootloader then select recovery but nothing appears, just a black screen.
The status code of my bootloader is : 3 and it says "Device is unlocked".
I can boot to CWM from the computer with : fastboot boot recovery.img
but when I type : fastboot flash recovery CWM-6.0.5.0-peregrine.img I get this error.
Can someone help me please ?
Thank you in advance.
Click to expand...
Click to collapse
I'm stil stuck.
Is there anybody able to help me ?
Thank you.
Ferguson35000 said:
I'm stil stuck.
Is there anybody able to help me ?
Thank you.
Click to expand...
Click to collapse
I got this problem when installing CWM too. I believed the problem is in this line:
fastboot flash recovery CWM-6.0.5.0-peregrine.img
Click to expand...
Click to collapse
instead, you could try this:
fastboot boot flash recovery CWM-6.0.5.0-peregrine.img
When I did this, it worked. Give it a try. You could also try this little program, I changed CWM to TWRP with it.
http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
UncolourTV said:
I got this problem when installing CWM too. I believed the problem is in this line:
instead, you could try this:
fastboot boot flash recovery CWM-6.0.5.0-peregrine.img
When I did this, it worked. Give it a try. You could also try this little program, I changed CWM to TWRP with it.
http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
Click to expand...
Click to collapse
Hello Hello,
Thank you for answering.
The command : fastboot boot flash recovery CWM-6.0.5.0-peregrine.img doesn't work because there is too much arguments. It gives me that answer :
cannot load 'flash': No such file or directory
I retried the right command but still the same problem.
I also tried the small program given by this URL on linux : http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
My computer under Ubuntu fails to recognize the device. The device shown is empty.
I will try it on windows then come back here to tell you what happened.
Ferguson35000 said:
Hello Hello,
Thank you for answering.
The command : fastboot boot flash recovery CWM-6.0.5.0-peregrine.img doesn't work because there is too much arguments. It gives me that answer :
cannot load 'flash': No such file or directory
I retried the right command but still the same problem.
I also tried the small program given by this URL on linux : http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710
My computer under Ubuntu fails to recognize the device. The device shown is empty.
I will try it on windows then come back here to tell you what happened.
Click to expand...
Click to collapse
I have the same issue with this program under linux or windows, it doesn't recognize my device. I have activated USB debug, tried under bootloader or with the phone normally started but nothing better.
only fastboot boot recovery.img works.
You have to flash the recovery with mfastboot from motorola when flashing partitions else you will get the size mismatched error.
Standard fastboot is only good for basic things such as getvar etc.
Always flash with mfastboot and it will not error out.
So the command will then be mfastboot flash recovery CWM-6.0.5.0-peregrine.img which should then work without issues
hacktrix2006 said:
You have to flash the recovery with mfastboot from motorola when flashing partitions else you will get the size mismatched error.
Standard fastboot is only good for basic things such as getvar etc.
Always flash with mfastboot and it will not error out.
So the command will then be mfastboot flash recovery CWM-6.0.5.0-peregrine.img which should then work without issues
Click to expand...
Click to collapse
Thank you for answering.
I will try this then come back.
Ferguson35000 said:
Thank you for answering.
I will try this then come back.
Click to expand...
Click to collapse
Same error :
I still have the mismatch thing with mfastboot ...
Have you tried going back to a stock 4.4.4 if you have ota'd to 4.4.4 you need 4.4.4 stock image.
hacktrix2006 said:
Have you tried going back to a stock 4.4.4 if you have ota'd to 4.4.4 you need 4.4.4 stock image.
Click to expand...
Click to collapse
Hello, I have bought the phone less than one month ago.
It was directly on 4.4.4 after unpacking.
Have you tried renaming the CWM file? Maybe the "-" are a problem although I highly doubt it. Did you try re downloading the file? Running the command window as an administrator? Last resort, you could use TWRP, I'm running on this currently and haven't had any problems installing/flashing ROMs with it and imo prefer it over CWM.
Click to expand...
Click to collapse
I have tried both and they both have the same problem :/ CWM as well as TWRP...
Still no idea what happens.
same problem
I got the same problem using mac..
Impossible to install cwm or twrp also.. i cannot enter in the recovery mode any more
the boot loader is unlocked. I don't know whats going on
kosamuky said:
I got the same problem using mac..
Impossible to install cwm or twrp also.. i cannot enter in the recovery mode any more
the boot loader is unlocked. I don't know whats going on
Click to expand...
Click to collapse
Did you find any solutions for this ?
I'm still stuck
Is it normal when entering the bootloader to have the message :
"Device is UNLOCKED. Status code: 3 "
Is it the right status code ?
Thank you
Back to stock
Ferguson35000 said:
Did you find any solutions for this ?
I'm still stuck
Is it normal when entering the bootloader to have the message :
"Device is UNLOCKED. Status code: 3 "
Is it the right status code ?
Thank you
Click to expand...
Click to collapse
Yes its normal if you have unlocked your bootloader
To get back to stock, download a stock Fw for your device model and region, you can find a link for one if you enter the moto g section of this site and head to moto 4g lte android development section (only section specifically for peregrine model) unpack the fw files into your fastboot directory (windows) reboot your phone to fastboot mode (where u saw the status code) then press control + shift + right click to launch a command prompt window here (from within fastboot directory in windows) then copy and paste these fastboot commands 1 by 1 pressing enter each time until compete.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
So you mean, it is compulsory to have stock ROM in order to install the recovery ?
Because my problem is not to return to stock, it is to install a proper recovery (CWM or TWRP) in order to boot on it without my computer.
Thanks for your help
No but I think your problem is you have corrupt the recovery partition size maybe through bad flash or something so ur unable now to flash a recovery as the partition size is for different device or damaged and flashing cwm will no longer work as the cwm image is too big or too small for the allocation assigned to it as the devices core partition table has changed (can happen when u flash something for the falcon when you have a peregrine), I would flash back to stock via that method to restore to stock partition sizes and then reroot and flash cwm again after, just a guess from my own understanding.
Sent from my XT1039 using XDA Free mobile app
Guys I had the same trouble installing the recovery with the mismatched partition size message. This message is normal and the recovery is already installed on your device. The problem i had when selecting the recovery with the following black screen was that I used the Power Button instead of the up Button.
5) using volume down scroll to recovery and then use volume up to select

[Q&A] Moto G x1032 HARD BRICKED since 4.4.4 GPE to Lollipop

Hi all,
Since Sunday I try to solve the hard brick of my Moto G XT1032. I was on a rom GPE in 4.4.4 (EU) and by making the MAJ Lollipop during the sunday, the tel reboot on the logo Motorola and nothing more.
I tested severals tutos on XDA and many french websites, as:
Http: // forum.xda-developers.com / showthread.php? T=2633272
http: // forum.xda-developers.com/moto-g/help/mo to-g-hard-brick-lollipop-t2998124
And a lot of the others...but nothing!
Well, I said myself it doesn't matter because mototool repair the tel with no problems, as usual. But not, many errors when I try of downgrade in 4.4.2 or in 4.4.4 with it. I tried to flash (cache/ system / data / Dalvik) with CWM and TWRP with one tens of versions all in all and impossible to make no anything to put back. I tried to install many rom's, always the same.
I have errors as " remote failure ", impossible of mount the partitions system/cache, hab check failed and more more more, i don't remember the other's errors...
I cannot copy files (like a rom) via ADB to the tel in mode bootloader and I don't know what to do anymore of the whole...
If you have an idea, I am interested because there I think that except the SAV ... i'am in bull***t. :silly:
Thanks to all of your help and good week!
(sorry for my poor english)
Try manually flashing a stock 4.4.4 ROM , not a 4.4.2 ROM, for your phone. You may not be able to flash motoboot if the bootloader on your phone is newer than the bootloader you are trying to flash.
audit13 said:
Try manually flashing a stock 4.4.4 ROM , not a 4.4.2 ROM, for your phone. You may not be able to flash motoboot if the bootloader on your phone is newer than the bootloader you are trying to flash.
Click to expand...
Click to collapse
I try but the problem it's adb, because it's impossible to synchronize my phone with it.
When i try "adb reboot-bootloader" in a shell, i have the error "device not found".
And it's impossible to continue the tutorial :
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
What is the solution for this?
adb reboot bootloader works if your phone is booted and you have debugging enabled.
ADB commands don't work when the phone is in fastboot mode.
Put your phone into fastboot mode, connect it to your computer, type in "fastboot devices" and your's phone serial # should appear on screen.
audit13 said:
adb reboot bootloader works if your phone is booted and you have debugging enabled.
ADB commands don't work when the phone is in fastboot mode.
Put your phone into fastboot mode, connect it to your computer, type in "fastboot devices" and your's phone serial # should appear on screen.
Click to expand...
Click to collapse
OK. I have a phone serial who appear on screen (with the command "fastboot devices"), but with the command "adb devices", i have no serial, so no devices attached...
EDIT : Into TWRP Recovery, i have the adb serial too
ok, now it's good I the phone turn on a retail rom 4.4.4.
For all those who have experienced the problem (a GPE 4.4.2 update to 4.4.4 and 5.0.1), the procedure is "simple".
Install adb+fastboot and copy the rom into the folder.
Fisrt, put your phone into bootloader mode and check the command 'fastboot devices"; you must have a serial into the shell. Boot on the TWRP recovery (2.7.1.1) and type the command into the shell "adb devices"; again, you must have a serial. If it's OK, format cache/system/data/dalvik and reboot the phone into the bootloader.
In my case, i use the rom RETAIL-FR_4.4.4 OTA.
Code:
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot erase cache
fastboot erase userdata
fastboot reboot
IF this does not work , it is still possible to achieve a different manipulation .
Take CWM recovery (Philz Touch for example) and try to push a rom with adb.
@+
You can't use adb commands when the phone is in fastboot mode. THis is why adb devices returns nothing.
Glad you got it working.

Stuck at Motorola Bootlogo after Security update

Device: XT1031 converted to XT1028 for use on Page Plus. Bootloader unlocked. Rooted with SuperSU 2.46 Running Stock Verizon 5.1 ROM 221.26.7.falcon_cdma.Verizon.en.US
Recovery: TWRP 2.8.7.0
I accepted the new security update - http://forum.xda-developers.com/moto-g/general/moto-g-1st-gen-actually-security-update-t3362323
and when it tried to install the update, the phone just rebooted into TWRP Recovery.
So I flashed stock recovery from the Verizon 5.1 ROM and then tried the update again. This time it completed the update and rebooted but is now stuck at the Motorola bootlogo.
I'm able to reboot into fastboot.
I tried flashing system.img_sparsechunk.0, .1, .2, and .3, and rebooted but there is no change.
What can I try to get past this?
Before starting this I made a backup using TWRP Recovery, can I reinstall TWRP and restore that backup?
it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If the TWRP backup is still on phone, it might be worth transferring it to a PC / external OTG usb drive, as using the following fastboot command will erase it, along with everything else on internal storage:
fastboot command erase userdata​
lost101 said:
it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If the TWRP backup is still on phone, it might be worth transferring it to a PC / external OTG usb drive, as using the following fastboot command will erase it, along with everything else on internal storage:
fastboot command erase userdata​
Click to expand...
Click to collapse
The TWRP backup was saved to an external OTG USB drive, so that's safe.
I was originally going to do the same as I did for the last update - http://forum.xda-developers.com/showpost.php?p=63976723&postcount=109 but tried it first and when it went straight to recovery, I figured I needed to flash stock recovery. I also figured I needed to flash system also, but it through me off when the sparsechunks were numbered 0 - 3 instead of 1 - 4.
I didn't see any errors when I did the flashes.
Right now my battery is drained all the way to 0%. Hopefully it charges back up.
I appreciate the response. Thanks.
Do all fastboot commands including erase userdata. Change sparsechunk names to match the files in the firmware folder you have downloaded. Phone should charge on fastboot screen, but probably not if at a very low percentage.
lost101 said:
Do all fastboot commands including erase userdata. Change sparsechunk names to match the files in the firmware folder you have downloaded. Phone should charge on fastboot screen, but probably not if at a very low percentage.
Click to expand...
Click to collapse
I'm using this stock ROM: XT1028_FALCON_VERIZON_5.1_LPB23.13-33.7_cid2_CFC.xml.zip
The sparsechunk files in that zip are named:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
and I need to rename them:
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
system.img_sparsechunk4
Correct?
Then I would run the following commands one at a time and checking for an OK on each, correct?
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
After that I can check that I can boot into the OS and then I can flash TWRP and restore my saved backup.
Does that sound right?
Thanks.
Don't rename the sparsechunk files. I said change the name when doing the fastboot commands.
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3​
Edit: Use mfastboot: https://www.androidfilehost.com/?fid=24052804347778493
lost101 said:
Don't rename the sparsechunk files. I said change the name when doing the fastboot commands.
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3​
Edit: Use mfastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
OK, I got an error on the first one I tried:
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>mfastboot devices
TA965000I5 fastboot
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.318s
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>
And on the Moto G's screen:
cmd: getvar:max-sparse-size
cmd: download:00008000
cmd: flashartition
version downgraded for primary_gpt
Is that a problem?
Try flashing the latest available XT1028 Verizon 5.1 Factory Firmware Image:
XT1028_FALCON_VERIZON_5.1_LPBS23.13-33.7-2_cid2​
lost101 said:
Try flashing the latest available XT1028 Verizon 5.1 Factory Firmware Image:
XT1028_FALCON_VERIZON_5.1_LPBS23.13-33.7-2_cid2​
Click to expand...
Click to collapse
OK, that worked. I was able to flash back to the stock ROM.
I'm wondering if there would be any issue if I were to flash TWRP recovery and restore my saved backup?
Thanks for your help.
bw 1 said:
I'm wondering if there would be any issue if I were to flash TWRP recovery and restore my saved backup?
Click to expand...
Click to collapse
I don't personally restore TWRP backups because of bad experiences, but as long as you are using the latest available TWRP you should be okay.
lost101 said:
I don't personally restore TWRP backups because of bad experiences, but as long as you are using the latest available TWRP you should be okay.
Click to expand...
Click to collapse
I decided to start over and not try to recover from the saved file. I don't think there was anything on there that I really needed anyway. All my pictures and stuff was synced to Google.
I'm guessing that I ran into a problem by not flashing the 4 system sparsechunks from the stock ROM to remove root and I wasn't able to flash the same 5.1 that I had on there since it was updated. Flashing the latest newer build Verizon ROM worked because it was the same as what was contained in the update.
I didn't receive another OTA update and system update shows my phone as up to date with:
Android version: 5.1
Android security patch level: 2016-03-01
System version: 221.201.2.falcon_cdma.Verizon.en.US
Build number: LPBS23.13-33.7-2
I'm back to having a working phone. Thanks for your help. Hopefully this will help others too.

Moto G (India) - XT1033 - can't FLASH anything (bootloop)

Hi All,
Phone - Moto G 1st Gen (India)
Model - XT1033 (falcon)
data backup - not required. Trying to bring phone to life is only objective. So anyone has any suggestion other than what I am trying below and will make phone alive I do not mind trying.
Phone was working very well before three days . After I did soft reset, it is going in bootloop only.
1. I can access bootloader and recovery menu.
2. I wiped cache, data/factory reset but did not help
3. after reading many threads on xda, so far i did following,
a. unlocking bootloader - done successfully, i can see status code -3 on reboot
b. flashing custom recovery TWRP - shows success on command line but neither i see teamwin logo nor twp recovery (goes back to stock recovery or shows black screen). I also tried CWM but same result!!!
mfastboot.exe flash recovery twrp-3.0.2-0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (9330 KB)...
OKAY [ 0.377s]
writing 'recovery'...
OKAY [ 0.185s]
finished. total time: 0.577s​
c. tried booting in twrp successfully, i can access TWRP
mfastboot.exe boot twrp-3.0.2-0-falcon.img
d. flash custom rom
- MTP is enabled by TWRP so moto g is detected in windows so copied Android6.0.1_NX_R10.3.3_MotoG2013.zip
- used TWRP to install it but gets stuck in "patching system image unconditionally" forever...
- Tried other ROMs such as XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xml with following steps, shows success but after rebooting I dont see anything happened.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot​​
It seems as all the tools/commands are executed successfully but not able to make changes in flash.
can anyone pls. point me or guide me for the solution ahead?
Appreciate your support in advance.
Best Regards,
Jignesh Shah
jignesh_shah said:
Hi All,
Phone - Moto G 1st Gen (India)
Model - XT1033 (falcon)
data backup - not required. Trying to bring phone to life is only objective. So anyone has any suggestion other than what I am trying below and will make phone alive I do not mind trying.
Phone was working very well before three days . After I did soft reset, it is going in bootloop only.
1. I can access bootloader and recovery menu.
2. I wiped cache, data/factory reset but did not help
3. after reading many threads on xda, so far i did following,
a. unlocking bootloader - done successfully, i can see status code -3 on reboot
b. flashing custom recovery TWRP - shows success on command line but neither i see teamwin logo nor twp recovery (goes back to stock recovery or shows black screen). I also tried CWM but same result!!!
mfastboot.exe flash recovery twrp-3.0.2-0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (9330 KB)...
OKAY [ 0.377s]
writing 'recovery'...
OKAY [ 0.185s]
finished. total time: 0.577s
c. tried booting in twrp successfully, i can access TWRP
mfastboot.exe boot twrp-3.0.2-0-falcon.img
d. flash custom rom
- MTP is enabled by TWRP so moto g is detected in windows so copied Android6.0.1_NX_R10.3.3_MotoG2013.zip
- used TWRP to install it but gets stuck in "patching system image unconditionally" forever...
- Tried other ROMs such as XT1033_FALCON_ASIA_DS_5.1_LPBS23.13-56-2_cid7_CFC.xml with following steps, shows success but after rebooting I dont see anything happened.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
It seems as all the tools/commands are executed successfully but not able to make changes in flash.
can anyone pls. point me or guide me for the solution ahead?
Appreciate your support in advance.
Best Regards,
Jignesh Shah
Click to expand...
Click to collapse
Which android version u have in your mobile before bootloop.....?
skyrajparmar said:
Which android version u have in your mobile before bootloop.....?
Click to expand...
Click to collapse
It was android lollipop...
skyrajparmar said:
Which android version u have in your mobile before bootloop.....?
Click to expand...
Click to collapse
It was android lollipop...
jignesh_shah said:
It was android lollipop...
Click to expand...
Click to collapse
1-Reboot into recovery (twrp)
2-Wipe data system cache
3-Flash cm13 zip file.....
4-reboot system
Enjoy
@skyrajparmar, appreciate your response.
I tried your suggestion but result is same.
details:
1-Reboot into recovery (twrp) - success
2-Wipe data system cache - cleaned data/dalvik cache/cache/system successfully using TWRP
3-Flash cm13 zip file..... - using TWRP copied cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon.zip to internal storage (over MTP) and installing using TWRP. It stays in "patching system image unconditionally" forever... I waited for more than 30 minutes and still its going on...
4-reboot system - not done as it does not come out from previous step
Can you suggest if I have missed anything or doing something incorrect or any thing else?
jignesh_shah said:
@skyrajparmar, appreciate your response.
I tried your suggestion but result is same.
details:
1-Reboot into recovery (twrp) - success
2-Wipe data system cache - cleaned data/dalvik cache/cache/system successfully using TWRP
3-Flash cm13 zip file..... - using TWRP copied cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon.zip to internal storage (over MTP) and installing using TWRP. It stays in "patching system image unconditionally" forever... I waited for more than 30 minutes and still its going on...
4-reboot system - not done as it does not come out from previous step
Can you suggest if I have missed anything or doing something incorrect or any thing else?
Click to expand...
Click to collapse
reasons
1-may be your cm12.1 zip file is bad..... try with cm13
2-your system partition may be damaged (fix-repair system n data partition in twrp )
@skyrajparmar,
1. cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon.zip is a snapshot and all CM13 are nightly. since i wanted to use stable than beta, i tried CM12.1
2. as you suggested, i tried wipe ->advanced wipe -> data - success
3. as you suggested, i tried wipe ->advanced wipe -> system - fail with error 4 - unable to repair system (pls see attached image)
jignesh_shah said:
@skyrajparmar,
1. cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon.zip is a snapshot and all CM13 are nightly. since i wanted to use stable than beta, i tried CM12.1
2. as you suggested, i tried wipe ->advanced wipe -> data - success
3. as you suggested, i tried wipe ->advanced wipe -> system - fail with error 4 - unable to repair system (pls see attached image)
Click to expand...
Click to collapse
1-First convert system into f2fs format 2-now convert system into e4ft
3-try again repair function
Q had u tried cm13.....?
@skyrajparmar, as suggested,
1. converting to f2fs - on phone it shows success but when I press back it shows /system as ext4 only. should not it change to f2fs? pls. refer images...
2. converting to ext4 ( i assume there is a typo in your reply where you mentioned e4ft)
3. trying to repair - same error
I am downloading CM13, it will take few more minutes before I can try it...
jignesh_shah said:
@skyrajparmar, as suggested,
1. converting to f2fs - on phone it shows success but when I press back it shows /system as ext4 only. should not it change to f2fs? pls. refer images...
2. converting to ext4 ( i assume there is a typo in your reply where you mentioned e4ft)
3. trying to repair - same error
I am downloading CM13, it will take few more minutes before I can try it...
Click to expand...
Click to collapse
Okay.... try cm13... then reply me..... i m waiting
@skyrajparmar, as suggested, trying cm-13.0-20160617-NIGHTLY-falcon.zip and its stuck into 'patching system image unconditionally...'
FYI- before this, i booted with TWRP and cleaned cache/dalvik/data etc. as usual...
jignesh_shah said:
@skyrajparmar, as suggested, trying cm-13.0-20160617-NIGHTLY-falcon.zip and its stuck into 'patching system image unconditionally...'
FYI- before this, i booted with TWRP and cleaned cache/dalvik/data etc. as usual...
Click to expand...
Click to collapse
Now i m understand whole situation......
System partition of your mobile damaged........ if mobile is still on warranty then send it to service centre
R u living in gujarat.....?
hmmm, thats what i feared.... Not in warranty as its been 2 yrs now.
btw, i m from ahmd but in pune...
thanks for all your support and help....
is there anything else can be done?
jignesh_shah said:
hmmm, thats what i feared.... Not in warranty as its been 2 yrs now.
btw, i m from ahmd but in pune...
thanks for all your support and help....
is there anything else can be done?
Click to expand...
Click to collapse
May be someone's moto g system partition backup help u......
I think i can manage to get /system partition from working motog from someone.
would it be possible for you to provide working steps to do after that?
thanks in advance...
jignesh_shah said:
I think i can manage to get /system partition from working motog from someone.
would it be possible for you to provide working steps to do after that?
thanks in advance...
Click to expand...
Click to collapse
Copy that backup in pendrive(twrp>backups).... n connect pendrive to your moto g .... n restore backup....... but before backup check md5 create box (don't create md5)
if u want it in other moto g Backup must be without md5
Don't say thanks...hit thanks
@skyrajparmar,
is there any difference between using someone's system folder and following commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
would not above list of commands will overwrite /system partition?
I am asking because I have already tried above commands with much of the help!!!
jignesh_shah said:
@skyrajparmar,
is there any difference between using someone's system folder and following commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
would not above list of commands will overwrite /system partition?
I am asking because I have already tried above commands with much of the help!!!
Click to expand...
Click to collapse
Did u tried restore system partition of other moto g......?
No, I am still trying to get /system. I have not got succeeded with getting /system partition as most of the people I know have unrooted device.

Need help to install stock ROM on Moto G 2013 Falcon

Hi guys,
Im from the UK and I have a Moto G XT1032 device which was running Cyanogenmod 12 up until yesterday when I decided to re-install the stock rom. Unfortunately, I have well and truly botched it. The current situation is that I have TWRP set up as the recovery image, so I can get into 'AP Fastboot Flash Mode (S)' OR into TWRP.
I accidentally wiped the 'system' via TWRP which seems to have caused most of my problems. I have tried to install the stock rom using a flashable zip (which failed) and I have also tried around 10 times to install the stock rom using the fastboot commands:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
#fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
When I try to do a basic wipe using TWRP, this is what shows up: hxxps://s27.postimg.org/r1dax21mb/falcon.jpg (change xx for tt, I don't yet have 10 posts so I cannot post links)
I just cannot seem to get the stock rom installed and booting no matter what I try. Can someone please work with me to get this sorted?
I would very, very much appreciate the help.
Thank you
Ok so i've managed to fix the 'unable to mount storage' issue via TWRP. I changed 'data' to EXT4 and I don't get any errors now.
But the problem is, for whatever reason, I am just unable to install a stock rom. I've used tutorials and still cannot seem to get a stock rom to load/work.
I used fastboot to install the rom files is this zip: XT1032_FALCON_TESCOGBSL_5.1_LPBS23.13-56-2_cid7_CFC.xml.zip
When I do a normal boot it gets stuck on 'Warning bootloader unlocked'
When I go to 'recovery', it boots up to a dead android which says 'no command'
When I go to factory restore, it gets stuck on the 'Warning bootloader unlocked' screen
What am I doing wrong?
edit: I even tried sideloading cyanogenmod and it said it was successful, but then it boots up to TWRP. Totally confused! In desperate need of help.
EDIT: I have now made progress. Here are my basic instructions:
put all the files from the zip file in a folder
put mfastboot.exe files into the same folder
install TWRP, erase
run bat file (add/remove sparse depending on files)
reboot and wait. Should work
I have managed to install the OS but wifi isn't working. And i'm now learning about a file called persist that I need to look into regarding wifi.

Categories

Resources