Содержание
- Error reading sparse file xiaomi
- Can’t reinstall nothing to /system
- 3 Answers 3
Error reading sparse file xiaomi
Инструкция по установке (способ прошивки на ПК) :
Данная инструкция подразумевает разблокированный загрузчик на смартфоне, установленные ADB драйвера MTK на пк.
Прошивку для фастбут (Fastboot) распаковываем в корень диска «C:». Для удобства сокращаем имя папки с прошивкой (буквы, цифры в названии должны быть только латинские!). Открываем её и туда же распаковываем компоненты из архива во вложении — tools_r29.0.6-windows.zip.
Переводим аппарат в режим fastboot (выключаем, зажимаем кнопки включения и громкости минус, после вибрации отпускаем кнопку включения и ждём появления картинки с зайцем) и подключаем к ПК. Далее открываем терминал виндовс (в папке с файлами зажимаем Shift и по нажатию правой кнопки мыши выбираем Открыть окно команд / Или просто введите CMD в адресной строке в папке и нажмите Enter) и вводим следующие команды, после каждой нажимаем кнопку ентер(ввод):
fastboot devices
ответ должен быть в виде — «77ghtp738u5pkgg1 fastboot» — латинские буквы и цифры, это значит что пк видит ваш телефон. Так же в диспетчере устройств можно проверить, вверху дерева будет подключенное Андроид-устройство.
Если здесь все хорошо, далее пишем в терминале:
flash_all
(эта команда начисто прошьет. Gpay не будет работать)
или flash_all_lock
(эта команда начисто прошьет и заблокирует загрузчик. Gpay работать будет)
Выбираем один из вариантов. Начнется процесс прошивки, по окончании которого аппарат сам перезагрузится и только после этого можно отсоединять его от пк.
Сообщение отредактировал LexaSun — 07.06.22, 23:22
Источник
Can’t reinstall nothing to /system
I tried to update my Xiaomi Mi A2 to Android Pie since yesterday the Beta was Released. At first, I tried to install the official provided one, but after facing some errors, I installed the Treble version of the Android Pie Pixel Experience ROM.
It was working perfectly, but after installing Pixelify with Magisk, my WiFi stopped working, and I got the error MAC 02:00:00:00:00.
After trying some things with terminal apps and root, I opted for reinstalling the modem image, which I thought that could solve the problem, but instead, the phone didn’t turn on, it kept on the Android One screen. So after waiting for some hours, I decided to format the phone and lose all of my data.
I formatted the system partition with fastboot erase system_a and fastboot erase system_b , but when trying to reinstall the PixelExperienceP ROM, I receive this error again and again:
After that, I am not allowed to send any command to the phone until I restart de bootloader.
I have tried to install different ROMs, the stock one, other Android versions, but I get the same error on all of them.
Please, any ideas on how to solve my problem? I am really worried about having broken it. Thanks in advance.
3 Answers 3
I just solved it simply by trying and trying, changing cable, USB port, restarting computer.
Was facing the same problem with two devices (Google Pixel 4 and Samsung Galaxy S21 Ultra 5G (Exynos variant))
I’ve found that, in my case, for both the devices discussed, using the vendor provided flashing solutions (Odin 3.14.4 for Samsung and «flash-all.bat» script for Google) the procedure was stuck/hanging on some large transfer for both the devices (Odin was simply stuck at the «SYSTEM» phase ( system.img ) with the green progress bar halted/not moving while the Google script returned the infamous » FAILED (Error reading sparse file) » error message after » Sending sparse ‘vendor_b 1/2 (524284 KB) «).
I’ve tried leaving the devices connected for over 30 minutes, changing/swapping USB cables, upgrading/downgrading USB/Thunderbolt drivers, BIOS/UEFI to no avail.. I’ve retried the procedure many times with no different outcome..
I’ve then connected the devices to a USB 3.0 «A» port of my motherboard (Gigabyte Z170X-UD5 TH — fully updated Windows 10 1607 LTSB) instead of the USB/Thunderbolt enabled USB «C» port on the rear that I was previously using and to my surprise it worked flawlessy for both on the first try!
No idea if the Thunderbolt IC (or maybe its driver) was the culprit TBH but it seems so..
Источник
I tried to install CalyxOS on my Pixel 4a(5G). The installation went well until an error occurs (see log). I wasn’t able to start anything. I just came to the fastboot menu — nothing more worked. So I went through a complete re-installation by using the [Google Factory Flash][1], which worked very well. After that, I was able to Start Google Android again like it was brand new out of the factory.
So I downloaded the image again and tried to install CalyxOS the second time, but unfortunately, the process stopped again at the exact same step. What should I do? I now have to flash again, but then? Any Ideas?
Android Factory Image Flasher version 1.0.3
Extracting bramble-factory-2.7.0.zip
Downloading https://dl.google.com/android/repository/platform-tools_r30.0.4-windows.zip
Downloading... 8.4 MB downloaded
Verifying platform-tools_r30.0.4-windows.zip
Extracting platform-tools_r30.0.4-windows.zip
1. Connect to a wifi network and ensure that no SIM cards are installed
2. Enable Developer Options on device (Settings -> About Phone -> tap "Build number" 7 times)
3. Enable USB debugging on device (Settings -> System -> Advanced -> Developer Options) and allow the computer to debug (hit "OK" on the popup when USB is connected)
4. Enable OEM Unlocking (in the same Developer Options menu)
Press ENTER to continue
Detected bramble 14221JECB06677
Devices to be flashed:
bramble 14221JECB06677
Press ENTER to continue
Unlocking bramble 14221JECB06677 bootloader...
5. Please use the volume and power keys on the device to unlock the bootloader
Flashing bramble 14221JECB06677 bootloader...
Sending 'bootloader_a' (8754 KB) OKAY [ 0.338s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b5-0.3-7241846
(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 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 devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition featenabler_a
(bootloader) Flashing partition logfs
OKAY [ 0.260s]
Finished. Total time: 0.863s
Rebooting into bootloader OKAY [ 0.048s]
Finished. Total time: 0.052s
< waiting for any device >
Sending 'radio_a' (149780 KB) OKAY [ 3.948s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g7250-00132-210419-B-7294132
(bootloader) Flashing partition modem_a
OKAY [ 0.809s]
Finished. Total time: 5.023s
Rebooting into bootloader OKAY [ 0.048s]
Finished. Total time: 0.052s
< waiting for any device >
Erasing 'avb_custom_key' OKAY [ 0.215s]
Finished. Total time: 0.339s
Sending 'avb_custom_key' (0 KB) OKAY [ 0.138s]
Writing 'avb_custom_key' OKAY [ 0.221s]
Finished. Total time: 0.556s
Rebooting into bootloader OKAY [ 0.047s]
Finished. Total time: 0.051s
< waiting for any device >
--------------------------------------------
Bootloader Version...: b5-0.3-7241846
Baseband Version.....: g7250-00132-210419-B-7294132
Serial Number........: 14221JECB06677
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.067s]
Checking 'version-bootloader' OKAY [ 0.067s]
Checking 'version-baseband' OKAY [ 0.066s]
Setting current slot to 'a' OKAY [ 0.082s]
extracting boot.img (96 MB) to disk... took 0.268s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 2.688s]
Writing 'boot_a' OKAY [ 0.482s]
extracting dtbo.img (16 MB) to disk... took 0.040s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (16384 KB) OKAY [ 0.478s]
Writing 'dtbo_a' OKAY [ 0.143s]
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' (8 KB) OKAY [ 0.138s]
Writing 'vbmeta_a' OKAY [ 0.075s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.138s]
Writing 'vbmeta_system_a' OKAY [ 0.075s]
extracting vendor_boot.img (96 MB) to disk... took 0.196s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.419s]
Writing 'vendor_boot_a' OKAY [ 0.469s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.065s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.002s]
Updating super partition OKAY [ 0.008s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'system_ext_a' OKAY [ 0.005s]
Resizing 'system_b' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.005s]
Resizing 'vendor_b' OKAY [ 0.005s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (994 MB) to disk... took 3.752s
archive does not contain 'product.sig'
Resizing 'product_a' OKAY [ 0.005s]
Sending sparse 'product_a' 1/4 (262140 KB) OKAY [ 6.571s]
Writing 'product_a' OKAY [ 2.533s]
Sending sparse 'product_a' 2/4 (262140 KB) OKAY [ 6.435s]
Writing 'product_a' OKAY [ 1.567s]
Sending sparse 'product_a' 3/4 (262140 KB) OKAY [ 6.438s]
Writing 'product_a' OKAY [ 1.553s]
Sending sparse 'product_a' 4/4 (231696 KB) OKAY [ 5.773s]
Writing 'product_a' OKAY [ 1.381s]
extracting system.img (801 MB) to disk... took 3.667s
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.005s]
Sending sparse 'system_a' 1/4 (262140 KB) OKAY [ 6.492s]
Writing 'system_a' OKAY [ 2.535s]
Sending sparse 'system_a' 2/4 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Rebooting into bootloader
asked Jul 23, 2021 at 8:26
I was having FAILED (Error reading sparse file) issue when I was connecting the USB cable to the dock of my laptop.
Instead connecting the USB Type-A end directly to my laptop port helped me fix this problem. Be mindful of USB 3.0, USB Type C and USB 2.0 ports (try with all) and run your commands in command prompt in Administrator mode.
answered Oct 29, 2021 at 4:00
zeitgeistzeitgeist
76011 silver badges17 bronze badges
SOLVED: First, I had to change the USB Cable. I got an error during installation all the time. The cabel USB-C<>USB-A from my old HTC was the solution….very strange but just after using it, my Google 4a(5G) was detected correctly from my PC.
I also installed ADB manually before lunching the device flasher.
sudo apt-get install adb
The error also pooped up, because I had to re-approve on the device, that USB-Debugging is allowed (simply de-activating for giving the approval to my PC). I checked it with:
adb devices
After that my device was detected correctly.
Then I ran the flasher and everything went fine.
answered Jul 24, 2021 at 14:51
MiFlash ver: 2020.3.14.0 & 2019.12.6.0.
Latest platform-tools installed systemwide. I also tried some outdated but I got an even worse result.
Phone: Mi 9T Pro 6/64 Global with unlocked bootloader.
I softbricked my phone trying to flash a ROM but for some weird reason I can’t flash MIUI on fastboot. I’ve tried to flash the following builds:
-
V12.0.1.0.QFKMIXM (downloaded from XiaomiFirmwareUpdater)
-
V12.0.2.0.QFKMIXM (downloaded from 3 different places: Xiaomi, XiaomiFirmwareUpdater and with XiaoMiTool V2)
I’ve also confirmed that the phone is indeed unlocked (that’s what the MiUnlockTool tells me as you can see in the printscreen here).
The error I get is the following:
Sending sparse ‘vendor’ 1/2 (773888 KB) FAILED (Error reading sparse file)
Logs and printscreens here:
LOG
PRINTSCREEN
I’ve also tried other tools like MiFlashPro, XAFT (Xiaomi ADB / Fastboot Tools) and simply executing the script (in both Windows the .bat and Linux the .sh) but to no success.
For Linux I used FWUL.
I also tried 4 different computers but the result was always the same. The computers were:
-
AMD Ryzen 1600 based (with both Linux and Windows)
-
AMD Ryzen 2600 based *AMD A8-7410 based (with both Linux and Windows)
-
Intel Core i7 3632QM based
I think I should also tell that for some reason fastboot only works if I connect a phone to a USB hub.
I’ve tried many things but to no success. I’ve tried USB 2.0, USB 3.0 and USB 3.1 ports, still no success.
Only thing left is swapping the cable but as this is my first USB-C device I don’t have a spare one. And I bought this phone used and it came with every factory accessory except for the cable. I’ll try a new cable as soon as I can but maybe you guys know something that I don’t.
On a side note, I also tried flashing manually vendor alone and got the same result. I also tried to do the same with system and got the exact same error, so I suppose it has something to do with the sparse thingy. I also tried to do fastboot flash:raw xx xx.img but instead got an allocation error.
I can provide more info if needed. All ideas are welcome.
EDIT: it was the cable all along. Have a nice day 
-
#1
Привет друзья подскажите пожалуйста как быть в данной ситуаций принесли аппарат Xiaomi redmi Note 10T жаловолись на то что на 13 версий лагает клиент хотел откатиться до 12 miui
зашел на сайт
купить чтобы получить доступ к скрытому контенту.
это не реклама сайта скачал прошивку Global предварительно открыл загрузчик ну и начал шить через MiFlash20220507
MiFlash выдавал ошибку (error:Sending sparse ‘super’ 1/43 (130672 KB) FAILED (Error reading sparse file) в поисках решения я прошил прошивку
(Xiaomi Redmi Note 10T (Camellia) China Version Convert To Global Version) проблема была в моем кабели после замены кабеля прошивка пошла теперь у меня вечный перезапуска Fastboot. Потом прошил Global-КУ которая до замены кабеля не шылось
-
#2
Только что прошил на 13 Miui устройство запустилось но моя задача именно сделать откат до 12
-
#3
Это все что возможно .
купить чтобы получить доступ к скрытому контенту.
Отвязывайте бут , ставьте twrp дальше кастом .
-
#4
Это все что возможно .
купить чтобы получить доступ к скрытому контенту.
Отвязывайте бут , ставьте twrp дальше кастом .
понятно буду обговаривать с клиентам. А почему 12 miui крайняя не шеться через Fastboot загрузчик открыт что ему мешает ? ARB
-
#5
После прошивки он у вас грузиться не с того слота, так сказать. Была ситуация как у вас 1 в 1. Помогла смена слота загрузки через unlocktool.
-
#6
После прошивки он у вас грузиться не с того слота, так сказать. Была ситуация как у вас 1 в 1. Помогла смена слота загрузки через unlocktool.
попробую спасибо за совет
-
#7
После прошивки он у вас грузиться не с того слота, так сказать. Была ситуация как у вас 1 в 1. Помогла смена слота загрузки через unlocktool.
SET BOOT SLOT, во вкладке mediatec
Yogurt-Filled Chocolate Cauldrons
Cute chocolate «cauldrons» hold a cool, creamy orange-flavored yogurt in this recipe. The unfilled cups…
Provided by Taste of Home
Demi-Glace
This is my technique for veal demi-glace, and there’s not much to it. I’m going for a pure veal stock…
Provided by Chef John
Easy Butterfinger Cake
OMG!!! I had to make this cake this past Sunday for my Mary Kay party.. It was a huge hit. It was also…
Provided by vicky hunt
Pork Neck Slow Cooker Stew
Good food doesn’t always have to cost a fortune! Your family will love this. Full of flavor and easy…
Provided by Melissa Baldan
Steamed Parsley Red Potatoes
This is a very good potato dish , I stem baby red potatoes and smother them in real butter and parsley…
Provided by Karla Everett
Homemade Chicken Pot Pie
Sure you can make a quick Chicken Pot Pie using already made pie crust, canned soups, vegetables and…
Provided by Julia Ferguson
Red Velvet Pound Cake
This delicious red velvet pound cake is the perfect combination of flavors. Make sure the cake has cooled…
Provided by Taste of Home
Boudreaux’s Zydeco Stomp Gumbo
Dis is da toe curlin Texicajun hybrid of a classic dish. This will put a smile on everyone’s face that’s…
Provided by Lupe Boudreaux
Pesto Baked Pork Chops
This is a tender and delicious baked pork chop recipe, with an Italian flair.
Provided by larvia57
Previous
Next
FINALLY FOUND A FIX FOR THE «FILE READING ERROR»/»FAILED …
WebApr 23, 2015 Instead, I found a folder called «userdata_backup». I did the following steps and was able to launch PVZ AND keep my progress from before the «File reading …
From steamcommunity.com
See details »
INVALID — FAILED (ERROR READING SPARSE FILE) FASTBOOT: ERROR: …
WebJan 27, 2023 » Sending sparse ‘super’ 1/7 (777724 KB) FAILED (Error reading sparse file) fastboot: error: Command failed Rebooting » It does not reboot and I have to reboot device to fastboot myself to be able to try it again. But it doesnt work.. Solution: USB 2.0 …
From xiaomi.eu
See details »
WHAT NOW? INSTALLATION FAILURE… SENDING SPARSE ‘VENDOR_B’ 1/2 …
WebConnect to a wifi network and ensure that no SIM cards are installed 2. Enable Developer Options on device (Settings -> About Phone -> tap «Build number» 7 …
From reddit.com
See details »
ROM FLASHING — CAN’T REINSTALL NOTHING TO /SYSTEM — ANDROID …
WebI was having FAILED (Error reading sparse file) issue when I was connecting the USB cable to the dock of my laptop. Instead connecting the USB Type-A end directly to my …
From android.stackexchange.com
See details »
UNABLE TO FLASH STOCK GOOGLE PIXEL 3 — «SENDING SPARSE ‘VENDOR_A’ …
WebJan 31, 2019 Unable to flash stock Google Pixel 3 — «Sending sparse ‘vendor_a’ 1/2 (262140 KB) Hey I am trying to flash the factory image for Google Pixel 3. … File system …
From forum.xda-developers.com
See details »
BASH — FAILED TO INITIALIZE SPARSE-CHECKOUT — STACK OVERFLOW
WebMay 13, 2022 I upgraded git from 2.25.1 to 2.37.3 and now sparse cloning works. Unfortunately, the git version that is installed through the standard package repos on …
From stackoverflow.com
See details »
ERROR DURING INSTALLATION OF CALYXOS: SENDING SPARSE ‘SYSTEM_A’ 2/4 …
WebJul 23, 2021 I was having FAILED (Error reading sparse file) issue when I was connecting the USB cable to the dock of my laptop. Instead connecting the USB Type-A …
From stackoverflow.com
See details »
FAILED (ERROR READING SPARSE FILE) | XIAOMI EUROPEAN COMMUNITY
WebJan 4, 2022 Invalid FAILED (Error reading sparse file) fastboot: error: Command failed fastboot: error: Device does not support slots Just wanted to post this in case of anyone …
From xiaomi.eu
See details »
QUESTION [SOLVED] INVALID SPARSE FILE FORMAT AT HEADER …
WebMay 8, 2022 Invalid sparse file format at header magic after the flash continue, I reboot on BL, wipe data, reboot and go directly on standard fastboot…..can’t boot anymore on BL I …
From forum.xda-developers.com
See details »
OCTOBER UPDATE FAILING TO FLASH FROM FACTORY IMAGES ON PIXEL 2
WebThat was going to be next step, but I just fixed it. Tried flashing again from another PC, with an older version of ADB and FASTBOOT. Worked first time, no problems. Same file and …
From reddit.com
See details »
OS ERRORS 665 AND 1450 ARE REPORTED FOR SQL SERVER FILES
WebDec 29, 2022 How It Works: SQL Server Sparse Files (DBCC and Snapshot Databases) Revisited. How Database Snapshots Work. DBCC CHECKDB (Transact-SQL) [See …
From learn.microsoft.com
See details »
CANNOT FLASH FACTORY IMAGES TO GOOGLE PIXEL 2 XL
WebDec 30, 2017 2. Device: Google Pixel 2 XL (taimen) Carrier: Unlocked (purchased from the Play store) Image: image-taimen-opm1.171019.011.zip. Ultimately, I’m trying …
From android.stackexchange.com
See details »
INVALID SPARSE FILE FORMAT AT HEADER MAGIC FAILED TO READ …
WebNov 6, 2020 The text was updated successfully, but these errors were encountered:
From github.com
See details »
PIXEL 4 XL STUCK IN FASTBOOT: ‘ERROR BOOT PREPARE,’ NO RECOVERY
WebTurned on developer options, switched on OEM Unlock, switched on USB Debug, went into Fastboot: fastboot flashing unlock fastboot flash boot lineage-17.1-20210110-recovery …
From reddit.com
See details »
CAN’T FLASH FASTBOOT ROMS : XIAOMI — REDDIT.COM
WebThe error I get is the following: Sending sparse ‘vendor’ 1/2 (773888 KB) FAILED (Error reading sparse file) Logs and printscreens here: LOG PRINTSCREEN I’ve also tried …
From reddit.com
See details »
FAILED BUILDING WHEEL FOR SPARSE-DOT-TOPN #46 — GITHUB
WebJan 12, 2021 @marioespinosaperales @ipfann @selfcontrol7 @fletcheaston @lpfann. Thanks for involving the discussion of this thread! We just released v0.3.3.We employed …
From github.com
See details »