Preflash validation failed Moto G XT1039 - Moto G Q&A, Help & Troubleshooting

Hello!
I tried to make a downgrade of my XT1039 from Lolipop to Kit Kat.
My XT1039 bootloader is unlock (I have status3 in the fastboot menu) but when I try to flash the kit kat stock rom I see this:
writing 'partition' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.352s
I am not an expert but I think that from this point the rest of commands are not applied. After finishing the flash I reboot the device and it get's stuck in the bootanimation.
I don't know what to do. I red that is not possible to recover if the device was already updated to Lolipop but I am not sure. Should I try a Cyanogen firmware?
Any advice please?
Thanks you so much

This is a dangerous way to downgrade to KitKat. People have dead phones by flashing an older Bootloader.
You can safely flash one of these Stock KitKat ROMs: http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-kitkat-rom-t3160127
If you choose an Untouched ROM - Do not accept OTA Updates. Such updates are disabled in the Optimized ROMs.

OK, thak you very much.

Related

[Q] Flashing stock rom error - Moto g

Please help, i tried to install cyanogenmod 12 in my moto g, but because of and error with the ui stopping working i tried to back up, to find that i couldn't because of this error:
(bootloader) Preflash validation failed
FAILED (remote failure)
This happend when trying to flash gpt.bin and motoboot.bin, everything else flashed fine.
If someone out there could help me fix this problem i will be very thankfull.
Thanks.
(sorry for my bad inglish, im not an inglish speaker)
Which moto g do you have? What is your bootloader version?
The motoboot file probably isn't flashing because you're trying to load an older bootloader.

moto g preflash validation failed-help me

i have done many moto g using file below
ASIA-DS_4.4.4_KXB21.14-L1.40_34_cid7_CFC_1FF.xml
but now this file error as below
C:\MOTO G>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.047s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.359s
phone screen flash logo error is """version downgraded for primary gpt"""
customer said he tried to upgrade-after it hang in logo
help me
Bootloader unlocking may resolve this. Try to not flash motoboot.img (Bootloader) - as it is dangerous and not even necessary.
lost101 said:
Bootloader unlocking may resolve this. Try to not flash motoboot.img (Bootloader) - as it is dangerous and not even necessary.
Click to expand...
Click to collapse
my phone bootloader shows unlocked in fastboot mode
you can not flash motoboot and a partition table from an older firmware if you already have a newer one i think (downgrade)
alwayspunk said:
you can not flash motoboot and a partition table from an older firmware if you already have a newer one i think (downgrade)
Click to expand...
Click to collapse
i think now 5.1 the lateset version.
from where i get official firmware?
zonetrichur said:
i think now 5.1 the lateset version.
from where i get official firmware?
Click to expand...
Click to collapse
i can not post spam, anyways check the ultimate guide to flash gpe in general section. theres a link to the firmware there
i tried many many recovery files also
that also error
so i think it emmc problem-am i right?
zonetrichur said:
i tried many many recovery files also
that also error
so i think it emmc problem-am i right?
Click to expand...
Click to collapse
May i know whether u flashed stock firmware, because i also getting same error and phone struck in "Bootloader unlocked warning screen" in startup...

Bricked Moto G XT1032

So my friend gave me her old first gen Moto G (XT1032 from Telus in Canada) because it stopped working for her. She told me nothing special happened before and she did not try to do an update. I have no way to know what version of Android the device was running before it bricked. I am familiar with Android devices but mostly Nexus phones so I thought I could try to fix it myself. So right now, here is what it does :
- If I try to turn it on, it stays stuck on the Motorola logo
- If I try to go in the bootloader, I can see it and it says the version number is 41.18 (also the device is locked and was never rooted or anything)
- When in the bootloader, if I try to Normal startup it reboots and stays stuck on the Motorola logo
- If I try to go to recovery or factory reset, the phone just shuts down and nothing happens
I have seen other posts on XDA which seem to relate to the same problem but none of them could fix the one I have. Any help would be much appreciated.
Thanks
Unstable hardware. It happened to me too after throwing on the floor for the 1000th time. The screen is still 100% healthy LoL.
Try returning it if it's still in warranty. If not, try unlocking the bootloader and flashing the latest GPE
Sent from my XT1562 using Tapatalk
Hi,
Seems like firmware goes away... **** happens, even without "throwing" it on the floor a thousand times Unlock it, install a custom recovery (latest Twrp is 2.8.7.0) and flash firmware you want...
If you get an error when flashing, maybe due to your bootloader version... Latest roms require latest bootloader (41.1A). There is a bootloader upgrader tool available in the general section of Moto G forum.
Sorry if I don't give you direct links but I'm on my phone Don't worry, you'll find easily...
Let us know evolution
Can't flash recovery
satanas17 said:
Hi,
Seems like firmware goes away... **** happens, even without "throwing" it on the floor a thousand times Unlock it, install a custom recovery (latest Twrp is 2.8.7.0) and flash firmware you want...
If you get an error when flashing, maybe due to your bootloader version... Latest roms require latest bootloader (41.1A). There is a bootloader upgrader tool available in the general section of Moto G forum.
Sorry if I don't give you direct links but I'm on my phone Don't worry, you'll find easily...
Let us know evolution
Click to expand...
Click to collapse
OK So Im trying to flash TWRP (2.8.6.0) with fastboot but when I do I get 2 errors :
target max-sparse-size: 256MB
sending 'recovery' (8480 KB)...
OKAY [ 10.195s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.208s
It seems my recovery partition is not formatted or something. What should I do now ? Also Im on a MAC so I think there is now way for me to update the bootloader which is not at 41.18
I also tried to boot the recovery (both stock and twrp 2.8.6.0 and 2.8.7.0) instead of flashing it by doing this :
fastboot boot recovery.img
I get this :
downloading 'boot.img'...
OKAY [ 5.330s]
booting...
FAILED (remote failure)
finished. total time: 15.383s
Im not sure where the boot.img is supposed to come from. Am I doing something wrong?
Thanks!

Unbrick moto g turbo

I have a bricked moto g turbo which is locked so i cant flash firmware files i tried getting bootloader unlock code but a error shows up to tick allow bootloader unlock in developer options but i can't turn on my phone so I cant enable that option. please help
You don't need to be unlocked to flash factory firmware. Just go to http://forum.xda-developers.com/showthread.php?t=3169639 and get the correct firmware and follow the instructions in http://forum.xda-developers.com/showthread.php?t=3187750 and flash your device.
Bootloader unlock is only needed for downgrading, root, and flashing custom ROMs and recovery. It is not needed to flash a full factory image that is the same or newer.
And for the record, if OEM Unlocking is not enabled, the bootloader cannot be unlocked.
fastboot flash partition gpt.bin
sending 'partition' (32 KB)... OKAY
writing 'partition'... (bootloader) Preflash validation failed
FAIL
FAILED (remote failure)
Execution time is 1(s)
getting error
Hi i have the same error. But my problem is with the módem. I cant take signal. I try flash the original rom and don't work
Do you have the log file?

Bricked. Stuck on a generic Bootloader. No recovery. Bootloader suddenly locked.

Hi. I got a Moto Maxx with Android Marshmallow (Telcel carrier).
After trying several roms, I decided to go back to stock, since I couldn't find a Marshmallow rom, I decided to update from 4.4. I installed "Mexico Retail Stock Kitkat /// RETLA_XT1225_4.4.4_KXG21.50-9_cid12_subsidy-DEFAULT_CFC.xml.zip" from this thread. Everything went fine, although I lost the custom recovery during the process.
Then, from the software updater option on the phone, I updated to Lollipop. Unfortunately, it didn't updated. Instead, I got a bricked phone. It didn't turned on.
In order to recover it. I followed this guide. The phone turned on again, and now I am stuck on an "empty" bootloader. The upper half of the screen only shows "Start", similar to the picture from the guide.
But I can't flash any stock rom. It seems by doing the steps of that guide, I re-locked my phone. I can't unlock it because, while I know my unlock bootloader code, mfastboot tells me I must enable "Enable OEM Unlock" in the developer settings (which I can't reach).
Trying to flash any stock rom gives me the following errors:
Code:
[B]>mfastboot flash partition gpt.bin[/B]
[I]target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.104s[/I]
>[B]mfastboot flash bootloader bootloader.img[/B]
[I]target max-sparse-size: 256MB
sending 'bootloader' (2159 KB)...
OKAY [ 0.112s]
writing 'bootloader'...
[B](bootloader) Motoboot: Unknown partition name[/B]
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.202s[/I]
>[B]mfastboot flash radio radio.img[/B]
[I]target max-sparse-size: 256MB
sending 'radio' (85457 KB)...
OKAY [ 2.753s]
writing 'radio'...
[B](bootloader) Motoboot: Unknown partition name[/B]
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.802s[/I]
>[B]mfastboot.exe flash system system.img_sparsechunk.0[/B]
[I]target max-sparse-size: 256MB
sending 'system' (253363 KB)...
OKAY [ 8.205s]
writing 'system'...
[B](bootloader) Permission denied[/B]
FAILED (remote failure)
finished. total time: 8.226s[/I]
I can't access to recovery. Please, help me :crying::crying::crying:
Why do people relock their bootloader?
With an unlocked bootloader you can flash other region images, if necessary, like Brazil. With locked bootloader your need Mexico. Your may even need your carrier firmware.
ChazzMatt said:
Why do people relock their bootloader?
Click to expand...
Click to collapse
It wasn't my intention. The phone bricked, and in order to return to bootloader I followed that guide. It worked but it seems that during the process it locked the phone.
But you went from Marshmallow 6.0.1 back to Lollipop 5.0.2. You can't do that unless you omit gpt.bin in your flash commands. Otherwise you will get bootloop or brick your phone.
I assume at one time you had stock Marshmallow on the phone before trying custom ROMs? Or at the least, probably had flashed Marshmallow radio and bootloader?
With unlocked bootloader you can downgrade back to Lollipop or Kitkat, but you need to omit gpt.bin.
I would also omit recovery.img, to keep TWRP.
---------- Post added at 03:23 PM ---------- Previous post was at 03:14 PM ----------
See this thread, but you'll need your region firmware.
https://forum.xda-developers.com/showthread.php?t=3662683
ChazzMatt said:
But you went from Marshmallow 6.0.1 back to Lollipop 5.0.2. You can't do that unless you omit gpt.bin in your flash commands. Otherwise you will get bootloop or brick your phone.
I assume at one time you had stock Marshmallow on the phone before trying custom ROMs? Or at the least, probably had flashed Marshmallow radio and bootloader?
With unlocked bootloader you can downgrade back to Lollipop or Kitkat, but you need to omit gpt.bin.
I would also omit recovery.img, to keep TWRP.
Click to expand...
Click to collapse
Yes, as I said. The phone had Stock Marshmallow. I unlocked my bootloader, I tried custom roms, tried TWRP, I even could go back to stock KitKat (by omitting gpt.bin)
The problem came when I accepted to update to OTA Lollipop. The phone bricked; the screen didn't turned on. And while I found a guide that could unbrick the phone, I ended without recovery and with a relocked phone.
jairjy said:
Yes, as I said. The phone had Stock Marshmallow. I unlocked my bootloader, I tried custom roms, tried TWRP, I even could go back to stock KitKat (by omitting gpt.bin)
The problem came when I accepted to update to OTA Lollipop. The phone bricked; the screen didn't turned on. And while I found a guide that could unbrick the phone, I ended without recovery and with a relocked phone.
Click to expand...
Click to collapse
Because while you had downgraded to Kitkat, but you still had Marshmallow bootloader. You can't take OTA, because it will install bootloader and you cannot downgrade bootloader.
Have we discussed this before, because someone else did EXACTLY the same thing. Downgraded to Kitkat, then tried to take Lollipop OTA --which tries to install Lollipop bootloader!

Categories

Resources