Hi
I was running latest Xiaomi EU rom on custom recovery and unlocked bootloader. Then I downloaded latest rom from Xiaomi.eu (xiaomi.eu_multi_MI10_V12.2.2.0.RJBCNXM_v12-11.zip) and flashed it via phone updater. It restarted into custom recovery, flashed the rom and everything was running fine. I restarted the phone and then it stucked in fastboot.
I tried to enter recovery but it loads fastboot every time.
Tried to install twrp, and it was flashed but when I try to manually enter recovery it loads only fastboot.
I tried this commands:
fastboot flash recovery twrp.img
fastboot boot twrp.img, but the second one won't go through because of the error: Failed to load/authenticate boot image: Load Error.
Please help, I have so many important stuff on my phone
Let this be a lesson to do a backup next time before flashing custom ROM's.
Most likely the TWRP you were using before is not compatible with the latest Xiaomi.EU ROM, and they also mentioned some issues with TRWP's on UMI/CMI/ and some other devices.
Most likely you will need to FORMAT your data, since even if you manage to get into TWRP, you won't be able to do a backup since TWRP's at the moment don't support Decryption on Android 11 ROM's.
Try downloading this TWRP and Flash it.
https://androidfilehost.com/?fid=10763459528675582373
If you manage to boot into TWRP, try flashing the latest Weekly, I SAID WEEKLY, ROM, as you may get a chance of booting without formating your data. If that doesn't work out, then you'll need to Flash the phone again with MI Flash.
@ekin_strops
I had the same problem. I could install your new twrp however i cant see with this twrp any files from the phone. Without this a transfer a new rom to the phone is not possible. The data manager within the MMX Miui 12 is able to see the files, so there is a problem with the twrp.
@ekin_strops
The solution: Flash via fastboot the above TWRP (recovery) and boot to recovery via fastboot.
Take a USB stick (USB OTG C) and copy the new rom (.zip) on it, connect it to the phone and install via recovery from the USB OTG the rom to your phone. Its really easy when you have a USB OTG C stick.
I managed to boot he phone, but my recovery is not working properly (won't mount).
So i tried to flash the new firmware with Miflash and it stops at the end, this is the error:
error: sending vmbeta... CRC error...
I tried to flash umi_eea_global_images_V12.0.6.0.QJBEUXM rom.
Here is the log:
[19:46:39 f5601ffc]:MiFlash 2020.3.14.0
[19:46:39 f5601ffc]:vboytest index:1
[19:46:39 f5601ffc]:idproduct: 53261 idvendor: 6353
[19:46:39 f5601ffc]:Thread id:14 Thread name:f5601ffc
[19:46:39 f5601ffc]:image path:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea
[19:46:39 f5601ffc]:env android path:"C:\Program Files\MiFlash20200314\Source\ThirdParty\Google\Android"
[19:46:39 f5601ffc]:script :\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\flash_all.bat
[19:46:39 f5601ffc]hysical Memory Usage:1699840 Byte
[19:46:39 f5601ffc]:start process id 3068 name cmd
[19:46:39 f5601ffc]:info1:$fastboot -s devicename getvar product 2>&1 | findstr /r /c:"^product: *umi" || echo Missmatching image and device
[19:46:39 f5601ffc]:info1roduct: umi
[19:46:39 f5601ffc]:info1:$fastboot -s devicename getvar product 2>&1 | findstr /r /c:"^product: *umi" || exit /B 1
[19:46:39 f5601ffc]:info1roduct: umi
[19:46:39 f5601ffc]:info1:$if exist D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\anti_version.txt (for /F "delims==" %a in (D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\anti_version.txt) do (set CURRENT_ANTI_VER=%a ) )
[19:46:39 f5601ffc]:info1:$(set CURRENT_ANTI_VER=1 )
[19:46:39 f5601ffc]:info1:$if [1] EQU [] set CURRENT_ANTI_VER=0
[19:46:39 f5601ffc]:info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s devicename getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
[19:46:39 f5601ffc]:info1:$(set version=1 )
[19:46:39 f5601ffc]:info1:$if [1] EQU [] set version=0
[19:46:39 f5601ffc]:info1:$set anticheck="antirollback check pass"
[19:46:39 f5601ffc]:info1:$if 1 GTR 1 set anticheck="Current device antirollback version is greater than this pakcage"
[19:46:39 f5601ffc]:info1:$echo "antirollback check pass" | findstr /r /c:"pass" ||
[19:46:39 f5601ffc]:info1:"antirollback check pass"
[19:46:39 f5601ffc]:info1:$fastboot -s devicename erase boot ||
[19:46:39 f5601ffc]:info2:Erasing 'boot' OKAY [ 0.000s]
[19:46:39 f5601ffc]:info2:Finished. Total time: 0.016s
[19:46:39 f5601ffc]:info1:$fastboot -s devicename flash crclist D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\crclist.txt ||
[19:46:39 f5601ffc]:info2:Sending 'crclist' (0 KB) OKAY [ 0.016s]
[19:46:39 f5601ffc]:info2:Writing 'crclist' OKAY [ 0.007s]
[19:46:39 f5601ffc]:info2:Finished. Total time: 0.053s
[19:46:39 f5601ffc]:info1:$fastboot -s devicename flash sparsecrclist D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\sparsecrclist.txt ||
[19:46:39 f5601ffc]:info2:Sending 'sparsecrclist' (0 KB) OKAY [ 0.000s]
[19:46:39 f5601ffc]:info2:Writing 'sparsecrclist' OKAY [ 0.000s]
[19:46:39 f5601ffc]:info2:Finished. Total time: 0.016s
[19:46:39 f5601ffc]:info1:$fastboot -s devicename flash xbl_4 D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\xbl_4.elf ||
[19:46:40 f5601ffc]:info2:Sending 'xbl_4' (3350 KB) OKAY [ 0.116s]
[19:46:40 f5601ffc]:info2:Writing 'xbl_4' OKAY [ 0.134s]
[19:46:40 f5601ffc]:info2:Finished. Total time: 0.265s
[19:46:40 f5601ffc]:info1:$fastboot -s devicename flash xbl_config_4 D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\xbl_config_4.elf ||
[19:46:40 f5601ffc]:info2:Sending 'xbl_config_4' (95 KB) OKAY [ 0.010s]
[19:46:40 f5601ffc]:info2:Writing 'xbl_config_4' OKAY [ 0.005s]
[19:46:40 f5601ffc]:info2:Finished. Total time: 0.042s
[19:46:40 f5601ffc]:info1:$fastboot -s devicename flash xbl_5 D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\xbl_5.elf ||
[19:46:40 f5601ffc]:info2:Sending 'xbl_5' (3373 KB) OKAY [ 0.115s]
[19:46:40 f5601ffc]:info2:Writing 'xbl_5' OKAY [ 0.133s]
[19:46:40 f5601ffc]:info2:Finished. Total time: 0.280s
[19:46:40 f5601ffc]:info1:$fastboot -s devicename flash xbl_config_5 D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\xbl_config_5.elf ||
[19:46:40 f5601ffc]:info2:Sending 'xbl_config_5' (95 KB) OKAY [ 0.011s]
[19:46:40 f5601ffc]:info2:Writing 'xbl_config_5' OKAY [ 0.005s]
[19:46:40 f5601ffc]:info2:Finished. Total time: 0.045s
[19:46:40 f5601ffc]:info1:$fastboot -s devicename flash abl D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\abl.elf ||
[19:46:40 f5601ffc]:info2:Sending 'abl' (204 KB) OKAY [ 0.017s]
[19:46:40 f5601ffc]:info2:Writing 'abl' OKAY [ 0.009s]
[19:46:40 f5601ffc]:info2:Finished. Total time: 0.036s
[19:46:40 f5601ffc]:info1:$fastboot -s devicename flash tz D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\tz.mbn ||
[19:46:40 f5601ffc]:info2:Sending 'tz' (3228 KB) OKAY [ 0.105s]
[19:46:41 f5601ffc]:info2:Writing 'tz' OKAY [ 0.123s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.261s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash hyp D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\hyp.mbn ||
[19:46:41 f5601ffc]:info2:Sending 'hyp' (434 KB) OKAY [ 0.018s]
[19:46:41 f5601ffc]:info2:Writing 'hyp' OKAY [ 0.022s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.070s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash devcfg D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\devcfg.mbn ||
[19:46:41 f5601ffc]:info2:Sending 'devcfg' (47 KB) OKAY [ 0.010s]
[19:46:41 f5601ffc]:info2:Writing 'devcfg' OKAY [ 0.000s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.022s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash storsec D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\storsec.mbn ||
[19:46:41 f5601ffc]:info2:Sending 'storsec' (19 KB) OKAY [ 0.002s]
[19:46:41 f5601ffc]:info2:Writing 'storsec' OKAY [ 0.000s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.022s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash bluetooth D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\BTFM.bin ||
[19:46:41 f5601ffc]:info2:Sending 'bluetooth' (412 KB) OKAY [ 0.020s]
[19:46:41 f5601ffc]:info2:Writing 'bluetooth' OKAY [ 0.018s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.060s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash cmnlib D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\cmnlib.mbn ||
[19:46:41 f5601ffc]:info2:Sending 'cmnlib' (382 KB) OKAY [ 0.020s]
[19:46:41 f5601ffc]:info2:Writing 'cmnlib' OKAY [ 0.018s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.048s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash cmnlib64 D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\cmnlib64.mbn ||
[19:46:41 f5601ffc]:info2:Sending 'cmnlib64' (496 KB) OKAY [ 0.022s]
[19:46:41 f5601ffc]:info2:Writing 'cmnlib64' OKAY [ 0.020s]
[19:46:41 f5601ffc]:info2:Finished. Total time: 0.060s
[19:46:41 f5601ffc]:info1:$fastboot -s devicename flash modem D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\NON-HLOS.bin ||
[19:46:48 f5601ffc]:info2:Sending 'modem' (220348 KB) OKAY [ 6.662s]
[19:46:56 f5601ffc]:info2:Writing 'modem' OKAY [ 8.239s]
[19:46:56 f5601ffc]:info2:Finished. Total time: 14.929s
[19:46:56 f5601ffc]:info1:$fastboot -s devicename flash dsp D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\dspso.bin ||
[19:46:58 f5601ffc]:info2:Sending 'dsp' (65536 KB) OKAY [ 1.990s]
[19:47:01 f5601ffc]:info2:Writing 'dsp' OKAY [ 2.450s]
[19:47:01 f5601ffc]:info2:Finished. Total time: 4.469s
[19:47:01 f5601ffc]:info1:$fastboot -s devicename flash keymaster D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\km4.mbn ||
[19:47:01 f5601ffc]:info2:Sending 'keymaster' (244 KB) OKAY [ 0.012s]
[19:47:01 f5601ffc]:info2:Writing 'keymaster' OKAY [ 0.012s]
[19:47:01 f5601ffc]:info2:Finished. Total time: 0.041s
[19:47:01 f5601ffc]:info1:$fastboot -s devicename flash logo D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\logo.img ||
[19:47:01 f5601ffc]:info2:Sending 'logo' (24704 KB) OKAY [ 0.751s]
[19:47:02 f5601ffc]:info2:Writing 'logo' OKAY [ 0.924s]
[19:47:02 f5601ffc]:info2:Finished. Total time: 1.701s
[19:47:02 f5601ffc]:info1:$fastboot -s devicename flash featenabler D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\featenabler.mbn ||
[19:47:02 f5601ffc]:info2:Sending 'featenabler' (84 KB) OKAY [ 0.006s]
[19:47:02 f5601ffc]:info2:Writing 'featenabler' OKAY [ 0.002s]
[19:47:02 f5601ffc]:info2:Finished. Total time: 0.036s
[19:47:02 f5601ffc]:info1:$fastboot -s devicename flash misc D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\misc.img ||
[19:47:03 f5601ffc]:info2:Sending 'misc' (8 KB) OKAY [ 0.008s]
[19:47:03 f5601ffc]:info2:Writing 'misc' OKAY [ 0.001s]
[19:47:03 f5601ffc]:info2:Finished. Total time: 0.042s
[19:47:03 f5601ffc]:info1:$fastboot -s devicename flash aop D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\aop.mbn ||
[19:47:03 f5601ffc]:info2:Sending 'aop' (197 KB) OKAY [ 0.014s]
[19:47:03 f5601ffc]:info2:Writing 'aop' OKAY [ 0.009s]
[19:47:03 f5601ffc]:info2:Finished. Total time: 0.037s
[19:47:03 f5601ffc]:info1:$fastboot -s devicename flash qupfw D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\qupv3fw.elf ||
[19:47:03 f5601ffc]:info2:Sending 'qupfw' (52 KB) OKAY [ 0.010s]
[19:47:03 f5601ffc]:info2:Writing 'qupfw' OKAY [ 0.003s]
[19:47:03 f5601ffc]:info2:Finished. Total time: 0.028s
[19:47:03 f5601ffc]:info1:$fastboot -s devicename flash uefisecapp D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\uefi_sec.mbn ||
[19:47:03 f5601ffc]:info2:Sending 'uefisecapp' (120 KB) OKAY [ 0.009s]
[19:47:03 f5601ffc]:info2:Writing 'uefisecapp' OKAY [ 0.006s]
[19:47:03 f5601ffc]:info2:Finished. Total time: 0.026s
[19:47:03 f5601ffc]:info1:$fastboot -s devicename flash multiimgoem D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\multi_image.mbn ||
[19:47:03 f5601ffc]:info2:Sending 'multiimgoem' (32 KB) OKAY [ 0.009s]
[19:47:03 f5601ffc]:info2:Writing 'multiimgoem' OKAY [ 0.002s]
[19:47:03 f5601ffc]:info2:Finished. Total time: 0.022s
[19:47:03 f5601ffc]:info1:$fastboot -s devicename flash super D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\super.img ||
[19:47:27 f5601ffc]:info2:Sending sparse 'super' 1/8 (757789 KB) OKAY [ 22.849s]
[19:47:27 f5601ffc]:info2:Writing 'super' OKAY [ 0.001s]
[19:48:05 f5601ffc]:info2:Sending sparse 'super' 2/8 (786430 KB) OKAY [ 38.005s]
[19:48:05 f5601ffc]:info2:Writing 'super' OKAY [ 0.001s]
[19:48:48 f5601ffc]:info2:Sending sparse 'super' 3/8 (785877 KB) OKAY [ 42.735s]
[19:48:48 f5601ffc]:info2:Writing 'super' OKAY [ 0.000s]
[19:49:36 f5601ffc]:info2:Sending sparse 'super' 4/8 (784134 KB) OKAY [ 48.626s]
[19:49:36 f5601ffc]:info2:Writing 'super' OKAY [ 0.001s]
[19:50:25 f5601ffc]:info2:Sending sparse 'super' 5/8 (786140 KB) OKAY [ 48.351s]
[19:50:25 f5601ffc]:info2:Writing 'super' OKAY [ 0.001s]
[19:51:07 f5601ffc]:info2:Sending sparse 'super' 6/8 (786201 KB) OKAY [ 42.274s]
[19:51:07 f5601ffc]:info2:Writing 'super' OKAY [ 0.002s]
[19:51:49 f5601ffc]:info2:Sending sparse 'super' 7/8 (778180 KB) OKAY [ 42.125s]
[19:51:49 f5601ffc]:info2:Writing 'super' OKAY [ 0.000s]
[19:52:29 f5601ffc]:info2:Sending sparse 'super' 8/8 (544992 KB) OKAY [ 39.887s]
[19:52:29 f5601ffc]:info2:Writing 'super' OKAY [ 0.000s]
[19:52:29 f5601ffc]:info2:Finished. Total time: 326.263s
[19:52:29 f5601ffc]:info1:$fastboot -s devicename flash vbmeta D:\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea_e0f755c9d5\umi_eea_global_images_V12.0.6.0.QJBEUXM_20201020.0000.00_10.0_eea\images\vbmeta.img ||
[19:53:00 f5601ffc]:info2:Sending 'vbmeta' (8 KB) FAILED (remote: 'Error: Last flash failed : CRC Error')
[19:53:00 f5601ffc]:info2:fastboot: error: Command failed
[19:53:00 f5601ffc]:info1:"Flash vbmeta error"
[19:53:00 f5601ffc]:begin FlashDone
[19:53:00 f5601ffc]:error:Sending 'vbmeta' (8 KB) FAILED (remote: 'Error: Last flash failed : CRC Error')
[19:53:00 f5601ffc]rocess exit.
[19:53:00 f5601ffc]:flashSuccess False
[19:53:00 f5601ffc]:isFactory False CheckCPUID False
[19:53:00 f5601ffc]:before:flashSuccess is False set IsUpdate:True set IsDone True
[19:53:00 f5601ffc]:after:flashSuccess is False set IsUpdate:false set IsDone true
@ elvirr:
What did I tell you above????? Do not flash any rom whwn you are using the above TWRP.3.4.0 via ADB or fastboot. You MUST flash the rom via USB OTG.
Boot to the twrp, format data (you see nothing, wait for a minute or two), boot again to recovery, connect to USB OTG with the rom on it. Install from USB OTG., clean cach and boot to system.
elvirr said:
Hi
I was running latest Xiaomi EU rom on custom recovery and unlocked bootloader. Then I downloaded latest rom from Xiaomi.eu (xiaomi.eu_multi_MI10_V12.2.2.0.RJBCNXM_v12-11.zip) and flashed it via phone updater. It restarted into custom recovery, flashed the rom and everything was running fine. I restarted the phone and then it stucked in fastboot.
I tried to enter recovery but it loads fastboot every time.
Tried to install twrp, and it was flashed but when I try to manually enter recovery it loads only fastboot.
I tried this commands:
fastboot flash recovery twrp.img
fastboot boot twrp.img, but the second one won't go through because of the error: Failed to load/authenticate boot image: Load Error.
Please help, I have so many important stuff on my phone
Click to expand...
Click to collapse
I've been having this same problem all week trying to install the Global recovery ROM. Unfortunately the only way I was able to get my phone to boot normally again was to flash the 12.0.1 fastboot ROM using the MiFlash tool
@pascha46
You can flash any region ROMs via Fastboot.
In my opinion I have never been able to get MiFlash tool to work. Much easier to just use Fastboot and flash the stock region ROM manually
hello good morning,
I have the same problem ...
it's blocked in fastboot, when connecting to the pc says unrecognized device.
help please
Same issue here. Phone is not recognised by PC, I don't what to do. Flashtool doesn't see the device. Goddamn Android 11
daleksi said:
Same issue here. Phone is not recognised by PC, I don't what to do. Flashtool doesn't see the device. Goddamn Android 11
Click to expand...
Click to collapse
Next time, stay away from things that you didn't understand 100 percent. Try this tool - very suitable for beginners: https://www.xiaomitool.com/V2/
Good luck. No backup - no mercy.
Problem described below is solved. Found out that the problem was a missing/deprecated certificate for the driver installation. Helped getting the newest version of Mi Flash and installing a stock ROM.
----
I also can't boot to anything but this fastboot screen. Tried the beginners tool suggested, but it fails at vbmeta, cf. image.
Tried a few other commands with fastboot, but in general get the following error message:
"FAILED (Write to device failed (Unknown error))" [EDIT: After a hard reboot of the phone, it was possible to write to it again via fastboot. Have an idea what to try now, downloading a ROM for fastboot. But mostly wondering if formatting is safe; might it be impossible to connect to the phone afterwards?]
Guess I should mention that the device is rooted and encrypted.
I don't care too much if I lose all data (probably already happened), but I'd very much appreciate help as to how to get a working phone again. Anyone, please? Is the way forward this usb-c stick plugged into the phone, even though I can't write recovery.img to it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AllanStig said:
Problem described below is solved. Found out that the problem was a missing/deprecated certificate for the driver installation. Helped getting the newest version of Mi Flash and installing a stock ROM.
----
I also can't boot to anything but this fastboot screen. Tried the beginners tool suggested, but it fails at vbmeta, cf. image.
Tried a few other commands with fastboot, but in general get the following error message:
"FAILED (Write to device failed (Unknown error))" [EDIT: After a hard reboot of the phone, it was possible to write to it again via fastboot. Have an idea what to try now, downloading a ROM for fastboot. But mostly wondering if formatting is safe; might it be impossible to connect to the phone afterwards?]
Guess I should mention that the device is rooted and encrypted.
I don't care too much if I lose all data (probably already happened), but I'd very much appreciate help as to how to get a working phone again. Anyone, please? Is the way forward this usb-c stick plugged into the phone, even though I can't write recovery.img to it?
View attachment 5175947
Click to expand...
Click to collapse
I had the same problem trying to flash any stock ROM with XiaoMiTool, even using the bat File resulted in an error on vbmeta. In the end i tried to flash via console using minimal ADB and Fastboot and hacking the commands into cmd line by line worked fine
pascha46 said:
@ elvirr:
What did I tell you above????? Do not flash any rom whwn you are using the above TWRP.3.4.0 via ADB or fastboot. You MUST flash the rom via USB OTG.
Boot to the twrp, format data (you see nothing, wait for a minute or two), boot again to recovery, connect to USB OTG with the rom on it. Install from USB OTG., clean cach and boot to system.
Click to expand...
Click to collapse
you sir are a genius. Flashing with the older TWRP and using USB worked fine! Just one question: Is updating the ROM over TWRP possible without loosing all data?
elvirr said:
Hi
I was running latest Xiaomi EU rom on custom recovery and unlocked bootloader. Then I downloaded latest rom from Xiaomi.eu (xiaomi.eu_multi_MI10_V12.2.2.0.RJBCNXM_v12-11.zip) and flashed it via phone updater. It restarted into custom recovery, flashed the rom and everything was running fine. I restarted the phone and then it stucked in fastboot.
I tried to enter recovery but it loads fastboot every time.
Tried to install twrp, and it was flashed but when I try to manually enter recovery it loads only fastboot.
I tried this commands:
fastboot flash recovery twrp.img
fastboot boot twrp.img, but the second one won't go through because of the error: Failed to load/authenticate boot image: Load Error.
Please help, I have so many important stuff on my phone
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
for those still not booted into TWRP
AllanStig said:
Problem described below is solved. Found out that the problem was a missing/deprecated certificate for the driver installation. Helped getting the newest version of Mi Flash and installing a stock ROM.
----
I also can't boot to anything but this fastboot screen. Tried the beginners tool suggested, but it fails at vbmeta, cf. image.
Tried a few other commands with fastboot, but in general get the following error message:
"FAILED (Write to device failed (Unknown error))" [EDIT: After a hard reboot of the phone, it was possible to write to it again via fastboot. Have an idea what to try now, downloading a ROM for fastboot. But mostly wondering if formatting is safe; might it be impossible to connect to the phone afterwards?]
Guess I should mention that the device is rooted and encrypted.
I don't care too much if I lose all data (probably already happened), but I'd very much appreciate help as to how to get a working phone again. Anyone, please? Is the way forward this usb-c stick plugged into the phone, even though I can't write recovery.img to it?
View attachment 5175947
Click to expand...
Click to collapse
Hi there
I have the same error,how did you manage to resolve and what certificate was missing from the driver.If you can help in this .Thanks
jjgvv said:
fastboot --cmdline "lge.kcal=0|0|0|x" boot twrp.img
Click to expand...
Click to collapse
I tried this command but again same error
error message:
"FAILED (Write to device failed (Unknown error )
any help appreciated
your emmc is fried
maybe use EDL flash method
Related
Hi, I´m trying to recovery my Huawei G740, and I have from the other Huawei G740 all files to recovery my phone (boot.img/recovery.img/system.img/userdata.img/cache.img and custom.img, but when I put all together with fastboot the phone don´t work, It try to start after that restart itself and come inside recovery mode, any suggestion or advice to make this work guys.Thank you.
I:\Android\sdk\platform-tools>fastboot devices
96ee49a fastboot
I:\Android\sdk\platform-tools>fastboot flash cache cache.img
sending 'cache' (196608 KB)...
OKAY [ 12.415s]
writing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 12.421s
I:\Android\sdk\platform-tools>fastboot flash cust cust.img
sending 'cust' (262144 KB)...
OKAY [ 16.512s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 16.517s
I:\Android\sdk\platform-tools> fastboot flash boot boot.img
sending 'boot' (12288 KB)...
OKAY [ 0.773s]
writing 'boot'...
OKAY [ 0.608s]
finished. total time: 1.382s
I:\Android\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (16384 KB)...
OKAY [ 1.029s]
writing 'recovery'...
OKAY [ 1.023s]
finished. total time: 2.053s
I:\Android\sdk\platform-tools>fastboot flash userdata userdata.img
sending 'userdata' (460449 KB)...
OKAY [ 28.798s]
writing 'userdata'...
OKAY [ 22.669s]
finished. total time: 51.469s
I:\Android\sdk\platform-tools>fastboot flash system system.img
sending 'system' (445101 KB)...
OKAY [ 27.826s]
writing 'system'...
OKAY [ 21.810s]
finished. total time: 49.636s
I:\Android\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.005s
Hi guys,
Recently after a
fastboot boot twrp-3.3.1-test43-hotdog-unified-mauronofrio.img
Click to expand...
Click to collapse
I'm stuck in a bootloop. I would like to specify that I ran the twrp checked if I was able to flash something but I saw that I was not able to flash anything because my phone doesn't have the root I rebooted the phone, and from that moment I cannot run the os at all. I'm able to go to the fastboot and I'm able to run the twrp and the recovery.
I tried to reflash the boot only but without success. At this moment I tried to reinstall all the system 10.0.9 but I received this message:
Do you want to wipe all the data ( Reccomended )[Y/N]?n
Sending 'boot_b' (98304 KB) OKAY [ 2.785s]
Writing 'boot_b' OKAY [ 0.468s]
Finished. Total time: 3.700s
Sending 'dtbo' (16384 KB) OKAY [ 0.473s]
Writing 'dtbo' OKAY [ 0.043s]
Finished. Total time: 0.621s
Sending 'modem_b' (166356 KB) OKAY [ 4.741s]
Writing 'modem_b' OKAY [ 0.686s]
Finished. Total time: 6.146s
Sending 'reserve' (250136 KB) OKAY [ 7.109s]
Writing 'reserve' FAILED (remote: '(reserve_b)
No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 2.794s]
Writing 'recovery' OKAY [ 0.353s]
Finished. Total time: 3.314s
Sending 'vbmeta' (8 KB) OKAY [ 0.013s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.039s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.034s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 9.956s
Sending 'abl_b' (1164 KB) OKAY [ 0.036s]
Writing 'abl_b' OKAY [ 0.013s]
Finished. Total time: 0.071s
Sending 'aop_b' (200 KB) OKAY [ 0.006s]
Writing 'aop_b' OKAY [ 0.007s]
Finished. Total time: 0.041s
Sending 'bluetooth_b' (828 KB) OKAY [ 0.025s]
Writing 'bluetooth_b' OKAY [ 0.011s]
Finished. Total time: 0.057s
Sending 'cmnlib_b' (384 KB) OKAY [ 0.012s]
Writing 'cmnlib_b' OKAY [ 0.008s]
Finished. Total time: 0.036s
Sending 'cmnlib64_b' (500 KB) OKAY [ 0.015s]
Writing 'cmnlib64_b' OKAY [ 0.009s]
Finished. Total time: 0.042s
Sending 'devcfg_b' (52 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.006s]
Finished. Total time: 0.022s
Sending 'dsp_b' (65536 KB) OKAY [ 1.919s]
Writing 'dsp_b' OKAY [ 0.335s]
Finished. Total time: 2.553s
Sending 'hyp_b' (480 KB) OKAY [ 0.015s]
Writing 'hyp_b' OKAY [ 0.007s]
Finished. Total time: 0.041s
Sending 'imagefv_b' (20 KB) OKAY [ 0.001s]
Writing 'imagefv_b' OKAY [ 0.006s]
Finished. Total time: 0.022s
Sending 'keymaster_b' (248 KB) OKAY [ 0.008s]
Writing 'keymaster_b' OKAY [ 0.007s]
Finished. Total time: 0.034s
Sending 'LOGO_b' (6540 KB) OKAY [ 0.195s]
Writing 'LOGO_b' OKAY [ 0.046s]
Finished. Total time: 0.284s
Sending 'multiimgoem_b' (16 KB) OKAY [ 0.001s]
Writing 'multiimgoem_b' OKAY [ 0.006s]
Finished. Total time: 0.030s
Resizing 'odm_b' OKAY [ 0.006s]
Sending 'odm_b' (912 KB) OKAY [ 0.028s]
Writing 'odm_b' FAILED (Status read failed (T
oo many links))
fastboot: error: Command failed
Sending 'oem_stanvbk' (876 KB) FAILED (Write to device faile
d (No such file or directory))
fastboot: error: Command failed
Sending 'opproduct' (612316 KB) FAILED (Write to device faile
d (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Sending 'qupfw' (72 KB) OKAY [ 0.012s]
Writing 'qupfw' OKAY [ 0.003s]
Finished. Total time: 0.042s
Sending 'storsec' (24 KB) OKAY [ 0.007s]
Writing 'storsec' OKAY [ 0.003s]
Finished. Total time: 0.032s
Sending 'tz' (3092 KB) OKAY [ 0.096s]
Writing 'tz' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.011s]
Writing 'uefisecapp' OKAY [ 0.003s]
Finished. Total time: 0.037s
Sending 'xbl' (3120 KB) OKAY [ 0.094s]
Writing 'xbl' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.014s]
Writing 'xbl_config' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784696 KB) OKAY [ 23.363s]
Writing 'system' FAILED (remote: 'Partition no
t found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 23.425s]
Writing 'vendor' FAILED (remote: 'Partition no
t found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785428 KB) OKAY [ 23.379s]
Writing 'product' FAILED (remote: 'Partition no
t found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.005s
Premere un tasto per continuare . . .
Click to expand...
Click to collapse
Unfortunately, all these attempts failed. In the past, I tried the rooting. After the first period, it worked properly but I was not able to re-install magisk boot file as it was not recognized by the magisk app. I don't remember if there were some magisk module.
I don't know if this helps, please assist. If the topic is in the wrong section, please move it.
Thank you in advance for your help.
Gorthan said:
Hi guys,
Recently after a
I'm stuck in a bootloop. I would like to specify that I ran the twrp checked if I was able to flash something but I saw that I was not able to flash anything because my phone doesn't have the root I rebooted the phone, and from that moment I cannot run the os at all. I'm able to go to the fastboot and I'm able to run the twrp and the recovery.
I tried to reflash the boot only but without success. At this moment I tried to reinstall all the system 10.0.9 but I received this message:
Unfortunately, all these attempts failed. In the past, I tried the rooting. After the first period, it worked properly but I was not able to re-install magisk boot file as it was not recognized by the magisk app. I don't remember if there were some magisk module.
I don't know if this helps, please assist. If the topic is in the wrong section, please move it.
Thank you in advance for your help.
Click to expand...
Click to collapse
Try to install again the rom, and when the device reboot itself in recovery don't reboot it
thanks so much for your reply.
I realized that with the twrp I selected the partition A and I reinstalled the rom again and the system restarted. Now I'll try to restore the partition B. (But in meantime I'm performing a backup all the data ).
Update: I reinstalled the system in the Partition B and works properly.
mauronofrio said:
Try to install again the rom, and when the device reboot itself in recovery don't reboot it
Click to expand...
Click to collapse
thanks so much for your reply. I followed your advice and actually helps.
I realized that with the twrp I selected the partition A and I reinstalled the rom again and the system restarted. I'll try to restore the partition B. (But in meantime I'm performing a backup all the data ).
Update: I reinstalled the system in Partition B and works properly.
Update 2: I finally spend a bit of time on the phone and I already rooted. Thanks to @mauronofrio for help.
Plaese if someone can help
i ininstalled magisk because bugs, and it restart and stay on AndroidOne screen
when i tried to reinstall stock i got this
C:\adb>echo "laurel_sprout fastboot flash tools"
"laurel_sprout fastboot flash tools"
C:\adb>set CURRENT_ANTI_VER=0
C:\adb>for /F "tokens=2 delims=: " %i in ('fastboot getvar anti 2>&1 | findstr /r /c:"anti:"') do (set version=%i )
C:\adb>(set version=0 )
C:\adb>if [0] EQU [] set version=0
C:\adb>set anticheck="antirollback check pass"
C:\adb>if 0 GTR 0 set anticheck="Current device antirollback version is greater than this package"
C:\adb>echo "antirollback check pass" | findstr /r /c:"pass" ||
"antirollback check pass"
C:\adb>fastboot getvar product 2>&1 | findstr /r /c:"^product: *laurel_sprout" || echo Missmatching image and device
product: laurel_sprout
C:\adb>fastboot getvar product 2>&1 | findstr /r /c:"^product: *laurel_sprout" || exit /B 1
product: laurel_sprout
C:\adb>fastboot flash crclist "C:\adb\images\crclist.txt"
Sending 'crclist' (0 KB) OKAY [ 0.003s]
Writing 'crclist' OKAY [ 0.006s]
Finished. Total time: 0.019s
C:\adb>fastboot flash sparsecrclist "C:\adb\images\sparsecrclist.txt"
Sending 'sparsecrclist' (0 KB) OKAY [ 0.007s]
Writing 'sparsecrclist' OKAY [ 0.001s]
Finished. Total time: 0.022s
C:\adb>fastboot flash tz_a "C:\adb\images\tz.mbn" ||
Sending 'tz_a' (1968 KB) OKAY [ 0.074s]
Writing 'tz_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
"Flash tz_a error"
C:\adb>pause
Drücken Sie eine beliebige Taste . . .
It seems that you have locked bootloader "remote: 'Flashing is not allowed in Lock State'".
You cannot use flashtool with locked bootloader. Unlock it first then run flashtool. After flash complete, set boot slot to A, complete the first boot then relock bootloader if you want
I was trying to upgrade from Android 11 to 12 with an Android 12 GSI using Fastboot, but whenever I try to install the system.img, it always fails with the error:
(bootloader) Preflash validation failed FAILED (remote failure)
Click to expand...
Click to collapse
I have seen that this error is common if you have the bootloader locked, but mine is unlocked.
Here's the full list of commands I used:
Code:
F:\Programs\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (52224 KB)...
OKAY [ 1.276s]
writing 'boot_b'...
OKAY [ 0.779s]
finished. total time: 2.056s
F:\Programs\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.005s]
writing 'vbmeta_b'...
(bootloader) WARNING: vbmeta_b anti rollback downgrade, 0 vs 16
OKAY [ 0.036s]
finished. total time: 0.041s
F:\Programs\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/3 (786340 KB)...
OKAY [ 19.870s]
writing 'system_b' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.962s
Why do I get this error, and is there any way to solve it?
ByteSeb said:
I was trying to upgrade from Android 11 to 12 with an Android 12 GSI using Fastboot, but whenever I try to install the system.img, it always fails with the error:
I have seen that this error is common if you have the bootloader locked, but mine is unlocked.
Here's the full list of commands I used:
Code:
F:\Programs\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (52224 KB)...
OKAY [ 1.276s]
writing 'boot_b'...
OKAY [ 0.779s]
finished. total time: 2.056s
F:\Programs\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.005s]
writing 'vbmeta_b'...
(bootloader) WARNING: vbmeta_b anti rollback downgrade, 0 vs 16
OKAY [ 0.036s]
finished. total time: 0.041s
F:\Programs\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
Invalid sparse file format at header magic
sending sparse 'system_b' 1/3 (786340 KB)...
OKAY [ 19.870s]
writing 'system_b' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.962s
Why do I get this error, and is there any way to solve it?
Click to expand...
Click to collapse
You need to be in fastboot d to flash system images. In regular fastboot, type fastboot reboot fastboot.
Beetle84 said:
You need to be in fastboot d to flash system images. In regular fastboot, type fastboot reboot fastboot.
Click to expand...
Click to collapse
It seems like that was working, but now I get this error:
FAILED (remote: Operation not permitted)
Click to expand...
Click to collapse
Here's the commands I used:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot_a' (52224 KB)...
OKAY [ 1.373s]
writing 'boot_a'...
OKAY [ 1.584s]
finished. total time: 2.958s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 268435456 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.003s]
writing 'vbmeta_a'...
OKAY [ 0.047s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/7 (262108 KB)...
OKAY [ 7.087s]
writing 'system_a' 1/7...
OKAY [ 1.746s]
sending sparse 'system_a' 2/7 (262120 KB)...
OKAY [ 7.075s]
writing 'system_a' 2/7...
OKAY [ 1.723s]
sending sparse 'system_a' 3/7 (262112 KB)...
OKAY [ 7.015s]
writing 'system_a' 3/7...
OKAY [ 1.746s]
sending sparse 'system_a' 4/7 (262124 KB)...
OKAY [ 7.001s]
writing 'system_a' 4/7...
OKAY [ 1.736s]
sending sparse 'system_a' 5/7 (262088 KB)...
OKAY [ 7.013s]
writing 'system_a' 5/7...
FAILED (remote: Operation not permitted)
finished. total time: 43.777s
ByteSeb said:
It seems like that was working, but now I get this error:
Here's the commands I used:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot_a' (52224 KB)...
OKAY [ 1.373s]
writing 'boot_a'...
OKAY [ 1.584s]
finished. total time: 2.958s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 268435456 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.003s]
writing 'vbmeta_a'...
OKAY [ 0.047s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/7 (262108 KB)...
OKAY [ 7.087s]
writing 'system_a' 1/7...
OKAY [ 1.746s]
sending sparse 'system_a' 2/7 (262120 KB)...
OKAY [ 7.075s]
writing 'system_a' 2/7...
OKAY [ 1.723s]
sending sparse 'system_a' 3/7 (262112 KB)...
OKAY [ 7.015s]
writing 'system_a' 3/7...
OKAY [ 1.746s]
sending sparse 'system_a' 4/7 (262124 KB)...
OKAY [ 7.001s]
writing 'system_a' 4/7...
OKAY [ 1.736s]
sending sparse 'system_a' 5/7 (262088 KB)...
OKAY [ 7.013s]
writing 'system_a' 5/7...
FAILED (remote: Operation not permitted)
finished. total time: 43.777s
Click to expand...
Click to collapse
if you update adb, you will see that it gives you an error for no space (atleast for me it did). To fix this, since your phone uses AB partitioning, you will need to do fastboot delete-logical-partition product_a and it should be good since you are using a GSI
Thanks! That worked
GigaPVP said:
if you update adb, you will see that it gives you an error for no space (atleast for me it did). To fix this, since your phone uses AB partitioning, you will need to do fastboot delete-logical-partition product_a and it should be good since you are using a GSI
Click to expand...
Click to collapse
i tried "fastboot delete-logical-partiton product_a" (a partition was active)
but error message occurs "unknown command delete-logical-partiton "
~using latest platform toot
~installing Android 13 GSI arm64+GSM .img
~on pixel 3
Hello guys, I am trying to root my device for the first time.
Version is MIUI 13.0.5, Bootloader and MIUI unlocked.
I've followed youtube video.
Now my device has failed to boot a lot of times. Now when I turn on the device it goes to fastboot.
What I've done is below
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.011s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.032s
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot flash boot magisk_patched-23000_74Ls8.img
Sending 'boot_b' (131072 KB) OKAY [ 3.181s]
Writing 'boot_b' OKAY [ 0.639s]
Finished. Total time: 3.839s
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.003s
Boot failed, and I tried again.
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.007s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.038s
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot flash boot magisk_patched-23000_74Ls8.img
Sending 'boot_a' (131072 KB) OKAY [ 4.603s]
Writing 'boot_a' OKAY [ 0.639s]
Finished. Total time: 5.382s
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.003s
What do I have to do from now?
Can I still download other diffrent magisk patched image file and try it again?
Or do I have to fix my device first and challenge this again?
I've downloaded this now: mojito_global_images_V13.0.5.0.SKGMIXM_20220209.0000.00_12.0_global_36ff0ca7ff.tgz
I am currently confused to what to do.
I'd appreciate if you can give me any advice or tips. Thank you.
I felt like that I need to flash official firmware.
So I did it with MiFlash. But it says "Missmatching image and device".
How do I find correct image for my device when I can't boot?
Since firmware files are quite heavy, I can't download and try all.
What I know is that It was MIUI 13.0.5 Global and Android 12 when I tried to root it.
What I have found by IMEI i:
Description: Redmi Note 10 JE Chrome Silver 4 RAM 64 ROM
IMEI: 868096051729159
Brand: Xiaomi Communications Co Ltd
Model: XIG02
Name: XIG02
Purchase Country: Japan
Production Date: 2021-12-10 16:18:19
Does anybody know what is the correct image for my device?
Ok nevermind this thread. I found out that my device isn't Redmi Note 10. It is Remi Note 10 5G.
can i have a stock rom ive lost mine please help