Database Info

HTC Desire S Clockwork Mod issues

Hi,
I'm running an HTC Desire S S-ON but unlocked via the htc dev site.
HBOOT 2.00.0002
Revolutionary CWM v4.0.1.4
Previously I was on the stock Android 2.3.5 and HTC Sense 3.0 from an OTA update.
I used Clockwork to do a Nadroid backup and tried to install Cyanogen 7.1 this got stuck in a boot loop and I then found I couldn't restore to the backup or install any other ROMs.
I have been searching everywhere and I can't find a method to de-brick my phone that works, can anyone point me in the right direction please?
Cheers,
Matt H

While your phone is s-on you can only flash stock roms.
You need to s-off your phone first
Sent from my Desire S using XDA App

extract boot.img from the CyanogenMOD7.zip and flash it with fastboot:
Code:
fastboot flash boot {path to the file on your PC}\boot.img
You will need fastboot configured - link in my signature.

eyahl said:
While your phone is s-on you can only flash stock roms.
You need to s-off your phone first
Sent from my Desire S using XDA App
Click to expand...
Click to collapse
not true, you only need to flash the boot image separetly

amidabuddha said:
extract boot.img from the CyanogenMOD7.zip and flash it with fastboot:
Code:
fastboot flash boot {path to the file on your PC}\boot.img
You will need fastboot configured - link in my signature.
Click to expand...
Click to collapse
Ahhh that makes more sense now, I had only half understood a thread I had read earlier,
Thanks

loading the boot.img via fastboot comes back as a success on the command line, however it still hangs at the 3 mobile loading screen.

Reflash the ROM and the boot.img from the ZIP after doing a full wipe.

Just to be clear, I have wiped the phone using clockwork, and reflashed using fastboot from the commandline, this is still hanging on 3 mobile splash screen, I am starting to think I am cursed...
Cheers,
Matt H

Try 4ext
Sent from my HTC Desire S using XDA Premium App

given that I can't actually boot my phone to install 4ext from the market, is there any way of flashing it in place of clockwork? Or is there any way of just restoring it to the state before I flshed clockwork to it?

shrome99 said:
Reflash the ROM and the boot.img from the ZIP after doing a full wipe.
Click to expand...
Click to collapse
This should do it.
matthearn said:
Just to be clear, I have wiped the phone using clockwork, and reflashed using fastboot from the commandline, this is still hanging on 3 mobile splash screen, I am starting to think I am cursed...
Click to expand...
Click to collapse
Take a deep breath You phone is fine just need the proper components
Make a full wipe (system, data, cache, dalvik cache, boot) from the recovery
Install the custom ROM again (important)
Reboot to bootloader from the recovery power menu
Use the fastboot command to flash the boot.img
Reboot the phone normally and wait (it can take up to 10 minutes to boot)
Report here

amidabuddha said:
Take a deep breath
Click to expand...
Click to collapse
MOST IMPORTANT STEP. Be calm

Thanks everyone for your help my Desire S is now Cyanogenmodded .
I think next week I may write a step by step for doing this on linux, once I have got over the trauma...

First posting with a problem but done a lot of reading and can't find my answer...
I have a Desire S which had the initial telco branding splash screens for boot and animation as well as all the apps they install.
Following the excellent guide here by nodeffect for beginners I used Revolutionary to S-Off and install CWM then flashed su-2.3.6.3-efgh-signed.zip to get root.
I then followed this thread by vampire36 about flashing a rom the perfect way but did not have the option to format boot in cwm so carried out all the other steps and I have Reaper 2.0 flashed but still with the initial boot splash screen of the telco when the phone initially powers on.
Two questions...
1. Why would I not get the option in cwm to format boot ?
2. Is this why the initial splash screen still remains and do i need to use adb to flash a new boot.zip through fastboot ?

RevheadKev said:
Two questions...
1. Why would I not get the option in cwm to format boot ?
2. Is this why the initial splash screen still remains and do i need to use adb to flash a new boot.zip through fastboot ?
Click to expand...
Click to collapse
1. There is no need to format boot on devices with flash memory (honestly I do not know exactly why, you can make a research if you like).
2. The splash screen is just a picture but is stored on another partition, so is not affected by installing other components. If you want to change it you can use Android Flasher and any image you like.

i cant do Recovery

hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.

Snow201 said:
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Click to expand...
Click to collapse
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:

FatherD said:
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
Click to expand...
Click to collapse
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?

Snow201 said:
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Click to expand...
Click to collapse
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!

osugsxr said:
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
Click to expand...
Click to collapse
NVM, there is no recovery for HTC at all, only Galaxy and some more. what i need to do?

I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium

k1llacanon said:
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)

Snow201 said:
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Click to expand...
Click to collapse
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium

k1llacanon said:
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?

Snow201 said:
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Click to expand...
Click to collapse
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img

frdd said:
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
Click to expand...
Click to collapse
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?

Snow201 said:
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Click to expand...
Click to collapse
If you have working ADB and fastboot working (there is a sticky by user fibsib that explains this) you can make sure your phone isnt really just trying to boot the OS and failing rather than trying to enter recovery with the command
Code:
adb reboot recovery
But anyways figure out which version you have before doing anything more, flash the wrong stuff and you could break stuff. There are good info here as to how to see if you have the Ville=Z520e=S4 processor model or the Ville C2/Z560e/S3 processor model.
Then download a recovery for your phone model and install it with this command from your computer
Code:
fastboot flash recovery nameofrecoveryyoudownloaded.img
Should work.

have you actually flashed a recovery yet?
which one and how did you do it?

Make sure you have your phone updated to the latest software version before you root. Download system update OTA and click update.
Otherwise you will have issues.
I am rooted T-Mobile phone with original software 1.54 and still can not do recovery or update, it is probably me but it is difficult.
If you are in the US, make sure you use the US version in the development section after you upgrade your phone. Update then try to root it might be easier.

do i need to flash boot ?

hi guys
when i was flashing roms before i had to manually flash boot.img in fastboot since i didnt have twrp
but i noticed the kernel is the same date as the rom i just flashed today (cm10)
do the new CWMs flash the boot.img ?

You need to fastboot because there is no s off
Sent from my HTC One S using xda premium

qwerty warrior said:
hi guys
when i was flashing roms before i had to manually flash boot.img in fastboot since i didnt have twrp
but i noticed the kernel is the same date as the rom i just flashed today (cm10)
do the new CWMs flash the boot.img ?
Click to expand...
Click to collapse
CWM has always been able to flash boot.img with the ROM if you fastboot booted into CWM, like so: (provided the clockwork-recovery-version-blabla.img file is in your current dir ofc)
Code:
fastboot boot clockwork-recovery-version-blabla.img
Maybe CWM can flash the boot.img on certain Hboot versions, what is yours?
Ooh is there a new CWM version for ville?

frdd said:
CWM has always been able to flash boot.img with the ROM if you fastboot booted into CWM, like so: (provided the clockwork-recovery-version-blabla.img file is in your current dir ofc)
Code:
fastboot boot clockwork-recovery-version-blabla.img
Maybe CWM can flash the boot.img on certain Hboot versions, what is yours?
Ooh is there a new CWM version for ville?
Click to expand...
Click to collapse
from what i read only TWRP had the ability to flash boot.img without going into fastboot and using ADB
but when i went into rom manager it said new clockworkmod 5.8.3.1 so i updated
and noticed the new kernel after a normal rom update in recover (CWM)

qwerty warrior said:
from what i read only TWRP had the ability to flash boot.img without going into fastboot and using ADB
but when i went into rom manager it said new clockworkmod 5.8.3.1 so i updated
and noticed the new kernel after a normal rom update in recover (CWM)
Click to expand...
Click to collapse
Na CWM can do it if booted the way i described. Kind of defeats the purpose though as you still need to have a computer hooked up, might as well fastboot flash the boot image. 5.8.3.1 is a couple of months old. But check which Hboot version you have, that might explain why it works for you. You can also check your kernel version with ADB by the way, like so:
HTML:
adb shell uname -a

[Q] Problem with instalation Flinny b22 [s-on]

Hi everyone,
i try install flinny cm 10.1 b22 on my HTC Desire S with
S-ON;
HBOOT-2.02.0002;
RADIO-3831.19.00.110
EXT Recovery;
I wiped cache and sys. data, and install *zip ROM but when i reboot,
device doesn't start => first run white HTC Logo and after stuck on black screan.
I don't know what i have to do now, because i can't run my device now. But i still want the best rom - flinny.
Sry for my english,
regards

dzordzan said:
Hi everyone,
i try install flinny cm 10.1 b22 on my HTC Desire S with
S-ON;
HBOOT-2.02.0002;
RADIO-3831.19.00.110
EXT Recovery;
I wiped cache and sys. data, and install *zip ROM but when i reboot,
device doesn't start => first run white HTC Logo and after stuck on black screan.
I don't know what i have to do now, because i can't run my device now. But i still want the best rom - flinny.
Sry for my english,
regards
Click to expand...
Click to collapse
assuming- when s- on- you flashed boot.img of that rom- via fastboot,
your device may be one of those- " blessed" with non sony panel,
and therefore having issues with < non sense > JB roms...
such mantra mate- you`re not the only one with this problem though...
In general section of the forum there is a thread devoted in particular
to the non sony panel topic- check it up
Just restore the backup of a previous rom ( you surely`ve made- don`t you)
and prepeare yourself for the next rom flashing, with more knowledge,
knowing now about that particular secret your devie is having.....

theorizing if "someone" did not do a backup, what this guy have to do now ?
p.s
i had before cm 10.1 flinny (build 21) i had then s-off and older hboot - but i have to return device on guarantee and i restore to s-on, new hboot and ruu ROM. And yesterday they give me back repaired device so i try install again flinny and here i'am now
Now i download ICS_DS v8.0 maybe this rom will run
Regards

dzordzan said:
theorizing if "someone" did not do a backup, what this guy have to do now ?
p.s
i had before cm 10.1 flinny (build 21) i had then s-off and older hboot - but i have to return device on guarantee and i restore to s-on, new hboot and ruu ROM. And yesterday they give me back repaired device so i try install again flinny and here i'am now
Now i download ICS_DS v8.0 maybe this rom will run
Regards
Click to expand...
Click to collapse
But you did flash the boot.img in fastboot?

teadrinker said:
But you did flash the boot.img in fastboot?
Click to expand...
Click to collapse
Flash boot.img ?
sorry but i don't know exactly what's mean
maybe i do this i don't know

dzordzan said:
Flash boot.img ?
sorry but i don't know exactly what's mean
maybe i do this i don't know
Click to expand...
Click to collapse
Because you're s-on, you can't flash the /boot partition from recovery, so after installing a new rom, kernel or update, you have to put your phone in fastboot mode (bootloader, saying fastboot usb) and use the command:
fastboot flash boot boot.img
(use the boot.img extracted from the zip of the rom or kernel you installed)
(for more information read guides to installing roms for s-on)

[Q] Help with ROM needed (maybe trivial ...)

Oh my ... I have now spent sure 6 or 7 hours trying to figure this out. If anybody could help me, please ?
This is not my first attempt at root, and I have been succesful with my HTC Wildfire S and installed various Custom ROMs on that, all fine.
Now I have a Desire S, that I managed to unlock (UNLOCKED), which is still S-ON, and, from all I can tell, rooted (superuser app does not complain about anything), I had installed 4EXT on the HTC Sense Stock rom that came with the phone, and that installed fine and no complaints.
HBOOT is 2.02.0002, which many people say requires downgrading, but then in other places it is said, this is not strictly necessary.
Now the following:
The ONLY recovery I have been able to install is recovery-clockwork-5.0.2.0-saga.img (using adb flash recovery ... under ubuntu 12.04).
That seems to go well, and the CM recovery comes up fine and I can do backups and so on. If I try to flash 4EXT_Recovery_Touch_v1.0.0.5_RC5 or RC9 and go into recovery, the phone remains stuck in the white boot screen (Telekom branding, it seems). Oh well ... so no 4EXT and back to CM. No problem, just strange.
Now, with S-ON it SHOULD be possible to install custom ROMs, like flinnycm101_saga_22.zip. so i pushed this onto /sdcard, and also extracted the boot.img from this zip. In recovery I can install the .zip seemingly fine, no errors, and then, since this is S-ON, I
sudo adb flashboot flash boot flinnycm101_saga_22.img
(i renamed it from boot.img to that to keep track, should not be a problem, right?). and that goes over well, too. I do not know how many times I have already erased cache, dalvik, factory, battery. all to no avail. when i reboot the phone remains stuck in the white boot screen. at least i would have expected to get the CM spash screen (like that rotating wheel or something like that), but that may not be a problem.
I have tried a few other roms (devilkin 11.0 and carbon) with this method. same, same ...
I really don't know ... sheesh ... any ideas ? And if it boils down to downgrading: can I do that on ubuntu ? All the guides I have found so far required Windows.
Sorry ... clearly I am not a developer. If somebody could nudge me into the right direction ? I am quite happy to do my homework, but not really sure anymore where else to look. This SHOULD work, from all I found in the internet.
And ... I hope this is not the wrong forum. If so, really sorry ...
1000 thanks
Ingo

ipk1 said:
Oh my ... I have now spent sure 6 or 7 hours trying to figure this out. If anybody could help me, please ?
This is not my first attempt at root, and I have been succesful with my HTC Wildfire S and installed various Custom ROMs on that, all fine.
Now I have a Desire S, that I managed to unlock (UNLOCKED), which is still S-ON, and, from all I can tell, rooted (superuser app does not complain about anything), I had installed 4EXT on the HTC Sense Stock rom that came with the phone, and that installed fine and no complaints.
HBOOT is 2.02.0002, which many people say requires downgrading, but then in other places it is said, this is not strictly necessary.
Now the following:
The ONLY recovery I have been able to install is recovery-clockwork-5.0.2.0-saga.img (using adb flash recovery ... under ubuntu 12.04).
That seems to go well, and the CM recovery comes up fine and I can do backups and so on. If I try to flash 4EXT_Recovery_Touch_v1.0.0.5_RC5 or RC9 and go into recovery, the phone remains stuck in the white boot screen (Telekom branding, it seems). Oh well ... so no 4EXT and back to CM. No problem, just strange.
Now, with S-ON it SHOULD be possible to install custom ROMs, like flinnycm101_saga_22.zip. so i pushed this onto /sdcard, and also extracted the boot.img from this zip. In recovery I can install the .zip seemingly fine, no errors, and then, since this is S-ON, I
sudo adb flashboot flash boot flinnycm101_saga_22.img
(i renamed it from boot.img to that to keep track, should not be a problem, right?). and that goes over well, too. I do not know how many times I have already erased cache, dalvik, factory, battery. all to no avail. when i reboot the phone remains stuck in the white boot screen. at least i would have expected to get the CM spash screen (like that rotating wheel or something like that), but that may not be a problem.
I have tried a few other roms (devilkin 11.0 and carbon) with this method. same, same ...
I really don't know ... sheesh ... any ideas ? And if it boils down to downgrading: can I do that on ubuntu ? All the guides I have found so far required Windows.
Sorry ... clearly I am not a developer. If somebody could nudge me into the right direction ? I am quite happy to do my homework, but not really sure anymore where else to look. This SHOULD work, from all I found in the internet.
And ... I hope this is not the wrong forum. If so, really sorry ...
1000 thanks
Ingo
Click to expand...
Click to collapse
From what I see you done it as needed.
First for recovery try find 4ext touch 1.0.0.6 RC1 and try to flash via fastboot ( fastboot flash recovery recovery.img).If you don't get in try TWRP 2.7.0.0 by devil-kin you got it in this forum.
About white screen you should check your display.There's sony and hitachi.If you have sony then you are good and something else is problem but hitachi is problem bc you need MDDI capable kernel or use only CM 7 or older roms.
Read this about that problem http://forum.xda-developers.com/showthread.php?t=1943524
GL.

Hello!
I find it strange that you're experiencing so many issues while for everybody else things are just fine. I'm not trying to accuse you of anything, it just makes me think that your problems are likely to be on your end...
You don't need to do anything with your hboot, it's fine
Are you sure that flashing www.4ext.net/ddl/saga/recovery.zip using
Code:
fastboot flash recovery recovery.img
doesn't work?
sudo adb flashboot flash boot flinnycm101_saga_22.img
Click to expand...
Click to collapse
This is wrong - should be:
Code:
flashboot flash boot flinnycm101_saga_22.img
But first try:
Code:
flashboot boot flinnycm101_saga_22.img
That will just boot the image from RAM without flashing it to /boot. I recommend trying this out first with this ROM - http://forum.xda-developers.com/showthread.php?t=2240592 - because that ROM is known good. If that works then we know the procedure you use is OK and you can then try to flash a ROM you actually like.
Note that AOSP roms may be problematic, because they only work with sony panels. We can check whether you have a sony or a hitachi panel once you have a ROM booting properly. (Unless there is a fastboot command that can tell you this that I'm not aware of.)
And ... I hope this is not the wrong forum. If so, really sorry ...
Click to expand...
Click to collapse
It is - questions should be posted in the Questions subforum :silly:

SKENER said:
From what I see you done it as needed.
First for recovery try find 4ext touch 1.0.0.6 RC1 and try to flash via fastboot ( fastboot flash recovery recovery.img).If you don't get in try TWRP 2.7.0.0 by devil-kin you got it in this forum.
About white screen you should check your display.There's sony and hitachi.If you have sony then you are good and something else is problem but hitachi is problem bc you need MDDI capable kernel or use only CM 7 or older roms.
Read this about that problem http://forum.xda-developers.com/showthread.php?t=1943524
GL.
Click to expand...
Click to collapse
all right. thanks. i found that recovery and did
sudo fastboot flash recovery 4EXT_Recovery_Touch_v1.0.0.6_RC1.img
when i go into recovery then, again nothing ... phone is stuck in the white screen. sorry. with white screen i meant the splash screen, which is white on my phone, but has the telecom logo. so i think the screen is allright.
so i pulled the battery and back to cwm (flashed the cms recovery and voila).

Aquous said:
Hello!
I find it strange that you're experiencing so many issues while for everybody else things are just fine. I'm not trying to accuse you of anything, it just makes me think that your problems are likely to be on your end...
Click to expand...
Click to collapse
absolutely. that's why i came here. the phone was fine under htc sense, so its not the phone. it got to be me.
Aquous said:
You don't need to do anything with your hboot, it's fine
Click to expand...
Click to collapse
Good.
Aquous said:
Are you sure that flashing www.4ext.net/ddl/saga/recovery.zip using
Code:
fastboot flash recovery recovery.img
doesn't work?
This is wrong - should be:
Code:
flashboot flash boot flinnycm101_saga_22.img
Click to expand...
Click to collapse
oh. typo. sorry.
Aquous said:
But first try:
Code:
flashboot boot flinnycm101_saga_22.img
Click to expand...
Click to collapse
This boots into recovery. But not exactly. It boots to the white Telekom screen, and then it reboots and goes into recovery. Since I found that strange I extracted the boot image once more from the flinny...zip and tried again. confirmed.
Aquous said:
That will just boot the image from RAM without flashing it to /boot. I recommend trying this out first with this ROM - http://forum.xda-developers.com/showthread.php?t=2240592 - because that ROM is known good. If that works then we know the procedure you use is OK and you can then try to flash a ROM you actually like.
Click to expand...
Click to collapse
Downloading. This is "SVHD v2.1.0 by mygamers (MultiDevice)", right ? The thing is huge. That's gonna take a bit and I have to go to work. Get back to you later ...
Aquous said:
Note that AOSP roms may be problematic, because they only work with sony panels. We can check whether you have a sony or a hitachi panel once you have a ROM booting properly. (Unless there is a fastboot command that can tell you this that I'm not aware of.)
It is - questions should be posted in the Questions subforum :silly:
Click to expand...
Click to collapse
I extracted the boot.img
Can somebody move this ?

SKENER said:
From what I see you done it as needed.
First for recovery try find 4ext touch 1.0.0.6 RC1 and try to flash via fastboot ( fastboot flash recovery recovery.img).If you don't get in try TWRP 2.7.0.0 by devil-kin you got it in this forum.
GL.
Click to expand...
Click to collapse
4ext touch 1.0.0.6 RC1, same problem. stuck at the white telekom screen.
twrp-2.7.0.0-saga-recovery.img, same problem.
but openrecovery-twrp-2.6.3.0-saga.img did work
Ingo

Aquous said:
I recommend trying this out first with this ROM - http://forum.xda-developers.com/showthread.php?t=2240592 - because that ROM is known good.
Click to expand...
Click to collapse
tdDDAAA !!!
So I installed the SVHD .zip with TWRP 2.6 (see above) and that did go nowhere yet.
But I then extracted the saga boot image from that zip kernel/saga/boot.img, renamed that to avoid confusions, and then
<code>
fastboot boot "SVHD v2.1.0 by mygamers (saga).img"
</code>
And my Telekom splash screen blinks up, then the HTC sense (quietly brilliant), and some 3 minutes later ... it worked.
Flashing
<code>
fastboot flash boot "SVHD v2.1.0 by mygamers (saga).img"
</code>
MY guess is it was the reformatting to ext4 ... is that something I should have done all along ? Or any other idea ?

Now you have a working phone, you can check which panel type you have, I suspect that has been your problem all along.
Edit: check this thread:
http://forum.xda-developers.com/showthread.php?t=1943524

teadrinker said:
Now you have a working phone, you can check which panel type you have, I suspect that has been your problem all along.
Edit: check this thread:
http://forum.xda-developers.com/showthread.php?t=1943524
Click to expand...
Click to collapse
Yeah,check panel now.Some phones has that problem.If you have hitachi then I'm sorry.From what I know no1 make MDDI kernel anymore.

teadrinker said:
Now you have a working phone, you can check which panel type you have, I suspect that has been your problem all along.
Edit: check this thread:
http://forum.xda-developers.com/showthread.php?t=1943524
Click to expand...
Click to collapse
Must be, since I tried to install blindnnumbs cm now, and same problem, again ... Good ... so back to SVHD and check that thread. Thanks.
Ingo

One more thing:
On the link you provided the instructions are given as follows, and i am not 100% clear on everything:
1) Wipe all data
2) Flash your custom ROM
3) Get your MDDI compatible kernel and flash it
--> IF (and only IF) you've this error when flashing kernel in recovery: assert failed:write_raw_image("/tmp/boot.img","boot"):
--> 3a) extract boot.img from custom rom ZIP and put it in the adb directory on your PC
--> 3b) reboot in fastboot mode
--> 3c) execute from PC: fastboot flash boot.img
--> 3d) reboot in recovery and retry to flash your new kernel
--> 3e) Now, flashing kernel is completed and you can continue to Step 4)
4) Get new boot.img: in recovery, attach USB cable and run from PC terminal --> adb pull /tmp/newboot.img (it will trasfer generated boot.img to your PC) <--
5) On your PC rename newboot.img file to boot.img
6) Reboot in fastboot mode
7) Install new boot.img (from PC terminal execute --> fastboot flash boot.img <--)
So I
- in twrp i installed cm-10.1-20130709-UNOFFICIAL-saga.zip (blindnnumb cm-10.1, penultimate version. the very last version does not unzip, no matter how many times i download it)
- then flashed fastboot flash boot cm-10.1-20130709-UNOFFICIAL-saga.img
- then flashed fastboot flash boot saga_mddi_291212.img (from your link)
- i pulled newboot.img and then flashed newboot.img
and i am stuck again ... but maybe i did not totally understand the instruction from above ? i.e. 2). do i need to install the zip and the img ?
also in line 7) the command seems to be wrong. right ?
ingo

If you already have a boot.img for the mddi kernel, all you have to do is:
1) flash rom zip file in recovery
2) flash mddi kernel zip in recovery
3) flash mddi kernel boot.img in fastboot
The special instructions for s-on are only needed if you have the kernel zip without the boot.img

teadrinker said:
If you already have a boot.img for the mddi kernel, all you have to do is:
1) flash rom zip file in recovery
2) flash mddi kernel zip in recovery
3) flash mddi kernel boot.img in fastboot
The special instructions for s-on are only needed if you have the kernel zip without the boot.img
Click to expand...
Click to collapse
Oh my ... that did not go either. Now I flashed
cm-10-20121116-EXPERIMENTAL-saga-NK111.zip
saga_kernel_82n_4.0_4.1.zip (which does not seem to produce a newboot.img, and does not have a boot.img either)
that, at least, brings up the spinning clockworkmod wheel ... but then that's that, too ...
oh well ... i guess SENSE it is gonna be then ...
ingo

Didn't you read the warning at the top of the hitachi panel thread? It said:
WARNING!
ALL THE LATEST 4.1.x AND 4.2.x ROMS DO NOT SUPPORT HITACHI SCREEN PANELS, EVEN AFTER APPLYING THE CORRECT MDDI KERNEL!
THIS APPLIES TO ROMS THAT ARE BASED ON AOSP, AOKP, CyanogenMod, ParanoidAndroid, PAC-Man, etc., AND ROMS THAT ARE BASED ON MIUI
THE LAST CUSTOM ROM THAT DOES SUPPORT MDDI PANELS IS CyanogenMod 10.1 Build 13 by Flinny, SO THE DATE WHEN BUILD 13 WAS RELEASED IS YOUR GUIDE TO CHOOSE THE CORRECT ROM THAT WILL BOOT UP AFTER FLASHING THE MDDI KERNEL
Click to expand...
Click to collapse

Aquous said:
Didn't you read the warning at the top of the hitachi panel thread? It said:
Click to expand...
Click to collapse
Read it ... and I think I did not understand it right ... I guess I got too tired over it. I thought I had one that should match those criteria. Tomorrow is another day ...
Ingo