How to unbrick my Huawei Mate 10 lite - Honor 10 Lite Questions & Answers

Hi guys,
My huawei unbrick when update firmware.
the current state is like this error mode
error!
Func NO: 15(bl31 image)
Error NO: 1(security verify failed!)
Fastboot mode&rescue works !
This info fastboot mode:
Microsoft Windows [Wersja 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Wszelkie prawa zastrzeżone.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-product-model
...
(bootloader) RNE-L21
OKAY [ 0.013s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar vendorcountrycou
ntrycountry
vendorcountrycountrycountry: hw/eu
finished. total time: 0.014s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :MorfuZ-*čĹŻ 3.6
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar rescue_enter_rec
overy
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.025s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-SYSTEM_
VERSION
...
(bootloader) :RNE-L21 8.0.0.304(C432CUSTC432D1)
OKAY [ 0.014s]
finished. total time: 0.015s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Please help me unbrick this phone sorry my bad english

soniqgsm said:
Hi guys,
My huawei unbrick when update firmware.
the current state is like this error mode
error!
Func NO: 15(bl31 image)
Error NO: 1(security verify failed!)
Fastboot mode&rescue works !
This info fastboot mode:
Microsoft Windows [Wersja 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Wszelkie prawa zastrzeżone.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-product-model
...
(bootloader) RNE-L21
OKAY [ 0.013s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar vendorcountrycou
ntrycountry
vendorcountrycountrycountry: hw/eu
finished. total time: 0.014s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :MorfuZ-*čĹŻ 3.6
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar rescue_enter_rec
overy
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.025s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-SYSTEM_
VERSION
...
(bootloader) :RNE-L21 8.0.0.304(C432CUSTC432D1)
OKAY [ 0.014s]
finished. total time: 0.015s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Please help me unbrick this phone sorry my bad english
Click to expand...
Click to collapse
Sorry mate, this is Forum is for the HONOR 10 Lite, not for Huawei...

Related

After de-brand, bootloader unlocked, but impossible flash boot.img

Hi
After de-brand, and upgraded to Nougat, bootloader isn't restored to locked
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.009s
But when i flash pre-rooted boot image,
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot rooted_b378_boot.img
target reported max download size of 471859200 bytes
sending 'boot' (16204 KB)...
OKAY [ 0.350s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.365s
Help me please

can anyone help me if I run fastboot oem unlock it says failed remote unknown command

can anyone help me plz when i run fastboot oem unlock it say failed remote unknown command
here is my full command line
Microsoft Windows [Version 10.0.18362.900]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
"my imei" device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
"my imei" fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.018s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell getprop ro.serialno
"my imei"
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem key "my imei through a md5 hash generator"
...
OKAY [ 0.004s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>"fastboot --version
'"fastboot --version' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem help
...
FAILED (remote: unknown command)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar info
getvar:info FAILED (remote: GetVar Variable Not found)
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>
FireHeart_Max said:
can anyone help me plz when i run fastboot oem unlock it say failed remote unknown command
here is my full command line
Microsoft Windows [Version 10.0.18362.900]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
"my imei" device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
"my imei" fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.018s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell getprop ro.serialno
"my imei"
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem key "my imei through a md5 hash generator"
...
OKAY [ 0.004s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>"fastboot --version
'"fastboot --version' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem help
...
FAILED (remote: unknown command)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar info
getvar:info FAILED (remote: GetVar Variable Not found)
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
use this command:
fastboot flashing unlock
you will see a message on your phone asking for yes or no to unlock flashing,
press volume + button and boom! flashing is now unlocked.
but you can only use this command after turning on OEM Unlocking in Developer Options.
see this thread below for more help.
Root Nokia 1 (TA-1066) (MT6737M) (Android 9 - Pie)
So, after trying more than a few methods I finally gained root on my TA-1066. 😴😪 If you also wanna root, here is how: 👇 To Root Nokia 1 (TA-1066) (Pie - Android 9) (Dual SIM) What you're gonna need: Working PC, 💻 Some Packet Data, 🌐 Some...
forum.xda-developers.com

(solved) Can't either unlock OEM or install recovery (Preflash validation failed)

Hello
I just purchased a cheap new Moto G7 Plus, only to install LineageOS on it. The phone is brand new and I just upgraded it to the latest Android 10.
I followed all instructions so far, and I am stuck, can't unlock the bootloader and/or install a recovery.
To unlock the bootloader I carefully followed instructions on the LineageOS wiki
Then I followed instructions on Motorola website
I received an email from Motorola with the unlock code
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock CODE_RECEIVED_IN_THE_MAIL
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: 0.016s
Despite the fact that it says OKAY, when I reboot in fastboot flash mode, I still see the message "oem_locked". So I am not totally sure that the unlock succeeded.
Then whatever I try, I can't install TWRP, see below :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
Z*****F5RR fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock CODE_RECEIVED_IN_THE_MAIL
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp-3.4.0-0-lake.img
target reported max download size of 536870912 bytes
sending 'boot' (30080 KB)...
OKAY [ 0.686s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.708s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.4.0-0-lake.img
downloading 'boot.img'...
OKAY [ 0.686s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.702s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I obviously googled a few time but can't find any working solution. Some says its because my OEM is still locked, others because the USB port or cable might be problematic. I tried on 5 USB ports and a USB hub and I have the same issue, and my cable is brand new. I also restarted the whole unlocking procedure, received another mail from Motorola, with exactly the same unlock key, unlocked 10 times, nothing changes.
Any hint ?
Cheers
Ok forget it, its solved. I am an idiot I forgot to activate developer mode in the settings
Fastboot boot twrp 3.4 infinitely?
Unlocked my oem, adp whenever I fastboot boot twrp 3.4 it just gets stuck on downloading. No fail code just stays on downloading infinitely. Would love some help!
same
Richard2707 said:
Unlocked my oem, adp whenever I fastboot boot twrp 3.4 it just gets stuck on downloading. No fail code just stays on downloading infinitely. Would love some help!
Click to expand...
Click to collapse
trying on my xt1965-2 and having this same issue, did you manage a workaround?
The twrp file needs to be in the correct location and the name needs to be exact.
I use linux so check up on which locations to use in windows.
But on linux I open a terminal in the folder where twrp is located.
So if the filename for twrp is for instance "twrp-3.3.1-0-lake.img", the command needs to be:
fastboot boot twrp-3.3.1-0-lake.img (NO spaces in the file name!)
Fastboot then pushes the file to the phone and boots it.

Flashing back to stock ends with errors

I was trying to go back to stock 10 from latest official lineage as I did few times before, but what I get is errors like below:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY225F37PD fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar max-sparse-size
getvar:max-sparse-size FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count-size: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'fb_mode_setfixes' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot flash partition gpt.bin
(bootloader) slot-countxes: not found
(bootloader) slot-suf: not found
(bootloader) slot-suffi: not found
(bootloader) partition-typ: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'partition' (37 KB)...
Then the flashing process hangs.
Has anyone have an idea what may be causing this behavior?
I tried different cables, different PC's (windows and linux), phone boots to lineage, fastboot mode states flashing unlocked, boots to TWRP or lineage recovery so all seems to be fine but obviously isn't.
Anyone else experienced a problem of this sort?
[SOLVED] If anyone is interested I came to this last idea and dug out the oldest laptop we have at home and it came through with minimal adb and fastboot!
No idea why, my bet is that this has to do with USB on three other computers I had used being 3.0 only and a 2.0 on the old ASUS.
Anyways, I'm happy I made it and hope this can help someone looking for a solution to a similar problem.

[ROM][13][amogus] AOSP 13.0

AOSP 13
This is a moto-common project release under the codename amogus. This build supports the following devices: rav, rav_t, sofia, sofiap, sofiap_ao, sofiap_sprout, sofiar.​
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's AOSP?
AOSP is Android as Google publish without any modifications.
Whats not working?
Speakerphone on sofia variants​
Instructions to install the ROM:
Reboot to bootloader:
Code:
adb reboot bootloader
The following will wipe your internal data:
Code:
fastboot -w
Code:
fastboot update package.zip
It will reboot your device to fastbootd, you might get the following warning:
Code:
FAILED (remote: 'Old partitions are not compatible with the new super layout; wipe needed')
, but you can continue with the following commands
Fastbootd:
Code:
fastboot flash product product.img
Code:
fastboot flash system system.img
Code:
fastboot flash vendor vendor.img
Code:
fastboot reboot
Downloads: Here
Source Code: Here
Sept 2: Fixed USB Mode Switching, Switched to new rebased kernel, Switched to EROFS
Sept 12: EGIS Fingerprint gestures fixed, Switch BtAudio to AIDL and September Patch level
Sept 28:
System Responsiveness has been tuned and improved
Introduce Multigenerational LRU Framework
Tune Dalvik Heap Sizes
Switched to QTI Thermal HAL
DT2W has been fixed for RAV (HIMAX) variants of amogus
Signature Spoofing support has been added to the ROM
Jan 26:
January Security Patch
Feb 27:
Feb security patch
Electimon said:
AOSP 13
This is a moto-common project release under the codename amogus. This build supports the following devices: rav, rav_t, sofia, sofiap, sofiap_ao, sofiap_sprout, sofiar.​
Click to expand...
Click to collapse
Great job! Thank you!
Would love to try but I can't downgrade :/
spiral777 said:
Great job! Thank you!
Would love to try but I can't downgrade :/
Click to expand...
Click to collapse
You can't downgrade? What do you mean by this?
Electimon said:
You can't downgrade? What do you mean by this?
Click to expand...
Click to collapse
I'm on a11, I don't have to downgrade to a10 to apply this update.zip?
spiral777 said:
I'm on a11, I don't have to downgrade to a10 to apply this update.zip?
Click to expand...
Click to collapse
No you don't, moto-common projects use custom vendors.
i got this to boot on my moto g fast thank you
edit: its still on android 11
just incase anyone might need it and something unexpected happens... https://support.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
spiral777 said:
i got this to boot on my moto g fast thank you
edit: its still on android 11
just incase anyone might need it and something unexpected happens... https://support.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.22000.856]
(c) Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
xxxxx fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.835s]
finished. total time: 0.835s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update package.zip
W/ziparchive(11136): Unable to open 'package.zip': No such file or directory
error: failed to open zip file 'package.zip': I/O error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 799954944 bytes
sending 'product_b' (273816 KB)...
OKAY [ 9.958s]
writing 'product_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 799954944 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/2 (778517 KB)...
OKAY [ 28.791s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 28.885s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vendor vendor.img
target reported max download size of 799954944 bytes
sending 'vendor_b' (471860 KB)...
OKAY [ 17.570s]
writing 'vendor_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.649s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.016s
spiral777 said:
Microsoft Windows [Version 10.0.22000.856]
(c) Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
xxxxx fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.835s]
finished. total time: 0.835s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update package.zip
W/ziparchive(11136): Unable to open 'package.zip': No such file or directory
error: failed to open zip file 'package.zip': I/O error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 799954944 bytes
sending 'product_b' (273816 KB)...
OKAY [ 9.958s]
writing 'product_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 799954944 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/2 (778517 KB)...
OKAY [ 28.791s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 28.885s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vendor vendor.img
target reported max download size of 799954944 bytes
sending 'vendor_b' (471860 KB)...
OKAY [ 17.570s]
writing 'vendor_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.649s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.016s
Click to expand...
Click to collapse
Uh you actually have to use the name of the zip in place of package.zip
Sept 2: Fixed USB Mode Switching, Switched to new rebased kernel, Switched to EROFS
So like are we able to go back to 11 if we don’t like 13?
TS_Brittany said:
So like are we able to go back to 11 if we don’t like 13?
Click to expand...
Click to collapse
Yes
Sept 12: EGIS Fingerprint gestures fixed, Switch BtAudio to AIDL and September Patch level
amogus
Truly an amogus moment
ive followed the install instructions as much as i can...factory reset...but this rom just bootloops on my moto g...anyone else get this to boot up?
spiral777 said:
ive followed the install instructions as much as i can...factory reset...but this rom just bootloops on my moto g...anyone else get this to boot up?
Click to expand...
Click to collapse
Can you show me the output of the commands?
Electimon said:
Can you show me the output of the commands?
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
xxxxx fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.835s]
finished. total time: 0.835s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update aosp_amogus-img-eng.electimon-1.zip
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 799954944 bytes
sending 'product_b' (273816 KB)...
OKAY [ 9.958s]
writing 'product_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 799954944 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/2 (778517 KB)...
OKAY [ 28.791s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 28.885s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vendor vendor.img
target reported max download size of 799954944 bytes
sending 'vendor_b' (471860 KB)...
OKAY [ 17.570s]
writing 'vendor_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.649s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.016s
on rav moto g fast, thank you
spiral777 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
xxxxx fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.835s]
finished. total time: 0.835s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update aosp_amogus-img-eng.electimon-1.zip
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 799954944 bytes
sending 'product_b' (273816 KB)...
OKAY [ 9.958s]
writing 'product_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 799954944 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/2 (778517 KB)...
OKAY [ 28.791s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 28.885s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vendor vendor.img
target reported max download size of 799954944 bytes
sending 'vendor_b' (471860 KB)...
OKAY [ 17.570s]
writing 'vendor_b'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.649s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.016s
on rav moto g fast, thank you
Click to expand...
Click to collapse
Please use official platform-tools and not ancient Minimal ADB and Fastboot from like 2015. Thanks.
touchscreen and fingerprint reader not working on my retus moto g fast.
Electimon said:
Please use official platform-tools and not ancient Minimal ADB and Fastboot from like 2015. Thanks.
Click to expand...
Click to collapse
updating platform tools worked ty
https://app.box.com/s/voj724lqdb7cc8z3i8xt6mx3wxc96e3p
but product, system, and vendor failed to flash from twrp

Categories

Resources