Develop Bugs

Issue with clockworkmod...

Hi...
Yesterday i've installed cwm 3.x.x.x and flashed cm nightly build #18. Today i've downgraded the cwm cause i couldn't get any connection to my dhd with the neew recovery (fastboot commands just came back with an error i can't remember atm). The downgrade was flashed through terminal emu, code:flash_image recovery /sdcard/clockwork-recovery2.1.5.3.img and went fine. I then changed the splashscreen through fastboot as i have before and no problem here. Then i desided to make my own splash in gimp and when i tried to flash that it failed and wouldn't write and now i have this error in cwm:
E:can't mount cache:recovery/command
E:can't mount cache:recovery/log
E:can't open cache:recovery/log
I've tried to flash back to cwm 3.x.x.x through terminal emu and then use rom manager to flash 2.1.5.3, but still same issue when booting into cwm and still a fail when trying to flash splashscreen (and yes the cwm changes beween flashes in terminal, green 2.1.5.3, orange 3.x.x.x)
Is it because off cm7 build #18 that i can't use cwm 2.1.5.3 to flash through fastboot.
I havn't tried another rom like leedroid to see if that changes, i'm a tad afraid that it won't wipe nor flash cause of this error and hence brick my phone.
I've got a nandroid from the beginning of this month, but thats a cwm 2.1.5.3 backup, can that be restored in cwm 3.x.x.x?
Ohh cuold it be that i've morphed some icons plus FM radio skin?
Any help is welcome
TIA Dousan... Aka Martin...
e:the error i get when flashing splash1 with fastboot:
writing 'splash1'... FAILED (remote: image update error)
e2: Fixed the splash1 error - image had the wrong dimensions... :S

Dousan said:
Hi...
Yesterday i've installed cwm 3.x.x.x and flashed cm nightly build #18. Today i've downgraded the cwm cause i couldn't get any connection to my dhd with the neew recovery (fastboot commands just came back with an error i can't remember atm). The downgrade was flashed through terminal emu, code:flash_image recovery /sdcard/clockwork-recovery2.1.5.3.img and went fine. I then changed the splashscreen through fastboot as i have before and no problem here. Then i desided to make my own splash in gimp and when i tried to flash that it failed and wouldn't write and now i have this error in cwm:
E:can't mount cache:recovery/command
E:can't mount cache:recovery/log
E:can't open cache:recovery/log
I've tried to flash back to cwm 3.x.x.x through terminal emu and then use rom manager to flash 2.1.5.3, but still same issue when booting into cwm and still a fail when trying to flash splashscreen (and yes the cwm changes beween flashes in terminal, green 2.1.5.3, orange 3.x.x.x)
Is it because off cm7 build #18 that i can't use cwm 2.1.5.3 to flash through fastboot.
I havn't tried another rom like leedroid to see if that changes, i'm a tad afraid that it won't wipe nor flash cause of this error and hence brick my phone.
I've got a nandroid from the beginning of this month, but thats a cwm 2.1.5.3 backup, can that be restored in cwm 3.x.x.x?
Ohh cuold it be that i've morphed some icons plus FM radio skin?
Any help is welcome
TIA Dousan... Aka Martin...
e:the error i get when flashing splash1 with cwm 2.1.5.3:
writing 'splash1'... FAILED (remote: image update error)
Click to expand...
Click to collapse
CWM 2.x cannot access ext4 partitions, so whilst you've got gingerbread on there it will throw up all kinds of errors, you should be good to restore a cwm 2.x backup with cwm 3.x but you will have problems restoring the whole backup as cwm 3.x can't write /boot at present

ghostofcain said:
CWM 2.x cannot access ext4 partitions, so whilst you've got gingerbread on there it will throw up all kinds of errors, you should be good to restore a cwm 2.x backup with cwm 3.x but you will have problems restoring the whole backup as cwm 3.x can't write /boot at present
Click to expand...
Click to collapse
Cheers mate, thanks for the answer... Had a feeling it might be something with the new ext4...
Just weird i could flash one splashscreen today after reverting to cwm 2.1.5.3?
Will stay with the new CM7 builds, really nice and smooth
Anyway was just afraid of bricking the phone if did have to restore a nandroid.
So it's the same story with the fastboot commands or what, not working with ext4?

Dousan said:
So it's the same story with the fastboot commands or what, not working with ext4?
Click to expand...
Click to collapse
shouldn't think so, certainly fastboot is working fine for me on cm7

Lol, noob me i was trying to flash a corrupt splashscreen (not the right dimensions) all fixed and the fastboot commands works for me aswell
Back on track... Thanks again for your help

[Q] Help! I am stuck, Can't flash any Rom on my Htc Desire

Whenever I try to flash a rom, i get this error:
E:Can't chown/mod /system/etc/init.d (No such file or directory)
E:Failure at line 64: set_perm etc.
Installation aborted!
The roms i have tried are: Pinky's Rom, Leedroid, Official(rooted) rom
Hboot; Version: 0.93
I can't figure out what to do! Someone please help!

Did you root with alpharev?
If not do it and install alpharev recovery as you root it and will be fine.
I had same issue and that fixed it
Sent from my HTC Desire using XDA Premium App

08r3308 said:
Did you root with alpharev?
If not do it and install alpharev recovery as you root it and will be fine.
I had same issue and that fixed it
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
You cannot root with alpharev! Alpharev seets you s-off. Before alpharev can do this, you need root access. This you get by rooting your phone e.g. with unrevoked. Alpharev does not have an own recovery, it is clockworkmod.
@Umair.K:
Did you root your phone already?

So you run unrevoked then alpharev? Or only unrevoked? Because with mine i had to run untrvoked then alpha to be able to use recovery
Sent from my HTC Desire using XDA Premium App

08r3308 said:
So you run unrevoked then alpharev? Or only unrevoked? Because with mine i had to run untrvoked then alpha to be able to use recovery
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Yes. First unrevoked to get root + recovery and then alpharev to s-off.

Ok thank you i hope this helps op as well
Sent from my HTC Desire using XDA Premium App

Oh sorry should have given all those details before, here you go:
Bravo Pvt3 S-off
Hboot- 0.93.1000
Radio: 5.09.00.20
And as you can see, I am rooted and plus S-off with Alpha rev... The weird part is that I can flash Cm7-Stable mod and its working but whenever i try to flash any other rom, i get the error!
E:Can't chown/mod /system/etc/init.d
(No such file or directory)
E: Failure at line 65:
set_perm_recursive 0 0 0777 0777 SYSTEM:etc/init.d
Installation aborted.
and the last rom i tried to flash was "Bravo_WWE_2.29.405.5_v5"

Umair.K said:
Oh sorry should have given all those details before, here you go:
Bravo Pvt3 S-off
Hboot- 0.93.1000
Radio: 5.09.00.20
And as you can see, I am rooted and plus S-off with Alpha rev... The weird part is that I can flash Cm7-Stable mod and its working but whenever i try to flash any other rom, i get the error!
E:Can't chown/mod /system/etc/init.d
(No such file or directory)
E: Failure at line 65:
set_perm_recursive 0 0 0777 0777 SYSTEM:etc/init.d
Installation aborted.
and the last rom i tried to flash was "Bravo_WWE_2.29.405.5_v5"
Click to expand...
Click to collapse
You have partition for CM7, so any sense rom don't have enough space in /system.
Repartition your phone (look in alpharev site) as sense (default) partition. /system must be 250mb
Sent from my pocket using a pen

mendozinas said:
You have partition for CM7, so any sense rom don't have enough space in /system.
Repartition your phone (look in alpharev site) as sense (default) partition. /system must be 250mb
Sent from my pocket using a pen
Click to expand...
Click to collapse
Oh Thankyou soo much man! Thats exactly what I didn't think of before
But could you give me a guide line on how to partition my sd card like that? Because I purchased the phone from someone else, and he had done all the work himself!
It would be really helpful! Thanks!

You cant partition your sd like that ... you should flash STOCK HBOOT... find it at Alpha Rev pages... and there you will find diferent HBOOT's and everything will be clear for you... You partition your SD for needs of diferent ROM's but when it comes to HBOOT there is only few of them... I suggest CM7 HBOOT.. the one with 130 Mb for system, but pay attention on which ROM you flash...

bluzermajstor said:
You cant partition your sd like that ... you should flash STOCK HBOOT... find it at Alpha Rev pages... and there you will find diferent HBOOT's and everything will be clear for you... You partition your SD for needs of diferent ROM's but when it comes to HBOOT there is only few of them... I suggest CM7 HBOOT.. the one with 130 Mb for system, but pay attention on which ROM you flash...
Click to expand...
Click to collapse
Ha ha.
He is having problems because of CM7 hboot and you suggest to flash it? He needs stock hboot.
Sent from my pocket using a pen

bluzermajstor said:
You cant partition your sd like that ... you should flash STOCK HBOOT... find it at Alpha Rev pages... and there you will find diferent HBOOT's and everything will be clear for you... You partition your SD for needs of diferent ROM's but when it comes to HBOOT there is only few of them... I suggest CM7 HBOOT.. the one with 130 Mb for system, but pay attention on which ROM you flash...
Click to expand...
Click to collapse
Alright thats quite clear but the instructions aren't quite clear on Alpha Rev's page!
It says "If you are already S-OFF, you can get our newest patched HBOOTs from here. (without going through the entire procedure again).
Please read the entire table and pick the partition table with the correct sizes for your ROM. One easy way to switch partition tables, is to nandroid backup,
and verify that the sizes of your backup are indeed the ones listed in the table (or smaller), and restore after flashing hboot"
-So afterwards I tried to use the PB99.img by placing it on the root of my sd card and flashing it via recovery, but didn't work!
-Then i tried to use "Android Flasher(1.76)" to flash the new hboot, but that failed aswell! :S
So do i have to repeat the whole S-off procedure again or do i need to use cmd and type in commands to flash a new H-boot? This is getting confusing :O!

If your phone is s-off, you do not have to s-off again. To recognize if your phone is s-off:
1.) Splash screen is the joker
2.) If you boot into hboot (starting with pressed volume down button) first line should be "alpharev" and in the second line the last should be "s-off".
When you use android flasher, you must not use the file PB99_IMG-XXX.zip. You have to use the file bravo_alphaspl-xxx.img ("xxx" stands for the hboot you want).
When you use the method with PB99IMG_XXX.zip, you have to rename the file into PB99IMG.zip and copy it to the root of you sd-card (just watch out, you do not rename it to PB99IMG.zip.zip, because windows hides known file extensions).
Wether you decide for android flasher or directly the method with the zip files, make a complete nandroid backup first. Then download the hboot you want and you need for the method you decided (Do not forgot to check md5 after downloading the hboot!) and run the update.
How you do this:
Android flasher:
1.) Make sure you have usb debug mode on, the behaviour when usb is connected is on "only load" and you have installed hboot dand htc drivers
2.) Connect the phone with your computer
3.)
4.) Choose the file bravo_alphaspl-xxx.img and run the update (android flasher will say you when it's finished)
PBIMG99.zip:
(...)Start the phone in HBOOT mode (VolDown+POWER) to flash the HBOOT without a PC.
Click to expand...
Click to collapse
(from alpharev website)
In both methods now boot into recovery, wipe everything and restore the nandroid backup.
No warranty for any damage!

I get this while using android flasher
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* daemon started successfully *
fastboot.exe flash hboot hboot.img
< waiting for device >
sending 'hboot' (512 KB)...
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
OKAY [ 0.161s]
finished. total time: 0.248s
rebooting into bootloader...
OKAY [ 0.096s]
finished. total time: 0.096s
finished. total time: 0.096s
erasing 'cache'...
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
Del hboot.img
fastboot.exe reboot
rebooting...
Is this right or is there something wrong?
finished. total time: 0.000s

Umair.K said:
I get this while using android flasher
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* daemon started successfully *
fastboot.exe flash hboot hboot.img
< waiting for device >
sending 'hboot' (512 KB)...
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
OKAY [ 0.161s]
finished. total time: 0.248s
rebooting into bootloader...
OKAY [ 0.096s]
finished. total time: 0.096s
finished. total time: 0.096s
erasing 'cache'...
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
Del hboot.img
fastboot.exe reboot
rebooting...
Is this right or is there something wrong?
finished. total time: 0.000s
Click to expand...
Click to collapse
Download and install the app quick system info pro:
http://www.appbrain.com/app/quick-system-info-pro/org.uguess.android.sysinfo.pro
After starting you can compare the showed partition sizes to these of downloaded hboot. If it's fitting, everything is all right. I remember i had the same "issue" and everything is fine.

hi, i'm new to tis, i've root my phone (i thought so) ...
i've root using Unrevoked and S-OFF using AlphaRev....
---AlphaRev---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051D
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
Aug 10 2010, 17:52:18
i've done it for quite a while, but until now i still cant flash any ROM to my phone... really meant it, cant flash any ROM...
when i try to flash, smthing like this pop out...
--Installing: SDCARD:update-cm-6.1.1-Desire-signed.zip
E:Can't find MISC:
Finding update package...
Opening Update package...
Installing update...
Welcome to CyanogenMod-6.1.1-Desire!
assert failed: write_raw_image('/tmp/boot.img'.'boot')
E:Error in /sdcard/update-cm-6.1.1-Desire-signed.zip
(status 7)
Installation aborted.
is it because of my SD Card...??? Im using Samsung 16G, but i've tried using few other brand of 2Gb SD Card, still unsuccessfull...
can anyone help me...??? sorry coz i'm a noob...

MatDrOiD said:
You cannot root with alpharev! Alpharev seets you s-off. Before alpharev can do this, you need root access. This you get by rooting your phone e.g. with unrevoked. Alpharev does not have an own recovery, it is clockworkmod.
@Umair.K:
Did you root your phone already?
Click to expand...
Click to collapse
you don't need a rooted rom for revolutionary or alpharev... When the utility runs it gains temp root and is able to continue. The proof is in the wildfire AND me running it straight after I used a RUU on my Desire and used it without rooting

HTC Desire (ojan) said:
is it because of my SD Card...??? Im using Samsung 16G, but i've tried using few other brand of 2Gb SD Card, still unsuccessfull...
can anyone help me...??? sorry coz i'm a noob...
Click to expand...
Click to collapse
I doubt it's your sd-card. Okay since you've got S-OFF lets flash a different recovery. Follow these steps:
All you have to do is downlaod fastboot commander, and the java jdk for the tool to work.
Then, download the Ra Desire recovery
Once you've got that, but into fastboot (power off, hold back key & power), and plug in via USB.
run fastboot commander, navigate to the "misc" tab, select "recovery" "boot" "userdata" "system" "cache" "sd-ext"and nothing else and click "erase chosen partition(s)", then go back to the "Hboot, radio & rec" tab, choose "recovery", and find the recovery.img you have downloaded.
Then, simply press "flash recovery"
Once that's done, power off and reboot into recovery (power off, volume down & power, then use volume down key to navigate to RECOVERY and press power to select)
Then flash a ROM of your choice. For me this is the best way to flash new ROMs since it's a good, clean install and you don't get remaining crap left over from old ROMs

Did you wipe everything before flashing the rom?
Swyped from Oxygen with Transparent XDA App

yes, i'll try this and let u know if its working... thanks...
by the way, i've wipe everything before i try to flash a new ROM, wiping DalvikCache is unsuccesfull...

Error in Recovery and Flashing! Help!

Ok, I’m a new Desire user and rooted the phone using unrevoked 3.32, I went into ClorkworkMod 2.5.0.7 and this is the error:
E:Can’t find MISC:
E:Can’t mount CACHE:recovery/command
E:Can’t find MISC:
E:Can’t mount CACHE:recovery/log
E:Can’t find MISC:
I followed the steps, and I don’t know what I did wrong. I can’t flash a new ROM (Oxygen 2.1.2). Here’s the error:
Installing update…
assert failed: write_raw_image("/tmp/boot.img"."boot")
E:error in /sdcard/update-oxygen-2.1.2-signed.zip
(Status 7)
Installation aborted
Can anyone guide me?

Flash another recovery in fastboot (if you're s-offed) or with unrevoked if you're s-on

I tried but it does not work with the flash process fails AmonRa finish
root its clockwork ..
Bravo PVT4 SHIP s-on
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27

same problem with my Desire.
I found the recovery-RA-desire-v2.0.1 here work for my desire
flash it using Unrevoked 3.21 here with the custom image option, just point it to the recovery-RA-desire-v2.0.1.img and rerun the root.
then you can flash new rom with no error (status 7)

Unrevoked usually flashes clockworkmod recovery 2.x.x.x. This version 2 does not work with pvt4 versions of the desire:
http://www.roms-au.com/installation/rooting/pvt4-issues/
Flashing amonra recovery will solve your problem. If you really want clockwork mod, you should download clockwork since version 3 oder even 4:
http://forum.xda-developers.com/showthread.php?t=1112658&highlight=recovery

[Q] I think I bricked my DHD?

Hi all,
I have a previously rooted DHD that won't boot beyond the white HTC load screen.
The problem is that a number of things were tried on the phone to get it working again, and I think it may have made things worse, like unrooting it.
I can access the stock bootloader, this is what I get:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Click to expand...
Click to collapse
When I select Recovery, ClockworkMod Recovery v5.0.1.0 starts but also has some error messages:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
I think these errors are because unfortunately the SD card was wiped when trying to fix it
I've tried connecting it to a Windows PC to run the RUU but got an error about the Customer ID.
I don't care if the phone gets unrooted, or if it has an old stock rom, I just want to get the phone working again.
Does anyone have any hints for how I can fix this phone?
EDIT: I found out that this is my CID: VODAP102. Maybe I just need to correct RUU? Does anyone know which one that may be?

You have a Vodaphone German CID so if you don't find a Vodaphone German RUU for desire HD that is the same or higher from your misc version you won't be able to fix your phone.You could try to extract a rom.zip from an {RUU}.exe and you add or change your CID number with yours by editing the android-info.txt file inside the rom.zip in order you be able to flash it from your sdcard or by using the command fastboot flash zip rom.zip.(If you would like to follow this path I would suggest you to make a goldcard before you flash the zip).
If you have not a working rom or at least a working adb shell in order you make a goldcard you should try to install a custom rom to create the goldcard (I don't know if you can create a goldcard from recovery).
If any of these can help you I think the only solution you could try (and the best in my opinion) is to S-OFF your device and you change the vodaphone crap cid with SuperCID or one of your choice.After that you can install any RUU you like.
I have answered a lot of times how to S-OFF this device.You can find the answer here.
The situation you are not rooted is not a good thing because you won't have a root shell either.You could try rerooting your current rom from recovery by flashing a Superuser or SuperSU zip.You can find the latest flashable zip of SuperSU here.
** However if you want to make this proccess you must have enabled USB debugging (at least to create a goldcard as the manual describes) **
We could also help you a little bit more if you gave us the results that prints the command fastboot getvar all.
You can find Desire HD RUU's here.

[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.