Hello,
I have rooted my Desire last week with Unrevoked (Clockwork Mod) to do Nandroid Backup. Firmware is the official stock ROM of HTC. Yesterday I want to update it to newest OTA update --> Bad idea.
After that it does not boot anymore and no Recovery is available. The only thing which works is the HBoot and Fastboot with USB-plug.
How can I get back my Desire with live.
What I already tried (with/without SIM or SD/Goldcard):
- cleared Storage
- Tried to install official Update: RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe -> Want to upgrade from 2.29.405.2 to 2.09.405.8 -> OK -> Error 140 Bootloader Version Error
- Tried to flash by Fastboot from SDK Tools (Radio, HBoot, ...). The Images that I tried are the ones extracted of the exe mentioned before -> Message: FAILED (remote: signature verify fail) with every type of Image
- Tried update by Fastboot (fastboot update update.zip) -> MSg: Whoops: didn't find expected signature
So all my tries are with no success. Is there any chance to bring any firmware to my device?Is ther anything that I have done wrong or else what I can try?
Additional Informations from Bootloader:
Bravo PVT1 SHIP S-ON
HBOOT-0.93.0001
Microp-031d
Touch Panel Synth-Synth0101
RADIO-5.11.05.27
Thanks in advance for your help,
tommyboy
Download the RUU in my signature and try again
EddyOS said:
Download the RUU in my signature and try again
Click to expand...
Click to collapse
Thank you very much, EddyOS. It was just so simple. I picked the wrong ROM-Version. Stupid me and thank you for saving my life
Hi All,
Any help would be appreciated. I have the following device:
Bravo PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
RA-desire-v2.0.0
but when I got to install a ROM (insertcoin and Leedroid tried so far) I get this message in the recovery screen:
Install from sdcard…
Finding update package…
Opening update package…
Verifying update package…
E:Wrong Digest:
System/customization/CID/default.xml
E:Verification failed
Installation aborted.
Thanks for your help.
Try to toggle (disable) verification in the recovery.
I downloaded the latest CyanogenMod 7 with Google apps, renamed to update.zip, placed in the root of SD card, booted up the HBOOT screen (volume down + power button) and selected RECOVERY. It went into another screen where there is a phone picture with red triangle and exclamation mark in the middle, at the bottom it says "E:can't open /cache/recovery/command". I googled it up and many said to just ignore it, so I did.
Then following video guide I got up to the point where I have to install from update.zip and it fails there saying:
Finding update package
Openinng update package
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
So now I have no data, no cache partition and no phone.
These are the specs of the phone reported by Revolutionary HBOOT:
BUZZ PVT SHIP S-OFF
HBOOT-1.01.0002
MICROP-0622
TOUCH PANEL-ATMEL224_16ab
RADIO-3.35.20.10
Dec 2 2010, 17:14:53
You may want to post in the correct section.
Sent from my Wildfire S A510e using xda app-developers app
therabbit08 said:
I downloaded the latest CyanogenMod 7 with Google apps, renamed to update.zip, placed in the root of SD card, booted up the HBOOT screen (volume down + power button) and selected RECOVERY. It went into another screen where there is a phone picture with red triangle and exclamation mark in the middle, at the bottom it says "E:can't open /cache/recovery/command". I googled it up and many said to just ignore it, so I did.
Then following video guide I got up to the point where I have to install from update.zip and it fails there saying:
Finding update package
Openinng update package
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
So now I have no data, no cache partition and no phone.
These are the specs of the phone reported by Revolutionary HBOOT:
BUZZ PVT SHIP S-OFF
HBOOT-1.01.0002
MICROP-0622
TOUCH PANEL-ATMEL224_16ab
RADIO-3.35.20.10
Dec 2 2010, 17:14:53
Click to expand...
Click to collapse
Look for a pc49img.zip file of clockworkmod recovery for the wildfire (buzz) and put it on the root of your sdcard. Boot to hboot and let it update your recovery. Once that is done delete the file from your sdcard and boot back into hboot. Select recovery. Perform the following.
Factory reset
Wipe data
Wipe cache
Install from sdcard/choose/cyanogenmod.
Install from sdcard/choose/ gapps.
Reboot.
Allow up to 10 minutes for the first boot to work and you should be good to go.
Your problem is that the stock recovery still checks for htc signatures I believe so it won't (or will only partially flash) other firmwares.
Also this is the wrong forum, you want the (buzz) wildfire forums. This is the more up to date wildfire (marvel)
tapped out from my sexy sensation XE
Hi
My English is not good (with the help of Google Translator wrote the text!)
I wanted to upgrade phone ROM, but I've had the problem of
The phone is rooted and s-off
I chose to do the following for threads:
http://forum.xda-developers.com/showthread.php?t=2651790
According to the guideline developer ROM
Must be installed TWRP recovery. (Cwm recovery I was put in its place I installed TWRP)
But after installing this recovery is anything to do with errors.
Errors:
E:Find_File: Error opening '/sys/class/backlight'
...
...
...
E:Could not creat file for updater extract in '/tem/updater'
Error flashing zip '/sdcard/BeanStalk-4.4.4407-20140713-bravo-RC6.zip'
=======
I tested other rom (different for threads)
Got the same errors
After this I could not even install 4ext recovery
error:
CID incorrect
===========
Information in the boot will be displayed:
----Alpha Rev----
BRAVO PVT4 SHIP S-OFF
HBOOT-0.93.0001
MICROP_051d
TOUCH PANEL-SYNW0101
RADIO-5.17.05.23
Aug 10 2010,17:52:18
==============
Please advise your
Thanks
Hey Folks!
After the dead of my desire (7 buzzes / vibrates -> indicates a broken soc/motherboard) and the new rising (got a motherboard of a desire with a broken screen) the old lady worked again!
I got the s/n and system from the one with the broken screen - this is normal because it's stored on the mainboard. It was a CM v7 as I remember.
Here as a list of things I did and where I stuck now:
flashed an up-to-date recovery TWRP -> worked
tried to install a new rom with a new hboot which -> didn't worked out
Since here I only can access the recovery
All attempts to flash something (via recovery or fastboot) -> doesn't work
also tried to use revolutionary (even it's already unlooked and s-off) -> but the app stucks
I could only flash the boot logo via fastboot the rest results in different errors like:
CID incorrect (pb99img.zip method)
Error (When trying to flash a .zip via recovery)
And an other Error i forgott (when flash via fastboot)
Also i can't get an information via fastboot (-getvar all). There is always a errormessage.
Here is my hboot-screen
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
I'm not sure if something went wrong while trying to put a new hboot (partition-layout).
I have no idea what to do. Read about the half of the internet....
Anyone any idea?
Here is an other error message i get when running this fastboot command
Code:
fastboot getvar all
getvar:all FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I'm realy appreciate any help!
BTW: I'm not a robot!
Des!re said:
CID incorrect (pb99img.zip method)
Error (When trying to flash a .zip via recovery)
And an other Error i forgott (when flash via fastboot)
Also i can't get an information via fastboot (-getvar all). There is always a errormessage.
Here is my hboot-screen
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
I'm not sure if something went wrong while trying to put a new hboot (partition-layout).
I have no idea what to do. Read about the half of the internet....
Anyone any idea?
Click to expand...
Click to collapse
So good news is that it's not bricked if you can reach bootloader and recovery screen. Sounds like a driver issue or bad download of ROM, or both.
A few things to note:
- You haven't changed hboot because it still says 'Alpharev' on top of the bootloader screen. It should say the name of the hboot e.g. Alpharev CM7R2 if successful.
- CID incorrect happens when you try to flash a different region RUU. You should have tried the 2.3.3 GB WWE RUU, many threads in Q&A cover this.
- You should always try 'fastboot devices' command before flashing anything via fastboot, this will tell you straight away if you have driver issues.
This info I must have learnt reading the other half of the internet ...
What I would do:
- Confirm that fastboot is working first, check your drivers. Did you flash the recovery using fastboot? Flashing an hboot is largely the same method.
- Verify that the md5sum of the ROM.zip is correct on PC before flashing. Test several ROMs to be sure.
- Verify that the ROM is also compatible with the hboot as well or it won't boot.
- Make sure you nandroid backup if you have anything to save, then full wipe (wipe data/factory reset) before flashing the ROM.
- Make sure your sd card is correctly partitioned if the ROM requires one., as some put parts of the ROM on the partition. You will need a partition to install more than a few apps anyway.
- Post / research the exact error message if it's still not working, and at least state which ROMs you've tried.
eddiehk6 said:
So good news is that it's not bricked if you can reach bootloader and recovery screen. Sounds like a driver issue or bad download of ROM, or both.
A few things to note:
- You haven't changed hboot because it still says 'Alpharev' on top of the bootloader screen. It should say the name of the hboot e.g. Alpharev CM7R2 if successful.
- CID incorrect happens when you try to flash a different region RUU. You should have tried the 2.3.3 GB WWE RUU, many threads in Q&A cover this.
- You should always try 'fastboot devices' command before flashing anything via fastboot, this will tell you straight away if you have driver issues.
This info I must have learnt reading the other half of the internet ...
Click to expand...
Click to collapse
Thanks for your reply. Some things I forgot to mention in the thread above.
I successfully rooted, s-off, and flashed a new hboot & rom to my old desire.... all before she died. I remembered I needed some tries for the hboot... but it worked out fine in the end.
I also need to say that I tried (with the new/repaired one) different clients (hardware and os, win & linux) and different cables. Just to be sure.
I also went sure that fastboot is working (fastboot devices) and there always was my serial -> so it's good for sure
I read something about that the Alpharev hboot (with the repaired phone there was also the bootsplash with 'alpha-rev s-off / why so serious?' before I flashed it away to the stock 'htc') is somehow write-protected itself which can cause issues???
I tried to flash the "Alpha Jelly (250/5/182) hboot" to be able to install CarbonRom 1.0 (4.4.4) by spezi77 (http://forum.xda-developers.com/showthread.php?t=2658853). But I didn't succeeded at all.
eddiehk6 said:
What I would do:
- Confirm that fastboot is working first, check your drivers. Did you flash the recovery using fastboot? Flashing an hboot is largely the same method.
Click to expand...
Click to collapse
I think I flashed the recovery via fastboot, it just worked once. When I tried to flash CWM it didn't worked anymore.
eddiehk6 said:
- Verify that the md5sum of the ROM.zip is correct on PC before flashing. Test several ROMs to be sure.
Click to expand...
Click to collapse
I did checked the md5sum's and I tested a couple of Roms (more than 3)
eddiehk6 said:
- Verify that the ROM is also compatible with the hboot as well or it won't boot.
Click to expand...
Click to collapse
My old devices was a PVT4 and the repaired one is a PVT1 - there should be no difference for the hboot i guess?
eddiehk6 said:
- Make sure you nandroid backup if you have anything to save, then full wipe (wipe data/factory reset) before flashing the ROM.
Click to expand...
Click to collapse
This I should have done straight after I repaired the hardware and I was able to boot in CM7.... To late for now but if I have a working state I definitely do this!! :good:
eddiehk6 said:
- Make sure your sd card is correctly partitioned if the ROM requires one., as some put parts of the ROM on the partition. You will need a partition to install more than a few apps anyway.
Click to expand...
Click to collapse
I don't have a booting system yet so I need to postpone this. To be able to do the pb99img.zip method i formatted the whole sd-card with one partition as fat32. But when I have (hopefully) soon a working system I need to partion it correctly - easy!
eddiehk6 said:
- Post / research the exact error message if it's still not working, and at least state which ROMs you've tried.
Click to expand...
Click to collapse
I'm the resarcher! I'm going down to reasearch - I will report!
Thanks for your help so far!
I'm the resarcher! I'm going down to reasearch - I will report!
Click to expand...
Click to collapse
I went down to research!
I tried to flash hboot 'Bravo Stock' by Alpharev.
Code:
fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)...
OKAY [ 0.104s]
writing 'hboot'...
OKAY [ 0.160s]
finished. total time: 0.264s
looks good for me!
the bootscreen changed from
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
to
Code:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
so first and third line changed!
And because it's so nice to flash hboot i also flashed AlphaRev Jelly successfully!!
I try flash a rom now :fingers-crossed:
After I successfully flashed my hboot (twice!)....
I'm not able to wipe or install stuff....
Team Win Recovery Project v2.7.1.0
WIPE -> Factory Reset (Wipe Data, Cache and Dalvik)
Code:
Factory Reset Complete
Failed
E:Find_File: Error opening '/sys/class/backlight'
E:Unable to recreate and-sec folder.
Updating partition details...
E:Unable to mount storage
E:Unable to mount /sdcard during GUI startup.
Full SELinux support is present.
E:Unabke to mount /sdcard/TWRP/.twrps when trying to read settings file.
MTD Formatting "cache"
Done.
MTD Formatting "userdata"
Done.
Updatting partition details...
E:Unable to mount storage.
### FAILED ###
Team Win Recovery Project v2.7.1.0
Install -> ZIP
Code:
Zip Install Complete
Failed
E:Find_File: Error opening '/sys/class/backlight'
Updating partition details...
Full SELinux support is present.
Installing '/sdcard/roms/CARBON-KK-UNOFFICIAL-20140914-1119-bravo.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Could not create file for updater extract in '/tmp/updater'
Error flashing zip '/sdcard/roms/CARBON-KK-UNOFFICIAL-20140914-1119-bravo.zip'
Updatting partition details...
### FAILED ###
Maybe there is something "broken" with the filesystem?
As always I appreciate any help
Did a 'clear userdata' in the boot menu and then a wipe via TWRP.
Now it was successful but with this errors in the console:
Code:
Factory Reset Complete
Successful
E:Find_File: Error opening '/sys/class/backlight'
Updating partition details...
Full SELinux support is present.
MTD Formatting "cache"
Done.
MTD Formatting "userdata"
Done.
Wiping Android Secure
Formatting SD-Ext using make_ext4fs function.
Updating partition details...
But I wonder where are these errors from
Installing a rom still doesn't work. I think the problem is this line:
Code:
E:Could not create file for updater extract in '/tmp/updater'
There is BIG FAT BUG in the newest TWRP (v2.7.1.0)
You can't install anything before manually create the tmp directory
You have to do the following steps to flash any files :
- boot into recovery mode
- choose 'Advanced'
- choose 'Terminal Command'
- You're now on the '/' (root of the file system). Choose 'Select'
- Type : 'mkdir tmp' without quotes, then Hit the enter key of your keyboard.
- Return to the main screen (Go back 3 times)
- Choose 'Install' and select the file.
Click to expand...
Click to collapse
>>> http://forum.xda-developers.com/showthread.php?t=2595654&page=12
This is to bad - it's the most recent version and the recovery has a bug like this!
Code:
Installing Carbonrom 4.4.4. for HTC Desire
Homemade by spezi77
Next shot should be Lollipop :victory:
[ROM/WIP] [5.0.2] [Jan-17] [UNOFFICIAL] ParanoidAndroid 5.0 Alpha
>>> http://forum.xda-developers.com/htc-desire/development/rom-paranoidandroid-5-0-alpha-t3002046
Des!re said:
There is BIG FAT BUG in the newest TWRP (v2.7.1.0)
You can't install anything before manually create the tmp directory
>>> http://forum.xda-developers.com/showthread.php?t=2595654&page=12
This is to bad - it's the most recent version and the recovery has a bug like this!
Code:
Installing Carbonrom 4.4.4. for HTC Desire
Homemade by spezi77
Next shot should be Lollipop :victory:
[ROM/WIP] [5.0.2] [Jan-17] [UNOFFICIAL] ParanoidAndroid 5.0 Alpha
>>> http://forum.xda-developers.com/htc-desire/development/rom-paranoidandroid-5-0-alpha-t3002046
Click to expand...
Click to collapse
I've personally never used TWRP on the Desire.
I recommend trying with 4EXT Recovery, never had any issues with it.
If you can successfully flash an hboot, you should be able to flash the recovery.img using the same method.