Database Info

[Q] Question about bootloader

Probably showing my ignorance but i would like to know if any functionality is lost by changing the bootloader of a rom to the revolutionary bootloader when s-offing the rom?
I would also be grateful if somebody could explain to me what improvements or ill effects a change of bootloader can invoke i.e. what parts of the functionality of the rom do the bootloader effect.

Bootloader doesn't affect the ROM at all. The bootloader is just what boots into a rom.

bobsie41 said:
Probably showing my ignorance but i would like to know if any functionality is lost by changing the bootloader of a rom to the revolutionary bootloader when s-offing the rom?
I would also be grateful if somebody could explain to me what improvements or ill effects a change of bootloader can invoke i.e. what parts of the functionality of the rom do the bootloader effect.
Click to expand...
Click to collapse
If you go through the Revolutionary process. You'll get a Hboot with a slightly different version.
You will however, get S-OFF and Su and a Custom Recovery (ClockworkMod, CWM).
The phone will operate normally. You will have the opportunity of backing it up (Nandroid), installing apps that require Root access and install Custom ROMs.
As I think the other poster mentioned, can't see it ATM, the bootloader is Phone based and independent of the ROM.
I originally used a similar process (AlphaRev) on my desire, AlphaRev and Unrevoked produced Revolutionary together.
From personal experience, it has not affected my phone in any adverse manner, as always YMMV. It opened possibilities though.

Then why are there different bootloaders??
Sent from my HTC Sensation Z710e using xda premium

bobsie41 said:
Then why are there different bootloaders??
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Usually 'cos HTC release slightly different versions of them.
The latest one 1.19 seems more locked down for example.
TBH most folks just use Revolutionary to S-OFF etc. then just leave it at that, mine is 1.17.1111 Once it's done it's done. There is a new Radio that seems to require 1.19 but as my phone works well with the current version I have installed, I'm leaving that well alone.
According to their site they can apply S-OFF to the following versions: HTC Sensation (pyramid) 1.17.0006, .0008, .0011 and .0012, 1.18.0000
What are you actually trying to do / want to achieve ?

what u loose is if u are on stock can update using HTC OTA
If u are stock rom u will not be able to make the OTA updates as it will hang since it expect its own hboot, this is the drawback I know. u will have them to reload a stock copy to have the official hboot and recovery again.

boalos said:
If u are stock rom u will not be able to make the OTA updates as it will hang since it expect its own hboot, this is the drawback I know. u will have them to reload a stock copy to have the official hboot and recovery again.
Click to expand...
Click to collapse
Good point.
However Custom ROMs seem to be "nicer" and tend to have updates earlier.
EDIT: As a fellow Vodafone UK user I thought I'd add that: When I had my HTC Desire (was running Eclair initially) and Froyo was being released, Vf UK was one of the slowest companies to release it. As the newer Froyo offered significant improvements I jumped at the chance to go for a Carrier independent ROM that supported Froyo. Thus freeing myself from Vf release schedule and also removing the Vf bloat ware that I never used. I did suffer a set back when I got the Sensation as initially S-OFF wasn't possible. This situation looks like it'll repeat itself with the release of ICS. PM if you want more info.

gol_n_dal said:
Usually 'cos HTC release slightly different versions of them.
The latest one 1.19 seems more locked down for example.
TBH most folks just use Revolutionary to S-OFF etc. then just leave it at that, mine is 1.17.1111 Once it's done it's done. There is a new Radio that seems to require 1.19 but as my phone works well with the current version I have installed, I'm leaving that well alone.
According to their site they can apply S-OFF to the following versions: HTC Sensation (pyramid) 1.17.0006, .0008, .0011 and .0012, 1.18.0000
What are you actually trying to do / want to achieve ?
Click to expand...
Click to collapse
I am trying to achieve the best possible stock experience but i don't want to lose the ability to root.
The reason i was asking was the fact that it was stated that, the new h-boot was needed for the new radio to work properly on the leaked ics with sense RUU which suggests that the bootloaders have slightly different functionality.

bobsie41 said:
I am trying to achieve the best possible stock experience but i don't want to lose the ability to root.
The reason i was asking was the fact that it was stated that, the new h-boot was needed for the new radio to work properly on the leaked ics with sense RUU which suggests that the bootloaders have slightly different functionality.
Click to expand...
Click to collapse
Ahh you're talking about 11.59..... Sorry I think I got off topic :-((
I've seen a few still using 10.58.........10.15... on ICS with success. I have downloaded an ICS ROM and it seems to work on HBoot 1.17.1111 with my radio. Reflashed back to CM7 though, but I now have the option. I'll reflash ICS again and just confirm it works on 3G and WiFi as usual. I didn't check too far when I first tried. Please bear in mind that these ICS ROMs are based on unreleased versions, so really a taster at the moment.

Can't Get Back To Unrooted Stock No Matter What I Try

Last week I went back to stock to familiarize myself with the process (which unfortunately brought my HBoot to 1.14). I also decided to try out TWRP when I rooted again. But before I could finish up I hit a button in TWRP that didn't need any confirmation. I don't remember which button because it did what it did quicker than I could notice. After that I couldn't even flash a ROM because I couldn't mount the sd card and whatever happened erased everything on my phone but I ended up figuring that out.Now I'm on ViperOneS but I can't unroot. I can't flash either of the RUU (Error 155) that are for T-Mobile US I even changed my CID to 11111111 but no dice(and yes I did flash the stock recovery and boot before relocking). The only thing I can do to get close to unrooted stock is flash the nandroid of a rooted stock ROM. Now I haven't mentioned every method I've tried, so before I start getting bashed for not searching, I want to mention that I've been at this for about 4 days and I have tried EVERYTHING that I've found on XDA and other forums but nothings worked. Is it my HBoot that prevents from doing anything? Should get another One S? Or should I just be thankful that I have a functioning phone?
Sorry for the long winded post but I wanted to make sure I put in as much detail as possible.

antny said:
Last week I went back to stock to familiarize myself with the process (which unfortunately brought my HBoot to 1.14). I also decided to try out TWRP when I rooted again. But before I could finish up I hit a button in TWRP that didn't need any confirmation. I don't remember which button because it did what it did quicker than I could notice. After that I couldn't even flash a ROM because I couldn't mount the sd card and whatever happened erased everything on my phone but I ended up figuring that out.Now I'm on ViperOneS but I can't unroot. I can't flash either of the RUU (Error 155) that are for T-Mobile US I even changed my CID to 11111111 but no dice(and yes I did flash the stock recovery and boot before relocking). The only thing I can do to get close to unrooted stock is flash the nandroid of a rooted stock ROM. Now I haven't mentioned every method I've tried, so before I start getting bashed for not searching, I want to mention that I've been at this for about 4 days and I have tried EVERYTHING that I've found on XDA and other forums but nothings worked. Is it my HBoot that prevents from doing anything? Should get another One S? Or should I just be thankful that I have a functioning phone?
Sorry for the long winded post but I wanted to make sure I put in as much detail as possible.
Click to expand...
Click to collapse
It's most likely your hboot that prevents the RUU's from working. You can only use a RUU that contain a hboot of 1.14 or higher.
Since your signature says HBoot: 1.14 & Radio: 1.08ts.50.02.16_10.08e.50.04L. I assume you updated via the T-mobile US OTA, is that correct?
What's interesting is that other hboots in the 1.14 family are listed as 1.14.0002 but the T-mobile OTA the hboot is labeled 1.14.0004. I haven't seen anyone state if this is will prevent "downgrading" to 1.14.002 and don't feel like finding out myself.
What RUU are you trying?

dc211 said:
It's most likely your hboot that prevents the RUU's from working. You can only use a RUU that contain a hboot of 1.14 or higher.
Since your signature says HBoot: 1.14 & Radio: 1.08ts.50.02.16_10.08e.50.04L. I assume you updated via the T-mobile US OTA, is that correct?
What's interesting is that other hboots in the 1.14 family are listed as 1.14.0002 but the T-mobile OTA the hboot is labeled 1.14.0004. I haven't seen anyone state if this is will prevent "downgrading" to 1.14.002 and don't feel like finding out myself.
What RUU are you trying?
Click to expand...
Click to collapse
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium

antny said:
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I feel your pain. I updated with the OTA that moved us to hboot 1.13 before anyone said they changed the security :crying:.
The 1.84 and 1.53 RUU's wouldn't work for sure. 1.84 has the 1.13 hboot and 1.53 has the 1.09 hboot. Your only hope of using an RUU at this time is one of the Europe RUU's. The good news is that you already moved to supercid so you got that out of the way.
The ones that might work are the ones labeled "RUU_Ville_U_ICE_40_S_Europe_2.xxxxxx"
Here you can get the 2.21 RUU I can't recall if it's the 4.0.4 based one though. Not really sure where to get the other ones as file factory changed their download rules.
http://www.mediafire.com/?xlklqrlljb2zt#r9489rkr82wh2
You might need to click the "mainver error fix" on the on the All-in-one tool kit to get them to work since you would be downgrading the rom.
And if you do use that RUU from mediafire you can go here and click the thanks button for SneakyGhost for putting up the RUU for you to download.
http://forum.xda-developers.com/showpost.php?p=32262143&postcount=153
Then go here and click the thanks button for Football since he's the only source of RUU's there is.
http://forum.xda-developers.com/showpost.php?p=23542379&postcount=1
Good luck.

I've downgraded from 2.31 to 2.21, I know both have HBOOT 1.14 but not exactly sure if they have the exact identical numbers after the 1.14.
HTC One S
---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------
antny said:
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
2.21 RUU worked better for me than the T-Mobile stock Rom, it doesn't have w Wi-Fi calling do if that's a must for you only hope is to wait for the T-Mobile 2.35 RUU to be released.
HTC One S

dc211 said:
I feel your pain. I updated with the OTA that moved us to hboot 1.13 before anyone said they changed the security :crying:.
The 1.84 and 1.53 RUU's wouldn't work for sure. 1.84 has the 1.13 hboot and 1.53 has the 1.09 hboot. Your only hope of using an RUU at this time is one of the Europe RUU's. The good news is that you already moved to supercid so you got that out of the way.
The ones that might work are the ones labeled "RUU_Ville_U_ICE_40_S_Europe_2.xxxxxx"
Here you can get the 2.21 RUU I can't recall if it's the 4.0.4 based one though. Not really sure where to get the other ones as file factory changed their download rules.
http://www.mediafire.com/?xlklqrlljb2zt#r9489rkr82wh2
You might need to click the "mainver error fix" on the on the All-in-one tool kit to get them to work since you would be downgrading the rom.
And if you do use that RUU from mediafire you can go here and click the thanks button for SneakyGhost for putting up the RUU for you to download.
http://forum.xda-developers.com/showpost.php?p=32262143&postcount=153
Then go here and click the thanks button for Football since he's the only source of RUU's there is.
http://forum.xda-developers.com/showpost.php?p=23542379&postcount=1
Good luck.
Click to expand...
Click to collapse
I've thanked Football and gone to the link you provided but I don't get the whole Pt.1,2 and 3 thing. What am I supposed to do with that?
Edit: All good, just got it from the Dropbox link.... T-Mobile and Easy Tether don't mix.
fmedrano1977 said:
I've downgraded from 2.31 to 2.21, I know both have HBOOT 1.14 but not exactly sure if they have the exact identical numbers after the 1.14.
HTC One S
---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------
2.21 RUU worked better for me than the T-Mobile stock Rom, it doesn't have w Wi-Fi calling do if that's a must for you only hope is to wait for the T-Mobile 2.35 RUU to be released.
HTC One S
Click to expand...
Click to collapse
I don't really care about wifi calling, cool feature but I hardly use it. Is it 4.0.4 and Sense 4.1 though? It wouldnt stop me from using it if it wasn't but I'm just curious haha.

4.0.4 and Sense 4.0
HTC One S

fmedrano1977 said:
4.0.4 and Sense 4.0
HTC One S
Click to expand...
Click to collapse
Cool Cool Cool thanks

Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium

antny said:
Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Glad it worked out for you.

antny said:
Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
One last thing I did after installing that RUU was edit the build.prop to match some lines from the T-Mobile one:
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.fast.dormancy.rule=2
ro.ril.radio.svn=1
Make sure those match, these have given me the fastest DL speeds.
HTC One S

Yes! Thank you. This seems to be what I'm looking for. You can see the question I posted recently about this similar issue. But I also don't understand the part 1, 2, and 3 thing. Help?

DoogleDood said:
Yes! Thank you. This seems to be what I'm looking for. You can see the question I posted recently about this similar issue. But I also don't understand the part 1, 2, and 3 thing. Help?
Click to expand...
Click to collapse
What are you trying to do?
HTC One S

Nevermind I got it! I wasn't sure if the 3 "parts" of the EU RUU needed to be combined or... what. But upon extracting I found the full file.

fmedrano1977 said:
One last thing I did after installing that RUU was edit the build.prop to match some lines from the T-Mobile one:
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.fast.dormancy.rule=2
ro.ril.radio.svn=1
Make sure those match, these have given me the fastest DL speeds.
HTC One S
Click to expand...
Click to collapse
Why thank you sir.

antny said:
Why thank you sir.
Click to expand...
Click to collapse
Please someone help me I just flashed axiom rom wifif won't work I tryd other roms too, wifi won't work how can I fix this ??
Do I need to flash a RUU I am new to this. I had th latest tmo update before I rooted the phone people says that's why wifi won't work in other thread.
Please help me fix this !!!

johnyguy said:
Please someone help me I just flashed axiom rom wifif won't work I tryd other roms too, wifi won't work how can I fix this ??
Do I need to flash a RUU I am new to this. I had th latest tmo update before I rooted the phone people says that's why wifi won't work in other thread.
Please help me fix this !!!
Click to expand...
Click to collapse
I'm honestly not to sure on how to fix this. I've searched it before I went back to stock (going back to stock is a definite fix) and couldn't find much on it. I'm sure something has developed from it by now though. Actually :: navigates to another tab:: http://forum.xda-developers.com/showthread.php?t=1900644 if it's compatible with your ROM, this kernel claims to have a fix for wifi and sound (I don't know what the sound issue is all about) but try that, it might work. But most importantly search, read, search and read some more, especially since you're new to this, I've rooted many phones and I still had problems with the One S. Good luck!

Found RUU 2.35 and finally got my phone back to stock. I posted info here:
http://forum.xda-developers.com/showthread.php?t=1941402

sylvestk said:
Found RUU 2.35 and finally got my phone back to stock. I posted info here:
http://forum.xda-developers.com/showthread.php?t=1941402
Click to expand...
Click to collapse
That release gives you the no data when screen is off issue.
HTC One S

[Q] Differences between hboots 1.06, 1.09, 1.13, and 1.14?

So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.

byliu88 said:
So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.
Click to expand...
Click to collapse
1.06, flash the new radio seperately once your on 1.06.

usaff22 said:
1.06, flash the new radio seperately once your on 1.06.
Click to expand...
Click to collapse
Thanks for the info, which radio is that though?

<here you go mate, http://d-h.st/XBu it was posted on this forum by torx, i think , it's a flashebel zip. with aroma installer so just folow the instructions

alexskin said:
<here you go mate, http://d-h.st/XBu it was posted on this forum by torx, i think , it's a flashebel zip. with aroma installer so just folow the instructions
Click to expand...
Click to collapse
Alright I'll try it out. thanks!

byliu88 said:
So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.
Click to expand...
Click to collapse
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.

HD Case said:
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.
Click to expand...
Click to collapse
He probably used the instructions in the development section:
http://forum.xda-developers.com/showthread.php?t=1990043

Kamilr97 said:
He probably used the instructions in the development section:
http://forum.xda-developers.com/showthread.php?t=1990043
Click to expand...
Click to collapse
Thanks,
Yikes! Now I see why a lot of people don't even attempt this

I have also downgrade my hboot back to 1.06 and my wifi is also buggy i hope there is a solution for
Maybe i must go back to stock but i dont know if my wifi then is fix

fjjfrank said:
I have also downgrade my hboot back to 1.06 and my wifi is also buggy i hope there is a solution for
Maybe i must go back to stock but i dont know if my wifi then is fix
Click to expand...
Click to collapse
I downgraded from 1.14 to 1.06 too, installed 1.53 RUU and then experienced wifi issues on Trickdroid 8.
I had to flash "extra partitions" to make it work. Seems to be some partitions required for wifi to work on versions based on latest sense kernels.
I flashed extra partitions 2.35 and wifi did not work. Then I flashed 1.84 and wifi on Trickdroid 8 would connect, but from time to time (very frequently every 15 seconds on average) disconnect and reconnect, randomly (was annoying and killing my battery). I moved to trickdroid 7 TMOUS version and wifi works perfectly, never disconnects.
(My phone was from T-Mobile)
Here are the links, taken from this post: http://forum.xda-developers.com/showthread.php?t=1657831&page=271
2.35 Extra Partitions
https://www.dropbox.com/s/7gtuvbynr3...rtitions.zip?m
1.84 Extra Partitions
https://www.dropbox.com/s/mmjcqisgoo...rtitions.zip?m
NOTE: On CM rom I never had issues even without flashing extra partitions, and even when I was on hboot 1.14.
Hope this helps,
Regards,
Diego
---------- Post added at 07:57 PM ---------- Previous post was at 07:51 PM ----------
And regarding the topic from this post, hboot is like the BIOS of the phone. You gain nothing from upgrading it, only gain restrictions from 1.13 and above. So as far as I read it is better to stick to 1.06
Regarding the procedure to downgrade, for the one that asked, it can make you panic on the step when you upload hboot 1.06. For me, it failed 3 times, and I had to go to work after third time with a "bricked" phone -.-
But I came back, tried from my laptop instead of my PC, and worked on the first attemp!. Seemed to be my PC USB not working properly or not being fast enough/not having enough power, who knows.
It seems scary but is fairly straight through, the procedure is perfectly detailed. Did it from an Ubuntu 12.04 live image.
Regards,
Diego

HD Case said:
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.
Click to expand...
Click to collapse
Yes, I used the guide Kamilr mentioned. It was fairly nerve wracking but if you carefully read all of the instructions and get an idea of what your doing it goes pretty smoothly. Same with sperad, flashing the hboot itself failed for me 3 times, but all you had to do was reboot and retry. But anyways regarding the wifi issue. flashing the new radio did not seem to alleviate anything, but I flashed viperOneS and wifi now works fine, so I plan to stay with it.
@fjjfrank Try relocking your bootloader, then running your RUU http://d-h.st/users/agentc13/?fld_id=2293#files (if you're on tmobile its 1.53, im not sure about the other networks), which'll bring you back to stock. Wi-Fi worked perfectly on stock when I tried that after downgrading to 1.06. If its good from there you can try what i did and unlock your bootloader again and flash viperOneS which worked for me.

byliu88 said:
Yes, I used the guide Kamilr mentioned. It was fairly nerve wracking but if you carefully read all of the instructions and get an idea of what your doing it goes pretty smoothly. Same with sperad, flashing the hboot itself failed for me 3 times, but all you had to do was reboot and retry. But anyways regarding the wifi issue. flashing the new radio did not seem to alleviate anything, but I flashed viperOneS and wifi now works fine, so I plan to stay with it.
@fjjfrank Try relocking your bootloader, then running your RUU http://d-h.st/users/agentc13/?fld_id=2293#files (if you're on tmobile its 1.53, im not sure about the other networks), which'll bring you back to stock. Wi-Fi worked perfectly on stock when I tried that after downgrading to 1.06. If its good from there you can try what i did and unlock your bootloader again and flash viperOneS which worked for me.
Click to expand...
Click to collapse
oke thanks
i am from the netherlands and i have got a unbranded one s
witch hboot can i install without updating my bootloader

Excuse me for sounding stupid but grey matter not working

I have been flashing for some time but excuse me if I sound stupid but the grey matter just don't work any more. I have RUU'd different RUU's from the 1.82 to 2.20 trying to get different customs to work and I can't figure out what base I am on. At the time I am using Clean Rom 6.1 R2 and things seem to work fine but just wondering. Some how I managed to go from HBOOT 2.14 I think down to HBOOT 1.09 without downgrading. I think I got it from some RUU. I have read that the HBOOT 1.09 is a golden thing on the phone but don't know why.
With this rom I have tried to flash the 3.18 radio and get a soft brick at the boot screen. I am pretty sure the last time I RUU'd I used the Cingular Us 1.82 and in the process it upgraded itself to the 1.83 . Now I have read that some roms with sense work better on the 3.18 RUU.. Will I loose the HBOOT 1.09 if I do this?
At the present
S-OFF
unlocked
CID 11111111
radio 0.24p..32.09.0501.......
I am just looking and trying different variations to find the best setup for my phone. Excuse me for sounding so stupid. The grey matter just is slush any more.

The 3.18 ruu will give you the 2.14 hboot but sense you are s-off which hboot you have is not that important people wanted the 1.09 hboot because you could flash radios and boot.img with it s-off allows you too do this no matter what hboot you have
Sent from my HTC One X using Tapatalk 2

Because you're s-off it doesn't matter what hboot you're on. Sense ROMs tend to run smoother/better with the latest update. So feel free to RUU up to 3.18. Don't relocked your bootloader, just ruu.
If you want to run AOSP ROMs after, though, you'll need to downgrade your touchscreen firmware.
Also for some people cm10 doesn't boot until they've upgraded for some odd reason.
Sent from my HTC One XL using xda app-developers app

exad said:
Because you're s-off it doesn't matter what hboot you're on. Sense ROMs tend to run smoother/better with the latest update. So feel free to RUU up to 3.18. Don't relocked your bootloader, just ruu.
If you want to run AOSP ROMs after, though, you'll need to downgrade your touchscreen firmware.
Also for some people cm10 doesn't boot until they've upgraded for some odd reason.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I understand that being S-OFF one could do most anything and be safe but I didn't really know if loosing the HBOOT 1.09 had any consequents or not. Plus, didn't know if upgradeing to the 3.18 firmware would be that beneficial or not. At one point I was on the 2.20 and took the OTA ATT udgrade to see what it was about but didn't like the rom ,but I did downgrade the touch screen . There are features with all the customs but don't like any one in particular, wish there some way to combine certain features from each one into one to make one that I liked for my phone. So far the best I can come up with is Clean Rom 6.1R2 with BlueIceSense CR6 and cityID apk. plus the radio from 3.18.
Thanks for understanding loss of grey matter stupidity

Going back to stock?

Need some help on how to do this? At present I am HTC Dev unlocked, S-OFF HBOOT 1.27, The only RUU for my O2UK device is the very first release of GB, so I am gonna have to install that and get the OTA updates I guess, but how do I go about doing this? I have downloaded the RUU and tried to run it but it got so far and gave an error, probably because I was downgrading rather than upgrading.

slugger09 said:
Need some help on how to do this? At present I am HTC Dev unlocked, S-OFF HBOOT 1.27, The only RUU for my O2UK device is the very first release of GB, so I am gonna have to install that and get the OTA updates I guess, but how do I go about doing this? I have downloaded the RUU and tried to run it but it got so far and gave an error, probably because I was downgrading rather than upgrading.
Click to expand...
Click to collapse
Hi,
Why do you want OTA?
You have s-off,and you can run any ROM out there.
All of which are better than anything HTC are putting out.
And there are some who have used the OTA and lost s-off.

malybru said:
Hi,
Why do you want OTA?
You have s-off,and you can run any ROM out there.
All of which are better than anything HTC are putting out.
And there are some who have used the OTA and lost s-off.
Click to expand...
Click to collapse
I've been playing about with ROMs and all have something annoying wrong with them, whether it be battery life, sluggishness, overheating. The phone ran better on GB

Why not try RCMix sense 3.5 gb rom? Very very good, i used it for a while.

slugger09 said:
I've been playing about with ROMs and all have something annoying wrong with them, whether it be battery life, sluggishness, overheating. The phone ran better on GB
Click to expand...
Click to collapse
Hi,
OK.
Look HERE
Choose a branded or general one.
The ones with a 10.56 or 10.58 radios are the ones you want.