Develop Bugs

Fastboot Flashing

Hi, i'm trying to flash by using fastboot with command prompt. I can't flash anything by useing the recovery option in hboot because it keeps taking me back to the hboot menu.
Right. I extracted the rom.zip from the RUU Rom "testruu" which went okay, it has all the images, includeing the recovery image to get it working again. but when i type in "fastboot -p (serial number) update rom.zip" which the rom.zip is located in the sdk tools folder. it comes up with the error
"Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in "MS-DOS symbols.........."
Any ideas? i tried flashing other rom's but they don't contain the "android-info.txt" within the image zip package.....
Please help because my phone is 100% dead with no recovery working and stuck at the htc logo screen.

so no one knows how to flash in fastboot? well great.

Enter fastboot then plug Desire to your computer and run official RRU (*.exe file)
That should help
Cheers

Jacked up Phone

Ok so I cannot figure out what I did to my phone. I have s-off and my phone was rooted with TWRP Custom Recovery. I do not know why I did this but I installed the CWM app and installed the newest CWN recovery for the HTC One. I rebooted into CWM and tried wiping data. It got stuck on that so I rebooted and it gets stuck on the HTC boot up screen. When I go back into the bootloader and try installing the TWRP recovery using fastboot flash recovery recovery.img it gives me a remote: not allowed. When I do fastboot oem lock it says phone is already locked. I then do fastboot oem rebootruu and I get (bootloader) [err] command error!!! When I try rebooting into cwm I just get E: can't mount /cache/recover/commad, E: can't mount /cache/recovery/log and a bunch of other e: cant mount and open errors. Not sure how to get my phone to install the TWRP recovery and get a custom rom back on there. Anyone have any solutions?

slaz13 said:
Ok so I cannot figure out what I did to my phone. I have s-off and my phone was rooted with TWRP Custom Recovery. I do not know why I did this but I installed the CWM app and installed the newest CWN recovery for the HTC One. I rebooted into CWM and tried wiping data. It got stuck on that so I rebooted and it gets stuck on the HTC boot up screen. When I go back into the bootloader and try installing the TWRP recovery using fastboot flash recovery recovery.img it gives me a remote: not allowed. When I do fastboot oem lock it says phone is already locked. I then do fastboot oem rebootruu and I get (bootloader) [err] command error!!! When I try rebooting into cwm I just get E: can't mount /cache/recover/commad, E: can't mount /cache/recovery/log and a bunch of other e: cant mount and open errors. Not sure how to get my phone to install the TWRP recovery and get a custom rom back on there. Anyone have any solutions?
Click to expand...
Click to collapse
Isn't it "fastboot oem reboot ruu" ?

Its
fastboot oem rebootRUU
Are you still s-off?

Sorry guys I actually some how got everything working again. Thanks!!

can only go to fastboot and nothing else

i think i've ****ed up my zenfone 2.
i can only go to fastboot and i can flash boot.img , droidboot.img and recovery.img
but i can't flash system.img (it says error: cannot load 'system.img') and everytime i try to go to recovery , it just freeze on asus logo and that's it.
i can't flash asus zip file (from asus site) because the size of the file is too large and i receive error.
i was using a custom rom and decided to return to stock.
how can i fix my phone?

Your system.img is corrupted somehow, if you are using shakalaca's img just delete the current one in your folder and unzip like you did before, that worked for me after the same thing happened to me while flashing.

okay.i have some good news (for myself )
i can now get into Recovery mode.it's stock recovery with and android robot in it and saying "installing System Update"
but after a few seconds it says error and that's it.
i use "adb devices" but there's no device connected.same for "fastboot devices"
now what should i do?
p.s : i get error everytime i want to "fastboot flash system system.img" and everytime i use "fastboot -w".for flashing system it gives the "error: cannot load 'system.img'" and for -w it says "FAILED (remote: flash_cmds error! )"
edit: now i have TWRP recovery.it's the UN-Tethered one.so i don't think i can install stock rom.right?
what should i do if i want to install stock rom?
edit 2:finally.i installed a custom rom for now.everything is ok.the phone is up and running.
but now i want to return to stock rom.how?

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img

Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command

Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img

DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....

Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards

lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C

Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html

@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!

How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions

bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly

8.1 OTA won't flash - E: Failed to verify whole-file signature??

Hey guys, coming from 8.0.0, trying to flash OTA for 8.1 that was just released.
Unfortunately, after reboot to recovery, pressing power + vol up, choosing to sideload from adb, and running "adb sideload [ota filename].zip" I get the following error on my phone:
E: failed to verify whole-file signature
Update package verification took 77.5s (result 1).
E: Signature verification failed
E: error: 21
I've confirmed I'm using the latest sdk platform tools, and initially I figured it might have been a bad ota file download so I tried downloading a 2nd time but got the same results. I then checked the SHA256 hash of the file and it matched what the Google images pages says it should be so the download isn't corrupt. I'm stock, other than an unlocked bootloader (and critical), magisk, and flash kernel. Any ideas what the heck is going on here??? Thanks!

ohlin5 said:
Hey guys, coming from 8.0.0, trying to flash OTA for 8.1 that was just released.
Unfortunately, after reboot to recovery, pressing power + vol up, choosing to sideload from adb, and running "adb sideload [ota filename].zip" I get the following error on my phone:
E: failed to verify whole-file signature
Update package verification took 77.5s (result 1).
E: Signature verification failed
E: error: 21
I've confirmed I'm using the latest sdk platform tools, and initially I figured it might have been a bad ota file download so I tried downloading a 2nd time but got the same results. I then checked the SHA256 hash of the file and it matched what the Google images pages says it should be so the download isn't corrupt. I'm stock, other than an unlocked bootloader (and critical), magisk, and flash kernel. Any ideas what the heck is going on here??? Thanks!
Click to expand...
Click to collapse
Try downloading the November factory image, unzip and edit the flash-all.bat and remove the "-w" at the end
Reboot into bootloader and run flash-all.
This will remove flash kernel and magisk
Then try to take the December ota

Dielahn said:
Try downloading the November factory image, unzip and edit the flash-all.bat and remove the "-w" at the end
Reboot into bootloader and run flash-all.
This will remove flash kernel and magisk
Then try to take the December ota
Click to expand...
Click to collapse
Thanks! I decided to try a slightly different route and just ended up downloading the full December (8.1) image, then removed the "-w" as suggested, and ran the "flash-all.bat" script from fastboot/bootloader mode. Booted back up perfectly fine with data intact and now just re-patching boot.img so I can get Magisk back up and running…running into another Magisk related issue but otherwise looks good. Thanks!