Database Info

[Q] Is there a RUU for HBOOT 1.27.1100

Hello,
my HTC SENSATION has the HBOOT Version 1.27.1100 and I want to download a RUU to restore my HTC device completely. But I can´t find a RUU with this HBOOT version.
I only have to download the right RUU and install it on my HTC device to restore it completely, right?

james0912 said:
Hello,
my HTC SENSATION has the HBOOT Version 1.27.1100 and I want to download a RUU to restore my HTC device completely. But I can´t find a RUU with this HBOOT version.
I only have to download the right RUU and install it on my HTC device to restore it completely, right?
Click to expand...
Click to collapse
Hi,
Download hboot 1.17 HERE
Then you can use an RUU for that firmware.

which ruu can i use now???
i only want to restore my htc sensation completely!

james0912 said:
which ruu can i use now???
i only want to restore my htc sensation completely!
Click to expand...
Click to collapse
Hi,
You need an RUU that matches your area and carrier.
Look HERE

malybru said:
Hi,
Download hboot 1.17 HERE
Then you can use an RUU for that firmware.
Click to expand...
Click to collapse
Hey malybru can you flash this file with the stock recovery? Also this only changes the Hboot version correct?

T-Macgnolia said:
Hey malybru can you flash this file with the stock recovery? Also this only changes the Hboot version correct?
Click to expand...
Click to collapse
Hi,
It's a PG58IMG.zip .
So, it's just placed on the sd card.
Recovery is not involved.
Yes,it will only change the hboot.

malybru said:
Hi,
It's a PG58IMG.zip .
So, it's just placed on the sd card.
Recovery is not involved.
Yes,it will only change the hboot.
Click to expand...
Click to collapse
Man I had a duh money, I realized after I posted that that that file will flash automatically when you boot to Hboot, as that is the file name that Hboot looks for. But still doesn't Hboot use the recovery to flash the file?

T-Macgnolia said:
Man I had a duh money, I realized after I posted that that that file will flash automatically when you boot to Hboot, as that is the file name that Hboot looks for. But still doesn't Hboot use the recovery to flash the file?
Click to expand...
Click to collapse
Hi,
I knew you knew that.
I just posted for general information.
I think it flashes in bootloader,before recovery starts.

malybru said:
Hi,
I knew you knew that.
I just posted for general information.
I think it flashes in bootloader,before recovery starts.
Click to expand...
Click to collapse
Ok this will be my last post here cause I don't want to hyjack this thread.
This has brought a question to mind and I will have to see if I can find the answer some how. The question is what does Hboot use to flash the PG58IMG.zip. I personally have always thought it used recovery to flash the file.

T-Macgnolia said:
Ok this will be my last post here cause I don't want to hyjack this thread.
This has brought a question to mind and I will have to see if I can find the answer some how. The question is what does Hboot use to flash the PG58IMG.zip. I personally have always thought it used recovery to flash the file.
Click to expand...
Click to collapse
It uses the bootloader to flash the file. If you put it on your sd card and reboot into bootloader (volume down button + power button) you will be asked to update. Choose yes using the volume buttons and the file will be flashed, easy as that
Sent from my HTC Sensation using XDA

james0912 said:
Hello,
my HTC SENSATION has the HBOOT Version 1.27.1100 and I want to download a RUU to restore my HTC device completely. But I can´t find a RUU with this HBOOT version.
I only have to download the right RUU and install it on my HTC device to restore it completely, right?
Click to expand...
Click to collapse
When you install a rom by a RUU, it will also flash the stock Hboot version. Take a look at the shipped roms thread.
Sent from my HTC Sensation using XDA

james0912 said:
Hello,
my HTC SENSATION has the HBOOT Version 1.27.1100 and I want to download a RUU to restore my HTC device completely. But I can´t find a RUU with this HBOOT version.
I only have to download the right RUU and install it on my HTC device to restore it completely, right?
Click to expand...
Click to collapse
Hboot 1.27 is clearly ICS.
Download official RUU from here (RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed)
This is the latest official ICS RUU for unbranded Europe Sensation.
If your device is branded or your region is not Europe then search for the appropriare RUU.
Run the exe from pc with phone usb plugged. It will restore your phone as "out of the box".
Hope it helped.

Man I really don't understand any of this lol......... I'm just gonna ask a few questions and you guys can either respond or not....
1) I am on stock ICS, rooted, with HTC Dev Unlocked and using Clockwork. If I wanted to un-root, remove clockwork and re-lock the Hboot... How would that go exactly? 1.27.0000 etc...
2) I don't understand why getting S-Off is so difficult. If one would simply downgrade from ICS to GB, wouldn't that change the Hboot version to a lower one, and then you would be able to use the Revolutionary way? Or is that not possible to do? Or does the downgrade not affect the Hboot?
3) Which Custom ROM am I able to flash at the moment? Any, based on ICS?

FnH84 said:
Man I really don't understand any of this lol......... I'm just gonna ask a few questions and you guys can either respond or not....
1) I am on stock ICS, rooted, with HTC Dev Unlocked and using Clockwork. If I wanted to un-root, remove clockwork and re-lock the Hboot... How would that go exactly? 1.27.0000 etc...
2) I don't understand why getting S-Off is so difficult. If one would simply downgrade from ICS to GB, wouldn't that change the Hboot version to a lower one, and then you would be able to use the Revolutionary way? Or is that not possible to do? Or does the downgrade not affect the Hboot?
3) Which Custom ROM am I able to flash at the moment? Any, based on ICS?
Click to expand...
Click to collapse
Hi,
1. I think that you can just run the RUU in the post above yours.(If your phone is European)
2.Downgrading is not possible on hboot 1.27.000
HTC have locked you out of this possibility.
3.As you say.Any 3.32. based ICS ROM.

malybru said:
Hi,
1. I think that you can just run the RUU in the post above yours.(If your phone is European)
2.Downgrading is not possible on hboot 1.27.000
HTC have locked you out of this possibility.
3.As you say.Any 3.32. based ICS ROM.
Click to expand...
Click to collapse
Thank you very much Not planning un-root but was just wondering, in case I have to do that at some point, it's good to know how

FnH84 said:
Man I really don't understand any of this lol......... I'm just gonna ask a few questions and you guys can either respond or not....
1) I am on stock ICS, rooted, with HTC Dev Unlocked and using Clockwork. If I wanted to un-root, remove clockwork and re-lock the Hboot... How would that go exactly? 1.27.0000 etc...
Click to expand...
Click to collapse
It can be done only by running corresponding RUU which can be found based on your firmware(in your case it is 3.32) and cid (to get cid "fastboot getvar cid")...if you are unbranded i.e. cid is HTC__001..then you can run the above mentioned ruu...or else you should get the appropriate one...if you can't find it then post your cid along with radio..we can find the appropriate one for you
2) I don't understand why getting S-Off is so difficult. If one would simply downgrade from ICS to GB, wouldn't that change the Hboot version to a lower one, and then you would be able to use the Revolutionary way? Or is that not possible to do? Or does the downgrade not affect the Hboot?
Click to expand...
Click to collapse
If you are S-ON you can't downgrade...not by running a RUU or by flashing firmware directly...that's why people use revolutionary first to get soff and then they'll flash unlocked firmware to update the hboot and all...
It you are SOFF you can literally do anything ..upgrade, downgrade..its your choice..
3 ) Which Custom ROM am I able to flash at the moment? Any, based on ICS?
Click to expand...
Click to collapse
As you are unlocked via HTC dev..if you update your recovery with 4EXT latest one which has smartflash mode ON(exclusive SON flash)..you could have any ROM
Edit: I'm bit late huh anyways for more detailed answer look ay my post
sent from my blazing fast pyramid through sonic waves

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!

[HOWTO] [HTC One SV] Unbrand your phone to get the OTA updates

Bonjour everyone, here's a little guide on how to unbrand your phone in order to get the OTA updates notifications directly and be able to install them.
If you want to get S-OFF one day on your One SV, read this first. You need to change CID to SuperCID to do so, and it's not possible (for the moment) if you upgrade to JB
Basically this works as long as your phone model is sold unbranded somewhere in the world and that the people having such a phone got an OTA update.
For now, ther's no way to change CID if you're running JB and are S-ON. That means that this only work for One SV's running ICS who want to get the OTA updates.
As far as I know, it works on K2_U and K2_UL, since they both got an OTA update to JB.
The trick is simple, I didn't invent it and haven't been able to find its original founder, but thanks a lot to her or him !
I'm basically just a messenger here since I only tried out some stuff that worked with other phones, so thanks a lot to bkcokota, old.splatterhand and jmztaylor
Don't try it if you're worried, bricks happen, you'd be the only one responsible !
Here we go :
1. First you need to root your phone, here's how.
2. Change you CID using the same method than for the One S.
Personnaly, I changed it to "HTC__203", which is the CID unbranded HTC phones have in France (HTC-FRA).
For example, "HTC__001" is HTC-WWE, which stands for World Wide English.
You can change it to whatever CID you like : choose it well. I can only recommend to use HTC__203 since it's the only one I tried and that it worked, but do as you please !
3. Flash stock recovery back. You'll find it here or here. Flash it like you flashed CWM recovery (into fastboot, using fastboot flash recovery xxxxxx.img).
4. Relock your bootloader. It's possible that it's not necessary, but it can't hurt ("fastboot oem lock", when in fastboot usb)
5. Run a RUU that matches you unbranded CID to get an "unbranded" rom.
You'll find them here, for example. The "RUU_K2_UL_ICS_40_HTC_Europe_1.17.401.5_R....exe" one will work with HTC__203 and HTC__001 CIDs.
6. Go ask your phone if he can find any updates
WARNING : for the moment there's no way to change CID if you upgrade to JB since the newer HBOOT (v2.00) don't let you do it. That means that for now you won't be able to S-OFF if you upgrate to JB using this method. For now...

Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).

old.splatterhand said:
Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).
Click to expand...
Click to collapse
Done, sir.
It was only said at the bottom of the message at first, but now I put it at the beginning as well.
There's one thing that I'm trying to get though : according to a lot of people and forums, you don't get OTA when you have SuperCID... but some poeple say they do.
It probably changes depending on the type of HTC phone, but also depending on the OTA (some got the first ones, but not the latest...).

I got the ota notification with SuperCID, i think it depends on more things.
But there i'm not far enough into it.

I have had no success at all. My story:
Updated a branded phone to JB, rooted. Then I did a moonshine S-off and changed CID to HTC__001 (even tried 11111111).
I have downloaded a ICS RUU (couldn't find stock K2_UL so I thought that I would download ICS first and then do OTA to JB) but I am getting error 158. I have checked md5 sum and it matches (http://androidfiles.org/ruu/getdown...0.14_2_10.49.40.11L_release_301902_signed.exe). Any ideas?

If you're on jb and hboot 2.00, that's normal... and written in the first post.

There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?

Is there any chance to make this for the k2cl ( boost mobile ) version?

idr666 said:
Is there any chance to make this for the k2cl ( boost mobile ) version?
Click to expand...
Click to collapse
Can you be more specific, what you mean with "this".

old.splatterhand said:
Can you be more specific, what you mean with "this".
Click to expand...
Click to collapse
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB

idr666 said:
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB
Click to expand...
Click to collapse
Boost has no official jb, but i know that there is work for an custom jb rom for boost.

Oh, thank you for the info. Is there any link about this work in progress?

idr666 said:
Oh, thank you for the info. Is there any link about this work in progress?
Click to expand...
Click to collapse
Look here

szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?

szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot,...
Click to expand...
Click to collapse
This was before moonshine was available. With S-Off i think it should be possible.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
I think so.
szympro said:
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?
Click to expand...
Click to collapse
To get it a bit clearer.
At this point i'm not very up to date, thats why i didn't answer til now.
I think (but i'm not sure) you can flash the ruu, if you are on hboot 1.0.
And as you are S-Off you should be able to downgrade hboot. But this is a very risky point, you can easily brick your device. Here is, how you have to do:
rollon76 said:
To change hboot you will need a PL80IMG.zip on sdcard with android-info.txt and hboot.img inside it.
reboot to bootloader and flash.
Click to expand...
Click to collapse
The thing what makes it difficult, is to get the hboot.img (its inside ics ruu), cause the htc ruu's encrypted and i only have heard about tools for linux which can decrypt it.

Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!

szympro said:
Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!
Click to expand...
Click to collapse
Glad, it worked for you.
Yes, of course, everything is appreciated! You can use this thread, please post ruu name too. You can look at my posts there. Hboot, boot.img, recovery, radio, would be fine.

HERE have other ruu
https://www.dropbox.com/sh/1t2zswod7tc97az/5hbzEgTv80

szympro said:
I have downgraded hboot first (by extracting and encrypting ICS RUU using linux)
Click to expand...
Click to collapse
Wow, that's cool !
Did you use rollon's method and flashed PL80IMG.zip in bootloader mode ?
If yes, which android-info.txt did you use ?
If not, how did you do it ?
szympro said:
then I could run RUU and now I am stock ICS with S-off and superCID
Click to expand...
Click to collapse
Even cooler for you.
Did you get the ota update notification for JB then ?
Did you manage to apply it ?
Thanks and congratulations !

Hi everyone.
Just a quick message to confirm that rollon's method works.
To downgrade you need to be S-OFF, extract and decrypt (with ruuveal, using linux or a linux virtualbox runned in windows) hboot and androidinfo from ICS RUU, put them in a zip named PL80IMG.zip, put it on your sd card and boot into bootloader. Then you can run the ICS RUU normally and you'll be back to stock ICS, with a "*** LOCKED ***" bootloader (not relocked !), will be able to go back to S-ON using "fastboot oem writesecureflag 3" (thanks to JMZ)...
You'll then have a locked S-ON out of box phone running 100% stock ICS with original boot, recovery and all that... who'll get the 2 JB OTA's...
In case anyone's interested

Firmware Update Q&A [extra noob friendly]

WARNING*WARNING*WARNING
do this at your own risk! This is for s4 only!!
It has been brought to my attention that there might be a mid (model id) conflict
With flashing this and me along with others are trying to narrow down the issue. Thanks to @real187 for bring this to my attention.
I'm
S-off
Cid 11111111
MID PJ4011000
And had no problems flashing this firmware but others with same setup have reported soft brick.
OK I think @mkinney88 may have pin pointed where the soft brick may be coming from. If you s-off using facepalm, flash the firmware.zip and get soft bricked try this.
1. Get back to s-on (warning read directions several times before doing you CAN hard brick your phone) ~ http://forum.xda-developers.com/showthread.php?p=38267667
2. Get s-off with moonshine ~ http://forum.xda-developers.com/showthread.php?p=42613403
First off this is mostly ment for the T-Mobile branded phones but ill try and help all please let me know when asking questions if you have a T-Mobile or HTC branded phone (it has it right on the front of phone ).
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111 (I had no problem flashing firmware with s-off and Cid 11111111 but others have reported problems so if you don't want to chance it write your Cid to T-MOB010)
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin

Downloads
FIRMWARE ZIP DOWNLOAD
https://drive.google.com/folderview?id=0B-BYnLh2sosKamRwaUJJS05oU3M&usp=sharing or http://db.tt/Wua8mDS2
Credit go's to mkinney88 for the firmware

Bricks
First off if you can get into bootloader then you don't have a hard brick.
If your phone is in the black screen of death there may be hope but we're still trying to figure that one out.
If your phone doesn't respond to any input from you (power, power+volume down) then congratulations you have a hard brick but don't through it in the junk drawer just yet, you can have it jtag repaired (they open phone plug into main board and flash everything)
Here's the link (you do have to pay for this)
http://forum.xda-developers.com/showthread.php?p=37136553

One more just in case

rc420head said:
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin
Click to expand...
Click to collapse
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though

vatsaman said:
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though
Click to expand...
Click to collapse
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!

I put a note of this in op just now, thanks for the warning, I'm trying to figure out why some can do this Cid 11111111 and some can't.
-----------------------------------------
Friends don't let friends post without searching first!

rc420head said:
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!
Click to expand...
Click to collapse
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.

vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
Something else is going on. I used facepalm, and Cid 11111111 to flash firmware twice now with no issues and started same as you hboot 1.14
-----------------------------------------
Friends don't let friends post without searching first!

thank you!

I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?

khan.orak said:
I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?
Click to expand...
Click to collapse
I'm not sure if I understand your question. So let me ask a few questions.
What hboot are you on?
What carrier are you using?
Are you wanting to try cm 10.1 and afraid for losing stock?
What is stock just HTC sense 4+ or is there carrier added stuff?

rc420head said:
I'm not sure if I understand your question. So let me ask a few questions.
Click to expand...
Click to collapse
ok I'll try to make it clearer.
What hboot are you on?
Click to expand...
Click to collapse
I'm on hboot 2.15.0000
What carrier are you using?
Click to expand...
Click to collapse
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Are you wanting to try cm 10.1 and afraid for losing stock?
Click to expand...
Click to collapse
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
What is stock just HTC sense 4+ or is there carrier added stuff?
Click to expand...
Click to collapse
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.

khan.orak said:
ok I'll try to make it clearer.
I'm on hboot 2.15.0000
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.
Click to expand...
Click to collapse
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)

rc420head said:
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)
Click to expand...
Click to collapse
Thanks for the reply, really much appreciated.
I already have rooted the device and custom recovery TWRP 2.5. Though I am considering to downgrade it to 2.3.30. Now I made a backup of stock ROM. (System + Boot Partition)
So is this the only way I can get to stock?
I read somewhere that the following method could be used too(?)
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?

khan.orak said:
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?
Click to expand...
Click to collapse
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app

ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Big thanks! :good:

vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app

ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Yes this will also work (I was under the impression no ruu's were available)
khan.orak said:
Big thanks! :good:
Click to expand...
Click to collapse

forgiven90 said:
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah disabling the fast dormancy solved all my problems. :good:

Relock and RUU for o2 Germany One XL

I have a One XL with o2 Germany Branding (CID: O2___102)
HBOOT 2.14
S-ON
ROM installed: CM 10.1
I want to relock it and flash a Stock ROM. Reason is that I want to send it to warranty.
As far as I know the HBOOT of the ROM must not be older than 2.14 and I can't find an appropriate ROM.
1. fastboot oem lock
2. launch RUU (I tried some, but it did't work)
Do I have to flash a Stock Recovery after that?

Running an RUU returns the phone to being completely stock, including recovery. I hope your don't have SuperCID or you're gonna brick. Click the link in my signature, you'll find RUU threads there.
Sent from my Evita

timmaaa said:
Running an RUU returns the phone to being completely stock, including recovery. I hope your don't have SuperCID or you're gonna brick. Click the link in my signature, you'll find RUU threads there.
Sent from my Evita
Click to expand...
Click to collapse
And what if none of these RUUs work?
O2:
OTA_EVITA_UL_JB_45_S_O2_DE_3.17.207.1_0.23a.32.09. 29_10.128.32.34a_release_2990766qakrzbj4mpslnsy.zi p
OTA_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1-1.92.207.3_release_272963z2vl7cdycjk01nm4.zip

fly23 said:
And what if none of these RUUs work?
O2:
OTA_EVITA_UL_JB_45_S_O2_DE_3.17.207.1_0.23a.32.09. 29_10.128.32.34a_release_2990766qakrzbj4mpslnsy.zi p
OTA_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1-1.92.207.3_release_272963z2vl7cdycjk01nm4.zip
Click to expand...
Click to collapse
Those are ota updates... A ruu is an exe file that is run from Windows
Sent from my HTC One XL using xda app-developers app

The available o2 RUUs are too old
Sent from my One X using Tapatalk 4

So you run an older RUU and then take OTAs, you can't just flash OTA files, it won't work. You need to return the phone to being completely stock first though, s-on, original CID, locked bootloader, original recovery.
Sent from my Evita

I tried this file: RUU_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1_Radio_0.19as.32.09.20_3_10.107.32.25L_release_272946_signed.exe, it didn't work (contentual: Error 170, USB Error)
The XL is S-ON (never was S-OFF), bootloader is relocked (fastboot oem lock), then I launched the RUU.exe.
What I read is, that I can't flash older ROMs (what ever that means). So, what can I do if the o2-RUUs are to old? Can I downgrade the HBOOT?
edit: Can I downgrade HBOOT with the JET (http://forum.xda-developers.com/showthread.php?t=1940512) and then ran a RUU?