Develop Bugs

[Q] Failed ROM flash and lost recovery image, stuck at HTC boot

I really hope anyone can help me
atleast maybe just pointing me to the right guides or info would be really appreciated.
after flashing leedroid it said installation from sd card completed and i was back in recovery menu (rom manager 2.0.1.5) but when i pressed back btn i think it crashed, nothing more happend (i.e. i never got the reboot now menu option) so i took out the battery. Now it won't boot, stuck at white/green HTC logo.
When i go inte to recovery, instead of the clockworkmod custom recoveryscreen it's (blue text) Android system recovery 2e and i get error E:Can't open /cache/recovery/command and E:Can't open /data/data/recovery/log
I have working nandroid (via rom manger) backup that i would like to restore.
As i said help/pointers would be very appreciated. Maybe i can simply apply fake flash image again and try a different ROM? i just don't want to mess up the phone any more then i have already have
Desire 0.80 with latest radio

I had that last night, what I did was to re-root my phone then did a recovery from a backup I had.
Sent from my HTC Desire using XDA App

ribbox said:
I had that last night, what I did was to re-root my phone then did a recovery from a backup I had.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Thanks! what root method did you use? MoDaCo r6 riskfreeroot?

SOLVED
So i managed to solve this.
as i hadn't lost root i could simply copy fake flash update.zip and follow the fake flash instructions @ modaco here
so in recovery i ran update.zip which loaded the custom rom and allowed me to run a nandroid recovery
now Bob's my uncle

[Q] E:signature verification failed ClockWorkMod

Hi Guys
been searching for hours for a solution but can't find anything.
Installed Lambros Rom - all fine. I've booted into recovery to put my old rom on and I get the following error:
E: Can't Open/cache/recovery/command
--Install from sdcard--
Finding update package
Opening update package
Verifying update package
E:signature verification failed
Installation aborted.
So i've reformatted the card, wiped the phone cache and tried several different rom and I get the same error. Using ClockWorkMod recovery and rom manager.
Can anyone help? Is this a common error?
Bootloader 0.80
Baseband 32.42.00.32U_5.09.00.20

I dont know very well but it can be about S-on-off issue

Try disabling verification in clockwork. From memory I think its under the advanced option. It says toggle verification. Hope this helps
Sent from my HTC Desire using XDA App

It is the signature verification but to toggle it you need to (in recovery) go to 'install update from zip' and there should be the option to toggle it.

I have the same problem. My question is whether there is anything I can do to avoid this problem the next time I upgrade to a newer version of leedroid?
BTW my HTC Desire was unrooted using the unrevoked method and I'm currently running leedroid 2.2f.
Thanks in anticipation.
Sent from my HTC Desire using Tapatalk

I still have bootloader 0.80 - this sort of indicates I didn't upgrade to the OTA 2.2 can someone back me up on this?
If I unroot my phone to 2.1 using a gold card and then re-root do you think this will work?

TheGhost1233 said:
It is the signature verification but to toggle it you need to (in recovery) go to 'install update from zip' and there should be the option to toggle it.
Click to expand...
Click to collapse
^ This.
All you have to do is go into recovery, install zip file from sd, and toggle the signature verification. This has happened to me a few times; I just simply toggled it, and the ROM flashed perfectly.

sorry for ressurecting, but i have a similar problem.
wanted to install a custom rom and for some reason it failed und bricked my phone.
i boot into fastboot, but every time i want to flash a new rom, it says "signatur verfication failed" and i do not have the option to toggle it off.
hboot 0.80

Niteruner said:
sorry for ressurecting, but i have a similar problem.
wanted to install a custom rom and for some reason it failed und bricked my phone.
i boot into fastboot, but every time i want to flash a new rom, it says "signatur verfication failed" and i do not have the option to toggle it off.
hboot 0.80
Click to expand...
Click to collapse
You need to be in recovery, not in fastboot.
Are you even rooted and have a custom recovery image?
Sent from my HTC Desire using XDA App

Niteruner said:
sorry for ressurecting, but i have a similar problem.
wanted to install a custom rom and for some reason it failed und bricked my phone.
i boot into fastboot, but every time i want to flash a new rom, it says "signatur verfication failed" and i do not have the option to toggle it off.
hboot 0.80
Click to expand...
Click to collapse
You need a fake flash recovery image.
AmonRa version can be found here - http://forum.xda-developers.com/showthread.php?t=689778
download it, place it on SD card. Boot into fast boot, chose run update.zip and it will boot in to the fake flash this is where you get all the option you need.
Get back to me if you have an trouble.

chribonn said:
I have the same problem. My question is whether there is anything I can do to avoid this problem the next time I upgrade to a newer version of leedroid?
BTW my HTC Desire was unrooted using the unrevoked method and I'm currently running leedroid 2.2f.
Thanks in anticipation.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
I have exalty the same problem as you. I have been looking all over the place for a tutorial I could follow. I even downloaded a zip signer and tried to sign the update.zip file I downloaded from the leedroid thread on xda. It did not work.

From what I understand from the above:
You have the exact problem as you
​

I think if you're on the leaked 2.2 rom you won't be able to use clockwork recovery successfully. You'll have to downgrade to 2.1, root, install clockwork recovery and then install the rom.
That's what worked for me.

Install Clockwork recovery.
Then boot into recovery (after a nandroid backup) and toggle off verification.
Then you won't get the error when you apply the update.zip. You must do this in recovery.
Toggle off verification in Clockwork recovery:
http://jaxov.com/2010/10/fix-android-no-signature-verification-failed-error/
Cheers!

I've read all these posts, but my phone refuses to show me the clockwork recovery menu.. no matter what I do, I always get the android system recovery menu..
Please help..
Also, I cant get my phone into recovery/download mode using the 3 button combo. I've tried every possible combination, but the only way I can get to the default 'android' recovery menu is by using the ROM Manager app.
Galaxy: GT i9000
Baseband: i9000DDjP2
Kernel: 2.6.32.9 [email protected]#1
Build: FROYO.DDjP6

Hey guys, if you're still having this 'Signature Verification Failed" nonsense and Clockwork Mod is not letting you flash anything, check this thread (on the third page, my post tells you the fix), I just solved my own issue
http://forum.xda-developers.com/showthread.php?t=944426&page=3
Good luck, post back if you have questions/comments, I'll check back and hopefully find you solved your problems as I have
Cheers

just try flashing clockwork mod

I am having the same exact issues. But i have found a workaround that is working for me.
When presented with the error, i go to the "Advanced" menu and select "Reboot recovery". After rebooting, on my phone, the process will start as desired

by me the same problem, it always comes E: signatur verification failed

So turn off signature verification in recovery. Should be in "Advanced".

[Q] Updating Cyanogenmod recovery problem

To prevent Terepin getting his knickers in a twist, reposted here.
================================================
Hi there,
Currently have cyanogenmod recovery 2.5.0.1 and want to upgrade to the latest (5.0.0.?)
Have tried doing this via ROM Manager, but it simply says it's installed and reports the latest version number, but when I restart in recovery it's still displaying the old version (and has none of the new features, i.e. - it hasn't updated at all)
I've read some guides on forcing ROM Manager to install newer or different .img's, but I can't even see any .img's it's downloaded. Are the downloads just failing?
Any help would be really appreciated!
Thanks in advance!

Download recovery image and flash it via fastboot:
fastboot flash recovery /path/to/<recovery>.img
fastboot reboot

I noticed this same thing this morning, from some googling it seems if you are s-on that ROM manager can't flash the recovery image. Either go s off or use fast boot, i will be using fast boot.
Sent from my HTC Desire using XDA App

Having done some more googling myself I have found out that I have s-on. Am guessing that's related. Not sure why as I initially rooted using unrevoked.
Is it wise to re-root, or at least run the latest unrevoked and allow it to install cyanogenmod recovery at the same time? Am I correct in thinking that this will turn s-off too?
Thanks for the help!

[Q] Weird bootloop issue

Alright, so I dun goofed. If some kind soul could help me with this, or just point me in the right direction.
How I dun goofed:
I used the All-In-One Toolkit to unlock bootloader and flash a custom recovery. After that I pulled the boot.img out of the PrimoC CM10 rom and used the toolkit to flash that as the kernel (I realize now this was extremely stupid).
Symptoms:
Cyanogen loading screen comes up and just hangs there. When hboot runs it says "SD checking...Loading...[PK76DIAG.zip] No image! Loading [PK67DIAG.nbh] No image! etc etc etc" eventually, though, I can access the bootloader and from there, the recovery. But when I try to restore my original set up and then reboot the stock Virgin Mobile rom does the same thing and just hangs on the HTC loading screen.
Details:
-Virgin Mobile (CDMA)
-bootloader unlocked, custom recovery (TWRP v2.2.0)
I've tried everything I can think of. I've used the recovery's restore feature, I've tried to reflash a different kernel. Nothing
Any help would be greatly appreciated. Thanks.

Try cm9 ROM and try to flash the ICS boot.img cm10 causes weird problems sometimes
Sent from my One V using xda app-developers app

basalate said:
Alright, so I dun goofed. If some kind soul could help me with this, or just point me in the right direction.
How I dun goofed:
I used the All-In-One Toolkit to unlock bootloader and flash a custom recovery. After that I pulled the boot.img out of the PrimoC CM10 rom and used the toolkit to flash that as the kernel (I realize now this was extremely stupid).
Symptoms:
Cyanogen loading screen comes up and just hangs there. When hboot runs it says "SD checking...Loading...[PK76DIAG.zip] No image! Loading [PK67DIAG.nbh] No image! etc etc etc" eventually, though, I can access the bootloader and from there, the recovery. But when I try to restore my original set up and then reboot the stock Virgin Mobile rom does the same thing and just hangs on the HTC loading screen.
Details:
-Virgin Mobile (CDMA)
-bootloader unlocked, custom recovery (TWRP v2.2.0)
I've tried everything I can think of. I've used the recovery's restore feature, I've tried to reflash a different kernel. Nothing
Any help would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
ok do the following
go to the fast boot menu
recovery
factory reset
wipe cache/dalvik cache
go here
http://forum.xda-developers.com/showthread.php?t=1878994
download the ROM
download boot.img
first flash the boot img in command prompt
then don't restart
go to recovery and flash the ROM
now restart
PM me if problem persists

cybervibin said:
ok do the following
go to the fast boot menu
recovery
factory reset
wipe cache/dalvik cache
go here
http://forum.xda-developers.com/showthread.php?t=1878994
download the ROM
download boot.img
first flash the boot img in command prompt
then don't restart
go to recovery and flash the ROM
now restart
PM me if problem persists
Click to expand...
Click to collapse
HOORAY! That did the trick. Thank you so much. My hat is off to you sir. :laugh:

basalate said:
HOORAY! That did the trick. Thank you so much. My hat is off to you sir. :laugh:
Click to expand...
Click to collapse
M glad to help and really glad it worked....hf
Sent from my One V using xda app-developers app

[Q] can't boot into CM , can't update bootloader

I've been using viperX for about 9 months now, and today i wanted to upgrade to CM 10. so I downloaded the ROM and used ROM Manager (instead of bootloader) and it after CM was installed, it wouldn't boot. the flash screen was the only thing i saw for about 30 minutes.
then i googled for this situation and found out that most times the solution was to install CM via bootloader, so i tried to do so, and again the same thing happened.
next i thought i should update my bootloader. i was using CWM 2.x, i think it was 2.6.. can't really remember (it wasn't updated since around December 2012 when i switched to viperX). anyway, i tried to install TWRP, downloaded the latest version from their site and used the sdk tools that i already had on my computer (i updated it about a month ago) just as the instructions said. i got no error in the cmd, nor on the phone screen. i tried to get into recovery and got stuck on HTC logo.i tried also downloading the latest version of CWM and the result was the same.
now when I'm trying to boot into CM i get stuck on their logo, and when i try to boot into recovery i get stuck on HTC logo..i couldn't do factory reset either.
my phone is HTC one x (bought in Singapore)
HBOOT version is 1.36.0
any ideas where to go from here?
thanks in advance

You're in the wrong forum, this is the HTC One XL/at&t One X forum. I'll ask for this to be moved to the correct device forum for you.
Sent from my Evita

your problems were obviously because you were trying to flash things for the wrong device, Go here >>>>>http://forum.xda-developers.com/showthread.php?t=2069904

nogotaclue said:
your problems were obviously because you were trying to flash things for the wrong device, Go here >>>>>http://forum.xda-developers.com/showthread.php?t=2069904
Click to expand...
Click to collapse
omg, i feel so stupid that i did this.. thank you very much! i now flashed TWRP and it worked, I'm waiting till the battery charges and i'll install CM again, but looks like it gonna work this time.
thanks again, that link was really helpful.:good:

Ok, don't forget to use the right cm, not the version you used previously
Sent from my HTC One X using XDA Premium 4 mobile app

xulube said:
I've been using viperX for about 9 months now, and today i wanted to upgrade to CM 10. so I downloaded the ROM and used ROM Manager (instead of bootloader) and it after CM was installed, it wouldn't boot. the flash screen was the only thing i saw for about 30 minutes.
then i googled for this situation and found out that most times the solution was to install CM via bootloader, so i tried to do so, and again the same thing happened.
next i thought i should update my bootloader. i was using CWM 2.x, i think it was 2.6.. can't really remember (it wasn't updated since around December 2012 when i switched to viperX). anyway, i tried to install TWRP, downloaded the latest version from their site and used the sdk tools that i already had on my computer (i updated it about a month ago) just as the instructions said. i got no error in the cmd, nor on the phone screen. i tried to get into recovery and got stuck on HTC logo.i tried also downloading the latest version of CWM and the result was the same.
now when I'm trying to boot into CM i get stuck on their logo, and when i try to boot into recovery i get stuck on HTC logo..i couldn't do factory reset either.
my phone is HTC one x (bought in Singapore)
HBOOT version is 1.36.0
any ideas where to go from here?
thanks in advance
Click to expand...
Click to collapse
Hi,
I assume your bootloader is unlocked, I had same problem when I originally tried to flash custom rom (soft bricked phone).
Start from scratch and place fastboot folder in root directory of an easily accesible drive (c and place CWM zip file, Version 5.8.4.0 (for one x) in that folder and use CMD prompt to flash CWM again, then boot into CWM recovery and mount phone as USB storage and hopefully you have backed up original software as Nandroid backup (copy to pc so you have a backup copy). From there you can place CM 10 zip file in root directory of phone and install from CWM after doing full wipe, and wipe cache (all through CWM). Youtube has some good videos (Cursed4Eva in particular) on flashing roms. You may also have to flash boot image or you may get stuck in bootloop.
Hope this helps.

okhughes said:
Hi,
I assume your bootloader is unlocked, I had same problem when I originally tried to flash custom rom (soft bricked phone).
Start from scratch and place fastboot folder in root directory of an easily accesible drive (c and place CWM zip file, Version 5.8.4.0 (for one x) in that folder and use CMD prompt to flash CWM again, then boot into CWM recovery and mount phone as USB storage and hopefully you have backed up original software as Nandroid backup (copy to pc so you have a backup copy). From there you can place CM 10 zip file in root directory of phone and install from CWM after doing full wipe, and wipe cache (all through CWM). Youtube has some good videos (Cursed4Eva in particular) on flashing roms. You may also have to flash boot image or you may get stuck in bootloop.
Hope this helps.
Click to expand...
Click to collapse
he doesn't need to start from scratch, he knows how to do it. the problem was he was in the wrong forum. did you even read the thread?