Database Develop

Need help ASAP! (fastboot preflash validation failed)

EDIT 3: Okay, just flashed a new kernel and the WiFi is working now. Must have been the stock kernel for some reason.
So all problems solved now
EDIT 2: Succesfully flashed the ROM, but unable to connect to Wifi. When I press the on button, it switches on for a second and then switches off again. Any idea guys why?
I've been trying to flash the stock ROM, but can't because as soon as I begin with the first step i.e fastboot flash partition gpt.bin, the following error is displayed- fastboot preflash validation failed.
Now I've been reading up on the forums here and a some have said that this error occurs when someone tries to downgrade. But I'm on the latest build and I don't know why this is happening?
Just so everyone knows, I'm unlocked and rooted.
Please, I need help since the ROM I'm on, which by itself is stock, is pretty much not working.
EDIT: The full message on fastboot is as follows
PHP:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.036s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.397s
And on the bootloader
PHP:
version downgraded for primary_gpt

mahendru1992 said:
I've been trying to flash the stock ROM, but can't because as soon as I begin with the first step i.e fastboot flash partition gpt.bin, the following error is displayed- fastboot preflash validation failed.
Now I've been reading up on the forums here and a some have said that this error occurs when someone tries to downgrade. But I'm on the latest build and I don't know why this is happening?
Just so everyone knows, I'm unlocked and rooted.
Please, I need help since the ROM I'm on, which by itself is stock, is pretty much not working.
EDIT: The full message on fastboot is as follows
PHP:
target reported max download size of 536870912 bytessending 'partition' (32 KB)...OKAY [ 0.036s]writing 'partition'...(bootloader) Preflash validation failedFAILED (remote failure)finished. total time: 0.397s
And on the bootloader
PHP:
version downgraded for primary_gpt
Click to expand...
Click to collapse
You can ignore gpt.bin and motoboot.bin. They won't flash if the same or lower version. Not a problem. Just continue flashing the other files.

doppelhelix said:
You can ignore gpt.bin and motoboot.bin. They won't flash if the same or lower version. Not a problem. Just continue flashing the other files.
Click to expand...
Click to collapse
Okay, thanks man, I successfully flashed the ROM. But now I have another problem. I'm not able to switch on my Wifi. When press the on button, it switches on for a micro sec and then switches off. Any idea why?

Don't know. Maybe a reboot. After that I would wipe dalvic, cache and data?

doppelhelix said:
Don't know. Maybe a reboot. After that I would wipe dalvic, cache and data?
Click to expand...
Click to collapse
I did better, a factory reset. Nada.
Would flashing a different kernel help?

Did you do a
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
This is a wififix for the kernel

doppelhelix said:
Did you do a
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
This is a wififix for the kernel
Click to expand...
Click to collapse
Oh I didn't know that this was a wifi fix, but yes I did perform the above steps as well.
But anyhow, I flashed a new kernel and it did solve the problem.

Thanks
doppelhelix said:
You can ignore gpt.bin and motoboot.bin. They won't flash if the same or lower version. Not a problem. Just continue flashing the other files.
Click to expand...
Click to collapse
Thanks 4 Your Help i been stuck whit that errors all night and now i have back on 4.4.4.

C:\Users\Raghavendra\Documents\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1F
F_SVC.xml>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.133s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.192s
pl help me i have the same problem..... but idk how to fix it...... plz help me asap... i have just unbricked my phone and tried to flash the brazillian 4.4.4....... i was already on this firmware before but when i tried to update to brazilian ota 5.0 my phone was bricked... now i have successfully unbricked it but i cant flash it to any rom cause of this problem...... if it the files prob?? should i get another rom?? pl help asap:crying::crying::crying::crying::crying::crying:

Raghavendra2k14 said:
C:\Users\Raghavendra\Documents\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1F
F_SVC.xml>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.133s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.192s
Click to expand...
Click to collapse
As you pointed out here: http://forum.xda-developers.com/showpost.php?p=57483947&postcount=115, your bootloader is locked. Please don't double-post. Forum Rules

pl help
doppelhelix said:
As you pointed out here: http://forum.xda-developers.com/showpost.php?p=57483947&postcount=115, your bootloader is locked. Please don't double-post. Forum Rules
Click to expand...
Click to collapse
when i try unlocking bootloader again it gives me me a error
C:\Users\Raghavendra\Desktop\platform-tools>fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [ 0.016s]
finished. total time: 0.016s
even if i put my old code it doesnt work... pl help..... but in this forum it tells us to flash the two files gpt.bin and motoboot.img but when i try to flash these they give me preflash validation error <remote failure> and display "version downgraded for primary_gpt" on the moto g
my bootloader is locked because it got hard bricked and i recently unbricked it.... the next step was to flash these two files but i get this preflash validation error <remote failure> and display "version downgraded for primary_gpt" on the moto g
pl help me

Raghavendra2k14 said:
when i try unlocking bootloader again it gives me me a error
C:\Users\Raghavendra\Desktop\platform-tools>fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [ 0.016s]
finished. total time: 0.016s
even if i put my old code it doesnt work... pl help..... but in this forum it tells us to flash the two files gpt.bin and motoboot.img but when i try to flash these they give me preflash validation error <remote failure> and display "version downgraded for primary_gpt" on the moto g
my bootloader is locked because it got hard bricked and i recently unbricked it.... the next step was to flash these two files but i get this preflash validation error <remote failure> and display "version downgraded for primary_gpt" on the moto g
pl help me
Click to expand...
Click to collapse
Didn't you read anything of the previous posts?
If you've unlocked your bootloader, and getting these errors, you can safely ignore them. Just carry on flashing the other files.

Carried on
I did carried on with the fastboot steps but I get this "UTAG "flashfail" is configured as fastboot" and I'm still stuck in Bootloader.
How do I change the Kernel?
Oh yeah, I updated to Lollipop about 20 days ago, worked fine until a few days back and suddenly I get these strange errors. What could be the cause though?

Kindle Fire 5th gen: fastboot boot boot.img returns 'remote: unknown command'

I have a Kindle Fire 5th Gen (Fire OS 5.1.1 installed december 9th 2015). When I go into bootloader mode it says fastboot mode, but when I issue the command 'fastboot boot boot.img' this does not work. Does anyone know how to solve this? I used the same method on another Fire (same version) some weeks ago, and there I could boot into TWRP using the same method.
adb reboot bootloader
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.168s
fastboot getvar product
product: FORD
finished. total time: 0.002s
fastboot getvar version
version: 0.5
finished. total time: 0.002s
fastboot devices
G000H40454120K64 fastboot
Best regards,
Leen

toelen said:
I have a Kindle Fire 5th Gen (Fire OS 5.1.1 installed december 9th 2015). When I go into bootloader mode it says fastboot mode, but when I issue the command 'fastboot boot boot.img' this does not work. Does anyone know how to solve this? I used the same method on another Fire (same version) some weeks ago, and there I could boot into TWRP using the same method.
adb reboot bootloader
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.168s
fastboot getvar product
product: FORD
finished. total time: 0.002s
fastboot getvar version
version: 0.5
finished. total time: 0.002s
fastboot devices
G000H40454120K64 fastboot
Best regards,
Leen
Click to expand...
Click to collapse
Can't use this method with FireOS 5.1.1. Try FlashFire.

Davey126 said:
Can't use this method with FireOS 5.1.1. Try FlashFire.
Click to expand...
Click to collapse
Once the device is running a custom rom (mine is on Fire Nexus) and if the device was originally on 5.3.1 then can this method be used to boot into twrp recovery?

jinxt said:
Once the device is running a custom rom (mine is on Fire Nexus) and if the device was originally on 5.3.1 then can this method be used to boot into twrp recovery?
Click to expand...
Click to collapse
Nope - bootloader must be 5.0.x to permit twrp (or any custom recovery) to be booted. Bootloader can not be downgraded. You're stuck with Fastboot, mate.

so you can't use fastboot to chainload twrp on a 1time basis ? making the protected device bootloader irrelevant
i thought thats what ""fastboot boot boot.img "" was doing - chainloading

jinxt said:
so you can't use fastboot to chainload twrp on a 1time basis ? making the protected device bootloader irrelevant
i thought thats what ""fastboot boot boot.img "" was doing - chainloading
Click to expand...
Click to collapse
No. If possible it would have been offered. Bootloader is locked; Amazon crippled fastboot; boot command no longer recognized on v5.1+.

Ok i get it, hence the reason for the FAILED message from OP below:
toelen said:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.168s
Click to expand...
Click to collapse

Unbrick

Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks

frencisis said:
Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks
Click to expand...
Click to collapse
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry

danifilth4king said:
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry
Click to expand...
Click to collapse
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>

frencisis said:
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>
Click to expand...
Click to collapse
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/

danifilth4king said:
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/
Click to expand...
Click to collapse
I've tried to contact Funky Huawei, but they answered to me that: "Unfortunately in your situation recovery might not be possible".
So the last one is to try with warranty into Huawei service.
I hope they could repair it with less money as possible. Maybe they will replace the main board or just re flash he firmware with special method?:crying:

not possible to flash firmware in downloade mode?

mrt box

elvis87 said:
mrt box
Click to expand...
Click to collapse
Have you seriously just answered a 2 years old thread?..

Dude, I have the same problem with a P20 Pro since january!

Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.

deucecorp said:
Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.
Click to expand...
Click to collapse
Can I pm you for details?

how to flash intercepted Pie OTA with unlocked bootloader?

My bootloader unlocked RETEU 1900-7 is running 8.0 November 2018 update on slot B and received the OTA today. But no matter what I tried, it failed to install.
This is strange. I have received one OTA (8.0 security patch) once and could install it.
I tried
removing Magisk
fastboot oem lock
but still no luck.
So I have picked the OTA payload.bin and have converted it to several fastboot flashable images.
But I get more images than I have previously seen, e.g. cmnlib64.img. And flashing those images fail all the same way:
Code:
C:\Users\Olaf\Downloads\ROM9\flashable>mfastboot flash xbl_a xbl.img
target max-sparse-size: 256MB
sending 'xbl_a' (2247 KB)...
OKAY [ 0.062s]
writing 'xbl_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.078s
The usual stuff like system.img installs just fine, even with a 3 GB system.img. But when I say "fastboot set_active a" and reboot, booting fails. "fastboot set_active b", and I am back at 8.0.
What can I try next?

oz42 said:
My bootloader unlocked RETEU 1900-7 is running 8.0 November 2018 update on slot B and received the OTA today. But no matter what I tried, it failed to install.
This is strange. I have received one OTA (8.0 security patch) once and could install it.
I tried
removing Magisk
fastboot oem lock
but still no luck.
So I have picked the OTA payload.bin and have converted it to several fastboot flashable images.
But I get more images than I have previously seen, e.g. cmnlib64.img. And flashing those images fail all the same way:
Code:
C:\Users\Olaf\Downloads\ROM9\flashable>mfastboot flash xbl_a xbl.img
target max-sparse-size: 256MB
sending 'xbl_a' (2247 KB)...
OKAY [ 0.062s]
writing 'xbl_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.078s
The usual stuff like system.img installs just fine, even with a 3 GB system.img. But when I say "fastboot set_active a" and reboot, booting fails. "fastboot set_active b", and I am back at 8.0.
What can I try next?
Click to expand...
Click to collapse
1) Keep bootloader unlocked.
2) Flash stock 9 retail firmware. Download it here. Make sure the flash script leaves 'userdata' alone.

It has worked well. Thanks!

Question Help installing LineageOS on Pixel 5a5g (Can't unlock)

Hey all, new poster but long time user of the site, just never needed an account until today lol. Anyways, just got a Pixel 5a5G that I am trying to install LineageOS on. I am following the instructions from here, and once I get to the point of flashing the vendor_boot partition, I receive this:
Code:
PS C:\Windows\system32> fastboot flash vendor_boot C:\Users\bobby\Downloads\vendor_boot.img
target reported max download size of 268435456 bytes
sending 'vendor_bootb' (98304 KB)...
OKAY [ 2.225s]
writing 'vendor_bootb'...
FAILED (remote: Not allowed to flash (vendor_bootb))
finished. total time: 2.307s
When running fastboost unlock bootloader, I receive this:
Code:
PS C:\Windows\system32> fastboot flashing unlock
...
(bootloader) Device already unlocked
OKAY [ 0.055s]
finished. total time: 0.056s
I have reflashed the stock firmware with the Android Flashing Tool to 13.0.0, both keeping the bootloader locked and unlocked. I have tried unlocking and relocking the bootloader. I used the utility's "full-flash" feature to flash both partitions, all to no avail. Research on here seems to point that the bootloader is locked, but fastboot says it isn't, settings is greyed out saying the bootloader is already unlocked, and fastboot mode on the phone says Device state: unlocked.
Any ideas?

Did you remove your screenlock and Google account before flashing?

Leberkuchen said:
Did you remove your screenlock and Google account before flashing?
Click to expand...
Click to collapse
Yes. I've flashed from a factory install with no passcode or account ever set. Same issue

From the output it's trying to write vendor_bootb??? Some combination of this should fix it:
-Make sure to use platform tools r33.0.3, the latest r34 has at least one known problem with fastboot and I don't trust it
-If you're using powershell you have to run the command as .\fastboot flash you can only run fastboot flash if you are in cmd
-Make sure both slots are on latest February firmware (probably not really necessary but a last ditch effort)