should i have radio img and bootloader img of nexus4's kitkat??
i have flashable zip,but i don't want to install there by recovery...i would like to flash them via fastboot on ubuntu terminal.
thanks to all
download the factory image from google. Then you can extract all of the xxxx.img and flash those via fastboot.
Related
Hello! I have an P8Lite ALE-L21 unlocked and by mistake I delete the system.. Now I don't have OS to boot
What can I do now to have back?
Download the rom for your phone then install the rom using the recovery system op the phone.
If that doesn't work try flashing the rom through fastboot.
EpicBas said:
Download the rom for your phone then install the rom using the recovery system op the phone.
If that doesn't work try flashing the rom through fastboot.
Click to expand...
Click to collapse
I tried both but it dosen't work
I don't find source with system.img
Use this http://forum.xda-developers.com/showthread.php?t=2433454&page=31 to extract the system.img
- Fastboot flash boot boot.img
- Fastboot flash recovery recovery.img
- Fastboot flash cust cust.img
- Fastboot flash system system.img
- Fastboot reboot
Use those commands and I hope it will be fixed.
Is it possible to fastboot flash recocery twrp.img to get twrp back if i had to flash stock recovery img for something. Given im running custom ROM.
Need to roll back from Nougat to Marshmallow and not entirely sure how to flash the revolution recovery via fastboot. Help is appreciated
fastboot flash recovery recoveryname.img
I just finished flashing the latest vendor image + dirty unicorns rom + root + gapps and made a reboot.
Then I decided to also update my bootloader and downloaded 3.68.
I went into TWRP, flash .img, boot, choose bootloader.img
Thw flash was successfull but since then i cant boot the rom anymore? I am only able too boot the recovery but not the rom.
Do I need to re-flash the rom now or what should I do?
Oh it seems like flashing "boot" in "TWRP" means that you will flash the boot.img and not the bootloader.
So I just flashed the bootloader via fastboot and I guess I will be just fine if I extract boot.img from the lates rom.zip and flash that in TWRP?
@edit: ye that fixed it.
Utini said:
Oh it seems like flashing "boot" in "TWRP" means that you will flash the boot.img and not the bootloader.
So I just flashed the bootloader via fastboot and I guess I will be just fine if I extract boot.img from the lates rom.zip and flash that in TWRP?
@edit: ye that fixed it.
Click to expand...
Click to collapse
Yep, never flash any images other than the vendor, bootloader and radio unless you are trying to restore to stock. Bootloader is the obvious area of the phone you can use to enter recovery but boot is the actual boot process of the phone so be careful there. Glad you got it sorted.:good:
I have Oreo 27-12-2017 installed on my mi a1, I downloaded the official update.zip file to be installed via adb sideload
I was having TWRP recovery installed but i changed it to Stock recovery to install oreo via adb sideload, but I an't do it it always give me error and phone keep restarting, anyone have an idea how to install it via adb sideload ?
Sideload din't work for me with any OTA update, but I got also at a ceratin point a bootloop. It was solved by downloading the latest fastboot ROM from the xiaomi site. Download the tgz, extract it and use the flash_all_except_storage.sh (mac/linux) or the .bat for windows.
You will then have nougat but at least it solved the issue without data loss. I think that articles about updating via stock recovery and adb are not working at all. Also a lot of articles found via google are kind of fake. A lot say to flash the boot.img via "fastboot flash boot boot.img" but the official .bat and .sh file say that its done via:
fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
pmmtch said:
Sideload din't work for me with any OTA update, but I got also at a ceratin point a bootloop. It was solved by downloading the latest fastboot ROM from the xiaomi site. Download the tgz, extract it and use the flash_all_except_storage.sh (mac/linux) or the .bat for windows.
You will then have nougat but at least it solved the issue without data loss. I think that articles about updating via stock recovery and adb are not working at all. Also a lot of articles found via google are kind of fake. A lot say to flash the boot.img via "fastboot flash boot boot.img" but the official .bat and .sh file say that its done via:
fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Click to expand...
Click to collapse
fastboot flash boot boot.img is the same as fastboot flash boot_a boot.img and fastboot flash boot_b boot.img. You would use the two commands to flash different boot images to different partitions because as you know our device is divided into 2 partitions because of the seamless update