I have a Rogers HTC one x with bootloader unlocked, root, and S-off. I'd like to install a rogers Radio on it but after hours of searching I still cannot find a flashable zip of the radio. I do have the Radio.img from the OTA update... Is there some way I can make that into a TWRP flashable zip? Otherwise, does anyone know where I can get this radio in a TWRP flashable zip? - HTC ROGERS 1.94 (0.18as.32.09.28_L_10.103.32.24L)?
If that isn't possible, can somebody please explain if/how I can flash the radio.img via fastboot? Despite being in rebootRUU, I get FAILED <remote: not allowed> when trying to fastboot flash the radio. Currently my hboot is 1.09, and I'm running ViperXL 4.2.0.
Can't tell you how to flash an extracted radio.img. But keep in mind that just because you have the Rogers version, that does not require you to use a Rogers intended radio, nor does that even mean that a Rogers radio will give you the best performance (reception, battery, etc.).
In fact, older radios are known to not play well with the Power save function on Sense 5 ROMs. Although a minority of folks have reported worse reception on Sense 5 radios, and better performance on older Sense 4+ radios. But this is the exception, majority of folks will have more success sticking to Sense 5 radios with Sense 5 ROMs.
The radio isn't your problem, it's your firmware. You need to get s-off so you can update your firmware.
Sent from my Evita
hi. i've got a hoxl with signal loss issue right now.
the first thing i thought is to update via ota but i still have issue.
so i was going to flash radio and i saw your reply.
i don't understand if and how i can fix it... could you give me more details?
the hoxl is swisscom branded, already s-off and supercid, last fw over ota.
please let me know...
no, i can exclude the coverage because i have also a galaxy i9505 and it is fine with the same sim.You're already on the correct firmware. You could try flashing a different radio but the problem may be with your coverage from your provider rather than the phone itself.
Sent from my Evita
It's possible that it's the antenna, but I'd flash a radio first to count that out before changing hardware.
Sent from my Evita
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.
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...