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

[Q] CID

Hi ,
Wanting to get rid of 3 uk junk and flash to normal UK RUU
Do we need super CID?
My bootloader is unlocked , can't download the RUU from from the Dev section as all the slots are gone , or when it seems to work it errors out .
Has anyone got the latest UK RUU file they can share with me and can someone confirm if I need Super CID to run RUU to unbrand
Thanks in Advance

Just flash Modaco or the Virtuous roms through recovery, these are unbranded and really good.
You will need to flash a Recovery image first though.

Hi and thanks
Yes , I understand this but I want to just unbrand through RUU then re-lock my bootloader.
Do we need Super CID ?

Ok can someone remind me if I need S-Off to change the CID , playing around with ADB at the moment

If Im honest mate, no idea what you mean by CID...
But if you want a new rom, all that needs to be done is unlock bootloader, flash recovery, flash rom.
Thats all anyone has done in the dev threads, and worked fine for me (coming from a retail, unbranded unit).
You can 'lock' the bootloader again, BUT it never goes back to its true original state. This is as HTC designed their unlocking/locking process to be (and is stated in their terms when you go to their site to unlock).
Edit: OK, just read up on it. Possibly then! Depends how annoying 3 are I suppose... Probably best to ask one of the devs
Edit 2: CHeck the following, may be of help (though its for the One X)
http://forum.xda-developers.com/showthread.php?t=1594262
http://android.modaco.com/topic/353106-debrand-one-x/
Edit 3: If you're applying a flashable zip, does the CID limitiation on RUUs even come into play?

Hi thanks ,
Yea what I want to achieve is this .
My CID is HG3____001 this will need to be changed to a CID that is HTC UK specific usually HTC_____001
To find out your CID in ADB
Fastboot Getvar CID
To get to a retail version from a branded version , what usually needed to happen was this .
Unlock bootloader , change CID to 11111111 via ADB
Run the specific UK RUU.exe
Change your CID to the HTC_____001 which is the usual default for UK unbranded devices .
re-lock your bootloader and then you should receive OTA updates from HTC instead of your network supplier which can take months
I can't remember if S-off was needed to do this. I have just checked revolution site and One s is not listed , will play around tonight though and see
Thanks for the help so far

Hi, I know what CID is - coming from the Sensation.
I dont think its possible to change CID without S-OFF, you cant use advanced ADB functions with S-ON
Until revolutionary or someone else makes tool for S-OFF, we will just have to stick with HTCDev, Its not the best, but it allows to flash recovery and ROMs so its better than nothing.
Im pretty sure there will be some progress in the next few weeks, Once the phone is available worldwide

Ahh ok , thanks , yea this phone is set S- on , so S-off will be needed sooner or later

yeah, as development develops and more rights are needed from the phone, S-0FF will eventually be a MUST.
I wish it was available already, I hate the fact that HTC know i have tampered with my HBOOT and voided my warranty.
Luckily enough, if i have a problem, my provider fixes / repairs the phone, Not HTC, So i might just get off lightly

I think HTC will know if you have tampered with the phone period if they wish to look that far into it .
Unless you fry your processor where you have set it too high etc then shouldn't be a problem. If you have a hardware problem such as your screen fails , battery etc then should be fine .
As you say though , if you brought it through a retail unit then that is where it is returned so in some respects is a bit easier as they will use a third party repairer acting for HTC .

well with the sensation it was possible to return everything back to stock, Including the bootloader and S-ON..
There was no way it could be diagnosed as being tampered with, If you did it properly..
But with HTCDev. youve already submitted a code (which i assume contains serial number) so all they have to do is check whether that device matches anything on their database of tampered devices. Thats why i dislike it so much..
But i need root for most of my apps so there was no workaround for me...

I see on the One X forum S-off is under way . Can't wait to get this baby to true stock.
Just did another Google search for S-Off on the S but nothing as yet .

***LOCKED***Security Warning on bootloader

Hi all,
I have tired to flash the new Rom yesterday and during checking the signature device reboot and installer said that it can not proceed.
After reboot phone goes directly into fastboot and gives ***Locked*** with Security Warning massage. I have tried different RUU but it is exactly the same.
Installation is failing on the checking signature.
I have tried Unrevoked3 but it is not able to find the device. Could you please let me know how to do it?
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-2822.10.0804_M
eMMC-boot
I was trying to upload RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_234765_signed

http://forum.xda-developers.com/search.php?searchid=23896455
Error nr 141?
LE: hope it works now, if not search the forum, the link reffers to the search results.
You will certainly get the answer there.

Link does not work:
Sorry - no matches. Please try some different terms.

I have tried to find an answer but no luck so far, I am quite new to this. Is there anyone who can point me in the right direction?

Another solution is to try the RUU 2.10.401.8
I had some problems with the same Ruu, but not with the signature, and the previous version worked flawlesly.
What's your CID?
Sent from my HTC Desire S

I have tried few others RUU and every single of them is falling during the installation.

ok I manage to unlock the device finally
But again it is falling during the installation of a new ROM. Do I have to revert back Hboot to 0.98 before installation? if so how to do it?

So the RUU that I recommended completed successfully?
What do you want to do next?
Now you are S-ON, if you want to install custom roms you have to unlock your bootloader with the htcdev method(you will lose your warranty and need to flag manually the boot file) or to downgrade.
Sent from my Samsung Galaxy Tab

I want to downgrade the phone to orginal ROM T-mobile uk. So I could take off the simlock, I have put the unlocking code yesterday but nothing happens. I was advised to downgrade the rom and should be ok.

Could some help me out with my problem please when ever I am trying to upload new rom it is stuck on signature verification.

I will quote Enigmaamit as he said it better than me:
enigmaamit said:
SIM unlock and bootloader unlock are two completely different things.
Click to expand...
Click to collapse
The only way to SIM-unlock your phone yourself is a XTC clip... better ask your phone operator.

I know the diffrance between those two, I have ordered unlocking code. After putting this into device when ever I put into new sim card it stoped nofifing me about it. But it is not able to find a new network. Below what I have receive form operator:
"It said "Successful" but nothing has happened
Darren
posted this on Apr 11 16:22
This has happened to a handful of customers who have all had one thing in common - the phones have been "rooted".
By rooting a handset the owner has removed some of the restrictions on the phone, which allows the owner to install whichever software of the phone that they wish. Unfortunately this has caused some issues when an unlock code has been entered.
It is easily rectified by reinstalling the original operating system that the phone was supplied with, then applying the unlock code and the phone should be unlocked, truly, successfully.
You can then reinstall the software you had on the phone before attempting the unlock and continue using the phone as you wish."
So that is the reason why I am trying to revert any changes.

i for one don't believe this

So their replay is bull**** in that case?

In my opinion yes(i can't say that i am a very experienced user) but i like to think i know some stuff about this.
I can't imagine what custom rom/Ruu version/app will "block" you to sim unlock your phone.
The only restrictions may be made by the phone manufacturer.

So i will try through HTC Clip in that case. But why I can upload any new RUU?

like i said earlier, i had some problems to with the 2.10.401.9 ruu.
Try the 2.10.401.8 it should work, if your phone is branded try a gold card.

[Q] HELP - getting back to stock for warranty purposes

Hi everyone,
Few weeks ago my device started to overheat quite a lot when being used (I dont play 3d games, well I dont play games at all on this device), for browsing the internet on wifi or 3g network, it gets hot in the bottom part of the screen above the touch buttons. I tried buying a new battery, I bought a original HTC, but a bigger one for Evo 3D, but it is still getting hot, and I dont know whether it is a hardware issue or a software caused. Do you have any ideas what could be wrong? ...my sensation is rooted, bootloader unlocked via HTCDev, S-OFF..and I still might try to use my warranty to get it repaired but I dont want to take the chance that I would be told that the device had been unlocked and rooted and thus not being repaired...I read that it ist possible to get device back to S-ON and LOCKED, not RELOCKED, so that the repair center wont find out that it was unlocked and rooted before...but I could not find a tutorial and I also do want to brick my device so I am asking for some help how to get the device back to STOCK rom with S-ON and LOCKED status...
my bootloader says this:
-Firmware-3.33-
Pyramid PVT SHIP S-OFF RL
HBOOT 1.27.1100
RADIO-11.24A.3504.31_M
OpenDSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13....
Can you help me with some steps what to do or just point me to some tutorial? I would be really gratefull for any advice.

arriva13sk said:
Hi everyone,
Few weeks ago my device started to overheat quite a lot when being used (I dont play 3d games, well I dont play games at all on this device), for browsing the internet on wifi or 3g network, it gets hot in the bottom part of the screen above the touch buttons. I tried buying a new battery, I bought a original HTC, but a bigger one for Evo 3D, but it is still getting hot, and I dont know whether it is a hardware issue or a software caused. Do you have any ideas what could be wrong? ...my sensation is rooted, bootloader unlocked via HTCDev, S-OFF..and I still might try to use my warranty to get it repaired but I dont want to take the chance that I would be told that the device had been unlocked and rooted and thus not being repaired...I read that it ist possible to get device back to S-ON and LOCKED, not RELOCKED, so that the repair center wont find out that it was unlocked and rooted before...but I could not find a tutorial and I also do want to brick my device so I am asking for some help how to get the device back to STOCK rom with S-ON and LOCKED status...
my bootloader says this:
-Firmware-3.33-
Pyramid PVT SHIP S-OFF RL
HBOOT 1.27.1100
RADIO-11.24A.3504.31_M
OpenDSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13....
Can you help me with some steps what to do or just point me to some tutorial? I would be really gratefull for any advice.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1672425 There is pretty much everything covered about RUUs.
And gaining the ''***Locked***'' status for bootloader is impossible. It will say ''***RELOCKED***''

Nicx59 said:
http://forum.xda-developers.com/showthread.php?t=1672425 There is pretty much everything covered about RUUs.
And gaining the ''***Locked***'' status for bootloader is impossible. It will say ''***RELOCKED***''
Click to expand...
Click to collapse
is it impossible? cos I read it somewhere that it is possible with some ADB action...unfortuntelly did not save the link...

arriva13sk said:
is it impossible? cos I read it somewhere that it is possible with some ADB action...unfortuntelly did not save the link...
Click to expand...
Click to collapse
it is possible since you are on S-OFF
but i don't remember the link
you can use also the flashable zip(only from bootloader can be flashed)except of adb command

arriva13sk said:
is it impossible? cos I read it somewhere that it is possible with some ADB action...unfortuntelly did not save the link...
Click to expand...
Click to collapse
Okay, maybe it goes to ''Locked'' state itself once you go to S-ON/Flash a RUU
http://forum.xda-developers.com/showthread.php?t=1731666 (Read ganehs's last post)
I just read that, but I am not 100% sure of anything. I haven't done it.

thank you guys for your help! :good:

Sim unlock with Hboot 1.29

Hello guys,
I think my sensation xe is simlocked to T-Mobile. I have bought it off ebay and had returned it to the seller for repairing the camera. The seller has apparently fixed the issue but when i insert my sim card it does not connect to network and gives error 'your sim card does not allow connection to this network'. I have tried the settings inside phone information(*#*#4636#*#*) and also the sim unlock guide method 1 and 2. But it still does not connect. I think that the sim unlock method failed due to Hboot v 1.29. My device info is as follows
PYRAMID PVT SHIP S-OFF RL
Hboot-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Is there any was to unlock this phone? Any help would be awesome...
Thanks!

ushmal said:
Hello guys,
I think my sensation xe is simlocked to T-Mobile. I have bought it off ebay and had returned it to the seller for repairing the camera. The seller has apparently fixed the issue but when i insert my sim card it does not connect to network and gives error 'your sim card does not allow connection to this network'. I have tried the settings inside phone information(*#*#4636#*#*) and also the sim unlock guide method 1 and 2. But it still does not connect. I think that the sim unlock method failed due to Hboot v 1.29. My device info is as follows
PYRAMID PVT SHIP S-OFF RL
Hboot-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Is there any was to unlock this phone? Any help would be awesome...
Thanks!
Click to expand...
Click to collapse
Does your phone ask for pin? Usually phones with sim lock don't do that and you'll get the warning that the sim card can't be used.
Maybe try to manually select the network in settings.

No good...
Sajito said:
Does your phone ask for pin? Usually phones with sim lock don't do that and you'll get the warning that the sim card can't be used.
Maybe try to manually select the network in settings.
Click to expand...
Click to collapse
Nope...no pin request...
I even tried this guys thread...http://forum.xda-developers.com/showthread.php?t=2597778&page=2... My mobile also shows TMOB010 below the IMEI during the unlock method...but even after downgrading the firmware and erasing S58 data...upgrading to 3.33 and flashing a new rom, the phone still does not connect... and by the way, TMOB010 is still there...

ushmal said:
Nope...no pin request...
I even tried this guys thread...http://forum.xda-developers.com/showthread.php?t=2597778&page=2... My mobile also shows TMOB010 below the IMEI during the unlock method...but even after downgrading the firmware and erasing S58 data...upgrading to 3.33 and flashing a new rom, the phone still does not connect... and by the way, TMOB010 is still there...
Click to expand...
Click to collapse
Then I'm sorry, I have no clue...

One guy had the same problem and as far as I know he fixed it with hboot downgrade, PB file again, then hboot upgrade and stock ARHD (not TMOB).
Search a bit, it wasn't long time ago.
EDIT:
Take a look here:
http://forum.xda-developers.com/showpost.php?p=27813767&postcount=531
and here:
http://forum.xda-developers.com/showthread.php?t=2597778&page=2

nlooooo said:
One guy had the same problem and as far as I know he fixed it with hboot downgrade, PB file again, then hboot upgrade and stock ARHD (not TMOB).
Search a bit, it wasn't long time ago.
Sent from my HTC Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
Thanks, i will search a bit more, but when i downgraded the firmware to 1.17, my HBOOT will also be downgraded right.. so i already did the method you are suggesting...anyways i will look a bit more... i need all the help i can get...
thanks again for replying!

ushmal said:
Thanks, i will search a bit more, but when i downgraded the firmware to 1.17, my HBOOT will also be downgraded right.. so i already did the method you are suggesting...anyways i will look a bit more... i need all the help i can get...
thanks again for replying!
Click to expand...
Click to collapse
Try with the links I gave you, especially the second one cause that's the guy that had the same issue and solved it.

Also i had another thought... what if there is something else wrong with the phone? What if its not locked but has some other problem? This is because i have tried almost every method i could find out there. So can anybody tell me how to check if your phone is really simlocked??

nlooooo said:
One guy had the same problem and as far as I know he fixed it with hboot downgrade, PB file again, then hboot upgrade and stock ARHD (not TMOB).
Search a bit, it wasn't long time ago.
EDIT:
Take a look here:
http://forum.xda-developers.com/showpost.php?p=27813767&postcount=531
and here:
http://forum.xda-developers.com/showthread.php?t=2597778&page=2
Click to expand...
Click to collapse
I have tried methods suggested in both of these thread my friend and sadly it does not work...both go pretty much the same way....

ushmal said:
I have tried methods suggested in both of these thread my friend and sadly it does not work...both go pretty much the same way....
Click to expand...
Click to collapse
Tried to supercid before everything?

nlooooo said:
Tried to supercid before everything?
Click to expand...
Click to collapse
Ohh i forgot to mention before...the cid was already 111111 when it was delivered... so no need to supercid...
Anyways i plan to do the process all over again one more time...just to be double sure that i didnt miss anything..its getting late so maybe i will have to do it tomorrow...will report if anything good comes out of it...fingers crossed...
In the meantime if anybody has a suggestion please do share...
Thanks guys for all the support...