mis estimados comunos el dia de ayer publique un tema
http://www.svcommunity.org/forum/htc-android-motorola/htc-no-arranca-pantalla-blanca-logo-de-htc-ayuda-por-favor/ con un HTC sensation que simplemente no pasaba de la pantalla de inicio, luego de buscar en internet, y tambien luego de unos cuantos experimentos de dudosa procedencia lo revivi, esta guia esta muy completa, se encuentra en ingles pero se soluciona eso, explica muchas cosas
1. 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
Files for recovery options
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's bootloader is locked, then you cannot flash an RUU with version less than your phone's current 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.
2. Naming convention & finding the right RUU
RUUs for the HTC Sensation & Sensation XE are named as
Code:
RUU_PYRAMID or PYRAMID_LE_(Provider/Location name)_(Software base).(Provider/Location).x_RADIO_(Radio version)
As an added note, RUU for the Sensation is PYRAMID, and the RUU for the Sensation XE is PYRAMID_LE.
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 here. 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 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 here or search/post in this thread.
Here is a list of variants:
x.xx.61.x - Orange UK (United Kingdom)
x.xx.69.x - Orange PL (Poland)
x.xx.73.x - Orange FR (France)
x.xx.75.x - Orange ES (Spain)
x.xx.110.x - T-Mobile UK (United Kingdom)
x.xx.111.x - T-Mobile DE (Germany)
x.xx.113.x - T-Mobile CZ (Czech Republic)
x.xx.161.x - Vodafone UK (United Kingdom)
x.xx.163.x - Vodafone FR (France)
x.xx.165.x - Vodafone IT (Italy)
x.xx.168.x - Vodafone GR (Greece)
x.xx.206.x - O2 UK (United Kingdom)
x.xx.401.x - World Wide English (Europe Unbranded)
x.xx.415.x - Arabic (UAE/Middle East)
x.xx.468.x - Turkey
x.xx.497.x - Morocco
x.xx.498.x - WWE Brightpoint US (United States)
x.xx.531.x - T-Mobile US (United Kingdom)
x.xx.666.x - Bell Canada
x.xx.707.x - Asia WWE (World Wide English)
x.xx.709.x - Asia TW (Taiwan)
x.xx.720.x - Asia India
x.xx.771.x - Hutchison 3G UK (United Kingdom)
x.xx.841.x - Telsra WWE (World Wide English)
x.xx.862.x - Voda-Hutch AU (Australia)
x.xx.901.x - TIM IT (Italy)
x.xx.911.x - SK Telecom (South Korea)
x.xx.1400.x - HTC China
x.xx.1403.x - HTC China CMCC (China Mobile Communications Corporation)
2.3 To find your software version:
If you have S Off, this doesn't matter, but you should always try to flash the oldest RUU, so that it is easier to S Off later, unless you don't intend to perform S Off again.
Go to "Settings" > "About phone" on your device.
The right software version for you is any version higher than 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:
http://forum.xda-developers.com/show....php?t=1335368
http://www.shipped-roms.com/index.ph...&model=Pyramid
http://www.filefactory.com/f/c87a2330449af512/
For the extracted rom.zip file from RUU, look here:
http://goo.im/stock/pyramid/ruu
3. RUU to restore stock
The main reason that people flash RUUs is because they want to get back to stock, and a major reason for this is warranty claims or to clean partitions.
You need to get the bootloader back to it's original state.
Here is how it's done.
For HTC Dev unlocked users with S On, you need to follow 3.1 & 3.2
For other users, you need to follow 3.2 & 3.3 (Optional/Only if required)
If your bootloader says *Locked* or *Relocked* & S-Off, please flash firmware corresponding to your current version from here.
3.1 Relocking the bootloader
You will need sdk & and drivers, please take a look here. 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 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 oem lock
Finally, type
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 here. 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 tools folder located inside android-sdk folder
Hold down shift and right-click anywhere in the empty space inside the window.
Next type:
Code:
fastboot oem writesecureflag 3
Finally, type
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.
4. 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:
C:\Documents and Settings\%USERNAME%\Local Settings\Temp\
If you use Windows Vista/7
Press & hold Windows key on the keyboard and then press R (Win key + R). Once the box pops up, copy paste this:
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.
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 oem writecid 11111111
Now type :
Code:
fastboot reboot-bootloader
Wait for the phone to reboot into bootloader.
Type this:
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 here. 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 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 erase cache
You may not see any output, then enter the command
Code:
fastboot oem rebootRUU
You phone will now go into the RUU mode.
Wait for around 30 seconds, then enter the command
Code:
fastboot flash zip PG58IMG.zip
The installation will begin and you will be able to see the progress at every step.
Once done, enter the command
Code:
fastboot reboot
If you experience a boot loop, repeat 4.4.2 again.
cualquier duda hay me avisan o este thread vamos viendo que sale
----
Mod Edit: Fuente:
http://forum.xda-developers.com/showthread.php?t=1672425
