Database Info

(bootloader) Preflash validation failed

Hi I've Installed Chainfire(dumbest idea ever) -I had GLTools with only default plugin- ,too check whenever It would be possible to run Portal-So memory is almost full ,so I couldn't do neither full CWM backup ,and Advanced Backup didn't worked for me.
So What I did was flash 4.4.2(and I was on 4.4.4 europe rom -XT1032)
I have Fastboot Reason: UTAG *flashfail* configured as fastboot(no not after installing chainfire)
I was flashing with my premade /.sh file (fastboot flash partition gpt.bin etc.) and it seems like what have been flasheed is:
wirting 'partition'...
(bootloader) Preflash validation failed
FAILED(remote failure)
wirting 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
witing 'boot'...
OKAY
'system' -sparechunk.0
FAILED (data transfer failure (No such file or directory)) - lol? ,I've actually modified VM to have 512 mb of ram instead of 1536mb and cores from 2 to 1.
*fastboot resets*
Fastboot Reason: UTAG *flashfail* configured as fastboot
'system'-sparechunk.1
OKAY
and the rest wasn't flashed ,What can I do ,...I've just clicked factory(up button-congrats idiot-I wanted to go into recovery to say that I can go there and do something from there *facepalm* and clicked Up button ,because I was on factory option).
Okay ,so know I have no UTAG error recovery still works ,phone gets stuck on unlocked bootloader disclamer.
Btw before I started to install chainfire I've followed some instructions:
Code:
Backup
[B] * boot into recovery
* adb backup -f boot.img boot
* adb backup -f system.img system[/B]
Restore
[B] * boot into recovery[/B]
* adb shell echo -n boot > /tmp/ro.bu.restore
* adb restore boot.img
[I][B] * adb shell echo -n system > /tmp/ro.bu.restore
* adb restore system.img[/B][/I]
I've followed ,Failed
As boot.img from 4.4.2 have flashed can I actually flash that( * adb backup -f boot.img boot) boot.img and I don't magic will help me. Or can Actually someone who Have XT1032 falcon_umts do like CWM Backup without any personal stuff and I would try to flash it(Preloader/boot is not corrupted- device unlocked etc.-) ,when I used Used factory then everything seems to be working(expect for the android of course... and I don't know whenever VM will work If I don't have everything flashed).
Btw I can't Flash System.img from before I've destroyed it with Chainfire ,because the size is more than 600/700 mb and it just out numbers max number for sending system partition to fastboot.

Not saying this will definitely work, but if you get the gpt.bin and emmc_appsboot.mbn files from the 4.4.4 OTA zip (probably floating around here) and overwrite the originals from 4.4.2 in your factory image (delete the old ones or rename them to something else), then do the following:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Then flash as normal according to the guide that's floating around here, but leave out the gpt.bin and emmc_appsboot.mbn (you already flashed these) and the motoboot.img or it will brick it!

I just installed Paranoid Android ontop of it(adb sideload-I couldn't get into CWM ,and by accidently clicking factory in fastboot I could then go to CWM) and it works-then I launch PA install minimal gapps then factory reset it in cwm delete all data and slowly update pa update by update(installing 4.4RC2 into 4.45 is an bad idea for overall performance and stability) -I just kinda paniced.And I think ,because I was using generic fastboot instead of provided in guide ,preloadder didn't get corrupted(when to look at It only boot have been flashed correctly , and PA have boot.img in package).
So far so good.

This error has been associated with locked bootloader.

I know but my is still unlocked.
Btw that message "Preflash validation failled" supposed to show after booting too fastboot(actually that sounds like a total bull****) or on flasher linux terminal.

Shuttwind215 said:
I know but my is still unlocked.
Btw that message "Preflash validation failled" supposed to show after booting too fastboot(actually that sounds like a total bull****) or on flasher linux terminal.
Click to expand...
Click to collapse
My moto's bootloader is unlocked too, but it still gives the error...
Found an article:
https://giorgiosadventures.wordpres...rom-gpe-4-4-4-to-stock-and-recover-softbrick/
Try this... Lets see if it helps...
BTW, I got this error after converting xt1033 to gpe, then OTA'ing it to 5.0.1, then downgrading to 4.4.2.

@layman806 My moto g allready work look at post #3 this is what I did it[it looks extremly confusing]. It mightn't work for you through
,but if yours moto g have unlocked bootloader then you can do a lot ,and your situation isn't that bad.

lost101 said:
This error has been associated with locked bootloader.
Click to expand...
Click to collapse
i have unlocked my bootloader but i still get that error. every other command executes perfectly but this gpt.bin doesnt
any solution?

khiladi_786 said:
i have unlocked my bootloader but i still get that error. every other command executes perfectly but this gpt.bin doesnt
any solution?
Click to expand...
Click to collapse
I have the exact same problem on my xt1031 motog. I cant get any roms to boot and I cant figure out what version of gpt.bin i need to use. I get the same error.
Driving me crazy.

not solved
I am flashing the stock rom into my moto g3 but it keep tellin preflash validation failed........I did everything ......still not solved.......help me out please..........
on bootloader it shows....
device is unlocked. status code :3
software status: official
it is bit odd.....

heisenberg1546 said:
I am flashing the stock rom into my moto g3 but it keep tellin preflash validation failed........I did everything ......still not solved.......help me out please..........
on bootloader it shows....
device is unlocked. status code :3
software status: official
it is bit odd.....
Click to expand...
Click to collapse
This subforum is not for your phone. https://forum.xda-developers.com/2015-moto-g is the place for you.
If you are getting a 'pre-flash validation' error - even with the latest available firmware image - then you have to either wait for an even newer firmware image or unlock Bootloader and flash a ROM zip.

help me plseeeeeeeeeeeeee i m getting preflash validation failed error on gpt.bin and sparsechunk plseee help me anyone i m using moto g3 xt1550 and trying to flash marshmallow.

[SOLVED] [CM11] [XT1032] Stuck at boot splash logo

Hello,
I have a Motorola Moto G XT1032 on which I have successfully unlocked the bootloader. I can access to recovery (CWM 6.0.4.7) and transfer files using adb in this mod. However, CWM does not get past the splash logo (I do get the occasionnal lag when CWM rebuilds the cache, but this is another minor issue). I have tried the following ROMs, installed each after formatting /system, /data and /cache:
cm-11-20140308-SNAPSHOT-M4-falcon.zip
cm-11-20140405-SNAPSHOT-M5-falcon.zip
cm-11-20140504-SNAPSHOT-M6-falcon.zip
cm-11-20140613-NIGHTLY-falcon.zip
cm-11-20140730-NIGHTLY-falcon.zip
cm-11-20140823-NIGHTLY-falcon.zip
None worked. I did checked the md5 checksums. I have also tried installing GApps using gapps-kk-20140606-signed.zip .
I do not know how to get more information on what happens when CM11 stucks during the boot. 'Show log' from recovery only prints some configuration information as well as:
Code:
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
From what I undersood, extendedcommand is an optional executable used to launch stuff at boot.
I found some ideas from another thread and tried locking/unlocking oem:
Code:
$ fastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.057s]
finished. total time: 0.057s
$ fastboot oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.037s]
finished. total time: 0.037s
$ fastboot oem unlock
...
(bootloader) Device already unlocked!
FAILED (remote failure)
finished. total time: 0.008s
Additionnally I also reinstalled recovery:
Code:
$ fastboot erase recovery
$ fastboot flash recovery CWM-swipe-6.0.4.7-falcon.img
I did have a message "Mismatched partition size (recovery)" but CWM starts fine. I then reinstalled CM11 again, but it did not help either.
Would you have further instruction to try and get CM11 to work?

Just a short post to avoid the thread from being buried down into oblivion.

Same happened to me days ago. I was unable to install any custom ROM. I was in Enhdroix and I flashed the original version of my ROM via fast boot but every time I tried to install a custom was stocked and bootlogo. Some how I figured that the boot loader of the original version was corrupted so I flashed a different stock ROM, after that was able to install custom.
The recovery message is normal you can check videos or post.
Hope this helps my friend.

To prevent any further problems, I also recommend that you flash twrp or philz recovery because the stock cwm recovery is outdated and it will give you problems while flashing ROMs in the future...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------

ThisIsMadness said:
Just a short post to avoid the thread from being buried down into oblivion.
Click to expand...
Click to collapse
Check previous answers

Thanks for your help, I finally got it to work!
If someone gets stuck with the same problem, here is what I did:
first, fastboot flash recovery to TWRP
reinstalling (wipe and so) CM11 from TWRP did not work any better
I reinstalled a stock ROM following http://forum.xda-developers.com/showthread.php?t=2542219
I did not boot at all (no logo), but I could still get to fastboot
I reinstalled TWRP, and then CM11
it worked!
From my own diagnosis, I must have accidentely corrupted a partition with fastboot flash. Or maybe I wiped something that I should not have. Anyway, by reinstalling stock, I restored all the partitions and could install CM11. I do not think CWM is to blame here.

[Q] Moto G stuck in boot loop

This started with a brand new Boost Mobile Moto G (XT1031).
It was taken right from the box and unlocked using oem unlock.
After the unlock it booted to the stock image then was powered off and booted to fastboot.
Once in fastboot TWRP 2.7.1.0 recovery was flashed.
When trying to boot into recovery it would only loop.
Tried to boot normally and it would only loop.
Flashed the device back to stock using all the available firmwares from sbf.droid-developers.org for Boost US and it still wont boot.
Tried other recovery images and the only one I was able to get working was Philz Touch 6.55.
Wiped and formated everything and rebooted the phone and it went straight to recovery.
Using Philz recovery tried to install CyanogenMod 11 and bool loop proceeded.
I took another working Moto G and flashed Philz recovery and made a back up onto a usb drive using an otg cable.
On the broken device tried to restore from the backup and it said it was completed but it ran way to fast and didn't seem to restore completely and failed to boot.
I've gone through every method of recovery i could find and nothing seems to be working
This phone is kicking my butt, any help would be greatly appreciated.

manicresin said:
This started with a brand new Boost Mobile Moto G (XT1031).
It was taken right from the box and unlocked using oem unlock.
After the unlock it booted to the stock image then was powered off and booted to fastboot.
Once in fastboot TWRP 2.7.1.0 recovery was flashed.
When trying to boot into recovery it would only loop.
Tried to boot normally and it would only loop.
Flashed the device back to stock using all the available firmwares from sbf.droid-developers.org for Boost US and it still wont boot.
Tried other recovery images and the only one I was able to get working was Philz Touch 6.55.
Wiped and formated everything and rebooted the phone and it went straight to recovery.
Using Philz recovery tried to install CyanogenMod 11 and bool loop proceeded.
I took another working Moto G and flashed Philz recovery and made a back up onto a usb drive using an otg cable.
On the broken device tried to restore from the backup and it said it was completed but it ran way to fast and didn't seem to restore completely and failed to boot.
I've gone through every method of recovery i could find and nothing seems to be working
This phone is kicking my butt, any help would be greatly appreciated.
Click to expand...
Click to collapse
What did you use to flash? fastboot or mfastboot?

280
oversleeper said:
What did you use to flash? fastboot or mfastboot?
Click to expand...
Click to collapse
I used mfastboot.

http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Try to use the bootloader refresh tool, for someone worked.:good:

oversleeper said:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Try to use the bootloader refresh tool, for someone worked.:good:
Click to expand...
Click to collapse
I ran the bootloader refresh after modifying the bat file for the correct cpu.
The boot loader version is showing it was updated but the device is still not booting.
[EDIT] I did try to reflash the stock frimware and there where some erros i wasnt getting before
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash aboot emmc_appsboot.mbn
sending 'aboot' (512 KB)...
OKAY [ 0.051s]
writing 'aboot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.335s
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash motoboot motoboot.img
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
Motoboot: Preflash validation for tz
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.407s

On a whim I decided to try the retail firmware and was able to get the phone to boot to stock, but I tried to load TWRP again and it went back to the boot looping state.
I really don't understand what is wrong with this phone because this are for the company I work for and we have flash about a thousand this exact same way and have never ran into this issue.
I am going to try philz recovery to see if it cause the normal boot process to break and if not I try loading the a custom rom from there.

manicresin said:
I ran the bootloader refresh after modifying the bat file for the correct cpu.
The boot loader version is showing it was updated but the device is still not booting.
[EDIT] I did try to reflash the stock frimware and there where some erros i wasnt getting before
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash aboot emmc_appsboot.mbn
sending 'aboot' (512 KB)...
OKAY [ 0.051s]
writing 'aboot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.335s
Code:
C:\falcon_boost_user_4.4.2>mfastboot.exe flash motoboot motoboot.img
sending 'motoboot' (1940 KB)...
OKAY [ 0.111s]
writing 'motoboot'...
Motoboot: Preflash validation for tz
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.407s
Click to expand...
Click to collapse
Pretty normal, you got errors because you upgraded the bootloader to the last version, so you can't downgrade it. Now you can: try to flash the 4.4.2 stock boost version (without flashing gpt.bin and motoboot.img) or if doesn't work due to upgraded bootloader, just wait few days until the 4.4.4 firmware for boost will be downloadable. It's already realeased don't worry, look https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/100754/p/30,6720,9050
EDIT: It's a boost version, it's pretty different... You can't flash whatever you want so easily... search for some guide, I can't help about boost version.

The boost 4.4.2 stock firmware failed but the retail version worked, I'm try that with philz recovery to see if I can get CM 11 to work. If that fails ill wait for the 4.4.4 boost firmware.
Thanks for the help

I know some people love TWRP and only use TWRP and some people only use ClockWorkMod Recovery, but since you've been trying with TWRP humour me and flash this, it's the latest ClockWorkMod Recovery 6.0.5.0 compiled from source.
Flash it then try to flash a CM nightly or something like that...clear cache and dalvik cache first then do a factory reset then flash.
ClockWorkMod Recovery 6.0.5.0

CodyF86 said:
I know some people love TWRP and only use TWRP and some people only use ClockWorkMod Recovery, but since you've been trying with TWRP humour me and flash this, it's the latest ClockWorkMod Recovery 6.0.5.0 compiled from source.
Flash it then try to flash a CM nightly or something like that...clear cache and dalvik cache first then do a factory reset then flash.
Click to expand...
Click to collapse
I downloaded your recovery image and flashed it, wiped everything and reset.
Installed cm-11-20140903-NIGHTLY-falcon from usbdisk, it said completed only after ~20 seconds but there where no errors.
Rebooted the device and the cyanogenmod animated boot logo was displayed.
The phone booted fine was is working, now to try and see if I can get my image loaded.
Thanks for the recommendation, I didn't think to try CWM since Philz recovery is based on it, but it failed to load CM 11.

Hard bricked? Can't get into recovery, can't unlock bootloader

Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!

How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.

sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,

rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,

man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there

therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...

rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?

therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!

DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..

therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.

rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?

heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,

Bump!
Does anyone have any other suggestion please?
Thanks,

Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!

Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.

I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?

I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..

Recovery installation failed

Hello,
I have a Moto G (XT1032) since 3 years and all of a sudden, it didn't boot. I had the Stock ROM, I never installed a new ROM or Recovery...
I unlocked my phone and then tried to install TWRP to boot on recovery and make a backup of my data.
I tried several recoveries (twrp-2.8.6.0-xt1032, twrp-3.0.0.0_2-falcon, twrp-3.1.0-0-falcon, twrp-3.1.0-0-xt1032 & clockwork-touch-6.0.4.7-falcon).
I have no problem to send the recovery on the phone. In the fastboot mode on the phone, it says the installation is okay and then, I choose "Recovery" in the fastboot mode on the phone.
The phone reboot and I have the android logo with "No Command". I find this blog : https://wasconet.com/solution-moto-g-android-recovery-mode-no-command/ and so I hold the power button and press the volume up button to enter recovery mode screen.
The problem is, I access the default recovery — which is not TWRP, only a basic recovery where I can't mount the phone. This recovery says :
Android system recovery
LPBS23.13-56-2
...
From there I can reboot, apply update from sdcard or ADB, wipe data/factory, wipe cache, reboot to bootloader, power down or view recovery logs.
What can I do to install a good recovery and to mount my phone to make a backup ?
Thanks guys !

Lately it happens with the latest versions of twrp. Do not boot or boot once, then return the Stock Recovery again.
In my case I can not install v3.1 because it throws me max download size error. :silly:
Try the v3.0.2-2. It works without any problem over my old falcon.
https://dl.twrp.me/falcon/twrp-3.0.2-2-falcon.img.html
I'm not sure if the command works on the Falcon, but first try starting it without flashing it
fastboot boot twrp-3.0.2-2-falcon.img
By the way, can i assume that having Lollipop you have the latest version of the bootloader (41.1A)?

Thanks, it worked ! I made a backup of my files.
Now I try since this morning to install a new ROM... I tried "Factory" in the fastboot mode => Phone blocks on "Bootloader unlock".
With TWRP, I havea lot of problem with the mount. I can see the data but to copy files, it was not possible.
I mount the sdcard in Read Write with the terminal on the phone to copy the Lineage ROM. I tried to install it but I receive an error "1001".
I use now the last version of TWRP, the 3.1.0 with the command fastboot boot. This version works but I have the same error to install Lineage.
I also tried to install the stock version EU 5.1 Stock ROM (Untouched) (522mb) (from here https://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510) with adb sideload.
I saw "succesful" but the phone is always block on the "Bootloader unlock" image...
The bootloader version is indeed 41.1A.
Someone should have an idea to install a system ? (any system, I don't care, I just want a phone that I can use )
Thanks a lot !

Usually error 1001 relates to an encrypted or unreadable partition.
Have you used fastboot or mfastboot to install the system again?
Try Repair or Change file system using twrp.
Wipe>>Advanced Wipe>>
Then try to install any ROM.
If doesn't work. Inside of TWRP go to Advanced>Terminal Emulator
Then execute the command df
That should list you the partitions. Share it and if you know how to take it please share the recovery log after doing all this.

I use fastboot to just boot on the recovery.
To install, I don't tried fastboot or mfastboot. I find a guide to flash with mfastboot, I will try.
Yesterday I made all the wipe possible. Today I made a Repair on the system partition.
Here is the result of the df command :
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 446184 20 446164 0% /dev
tmpfs 446184 20 446164 0% /tmp
/dev/block/mmcblk0p33
667328 11836 655492 2% /cache
/dev/block/mmcblk0p36
5789552 5210064 528432 91% /data
/dev/block/mmcblk0p36
5789552 5210064 528432 91% /sdcard
I noticed something strange yesterday. I tried several times to delete files on the "sdcard" partition, where I found the pictures, whatsapp, ... I deleted some files with Windows (MTP Mode) and the files are always there after delete with no error message. I don't know if it's important or not.

lolo1410 said:
I I noticed something strange yesterday. I tried several times to delete files on the "sdcard" partition, where I found the pictures, whatsapp, ... I deleted some files with Windows (MTP Mode) and the files are always there after delete with no error message. I don't know if it's important or not.
Click to expand...
Click to collapse
When you unlock the bootloader, all your personal data should be deleted normally, but that didn't happen. The internal memory partition is recognized (that's good) but is unreadable, obviously corrupted. (Sorry for not noticing before)
Try installing the firmware again using mfastboot avoiding BOOTLOADER (motoboot) AND GPT files to see if works. If didn't, flash it again including GPT file (Partitions table).
If it still doesn't work, you'll have to figure out how to repartition the entire phone memory.
----------
By the way, never try to restore that DATA BACKUP. Like i say before, it's corrupted. Search a way to decompress and takes only the important files.

Thanks a lot for your time !
Indeed, it's seems there is a probleme with the filesystem.
I tried a flash of GPT & Bootloader but it didn't work.
Here is the log :
C:\adb\tmp>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.026s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.320s
&
C:\adb\tmp>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.093s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.370s
But I'm not sure if I choose the good firmware & bootloader.
On this link (http://www.filefactory.com/folder/c6cdedc45a775d27), which version can I take ?
Here is the information that I have for the phone :
Motorola G XT1032 - Type M0DEB - FCCID ihdt56pf1 buyed in Belgium
AP Fastboot Flash Mode (S)
41.1A (2015-04-10)
CPU MSM8226 CS
eMMC : 8GB Sandisk
DRAM : 1024MB Samsung S4

Try with one of these, and again. DONT FLASH BOOTLOADER (Usually cant be flashed after unlock but, I do not think you want a paperweight)
Retail EU 5.1
https://www.androidfilehost.com/?fid=24052804347848287
Retail EU 5.1 (NEWER BUILD)
https://www.androidfilehost.com/?fid=24499762636006646
You can download others from Here
https://forum.xda-developers.com/mo...rmware-t3110795?_e_pi_=7,PAGE_ID10,4937194410

After several tests, I find a good package, this : XT1032_FALCON_RETFR_5.1_LPBS23.13-56-2_cid7_CFC.xml
I had no error.
I see your message too late, I flash the bootloader
But it's a 41.1A version, here is the info on this package :
BUILD REQUEST INFO:
SW Version: falcon_retfr-user 5.1 LPBS23.13-56-2 2 release-keysMSM8626BP_1032.3116.98.00R
MBM Version: 41.1A
Modem Version: MSM8626BP_1032.3116.98.00R
FSG Version: MSM8626BP_FSG_01.101.00R
Build Fingerprint: motorola/falcon_retfr/falcon_umts:5.1/LPBS23.13-56-2/2:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 221.201.2.falcon_umts.Retail.en.FR
Model number: Moto G
Android Version: 5.1
Baseband Version: MSM8626BP_1032.3116.98.00R
Build Number: LPBS23.13-56-2
Build Date: Fri Feb 26 06:59:41 CST 2016
OTHER MISC VERSION INFO:
Subsidy Lock Config: None
Blur Version: Blur_Version.221.201.2.falcon_umts.Retail.en.FR
Version when read from CPV: falcon_retfr-user 5.1 LPBS23.13-56-2 2 release-keys
I followed the guide here https://forum.xda-developers.com/showthread.php?t=2542219 and no error during all the command. I switch off the phone and unfortunately, no boot...
It's block on the "Warning bootloader unlocked" screen...

The phone is still alive and that's good. Keep trying others roms if you want. But as I said before, surely the internal memory of the phone is corrupt. Unfortunately, I can't help you with that.
Maybe here over XDA there's a tutorial about how to solve your problem.

Okay, thanks a lot for your help.
I just tried the Retail EU 5.1 (NEWER BUILD) and same result : no error but blocks on the boot..
I will continue to test other ROM

I ended up in the same situation when trying to flash GPe on MotoG XT1032; the device was only able to boot into fastboot
After booting into TWRP, I formatted the /data partition again (in order to fallback to F2FS instead of ext4) and I used adb sideload to transfer "XT1032_Retail_Brazil_51_Untouched.zip" (you can find it on xda, under "Stock Motorola Lollipop ROM Collection" thread).
Phone was in full working condition once more