Database Develop

HowTO if Flash Recovery INFOsignature checking... FAILED (remote: signature verify fa

Hello after my last problem with flash recovery fail...
PROBLEME WITH FASTBOOT : Ex :
Code:
recorvery recovery-RA-nexus-v1.7.0.img
sending 'recorvery' (3954 KB)... OKAY
writing 'recorvery'... INFOsignature checking...
FAILED (remote: signature verify fail)
--------------------------------------------
If you have the same problem :
You need to have the device unlocked
1° Download the last Recovery Image RA-nexus
2° Go to Bootlader : Fastboot
3° cmd for Linux :
Code:
./fastboot boot recovery-RA-nexus-v1.7.0.img
You have booted in recovery but without installing....
4° ADB cmd linux :
Code:
./adb remount
./adb push recovery-RA-nexus-v1.7.0.img /sdcard/recovery-RA-nexus-v1.7.0.img
./adb shell flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.img
Okey you have installed your Recovery customised
Reboot your N1 and Enjoy your new recovery
Adapt cmd for Windows or Mac...

did you try re-downloading it?
and you're sure you spelled recovery right when you typed it in?

My brother got similar errors one time until we realized (I was remote) that his device was plugged into a USB hub. Took out HUB and it worked right away
Thanks for the info to boot the recovery without installing it... pretty neat
thanks

You spelled recovery incorrectly. You had recoRvery. Had you spelled it correctly, you would have been fine.
Good info none-the-less though.

No no i've good spelling : in ADB cmd it's Recovery
;-)

seppi68 said:
Hello after my last problem with flash recovery fail...
PROBLEME WITH FASTBOOT : Ex :
Code:
recorvery recovery-RA-nexus-v1.7.0.img
sending 'recorvery' (3954 KB)... OKAY
writing 'recorvery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
^^^ Not right there you didn't.

Right you have.....
Thx...
I stay here the HowTo because it's a exemple for ADB cmd....

Moved as not Android Development.

Thank you
I have faced the same problem and i have to say that your technique helped a lot solving it so for that Thank you very match.
I just wanted to add for others that when you enter adb remount it will display an error or something like buit don't worry it's ok and it does work just fine.
Thanks again.

[HELP!] I need rom ship HTC ONE M7 Australia ( CID-VODAP021)

I can't find official rom of my HTC One M7 from Vodafone, i search google and I know my CID is VODAP021, can anybody give me an official rom for my HTC One M7. Thank you a lot !
:crying::crying::crying::crying::crying:

No Ruu. Only guru reset file http://www.htc1guru.com/dld/guru_reset_m7_2-24-980-2-zip/
What's the issue?
sent from my mobile device

mikadoofvn said:
I can't find official rom of my HTC One M7 from Vodafone, i search google and I know my CID is VODAP021, can anybody give me an official rom for my HTC One M7. Thank you a lot !
:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/guru_reset_m7_2-24-980-2-zip/
Sent from my HTC One using xda app-developers app

I have downloaded, but run by ADB command error "Fail", I've tried a lot of times, and are in need of an exe file, not the zip file

mikadoofvn said:
I have downloaded, but run by ADB command error "Fail", I've tried a lot of times, and are in need of an exe file, not the zip file
Click to expand...
Click to collapse
There is no ruu.exe for your phone.
Sent from my HTC One using xda app-developers app
---------- Post added at 04:55 AM ---------- Previous post was at 04:53 AM ----------
SaHiLzZ said:
No Ruu. Only guru reset file http://www.htc1guru.com/dld/guru_reset_m7_2-24-980-2-zip/
Click to expand...
Click to collapse
Almost at same time
Sent from my HTC One using xda app-developers app

HTML:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rauvang>cd \Android
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.049s]
finished. total time: 0.049s
C:\Android>fastboot flash zip guru.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1045181 KB)...
OKAY [ 39.588s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 55.879s
C:\Android>

mikadoofvn said:
HTML:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rauvang>cd \Android
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.049s]
finished. total time: 0.049s
C:\Android>fastboot flash zip guru.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1045181 KB)...
OKAY [ 39.588s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 55.879s
C:\Android>
Click to expand...
Click to collapse
This is a guru reset, you have to adb push the zip to /sdcard/ and then install the zip from recovery
Sent from my HTC One using xda app-developers app
---------- Post added at 05:00 AM ---------- Previous post was at 04:59 AM ----------
Go see the video guide on htc1guru.com
Sent from my HTC One using xda app-developers app

alray said:
This is a guru reset, you have to adb push the zip to /sdcard/ and then install the zip from recovery
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Stuck at Bootloader, cannot connect to storage.... how can I put adb file to /sdcard/ :crying:

@alray .. What else can anyone ask for! Multiple people helping out.
@ OP. Unlock bootloader. Flash custom recovery, push file via adb and FLASH!!
sent from my mobile device

SaHiLzZ said:
@alray .. What else can anyone ask for! Multiple people helping out.
@ OP. Unlock bootloader. Flash custom recovery, push file via adb and FLASH!!
sent from my mobile device
Click to expand...
Click to collapse
I have TWRP
How to flash file in TWRP
File zip

SaHiLzZ said:
@alray .. What else can anyone ask for! Multiple people helping out.
@ OP. Unlock bootloader. Flash custom recovery, push file via adb and FLASH!!
sent from my mobile device
Click to expand...
Click to collapse
If OP wants to be completely stock, why unlock bootloader? Let him just use the standard factory reset from the stock recovery right?
Sent from my iPod touch using Tapatalk

mikadoofvn said:
Stuck at Bootloader, cannot connect to storage.... how can I put adb file to /sdcard/ :crying:
Click to expand...
Click to collapse
Yeah, as SaHiLzZ said, you will be able to use adb when booted in cuatom recovery. I recomemd you go with trwp if you havent one installed yet
Sent from my HTC One using xda app-developers app
---------- Post added at 05:11 AM ---------- Previous post was at 05:07 AM ----------
n1234d said:
If OP wants to be completely stock, why unlock bootloader? Let him just use the standard factory reset from the stock recovery right?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I thought he tried before asking how to return stock... Did he?
Sent from my HTC One using xda app-developers app

mikadoofvn said:
I have TWRP
How to flash file in TWRP
File zip
Click to expand...
Click to collapse
Search how to adb push
sent from my mobile device
---------- Post added at 11:15 PM ---------- Previous post was at 11:12 PM ----------
Also. Do NOT FLASH if you have a 1.54+ hboot.
sent from my mobile device

mikadoofvn said:
I have TWRP
How to flash file in TWRP
File zip
Click to expand...
Click to collapse
open a cmd prompt from you adb/fastboot folder of your computer
connect phone to pc and boot in twrp
Code:
adb push name_of_file.zip /sdcard/
then in twrp select install then chose the zip.
and make sure your hboot version is compatible before as sahillz said.
you can see hboot version in bootloader
and btw did you first tried to factory reset ?

alray said:
open a cmd prompt from you adb/fastboot folder of your computer
connect phone to pc and boot in twrp
Code:
adb push name_of_file.zip /sdcard/
then in twrp select install then chose the zip.
and make sure your hboot version is compatible before as sahillz said.
you can see hboot version in bootloader
and btw did you first tried to factory reset ?
Click to expand...
Click to collapse
HTML:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rauvang>cd \Android
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.3-m7.img'
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.073s]
writing 'recovery'...
OKAY [ 0.705s]
finished. total time: 1.779s
C:\Android>adb push Guru_Reset_M7_2.24.980.2 /sdcard/
error: more than one device and emulator
C:\Android>adb push Guru_Reset_M7_2.24.980.2.zip /sdcard/
error: more than one device and emulator
C:\Android>adb push Guru_Reset_M7_2.24.980.2.zip /sdcard/
error: device offline
C:\Android>
I try..... in TWRP and Bootloader

mikadoofvn said:
HTML:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rauvang>cd \Android
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.3-m7.img'
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.073s]
writing 'recovery'...
OKAY [ 0.705s]
finished. total time: 1.779s
C:\Android>adb push Guru_Reset_M7_2.24.980.2 /sdcard/
error: more than one device and emulator
C:\Android>adb push Guru_Reset_M7_2.24.980.2.zip /sdcard/
error: more than one device and emulator
C:\Android>adb push Guru_Reset_M7_2.24.980.2.zip /sdcard/
error: device offline
C:\Android>
I try..... in TWRP and Bootloader
Click to expand...
Click to collapse
what is the output of
Code:
adb devices
when in twrp?
make sure you don't have any other devices connected to your pc and that you don't have an android emulator like ''bluestacks'' or ''windows android'' installed on your computer.
---------- Post added at 05:55 AM ---------- Previous post was at 05:37 AM ----------
if you have multiple devices (or emulator) connected to your computer then use this command:
Code:
adb -s YOUR_PHONE_SERIAL_NUMBER push NAME_OF_FILE.zip /sdcard/

alray said:
what is the output of
Code:
adb devices
when in twrp?
Click to expand...
Click to collapse
HTC is one of my TWRP mode, I've tried adb command to copy the zip file but not, I only connect one device in recovery mode
HTML:

alray said:
what is the output of
Code:
adb devices
when in twrp?
make sure you don't have any other devices connected to your pc and that you don't have an android emulator like ''bluestacks'' or ''windows android'' installed on your computer.
---------- Post added at 05:55 AM ---------- Previous post was at 05:37 AM ----------
if you have multiple devices (or emulator) connected to your computer then use this command:
Code:
adb -s YOUR_PHONE_SERIAL_NUMBER push NAME_OF_FILE.zip /sdcard/
Click to expand...
Click to collapse
HTML:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rauvang>cd \Android
C:\Android>adb devices
List of devices attached
HT34WW904065 offline
HT34WW904065 recovery
C:\Android>adb -s HT34WW904065 push Guru_Reset_M7_2.24.980.2.zip /sdcard/
error: more than one device
C:\Android>

@nkk71.. How goes it! Does 1.54 works with 2.260.x firmware? Any insight for OP?
sent from my mobile device

SaHiLzZ said:
@nkk71.. How goes it! Does 1.54 works with 2.260.x firmware? Any insight for OP?
sent from my mobile device
Click to expand...
Click to collapse
good & yourself, all well i trust.
you mean hboot 1.54 with 2.24.xxx.x firmware? haven't seen any 2.26 firmware. but guru reset should work fine as you guys mentioned to him.
OP, can you post a "fastboot getvar all" (removing IMEI and s/n), and confirm bootloader is unlocked.

[Q] A Unique Problem...:confused:

Hello fellow One users,
I have browsed threw most if not all the HTC One problems on the site and google to try and figure this thing out as i KNOW how people hate Duplicated Threads... Anyways i hope someone can help me with this situation.. Thanks
I received this phone from a friend, ive attached pic showing the state he gave it t me in... According to him he was able to get the phone into Bootmode .. when he gives it to me AFTER TRYING TO RUN A RUU without S-OFF ...
Heres my problem... Basically the phone will not power on, into anything... I try to power on i get this... either a red flashing LED inside the top speaker... or a solid RED led when plugged into the power outlet .... Then ill try to boot into Bootmode and i get this ... Home and Back buttons flashing with no LED on, after the Home and Back buttons flash 10 times i then get a solid red LED , plugged in or not... ive even trying to just charge the device ( I had it charging for a week CONSTANTLY ) no results .. i even try to run a RUU ( for luck i guess ) but no cigar... all i get is an error saying the device has less then 30% battery .. i don't know how it can tell that even tho my PC actually doesn't even see the phone EVER connect.
If anyone can give me ideas and solutions on how to go about fixing this please do as i have tried almost everything. I am very familiar with android and electronics so please don't noob me.
Thank you and i do apologize if i do respond with Noobish questions and the HTC One is a newer device to me.
Thanks
**UPDATE**
Got it to boot into bootloader and it also boots to the HTC screen as shown below.... now i try to run adb commands but the PHONE IS NOT AUTHORIZED...What do i do now??

RED light solid = Not enough battery - at least 30% is required other the security measures will prevent you from flashing RUUs.
Device unauthorized? Try to check and uncheck the USB Debugging option in the device, if possible. If not, you can plug in and out the USB and the device should show up a messagebox to ask you if you authorize the computer, but for that Debugging must be checked AFAIK.
delete the computers adb key: rm /data/misc/adb/adb_key on device
(I have no idea if in case of multiple authorized computers the additional keys are in a new line of the file or if they are in new files. I have only 1 computer.)
stop all adb processes "killall adb" in linuxoids and "taskkill /IM adb.exe" in windows or simply the taskmanager in both.
restart the phone
toggle usb debugging off and on
connect
use adb
click authorize
Click to expand...
Click to collapse
If ADB does not work, you can still use fastboot commands.

davebugyi said:
Try to check and uncheck the USB Debugging option in the device, if possible.
If ADB does not work, you can still use fastboot commands.
Click to expand...
Click to collapse
I can't access the device itself as there is no OS on the device, so I also don't know if I can even get the device authorized...
If Fastboot commands still work, I should be able to flash a rom to the device correct??
Sent from my LG-D801 using XDA Free mobile app

Shotgun4 said:
I can't access the device itself as there is no OS on the device, so I also don't know if I can even get the device authorized...
If Fastboot commands still work, I should be able to flash a rom to the device correct??
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
1- RUU will not work with S-On and UNLOCKED bootloader, with S-On you need to relock bootloader for RUU to work -> but don't do that yet!!
2- for future reference: Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
3- what adb version are you running and what OS do you have
4- start by posting a "fastboot getvar all" (excluding IMEI and s/n) and what do you ultimately want to achieve?

nkk71 said:
3- what adb version are you running and what OS do you have
4- start by posting a "fastboot getvar all" (excluding IMEI and s/n) and what do you ultimately want to achieve?
Click to expand...
Click to collapse
I am running Windows 8 64bit with the latest adb version. also all i have are USB 3.0 ports
and ive tried to run the command "fastboot getvar all" but it just says waiting for device when the device is in fastboot usb mode...

Ok guys, so because i had windows 8.1 and only USB 3.0 Ports i followed this guide to fix the fastboot issue... http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers...
it now connects to fast boot, after running the fastboot command "fastboot getvar all" i get this in return... (refer to pic)
so any ideas how to RETURN THE PHONE TO STOCK
thanks

Shotgun4 said:
Ok guys, so because i had windows 8.1 and only USB 3.0 Ports i followed this guide to fix the fastboot issue... http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers...
it now connects to fast boot, after running the fastboot command "fastboot getvar all" i get this in return... (refer to pic)
so any ideas how to RETURN THE PHONE TO STOCK
thanks
Click to expand...
Click to collapse
1- Win8.1 doesn't play nice with hboot 1.44, so recommend you use a Win7 or Ubuntu Live USB.
2- why don't you just flash a custom recovery and install a custom ROM? because with S-On, you can only get your bootloader to say RELOCKED, not the original LOCKED
And I'll leave this here just in case:
There is a newer RUU for your version here
but I personally would not use it, because you can still achieve S-Off on hboot 1.44

nkk71 said:
1- Win8.1 doesn't play nice with hboot 1.44, so recommend you use a Win7 or Ubuntu Live USB.
2- why don't you just flash a custom recovery and install a custom ROM? because with S-On, you can only get your bootloader to say RELOCKED, not the original LOCKED
And I'll leave this here just in case:
There is a newer RUU for your version here
but I personally would not use it, because you can still achieve S-Off on hboot 1.44
Click to expand...
Click to collapse
Ok, I'll look for a Custom Rom and I'll flash that threw Fastboot.
Thanks
Sent from my LG-D801 using XDA Free mobile app

Shotgun4 said:
Ok, I'll look for a Custom Rom and I'll flash that threw Fastboot.
Thanks
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
1- ROMs are installed using custom recovery. (TWRP 2.6.3.3 or 2.6.3.4 recommended at the moment)
2- do you intend on trying to S-Off your phone?

nkk71 said:
1- ROMs are installed using custom recovery. (TWRP 2.6.3.3 or 2.6.3.4 recommended at the moment)
2- do you intend on trying to S-Off your phone?
Click to expand...
Click to collapse
I have TWRP 2.6.3.4 installed already as the recovery... And I do intend to gain S-Off
Sent from my LG-D801 using XDA Free mobile app

Shotgun4 said:
I have TWRP 2.6.3.4 installed already as the recovery... And I do intend to gain S-Off
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
then install the ROM mentioned here: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and then use revone to get S-Off: http://forum.xda-developers.com/showthread.php?t=2314582

nkk71 said:
then install the ROM mentioned here: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and then use revone to get S-Off: http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
Ok thanks, I'll let you know how things go
Sent from my LG-D801 using XDA Free mobile app

nkk71 said:
then install the ROM mentioned here: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and then use revone to get S-Off: http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
ok sorry for the delay but here are some snaps of the issues im having. Every time try to push something to the device, it gives me "FAILED <remote:not allowed>
then it even says that the bootloader is not unlocked ..how is that if it clearly states in the bootloader menu *** UNLOCKED ***??
Any ideas on how to fix this? if the HTC One only had an SD Card Slot this could be so much easier ...

Shotgun4 said:
ok sorry for the delay but here are some snaps of the issues im having. Every time try to push something to the device, it gives me "FAILED <remote:not allowed>
then it even says that the bootloader is not unlocked ..how is that if it clearly states in the bootloader menu *** UNLOCKED ***??
Any ideas on how to fix this? if the HTC One only had an SD Card Slot this could be so much easier ...
Click to expand...
Click to collapse
hmm , and you want to s-off your device?
are you trying to brick your device in the 20 commands or so you ran (with the exception of fastboot devices), none of them are correct... either mistyped or completely inappropriate.
fastboot commands are not a joke, don't treat them as such, or you will end up bricking your phone. randomly typing fastboot commands is not a good habit.
Now please do some reading and research, but here's some quick info: Your phone has three states
1- bootloader (this is where you use fastboot.exe to flash things appropriate for bootloader mode flashing, such as a custom recovery)
2- recovery (with custom recovery you can use adb.exe commands, and install ROMs)
3- ROM (if you have USB debugging enabled you can also use adb.exe commands here)

nkk71 said:
hmm , and you want to s-off your device?
are you trying to brick your device in the 20 commands or so you ran (with the exception of fastboot devices), none of them are correct... either mistyped or completely inappropriate.
fastboot commands are not a joke, don't treat them as such, or you will end up bricking your phone. randomly typing fastboot commands is not a good habit.
Now please do some reading and research, but here's some quick info: Your phone has three states
1- bootloader (this is where you use fastboot.exe to flash things appropriate for bootloader mode flashing, such as a custom recovery)
2- recovery (with custom recovery you can use adb.exe commands, and install ROMs)
3- ROM (if you have USB debugging enabled you can also use adb.exe commands here)
Click to expand...
Click to collapse
Ok but even if the Command codes are wrong ( I did them at 2am I was so tired) the program Squabbi Toolkit should have worked... Right?
Sent from my LG-D801 using XDA Free mobile app

Shotgun4 said:
Ok but even if the Command codes are wrong ( I did them at 2am I was so tired) the program Squabbi Toolkit should have worked... Right?
Click to expand...
Click to collapse
Wrong.
you use fastboot to flash
* recoveries
* erase cache
* ruu.zip packages
* firmware.zip packages
you use a custom recovery (such as TWRP 2.6.3.3), to install a <name of ROM>.zip
you cannot "fastboot flash ..." a custom ROM.ZIP.
PS: I seriously recommend you don't do these commands at 2am when you're tired, that could end badly

nkk71 said:
Wrong.
you use fastboot to flash
* recoveries
* erase cache
* ruu.zip packages
* firmware.zip packages
you use a custom recovery (such as TWRP 2.6.3.3), to install a .zip
you cannot "fastboot flash ..." a custom ROM.ZIP.
PS: I seriously recommend you don't do these commands at 2am when you're tired, that could end badly
Click to expand...
Click to collapse
Ok so what I want to do is...
1. Upload the ROM you previously posted to my device via Fastboot
2. Gain S-Off using revon
My issue is what proper command I use to load the rom to my device for flashing threw the recovery??
I can access the Bootloader, Fastboot and Recovery.
ADB will not work, not sure why...
In Recovery I can not mount the storage, as I would on my LG to load the zip file to storage and flash threw recovery...
Sent from my LG-D801 using XDA Free mobile app
**Update**
So I found this in a guide...
""Alternatively you can flash through Fastboot. Download the ROM and place it in the platform-tools folder.
To start flashing, type fastboot update [romfile.zip].
This will take a few minutes to complete, so do not touch the device while it is working. ""

Shotgun4 said:
Ok so what I want to do is...
1. Upload the ROM you previously posted to my device via Fastboot
2. Gain S-Off using revon
My issue is what proper command I use to load the rom to my device for flashing threw the recovery??
I can access the Bootloader, Fastboot and Recovery.
ADB will not work, not sure why...
In Recovery I can not mount the storage, as I would on my LG to load the zip file to storage and flash threw recovery...
Sent from my LG-D801 using XDA Free mobile app
**Update**
So I found this in a guide...
""Alternatively you can flash through Fastboot. Download the ROM and place it in the platform-tools folder.
To start flashing, type fastboot update [romfile.zip].
This will take a few minutes to complete, so do not touch the device while it is working. ""
Click to expand...
Click to collapse
Search more next time.
If I had a nickel for every time I post this
adb/fastboot files for Windows: http://www.androidfilehost.com/?fid=23329332407585867
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
then you can either:
1- OTG cable
2- adb push <name of rom>.zip /sdcard/
3- initiate sideload in custom recovery, then adb sideload <name of rom>.zip
adb push example:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
if you're having problems with PC seeing your phone, check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

nkk71 said:
Search more next time.
If I had a nickel for every time I post this
adb/fastboot files for Windows: http://www.androidfilehost.com/?fid=23329332407585867
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY
then you can either:
1- OTG cable
2- adb push <name of rom>.zip /sdcard/
3- initiate sideload in custom recovery, then adb sideload <name of rom>.zip
adb push example:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
if you're having problems with PC seeing your phone, check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
Finally after 6 hours of sitting at my laptop, browsing the internet for answers ... it was so simple ...
1. adb wasnt working because when the device was connected in recover mode, Windows 8 had installed the "My HTC" drive ... To fix it all i did was uninstall that driver "My HTC".. refresh Device Manager and look under "unknown Devices" ... and install the Samasung OEM adb device driver in its place ...BOOM working adb!?
Next i followed your steps to push the rom via adb and it finished successful.
C:\Users\Peter\Android>adb devices
List of devices attached
FAXXXXXXXXXX recovery
C:\Users\Peter\Android>adb push rom.zip /sdcard/
4739 KB/s (1017950778 bytes in 209.742s)
C:\Users\Peter\Android>adb shell md5sum /sdcard/rom.zip
06c863ce41b0d5001290737a31e198a1 /sdcard/rom.zip
C:\Users\Peter\Android>
3. i check the "md5sum" and got "06c863ce41b0d5001290737a31e198a1" ... File i pushed was Android_Revolution_HD-One_9.4...
4. Flashed and device is now working perfectly :victory:
Thank You so much and for being so patient with me aha ... you deserve a thanks and a donation for all your help :highfive:
Also gained S-Off using Revon

HELP - BRICKED One!

I was flashing a new rom onto my HTC One today and my daughter got hold of it (Age 3) whilst my back was turned and has wiped the ROM completely!
I have TWRP v2.7.1.1 touch bootloader but I cant get a ROM installed - fastboot won't recognise that there is a device attached even though I get the 'connected sound' when I connect to my windows 8 laptop. I have searched for all the fastboot and adb solutions but have come to a dead end!
I think its dead! :crying:
Fastboot usb shows on the phone screen when connected though
the OS - on the fastboot screen shows blank too!
*** TAMPERED ***
*** RELOCKED ***
M7_ PVT SHIP S_ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 21 2013,22:50:54.0
Can anyone help?

lol if you have a working recovery then your device is not bricked. Even if your recovery is broken if you can access the bootloader your device is still fine.
It sounds to me like you are having some trouble with the windows drivers.. if you have a pc with linux I would try it there as it is easier. or if you only have win8 then you have to install these drivers http://forum.xda-developers.com/showthread.php?t=2544146
btw what problem do you have when installing the rom via recovery?

cuyo11 said:
lol if you have a working recovery then your device is not bricked. Even if your recovery is broken if you can access the bootloader your device is still fine.
It sounds to me like you are having some trouble with the windows drivers.. if you have a pc with linux I would try it there as it is easier. or if you only have win8 then you have to install these drivers http://forum.xda-developers.com/showthread.php?t=2544146
btw what problem do you have when installing the rom via recovery?
Click to expand...
Click to collapse
"C:\android-tools>fastboot devices
HT34PW913345 fastboot"​
CID = HTC__001
I can attempt to flash a .zip rom (same recovery number = stock 5.11.401.10) but it fails!
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 43.432s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 179.412s​
I cant flash a different recovery anymore I presume as my bootloader is "RELOCKED" and I can't work out how to unlock it. HTCDev can't unlock it.
C:\android-tools>fastboot flash recovery recovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.187s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.141s​
What is "bootloader signature checking"? How do I resolve that problem of FAILED?
I can access the RUU screen successfully
[INDENTC:\android-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.187s]
finished. total time: 0.234s][/INDENT]
but when I try to flash a .zip it doesn't work still
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 44.000s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 159.127s​
Anyone have any ideas of how to get the signature checking to work?

I have managed to unlock again using my Unlock_code.bin file but it still fails to load the .zip ROM
C:\android-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.172s
C:\android-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.172s
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 43.874s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.203s​

I have now managed to load ClockworkMod Recovery v6.0.4.6
I have found I can't mount the /sdcard
I guess that's where my problem lies? If my phone has forgotten how to find /sdcard then how can it flash to it?

targett said:
I have now managed to load ClockworkMod Recovery v6.0.4.6
I have found I can't mount the /sdcard
I guess that's where my problem lies? If my phone has forgotten how to find /sdcard then how can it flash to it?
Click to expand...
Click to collapse
Check this http://forum.xda-developers.com/showthread.php?t=2228274&page=3
then let me know if you have any questions.

nkk71 said:
Check this http://forum.xda-developers.com/showthread.php?t=2228274&page=3
then let me know if you have any questions.
Click to expand...
Click to collapse
I have wiped the system and cache just in case and am attempting the sideload but when i do the "adb devices" it doesn't sow my device number, where it does if in fastboot.
G:\adb>adb devices
List of devices attached
​
And when I attempt at adb sideload I get this
G:\adb>adb sideload One_5.11.401.10_odexed.zip
error: device not found​Stuck again :crying:
Oh - How important is the USB OTG in the adb sideload

targett said:
I have wiped the system and cache just in case and am attempting the sideload but when i do the "adb devices" it doesn't sow my device number, where it does if in fastboot.
Stuck again:crying:
Click to expand...
Click to collapse
it is mentioned in the post, but here again: FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

nkk71 said:
it is mentioned in the post, but here again: FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
Sorry for being so stupid! I feel like a noob on this device (not flashed or rooted in about 3 years!)
Reading it all again I see I need S-Off. My Security is ON. and I can't turn it off as I can't install SuperSU or Superuser or anything at all.
Any thoughts?

targett said:
Sorry for being so stupid! I feel like a noob on this device (not flashed or rooted in about 3 years!)
Reading it all again I see I need S-Off. My Security is ON. and I can't turn it off as I can't install SuperSU or Superuser or anything at all.
Any thoughts?
Click to expand...
Click to collapse
sorry, i don't follow. it has nothing to do with s-on or s-off.
you say your device isn't being seen while in custom recovery, but it has to show somewhere in device manager, no? if yes, then you may need to manually select the correct drivers, that's it

nkk71 said:
sorry, i don't follow. it has nothing to do with s-on or s-off.
you say your device isn't being seen while in custom recovery, but it has to show somewhere in device manager, no? if yes, then you may need to manually select the correct drivers, that's it
Click to expand...
Click to collapse
Sorry!
I have sorted the Win8 driver issue - Hadn't spotted that one.
I have now managed to adb push the .zip file and adb sideload it too.
I'm now installing the 'sideload.zip' Wish me luck!
Wordked! It F#*king WORKED!!!!!
Thank you, thank you, thank you!

targett said:
Sorry!
I have sorted the Win8 driver issue - Hadn't spotted that one.
I have now managed to adb push the .zip file and adb sideload it too.
I'm now installing the 'sideload.zip' Wish me luck!
Wordked! It F#*king WORKED!!!!!
Thank you, thank you, thank you!
Click to expand...
Click to collapse
Good Luck :good: :good:

Stock Recovery 4.20.651.10

I am looking to download the stock recovery for version 4.20.651.10.
I've found the zip of all previous recoveries here: http://forum.xda-developers.com/showpost.php?p=56557802&postcount=84
Is there a place I can download the stock recovery for 4.20.651.10. I need that recovery so I can download the update just released, 4.25.651.14 as I run stock with root and my current recovery is TWRP. The older recoveries are not allowing the update to run.

ReproOne said:
I am looking to download the stock recovery for version 4.20.651.10.
I've found the zip of all previous recoveries here: http://forum.xda-developers.com/showpost.php?p=56557802&postcount=84
Is there a place I can download the stock recovery for 4.20.651.10. I need that recovery so I can download the update just released, 4.25.651.14 as I run stock with root and my current recovery is TWRP. The older recoveries are not allowing the update to run.
Click to expand...
Click to collapse
I extracted the recovery from 4.25.651.14 and flashed it. The update applied, but upon final restart it locked up and currently it will not start. I can force it to reboot, I get the startup screen for a few seconds, then it goes to a blank screen.
Any ideas?

ReproOne said:
I extracted the recovery from 4.25.651.14 and flashed it. The update applied, but upon final restart it locked up and currently it will not start. I can force it to reboot, I get the startup screen for a few seconds, then it goes to a blank screen.
Any ideas?
Click to expand...
Click to collapse
Either flash a custom recovery again from fastboot or RUU. Are you still unlocked bootloader? If not and you modified any system files, that would be why it will not boot.
Unlock your bootloader and it might boot with stock recovery. Otherwise RUU is the way to go, then you can take the OTA, unlock the boot, install custom recovery and root and do whatever you want from there.
Also, stock recovery is not required for RUU but you must lock the bootloader if you are s-on, not sure about s-off but if youi are and try, if it fails just lock it and try again.

dopy25 said:
Either flash a custom recovery again from fastboot or RUU. Are you still unlocked bootloader? If not and you modified any system files, that would be why it will not boot.
Unlock your bootloader and it might boot with stock recovery. Otherwise RUU is the way to go, then you can take the OTA, unlock the boot, install custom recovery and root and do whatever you want from there.
Also, stock recovery is not required for RUU but you must lock the bootloader if you are s-on, not sure about s-off but if youi are and try, if it fails just lock it and try again.
Click to expand...
Click to collapse
It will not boot to fastboot, just the splash screen then blank. Is there a way around this?

ReproOne said:
It will not boot to fastboot, just the splash screen then blank. Is there a way around this?
Click to expand...
Click to collapse
Have you tried to boot into the bootloader and then using the volume keys to navigate to "fastboot" and pressing power?
S-ON or S-OFF? If you are S-ON you should have the super security still and would have almost no possibility of a brick and should still be able to boot into the bootloader, if you can at least get there you are still in a (semi) working device and only takes a few things to do to get back to fully functional.

dopy25 said:
Have you tried to boot into the bootloader and then using the volume keys to navigate to "fastboot" and pressing power?
S-ON or S-OFF? If you are S-ON you should have the super security still and would have almost no possibility of a brick and should still be able to boot into the bootloader, if you can at least get there you are still in a (semi) working device and only takes a few things to do to get back to fully functional.
Click to expand...
Click to collapse
I am s-on, it is only HTC unlocked so I can have root access. So far, I cannot get it to boot to the boot loader via power and volume down.

ReproOne said:
I am s-on, it is only HTC unlocked so I can have root access. So far, I cannot get it to boot to the boot loader via power and volume down.
Click to expand...
Click to collapse
That's odd, all you did was unlock using HTC dev?
Are you charged to enough battery power? That could be a huge factor.

dopy25 said:
That's odd, all you did was unlock using HTC dev?
Are you charged to enough battery power? That could be a huge factor.
Click to expand...
Click to collapse
Yes unlock with HTCDev and then root. Phone charge 91%.

To get to the bootloader while having a bootloop : Hold Power + VolUp + VolDown until screen turns off. Then ... IMMEDIATELY release Power and volume UP, and keep hold of volume Down.

ReproOne said:
I am s-on, it is only HTC unlocked so I can have root access. So far, I cannot get it to boot to the boot loader via power and volume down.
Click to expand...
Click to collapse
Fastboot reboot-bootloader
From your PC...just throwing it out there it might work.
BTW I have only seen the HK firmware posted 4.25.654.14 but I wouldn't think it would flash at all since you are s-on.

BD619 said:
Fastboot reboot-bootloader
From your PC...just throwing it out there it might work.
BTW I have only seen the HK firmware posted 4.25.654.14 but I wouldn't think it would flash at all since you are s-on.
Click to expand...
Click to collapse
I can now get it to the recovery screen, so what can I do from adb to possibly redo the update?

ReproOne said:
I can now get it to the recovery screen, so what can I do from adb to possibly redo the update?
Click to expand...
Click to collapse
You will have to wait for someone to upload the non HK firmware...I'm in the process of pulling the OTA and pulling the firmware right now.
I'll post a link when I'm done.

BD619 said:
You will have to wait for someone to upload the non HK firmware...I'm in the process of pulling the OTA and pulling the firmware right now.
I'll post a link when I'm done.
Click to expand...
Click to collapse
I will wait for your reply. I did find this, but it fails:
http://forum.xda-developers.com/showthread.php?t=2729173

ReproOne said:
I will wait for your reply. I did find this, but it fails:
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
Fails how?

BD619 said:
Fails how?
Click to expand...
Click to collapse
I downloaded "0P6BIMG_Sprint_HTC_One_M8_4.20.651.10_RUU.zip" and renamed to 0P6BIMG.ZIP to my computer (not sdcard)
I then did the following:
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.ZIP
and I get this...
target reported max download size of 1826418688 bytes
sending 'zip' (1502254 KB)...
OKAY [ 48.930s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 51.090s
If I run the flash zip a second time it gives this...
target reported max download size of 1504755712 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 33557229 is not a multiple of th
e block size 4096
sending sparse 'zip' (1469484 KB)...
error: write_sparse_skip_chunk: don't care size 33557229 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 33557229 is not a multiple of th
e block size 4096
OKAY [ 49.480s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 49.620s

ReproOne said:
I downloaded "0P6BIMG_Sprint_HTC_One_M8_4.20.651.10_RUU.zip" and renamed to 0P6BIMG.ZIP to my computer (not sdcard)
I then did the following:
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.ZIP
and I get this...
target reported max download size of 1826418688 bytes
sending 'zip' (1502254 KB)...
OKAY [ 48.930s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 51.090s
If I run the flash zip a second time it gives this...
target reported max download size of 1504755712 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 33557229 is not a multiple of th
e block size 4096
sending sparse 'zip' (1469484 KB)...
error: write_sparse_skip_chunk: don't care size 33557229 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 33557229 is not a multiple of th
e block size 4096
OKAY [ 49.480s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 49.620s
Click to expand...
Click to collapse
You have to be S-OFF I believe to use that method.
Here is the Full Firmware 4.25.651.14
https://www.androidfilehost.com/?fid=95916177934552553
Use these instructions
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot

I would relock bootloader run 4.20 ruu take 4.25 ota then unlock bootloader flash twrp then root.
Sent from 27.5244° N, 99.4906° W

BD619 said:
You have to be S-OFF I believe to use that method.
Here is the Full Firmware 4.25.651.14
https://www.androidfilehost.com/?fid=95916177934552553
Use these instructions
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Click to expand...
Click to collapse
The file does not appear to be there, possibly still uploading?

ReproOne said:
The file does not appear to be there, possibly still uploading?
Click to expand...
Click to collapse
My bad I deleted it lol I will upload again

BD619 said:
My bad I deleted it lol I will upload again
Click to expand...
Click to collapse
Thanks. Can't give you a hard time as you are helping me!
Waiting for upload...