Database Info

Radio + Wifi not turning on, probably something simple

My brother bought a Sensation, the guy who had it had done everything but S-CID, so I S-CID. The guy had ICS Revo HD, he loaded GB Revo HD. I went back to ICS, but I don't have radio or wifi. I tried a few roms like stock Revo HD but nothing. I tried a few kernels but nothing. I know its something simple.
Pretty sure all I have to do is install RUU ICS and it will fix the issue (correct me if I am wrong). But I have to wait 2-3 hours to finish downloading RUU ICS, is there a faster way I can fix this issue?
woops just realized I posted in the wrong sections. Sorry, please move.

F9zSlavik said:
My brother bought a Sensation, the guy who had it had done everything but S-CID, so I S-CID. The guy had ICS Revo HD, he loaded GB Revo HD. I went back to ICS, but I don't have radio or wifi. I tried a few roms like stock Revo HD but nothing. I tried a few kernels but nothing. I know its something simple.
Pretty sure all I have to do is install RUU ICS and it will fix the issue (correct me if I am wrong). But I have to wait 2-3 hours to finish downloading RUU ICS, is there a faster way I can fix this issue?
Click to expand...
Click to collapse
firstly wrong place, this should be in the q&a. secondly it sounds like you should go for the ruu. sorry bud.

heavy_metal_man said:
firstly wrong place, this should be in the q&a. secondly it sounds like you should go for the ruu. sorry bud.
Click to expand...
Click to collapse
Firstly, I know I posted in the wrong section, I edited my first post and pointed that out. Again I apologize for that it's just that I been looking all over for the answer, I had the wrong tab open and accidentally posted here.
Thanks for the answer, you confirm what I thought I had to do.
But ok... just 2 more hours to go finish my download ;/
And again I apologize for posting in the wrong section.

F9zSlavik said:
Firstly, I know I posted in the wrong section, I edited my first post and pointed that out. Again I apologize for that it's just that I been looking all over for the answer, I had the wrong tab open and accidentally posted here.
Thanks for the answer, you confirm what I thought I had to do.
But ok... just 2 more hours to go finish my download ;/
And again I apologize for posting in the wrong section.
Click to expand...
Click to collapse
Report the thread to be moved.
Nah don't waste your time with the RUU... Just flash the 3.32 firmware for ICS. That's all you need.
Sent from my HTC Sensation 4G using PKMN ROM using Sense 4.0

Freshly_Snipes said:
Report the thread to be moved.
Nah don't waste your time with the RUU... Just flash the 3.32 firmware for ICS. That's all you need.
Sent from my HTC Sensation 4G using PKMN ROM using Sense 4.0
Click to expand...
Click to collapse
How do I report the thread?
I did some digging and found the following.
http://forum.xda-developers.com/showthread.php?t=1459767
I downloaded the first link for Tmobil 3.32, installed it, same issue.
Do I also download and install Others 1 and Others 2?

I installed the latest RUU and I still have no Radio or Wifi.
Do I need to install something else?

I installed GB RUU, I had no radio or wifi. I then allowed GB to upgrade to ICS, still no Radio or Wifi. I installed the 3.32 firmware, still no radio or wifi!
I currently have 4.0.3 sense 3.6 3.32.531.14 710rd
Revolutionary
Pyramid PVT Ship S-Off RL
Hboot 1.27.1100
Radio 11.22.3504.07_m
Open ADSP-v02.6.0.2226.00.0131
eMMC-boot
I have tried everything I can think of and been all over the forum. I need help.

Doesn't anyone have a solution for me? I tried searching but have found no useful information. It's not the firmware, it's not the rom, its not the radio, so what is the problem??
I can't find a RUU that has ICS.

What to do?
Same here.
I´ve tried nearly every Rom/Radio/Kernel Combination.
Even testet a few JB Roms and RUU.
Since my Sensa XE made an update to ICS 2 Month ago
there is no chance to get WIFI work again.
With JB it worked fine.
Same with BT.
I´ve unlocked with HTC Dev and Revolutionary S-OFF.
Still hoping for a Fix or Help.
cu

The only thing I have not tried is a RUU that has ICS. I found RUU with GB, but I recent;y found one that is ICS. Before I found the ICS RUU, I downloaded the GB RUU, installed it, and allowed it to update to ICS, but that did not fix my issue. I'm hoping that if I flash it in fastboot, might just fix it.
If it does I'll let you know! It's a slow download! 3 hours!

I also have testet with ICS RUU (RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R_Radio_11.69.3504.00U_11.22.3504.07_M_release_251961_signed)
but no sucsess for me.
Please let me know when the Problem is solved for you.
cu

This doesn't make any sense... It did not work! I had Hboot 1.27.0000 and radio 11.23.35.04.07_m7 after installing stock RUU and it is still not working.
What are we missing?
I started over, installed the latest Revolution HD with custom kernel, same issue. I also updated to hboot 1.27.1100.
261 view and no one has a solution of even an idea I can try out? Has to be a reason why I don't have radio and wifi.

I have 4g now and I can make calls
Just need Wifi working. I read that it is a common issue if your not on Revolutionary, but I am, so why am I having this issue?
I had Revolution HD Rom and I tried the Wifi akp fix but that did not work. So I tried Energy rom and I had the same issue. I am trying a few more roms.
Any advice would be appreciated.

F9zSlavik said:
I have 4g now and I can make calls
Just need Wifi working. I read that it is a common issue if your not on Revolutionary, but I am, so why am I having this issue?
I had Revolution HD Rom and I tried the Wifi akp fix but that did not work. So I tried Energy rom and I had the same issue. I am trying a few more roms.
Any advice would be appreciated.
Click to expand...
Click to collapse
Check the pins(lift the pins a bit) on the back of phone just above camera lens.. Also check the corresponding antennas present on back cover
Sent from my pyramid.. Through blazing fast sonic waves

Wifi Error
Hi im newbie in this, I installed ordroid 9 and have problem to turn on wifi.
I use htcdev to unlock bootloader, install superid and clockmod recovery.
My hboot information is
***UNLOCKED***
PYRAMID PVT SHIP S-ON BL
HBOOT 1.127.0000
I think it could be s-on but im not sure, if that the problem how i can swith to s-off if i have my phone rooted?
Sorry for my english.
Thanks,
Stig

ganeshp said:
Check the pins(lift the pins a bit) on the back of phone just above camera lens.. Also check the corresponding antennas present on back cover
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Antennas look fine, raised them up a little, no change. Seems like a kernel issue though. Did my brother buy a defective phone? He spent 250 on it ;/
Any other ideas I can try?

stigmaster0780 said:
Hi im newbie in this, I installed ordroid 9 and have problem to turn on wifi.
I use htcdev to unlock bootloader, install superid and clockmod recovery.
My hboot information is
***UNLOCKED***
PYRAMID PVT SHIP S-ON BL
HBOOT 1.127.0000
I think it could be s-on but im not sure, if that the problem how i can swith to s-off if i have my phone rooted?
Sorry for my english.
Thanks,
Stig
Click to expand...
Click to collapse
Do Extra 1 step from the below guide
http://forum.xda-developers.com/showthread.php?p=25587345
Then read the guide completely.. It's for you. You need to flash roms bit differently than the traditional way.. The guide explains how
Sent from my pyramid.. Through blazing fast sonic waves

F9zSlavik said:
Antennas look fine, raised them up a little, no change. Seems like a kernel issue though. Did my brother buy a defective phone? He spent 250 on it ;/
Any other ideas I can try?
Click to expand...
Click to collapse
Just wonder if it says "Error" then you are trying to turn it on?
I've got the same problem on my device after OTA update. Solved it by flashing corresponding radio + kernel.

ganeshp said:
Do Extra 1 step from the below guide
http://forum.xda-developers.com/showthread.php?p=25587345
Then read the guide completely.. It's for you. You need to flash roms bit differently than the traditional way.. The guide explains how
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
I will try that.
artello73 said:
Just wonder if it says "Error" then you are trying to turn it on?
I've got the same problem on my device after OTA update. Solved it by flashing corresponding radio + kernel.
Click to expand...
Click to collapse
I've tried a few radios and nothing worked. Even back to stock GB and ICS, which have the original radios, same issues.
What radio did you use?

I'm seeing more and more Wifi issue threads. Does no Dev have a fix for this issue?
I tried the above fix, the above fix is only for the phones that don't have Revolution hboot, I tried it anyways, same issue.
BUT I found out that if I disable Data, and then turn on Wifi, it works, sometimes for a few seconds other times permanently. Other times as soon as I turn on Data, Wifi goes out. Tethering seems to suffer from the same issue too. So far its happened on Revolution HD on all kernels and Energy rom. Viper didn't work but then again I did not disable data. Going to try tomorrow. I would try Cynogen but its missing Google Play app ;/
I've flashed kernels and latest firmware in fastboot, same issue. I've enabled smart flash in 4xt, same issue.
I don't know what to make of this. I'm installing ICS RUU, going back to stock, even though stock has the same issue, going to see what I can do.
Is this just a poorly design phone? Did my brother just waste 250 bucks? Also, 4g is TERRIBLY SLOW! I'm assuming its

update radio with hboot 1.08

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.

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

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

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

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

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

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

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

4.0.4 and Sense 4.0
HTC One S

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Stupid upgrading existing root question [ANSWERED]

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.

confused, can I get some clarification on this?

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