Database Info

[Q] Help! Something went wrong while installing an RUU!

Hi, I was trying to unroot my desire S, I have been following the desire fanatics guide on youtube (Can't post the link - sorry)
And I got up to the point where I was running the RUU utility. It started and then It got to about 50% in and then said Error, please use the correct RUU utility. (I'm guessing I've downloaded the incorrect RUU file.
So now, when I turn the phone on it goes right into the white menu with all the stuff on HBOOT etc.. fastboot I think it is, and it says security warning.
I'm guessing Its wiped the data but no longer has an OS to boot into. I honestly don't think it is bricked but I have no clue what to do from now!
I got my phone from mobiles.co.uk (A carphone warehouse subsidiary) and it is on contract with T-mobile. The phone had no branding on it from T-mobile so I guess its unlocked.
However I downloaded the T-mobile UK RUU and ran that..
Any advice on what to do from here? I'm currently in the process of downloading The Saga_HTC _Europe_1.28.401.1_Radio20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
I don't even know if this will work because I can't get into any OS. I also read a lifehacker article and it said I can put a file onto the SD card and it will automatically run fixing the phone, making it better.
Please help me!

So far, I've tryed:
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
and
RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed
But neither of these have worked, it gives me an error 140 saying I'm using the wrong version!
Can anybody tell me the correct version for an unlocked desire S bought in the UK from mobiles.co.uk?
Something that may of made this slightly more difficult for myself Is that While following the guide I followed, I used android flasher and flashed the bootloader included in the Revert to stock bundle kit thing, It was called engHBOOToverARX
I honestly have no Idea how I can fix this but Hopefully somebody else can!

can you tell me your current hboot version?
is your device detected by ADB?
if you have not set up ADB before read this below link

His device won't be detected by adb, only fastboot.
Run fastboot command "fastboot getvar all" and post the response.

Ok, this is what I get after fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) serialno: SH15NTJ00762
(bootloader) imei: 356708049175530
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.023s
And I have the ability to run adb commands but I don't know what command to use to check if its detecting my device, I type adb into cmd and loads of commands come up..

@imattacus
Okay you have a UK unbranded phone, I say this cause your CID is HTC__001 and your main version is 1.47.401.4.
So to fix you can either;
1) You can download this RUU (v1.47.401.4, hboot 0.98.0002) and run it from the PC.
Or
2) Change your main version (by getting shell root) then trying again with the 1.28.401.1 RUU. (but may be impossible since you can't get adb)
Option 1 is the easiest.

Same issue with Virgin Mobile RUU
Anyone got the correct RUU for me as I've got the same issue with a Virgin Mobile RUU. I followed the instructions for unrooting here. I was using the Virgin Mobile RUU listed on the link provided which was this list but I keep on getting error 140 when I run the RUU, telling me to use the correct one.
My bootloader is as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
I just need to find the right RUU version.
Any help would be greatly appreciated and as soon as possible.
Thanks

Just use Goldcard and try 1.47.401.4 again.

I also have a few problems with my Desire-S:
-my android email app keeps crashing when i try to open any email;
-official update aborts instalation (system 7) (even after hard reset).
So i decided to try fixing this via RUU. My phone is unbranded (bought in Slovenia's Vodafone), unrooted:
-android 2.3.3
-Sense 2.1
-Build 1.47.401.4
-Boot says: Saga PVT Ship S-on RL, Hbroot 0.98.0002, radio 3805.06.02.03_M
I tried to install:
-RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_234765_signed.exe
Every time i get an error 131- customer id error and message, that the ruu is wrong...
So i tried with the older one:
-RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed.exe
And i keep getting error 140.
And i'm stuck here. Any help? I'd like to put on 2.3.5 with sense 3 without that email bug.... and i'm considering taking it to the repair service...
Thank You

i had in a way similar problem with imattacus...
only i can't run adb commands (adb devices returns no value)
i tried folowing ruu-s:
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed
RUU's installed, but after boot phone was stuck in white screen with green htc.
after i installed this RUU my phone booted:
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
update>>
I checked for updates and there were some... After installing phone stuck on white screen...
I just whish to restore my phone to it's factory outofthebox state..
My getvar all result is::
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) serialno: HT13HTJ16283
(bootloader) imei: 355067040509788
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4020mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Any sugestions?

Goldcard
Sent from my HTC Desire S

I have installed ruu with the gold card, but I did removed it before update... Will try again and post back. Thank you very much for quick response!
>>>>>update...
Unfortunately, with gold card everything went same as before...
When i download and run update, phone reboots into update screen with progress bar, then reboots to update screen with same bar, then reboots to update screen without progress bar, then reboots and stays stuck on white screen...
i guess i have to find a way to unroot and s-on my device to the stock values before i try to update again...
my fastboot screen reads:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
One more curious thing..
When i install RUU ver 1.47.401.4 (only i'm able to boot so far) image version that i overwrite (visible from RUU install screen) is 13.10.401.8... A bit large number, isn't it?
>>> FINAL UPDATE
SUCCESS!!!
as i suspected earlier, when i folowed first post on this topic i locked the phone, and then update worked.
have a nice day, everyone!

Another help required: Cant load recovery

Hi Guys,
Decided to put a new rom on my daughters HTC ONE X (my old phone), and right royally stuffed it up.
Was going to put a new hboot on as the one I had I thought was old, but now I've wiped the recover (TWRP) and can't seem to get it back. Phone was Telstra.
Details as follows:
C:\htc\Data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.89.841.9
(bootloader) serialno: HT26NW30xxxx
(bootloader) imei: 35222xxx80506xxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8312000
(bootloader) cidnum: TELST001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3664mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8d23f0c0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Have tried for two days on/off to get it to load a recovery, but no luck.
any help really appreciated..

jnrdavo said:
Hi Guys,
Decided to put a new rom on my daughters HTC ONE X (my old phone), and right royally stuffed it up.
Was going to put a new hboot on as the one I had I thought was old, but now I've wiped the recover (TWRP) and can't seem to get it back. Phone was Telstra.
Details as follows:
C:\htc\Data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.89.841.9
(bootloader) serialno: HT26NW30xxxx
(bootloader) imei: 35222xxx80506xxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8312000
(bootloader) cidnum: TELST001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3664mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8d23f0c0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Have tried for two days on/off to get it to load a recovery, but no luck.
any help really appreciated..
Click to expand...
Click to collapse
Place the recovery.img in you folder where your adb is located, reboot your phone into bootloader and select fastboot. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery "recoveryfilename.img" In this command line make sure to rename recoveryfilename to which match the name of the the version you are using
example: fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
after it has finished reboot

More information required. Please post your bootloader details (I'm mostly interested in the top line where it says tampered/locked/unlocked/relocked), what ROM you flashed, what recovery you flashed, and the method used to flash both.
PS. Questions go in the q&a section. I've asked for this to be moved for you.
[EDIT] What venomtester has said above is the correct procedure, but we still need the info I've requested to troubleshoot effectively.
Sent from my Evita

Thanks all for your help. Sorry for putting in the wrong forum. Here is the boot screen:
**** TAMPERED ****
**** UNLOCKED ****
EVITA PVT SHIP S-ON RL
HBOOT-1.11.0000
RADIO-0-.23a.32.09.29
OpenDSP-v28.1.0.32.0504
eMMC-boot
Jun 7 2012,13:10:34
What have I tried, lots (to be honest). I started to use Hasoon2000 v2.5 great utility (ONE X), I have tried the flash FactoryRUU, tried CWM, TWRP, but still no luck.
Not sure if the hboot version is causing all the problem, but tried to update that, unsuccessfully (probably to do with s-off).
good news is I can talk to the phone with fastboot, get back results etc.. Just tried to flash openrecovery-twrp-2.4.0.0-endeavoru.img, it seems to flash ok with fastboot, but when I reboot to recovery, I can see the brown bar at the top right of the screen run twice, but then nothing else happens, just sits on the white 'HTC quitely brilliant, this build is for' ... screen.

jnrdavo said:
Just tried to flash openrecovery-twrp-2.4.0.0-endeavoru.img,
Click to expand...
Click to collapse
That's your problem right there. You tried to flash TWRP for the ENDEAVORU (quad core version) when your phone is the EVITA (dual core).

redpoint73 said:
That's your problem right there. You tried to flash TWRP for the ENDEAVORU (quad core version) when your phone is the EVITA (dual core).
Click to expand...
Click to collapse
Thanks mate for pointing me in the right direction. I'll try the right file
I really should stop doing this kind of work at 5:00am in the morning!

just a quick question, if I download the correct twrp, should I just have to fastboot it and overwrite what I have done, or do I need to do anything prior before flashing the correct one?

jnrdavo said:
just a quick question, if I download the correct twrp, should I just have to fastboot it and overwrite what I have done, or do I need to do anything prior before flashing the correct one?
Click to expand...
Click to collapse
I'd try to flash it over fastboot, and see what happens.

jnrdavo said:
just a quick question, if I download the correct twrp, should I just have to fastboot it and overwrite what I have done, or do I need to do anything prior before flashing the correct one?
Click to expand...
Click to collapse
Just make sure after flashing the correct recovery you also give this command:
fastboot erase cache
Sent from my Evita

timmaaa said:
Just make sure after flashing the correct recovery you also give this command:
fastboot erase cache
Sent from my Evita
Click to expand...
Click to collapse
Thanks guys, all working well now!

[Q] No Fastboot USB

Hey guys,
I've got a problem with my HTC One S...
I want to run a RUU to go back to my stock rom, but the problem is that, when I go to HBoot and then Fastboot, my PC doesn't recognize the device, only after 2 minutes it says that the last USB device can't be recognized... I did an uninstall en reinstall of the HTC Drivers/ HTC Sync, but with no succes... I'm running windows 8.1 btw.
Thanks for the help!

Hi !
On W8.1 there is a lot of problem for fastboot, it's normal. Try on another PC.

AndroGeek974 said:
Hi !
On W8.1 there is a lot of problem for fastboot, it's normal. Try on another PC.
Click to expand...
Click to collapse
Thanks for the reply!
I was guessing that was the problem... But still got a windows 7 pc here, I'll try on that one!
Hopefully they will make an update for all the windows 8.1 users.

Yeah, I think to
I go back to W8 to solve this problem ^^
And we just have to wait

i have bought a used htc one s and it had sense 5.5 based JB4.2.2 rom but i want to downgrade to stock firmware. kindly tell me which RUU i should use and how should i procede.
HBOOT shows tampered, unlocked and S-ON
and here is other details
Code:
sudo fastboot getvar all
[sudo] password for hasan:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH267W
(bootloader) imei: 35990
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4111mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I tried RUU RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4 on windows 8.1 64bit but it is not detecting the phone at all
currently I am on linux so i hope you guys can suggest something relevant
thanks a lot

So the point is, that you can't get it to work on a windows 8.1. You will have to use another pc or try a different os. Maybe an emulator works to,but i'm not sure about that...
For your RUU you'll have to search one for your CID, which is in your case Vodaphone. So maybe try,googling your cid for finding the right one for you
Another option is to get S-OFF, the, you can run any RUU you want!
Hope this helped you out.

FantasyGamer said:
So the point is, that you can't get it to work on a windows 8.1. You will have to use another pc or try a different os. Maybe an emulator works to,but i'm not sure about that...
For your RUU you'll have to search one for your CID, which is in your case Vodaphone. So maybe try,googling your cid for finding the right one for you
Another option is to get S-OFF, the, you can run any RUU you want!
Hope this helped you out.
Click to expand...
Click to collapse
I have searched a lot but i cant find matching RUU for this CID. I also tried to get S-OFF but i am not doing it right i think
As you said windows 8.1 is not going to be helpful so can you tell me how to get things done on linux please.

i finally got cid 1111111 which is i think supercid but i cant get it s-off

hasanalikhattak said:
i finally got cid 1111111 which is i think supercid but i cant get it s-off
Click to expand...
Click to collapse
Did you already try to get S-OFF with the All-In-One Toolkit V4.0? It worked for me... On Windows 8 ofcourse not 8.1. Since you're on linux you could try to search for an emulator and run it from there, on a windows 7/8 emulation...
No Idea of this works, but you could try it!

no not yet. may be when i go back home i will try on my desktop pc. i downloaded windows xp and virtualbox. i hope i will be able to do all this on virtual machine.

[Completed] Chicken & Egg problem un-soft-bricking HTC One S

Hi Guys
I'm working on reviving a soft-bricked HTC One S (tmobile, I suspect S4)
I am unable to install any android ROM that I have been able to find, because HBOOT is still version 1.14, and they all require a higher version
TL;DR;
I think I just need a ROM that will install on a HTC ONE S (ville) for HBOOT version 1.14
I'm using an OSX machine, so I don't have the ability to run RUU.exe files. (is there a way to do this?) Attempts at flashing wiht RUU.zip have uniformly failed.
My attempts to upgrade HBOOT via the firmware upgrades with "fastboot flash zip <file>" have not had any luck, I suspect because the phone
is still S-ON (More or less following this instruction set http://forum.xda-developers.com/showthread.php?p=39216236#post39216236 )
My attempts at to remove S-ON using this explanation ( http://forum.xda-developers.com/showthread.php?t=2155135 ) haven't had much for potentially one of two reasons:
Possible reason #1) Step 6 calls for a "fastboot oem boot", which then tries to boot, but there is no working android install. I tried working around this by calling "fastboot oem gotohboot" instead and then booting into recovery (TWRP).
possible reason #2) adb shell doesn't seem to have access to su for me. ("adb shell su" returns "/sbin/sh: su: not found"). I have been assuming that this is the actual problem. I am assuming that this is because I don't have superuser access.
The SuperBoot package doesn't seem to work ( I grabbed it from here http://loadbalancing.modaco.com/download.php?file=r1-ville-superboot.zip referred by http://www.android.gs/root-htc-one-s/ ). I *think* it doesn't work because there is no android version to boot into.
So in short it seems that:
Android requires higher HBOOT requires S-OFF requires Superuser requires Android
Thanks so much for any direction or help, or even just commiseration!
For reference at the moment it is/has:
unlocked
HBoot 1.14 and fastboot is working well, and behaves as expected.
S-On
TWRP (working, and able to access with ADB)
No Working android install
CID: 1111111
Here is a dump of "fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0005
(bootloader) version-baseband: 1.13.50.05.25
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.35.531.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24NW401635
(bootloader) imei: 359902041820139
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8be28a51
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

XDA Visitor said:
Hi Guys
I'm working on reviving a soft-bricked HTC One S (tmobile, I suspect S4)
I am unable to install any android ROM that I have been able to find, because HBOOT is still version 1.14, and they all require a higher version
TL;DR;
I think I just need a ROM that will install on a HTC ONE S (ville) for HBOOT version 1.14
I'm using an OSX machine, so I don't have the ability to run RUU.exe files. (is there a way to do this?) Attempts at flashing wiht RUU.zip have uniformly failed.
My attempts to upgrade HBOOT via the firmware upgrades with "fastboot flash zip <file>" have not had any luck, I suspect because the phone
is still S-ON (More or less following this instruction set http://forum.xda-developers.com/showthread.php?p=39216236#post39216236 )
My attempts at to remove S-ON using this explanation ( http://forum.xda-developers.com/showthread.php?t=2155135 ) haven't had much for potentially one of two reasons:
Possible reason #1) Step 6 calls for a "fastboot oem boot", which then tries to boot, but there is no working android install. I tried working around this by calling "fastboot oem gotohboot" instead and then booting into recovery (TWRP).
possible reason #2) adb shell doesn't seem to have access to su for me. ("adb shell su" returns "/sbin/sh: su: not found"). I have been assuming that this is the actual problem. I am assuming that this is because I don't have superuser access.
The SuperBoot package doesn't seem to work ( I grabbed it from here http://loadbalancing.modaco.com/download.php?file=r1-ville-superboot.zip referred by http://www.android.gs/root-htc-one-s/ ). I *think* it doesn't work because there is no android version to boot into.
So in short it seems that:
Android requires higher HBOOT requires S-OFF requires Superuser requires Android
Thanks so much for any direction or help, or even just commiseration!
For reference at the moment it is/has:
unlocked
HBoot 1.14 and fastboot is working well, and behaves as expected.
S-On
TWRP (working, and able to access with ADB)
No Working android install
CID: 1111111
Here is a dump of "fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0005
(bootloader) version-baseband: 1.13.50.05.25
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.35.531.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24NW401635
(bootloader) imei: 359902041820139
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8be28a51
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
I found some guide how to unbrick your device:
[HOW-TO] Unbrick Your Android Phone (HTC ONE S) by fabiane79
[TUT] Downgrade/Unbrick Ville S4 by mirGantrophy
[HOW-TO] Fix soft brick & error mounting sdcard by cannondale0815
[TUT] Unbrick Your HTC One S [TUT] by immortal_warrior
Hopefully one of them can help in your case.
If not, please register on xda and ask in the One S Q&A, Help & Troubleshooting forum.
Good luck !

Thread closed. Thank you!

[Solved] AT&T Evita firmware 5.18 - USB debugging not enabled

Hi everyone,
I have been searching for hours and hours to find a solution to my issue. While there is an invalueable amount of information on this forum, the vast quantity can be confusing to NOOBs like myself. Please forgive me if this has already been asked but I did not see anyone discuss a situation such as mine.
I have an AT&T HTC One with the following info that became stuck on the "HTC" logo and then turns off after trying a manual update. To be honest, I am not sure what firmware was attempted to be flashed because I didnt do it myself. I am just trying to help a friend here.
From what I gather, I need to either root the phone using WeakSauce and then try to unlock the bootloader via the HTCDev website. The problem is the phone doesnt boot for me to install weaksauce so I cant get root. Can someone kindly point me in the right direction?
NOTES:
1. HTC Sync does not recognise my device - No phone connected
2. I can enter fastboot and see my device info in fastboot mode (command prompt)
3. The command (adb devices) shows no devices in the list
4. I believe USB debugging was never enabled when the phone was working.
Please, any help will be very much appreciated.
My Info:
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.18.0000
(bootloader) version-baseband: 1.35a.32.45.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.18.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24YWxxxxxxx
(bootloader) imei: 3xxxxxxxxxxxx7
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3783mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d3bfc037
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.140s

Anyone???...Please

As I mentioned before, this forum is like a gold mine for information. The only catch is, you have to spend hours upon hours to look for what you want to accoplish - don't expect anyone to help you even if it is a simple solution - I learned this the hard way!.
I wish someone had simply pointed to me that all I needed to do was flash the stock RUU (Hboot 2.18, Firmware 5.18 At&t) while the phone was in "fastboot USB". The device must me recognised as "Android ADB Composite Device" in device manager.
That's it! My phone is up and running now!
Note: My device bootloader was locked with S-ON and no USB debugging enabled.