Database Info

[Q] Requesting help with Desire S - Posting this after much research

Hi Everyone,
Apologies for this post, I've spent the last week and a half trawling through forum posts for my problem with limited success.
My Desire S had been experiencing random freezes, which would require a battery pull to reboot. I had tried a factory reset from HBOOT, but the phone would still freeze after that.
After the 5th or 6th battery pull, my phone would no longer boot successfully - It would get stuck on the white screen with green 'HTC' Text.
I can still successfully boot into HBOOT. If i select RECOVERY, it shows a black screen with a green triangle, then the screen goes black and the phone vibrates seven times.
If i select FACTORY RESET, the phone freezes and is not responsive.
My Phone details from HBOOT are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011, 17:29:31
I've tried connecting the phone to the PC and running some of the RUUs from here: http://forum.xda-developers.com/showthread.php?t=1002506
specifically: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
If I connect in HBOOT and run the RUU, I get a less than 30% battery power error, but if i connect through FASTBOOT, the RUU will run but gets stuck on a 'rebooting to bootloader' message.
The phone cannot be seen in a devices search in ADB either. Also, In an effort to remove S-ON to load PG88IMG.zip from my SD CARD, i tried the revolutionary and HTC provided methods, both were unsuccessful.
with Revolutionary, it would show "Waiting on device" and then nothing, and with the HTC method, the fastboot command to get the device token wouldn't work due to a command error. I know that the HTC method doesnt officially support the Desire S, but another XDA poster said that worked for his (or hers).
So, I'm asking for help. There are a lot of posts that relate to my issue, but none match 100%. I wanted to figure this out myself, but I defer to your greater knowledge.
Thanks very much, any help would be great.

sorry, as an addendum, I've also successfully created a gold card, if that helps.

Blindshot888 said:
Hi Everyone,
Apologies for this post, I've spent the last week and a half trawling through forum posts for my problem with limited success.
My Desire S had been experiencing random freezes, which would require a battery pull to reboot. I had tried a factory reset from HBOOT, but the phone would still freeze after that.
After the 5th or 6th battery pull, my phone would no longer boot successfully - It would get stuck on the white screen with green 'HTC' Text.
I can still successfully boot into HBOOT. If i select RECOVERY, it shows a black screen with a green triangle, then the screen goes black and the phone vibrates seven times.
If i select FACTORY RESET, the phone freezes and is not responsive.
My Phone details from HBOOT are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011, 17:29:31
I've tried connecting the phone to the PC and running some of the RUUs from here: http://forum.xda-developers.com/showthread.php?t=1002506
specifically: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
If I connect in HBOOT and run the RUU, I get a less than 30% battery power error, but if i connect through FASTBOOT, the RUU will run but gets stuck on a 'rebooting to bootloader' message.
The phone cannot be seen in a devices search in ADB either. Also, In an effort to remove S-ON to load PG88IMG.zip from my SD CARD, i tried the revolutionary and HTC provided methods, both were unsuccessful.
with Revolutionary, it would show "Waiting on device" and then nothing, and with the HTC method, the fastboot command to get the device token wouldn't work due to a command error. I know that the HTC method doesnt officially support the Desire S, but another XDA poster said that worked for his (or hers).
So, I'm asking for help. There are a lot of posts that relate to my issue, but none match 100%. I wanted to figure this out myself, but I defer to your greater knowledge.
Thanks very much, any help would be great.
Click to expand...
Click to collapse
A very rare problem, and since you've done a lot on your phone that were'nt successful, hope for the best that you haven't fried your eMMC. (Check forum for reference)
I would strongly suggest to remove the battery out for atleast 30secs to 1min. Then place it back in.
don't turn on the phone and charge it until full.
Once full, disconnect from power.
Go to bootloader, post your hboot version.
If hboot is still the same, go to fastboot and RUU with the one that your phone came with when you bought it.
It's great that you have a GoldCard, if the step above don't work, try RUU to the latest one.
Now regarding the freezes, I haven't received any freezes from my phone when it was still on stock. It might be a software problem and RUU might fix it. But if its a hardware, you might need to send for repair or maybe replacement.

Thanks very much for the reply Skanob,
Unfortunately, I didn't receive a RUU with my phone when it bought it. I checked through the SC card that was in the phone, but there's nothing that resembles an RUU. If you could please direct me to the latest version you mention, I would appreciate it.
when you say to post my HBOOT version, do you mean for me to post it here on the forums?
Apologies for the questions, I'm still getting used to the lingo.

Blindshot888 said:
Thanks very much for the reply Skanob,
Unfortunately, I didn't receive a RUU with my phone when it bought it. I checked through the SC card that was in the phone, but there's nothing that resembles an RUU. If you could please direct me to the latest version you mention, I would appreciate it.
when you say to post my HBOOT version, do you mean for me to post it here on the forums?
Apologies for the questions, I'm still getting used to the lingo.
Click to expand...
Click to collapse
The phone really didn't came with an RUU file. What I meant is that try to remember the Software Version of the phone when it came when you bought it. That means that software version is the RUU that was installed with it. Also the region.
My phone was installed with the one prior to RUU_Saga_hTC_Asia_WWE_1.48.707.1......
Try to get the RUU of your phone.
Post your HBOOT means post here or atleast tell me what is the version of your bootloader.
Example:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2011, 14:58:38
the latest as of now is RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed.

Thanks again Skanob,
I'll try what you said to do and post the results.
from my initial post, I stated my HBOOT version as 0.98.0002. From what you've told me, should I expect my HBOOT version to change?
Also, I've checked the Europe RUU I attempted to use initially, i can confirm that it was the same version number as my phone. However, it got stuck on the status of "Rebooting to Bootloader" for hours.

Hi Skabob,
Just an update, after performing the steps you told me, my Desire S is still the same, with HBOOT version as 0.98.0002.
The rest of the details are the same as my original post.

Blindshot888 said:
Hi Skabob,
Just an update, after performing the steps you told me, my Desire S is still the same, with HBOOT version as 0.98.0002.
The rest of the details are the same as my original post.
Click to expand...
Click to collapse
I was expecting that your HBOOT would've been changed to the new one, it was an honest error on my end. I thought you've RUUed on the latest one. Sorry about that.
Seeing that you already have a GoldCard, I strongly suggest to RUU to the latest Europe version first.
If it still doesn't work, prepare for a long instruction, read on:
If you cannot use any RUU, the only thing you can do is update your HBOOT to the latest official S-ON.
Seeing that you are still currently S-ON. you wont be able to flash anything on your phone properly.
I myself don't have a proper guide on how you can update it as stock as possible, but maybe you can try what I've done before.
Skanob said:
amidabuddha said:
Ok taking my words back And how do you did this? You flashed the Stock 2.10.401.4 ROM over you bricked phone and it worked? (overwritted the revolutionary hboot or which version was it before?).
Click to expand...
Click to collapse
To make the long story short:
I stupidly get the firmware.zip file inside the ota file. That file had the latest hboot, recovery, and others. I renamed it to the correct pgxxximg.zip (cant remember the correct filename, currently drinking ) to flash it from bootloader.
Everything went well. Everything inside the file updated the corresponding file/partition/image to my phone. Hence letting me be stuck to the "locked" hboot 2.xx.xx s-on. ROM wouldn't boot as I said.
Being on the "locked" state wouldn't allow me to flash anything on the phone as far as i can remember. While writing, it will say has its unsuccessful.
But "unlocking" the hboot let me flash the recovery.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
The OTA file that I've mentioned here is the recently released OTA file for Sense 3.0. Use search on where to get the download link.
Once you have the OTA file, just extract it and gather the firmware.zip file. copy it to your phones SD Card and rename it to PG88IMG.zip (.zip should be the extension of the file, not included in the name of the file).
Boot your phone into bootloader and agree to the phone if it asks you to update. AFAIK it should automatically do its thing.
Also, I remembered that it should be stuck in the middle of its update, just past the HBOOT and RADIO procedure. Once you are on that stuck state, maybe wait for about 10-15mins and see if it doesn't move. That is when I've removed the battery and waited for 30secs to 1min then re-plug it in. So you should pay close attention to what it is doing. Then check your HBOOT and see if it is updated.
If it is successful on updating your HBOOT, you would now need to UNLOCK your bootloader. The HTC unlock method supports the new HBOOT, seeing that you are still on the OLD one, thats one reason it wasn't successful.
What we're trying to do here is to get your phone to a state where you should be able to flash a custom recovery (check partitions if they are corrupted, most especially cache), full wipe partitions, flash a custom rom (pre-rooted stock recommended), then RUU back if you still want stock roms.
Goodluck!
P.S.
These instructions that I've given you are the methods that I would've used and thought of if I was in your situation. I am no expert in ADB nor on how to fix the phone properly. I assume that you already know the world-wide disclaimer: "not held responsible, know what you are doing" blah blah blah...
Also, full charge your phone first prior to doing it.
---------- Post added at 02:51 AM ---------- Previous post was at 02:32 AM ----------
And it's Skanob...

oh! my apologies Skanob! the B and N keys are right next to each other..but still I should have double checked.
Okay, I've tried running the RUU exe file for the RUU you referred me to. unfortunately it didnt move past "rebooting to bootloader".
I also grabbed the OTA file from this link. http://forum.xda-developers.com/showthread.php?t=1282019&page=65
Post number 643 had the link
I renamed the file to PG88IMG, put it on my sd card and loaded the Bootloader on the phone. It scanned the file, but did not give me am option to update.

Blindshot888 said:
oh! my apologies Skanob! the B and N keys are right next to each other..but still I should have double checked.
Okay, I've tried running the RUU exe file for the RUU you referred me to. unfortunately it didnt move past "rebooting to bootloader".
I also grabbed the OTA file from this link. http://forum.xda-developers.com/showthread.php?t=1282019&page=65
Post number 643 had the link
I renamed the file to PG88IMG, put it on my sd card and loaded the Bootloader on the phone. It scanned the file, but did not give me am option to update.
Click to expand...
Click to collapse
it should be PG88IMG.zip (.zip is the file extension). But have you double checked if the HBOOT was updated?

I can confirm that the file I used was indeed a .zip file.
From looking at the HBOOT version, its still sitting at 0.98.0002.

Blindshot888 said:
I can confirm that the file I used was indeed a .zip file.
From looking at the HBOOT version, its still sitting at 0.98.0002.
Click to expand...
Click to collapse
you might want to try to re-create your GoldCard. You might have a bad one.
Does the phone detects the file? There should be a check of .zip files once you boot on bootloader. The screen will take you there within 3-5 seconds after boot and will stay on checking the files for 1-2 seconds.

Blindshot888 said:
My Phone details from HBOOT are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011, 17:29:31
Click to expand...
Click to collapse
Hey man this says it all. You do not need to change hboots, flash RUU or other stuff. Just go to the service center and they will repair it for free. Like this guy did. If you have warranty of course

amidabuddha said:
Hey man this says it all. You do not need to change hboots, flash RUU or other stuff. Just go to the service center and they will repair it for free. Like this guy did. If you have warranty of course
Click to expand...
Click to collapse
or that ^^^^

[Q] Error 155 Such a case has not yet gone.

I have RUU which I used a few times, this time one pops me "error 155" and check the CID still gives me H3G-UK H3G__001 but as I check the version does not show any information. Already changed the cables, I have uploaded the drivers, I downloaded the new files from the RUU.
TEMPERED
RELOCKED
VLE PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-1.08es 50.02.16
PpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
If anyone can solve this riddle?

Ironic this happened to you because I was just trying to go back to ( which I have successfully have done several times before ) my stock RUU file. I am also getting the ERROR 155. Maybe our issues are the same.
I have :
- Gone back to a stock rom
- Relocked Bootloader
- tried to run RUU from within Fastboot ( and every other way I could imagine )
Still get the ERROR 155! The only difference now is that I am coming back off a Jelly Bean ROM ( every other time I was on a Sense 4.04 based ROM)
Could that be the issue? Did it update my HBOOT to one that my stock RUU won't recognize? That seems to be were the RUU fails everytime. It blinks fast but I do beleive the RUU installer says something about HBOOT before it craps out.
Any suggestions or help would be appreciated by us both I presume!
Thanks! :fingers-crossed:

Have you checked the ruu log on your c drive?
The utility usually saves one there.
That may provide some incite.
Sent from rooted awesomeness using xda premium

TheArtiszan said:
Have you checked the ruu log on your c drive?
The utility usually saves one there.
That may provide some incite.
Click to expand...
Click to collapse
Thanks for the reply! I didn't even think to look for a log file for the RUU. Sure enough it was right on the root of my hard drive! The log confirms my suspicion :
<T230213><DEBUG><OUT>INFOchecking hboot version...</OUT>
</DEBUG></T230213>
<T230213><DEBUG><OUT>FAILED (remote: 44 hboot version check fail)</OUT>
Somehow my HBOOT has been updated from the last time I have went back to stock. I don't remember doing an update last time I was STOCK and RELOCKED ( i might of though, can't remember! ). Is it possible that the Jelly Bean ROM I had installed after my last RELOCK, updated the HBOOT?
Sooooo.....I went ahead and I have extracted the HBOOT NB0 file from the ROM.ZIP that the RUU creates in a temp folder. Is there a way to push that onto my phone, then run the RUU?

Hope this helps!
So first off, to the OP Kobi71, sorry if I hijacked your thread! I was going to post about my issue and came across yours first which sounded pretty much identical! So hopefully my experience can help you!
So I got it to work! I have successfully flashed my RUU. What I found out from reading other threads and poking around was that my HBOOT was to new for the RUU file I had. There isn't an update RUU for my phone out there so I decided to give the HBOOT downgrade to 1.06 a shot.
[TUT] Downgrade/Unbrick Ville S4
http://forum.xda-developers.com/showthread.php?t=1990043&page=16
I followed the instructions and it all worked out just fine. READ through the instructions twice if you have too!
Understand them if you decide to try this because your essentially bricking your phone (at first). All being said, worked like a charm. Downgraded to HBOOT 1.06 from 1.13. The only "troubles" I had during the process, was that when I did step 9 and 12 the phone would hang on Sending Reset randomly throughout the process. Probably about ten times. So I did this each time :
absolutelygrim said:
" If it stalls at "Waiting for /dev/sdc12, hold the power button down on your phone about 10 seconds, or until your see "Qualcomm. Inc. Gobi Wireless Modem (QDL mode) disappear from your terminal window, then release it. 10 seconds or less after you do this, emmc_recovery will see your phone and proceed "
Click to expand...
Click to collapse
It also hung at the very end of the process too, so again hold the power button down if that happens to you.
After all that was done, I flashed the stock recovery from the ROM.ZIP that i got from the RUU ( don't know if I needed to do this ). Wiped everything/Factory reset. Then i relocked the bootloader. I then ran the RUU file, and it worked perfectly. Just like before. HBOOT was also "upgraded" to 1.08
Hope this helps your situation!

[Q] Need some help badly, I just messed up my phone

OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.

beppomarx said:
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
Click to expand...
Click to collapse
First, what phone do you have? We will need the first five lines of your bootloader to help you later.
If all you need right now is to try and recover the files and you are on windows, here is a freeware file recovery program I've used in the past. You will need to be able to mount your sd card in TWRP.
http://www.softpedia.com/get/System/Back-Up-and-Recovery/Recuva.shtml
Once you get that done, you do have some problems to work through (Android Revolution Rom is not for our phone.)

beppomarx said:
OK i will admit I am over my head on this one. Frustration kicked in and I think I just lost all the data on my phone (pics and videos and everything which is the worst part). Here's the story.
I was originally on Team Venom 4.2 and was having random reboots.
I tried fixing by updating the Radio to ATT 3.18: http://d-h.st/DcT in this thread: http://forum.xda-developers.com/showthread.php?t=1694012 I flashed WITh the RIL (under the line that says do not flash these with newer roms) yeah I know.
flashed 3.18 again without RIL (above the 'do not flash' line
flashed att 2.0 radio
so now my radio still isnt working, tries to prepare sim card and will not work.
now I am trying to flash a new ROM to rewrite everything. tried to install android revolution HD. http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
flashed the android revolution boot.img file and attempted to flash the android revolution rom and would not flash, rebooted twrp after 30%
messed around in twrp a bit and hit factory reset. thought that would do a reboot of the android install. looks like i just formatted my sd card AND deleted android operating system. i cannot reboot into system 'no android os installed' and under twrp file manager i have NOTHING LEFT in my sd card. except the twrp folder. the phone has not been rebooted since.
DID I JUST LOSE EVERYTHING?
i am seriously interested in getting the pictures and data off the sd partition somehow. that is my main concern, i will deal with reinstalling android afterward.
any help will be rewarded, thank you in advance.
Click to expand...
Click to collapse
Ok, first, you're all over the place. Why did you install a radio+RIL when it explicitly tells you not to? It's actions like this that get people like you into a lot of trouble and destroys phones.
Secondly, there is no Android Revolution HD for this device. I believe you have the HTC One XL / at&t One X (Evita) judging from your post, but like I said there's no ARHD ROM for the Evita, only for the HTC One X (Endeavoru). This leads me to believe that you're jumping between the two device forums, very bad idea, none of the stuff from the Endeavoru forum is compatible with our phone.
You're lucky the ROM install stopped otherwise you would have bricked your phone. Long story short, you have no OS because the ROM install didn't complete, you have a corrupt boot partition because you flashed the ARHD boot.img which isn't compatible. In future do not stray outside our device forum for any reason at all. Here's our forum main page, bookmark it:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Next. Performing a factory reset in TWRP recovery does not wipe user data (images/music etc). I'm not sure what you've done but the factory reset in recovery wasn't it. A factory reset performed in the bootloader does however corrupt the sd card, so never do a factory reset from the bootloader.
You might have a chance at saving some of your data using a data recovery tool in Windows. You'll need to mount usb storage in TWRP for Windows to access the sd. Do not under any circumstances do any writing to the sd card before you attempt to save your data.
In conclusion, you've made numerous mistakes with your device. You need to slow down a bit and educate yourself a bit better, a lack of knowledge when it comes to modifying devices is a very dangerous thing.
Please post the first five lines of your bootloader.
Sent from my Evita.

i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
ok guys thanks so much so far i will pick up again after work today.
bootloader says:
TAMPERED
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.19as.32.09.11_2
OpenDSP-v34.1.0.45.1219
eMMC-boot
Apr 2 2012,21:08:24
I'm 99.9% i was s-off before this all...

There isn't and never has been an Android Revolution ROM in this forum. It's kinda easy to make the mistake, the forums are named similarly.
I'm 99.9% sure you weren't s-off before all this. A phone can't change the security status without you doing it manually. It just can't happen. Did you actually go through either the Facepalm or Rumrunner s-off processes?
Well, you definitely have the Evita (HTC One XL / at&t One X) so make sure you stay within the forum I linked to earlier.
Good luck with attempting to recover your data, I hope you get at least some of it back.
Sent from my Evita.

Ok so as far as mounting my sd card in twrp, there's something up with my screen touch input I think... I am not able to click that particular box in the 'mount' menu. It seems like that part of the screen was not clickable when installing roms and such but once I get into android everything works perfectly.
Is there a way to rotate the screen in twrp?
Also by looking at my bootloader info once I get my sd card mounted and recovered best as I can, what is my best plan of action? Re-lock and flash a stock att ruu and begin from scratch or what? Or just try and load a correct radio and rom? I'm not a complete newbie I know I made a foolish mistake but I have done this quite a few times playing on the inspire, cha-cha, my kids nabi 2 tablets and on this att one x. This is the first time I have gotten really stuck in probably 35 flashes. Just this time I might be over my head...

To be honest I've never tried rotating the screen while in recovery, so I'm not sure about that. Exactly which recovery type (CWM/TWRP) and version number are you using?
I think your best plan of action would be to run an RUU, this will bring everything back to the way it should be. You're lucky in the sense that you're still on quite an early firmware version, so you should have a couple of RUU options. One thing to be careful of though, absolutely do not run a jb RUU if you have SuperCID, it will brick your device. SuperCID + s-on + jb RUU = brick. We should check your CID just in case, connect your phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
Sent from my Evita.

beppomarx said:
i could have sworn i got the android revolution rom from the att one x forum but i suppose not....
Click to expand...
Click to collapse
There is absolutely no ARHD ROM for EVITA. You've made a grave error, and as timmaaa mentioned, you are lucky your phone isn't a paperweight now.
EVDEAVORU is partitioned completely differently from EVITA, so all bets are pretty much off on whether your data is still intact or not. The ROM itself may have overwritten your data. Also, if you happened to do a factory reset in hboot instead of TWRP (as you mentioned) this will corrupt the SD card on modded EVITAs (known issue, and somewhat common error).
Your best bet is to get the phone back up and running using timmaaa instructions. Then see if the files are still on the SD. If the data files aren't easily visible, you can also try data recovery programs to see if they can be salvaged (sometimes corrupted files get dumped to a temp folder, or otherwise recoverable).
But I wouldn't hold my breath on recovering the files. This is what always puzzles me (why folks never back their data, then freak out when its gone of damaged). If your data is important to you, its important enough to back up. And there are so many easy methods to do so (with built-in cloud backup apps and whatnot) yet so many folks neglect to do that. And all you are left with is regret when things do south. Its pretty much a no-brainer to backup anything important to you when modding the phone. I'm puzzling why so many folks never do it.

So since I have the 1.09.000 hboot i am going to download and install this:
1.85.502.3
File Timestamp: 25/05/12
Publically Seen: 06/06/12
Android: 4.0.3
Kernel: 3.0.8-01155-gca24d1e
hboot: 1.09.0000
radio: 0.17.32.09.12_10.86.32.08
adsp: 28.1.0.32.0504
wcnss: 1031120A
tp_syn3202: 3.0_PR1100755
tz: 001.031.511
sbl1: 001.031.503
sbl2: 001.031.501
sbl3: 001.031.502
OTA: OTA_Evita_UL_Cingular_US_1.85.502.3_R2_NEW_NFCPHON ESTORAGE-1.73.502.1_release_263287jkmeqj8u75z409z9.zip
RUU: RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17. 32.09.12_10.86.32.08L_release_262092_signed.exe (Download)
Source: evita-ics-crc-3.0.8-271616b.zip
is this my best bet? I am going to try and check my CID status right now just need to download the android SDK and get that going...
**EDIT**
my CID is 11111111. is that superCID?
**EDIT**
looking for a way to remove superCID. If i just go S-off am i OK to run a RUU or should I keep looking to change my CID back?
**EDIT**
just downloaded WinDrid HTC One XL Toolkit and seems to be up and running fine. my plan so far is to S-off and run the RUU I posted above but I will wait for someone to chime in before I do anything else.. I feel like I am on the edge here and don't want to brick it... I can't find any way so far to return my CID but from what I read if I am S-off it should keep me safe.

S-off won't work unless you're able to boot into a ROM. I'd forget about using a toolkit for now, it completely bypasses some much needed learning, and doesn't always work anyway. I believe all you need to do is relock your bootloader and then run the RUU.
Sent from my Evita.

Ok I will look into how to re-lock that after work today. Can anyone else confirm this? Not that I don't trust you but wording it like 'I believe this will work' makes me ask again...

I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Sent from my Evita.

timmaaa said:
I'm 99.99% sure it's only the jb and above RUU that you need to worry about while s-on and SuperCID.
Click to expand...
Click to collapse
ICS RUUs are free of the S-on and SuperCID bug. Plenty of folks have flashed that RUU (such as 2.20) with SuperCID with no issue.

so I am going to relock the bootloader, it's as simple as 'fastboot oem lock'? that's it? before doing so should i bother s-off first? here's my plan of action:
s-off
relock bootloader
run 2.20.502.7 ruu
unlock bootloader again
install twrp
load custom rom
that should work correct?

If you s-off first, I believe you do not need to relock the bootloader to run the RUU. Just s-off, then run the RUU.

As I've previously mentioned, you won't be able to get s-off unless your phone will boot a ROM. The above process looks right.
Sent from my Evita.

got back to stock just fine, now to work my way back to modded. You guys are the best thank you a million.

Please hit the thanks button on any post that you've found helpful on XDA.
Sent from my Evita.

Remember also to either s-off or change cid back to normal, it will assist in the future if you get in a jam like this.
Although s-off and flashing a rom for a different phone(like you did) may have ended up much worse as some of the checks that likely saved you will be disabled.
At very least do not OTA/RUU update to Jellybean while you are s-on and supercid!

[Q] Manual update, need help

Hello,
I am trying to update my phone without losing all of my data and of coarse, root as well. Below is what I am working with:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19AS.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Recovery TWRP v2.6.3.0
Android Version 4.0.4
Sense 4.0
software # 2.20.502.7.710RD
API Level 4.23
HTC extension 403_1_GA_20
Kernel 3.0.8-01558-g7f75e5b
baseband 0.19as
build 2.20.502.7
That's probably way more than you needed to know, but I like to be through. (c;
anyhow, I want to update everything to the latest version... firmware, hboot (if applicable), OS, radio, etc. without losing my data, recovery or root.
I have downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe from HTC
and OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k.zip from my phone.
I tried upgrading using adb sideload (renaming zip from carrier to update.zip) and it failed
I tried upgrading using install feature of TWRP using update.zip and it failed
I then thought I will just extract the .img files and flash using adb, but quickly discovered I don't know what .img file is which. If some one has a better way of accomplishing my goal i am all ears, however if someone can assist in identifying which .img files i should flash and how to best approach it I would be very appreciative.
the files extracted are attached (didn't want to flood the post)

It's better to provide too much information than not enough, which is what most people do lol.
I think you're a bit misguided on the whole process so I'll break it down for you. You've downloaded the right RUU but you don't need the OTA. You're also approaching it with the wrong methodology, you're not meant to extract the RUU and flash any image files manually. All you need to do is connect your phone to your PC in fastboot mode and run the RUU exe program in Windows then follow the prompts. You must get s-off first though, very important, do not skip this step!
You will lose your custom recovery and root, there's no way around that. But getting them back is as easy as flashing the custom recovery again and installing root or a rooted ROM. The RUU shouldn't wipe anything from your sd card but it's a good idea to make a backup just in case. You'll lose text messages, call logs, things like that but you can back those up using backup apps before the process.
So head over to the Rumrunner site and get s-off first and you'll be good to go.
Sent from my Evita

timmaaa said:
It's better to provide too much information than not enough, which is what most people do lol.
I think you're a bit misguided on the whole process so I'll break it down for you. You've downloaded the right RUU but you don't need the OTA. You're also approaching it with the wrong methodology, you're not meant to extract the RUU and flash any image files manually. All you need to do is connect your phone to your PC in fastboot mode and run the RUU exe program in Windows then follow the prompts. You must get s-off first though, very important, do not skip this step!
You will lose your custom recovery and root, there's no way around that. But getting them back is as easy as flashing the custom recovery again and installing root or a rooted ROM. The RUU shouldn't wipe anything from your sd card but it's a good idea to make a backup just in case. You'll lose text messages, call logs, things like that but you can back those up using backup apps before the process.
So head over to the Rumrunner site and get s-off first and you'll be good to go.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the response!
I figured I didn't need both the ruu and the ota, but I didn't know if one had newer componets than the other. Also, I didn't know that s-off had been accomplished, last I checked it was still unavailable.
The reason I was thinking of flashing the images manually was because it was so simple for the nexus 7 upgrade, and prevented data loss. The ruu says data loss will happen on it, so I was skeptical to run it as is. So now I am off to check out that link and get this party started! Thanks again!

Spy_64 said:
Hello,
I am trying to update my phone without losing all of my data and of coarse, root as well. Below is what I am working with:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19AS.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Recovery TWRP v2.6.3.0
Android Version 4.0.4
Sense 4.0
software # 2.20.502.7.710RD
API Level 4.23
HTC extension 403_1_GA_20
Kernel 3.0.8-01558-g7f75e5b
baseband 0.19as
build 2.20.502.7
That's probably way more than you needed to know, but I like to be through. (c;
anyhow, I want to update everything to the latest version... firmware, hboot (if applicable), OS, radio, etc. without losing my data, recovery or root.
I have downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe from HTC
and OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k.zip from my phone.
I tried upgrading using adb sideload (renaming zip from carrier to update.zip) and it failed
I tried upgrading using install feature of TWRP using update.zip and it failed
I then thought I will just extract the .img files and flash using adb, but quickly discovered I don't know what .img file is which. If some one has a better way of accomplishing my goal i am all ears, however if someone can assist in identifying which .img files i should flash and how to best approach it I would be very appreciative.
the files extracted are attached (didn't want to flood the post)
Click to expand...
Click to collapse
If you get stuck or need more info, I threw together a guide with info from the forums that may help:
http://forum.xda-developers.com/showthread.php?t=2593037

By the way, tell me about your footer "HTC Evita Gummy 4.4.2 | Torched KK Kernel S-off | 2.14 | Modified TWRP 2.6.3"..... Cooked rom? How do you like it? How does it compare to stock?

Madcat8686 said:
If you get stuck or need more info, I threw together a guide with info from the forums that may help:
http://forum.xda-developers.com/showthread.php?t=2593037
Click to expand...
Click to collapse
Thanks!

Spy_64 said:
By the way, tell me about your footer "HTC Evita Gummy 4.4.2 | Torched KK Kernel S-off | 2.14 | Modified TWRP 2.6.3"..... Cooked rom? How do you like it? How does it compare to stock?
Click to expand...
Click to collapse
It's a really good Rom. Extremely stable with excellent battery life. It's my current "go to" Nandroid back up I use during the day now. I flash new Roms almost daily when I don't need the phone for work. It's based off AOSP and that's what I like most about it. It has tweaks but not too many. For someone making a jump to 4.4+ Roms, I would highly recommend this one as a starter. We are very fortunate to have many like this and I'm getting around too try all of them (we are very lucky to have some talented individuals working Roms in our Forum.)
As for stock, I have to be honest, I can hardly remember what stock is like. I tried most of the stock Roms a few months ago and I have Nandroid backups of them. I remember a few were very stable but as I said, I'm a sucker for pure AOSP.
AHHH shoot, I suppose I just fielded a question meant for Timmaa, my bad!

Madcat8686 said:
It's a really good Rom. Extremely stable with excellent battery life. It's my current "go to" Nandroid back up I use during the day now. I flash new Roms almost daily when I don't need the phone for work. It's based off AOSP and that's what I like most about it. It has tweaks but not too many. For someone making a jump to 4.4+ Roms, I would highly recommend this one as a starter. We are very fortunate to have many like this and I'm getting around too try all of them (we are very lucky to have some talented individuals working Roms in our Forum.)
As for stock, I have to be honest, I can hardly remember what stock is like. I tried most of the stock Roms a few months ago and I have Nandroid backups of them. I remember a few were very stable but as I said, I'm a sucker for pure AOSP.
AHHH shoot, I suppose I just fielded a question meant for Timmaa, my bad!
Click to expand...
Click to collapse
Thanks for the insight. (c; Know of any place i can see screenshots or more info? better battery life is very important to me. I have been steering clear of aftermarket rom's because it always seems that there is always one thing or another that doesn't work... and it always seems to be either or a combination of, tethering, GPS, MMS, or wifi, all are rather important to me. (c;

Spy_64 said:
Thanks for the insight. (c; Know of any place i can see screenshots or more info? better battery life is very important to me. I have been steering clear of aftermarket rom's because it always seems that there is always one thing or another that doesn't work... and it always seems to be either or a combination of, tethering, GPS, MMS, or wifi, all are rather important to me. (c;
Click to expand...
Click to collapse
The Roms are in the development and original development threads. I don't want to steer you down the wrong path and tell you that one Rom is better than another because that's not the XDA way. It implies that one dev's work is better or inferior in some way (plus it's against the rules.)
I can recommend Gummy Rom as a starter if you are ready to try out a custom Rom. I like it and I consider it a daily driver but a couple of the others are just as good. You just have to flash and find out. Many of the 4.4+ Roms on our Forum are stable and work really well.

well I have tried two different PC's running different OS's, and two different USB cables and I cannot get past
....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (11/120)
Waiting
Test 2: Booting device
Waiting for ADB (49/120)
Device detected.....................
[TTTT********************************************** **********]
Press ENTER to exit
Click to expand...
Click to collapse
when running rumrunner. I cannot seem to find anything out there that fixes it either )c;
Any thoughts?

Sometimes Rumrunner says it's failed but it has actually worked, does it still at s-on in your bootloader?
Sent from my Evita

timmaaa said:
Sometimes Rumrunner says it's failed but it has actually worked, does it still at s-on in your bootloader?
Sent from my Evita
Click to expand...
Click to collapse
Yah bootloader still says s-on. )c;

It's possible that it's the ROM/kernel that's the problem. You might consider flashing the latest MagioRom, I've had confirmed reports of success with that ROM.
Sent from my Evita

timmaaa said:
It's possible that it's the ROM/kernel that's the problem. You might consider flashing the latest MagioRom, I've had confirmed reports of success with that ROM.
Sent from my Evita
Click to expand...
Click to collapse
Wont I lose all my data doing so?

What do you mean by data? If you mean your images, music and such on your sd card, no you won't lose it. You never lose that when changing ROMs, I've flash multiple ROMs every week for the last few years and I've never once lost that data in all this hundreds of flashes.
You will lose your text messages, call logs, apps, stuff like that, but you can use several apps to back those up before you flash and then restore it afterwards. Do you use Titanium Backup? If not I suggest you look into it, it allows you to backup pretty much everything.
Sent from my Evita

timmaaa said:
What do you mean by data? If you mean your images, music and such on your sd card, no you won't lose it. You never lose that when changing ROMs, I've flash multiple ROMs every week for the last few years and I've never once lost that data in all this hundreds of flashes.
You will lose your text messages, call logs, apps, stuff like that, but you can use several apps to back those up before you flash and then restore it afterwards. Do you use Titanium Backup? If not I suggest you look into it, it allows you to backup pretty much everything.
Sent from my Evita
Click to expand...
Click to collapse
Mainly just, well data and apps...stored on sd or internal storage. That's great news though!

No problems. The rule of thumb is this: if it's worth worrying about it's worth backing up, just in case.
Sent from my Evita

I was going to backup using twrp to USB and an OTG cable but apparently that is not implemented in this kernel... so now its onwards to titanium backup... i haven't tried it for a few years now.

another question.... the romrunner page has modified hboots for htc one....does that include onex? could I use it once i get this all sorted out?

No. You don't want to use a modified hboot. Also, in TWRP recovery you can use the mount usb storage feature so your internal storage shows up on your PC and you can backup that way.
Sent from my Evita

[Q] Ask a Stupid (Firmware) Question

Okay....so I need to twiddle around with my trusty old HOX in order to solve the constant rebooting issues. (I also want to jump ship off of the memory-heavy Viper Venom that's on it to just straight CM or something similarly light weight)
To do that I've got to update the firmware.
And to do that... first I have to identify what bloody firmware I have so that I use the correct updating method and don't brick my one and only device.
I'm not a total noob... I've been working on a beginner/moderate level with Android for 3 years now... I can get around ADB (typos not withstanding) reasonably well, push commands, get to hboot, know fastboot and such... but I am just not finding the specific answers I need right this moment to get this work done. So if Someone can point me in the proper direction, I would be muchly appreciative.
Right Now my bootloader screen says the following
Tampered
Unlocked
Evita PVT Ship S-ON RLHboot 1.09.0000
Radio 0.20os.32.09.10_2
OpenDSP-v31.1.0.45.0815
eMMC-boot
Click to expand...
Click to collapse
So, who can tell me which firmware version contains Hboot1.09? Once I know that, I can start the process of SuperCID and S-OFF to make these updates. Barring that, anyone who can point me to a one-click unlock tool would be great too... the ones I find on the first few pages of the forum all recommend firmware newer than what I know is installed on here according to the above into, and I am leery to use them for risk of bricking my one and only phone.

Your current firmware is actually irrelevant, you need not worry about that at all. All you need to do is get s-off, which should be a sinch. Because you don't have SuperCID (I'm assuming from your last paragraph) you really only have one option, which is the Rumrunner method. It should work with Viper installed, if not it has a good success rate with the Kickdroid ROM.
Rumrunner S-off
Sent from my Evita

So I did have SuperCID... a readCID command demonstrated that.
and thanks to your assuaging my fears, timmaaaa, I was able to flash to 2.15 without a problem.
the problem now... is even after pushing TWRP every way I know how, I can't get into recovery, even with fastboot erase cache. ugh I feel like yanking my hair out.
but at least the phone hasn't randomly slowed down or rebooted since flashing the new firmware. (and the pesky double-reboot that made flashing it such a core in the first place is fixed too)
::edit:: gonna spend the next hour redownloading the venom ro so I can push the boot.img file, maybe that will fix things.

Did you check the md5 of the recovery download?
Sent from my Evita

timmaaa said:
Did you check the md5 of the recovery download?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did. I also tried to install it via a few onboard solutions like goo.im. no go. it says it's been installed, fastboot insists the phone is unlocked and s-off; but it boots to the flash screen, tries to load recovery, fails, and reboots to the rom.
I am going to assume that the unlock is fubar somehow and start from scratch by installing 2.20 and using the HTC unlock, and go from there.
now if only damned downloads didn't take 5 hours on my slow rural connections... thank you isp conglomeracy.