I've been trying to flash a stock recovery or CWM Touch onto my HTC One using fastboot.exe that came with the latest version of ADK.
This is what happened:
sending 'recovery' (9480 KB)...
OKAY [ 1.096s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.630s
Please help. I've looked upon at least 30 websites, including xda-developers.Thanks!
Why don't you just flash it through the app? Or flash twrp through goo manager. It's also touch based.
mr_verystock said:
I've been trying to flash a stock recovery or CWM Touch onto my HTC One using fastboot.exe that came with the latest version of ADK.
This is what happened:
sending 'recovery' (9480 KB)...
OKAY [ 1.096s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.630s
Please help. I've looked upon at least 30 websites, including xda-developers.Thanks!
Click to expand...
Click to collapse
Redownload the image.
mr_verystock said:
I've been trying to flash a stock recovery or CWM Touch onto my HTC One using fastboot.exe that came with the latest version of ADK.
This is what happened:
sending 'recovery' (9480 KB)...
OKAY [ 1.096s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.630s
Please help. I've looked upon at least 30 websites, including xda-developers.Thanks!
Click to expand...
Click to collapse
It sounds like your bootloader is still locked. Unlock it through htcdev before trying to fastboot flash recovery.
Sent from my HTC One S using Tapatalk 2
I’ve tried two JB roms, Jellytime and CM10 by nk111, but both are freezing at the white HTC screen. Yes, I’m htc unlocked, and I’ve flashed the boot.img both before and after flashing the rom, formatted partitions etc, all without success. I originally posted this in the Jellytime forum as I thought it might be a rom issue but now it seems like a JB issue, particularly as I’ve since flashed Primo ICS rom, then the boot, and everything is as it should be.
It’s as if the JB boot flash isn’t ‘sticking’, yet the Primo boot flashes okay which is confirmed by the kernel description in settings. If it matters, I'm coming from Fallout with amidabuddha’s latest kernel, hboot is 2.02.0002.
Hope someone can help out as I’m itching to try JB..
it's possible you have a none Sony panel, try using the 82n kernel with cm10
sent from the thing I stab with my finger when I get two minutes
I think you may be right - the dmesg is 'saga panel unblank' - but how to flash the 82n from goo.im? I understand that the kernel zip needs to be flashed in recovery to update the modules, but it contains a zImage rather than a boot.img to fastboot flash.
If this is the case, for moral support check out
http://forum.xda-developers.com/showthread.php?t=1943524
[OFF-TOPIC] Non-Sony screen panel DS users lounge
Sywepd form my DsereiS
Please help me cannot support job 4.1.2
Sent from my HTC Saga using xda premium
frozen on bootscreen
Hi Guys,
after unlocking my Desire S (S-ON) and flashing CM 10.1, i am stuck on the white screen with the green htc logo.
This was first time i ever done this on my desire s. I also send the boot.img to the device (see below) via Windows 8 and it said it worked properly:
c:\Android>fastboot devices
SH1BVTJ01122 fastboot
c:\Android>fastboot flash boot boot.img
sending 'boot' (3390 KB)...
OKAY [ 1.063s]
writing 'boot'...
OKAY [ 1.198s]
finished. total time: 2.261s
c:\Android>fastboot devices
SH1BVTJ01122 fastboot
c:\Android>fastboot flash boot boot.img
sending 'boot' (3522 KB)...
OKAY [ 1.159s]
writing 'boot'...
OKAY [ 1.385s]
finished. total time: 2.545s
c:\Android>fastboot reboot
rebooting...
finished. total time: 0.300s
So, what's the problem over here?
schafholt said:
Hi Guys,
after unlocking my Desire S (S-ON) and flashing CM 10.1, i am stuck on the white screen with the green htc logo.
This was first time i ever done this on my desire s. I also send the boot.img to the device (see below) via Windows 8 and it said it worked properly:
c:\Android>fastboot devices
SH1BVTJ01122 fastboot
c:\Android>fastboot flash boot boot.img
sending 'boot' (3390 KB)...
OKAY [ 1.063s]
writing 'boot'...
OKAY [ 1.198s]
finished. total time: 2.261s
c:\Android>fastboot devices
SH1BVTJ01122 fastboot
c:\Android>fastboot flash boot boot.img
sending 'boot' (3522 KB)...
OKAY [ 1.159s]
writing 'boot'...
OKAY [ 1.385s]
finished. total time: 2.545s
c:\Android>fastboot reboot
rebooting...
finished. total time: 0.300s
So, what's the problem over here?
Click to expand...
Click to collapse
Check the thread posted 2 posts above yours
teadrinker said:
Check the thread posted 2 posts above yours
Click to expand...
Click to collapse
thanks.
Hopefully working (but not on my device) CM 10.1 Build 16: http://forum.xda-developers.com/showpost.php?p=42472233&postcount=2640
i was trying to flash recovery after i s-off my htc sensation hboot 1.27
i put in command C:\android\android-sdk-windows\sdk\platform-tools>fastboot flash recovery recovery-clockwork-touch-5.8.0.9-pyramid.img
and C:\android\android-sdk-windows\sdk\tools>fastboot flash recovery recovery-clockw
ork-touch-5.8.0.9-pyramid.img
sending 'recovery' (4876 KB)... OKAY [ 1.254s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.571sC:\android\android-sdk-windows\sdk\tools>fastboot flash recovery recovery-clockw
ork-touch-5.8.0.9-pyramid.img
sending 'recovery' (4876 KB)... OKAY [ 1.254s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.571s
i get this error all files are there and is very frustrating as ive researched all over the internet and cant find a solution
hydroponics said:
i was trying to flash recovery after i s-off my htc sensation hboot 1.27
i put in command C:\android\android-sdk-windows\sdk\platform-tools>fastboot flash recovery recovery-clockwork-touch-5.8.0.9-pyramid.img
and C:\android\android-sdk-windows\sdk\tools>fastboot flash recovery recovery-clockw
ork-touch-5.8.0.9-pyramid.img
sending 'recovery' (4876 KB)... OKAY [ 1.254s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.571sC:\android\android-sdk-windows\sdk\tools>fastboot flash recovery recovery-clockw
ork-touch-5.8.0.9-pyramid.img
sending 'recovery' (4876 KB)... OKAY [ 1.254s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.571s
i get this error all files are there and is very frustrating as ive researched all over the internet and cant find a solution
Click to expand...
Click to collapse
Your hboot is still locked.. Until that status is changed you can't use fastboot commands..
Flash juopunutbear hboot or revolutionary hboot
Check firmware thread by kohr-ah in sensation development section... There is a patched hboot zip there (at the end I think).. First flash that and then continue the rest
Sent from my HTC Sensation using xda premium
ganeshp said:
Your hboot is still locked.. Until that status is changed you can't use fastboot commands..
Flash juopunutbear hboot or revolutionary hboot
Check firmware thread by kohr-ah in sensation development section... There is a patched hboot zip there (at the end I think).. First flash that and then continue the rest
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
u unlocked to s-off then its locked again so do i have to unlock again?
Yes mate ull hve to unlock ur bootloader as fastboot commands nly work on unlocked bootloader
Hit the thanx button if I hve helped you
A friend brought a HTC One Mini in a very unusual situation to me. The phone bootloader is "Locked" and "S-ON". It only boots to fastboot usb mode only. The battery is still ok because I checked with a script that is used to charge in that mode when the battery is low; at least it still has about 3870mV, and the minimum is around 3680mV. The problem is that:
1. When I try to unlock so I can flash a custom TWRP recovery the unlock spalsh screen does not appear, although the unlock command says sucessful.
C:\fastboot-win>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.161s
Click to expand...
Click to collapse
2. I downloaded this stock file OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip because it matches the OS version showing on the fastboot screen on the phone. When I try to flash it from fastboot I get this error:
C:\fastboot-win>fastboot flash zip OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip
sending 'zip' (346477 KB)...
OKAY [ 16.826s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 49.466s
Click to expand...
Click to collapse
Can anyone please render any help? I can follow any instructions to the letter, just that I have never come across this kind of issue before.
Thanks in advance.
It has taken a long since I tried to root my ZTE kis Q with no success. FramaRoot didn't work, so I tried adb and fastboot. However I think the recovery image from Clockworkmod is no working with my ZTE version, because it refuses to install it when I make
fastboot flash recovery recovery-clockwork-5.0.2.0-blade.img I get
> sending 'recovery' (3768 KB)... OKAY [ 0.142s]
writing 'recovery'...
FAILED (remote: partition 'recovery' not support flash )
finished. total time: 0.155s
Since I'm using linux I don't have drivers issues
Does anyone have an opinion about it.
Thanks