My phone is stuck in a boot loop, I have attempted to use flash_all_lock to flash and relock my bootloader, but it's failing when it tries to flash vbmeta, if I reboot back to fastboot and flash it vbmeta manually it works (I then flash the rest of the contents of the .bat manually) but the phone remains in the same state and won't boot. The error I get is:
C:\MiFlash20191206\rom\firmware>fastboot flash vbmeta C:\MiFlash20191206\rom\firmware\images\vbmeta.img ||
Sending 'vbmeta' (8 KB) FAILED (remote: 'Error: Last flash failed : CRC Error')
fastboot: error: Command failed
"Flash vbmeta error"
Using this rom : umi_eea_global_images_V12.0.1.0.QJBEUXM_20200721.0000.00_10.0_eea_e47a18fd29
Please Ignore this Fixed via adb sideload Phew!
Try to use adb platform tools v29 and flash rom via fastboot using flash.all.bat
Your bootloader is unlocked? If yes then fastboot flash twrp and flash any fw you want sry just saw you fixed it
Related
Hi,
I have flash system.img file by using
Code:
D:\ADB\Android>fastboot flash system d:\backup\flash\system.img
sending 'system' (116302 KB)...
OKAY [114.524s]
writing 'system'...
OKAY [ 47.582s]
finished. total time: 162.108s
It seems normal to me, but the problem arise when I restart the the phone. The phone unable to boot, and when I try
Code:
ADB Shell
It says somethings like "sh" is not found. So I do reboot recovery go to the shell and mount /system. Shockingly there is nothing in there.
I have checked the contents of system.img, and there is a lot of things in there, including the "sh". But it seems fastboot failed to flash the system partition.
Anyone can help me ?
maybe you should tell more info about your device, brand,chipset, etc ?
so people can be more easy to help.
just newbie suggestion, ignore this if its no help xD
Looks like your system image file is corrupted cause its not mounted after loading kernel. What kind of filesystem the image is using?
lolet said:
Looks like your system image file is corrupted cause its not mounted after loading kernel. What kind of filesystem the image is using?
Click to expand...
Click to collapse
The system image is not corrupted, because I can safely flash it using Clockworkmod. The filesystem is yaff2, and I have tried opening it using some software and my file is there. I think the problem lies on fastboot who failed flashing properly.
simple
yokowasis said:
Hi,
I have flash system.img file by using
Code:
D:\ADB\Android>fastboot flash system d:\backup\flash\system.img
sending 'system' (116302 KB)...
OKAY [114.524s]
writing 'system'...
OKAY [ 47.582s]
finished. total time: 162.108s
It seems normal to me, but the problem arise when I restart the the phone. The phone unable to boot, and when I try
Code:
ADB Shell
It says somethings like "sh" is not found. So I do reboot recovery go to the shell and mount /system. Shockingly there is nothing in there.
I have checked the contents of system.img, and there is a lot of things in there, including the "sh". But it seems fastboot failed to flash the system partition.
Anyone can help me ?
Click to expand...
Click to collapse
ur work is simple...just plug in ur phone in fastboot mode...keep a boot.img file in the same folder that that of the fastboot folder....boot.img can be taken from ur STOCK ROM
and type ==
fastboot devices
then ur device will be shown.....
then type
fastboot flash boot boot.img
n its done!
I stuck with my Mate 9 Error mode numbers 11 and 2
MEGHSHAH said:
ur work is simple...just plug in ur phone in fastboot mode...keep a boot.img file in the same folder that that of the fastboot folder....boot.img can be taken from ur STOCK ROM
and type ==
fastboot devices
then ur device will be shown.....
then type
fastboot flash boot boot.img
n its done!
Click to expand...
Click to collapse
I would like to tell you my problem, I have a Mate 9 MHA-L09C605B111 which I did a rebrand a while ago and I'm with CUST 432 and installed the version of Oreo 8.0.0.368, a few weeks ago I received the update 369 via OTA. It was interesting to try; the problem is that I had open bootloader, TWRP Pretorian 3.2.0 and Root, take a terrible decision to do a relock of the bootloader.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in a tutorial
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.
I got the OTA for 5.01 but when it go through the reboot process , it shows a error. I don;t know what it is so I try to flash the sys and boot img but I can't flash them either..........
Can anyone help........
What happens when you try to manually flash them? Does fastboot devices show tablet connected?
di11igaf said:
What happens when you try to manually flash them? Does fastboot devices show tablet connected?
Click to expand...
Click to collapse
When I try to flash the boot img I got this "FAILED (remote: image error! (BootMagic check fail))"
And also when I try to flash sys img it shows
" fastboot: ../libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Aborted "
Weird...
Me too
I'm having the same error as you. When I tried to update the Standart way the error appeared. I tried via sideload and It didn't work either. I tried Rooted, unrooted, both ways fail.
Anybody help please
Hi, I just got the OTA and after make a complete unroot with supersu I have the same problem, OTA error with the lay android and a red triangle.
Any ideas?
Thanks
Jarvia_STGL said:
When I try to flash the boot img I got this "FAILED (remote: image error! (BootMagic check fail))"
Click to expand...
Click to collapse
With latest version of fastboot and lrx22c rom completely unzipped I did the following and it fixed my stuck at "Google" Nexus 9 that also had the bootmagic issue:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase userdata
fastboot erase vendor
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot flash userdata vendor.img
select hboot
factory reset
Not sure the 'fastboot flash userdata vendor.img' is needed here, but it worked so do with this info what you will.
Thank you this helped me get mine running again.
Hi guys, my phone is Infocus M2 3G and I have rooted it earlier. Now I accidentally removed some services and now getting errors. I want to flash stock rom so it can be like previous one.
I installed ADB and fastboot in my system.
When I tried the command
Code:
fastboot flash recovery recovery.img
the following error came:
Code:
sending 'recovery' (10240 KB)...
OKAY [ 0.417s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017
)
finished. total time: 0.430s
I searched and I got to know that this may be because of bootloader lock.
So I tried the command
Code:
fastboot oem unlock
and
Code:
fastboot flashing unlock
For oem unlock it showed unknown command and for flashing unlock it showed all options of fastboot.
I installed Rom Manager and select boot into recovery option, it took me to Android Recovery System 3e.
I have stock rom files downloaded and just want to put stock rom in my phone. Any Ideas that can help?
sumit77seo said:
Hi guys, my phone is Infocus M2 3G and I have rooted it earlier. Now I accidentally removed some services and now getting errors. I want to flash stock rom so it can be like previous one.
I installed ADB and fastboot in my system.
When I tried the command
the following error came:
I searched and I got to know that this may be because of bootloader lock.
So I tried the command and
For oem unlock it showed unknown command and for flashing unlock it showed all options of fastboot.
I installed Rom Manager and select boot into recovery option, it took me to Android Recovery System 3e.
I have stock rom files downloaded and just want to put stock rom in my phone. Any Ideas that can help?
Click to expand...
Click to collapse
You can try putting the stock ROM zip file on the root of your sdcard (As in not located in any sub folders) and renaming the ROM file to update.zip then use the stock recovery to flash the ROM. Let me know if you still have questions!
So I bought a son new phone.
As he told he installed magisk first, flashing "magisk_patched.img" through windows shell, everything was fine. Then He flashed twrp and magisk, everything was almost fine, he noticed that he cant play audio. He was trying to fix it first through installing magisk audio mods like viper and sauron. It didn't fixed anything, he unistalled it, everything was still in the same state, so he decided to flash stock frimware. He flashed through mi flashing tool, unfortunetaly It was image for "global xiaomi version" I mean "PFQMIXM" when as far as I know It should be "PFQEUXM". It didn't work and he was stuck in a bootloop. He found "MiUi 11 " image and for still unknown to me reason thought that it is going to fix everything. He flashed It again through mi flashing tool. It didn't work. He did that second time but at last he just closed the flashing tool while it was doing its thing.
At last he found eu firmware but now after all of that when i try to flash it or single files like crc list i get this:
flash crclist "E:\ModCR\adb\images\crclist.txt"
Sending 'crclist' (0 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Device only boots to fastboot (no recovery/twrp either).
I tried erasing cache:
./fastboot erase cache
Erasing 'cache' FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
I tried to check slots:
./fastboot getvar active-slot
getvar:active-slot FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.003s
I tried to change slot:
./fastboot set_active b
fastboot: error: Device does not support slots
When i typed "fastboot devices" It appeared as "??????"
./fastboot devices
???????????? fastboot
I don't know how to fix it, If anyone knows or has any kind of even small idea please write it down. I would be very greatfull.
Install custom recovery twrp
Install custom rom
Reboot
Download firmware EU
Install a firmware witch miflash
Restore Factory
Walaaaaa
xt610 said:
Install custom recovery twrp
Install custom rom
Reboot
Download firmware EU
Install a firmware witch miflash
Restore Factory
Walaaaaa
Click to expand...
Click to collapse
What i understand from op post is that fastboot commands are not working. So how will he flash twrp?
The firmware version doesn't matter at all you can flash EU on global and vice versa it doesn't matter.
What I think happened was your son never switched to slot 'a' before using mi flash.
Xiaomi's install script for miflash requires you to be on slot 'a' before flashing.
The only way to recover from this is edl mode which requires a xiaomi verified account to fix.
MOD EDIT: Part removed
Please do not advertise/recommend remote unlock services on XDA. Please read the FORUM RULES especially those:
Hi all. I feel like a bit of an idiot. I've been rooting phones for a while, and I finally decided to swap to something new...but I slipped up...and messed up...and feel like an idiot...
I can still get into slot a without a problem (boots into regular os). Slot b though doesn't have an OS. I can't boot manually into TWRP either:
Code:
$ fastboot boot twrp-3.4.0-0-laurel_sprout.img
Sending 'boot.img' (39892 KB) OKAY [ 1.115s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Reflashing twrp to boot_b doesn't work...any thoughts? Worst case, I have the stock OS I guess...
Notes:
Code:
# twrp
https://dl.twrp.me/laurel_sprout/twrp-3.4.0-0-laurel_sprout.img.html
# original guide (unofficial twrp)
https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509
# newer guide (official twrp)
https://forum.xda-developers.com/showpost.php?p=80168528&postcount=16
# magisk
https://github.com/topjohnwu/Magisk/releases/tag/v20.2
# rom
https://crdroid.net/laurel_sprout
https://sourceforge.net/projects/crdroid/files/laurel_sprout/6.x/crDroidAndroid-10.0-20200715-laurel_sprout-v6.8.zip/download
# approximate steps
adb reboot bootloader
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot getvar current-slot
# !!!!!!!!!!!!!!!!!!DO THE INACTIVE OTHER SLOT!!!!!!!!!!!!!!!!!!
fastboot --set-active=b
fastboot flash boot twrp-3.4.0-0-laurel_sprout.img
fastboot reboot
# VOL+ and POWER
Update 0:
I was able to get it back into TWRP with some trial and error. Weirdest thing is that SHRP was installed with crdroid? Weird...?
1. You cannot use boot command in fastboot,
2. This device doesn't have recovery partition, recovery is contained in boot partition which will be always overwritten by custom ROM, thus you got SHRP which I recommend to use, because TWRP is outdated. However if you want to use other recovery, you must always flash it's installer zip right after flashing custom ROM.