Develop Bugs

Can't update 1/2020 flash, phone stuck in bootloader please help!

ETA: YAY, I'M BACK UP AND RUNNING AFTER USING STOCK RECOVERY TO SIDELOAD THE FULL OTA. THANKS EVERYONE, YOU'VE MADE MY DAY!!!
Hello all, I'm hoping someone has some advice:
I downloaded the 1/2020 factory image, removed the -w from the .bat file so I didn't lose data, and tried to flash the update via fastboot. Unfortunately, after the phone rebooted into fastbootd during the process, I got an error that says "write to device failed" when sending product. I can't get my system back up, but I can reboot into bootloader and enter recovery. Here is the output from when I tried to flash-all.bat from my computer to write the january update:
PS C:\Users\lukef\Documents\Phone stuff\Pixel 3 XL\crosshatch-qq1a.200105.002> .\flash-all.bat
Sending 'bootloader_a' (8521 KB) OKAY [ 0.141s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.2-5946827
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.281s]
Finished. Total time: 0.672s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.062s
Sending 'radio_a' (71404 KB) OKAY [ 0.484s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00086-191011-B-5933466
(bootloader) Flashing partition modem_a
OKAY [ 0.297s]
Finished. Total time: 1.031s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 894Y03RLY
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.055s]
Checking 'version-bootloader' OKAY [ 0.050s]
Checking 'version-baseband' OKAY [ 0.046s]
Setting current slot to 'a' OKAY [ 0.062s]
extracting boot.img (64 MB) to disk... took 0.250s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.453s]
Writing 'boot_a' OKAY [ 0.203s]
extracting dtbo.img (8 MB) to disk... took 0.063s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.125s]
Writing 'dtbo_a' OKAY [ 0.063s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_a' OKAY [ 0.062s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.047s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 0.031s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.000s]
Resizing 'vendor_a' OKAY [ 0.010s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1984 MB) to disk... took 8.416s
archive does not contain 'product.sig'
Sending 'product' (2032548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Press any key to exit...
This happens with both the .002 factory image (the correct one for my at&t phone), and the .003 TMO/Fi image. Anyone have any ideas? I'm desperate!

lukefgoogler said:
Hello all, I'm hoping someone has some advice:
I downloaded the 1/2020 factory image, removed the -w from the .bat file so I didn't lose data, and tried to flash the update via fastboot. Unfortunately, after the phone rebooted into fastbootd during the process, I got an error that says "write to device failed" when sending product. I can't get my system back up, but I can reboot into bootloader and enter recovery. Here is the output from when I tried to flash-all.bat from my computer to write the january update:
...
archive does not contain 'product.sig'
Sending 'product' (2032548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Press any key to exit...
This happens with bothe the .002 factory image (the correct one for my at&t phone), and the .003 TMO/Fi image. Anyone have any ideas? I'm desperate!
Click to expand...
Click to collapse
Seems odd. Did you try a different cable or USB port? Do you have the latest ADB / SDK on your PC?

swieder711 said:
Seems odd. Did you try a different cable or USB port? Do you have the latest ADB / SDK on your PC?
Click to expand...
Click to collapse
Thanks for the quick reply, those are all good ideas. Before asking for help I tried 2 different USB ports and 2 different cables. I fully updated my Android Studio before starting this, which includes the latest SDK, platform tools, etc., I was current with everything before starting.I have no idea how to fix this, I haven't hears a lot of people having issues flashing the january update so I assume its something on my end. I DO use Magisk and Kirisakura custom kernel, but I dont know how to disable either one via fastboot, which is all I have available.

lukefgoogler said:
Thanks for the quick reply, those are all good ideas. Before asking for help I tried 2 different USB ports and 2 different cables. I fully updated my Android Studio before starting this, which includes the latest SDK, platform tools, etc., I was current with everything before starting.I have no idea how to fix this, I haven't hears a lot of people having issues flashing the january update so I assume its something on my end. I DO use Magisk and Kirisakura custom kernel, but I dont know how to disable either one via fastboot, which is all I have available.
Click to expand...
Click to collapse
Is there a way to disable Magisk via Fastboot? I was able install the December update with just -w removed. I had Magisk+modules enabled along with Kiris kernel installed. I haven't installed the Jan update yet because I am waiting for the new kernel.
Other than disabling Magisk, you might have to try installing the update with the -w option. Hopefully you have some good backups offline!

swieder711 said:
Is there a way to disable Magisk via Fastboot? I was able install the December update with just -w removed. I had Magisk+modules enabled along with Kiris kernel installed. I haven't installed the Jan update yet because I am waiting for the new kernel.
Other than disabling Magisk, you might have to try installing the update with the -w option. Hopefully you have some good backups offline!
Click to expand...
Click to collapse
I tried to do a factory reset via recovery, other than nuke my personal data it didn't seem to do much, still only able to boot to bootloader with either a or b partition active. Starting to get worried...

lukefgoogler said:
I tried to do a factory reset via recovery, other than nuke my personal data it didn't seem to do much, still only able to boot to bootloader with either a or b partition active. Starting to get worried...
Click to expand...
Click to collapse
Have you tried sideloading the OTA with the stock recovery?

To not lose data you need to flash the "Full Ota" image and not the factory one... Then you need to do nothing just flash it...
Also from your console output it seems that the image you downloaded is corrupted as it's missing files...

lukefgoogler said:
Hello all, I'm hoping someone has some advice:
I downloaded the 1/2020 factory image, removed the -w from the .bat file so I didn't lose data, and tried to flash the update via fastboot. Unfortunately, after the phone rebooted into fastbootd during the process, I got an error that says "write to device failed" when sending product. I can't get my system back up, but I can reboot into bootloader and enter recovery. Here is the output from when I tried to flash-all.bat from my computer to write the january update:
PS C:\Users\lukef\Documents\Phone stuff\Pixel 3 XL\crosshatch-qq1a.200105.002> .\flash-all.bat
Sending 'bootloader_a' (8521 KB) OKAY [ 0.141s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.2-5946827
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.281s]
Finished. Total time: 0.672s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.062s
Sending 'radio_a' (71404 KB) OKAY [ 0.484s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00086-191011-B-5933466
(bootloader) Flashing partition modem_a
OKAY [ 0.297s]
Finished. Total time: 1.031s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 894Y03RLY
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.055s]
Checking 'version-bootloader' OKAY [ 0.050s]
Checking 'version-baseband' OKAY [ 0.046s]
Setting current slot to 'a' OKAY [ 0.062s]
extracting boot.img (64 MB) to disk... took 0.250s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.453s]
Writing 'boot_a' OKAY [ 0.203s]
extracting dtbo.img (8 MB) to disk... took 0.063s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.125s]
Writing 'dtbo_a' OKAY [ 0.063s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_a' OKAY [ 0.062s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.047s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 0.031s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.000s]
Resizing 'vendor_a' OKAY [ 0.010s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1984 MB) to disk... took 8.416s
archive does not contain 'product.sig'
Sending 'product' (2032548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Press any key to exit...
This happens with both the .002 factory image (the correct one for my at&t phone), and the .003 TMO/Fi image. Anyone have any ideas? I'm desperate!
Click to expand...
Click to collapse
The failure at product started during Q beta. To this day, I have seen nobody with an exact reason for it, but there is a fairly easy solution. When the error happens, don't unplug anything or even turn off command prompt. You are still in fastbootd. Press a key on the computer to get back to a command line. Go to recovery on the phone, and start an OTA sideload. If you don't already have the OTA downloaded, you will need to do that. Going from fastbootd to recovery will get you the ability to run adb sideload XXX from command prompt. It will run, complete, change slots and you will not lose data. I have had to do it a few times with my wife's P3. This month before running the flash-all (without -w), I flashed the Dec stock boot.img to both slots and then while still in BL ran the flash-all. Guess what? It took just fine with no product failure.

lukefgoogler said:
Hello all, I'm hoping someone has some advice:
I downloaded the 1/2020 factory image, removed the -w from the .bat file so I didn't lose data, and tried to flash the update via fastboot. Unfortunately, after the phone rebooted into fastbootd during the process, I got an error that says "write to device failed" when sending product. I can't get my system back up, but I can reboot into bootloader and enter recovery. Here is the output from when I tried to flash-all.bat from my computer to write the january update:
PS C:\Users\lukef\Documents\Phone stuff\Pixel 3 XL\crosshatch-qq1a.200105.002> .\flash-all.bat
Sending 'bootloader_a' (8521 KB) OKAY [ 0.141s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.2-5946827
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.281s]
Finished. Total time: 0.672s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.062s
Sending 'radio_a' (71404 KB) OKAY [ 0.484s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g845-00086-191011-B-5933466
(bootloader) Flashing partition modem_a
OKAY [ 0.297s]
Finished. Total time: 1.031s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.047s
--------------------------------------------
Bootloader Version...: b1c1-0.2-5946827
Baseband Version.....: g845-00086-191011-B-5933466
Serial Number........: 894Y03RLY
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.055s]
Checking 'version-bootloader' OKAY [ 0.050s]
Checking 'version-baseband' OKAY [ 0.046s]
Setting current slot to 'a' OKAY [ 0.062s]
extracting boot.img (64 MB) to disk... took 0.250s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 0.453s]
Writing 'boot_a' OKAY [ 0.203s]
extracting dtbo.img (8 MB) to disk... took 0.063s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.125s]
Writing 'dtbo_a' OKAY [ 0.063s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB) OKAY [ 0.109s]
Writing 'vbmeta_a' OKAY [ 0.062s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.047s]
< waiting for any device >
Sending 'system_a' (4 KB) OKAY [ 0.000s]
Updating super partition OKAY [ 0.031s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.000s]
Resizing 'vendor_a' OKAY [ 0.010s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (1984 MB) to disk... took 8.416s
archive does not contain 'product.sig'
Sending 'product' (2032548 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Press any key to exit...
This happens with both the .002 factory image (the correct one for my at&t phone), and the .003 TMO/Fi image. Anyone have any ideas? I'm desperate!
Click to expand...
Click to collapse
Make sure the USB is not plugged into a charging port

I owe a big "Thank You!" to EVERYONE who replied, sideloading the full OTA using the stock recovery worked like a charm! (Wish I didn't wipe data when I was casting about for a fix...)
Thanks all, you rock.

Stuck on G after running flash-all.bat

Downloaded the most recent and correct firmware for the 3a XL. I unzipped it and ran flash-all.bat.
It has been stuck on G forever. I have tried to then run flash-all.bat from the August firmware and Android 10 with the same result, stuck on G.
Any help appreciated.

OKAY [ 0.300s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.2-6355063
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
OKAY [ 0.285s]
finished. total time: 0.600s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
target reported max download size of 268435456 bytes
sending 'radio' (73340 KB)...
OKAY [ 2.072s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00042-200421-B-6414611
(bootloader) Flashing partition modem_a
OKAY [ 0.564s]
finished. total time: 2.636s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.062s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: variable not found)
--------------------------------------------
Bootloader Version...: b4s4-0.2-6355063
Baseband Version.....: g670-00042-200421-B-6414611
Serial Number........: 937AX05B5P
--------------------------------------------
checking product...
OKAY [ 0.069s]
checking version-bootloader...
OKAY [ 0.062s]
checking version-baseband...
OKAY [ 0.054s]
sending 'boot' (65536 KB)...
OKAY [ 1.992s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.471s
Press any key to exit...

Is it failing to flash? Do I do flash-all.bat in fastboot?

Holysmoke99 said:
Is it failing to flash? Do I do flash-all.bat in fastboot?
Click to expand...
Click to collapse
You don't use the flash-all.bat in fastboot. You simply run the bat file (or equivalent) on your computer that you have downloaded the files to and hooked your phone up to. The directions are listed here: https://developers.google.com/android/images
That being said, it does appear to be failing for some reason. Triple check that you have downloaded the correct version for your phone and also check the SHA-256 checksum to ensure the file is not corrupted. Make sure you are on the latest Android SDK Platform Tools as well.

sic0048 said:
You don't use the flash-all.bat in fastboot. You simply run the bat file (or equivalent) on your computer that you have downloaded the files to and hooked your phone up to. The directions are listed here: https://developers.google.com/android/images
That being said, it does appear to be failing for some reason. Triple check that you have downloaded the correct version for your phone and also check the SHA-256 checksum to ensure the file is not corrupted. Make sure you are on the latest Android SDK Platform Tools as well.
Click to expand...
Click to collapse
I had the same issue with a Pixel 3 some time ago and the resolution was to use the latest Android SDK Platform Tools.

Can't flash bonito-sp1a.211105.002 ( 12.0.0 (SP1A.211105.002, Nov 2021) ) - "Not enough space"

So I'm having the weirdest issue right now and it's driving me crazy.
I have a Pixel 3a XL. All good. It prompted me about updates for a while and now I had some time to do it.
I grabbed the (title) rom file from Google's site, extracted it and changed "flash-all" so it would not wipe storage. (It's the -w switch).
Like I've done a 100 times already. Nothing fancy, nothing new.
I also removed all images from DCIM and my recordings, etc. So there was like a ton of space on the device when I started.
And yet... I run the script and I get this:
Code:
PS D:\_rom\bonito-sp1a.211105.002> .\flash-all.bat
target reported max download size of 268435456 bytes
sending 'bootloader' (8377 KB)...
OKAY [ 0.307s]
writing 'bootloader'...
(bootloader) Flashing Pack version b4s4-0.4-7617386
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition cmnlib_b
(bootloader) Flashing partition cmnlib64_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition storsec_b
OKAY [ 0.326s]
finished. total time: 0.635s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.051s
target reported max download size of 268435456 bytes
sending 'radio' (73372 KB)...
OKAY [ 1.873s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g670-00129-210806-B-7617386
(bootloader) Flashing partition modem_b
OKAY [ 0.473s]
finished. total time: 2.348s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
error: failed to load 'image-bonito-sp1a.211105.002.zip': Not enough space
Press any key to exit...
PS D:\_rom\bonito-sp1a.211105.002>
I am without a clue and I would really need my device.
Please help?
OS is Windows 11, ADB drivers are from the Google USB package (and fastboot commands go out as you can see so that should be fine).
Not sure what else could be amiss.

Okay, another "self-solved mistery".
I've had the latest platform-tools in my PATH, yet something must have messed it up.
So I ran "flash-all.bat" (while removing -w of course) and then once it gets stuck with "not enough space", I simply run the .exe file directly from the new platform-tools folder, with "update ....zip" and that worked.
Man, every update, something gives me a heart attack.

Question Xiaomi pad 5 fastboot error

Hello!
I'm writting this post because I have a problem and I'm going nuts. The only thing I want is to flash fastboot global version (I have the EU one). I flashed it and this is what I found:
product: nabu
erasing 'boot_ab'...
(bootloader) Partition boot_a erase successfully
(bootloader) Partition boot_b erase successfully
OKAY [ 0.017s]
finished. total time: 0.017s
target reported max download size of 805306368 bytes
sending 'crclist' (0 KB)...
OKAY [ 0.010s]
writing 'crclist'...
OKAY [ 0.007s]
finished. total time: 0.018s
target reported max download size of 805306368 bytes
sending 'sparsecrclist' (0 KB)...
OKAY [ 0.009s]
writing 'sparsecrclist'...
OKAY [ 0.003s]
finished. total time: 0.012s
target reported max download size of 805306368 bytes
sending 'xbl_ab' (4054 KB)...
OKAY [ 0.164s]
writing 'xbl_ab'...
(bootloader) Partition xbl_a flashed successfully
(bootloader) Partition xbl_b flashed successfully
OKAY [ 0.037s]
finished. total time: 0.201s
target reported max download size of 805306368 bytes
sending 'xbl_config_ab' (120 KB)...
OKAY [ 0.016s]
writing 'xbl_config_ab'...
(bootloader) Partition xbl_config_a flashed successfully
(bootloader) Partition xbl_config_b flashed successfully
OKAY [ 0.012s]
finished. total time: 0.028s
target reported max download size of 805306368 bytes
sending 'abl_ab' (204 KB)...
OKAY [ 0.013s]
writing 'abl_ab'...
(bootloader) Partition abl_a flashed successfully
(bootloader) Partition abl_b flashed successfully
OKAY [ 0.008s]
finished. total time: 0.021s
target reported max download size of 805306368 bytes
sending 'tz_ab' (3115 KB)...
OKAY [ 0.120s]
writing 'tz_ab'...
(bootloader) Partition tz_a flashed successfully
(bootloader) Partition tz_b flashed successfully
OKAY [ 0.021s]
finished. total time: 0.141s
target reported max download size of 805306368 bytes
sending 'hyp_ab' (476 KB)...
OKAY [ 0.025s]
writing 'hyp_ab'...
(bootloader) Partition hyp_a flashed successfully
(bootloader) Partition hyp_b flashed successfully
OKAY [ 0.012s]
finished. total time: 0.037s
target reported max download size of 805306368 bytes
sending 'devcfg_ab' (53 KB)...
OKAY [ 0.015s]
writing 'devcfg_ab'...
(bootloader) Partition devcfg_a flashed successfully
(bootloader) Partition devcfg_b flashed successfully
OKAY [ 0.010s]
finished. total time: 0.025s
target reported max download size of 805306368 bytes
sending 'storsec' (20 KB)...
OKAY [ 0.008s]
writing 'storsec'...
OKAY [ 0.005s]
finished. total time: 0.013s
target reported max download size of 805306368 bytes
sending 'bluetooth_ab' (1020 KB)...
OKAY [ 0.041s]
writing 'bluetooth_ab'...
(bootloader) Partition bluetooth_a flashed successfully
(bootloader) Partition bluetooth_b flashed successfully
OKAY [ 0.013s]
finished. total time: 0.055s
target reported max download size of 805306368 bytes
sending 'cmnlib_ab' (385 KB)...
OKAY [ 0.024s]
writing 'cmnlib_ab'...
(bootloader) Partition cmnlib_a flashed successfully
(bootloader) Partition cmnlib_b flashed successfully
OKAY [ 0.012s]
finished. total time: 0.036s
target reported max download size of 805306368 bytes
sending 'cmnlib64_ab' (503 KB)...
OKAY [ 0.025s]
writing 'cmnlib64_ab'...
(bootloader) Partition cmnlib64_a flashed successfully
(bootloader) Partition cmnlib64_b flashed successfully
OKAY [ 0.011s]
finished. total time: 0.036s
target reported max download size of 805306368 bytes
sending 'modem_ab' (108236 KB)...
OKAY [ 3.986s]
writing 'modem_ab'...
(bootloader) Partition modem_a flashed successfully
(bootloader) Partition modem_b flashed successfully
OKAY [ 0.437s]
finished. total time: 4.423s
target reported max download size of 805306368 bytes
sending 'dsp_ab' (65536 KB)...
OKAY [ 2.193s]
writing 'dsp_ab'...
(bootloader) Partition dsp_a flashed successfully
(bootloader) Partition dsp_b flashed successfully
OKAY [ 0.267s]
finished. total time: 2.460s
erasing 'metadata'...
FAILED (remote: Erase of metadata is not allowed in merging state)
finished. total time: 0.003s
Erase metadata error
I've changed the USB cable, the USB port, tryed a windows and linux pc, erased data with xiaomi's recovery... And no idea what else to do. The bootloader is unlocked. Thanks in advance.

Well, it seems I've hit the nail on the head. I have tried to flash by fasboot with linux and with windows, change the cable and ports, with different miflash... and nothing.
I found this link (https://source.android.com/devices/t...l_ab/implement) to know what happens with the fastboot protocols because of the "merging state" problem, so I tried the following command to find out what status the tablet was in: fastboot getvar snapshot-update-status. It said it was in "merging" As a last resort I went to the miui updater and downloaded the rom from there again and updated from it. It was updated and I entered the same command again for fastboot: fastboot getvar snapshot-update-status. It said it was set to "none". From there I flashed the rom by fastboot running flash_all.bat and I have the global rom.
For those who, having the same problem as me, do not boot the tablet and go back to fastboot automatically, take the boot.img of the fastboot rom from the area that had the rom (in my case it was the European one) and open the cmd and put the following command: fastboot flash boot boot.img. Reboot and it should be back to normal. All this should work as long as you have the same error as me and the data and metadata partitions have not been deleted. I hope that it would be useful to someone.

Question Unlocked PAD 5 only shows red fastboot after Update to nabu_eea_global_images_V14.0.4.0.TKXEUXM

So here i am.
I've unlocked my Tab 5 after 7 days of waiting and decied to use the xiaoMiTool v2 to update to the nabu_eea_global_images_V14.0.4.0.TKXEUXM rom. Unfortunately after the successfull flash the tablets reboots 4-5 times and then shows me "fastboot" in red letters.
I'Ve tried to reflash the nabu_eea_global_images_V14.0.4.0.TKXEUXM again but it always ends up bootlooping and showing me the red fastboot letters.
I thought that just flashing the v14 Image over the fastboot option would let me start over (main goal is getting root/magsik).
Did i select the wrong update/image? I would have expected that little miui fastboot android splash screen and red letters seem wrong
Tablet came with miui 13.0.5. and I'm in Germany, that's why I chooses the Europe image with the toolkit.
Just tried to reflash the Global Firmware which also worked and it seems i'm able to go into recovery before all 5 bootloops are happening. So i can access fastboot and i'm able to access miui recovery 5.0 when the first boot happens.
TL;DR and the "Solution"
Flashing V13 worked - V14 did not. So i will update it over android and then root ;-)

Seelbreaker said:
So here i am.
I've unlocked my Tab 5 after 7 days of waiting and decied to use the xiaoMiTool v2 to update to the nabu_eea_global_images_V14.0.4.0.TKXEUXM rom. Unfortunately after the successfull flash the tablets reboots 4-5 times and then shows me "fastboot" in red letters.
I'Ve tried to reflash the nabu_eea_global_images_V14.0.4.0.TKXEUXM again but it always ends up bootlooping and showing me the red fastboot letters.
I thought that just flashing the v14 Image over the fastboot option would let me start over (main goal is getting root/magsik).
Did i select the wrong update/image? I would have expected that little miui fastboot android splash screen and red letters seem wrong
Tablet came with miui 13.0.5. and I'm in Germany, that's why I chooses the Europe image with the toolkit.
Just tried to reflash the Global Firmware which also worked and it seems i'm able to go into recovery before all 5 bootloops are happening. So i can access fastboot and i'm able to access miui recovery 5.0 when the first boot happens.
Click to expand...
Click to collapse
Have you tried re-downloading the file, maybe it's corrupt... https://xiaomifirmwareupdater.com/archive/miui/nabu/
Also, varify the download MD5 sum before flashing. Question; did you note the original ROM version - was it TKXEUXM or TKXMIXM? The latter is global, former EU ROM
Have you also tried with different flashing tool - https://miflashpro.com/ (ignore the box that opens to sign into MiAccount, just close that box if you use this tool)
When you do get it working, here's a good guide for pulling boot img and rooting Guide
OH and... Which ever tool you use to flash your device be sure to CHECK FLASH ALL, not flash all and lock

If you have only used Xiaomi Tool V2 and downloaded/flashed ROM automatically, would you like me to provide you with steps to flash fastboot rom using MiFlash Pro (MiFlash)??

Thanks for your reply!
No unfortunately i did not note which version was installed at the beginning.
I've let the XiaomiTool2 do the downloading because i assume those tools would check the md5 and tried Global, EU and "Other" Region but it did not help.
Also the tgz files don't have their md5 setup And miflashpro is always asking for flash skripts (which so far only got generated by the XiaomiToolv2)
The flash in fastboot goes completely trough but then it bootloops the whole time until it stays on fastboot.
At the beginning of the bootlops i'm also able to get into the recovery and then into sideload mode (because recovery is unauthorized) but flashing trough sideload fails 33 seconds after starting the flash and then immediately reboots.
I would have expected that atleast either the global or EU miui Rom would work if i flashed it trough fastboot but so far i did not have success.
I only know that i have miui 13.0.5 installed but i guess it shouldn't be a problem to flash 14.x.

reg66 said:
If you have only used Xiaomi Tool V2 and downloaded/flashed ROM automatically, would you like me to provide you with steps to flash fastboot rom using MiFlash Pro (MiFlash)??
Click to expand...
Click to collapse
Xiaomi Tool V2:
Done with EU set in the tool which automatically downloads/downloaded
nabu_eea_global_images_V14.0.4.0.TKXEUXM_20230305.0000.00_13.0_eea_d3eaf75a6f.tgz
1. Start the Tool
2. Agree the Disclaimer
3. wait till the drivers are installed
4. Select right option: "My Device is bricked I want to unbrick it"
5. OK, I understand
6. Device is charged --> Ok, I understand
7. Search for connected devices
- Device is in fastboot and shows serial and status fastboot
- Codename, Brand and Model are unknown
- Select that Device
8. Select my Device from the list (as it isn't recognized) (nabu - Xiaomi Pad 5)
9. Flashing starts (since the tgz has been downloaded already)
10. Flash done and automatically reboots
7 bootloops later (only seeing the android logo and the unlock icon) it shows fastboot and i can start the flashing process again.
At the beginning of the bootloops after the flash i'm able to get into the recovery by pressing Volume up.
But after the bootloops are done i can't seem to go into recovery mode.
Also here is the output from the flash_all.bat which gets created by the tool:
Spoiler: output from flash_all.bat
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>flash_all.bat
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot getvar product 2>&1 | findstr /r /c:"^product: *nabu" || echo Missmatching image and device
product: nabu
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot getvar product 2>&1 | findstr /r /c:"^product: *nabu" || exit /B 1
product: nabu
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>if exist C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\anti_version.txt (for /F "delims==" %a in (C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\anti_version.txt) do (set CURRENT_ANTI_VER=%a ) )
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>if [1] EQU [] set CURRENT_ANTI_VER=1
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>for /F "tokens=2 delims=: " %i in ('fastboot getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>(set version=1 )
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>if [1] EQU [] set version=0
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>set anticheck="antirollback check pass"
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>if 1 GTR 1 set anticheck="Current device antirollback version is greater than this pakcage"
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>echo "antirollback check pass" | findstr /r /c:"pass" ||
"antirollback check pass"
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot erase boot_ab ||
Erasing 'boot_ab' (bootloader) Partition boot_a erase successfully
(bootloader) Partition boot_b erase successfully
OKAY [ 0.026s]
Finished. Total time: 0.035s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash crclist C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\crclist.txt ||
Sending 'crclist' (0 KB) OKAY [ 0.006s]
Writing 'crclist' OKAY [ 0.006s]
Finished. Total time: 0.027s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash sparsecrclist C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\sparsecrclist.txt ||
Sending 'sparsecrclist' (0 KB) OKAY [ 0.015s]
Writing 'sparsecrclist' OKAY [ 0.003s]
Finished. Total time: 0.032s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash xbl_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\xbl.elf ||
Sending 'xbl_ab' (4054 KB) OKAY [ 0.103s]
Writing 'xbl_ab' (bootloader) Partition xbl_a flashed successfully
(bootloader) Partition xbl_b flashed successfully
OKAY [ 0.031s]
Finished. Total time: 0.155s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash xbl_config_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\xbl_config.elf ||
Sending 'xbl_config_ab' (120 KB) OKAY [ 0.017s]
Writing 'xbl_config_ab' (bootloader) Partition xbl_config_a flashed successfully
(bootloader) Partition xbl_config_b flashed successfully
OKAY [ 0.013s]
Finished. Total time: 0.046s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash abl_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\abl.elf ||
Sending 'abl_ab' (204 KB) OKAY [ 0.012s]
Writing 'abl_ab' (bootloader) Partition abl_a flashed successfully
(bootloader) Partition abl_b flashed successfully
OKAY [ 0.011s]
Finished. Total time: 0.044s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash tz_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\tz.mbn ||
Sending 'tz_ab' (3115 KB) OKAY [ 0.083s]
Writing 'tz_ab' (bootloader) Partition tz_a flashed successfully
(bootloader) Partition tz_b flashed successfully
OKAY [ 0.050s]
Finished. Total time: 0.154s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash hyp_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\hyp.mbn ||
Sending 'hyp_ab' (476 KB) OKAY [ 0.017s]
Writing 'hyp_ab' (bootloader) Partition hyp_a flashed successfully
(bootloader) Partition hyp_b flashed successfully
OKAY [ 0.014s]
Finished. Total time: 0.049s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash devcfg_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\devcfg.mbn ||
Sending 'devcfg_ab' (53 KB) OKAY [ 0.016s]
Writing 'devcfg_ab' (bootloader) Partition devcfg_a flashed successfully
(bootloader) Partition devcfg_b flashed successfully
OKAY [ 0.009s]
Finished. Total time: 0.041s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash storsec C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\storsec.mbn ||
Sending 'storsec' (20 KB) OKAY [ 0.010s]
Writing 'storsec' OKAY [ 0.006s]
Finished. Total time: 0.033s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash bluetooth_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\BTFM.bin ||
Sending 'bluetooth_ab' (1020 KB) OKAY [ 0.032s]
Writing 'bluetooth_ab' (bootloader) Partition bluetooth_a flashed successfully
(bootloader) Partition bluetooth_b flashed successfully
OKAY [ 0.024s]
Finished. Total time: 0.073s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash cmnlib_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\cmnlib.mbn ||
Sending 'cmnlib_ab' (385 KB) OKAY [ 0.023s]
Writing 'cmnlib_ab' (bootloader) Partition cmnlib_a flashed successfully
(bootloader) Partition cmnlib_b flashed successfully
OKAY [ 0.016s]
Finished. Total time: 0.058s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash cmnlib64_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\cmnlib64.mbn ||
Sending 'cmnlib64_ab' (503 KB) OKAY [ 0.021s]
Writing 'cmnlib64_ab' (bootloader) Partition cmnlib64_a flashed successfully
(bootloader) Partition cmnlib64_b flashed successfully
OKAY [ 0.014s]
Finished. Total time: 0.055s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash modem_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\NON-HLOS.bin ||
Sending 'modem_ab' (108236 KB) OKAY [ 2.565s]
Writing 'modem_ab' (bootloader) Partition modem_a flashed successfully
(bootloader) Partition modem_b flashed successfully
OKAY [ 0.783s]
Finished. Total time: 3.366s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash dsp_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\dspso.bin ||
Sending 'dsp_ab' (65536 KB) OKAY [ 1.546s]
Writing 'dsp_ab' (bootloader) Partition dsp_a flashed successfully
(bootloader) Partition dsp_b flashed successfully
OKAY [ 0.449s]
Finished. Total time: 2.019s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash keymaster_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\km41.mbn ||
Sending 'keymaster_ab' (273 KB) OKAY [ 0.019s]
Writing 'keymaster_ab' (bootloader) Partition keymaster_a flashed successfully
(bootloader) Partition keymaster_b flashed successfully
OKAY [ 0.011s]
Finished. Total time: 0.058s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash aop_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\aop.mbn ||
Sending 'aop_ab' (196 KB) OKAY [ 0.016s]
Writing 'aop_ab' (bootloader) Partition aop_a flashed successfully
(bootloader) Partition aop_b flashed successfully
OKAY [ 0.012s]
Finished. Total time: 0.045s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash qupfw_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\qupv3fw.elf ||
Sending 'qupfw_ab' (69 KB) OKAY [ 0.006s]
Writing 'qupfw_ab' (bootloader) Partition qupfw_a flashed successfully
(bootloader) Partition qupfw_b flashed successfully
OKAY [ 0.010s]
Finished. Total time: 0.033s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot erase imagefv_ab ||
Erasing 'imagefv_ab' (bootloader) Partition imagefv_a erase successfully
(bootloader) Partition imagefv_b erase successfully
OKAY [ 0.013s]
Finished. Total time: 0.023s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash imagefv_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\imagefv.elf ||
Sending 'imagefv_ab' (2060 KB) OKAY [ 0.056s]
Writing 'imagefv_ab' (bootloader) Partition imagefv_a flashed successfully
(bootloader) Partition imagefv_b flashed successfully
OKAY [ 0.025s]
Finished. Total time: 0.103s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash uefisecapp_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\uefi_sec.mbn ||
Sending 'uefisecapp_ab' (122 KB) OKAY [ 0.013s]
Writing 'uefisecapp_ab' (bootloader) Partition uefisecapp_a flashed successfully
(bootloader) Partition uefisecapp_b flashed successfully
OKAY [ 0.011s]
Finished. Total time: 0.042s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash multiimgoem_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\multi_image.mbn ||
Sending 'multiimgoem_ab' (32 KB) OKAY [ 0.006s]
Writing 'multiimgoem_ab' (bootloader) Partition multiimgoem_a flashed successfully
(bootloader) Partition multiimgoem_b flashed successfully
OKAY [ 0.011s]
Finished. Total time: 0.035s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash super C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\super.img ||
Sending sparse 'super' 1/10 (722548 KB) OKAY [ 17.279s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 2/10 (744888 KB) OKAY [ 33.288s]
Writing 'super' OKAY [ 0.005s]
Sending sparse 'super' 3/10 (772940 KB) OKAY [ 34.978s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 4/10 (775676 KB) OKAY [ 35.538s]
Writing 'super' OKAY [ 0.005s]
Sending sparse 'super' 5/10 (786356 KB) OKAY [ 37.458s]
Writing 'super' OKAY [ 0.005s]
Sending sparse 'super' 6/10 (735148 KB) OKAY [ 36.288s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 7/10 (735060 KB) OKAY [ 34.237s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 8/10 (743876 KB) OKAY [ 32.977s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 9/10 (785057 KB) OKAY [ 34.347s]
Writing 'super' OKAY [ 0.005s]
Sending sparse 'super' 10/10 (478244 KB) OKAY [ 34.968s]
Writing 'super' OKAY [ 0.005s]
Finished. Total time: 331.443s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot erase metadata ||
Erasing 'metadata' OKAY [ 0.011s]
Finished. Total time: 21.497s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash metadata C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\metadata.img ||
Sending 'metadata' (48 KB) OKAY [ 0.005s]
Writing 'metadata' OKAY [ 0.008s]
Finished. Total time: 0.036s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash vbmeta_system_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\vbmeta_system.img ||
Sending 'vbmeta_system_ab' (4 KB) OKAY [ 0.013s]
Writing 'vbmeta_system_ab' (bootloader) Partition vbmeta_system_a flashed successfully
(bootloader) Partition vbmeta_system_b flashed successfully
OKAY [ 0.008s]
Finished. Total time: 0.035s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash vbmeta_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\vbmeta.img ||
Sending 'vbmeta_ab' (8 KB) OKAY [ 0.014s]
Writing 'vbmeta_ab' (bootloader) Partition vbmeta_a flashed successfully
(bootloader) Partition vbmeta_b flashed successfully
OKAY [ 0.008s]
Finished. Total time: 0.036s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash dtbo_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\dtbo.img ||
Sending 'dtbo_ab' (32768 KB) OKAY [ 0.769s]
Writing 'dtbo_ab' (bootloader) Partition dtbo_a flashed successfully
(bootloader) Partition dtbo_b flashed successfully
OKAY [ 0.240s]
Finished. Total time: 1.030s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash userdata C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\userdata.img ||
Sending 'userdata' (6136 KB) OKAY [ 0.147s]
Writing 'userdata' OKAY [ 0.183s]
Finished. Total time: 0.347s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash rescue C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\rescue.img ||
Sending 'rescue' (40 KB) OKAY [ 0.012s]
Writing 'rescue' OKAY [ 0.008s]
Finished. Total time: 3.529s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash vendor_boot_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\vendor_boot.img ||
Sending 'vendor_boot_ab' (98304 KB) OKAY [ 2.274s]
Writing 'vendor_boot_ab' (bootloader) Partition vendor_boot_a flashed successfully
(bootloader) Partition vendor_boot_b flashed successfully
OKAY [ 0.680s]
Finished. Total time: 2.972s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash cust C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\cust.img ||
Sending 'cust' (110024 KB) OKAY [ 2.615s]
Writing 'cust' OKAY [ 3.202s]
Finished. Total time: 5.843s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash boot_ab C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\boot.img ||
Sending 'boot_ab' (131072 KB) OKAY [ 3.085s]
Writing 'boot_ab' (bootloader) Partition boot_a flashed successfully
(bootloader) Partition boot_b flashed successfully
OKAY [ 0.920s]
Finished. Total time: 8.885s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot flash misc C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0\images\misc.img ||
Sending 'misc' (4096 KB) OKAY [ 0.105s]
Writing 'misc' OKAY [ 0.138s]
Finished. Total time: 0.263s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot set_active a ||
Setting current slot to 'a' OKAY [ 0.011s]
Finished. Total time: 0.015s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>fastboot reboot ||
Rebooting OKAY [ 0.002s]
Finished. Total time: 0.003s
C:\flash\nabu_eea_global_images_V14.0.4.0.TKXEUXM_13.0>
MiFlashPro:
1. Start the Application
2. Select MiFlash 2022.5.7.0
3. Select the Path to the extracted Package (extracted and prepared by XiaomiToolV2
4. Hit Refresh to see the Device
5. Hit Flash
Under configuration i had the defaults active which means nothing checked, no factory, main program set and Checkpoint has "\$fastboot -s .* lock" as an entry.
RawProgram xml and Patch xml are also empty.

Ok, so you have MiFlash Pro installed, right? Open it up and close the dialgue about signing in with Xiaomi account. Go to the 4th tab along the top 'Mi Flash' and select that.
Download the fastboot version at the bottom of this page (it's Global to try for now).
Extract the tgz file twice until you get a folder containing the images. Best to extract to the root of C: drive.
In Mi Flash click 'select' and point it to the main extracted folder of your ROM that contains the images folder and the RUN scripts.
Plug your phone into a USB 2.0 port in fastboot mode and click refresh in Mi Flash. Device should show under 'id'.
IMPORTANT: In Mi Flash, select 'clean all' in bottom right corner and NOT 'clean all and lock'
Click 'flash'.
Hopefully, fingers crossed you'll get flashed properly this time after 500+ seconds. Device will reboot when it's done. 1st boot takes some time. Mi Flash will probably give an error after flashing because the 'lock' wasn't done, but you don't want that anyway.
Good luck, report back when ur done if poss

Ahh, looks like you made another post while I was typing! Just incase something is up with Miflash tool V2 download, download it manually from the link in my post above and follow those instructions. Unfortunately there's no md5 to compare it with for that rom version on that site

Thank you very much for your help <3
I was always trying to install an V14 MIUI Version because obviously i wanted to have the latest version before starting the rooting and so on.
Now i just tried to flash a V13:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
And it just works like you would expect, or atleast it booted into the starter setup.
What a hazzle.
Never thought that flashing the 14.x version wouldn't work, so i guess i will update to the latest version within android/miui and then start the rooting process.
Thanks for giving me the link which explains how to extract the boot image, this will make it easier for me
And yeah, extracting the tgz files will give me the batch-files anyways which miiflash also takes (as long as i don't lock it. Altough you can unlock it again with the mi unlock tool since that happened to me ).

Seelbreaker said:
Thank you very much for your help <3
I was always trying to install an V14 MIUI Version because obviously i wanted to have the latest version before starting the rooting and so on.
Now i just tried to flash a V13:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
And it just works like you would expect, or atleast it booted into the starter setup.
What a hazzle.
Never thought that flashing the 14.x version wouldn't work, so i guess i will update to the latest version within android/miui and then start the rooting process.
Thanks for giving me the link which explains how to extract the boot image, this will make it easier for me
And yeah, extracting the tgz files will give me the batch-files anyways which miiflash also takes (as long as i don't lock it. Altough you can unlock it again with the mi unlock tool since that happened to me ).
Click to expand...
Click to collapse
Are you saying you're going to update each time via miui every update until you reach the latest?
Only I had a thought... You could try flashing/skipping to the last miui 13.1.4 before 14 was released.
(md5: eae12a3156a814d4ac6a7af801ab40b7)
Then flash miui 14 as before.

reg66 said:
Are you saying you're going to update each time via miui every update until you reach the latest?
Only I had a thought... You could try flashing/skipping to the last miui 13.1.4 before 14 was released here.
(md5: eae12a3156a814d4ac6a7af801ab40b7)
Then flash miui 14 as before.
Click to expand...
Click to collapse
No, i fastboot flashed to V13.1.5.0.SKXEUXM which worked (altough i can't even explain why the fastboot Flash to V14.x did not work) and after Android booted up and did the initial setup i've updated to the latest MIUI Version within Android which means i'm now on 14.0.4.0 (TKXEUXM).
Now i just gonna get my boot.img and then i can root.
But the recovery mode doesn't let me adb shell because i'm not authorized...​

Seelbreaker said:
No, i fastboot flashed to V13.1.5.0.SKXEUXM which worked (altough i can't even explain why the fastboot Flash to V14.x did not work) and after Android booted up and did the initial setup i've updated to the latest MIUI Version within Android which means i'm now on 14.0.4.0 (TKXEUXM).
Now i just gonna get my boot.img and then i can root.
But the recovery mode doesn't let me adb shell because i'm not authorized...​
Click to expand...
Click to collapse
Download 14.0.4.0.TKXEUXM fastboot rom and extract the tgz twice until you get the images folder. In images folder you'll find the boot.img for that EU version in order to root then flash

reg66 said:
Download 14.0.4.0.TKXEUXM fastboot rom and extract the tgz twice until you get the images folder. In images folder you'll find the boot.img for that EU version in order to root then flash
Click to expand...
Click to collapse
stupid me.
Yep, after unzipping these folders for some time, it just hit me while i was in the shower
Thanks again for your help, really appreciate that!

Seelbreaker said:
stupid me.
Yep, after unzipping these folders for some time, it just hit me while i was in the shower
Thanks again for your help, really appreciate that!
Click to expand...
Click to collapse
No worries, it dawned on me too that the other guide i linked you was using a custom recovery and that you're running stock miui, in which case the boot img is easily found as above. A big 'DOH' on both our parts!! Good luck with it all

I had the same problem. Why does flashing version 14 not work? any ideas?

opesel said:
I had the same problem. Why does flashing version 14 not work? any ideas?
Click to expand...
Click to collapse
Have you updated to latest/last 13 before flashing 14?

reg66 said:
Have you updated to latest/last 13 before flashing 14?
Click to expand...
Click to collapse
Yes I did, I just downloaded the latest 13 version and then flashes it and it worked, but the 14 doesn't.