Database Info

[SOLVED] which ruu do i need for s-on

hey folks. i hope some1 can point me in the correct direction.
(yea 1st post _yay_ lame indeed to start with a question at all, but im following xda for quite a while.. :-| )
i want to send in my phone to warranty because i got the dust under screen problem.
i have a vodafone DE branded sensation with software version 1.35.162.1...
now, according to the guide [Guide] to Installing S-off, ClockWork, Root, SuperCID & S-on [03/AUG/11](noobproof) i want to follow the steps to gain s-on again and removin CWM.
my problem is i cant find any RUU higher than/or equal to x.35.xxx.x since downgrading doesnt work and i only have this RUU RUU_Pyramid_Vodafone_DE_1.27.162.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_191975_signed.
i am on stock rom now, unrooted. i came from CM7 a10.
question is which ruu can i take now and could i use a htc europe ruu by changing the cid?
thanks in advance

ok didnt look for any search terms related to the word "downgrade"...
i found a link for Eng-Hboot where i can downgrade to HBOOT Version 1.17.2008
after that i shud be able to flash lower ruu versions...

My answer maybe is a litte OT but...
Do You think they will be check which exactly ROM you should have? Also read for terms of warranty, there is nothing about loosing warranty after changing software

*** LOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
SoftwareVersion 1.45.162.2
seems like i solved it on my own!
thread can be closed, deleted, whatsoever... sry for spam

Artur_q77 said:
My answer maybe is a litte OT but...
Do You think they will be check which exactly ROM you should have? Also read for terms of warranty, there is nothing about loosing warranty after changing software
Click to expand...
Click to collapse
yea but having CM running its obvious i unlocked it. and i wanted to remove any doubts that i did something like that. i dont have the money to buy something new

Put europe stock rom

Hello everybody, i've a big question for you I got an HTC One S with cid TIM__041, still locked. The installed ROM is the stock customized by my operator TIM, that's crappy without any updates, and i want to put the europe stock rom changing the cid to HTC__001 if it's needed. But i don't want to void my warranty. The device is OK, it has no problems.
How can I resolve this? Sorry for my bad english, but i'm an young italian
If you need bootloader information, here is it:
*** LOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-0.16.31501S.17_2
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 20 2012,15:14:18
Click to expand...
Click to collapse

no one?

Sevenarth said:
no one?
Click to expand...
Click to collapse
That was only 2½ hours later, in which the USA is mostly asleep. Patience young grasshopper ..ehmm.. I mean Italian.
EDIT: I missed the AM/PM. It was 14.5 hrs like frdd correctly corrected in the post below this one. Sorry for that.
I'm not 200% sure but I don't think you can change your CID without unlocking your bootloader. Unlocking your bootloader will not completely void your warranty. It will still cover unrelated defects. Also, you can always re-lock and go back to stock afterwards, but only if you have a RUU for your phone that accepts your new HBOOT (that comes with the EU RUU).
If the 'problem' is that you want to tinker with your device but not take responsibility, then there is no solution.
-Jobo

Try 14.5 hours but yeah jobo is correct you need htcdev unlock to root and change cid

So, if I unlock the bootloader, the warranty for hardware problems will not voided? I need only to get the european stock rom, what's the best way to get it? However, i don't think putting european stock rom will void the warranty :/
Thanks for answering my topic But when I maked the topic, in USA was day. xD

Me too, though I am on T-MOB005 CID. And I don't want to exactly root my phone. So until we get S-OFF, there is no way. Just have to wait and be patient, like me. (I'm still on 1.77 and 2.21 has already been released)

usaff22 said:
Me too, though I am on T-MOB005 CID. And I don't want to exactly root my phone. So until we get S-OFF, there is no way. Just have to wait and be patient, like me. (I'm still on 1.77 and 2.21 has already been released)
Click to expand...
Click to collapse
me too, i'm at 1.78, and i still didn't get 2.21 update i need it for wifi problems.

So, are there no other way?

You can try to just run the 2.21.401 RUU but probably won't work.
Or you can wait for TIM to release the OTA if you're only after the new radio, your branding will still be there.
You need root to change cid, and you need htcdev unlock to root. No other way yet.

Hm..are there some news about s-off?

s
I hope it's ok to post other sites like but there is a nice tutorial here that have links to xda forum!
hwupgrade.i t/forum/showpost.php?p=37896138&postcount=320

Sevenarth said:
me too, i'm at 1.78, and i still didn't get 2.21 update i need it for wifi problems.
Click to expand...
Click to collapse
I need it to fix camera focus issues. The camera won't focus on something close-up.

usaff22 said:
I need it to fix camera focus issues. The camera won't focus on something close-up.
Click to expand...
Click to collapse
Same here!! Can you please help me here? http://forum.xda-developers.com/showthread.php?t=1813535

I decided, and now I got 2.21.401.10 :laugh:
I follow this steps: (thanks addsfsds)
1. Unlock, install recovery mod, root --> HOW-TO
2. Changed CID to generic (HTC__001) --> HOW-TO
3. Relocked bootloader (It's important!) --> Command: "fastboot oem lock"
4. Installed 2.21 HTC Europe RUU (includes stock recovery + stock rom) --> DOWNLOAD
5. I'm free!

You guys are saying you don't want to change your CID until S-Off is out because you don't want to unlock bootloader... Even if S-Off is out, you still have to unlock your bootloader to change CID *facepalm*

So I needed the best choice, because I need europe stock rom now.

ShensMobile said:
You guys are saying you don't want to change your CID until S-Off is out because you don't want to unlock bootloader... Even if S-Off is out, you still have to unlock your bootloader to change CID *facepalm*
Click to expand...
Click to collapse
Don't facepalm without knowing. We don't want to unlock the bootloader now because once we get S-OFF, we can S-ON back again with no traces of being S-OFF'ed. However, with HTCDev, it says ***RELOCKED*** which is a clear indication that the device has had its bootloader unlocked before. Some of use don't like to void our warranties, which is why we're waiting for S-OFF.

[Q] [Solved] 2.20 RUU Question

Hello all. Quick question about running the 2.20 RUU -- I seem to recall, around the time that the 3.14 OTA update came out for the AT&T Version of the One XL a lot of folks were hard-bricking their phones that were previously rooted on a separate JB ROMs..perhaps something with the Super CID? I did not investigate this much because I wasn't ever interested in taking the 3.14 OTA but my question is: Can I safely run the 2.20 RUU on hboot 1.14 S-OFF; I am currently running a JB ROM right now. Sorry for the question but I can't seem to find the threads that explained why users were getting hard bricks from the OTA -- I'm about to wipe my phone and give it to someone else and I would hate to hard-brick it and the phone be no longer usable

TheEmpyre said:
Hello all. Quick question about running the 2.20 RUU -- I seem to recall, around the time that the 3.14 OTA update came out for the AT&T Version of the One XL a lot of folks were hard-bricking their phones that were previously rooted on a separate JB ROMs. I did not investigate this much because I wasn't ever interested in taking the 3.14 OTA but my question is: Can I safely run the 2.20 RUU on hboot 1.14 S-OFF; I am currently running a JB ROM right now. Sorry for the question but I can't seem to find the threads that explained why users were getting hard bricks from the OTA -- I'm about to wipe my phone and give it to someone else and I would hate to hard-brick it and the phone be no longer usable
Click to expand...
Click to collapse
The issue pertained to those with Super CID and S-ON.
Since you're S-OFF, it's safe to run the RUU. no need to relock the bootloader or change your CID.

exad said:
The issue pertained to those with Super CID and S-ON.
Since you're S-OFF, it's safe to run the RUU. no need to relock the bootloader or change your CID.
Click to expand...
Click to collapse
Thanks for the reply. Wow thats great, I remember last time I RUU I had to fastboot oem lock and then run it and flash the unlock token again which was pain in the a$$.
Thanks again for the clarification -- added [Solved]

exad said:
The issue pertained to those with Super CID and S-ON.
Since you're S-OFF, it's safe to run the RUU. no need to relock the bootloader or change your CID.
Click to expand...
Click to collapse
Just to clarify --- can I also run the 3.14 OTA if I am S-OFF without Brick?

TheEmpyre said:
Just to clarify --- can I also run the 3.14 OTA if I am S-OFF without Brick?
Click to expand...
Click to collapse
That's right.

Unfortunately for me, I was s-on and supercid when I took the OTA. Hard bricked my phone and I had to have it replaced lol.

marcur12 said:
Unfortunately for me, I was s-on and supercid when I took the OTA. Hard bricked my phone and I had to have it replaced lol.
Click to expand...
Click to collapse
Yeah I just vaguely remember seeing some unfortunate threads after the OTA came out and so I just thought I would check. Bummer about your device sorry
Sent from my HTC One using Tapatalk 2

TheEmpyre said:
Yeah I just vaguely remember seeing some unfortunate threads after the OTA came out and so I just thought I would check. Bummer about your device sorry
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Fun fact: Running the 2.20 RUU down from a 3.17 based ROM removes the "TAMPERED" tag from the bootloader. At least on hboot 1.14 and S-OFF

TheEmpyre said:
Fun fact: Running the 2.20 RUU down from a 3.17 based ROM removes the "TAMPERED" tag from the bootloader. At least on hboot 1.14 and S-OFF
Click to expand...
Click to collapse
Running any RUU should remove that Tampered text which is documented in the modding your bootloader screen thread.

[Q] help please

hey everyone, i had my telstra one xl on JB for awhile then i wanted to do the newest update from them so upon reading up on it i need to have supercid and s-off, so i thought no worries i'll check my cid first which was telst001 (or something like that), found a one click script and changed to the supercid, so it was 11111111, sweet now to do s-off which failed to flash the RUU, i needed to relock the bootloader, so i relocked it.
problem is now its stuck in a bootloop to fastboot and wont show up in ADB devices, i also cant get into twrp in recovery now.
is there any way to fix this or throw the phone out?

It's a bit difficult to make out what you're saying in parts of that post.
Was s-off successful?
Was the RUU successful?
Which RUU did you use?
What are your current bootloader details?
Sent from my Evita

sirus17 said:
so i thought no worries i'll check my cid first which was telst001 (or something like that), found a one click script and changed to the supercid, so it was 11111111,
Click to expand...
Click to collapse
Did you actually verify that you had SuperCID? I don't think there is a one-click for the Telstra version. The one-click app for SuperCID I'm aware of is intended for AT&T, and will fail with any other CID.
Which may actually be a good thing (if SuperCID failed). Since if a Jellybean RUU is flashed with SuperCID and s-on (its not clear whether you were successful with s-off) it will pretty much a guaranteed brick.
sirus17 said:
is there any way to fix this or throw the phone out?
Click to expand...
Click to collapse
If the screen comes on, its probably possible to recover. But we need more info as timmaaa indicated above.

There is actually a one-click tool for the Telstra version, I stumbled across it very soon after getting my phone mid last year. I found it on an Australian Android site, I think it was Ausdroid.
I'm not sure whether the tool is specifically for the Telstra version alone, but it definitely works on Telstra Evitas as I used it on my fiance's Evita (and mine which is a Hong Kong model).
Sent from my Evita

I thought the one click tool here supported AT&T, Rogers and Telstra CID changing.

twistedddx said:
I thought the one click tool here supported AT&T, Rogers and Telstra CID changing.
Click to expand...
Click to collapse
Really not sure, now that I look into it more. If its the old one by DesignGears, it does work with Rogers, but doesn't seem to mention Telstra (at least if I just search the thread for "Telstra"): http://forum.xda-developers.com/showthread.php?t=1672284
And x-factor also fails for any CID except AT&T, if I understand correctly. So it seems these scripts all look for certain CIDs, so if its not explicitly included, they will fail. Of course, if there is one made specifically for Telstra (as timmaaa mentioned) it apparently wasn't posted on XDA.
But really my main point is that the OP needs to verify and be clear on this, as well as several other factors.

[Q] s-off / supercid

so i managed to solve my recovery problem. i finally got twrp 2712 onto my device.
bootloader is unlocked
recovery on
superuser on..
hboot 2.15 s-on
i dont remember dealing with supercid when i rooted my old htc incredible.. from what im reading it allows us to use other carrier roms on the device?? im on tmobile and comfortable with that.. is modifying the CID actually necessary? im not planning on receiving any ota's n such.. just want the ability to flash radio's if need be and roms.. If i can skip CId and go to s-off that'd be fine with me, unless its needed for something else.. Will Ibe able to s-off without CID modified? cracking this ****er has been a little bit more difficult the past few phones ive had to do.. thanks much for the help..

As a noob, I installed CM 11 in February without s-off or super-cid (was too afraid to brick my phone). CM works great without s-off, but you need to flash boot.IMG on every update via fastboot.
I did s-off with rumrunner recently without Super-CID. Read my post here: http://forum.xda-developers.com/showthread.php?p=56185478<br/>

so in moonshine i was getting nowhere.. i had no inclination that the Yes/No were case sensitive to be executed....
Currently in test 3, mhy 7th row of **********..