Develop Bugs

[Q] HTC Wildfire Buzz: stuck and doesnt accept custom roms or RUUs

Hi,
I have HTC Wildfire Buzz which had a problem getting stucking at HTC logo and kept rebooting. I decided to unlock the bootloader and flash a custom rom, I downloaded CWM recovery and tried flashing a custom rom but got an error and then I tried flashing different variations of CM roms such as update-cm-7.1.0.1-buzz-signed.zip and cm_buzz_full-256.zip but I got different types of errors including Err 7.
The other custom rom I tried to install was Android_Freedom_Wildfire_By_MONI69_a2sd but I kept getting the following error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
I tried running different relevant RUUs based on my phone region but always ended up with error due to the fact that the firmware version currently installed is 2.46.0.0 and all the RUUs have versions lower than it.
I would appreciate providing me with your guidance and advice, my phone info is provided below.
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: SH13TPY12305
INFOimei: xxxxxxxxxxxxxx
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 4211mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0

yabdali said:
Hi,
I have HTC Wildfire Buzz which had a problem getting stucking at HTC logo and kept rebooting. I decided to unlock the bootloader and flash a custom rom, I downloaded CWM recovery and tried flashing a custom rom but got an error and then I tried flashing different variations of CM roms such as update-cm-7.1.0.1-buzz-signed.zip and cm_buzz_full-256.zip but I got different types of errors including Err 7.
The other custom rom I tried to install was Android_Freedom_Wildfire_By_MONI69_a2sd but I kept getting the following error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
I tried running different relevant RUUs based on my phone region but always ended up with error due to the fact that the firmware version currently installed is 2.46.0.0 and all the RUUs have versions lower than it.
I would appreciate providing me with your guidance and advice, my phone info is provided below.
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: SH13TPY12305
INFOimei: xxxxxxxxxxxxxx
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__044
INFObattery-status: good
INFObattery-voltage: 4211mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
Click to expand...
Click to collapse
Hello dude...i have the same phone with exactly same specs n had d same prob
go to fastboot,connect usb
now u have a .img file in ur rom's zip.
extract it to fastboot folder
via cmd go to fastboot folder with ur ph connected.. type
fastboot flash boot xxx.img
it will take some time
nxt flash cwm if u dont hv it
then get a micro sd wid ur rom(unedited) and flash it via cwm...disable signature verification if needed
press d thanks button n voila u have ur nw rom

ontheflames said:
Hello dude...i have the same phone with exactly same specs n had d same prob
go to fastboot,connect usb
now u have a .img file in ur rom's zip.
extract it to fastboot folder
via cmd go to fastboot folder with ur ph connected.. type
fastboot flash boot xxx.img
it will take some time
nxt flash cwm if u dont hv it
then get a micro sd wid ur rom(unedited) and flash it via cwm...disable signature verification if needed
press d thanks button n voila u have ur nw rom
Click to expand...
Click to collapse
Hi, Thanks for your advice, unfortunately it didnt work! I tried the following:
Extracting the rom zip and flashing boot.img via fastboot then using CWM flashing the rom xxxx.zip.
update-cm-7.1.0.1-buzz-signed.zip error:
assert failedackage_extract_file("boot.img","/tmp/boot.img")
E:error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 7)
Installation aborted
Android_Freedom_Wildfire_By_MONI69 error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
Hope this gives further insights about the problem, any suggestion advise would be highly appreciated.

hey man, silly question but are you sure you are doing a full factory wipe, data wipe cache wipe and dalvick cache wipe?
you should do the wipes every time you try to flash a new rom.

heavy_metal_man said:
hey man, silly question but are you sure you are doing a full factory wipe, data wipe cache wipe and dalvick cache wipe?
you should do the wipes every time you try to flash a new rom.
Click to expand...
Click to collapse
Yes, I use CWM to do factory reset, cache, dalvick wipes everytime I flash a rom!

yabdali said:
Hi, Thanks for your advice, unfortunately it didnt work! I tried the following:
Extracting the rom zip and flashing boot.img via fastboot then using CWM flashing the rom xxxx.zip.
update-cm-7.1.0.1-buzz-signed.zip error:
assert failedackage_extract_file("boot.img","/tmp/boot.img")
E:error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 7)
Installation aborted
Android_Freedom_Wildfire_By_MONI69 error:
E:Can't symlink /system/bin/cat
E:Failure at line 10: symlink toolbox SYSTEM:bin/cat
installation aborted
Hope this gives further insights about the problem, any suggestion advise would be highly appreciated.
Click to expand...
Click to collapse
Another alternative is formating all partitions before flashing..
and btw did u extract the whole zip for boot.img?
what is ur cwm version?
did u try disabling signature check and script asserts??

ontheflames said:
Another alternative is formating all partitions before flashing..
and btw did u extract the whole zip for boot.img?
what is ur cwm version?
did u try disabling signature check and string asserts??
Click to expand...
Click to collapse
Hi, thanks for your continous support, I tried the following but not matter what rom I flashed I still get some sort of an error. As for your question regarding the boot.img, yes I extracted the xxxx.zip flashed boot.img via fastboot pulled the batter started CWM and installed the original xxxx.zip. I tried the partiations formatting, below are the details.
ClockworkMod Recovery v2.5.0.7
Green color
wipe data/factory
wip cache
wipe delivak (E: can't mount /dev/block.mmcblk0p2)
format system
format boot
format data
format cache
toggle script asserts/signature (disabled)
Rom: cm-buzz_full-256.zip
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/cm-buzz_full-256.zip
(Status 7)
Installation aborted.
Rom: update-cm-7.1.0.1-buzz-signed.zip
E:Error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 0)
Installation aborted
I also get package_extract_file("boot.img","/tmp/boot.img") error in some other roms.

yabdali said:
Hi, thanks for your continous support, I tried the following but not matter what rom I flashed I still get some sort of an error. As for your question regarding the boot.img, yes I extracted the xxxx.zip flashed boot.img via fastboot pulled the batter started CWM and installed the original xxxx.zip. I tried the partiations formatting, below are the details.
ClockworkMod Recovery v2.5.0.7
Green color
wipe data/factory
wip cache
wipe delivak (E: can't mount /dev/block.mmcblk0p2)
format system
format boot
format data
format cache
toggle script asserts/signature (disabled)
Rom: cm-buzz_full-256.zip
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/cm-buzz_full-256.zip
(Status 7)
Installation aborted.
Rom: update-cm-7.1.0.1-buzz-signed.zip
E:Error in /sdcard/update-cm-7.1.0.1-buzz-signed.zip
(Status 0)
Installation aborted
I also get package_extract_file("boot.img","/tmp/boot.img") error in some other roms.
Click to expand...
Click to collapse
Strange...btw how did ur wf stop booting all of a sudden? I think u have failed to get proper root and unlocked bootloader
pl verify it in hboot..on top it must display 'UNLOCKED'
more when u comment
Hit thanks if i helped u

ontheflames said:
Strange...btw how did ur wf stop booting all of a sudden? I think u have failed to get proper root and unlocked bootloader
pl verify it in hboot..on top it must display 'UNLOCKED'
more when u comment
Hit thanks if i helped u
Click to expand...
Click to collapse
Its my wife's phone. Out of the blue started getting stuck in HTC logo and kept rebooting. Yes, its unlocked using HTCDEV and it shows that in hboot "UNLOCKED".
Appreciate your further feedback..

I'd first try a different sd card, it looks to me like it's not reading properly with some of those errors, mount /system from Cwm mounts and storage option before wiping and flashing the new rom too, if that fails try fastboot flashing Cwm 5.0.2.0, then try again. I've never seen this problem before so my apologies if I'm way off the mark.
Sent from my HTC Wildfire using xda premium

i have the same problem here.
hboot 1.02.0000 - won't downgrade for anything in the world
s-on
in cwm i cannot install any rom. says "status 0 installation aborted" or "bad"
the ruu's are not working either.
i don't have a backup or a rom installed. if there's anyone who can provide me a buzz backup so i can restore into my phone, i would much appreciate it. i think is the single thing i didn't try.

seagerfreak said:
i have the same problem here.
hboot 1.02.0000 - won't downgrade for anything in the world
s-on
in cwm i cannot install any rom. says "status 0 installation aborted" or "bad"
the ruu's are not working either.
i don't have a backup or a rom installed. if there's anyone who can provide me a buzz backup so i can restore into my phone, i would much appreciate it. i think is the single thing i didn't try.
Click to expand...
Click to collapse
It already has been mentioned a few times here in the forum: htcdev won't give you s-off and it's not absolutely clear (= not confirmed) that can get s-off after the htcdev unlock (because you can't downgrade the HBOOT).
I have no idea if there's a possibility but it doesn't look good - there are 2 other threads regarding this issue here in Q&A or General section - you might want to have a look.
For the install problem I'm pretty sure that's something different as you usually should be able to install a ROM...

i have looked into othet threads. nothing works

seagerfreak said:
i have looked into othet threads. nothing works
Click to expand...
Click to collapse
You need to relock your boot loader for an ruu to work. relock the bootloader and remove the rom.zip from the htcdev bootloader unlock ruu. Remember an ruu with a lower hboot will not run. Rename it to pc49img.zip and put it on the root of your sdcard. Boot to hboot and allow the bootloader to flash the rom. but if I was you I would just try to get access to an xtc clip and fully s-off the phone. Then it will run any ruu and custom rom.
Sent from my HTC Sensation using xda premium

heavy_metal_man said:
You need to relock your boot loader for an ruu to work. relock the bootloader and remove the rom.zip from the htcdev bootloader unlock ruu. Remember an ruu with a lower hboot will not run. Rename it to pc49img.zip and put it on the root of your sdcard. Boot to hboot and allow the bootloader to flash the rom. but if I was you I would just try to get access to an xtc clip and fully s-off the phone. Then it will run any ruu and custom rom.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
thanx for the answer. i have relocked my bootloader. renamed the rom and put it on the root of the sdcard. the hboot shows a loading bar, but after loading, nothing happens. the part with the removing the rom.zip from the htcdev bootloader unlock ruu i didn't understand. can you be more specific? thanx
quick edit: when running a ruu, it gives me usb connection error

Here's the quick guide
Install hTc drivers successfully on pc.
Remove hTc sync and other related apps.
Now download clockworkmod recovery(whichever you want) and fastboot+adb kit on pc.
Open fastboot.
Connect ur phone. Load the bootloader and then fastboot. Fastboot mode(something like that) should be on your phone. Paste recovery and boot image in fastboot folder.
Type fastboot devices
Type fastboot flash boot boot.img(i faintly remember what this was, sorry )
Type fastboot flash 'recoveryname'.zip
After that disconnect ur phone.
Select recovery.
(If u dont see anything, it was unsuccessful, hold vol up+power to see default recovery.)
Now install roms like this(http://forum.xda-developers.com/showthread.php?t=1851096):p(my rom) via recovery.
Hit Thanks.
You are done
Note:s off is not required for flashing a custom rom, however an unlocked bootloader is.
Edit: Hey sorry didnt read my earlier posts, after all wf is slow on internet.
However this is the problem where u you are flashing incorrect boot.img
Make sure its from your rom, or try using the one in cm7, try both as Im not exactly certain. If u have cwm it asserts that u have root and you can flash roms.

ontheflames said:
Here's the quick guide
Install hTc drivers successfully on pc.
Remove hTc sync and other related apps.
Now download clockworkmod recovery(whichever you want) and fastboot+adb kit on pc.
Open fastboot.
Connect ur phone. Load the bootloader and then fastboot. Fastboot mode(something like that) should be on your phone. Paste recovery and boot image in fastboot folder.
Type fastboot devices
Type fastboot flash boot boot.img(i faintly remember what this was, sorry )
Type fastboot flash 'recoveryname'.zip
After that disconnect ur phone.
Select recovery.
(If u dont see anything, it was unsuccessful, hold vol up+power to see default recovery.)
Now install roms like this(http://forum.xda-developers.com/showthread.php?t=1851096):p(my rom) via recovery.
Hit Thanks.
You are done
Note:s off is not required for flashing a custom rom, however an unlocked bootloader is.
Edit: Hey sorry didnt read my earlier posts, after all wf is slow on internet.
However this is the problem where u you are flashing incorrect boot.img
Make sure its from your rom, or try using the one in cm7, try both as Im not exactly certain. If u have cwm it asserts that u have root and you can flash roms.
Click to expand...
Click to collapse
i made every step you told me to. this is what i get.
the only way i can make the phone visible in adb, is in recovery. being unable to boot a rom, i cannot set the usb debugging mode. so, everything that i will make, is via fastboot or ruu. but ruu gives me usb connection error or error [155] in fastboot, and baterry < 30% in adb mode.

What if you unlock your bootloader again and flash a recovery.img from fastboot? Maybe there is problem with your cwm recovery. I guess you have already tried formatting you sd card, tried a different sd card and tried different custom roms.
I would definitely try to get some more charge in your phone first because if you loose power while flashing it could end up really bad. An RUU won't install on low battery (i thought you needed >70%) what if you charge up and run ruu from adb again?

Rename your CID to HTC_001 (fastboot writecid HTC__001). Relock your bootloader using fastboot oem lock. Run a WWE RUU. Use the rooting link in my sig.
Done, and don't ever root with HTCDev again.

hans moleman said:
What if you unlock your bootloader again and flash a recovery.img from fastboot? Maybe there is problem with your cwm recovery. I guess you have already tried formatting you sd card, tried a different sd card and tried different custom roms.
I would definitely try to get some more charge in your phone first because if you loose power while flashing it could end up really bad. An RUU won't install on low battery (i thought you needed >70%) what if you charge up and run ruu from adb again?
Click to expand...
Click to collapse
i tried every possible combination of cwms and roms.
usaff22 said:
Rename your CID to HTC_001 (fastboot writecid HTC__001). Relock your bootloader using fastboot oem lock. Run a WWE RUU. Use the rooting link in my sig.
Done, and don't ever root with HTCDev again.
Click to expand...
Click to collapse
i get this error
C:\android sdk\platform-tools>fastboot oem writecid HTC__001
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
C:\android sdk\platform-tools>
Click to expand...
Click to collapse
just to be clear, the phone was in this state, it's not mine. i am only trying to put whatever rom i can so i can make it work

[Q] Idiot With HTC one X stuck in boot loop.

Hello,
I’ve been following guides to root my phone and put a custom ROM onto it. I had no experience in doing this so I thought I would follow an idiots guide and was stupid enough not to back up the original ROM along with not reading up properly on what I was about to do… (yes you can call me names I shall accept it)
The problem I'm having is after putting the custom ROM which was ViperX3.2.0 The phone just stays stuck on the HTC one Tm with beats audio and keeps resetting it self, anyway i can fix it? or have i bricked it.
I'm a complete noobie cause I've been looking around for the past 3 days and still can't find anything (or something I can understand) :angel:
- I've wiped cache, dalvik cache and battery stats
- I go to recovery and click mount sd card nothing happens mount usb storage nothing happens.
- I don't understand next to nothing, need like android for idiots. :good:
- When phones booting up my computer recognises something but has not drivers and fails (But i had drivers and could transfer stuff too and from)
So if you can help i will love you forever
Many Thanks
RIch

I'm going to quote the instructions on the ViperX page. Have you even followed these steps?
Code:
1. Make sure your that your HBOOT is 1.31 or greater
2. Check if you CID is supported, visit http://forum.xda-developers.com/showthread.php?t=1957376 for updates. Cheers Mike
3. Unlock your bootloader via HTCDev and install a custom recovery.
4. Download the ROM and place it on your virtual SD card.
5. Do a nandroid backup!
6. Extract boot.img from ROM zip and flash it using ‘fastboot flash boot boot.img’.
7. Use 'fastboot erase cache' to avoid boot issues.
8. Go into recovery and install the ROM.
9. Please choose fullwipe if you are asked, highly recommended if you go from one rom from another rom.
10. Reboot the device and enjoy!

Did you flash the boot.img file in fastboot? fastboot flash boot boot.img followed by fastboot erase cache

tomascus said:
I'm going to quote the instructions on the ViperX page. Have you even followed these steps?
Code:
1. Make sure your that your HBOOT is 1.31 or greater
2. Check if you CID is supported, visit http://forum.xda-developers.com/showthread.php?t=1957376 for updates. Cheers Mike
3. Unlock your bootloader via HTCDev and install a custom recovery.
4. Download the ROM and place it on your virtual SD card.
5. Do a nandroid backup!
6. Extract boot.img from ROM zip and flash it using ‘fastboot flash boot boot.img’.
7. Use 'fastboot erase cache' to avoid boot issues.
8. Go into recovery and install the ROM.
9. Please choose fullwipe if you are asked, highly recommended if you go from one rom from another rom.
10. Reboot the device and enjoy!
Click to expand...
Click to collapse
Like I Said I was stupid enough not to follow instruction, where to start. First my Hboot is not 1.31 but 1.12 or somthing. No clue what CID is Trust an idiot like me to do something like this HA.
I never did a nandroid backup, I'm hitting myself for that one quite badly
Apart from that i did everything else HA yes i did do fastboot boot boot.img folowed by somthing to do with cache

Richlilrich said:
Like I Said I was stupid enough not to follow instruction, where to start. First my Hboot is not 1.31 but 1.12 or somthing. No clue what CID is Trust an idiot like me to do something like this HA.
I never did a nandroid backup, I'm hitting myself for that one quite badly
Apart from that i did everything else HA yes i did do fastboot boot boot.img folowed by somthing to do with cache
Click to expand...
Click to collapse
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip

tomascus said:
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Ahh, i've done what you just said it looks like i'm getting somewhere.
looks like i'm stuck on this one.
C:\fastboot>fastboot flash zip 3.16.61.6.zip
sending 'zip' (12875 KB)...
OKAY [ 1.786s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 5.130s

Just keep trying 'fastboot flash zip (lalala)' until it works.
Afterwards, you need to re-unlock your bootloader with 'fastboot flash unlocktoken unlock_code.bin'
then reflash boot.img 'fastboot flash boot boot.img'
then 'fastboot erase cache'
then reflash recovery 'fastboot flash recovery (lalalaa.img)'

tomascus said:
Just keep trying 'fastboot flash zip (lalala)' until it works.
Afterwards, you need to re-unlock your bootloader with 'fastboot flash unlocktoken unlock_code.bin'
then reflash boot.img 'fastboot flash boot boot.img'
then 'fastboot erase cache'
then reflash recovery 'fastboot flash recovery (lalalaa.img)'
Click to expand...
Click to collapse
I feel bad, wasting your time still. CMD has froze should i cancel ctrl +c? so i apologise in advance
C:\fastboot>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
also 0kb?
-EDIT-
DONE IT! However i don't have no signal and can't connect to wifi? did i miss a step?
also i would love the opportunity to learn about this stuff starting from the basics, any advice on some reading i should do? i know it's a cheeky question but it's a must I think LOL
But thank you for your time.
Rich

Richlilrich said:
I feel bad, wasting your time still. CMD has froze should i cancel ctrl +c? so i apologise in advance
C:\fastboot>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.008s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
also 0kb?
-EDIT-
DONE IT! However i don't have no signal and can't connect to wifi? did i miss a step?
also i would love the opportunity to learn about this stuff starting from the basics, any advice on some reading i should do? i know it's a cheeky question but it's a must I think LOL
But thank you for your time.
Rich
Click to expand...
Click to collapse
I'm happy for you.
Man, just search and you shall find
Try reflash boot.IMG or if it doesn't work- Full wipe and reflash ROM.
Sent from my HTC One X using xda app-developers app

tomascus said:
I'm happy for you.
Man, just search and you shall find
Try reflash boot.IMG or if it doesn't work- Full wipe and reflash ROM.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Whoopsie, did fastboot flash boot boot.img didn't start up so i thought i would check recovery and earse some caches, theres an error for it to load. (a phone laying down with an exclaimation mark) so i can't do a wipe

Reflash the custom recovery
Fastboot flash recovery recover.img
Fastboot erase cache

Anyway to get the recovery back? so i can try another ROM to see if that could possibly fix the problem, just can't get into recovery D: happy my phone turns on lol however no network or can't connect to wifi
by fashing the boot did nothing but crash it more.
so i had to redo what you taught me, thank you again and i'm back to where i said i was

Flash this one again
http://db.tt/Krlm4dPs
Fastboot flash recovery recovery.img
Rename the downloaded file to recovery.img before you flash !

Mr Hofs said:
Flash this one again
http://db.tt/Krlm4dPs
Fastboot flash recovery recovery.img
Rename the downloaded file to recovery.img before you flash !
Click to expand...
Click to collapse
Many thanks, recovery up and running. now that I know this I'll try to reinstall the ROM.
Are there any reasons why I'm not getting signal or WiFi? along with that from the unlock it seem rather slow,
But I guess it's time for me to experiment, now that i know how to fix it if I mess up

Maybe because of this :
When installing the viper you get a question about the custom kernel ....
Answer with NO !

Mr Hofs said:
Maybe because of this :
When installing the viper you get a question about the custom kernel ....
Answer with NO !
Click to expand...
Click to collapse
I am sure I have done that a few times, going to try re downloading and try to reinstall. May not be installing right,

Thanks
Just signed up to say thanks Mr Hofs for the help you've posted in this thread in particular but also in many other threads I've been referring to over the last 4 hours or so. I was well on my way to brickage following a screwed up attempt to root my HOX, but thanks to you I'm now up and running again. Admittedly I'm back at square one with a non-rooted handset, but I never would've believed that would be such a happy place to be, plus I feel a tiny bit less of a noob now.
Anyway, apologies for crashing your thread Richlilrich - as you were!

Screwed up my One X
tomascus said:
Okay, in fastboot mode, type 'fastboot getvar cidnum' to get your CID number.
then according to that number, go here: http://forum.xda-developers.com/showthread.php?t=1957376
and download your firmware.zip
then use the following commands:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Hey Guy's,
I know this thread is old and many of you might not see this anymore but I'm sure this is where I need to be.
I have a UK Quad Core HOX and rooted fine a while ago.
I placed Cyanogen on for a while and all was running fine but it doesn't have all the tweaks I'd like so looked around for another ROM.
I came across the ViperROM and thought - Great! Exactly what I wanted, checked the reviews - All good, checked my HBoot etc... All seems fine. Went ahead and installed it through CWM (5.8.4.0) like I have done a thousand times before and went and rewrote the boot.img and got a continuous HTC boot loop. Thought hey no harm no fuss and went back into recovery to restore my most recent back-up only to find that they had all gone - My stock recovery my previous tries at other ROMS and most importantly my most recent Backup!!!!
I followed the steps above over and over again, I can re-lock my HOX, reboot into RUU and flash the 3.16.61.6 firmware (and boot img inside zip) and it still bootloop's over and over....... (I can unlock again too)
I've tried adb pushing Stock and custom ROMS to the SD card which says success in windows cmd but says no files on SDcard.
What am I doing wrong?
P.S hboot details are;
Endeveavoru PVT Ship S-ON RL
HBOOT-1.36.0000
CPLD-None
Microp-None
Radio-5.1204.163R.30
eMMC-Bootmode: disabled
CPU-bootmode: disabled
HW Secure boot:enabled
Modem path : off
Nov 16 2012, 18:32:39
Hope someone can help
---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------
DrUmMiSt said:
Hey Guy's,
I know this thread is old and many of you might not see this anymore but I'm sure this is where I need to be.
I have a UK Quad Core HOX and rooted fine a while ago.
I placed Cyanogen on for a while and all was running fine but it doesn't have all the tweaks I'd like so looked around for another ROM.
I came across the ViperROM and thought - Great! Exactly what I wanted, checked the reviews - All good, checked my HBoot etc... All seems fine. Went ahead and installed it through CWM (5.8.4.0) like I have done a thousand times before and went and rewrote the boot.img and got a continuous HTC boot loop. Thought hey no harm no fuss and went back into recovery to restore my most recent back-up only to find that they had all gone - My stock recovery my previous tries at other ROMS and most importantly my most recent Backup!!!!
I followed the steps above over and over again, I can re-lock my HOX, reboot into RUU and flash the 3.16.61.6 firmware (and boot img inside zip) and it still bootloop's over and over....... (I can unlock again too)
I've tried adb pushing Stock and custom ROMS to the SD card which says success in windows cmd but says no files on SDcard.
What am I doing wrong?
P.S hboot details are;
Endeveavoru PVT Ship S-ON RL
HBOOT-1.36.0000
CPLD-None
Microp-None
Radio-5.1204.163R.30
eMMC-Bootmode: disabled
CPU-bootmode: disabled
HW Secure boot:enabled
Modem path : off
Nov 16 2012, 18:32:39
Hope someone can help
Click to expand...
Click to collapse
Would like to add that I would prefer Viper to stock but stock would help for now

Before going for RUU and stuff, try any other roms.
I'd say do this :
Flash TWRP - Better than CWM anyday.
Go to recovery. Mount USB. Copy Viper (or any other) rom to phone.
Reboot to bootloader.
Flash boot.img.
Fastboot erase cache.
Go to recovery.
Clean install ROM.
Reboot and wait for it. First boot takes pretty long sometimes.

There is no better recovery, a recovery is personal. I'm using CWM now for 2 years....never had a problem with that.....
Now the issue.
How to copy it is in the post above, however before you install the rom you need to make a real good full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the rom...and ofcourse flash the boot.img from the rom.zip
The option to mount in CWM is under mounts and storage copy the rom.zip over and unmount.
The way i personally follow is :
Flash the boot.img (fastboot, bootloader mode) then enter the recovery and follow the above....make sure you unplug the usb cable BEFORE installing the rom.zip

[Q] HTC Desire HD not working after flashing 4ext

My DHD will not boot up. I can put it into recovery mode, but am not able to navigate the menu with my volume buttons or select options with the power button.
This occurred after an (apparently failed) attempt to flash the 4ext recovery.img onto my phone.
My phone has an unlocked bootloader, S-ON, and not rooted, if that helps.
I appreciate any help with my issue in either successfully flashing the recovery.img or getting my phone to work in any way. Thanks!

Switch5050 said:
My DHD will not boot up. I can put it into recovery mode, but am not able to navigate the menu with my volume buttons or select options with the power button.
This occurred after an (apparently failed) attempt to flash the 4ext recovery.img onto my phone.
My phone has an unlocked bootloader, S-ON, and not rooted, if that helps.
I appreciate any help with my issue in either successfully flashing the recovery.img or getting my phone to work in any way. Thanks!
Click to expand...
Click to collapse
try reflashing another recovery?TWRP or CWM from the official site?
use this command
fastboot flash recovery recovery.img (rename your img to recovery.img )

Steam. said:
try reflashing another recovery?TWRP or CWM from the official site?
use this command
fastboot flash recovery recovery.img (rename your img to recovery.img )
Click to expand...
Click to collapse
sending 'recovery' (6116 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 4.849s
This is the error I get. realize that my phone is stuck in HBOOT because I cannot navigate to Fastboot. Thanks for the reply.

Switch5050 said:
sending 'recovery' (6116 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 4.849s
This is the error I get. realize that my phone is stuck in HBOOT because I cannot navigate to Fastboot. Thanks for the reply.
Click to expand...
Click to collapse
probably the misc partition is fked, or the chip's gone bad.I'd try reflashing HBOOT by putting it manually via the sdcard, naming it PD98IMG.zip and putting the sdcard back.I'd wait out on another opinion though.

Steam. said:
probably the misc partition is fked, or the chip's gone bad.I'd try reflashing HBOOT by putting it manually via the sdcard, naming it PD98IMG.zip and putting the sdcard back.I'd wait out on another opinion though.
Click to expand...
Click to collapse
In case I don't get another option, could you instruct me on how to transfer the file to the sdcard? Sorry, not very knowledgable on this type of thing.

Switch5050 said:
In case I don't get another option, could you instruct me on how to transfer the file to the sdcard? Sorry, not very knowledgable on this type of thing.
Click to expand...
Click to collapse
Remove it from the phone, insert it into a cardreader of some sort, transfer it to the sdcard renaming it to PD98IMG.zip,putting the file in the root of the sdcard, no folders, putting the card back into the phone, booting to Hboot, pressing the power button just once to start the procedure.If you can't press any of the buttons in HBOOT too, then your phone is effed.
again, don't try this before someone else gives an opinion on this matter.

Steam. said:
Remove it from the phone, insert it into a cardreader of some sort, transfer it to the sdcard renaming it to PD98IMG.zip,putting the file in the root of the sdcard, no folders, putting the card back into the phone, booting to Hboot, pressing the power button just once to start the procedure.If you can't press any of the buttons in HBOOT too, then your phone is effed.
again, don't try this before someone else gives an opinion on this matter.
Click to expand...
Click to collapse
Cannot navigate HBOOT. My phone is apparently effed.

Switch5050 said:
Cannot navigate HBOOT. My phone is apparently effed.
Click to expand...
Click to collapse
Have you tried Glevitan's tool to flash CWM recovery? You can find it here:
http://forum.xda-developers.com/showthread.php?t=2133336
Or actually, these are the steps his tool do for flashing the recovery (use adb.exe and fastboot.exe, and change the location of CWM image):
echo Rebooting into fastboot usb
echo.
adb reboot-bootloader
adb kill-server
sleep 10
set recovery=tools\recovery\recovery-clockwork-touch-5.8.1.5-ace.img
fastboot flash recovery %recovery%
fastboot reboot​

Matth59 said:
Have you tried Glevitan's tool to flash CWM recovery? You can find it here:
http://forum.xda-developers.com/showthread.php?t=2133336
Or actually, these are the steps his tool do for flashing the recovery (use adb.exe and fastboot.exe, and change the location of CWM image):
echo Rebooting into fastboot usb
echo.
adb reboot-bootloader
adb kill-server
sleep 10
set recovery=tools\recovery\recovery-clockwork-touch-5.8.1.5-ace.img
fastboot flash recovery %recovery%
fastboot reboot​
Click to expand...
Click to collapse
that is if he can get to adb working at all, he's in hboot and he can't navigate, so no go

Switch5050 said:
sending 'recovery' (6116 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 4.849s
This is the error I get. realize that my phone is stuck in HBOOT because I cannot navigate to Fastboot. Thanks for the reply.
Click to expand...
Click to collapse
Take The sdcard out And reboot in hboot. Then try navigating To fastboot

[Q] After downgrade touch don't work

My HTC wildfire touch don't work after downgrade from 2.34.186.1 to from 2.34.186.1.
The branding ist 1und1. After this i try to find the original OTA 2.34.186.1 to upgrade
to the old one that was on the phone before. - no way - i don't found
After this i unlocked the bootloader and i think that there is a way to upgrade any firmware
but its not possible.
My bootscreen:
*** UNLOCKED ***
BUZZ PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0622
RADIO-3.35.15.31
Dec 13 2011,12:08:54
The HTC boot normaly to the lock screen but the touch don't work.
Anyone an idea to solve my problem an install another rom?

Here is another thread that discusses a similar issue.
Hope it'll help.
http://forum.xda-developers.com/showthread.php?t=1056767
Sent from my G9 using Tapatalk

Pretendde said:
My HTC wildfire touch don't work after downgrade from 2.34.186.1 to from 2.34.186.1.
The branding ist 1und1. After this i try to find the original OTA 2.34.186.1 to upgrade
to the old one that was on the phone before. - no way - i don't found
After this i unlocked the bootloader and i think that there is a way to upgrade any firmware
but its not possible.
My bootscreen:
*** UNLOCKED ***
BUZZ PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0622
RADIO-3.35.15.31
Dec 13 2011,12:08:54
The HTC boot normaly to the lock screen but the touch don't work.
Anyone an idea to solve my problem an install another rom?
Click to expand...
Click to collapse
Hmmm. This is going to be hard to get out of as you upgraded your Hboot. Does the phone still register fastboot commands? Also what downgrade thread did you follow?
Sent from my HTC Sensation using Tapatalk

It dont work at update with ruu shows the version 2.46.0.0 of the divece rom....
The update prozess stops and there is " FEHLER [155] : ABBILD-UPDATE-FEHLER " (IMAGE UPDATE ERROR)
The same with the PC49IMG.zip on microsd card:
RUU
Security fail!
Update Fail!

Pretendde said:
It dont work at update with ruu shows the version 2.46.0.0 of the divece rom....
The update prozess stops and there is " FEHLER [155] : ABBILD-UPDATE-FEHLER " (IMAGE UPDATE ERROR)
The same with the PC49IMG.zip on microsd card:
RUU
Security fail!
Update Fail!
Click to expand...
Click to collapse
That's not what I mean, to unlock your bootloader you would have had to issue the command fastboot OEM unlock, or fastboot flash OEM unlock unlock_token.bin or something similar. These types of commands are the ones I'm interested in I want to see if you can flash clockworkmod recovery pal.
Sent from my HTC Sensation using Tapatalk

I downgraded with the standard buzzdowngrade.zip package, step1 but the goldcard-step fail.....i flashed after hboot downgrade RUU_Buzz_Vodafone_DE_1und1_1.19.186.3_Radio_13.45.55.24_3.35.15.31_release_133745_signed.exe
Than was the problem with the touch ... it dont work.
After this i tryed many ruu's ....no way.
Than i downloaded from htcdev - PC4910000_Buzz_Froyo_hboot_1.02.0000_R3.exe and flashed and unlocked with Unlock_code.bin
I was thinking i would be able to unlock and update every rom

Pretendde said:
I downgraded with the standard buzzdowngrade.zip package, step1 but the goldcard-step fail.....i flashed after hboot downgrade RUU_Buzz_Vodafone_DE_1und1_1.19.186.3_Radio_13.45.55.24_3.35.15.31_release_133745_signed.exe
Than was the problem with the touch ... it dont work.
After this i tryed many ruu's ....no way.
Than i downloaded from htcdev - PC4910000_Buzz_Froyo_hboot_1.02.0000_R3.exe and flashed and unlocked with Unlock_code.bin
I was thinking i would be able to unlock and update every rom
Click to expand...
Click to collapse
Ok so fastboot works, good good. Do you have clockworkmod recovery installed? If not follow my thread for rooting hboot 1.02.0000 and install clockworkmod but go no further.
Also just for your information the ruu will not install because of
1. Your honor is higher than the ones in the RUU,
2 your bootloader is unlocked.
We need to downgrade you to the WWE rom with hboot 1.01.0001 and hopefully that will restore your touch panel to working order
Sent from my HTC Sensation using Tapatalk

Clockworkmod recovery is installed, rooting hboot 1.02.0000 o.k.
and now?

Pretendde said:
Clockworkmod recovery is installed, rooting hboot 1.02.0000 o.k.
and now?
Click to expand...
Click to collapse
ok so what we want to do know is downgrade your hboot to 1.01.0001 so to do that we need your misc partition to be edited. as such i would like you to boot the phone into clockworkmod recovery and connect it to the pc with a usb cable. windows should install the drivers if it has not done so already.
next you will need to set up your command prompt for using adb/fastboot commands.
then we will pull a copy of your misc partition to your sdcard and then copy it into your windows adb folder.
then you will upload that image to me, i will make the necessary changes and then re-upload for you.
then you will flash it to the phone all going well, re-lock your bootloader and then downgrade your hboot and rom and hopefully regain touch input
then as an extra if you want to use a rooted version of that german ruu you were trying to flash i can make you a "safe to flash" version
ok, so....
step 1. Connect your wildfire up to your pc In clockworkmod recovery mode.
step 2. open a command prompt within your adb/fastboot folder. (the same one you used to flash clockworkmod recovery)
step 3. enter the following commands one at a time. copy paste is recommended.
Code:
adb shell
su
cat /dev/mtd/mtd0 > /sdcard/misc.img
exit
exit
adb pull /sdcard/misc.img misc.img
step 4. Upload this file to somewhere like dropbox or media fire and then send me a link to it.

in command prompt
su
/sbin/sh: su: not found
what i do wrong?

Pretendde said:
in command prompt
su
/sbin/sh: su: not found
what i do wrong?
Click to expand...
Click to collapse
OK just skip that and move onto the next bit.
Sent from my Nexus 7 using Tapatalk

I attached this file here, i hope it is o.k.
It takes a while until i found out to mount the SD card before

Pretendde said:
I attached this file here, i hope it is o.k.
It takes a while until i found out to mount the SD card before
Click to expand...
Click to collapse
okey dokey, here is your new misc image. extract it into your adb folder.
i have edited this so it will re-lock your bootloader automatically once you have flashed it. one problem solved
also download this package, it has some tools you will need and the WWE rom you need to flash
lastly we need to make a goldcard. this will be hard given that your touch screen is non-functional. as such you will need a different, working android phone and YOUR sdcard. this trick is sdcard specific so dont swap them about
ok once you are ready with the right stuff, do these steps.
step 5. now we need to make a gold card. if you already have one, you can skip this part. first using your working android phone, download and install Goldcard helper from the android market. Run the app and copy down your SD cards reverse cid. double check it
step 6. now go to this website here and enter in your reverse cid. it will then let you download a goldcard.img.
step 7. now go back to the package you downloaded earlier with the WWE rom (named 1.01.zip) in it and run the goldcardtool.exe, this will flash the goldcard to your sd card. Warning! this will format your card!! in order to achieve this you will have to mount the sdcard from clockworkmod recovery to the computer, use mount usb storage and not mount sdcard.
step 8. once that is done we are now ready for the final push

Now the gold card is ready, i leave al the data on the goldcard, its not been formatted. Goldcard tool says, G: Goldcard is now ready.
The new misc image, must be copy to the phone ?

Pretendde said:
Now the gold card is ready, i leave al the data on the goldcard, its not been formatted. Goldcard tool says, G: Goldcard is now ready.
The new misc image, must be copy to the phone ?
Click to expand...
Click to collapse
ok from here copy the Nmisc.img to your sdcard and do not rename it, leave it on the sd card within no folders.
then connect up the phone in clockworkmod recovery again, and mount the sdcard with mount sdcard and not usb mass storage.
lastly make sure that the 1.01.zip is in your adb folder.
issue the following commands.
Code:
adb shell
(your shell symbol should be a #)
flash_image misc /sdcard/Nmisc.img
exit
(now it should not be a #)
adb reboot bootloader
The phone should not reboot into bootloader and should say at the top locked OOW.
This is ok, if it does not say this then your misc image was not flashed.
if all is well issue these commands.
Code:
fastboot oem rebootRUU
fastboot flash zip 1.01.zip
This will state an error, and that it needs to be reflushed. this is what we want, if any other issue your goldcard may have failed.
repeat the last command to reflush.
Code:
fastboot flash zip 1.01.zip
(this will take a while.)
fastboot reboot
the phone should reboot into the WWE stock rom and hopefully your touch screen will be working again. if it is proceed to s-off with revolutionary here ignore all but revolutionary and then if you want the german ruu as a safe flash rom send me a link to the ruu and I will make it. but it make take a few days.
im at work atm so my replys will be delayed pal, good luck

INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 63.656s
i flashed 3 times....

Pretendde said:
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 63.656s
i flashed 3 times....
Click to expand...
Click to collapse
Your gold card has failed. Format the sdcard and then reissue the fastboot commands.
Sent from my HTC Sensation using Tapatalk

Yes the goldcard was bad, now its okay but n ow a new error :
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 56.078s
flashed 5 times ...same error

Pretendde said:
Yes the goldcard was bad, now its okay but n ow a new error :
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 56.078s
flashed 5 times ...same error
Click to expand...
Click to collapse
Does your bootloader still say locked?
Sent from my HTC Sensation using Tapatalk

heavy_metal_man said:
does your bootloader still say locked?
Sent from my htc sensation using tapatalk
Click to expand...
Click to collapse
yes
*** locked (00w) ***

[Q&A] Semi bricked Desire

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.