Database Info

fastboot bricked my device and it's not fixing it back

hello.
I tried to test a custom kernel today. So I followed the advice in cyanogenmod's wiki:
If you are developing a kernel, you may find it helpful to delete your boot.img and recovery.img to force booting into fastboot:
fastboot erase boot
fastboot erase recovery
You can then manually boot from your custom kernel and a ramdisk:
fastboot boot <kernel> <ramdisk>
Once you have a working kernel and ramdisk, you can automagically combine them within fastboot:
fastboot flash:raw boot <kernel> <ramdisk>
Click to expand...
Click to collapse
The erase steps worked happily! But when I reached the boot step:
Code:
% fastboot boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz
creating boot image...
creating boot image - 5416960 bytes
downloading boot.img...
OKAY [ 1.688s]
booting...
FAILED (remote: ()
finished. total time: 1.689s
And now, no matter what I try, I get:
Code:
Unrecoverable bootloader error <0x00000000>.
Flashing the previous (working) boot.img or recovery-jb-touch.img does not work. After finishing what appears to be a successful flash, the device gets unidentified for some reason. So I can't `fastboot reboot`.
Here is the full output:
Code:
% fastboot devices
015d262e983c120f fastboot
% fastboot flash recovery ../recovery-jb-touch.img
sending recovery (6942 KB)...
OKAY [ 1.961s]
writing recovery...
OKAY [ 3.136s]
finished. total time: 5.098s
% fastboot devices
???????????? fastboot
So every time I flash, I have to manually restart to the bootloader. And hence nothing gets fixed, I'm back to square one.
I understand that unlocking voids the warranty. But I expected the extra functionality to actually work if I follow the correct procedure. I didn't expect things to blow up in my face. The fact that I live overseas and there is probably no Asus tech support around here adds an insult to my injury.
I really hope there is a way to fix this.

y2012 said:
hello.
I tried to test a custom kernel today. So I followed the advice in cyanogenmod's wiki:
The erase steps worked happily! But when I reached the boot step:
Code:
% fastboot boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz
creating boot image...
creating boot image - 5416960 bytes
downloading boot.img...
OKAY [ 1.688s]
booting...
FAILED (remote: ()
finished. total time: 1.689s
And now, no matter what I try, I get:
Code:
Unrecoverable bootloader error <0x00000000>.
Flashing the previous (working) boot.img or recovery-jb-touch.img does not work. After finishing what appears to be a successful flash, the device gets unidentified for some reason. So I can't `fastboot reboot`.
Here is the full output:
Code:
% fastboot devices
015d262e983c120f fastboot
% fastboot flash recovery ../recovery-jb-touch.img
sending recovery (6942 KB)...
OKAY [ 1.961s]
writing recovery...
OKAY [ 3.136s]
finished. total time: 5.098s
% fastboot devices
???????????? fastboot
So every time I flash, I have to manually restart to the bootloader. And hence nothing gets fixed, I'm back to square one.
I understand that unlocking voids the warranty. But I expected the extra functionality to actually work if I follow the correct procedure. I didn't expect things to blow up in my face. The fact that I live overseas and there is probably no Asus tech support around here adds an insult to my injury.
I really hope there is a way to fix this.
Click to expand...
Click to collapse
You need to flash the correct kernel and such for the tf700, don't flash anything available out there, you are asking for bricking! I suggest to flash back to full stock firmware then start over.

buhohitr said:
You need to flash the correct kernel and such for the tf700, don't flash anything available out there, you are asking for bricking!
Click to expand...
Click to collapse
It was a CM10 kernel I compiled myself.
buhohitr said:
I suggest to flash back to full stock firmware then start over.
Click to expand...
Click to collapse
Explaining how this can be done from fastboot would be great. Especially when I can't even make recovery work.

Try flashing NVidia blobs instead of raw images ... AFAIK the TF700 bootloader's fastboot implementation only understands blobs.

You also forget the usb ID. Try this
Code:
fastboot -i 0x0B05 boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz

ostar2 said:
You also forget the usb ID. Try this
Code:
fastboot -i 0x0B05 boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz
Click to expand...
Click to collapse
I tried with and without the ID.
Is it really damaging if the ID is not included?

y2012 said:
I tried with and without the ID.
Is it really damaging if the ID is not included?
Click to expand...
Click to collapse
No. There were just some bootloader versions which never showed a serial number, just question marks, when issuing "fastboot devices", and then you needed to specify the ID to get anything to work.
The fastboot implementation in the TF700 is a bit strange. I also could not get "fastboot boot ..." to work, but I never erased my boot and recovery partitions. Just flashing blobs worked fine.

_that said:
The fastboot implementation in the TF700 is a bit strange. I also could not get "fastboot boot ..." to work, but I never erased my boot and recovery partitions. Just flashing blobs worked fine.
Click to expand...
Click to collapse
Can you elaborate on flashing blobs?
What blobs should I flash and where/how can I obtain them?

For reference:
Code:
% fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d262e983c120f
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.082s

y2012 said:
Can you elaborate on flashing blobs?
What blobs should I flash and where/how can I obtain them?
Click to expand...
Click to collapse
TF700 fastboot likes to flash blobs that start with a "-SIGNED-BY-SIGNBLOB-" header, followed by an "MSM-RADIO-UPDATE" header.
Try flashing the TWRP recovery from here (see "Fastboot method"): http://www.teamw.in/project/twrp2/105
y2012 said:
For reference:
Code:
% fastboot getvar all
...
Click to expand...
Click to collapse
I am getting the same output on mine, the only differences are the serial number (greetings from Captain Obvious) and the size of the userdata partition (I have a 64 GB tablet).

_that said:
TF700 fastboot likes to flash blobs that start with a "-SIGNED-BY-SIGNBLOB-" header, followed by an "MSM-RADIO-UPDATE" header.
Try flashing the TWRP recovery from here (see "Fastboot method"): http://www.teamw.in/project/twrp2/105
Click to expand...
Click to collapse
Flashing TWRP didn't work.
I think I'm giving up on this.

y2012 said:
Flashing TWRP didn't work.
Click to expand...
Click to collapse
Details?

Ive started the same thread erased the recovery it says it writed recovery image but i think the tablet freezes as any command after writing recovery will not work but before that it will an example:
try adb reboot the tablet will reboot
but after writing the recovery image try entering that command and see what happens
guess Im not the only one who has this problem now we need solutions
Edit: I just remembered I had plan to use Ubuntu to write recovery image see if you can flash ubuntu as the files are on SD rather then on tablet
also skythra had a similar problem he/she said that the fastboot unlocker for jellybean you cannot write you can only read and boot
I also want to ask you have a 64 GB as well?

_that said:
Details?
Click to expand...
Click to collapse
Same as the OP. Flashing looked like it succeeded. The device gets unidentified in fastboot after that. Manual restart. And choosing recovery shows the same error.
It looks like the only options left are:
1] fastboot flash -- I don't know where to get an update.zip that works with this.
2] fastboot flashall -- I don't know how this command works as it doesn't take any arguments.

4SHR4F said:
Ive started the same thread erased the recovery it says it writed recovery image but i think the tablet freezes as any command after writing recovery will not work but before that it will an example:
try adb reboot the tablet will reboot
but after writing the recovery image try entering that command and see what happens
Click to expand...
Click to collapse
Assuming you meant fastboot not adb. This is true. The device gets unidentified (see `fastboot devices` output). Whether the freeze is caused by the unidentified device, or both symptoms are caused by something else, I don't know.
guess Im not the only one who has this problem now we need solutions
Click to expand...
Click to collapse
Well, Asus will not help. They provide half-assed unlocking feature, broken fastboot, and void your warranty in the process. Way to go winning developers and advanced users!
I also want to ask you have a 64 GB as well?
Click to expand...
Click to collapse
No. 32GB here.

y2012 said:
Assuming you meant fastboot not adb. This is true. The device gets unidentified (see `fastboot devices` output). Whether the freeze is caused by the unidentified device, or both symptoms are caused by something else, I don't know.
Well, Asus will not help. They provide half-assed unlocking feature, broken fastboot, and void your warranty in the process. Way to go winning developers and advanced users!
No. 32GB here.
Click to expand...
Click to collapse
Let me know what happens someone suggested downgrading to ICS then use debugfs and then use custom rom root and terminal to send the recovery that way either way my computers PCI card decided to stop working so I have to tether it and then download the tools which is a problemsince I formatted my whole computer to get this transformer workin best of luck but like I said please post ur method cause im in the same boat

4SHR4F said:
Let me know what happens someone suggested downgrading to ICS then use debugfs and then use custom rom root and terminal to send the recovery that way either way my computers PCI card decided to stop working so I have to tether it and then download the tools which is a problemsince I formatted my whole computer to get this transformer workin best of luck but like I said please post ur method cause im in the same boat
Click to expand...
Click to collapse
Bump any solutions cant use flash or boot so cant do anything could someone send us bootlocker tool or something i dont know please help

y2012 said:
Same as the OP. Flashing looked like it succeeded. The device gets unidentified in fastboot after that. Manual restart. And choosing recovery shows the same error.
It looks like the only options left are:
1] fastboot flash -- I don't know where to get an update.zip that works with this.
2] fastboot flashall -- I don't know how this command works as it doesn't take any arguments.
Click to expand...
Click to collapse
fastboot -b flashall
-b (specify a custom kernel base address)
in the same boat

[Q] HTC one mini stuck in bootloader

My dads HTC one mini is stuck in the bootloader menu. I cannot access recovery. it is locked. I have tried To flash a custom recovery but since its locked it wont work. I tried to unlock it with
HTCdev unlock bootloader but i cant get the phone to react when i do (fastboot flash unlocktoken Unlock_code.bin.) the cmd prompt looks like it works but i don't get a screen to approval unlock on the phone. I have been at this for hours now and any help would be great. I'll check back in tomorrow

Unit3 said:
My dads HTC one mini is stuck in the bootloader menu. I cannot access recovery. it is locked. I have tried To flash a custom recovery but since its locked it wont work. I tried to unlock it with
HTCdev unlock bootloader but i cant get the phone to react when i do (fastboot flash unlocktoken Unlock_code.bin.) the cmd prompt looks like it works but i don't get a screen to approval unlock on the phone. I have been at this for hours now and any help would be great. I'll check back in tomorrow
Click to expand...
Click to collapse
Does fastboot say "fastboot usb"?
What happens when you type fastboot devices? This should return your serial number.
Are you on Windows? Which version?

jollywhitefoot said:
Does fastboot say "fastboot usb"?
What happens when you type fastboot devices? This should return your serial number.
Are you on Windows? Which version?
Click to expand...
Click to collapse
sorry it took so long for me to get back. so Yes it says "fastboot USB" . fastboot devices gives me HT38EWA03720 fastboot. I am on Windows 7

That's really strange.
Can you confirm the unlock token is in the same directory you're running your fastboot command from in command prompt? Can you post the output from the fastboot unlock command?

Hi
i have the same issue
the htc one mini is stuck on fastboot.
when trying to go recovery it just reboot back to fastboot
bootloader is locked, i tried to unlock it - this is the fastboot text:
C:\adb>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800227328 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.157s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.020s]
finished. total time: 0.183s
but im not getting the disclaimer on the phone to continue
i have win 8 (also have win 7- same thing there)
the device shown in the device manager as 'my htc"

reviving the dead ...
Anyone found a solution yet?

Anyone found a solution yet?

Moto G3 (XT1543, osprey) stuck at fastboot screen

Dear people,
First of all, although dilligent and trying to do my homework, I am a total newbie regarding anything Android. Therefore, if I am posting on the wrong section of the site, please let me know and I will try my best to fix it.
That being said, I have a Moto G3 (Moto G 2015), model XT1543 (osprey), that is stuck in the fastboot boot. I have searched a lot of the web trying to find solutions and, after having failed all of them, decided to come here for assistance.
My device only boots and displays:
AP Fastboot Flash Mode (Secure)
version downgrade for recovery
failed to validate recovery image
ERROR: Failed to pass verification, backup to fastboot
Fastboot Reason: Fall-through from recovery boot mode​
I already downloaded the appropriate TWRP recovery image for the device (osprey), but the bootloader is locked and, since I can't get into the system properly, I can't switch the "Unlock OEM boot" flag when the full system is running.
In particular, when I try to flash TWRP, this is what I get:
# fastboot flash recovery twrp-3.1.0-1-osprey.img
target reported max download size of 268435456 bytes
sending 'recovery' (7546 KB)...
OKAY [ 0.373s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.454s​
Indeed, since I am only in fastboot mode, I went away and requested a boot unlock code from Motorola and trying to unlock the bootloader and this is what I get:
# fastboot oem unlock <my-code-here>
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.034s​
I already tried looking at similar questions in many, many forums and no answer actually applied to my device (including, for example, https://forum.xda-developers.com/2015-moto-g/help/moto-g3-struck-fastboot-screen-t3542147 and even others for other models and vendors).
Thanks in advance for any help.

At this point your only option to flash the same or newer factory image through fastboot. The is no way to unlock the bootloader without the OEM unlock in developer options checked, and with a locked bootloader you can't flash an older version. See the thread on flashing factory images.
Sent from my MotoG3 using Tapatalk

riggerman0421 said:
At this point your only option to flash the same or newer factory image through fastboot. The is no way to unlock the bootloader without the OEM unlock in developer options checked, and with a locked bootloader you can't flash an older version. See the thread on flashing factory images.
Click to expand...
Click to collapse
OK. So, now, I know how to direct my energies and avoid useless efforts.
Thank you so very much, @riggerman0421. Now, to find which factory image was the one that was installed on this device (it is actually my father's device).

rtbrito said:
OK. So, now, I know how to direct my energies and avoid useless efforts.
Thank you so very much, @riggerman0421. Now, to find which factory image was the one that was installed on this device (it is actually my father's device).
Click to expand...
Click to collapse
You can follow the guide here. Try it with the latest firmware available here.
Broadcasted from Zeta Reticuli

Trying to root with Android 8.0

So I've been using this guide to finally try and root my Pixel on 8.0: {apparently I can't post links yet, but google "how to root google pixel droidviews" and it's the first link}
I'm able to get adb to recognize the phone, however, when I go to use the command "fastboot boot recovery twrpOreo.img", the console says "cannot boot 'recovery': No such file or directory". So then I did some googling and tried the command "fastboot flash recovery twrpOreo.img" to which the console spits out:
C:\adb>fastboot flash recovery twrpOreo.img
target reported max download size of 536870912 bytes
sending 'recovery' (26029 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.802s
All the while the screen on the phone says:
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
So it says the device is locked but I triple checked, and I unlocked the bootloader under developer settings? Can anyone help me out here?

Kew01 said:
So I've been using this guide to finally try and root my Pixel on 8.0: {apparently I can't post links yet, but google "how to root google pixel droidviews" and it's the first link}
I'm able to get adb to recognize the phone, however, when I go to use the command "fastboot boot recovery twrpOreo.img", the console says "cannot boot 'recovery': No such file or directory". So then I did some googling and tried the command "fastboot flash recovery twrpOreo.img" to which the console spits out:
C:\adb>fastboot flash recovery twrpOreo.img
target reported max download size of 536870912 bytes
sending 'recovery' (26029 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.802s
All the while the screen on the phone says:
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
So it says the device is locked but I triple checked, and I unlocked the bootloader under developer settings? Can anyone help me out here?
Click to expand...
Click to collapse
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images

Kew01 said:
So I've been using this guide to finally try and root my Pixel on 8.0: {apparently I can't post links yet, but google "how to root google pixel droidviews" and it's the first link}
I'm able to get adb to recognize the phone, however, when I go to use the command "fastboot boot recovery twrpOreo.img", the console says "cannot boot 'recovery': No such file or directory". So then I did some googling and tried the command "fastboot flash recovery twrpOreo.img" to which the console spits out:
C:\adb>fastboot flash recovery twrpOreo.img
target reported max download size of 536870912 bytes
sending 'recovery' (26029 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.802s
All the while the screen on the phone says:
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
So it says the device is locked but I triple checked, and I unlocked the bootloader under developer settings? Can anyone help me out here?
Click to expand...
Click to collapse
You skipped a step. You also need to issue the fastboot command to unlock it.
This will WIPE your phone. No way around that.
fastboot flashing unlock

TonikJDK said:
You skipped a step. You also need to issue the fastboot command to unlock it.
This will WIPE your phone. No way around that.
fastboot flashing unlock
Click to expand...
Click to collapse
Damn, really? There's no way to preserve my data? I know I can back up my photos/docs and **** but I'd sacrifice a lot of app data/preferences by wiping.

Kew01 said:
Damn, really? There's no way to preserve my data? I know I can back up my photos/docs and **** but I'd sacrifice a lot of app data/preferences by wiping.
Click to expand...
Click to collapse
This is why you should unlock the phone as soon as you buy it.

So maybe a dumb question but I'm new to all this. Is there any way I could completely backup a clone of my phone's data, and then restore it after root, so that everything is just as it was, except now I have root privileges?

Kew01 said:
So maybe a dumb question but I'm new to all this. Is there any way I could completely backup a clone of my phone's data, and then restore it after root, so that everything is just as it was, except now I have root privileges?
Click to expand...
Click to collapse
No. You can do this once you are rooted and have TWRP but not before. Just back up your important data and go for it.

Kew01 said:
Damn, really? There's no way to preserve my data? I know I can back up my photos/docs and **** but I'd sacrifice a lot of app data/preferences by wiping.
Click to expand...
Click to collapse
Isn't app data automatically backed up on Google servers? Or am I recalling it wrongly?

Golf c said:
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images
Click to expand...
Click to collapse
Whenever I click "Acknowledge" on the page, the page just reloads?

Golf c said:
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images
Click to expand...
Click to collapse
Kew01 said:
Whenever I click "Acknowledge" on the page, the page just reloads?
Click to expand...
Click to collapse
**** nevermind I figured it out.

Golf c said:
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images
Click to expand...
Click to collapse
Sorry for spamming you, but it looks like the official instructions only show you how to re-flash the system OS without root privileges? My goal is to re-flash with root.

Kew01 said:
Sorry for spamming you, but it looks like the official instructions only show you how to re-flash the system OS without root privileges? My goal is to re-flash with root.
Click to expand...
Click to collapse
1. Flash factory image
2. Boot system
3. Reboot bootloader
4. Fastboot Twrp 3.1.1.1
5. Flash Twrp 3.1.1.1 installer zip or not if you don't want permanent Twrp
6. Flash SuperSU or Magisk
7. Reboot system

Revert back to Android O

Finally got the Android P update and I hate it. I'm wanting to revert back to Android 8. I'm a complete noob and have never attempted to root or anything like this before. Can anyone help?
Also, I'm aware ill have to do a factory reset or something like that at some point. Can someone recommend a complete back up tool for android? I've obviously made back ups before but they've only ever been certain apps or call logs etc. Is there a (preferably free) tool that literally allows to me back up, reset, and restore and end up with my phone contents as if I never reset?

wiliestseven51 said:
Finally got the Android P update and I hate it. I'm wanting to revert back to Android 8. I'm a complete noob and have never attempted to root or anything like this before. Can anyone help?
Also, I'm aware ill have to do a factory reset or something like that at some point. Can someone recommend a complete back up tool for android? I've obviously made back ups before but they've only ever been certain apps or call logs etc. Is there a (preferably free) tool that literally allows to me back up, reset, and restore and end up with my phone contents as if I never reset?
Click to expand...
Click to collapse
Edit: Downgrading is not an easy task. My understanding is you will first need to downgrade your firmware, then flash a compatible RUU. I believe this requires you to be s-off.
As far as the backup you mentioned, well that's what TWRP is for. First you'll need to unlock your bootloader which you can do by following the instructions from the htcdev website (understand this will factory reset your phone). Then find the TWRP thread which will have instructions on how to temporarily boot TWRP or permanently install TWRP to your phone's boot partition. Within TWRP you can perform the backup you desire. There is a learning curve to all of this. Good luck.

RUU download here --> https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/edit#gid=0
About backup,if you are rooted, use twrp recovery o titanium backup app,otherwise google drive backup

I'm having trouble unlocking the bootloader and using fastboot. Im following the instruction son the htcdev page and the code it wants me to enter just fails every single time. When I use the 'fastboot devices' I get the verification code that everything is working. I've attached an image of what the error code. Im thinking its a windows driver issue, I download the google usb driver direct and it makes me choose one of 3 modes? I've tried all 3 and get the same error code on all 3. I've tried other commands but pretty much anything than the 'fastboot devices' causes the error code. Any ideas?
Thanks for your help.
Couldn't attach the image links so ill just type the error:
FAILED (write to device failed (unknown error))
fastboot: error : command failed
and the 3 driver choices were :
Android ADB interface
Android Bootloader interface
Android Composite ADB interface

Maybe this could help though
https://forum.xda-developers.com/u12-plus/how-to/downgrade-s-t3930103

wiliestseven51 said:
I'm having trouble unlocking the bootloader and using fastboot. Im following the instruction son the htcdev page and the code it wants me to enter just fails every single time. When I use the 'fastboot devices' I get the verification code that everything is working. I've attached an image of what the error code. Im thinking its a windows driver issue, I download the google usb driver direct and it makes me choose one of 3 modes? I've tried all 3 and get the same error code on all 3. I've tried other commands but pretty much anything than the 'fastboot devices' causes the error code. Any ideas?
Thanks for your help.
Couldn't attach the image links so ill just type the error:
FAILED (write to device failed (unknown error))
fastboot: error : command failed
and the 3 driver choices were :
Android ADB interface
Android Bootloader interface
Android Composite ADB interface
Click to expand...
Click to collapse
I use HTC windows driver version 4.10 and the fastboot binaries from step 4 of the unlock bootloader process. I've never had to make the choice you are describing.
Sounds like you are basically on the last step of the procedure, no?

Hi guys, sorry for reply after such a long time I was busy with work.
So I downloaded those drivers and have managed to get futher through the HTC unlock process. I'm now stuck on the final step. I've got the unlock code bin from htc and the dev site is telling to me to enter the code: fastboot flash unlocktoken Unlock_code.bin
I copied and paste this into the command prompt and I get this:
PS C:\Users\Wilie\Downloads\platform-tools_r29.0.2-windows\platform-tools> .\fastboot flash unlocktoken Unlock_code.bin
Sending 'unlocktoken' (0 KB) OKAY [ 1.002s]
Writing 'unlocktoken' (bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: 'UnlockToken Verify Fail!!')
fastboot: error: Command failed
From what i can tell the command works for the first part and then fails near the end. I'm completely stumped here, any ideas?

wiliestseven51 said:
Hi guys, sorry for reply after such a long time I was busy with work.
So I downloaded those drivers and have managed to get futher through the HTC unlock process. I'm now stuck on the final step. I've got the unlock code bin from htc and the dev site is telling to me to enter the code: fastboot flash unlocktoken Unlock_code.bin
I copied and paste this into the command prompt and I get this:
PS C:\Users\Wilie\Downloads\platform-tools_r29.0.2-windows\platform-tools> .\fastboot flash unlocktoken Unlock_code.bin
Sending 'unlocktoken' (0 KB) OKAY [ 1.002s]
Writing 'unlocktoken' (bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: 'UnlockToken Verify Fail!!')
fastboot: error: Command failed
From what i can tell the command works for the first part and then fails near the end. I'm completely stumped here, any ideas?
Click to expand...
Click to collapse
You have got oem unlock & adb debugging set in developers option sliders on? Try "adb reboot" command, see if your adb has been authorised on yr PC. I had a dodgy lead, using usb3 port, using shell instead of cmd cause similar problems