Database Info

[Q] What's the difference between 1.85 and 1.88 RUU? Why is 1.88 disappearing?

Scrosler based cleanrom 4.0 off the 1.85 ruu, whereas the previous one was 1.88. I also noticed the Att one x resource Page no longer has a link for the 1.88 RUU. What gives? Did we discover that 1.88 is subpar? I thought everyone agreed 1.85 was junk?

thechilipepper said:
Scrosler based cleanrom 4.0 off the 1.85 ruu, whereas the previous one was 1.88. I also noticed the Att one x resource Page no longer has a link for the 1.88 RUU. What gives? Did we discover that 1.88 is subpar? I thought everyone agreed 1.85 was junk?
Click to expand...
Click to collapse
Scott decided to base Cleanrom on 1.85 because It's the official firmware from AT&T. He said there are less problems and fewer tweaks necessary to make his changes work by using the "official" firmware for the phone he develops on.

Just thought that I'd point out my battery life was MUCH better on 1.88 while using CR DE 2.3. I wish I could find that version to download again.

gunnyman said:
Scott decided to base Cleanrom on 1.85 because It's the official firmware from AT&T. He said there are less problems and fewer tweaks necessary to make his changes work by using the "official" firmware for the phone he develops on.
Click to expand...
Click to collapse
I see, thanks for the info. I figured that I might be able to find the answer in one of the later pages of the ROM's thread, but that it might also be heinously difficult to locate.
Did he also mention why he's decided to go with odex? Is it for the same reason?

Odex is wicked fast.

Ignore me

gunnyman said:
Odex is wicked fast.
Click to expand...
Click to collapse
I agree.

Never knew there was a link to the [email protected] 1.88 leak can someone post it
Sent from my HTC One X using Tapatalk 2

vdub804 said:
Never knew there was a link to the [email protected] 1.88 leak can someone post it
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
there ISN'T an AT&T 1.88. That firmware is for the Asian HOXL

vdub804 said:
Never knew there was a link to the [email protected] 1.88 leak can someone post it
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You know, now that I think on it I don't actually know if a link was ever up. Is there an asian model that also uses S4? Answered right before me. And, weren't there grumblings about 1.85, or am I confusing myself..

gunnyman said:
there ISN'T an AT&T 1.88. That firmware is for the Asian HOXL
Click to expand...
Click to collapse
Thanks man I got excited for nothing
Sent from my HTC One X using Tapatalk 2

gunnyman said:
Scott decided to base Cleanrom on 1.85 because It's the official firmware from AT&T. He said there are less problems and fewer tweaks necessary to make his changes work by using the "official" firmware for the phone he develops on.
Click to expand...
Click to collapse
hey dude could you help me? i get a AT&T One XL i knew that the phone is rooted and unlocked i don't know what kind of method to unlocked the used (i received my phone and i just need to put my microSim on it)
i tried to update to the new version of the ICS 4.0.1 and HTC sense 4.1 without any success (yes its too sad) because when i tried to do it via OTA i get the message "we have determined that your phone may be running a modified version of its system software, etc, etc"
my android version is 4.0.4
HTC sense versio 4.0
Software Number 1.88.707.2
HTC SDK API level 4.11
HTC Extension Version 403_1_GA_4
i really appreciate your help
thanks in advance

fjej78 said:
i tried to update to the new version of the ICS 4.0.1 and HTC sense 4.1 without any success (yes its too sad) because when i tried to do it via OTA i get the message "we have determined that your phone may be running a modified version of its system software, etc, etc"
Click to expand...
Click to collapse
Can't be said enough: Don't ever install an OTA on a rooted Android device.
At a minimum, you will lose root. You may also be stuck in a bootloop, or you may get stuck on an unrootable firmware (depending on what they updated, and what holes they plugged).
If you are already rooted and bootloader unlocked, flash one of the stock rooted ROMs here under "Stock Rooted": http://forum.xda-developers.com/showthread.php?t=1671237
Not sure what 1.88 was updated to. But 2.23, 2.29, 2.33 are all very recent firmware builds (2.23 is Asian region for the carrier Singtel). Only difference is the carrier bloat, and you may need to manually enter the APN info for your carrier.

redpoint73 said:
Can't be said enough: Don't ever install an OTA on a rooted Android device.
At a minimum, you will lose root. You may also be stuck in a bootloop, or you may get stuck on an unrootable firmware (depending on what they updated, and what holes they plugged).
If you are already rooted and bootloader unlocked, flash one of the stock rooted ROMs here under "Stock Rooted": http://forum.xda-developers.com/showthread.php?t=1671237
Not sure what 1.88 was updated to. But 2.23, 2.29, 2.33 are all very recent firmware builds (2.23 is Asian region for the carrier Singtel). Only difference is the carrier bloat, and you may need to manually enter the APN info for your carrier.
Click to expand...
Click to collapse
Thanks for you quickly response, then if I remove the root of my phone, i will be able to update via OTA? I'm am a Rookie in this type of problems the only thing that i want its update my phone with the new version of ICS and HTC sense.
could you help me please?
Thanks in advance

fjej78 said:
Thanks for you quickly response, then if I remove the root of my phone, i will be able to update via OTA? I'm am a Rookie in this type of problems the only thing that i want its update my phone with the new version of ICS and HTC sense.
could you help me please?
Thanks in advance
Click to expand...
Click to collapse
If you are a noob, the best thing to do is read read read, and find out:
-What root and flashing ROMs means, and whether you will want them.
-What firmware number the new OTA is, and what has been changed.
People get all excited about a new OTA, without even knowing what has been changed. Newer firmwares include a new hboot, which patches holes which allowed flashing kernels and radios. You may not want to update.
Also, root and unlocked bootloader are both good things. There is really no reason to give them up, just for the latest firmware. If its just the newest firmware you want, as I already mentioned, there are stock rooted ROMs in the Development forum that you can flash, and probably in less steps than unrooting and installing the OTA.

redpoint73 said:
If you are a noob, the best thing to do is read read read, and find out:
-What root and flashing ROMs means, and whether you will want them.
-What firmware number the new OTA is, and what has been changed.
People get all excited about a new OTA, without even knowing what has been changed. Newer firmwares include a new hboot, which patches holes which allowed flashing kernels and radios. You may not want to update.
Also, root and unlocked bootloader are both good things. There is really no reason to give them up, just for the latest firmware. If its just the newest firmware you want, as I already mentioned, there are stock rooted ROMs in the Development forum that you can flash, and probably in less steps than unrooting and installing the OTA.
Click to expand...
Click to collapse
thanks and i started to read, in fact i tried to flashed my HOX with this stocked room "stock rooted 2.33.162.2 - odex/deodex and unsecure boot.img with init.d" using odex version but when the phone restarted the room wont boot then i think "i have a nice brick" could you help me i tried to post this problem in the develop section but i cant because i dont have he number of post to do it i dont know whats step i need to follow to bring from the death my phone

Did you factory reset and wipe cache and Dalvik before flashing?
Come to think of it, that's one reason that people like OTAs, they keep your user data (but that can often be a bad thing, as I've seen it mess up the performance for some people after the OTA). Also, wiping data is not really that big a deal. With Titanium Backup Pro, I'm up and running again in about 20 minutes after wiping data and flashing a new ROM.
Can you still get into hboot and recovery?

fjej78 said:
thanks and i started to read, in fact i tried to flashed my HOX with this stocked room "stock rooted 2.33.162.2 - odex/deodex and unsecure boot.img with init.d" using odex version but when the phone restarted the room wont boot then i think "i have a nice brick" could you help me i tried to post this problem in the develop section but i cant because i dont have he number of post to do it i dont know whats step i need to follow to bring from the death my phone
Click to expand...
Click to collapse
btw I dont know why if i connect the phone to the computer, HTCSync Detects the phone and shows me the information but the phone still death without boot

Also, what is the state of the phone. Do you have the white HTC screen at least?

fjej78 said:
thanks and i started to read, in fact i tried to flashed my HOX with this stocked room "stock rooted 2.33.162.2 - odex/deodex and unsecure boot.img with init.d" using odex version but when the phone restarted the room wont boot then i think "i have a nice brick" could you help me i tried to post this problem in the develop section but i cant because i dont have he number of post to do it i dont know whats step i need to follow to bring from the death my phone
Click to expand...
Click to collapse
redpoint73 said:
Did you factory reset and wipe cache and Dalvik before flashing?
Can you still get into hboot and recovery?
Click to expand...
Click to collapse
i cant get into hboot or recovery (i tried with power button +volume)
and i just install the zip from sdcard and the end i wipe the cache and dalvik and fixed the permissions and when the phones started just shows me the white screen of htc and a thin yellow bar in the right side like if something is loading and suddenly turns of and its all

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.

[Q] Differences between hboots 1.06, 1.09, 1.13, and 1.14?

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

CleanROM 7 stuck at splash screen

Stuck...just displays the HTC logo on white screen.
I had cleanrom 5.0 final. TWRP, super SU, rooted, unlocked. Firmware 2.20.
I dropped in the new ROM, did a factory reset in TWRP, and installed new rom. I read that that would work with my current setup, but apparently not. I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
I flashed back to 5.0 with no issues, but I would really like to try to get the cleanrom 7 working if possible. Any ideas?

It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita

timmaaa said:
It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your reply. You are correct, I am s-on. But I was able to re-load CleanROM 5. This is my second custom rom on this phone (the first being CleanROM 5). But this is only my third custom rom ever, so I am pretty much of a noober. :cyclops:

klaypigeon said:
I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
Click to expand...
Click to collapse
The ROM threads are to inform you of the features and requirements of the ROM, not to be a step-by-step guide. There are plenty of step-by-step guides in various places, for those that care to read and look.
If you don't flash often, a good resource is my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
My Index will at least point you to the s-off process. I intend to add some info about the 2.15 firmware (as people keep constantly asking about it), but work has been chaotic, to say the least.
Another good thing to do, is read through the more recent pages of the ROM thread, or do a search on the thread.

Thanks, I am subscribed to your index, that's where I found the ROM and what I used during my first flash.
I did the process for unlocking the 2.20 firmware about a year ago as that is what my phone came with. I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
'CID Getter' says I have no CID, which I read means I have superCID.
Firmware : 2.20
SuperSU installed and functioning (I have root)
Current ROM: CleanROM 5 Final
S-ON
TWRP 2.3.1.0
So you think I need to do s-off as described here? http://forum.xda-developers.com/showthread.php?t=2155071
If I brick this phone I am using a clam-shell for a year until contract renewal :/

klaypigeon said:
I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
Click to expand...
Click to collapse
You shouldn't be assuming anything. You just said the CID Getter says S-on. You can also confirm s-on or s-off by going into bootloader.
The main reason CleanROM7 will not boot, is that you forgot to extract boot.img from the ROM file, and flash it separately using fastboot. Some older versions of CleanROM didn't require this (boot.img was flashed in the AROMA installer), so that may be why you don't remember doing this.
S-off removed the requirement to flash boot.img separately (will flash in recovery automatically when you flash the ROM). It will also allow you to install hboot 2.15 and associated firmware, if you happen to suffer from signal drops or random reboots while on Sense 5 ROMs.

Further to that, CID Getter doesn't show your actual CID. The proper way to display your CID is by using the fastboot command "fastboot oem readcid". Like Redpoint said, you shouldn't be assuming anything.
Sent from my Evita

Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.

What did you flash?
Sent from my Evita

Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.

timmaaa said:
Further to that, CID Getter doesn't show your actual CID.
Click to expand...
Click to collapse
Ha, that's not a very useful app, then. What is it actually reading?
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
klaypigeon said:
Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.
Click to expand...
Click to collapse
Do you mean "locked the bootloader" instead of "flashed"?
If you locked the bootloader, this is what is supposed to happen. Locking the bootloader assumes you will be running RUU, and renders the phone unable to boot normally.
I know you got it back up and running. But for future reference, this phone is almost never bricked, as long as the screen comes on.
---------- Post added at 09:26 AM ---------- Previous post was at 09:24 AM ----------
klaypigeon said:
Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.
Click to expand...
Click to collapse
Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.

I'm not sure what CID Getter is actually reading, but when I used it it came up with the incorrect CID, can't remember exactly what it was now but it was definitely incorrect because I already had SuperCID.
Sent from my Evita

Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.
Click to expand...
Click to collapse
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out

klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
If you have s-off you don't need to flash the boot.img via fastboot, that's only required if you're s-on. It might be worthwhile updating your TWRP to the 2.6 version though.
What Redpoint was saying is that you need to have a firm understanding of what you're doing when it comes to modifying your phone. If you only do it once a year that's cool, but that probably means that once a year you need to brush up before making any changes to your device. Rushing in without the required knowledge is how bricks occur. This is only being suggested to help you, for your own good.
Sent from my Evita

klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do.
Click to expand...
Click to collapse
Only with hboot 1.14 or later and s-on. If s-off the protection which prevents boot.img from being written in recovery is bypassed.
I believe TWRP 2.3.1 was a pretty trustworthy version (although older). So not sure why CleanROM didn't flash. Might not be a bad idea to update to 2.6.0 (although the latest 2.6.4 seems to have some bugs).
klaypigeon said:
I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
Yeah, I understand that you only do this on a seldom basis. And its a lot of esoteric knowledge to have to relearn (or take in, since things have likely changed since lasts time). However, that doesn't change the fact that not fully understanding all the concepts and steps can have dire consequences for your phone.

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

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!