Develop Bugs

How can i get update OTA direct from HTC?

Hi everyone,
I'm S-on, unlocked. I used custom Rom, now i want to come back ROM stock for update firmware.
I formatted data and came back to Nandroid, then i flashed to come back stock recovery.
But when i do update, it notify:
Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance.
It means that i can't update directly from HTC.
Now how can i do ?
Thanks you for your help.

You need to find the ruu for your model and run it on your pc, that's the easiest method. Then you will need to reroot.

i relocked, go to RUU mod, run fastboot flash zip rom.zip and no result:
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1845895323 is not a multiple of
the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 1845895323 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 1845895323 is not a multiple of
the block size 4096
OKAY [ 1.015s]
writing 'zip' 1/1...
(bootloader) HOSD CL#738269
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_H
(bootloader) s9xlG
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap )
finished. total time: 3.089s

Using HTC 10 batch tool in this thread: http://forum.xda-developers.com/one-m9/development/firmware-t3068243
and i was was successful, may be this probem came from my phone/adb, fastboot

Fairphone FP2 Damaged bootloader

Hello all!
I have an Fairphone 2 (FP2) on my operational table with damaged bootloader.
The bootloader was damaged and it was not possible to to get into the fastboot mode. and it was another bootloader flashed from an Device with the same Qualcomm Snapdragon 801 MSM8974AA - OnePlus X.
No i have this problem:
Code:
[email protected]:/home/explit/Service/FP2/FW/FP2-GMS/17.04.8# ./flash.sh
< waiting for any device >
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.011s]
writing 'rpm'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.012s
target reported max download size of 1073741824 bytes
sending 'sbl1' (274 KB)...
OKAY [ 0.017s]
writing 'sbl1'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.018s
target reported max download size of 1073741824 bytes
sending 'tz' (326 KB)...
OKAY [ 0.017s]
writing 'tz'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.020s
target reported max download size of 1073741824 bytes
sending 'modem' (57425 KB)...
OKAY [ 3.272s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 3.273s
target reported max download size of 1073741824 bytes
sending 'splash' (6075 KB)...
OKAY [ 0.377s]
writing 'splash'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.378s
target reported max download size of 1073741824 bytes
sending 'aboot' (520 KB)...
OKAY [ 0.027s]
writing 'aboot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.029s
target reported max download size of 1073741824 bytes
sending 'boot' (14272 KB)...
OKAY [ 0.785s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.786s
target reported max download size of 1073741824 bytes
sending 'recovery' (13038 KB)...
OKAY [ 0.725s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.726s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.001s
wiping userdata...
Creating filesystem with parameters:
Size: 12611891200
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3079075
Block groups: 94
Reserved block group size: 751
Created filesystem with 11/770048 inodes and 88617/3079075 blocks
target reported max download size of 1073741824 bytes
wiping cache...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
erasing 'userdata'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.001s
Press Enter to reboot the device
rebooting...
finished. total time: 0.251s
Press any key to continue...
[email protected]:/home/explit/Service/FP2/FW/FP2-GMS/17.04.8# fastboot flashing unlock
...
I also have another FP2, which is working.
Is it somehow possible to download the bootloader (or all partitions) and restore them on the broking FP2?

You have flashed oneplus x bootloader on fp2 ?
How ?
Cam we use roms from oneplus x for fp2 ?

Stuck in bootloop, NRT doesn't help

My Nexus 5X was on 7.1.2 and rooted. But I wanted to go to 7.1.1 (for some compatibility).
So, I went on Google APIs and downloaded the 7.1.1 N4F26T, Mar 2017 build and together with Platform Tools I used "flash-all".
But... at a certain point, I get an error and it stopped.
Logs:
C:\Users\*\Desktop\android img\bullhead-n4f26t>flash-all
target reported max download size of 536870912 bytes
sending 'bootloader' (4603 KB)...
OKAY [ 0.173s]
writing 'bootloader'...
OKAY [ 0.135s]
finished. total time: 0.317s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.359s]
writing 'radio'...
OKAY [ 0.494s]
finished. total time: 1.859s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 27283927040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6661115
Block groups: 204
Reserved block group size: 1024
Created filesystem with 11/1667904 inodes and 148720/6661115 blocks
wiping cache...
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
--------------------------------------------
Bootloader Version...: BHZ11h
Baseband Version.....: M8994F-2.6.36.2.20
Serial Number........: 014702846496c259
--------------------------------------------
checking product...
OKAY [ 0.021s]
checking version-bootloader...
OKAY [ 0.017s]
checking version-baseband...
OKAY [ 0.018s]
sending 'boot' (12013 KB)...
OKAY [ 0.345s]
writing 'boot'...
OKAY [ 0.105s]
sending 'recovery' (16141 KB)...
OKAY [ 0.464s]
writing 'recovery'...
OKAY [ 0.163s]
erasing 'system'...
OKAY [ 0.575s]
sending sparse 'system' 1/6 (520438 KB)...
OKAY [ 13.092s]
writing 'system' 1/6...
OKAY [ 5.904s]
sending sparse 'system' 2/6 (515462 KB)...
OKAY [ 13.286s]
writing 'system' 2/6...
OKAY [ 5.574s]
sending sparse 'system' 3/6 (479562 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 53.984s
Press any key to exit...
Ok... the phone is in bootloop (for more than 20 min). I tried again, the same thing. I installed Nexus Root Toolkit 2.1.6 and I tried with "Flash Stock + Unroot" with the same build N4F26T but I get the same thing.
So, I tried an older build, N4F26O.
This one worked, kind of, some errors in the process but it managed to finish the flashing.
Logs:
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 536870912 bytes
sending 'bootloader' (4603 KB)...
OKAY [ 0.182s]
writing 'bootloader'...
OKAY [ 0.133s]
finished. total time: 0.320s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.013s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.404s]
writing 'radio'...
OKAY [ 0.491s]
finished. total time: 1.902s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 536870912 bytes
erasing 'vendor'...
OKAY [ 0.076s]
sending 'vendor' (25792 KB)...
OKAY [ 0.676s]
writing 'vendor'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 0.958s
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.568s]
sending sparse 'system' 1/6 (520382 KB)...
OKAY [ 12.999s]
writing 'system' 1/6...
OKAY [ 5.097s]
sending sparse 'system' 2/6 (515518 KB)...
OKAY [ 12.752s]
writing 'system' 2/6...
OKAY [ 5.570s]
sending sparse 'system' 3/6 (479542 KB)...
OKAY [ 11.994s]
writing 'system' 3/6...
OKAY [ 4.906s]
sending sparse 'system' 4/6 (514681 KB)...
OKAY [ 13.001s]
writing 'system' 4/6...
OKAY [ 5.170s]
sending sparse 'system' 5/6 (524285 KB)...
OKAY [ 13.645s]
writing 'system' 5/6...
OKAY [ 5.062s]
sending sparse 'system' 6/6 (182573 KB)...
OKAY [ 4.856s]
writing 'system' 6/6...
OKAY [ 1.688s]
finished. total time: 97.350s
Creating filesystem with parameters:
Size: 27283927040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6661115
Block groups: 204
Reserved block group size: 1024
Created filesystem with 11/1667904 inodes and 148720/6661115 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.611s]
sending 'userdata' (138993 KB)...
OKAY [ 3.435s]
writing 'userdata'...
OKAY [ 1.534s]
finished. total time: 5.581s
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.073s]
sending 'cache' (5688 KB)...
OKAY [ 0.231s]
writing 'cache'...
OKAY [ 0.068s]
finished. total time: 0.371s
rebooting...
finished. total time: 0.012s
Still in bootloop after 20 min, so I tried what the NRT said, went into recovery and did a factory reset from there, but same ****. After 20 minutes still in bootloop.
Tried the Soft-Bricked/Bootloop in NRT but it didn't help.
I don't really know what to do....
Send help

Omseik said:
My Nexus 5X was on 7.1.2 and rooted. But I wanted to go to 7.1.1 (for some compatibility).
So, I went on Google APIs and downloaded the 7.1.1 N4F26T, Mar 2017 build and together with Platform Tools I used "flash-all".
But... at a certain point, I get an error and it stopped.
Logs:
C:\Users\*\Desktop\android img\bullhead-n4f26t>flash-all
target reported max download size of 536870912 bytes
sending 'bootloader' (4603 KB)...
OKAY [ 0.173s]
writing 'bootloader'...
OKAY [ 0.135s]
finished. total time: 0.317s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.359s]
writing 'radio'...
OKAY [ 0.494s]
finished. total time: 1.859s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 27283927040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6661115
Block groups: 204
Reserved block group size: 1024
Created filesystem with 11/1667904 inodes and 148720/6661115 blocks
wiping cache...
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
--------------------------------------------
Bootloader Version...: BHZ11h
Baseband Version.....: M8994F-2.6.36.2.20
Serial Number........: 014702846496c259
--------------------------------------------
checking product...
OKAY [ 0.021s]
checking version-bootloader...
OKAY [ 0.017s]
checking version-baseband...
OKAY [ 0.018s]
sending 'boot' (12013 KB)...
OKAY [ 0.345s]
writing 'boot'...
OKAY [ 0.105s]
sending 'recovery' (16141 KB)...
OKAY [ 0.464s]
writing 'recovery'...
OKAY [ 0.163s]
erasing 'system'...
OKAY [ 0.575s]
sending sparse 'system' 1/6 (520438 KB)...
OKAY [ 13.092s]
writing 'system' 1/6...
OKAY [ 5.904s]
sending sparse 'system' 2/6 (515462 KB)...
OKAY [ 13.286s]
writing 'system' 2/6...
OKAY [ 5.574s]
sending sparse 'system' 3/6 (479562 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 53.984s
Press any key to exit...
Ok... the phone is in bootloop (for more than 20 min). I tried again, the same thing. I installed Nexus Root Toolkit 2.1.6 and I tried with "Flash Stock + Unroot" with the same build N4F26T but I get the same thing.
So, I tried an older build, N4F26O.
This one worked, kind of, some errors in the process but it managed to finish the flashing.
Logs:
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 536870912 bytes
sending 'bootloader' (4603 KB)...
OKAY [ 0.182s]
writing 'bootloader'...
OKAY [ 0.133s]
finished. total time: 0.320s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.013s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.404s]
writing 'radio'...
OKAY [ 0.491s]
finished. total time: 1.902s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 536870912 bytes
erasing 'vendor'...
OKAY [ 0.076s]
sending 'vendor' (25792 KB)...
OKAY [ 0.676s]
writing 'vendor'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 0.958s
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.568s]
sending sparse 'system' 1/6 (520382 KB)...
OKAY [ 12.999s]
writing 'system' 1/6...
OKAY [ 5.097s]
sending sparse 'system' 2/6 (515518 KB)...
OKAY [ 12.752s]
writing 'system' 2/6...
OKAY [ 5.570s]
sending sparse 'system' 3/6 (479542 KB)...
OKAY [ 11.994s]
writing 'system' 3/6...
OKAY [ 4.906s]
sending sparse 'system' 4/6 (514681 KB)...
OKAY [ 13.001s]
writing 'system' 4/6...
OKAY [ 5.170s]
sending sparse 'system' 5/6 (524285 KB)...
OKAY [ 13.645s]
writing 'system' 5/6...
OKAY [ 5.062s]
sending sparse 'system' 6/6 (182573 KB)...
OKAY [ 4.856s]
writing 'system' 6/6...
OKAY [ 1.688s]
finished. total time: 97.350s
Creating filesystem with parameters:
Size: 27283927040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6661115
Block groups: 204
Reserved block group size: 1024
Created filesystem with 11/1667904 inodes and 148720/6661115 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.611s]
sending 'userdata' (138993 KB)...
OKAY [ 3.435s]
writing 'userdata'...
OKAY [ 1.534s]
finished. total time: 5.581s
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.073s]
sending 'cache' (5688 KB)...
OKAY [ 0.231s]
writing 'cache'...
OKAY [ 0.068s]
finished. total time: 0.371s
rebooting...
finished. total time: 0.012s
Still in bootloop after 20 min, so I tried what the NRT said, went into recovery and did a factory reset from there, but same ****. After 20 minutes still in bootloop.
Tried the Soft-Bricked/Bootloop in NRT but it didn't help.
I don't really know what to do....
Send help
Click to expand...
Click to collapse
what happend to you happend to me as weel,
my phone was rooted and bootloader unlocked, so i unroot and lock the bootloader and send the phone do the warranty, after 2 days my phone was already ready to pick up and seems like the motherboard(tranlation from my language, sorry if is not the correct word) was changed to a new one, now the phone is tottaly fine :good:
I think you should send the phone to warranty.

HugoSilva said:
what happend to you happend to me as weel,
my phone was rooted and bootloader unlocked, so i unroot and lock the bootloader and send the phone do the warranty, after 2 days my phone was already ready to pick up and seems like the motherboard(tranlation from my language, sorry if is not the correct word) was changed to a new one, now the phone is tottaly fine :good:
I think you should send the phone to warranty.
Click to expand...
Click to collapse
That's not a solution for me.... I need to make it boot somehow

Omseik said:
That's not a solution for me.... I need to make it boot somehow
Click to expand...
Click to collapse
If this is not a solution for you, sorry cant help you :crying:

Fixed the problem
So... until today, I always used the USB-C cable provided by Google/LG. I used it on the Thunderbolt 3 port on my laptop.
I ordered a new cable, a cheap one, USB-C to USB-A 2.0 and I tried again to flash the device from Soft Bricked with Nexus Root Toolkit and it worked!
This reply is for future people who may have this problem. Looks like Thunderbolt is not always the best move.

Nexus 7 will not start anymore

My problem is that my Nexus 7 will not start anymore. It will still display a startup screen, but then it will not continue. Also, I'm still in the boot loader, but can not flash the Recovery TWRP, because apparently the device is not recognized. Also in the Recovery TWRP I can not start, it will then hang synonymous.
Had actually installed CyanogenMod 14.1 and ran for some time with it
What options do I have left?

JuergenRaab said:
My problem is that my Nexus 7 will not start anymore. It will still display a startup screen, but then it will not continue. Also, I'm still in the boot loader, but can not flash the Recovery TWRP, because apparently the device is not recognized. Also in the Recovery TWRP I can not start, it will then hang synonymous.
Had actually installed CyanogenMod 14.1 and ran for some time with it
What options do I have left?
Click to expand...
Click to collapse
I dont know if it work for you. I'm stuck in bootloader menu when i try to resize the partition... it still does not work for me
but try Nexus Root Toolkit 2.1.9
it work for me. whenever i screw up, i put stock back

flash write failure
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target didn't report max-download-size
sending 'bootloader' (3915 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.780s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
target didn't report max-download-size
sending 'boot' (7422 KB)...
OKAY [ 0.239s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.059s
target didn't report max-download-size
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.017s
target didn't report max-download-size
sending 'recovery' (8166 KB)...
OKAY [ 0.264s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.278s
target didn't report max-download-size
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.017s
Creating filesystem with parameters:
Size: 28521246720
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6963195
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1741488 inodes and 153337/6963195 blocks
target didn't report max-download-size
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.015s
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
target didn't report max-download-size
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.014s
rebooting...
finished. total time: 0.006s

[TWRP] recovery in htc desire 820 dual sim.

I want to insert a custom ROM in HTC Desire 820 dual sim. I have unlocked the bootloader and tried to insert a TWRP recovery. I have tried multiple recoveries namely:
HTC_A51_TWRP_Recovery_3.0.2-0_htcui
HTC_D820_TWRP-Recovery-2.8.7.0-en
HTC_TWRP_Recovery_All
recovery.iso
twrp-3.0.2-0-a32e
twrp-3.1.1-0-a5
twrp-3.2.2-0-a51cml_tuhl
While trying to flash these Unfortunately I Corrupted the OS. The first four of the above TWRP either won't get flashed due to
Code:
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 5736448 is not a multiple of the block size 4096
sending sparse 'recovery' (16382 KB)...
error: write_sparse_skip_chunk: don't care size 5736448 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 5736448 is not a multiple of the block size 4096
OKAY [ 1.673s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.689s
The other 2 flashed but when Executed the command fasboot boot twrp-3.0.2-0-a32e.img or the one with a5 the error is
Code:
downloading 'boot.img'...
OKAY [ 1.356s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.356s
the last didn't give any error but doesn't work either( possibly because its a Desire 830 .img but its the only one not giving the error
the phone is (or was) android 6.0.1
Code:
A51_DTUL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-01.01.010_U10305041_08.01.51015
OS-3.17.720.3
eMMC-boot 2048MB
Apr 11 2016,21:16:51.0
It doesn't have an OEM unlock and I'm pretty much new to recovery and root stuff. Please suggest me how can I root this device too, so I don't fall into further problems. Also my ADB doesn't detect the driver but fastboot does. Please not that all the above mentioned recoveries are for official Htc desire 820 (except the last one) some have been picked up from this site, some by youtube or other forums. Thanks in advance