Hi,
Apologies that this will very much be a noob post but help would be very much appreciated. I bought a HTC sensation XE which was imported from Taiwan. I wanted to use an RUU that is from Europe (the most recent one I found, 1.73.401.4), so that I wouldn't have all the branded apps. To do this, I first followed the htcdev unlocking guide, and then tried to change the CID to superCID, which it did not allow. Instead, I changed the CID to HTC__001 which I thought would work for Europe RUU. I then tried running the RUU exe file, but it eventually came up with a 155 error and did not install. From what I can gather, this is because I actually needed S-OFF to change the regions of the device.
I read that it was best to undo the htcdev lock (or perhaps even to not have done it in the first place). So, I ran "fastboot oem lock". This seems to have worked, because the bootloader now reads 'RELOCKED'. However, when I load the phone and click on bootloader it flashes a load of green lines like this:
sd checking...
loading...[PG58DIAG.zip]
No image!
Loading...[PG58DIAG.nbh]
No image or wrong image!
...
Otherwise it seems to be loading the original ROM without any issues. I cannot find any files on the SD card that include PGD58DIAG in their name. I have now changed the CID to HTC__622, but I'm not sure if this was the original one (is there any way to find out now?).
Does anybody have suggestions on how I proceed from here? Just to recap:
- Taiwanese import HTC sensation XE
- Used HTCdev to unlock, but have now relocked
- Have changed the CID to HTC__001 and now to HTC_622; may not be original.
The questions I have are:
1) Are the green lines of text that I am getting about PG58DIAG important?
2) If I want to debrand the phone and ideally move to European unbranded RUU, what should I do now? Should I try S-OFF and then changing to superCID as in the guide by Alexp999 here (http://forum.xda-developers.com/showthread.php?t=1193033) - i.e. is it safe to do this, despite the green lines of text and having re-locked the htcdev?
Thank you so much for any assistance. I've really tried looking everywhere on here and can't seem to find a guide or thread that takes into account all my issues!
Oliver
**********
Software number 1.77.709.104
Baseband version 10.58.9035.00U_10.15.9035.02_2
Build number 1.77.709.104 CL239628 release-keys
Hboot: 1.18
1. That green "loading img" message you keep getting almost always normally occurs when you enter boot loader....it checks for RUU file in sdcard root folder. This is normal.
2. Root...super cid...the fastboot flash ruu
Just as FYI. Wasn't sure if you knew this so forgive me if you did.
RUU flashed in fast boot must my named "PG58IMG.zip"
RUU must be in root folder of sdcard
Sent from my HTC Pyramid using XDA
Choose the correct firmware from here
super sid not needed
Read and follow the instructions carefully
Thanks for the advice and the reassurance! From the sounds of things I shouldn't go ahead until I have the original RUU downloaded in case things go wrong. Can't seem to find it for 1.77.709.104 anywhere, so perhaps I'll wait to change ROMs until it gets posted somewhere!
Related
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
smash_07 said:
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
Click to expand...
Click to collapse
Hi,
This is a SENSATION forum.
malybru said:
Hi,
This is a SENSATION forum.
Click to expand...
Click to collapse
Yes I noticed it i already asked the moderation if they could move the thread to the Desire S section.
I need to find this out to? I dont want to root my Desire S, I just want to changde CID so i could put unbranded software to it...?
You can just create a GoldCard and make it work, without root or S-Off.
Earlier today I created a GoldCard and upgraded my DS using the European RUU and I'm S-ON & Unrooted.
See here: http://forum.xda-developers.com/showthread.php?p=19171606
doghous said:
You can just create a GoldCard and make it work, without root or S-Off.
Earlier today I created a GoldCard and upgraded my DS using the European RUU and I'm S-ON & Unrooted.
See here: http://forum.xda-developers.com/showthread.php?p=19171606
Click to expand...
Click to collapse
Yes I know that works I have a Goldcard. The thing here is that I would like the phone to be completely unbranded without the need os special cards so in case i want to sell it or send it to warranty it won't be noticed that i changed something there. So if there is a way to re write de CID it would be good.
Well i actually successfully installed the unbranded european ROM 1.28.401.1 using the gold card. But now i can't receive OTA updates. Is there a way to get it to work?
Why don't you run the European RUU 2.10 version (RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed) from the following link:
http://forum.xda-developers.com/showthread.php?t=1002506
That's what I did
smash_07 said:
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
Click to expand...
Click to collapse
Just to answer your question:
(I may need to be corrected on this one)
Based on my observation and experimentation. The CID that you are trying to change, or the CID that the RUU is checking is actually on the build.prop on your phone.
Code:
ro.aa.maincid
But there are two checks that I've observed. Even though you changed the maincid, the corresponding cwkey should be changed accordingly.
cwkey created on your phone corresponds on what is on the build.prop and I believe is also being checked by RUUs.
And maybe just to be on the safe side, RUUs do check what is on your build.prop. If they are not what your RUU wants, it will not push through. Hence, you need a GoldCard.
I myself don't exactly, by codes, know how the GoldCard bypasses the checks. All I do know, is that it works.
Skanob said:
Just to answer your question:
(I may need to be corrected on this one)
Based on my observation and experimentation. The CID that you are trying to change, or the CID that the RUU is checking is actually on the build.prop on your phone.
Code:
ro.aa.maincid
But there are two checks that I've observed. Even though you changed the maincid, the corresponding cwkey should be changed accordingly.
cwkey created on your phone corresponds on what is on the build.prop and I believe is also being checked by RUUs.
And maybe just to be on the safe side, RUUs do check what is on your build.prop. If they are not what your RUU wants, it will not push through. Hence, you need a GoldCard.
I myself don't exactly, by codes, know how the GoldCard bypasses the checks. All I do know, is that it works.
Click to expand...
Click to collapse
So what that means is the phone has to stay branded? There is no way that we can fully unbrand the phone by changing the CID?
And after we use the Goldcard what happens to the CID of the phone?
smash_07 said:
So what that means is the phone has to stay branded? There is no way that we can fully unbrand the phone by changing the CID?
And after we use the Goldcard what happens to the CID of the phone?
Click to expand...
Click to collapse
The goldcard does not alter the CID. It just tells the bootloader to ignore the CID check when running a RUU.
One way to alter the CID is to XTC clip the phone.
Well i ended up doing what you all suggested and flashed the RUU with the 2.10 european rom with the goldcard in it.
But something went wrong and my Desire S is in a strange situation. For some reason the Goldcard did not work like the first time and gave me a CID error. But it flashed the hboot 2.00.0002 but retained the 1.28 rom i had installed on it. I have used the HTCDev method to unlock the bootloader but everytime i try to flash the 1.28 RUU again (to flash the old hboot again) it gives me an "unknown error" that is actually a security error.
Is there a way to get the old hboot back?
smash_07 said:
Well i ended up doing what you all suggested and flashed the RUU with the 2.10 european rom with the goldcard in it.
But something went wrong and my Desire S is in a strange situation. For some reason the Goldcard did not work like the first time and gave me a CID error. But it flashed the hboot 2.00.0002 but retained the 1.28 rom i had installed on it. I have used the HTCDev method to unlock the bootloader but everytime i try to flash the 1.28 RUU again (to flash the old hboot again) it gives me an "unknown error" that is actually a security error.
Is there a way to get the old hboot back?
Click to expand...
Click to collapse
My reply to this post of yours is already a hint.
Use search PLEASE.
Hey, All
I was successful unlock , root following this thread,
http://forum.xda-developers.com/showthread.php?t=1583427
Then I'm trying to install this RUU , RUU_Ville_U_Rogers_WWE_1.70.631.1
this step always get device id error,
so I back to stock recovery, modify CID form "HTC__203" to "11111111", and relock with following this thread,
http://forum.xda-developers.com/showthread.php?t=1674202
Yes, finally "RUU_Ville_U_Rogers_WWE_1.70.631.1" installed, all function works.
Now, I have a problem , I'm trying to unlock again, so i using "faseboot oem get_identifier_token", and paste id to htcdev step 11, and get a new "Unlock_code.bin"
when I using this "Unlock_code.bin" to unlock my device, everything seems normal, but when I reboot, the device still display RELOCKED
any suggestion?
chuaniyang said:
Hey, All
I was successful unlock , root following this thread,
http://forum.xda-developers.com/showthread.php?t=1583427
Then I'm trying to install this RUU , RUU_Ville_U_Rogers_WWE_1.70.631.1
this step always get device id error,
so I back to stock recovery, modify CID form "HTC__203" to "11111111", and relock with following this thread,
http://forum.xda-developers.com/showthread.php?t=1674202
Yes, finally "RUU_Ville_U_Rogers_WWE_1.70.631.1" installed, all function works.
Now, I have a problem , I'm trying to unlock again, so i using "faseboot oem get_identifier_token", and paste id to htcdev step 11, and get a new "Unlock_code.bin"
when I using this "Unlock_code.bin" to unlock my device, everything seems normal, but when I reboot, the device still display RELOCKED
any suggestion?
Click to expand...
Click to collapse
Well it's still gonna show relocked if that's what your talking about bcuz you unlocked it then relocked so it isn't gonna show tampered with unlocked at the bottom that's only for the first time you unlock it that it says tampered with unlocked at the bottom, but if you unlock it again it's just gonna say relocked not unlocked. Hopefully this answers your question.
Sent from my samsung galaxy player
my screen didn't have "tampered" any more. I'm not sure but it's strange.
so, I post the photo step by step what am i do. see 001.jpg ~ 009.jpg with following link
https://www.dropbox.com/sh/ksyrdgvjo4xrgiw/1Kr3CmwHnd
chuaniyang said:
my screen didn't have "tampered" any more. I'm not sure but it's strange.
so, I post the photo step by step what am i do. see 001.jpg ~ 009.jpg with following link
https://www.dropbox.com/sh/ksyrdgvjo4xrgiw/1Kr3CmwHnd
Click to expand...
Click to collapse
Yea that is strange but I don't think it would be considered a problem unless you have the phone stuck in Bootloop or something strange is going on with the phone like apps.not working or battery draining fast. I can see what your worried about and it is strange but I wouldn't worry too much about it but you should look up somewhere in the forums about that but I wouldn't know much about the international version I'm on the US version. Good luck with your problem
Sent from my samsung galaxy player
I checked this thread
http://forum.xda-developers.com/showthread.php?t=1671643
seems I need to wait someone can S-OFF this device
superCID can install any RUU, but can't unlock, root, install custom ROM without S-OFF
I've managed to change my cid and install a new Rom then unlock it and root so it's possible
Sent from my HTC One S using Tapatalk 2
the other reason maybe user just can unlock/relock limited times. ?
does any one change CID and unlock/relock over 3 times ?
I've relocked about 4 time's now changed cid once
Sent from my HTC One S using Tapatalk 2
My default cid is HTC_203, i changed to HTC__102, HTC__001 and 11111111.
Everytime cid changed, I will lock/unlock again. When changed to 11111111, I can't unlock anymore.
Sent from my HTC VLE_U using xda app-developers app
Mate, the CID is in the partition that gets summarized together with the other partitions when calculating the Unlock Token.
So, if you change this or any other relevant partition by for example changing the CID, you will invalidate your old unlock token.
After changing CID, please re-lock bootloader, then go "fastboot oem get_identifier_token" and go to HTC-Dev and unlock again.
After that, you can proceed with everything else as usual.
If you cannot unlock with CID 11111111 this is NOT normal. Everyone else can.
So either you did something wrong in the above process or you somehow half-bricked your phone.
Yes, everytime I changed cid, I got a new unlock code. if not, fastboot will give me error message during unlock process.
I think my situation is not normal, and I'm trying to find out why then fix it. Now, I still can install any RUU , if they have the same HBOOT version.
Sent from my HTC VLE_U using xda app-developers app
I'd guess it's a half brick because if you can't unlock something is wrong. There is no unlock counter because no-one has had it yet. I've unlocked about four or five times now too and don't have that problem. You should consider sending it in for repair. As long as there's no S-OFF you'll have no chance to force an unlock I guess. If the security is as complex as on the HOX, it's likely the situation couldn't even be resolved by a jtag programmer or such.
sent from the tip of my finger
Thanks, no one have the same question as me. I will try to call HTC service.
CID 11111111 Issue
Hello there,
I want to install an older RUU (actually installed is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed )
my intention is to downgrade the Basbeand Version with this Procedure to get rid of this "HomeButton-Jumparound-Whatever" Issue which occures when i am in GSM (2G) Mode.
when i get this phone brandnew there was no Problem, just after updating to 1.78 this ****** began.
When i changed my CID from HTC__102 to 11111111 the first time everything went fine and i was able to install every RUU
Now i tried to change my Radio to an older Version by install an older RUU, but it won't work no more, i allways get an Error 140 or 131.
if there is another method to change the radio version, I'd appreciate any council
relock Bootloader, turn off virus scanners, run ruu as admistrator, I've done of course
I would be grateful for any help
ERROR 140 : bootloader error
ERROR 131 : cid error
are you install T-MOBILE 1.84 RUU ?
this will chane HBOOT version from 1.08 to 1.09
if you can unlock, try to find some way change your HBOOT version back to 1.08.
then you can insall RUU_Ville_U_HTC_Europe_1.78.401.2.
RUU_Ville_U_HTC_Europe_1.78.401.2 can be installed only with the other it does not work
i've got HBOOT 1.13.000 (shown in bootloader)
i just want to downgrade the Radio..
edit: when try to install RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed
or
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed
i get Error 155
we have some thing different. but you are lucky then me. I just can install T-MOBILE 1.84 RUU, if I try to install another version. always got HBOOT version error
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.16_2
(bootloader) version-main: 1.84.531.2
(bootloader) commitno-bootloader: e964c535
The HTC srevice center(tw) call back. they say they find some motherboard error on my device.
I don't think change cid and unlock will cause it happen.
I know there are several threads like this one but I prefer not to write another RUU request while you're answering to another user
So, I got a HTC One S S3 yesterday... I began to unlock it because I wanted to change its CID. I found that in the S3 version the CID can't be changed (still) when I had already installed the TWRP Recovery.
Now I'd like to go back to stock, but there is not a RUU compatible with my device: It has VODAP102 as CID, but the RUU for Vodafone AT here doesn't work. I found the kernel source for the same software version I have in htcdev.com, my question is: is it possible to build a RUU or at least a boot.img from it?
The sources can be found in htcdev /devcenter/downloads (sorry but being new I can't post direct links!), HTC One S as Device, Vodafone as Carrier and UK -
1.11.161.133 as software version. Actually I am in Italy, but the software and kernel version are exactly the same.
Thank you in advance.
Bump to first page and a little addendum:
I've read again all the possibilities I have with this phone, and if I have understood accurately then I'm forced to go back to stock, roms like the ThickDroid seem to require a non-branded CID, but that's the point... it is the CID that's compelling me to maintain this original Vodafone software, otherwise I would have already installed the HTC "basic" rom.
Am I missing something?
Thank you again!
Have you tried looking on HTCRUU.COM?
Check your radio id on the bootloader screen then flash the appropriate ROM
mikejasonsmith said:
Have you tried looking on HTCRUU.COM?
Check your radio id on the bootloader screen then flash the appropriate ROM
Click to expand...
Click to collapse
Yes I checked, but they have just unbranded RUUs, here in the forum there's one RUU for Vodafone but the region isn't the same as mine.
I've read that it is possible to flash an OTA update deleting the string that checks the CID - I'll have to take a look about that (moreover, it seems very difficult to find .zip OTA updates for this phone...).
Nevertheless I'd like to find this RUU update too - it is an important option too. So... bump to first page.
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:
Hi all!
I've been having a big problem and I can't solve it on my own since I can't understand what am I doing wrong...
I tried to install a custom os on my HTC one S but something went wrong (I can't remember exactly what) and my HTC One S was just rebooting in TWRP recovery without loading the system.
I assume there is no system anymore and I don't know what to do..
Some friends of mine told me that I should return to stock ROM throughout RUU Ville and I've tried to follow some tutorials about that failing miserably...
I've been going crazy for the last month trying to figure out which RUU I should download since my model is VODAP102 and it seems that this CID is pretty much uncommon.
I don't know what to do and I'm at the point of no return and giving up, please help me
Wrong section, head over to the HTC One S thread for help.
Anyone?
Sorry for having to say that but the Information you provide are pretty much useless. According to your post I assume you don't know what S-OFF is and therefore your phone is probably S-ON (stated in Bootloader Mode, btw), right? Therefore you need a RUU that matches your firmware or belongs to a higher firmware version.
Set up an ADB/Fastboot environment (if you haven't already): Download this archive, create the directory "C:\Android" and unzip the archive into that folder. Right-click into the folder while the Shift button is pressed and choose "Open command line here" (the naming might be a bit different - I only translated it from German into English). Use the command "fastboot getvar all" and look at the line with "version-main" (Edit: never post the fastboot getvar all output somewhere on the internet unless you removed your IMEI and your serial number). That's your currently installed firmware. Besides you need to look at the line with "product" to find out whether you own the Snapdragon S4 model (Ville aka vle) or the Snapdragon S3 model (VilleC2). Search on this site (for the Ville) or this Site (for the VilleC2) for a RUU with the same or a higher version number. Be aware that the 3 numbers behind the second dot always have to stay the same. E.g. a phone with S-ON and firmware 2.31.401.5 can also use a RUU for 3.16.401.8 but not for 2.21.401.10.
If your version-main is deleted (happens if you flash a faulty TWRP version - I forgot which one it was because it's a pretty old version) then you should try to use the latest RUU that belongs to your SKU (those are the 3 numbers behind the second dot). The CID VODAP102 either belongs to SKU 161 or 166. (I know that HTC changed that somewhere in the past but I forgot when that was. On the M9 VODAP102 belongs to 161 but I'm not sure whether this applies to the Ville, too).
If there is no RUU available you could use your only hope is Llabtoofer's RUU Service.