Database Info

How to debrand after S-OFF

Now that we have S-OFF how can we debrand our phones? Is it enough to flash the unbranded RUU? Or do we have to do it through recovery?

I would like to know this too, would like to remove the branding from my Sensation as well.

Download a custom rom.Any chance either of you can perform a backup in recovery and upload the recovery.img please

same querry i m on s off
i installed super cid on tried to flash asia_wwe {381 mb} on mt tmobile sensation, it gave me error 130 (ruu not specific for device).

http://forum.xda-developers.com/showthread.php?t=1192300
follow the guide the flash any rom for the "unlocked" international version of the Sensation.

tsekh501 said:
http://forum.xda-developers.com/showthread.php?t=1192300
follow the guide the flash any rom for the "unlocked" international version of the Sensation.
Click to expand...
Click to collapse
How is that supposed to help in debranding the phone??

ok
I installed leedroid, based on europe unbranded rom on my tmobile. i knew it before hand that would not debrand my phone, even then i did it.
i then tried to install ruu for the same version. got smae error 130 (not specific for device).
I noticed that installing leedroid did not update my baseband.(radio)
Maybe i'll try installing radio and see if it works.
Guys if anyone has any idea kindly help! we dont wana pay $30 for getting an ulock code, if it can be done on our own
S-off done
Clockworkmod
Perm Root
SuperCID installed
Update: Changed baseband as well did not work

Ok
I think the SuperCID posted in the DEV section is not working.
Because in the HTC desire Z section here, there is a post on how to debrand the phone.
and its pretty simple:
1-S off
2-CID Off
Flash any unbranded RUU from PC and good to go!
I have SuperCID installed but when i Flash RUU it give error 130 (Incoorect RUU for the Device).
So i guess SUper CID is not doing what its supposed to do

Here you go guys, I wrote up a guide in the dev section:
http://forum.xda-developers.com/showthread.php?t=1193033

Thanks alexp999. Is there any difference with the SuperCID method? Is having ENG H-BOOT better? Noob questions, I know....

Fritti said:
Thanks alexp999. Is there any difference with the SuperCID method? Is having ENG H-BOOT better? Noob questions, I know....
Click to expand...
Click to collapse
I prefer not changing cid, then I don't have to keep backup for warranty purposes. My method also doesn't require root.
Eng hboot is only temporary as it gets overwritten with shipped hboot when you flash the ROM from the ruu. Eng is only used to bypass cid check.

[Q] Desire S Need to get back to stock on 3 UK

Hi everyone,
The microphone on my beloved Desire S has packed in and I need to return in for warranty repair.
It is currently rooted running Virtuous Unity. I don't think I should send it back with a custom ROM on it.
I would like to get it back to factory state before I send it, including HBOOT and recovery, but I can't find an RUU for 3UK.
Does anyone have any ideas how I can go about this?

iTroll said:
Hi everyone,
The microphone on my beloved Desire S has packed in and I need to return in for warranty repair.
It is currently rooted running Virtuous Unity. I don't think I should send it back with a custom ROM on it.
I would like to get it back to factory state before I send it, including HBOOT and recovery, but I can't find an RUU for 3UK.
Does anyone have any ideas how I can go about this?
Click to expand...
Click to collapse
Daft question, but, did you perform a full nandroid backup before you flashed you first custom which you still have on SD?

If not see post #1 of this thread All shipped ROMs
I believe that this RUU might suit...
RUU_Saga_H3G_UK_1.31.771.1_Radio_20.28b.30.0805U_3 8.03.02.14_M_release
further threads explaining how to
[Tutorial] How to restore stock ROM and S-On after AlphaRevX S-Off [31 july 11]
http://forum.xda-developers.com/showthread.php?t=1187231
along with many other useful info in the INDEX sticky thread within the development forum.

ben_pyett said:
If not see post #1 of this thread All shipped ROMs
I believe that this RUU might suit...
RUU_Saga_H3G_UK_1.31.771.1_Radio_20.28b.30.0805U_3 8.03.02.14_M_release
Click to expand...
Click to collapse
and if yes? how is the backup helping?

Nomader0 said:
and if yes? how is the backup helping?
Click to expand...
Click to collapse
Backup is helping in a couple of ways:
As it will be the actual stock version of ROM that he was supplied with it will enable him to confirm exactly which version of ROM that he'll need to return to etc.
Also, depending on how 'eagle eyed' the person in the repair centre is he may only need to return recovery and hboot back to original and simply remove the superuser application from it rather than re-flash RUU.

That's really great info guys!
So from reading the tutorial it looks like HBOOT is not replaced by the RUU and has to be restored manually with adb, is that right?
Thanks a lot!

iTroll said:
That's really great info guys!
So from reading the tutorial it looks like HBOOT is not replaced by the RUU and has to be restored manually with adb, is that right?
Thanks a lot!
Click to expand...
Click to collapse
I'm not 100% about this....But, I believe that some RUUs do replace the HBOOT, but, they're only ever able to upgrade the HBOOT version, so if you need to downgrade the hboot version, which you may need to do if you're software S-OFF'd. Then adb can be used to downgrade the HBOOT version as you've seen.
Which HBOOT version do you have?

ben_pyett said:
I'm not 100% about this....But, I believe that some RUUs do replace the HBOOT, but, they're only ever able to upgrade the HBOOT version, so if you need to downgrade the hboot version, which you may need to do if you're software S-OFF'd. Then adb can be used to downgrade the HBOOT version as you've seen.
Which HBOOT version do you have?
Click to expand...
Click to collapse
HBOOT-6.98.1002 (from AlphaRevX)
RADIO-38.03.02.14_M
The HBOOT linked in the tutorial above is 0.98.0000 right?
Will that work on mine?

iTroll said:
HBOOT-6.98.1002 (from AlphaRevX)
RADIO-38.03.02.14_M
The HBOOT linked in the tutorial above is 0.98.0000 right?
Will that work on mine?
Click to expand...
Click to collapse
Yes, that's correct version, follow as the tutorial says.....

Returning to Stock few questions.

So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2.
If you have S Off, this doesn't matter, but you should always try to flash the oldest RUU, so that it is easier to S Off later, unless you don't intend to perform S Off again.
Click to expand...
Click to collapse
I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get
error: -5001. Please make sure you have finished any previous setup and closed other applications.
Click to expand...
Click to collapse
Is the problem with compatibility or something else?

Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?

SsBloodY said:
So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2. I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get Is the problem with compatibility or something else?
Click to expand...
Click to collapse
SsBloodY said:
Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?
Click to expand...
Click to collapse
1. RUU naming convention
RUU_Pyramid_<an extra LE in the name if XE>_HTC_<country/cariier>_<rom main version>_Radio_<radio version>_release_<release version>_signed.exe
dont bother about release version ..we dont need that
the only concerns are ..
country/carrier -> which determines the cid
rom main version ->explains whether youy are on GB or ICS (lesser the version ..older it is ...only between same country/carrier RUU's)
radio version -> tells the radio
2.oldest RUU ..ive explained earlier ..the main version should be least ..but this comparison is only valid if the country/carrier matches
eg:
in case of
RUU_pyramid_tmous_1.52.xx
and
RUU_pyramid_europe_1.27.xx (you cant say which one is oldest)
3.no firmware questions when we are talking about RUU (firmware arises when you talk about custom roms)
RUU has everything ...it wipes everything and converts it to stock (RUU cant touch the SOFF and CID though ..they can be changed only manually ..i.e. by we doing it manually by commands)
4.which RUU ..is you decide by CID ...
if you are supercid ..and dont know the original cid
you need to select the RUU based on your country and carrier
there is an excellent guide on RUU and it explains everything
here is the link to it ...do read it
(it helps you in finding right RUU too )
RUU RELEATED INFO AND FLASHING GUIDE
also remember by flashing RUU ..you wont lose SOFF ...unless you change it manually ..to know how to change it please refer the above guide
also i believe this answer ..answers your second post questions too

Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app

SsBloodY said:
Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
im confused
did you mean you solved it ? or are you asking me how to bypass that error ?
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe

I can't solve the problem. I connect it in bootloader/fastboot and try to run the RUU.exe. And I did revolutionary S-OFF.

Hey no idea that
error: -5001. Please make sure you have finished any previous setup and closed other applications.
is pretty annoying.

What is the CID currently on the phone ?
The RUU with xxx.401.xxxx IRC will require SuperCID (11111111) or a CID of HTC__001.
1.27... will end up installing HBOOT 1.17.0008 (just gone through the process on my replacement replacement phone.
As mentioned earlier you'll keep S-OFF and your existing CID after installing the RUU.
As far as the comms are concerned have you got the latest HTC drivers on the PC ?
---------------snip-------------
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe
---------------snip-------------
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.

I am super CID.

gol_n_dal said:
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.
Click to expand...
Click to collapse
regarding RUU running normally ..you should have usb debugging enabled ..and need to have proper drivers too to recognize the device ..
running from fastboot no hassle there.. (most 155 errors can be prevented from running from fastboot)
couple of people were thrown error 99 when they ran RUU with unlocked bootloader ..so relock is a safer bet to prevent that error too

RUU or a backup TMOB-101

Hi, I really f up.
I can't install roms, and I got TMOB-101.
I tried recently flash a new rom. and didn't backed it up.
please someone send me TMOB-101 backup ot RUU.
HELP!

if you've unlocked your hboot, you need to relock it and then you can install a RUU.
http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
Good luck

No ruu for me there
Sent from my HTC One S using Tapatalk 2

Do you have the TMo USA?

No. I've got t-mob101 (t-mobile Germany)
Sent from my HTC One S using Tapatalk 2

try this:
http://androidfiles.org/ruu/?dir=Ville

Tried this already...
No ruu
Sent from my HTC One S using Tapatalk 2

RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
Really not?

It's a early ruu. I need the 3.16 one
Sent from my HTC One S using Tapatalk 2

lol. There isn't one from TMOB_101 and I really doubt that there ever will be one...
If you want to stick to your CID you should flash this one above and check the OTA updates. Things can be soooo easy...
If you want to go for JB you'll have to change CID to HTC__001 and flash the appropriate RUU. 3.16 will come in by OTA update.

Isn't it will brick my device? (flashing a earlier version then I got)
Sent from my HTC One S using Tapatalk 2

No, it will simply not flash (= exit with an error).
Each RUU/OTA update comes with a certain new bootloader version. Dependant on this version you can upgrade to the next higher hboot but usually not downgrade to a lower hboot. E.g. if youre on 2.15 JB you can't downgrade to 1.14 ICS by RUU anymore. But you are still able to flash custom roms based on whatever android version. The only thing here is with bootloaders > 1.09 the kernel needs to be flashed separately in fastboot mode.
That's where s-off / downgrading bootloader comes into game. As downgrading bootloader is a pain, s-off would be the way to go. For warranty purposes you will be able to restore a stock phone (locked, tampered warning removed, s-on). And if your screen is blank, it will also be blank for TMOB, so there is no need to restore stock.

Look here: http://forum.xda-developers.com/showthread.php?t=2200930
There is the "RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09 es.50.02.07_2_10.09d.50.04L_ver2_release_287723_signed.exe"
(Android 4.04 version)

rootrider said:
No, it will simply not flash (= exit with an error).
Each RUU/OTA update comes with a certain new bootloader version. Dependant on this version you can upgrade to the next higher hboot but usually not downgrade to a lower hboot. E.g. if youre on 2.15 JB you can't downgrade to 1.14 ICS by RUU anymore. But you are still able to flash custom roms based on whatever android version. The only thing here is with bootloaders > 1.09 the kernel needs to be flashed separately in fastboot mode.
That's where s-off / downgrading bootloader comes into game. As downgrading bootloader is a pain, s-off would be the way to go. For warranty purposes you will be able to restore a stock phone (locked, tampered warning removed, s-on). And if your screen is blank, it will also be blank for TMOB, so there is no need to restore stock.
Click to expand...
Click to collapse
I've got the same Problem.
But I can't SuperCID / S-Off my Phone like here: http://forum.xda-developers.com/showthread.php?t=1671396
It just doesn't work!!!
How could I go back to a Stock ROM ??
I have really no idea

TMOB-101 ?
Which bootloader version?

rootrider said:
TMOB-101 ?
Which bootloader version?
Click to expand...
Click to collapse
hboot-2.15.0000

Golden-One said:
I've got the same Problem.
But I can't SuperCID / S-Off my Phone like here: http://forum.xda-developers.com/showthread.php?t=1671396
It just doesn't work!!!
How could I go back to a Stock ROM ??
I have really no idea
Click to expand...
Click to collapse
I can sent you a twrp nandroid backup from my phone (s4-tmobile germany)
I have backups from the 3.16.111.5.and from the latest 3.16.111.7. They are the stock roms with the supersu added.
If you recover the 3.16.111.5 nandroid backup you will take a OTA update to clean 3.16.111.7 (without supersu).

hi
Can you send me the backups too?
thank you so much!

kevin3688 said:
hi
Can you send me the backups too?
thank you so much!
Click to expand...
Click to collapse
You can find it/them here.
It's just plain stock nandroids. No root - nothing.

rootrider said:
You can find it/them here.
It's just plain stock nandroids. No root - nothing.
Click to expand...
Click to collapse
Thanks a lot!

[Q] Juopunutbear HBOOT 1.27 Stock RUU

Hello guys. I'm new in this "world" and I need some help.
I have unlocked the bootloader using HTC Dev, I'm also root and I have 4EXT recovery.
I want to be S-off to be SuperCID, install firmware 3.33 universal and then install ROMs without problems.
The webpage of Juopunutbear says that I needd to have a stock RUU and no other ROMs are supported. I have Android 4.0.3 official, it was updated by the phone (I haven't changed anything, for now hehe). Can I use Juopunutbear? Is my Android a stock RUU? If not, how can I use Juopunutbear? I've been looking for Stock RUU but I haven't found any version equals or bigger than my build number (3.32). My sensation is a Vodafone Spanish phone.
Thank you!!!

NasterRetsan said:
Hello guys. I'm new in this "world" and I need some help.
I have unlocked the bootloader using HTC Dev, I'm also root and I have 4EXT recovery.
I want to be S-off to be SuperCID, install firmware 3.33 universal and then install ROMs without problems.
The webpage of Juopunutbear says that I needd to have a stock RUU and no other ROMs are supported. I have Android 4.0.3 official, it was updated by the phone (I haven't changed anything, for now hehe). Can I use Juopunutbear? Is my Android a stock RUU? If not, how can I use Juopunutbear? I've been looking for Stock RUU but I haven't found any version equals or bigger than my build number (3.32). My sensation is a Vodafone Spanish phone.
Thank you!!!
Click to expand...
Click to collapse
you have the stock ruu
but i suggest to use this guide for S-OFF
http://forum.xda-developers.com/showthread.php?t=2751187
you will avoid the wire trick

rzr86 said:
you have the stock ruu
but i suggest to use this guide for S-OFF
http://forum.xda-developers.com/showthread.php?t=2751187
you will avoid the wire trick
Click to expand...
Click to collapse
Thank you for your help! But Rumrunner didn't work, anyway I'll try to find out what the problem is

NasterRetsan said:
Thank you for your help! But Rumrunner didn't work, anyway I'll try to find out what the problem is
Click to expand...
Click to collapse
read my post in the rumrunner thread
you will see it will work