Database Info

[Q] Defining RUU

hey guys,
I have a one s with the following info
cid = t-mob102
android version = 4.03
htc sense = 4.0
software number = 1.84.531.2 710RD (MoDaCo.one ir3)
i wanted to go back to stock rom, so ive downloaded a RUU, but it wasnt the right one.(says ERROR [130]: MODEL ID ERROR)
i wonder if anyone knows which ruu i should use to get back to my phones stock?
its kinnda urgent.
thanks in advance

m2afs said:
hey guys,
I have a one s with the following info
cid = t-mob102
android version = 4.03
htc sense = 4.0
software number = 1.84.531.2 710RD (MoDaCo.one ir3)
i wanted to go back to stock rom, so ive downloaded a RUU, but it wasnt the right one.(says ERROR [130]: MODEL ID ERROR)
i wonder if anyone knows which ruu i should use to get back to my phones stock?
its kinnda urgent.
thanks in advance
Click to expand...
Click to collapse
Goto http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html
I think there are a few T Mobile RUUs there. On the second page there is
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501
which likely should work.
On the first page there is also an upgraded RUU for T Mobile
RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04
If your OK with an upgrade go for that one. Just remember it may upgrade your bootloader and radio. If you wanted to flash older radios after that, you would have to go through a more complicated bootloader downgrade.
Those should work.
AKToronto

actually the ruu i have downloaded that says its the wrong model is exactly the following
RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed
as Ive looked inside its ROM this ruu is for t-mob010 not for t-mob102. and i guess thats why it fails.
what now?
Ive realized my phone loses signal from time to time and after a research i found out that upgrading to that specific version will solve the problem, but right now i cant really get into it coz i don't know the exact RUU to use.
the process i tried to do this is
1.i tried the normal way
-boot into fastboot
-relock the bootloader
-reboot to fastboot again
-run the ruu
-got error 130
2.i tried without locking the bootloader
the same process
-got error 155
i dont know if im missing something here, im new to android and all the flashing stuffs, any help would be appreciated.

So, I've found out that T-MOB102 refers to T-Mobile Austria, and I should be looking for one with this signature x.xx.112.x.
Still I haven't found any with the signature for ONE S.
Any Suggestions?

still nothing on the TMA T-MOB102 T-Mobile Austria RUU.
I've tested every RUU in Here: filefactory.com/f/cf061f69b5bf7878/
None of them were mine, how is it possible that there's no RUU made for my phone type.
Should I Change my CID? Is It possible?

m2afs said:
still nothing on the TMA T-MOB102 T-Mobile Austria RUU.
I've tested every RUU in Here: filefactory.com/f/cf061f69b5bf7878/
None of them were mine, how is it possible that there's no RUU made for my phone type.
Should I Change my CID? Is It possible?
Click to expand...
Click to collapse
So I think you have two options. One is CID, or two is to keep trying to find that RUU.
1. There is a link to Super CID instructions in the dev forum at http://forum.xda-developers.com/show....php?t=1671643
-Do read a bit of the thread. You can still only flash a RUU that has a bootloader version equal or higher than what is on your phone.
2. If there is a RUU that you think exists that Football has not posted in his thread, than I suggest PM ing him. Thats how I was able to get the three Bell Mobility RUUs onto FileFactory. He was pretty helpful when I PMed him myself.
Cheers,
AKToronto

How Can I PM Football?

m2afs said:
How Can I PM Football?
Click to expand...
Click to collapse
Click on his name in any of his posts. Then click send message. I use PM to stand for private message.
AKToronto

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

[Q] Help with TMB101 branding

Hi guys,
I would like some help with flashing a Stock RUU onto my desire s.. I have gotten it S-On and removed revolutionary.
You can see my phoneinformation from adb below i attached it. Hboot 0.98 and a T-MB101 branding.. Build(main) 2.10.401.5 german phone
The problem is I cannot find any RUU to flash which will work for my Phone (I open them as admin)
I have tried the TMO 1.3.111.1 with the RUU error 140
I have tried the 2.10.401.5 and 8 and 9 builds for EU but they all give me error 131 (as they are not for branded phones?)
What can I do know what RUU could work how do I get the TMO to work? Are there any more RUUS I could even try to use? Should I try a Goldcard? Any Ideas? Thanks guys..
Please Help

Looking for a compatible RUU File for HTC One S Cincinnati Bell (PJ40110)

Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance

Auraburst said:
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Click to expand...
Click to collapse
It's easier to find the correct one if you know your firmware version/build number. If you're still using stock rom you can find it in settings>about>software information>more. If you already deleted the stock system on your phone you need to use
Code:
fastboot getvar all
in fastboot mode (look at the line beginning with "version-main"). Since you already unlocked your phone I assume you know how to use fastboot with the windows cmd.
RUUs can be found here for example. Just use the search function of your browser and be sure that you download a RUU and not an OTA. Since there are two versions of the One S you need to be careful not to use VilleC2 (Snapdragon S3 with 1.7 gHZ) files on a Ville (Snapdragon S4 with 1.5 gHz) and vice versa (this rule applies on roms, kernels, etc., too). If I remember correctly your hboot is Ville specific but if you want to be sure you can find the answer in the getvar all output (look at the line beginning with "product").

Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)

Auraburst said:
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Click to expand...
Click to collapse
The problem is that the only file with the 422 SKU is an OTA and not a RUU. If your phone was S-OFF you wouldn't need to use corresponding RUUs because you were able to flash any you want. It's a vicious circle in your case since you wanted the correct RUU before you start flashing. On the other side if you carefully follow the instructions of the S-OFF guides there shouldn't be any risk of bricking. Simply don't try to use any short cuts if any step doesn't not work the way the instructions tell you. Since I'm not living in the states I'm not completely sure but Cincinnati Bell is part of Bell Mobile, right? If that's correct I would change the CID to SuperCID (depending on the S-OFF method you use you may need to get the SCID anyway) and try to run one of the "BM" RUUs on AndroidRUU. Since all of them are older than you actual firmware your phone will be downgraded then but you can update it by using the OTA function in settings>about.
Btw.: With that output you can be sure it's the Ville and not the VilleC2.

Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone

Auraburst said:
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Click to expand...
Click to collapse
Actually your radio doesn't matter at all in regard of RUUs. Flashing a RUU is never risky as long as it's a signed/official one and you do not turn off the phone during the flashing process or disconnect it from your pc. If you are not S-OFF and your CID and/or firmware version doesn't match (SCID always matches) official RUUs will simply abort the flashing process.
After you achieved S-OFF and got the SCID you simply need to relock your bootloader, boot into fastboot mode, connect the phone to your pc and run the RUU.exe. (As far as I remember relocking was needed for being able to install OTAs afterwards but I'm not completely sure. I just remember that I always did when I downgraded. Maybe someone else can confirm this.)
I personally do not like Cyanogenmod on this phone. Since there never was a GPE of the One S (the first HTC GPE that ever existed was the HTC One M7 GPE which is actually younger than this phone) there are no AOSP drivers for this phone and you can notice this problem for example in a worse camera quality on roms that are not based on sense (there are other problems but that's the most prominent one I can remember).
MaxximusHD is based on the leaked but never officially published android 4.2.2 firmware of the One S. If you want to use it without memory problems (the leaked firmware changes the way the phone interacts with it's memory) you need to flash the hboot 2.16. Instructions can be found in the Maxximus thread for example. I personally prefer hboot 2.16 because of its reorganized memory but the radio 1.20 that gets flashed with that firmware has some problems with the incall voice quality.
To sum it up, every custom rom has its pros and cons and every user has his/her own preferences so it's hard to tell others which rom to use. The best way is to look which ones fullfil your needs and to test them out by yourself.
Edit: Downgrading isn't needed if you just want to start flashing. I just wanted to point out what happens if you run a RUU that is older than your actual firmware.
Edit2: Nevertheless here is a chronological list of the roms I liked and used longer than a week on this phone: Viper 2.2 (hboot 2.15), MaxximusHD (hboot 2.16), Viper 3.2.1 (hboot 2.16).

Advice on S-Off for rooted/unlocked HOX w/ 4.0.2

I have an AT&T HOX running the original stock ICS 4.0.2 The phone is rooted, bootloader unlocked and has Supercid.
I would like to install one of the new Cyanogenmod ROMs that require HBoot version to be 2.14 or newer, but I'm having problems. I can't use an RUU to upgrade to 4.2.2 or whatever, because I'm supercid and will probably brick the phone. Facepalm/Rumrunner/Firewater/moonshine etc, S-Off tools do not work with this particular kernel for whatever reason, and I just get the "Please install an 'unsecure kernel" advice at the end of the attempt.
So, basically, I can't get S-Off because none of the tools work with my OS version, and I can't update my OS via the normal channels because of having supercid, and I can't upgrade my firmware because I'm not S-Off. Kind of a catch 22-22-22 situation.
I'm not even sure what question to ask at this point, so I'm open to any advice you guys are willing to offer in regard to upgrading to HBoot 2.14 to meet the requirements to install CM 11 on my phone. My current HBoot version is 1.14
**Edit** Current firmware - 2.20
Thanks in advance.

Maybe a solution
Well, I finally found a thread by someone with a similar situation. It looks like the procedures outlined by Heisenberg in his replies did the trick for that particular person, so I'm gonna give that a try I guess. I'm not sure how I missed that thread after all the searching I've done before now, but for anyone who might be interested:
http://forum.xda-developers.com/showthread.php?t=2218990
Thanks

Try to flash Kickdroid 5.0 as outlined in the other thread, then you should be able to get s-off.