Database Info

Need help finding my RUU

baseband: 0.17.31501S.10_2_10.27.31501S.10L
CID: HTC_K18
Image Version: 1.84.461.11
I can't find my ruu and i was searching here:
http://forum.xda-developers.com/showthread.php?t=1543588 (i have the s4 version)
the closest one found was with my baseband version but had a different image version.

Try this one
http://www.filefactory.com/file/zfv..._2_10.27.31501S.10L_release_265369_signed.exe
Sent from my HTC One S using xda app-developers app

mirror
blackcell1 said:
Try this one
http://www.filefactory.com/file/zfv..._2_10.27.31501S.10L_release_265369_signed.exe
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
thats the one i was talking about but as you can see the image version is different from mine
i have 1.84.461.11 and the download have 1.84.666.9.
my question is if it will be compatible?

Hi you, why you not change CID to supper CID 1111111?, you can flash any RUU file if you want.

thanhthao2002 said:
Hi you, why you not change CID to supper CID 1111111?, you can flash any RUU file if you want.
Click to expand...
Click to collapse
cause someone told me that i need to have s-off to supercid and i can't s-off one s.
i don't know if i need s-off or just unlocked bootloader?

LSGio said:
cause someone told me that i need to have s-off to supercid and i can't s-off one s.
i don't know if i need s-off or just unlocked bootloader?
Click to expand...
Click to collapse
You need S-OFF if you have an S3. If you have an S4, just an unlocked bootloader is fine.
Sent from my HTC One S using Tapatalk 2

usaff22 said:
You need S-OFF if you have an S3. If you have an S4, just an unlocked bootloader is fine.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
i have s4 but can you please give me a link on how to supercid?
thank you!

LSGio said:
i have s4 but can you please give me a link on how to supercid?
thank you!
Click to expand...
Click to collapse
Reboot phone into fastboot mode, open cmd window on your computer linking to the adb path.
fastboot oem writecid 11111111. Being SuperCID you can flash whatever RUU, but not receive OTA updates.
Sent from my HTC One S using Tapatalk 2

usaff22 said:
Reboot phone into fastboot mode, open cmd window on your computer linking to the adb path.
fastboot oem writecid 11111111. Being SuperCID you can flash whatever RUU, but not receive OTA updates.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
first i have to say that i have a S4 version that i checked with cpu spy and you told me that i only need unlocked bootloader so its unlocked and when i try to supercid it says: FAILED (status read failed (Too many links)) and then i get stuck in bootloader mode and i have to get it out of bootloader mode manually (command fastboot reboot-bootloader didn't help cause i got a respond of waiting for device)
and then when i boot again into fastboot usb and type fastboot getvar cid it says HTC__K18 like the old one.
what do i have to do?
is there any way to s-off htc one s?

LSGio said:
first i have to say that i have a S4 version that i checked with cpu spy and you told me that i only need unlocked bootloader so its unlocked and when i try to supercid it says: FAILED (status read failed (Too many links)) and then i get stuck in bootloader mode and i have to get it out of bootloader mode manually (command fastboot reboot-bootloader didn't help cause i got a respond of waiting for device)
and then when i boot again into fastboot usb and type fastboot getvar cid it says HTC__K18 like the old one.
what do i have to do?
is there any way to s-off htc one s?
Click to expand...
Click to collapse
There is a link to Super CID instructions in the dev forum at http://forum.xda-developers.com/showthread.php?t=1671643
Also, there is no s-off yet for HTC One S.
Third, what carrier do you have? I did not recognize your CID. 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. But I am curious about your carrier as it may already be in his list.
Cheers,
AKToronto

AKToronto said:
There is a link to Super CID instructions in the dev forum at http://forum.xda-developers.com/showthread.php?t=1671643
Also, there is no s-off yet for HTC One S.
Third, what carrier do you have? I did not recognize your CID. 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. But I am curious about your carrier as it may already be in his list.
Cheers,
AKToronto
Click to expand...
Click to collapse
My carrier is cellcom, israel.

Help with RUU'ing to 2.20

I've been running AOSP ROM's on my evita for a while now, but apparently with the 3.4 kernel you now need hboot 2.14 or higher and mine's at 1.09. My phone was unlocked with S-ON, but I did "fastboot oem lock" this morning because I read that it's necessary for an RUU. I downloaded the 2.20 RUU and tried to run the installer but I always get an Error [170] USB Connection Error. I have the HTC and adb drivers installed successfully and have tried to run the RUU as admin in both Sense and fastboot (bootloader). I'm a bit stumped and would really like to get AOSP back on my phone.

You need to S-off first.
Sent from my HTC One X using xda premium

tlazarus said:
You need to S-off first.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Should I use facepalm for that then?
EDIT
I got s-off, but still no go. Still the error 170.
I know on my old Incredible I was able to rename the rom.zip from the RUU as PB99IMG.zip and put it on the root of my sdcard. Then in hboot it would detect it and ask to flash it. This isn't happening on my evita though. Is there a way to do that, or is that only for older htc devices?

Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium

Venomtester said:
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Where can I find this error log? It did see my device, I did that command (which ended at the black htc screen) and I ran the RUU again but I still get the error 170. I'm also using this RUU http://bugsylawson.com/index.php/fi...320911-2-101053225l-release-271865-signedexe/

Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium

Venomtester said:
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It is that size, though I may try the link you gave.
EDIT
Okay, I think I found out what I've been doing wrong. I found this link http://forum.xda-developers.com/showthread.php?t=2119610 and it turns out that the file I've been trying does NOT include the 2.14 hboot that I need. The one I need is the latest JB release, but someone said that if you flash it with superCID and S-ON that it will brick your device. I have superCID but S-OFF, does anyone think that will brick my device? Should I flash the RUU with the 1.09 hboot (which I'm running) first, and then flash the newest RUU? Also, it looks like the link I provided offers flashable OTA's of each update. Would those work/be recommended for TWRP?

Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium

Venomtester said:
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error

dshoe said:
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
Click to expand...
Click to collapse
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium

31ken31 said:
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....

dshoe said:
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
Click to expand...
Click to collapse
Just make sure you are s-off before running ruu or risk a brick..
Sent from my HTC One XL using xda premium

Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?

For what it's worth, I was on stock 2.20, got s-off and unlocked bootloader with superCID, and ran the 3.18 RUU with no problems. I didn't need to relock or anything.

knanda said:
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
Click to expand...
Click to collapse
You can go ahead and run the RUU. No real risk because you're s-off. Maybe make a backup though.
Sent from my Evita

[Q] Can't update CM 10.1 OTA

I'm having issues updating to the latest version of CM 10.1. I currently run CM10.1-2013-0509-UNOFFICIAL-evita (4.2.2, May 9 2013) and when I try to update OTA I get the following error:
assert failed: getprop("ro.bootloader") == "2.14.000"
E: Error in sdcard/cmupdater/cm-10.1-2013030725-NIGHTLY-evita.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I've been trying to research the solution on my own and I'm confused. I think my hboot is out of date but in order to update it I need to have s-off and Super CID enabled (or change my CID to 111111 or 00000, can't remember which). Anyways, can anyone give me some guidance on how to get the latest CM versions installed?

Yeah you have to s-off and then run the 3.18 ruu. No way around it.
Sent from my evita

Fastboot OEM readcid will give you your current cid. If your phone is from at&t you should have it already. What hboot are you on right now?
Sent from my One X using xda app-developers app

RollTribe said:
Yeah you have to s-off and then run the 3.18 ruu. No way around it.
Sent from my evita
Click to expand...
Click to collapse
Can you point me in the direction of some guides? I've found different posts and guides and it's all confusing as I'm not sure which order to follow or if they all apply to my phone.
exad said:
Fastboot OEM readcid will give you your current cid. If your phone is from at&t you should have it already. What hboot are you on right now?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
My phone is from Rogers, I'm on hboot 1.11
I found a guide for fastboot oem readcid which reads:
Connect your phone with USB Debugging enabled
Open up an adb shell (if you don't know how to do this, Google it!)
Reboot into fastboot mode in the Bootloader.
Type: fastboot oem writecid 11111111
Type: adb reboot-bootloader
Type: fastboot oem readcid
If it says 11111111 then you have SuperCID
You can reboot as normal
Click to expand...
Click to collapse
When following the steps (only typing fastboot oem readcid, not the other lines) my cid is stated as: ROGER001
I do have S-ON enabled if that matters. I know I have to disable it but I'm not sure if I have to do that before or after I rewrite my CID, against some more confusion on my part and I've read doing it wrong can brick my device.

http://forum.xda-developers.com/showthread.php?t=2349919
Sent from my HTC One X using xda app-developers app

exad said:
http://forum.xda-developers.com/showthread.php?t=2349919
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
So I followed the steps and was able to enable S-OFF and achieve CID 11111111. I tried to update the hboot following the instructions here: http://forum.xda-developers.com/showthread.php?t=2156686
I tried installing the first version of the Hboot and when I rebooted the screen hung on the CM 10.1 boot logo. I tried to enter recovery through fastboot but a red exclamation mark screen would load. I reinstalled recovery through fastboot and then tried to do a factory reset through recovery and fastboot and my device is now stuck on the HTC logo when booting. I've tried reinstalling different versions of hboot (which I downloaded from those instructions) and nothing happens. Please advise, as of now my phone won't boot.
Edit:
I think what caused this problem was flashing this file: /ALL FILES FROM OTA 3.17 T-MO germain hboot 2.14 (incl recovery and other firmware files, be careful with that).
I'm pretty sure I did the firmware and recovery files as it took 60s to flash and I remember seeing a lot of RADIO files being written. My cell phone is a Rogers cell phone is there a stock version I can re-flash to make it work?
Edit II:
I was able to mount my phone via recovery and install cm 10.1. However, the phone isn't responding to any touch.

Which version of CM10.1 did you install? It sounds like it's an older one because they're not compatible with the newer touchscreen firmware. Download the latest nightly and flash that and you should be ok.
Sent from my Evita

Okay I finally got her working. I followed instructions here http://forum.xda-developers.com/showthread.php?t=2159863 to re-install the touch panel firmware, installed the corrected hboot update and upgraded to the latest cm 10.1. Cheers to everyone who contributed and helped me out!

For anyone who may find this thread in the future, the best thing to do would have been run an older RUU because there is no 3.17 RUU i believe and then either install the ota through stock recovery or Download the OTA through android (check for updates)

exad said:
For anyone who may find this thread in the future, the best thing to do would have been run an older RUU because there is no 3.17 RUU i believe and then either install the ota through stock recovery or Download the OTA through android (check for updates)
Click to expand...
Click to collapse
I was wondering if you could help me as I am getting the same error as the original poster and I can't update cyanogenmod. The only difference I think is that I am on the AT&T htc one x. I'm just looking for some direction so I don't end up bricking my phone. Thanks!

Are you s-off?
Sent from my HTC One X using xda app-developers app

exad said:
Are you s-off?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Nope! I have super cid never bothered with s-off. Is it required? I'm also on hboot 1.14...

You can't be serious.
Did you not read the rest of this thread? Or the clear install instructions on the cm10.1 thread? Must s-off and RUU to 3.18. Ugh.
Sent from my Evita

can't see version-main

i wanna flash RUU on my HTC One S and for that i need to know my version-main but when i go to fastboot and type "fastboot getvar version-main"
it shows blank!
also when i type "fastboot getvar all" i see everything but the version-main is blank! why?
is there any other way to determine which RUU i need?

What is your CID?
Sent from my Nexus 5 using Tapatalk

attelaut said:
What is your CID?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My CID is :
HTC__K18
i'm from israel!
can you help me find my ruu?

This RUU might work if your One S is S4 model.

What do you mean might work?
I have two questions:
If it doesn't work would my phone Get bricked?
How do I properly flash a RUU?
this is my current state:
Bootloader unlocked
Team win recovery
Cyanogenmod 10.2
Edit:yes,i have the snapdragon s4 (z520e)
Sent from my HTC One S using xda app-developers app

LSGio said:
What do you mean might work?
I have two questions:
If it doesn't work would my phone Get bricked?
How do I properly flash a RUU?
this is my current state:
Bootloader unlocked
Team win recovery
Cyanogenmod 10.2
Edit:yes,i have the snapdragon s4 (z520e)
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I'm not sure if there is RUU for your CID. I tried to Google that but I didn't find much. If you've bought your phone from carrier, then there is probably no RUU for your phone. If the CID doesn't match, then RUU won't run at all and it will throw an error. To run RUU you need to have locked bootloader and stock recovery.

attelaut said:
I'm not sure if there is RUU for your CID. I tried to Google that but I didn't find much. If you've bought your phone from carrier, then there is probably no RUU for your phone. If the CID doesn't match, then RUU won't run at all and it will throw an error. To run RUU you need to have locked bootloader and stock recovery.
Click to expand...
Click to collapse
if i relock the bootloader and flash stock recovery (please give me a link for it)
so can i flash the RUU mensioned erlier?
what if it fails?

Follow this guide to do it. You don't need to root since you have CyanogenMod. The links to XDA threads doesn't work, but all you need is RUU and all in one toolkit for One S which should be in Android Development section on this forum. Also you need to have the unlock token for your device.
If the RUU doesn't work, then you can try another RUU if you find correct one for your device. Some have went as far as changing CID to HTC__001 to run the European RUU, which I linked earlier, but to do it you need to unlock bootloader again.

Problem during back to stock rom S4

Today I tried back from CyanogenMod 12 to stock rom in HTC ONE S.
One S 1.5, TWRP 2.8.5, HBoot 2.15, S-ON. Cid T-MOB101
During this procedure: https://translate.google.pl/translat...OMu&edit-text=
In this 6. point "6. Turn the phone back - no, it's not over yet, but the worst is behind us. We run suitable for our model and already RUU.exe normally carry out the procedure ROM Upgrade Utility - Using the instructions of the installer. ". I used RUU from this link https://drive.google.com/folderview?id=0B1IYElPvrGZrdGR6SXIwYjgxd1U&usp=sharing#list
Installer (RUU) show me error [140]: error bootloader version.
After I close installer phone was reboot and I see only bootloader - On the top I see TAMPERED RELOCKED Security Warning)
I can not run Android now
Could you help me? Please
Update> I unlock it using fastboot flash unlocktoken Unlock_code.bin, but what is next?

noiserobert said:
Today I tried back from CyanogenMod 12 to stock rom in HTC ONE S.
One S 1.5, TWRP 2.8.5, HBoot 2.15, S-ON. Cid T-MOB101
During this procedure: https://translate.google.pl/translat...OMu&edit-text=
In this 6. point "6. Turn the phone back - no, it's not over yet, but the worst is behind us. We run suitable for our model and already RUU.exe normally carry out the procedure ROM Upgrade Utility - Using the instructions of the installer. ". I used RUU from this link https://drive.google.com/folderview?id=0B1IYElPvrGZrdGR6SXIwYjgxd1U&usp=sharing#list
Installer (RUU) show me error [140]: error bootloader version.
After I close installer phone was reboot and I see only bootloader - On the top I see TAMPERED RELOCKED Security Warning)
I can not run Android now
Could you help me? Please
Update> I unlock it using fastboot flash unlocktoken Unlock_code.bin, but what is next?
Click to expand...
Click to collapse
to use a RUU your bootloader need be relocked
---------- Post added at 06:28 PM ---------- Previous post was at 06:26 PM ----------
You can try rumrunner to S-OFF and after that try with Ruu

JavierG123 said:
You can try rumrunner to S-OFF and after that try with Ruu
Click to expand...
Click to collapse
I tried it but it not work. I think because it work only with stock rom
How back t stock rom with s-on?

noiserobert said:
I tried it but it not work. I think because it work only with stock rom
How back t stock rom with s-on?
Click to expand...
Click to collapse
Flash the proper RUU for your CID, you don't need S-Off for that.
Sent from nowhere over the air...

@thanks Rapier
I describe as I did it in detaliled:
1. Run fastboot oem readcid and fastboot getvar version-main and receive inforamtion Cid T-MOB101 3.16.111.11
2. Downlaod proper (??) RUU RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09es.50.02.07_2_10.09d.50.04L_ver2_release_287723_signed.exe . Is it proper for my device One S 1.5, TWRP 2.8.5, HBoot 2.15, S-ON. Cid T-MOB101?
3. Run fastboot oem lock
4. Run fastboot erase cache
5. Run RUU (from 1 point)
6. RUU inform me that will be install oddest (something like 2.38.111.xx - I dont remember all number) version then is on my ONE S (3.16.111.11), I accept it
7. RUU reboots my phone, and HTC starts and on blac background was logo htc
8. After few minutes RUU installer show me error [140]: error bootloader version.
9. I accept RUU and it close and my phone reboot to bootloader On the top I see TAMPERED RELOCKED Security Warning)
Where is wrong ?
Plese help me

I resolve it
1. Install a Viper 2.20
2. Use rumrunner.us to set your phone S-OFF

noiserobert said:
I resolve it
1. Install a Viper 2.20
2. Use rumrunner.us to set your phone S-OFF
Click to expand...
Click to collapse
And the RUU works?

I do not RUU because I did S-Off and it was fantastic
I go to Maximums HD (based on stock rom)

noiserobert said:
I do not RUU because I did S-Off and it was fantastic
I go to Maximums HD (based on stock rom)
Click to expand...
Click to collapse
but... for install Maximums HD you don't need S-OFF....

JavierG123 said:
but... for install Maximums HD you don't need S-OFF....
Click to expand...
Click to collapse
Of course you MUST have S-OFF to install Maxiums HD. Please read about it!

noiserobert said:
Of course you MUST have S-OFF to install Maxiums HD. Please read about it!
Click to expand...
Click to collapse
i'm sorry men. my bad

No problem
Only one problem is that not support beatsaudio

noiserobert said:
No problem
Only one problem is that not support beatsaudio
Click to expand...
Click to collapse
in android development or other section like that here in the forum... exist a flasheable zip to get on any device beats audio and other features...

I am wrong, this rom support BA! It is fantastic!