Can't flash vendor.img - Huawei P9 Questions & Answers

I'm trying to flash it using TWRP, but when it asks which partition to flash it to, my only options are Boot and Recovery. Vendor is not there (it is mounted, though).
when I try flashing it using fastboot, I get this:
Code:
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'vendor' (311613 KB)...
OKAY [ 7.933s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 7.940s

Exact same problem
D:\phone extracts>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (457331 KB)...
OKAY [ 10.760s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.768s

any help on this?

Same problem here on ANE-lx1
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (435194 KB)...
OKAY [ 16.808s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 16.808s

Sounds like your bootloader has been locked. Try unlocking before re-flashing

Related

Return to stock issues

Hello all,
I am attempting to reset my Nexus 6 XT1103 and I think I've tried everything.
I tried to run "flash-all.bat" and command shows:
Code:
C:\Users\Default.Default-PC>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3524 KB)...
OKAY [ 0.127s]
writing 'bootloader'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.145s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'radio' (48360 KB)...
OKAY [ 1.595s]
writing 'radio'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.616s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 2004185752 bytes
error: update package missing system.img
Press any key to exit...
When I try and run a single file piece by piece it shows:
Code:
C:\Users\Default.Default-PC>fastboot flash bootloader bootloader-angler-angler-02.01.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3524 KB)...
OKAY [ 0.126s]
writing 'bootloader'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.135s
I am running Windows 10 and all drivers up and operational. Has anyone ran into this before? I searched the forums but was unable to find the answer I needed.
Thanks in advance for your assistance!
Angler is code name for Nexus 6P. You are trying to flash wrong image.
https://developers.google.com/android/nexus/images#shamu
So I just happened to buy the 6P. Didn't even realize I was clicking it. Let's pretend this post was never here...
Sent from my Nexus 6P using Tapatalk

lg v10 h901 . Error message. Please Help .comd flash recovery not worck

:crying:
C:\Minimal ADB and Fastboot>fastboot flash recover twrp.img
target reported max download size of 536870912 bytes
sending 'recover' (32444 KB)...
OKAY [ 0.735s]
writing 'recover'...
FAILED (remote: unknown command)
finished. total time: 0.755s
help me pls

Failed Root and serious troubles with flashing stock ROM on MOTO G6 XT1925-4 (solved)

Hello everyone, I own a Moto g6 xt1925-4 and I decided to root the device. First thing I unlocked the bootloader, it worked (with bad key logo). Second, I flashed TWRP, which I downloaded the IMG of from the official thread here on XDA. Third, I flashed the no-verity modified image: now I think I made a mistake because I flashed a OPS image which I should suppose is Oreo but the device was already updated to PIE.
Then the troubles started. I couldn't flash magisk, so I tricked too much on the MOUNT page on TWRP, perhaps I have mounted system or storage, then I also pulled out the USB cable without safe ejection and in the end, when I rebooted the phone in Bootloader mode and pushed Start, nothing happened at all.
I thought then: I have to restore to stock. I followed the procedure on the thread here on XDA, and I should say, something happened, but strange.
Now the phone boots up, but goes in a kind of a strange bootloop, because sometimes it says the "hello moto", sometimes not, sometimes it even starts the initial configuration, but the screen flashes on and off at random, and a few centimeters of the bottom screen are black. This happened also on TWRP recovery, the bottom part of the screen appeared cut by 2/3 centimeters.
Now I surely made mistakes, but I can't get what's wrong, and most of all this in going to get me crazy. I'm near to desperation, so I pray you to help me, please!
This is the result of the stock firmware flash I tried twice. I can see a couple of "failed" and "no such files"
Microsoft Windows XP [Versione 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Programmi\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.020s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.090s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.250s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.461s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71577 KB)...
OKAY [ 10.255s]
writing 'modem'...
OKAY [ 0.571s]
finished. total time: 10.836s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (6780 KB)...
OKAY [ 2.464s]
writing 'fsg'...
OKAY [ 0.100s]
finished. total time: 2.564s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash bluetooth BTFM.bin
error: cannot load 'BTFM.bin': No such file or directory
C:\Programmi\Minimal ADB and Fastboot>fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin': No such file or directory
C:\Programmi\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 3.515s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.300s]
finished. total time: 3.815s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.0
target reported max download size of 534773760 bytes
sending 'system' (259756 KB)...
OKAY [ 65.294s]
writing 'system'...
OKAY [ 2.293s]
finished. total time: 67.587s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.1
target reported max download size of 534773760 bytes
sending 'system' (253441 KB)...
OKAY [ 27.379s]
writing 'system'...
OKAY [ 1.763s]
finished. total time: 29.142s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.2
target reported max download size of 534773760 bytes
sending 'system' (254074 KB)...
OKAY [ 32.957s]
writing 'system'...
OKAY [ 1.773s]
finished. total time: 34.730s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.3
target reported max download size of 534773760 bytes
sending 'system' (260545 KB)...
OKAY [ 44.554s]
writing 'system'...
OKAY [ 1.803s]
finished. total time: 46.357s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.4
target reported max download size of 534773760 bytes
sending 'system' (259733 KB)...
OKAY [ 28.171s]
writing 'system'...
OKAY [ 1.813s]
finished. total time: 29.983s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.5
target reported max download size of 534773760 bytes
sending 'system' (246724 KB)...
OKAY [ 36.092s]
writing 'system'...
OKAY [ 1.682s]
finished. total time: 37.794s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.6
target reported max download size of 534773760 bytes
sending 'system' (246141 KB)...
OKAY [ 24.425s]
writing 'system'...
OKAY [ 1.702s]
finished. total time: 26.148s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.7
target reported max download size of 534773760 bytes
sending 'system' (262029 KB)...
OKAY [ 26.448s]
writing 'system'...
OKAY [ 1.933s]
finished. total time: 28.391s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.8
target reported max download size of 534773760 bytes
sending 'system' (262001 KB)...
OKAY [ 26.198s]
writing 'system'...
OKAY [ 1.803s]
finished. total time: 28.010s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechu
nk.9
target reported max download size of 534773760 bytes
sending 'system' (25072 KB)...
OKAY [ 2.654s]
writing 'system'...
OKAY [ 0.170s]
finished. total time: 2.824s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash vendor vendor.img_sparsechu
nk.0
target reported max download size of 534773760 bytes
sending 'vendor' (260148 KB)...
OKAY [ 35.711s]
writing 'vendor'...
OKAY [ 2.023s]
finished. total time: 37.744s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash vendor vendor.img_sparsechu
nk.1
target reported max download size of 534773760 bytes
sending 'vendor' (178315 KB)...
OKAY [ 16.644s]
writing 'vendor'...
OKAY [ 1.412s]
finished. total time: 18.056s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.040s]
finished. total time: 0.040s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.080s]
finished. total time: 0.080s
C:\Programmi\Minimal ADB and Fastboot>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.010s]
finished. total time: 0.010s
C:\Programmi\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2182 KB)...
OKAY [ 0.681s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.751s
C:\Programmi\Minimal ADB and Fastboot>fastboot reboot
EDIT:
Good news, at least for me. I solved by flashing the PIE STOCK ROM, despite I liked OREO the most, I find this PIE slower and less smooth but anyways, that's it, I have my phone back.
But still..... I can't get the root, but that's fine, I'm still enjoying the feel of victory... maybe I'll try, some day...

Bricked my device Need URGENT help please look at the pics posted

i accidentally flashed a wrong rom and now it is stuck in fastboot and im unable to flash recovery or system through fastboot. i will show the error i get in picture below
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.428s]
writing 'recovery'...
OKAY [ 0.256s]
finished. total time: 1.687s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (41812 KB)...
OKAY [ 0.918s]
writing 'recovery'...
OKAY [ 0.176s]
finished. total time: 1.097s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot system raphael.tgz
fastboot: usage: unknown command system
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
375d8e65 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system raphael.tgz
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 3492589356 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.102s]
sending sparse 'system' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 3492589356 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 3492589356 is not a multiple of the block size 4096
OKAY [ 0.021s]
writing 'system' 1/1...
OKAY [ 0.003s]
finished. total time: 0.129s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (41812 KB)...
FAILED (remote: Error: Last flash failed : Bad Buffer Size)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.731s]
writing 'recovery'...
OKAY [ 0.250s]
finished. total time: 1.983s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system raphael.tgz
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 3492589356 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.025s]
sending sparse 'system' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 3492589356 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 3492589356 is not a multiple of the block size 4096
OKAY [ 0.034s]
writing 'system' 1/1...
OKAY [ 0.004s]
finished. total time: 0.124s
was trying to unbrick it by going to edl mode not working
Sending 'recovery' (65536 KB) OKAY [ 1.432s]
Writing 'recovery' OKAY [ 0.249s]
Finished. Total time: 5.519s
Sending 'boot.img' (65536 KB) OKAY [ 1.392s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Press any key to continue . . .
Use Xiaomi Flash Tool to Flash Stock Rom for your device.
Sent from my Redmi K20 Pro using Tapatalk
@albysprx @phantomDuck @Fantomduck please help guys
@albysprx @phantomDuck @Fantomduck please help guys
Are you trying to flash system without extracting it? It's kind of confusing so correct me if I'm wrong. From what I can gather you're trying to flash system.tgz, you need to extract the fastboot rom twice until you get system.img, move that to platform tools then open cmd and type "fastboot flash system system.img"
Or better yet once fastboot rom has been extracted properly flash the full rom

Question Help restoring Stock ROM [SOLVED]

So... I tried to unlock/root my Redmi Note 11 (SPES), and something went wrong. So now I am trying to fix it, restore to the stock ROM to try again.
How I broke it:
1. Unlocked the bootloader.
2. Installed probably the wrong TWRP (I installed twrp-3.6.2-12.1-21.06.22.img from https://razaoinfo.dl.sourceforge.ne...ld/Recovery-Spes/twrp-3.6.2-12.1-21.06.22.img )
3. I tried flashing said img using fastboot (fastboot flash recovery_a <img>, followed by fastboot flash recovery_b <img>, then fastboot boot <img>
4. Got into TWRP, flashed Magisk.
5. Got into ROM. Everything seems to work, I have root. Next day, I realize my bluetooth is not working.
Next day, I tried flashing another TWRP that I found linked in this forum (twrp-3.6.2_12-0-spes-Jabiyeff.img, downloaded from https://forum.xda-developers.com/t/...-redmi-note-11-and-how-do-i-flash-it.4466177/ post #4).
6. After flashing, ROM no longer boots, and just sends me to fastboot.
7. I checked again with fastboot, and.. it seems the recovery partition isn't there?
Code:
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.902s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.909s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.828s]
writing 'recovery_a'...
FAILED (remote: (recovery_a_b) No such partition)
finished. total time: 2.835s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.805s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 2.812s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.849s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.857s
C:\adb2>fastboot.exe boot twrp-3.6.2_12-0-spes-Jabiyeff.img #NOTE: Here I changed the active partition in this TWRP from B to A.
downloading 'boot.img'...
OKAY [ 2.790s]
booting...
OKAY [ 0.367s]
finished. total time: 3.159s
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.933s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.946s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.899s]
writing 'recovery_a'...
FAILED (remote: No such file or directory)
finished. total time: 2.918s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.931s]
writing 'recovery_b'...
FAILED (remote: No such file or directory)
finished. total time: 2.943s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.874s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.887s
So, I wonder if I should be concerned about not finding a recovery/recovery_a/recovery_b partition (I am pretty sure recovery_a/b where there when I flashed TWRP the first time).
So, I am following now this guide to install the stock ROM: https://xiaomistockrom.com/xiaomi-redmi-note-11
Am I on the right path? I want to check before proceeding, because... right now I have fast boot and can boot into TWRP using it, but if I do things incorrectly from now on, I could brick the device. So I wanted to ask for advice on what I am doing first here.
TIA.
It's fairly difficult to hard brick a device. Most of the time you'll just end up soft bricking your device which is easy to fix as long as you can access bootloader mode. If you want to fully restore your device to default, you can download your stock rom (fastboot version) and flash using miflash.
Also yes, the guide you linked is correct.
Thanks, I managed to solve it.
The fastboot issue went away some time afterwards, and I could boot normally into the ROM, but... my bluetooth stopped working (which is really strange considering I only flashed the recovery partition). I tried flashing the bluetooth partition from the stock ROM's, but that didn't fix it.
So I tried flashing the stock ROM, following the previously linked guide (and that guide, not the guides that came bundled in the downloaded ROM, that one was for a different device, not a Xiaomi phone at all, weird!).
And now, I have bluetooth again. Thanks goodness for Migrate, I should be able to restore the rest of the device swiftly now.

Categories

Resources