Develop Bugs

[Q] HELP! My Desire doesn't boot

PLEASE, HELP!!!
I HAD:
OXIGEN 2.1.6, AlphaRev Sense HBOOT S-OFF
after attempt to repair the speaker in service center of HTC, my Desire hangs on splash screen. (nothing was repaired, changed etc., but as far as I understand, they tried to flash something)
SO, NOW I HAVE:
Desire of the same phisical condition, but:
If normally to boot - I've seen only splash screen.
If to boot into bootloader - it's started, fastboot working, but option RECOVERY doesn't work - if to choose it, phone goes to reboot and hangs on splash screen again.
I tried to root the phone again, but step2 doesnt work, because "device not found" (although all the drivers are installed and are working normally)
After that 1st step of rooting, the normal boot goes directly to bootloader.
I tried to re-flash Recovery with fastboot-windows, but got the error:
FAILED (remote: siignature verify fail)
So, as far as I understand, phone not dead yet, but I can't call it alive as well.
PLEASE, help!

AndrewMe said:
PLEASE, HELP!!!
I HAD:
OXIGEN 2.1.6, AlphaRev Sense HBOOT S-OFF
after attempt to repair the speaker in service center of HTC, my Desire hangs on splash screen. (nothing was repaired, changed etc., but as far as I understand, they tried to flash something)
SO, NOW I HAVE:
Desire of the same phisical condition, but:
If normally to boot - I've seen only splash screen.
If to boot into bootloader - it's started, fastboot working, but option RECOVERY doesn't work - if to choose it, phone goes to reboot and hangs on splash screen again.
I tried to root the phone again, but step2 doesnt work, because "device not found" (although all the drivers are installed and are working normally)
After that 1st step of rooting, the normal boot goes directly to bootloader.
I tried to re-flash Recovery with fastboot-windows, but got the error:
FAILED (remote: siignature verify fail)
So, as far as I understand, phone not dead yet, but I can't call it alive as well.
PLEASE, help!
Click to expand...
Click to collapse
My guess is that they've tried to install stock ROM and it failed because I suspect you have custom hboot partitions.
The safest way would be to bring your phone to stock and then try re-rooting, custom Hboot and Rom.
Good luck !

AndrewMe said:
PLEASE, HELP!!!
I HAD:
OXIGEN 2.1.6, AlphaRev Sense HBOOT S-OFF
after attempt to repair the speaker in service center of HTC, my Desire hangs on splash screen. (nothing was repaired, changed etc., but as far as I understand, they tried to flash something)
SO, NOW I HAVE:
Desire of the same phisical condition, but:
If normally to boot - I've seen only splash screen.
If to boot into bootloader - it's started, fastboot working, but option RECOVERY doesn't work - if to choose it, phone goes to reboot and hangs on splash screen again.
I tried to root the phone again, but step2 doesnt work, because "device not found" (although all the drivers are installed and are working normally)
After that 1st step of rooting, the normal boot goes directly to bootloader.
I tried to re-flash Recovery with fastboot-windows, but got the error:
FAILED (remote: siignature verify fail)
So, as far as I understand, phone not dead yet, but I can't call it alive as well.
PLEASE, help!
Click to expand...
Click to collapse
Bring your phone back to stock rom:
1.) Create goldcard: http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
2.) Put this in your desire
3.) Download latest stock ruu: RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
4.) Boot your phone into fastboot mode and run exe on your computer
5.) If this does not work, extract pb99img from the ruu:
http://forum.xda-developers.com/showpost.php?p=9036922&postcount=2
6.) Put this on your goldcard and boot your desire into bootloader
7.) Follow the instructions

paul.c said:
My guess is that they've tried to install stock ROM and it failed because I suspect you have custom hboot partitions.
The safest way would be to bring your phone to stock and then try re-rooting, custom Hboot and Rom.
Good luck !
Click to expand...
Click to collapse
Thank you for reply, I tried it as well - device not found...

MatDrOiD said:
Bring your phone back to stock rom:
1.) Create goldcard: http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
2.) Put this in your desire
3.) Download latest stock ruu: RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
4.) Boot your phone into fastboot mode and run exe on your computer
5.) If this does not work, extract pb99img from the ruu:
http://forum.xda-developers.com/showpost.php?p=9036922&postcount=2
6.) Put this on your goldcard and boot your desire into bootloader
7.) Follow the instructions
Click to expand...
Click to collapse
Thanks for your reply, start to try the 2nd variant..

MatDrOiD said:
Bring your phone back to stock rom:
1.) Create goldcard: http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
2.) Put this in your desire
3.) Download latest stock ruu: RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe
4.) Boot your phone into fastboot mode and run exe on your computer
5.) If this does not work, extract pb99img from the ruu:
http://forum.xda-developers.com/showpost.php?p=9036922&postcount=2
6.) Put this on your goldcard and boot your desire into bootloader
7.) Follow the instructions
Click to expand...
Click to collapse
It worked.. a bit by the other way - first placed stock hboot from AlphaRev's site, then booted into bootloader, then normal flashing of stock RUU went well.
Thanks once again!

It worked.. a bit by the other way - first placed stock hboot from AlphaRev's site, then booted into bootloader Can you explain please!! I am not as expert as you are...

it worked actually!! the phone's has been ROMed but I still have the same original problem!! it goes off by itself and the camera doesn't work??
Any Ideas??

HTC_DeSiRe_83 said:
it worked actually!! the phone's has been ROMed but I still have the same original problem!! it goes off by itself and the camera doesn't work??
Any Ideas??
Click to expand...
Click to collapse
Sounds like an hardware issue. You are back on stock ruu, so you can give htc a ring.

Desire stuck in fastboot RUU mode

First of all, hello to all forum members!
I had not been particularly active here in the forum,
but I read a lot here and build some knowledge.
so far I have solved all my problems due to browse and read.
But now I am facing a problem, where I need help.
I got a desire from a friend with wrong nexus one blackrose hboot.
I managed to install alpharev hboot on it, but its not booting the rom, neither the recovery.
I decided to get a ruu on it, to reflash boot, system, recovery, etc.
After i did:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <rom.zip>
the phone is stuck in fastboot RUU mode. No matter if I pull the battery and power on with vol-, vol+ or back, the fastboot RUU mode starts (Black screen with htc logo in the middle and 4 exclamation marks in the corners).
What Ive done so far:
Tried different RUUs(Europe, WWE) via fastboot. Most of them fail while writing radio image.
Tried to flash the radio image via fastboot. Most of them stuck while writing.
Asked a friend with exactly matching hardware to send me his working nand backup, his hboot is CM7 r2, so I flashed it
to match his nand backup.
I flashed his boot/recovery/system/cache and the latest radio, matching the nand backup.
The latest radio was flashed successfully.
The recovery in his nand backup was 4EXT Touch 1.0.0.3
So, after flashing boot, recovery, system, cache and even misc and userdata (AND erasing them prior on second try), the behaviour stays the same, the phone wont boot the rom or recovery and no matter what buttons I press on power on, it boots at fastboot RUU mode.
I tried
Code:
fastboot oem boot
, but that keeps stucking in the white htc splash1
If I plug in the usb cable and pull it out again, I see the hboot infos:
AlphaRev CM7 r2
BRAVO PVT1 SHIP S-OFF
HBOOT-6.92.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
<date>
RUU
After a lot of research, Ive found several opinions:
-its a brick (sure it is ;D)
-its a radio brick (ive sucessfully flashed the newest radio, so I doubt it)
Almost all users wo tried it hardly, and havent given up after the second try,
recovered their phone from this fastboot RUU mode.
I can run all fastboot extended commands, and flash RUUs over it.
So: what have I done wrong? Is there anything missing?
Can someone who knows what he says please take a look over it?
Thank you really much
criestr

After "a lot" of research you still haven't looked at my guide, well done.

Sure Ive looked at your guide,
I work with linux, and I hate flashing tools.
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
Click to expand...
Click to collapse
Is it any difference to use
Code:
fastboot flash hboot bravo_alphaspl.img
instead of using Android Flasher?
I dont think so, and Ive already done the steps in your guide, except using Android Flasher to flash the AlphaRev stock version.
Or is there another point in your guide that Im missing?
If so, then I am sorry for wasting your time.
I know, I am "new" here, so thats the standard answer for all newbs from you.
Thats ok. But Ive fixed a lot of phones without open even one thread, just with hours of research. But after google search for about 8 hours, several tries and following several guides and tips I didnt find an answer yet.
New update: Ive managed to push and boot the 4EXT Recovery image.

Fair enough, but the guide was meant to be made as easy to use as possible.
All you had to do was flash the stock hboot, or the downgrader, and then try a RUU.
The reason for it being stuck, is because alpharev hboots have write protection (meaning they won't be overwritten until you use the downgrader), and since you had the cm7r2 partition flashed, there was not enough space in /system for the stock ROM.

Hi again,
thanks for your answer.
I had the right stock hboot whilst flashing the RUU, so that wasnt the problem.
The RUU always failed to write the radio. A few hours ago i figured out that
the problem was because of a faulty battery. I changed the battery, loaded it
half an hour, and voila! the RUU was running quite fine.
The stock rom wasnt booting yet, but from then it was possible to go into the HBOOT/Fastboot, so it was making progress ;D
After another research I found out that my misc partition was screwed, maybe because the blackrose hboot, maybe because of the pre-owner.
Fixed the misc partition with cid, kernel commandlines & rom version.
After that I wiped cache and data, and did fastboot oem boot.
The rom was booting, but did random reboots/crashes after about 3-5 mins.
After 3 or 4 reboots the phone is now stuck at htc splash1, and isnt booting anymore.
For now I will try to flash the nand backup again, see if that works out.
Anyone has an better idea?
Thanks alot
criestr

New update:
The phone switched randomly between bootable and non-bootable bootloop/stuck in splash1.
I tried different radios, different boot & system.img from RUUs.
I can flash a new recovery, tried 4 different ones, none of them is booting,
not over hboot->recovery and also not over
Code:
fastboot oem gencheckpt
.
The only thing that worked was to erase cache and immediatly do
Code:
fastboot boot recovery.img
,
so after the stock rom randomly reboots, I decided to install a custom rom for CM7 r2 hboot. So I flashed the CM7 r2 hboot again, erased cache, booted the recovery and flashed rom.
The rom was booting! But again, after fiddling with flashing a new recovery with 4EXT Updater, the rom rebooted into splash1 and stuck there.
After this first time, it has yet never rebooted again. So I twist my fingers that it was a custom rom bug on first boot.
Flashing the recovery via 4EXT Updater worked for me, despite of none of the recoverys flashed via fastboot had booted before.
Anyway, thanks for the help.
Hopefully it helps someone with the same problem,
but I doubt there are many people dumb enough to flash blackrose hboot on a desire
Cheers
criestr

I had a similar problem with my old Magic. I have Desire now but never had that problem. I hope not.
Anyways, the way I solved it was to flash the right radio.img. I supposed you can try to fastboot flash radio radio.img. Make sure you use the right radio.img. That is what I did if I recall correctly and it worked for me on Magic. I don't know if it is will work on Desire that way.
The other thing is when Ruu failed at radio, I think it is because the lower version of radio.
I hope this helps.
Try it and let me know.

bortak said:
After "a lot" of research you still haven't looked at my guide, well done.
Click to expand...
Click to collapse
link please

[Q] Unlocked bootloader with S ON - Black Screen Recovery issue + Can't flash ROMs

So... I am gone try and put my question in this post as detailed as I can... And I really hope that someone can help...
I have an HTC Wildfire S (Marvel, bought in Denmark) that had 2.2.1, I wanted to use ICS on it and so I started researching for a good ICS ROM. My phone had the below,
Marvel S HTC Europe
HBoot 1.09.0099
2.26.401.3 Radio 47.23e.35.3038H 7.57.39.10M
I decided to flash the below ROM,
Paranoid Android pa_marvel-1.6a-beta1-24AUG2012-142650
My steps were the following,
1. Went on HTCDEV.com and unlocked the bootloader
2. I downloaded the necessary SDK files on a folder on C drive (adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll & fastboot.exe) I then used the following command to flash a recovery “fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img”, this was a ClockWorkMod official recovery.
3. When I tried to access the recovery it seems that it was ok but I had a black screen with the tactile buttons switched on for about a minute and then it booted... I research in XDA and I found a solution... the following.... http://forum.xda-developers.com/showthread.php?t=1781105 it is a small jave software that enables you PC screen to display your htc screen when it is black to actually see what is happening... this saved me!!!!!! Thanks to “rajanand”....
4. After I managed to see my recovery on my PC screen I flashed Paranoid Android... doing always the norm of Wiping Data, Cache and Dalvik first.
5. When I tried booting I only got the HTC White Screen logo and nothing else... (PANIC!!!) I assumed there was something wrong with the ROM.
6. I then flashed CM9 from Alquez... doing always the norm of Wiping Data, Cache and Dalvik first.
7. When I tried booting I only got the HTC White Screen logo and nothing else... (PANIC AGAIN!!!)
8. I then decided to put it back to its original state by running the official RUU of the phone by downloading it from here http://forum.xda-developers.com/showthread.php?t=1074445
9. When I run the RUU, but first I relocked the bootloader with the following command in the bootloader “fastboot OEM Lock”, (RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed), the phone got an error 140, meaning that my bootloader was a higher version... and the is not other RUU which is higher than this... so I was a bit stuck and confused as to how this happened.
10. I WAS REALLY NERVOUS...
11. I then read a post from someone, I can’t remember saying that only EQDKP ROMs worked for him.
12. I unlocked the bootloader again using the same key when I unlocked it the first time. Keep it.
13. And I flashed the following, [Drk_mod]EQDKPv4.9_multi_deodexed_mhr.zip, and finally my phone booted in the ROM and it is currently working...
See below a screen shot from the Java program and my cwd... it seems that this ROM things a bit different when flashing things or is this a misunderstanding...
Can anyone explain why NO OTHER ROM is working?

[SOLVED] Bootloop with no access to recovery (S-OFF)

SOLVED. THE PHONE IS BROKEN AKA HARDWARE FAILURE
Hi,
My old Desire had been sitting in my desk for about a year since i bought myself a Galaxy S2. Today, I decided to try it out. Charged the battery first and then tried to boot it. Well, I got stuck in the splash screen. The phone had been working normally the last time i used it (maybe 6 months ago?) so i thought it was weird. Then I tried to boot it into recovery, and got again stuck in the splash screen. HBOOT came up normally but after pressing the recovery button the phone just made the boot vibration multiple times and then was stuck in the splash screen.
What I have:
- Alpharev S-OFF HBOOT: bravo_alphaspl-oxygenr2.img
- Oxygen rom (don't remember the version but i have the zip on my computer): update-oxygen-2.1.6-signed.zip
- My current HBOOT screen shows the following:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
- AFAIK the phone is the older AMOLED version (if that matters)
- I have a working ADB
- I dont have a goldcard
What I did after noticing the problem:
1. Read the sticky which told me to reflash my recovery.
2. Flashed the CWM 2.5.0.7 recovery via Android flasher. The program said it was successful but my phone was in a bootloop again without access to recovery.
3. Flashed the Amon Ra recovery via Android flasher. The program again said it was successful but the bootloop persisted.
4. Flashed both of the recoveries (one at time of course) via the adb fastboot command. Again, it was supposed to be successful, but the phone STILL was in the bootloop.
I thought the sticky explained my situation perfectly but apparently this is not the case
I have also a RUU lying around:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
But I was hesitant to use it as I have the custom Alpharev HBOOT which might cause problems.
So what should I do now? I appreciate all advice.

Re: Bootloop with no access to recovery (S-OFF)
In my sig you'll find a thread with how to install 4ext recovery through pb99img. Check it out.

I DL'd the PB99IMG.zip file for the recovery and put it on my SD by moving the SD to my other phone and connecting it to my PC.
However, when the HBOOT searches for the PB99IMG.zip, it only says "No Image!".

Re: Bootloop with no access to recovery (S-OFF)
Are you sure you didn't put it in any folder?
Then, again in my sig, you'll find a partitioning guide. The first part of the guide will help you install a recovery. Try it.

Yes, I put it right in the root of the sd card.
The partitioning thread in your sig has a few methods of installing the recovery. But i have already tried them and for some reason they fail. I have now tried the Android flasher method, the ADB + Fastboot method and the PB99IMG.zip method. I have no clue why these should fail like i have described.
EDIT: Looks like I cannot run the RUU either. It says it failed to detect the device. What on earth could be going on when EVERY possible way of reinstalling the recovery fails? I was starting to think that maybe there was something wrong with my USB connection/drivers or ADB so I made a test and flashed another alpharev HBOOT (their bravo stock one: bravo_alphaspl.img) and the flashing procedure worked. So at least my ADB is working. Still no idea why the PB99IMG.zip just won't work... looks like my phone defies all these guides available here.

Update:
I downloaded the 2.3 GB RUU from the sticky topic. Suprisingly enough I could run it, it detected my device and went throught the whole RUU process without a single error. I booted the phone - and was again stuck in a bootloop. Went to HBOOT, chose recovery (the RUU should have flashed the stock recovery) but no, I could not get into the recovery. Instead the phone was again stuck in a bootloop. So I still cannot get into the recovery. The only thing that changed was the splash screen I was stuck on... (I had a custom splash, now it's the stock one)
I then formatted my SD, put the 4ext recovery PB99IMG.zip there and booted into HBOOT. This time It found the PB99IMG.zip. It asked if I wanted to update, I pressed yes and it went through it without any error. When it asked if i wanted to reboot, i pressed no, navigated into recovery and pressed the power button. This should have taken me to the 4ext recovery i just flashed successfully. And guess what? Bootloop again...
So after all this, I still do not have access to the recovery. I just get the bootloop every time. I've whacked around with android phones (mostly Galaxy S2 though) quite a lot but this far have never seen such a persistent problem which just evades all (for other people) working attempts to fix it. The procedures work exactly as described and give me no errors, but in the end the issue still persists: I cannot access the recovery because of the bootloop.
I was starting to wonder if it could be hardware failure causing this? Just a wild guess but the phone has been sitting in my desk for almost a year... I didn't change anything in the software. The only thing that comes to my mind is that the memory where the recovery and rom are stored is somehow corrupt. This would explain why I cannot get into the recovery even though i have reflashed it successfully multiple times. I also can change my HBOOT and splash screen.
Does anyone have any ideas left?

Re: Bootloop with no access to recovery (S-OFF)
Are you s-on now?

Yep,
At the moment i'm S-ON with the 2.3 RUU from your sig. Bootloader is 1.02.0001. I flashed the RUU from the PB99IMG. No errors. Still cannot get to recovery.
I then opened the phone and removed the mainboard but i could not see any damage at all. No burns, marks of water damage etc.

Re: Bootloop with no access to recovery (S-OFF)
As weird as it sounds, try putting the phone in the freezer without the battery for 10 minutes, then try to boot.

You are pretty good, man.
CASE CLOSED
Explanation: after putting the phone into the freezer for some time, I tried to boot. It booted normally to the ROM. Wifi worked, I could use internet, setup my settings etc. After 10 minutes the phone rebooted into a bootloop. This proves that the problem always was a hardware one, and this is why any software fixes couldn't solve the issue. Because i don't have a freezer in my pocket I can safely say the phone is broken and I can throw it away.
Thank you!

Stuck on boot screen

Hi!
I've been using ViperDHD 1.2.3 on my HTC DESIRE HD but now it crashed and it's stuck on the HTC logo. I belive the problem isn't the rom because I've been using it for almost a year and it has worked perfectly.
I can get it to HBOOT screen, but I cant go to RECOVERY because it just show the HTC logo and nothing happens.
Some text found in HBOOT:
***** AAHK *****
ACE PVT ENG S-OFF RL
HBOOT-0.85.2425
MCROP-0438
RADIO- 26.10.04.03_M
eMMC-boot
Apr 12 2011, 00:55:45
I spend whole yesterday searching but I didn't found any solution. So please help me! :crying:

you can try flashing recovery from hboot and see if then you can at least boot into it. then make a backupz and reflash. dirty flash might help, if it doesnt, fullwipe then reflash. your data should still be in nand backup, and you should be able to extract it with titanium backup. if this dont work, you probably have a more serious problem...
it might be helpful if you could provide more details what exactly happened, because "crash" doesnt really tell a lot.

t0mas_ said:
you can try flashing recovery from hboot and see if then you can at least boot into it. then make a backupz and reflash. dirty flash might help, if it doesnt, fullwipe then reflash. your data should still be in nand backup, and you should be able to extract it with titanium backup. if this dont work, you probably have a more serious problem...
it might be helpful if you could provide more details what exactly happened, because "crash" doesnt really tell a lot.
Click to expand...
Click to collapse
I choose the RECOVERY option from HBOOT menu (is this what you mean?), then it vibrated and showed the HTC logo and after that nothing happened.
I was playing music when the phone vibrated few times and the screen went black, I could still hear noise from the speaker. Then I took out the battery and put it back and then I booted the phone but it was stuck in the HTC logo.
So is it dead now? :crying:

You can try what the previous member said. Flash a recovery either using pd98img.zip or fastboot.
Sent from a dream.

It says: "No image or wron image!"

MMCMVI said:
It says: "No image or wron image!"
Click to expand...
Click to collapse
or your sdcard is corrupted to work as a goldcard and there to flash PD98IMG files (try the same file with another sdcard) or perharps the file is misspelled. Check that you don't have .zip.zip or something similar.

glevitan said:
or your sdcard is corrupted to work as a goldcard and there to flash PD98IMG files (try the same file with another sdcard) or perharps the file is misspelled. Check that you don't have .zip.zip or something similar.
Click to expand...
Click to collapse
I've tried diffrend sdcards and diffrend files but it doesn't work. I found onde PD98IMG file that the phone regonized but when i pressed "yes" it did something and showed the HTC logo and after that nothing happened.
The file that my phone found (link) is only 220kt so I think it would not work anyway.

MMCMVI said:
I've tried diffrend sdcards and diffrend files but it doesn't work. I found onde PD98IMG file that the phone regonized but when i pressed "yes" it did something and showed the HTC logo and after that nothing happened.
The file that my phone found (link) is only 220kt so I think it would not work anyway.
Click to expand...
Click to collapse
Why are you trying to mess your device? You were running Gingerbread and you are trying to flash a Froyo RUU?? That is not good...you will probably mess the bootloader that way.
If you are s-off you can flash any ruu in fastboot...but if your device keeps vibrating for a while when you turn it on... and youwait for about 30 minutes and boots, then that means that your bootloader is corrupted and you need to fix it.
How long does it take to boot in hboot?

glevitan said:
Why are you trying to mess your device? You were running Gingerbread and you are trying to flash a Froyo RUU?? That is not good...you will probably mess the bootloader that way.
If you are s-off you can flash any ruu in fastboot...but if your device keeps vibrating for a while when you turn it on... and youwait for about 30 minutes and boots, then that means that your bootloader is corrupted and you need to fix it.
How long does it take to boot in hboot?
Click to expand...
Click to collapse
The phone starts like it should but it just get stuck on the HTC logo.
Booting in HBOOT goes also normaly, just few seconds from pressing the buttons.

mate, what are you trying to flash is bootloader not recovery. dont know why you want to do that? since your phone is behaving wierd, i dont think it is a good idea. you should find recovery image (.img) and flash with fastboot (your bootloader says you are eng s-off) or pdimg containing recovery, and then see if you can boot into it. if it does, you are on a good way to have your phone working again. if recovery flashes good and you still cant boot into it, i have no clue how to proceed...

I managed to install a PD98IMG file (with recovery image), but it's still stuck at HTC logo.