Database Info

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

Help, i think i destroyed my phone.........

Hello. I have a htc one s ville c2(s3 proc) and a long time ago i installed a custom rom (trickdroid 5.0.0 ) and it started to work hard, wi-fi not working, and things like this.So i decided to go back to stock. My phone's cid is htc_032 wich means that is for Eastern europe. I downloaded a ruu 2.15......... and i installed it. The mobile network was working very hard (100kb/s) so i think the baseband is not good.Then i found an ota for htc_032 and i tried to install it. i relocked the hboot, then flashed the firmware.zip with fastboot. All fine, but after the install i candt even open my phone or enter in hboot........ please help...

[Q] Problems going back to stock after Venom Rom installed

Hi Everyone,
knowing it's all out there, just need to read (a lot), please help me finding the correct way to solve my problem. I can not change to other ROM, mostly due to lack of knowledge. Please before you judge and claim I should read and learn, i have kids who don't allow me read things properly, and there are tons of information out there, seems simplier to ask for directions this time, based on the situation of the phone.
This is the first custom rom I tried on my new S4 HTC One S (not brand new, just new to me). It was stock rom, locked. Followed instructions on different threads, I unlocked the phone, flashed TWRP recovery, installed SuperSU, copied Venom Rom zip to SD card and installed from recovery, with the aroma. Success. Before installation I did a backup in TWRP.
I very much like the rom (though have 2 issues: 1. phone reboots randomly without any notification. 2 phone loses carrier randomly, so I see no GSM connection as if SIM was removed. This happens when phone is untouched so no way SIM is loosy or something). When I try to chose carrier manually from settings, it sais no SIM card is installed...
But I would like to try other roms as well, and also wish to compare some stock roms. So I downloaded a generic HTC Europe stock RUU, hoping I can easily flash it. Relocked the phone, ran the RUU.exe with Fastboot USB mode in bootloader, but it all came up with error messages and left me at the HTC logo. All I can do is to re-install Venom 3.0.0 from recovery, that works, otherwise I end up in boot loop.
Also I can not go back to the original state using the backup from TWRP. It installs boots but it basicaly freezes before the phone setup comes. I can see the background image, the clock and the GSM antenna sign, but thats all, nothing else happens, no matter how hard I try to reboot.
Phone current boot screen shows: Tampered + Unlocked
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
Radio-1.15.50.05.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10
When I re-locked the phone it said Tampered + Relocked + Security Warning
As recovery I have TWRP 2.6.0.0 flashed. I did nothing else.
Could someone help me with instructions or at least directions how I could go back to a nice stock RUU? With the one I downloaded i had different error codes 213 (wrong ID) and 255 Unkown error.
I believe as the phone is not S-OFF and/or Super CID, it is relevant which RUU I download. The phone used to boot with a voda logo, so I believe it was one of the UK or AT voda stock roms, but neither works.
Your opinion/feedback is highly appreciated.
Cheers,
skee

skee81 said:
Hi Everyone,
knowing it's all out there, just need to read (a lot), please help me finding the correct way to solve my problem. I can not change to other ROM, mostly due to lack of knowledge. Please before you judge and claim I should read and learn, i have kids who don't allow me read things properly, and there are tons of information out there, seems simplier to ask for directions this time, based on the situation of the phone.
This is the first custom rom I tried on my new S4 HTC One S (not brand new, just new to me). It was stock rom, locked. Followed instructions on different threads, I unlocked the phone, flashed TWRP recovery, installed SuperSU, copied Venom Rom zip to SD card and installed from recovery, with the aroma. Success. Before installation I did a backup in TWRP.
I very much like the rom (though have 2 issues: 1. phone reboots randomly without any notification. 2 phone loses carrier randomly, so I see no GSM connection as if SIM was removed. This happens when phone is untouched so no way SIM is loosy or something). When I try to chose carrier manually from settings, it sais no SIM card is installed...
But I would like to try other roms as well, and also wish to compare some stock roms. So I downloaded a generic HTC Europe stock RUU, hoping I can easily flash it. Relocked the phone, ran the RUU.exe with Fastboot USB mode in bootloader, but it all came up with error messages and left me at the HTC logo. All I can do is to re-install Venom 3.0.0 from recovery, that works, otherwise I end up in boot loop.
Also I can not go back to the original state using the backup from TWRP. It installs boots but it basicaly freezes before the phone setup comes. I can see the background image, the clock and the GSM antenna sign, but thats all, nothing else happens, no matter how hard I try to reboot.
Phone current boot screen shows: Tampered + Unlocked
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
Radio-1.15.50.05.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10
When I re-locked the phone it said Tampered + Relocked + Security Warning
As recovery I have TWRP 2.6.0.0 flashed. I did nothing else.
Could someone help me with instructions or at least directions how I could go back to a nice stock RUU? With the one I downloaded i had different error codes 213 (wrong ID) and 255 Unkown error.
I believe as the phone is not S-OFF and/or Super CID, it is relevant which RUU I download. The phone used to boot with a voda logo, so I believe it was one of the UK or AT voda stock roms, but neither works.
Your opinion/feedback is highly appreciated.
Cheers,
skee
Click to expand...
Click to collapse
To go back to stock u have to flash the right RUU, depends on which CID ur phone got.
u can download it here: http://www.androidruu.com/?developer=Ville
If u downloaded the right RUU, boot ur HOS into fastboot relock the phone and start the RUU.
Let it finish and u r on stock

Hi Homeboy, thanks for the answer. Seems clear. I have only 1 question. How can I make sure which is the right RUU?
I believe I should do a getvar all command, to see the CID id? Then what shall I look at the RUU's filename?
And after the phone having been relocked, shall it be in fatboot USB in bootloader or shall the phone be up and running when I start the RUU.exe from the computer?
thanks

skee81 said:
Hi Homeboy, thanks for the answer. Seems clear. I have only 1 question. How can I make sure which is the right RUU?
I believe I should do a getvar all command, to see the CID id? Then what shall I look at the RUU's filename?
And after the phone having been relocked, shall it be in fatboot USB in bootloader or shall the phone be up and running when I start the RUU.exe from the computer?
thanks
Click to expand...
Click to collapse
hi,
i saw u live in Hungary so it should be the Europe RUU try this:
http://www.androidruu.com/getdownload.php?file=Ville/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
And yes phone should be in fastboot when u start the RUU.

[Q] Failed attempt at re-branding K2_UL - help needed

I have been faffing about with S-OFF and the like in an attempt to de-brand my phone to stock HTC with root (the handset was an Orange UK CID). I've been at this for a couple of days now and have seemingly got myself stuck in a corner with the 2.0 hboot, which seems to be what's causing the problem for me - I was previously able to run the stock ICS RUU, but can't any longer.
Handset: HTC One SV LTE (model ID PL8010000)
*** UNLOCKED ***
K2_UL PVT SHIP S-OFF RL
CID: HTC__001 (have also been in SuperCID 11111111 numerous times)
HBOOT: 2.00.0000
RADIO: 1.15.40a.00.04
OpenDSP: v9.2.0268.1214
eMMC-boot
Mar 14 2013, 22:10:43-1
OS at the moment is Viper, because that's all I can get to install. None of the OTAs work (various errors relating to parsing android-info.txt and remote access issues in fastboot). The trouble with Viper is that the radio is apparently knackered, because I can't get a signal at all, and I was on stock JB and on ICS.
If anyone can provide me with a stock ICS 1.00.0000 HBOOT, I can try the RUU again at least. OTAs don't work from there, but it'd be a start. Any other ideas would also be greatly appreciated!
EDIT: Sorry, I forgot I'd already found a stock HBOOT and used it earlier, so have done that again now. Have now run RUU and am on stock HTC__001 version of ICS (K2_UL_ICS_40_HTC_Europe_1.17.401.5_R_Radio_0.12.40.00.14_2_10.49.40.11L_release_301902_signed). However, I still need help getting updated through the OTAs, of which I have 3 in .zip form:
OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.2-1.17.401.5_R_release_308698hqk34kifwjk0g071
OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.6-2.14.401.2_release_311966gsyc11xrfb40ox3c
OTA_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1-2.14.401.6_release_338297mseg08soslxcubit
METHOD 1:
When I try to run any of the above via fastboot oem rebootRUU, it fails and says it can't parse android-info.txt. I've checked the android-info in all three files, and the CID I have on the handset is listed in there, and the model ID is correct. I have verified with fastboot getvar cid that the CID is indeed HTC__001, so I don't understand what the problem is.
METHOD 2:
I've tried re-locking the bootloader and running again, but that still fails as above.
METHOD 3:
I've also tried just flashing the firmware.zip alone, but that spits out errors relating to the checks at two early stages in the updater script:
assert(check_cid(getprop("ro.cid") - I'm not sure why that fails given that the CID is correct for the OTAs, but it works if I just delete this check
assert(getprop("ro.product.device") == "k2ul" || - again, this is the correct device I'm trying to apply the OTA to, so I don't understand the issue
Sorry about the confusion in the initial post; any help would be greatly appreciated!

Your task should basicly be the easiest today, lol.
Get back to SuperCID, flash the RUU again (if needed, the 1.0 hboot before), and then, when phone is booted into android, let it search for updates.
Download and installing should go fine, because you are stock from the RUU and have SuperCID. Do this until no updates left and you are on 4.2.2.
You can also orientate on this guide.

old.splatterhand said:
Your task should basicly be the easiest today, lol.
Get back to SuperCID, flash the RUU again (if needed, the 1.0 hboot before), and then, when phone is booted into android, let it search for updates.
Download and installing should go fine, because you are stock from the RUU and have SuperCID. Do this until no updates left and you are on 4.2.2.
You can also orientate on this guide.
Click to expand...
Click to collapse
Man, I am so sorry. Not only did I fix this myself, I found out what I'd done to cause the ballsup. You know how I said I was getting 0 signal on the network? When changing the CID, I had accidentally overwritten the first 4 digits of the IMEI, so it wasn't recognised as valid any more. Just re-edited mmcblk0p4 to reinsert the original IMEI and it's now getting a signal. Prior to that, I managed to flash HBOOT 1.0 and run RUU then flash the OTAs manually. Have also reflashed TWRP 2.7 and backed up so I can hopefully recover faster from any more mess I make for myself...
Having said that, when I was trying to get the OTAs actually over-the-air, it kept reporting no updates available. Do you think that's just a result of the IMEI issue or do I need to be fully S-ON and locked (as in HTCL) to get OTAs? Do I also need the stock recovery?
Thanks very much for the reply, mate. I wouldn't have been able to do this stuff without your guides and replies on this forum, as well, so I'm grateful for your help.

Well, hard to say with your OTAs, because i never had a non-working CID.
But to run the official OTAs you need for sure a stock recovery!

old.splatterhand said:
Well, hard to say with your OTAs, because i never had a non-working CID.
But to run the official OTAs you need for sure a stock recovery!
Click to expand...
Click to collapse
The CID's fine, it's just the fact I overwrote it onto part of the IMEI... at one point I had manually edited HTC__001 into mmcblk0p4 then later rewritten it via the set cid command, which resulted in that line of the file being set to "HTC__001_001" because I'd keyed it in with the _001 overwriting the first 4 digits of my IMEI. Because I am an idiot, it would seem. Nonetheless, when I was requesting the updates OTA the CID was working fine. However, I only had stock recovery *some* of those times I tried to get OTAs, and I can't say whether the IMEI ballsup was there right from the start or not because I have no idea when I did that. I'll possibly reflash from the RUU again at some point and attempt an OTA on stock recovery with the correct IMEI, but for the time being I'm playing around with Viper because half the reason I started faffing about in the first place was that I thought some of the stock bloatware on the Orange firmware was possibly slowing down the handset (which it evidently was, since it remained slow post-fstrim) and Viper lets me strip the HTC crap out as well.
Anyway, sorry about the dimwittedness, and thanks very much for your help! :good: