Q&A for [Radio][RIL]HOXL Radios/RILs including CM10.x based ROMs (Flashable zips)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Radio][RIL]HOXL Radios/RILs including CM10.x based ROMs (Flashable zips). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hi,
I recently Installed CyanogenMod 11 (R12) and I have calls drops and my WiFi stop working often (even though it looks like it currently connected). I was reading that switching the Radio might solve it, but the first post left me a bit confused, and I want to make sure I'm not going to brick my device. First, here's my current setup:
HTC One X AT&T
HBoot 2.18 (S-off)
CyanogenMod 11 (R12)
Radio: 1.35a.32.45.27_10_144.32_34aL
And here are my questions:
1. The phone of-course was bought in America, but I'm using it out of the states with a local carrier. I noted the Radios listed on the front page have Carrier name assigned to them, like Telstra, Telus, AT&T, Vodaphone etc. Those can work with my local carrier? or only with the carriers listed? Should I just try them all or some considered to have more chances to have fit for much people?
2. Are any of those even good for CM11 as it mentioned they should be used with CM10 and beyond. Is beyond is CM11 also?
3. I'm not 100% sure I understand what NIL is. I flashed Radio previously on an older phone, and all I had to do was to flash it using Fastboot. Or those are zip that you flash from Recovery?
4. I didn't notice my current Radio on the List. Why is that? I'm worried I might need to come back to it and I won't have it available.
Thanks!
Okiba said:
Hi,
I recently Installed CyanogenMod 11 (R12) and I have calls drops and my WiFi stop working often (even though it looks like it currently connected). I was reading that switching the Radio might solve it, but the first post left me a bit confused, and I want to make sure I'm not going to brick my device. First, here's my current setup:
HTC One X AT&T
HBoot 2.18 (S-off)
CyanogenMod 11 (R12)
Radio: 1.35a.32.45.27_10_144.32_34aL
And here are my questions:
1. The phone of-course was bought in America, but I'm using it out of the states with a local carrier. I noted the Radios listed on the front page have Carrier name assigned to them, like Telstra, Telus, AT&T, Vodaphone etc. Those can work with my local carrier? or only with the carriers listed? Should I just try them all or some considered to have more chances to have fit for much people?
2. Are any of those even good for CM11 as it mentioned they should be used with CM10 and beyond. Is beyond is CM11 also?
3. I'm not 100% sure I understand what NIL is. I flashed Radio previously on an older phone, and all I had to do was to flash it using Fastboot. Or those are zip that you flash from Recovery?
4. I didn't notice my current Radio on the List. Why is that? I'm worried I might need to come back to it and I won't have it available.
Thanks!
Click to expand...
Click to collapse
1. The radios don't have to be used with the carrier that's listed in the name. For example, I can use an at&t radio on my Telstra network.
2. Yes, CM10 and beyond means Jelly Bean and newer, so 4.1+.
3. Where does it mention NIL? Do you mean RIL? If so, don't ever use those ones (radio + RIL). All of these radio zips are flashed in recovery.
4. Because this device is pretty much dead now so new zips aren't being created.
Transmitted via Bacon
timmaaa said:
1. The radios don't have to be used with the carrier that's listed in the name. For example, I can use an at&t radio on my Telstra network.
2. Yes, CM10 and beyond means Jelly Bean and newer, so 4.1+.
3. Where does it mention NIL? Do you mean RIL? If so, don't ever use those ones (radio + RIL). All of these radio zips are flashed in recovery.
4. Because this device is pretty much dead now so new zips aren't being created.
Transmitted via Bacon
Click to expand...
Click to collapse
Yes, sorry - I meant RIL
So It it save to save I can flash any of the 12 Radios from the first section and be OK? Randomly? or if I'm outside of the US I should first try the non-us Carriers?
By the way, I didn't have those issues with the last Rom I used. I recently upgraded from HBOOT 2.14 to 2.18 by Cyanogen Mod recommendation, before I flashed the CM Mod. Does Radios work differently on different roms? or perhaps its the HBOOT upgrade?
Thanks again.
Okiba said:
Yes, sorry - I meant RIL
So It it save to save I can flash any of the 12 Radios from the first section and be OK? Randomly? or if I'm outside of the US I should first try the non-us Carriers?
By the way, I didn't have those issues with the last Rom I used. I recently upgraded from HBOOT 2.14 to 2.18 by Cyanogen Mod recommendation, before I flashed the CM Mod. Does Radios work differently on different roms? or perhaps its the HBOOT upgrade?
Thanks again.
Click to expand...
Click to collapse
Yes, technically you can flash any of the radios from the top section. However, you can't at the same time. If you're on recent firmware (2.15 or above) then you can only use radios 1.3x and above.
It doesn't matter whether they're US carrier radios or non-US carrier radios, the only way you'll know which is best is by doing thorough testing on each of them (testing radio performance and battery drain).
Transmitted via Bacon
timmaaa said:
Yes, technically you can flash any of the radios from the top section. However, you can't at the same time. If you're on recent firmware (2.15 or above) then you can only use radios 1.3x and above.
It doesn't matter whether they're US carrier radios or non-US carrier radios, the only way you'll know which is best is by doing thorough testing on each of them (testing radio performance and battery drain).
Transmitted via Bacon
Click to expand...
Click to collapse
I see. Well, it seems all the top section is already above 1.3x, so I can test those all. Is there any Radio performance Apps that I can use to test it properly?
Can you comment on the other issues I mentioned? why did the WiFi issues started on CyanogenMod? is it because some Roms acts differently with specific Radio firmware, or because the HBoot upgrade and If I'll to revert back to my old Rom i'll have the same issue?
Okiba said:
I see. Well, it seems all the top section is already above 1.3x, so I can test those all. Is there any Radio performance Apps that I can use to test it properly?
Can you comment on the other issues I mentioned? why did the WiFi issues started on CyanogenMod? is it because some Roms acts differently with specific Radio firmware, or because the HBoot upgrade and If I'll to revert back to my old Rom i'll have the same issue?
Click to expand...
Click to collapse
Sorry, I wasn't very clear. There are only two in the top list that are 1.3x or above, we go by the radio version number, not the firmware in which it resides. See the bold part below:
HTC VODAPHONE 3.17.162.8 (1.27a.32.45.28_10.135.32.34a)
I don't know of any apps for testing radio performance, I usually just flash one and regularly note the signal strength. Signal strength is found in Settings/About Phone/Status, and measured in decibels. The values are in negative so remember that -51dBm is good strength and -110dBm is weak.
I honestly don't know why your WiFi is acting up, it could be due to the radio, it could be due to the ROM, only thorough testing of different ROM/radio combinations will really answer that question.
Transmitted via Bacon
timmaaa said:
Sorry, I wasn't very clear. There are only two in the top list that are 1.3x or above, we go by the radio version number, not the firmware in which it resides. See the bold part below:
HTC VODAPHONE 3.17.162.8 (1.27a.32.45.28_10.135.32.34a)
I don't know of any apps for testing radio performance, I usually just flash one and regularly note the signal strength. Signal strength is found in Settings/About Phone/Status, and measured in decibels. The values are in negative so remember that -51dBm is good strength and -110dBm is weak.
I honestly don't know why your WiFi is acting up, it could be due to the radio, it could be due to the ROM, only thorough testing of different ROM/radio combinations will really answer that question.
Transmitted via Bacon
Click to expand...
Click to collapse
Oh, I see. So basically I can only test those:
HTC TMobile-Germany 5.08 (1.31a.32.45.16_2)
HTC VodaPhone 5.06 (1.31a.32.45.16_2_10)
Is there anyway I can backup my current Radio? so I can revert back if any of those won't work? I couldn't find it on the list nor online.
Okiba said:
Oh, I see. So basically I can only test those:
HTC TMobile-Germany 5.08 (1.31a.32.45.16_2)
HTC VodaPhone 5.06 (1.31a.32.45.16_2_10)
Is there anyway I can backup my current Radio? so I can revert back if any of those won't work? I couldn't find it on the list nor online.
Click to expand...
Click to collapse
I'm sure there's a way to back it up or extract it but I can't for the life of me remember how.
Transmitted via Bacon
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
Actually, if you're on the 2.18 firmware you can either run the 5.18 RUU to get it back or you can just flash the 2.18 firmware package.
Transmitted via Bacon
timmaaa said:
I'm sure there's a way to back it up or extract it but I can't for the life of me remember how.
Transmitted via Bacon
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
Actually, if you're on the 2.18 firmware you can either run the 5.18 RUU to get it back or you can just flash the 2.18 firmware package.
Transmitted via Bacon
Click to expand...
Click to collapse
Oh, so the HBOOT Update change the Radio? that explains the sudden change in Radio quality. The radio has been changed I'm guess. Oh, I hope the other two options will be better, or else I'll have to downgrade the HBOOT.
I'll update when it's done. Thanks again
It isn't just the hboot that was changed, it was the entire firmware. It's just referred to by the hboot number usually.
Transmitted via Bacon
Hey folks, long time no see!
If you want to back up your radio, and are comfortable with running commands in adb shell then just run this:
adb shell
su
dd if=/dev/block/mmcblk0p17 of=/sdcard/radio_backup.img
It will write a copy of the existing radio partition into an img file on your sdcard.
Big thank you again to @timmaaa for holding it down in here. Happy HOXing.
timmaaa said:
I'm sure there's a way to back it up or extract it but I can't for the life of me remember how.
Transmitted via Bacon
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
Actually, if you're on the 2.18 firmware you can either run the 5.18 RUU to get it back or you can just flash the 2.18 firmware package.
Transmitted via Bacon
Click to expand...
Click to collapse
Okiba said:
Oh, I see. So basically I can only test those:
HTC TMobile-Germany 5.08 (1.31a.32.45.16_2)
HTC VodaPhone 5.06 (1.31a.32.45.16_2_10)
Is there anyway I can backup my current Radio? so I can revert back if any of those won't work? I couldn't find it on the list nor online.
Click to expand...
Click to collapse
Thanks for the help Taylor. Sadly enough I was only reading it after changing my Firmware.
@timmaaa - You mentioned I can revert to my old Radio if I'll re-flash the Firmware. I have the firmware file (evita_firmware_5.18.502.1.zip) from the Cyanogenmod Website. I already reflash it once before. Can I reflash it even though I already flashed and my HBOOT version is already 2.18? (just to get the default Radio version)
Okiba said:
Thanks for the help Taylor. Sadly enough I was only reading it after changing my Firmware.
@timmaaa - You mentioned I can revert to my old Radio if I'll re-flash the Firmware. I have the firmware file (evita_firmware_5.18.502.1.zip) from the Cyanogenmod Website. I already reflash it once before. Can I reflash it even though I already flashed and my HBOOT version is already 2.18? (just to get the default Radio version)
Click to expand...
Click to collapse
I thought you meant the radio that you were currently on, not the radio you were previously on.
timmaaa said:
I thought you meant the radio that you were currently on, not the radio you were previously on.
Click to expand...
Click to collapse
I'm not sure exactly what you mean...
Okiba said:
I'm not sure exactly what you mean...
Click to expand...
Click to collapse
From what I understand you would like to return to the radio you were on prior updating your firmware, is that correct?
timmaaa said:
From what I understand you would like to return to the radio you were on prior updating your firmware, is that correct?
Click to expand...
Click to collapse
Oh, no. This will require me to downgrade the HBOOT also right? and the way to do it is by installing the 5.18 RUU?
What I mean is that when I upgraded to 2.18 using the CyanogenMod firmware zip, It also applied a specific Radio version that I can't find online. Can I just flash again the Firmware zip from "fastboot oem rebootRUU" mode? or I should not try to apply the same HBOOT again just for to get the Radio out of it?
Okiba said:
Oh, no. This will require me to downgrade the HBOOT also right? and the way to do it is by installing the 5.18 RUU?
What I mean is that when I upgraded to 2.18 using the CyanogenMod firmware zip, It also applied a specific Radio version that I can't find online. Can I just flash again the Firmware zip from "fastboot oem rebootRUU" mode? or I should not try to apply the same HBOOT again just for to get the Radio out of it?
Click to expand...
Click to collapse
Ok, I was misunderstanding you. Yes, you just flash that firmware package again to get the radio back.
Transmitted via Bacon
timmaaa said:
Ok, I was misunderstanding you. Yes, you just flash that firmware package again to get the radio back.
Transmitted via Bacon
Click to expand...
Click to collapse
Great. Thanks again tiammaaa!
@timmaaa - Sorry to bother you again, but I gave up on the 2.18 HBoot version I think. There's not too many Radio options, and I didn't have WiFi issues with my older HBOOT (I think It was 2.14). I'm not sure I fully understand Cyanogenmod Evita instructions - they urged "AT&T Users" to upgrade into HBOOT 2.18, I guessed I am an AT&T user as my HTC one X is made by AT&T, but perhaps they meant AT&T CARRIER users?
At any rate, I'm not sure to which HBOOT I should downgrade to.
1. Is there any real difference in HBOOT except the type of Radios you can use? does some HBOOTs perform better then other HBOOT versions?
2. I want to try use KarbonKat rom, and on the first page, Soenisti mentions his using Firmware 5.14.61.2-3.17.61.1. Can I know which HBOOT is it? Can I flash it from within the Recovery? or do I need to flash it like mentioned in the Cyanogen instruction webpage using fastboot commandline? should I even flash it or there is I'll brick my phone?
Thanks again!
Related
hi there,
I have Hboot 1.08, is there any flash-able zip files to update the radio?
Check the op of the OTA update thread in this very section
Sent from my HTC One S
ultimul said:
hi there,
I have Hboot 1.08, is there any flash-able zip files to update the radio?
Click to expand...
Click to collapse
The answer is yes, so do as Pheroh says
Try to either flashing through recovery or manually dd-ing the image files.
Don't take an OTA or run an RUU, as that will update your HBOOT.
You want to stay on 1.08.
-Jobo
I dont want the OTA update, anyway the phone is rooted and using custom rom so dont think ota will ever work.
where can I find the latest radio, zip files flashable thru recovery or fastboot?
touch of jobo said:
Try to either flashing through recovery or manually dd-ing the image files.
Don't take an OTA or run an RUU, as that will update your HBOOT.
You want to stay on 1.08.
-Jobo
Click to expand...
Click to collapse
ultimul said:
I dont want the OTA .. where can I find the latest radio, zip files flashable thru recovery or fastboot?
Click to expand...
Click to collapse
This is the thread Pheroh was referring to: OTA Update to Android 4.0.4 for S4 is Out! You can extract the images from the OTA .zip or use any of the methods explained in post #1.
I used the one by Dima901 and flashed thru twrp
https://www.dropbox.com/s/zvi1a70n41yy2ri/radio_OTA_19072012.zip
rugmankc said:
I used the one by Dima901 and flashed thru twrp
]
Click to expand...
Click to collapse
10x a lot;
flashed thru recovery in no time.
hope will solve the few little problems with data and Bluetooth I had.
It has helped many from reading posts. I am not sure I gained anything though.
But, always nice to have latest anything--
rugmankc said:
It has helped many from reading posts. I am not sure I gained anything though.
But, always nice to have latest anything--
Click to expand...
Click to collapse
I can only hope will improve something. I have a problem with data switching from G to 3G to H for few seconds when I first start every session, I dont know it has impact on actually speed;
most annoying is the Bluetooth dropout from time to time, even at (very) short distances, my earpiece has no problem cause i tested with my other phones.
Anyway, if things goes wrong I still can go back to 0.16 radio I had before ( I hope at least )
Yes, flashing radios is Rom independent. Just don't upgrade to hboot .13 or higher. Or, you will have issues flashing radios. Hope new radio helps.
rugmankc said:
Yes, flashing radios is Rom independent. Just don't upgrade to hboot .13 or higher. Or, you will have issues flashing radios. Hope new radio helps.
Click to expand...
Click to collapse
for the moment I use trickdroid 6.0, probably I'll change in the future if support and updates stop;
from what I know, changing rom's shouldn't change the hboot, only ruu upgrade will change it. true?
correct-
radios and hboots stay unless flashing a ruu
if/when we get s-off then hboot can be changed and we will be able to adjust partition table sizes for more data size
first day of testing, results are confusing
the data icon stays now mostly at 3G, think this is the real provider network; the differences in speed are not noticeable
for the bluetooth, the same thing, earpiece disconnect after few minutes even if with the phone in my hand; something is wrong here; I'll have to look for my older earpiece to try it. maybe plantronics 520 is not fully compatible with htc one s
should I try a custom kernel? any chance will help?
I had the Bluetooth disconnect issue . Haven't flashed a radio yet but flashing the Sensisimo Rom has seem to have fixed the Bluetooth disconnect. Fix could have something to do with the Rom being based off the latest update available (2.21 or something like that). I'm having data disconnect issues, does new radio fix it?
T-MobileUS HTC One S
I would try it, no harm done
looks like bloetooth disconnect is a small bug in trickdroid 6.0; tried another 2 earpieces and all are doing the same;
just flash trickdroid 7.1.0, I'll try it tomorrow and came back with feedback.
Hey Guys...
i updated my HTC One S (S4) to CM10 (stabile), but now there is no radio....
and after downgrade to an old nightly, now there is also no radio...
HTC One S (S4)
HBoot ist 1.13
Radio ist 0.16.31501S.17_2
I hope somebody can help me....i need the phone..
thanks and regards
anilini
anilini said:
Hey Guys...
i updated my HTC One S (S4) to CM10 (stabile), but now there is no radio....
and after downgrade to an old nightly, now there is also no radio...
HTC One S (S4)
HBoot ist 1.13
Radio ist 0.16.31501S.17_2
I hope somebody can help me....i need the phone..
thanks and regards
anilini
Click to expand...
Click to collapse
Did you fastboot flash the boot.img? The radio is part of CM10, so you need to flash special zip files found in the CM threads (where this should have been posted) to get your EU radio back (CM10 uses the US radio by default, regardless of what your bootloader says...check it yourself in settings/phone.)
el_smurfo said:
Did you fastboot flash the boot.img? The radio is part of CM10, so you need to flash special zip files found in the CM threads (where this should have been posted) to get your EU radio back (CM10 uses the US radio by default, regardless of what your bootloader says...check it yourself in settings/phone.)
Click to expand...
Click to collapse
Yes i flashed the boot.img...
where can i find zip for EU radio..(I can't find it)..and I'm not sure, I can flash it, because: HBoot 1.13
my settings/phone shows now:
baseband: 1.08ts.50.0216_10_08e.50.04L
Kernel: 3.0.51-geb1844c
http://forum.xda-developers.com/showthread.php?p=34041485
Does CM10 always choose US radio when you install it, no matter what? Or is this specific to this situation? It seems like a strange oversight if that's the case.
Mekuso said:
Does CM10 always choose US radio when you install it, no matter what? Or is this specific to this situation? It seems like a strange oversight if that's the case.
Click to expand...
Click to collapse
It includes the latest radio by default, which happens to be from the latest US release. I believe the opinion is that the radio is region independent...It's actually a very cool feature, as even those with high hboot version can replace their radios, they just have to do it with each ROM flash.
el_smurfo said:
It includes the latest radio by default, which happens to be from the latest US release. I believe the opinion is that the radio is region independent...It's actually a very cool feature, as even those with high hboot version can replace their radios, they just have to do it with each ROM flash.
Click to expand...
Click to collapse
thx for support and the link...i tried all 3 EU-versions, but it does not work for me .. still no signal
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
Hi,
I want to flash an AT&T One X to some of the latest jelly bean ROMs (MIUI in particular). The phone is currently rooted with the old firmware. I've read all the guides and I'm unclear as to how to upgrade the firmware on existing root.
Since its currently rooted, do I just flash one of the new ROMs and I'm updated to new firmware?
Or do I do RUU first to new firmware and re-root? (Do I use the original bin file from first root?) If so, is there a guide for this around?
Thanks for the help
Is your bootloader unlocked, and do you have TWRP installed?
If so, flashing JB is like flashing any other ROM (no need to RUU, and no benefit at all to do so). Just move the ROM to the phone's SD card, then flash from recovery. If on hboot 1.14, you will need to extract boot.img from the ROM zip, and flash with fastboot.
This will likely answer many of your questions: http://forum.xda-developers.com/showthread.php?t=1952076
Also, its customary (and useful) to have some information about the question you are asking in your thread title, not just [Q].
Sputnikk23 said:
Hi,
I want to flash an AT&T One X to some of the latest jelly bean ROMs (MIUI in particular). The phone is currently rooted with the old firmware. I've read all the guides and I'm unclear as to how to upgrade the firmware on existing root.
Since its currently rooted, do I just flash one of the new ROMs and I'm updated to new firmware?
Or do I do RUU first to new firmware and re-root? (Do I use the original bin file from first root?) If so, is there a guide for this around?
Thanks for the help
Click to expand...
Click to collapse
Just flash the new rom. You wouldn't want to update your firmware because then you would have to flash the boot.img seperately in fastboot, and you would n't be able to flash radios, or boot animations at all. In fact many people have downgraded their firmware to the old version because of these annoyances.
redpoint73 said:
Is your bootloader unlocked, and do you have TWRP installed?
Click to expand...
Click to collapse
yes bootloader is unlocked and TWRP installed
If so, just move the ROM to the phone's SD card, then flash from recovery. If on hboot 1.14, you will need to extract boot.img from the ROM zip, and flash with fastboot.
Click to expand...
Click to collapse
and that would update the phones firmware to 2.20 but still have hboot 1.14 - which I understand is the preferred version? The RADIO thread says you can't flash radios unless on CM10 with the newer hboot. I'd like to update the phone to the latest and greatest radio too, I'd be safe doing that then?
Also, its customary (and useful) to have some information about the question you are asking in your thread title, not just [Q].
Click to expand...
Click to collapse
Total duh moment...
Edit: crap. can't find a way to edit title. sorry. thanks for answering.
Sputnikk23 said:
and that would update the phones firmware to 2.20 but still have hboot 1.14 - which I understand is the preferred version? The RADIO thread says you can't flash radios unless on CM10 with the newer hboot. I'd like to update the phone to the latest and greatest radio too, I'd be safe doing that then?
Click to expand...
Click to collapse
Firmware and ROM are the same thing. Once you flash a ROM, it formats the system partition and installs the new ROM/firmware. The old firmware is wiped, and new one installed.
Firmware number reported in Settings is somewhat irrelevant when you flash a custom ROM. It will say whatever the dev makes it say, such as MIUI 2.12 etc. The custom ROM might be based on an official firmware number (such as JB 3.17) but its been modded by the dev, so its not really the same firmware anymore. The ROM thread will tell you what firmware version its based on. If you want JB, its going to be based on fimrware 3.xx.
Installing custom ROMs does not touch hboot. The only way to downgrade hboot is with the JET kit in the Development forum, which requires a Linux computer.
redpoint73 said:
Firmware and ROM are the same thing. Once you flash a ROM, it formats the system partition and installs the new ROM/firmware. Firmware number is irrelevant when you flash a custom ROM. It will say whatever the dev makes it say, such as MIUI 2.12 etc. It might be based on an official firmware number (such as JB 3.17) but its been modded by the dev, so its not really the same firmware.
Installing custom ROMs does not touch hboot. The only way to downgrade hboot is with the JET kit in the Development forum, which requires a Linux computer.
Click to expand...
Click to collapse
OK got the first part.
Bootloader says unlocked and hboot 1.09. So I'm good to go download the latest radio I think.
I'm having trouble identifying which latest radio to update to for an AT&T phone in the US.
Sputnikk23 said:
OK got the first part.
Bootloader says unlocked and hboot 1.09. So I'm good to go download the latest radio I think.
I'm having trouble identifying which latest radio to update to for an AT&T phone in the US.
Click to expand...
Click to collapse
Yes, you are good to flash radios with hboot 1.09.
The latest radio from AT&T is the one that was released with firmware 2.20. See the radio thread, if you haven't already: http://forum.xda-developers.com/showthread.php?t=1694012
Keeping in mind the latest radio will not always yield the best results. Radio reception is most often linked to your exact geographic location, and is often a matter of trial and error. But I think many people had some decent battery life improvement with the 2.20 radio. You are also free to try radios 2.29, 2.40 etc. The fact that they were released for other carriers in other countries is irrelevant. They may still yield reception improvements, or not. As mentioned, radio flashing is pretty much trial and error. The latest is not necessarily the greatest.
redpoint73 said:
Yes, you are good to flash radios with hboot 1.09.
The latest radio from AT&T is the one that was released with firmware 2.20. See the radio thread, if you haven't already: http://forum.xda-developers.com/showthread.php?t=1694012
Keeping in mind the latest radio will not always yield the best results. Radio reception is most often linked to your exact geographic location, and is often a matter of trial and error. But I think many people had some decent battery life improvement with the 2.20 radio. You are also free to try radios 2.29, 2.40 etc. The fact that they were released for other carriers in other countries is irrelevant. They may still yield reception improvements, or not. As mentioned, radio flashing is pretty much trial and error. The latest is not necessarily the greatest.
Click to expand...
Click to collapse
Cool. THank you. Very helpful. About to flash. TWRP is ver 2.2. Any significant reason to upgrade to 2.3?
Sputnikk23 said:
Cool. THank you. Very helpful. About to flash. TWRP is ver 2.2. Any significant reason to upgrade to 2.3?
Click to expand...
Click to collapse
Keeping recovery up-to-date is usually a good idea.
Please be sure to click the "Thanks" button for posts that helped you.
Also, you can edit the thread title at any time. Click "Edit" then click "Go Advanced" to edit the title.
---------- Post added at 12:56 PM ---------- Previous post was at 12:52 PM ----------
Ha, love the new thread title!
redpoint73 said:
Keeping recovery up-to-date is usually a good idea.
Please be sure to click the "Thanks" button for posts that helped you.
Also, you can edit the thread title at any time. Click "Edit" then click "Go Advanced" to edit the title.
---------- Post added at 12:56 PM ---------- Previous post was at 12:52 PM ----------
Ha, love the new thread title!
Click to expand...
Click to collapse
Hmm.. all is well except the phone died while playing with it and now won't charge via a PC USB cable? No charge light at all.
After you flashed a rom or before? If it completely died it'll take 5 or so minutes before the light comes on and able to boot up once its on the charger.
By all means I mean no disrespect and I'm not questioning your intelligence, but make sure your computer is on while you are charging via USB. I forget about that sometimes
Sent from my One X using Tapatalk 2
Also, use the wall charger, not USB, when something like this happens. The wall charger charges much faster (more amps?) than USB, by far. Leave it on the wall charger for several hours, then see if the charge light comes on, or if you can boot.
This has randomly happened to some people, and leaving the phone on the wall charger for a few hours usually does the trick.
yup it came back after a couple minutes. thanks again.
ultimate goal is to run the latest 4.2.2 rom from Magio without the reboots and data loss. So from what I understand I need to update the fw. Therfore I need S-Off and Super CID. Can I use the X-Factor Exploit to get Super CID while on 1.09 or do I need to get to 2.2. If so, how do I get to 2.2? I'm sure I have more questions but that's my first hurdle. Any assistance is appreciated and kudos will be given. Thanks
What's the status of the phone? Have you done anything to it or did you just get it and also what firmware are you on?
Sent from my HTC One XL using XDA Premium 4 mobile app
If that's under build number is 5.08.111 and I'm currently running magio rom 4.0.2.
No, he's asking for your bootloader details, can you post them please? Also, is your phone an at&t model?
Sent from my Evita
Yes it's at&t. I don't see something that says firmware but here is the info it does give me.
Evita PDT Ship S-On RL
Hboot 1.09
Radio 0.24p.32.09.06
Opendsp v34.1.0.45.1219
I thought that the fw version was usually found in the software version in settings>about but mine just says magio 4.0.2
djlobes said:
Yes it's at&t. I don't see something that says firmware but here is the info it does give me.
Evita PDT Ship S-On RL
Hboot 1.09
Radio 0.24p.32.09.06
Opendsp v34.1.0.45.1219
Hope that helps. Thanks
Click to expand...
Click to collapse
Did u flashed newer radio?....coz I use old radio + 1.09 hboot work fine for me ...no signal drop and no wifi issue.....with stock kernel from Magio ROM btw I used 1.89 radio ....0.18
Swyped from T3DRO1CS RedHoXence
It's standard procedure to give as much information as possible when asking a question here, that includes bootloader details. The info you gave wasn't the firmware by the way, that's just ROM information, when someone is asking for firmware version they're asking for bootloader details.
Anyway, you basically have two options:
You can leave your firmware as it is and flash the Beastmode kernel which should stop your signal loss and reboot problems. You're s-on but luckily you're on hboot 1.09 so you'll have no problems flashing kernels in recovery (anyone with s-on and hboot greater than 1.09 needs to flash the boot.img via fastboot for ROMs and kernels).
The other option is to get s-off and upgrade your firmware to the 2.15 version.
My suggestion would be to flash the Beastmode kernel first, if that doesn't work then move on to upgrading your firmware.
The fact that your phone is an at&t model almost certainly means you have SuperCID. If you want to check though you can give the following fastboot command:
Code:
fastboot oem readcid
If it comes back as 11111111 you have SuperCID, if it comes back as CWS__001 you don't.
Sent from my Evita
Thanks to both of you. I just flashed beastmode 3.5 and 1.85 radio. I'll see if that helps.
djlobes said:
Thanks to both of you. I just flashed beastmode 3.5 and 1.85 radio. I'll see if that helps.
Click to expand...
Click to collapse
I used old radio with stock kernel that came with the ROM.......different phone different place make it different.....u can try flashing beastmode kernel like timmaaa said if doesn't work
Swyped from T3DRO1CS RedHoXence
The radio alone probably won't fix signal drops. There are some lucky people that it works for though.
Sent from my Evita
djlobes said:
Can I use the X-Factor Exploit to get Super CID while on 1.09 or do I need to get to 2.2. If so, how do I get to 2.2?
Click to expand...
Click to collapse
I think you are confusing build numbers and hboot versions. For the AT&T version:
Build 1.73 and 1.85 = hboot 1.09
Build 2.20 = hboot 1.14
Build 3.18 = hboot 2.14
I believe the facepalm s-off should work with any hboot. Really getting SuperCID is the main hurdle (seems to be most problematic). S-off is very easy after that.
---------- Post added at 02:28 PM ---------- Previous post was at 02:24 PM ----------
ted77usa said:
Did u flashed newer radio?....coz I use old radio + 1.09 hboot work fine for me ...no signal drop and no wifi issue.....with stock kernel from Magio ROM btw I used 1.89 radio
Click to expand...
Click to collapse
Did you ever have signal drops? I don't think everyone necessarily had signal drops with Sense 5. And if you did, I wouldn't think flashing an older radio would fix it (as timmaaa suggests).
redpoint73 said:
I think you are confusing build numbers and hboot versions. For the AT&T version:
Build 1.73 and 1.85 = hboot 1.09
Build 2.20 = hboot 1.14
Build 3.18 = hboot 2.14
I believe the facepalm s-off should work with any hboot. Really getting SuperCID is the main hurdle (seems to be most problematic). S-off is very easy after that.
---------- Post added at 02:28 PM ---------- Previous post was at 02:24 PM ----------
Did you ever have signal drops? I don't think everyone necessarily had signal drops with Sense 5. And if you did, I wouldn't think flashing an older radio would fix it (as timmaaa suggests).
Click to expand...
Click to collapse
I still used 1.89 radio+1.09 hboot....work fine same as before.....plus now i'm using beastmode v2 and is ok too .... I think radio work better with build release.....for example ATT 1.85/1.82 radio with 1.85/1.82 build ....1.89 telstra radio with telstra build 1.89 or maybe sense 5 good with 5.08 radio with 5.08 Germany build( I will try this later on ) to match radio+ril on build version
Swyped From BlueICESense_HoXatt
ted77usa said:
I still used 1.89 radio+1.09 hboot....work fine same as before.....plus now i'm using beastmode v2 and is ok too .... I think radio work better with build release.....for example ATT 1.85/1.82 radio with 1.85/1.82 build ....1.89 telstra radio with telstra build 1.89 or maybe sense 5 good with 5.08 radio with 5.08 Germany build( I will try this later on ) to match radio+ril on build version
Click to expand...
Click to collapse
You seem to be contradicting yourself, so I'm not quite sure what you are trying to say.
The 1.31 baseband that came with 5.08 will work best for most people, since the signal drop issue seems to be caused by older radios being incompatible with the Sense 5 power save feature. And yes, using the radio and RIL that is intended for the ROM is often (but not always) the best option. Although some people have complained about power reception with the 1.31 radio, and better reception by flashing an older radio (as always, the "best" radio is very location specific, and no single radio works best for everyone).
Its still not clear from what you are saying whether you actually suffered the signal drop issue, or not. But it seems like you are saying you never had the issue to begin with. Not everyone suffers the signal drop issue. If you didn't suffer the issue on the older radio, then it may simply not apply to you (location or reception dependent, is my guess). And flashing Beastmode wouldn't make a difference either.
If you didn't have the issue to begin with, flashing a new radio or kernel isn't going to make a difference. If you are not sick in the first place, taking medicine (even the wrong one) isn't going to make a difference. You will still not feel sick.
redpoint73 said:
You seem to be contradicting yourself, so I'm not quite sure what you are trying to say.
The 1.31 baseband that came with 5.08 will work best for most people, since the signal drop issue seems to be caused by older radios being incompatible with the Sense 5 power save feature. And yes, using the radio and RIL that is intended for the ROM is often (but not always) the best option. Although some people have complained about power reception with the 1.31 radio, and better reception by flashing an older radio (as always, the "best" radio is very location specific, and no single radio works best for everyone).
Its still not clear from what you are saying whether you actually suffered the signal drop issue, or not. But it seems like you are saying you never had the issue to begin with. Not everyone suffers the signal drop issue. If you didn't suffer the issue on the older radio, then it may simply not apply to you (location or reception dependent, is my guess). And flashing Beastmode wouldn't make a difference either.
If you didn't have the issue to begin with, flashing a new radio or kernel isn't going to make a difference. If you are not sick in the first place, taking medicine (even the wrong one) isn't going to make a difference. You will still not feel sick.
Click to expand...
Click to collapse
Well, what I'm trying to say is that I don't have issue with signal and wifi on sense 5 Rom.... since I'm still using older radio ......I thought might help other to understand to try using older radio if they have issues.....but like u said it depend on their location it self......and they just need to try it them self.....
Swyped From BlueICESense_JBE
..... Do you play ingress?
Sent from my One X using Tapatalk 4