S-OFF voids warranty! At no point do I claim that this guide restores your warranty in any way. This guide includes steps to restore stock software, which will conceal that your phone's software was modified. It is up to you to chose how you use this guide. Remember that hiding the fact that you have modified the phone for purposes of warranty claim is unethical & I don't support this in any way. Let's discuss about RUU first: 1.1 What is an RUU?
RUU stands for ROM Update Utility Simply put, a RUU is executable (.exe) Windows program that contains the various files required for changing your phone's software via HTC. 1.2 The RUU contents. Files for it's own configuration & execution. adb and fastboot files for communicating with your device.
A signed HTC ROM to flash all partitions. Other miscellaneous files 1.3 Method of execution: The RUU can be started by double-clicking the executable file when the phone is connected to the PC via fastboot USB (in the bootloader).
The RUU works by passing commands to your device which will enable it to flash the ROM on your phone. Once the installation starts, the RUU executable does nothing except show you the current status of installation. When the installation is successful or when there is an error, it displays the appropriate message. 1.4 Security features: The RUU will ALWAYS check your CID & MID before installation.
If your phone's CID or MID does not match the RUU's list of supported CIDs & MIDs, it will not install. Before flashing, the software number of the RUU and the phone's current software number are compared. If your device is S-ON, then you cannot flash an RUU with version less than your phone's current version.
The same applies for hboot version 1.5 General PRECAUTIONS to take during RUU execution:. Always use USB 2.0 ports on the computer. Never use USB Hubs or extensions. Use a secure cable, preferably the one you got from HTC. The cable should not be loose or flimsy. Never pull out the USB cable unless you are absolutely sure that the RUU is not making any changes to the phone.
If you are using a laptop, charge the battery first & keep the battery as well as the charger connected until RUU has finished execution. Read & follow the guide to the letter. Naming convention & finding the right RUU RUUs for the HTC Sensation & Sensation XE are named as. Code: RUUPYRAMID or PYRAMIDLE(Provider/Location name)(Software base).(Provider/Location).xRADIO(Radio version)As an added note, RUU for the Sensation is PYRAMID, RUU for the Sensation 4G is PYRAMIDTMOUS, and the RUU for the Sensation XE is PYRAMIDLE. To find the right RUU for yourself, you need to know two things:. Your CID & corresponding region code. Your Current software version 2.1 To find your CID: You will need sdk & and drivers, please take a look.
That’s right—business acumen is not enough to succeed in Airlines: you need to think and act quickly before a day is over (or use slowdown programs to make it run very slowly). Airlines is an underrated airline management sim from Interactive Vision (who is actually hard at work on Airlines 2, slated for an early 2002 release). Although the game offers a lot of real-world options and a wide variety of airplanes, the designer somehow chose to make the game play in real time. In contrast to Air Bucks, Airlines is a complex sim with a steep learning curve. Airlines 2 game. The clock advances 4 hours at a time, and there never seems to be enough time to do everything in a day.
If you already have it, continue. Reboot to bootloader powering down the phone & then Holding Vol down + Power button. Connect your phone to the PC while in the bootloader. The phone should say fastboot USB, if not, select fastboot on the phone & check if it says fastboot USB, if not, change the USB port you are using. Navigate to the platform tools folder located inside android-sdk folder. Hold down shift and right-click anywhere in the empty space inside the window. Select the option: Open command window here.
Next, type. Code: fastboot getvar cid. You will now be shown your current CID. 2.2 To get provider/location code Note down your CID and check corresponding provider/location or search/post in. Code: fastboot getvar version-main. You will now be shown your current software number. The right software version for you is any version higher than or equal to this.
2.4 To find your RUU Please find your suitable RUU using key words ' RUU' ' Pyramid' (Sensation) or ' Pyramid LE' (Sensation XE) or ' Pyramid TMOUS' (Sensation 4G) ' Firmware Base. Provider/Location code' PYRAMID is for Normal Sensation PYRAMID LE is for Sensation XE PYRAMID TMOUS is for Sensation 4G They are not cross compatible. For example, If you want the RUU for Sensation XE Europe 3.32 based, find ' RUU Pyramid LE 3.32. 401 ' Execlutable RUUs can be found here.: For the extracted rom.zip file from RUU, look here.:.Please note, these files aren't hosted by me, so credit goes to whoever is uploading and hosting them. That being said, it is your responsibility to check the source & ascertain if they are reliable. Remember, an incomplete zip could possibly brick your device, especially S-OFF devices. RUU to restore stock The main reason that people flash RUUs is because they want to get back to stock.
Here is how it's done. Is your bootloader unlocked via HTC Dev? (If it is, it should say.
UNLOCKED. at the top) Yes, it says UNLOCKED on the bootloader: Follow points 3.1 & 3.2 to restore your phone back to stock. Optionally use 3.3 to turn back to S-ON. No, it doesn't say UNLOCKED on the bootloader: Follow point 3.2 only to restore your phone back to stock. Optionally use 3.3 to turn back to S-ON. 3.1 Relocking the bootloader You will need sdk & and drivers, please take a look.
If you already have it, continue. Reboot to bootloader by Holding Vol down + Power button. Connect your phone to the PC while in the bootloader. The phone should say fastboot USB, if not, select fastboot on the phone & check if it says fastboot USB, if not, change the USB port you are using. Navigate to the platform tools folder located inside android-sdk folder. Hold down shift and right-click anywhere in the empty space inside the window. Select the option: Open command window here.
Code: fastboot reboot-bootloader. Bootloader should now say.Relocked. & may or may not display a Security Warning 3.2 Using RUU to restore partitions. Find your right RUU using 2 in this guide. Flash your RUU as you normally would by double clicking the executable & following the instructions, you phone must be connected to PC via fastboot USB (in the bootloader). If you get a Hboot Pre-update message, re-run the RUU once again with your phone connected in fastboot USB.
If the previous step fails, follow points listed under 4. Flashing RUU manually.
Reboot your device to bootloader, your bootloader should now say.Locked. or.Relocked. 3.3 Turning S On after RUU flash You will need sdk & and drivers, please take a look. If you already have it, continue. This is optional, but if you want to do it, it must be done only after flashing the RUU! If your device has a hboot that isn't LOCKED, RELOCKED or UNLOCKED, do not do this!!. Reboot to bootloader powering down the phone & then Holding Vol down + Power button.
Connect your phone to the PC while in the bootloader. The phone should say fastboot USB, if not, select fastboot on the phone & check if it says fastboot USB, if not, change the USB port you are using. Navigate to the platform tools folder located inside android-sdk folder. Hold down shift and right-click anywhere in the empty space inside the window. Code: fastboot reboot-bootloader. Bootloader should now say S ON. If the bootloader says.Security Warning.
Remove the battery and then re-insert it. Reboot to bootloader by holding down the volume key and pressing the power button.
Connect your phone to the computer via USB. Re-run the RUU executable again. The bootloader should now say S On. Flashing RUU manually 4.1 Getting PG58IMG.zip from RUU Run the RUU executable as you normally would, but don't proceed to the second step i.e.
When a second window appears, do nothing. Do not proceed, just ignore it for now, but don't close the window. Right-click the Windows Start button and select 'Open Window Explorer' option. If you use Windows XP Copy-paste this in the navigation bar.
Code:%temp%. Right click anywhere inside explorer window (not on any folder) and select Sort by then select Date. Locate the latest one created (first in the list & it will most likely have random numbers in the name) & open it.
You will find a second folder with a set of random numbers. Open it, inside you will find a number of files and the rom.zip. Copy the rom.zip file to another location.
![Ruu Ruu](/uploads/1/2/3/8/123812048/222560338.jpg)
Now, close the RUU executable folder & rename the rom.zip file as PG58IMG.zip 4.2 Adding your CID to the PGIMG.zip This is only required if the RUU you have is not for your CID and you don't have SuperCID. Check your cid by referring to 2.1 in this guide. Double click the PG58IMG.zip file to open it. Double click android-info.txt to open in notepad. Add your CID to the end of the file uising the ones already in there as an example. Make sure there are no spaces in or after your CID. Press Ctrl +S and then close the window.
You will now see a pop up window. Click yes to modify the archive. 4.3 How to Super CID This is only required if the RUU you want to flash is not for your CID and you did not follow 4.2.
This requires that your bootloader should not say S-On. Follow all steps in 2.1 and then continue. Now type the following code. Code: fastboot getvar cid. Your CID should now be 11111111.
If this method failed, try 4.2 4.4 How to flash PG58IMG 4.4.1 Without a PC, via bootloader. Put the PG58IMG.zip onto the root of your SD Card. Reboot to bootloader by Holding Vol down + Power button. You will then be asked if you want to install the file, select yes by pressing Vol up. Don't touch anything till the install completes.
After the install is complete, when prompted to reboot, open the back casing of the phone and take out the SD Card. Then press the power button once to reboot. If you experience a boot loop, reboot to bootloader and re-flash the PG58IMG.zip. If booted into bootloader, select fastboot reboot.
If booted into fastboot, select reboot. Connect the SD Card to a computer and delete the PG58IMG.zip file If this method fails, try 4.4.2 4.4.2 With a PC, via fastboot USB You will need sdk & and drivers, please take a look. If you already have it, continue. Reboot to bootloader by Holding Vol down + Power button.
![Manager Manager](/uploads/1/2/3/8/123812048/958757519.jpg)
Connect your phone to the PC while in the bootloader. The phone should say fastboot USB, if not, select fastboot on the phone & check if it says fastboot USB, if not, change the USB port you are using. Navigate to the platform tools folder located inside android-sdk folder. Copy the PG58IMG.zip file from step 4.1 to this folder.
Hold down shift and right-click anywhere in the empty space inside the window. Enter the following command. Code: fastboot reboot. If you experience a boot loop, repeat 4.4.2 again. Common errors & Troubleshooting: If you get any error while running the executable, it is recommended that you use the method to extract the rom.zip & flash it. This is because the error code returned by the executable is not very clear. Stuck at.
Drivers not present or not installed correctly; Install the correct drivers. Phone is not in fastboot USB mode. Remove USB Cable; remove & reinsert phone battery; hold volume down + power; select FASTBOOT; connect USB. Error: cannot load 'xyz' You typed the wrong filename or the file isn't present in the folder. Check that the file is present & that the filename is correct, then repeat the command.
Error 150: ROM upgrade utility error This is most likely an error when you use Windows Vista. Error 170: USB Connection error The RUU cannot connect to your device. Drivers not present or not installed correctly; Install the correct drivers. Phone is not in fastboot USB mode. Remove USB Cable; remove & reinsert phone battery; hold volume down + power; select FASTBOOT; connect USB. Other unknown error. Extract rom.zip & flash manually via SD Card.
ERROR 155 to 159: IMAGE ERROR One of these error messages will appear when your device is S-ON & use the incorrect RUU having lower software number/hboot version than what is currently on your phone. FAILED (remote: not allowed). You did not reboot to RUU mode before running the flash command.
You are trying to use a command that you cannot use on a Locked and/or S-ON device. (bootloader) ERR Command error!!! Or INFOERR Command error!!!. You are trying to issue an invalid command. You are trying to use a command that you cannot use on a Locked and/or S-ON device.
FAILED (remote: signature verify fail)The zip that you extracted is broken or the RUU you downloaded is is corrupted. Get the zip again or use a different RUU. FAILED (remote: 99 unknown fail) Your bootloader is still unlocked.
You didn't relock your bootloader. Relock your bootloader using this command. Code: fastboot reboot-bootloader & let the phone charge for a while. FAILED (remote: 90 hboot pre-update!
Please flush image again immediately) Normal after Hboot version changes. You need to run only the flash command again (not the whole set of commands, just the fastboot flash command.) FAILED (remote: 42 custom id check fail) The RUU doesn't contain your CID. Either add your CID to the zip (needs S-OFF) or try changing your CID (usually works only on an S-OFF device) FAILED (remote: 92 supercid! Please flush image again immediately) Your device is S-ON & has Super CID. You need to run only the flash command again (not the whole set of commands, just the fastboot flash command.) FAILED (remote: 43 main version check fail) Your device is S-ON & you are trying to use an RUU that has software number less than your current software number. FAILED (remote: 44 hboot version check fail) Your device is S-ON & you are trying to use an RUU that has hboot version less than your current hboot version. FAILED (status read failed (Too many links)) Disregard & continue.
It is not really an error as such. FAILED (data transfer failed (Too many links)) Reboot the phone to fastboot USB. Remove USB Cable; remove & reinsert phone battery; hold volume down + power; select FASTBOOT; connect USB. Then, try the commands again. Any other error that says '(Too many links)' Reboot the phone to fastboot USB. Remove USB Cable; remove & reinsert phone battery; hold volume down + power; select FASTBOOT; connect USB.
Then, try the commands again. If you still get the error, please post the complete error code here & when the error occurred so that it can be solved & added to this list.
Any other error that says 'please flush image again immediately' You need to run only the flash command again (not the whole set of commands, just the fastboot flash command.) Please post the complete error code here & when the error occurred so that it can be added to this list Any error that isn't present in this list Please post the complete error code here & when the error occurred so that it can be solved & added to this list. I request you to link all RUU related questions & restoring S On questions to this guide as I it is the most complete guide in my opinion. This guide has been compiled from personal experience & various other sources on the internet as well as within XDA.
I do not take sole credit for the information contained in this guide. Any part of this guide may be used wherever needed without the need for my permission. If you modify the guide, please mention that it is a modified version & DO NOT present it as my work or link the guide to me in any way. Last but not the least, I claim no responsibility for any damage caused to your device as a result of following this guide. (This will only happen if you missed out on something.). Quote: Originally Posted by T-Macgnolia Great work on the guide it really covers the topic of a RUU very well.
Sorry to be the first one to post here, and these are just suggestions also. But I seen some things that could be revised. In the following part you can do away with all of the below. You can replace it with just navigating to the 'tools folder' in the of the SDK folder.
While in the tools folder simple hold down shift and right click anywhere in the window, then select 'Open command window here'. This will open a command window that is already in the tools directory so you have full access to ADB and fastboot commands. No need to copy and past files. Also you can modify the below to just double click the file. That is just some suggestions to make it a little simpler. Quote: Originally Posted by T-Macgnolia You did post this in the wrong place, but you only have 5 post so you can not post in the development thread. And sorry but i can tell you, no the next version of the Super Utility tool will not make S-off without the wire trick. 32bit-6.14.10.4885.zip.
If you do not have Hboot 1.18.0000 or below you can not use Revolutionary. The only S-off for Hboots 1.21.0000 and up is Juopunutbear S-off. Edit: I just read the thread in the development forum and I may have to retract my statement, lol.
Apache Web Server In case of problems write to Victor Ivanov - e-mail address protected from mail-bots, you need Javascript to see it or call (+359) 888-544-726 More RUU files for the hTC Sensation/XE 'Pyramid' at More RUU files for the hTC Sensation/XE 'Pyramid' at The files above are original hTC RUU files for the hTC Sensation smartphone. However, the names were too long, so to shorten them, the sign ' was changed to '-' and etc. Here is a full list, with the complete and accurate names, of the files above. RUUPYRAMIDICSHTCEurope3.32.401.5RRadio.00U.07Mrelease246089signed.exe RUUPYRAMIDICSHTCAsiaWWE3.32.707.10RRadio11.69A.3504.00U.07M2release251503signed.exe RUUPYRAMIDICSHTCEurope3.33.401.6Radio11.76A.3504.00U11.24A.3504.31Mrelease266171signed.exe RUUPYRAMIDICSHTCEurope3.33.401.53Radio11.76A.3504.00U11.24A.3504.31Mrelease280871signed.exe.
Apache Web Server In case of problems write to Victor Ivanov - e-mail address protected from mail-bots, you need Javascript to see it or call (+359) 888-544-726 More RUU files for the hTC Sensation/XE 'Pyramid' at More RUU files for the hTC Sensation/XE 'Pyramid' at The files above are original hTC RUU files for the hTC Sensation smartphone. However, the names were too long, so to shorten them, the sign ' was changed to '-' and etc. Here is a full list, with the complete and accurate names, of the files above. RUUPYRAMIDICSHTCEurope3.32.401.5RRadio.00U.07Mrelease246089signed.exe RUUPYRAMIDICSHTCAsiaWWE3.32.707.10RRadio11.69A.3504.00U.07M2release251503signed.exe RUUPYRAMIDICSHTCEurope3.33.401.6Radio11.76A.3504.00U11.24A.3504.31Mrelease266171signed.exe RUUPYRAMIDICSHTCEurope3.33.401.53Radio11.76A.3504.00U11.24A.3504.31Mrelease280871signed.exe.
Only a few days have passed since custom ROM of the official Ice Cream Sandwich test build RUU for the HTC Sensation has leaked and the folks responsible are back with the original RUU. Capychimp and Robocik, two XDA forums users have just leaked the original Ice Cream Sandwich RUU for the HTC Sensation and the Sensation XE smartphones. Android tech-savvy users who own any of the two smartphones can now download and flash the RUUs via XDA Developers. The initial release of the customer RUU has the following features: - Base - 3.06.401.101 Sensation XE, Android 4.0.1; - Kernel - Stock, 3.0.13-g8085863 htc-kernel; - Optimized and zipaligned apks, zipaligned with sdk16; - Speed optimization scripts; - init.d support; - HTCSync is working now; - Big MMS; - Face unlock and most of other Ice Cream Sandwich goodies; - Movie Studio; - Added Keyboard pop up animation; - EVO Latin IME (standard android keyboard).
HTC Sync Manager
Given the fact that this is a pre-release version, users may encounter bugs and issues that will probably be corrected in the future test builds. Until then, here is a short list of the known issues that have already been discovered by those who leaked this build: - Can’t set wallpaper from gallery; - HTC Sync not working - Small MMS issues. However, several of these problems have already been fixed by the persons responsible for this leak, who also added a few tweaks and improvements. This is the main reason that this release has been tagged as “custom” RUU. Optimized and zipaligned apks, zipaligned with sdk16; - Added some optimization scripts; - Added init.d support; - Added a reboot apk to make a normal/bootloader/recovery reboot (until a real APM comes); - Cleaned out unnecessary apk files (over the air, loggers and so); - Added social network lockscreen; - Fixed small MMS issue; - HTCSync is working now. HTC already confirmed it will deploy the Android 4.0 Ice Cream Sandwich to the HTC Sensation sometime next year, but until then those who know what they’re doing can take advantage of these leaked ROMs for a glimpse of what’s to come.