Database Info

[Radio][RIL]HOXL Radios/RILs including CM10.x based ROMs (Flashable zips)

These are flashable zips that will change your baseband (radio firmware). Google it See twistedxx's post quoted below if you have no idea what this means. If you have an HTC One X (Tegra 3) you're in the wrong place.
twistedddx said:
Radio = firmware
RIL(radio interface layer) = driver
Android = operating system
All 3 are "programs" that are running at different "levels", I have listed them from top to bottom in the order typically considered for how they interact. It is important to understand that a program is just code and how they interact is a philosophy programmers created and are now use to and not because it has to be set out that way.
In the case of the RIL, the API rarely/never changes so it is rarely/never updated.
The actual changes HTC make happen in the "Radio" program.
This is opposite to how say Windows/Nvidia tackle things. The firmware rarely/never changes and they make their changes in the "driver".
In Nvidia's case they do this because there is no standard way in x86BIOS/Windows for GPU firmware to be loaded from something as simple as the installed HDD, the firmware is actually written to chips on the card itself. It is just simpler to make all the code that gets changed inside the "driver" which is easily updated.
For our phones "radio" its trivial for the changes in code to happen at the "driver" level or the "firmware" level, HTC/Google decided they would stick changes in the "firmware". They did this because they created a separate partition for the radio so that they can protect it separately to the OS. Android typically means the phones OS should be open for tweaking, so it must be assumed the driver could easily be replaced.
Countries and Carriers have licensed spectrum to protect and transmitters must be licensed to use it, running custom radio code would break laws in many countries. This leads to the radio firmware being protected much more heavily than the OS itself.
It is because HTC is lazy and because we have awesome devs that we can replace the radio firmware at all. As far as HTC, Country communication regulators and carriers are concerned the user should NEVER be altering the radio software.
Radio:
radio(fancy code stuff) <-> ril(boring translator) <-> Android OS
Nvidia:
firmware(advanced fixed code that allows for flexible access) <-> driver(fancy code stuff and translator) <-> Windows
Note:
Radio is about wireless communications
Nvidia is about graphics processings. They are not similar technologies just some tech you may be familiar with.
PS. API = application programming interface.. and lets just say if you do not understand what that is.. I cant be arsed trying to explain that, go Google it.
Click to expand...
Click to collapse
If you're on the newer HBOOT (1.14) and insist on running a Sense based ROM use the Jet tool to downgrade to 1.09. This will allow you to write to the radio partition of the phone. Or just S-OFF (w00t!)
If you're running a CM 10.x ROM it doesn't matter what HBOOT you're on as the radio firmware is stored elsewhere (in a writable partition... /system to be precise).
Instructions:
1) Copy zip file to SD Card
2) Boot into Recovery (CWM or TWRP)
3) Flash
4) Reboot
Always take a Nandroid Backup in case something goes screwy!
Your bootloader will not show the correct baseband. I'm working on figuring out how the RUU updater handles the android_info.txt in the firmware.zip's
ethantarheels123 said:
I think maybe the op should add to the op that if you are running the official sense 5 4.2.2 builds, either telstra or tmobile germany, you SHOULD NOT be flashing the AT&T radios in the op, as they WILL cause data drops and reboots. Not quite sure about non-AT&T radios though...
Click to expand...
Click to collapse
These are radios for flashing in Sense OR CM 10.x builds after 7/15 nightly!!!. They don't include the RIL files.
CURRENTLY THE DROPBOX LINKS ARE DEAD, THEY'LL BE BACK SOON (Migrating everything over to dev host to avoid this situation in the future)
Rogers 1.73 (0.16a.32.09.06_10.81.32.14L):
ATT 1.73 & ATT 1.82 (0.16.32.09.19_2_10.79.32.08L) :
HTC ASIA HK 1.77 (0.16a.32.09.17_2_10.83.32.16L):
HTC TELSTRA 1.81 (0.17a.32.09.03_2_10.85.32.16L):
ATT 1.85 /1.82 (0.17.32.09.12_10.86.32.08L) : http://d-h.st/mgs - thanks to rburgman
HTC ASIA 1.88 (0.17a.32.09.16_2_10.88.32.17L):
ATT 2.09 (0.17a.32.09.24_2_10.91.32.19L):
HTC TELUS 1.91 (0.18a.32.09.01_2_10.94.32.20L):
HTC TELSTRA 1.89(0.18c.32.09.01_10.93a.32.20L):
HTC ROGERS 1.94 (0.18as.32.09.28_L_10.103.32.24L):
HTC ASIA 2.23 (0.19as.32.09.09_L_10.104b.32.25):
ATT 2.20 (0.19as.32.09.11_2_10.105.32.25): http://d-h.st/bZx
HTC O2 2.29 (0.19as.32.09.20_3_10.107.32.25): http://d-h.st/AKZ
HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L): http://d-h.st/cMp
HTC 2.41 VODAPHONE (Thanks Turge!)(0.20os.32.09.10_2_10.113.32.28L): http://d-h.st/HCL
HTC Singtel-Telstra 3.17 (0.23as.32.09.29_10.128.32.34):
HTC TMobile-Germany 3.17 (0.24a.32.45.03_10.129.32.34): http://d-h.st/TDQ - thanks to coldrazor!
HTC ATT 3.18 (0.24p.32.09.06_10.130.32.34): http://d-h.st/Aez
HTC TELSTRA 3.17.841.9 (1.26a.32.45.19_10.134.32.34a): http://d-h.st/VoB
HTC VODAPHONE 3.17.162.7 (1.27a.32.45.15_2_10.135.32.34a): http://d-h.st/pGK
HTC VODAPHONE 3.17.162.8 (1.27a.32.45.28_10.135.32.34a): http://d-h.st/CIM
HTC TMobile-Germany 5.08 (1.31a.32.45.16_2): http://d-h.st/Z6X
HTC VodaPhone 5.06 (1.31a.32.45.16_2_10): http://d-h.st/hIM
PLEASE DO NOT USE ANY OF THE RADIOS BELOW IF YOU ARE ON RECENT VERSIONS OF ROMS. THERE ARE HERE FOR ARCHIVAL PURPOSES ONLY
RIL Files + Radio: (YMMV. RIL versions change from one release to the next. Turge is on Record as not supporting these for his ROMs)
HTC O2 2.29 (0.19as.32.09.20_3_10.107.32.25): http://d-h.st/8tn
HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L): http://d-h.st/IJ4
HTC 2.41 VODAPHONE (Thanks Turge!)(0.20os.32.09.10_2_0.113.32.28L): http://d-h.st/KdE
HTC ATT 3.18 (Thanks to liamstears!)(0.24p.32.09.06_10.130.32.34): http://d-h.st/Maq
Radios for CM10.x based ROMs pre-7/15 builds (with radio in /system/etc/firmware)
TELSTRA 2.40 : http://d-h.st/vox
FIXED 2.41 VODAPHONE : http://d-h.st/0ah
O2 2.29 : http://d-h.st/gis
ATT 2.20 to revert back to stock cm10: http://d-h.st/R92
TELSTRA 1.89: http://d-h.st/yr4
Singtel-Telstra 3.17: http://d-h.st/UQa
TMOBILE GERMANY 3.17: http://d-h.st/645
ATT 3.18: http://d-h.st/DcT
HTC TELSTRA 3.17.841.9: http://d-h.st/Ewb
VODAPHONE 3.17.162.7: http://d-h.st/C9o
VODAPHONE 3.17.162.8: http://d-h.st/hKO
To Help decide which Radio is best for your area, try checking the Google Map: http://maps.google.com/maps/ms?ie=UTF&msa=0&msid=217917717250281685326.0004c262acfff78edb974
And please post your results to help other users out!!

possible to achieve soff since htc dev thinks its a rogers device?? rogers did achieve soff thrue htc dev right??? correct me if im wrong....

rpomponio said:
possible to achieve soff since htc dev thinks its a rogers device?? rogers did achieve soff thrue htc dev right??? correct me if im wrong....
Click to expand...
Click to collapse
I think only a handful did, mine didn't.
Sent from my HTC One X using xda premium

rpomponio said:
possible to achieve soff since htc dev thinks its a rogers device?? rogers did achieve soff thrue htc dev right??? correct me if im wrong....
Click to expand...
Click to collapse
I think over in the S=OFF Thread they've thrown around a few theories, I dont think any of them involved the radio partition.
The take away from this is that we've been able to flash images to partitions we didnt think we could without S=OFF (kernel, radio) so it might be a relatively moot point to achieve it. As far as ROM Development is concerned anyhow.
I think... could totally be wrong about all of that, though. =)

This is amazing man thank you!!

rpomponio said:
possible to achieve soff since htc dev thinks its a rogers device?? rogers did achieve soff thrue htc dev right??? correct me if im wrong....
Click to expand...
Click to collapse
Mine is a Rogers and didn't receive S-Off from HTC Dev.

any way you could make these for the AT&T radios? or at least point me in the right direction to find them?

Mosch26 said:
any way you could make these for the AT&T radios? or at least point me in the right direction to find them?
Click to expand...
Click to collapse
Looking for any one in particular?

When we get the kernel source, these forums will be buck wild
Sent from my HTC One X using xda premium

taylor.fowler said:
Looking for any one in particular?
Click to expand...
Click to collapse
the ones from 1.82 and 1.85 would be great!

Thanks for this, looking forward to att versions.
Sent from my HTC One X using Tapatalk 2

taylor.fowler said:
OK Folks, this is a CWM/TWRP Flashable zip to bring you back onto the Stock Rodgers Radio (Radio_0.16a.32.09.06). I'll add Asia and ATT versions if there's a demand for it (You can also just replace the radio.img file in the zip with whatever radio you want to flash).
Instructions:
1) Copy zip file to SD Card
2) Boot into Recovery
3) Flash
4) Reboot
Always take a Nandroid Backup in case something goes screwy!
https://www.dropbox.com/s/uje8r9erza80y0q/EVITA_Rodgers_Radio_0.16a.32.09.06.zip
Click to expand...
Click to collapse
great man. I'm on 1.73 ATT, any risk with flashing radio from either 1.82 or 1.85 ?

Do we have the ability to flash radios from the One S or does it have to be a S4 One X??

ge3kswag said:
Do we have the ability to flash radios from the One S or does it have to be a S4 One X??
Click to expand...
Click to collapse
This will most likely result in a brick
Sent from my HTC One X using XDA

First off thank you for this, I have been wanting my default rogers radio since upgrading to at&t 1.85 RUU. I have been questioning if there Is any difference in reception on my device.
Now, Please don't take this the wrong way, I am not trying to sound like an as!, but Rogers Canada does not have a "d" in Rogers. Again I realize this is a little petty, but I felt the point should at least be raised. Again, I am more then grateful that you have done this. Thanks again.
Sent from my HTC One X using Tapatalk 2

Zarboz said:
This will most likely result in a brick
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Or in one x getting hspa+ on T-Mobile lol.. jk
HTC oneSies

Please make one for ATT 1.85. I have been on 1.82 and didn't want to relock to RUU. I have been hoping for something like this for awhile now! Please good sir, may I have just a little more radios please, I haven't flashed anything in three long days.

rpomponio said:
possible to achieve soff since htc dev thinks its a rogers device?? rogers did achieve soff thrue htc dev right??? correct me if im wrong....
Click to expand...
Click to collapse
Why are you so adamant on achieving S-OFF now that were bootloader unlocked and we can flash full ROMS with the ability to flash the boot.img and flash the radios from within recovery there is absolutely nothing more that you need except for HTC to release the source. Once HTC releases the Source we can start getting custom kernels and AOSP ROMS can get moving.

Can someone post the ATT 1.73 radio ?
am uploading the ones for 1.82 and 1.85 now (it'll take a while)

Crappyvate said:
Can someone post the ATT 1.73 radio 0.16.32.09.01_3_10.79.32.08L ?
am uploading the ones for 1.82 and 1.85 now (it'll take a while)
Click to expand...
Click to collapse
Thanks...I'm like the other guy. Unlocked and on 1.73 running CleanRom 2.5...don't wanna relock to try the newer radio.

[Q] One X and question on firmware and HTC Dev bootloader unlocking

I am on my way to go and buy two At&t One x. They are currently still running 1.73 thankfully. Im not new to rooting or anything, just this device. My question is since its still on 1.73 should I unlock bootloader via HTC Dev, and will this mean i can always run a custom recovery and ROMS going forward?
Example: if bootloader is unlocked, can I then update a device to the most current (2.2 i believe) and still be able to have a custom recovery therefore run the ROM of my choice and even revert back to stock at will?
My goal is to keep it flexible and not lock myself out of an option because of an update. One of the devices is for my neice so I want her running stock for now, but would unlock the bootloader just as a safety net and to futureproof the device if we run some JB roms for her, or CM10. Any help would be greatly appreciate.
Im coming from a Nexus so Im not used to looking for exploits to run a ROM, well not since the EVO days. Thanks a plenty!

Honestly I wouldn't ever run the update on the phone. No reason to risk it as you can download the stock roms (or CleanROM) from the developers section and just flash it normally. This would be the most flexible.
Having said that, maybe someone else can chime in and answer your questions initial questions. I don't really know the answer.
Sent from my HTC One XL using xda app-developers app

Your lucky use one of the one click root methods there's some on xDA or some that I can givenu a link too.... Than go on to unlocked boot loader ...honestly of u want her to be stock put her on clean rom.

So you're saying I should root first and not use HTC boot loader unlock tool? I'm still trying to search for the answer to my questions as well. What's the best root method? I honestly would like to have a custom recovery, unlocked boot loader, and running stock 4.0.4 or better just to try it out first. Then find a good Rom . Any suggestions?
Sent from my HTC One X using Tapatalk 2

TheIowaKid said:
So you're saying I should root first and not use HTC boot loader unlock tool? I'm still trying to search for the answer to my questions as well. What's the best root method? I honestly would like to have a custom recovery, unlocked boot loader, and running stock 4.0.4 or better just to try it out first. Then find a good Rom . Any suggestions?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I would unlock your boot loader. Flash teamwin recovery project, and then flash a STOCK ROOTED rom, whether it be sense or cleanrom. This will remove the ota feature so you don't accidentally update your hboot
Using the HTC boot loader unlock method is fine, if you don't mind your warranty being void. If not try the manual version. All of these tutorials are available in the android development section.
Once your boot loader is unlocked you are good to go. Just DO NOT RUU to 2.20 or you will not be able to flash kernels and radios.
Sent from my One X using xda app-developers app

So even with an unlocked boot loader if I ota to 2.2 I'm screwed? Got it. So any suggestion on the best stock ROM and then a Jelly Bean ROM? Do the one click root methods work the best?
Sent from my HTC One X using Tapatalk 2

TheIowaKid said:
So even with an unlocked boot loader if I ota to 2.2 I'm screwed? Got it. So any suggestion on the best stock ROM and then a Jelly Bean ROM? Do the one click root methods work the best?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I was able to one click mine, however some users report they cannot use the one click method, but manual works for them.
Yes, never ruu to 2.20, even with an unlocked boot loader it will screw you over. If you ruu to 2.20 without supercid then you are just Sol completely.
As for stock ROMs, go try out Team Venoms ViperXL. Make sure you download "HTC One XL" and not "HTC One X" they are 2 different phones and flashing anything made for the One X will brick your One XL.
When it comes to jellybean, I am on MIUI because I like the iOS aspect of it. I still am a fan of Cyanogenmod, since that was the first aftermarket firmware I have used. So I would recommend CM10 unless you want a little more customization, then go with AOKP. I have never tried paranoid android, but it is a combination of CM10 and tablet display modes.
The One XL is codenamed "Evita" and the One X is codenamed "endeavour"
Sent from my One X using xda app-developers app

Are these ROMs fully functioning? Camera is important for me. I thought that CM10 wasn't quite there yet but I'm definitely going to check some of these out. I don't have a computer here so I can't do anything yet. Its killing me! Thanks again for all the suggestions, Ill take all the help I can get!
Sent from my HTC One X using Tapatalk 2

TheIowaKid said:
Are these ROMs fully functioning? Camera is important for me. I thought that CM10 wasn't quite there yet but I'm definitely going to check some of these out. I don't have a computer here so I can't do anything yet. Its killing me! Thanks again for all the suggestions, Ill take all the help I can get!
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Many of the sense ROMs are flawless.
The AOSP (Jellybean) ROMs are pretty stable, and camera does work on them.
CM10 is still in Nightly, but I think it'll be reaching a stable build soon.

absolutelygrim said:
As for stock ROMs, go try out Team Venoms ViperXL.
Click to expand...
Click to collapse
With a huge amount of awesome mods and customization options, I do not consider ViperXL to be a "stock ROM". Sense based, yes.
If the OP wants to stay strictly stock, there are flashable, pre-rooted versions of the most of the stock AT&T firmware versions.
But I think your point is a good one, that some of the custom ROMs build off of stock, while adding some optimizations and useful features, while keeping the stability of a stock ROM.
---------- Post added at 09:52 AM ---------- Previous post was at 09:43 AM ----------
TheIowaKid said:
So even with an unlocked boot loader if I ota to 2.2 I'm screwed?
Click to expand...
Click to collapse
The 2.20 hboot plugs the whole by which kernels and radios can be flashed via recovery. So flashing the kernel/boot.img requires flashing separately using adb every time you flash a ROM. Not sure about radios.
Really, there is no benefit to updating officially either by RUU or OTA. You gain nothing, and lose ability to flash kernel and radios via recovery.
Be sure to check out the index of all the resources (sticky at the top of the Development forum): http://forum.xda-developers.com/showthread.php?t=1671237

redpoint73 said:
With a huge amount of awesome mods and customization options, I do not consider ViperXL to be a "stock ROM". Sense based, yes.
If the OP wants to stay strictly stock, there are flashable, pre-rooted versions of the most of the stock AT&T firmware versions.
But I think your point is a good one, that some of the custom ROMs build off of stock, while adding some optimizations and useful features, while keeping the stability of a stock ROM.
---------- Post added at 09:52 AM ---------- Previous post was at 09:43 AM ----------
The 2.20 hboot plugs the whole by which kernels and radios can be flashed via recovery. So flashing the kernel/boot.img requires flashing separately using adb every time you flash a ROM. Not sure about radios.
Really, there is no benefit to updating officially either by RUU or OTA. You gain nothing, and lose ability to flash kernel and radios via recovery.
Be sure to check out the index of all the resources (sticky at the top of the Development forum): http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
Heh, I meant stock as in "sense based"
You know what I meant (I hope),
But he might not have, thanks for pointing that out
Sent from my One X using xda app-developers app

Yeah I knew what you meant! Like I said, not new to rooting and ROMs just knew to this device. Thanks again for the heads up on that thread. I'm going ROM crazy tonight once I root.
Sent from my HTC One X using Tapatalk 2

As said before - root, unlock bl, flash recovery and flash a rom, be it stock rooted or custom.
Don't update to 2.20 OTA.

Quick question but maybe off topic. Is the screenshot to MMS problem fixed with custom ROMs? I noticed that if I send a screen shot via MMS its so small the recipient can't see it. Maybe a bug just on 1.73? Annoying none the less!
Sent from my HTC One X using Tapatalk 2

TheIowaKid said:
Quick question but maybe off topic. Is the screenshot to MMS problem fixed with custom ROMs? I noticed that if I send a screen shot via MMS its so small the recipient can't see it. Maybe a bug just on 1.73? Annoying none the less!
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Can't answer that.. I can't send or receive MMS even though I have service and 4G LTE
But I don't think its an issue on AOSP
Sent from my One X using xda app-developers app

Sounds more like an APN issue in your case. I'd double check your APN or even delete and set it up again.
Sent from my HTC One X using Tapatalk 2

help with hboot

ive been on my comp for hours and i cant find a set answer
can i downgrade my hboot 1.14 running older ruu? example the 1.84 one or the 1.53
second......can i flash the wifi partitions for JB trickdroid with hboot 1.14
i would like just a positive straight answer.....please keep the negative off my thread as i have been searching......

Flipnfr3ak said:
ive been on my comp for hours and i cant find a set answer
can i downgrade my hboot 1.14 running older ruu? example the 1.84 one or the 1.53
second......can i flash the wifi partitions for JB trickdroid with hboot 1.14
i would like just a positive straight answer.....please keep the negative off my thread as i have been searching......
Click to expand...
Click to collapse
No and No.

Darknites said:
No and No.
Click to expand...
Click to collapse
Thank you. So gotta install ubunatato or what ever its called to downgrade
Sent from my HTC EVARE_UL using Tapatalk 2

Flipnfr3ak said:
Thank you. So gotta install ubunatato or what ever its called to downgrade
Sent from my HTC EVARE_UL using Tapatalk 2
Click to expand...
Click to collapse
Its Ubuntu haha.. Pretty awesome setup I use 12.04... If you decide to use it, install
64bit just in case you decide to try building from source.... I agree with the above answer as well.. You can not flash an ruu that is below your hboot.. The partitions will go through the motion of flashing but will not actually flash no matter how you try.. I've tried all three ways...to include flash image GUI and HTC dumlock...hope this helps
Sent from my HTC One S using xda premium

$droyd$ said:
Its Ubuntu haha.. Pretty awesome setup I use 12.04... If you decide to use it, install
64bit just in case you decide to try building from source.... I agree with the above answer as well.. You can not flash an ruu that is below your hboot.. The partitions will go through the motion of flashing but will not actually flash no matter how you try.. I've tried all three ways...to include flash image GUI and HTC dumlock...hope this helps
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
So another question. Is there any Rom I can flash with hboot 1.14 that the WiFi will work? I tried trickdroid, viper, zarboz's Rom.....non of them the WiFi worked.
Sent from my HTC EVARE_UL using Tapatalk 2

Flipnfr3ak said:
So another question. Is there any Rom I can flash with hboot 1.14 that the WiFi will work? I tried trickdroid, viper, zarboz's Rom.....non of them the WiFi worked.
Sent from my HTC EVARE_UL using Tapatalk 2
Click to expand...
Click to collapse
Energy rom, CM10, and paradroid (whatever it called)
but they are not a good rom for me..
I am in the same situation as you, because of there are not many roms for this garbage phone..
I am trying to selling it and get a popular phone which are easier to flash custom roms.
PS: HTC always make stupid phones, no wonder the company is going bankrupt.

Its funny how I have no issues whatsoever with my hboot 1.14.
Easier to flash custom roms? I flash roms the same way on all my devices - in recovery. The only difference with the S is i have to spend 5sec on typing "fastboot flash boot boot.img" before first boot up. Yea, hard stuff that
And... why did you buy it if you think htc only makes stupid phones? Makes no sense to me...

Goatshocker said:
Its funny how I have no issues whatsoever with my hboot 1.14.
Easier to flash custom roms? I flash roms the same way on all my devices - in recovery. The only difference with the S is i have to spend 5sec on typing "fastboot flash boot boot.img" before first boot up. Yea, hard stuff that
And... why did you buy it if you think htc only makes stupid phones? Makes no sense to me...
Click to expand...
Click to collapse
becoz it's the flagship phone on Tmobile store 10months ago..

Flipnfr3ak said:
So another question. Is there any Rom I can flash with hboot 1.14 that the WiFi will work? I tried trickdroid, viper, zarboz's Rom.....non of them the WiFi worked.
Sent from my HTC EVARE_UL using Tapatalk 2
Click to expand...
Click to collapse
You should get WiFi on almost all ICS ROMs.. If the base rom is your hboot or lower..
Sent from my HTC One S using xda premium

Just for informational purposes, I was having the same problems: serious problems with Wi-Fi on several different ROMS. I also have hboot 1.14. I'm currently running CM10 and installed a custom kernel and it seems to have fixed the problem.
Sent from my HTC One S using Tapatalk 2

Most wifi issues revolve around t-mobile phones I believe. It often relates to the 2.35 update. Others did not have these issues.
You can also solve via superCID and flash another RUU (that has a similar level of bootloader).
But yes, a bootloader downgrade will solve this, since then you can flash other wifi partitions (even the Jelly Bean ones).
Alternatively you can wait for the OTA upgrade to Jellybean.

Goatshocker said:
Its funny how I have no issues whatsoever with my hboot 1.14.
Easier to flash custom roms? I flash roms the same way on all my devices - in recovery. The only difference with the S is i have to spend 5sec on typing "fastboot flash boot boot.img" before first boot up. Yea, hard stuff that
And... why did you buy it if you think htc only makes stupid phones? Makes no sense to me...
Click to expand...
Click to collapse
I got it because it was the best hardware out at the time and not for Sense.
---------- Post added at 02:39 PM ---------- Previous post was at 02:37 PM ----------
AKToronto said:
Most wifi issues revolve around t-mobile phones I believe. It often relates to the 2.35 update. Others did not have these issues.
Click to expand...
Click to collapse
Ya its seems that to me too.

Well I moved from T-Mobile and went to att so I'm trying to sell the phone but I have particular buyer that wants it rooted and they'll pay the full price if I can get viper or a Jb Rom on it. Ok so ill attempt the hboot downgrade.
Sent from my HTC EVARE_UL using Tapatalk 2

[Q] Change radio with hboot more 1.14

Hey everybody,
I have a simple question.
What happens if i flash a new radio on hboot 1.14 and that doesn't work? Possibility to brick the phone?
Or just don't work and i keep my old radio?
Ty for your help!!
.

Im quite sure it simply wont flash/install.

Ty for your answer.
Ok so i flash the zip and all is ok. I reboot but i have always the old radio.
Sent from my HTC One S using xda app-developers app

Neugaine said:
Ty for your answer.
Ok so i flash the zip and all is ok. I reboot but i have always the old radio.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thats correct. You can try to flash it but it wont actually work. The only way to use a different radio on a higher hboot (besides OTA updates and RUUs) is to go to an AOSP ROM. They hold radio files in a different location (there is a CM10 radio flasher in the development forums). This still wont replace the underlying radio on your phone (which will be there if you go back to SENSE base ROMs). But it will allow you to try out different radios.

Not brick, only don't install

you don't tell us what rom you are on--
either way, read this thread
http://forum.xda-developers.com/showthread.php?t=1998270
some have flashed radios on to sense roms with .14 hboot with the installer
read/scan whole thread
the last post talks about the Tempory Installer

rugmankc said:
you don't tell us what rom you are on--
either way, read this thread
http://forum.xda-developers.com/showthread.php?t=1998270
some have flashed radios on to sense roms with .14 hboot with the installer
read/scan whole thread
the last post talks about the Tempory Installer
Click to expand...
Click to collapse
+1
Now any hboot can flash radios on sense, using the CM10 installer.
HTC_One_S | 1.06_Bootloader_Downgrade | Xparent_ICS_Tapatalk_2.4.1 | MIUI_Sense_Based | Beastmode_BRICKED_rc5

Yes!! Tyvm!! I flash new radio with hboot 1.14!! Without problem! Thanks for help!
Sent from my HTC One S using xda app-developers app

[Q] Can Rooted and Unlocked xl get OTA update?

If, and I mean if ATT ever updates to 4.1 would I be able to load that if I choose or would I
have to re-lock??
T

as long as you stay on the stock room you should get the OTA update. Issue though is, you might lose root and possibly your unlock

trevorb21 said:
If, and I mean if ATT ever updates to 4.1 would I be able to load that if I choose or would I
have to re-lock??
T
Click to expand...
Click to collapse
If you're going to root and unlock, you should forget about OTAs. You may get one, but taking it when you're rooted can brick your phone. There's no need to take one anyway, since pre-rooted versions usually show up in the Development section that day.

If your CID is 11111111 and you take the OTA, your phone will most likely brick.. so avoid it

Thanks all... actually went back to CM 10 last night. I had relocked and everything hoping for an update someday but I couldn't help it and had to go back to Cm. Battery life seems much better on the latest nightly compared to the stable version.
Sent from my One X using xda app-developers app

If a rooted / hboot 1.14 bootloader unlocked phone with super CID is unable to take an OTA without bricking, how does one get a new radio, wifi firmware, etc.? Please don't say downgrading hboot, because I am already familiar with that somewhat dangerous approach. Others are suggesting that if one's bootloader is relocked and a stock ruu flashed, OTAs are safe. Is this not true?
Sent from my HTC One X using xda premium

tlazarus said:
If a rooted / hboot 1.14 bootloader unlocked phone with super CID is unable to take an OTA without bricking, how does one get a new radio, wifi firmware, etc.? Please don't say downgrading hboot, because I am already familiar with that somewhat dangerous approach. Others are suggesting that if one's bootloader is relocked and a stock ruu flashed, OTAs are safe. Is this not true?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I bricked after relocking and running ruu but to be fair I downgraded my hboot to 1.09 and am not sure if that had anything to do with it.. good luck..dunno why you would want the ota anyway.

It is not that I necessarily want the OTA. I am concerned that an important radio update will come along, or something else that requires a full ruu, and I will be SOL. This HTC thing is driving me crazy - my Atrix was so easy to work with. I have yet to see a jb ROM that was 100% stable for 100% of people, so not having the option of using a stock ruu if it is available scares me.
Sent from my HTC One X using xda premium

tlazarus said:
It is not that I necessarily want the OTA. I am concerned that an important radio update will come along, or something else that requires a full ruu, and I will be SOL. This HTC thing is driving me crazy - my Atrix was so easy to work with. I have yet to see a jb ROM that was 100% stable for 100% of people, so not having the option of using a stock ruu if it is available scares me.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I have noticed that typically when things are not stable right away for me it was a bad download or just a bad flash. A stock based ROM like viper has always been stable for me and am currently using paranoid android also perfectly stable. In any case, once the source for the ota is released devs will most likely use that as a base for their next upgrades so I really wouldn't worry about it.

mirGantrophy said:
If your CID is 11111111 and you take the OTA, your phone will most likely brick.. so avoid it
Click to expand...
Click to collapse
My CID is 11111111 and I have taken many OTA's. I have switched and changed ROM's and reRUU'ed many times. From Hong Kong to German to Telstra. Taking OTA's all over the place. I would say my phone has at least done 8 official HTC OTA's.
Not once has it bricked.
Is it some check AT&T ROM's do?
Personally I have found unlocked bootloader and supercid do not effect an OTA. Modifications to /system are more likely to be troublesome. They are likely to be lost or could even make the update fail.

See, this is exactly why I can't necessarily trust much of what I hear about the HOX. I wish the official resources thread would answer this, and the answer woud be provided by experienced HOX devs.

tlazarus said:
See, this is exactly why I can't necessarily trust much of what I hear about the HOX. I wish the official resources thread would answer this, and the answer woud be provided by experienced HOX devs.
Click to expand...
Click to collapse
You're just unintelligent...

tlazarus said:
See, this is exactly why I can't necessarily trust much of what I hear about the HOX. I wish the official resources thread would answer this, and the answer woud be provided by experienced HOX devs.
Click to expand...
Click to collapse
Trust at&t they know what's best for your type
Sent from my HTC One XL

954wrecker said:
Trust at&t they know what's best for your type
Sent from my HTC One XL
Click to expand...
Click to collapse
Wow - you guys are so helpful. What exactly is my type? Someone who knows enough about hardware to believe that there is more than just front end changes included in some OTA/RUU updates? Turge had to include a wifi update to make Viper stable for some people. I am sure you two knew exactly what the problem was as soon as the ROM came out, including all of the necessary changes, the partitions involved, etc. You've pretty much just proved you are idiots if you believe that there is nothing else included in an RUU other than system and hboot updates.
Oh, and thanks for making me miss the Atrix forum some more. The people were actually nice there. I didn't realize that I should check out the XDA forums before buying a phone - the Nexus folks can't be any worse than you two.

tlazarus said:
Wow - you guys are so helpful. What exactly is my type? Someone who knows enough about hardware to believe that there is more than just front end changes included in some OTA/RUU updates? Turge had to include a wifi update to make Viper stable for some people. I am sure you two knew exactly what the problem was as soon as the ROM came out, including all of the necessary changes, the partitions involved, etc. You've pretty much just proved you are idiots if you believe that there is nothing else included in an RUU other than system and hboot updates.
Oh, and thanks for making me miss the Atrix forum some more. The people were actually nice there. I didn't realize that I should check out the XDA forums before buying a phone - the Nexus folks can't be any worse than you two.
Click to expand...
Click to collapse
Thank you for giving me a good laugh... The forums being kind and your intelligence level are directly proportional...because you're a stuck up noob you are getting the treatment you deserve...and your type is for the iPhone or better yet a flip phone from a couple years back you won't have to worry about software changes on that...I'm still kind curious what you're trying to get at? I'm a bit confused how you're comparing hardware and ruu and ota

Okay, really not sure how I am a stuck up noob. Or unintelligent, as I am perfectly capable of reading lots of threads where people who seem to know what they are talking about argue over one's ability to go back to stock using a RUU. I was merely looking for confirmation from more than one person that I could go back to stock using a RUU and then apply the OTA if necessary. My point was simply that if something came out that was not possible to implement via a ROM - i.e. a radio update, I wanted the ability to flash it. Without downgrading hboot, it appears that anyone with hboot 1.14 is STUCK WITH THEIR PRESENT RADIO. There is conflicting info out there regarding one's ability to go back to stock using an RUU and then apply the OTA in the future, and I was merely trying to confirm that this was possible. If you look in this thread, you will see one person say it is perfectly safe, and another that it will brick the phone. Care to decide who is right? I generally like to get a few opinions before I task a risk, but apparently you don't get that. It is a perfectly reasonable question.

Here's a straight answer.... That's a bit risky going back to stock through ruu than applying an ota I've seen many people brick that way idk if it's just because the cid is 11111111 or whatever but there's something in the system that the ota doesn't like and than rejects..though I do not see the point of doing an ota esepcially many involve huge security updates ie hboot as you stated which will probably result in no root. . I can confidently assure you att will bring out a new nazi hboot out with the jb update too...so my advice would be to stick to non stock and enjoy

Thanks - I appreciate the response. Still a bit concerned about being stuck on my present radio, but perhaps that will get resolved in the future. Have a great weekend.

I'm sire your aware but you can downgrade hboot

Thanks, yes. I've read the entire downgrade thread a few times. It appears that more than one person has bricked their phone, and that isn't a risk I can take right now.