I want to flash magisk patched boot.img but anytime I try, I get fastboot error 'size too large' but I can boot the img file.please help
Related
hi im getting fastboot mode started
udc_start()
i tried using fast boot reviving post but
im erasing recovery successful
but when i execute fastboot flash recovery recovery.img
im getting an error that not loading recovery.img heip me.......
Try typing the entire path to the recovery file.
follow this to flash custom recovery http://forum.xda-developers.com/showthread.php?t=1318750
for the command "fastboot flash recovery recovery.img", recovery.img refers to the file of your recovery. try doing either:
a) make sure that the name of the recovery file is "recovery.img".
b) change the command "fastboot flash recovery recovery.img" to "fastboot flash recovery (name of the file).img", where (name of the file).img is the actual name of the recovery file (for example, if the name of the file is thunderg.img, the command would be "fastboot flash recovery thunderg.img)
I was trying to change the boot logo using fastboot like you can with the X2 and it doesn't work on Razr, now i get this error "AP Fastboot Flash Mode (s) (Boot Failure)" on boot i have read i just need to flash anything via fastboot to correct the error, i don't want to flash the whole system if i can avoid does anyone have any other .img file like radio.img for the 12.173 cdma Verizon 2.3.6 leaked version?
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.
Hello!
Now I have a trouble with my Nokia 7.1.
When I try to boot twrp or another kernel (boot.img) it stuck. I do '"fastboot boot twrp.img" or "fastboot boot boot.img" and my phone frozes on Android One logo.
And if problem with twrp can be solved (first enter "fastboot flash recovery twrp.img" and only than "fastboot boot twrp.img"), problem with boot.img is still relevant.
I noticed, that after "fastboot boot ..." phone restarts into download mode.
My phone is unlocked.
Thank
Hi, before any boot command, you'll need to do that flash recovery counterpart. You can do it on a standard boot image as well, not just TWRP. There's no recovery partition, so, nothing gets flashed. But it somehow allows us to boot our bootable img files.
So,
Code:
fastboot flash recovery boot.img
fastboot boot boot.img
singhnsk said:
Hi, before any boot command, you'll need to do that flash recovery counterpart. You can do it on a standard boot image as well, not just TWRP. There's no recovery partition, so, nothing gets flashed. But it somehow allows us to boot our bootable img files.
So,
Code:
fastboot flash recovery boot.img
fastboot boot boot.img
Click to expand...
Click to collapse
Yes! Thank you.
I recently came to this conclusion, but what is it?
Does it bootloader bug or anything else?
i have similar problems and just started a new request
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