Database Info

[Q] Using official HTC unlocker for Sensation, Help installing Cyanogen

I recently "unlocked" my HTC Sensation 4g through HTC's official method. However, after successfully unlocking it, my phone is still set on S-On. Because of this, I am not recognized as a superuser, and so I cant boot into Clockwork Mod Recovery. Can anyone who knows more than me about this please give me a hand? This is my first time attempting any of this.

to make sure i understand this correctly- your phone now says "unlocked" at the top,but is still s-on?
what have you done to root?
once you have a truly unlocked bootloader,you can install a recovery thru that bootloader,and then flash superuser in that recovery.
having superuser permissions within a rom and being able to boot to a recovery shouldnt have anything to do with the bootloader.
if you are unable to install clockwork,or some other custom bootloader thru htcs "unlocked" bootloader,then they have lied to us... its not truly unlocked. that or something happened during the unlock process,possibly.
sorry im not of more help,its been awhile since i looked at the developer website. are there support forums there?
if everything is functioning correctly and you cant load whatever you want thru hboot,this unlock program is a joke. you could have gotten s-off with revolutionary or an xtc clip and not alerted them to the fact that you were messing with software and potentially "voided all or parts" of your warranty.
please keep us updated on this- im very interested to know how it turns out.

Thats exactly what it says. The method I used is on the front page of the htc dev site.
(the forum wont let me post outside urls yet)
The top of my H-boot screen says
"*** UNLOCKED ***
PYRAMID PUT SHIP S-ON RL
HBOOT-1.80.0000
eMMC-BOOT"
So this is a problem. I think...
I just figured the official method through HTC would be the easiest and safest

Oh and when I try and flash Clockwork Mod Recovery through ROM manager this is the message I get
"You must root your phone for ROM Manager to function. Superusuer was not found at /system/bin/su or /system/xbin/su. Use Google Search on your computer to find instructions to root your phone."
or
"An error occurred while attempting to run privileged commands."

So what have you done to root besides unlocking the bootloader? Just tried to install rom manager and clockwork?
Unless you have done something else,you are not rooted,you are just unlocked. Search the sensation forum for a PxxxIMG file that is clockwork recovery. When named that,and placed on root of your SD,hopefully your hboot will find and flash it.
Once you have done that,delete the PxxxIMG From your SD card,and place the superuser.zip file on it. Enter recovery thru hboot,and flash superuser.zip.it will install the root files.
After that you should be rooted.
Later I can try and find some links if you can't find them. PxxxIMG will be specific to the pyramid,I'm not sure what it is. For example,this type of file for the thunderbolt is PG05IMG.
Hope that helps.
edit:
here are some links for you:
download clockwork from here or multiupload (found the download in this thread)
download from one of those 2 places. rename the download "PG58IMG" and place on the root of your sd card. boot to hboot(power+vol down). when asked to update chose yes.
download superuser from here (this is the one i always use. found it here)
after deleting or renaming PG58IMG from your sd card,put the superuser.zip,boot to hboot,select recovery,then flash the superuser.zip.
hope it helps
Sent from my ADR6400L using XDA Premium App

Well I tried what you recommended and it did not work. But then I tried revolutionary and I managed to get s-off. However HBOOT doesnt recognize the P58IMG file. It just keeps saying P58IMG.*** NO IMAGE. (*** being different file types).
Im not sure if I need to try the recovery now that Im s-off but I cant flash the superuser file either.

gah! i wish you hadnt run revolutionary yet,as now we wont really know if your "unlocked" s-on hboot would have allowed the flash like a truly s-off one will.
one thing i know for certain,is that the troubles youre having werent because you were s-on. being able to place the superuser app,aND matching binary within the OS is not dependent on the hboot being s-off. s-off is handy,as it allows another method of flashing partitions like the radio and recovery. in the old days,before all the exploits were patched,alot of devices were rooted and a custom recovery installed from within the OS without ever bothering with the bootloader. the eris is a good example- prolly 95% of the eris community is still s-on and they change roms and such all the time.
-so i guess you downloaded the PG58IMG from multiupload? when i tried the first link,there was no valid attachement.
-you did name PG58IMG,correct? if you did name the file "P58IMG" maybe thats the prollem?
-make sure your SD card is formatted FAT32( not just plain FAT) and make sure you put the file on the root(not inside another folder)
*assuming you named the file correctly,have a FAT32 sd card,and placed the file onto the root of the SD,what happend when you went to hboot?
heres what should happen: the green writing flashes,hboot finds a PG58IMG file,then youll see a blue status bar on the far left as the phone unpacks it,then gold as it checks it. since the recovery file is small youll see that very fast. then you should get the "vol up to update" prompt.
if you have named the file correctly,FAT32 card,etc. maybe you just got a bad download. try downloading it again.
i downloaded and checked it- it contains a recovery image and an android info file,so it should be good to go. if you want to verify the integrity,the md5 i got is: 940fa14af3dcd055132adf292f668ad3
last and not least,if you ran revoltuinary it should have installed clockwork for you. if you dont want to keep messing with PG58IMG files,just run revoltionary again. it should detect your s-off,then ask if you want to install clockwork.
im sure youre getting a lil fustrated,but the method for rooting new phones is what im reccomending you to do:
1)unlock bootloader(revolutionary or htc unlock)
2)install recovery thru bootloader
3)install superuser files from recovery
it does work,i promise... ive done it many times on my thunderbolt.

Awesome, everything worked great. I had a few hitches but I figured them out. Thank you so much for all the help, I really appreciate it.

Until just now... I installed cm7 and now when i boot up my phone all I see is about 6 seconds of the cm7 start up animation (the one with the blue android guy on a skateboard). Then the phone starts up that same animation again. Its been doing this for about an hour now.

barnodian said:
Awesome, everything worked great. I had a few hitches but I figured them out. Thank you so much for all the help, I really appreciate it.
Click to expand...
Click to collapse
please list the hitches and what you did to make it work,so others will benefit that find this in future searches.
barnodian said:
Until just now... I installed cm7 and now when i boot up my phone all I see is about 6 seconds of the cm7 start up animation (the one with the blue android guy on a skateboard). Then the phone starts up that same animation again. Its been doing this for about an hour now.
Click to expand...
Click to collapse
sounds like you didnt do a full wipe. pull the pattery,go back to recovery thru hboot,and wipe data/factory reset,wipe cache,wipe dalvik chache,and format /system. i dont usually format /system,but when youre stuck in a bootloop it cant hurt

well it was my own dumb fault... like extracting the .zip files instead of leaving them compressed.
And yeah now i totally have cm7 running! thanks for all the help man. I really appreciate it

No prollem.glad you got it figured out.
Sent from my ADR6325 using XDA App

Well they were my own fault. Like forgetting to leave the .zip files compressed. Otherwise everything is working great and I'm running cyanogen perfectly. Thanks for all the help
Oh thats why I didnt see the response I thought i sent... it was on the second page. my bad. well now you get thanked twice.

[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] VM HTC One V CDMA Sooooo Messed Up!

I am new to all of this, and dumb as a rock. That being said, I have soft-bricked this phone. I loaded PACman v15.3 primoc inyourface09.zip first
Went to boot loop. In trying to fix that, I did a bunch of other stuff that didn't work and I don't really remember what all I did-been a week of this chaos. Last thing I did was load Cyanogen Mod 9, which boot looped. Still shows this when I go to fastboot:
*** UNLOCKED ***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0928
eMMC-boot
May 14 2012.20:27:30
Here is other possibly useful info.
MWID: Hex:A10000023E805EE
SN: FA2AJX40824
MB: 31B15AD04215
MEID Dec: 270113181115205870
SD Checking
LOADING
wRONG OR NO ZIPPED IMAGE [PK76IMG.ZIP]
lOADING
NO IMAGE [PK76IMG.NBH]
same for .TAR, .AES, .ENC
I then loaded gapps-jb-20120726-signed.zip, JmzStockDeodex-VirginMobile.zip and JmzStockodex-VirginMobile.zip
I still get the HTC white screen with red disclaimer. Then goes to buzz, lightning, Red Virgin Mobile splash screen with sound, and reboots to HTC white screen-boot loop.
When I got a PK76IMG.ZIP and tried to flash it, it says it can't open the zip file.
But I can still get to the Hboot, Fastboot screen and recovery. Backup was empty :s
Tried to load a different recovery, but just like pacman, twrp won't go away.
And just so you know, I did factory reset a gazillion times.
Help! What have I done, and what can I do to fix it? I am comfortable with command lines, poking around in code, etc., but not with a totally new device like this...obviously, too much to mess up.

.
..

Still need serious help! found a possible reason for problem
Seems my HBoot 1.53.00.00 is for GSM; my phone is CDMA. Do how do I install/where do I download the correct hboot for vmt120 (the model number for this One V)?
I have been researching the phone and the problem, not just posting for help ad nauseum. I really need some help, please.
Thanks in advance, folks.

goofed again said:
Seems my HBoot 1.53.00.00 is for GSM; my phone is CDMA. Do how do I install/where do I download the correct hboot for vmt120 (the model number for this One V)?
I have been researching the phone and the problem, not just posting for help ad nauseum. I really need some help, please.
Thanks in advance, folks.
Click to expand...
Click to collapse
Were you able to get a backup of the original config, (before you first rooted it?)
(I have the same phone, same radio, (hboot 1.57), for NTelos, and am able to boot, but just no wifi/mobile data).. So, if you have a good backup, I might be able to trade a stock kernel that works for my phone.
I'm desperate also, so I know how it feels to have a machine that doesn't work,...

goofed again said:
I am new to all of this, and dumb as a rock. That being said, I have soft-bricked this phone. I loaded PACman v15.3 primoc inyourface09.zip first
Went to boot loop. In trying to fix that, I did a bunch of other stuff that didn't work and I don't really remember what all I did-been a week of this chaos. Last thing I did was load Cyanogen Mod 9, which boot looped. Still shows this when I go to fastboot:
*** UNLOCKED ***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0928
eMMC-boot
May 14 2012.20:27:30
Here is other possibly useful info.
MWID: Hex:A10000023E805EE
SN: FA2AJX40824
MB: 31B15AD04215
MEID Dec: 270113181115205870
SD Checking
LOADING
wRONG OR NO ZIPPED IMAGE [PK76IMG.ZIP]
lOADING
NO IMAGE [PK76IMG.NBH]
same for .TAR, .AES, .ENC
I then loaded gapps-jb-20120726-signed.zip, JmzStockDeodex-VirginMobile.zip and JmzStockodex-VirginMobile.zip
I still get the HTC white screen with red disclaimer. Then goes to buzz, lightning, Red Virgin Mobile splash screen with sound, and reboots to HTC white screen-boot loop.
When I got a PK76IMG.ZIP and tried to flash it, it says it can't open the zip file.
But I can still get to the Hboot, Fastboot screen and recovery. Backup was empty :s
Tried to load a different recovery, but just like pacman, twrp won't go away.
And just so you know, I did factory reset a gazillion times.
Help! What have I done, and what can I do to fix it? I am comfortable with command lines, poking around in code, etc., but not with a totally new device like this...obviously, too much to mess up.
Click to expand...
Click to collapse
Hey! Just restore your Radio back to stock. Google "RUU Stock for HTC ONE V VM" and there are some articles that could help you. Basically, you just run the RUU and extract some files in it.
---------- Post added at 11:23 PM ---------- Previous post was at 11:17 PM ----------
plebevt said:
Were you able to get a backup of the original config, (before you first rooted it?)
(I have the same phone, same radio, (hboot 1.57), for NTelos, and am able to boot, but just no wifi/mobile data).. So, if you have a good backup, I might be able to trade a stock kernel that works for my phone.
I'm desperate also, so I know how it feels to have a machine that doesn't work,...
Click to expand...
Click to collapse
So guys, if you still have this problem here' what you'll need to do.
Originally Posted by CafeKampuchia
Before you start, you will need to set up your computer to properly recognize the phone. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync.
About HTC Sync: The only reason you need HTC Sync installed is for the USB drivers that come with it. But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
Here we go:
First of all, google "RUU of HTC ONE V CDMA" or sumthing. then you'll find alot of things. Choose the SPRINT/VM Then:
1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open,(LET IT OPEN UP, DONT DO ANYTHING!) find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT/B] using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
7. Re-run the RUU. It will restore the device to it's original condition, locked (though *** RELOCKED ***) and unrooted.
Once the install is done you'll have unlock the bootloader again using the token you already have from the first time, reflash CWM Recovery and re-root. All this will be 10x easier than the first time.
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!

Unable to do OTA from 1.09

I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks

stampy101 said:
I have a AT&T One X rooted
HBOOT-1.09.0000
RADIO-0.17.32.09.12
I am attempting to do the OTA's or RUU to bring it up to current because I realized since I had not touched it since first purchased and rooted so none of the OTA's went through. I never gave myself time allowed to figure out how to send them.
Well now I'm trying and I have gotten myself in to a hot mess.
I first tried using the FUU Upgrades provided by Flashalot but it said "wrong update" and I could not find a reason. I backed up a couple and tried 2.14. Well eventually it just stayed at the fastboot "HTC" screen for nearly an hour and appeared locked up. So I pulled it and rebooted. It would not let me get past the boot up screen until I cleared cache's and went back to my stock rom (cmod 10).
Now it will not mount "SD Card" when connected USB and in TWRP. I am also unable to download any files to it via browser or launched phone because it says no SD Card installed.
I attempted to send any of the OTA's via fastboot and it hangs (giving it hours...overnight even). I did writecid 11111111 before sending some with same results.
Any suggestions?
Thanks
Click to expand...
Click to collapse
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita

FUBAR?
timmaaa said:
First question is do you have s-off?
Second question is did you perform a factory reset from the bootloader at some point? I ask this because it looks like your sd card is corrupt, and that's what happens when you perform a factory reset from the bootloader on a modified Evita. Either way I believe you need to wipe your sd card with TWRP before it'll become usable again. If it still isn't usable after a wipe, try mounting it to your PC again so you can format it with Windows.
My last question is what is your end goal? Are you wanting to run a stock ROM and that's why you're wanting to install OTA updates? The rule of thumb for modified phones is to never install OTA updates on them. If you're just looking to update to the latest/latest needed firmware, you can just flash a firmware package or run an RUU. You must have s-off to do this though.
Another thing I should mention is that you don't use fastboot to install OTA updates. It seems like you're not exactly sure about what you're doing, which can be a very dangerous thing when messing with a modified device. I think you need to do a bit more research before continuing ahead. Tell me exactly what your end goal is though and I'll provide as much information as I can.
Sent from my Evita
Click to expand...
Click to collapse
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.

stampy101 said:
OK So it sounds like I've probably corrupted my memory from what you are saying. Any going back?
1. S-Off. I'm going with no. It was 2 years ago when I rooted it and installed CM10. I do not recall doing this but just flashing CM.
1a. Attempting to do it now just shows error 99 unknown error...
2. Yes. I do believe that I had hit the factory reset. Attempting to do the wipe in TWRP shows "success" but it also shows it could not mount E:\
2a. Still will not let me turn on USB storage. It just spins for a while and ends up giving up when the display is changed.
3. End goal...I could care less about root. I've always used modded ROM's and prefer them. I only did "OTA" when the RUU would not take. I became a bull in a china shop and started banging with a hammer...Was dumb but I think I had already corrupted the memory by hitting factory reset. (I'll be honest I never meant to hit that).
I've rooted and installed many a custom ROM's, but I prefer the simple methods of following one of the many awesome easy setups on here. I'm not completely useless...
I would like to get it back to the SD card working and be able to update the firmware and a moderately functioning ROM.
Thank you for any help. I really do appreciate it.
Click to expand...
Click to collapse
There's no point in attempting s-off at the moment because s-off requires that a working OS is installed. You can tell whether you're s-off by looking at your bootloader, it'll say s-on or s-off in the first line under the unlocked and tampered banners.
Your problem with your sd might be that the version of TWRP you have installed is too old, only the newer versions are able to fix a corrupt sd card. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now try wiping and mounting the sd card again. Once we have that sorted out we can move onto getting your firmware updated.
Sent from my Evita

OK! Looks like we are getting somewhere! It is now mounted.

Now you can copy files across to flash. You'll need to get s-off now so you can update your firmware. You'll need a bootable OS installed to do that, I'd suggest installing Kickdroid and then you can attempt getting s-off via the Rumrunner method.
Sent from my Evita

You are awesome! Thank you so very much for your help. Up and running.

How far have you gotten?
Sent from my Evita

S-Off and firmware updated and running with different ROM's. I'm golden man. Unless you can think of something I should consider?

As long as you're on the 2.15 firmware or higher, you are indeed golden. I was just curious.
Sent from my Evita

Hey there, I just noticed you made a donation to me with this thread as the reference. I just wanted to thank you, that's very generous of you. Donations aren't expected in return for my assistance but are greatly appreciated. Anyway, thanks again and have a great day.

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