Database Info

HTC Desire S bricked

I have a big problem, i had my htc desire s, s-off. i wanted to turn it back on. and i did something and did everything they said, but now i cant install a ruu but i keep getting this error 140 . please help, i am constantly in this white screen with fastboot usb etc etc.
What can i do, when i want to do the ruu rom, it goes from image 1.47.401.4 to image 1.28.401.1, is this the problem? Please help me. The pc doesnt find my htc
edit:
please help,
it is on now, hboot is 0.98.0000
radio is 3821.08.00.24_m
but i cant install this rom RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release_177977_signed
please help

dianaroelofs said:
I have a big problem, i had my htc desire s, s-off. i wanted to turn it back on. and i did something and did everything they said, but now i cant install a ruu but i keep getting this error 140 . please help, i am constantly in this white screen with fastboot usb etc etc.
What can i do, when i want to do the ruu rom, it goes from image 1.47.401.4 to image 1.28.401.1, is this the problem? Please help me. The pc doesnt find my htc
edit:
please help,
it is on now, hboot is 0.98.0000
radio is 3821.08.00.24_m
but i cant install this rom RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release_177977_signed
please help
Click to expand...
Click to collapse
Here's my answer:
Just so you know, you cannot just RUU to any RUU files that you can find.
Your phone comes with a thing called CID, this CID is the unique identification of your phone, on what region it belongs to. You can ONLY RUU your phone to the region it belongs to. if you have received the CID error, that means, that RUU is not for your phone.
Click to expand...
Click to collapse
You can a lot of information here:
[Q] Bricked my phone?

flashing ICS back to stock

Hey guys,
I have to flash my HTC Sensation back to stock, because it have a little hardware error (its sometimes suddenly shutting down ...)
My Sensation is from Germany..
On my phone is currently the Cyanogenmod 9. Yesterday I flashed the eng Hboot 1.17, because I read somewhere that i have to. Is this true?
After this I wanted to restore my backup of the original Rom, but this doesn't work. There were some errors and so on.
I think if I would send it back to HTC I have to uninstall the CWM and I have to install the old Hboot 1.18, but after a lot of reading today and yesterday I'm very confused., because I found no working way ...
greets
Tobi

http://forum.xda-developers.com/showthread.php?t=1516255
Person with pretty much same problem and some advice.

1. Flash old 1.17 FW (unless you're Super CID, in which case you may not need to)
-> ok i flashed a 1.17 FW. Everything is still working without any issue,but after I unlocked my phone i had the 1.17.111and so on FW. Now I have the 1.17.2008. Is this maybe a wrong fw?
2. Flash the RUU of your choice (normally the one your phone came with, if available)
->I don't know the RUU which my phone came with , the most was done by the program revolutionary. I have an unbranded European Sensation. Which is the right RUU?
RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
RUU_Pyramid_HTC_Europe_1.28.401.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_192608_signed.exe
RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198179_signed.exe
RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed.exe
RUU_Pyramid_HTC_Europe_1.45.401.3_Radio_10.56.9035.00U_10.14.9035.01_M_release_219990_signed.exe
RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.9035.00U_10.15.9035.02_2_release_228602_signed.exe
I read that I can brinck my phone very fast with it, so it is very important
I just have to download the exe and run it, after this it will flash my phone if it is in USB Debugging ?
I hope it is so easy to downgrade the phone from 4.0.3 to 2.3.4
3. Reset Super CID to one of your choice (again, usually the one your phone came with)
Is this important? Or is it enought if I just reinsert the battery, becuase I don't know if I'm Super CID
4. S-ON using the fastboot command in the guide in the Dev forum
with adb-tools:
-fastboot oem writesecureflag 3
-fastboot reboot-bootloader
right?

RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.90 35.00U_10.15.9035.02_2_release_228602_signed.exe
This was on my unbranded Sensation when I bought it.
For SuperCID look here (Step 4):
http://forum.xda-developers.com/showthread.php?t=1192300&page=1

warning
i updated to icecreamsandwich firmware h boot 1.23. i neede to go back to stock so i follwed directions on guide to s-on and ran ruu that came with my phone and it says error get the right bootloader ruu .however it didnt brick it but bootloader says security warning wifi and wifi hotspot both gives error. ive tried everything i know to fix it with no luck. ive heard its because i upgraded the firmware.

ok I'm now on Super cid. This was just very easy
Ok now I have to download the RUU (filefactory is very slow... )
What will happen, when I would flash the wrong EU ROM? Or is this just impossible?
Is it important to reset the cid to the cid which was set, when I got the phone? Or is it set back by flashing the RUU?
I have a lot of questions, but I don't wanna brick my lovely phone
Edit:
Ok everything is now fine. My phone is now on Andorid 2.3.4, S-On, old CID and unrootet...
I hope they will repair it, because sometimes the phone run 2 days without any issue and sometimes it just runs some hours without issue...

[Q] S-Off not possible because of "Error 131" - doesn't matter which RUU

Hi guys,
I am new here, so maybe I missed something.
Anyway, I followed the tutorial step-by-step to unlock my HTC Desire S which I got today (so it has a 2.x bootloader) like stated here:
http://forum.xda-developers.com/showthread.php?t=1443636
But I can't seem to install any RUU cause of "Error 131", as told in the tutorial, I must use the RUU for my specific region.
So, my Region is Germany and my phone is from o2.
So first I used
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
Click to expand...
Click to collapse
because Germany is in Europe. And the only GER RUU is from "TMO" which may mean "T-Mobile" I guess. But it didn't work.
Next I thought "**** that ****" and I tried to flash (after repeating all tutorial steps):
RUU_Saga_TMO_DE_1.30.111.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_178580_signed.exe
Click to expand...
Click to collapse
But it still shows up "Error 131"... so now I am depressed. Can anyone tell me what I am doing wrong?
Thank you very much

Samwan said:
Hi guys,
I am new here, so maybe I missed something.
Anyway, I followed the tutorial step-by-step to unlock my HTC Desire S which I got today (so it has a 2.x bootloader) like stated here:
http://forum.xda-developers.com/showthread.php?t=1443636
But I can't seem to install any RUU cause of "Error 131", as told in the tutorial, I must use the RUU for my specific region.
So, my Region is Germany and my phone is from o2.
So first I used
because Germany is in Europe. And the only GER RUU is from "TMO" which may mean "T-Mobile" I guess. But it didn't work.
Next I thought "**** that ****" and I tried to flash (after repeating all tutorial steps):
But it still shows up "Error 131"... so now I am depressed. Can anyone tell me what I am doing wrong?
Thank you very much
Click to expand...
Click to collapse
Hi there,
You need to flash the RUU that is supported by your phone's version.
Turn the phone into fastboot mode (voldown + power), click fastboot, wait till it shows fastboot usb.
Open console in PC and find the android tools, type:
<androidtool dir>\ fastboot getvar all
It should come up as: INFOversion etc.
What you need to look for is INFOversion-main and INFOcidnum
Go to http://forum.xda-developers.com/showthread.php?t=1002506
and download the RUU that matches!
If you've S-OFF'd the phone with Revolutionary, then RUU will have some problems with overwriting the bootloader, follow this guide to re S-ON.
http://forum.xda-developers.com/showthread.php?t=1187231

anchemis said:
If you've S-OFF'd the phone with Revolutionary, then RUU will have some problems with overwriting the bootloader, follow this guide to re S-ON.
http://forum.xda-developers.com/showthread.php?t=1187231
Click to expand...
Click to collapse
Very helpful reply buddy.
But i don't think the last line applies to him. He said he just got the phone, and it had the v2.xxx hboot to begin with, so he went looking to downgrade. If he had acheived S-off, he wouldn't be asking how to S-off in the first place.
@OP : You should try using a Goldcard when faced with a difficult choice of Region-specific RUUs. Try making one (Use Search function) and then re-running the European RUU. (You may also have to check your Misc_version to ensure compatibility, or you may hit a roadblock again.

Hi,
I just wanted to confirm for further searches / use that what has been stated inside the first answer is fully working.
I got my Desire S downgraded, S-OFFed and was able to flash MIUI, so it's finding it's way to my girlfriend as birthday present soon thank you for helping.

[Q] Which RUU for 3.32.401.105?

Hi, I think I have bricked my phone, it's a Sensation XE btw. I wanted to go back to stock S-ON and get the ICS OTA update so I ran "RUU_Pyramid_LE_HTC_Europe_1.73.401.4_Radio_10.58.9035.00U_10.15.9035.02_2_release_220036_signed". I went well and I was back on GB and entered the command for S-ON in cmd. Then I downloaded the OTA and installed it. Now the phone won't turn on, it just goes in boot loops just displaying the HTC splash screen then rebooting again. I can't enter recovery from bootloader and I can't do a factory reset, it just goes into a bootloop. So, what can I do to get it up and running again?
Have tried this guide, but I can't get passed the point where you are supposed to flash a rom from recovery since I can't get into it. I have unlocked the bootloader and flashed 4ext touch recovery but still can't boot to it.
Info:
HTC Sensation XE
Pyramid PVT Ship S-ON RL
HBOOT-1.27.0000
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot.
Any help will be greatly appreciated.

Y did u go back to s-on? U can take an ota and keep ur s-off. Have u tried to just get the 3.32 firmware update and put it on ur sdcard, go into bootloader and let it update the firmware, since u did the ics update?

I need to send it in to reperation. I will try to do that, but I will need to adb push it right? Since I can't mount the SD-card. I can see if I find a docking station for the SD-card tho.
Thanks btw
Edit: placed the firmware on sd card, will boot up now. crossing my fingers!

Hopefully that should work!

Nope, it says "Loading PG58IMG.zip!", then it says "Parsing.... PG58IMG.zip". Afterwards it just stays in bootloader. Do I need to have the bootloader locked for this to work?

Probably, what is ur hboot version

1.27.0000
10char

That's the correct one, have u tried the regular ruu for that ics?

Didn't find any, could you please link me?

There isn't an RUU for the new 3.32.401.105 ICS build (yet)
Try a factory reset of the unit

yeah it's all been ota so far. if u got anything eddy i don't man

@EddyOS: as mentioned in OP, I can't do a factory reset. I can't enter recovery and when i do it from bootloader it just bootloops.

And how long do you think it takes to make a RUU for my bootloader? How long does it usually take?

Man I have know idea, but if all u did is take an ota and ur phone crapped out then I would be getting my carrier or something to fix it.

yeah, that is a possibility, but my bootloader is unlocked. That may be a problem.

You can't 'make' an RUU. If you're S-OFF you can flash the old 1.73.401.4 from fastboot but. If you're S-ON you're kinda screwed

Relock it and tell them u took the ota and this is what happened. Most carriers don't look at ur bootloader and if by chance they do, tell them u were trying to fix the problem cause u need ur phone. Do u have insurance?

So the only hope for me is to either send it in to HTC or wait for a 1.27 RUU?

Or ur cell company. That's y I have insurance on my phone. Look for kingsrom in development section and ask him what he did cause he flashed something wrong and since the phone has a 1 yr warranty on it, he got his replaced. Sorry I couldn't be of more help man.

Ok, no problem, just glad you could help as much as you could.
One last question, is there any way to lock the bootloader again without it saying "RELOCKED". Just talked to a HTC representative who said that the workshop could get suspicious regarding the error I have and the bootloader beeing unlocked and relocked.

[REF] Dead/Bricked phone after JB OTA, QHSUSB_DLOAD

Hi All,
There are more and more reports coming in from people who ended up with a dead/bricked phone after the JellyBean Update 4.1.1 , 3.16.401.8 OTA. As you connect it to your PC you will soon find out it's in QHSUSB_DLOAD mode.
The purpose of this threat is to see how many people are affected, what people have done to attempt to recover their phone, and to find a possible solution (this chance seems rather small though).
There are alot of post about this in the JellyBean Speculation/News/Discussion threat, starting from page 157.
There are 2 threats about it in Q&A:
One S in QHSUSB_DLOAD mode
My HTC to really died
Reported attempts to recover:
QHSUSB_DLOAD Fix by team Unlimited
Unbricking HTC devices with the QHSUSB_DLOAD issue tutorial by kgs1992
Step 3 (and some others) from [TUT] Downgrade/Unbrick Ville S4
Another HTC one V recover guide where i can't find the link for.
Please report here if you have this issue. Please mention your CID, in what country you downloaded the OTA, the software version you upgrade from and the hboot version.
Also any new ideas to recover our phones our self are welcome!
My phone:
2.31 Unbranded Europe
1.14 Hboot
Downloaded in The Netherlands
1111111 Supercid

I have exactly the same problem, waiting...

As far as I know the issue is only caused by people who previously had SuperCID.
Sent from my HTC One S using Tapatalk 2

usaff22 said:
As far as I know the issue is only caused by people who previously had SuperCID.
Click to expand...
Click to collapse
I thought I saw a report of a fully stock device and one htc__001 cid as well. I can't find them at the moment, but this is also why I started this threat. But there seem to be more of these reports of supercid indeed, though there are also allot with supercid who successfully updated.

My phone is bricked too
Orginal CID was HTC_0001 (maybe), branded by 1&1 Germany
but changed to 11111111 to flash a unbranded RUU (what had worked)
I had Stock Recovery and relocked bootloader

My phone is bricked too
SuperCID 11111111 Hboot 1.14 Recovery Stock y Relocked bootloader.

My phone is bricked too
Orginal CID was HTC_203 (maybe), not branded by telecom company - France
but changed to 11111111
I had Stock Recovery and relocked bootloader and flash the 2.31 RUU

hellgod said:
My phone is bricked too
Orginal CID was HTC_203 (maybe), not branded by telecom company - France
but changed to 11111111
I had Stock Recovery and relocked bootloader and flash the 2.31 RUU
Click to expand...
Click to collapse
Dam it didnt mean to hit thank so enjoy that lol.
@Vauix, did you run a RUU before updating? if so what one?

let's discuss who and what options tried to output the list of sections? How you think why it happened?

All of them seem to be caused by SuperCID. But the updater script allows flashing for SuperCID, so I wonder why they get bricked.
Sent from my HTC One S using Tapatalk 2

I agree with you. But what it is necessary to undertake that Ubuntu saw sections?

Same here.
SuperCID and ota
Now nobody can call me

Same here.
SuperCID too

Darknites said:
Dam it didnt mean to hit thank so enjoy that lol.
@Vauix, did you run a RUU before updating? if so what one?
Click to expand...
Click to collapse
Yes I ran a RUU prior to flashing this update, i didn't chance anything to the rom yet but to search for the OTA. it was the RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
I thought about my supercid before I ran the RUU but i thought the worst thing that could happen was i could get a error that it couldn't flash it.
Its rather weird that some guys with supercid managed to flash it successfully. And i still think I saw some people with other cid's with bricked devices.

SuperCID too, previously Vodafone germany, unbranded an relocked ...

I ran the OTA update twice on my supercid'd device successfully.
In opposite to what I could read here, my bootloader was unlocked before and still after the update.
The first time I ran the update I forgot to reflash stock recovery. The phone started updating and rebooted, but no changes had happened. After restoring stock recovery and downloading the update again, I successfully updated.
As I couldn't get root I restored Venom and downgraded my new hboot from 2.15 to 1.06.
Today I started a second try successfully without a glitch.
Basically I keep an untouched nandroid backup of every new rom installation on my local harddisk. This means in case of custom roms I do a nandroid before the first boot.
As this is not possible on stock recovery I change back to custom recovery after the first boot, doing my backup then. I'm just checking the needed boxes otherwise I only proceed during the setup - the complete customization is done afterwards.
In this case I restored a backup called 2012-08-23--08-18-16_htc_stock_2.31
Stock here means: No apps, no customizations, no nothing, simply: stock and supercid.
After that was done I restored apps with Titanium.
That's how it worked (pretty simple) Maybe this will help you find some reasons for what has happened to your devices.

Same problem here...
SuperCID

All people here seem to have SuperCID, I have not.
I got my ville for about 7 months now and never had SuperCID.
I did it like everytime:
-Wiped everything ( Data / Cache / System )
-Flashed Stock Recovery
-Relocked
-Flashed 2.31 Europe RUU in Bootloader ( yes, that works but I guess noone knows )
-Downloaded 4.1.1 Update and let the Device do its magic
Now my phone is bricked.
Strange enough, a good friend of mine whos barely able to use its phone, got the same issue.
Im 100% sure he doesnt have any modifications done to his device.
Already tried the Ubricking-Tutorial but the Partitions just dont show up :-/

I did the super CID, too. No my phone is dead. Won't even charge.
I tried to do Enumerating the partitions but could only find up to 3. No 4 or 12.
Please help :crying:

SuperCID, German ONE S unbranded. Dead.
Unbrick/Downgrade instruction did not work here.