[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.

Originally Posted by twistedddx

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.

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


These are radios for flashing in Sense. 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 (0.17.32.09.12_10.86.32.08L) :
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): http://d-h.st/rTj - thanks to jac0b and twistedxx!
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

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 Latest CM10.x based ROMs (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=UT...2acfff78edb974
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....

Originally Posted by rpomponio

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....

I think only a handful did, mine didn't.

Sent from my HTC One X using xda premium

Originally Posted by rpomponio

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....

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!!

Originally Posted by rpomponio

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....

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?

Originally Posted by Mosch26

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

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

Originally Posted by taylor.fowler

Looking for any one in particular?

the ones from 1.82 and 1.85 would be great!