Database Info

Command Error when changing CID

Hi folks,
I have unlocked and s-offd my Voda HTC Chacha.. installed a WWE Rom but havent recieved any OTA since then.. I am on 1.19 and there is a 1.54 OTA out..
just checked the CID through adb and its set to Super CID 11111111 instead of generic HTC__001. Tried changing it but I get Command Error. Any idea or solution for this?
Also, Is this the reason why no OTA are showing up?
If no, please advise how can I update the phone via OTA
Many thanks

What's your full version number? Afaik, 1.19 isn't a WWE ROM, it's Vodafone UK

qzfive said:
What's your full version number? Afaik, 1.19 isn't a WWE ROM, it's Vodafone UK
Click to expand...
Click to collapse
Here are the full details mate:
Android 2.3.3
Software 1.19.206.2
Baseband 47.14.35.3030h_7.47.35.17
Kernel 2.6.35.10-g8db500e
cheers

Searching "1.19.206.2" on Google brings me back to a thread here in XDA's Chacha section saying it's an O2 ROM - so you see any O2 apps or bootanimations? I've heard that O2 don't actually "brand" their Android phones with apps, but still make all updates go through them.
EDIT: Yup, 1.19.206.1/2 is an O2-UK ROM - I found this out from this forum thread: http://forum.gsmhosting.com/vbb/7588766-post44.html
RUU_Chacha_O2_UK_1.19.206.1_Radio_47.14.35.3030H_7 .47.35.17_release_195486_signed.exe
RUU_Chacha_O2_UK_1.19.206.2_Radio_47.14.35.3030H_7 .47.35.17_release_197936_signed.exe
As you can see, your software number refers to 1 of 2 O2 UK RUUs
You should flash the 1.33.401.1 RUU from this thread, then see if you get an OTA update to 1.52.401.1 - if not, try downloading it from this thread and apply it via stock Recovery, which is reported to work if you're S-OFF and have a correct CID (HTC__001 for example) or SuperCID.

qzfive said:
Searching "1.19.206.2" on Google brings me back to a thread here in XDA's Chacha section saying it's an O2 ROM - so you see any O2 apps or bootanimations? I've heard that O2 don't actually "brand" their Android phones with apps, but still make all updates go through them.
EDIT: Yup, 1.19.206.1/2 is an O2-UK ROM - I found this out from this forum thread: http://forum.gsmhosting.com/vbb/7588766-post44.html
RUU_Chacha_O2_UK_1.19.206.1_Radio_47.14.35.3030H_7 .47.35.17_release_195486_signed.exe
RUU_Chacha_O2_UK_1.19.206.2_Radio_47.14.35.3030H_7 .47.35.17_release_197936_signed.exe
As you can see, your software number refers to 1 of 2 O2 UK RUUs
You should flash the 1.33.401.1 RUU from this thread, then see if you get an OTA update to 1.52.401.1 - if not, try downloading it from this thread and apply it via stock Recovery, which is reported to work if you're S-OFF and have a correct CID (HTC__001 for example) or SuperCID.
Click to expand...
Click to collapse
Fantastic mate, downloaded it as we speak..
not sure how it stayed on 1.19 as after I used XTC Clip, the logos and boot image were gone so I assumed I had a stock rom.. oh well.. everyday is a learning day..
I will let you know how I get on..
cheers for your help mate..

Update... Installed the 1.33 which then took the OTA update which is all good... However I still can't change the CID to HTC__001.. (currently set at 1111111)
Sent from my HTC Sensation Z710e using Tapatalk

why you like to change the CID?
SUPER-CID (1111111) might have set during S-off thru xtc clip.... SUPER-CID (1111111) signifies you device is universal device, which enables to flash all languages/APN/other settings in your phone

ajeevlal said:
why you like to change the CID?
SUPER-CID (1111111) might have set during S-off thru xtc clip.... SUPER-CID (1111111) signifies you device is universal device, which enables to flash all languages/APN/other settings in your phone
Click to expand...
Click to collapse
I know but it doesn't help with OTA updates
Sent from my HTC Sensation Z710e using Tapatalk

ok, but..
ajeevlal said:
why you like to change the CID?
SUPER-CID (1111111) might have set during S-off thru xtc clip.... SUPER-CID (1111111) signifies you device is universal device, which enables to flash all languages/APN/other settings in your phone
Click to expand...
Click to collapse
True, but it forces non-qwerty keyboard users to manually modify the layout in /system/usr/
as described here , because CID is taken into account on default layout.
Once you know the trick, it's OK, but really annoying to do every time you install a new ROM

[Q] Some questions about HOX ATT CID, bootloader & LTE

Hi, guys.
I'm using a HOX AT&T with stock rom 1.85, and yes I did the deed, root, spoof CID and unlock bootloader, install TWRecovery. Now I live in Asia so no LTE here, and I don't like the ATT's bloatware at all, also I read some complaints about LTE radio constantly drains battery if not in coverage. Some flashing is in order, but before diving in I have some questions:
1./ Is the spoofed CID permanent? I mean now my HOX is 11111111 CID - like a retail/generic one's, what will happen if I flash a RUU from another operator? Does a RUU from AT&T make my phone's CID go back to before and I need to start the whole nine yards again?
2./ I understood flashing a stock rom will un-root the phone okay, but what about bootloader? A RUU flashing wont re-lock the bootloader, or will it?
3./ Like I said, I can't stand bloatware, in the roms section I saw this RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed and a newer RUU 2.29 Asia somewhere else, are those unbrand roms - like the ones come with retail/operator-free One XL?
4./ I saw warnings about this specific rom, 2.20 of AT&T, no root, new hboot... all basically spells trouble, but what about branded roms with higher version number like O2 DE 2.29 or Vodafone DE 2.33, are they kosher?
5./ AFAIK, Europe and Asia has no LTE capability, so if I flash a radio rom from European operators or Asia does it disable the LTE radio in my AT&T HOX?
That's all, thank you guys in advance.
6./ In the thread radio & RIL , I read that update 2.2x will replace HBOOT and make old radio not compatible, is it because new HBOOT resize the radio partition smaller? So if I flash a custom rom based on Asia RUU 2.29 for example (not the dreaded 2.20 ATT), my current HBOOT will be replaced by new HBOOT as well? With no S-OFF, we can not flash HBOOT so will I be stuck with the new HBOOT and therefore, new radio roms only?
Looking forward to hearing from HOXL gurus. Thanks.

linhldz said:
Hi, guys.
I'm using a HOX AT&T with stock rom 1.85, and yes I did the deed, root, spoof CID and unlock bootloader, install TWRecovery. Now I live in Asia so no LTE here, and I don't like the ATT's bloatware at all, also I read some complaints about LTE radio constantly drains battery if not in coverage. Some flashing is in order, but before diving in I have some questions:
1./ Is the spoofed CID permanent? I mean now my HOX is 11111111 CID - like a retail/generic one's, what will happen if I flash a RUU from another operator? Does a RUU from AT&T make my phone's CID go back to before and I need to start the whole nine yards again?
2./ I understood flashing a stock rom will un-root the phone okay, but what about bootloader? A RUU flashing wont re-lock the bootloader, or will it?
3./ Like I said, I can't stand bloatware, in the roms section I saw this RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed and a newer RUU 2.29 Asia somewhere else, are those unbrand roms - like the ones come with retail/operator-free One XL?
4./ I saw warnings about this specific rom, 2.20 of AT&T, no root, new hboot... all basically spells trouble, but what about branded roms with higher version number like O2 DE 2.29 or Vodafone DE 2.33, are they kosher?
5./ AFAIK, Europe and Asia has no LTE capability, so if I flash a radio rom from European operators or Asia does it disable the LTE radio in my AT&T HOX?
That's all, thank you guys in advance.
Click to expand...
Click to collapse
1. Spoofed CID is permanent unless you go in and change it back. For all intents and purposes, it's permanent.
2. Actually to run an RUU, you must relock your bootloader or it will fail. As long as you have your unlock token or Super CID, you can re-unlocked your bootloader once you are done and flash SuperSU to get root back. Or just flash a pre-rooted stock ROM.
3. Not sure. Make sure to fully read the post. I have never run an RUU for a phone with an RUU from a different carrier. Again, make sure you read about that one.
4. You just don't want to run the 2.20 RUU for AT&T. It will make it so you can not flash radios at all and you must flash boot.img from adb or from Android terminal emulator. It is just the 2.20 RUU that will do this. A custom ROM will not, so no need to worry.
5. It will not disable LTE, but if you don't have an LTE APN in your phone it shouldn't be looking for LTE and you can also turn off the LTE radios on any non-AT&T ROM.
My recommendation after all of your questions would be to flash a pre-rooted stock ROM or a cleaned up debranded ROM (like Clean Rom, but there are more out there). Change the APN to what ever country you are in and do the *#*#4636#*#* thing to turn off your LTE radio. Again, the *#*#4634#*#* to turn off the radio will not work on a stock AT&T ROM.

Thank you, Butters. Still I've got one more question - added in the first post.

linhldz said:
Thank you, Butters. Still I've got one more question - added in the first post.
Click to expand...
Click to collapse
If you are flashing a custom ROM, you do not have to worry about your HBOOT being changed. It doesn't matter what the custom ROM is based on. You only have to worry about that with running an RUU (which is from HTC for a specific carrier).
If you have 1.85 on your phone, just keep a 1.85 RUU on your computer and flash away any ROM you want. If something gets messed up and you need to RUU, you'll always have that 1.85 RUU with the old hboot.
Running the 2.20 RUU, you will lose all ability to flash any radios, so you will be stuck with the AT&T 2.20 radio. Being that you are overseas, I would not recommend this because it may not (probably isn't) the best radio for your use case.

If you want a stock ROM, there are pre-rooted versions posted in Development that are flashable from TWRP. Easier then relocking the bootloader and running the RUU, and no threat of hboot changes (or having to research what was changed in the hboot).
Or just install a custom ROM. They are often based on recent firmware versions, but already de-bloated, and with awesome customizations added.
After all, if you want to run a stock RUU, why did you unlock the bootloader in the first place?

Thank guys, really appreciate. Just flashed CR5 with confidence, so far so good.
Early assessment: Quite smooth, the LTE problem with AT&T stock rom has disappeared, battery life improves greatly.

In need of major major help

I need some major help, good folks of XDA. I've purchased this HTC One S from a guy who got it from Fido; naturally it was locked to Fido. I was planning on giving it to my girlfriend who is with Telus. I used cellunlocker.net to unlock the phone to find out that it didnt work with Telus. It would pick up signal then lose signal, pick up signal and lose signal every 10 seconds or so. I thought if I put a custom ROM on it might get me signal so I unlocked bootloader, rooted and put Viper ROM on it but it turns out it still wouldn't pick up network on Telus. So I decided to try it on my network, Rogers, and it picks up network but only 2G!!! Now my One S has the stable CM10 on it with baseband 1.08ts.50.02.16_10.08e.50.04L, unlocked bootloader with s-on, hboot 1.06, radio - 0.16.31501s.02
Here are the solutions I have tried so far to this problem;
-Tried to install multiple RUU both with ROGER001 CID and Super CID:11111111 and I couldn't install any of the RUUs, kept getting Error 155 with Rogers RUU and Check CID errors with other RUUs.
-Used to have 1.13 hboot but downgraded to 1.06 so I could change basebands and everytime I flash a different baseband, nothing changes after reboot.
-There is a recent jellybean rogers ota update zip but I dont know how to install it
please someone help!!! Thank you in advance and even more if my problem ever gets solved

Wrong forum for this kind of question. Have you tried flashing the telus radio? Also modifying the build.prop with the telus settings might help. Odd that you're having that issue on Rogers since Fido is the same network. Sounds like someone may have sold you a dud...
Sent from my HTC One S using xda premium

alltubetone said:
Wrong forum for this kind of question. Have you tried flashing the telus radio? Also modifying the build.prop with the telus settings might help. Odd that you're having that issue on Rogers since Fido is the same network. Sounds like someone may have sold you a dud...
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Just asking, why is this the wrong (forum) as you say cuz this forum handles all devices does it not and I don't see anything wrong with his post?

SuperCID lets you flash any RUU, that error is most likely down to the bootloader being unlocked so if you really want to run a RUU then you want SuperCID and the lock the bootloader then run the RUU and also before you start the RUU be in fastboot mode first.

Darknites said:
SuperCID lets you flash any RUU, that or is most likely down to the bootloader being unlocked so if you really want to run a RUU then you want SuperCID and the lock the bootloader then run the RUU and also before you start the RUU be in fastboot mode first.
Click to expand...
Click to collapse
I did fastboot oem lock before flashing and got the same results; rather frustrating

alltubetone said:
Wrong forum for this kind of question. Have you tried flashing the telus radio? Also modifying the build.prop with the telus settings might help. Odd that you're having that issue on Rogers since Fido is the same network. Sounds like someone may have sold you a dud...
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
is it possible for a dud phone to have only 2g working and not get 3g?

dpk0875 said:
I did fastboot oem lock before flashing and got the same results; rather frustrating
Click to expand...
Click to collapse
Try hex editing mmcblk0p23 .... There is a method here for flashing RUUs that is discussed in the development forum in the sticky for downgrading your bootloader.... Try the hex edit, and then lock and then flash.
You could also try flashing a different baseband radio. For Canada, I didnt get the best reception from 1.08. You can d/l new baseband radios either for your phones radio partition or for CM10 (which uses a different location). There is a thread with radios collected in them in the development section.
I would try flashing a different radio before the RUU... The RUUs will upgrade your bootloader and then you cant flash new radios and other partition on SENSE seperately (ie ROMS wont flash properly and you will need to fastboot the boot.img every time)...

Funny , I unlocked my Original Fido One S to use it on Wind and it works perefectly. It should work on Telus ...have you tried inputting telus apn and restarting the phone after?

Applying RUUs on Unlocked 1.14/2.22 AT&T One X

Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium

tlazarus said:
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s :
- you don't need to root your phone to add apn . I can add T-Mobile apn just fine after I flashed ruu.
- ruu.exe can't run if you bootloader is unlocked.
Sent from my HTC One X using XDA Premium HD app

tritran18518 said:
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s : you don't need to root your phone to add apn .
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks - that answers my RUU questions as far as going back to stock using RUUs. I assume the same applies to other carrier's RUUs, i.e. Telus/Asia. What about using an OTA on a phone with Super-CID?

redpoint73 said:
A factory reset or running the RUU will not change the CID.
SuperCID doesn't prevent you from getting the AT&T OTA (although root and unlocked bootloader will).
Click to expand...
Click to collapse
^^

jiggamanjb said:
^^
Click to expand...
Click to collapse
Okay, I think that answers my questions. No problems with using a RUU, AT&T or otherwise, as long as it is for the XL. Stuck on my current radio unless I use a RUU. And I need to relock my bootloader before applying a RUU, although I can unlock it after. I will lose root, however. Thanks!

Looking for a compatible RUU File for HTC One S Cincinnati Bell (PJ40110)

Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance

Auraburst said:
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Click to expand...
Click to collapse
It's easier to find the correct one if you know your firmware version/build number. If you're still using stock rom you can find it in settings>about>software information>more. If you already deleted the stock system on your phone you need to use
Code:
fastboot getvar all
in fastboot mode (look at the line beginning with "version-main"). Since you already unlocked your phone I assume you know how to use fastboot with the windows cmd.
RUUs can be found here for example. Just use the search function of your browser and be sure that you download a RUU and not an OTA. Since there are two versions of the One S you need to be careful not to use VilleC2 (Snapdragon S3 with 1.7 gHZ) files on a Ville (Snapdragon S4 with 1.5 gHz) and vice versa (this rule applies on roms, kernels, etc., too). If I remember correctly your hboot is Ville specific but if you want to be sure you can find the answer in the getvar all output (look at the line beginning with "product").

Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)

Auraburst said:
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Click to expand...
Click to collapse
The problem is that the only file with the 422 SKU is an OTA and not a RUU. If your phone was S-OFF you wouldn't need to use corresponding RUUs because you were able to flash any you want. It's a vicious circle in your case since you wanted the correct RUU before you start flashing. On the other side if you carefully follow the instructions of the S-OFF guides there shouldn't be any risk of bricking. Simply don't try to use any short cuts if any step doesn't not work the way the instructions tell you. Since I'm not living in the states I'm not completely sure but Cincinnati Bell is part of Bell Mobile, right? If that's correct I would change the CID to SuperCID (depending on the S-OFF method you use you may need to get the SCID anyway) and try to run one of the "BM" RUUs on AndroidRUU. Since all of them are older than you actual firmware your phone will be downgraded then but you can update it by using the OTA function in settings>about.
Btw.: With that output you can be sure it's the Ville and not the VilleC2.

Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone

Auraburst said:
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Click to expand...
Click to collapse
Actually your radio doesn't matter at all in regard of RUUs. Flashing a RUU is never risky as long as it's a signed/official one and you do not turn off the phone during the flashing process or disconnect it from your pc. If you are not S-OFF and your CID and/or firmware version doesn't match (SCID always matches) official RUUs will simply abort the flashing process.
After you achieved S-OFF and got the SCID you simply need to relock your bootloader, boot into fastboot mode, connect the phone to your pc and run the RUU.exe. (As far as I remember relocking was needed for being able to install OTAs afterwards but I'm not completely sure. I just remember that I always did when I downgraded. Maybe someone else can confirm this.)
I personally do not like Cyanogenmod on this phone. Since there never was a GPE of the One S (the first HTC GPE that ever existed was the HTC One M7 GPE which is actually younger than this phone) there are no AOSP drivers for this phone and you can notice this problem for example in a worse camera quality on roms that are not based on sense (there are other problems but that's the most prominent one I can remember).
MaxximusHD is based on the leaked but never officially published android 4.2.2 firmware of the One S. If you want to use it without memory problems (the leaked firmware changes the way the phone interacts with it's memory) you need to flash the hboot 2.16. Instructions can be found in the Maxximus thread for example. I personally prefer hboot 2.16 because of its reorganized memory but the radio 1.20 that gets flashed with that firmware has some problems with the incall voice quality.
To sum it up, every custom rom has its pros and cons and every user has his/her own preferences so it's hard to tell others which rom to use. The best way is to look which ones fullfil your needs and to test them out by yourself.
Edit: Downgrading isn't needed if you just want to start flashing. I just wanted to point out what happens if you run a RUU that is older than your actual firmware.
Edit2: Nevertheless here is a chronological list of the roms I liked and used longer than a week on this phone: Viper 2.2 (hboot 2.15), MaxximusHD (hboot 2.16), Viper 3.2.1 (hboot 2.16).