Database Info

Moto G won't boot; can't flash stock firmware.

Hi folks,
first I apologies for my English!
I have some problems with my Moto G. Bought it very cheap, because it wasn't able to power up.
What I had done already:
It's possible to access the bootloader again. Then I tried to flash a stock firmware.
I got the following error in cmd: (for DE an EU Retail)
C:\Users\Stardust\Desktop\Androidzeug\Moto G\RETAIL-EU_4.4.2_KLB20.9-1.10-1.9_ci
d7_CFC_1FF_v8.xml>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (251136 KB)...
OKAY [ 8.112s]
writing 'system'...
OKAY [ 11.918s]
finished. total time: 20.030s
C:\Users\Stardust\Desktop\Androidzeug\Moto G\RETAIL-EU_4.4.2_KLB20.9-1.10-1.9_ci
d7_CFC_1FF_v8.xml>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (249008 KB)...
OKAY [ 8.034s]
writing 'system'...
OKAY [ 9.454s]
finished. total time: 17.503s
C:\Users\Stardust\Desktop\Androidzeug\Moto G\RETAIL-EU_4.4.2_KLB20.9-1.10-1.9_ci
d7_CFC_1FF_v8.xml>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (214009 KB)...
OKAY [ 6.911s]
writing 'system'...
(bootloader) Failed to validate sparse image
OKAY [ 18.330s]
finished. total time: 25.241s
Click to expand...
Click to collapse
And the Moto G bootloader tells me:
"PIV hash validation failed for PIV entry 0"
Mainly I tried this with many of DE, EU and GB Retails. Also US. (I live in germany)
DE and EU I got the same error. With US the bootloader shows some more errors.
At this state I can try to boot but got sucked in a bootloop sometimes or the Moto G get stacked in a blackscreen after the "bootloaderunlock-warning-logo"
Then i flashed a CWM recovery. And it's possible to enter the Recovery.
And this is the point where i don't know what to do.
I can access bootloader and recovery but can't flash a stock firmware.
Please help me!
PS: Want to past the errors when I flash: US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml
bootloader inside Moto G:
hab check failed for boot
hab check failed for recovery
hab check failed for system
Invalid PIV signed system image
cmd (last system_sparse.img):
(bootloader) Failed to validate sparse image

ikarugaski said:
Hi folks,
first I apologies for my English!
I have some problems with my Moto G. Bought it very cheap, because it wasn't able to power up.
What I had done already:
It's possible to access the bootloader again. Then I tried to flash a stock firmware.
I got the following error in cmd: (for DE an EU Retail)
And the Moto G bootloader tells me:
"PIV hash validation failed for PIV entry 0"
Mainly I tried this with many of DE, EU and GB Retails. Also US. (I live in germany)
DE and EU I got the same error. With US the bootloader shows some more errors.
At this state I can try to boot but got sucked in a bootloop sometimes or the Moto G get stacked in a blackscreen after the "bootloaderunlock-warning-logo"
Then i flashed a CWM recovery. And it's possible to enter the Recovery.
And this is the point where i don't know what to do.
I can access bootloader and recovery but can't flash a stock firmware.
Please help me!
PS: Want to past the errors when I flash: US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml
bootloader inside Moto G:
hab check failed for boot
hab check failed for recovery
hab check failed for system
Invalid PIV signed system image
cmd (last system_sparse.img):
(bootloader) Failed to validate sparse image
Click to expand...
Click to collapse
Those Errors are supposed to be normal my Friend!
They shouldn't be an issue!
Did you stop at the error? or did you complete the process?

Thaks for the answer!
Yes, I run it several times until the end. Just followed the "Moto G - Restore stock firmware" guide.
But this little G beast won't boot up.
Sometimes it does something like a bootloop and sometimes it ends in a blackscreen after the logo.
But then.... nothing.

ikarugaski said:
Thaks for the answer!
Yes, I run it several times until the end. Just followed the "Moto G - Restore stock firmware" guide.
But this little G beast won't boot up.
Sometimes it does something like a bootloop and sometimes it ends in a blackscreen after the logo.
But then.... nothing.
Click to expand...
Click to collapse
You own a DE Retail correct?
I'll help you after I write tomorrow's exam

Hi, try this guide, it worked for me.
https://www.youtube.com/watch?v=laU6NQ0LxR0

@deej_roamer
good luck for your exam!
Yeah, I think its an Retail, but maybe it could be an "O2 Germany" (the Moto bill says something of an O2 Combo). As I sayed I buyed it bricked.
Take youre time. I don't have freetime during weekend for the G.
Thanks for the link kirmr. I'll have a look.

I own a Moto G from O2 myself, however I was able to flash the regular german retail version without any errors (except for removing O2's bloatware, but I wouldn't exactly count that as an error ).
You might want to try redownloading the rom, extract it or try the german retail version. The error simply says that the disk image could not be validated. This could be because the sparse-images are defect, got written incorrectly or there might be an actual defect on the disk.

ikarugaski said:
@deej_roamer
good luck for your exam!
Yeah, I think its an Retail, but maybe it could be an "O2 Germany" (the Moto bill says something of an O2 Combo). As I sayed I buyed it bricked.
Take youre time. I don't have freetime during weekend for the G.
Thanks for the link kirmr. I'll have a look.
Click to expand...
Click to collapse
Did you try flshing this firmware?
Thanks for the wishes though!
If that doesnt work!
Please post your bootloader info. Copy what's written when bootloader boots.
That would give a better view!
EDIT: IF you are a lazy ass like me and dont wont to type. I suggest dump output of "fastboot getvar all" here

I'm back and now we can solve the problem hopefully!
I'll post a picture where you can see all firmware i had tried. (thats why i'm thinking all of them can't be defect. )
As you can see the one you suggested is in that list.
Just flashing the firmware again than i'll past the bootloader info here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

That's the answer of the getvar all command:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ***
(bootloader) cid: 0x0007
(bootloader) uid: 59D062020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ***
(bootloader) meid:
(bootloader) date: 01-24-2014
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 6 6: 7: 5 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.3/14.10.0Q3.X-76-LGG-11/57:user/
(bootloader) ro.build.fingerprint[2]: release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.14.91.11.falcon_umts
(bootloader) ro.build.version.full[1]: .Retail.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2_RB2.04.03
(bootloader) ro.build.version.qcom[1]: .00.129.057
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-g7161c60 ([email protected]
(bootloader) kernel.version[1]: l93lnxdroid92) (gcc version 4.7 (GCC) )
(bootloader) kernel.version[2]: #1 SMP PREEMPT Fri Oct 25 00:41:55 CDT 2
(bootloader) kernel.version[3]: 013
(bootloader) sdi.git: git=MBM-NG-V41.05-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.05-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.05-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V41.05-0-g11658be
(bootloader) aboot.git: git=MBM-NG-V41.05-0-gf4ab363
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.109s
Click to expand...
Click to collapse

I have Problems since months to Flash Stock JB or Kitkat. Every Time if i try to Boot, the Phone get stucked..
Only GPE Fastboot Flash Works great for me. After this i van Flash Every Rom with twrp..
Gesendet von meinem Moto G mit Tapatalk

Just now i tried to install something via TWRP / CWM (sideload because i had no assecc
Both are
- unable to mount /system
- unable to mount /data
- unable to mount /cache

ikarugaski said:
Just now i tried to install something via TWRP / CWM (sideload because i had no assecc
Both are
- unable to mount /system
- unable to mount /data
- unable to mount /cache
Click to expand...
Click to collapse
Format all of them! i mean /system /data /cache

I am unable to install Stock Firmware on My MOTO G
hydromän said:
I have Problems since months to Flash Stock JB or Kitkat. Every Time if i try to Boot, the Phone get stucked..
Only GPE Fastboot Flash Works great for me. After this i van Flash Every Rom with twrp..
Gesendet von meinem Moto G mit Tapatalk
Click to expand...
Click to collapse
Plz read this .... Give A Solution ... I hope U can Solve This Problem
I did following steps....
1. Installed motarola usb drivers, minimal adb drives and Adroid sdk
2.Extracted stock firmware by using win.rar (fastboot_falcon_asia_ds_user_4.3_14.10.0Q3.X-84-7-LCG-4_4_release-keys-cid7-AsiaRetail_03.tar.gz) file into folder which contains adb.exe and other stuff (C:\Android-SDK\platform-tools)
3. For Downgrading: i deleted following text and saved
Lines 89-90 in the flashall.bat file:
Code:
CALL :fastboot_flash partition gpt.bin
IF %errorlevel% NEQ 0 EXIT /b 1
Lines 120-121 in the flashall.sh file:
Code:
run $fastboot -s "$serial_number" flash partition gpt.bin
if [ $? -ne 0 ]; then echo "ERROR: fastboot failed."; exit -1; fi
4. Turn off the phone for 5 seconds.
Press and hold Volume Down + Power buttons together for few seconds until a Bootloader mode gets appeared
Connected the device to PC through a USB Cable.
Now on PC, go under the extracted files, there pressed “**** Key + Right Mouse Click” button, then from this selected “open command window here“. A command prompt window will opened.
On command prompt window, typed the following command:
flashall.bat /eu
installed the firmware, it take from 5-10 minutes to complete.
Its done, phone is restarted....
5. After that unlock bootloader warning massage appear for 5sec. then black screen and stacked...
no pink color warning massages while installing

deej_roamer said:
Format all of them! i mean /system /data /cache
Click to expand...
Click to collapse
I think there is the problem...
formatting 'system' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.047s
Click to expand...
Click to collapse
I don't know if it's possible to repair a corrupted filesystem...

ikarugaski said:
I think there is the problem...
I don't know if it's possible to repair a corrupted filesystem...
Click to expand...
Click to collapse
I meant from recovery not fastboot!

Okay, that worked fine for me in CWM!

Could you find something in the "getvar" text btw?
These creepy moto still won't boot. :silly:

Just want to mention that the command format will not work.
Instead you have to use erase.

Is it possible to format boot in CMW somehow?
I don't know how, but today i managed to see the CM logo with the cycling arrow, after flashing CM11 with CMW.
But it doesn't boot up, got stuck in the logo with cycling arrow.
And it only showed up ones, never saw it again.
I don't know what happens to the Moto but everything is quite irregular.
Sometimes it boot recovery (sometimes it won't), sometimes got suck with the "warning bootloader" or after that in blackscreen, ones it shows the CM11 logo....

[Q&A] [Recovery] Unofficial CWM - 6.0.5.0 - peregrine

Q&A for [Recovery] Unofficial CWM - 6.0.5.0 - peregrine
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Recovery] Unofficial CWM - 6.0.5.0 - peregrine. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

black screen cwm
EDIT: SOLVED (with somcom's recovery toolkit http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710 /please feel free to delete this post which now only serves as proof of my incompetence)
........................................................................
hello, i've just bought a moto lte (uk) xt1039
have successfully unlocked bootloader
trying to flash recovery via fastboot but having issues
seems to flash ok but then when rebooting into recovery device show (nearly) black screen with some white flickers.
i can boot into bootloader and access via fastboot on windows 7
i downloaded recovery and rom on the moto (before erasing partitions and being unable to boot) and have copies on laptop too.
what have i done? how can i get recovery working to install a rom?
thanks so much for your help, sorry I couldn't find answer here (I tried!
C:\Users\prosody\moto g\RECOVERY>fastboot devices
TA003002KC fastboot
C:\Users\prosody\moto g\RECOVERY>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113(*)
(bootloader) product: peregrine
(bootloader) secure: yes
(bootloader) hwrev: 0x82D0
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: TA003002KC
(bootloader) cid: 0x0007
(bootloader) channelid: 0x49
(bootloader) uid: B6C1B20515000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Nov 9 17:24:15 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/peregrine_o2gb/peregrine:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.56/52:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.56.peregrine_o
(bootloader) ro.build.version.full[1]: 2gb.o2gball.en.GB
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gc20375a-00001-g804
(bootloader) kernel.version[1]: 2017 ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .7 (GCC) ) #1 SMP PREEMPT Tue Aug 5 22:4
(bootloader) kernel.version[3]: 2:49 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.11-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: o2gb
all: listed above
finished. total time: 0.100s
C:\Users\prosody\moto g\RECOVERY>fastboot erase system -w
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.078s]
erasing 'userdata'...
OKAY [ 0.243s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.018s]
erasing 'cache'...
OKAY [ 0.070s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.021s]
finished. total time: 0.449s
C:\Users\prosody\moto g\RECOVERY>fastboot erase boot
erasing 'boot'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.113s]
finished. total time: 0.117s
C:\Users\prosody\moto g\RECOVERY>fastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.118s]
finished. total time: 0.122s
C:\Users\prosody\moto g\RECOVERY>fastboot flash CWM-6.0.5.0-peregrine.img
unknown partition 'CWM-6.0.5.0-peregrine.img'
error: cannot determine image filename for 'CWM-6.0.5.0-peregrine.img'
C:\Users\prosody\moto g\RECOVERY>fastboot flash recovery CWM-6.0.5.0-peregrine.i
mg
target reported max download size of 536870912 bytes
sending 'recovery' (7752 KB)...
OKAY [ 0.311s]
writing 'recovery'...
OKAY [ 0.426s]
finished. total time: 0.746s
C:\Users\prosody\moto g\RECOVERY>fastboot reboot
rebooting...
finished. total time: 0.006s
C:\Users\prosody\moto g\RECOVERY>

Blinking stripes when trying recovery
I just wanted to add that I too have trouble booting into CWM recovery. The screen goes black and some flashing stripes appear accross the screen before it goes completely black. Basically it's unusable...
I can hold the power button and the phone reboots as normal.
The bootloader is unlocked and the phone is rooted.
I hope this information is useful in some way and some fix can be found.
(I have the same problem with TWRP by the way.)
I'm so sorry, you can all ignore what I wrote above.
I fixed it the same way as noted in the post above...
Cheers,

I flashed the CWM recovery as described but when I try to enter it I only get a black screen. I also tried the non-touch version of the recovery but that didn't make any difference. Ideas!?
*edit*
Followed the instructions above and got stuck in the bootloader. Then somehow managed to flash CWM using the Toolkit mentioned above.
C:\Users\prosody\moto g\RECOVERY>fastboot erase boot
Click to expand...
Click to collapse
What's with the flashboot commands posted by prosodyspeaks, I guess that erasing the boot was somehow responsible for being unable to boot the system!?

Every time I create a recovery to my external SD card, it hangs at "Generating md5 sum" but works fine when its in the internal storage. I always have to restart my phone manually. Is there a fix to this, or can I just make a recovery to my internal storage and move the entire recovery folder to my external SD card?

Will this work this the Lollipop 5.1 bootloader?

SJHacker said:
Will this work this the Lollipop 5.1 bootloader?
Click to expand...
Click to collapse
I have 6.0.5.1 installed on my XT1039 Peregrine and it works, i downloaded it from here h t t p ://builder.unstableapps.com/#/latest/clockworkmodrecovery/peregrine .
Anyway you can always test before flash using
Code:
fastboot boot [B]HERE_YOUR_RECOVERY_IMG[/B]
.
If it boots and works then you flash.
PS: I use the CWM linked above, there is only one issue: when you flash it and boot the recovery screen flickers and shows an horizontal line that goes from up to bottom....but everything seems working.
If i simply boot the recovery image without flashing there are no graphical issues.

Try this
The easiest method to install CWM without pc:
1. Download the file on your phone (I moved it to the internal storage)
2. Download Flashify from Play Store
3.Go to "flash" section and select "flash recovery image"
4. Click on "choose a file"
5. Choose the downloaded file
6. Click on this file and select "yup"
7. CWM should be now installed
I have tried this method with my device (Motorola Moto G 4G) and everyrhing went well.

_Immanuel_ said:
I have 6.0.5.1 installed on my XT1039 Peregrine and it works, i downloaded it from here h t t p ://builder.unstableapps.com/#/latest/clockworkmodrecovery/peregrine .
Anyway you can always test before flash using
Code:
fastboot boot [B]HERE_YOUR_RECOVERY_IMG[/B]
.
If it boots and works then you flash.
PS: I use the CWM linked above, there is only one issue: when you flash it and boot the recovery screen flickers and shows an horizontal line that goes from up to bottom....but everything seems working.
If i simply boot the recovery image without flashing there are no graphical issues.
Click to expand...
Click to collapse
Thanks!

Does latest version supports the ext. sdcard used as internal in a marshmallow rom? Thx

Flashing Problem (Bricked phone)

Dear,
I bought a mobile XT1032 in Chile and had the bright idea to install Android 5.0.0, but before that should turn my phone GPE and worked smoothly for about two months, but a few weeks ago the screen began to random failures for example the phone is locked and unlocked without my intervention or the screen, the phone is locked, blinking (as it had voltage changes, such as when you move a flashlight with almost empty and this flashing batteries). I decided to go back to Android 4.4.4 Stock, however this time I did the procedure without considering the consequences, I first downloaded and installed the GPE 4.4.4, then downloaded and installed the Stock Brasil 4.4.4, then tried to go back to stock Movistar Chile but failed to find the 4.4.4 nowhere, so I decided to install the 4.4.3. My mistake. After that my phone did not work more.
Now if I switch it displays the message "Unlocked Bootloader" then shows motorola logos (the world turning) and then the screen goes black but not off (note that is on because it has brightness and that was with that flicker as if he had mentioned voltage failures) but this does not show anything.
I tried installing all the tutorials I found on the internet to revive my phone, I got about 15 different roms and nothing works. I can enter fastboot and no problems (strangely fastboot screen does not flash, it is as if he had nothing wrong), I can also enter recovery (either in recovery flashing display). If I make a recovery "wipe data / factory reset" does well, but if I do "wipe reset partition" android logo shows the blue loading bar appears 2 seconds and the phone reboots.
I not been possible to change the recovery of stock for some other recovery (eg Philz) because although fastboot or mfastboot shows that the process was well (sometimes shown on the phone that is making a downgrade) this does not change the recovery.
Currently my phone is flashed (at least it is assumed that no starts beyond the worlds of motorola) with Android 5.0.2 I downloaded some other forum.
I think, without knowing for sure, for more than I try with the common commands this dont "touch" or change the system version. It's like I always show as well (including with commands in cmd and phone) but practically nothing happened.
I appreciate any guidance to solve my problem.
I attach a "getall var" from my phone
-----------------------------
C:\WorkingMotoG>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4118
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9300B3Y4
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: D3BDB4030F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 15 12:11:29 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_tefcl/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/37:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.Movistar.en.CL
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 01:58:53 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.18-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.18-0-g5742832
(bootloader) rpm.git: git=MBM-NG-V41.18-0-gcecd6e9
(bootloader) tz.git: git=MBM-NG-V41.18-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.18-0-g99084d5
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.059s

Are you manually flashing each file/partition? You will get a validation error if you try to flash the motoboot file since you are already on a lollipop bootloader. A very important file to flash in my opinion is gpt.bin.
If you want a custom recovery on your phone, flash the recovery in fastboot or mfastboot, disconnect the USB cable, use the volume buttons to immediately boot into recovery without restarting the phone.

audit13 said:
Are you manually flashing each file/partition? You will get a validation error if you try to flash the motoboot file since you are already on a lollipop bootloader. A very important file to flash in my opinion is gpt.bin.
If you want a custom recovery on your phone, flash the recovery in fastboot or mfastboot, disconnect the USB cable, use the volume buttons to immediately boot into recovery without restarting the phone.
Click to expand...
Click to collapse
All the files loads OK, gpt.bin with exception of boot.img, it says: "version downgraded for boot" in the phone.
BTW: I do what you say about recovery and keep showing stock recovery. Dont show error messages, just no work.
Thanks anyway for you time...

Which recovery are you trying to flash?
So you flash custom recovery, use volumes button to boot to recovery from fastboot screen and you keep getting stock recovery, right?

audit13 said:
Which recovery are you trying to flash?
So you flash custom recovery, use volumes button to boot to recovery from fastboot screen and you keep getting stock recovery, right?
Click to expand...
Click to collapse
I'm trying to flash philz_touch_6.58.7-falcon.img
Thanks for your time

Did you try TWRP?

audit13 said:
Did you try TWRP?
Click to expand...
Click to collapse
Yes, but dont work neither

So both recoveries flash without an error but you can't boot into either receiver right after flashing?
If it doesn't work, there may be something wrong with the internal memory?

audit13 said:
So both recoveries flash without an error but you can't boot into either receiver right after flashing?
If it doesn't work, there may be something wrong with the internal memory?
Click to expand...
Click to collapse
Now my phone is recognized by Windows as "Qualcomm HS-USB QDLoader 9008". I try to fla**** with MotoFlasher and says:
OUTPUT: opening device: \\.\COM12
OUTPUT: OKAY [ 0.000s]
OUTPUT: greeting device for command mode
OUTPUT: OKAY [ -0.000s]
OUTPUT: identifying device
OUTPUT: ...serial = 0x3B4BDD3
OUTPUT: ...chip-id = 0x800 (MSM8226)
OUTPUT: ...chip-rev = 0x0
OUTPUT: ...sv-sbl = 0x0
OUTPUT: OKAY [ 0.002s]
OUTPUT: finding files
OUTPUT: ...programmer = programmer.mbn
OUTPUT: ...singleimage = singleimage.bin
OUTPUT: OKAY [ 0.000s]
OUTPUT: validating files
OUTPUT: OKAY [ 0.000s]
OUTPUT: switching to download mode
OUTPUT: OKAY [ 0.000s]
OUTPUT: greeting device for image downloading
OUTPUT: OKAY [ 0.001s]
OUTPUT: sending programmer
OUTPUT: OKAY [ 0.010s]
OUTPUT: flashing singleimage
OUTPUT: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
OUTPUT:
OUTPUT:

That's not good. You may have to try the unbrick method to fix it.

audit13 said:
That's not good. You may have to try the unbrick method to fix it.
Click to expand...
Click to collapse
Which method? Can you gave me instructions or a link, please...?

http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798

flashing with fastboot does nothing

My moto g get stucked on a blank screen after the motorola logo animation.
I tried going into the recovery and wiping data and cache. Nothing happened.
I tried unlocking the bootloader --> No problem, it's unlocked now.
I tried reflashing the stock ROM via fastboot. Apparently all goes OKAY, all commands pass without problems, but when I reboot, still a blank screen.
I tried flashing a new ROM (5.0.2 Lollipop). Same problem, apparently it flashes everything ok but when reboots... nothing.
I tried to update only the recovery to ither Team Wins or Clockwork, they flash without problems but when I go to the recovery I get the stock one (I didnt reboot the phone went straight to recovery after flashing, and tried rebooting the phone as well).
I also tried to update only the bootloader (right now I'm at 41.13) tried to update it to 41.18, same problem... Apparently it flashes but when I reboot I still get the 41.13
Finally, I tried to hard-brick my phone using the Bootloader Bricker Tool posted here: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798 and nothing happened.
So basically, it seems that everything I do via fastboot (or mfastboot - I tried both) it goes through without problems, but then it either reverts back to stock when the phone reboots or actually it doesnt write anything.
Any help, will be greatly appreaciated.
This is my getvar:all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: T09290UV3C
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: ADC65E030F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jun 26 18: 9:42 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_amxar/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/37:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.AmericaMovil.en.AR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld28) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 04:31:45 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.13-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.057s

Sounds like possible Bootloader corruption. I would try again with the unbrick tool. Best ask in the thread. Avoid trying to update Bootloader (motoboot.img) - Lollipop is not supported.
Here is the exact 4.4.2 Firmware Image:
http://www.filefactory.com/file/793...9_7_release-keys-cid12-AmericaMovil_AR.tar.gz

Thanks for the reply.
Ok, I'll head over to the unbrick thread again. The thing is my phone doesn't seem to be hard-bricked, because it boots to bootlader and it's not recognized by the PC as "qhsusb_bulk" in Device Manager.
That's why I tried to "brick" it using the tool on that thread, but it didnt get bricked at all :\

The unbrick tool should allow you to restore the Bootloader - if it is indeed corrupted.

lost101 said:
The unbrick tool should allow you to restore the Bootloader - if it is indeed corrupted.
Click to expand...
Click to collapse
I tried it several times now... The problem is that my phone is not being detected by Windows as "qhsusb_bulk" in the Device Manager. So I can't do what the instructions tell me to do.
So I used the Bootloader Bricer Tool
oversleeper said:
Bootloader Bricker Tool: If the previous tool had no effect or you think your bootloader is seriously damaged, this script will make your phone recognized as "qhsusb_bulk" so you can perform a blank flash
Click to expand...
Click to collapse
And this is what I get:
Code:
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y/N]?Y
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.033s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.067s
rebooting...
finished. total time: 0.002s
Your device is now hard bricked!
When it automatically reboots, it's like nothing happened: motorola logo, full animation, then blank screen. I can still enter the bootloader, run fastboot commands, etc etc...

epexy said:
I tried it several times now... The problem is that my phone is not being detected by Windows as "qhsusb_bulk" in the Device Manager. So I can't do what the instructions tell me to do.
So I used the Bootloader Bricer Tool
And this is what I get:
Code:
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y/N]?Y
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.033s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.067s
rebooting...
finished. total time: 0.002s
Your device is now hard bricked!
When it automatically reboots, it's like nothing happened: motorola logo, full animation, then blank screen. I can still enter the bootloader, run fastboot commands, etc etc...
Click to expand...
Click to collapse
I have two devices with the same problem as yours, one = motorola logo -> full animation -> black screen. And another boots up normally, but have a forgotten password, but if I try to enter recovery mode then "Boot Up Failed" message appear, and after I flash the device (and use erase userdata command), the device still have the password and all data apparently (the device boot up fast too).
The only thing that seems to work with fastboot is unlocking bootloader, and relock fails (even showing sucessful)
No one have this problems and have solutions ?????

I have the exact same problem. Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.

Moto G 2014 XT1033 - Boot Loop

Hi, I am new here and I wanted some assistnce to get my old Moto G working. Its stuck in boot loop. When I power it on, it is looping on the Moto screen. I tried flashing it seeing some old threads here and was getting remote failure. I also tried custom recovery but it was failing. I can see Motorola AD Interface on the PC and I have installed all drivers as well. Whatever i try just fails with the same message. "FAILED (remote failure)"
I also a saw thread which talked about the PC to show QLoader9008 in device manager but that also doesnt show in my device manager. I can just see Motorola ADB Interface.
Anything we can do to fix it. I'd really want it to get back to life if its possible.
Thank You for the help in advance.
Images tried
Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC1
XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml by jame
Motorola_Moto_G_XT1033_FALCON_TIMBR_DS_5.1_LPBS23.13-56-2_CID12_5.1
Tools used
RSDLite 6.2.4
mfastboot-v2
Fastboot
Log Sample
F:\DownloadsFolder\Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC1\Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC\Firmware>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 9.950s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 15.225s

If
maau1985 said:
Hi, I am new here and I wanted some assistnce to get my old Moto G working. Its stuck in boot loop. When I power it on, it is looping on the Moto screen. I tried flashing it seeing some old threads here and was getting remote failure. I also tried custom recovery but it was failing. I can see Motorola AD Interface on the PC and I have installed all drivers as well. Whatever i try just fails with the same message. "FAILED (remote failure)"
I also a saw thread which talked about the PC to show QLoader9008 in device manager but that also doesnt show in my device manager. I can just see Motorola ADB Interface.
Anything we can do to fix it. I'd really want it to get back to life if its possible.
Thank You for the help in advance.
Images tried
Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC1
XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml by jame
Motorola_Moto_G_XT1033_FALCON_TIMBR_DS_5.1_LPBS23.13-56-2_CID12_5.1
Tools used
RSDLite 6.2.4
mfastboot-v2
Fastboot
Log Sample
F:\DownloadsFolder\Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC1\Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC\Firmware>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 9.950s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 15.225s
Click to expand...
Click to collapse
If you have not already, first you need to unlock your bootlloader before flashing anything.