yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] trevorb21:
Thanks all... actually went back to CM 10 last night. I had relocked and everything hoping for an update someday but I couldn't help it and had to go back to Cm. Battery life seems much better on the latest nightly compared to the stable version.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
If a rooted / hboot 1.14 bootloader unlocked phone with super CID is unable to take an OTA without bricking, how does one get a new radio, wifi firmware, etc.? Please don't say downgrading hboot, because I am already familiar with that somewhat dangerous approach. Others are suggesting that if one's bootloader is relocked and a stock ruu flashed, OTAs are safe. Is this not true?
[AT&T, Rogers HTC One X, Telstra One XL] exad:
I bricked after relocking and running ruu but to be fair I downgraded my hboot to 1.09 and am not sure if that had anything to do with it.. good luck..dunno why you would want the ota anyway.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
It is not that I necessarily want the OTA. I am concerned that an important radio update will come along, or something else that requires a full ruu, and I will be SOL. This HTC thing is driving me crazy - my Atrix was so easy to work with. I have yet to see a jb ROM that was 100% stable for 100% of people, so not having the option of using a stock ruu if it is available scares me.
[AT&T, Rogers HTC One X, Telstra One XL] exad:
I have noticed that typically when things are not stable right away for me it was a bad download or just a bad flash. A stock based ROM like viper has always been stable for me and am currently using paranoid android also perfectly stable. In any case, once the source for the ota is released devs will most likely use that as a base for their next upgrades so I really wouldn't worry about it.
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
My CID is 11111111 and I have taken many OTA's. I have switched and changed ROM's and reRUU'ed many times. From Hong Kong to German to Telstra. Taking OTA's all over the place. I would say my phone has at least done 8 official HTC OTA's.

Not once has it bricked.

Is it some check AT&T ROM's do?

Personally I have found unlocked bootloader and supercid do not effect an OTA. Modifications to /system are more likely to be troublesome. They are likely to be lost or could even make the update fail.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
See, this is exactly why I can't necessarily trust much of what I hear about the HOX. I wish the official resources thread would answer this, and the answer woud be provided by experienced HOX devs.
[AT&T, Rogers HTC One X, Telstra One XL] a box of kittens:
You're just unintelligent...
[AT&T, Rogers HTC One X, Telstra One XL] 954wrecker:
Trust at&t they know what's best for your type

Sent from my HTC One XL
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Wow - you guys are so helpful. What exactly is my type? Someone who knows enough about hardware to believe that there is more than just front end changes included in some OTA/RUU updates? Turge had to include a wifi update to make Viper stable for some people. I am sure you two knew exactly what the problem was as soon as the ROM came out, including all of the necessary changes, the partitions involved, etc. You've pretty much just proved you are idiots if you believe that there is nothing else included in an RUU other than system and hboot updates.

Oh, and thanks for making me miss the Atrix forum some more. The people were actually nice there. I didn't realize that I should check out the XDA forums before buying a phone - the Nexus folks can't be any worse than you two.
[AT&T, Rogers HTC One X, Telstra One XL] a box of kittens:
Thank you for giving me a good laugh... The forums being kind and your intelligence level are directly proportional...because you're a stuck up noob you are getting the treatment you deserve...and your type is for the iPhone or better yet a flip phone from a couple years back you won't have to worry about software changes on that...I'm still kind curious what you're trying to get at? I'm a bit confused how you're comparing hardware and ruu and ota
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Okay, really not sure how I am a stuck up noob. Or unintelligent, as I am perfectly capable of reading lots of threads where people who seem to know what they are talking about argue over one's ability to go back to stock using a RUU. I was merely looking for confirmation from more than one person that I could go back to stock using a RUU and then apply the OTA if necessary. My point was simply that if something came out that was not possible to implement via a ROM - i.e. a radio update, I wanted the ability to flash it. Without downgrading hboot, it appears that anyone with hboot 1.14 is STUCK WITH THEIR PRESENT RADIO. There is conflicting info out there regarding one's ability to go back to stock using an RUU and then apply the OTA in the future, and I was merely trying to confirm that this was possible. If you look in this thread, you will see one person say it is perfectly safe, and another that it will brick the phone. Care to decide who is right? I generally like to get a few opinions before I task a risk, but apparently you don't get that. It is a perfectly reasonable question.
[AT&T, Rogers HTC One X, Telstra One XL] a box of kittens:
Here's a straight answer.... That's a bit risky going back to stock through ruu than applying an ota I've seen many people brick that way idk if it's just because the cid is 11111111 or whatever but there's something in the system that the ota doesn't like and than rejects..though I do not see the point of doing an ota esepcially many involve huge security updates ie hboot as you stated which will probably result in no root. . I can confidently assure you att will bring out a new nazi hboot out with the jb update too...so my advice would be to stick to non stock and enjoy
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Thanks - I appreciate the response. Still a bit concerned about being stuck on my present radio, but perhaps that will get resolved in the future. Have a great weekend.
[AT&T, Rogers HTC One X, Telstra One XL] a box of kittens:
I'm sire your aware but you can downgrade hboot
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
Thanks, yes. I've read the entire downgrade thread a few times. It appears that more than one person has bricked their phone, and that isn't a risk I can take right now.
[AT&T, Rogers HTC One X, Telstra One XL] a box of kittens:
I can understand that...I'm not trying to pressure you here right now but the only people I've seen brick their phone from using jet was people that had took the jb ota they did sucesfully downgrade but they bricked by flashing another ruu...bit if you do run into trouble there is the unbricking thread with grim and soul shadow usually present and they can usually help you finish to the end
[AT&T, Rogers HTC One X, Telstra One XL] exad:
I can attest to this as the hboot downgrade is quite unlikely to permabrick your phone as you can restore the p4 file. It was only after running the telus ruu that my phone bricked. The way I see it op has 3 choices. Live with ****ty radio, downgrade hboot and flash radio or go back to stock now before doing hboot downgrade. If youre Seriously worried about bricking then I would say phone rooting is not for you as theres always a risk of bricking. Rooting is for people who understand the risk but enjoy the process and the learning experience. Good luck bud.
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
From all advice that is wrong if on hboot 2.14. You will brick if you attempt to downgrade hboot.

Once on hboot 1.14 or above you need ruu and ota to update radio.

Ruu is stricter in that you must have a locked bootloader, but still supercid is fine if not desirable.

What exactly do you think people are doing with supercid if not using it for ruu's and ota's?

I have heard of no bricks when using ruu or ota alone. The only bricks are related to downgrading the hboot in an attempt to use an old ruu.

That's the next point there is currently no ruu that can work with hboot 2.14 that came with the 3.17 roms. So once there currently there you only choice will be to flash a stock system back and take ota's.

The 2 insulting the user should stop. If is entirely uncalled for. Plus their info given so far seems to be wildly inaccurate.

---------- Post added at 01:16 AM ---------- Previous post was at 01:13 AM ----------

From all reports that brick is not recoverable at all. But perhaps the few users that got to there have not entirely exhausted all avenues, but that would be risky to believe.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
Do you mean my Index thread? I'm no developer, and my opinion is no more or less trustworthy than a great many other users on this forum. But my advice is to not take any OTAs if you are rooted. At least not until you research the OTA (when it comes) and know ahead of time what the OTA will do to your phone. Reason I say this:

1) On rooted phones, if you receive the OTA, it may not install properly. Meaning it might send you into a bootloop, or freeze the phone on the boot screen. Also, an OTA will not install if your bootloader is unlocked.

Safest way, if you do want the OTA, is to return to stock by relocking the bootlaoder and running the RUU. But you will still have the following problem:

2) Any AT&T OTA will almost certainly patch the existing root exploit. They've done it for every OTA to date (1.85 and 2.20), so no reason they won't do so again. You will likely lose root, until a new exploit is found. There were dozens of people that installed the 2.20 OTA willy-nilly when it rolled out, then came on here crying that they lost root. Then they were stuck without root for months, until the X-factor exploit was found. If you do it, nobody to blame but yourself.

3) An AT&T version of JB will likely bring little or nothing new (aside from a truckload of crappy AT&T bloatware) compared to what is already available in Development as stock rooted ROMs, or custom ROMs based on the already available Sense JB builds. Even if there are any significant changes are in the AT&T build, it will likely be posted as a rooted stock ROM within days (or even hours) of the OTA deploying.

Yes, a new radio is possible. But a new radio does not mean a better one. A newer radio results in better reception and battery life for some, but worse for others. Switching to the newest radio is not a sure fire improvement, and possibly not worthwhile if the tradeoff is losing root. Unless you are experiencing particularly poor reception and/or battery life, I would not mess with the OTA just to try a new radio (it might not even help much or at all).

4) Also keep in mind that the JB OTA's contain some change (hboot or otherwise, don't think anyone knows for sure yet) that breaks the touchscreen function of any ROM except Sense JB based ROMs (including all AOSP ROMs). If the AT&T OTA contains the same change, you are stuck with very limited custom ROM choices, until the issue is resolved by the devs.
[AT&T, Rogers HTC One X, Telstra One XL] twistedddx:
I believe OTA's do not check if the bootloader is unlocked or not. I installed 3.17 OTA fine with my bootloader unlocked
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
I still don't understand why anyone who cares about rooting would take an OTA.

There are many reasons not to, and I have yet to see a single good reason to do it.
[AT&T, Rogers HTC One X, Telstra One XL] tlazarus:
That is exactly the answer I wanted in the beginning. Thank you for answering the questions, providing lots of detail, and not insulting me. I think this response would be great in your index thread.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
You're certainly welcome. I can throw in some insults, but that costs extra. ;)

My index is meant as exactly that, a listing of resources and links. And not necessarily a repository of general information and answers. I've frequently considered adding an "FAQ" section to the thread. But I just haven't made the time and effort to do so. I've just received word from another RC that they are working on a separate FAQ thread that will be stickied in the forums.
[AT&T, Rogers HTC One X, Telstra One XL] thedailyl3af:
Is there anyway to upgrade a hboot? Mine's 1.14 thought about it earlier today. Saw a chance to ask right quick lol.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
For what purpose? Upgrading hboot seems to take away functionality (at least in terms of custom mods), rather than give you any additional benefits. For instance, 1.14 patched the exploits that allowed flashing of kernels and radios via recovery. 2.14 broke the touch screen for any ROM that is not Sense JB. I haven't heard of any good reason to update hboot. Many of us are still on the original hboot (1.09) and everything works wonderfully on custom and stock ROMs.

If you install an OTA, or RUU, it will update your hboot (if it was updated for that firmware version). But I certainly don't recommend updating to 2.14, as I don't think anyone has been able to downgrade from that one. So you're stuck on that hboot, and stuck with only Sense JB custom ROMs (until the devs figure out the touch screen problem).
[AT&T, Rogers HTC One X, Telstra One XL] kaiser347:
For person who likes stock rooted Rom, firmware part of OTA is essential. That's the only reason I would prefer to have an OTA. Just my 2 cents...

Sent from my HTC One XL
[AT&T, Rogers HTC One X, Telstra One XL] exad:
You will not brick from downgrading 2.14 hboot. I did it myself.

And for the record, I was not insulting him. I was being honest. There is always a risk to bricking and most of the info needed is quickly available by searching.

Understanding and accepting the risks is definitely part of it all and you should not give people the illusion as to otherwise as unlocking the bootloader voids warranty and if you brick, fixing or replacing can be expensive.
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
In my experience, the firmware "differences" (outside of the ROM) are never enough to justify taking an OTA.

Must people taking the OTA don't do it for that reason, anyway. Or even know what that means.

---------- Post added at 10:54 AM ---------- Previous post was at 10:51 AM ----------

Interesting, I haven't been following the discussion terribly closely, as I'm still on hboot 1.09, and it therefore doesn't even apply to me. But I haven't heard of anyone downgrading from 2.14 successfully, and many reports of users that have been unsuccessful.

Is there a thread discussing the proper downgrade procedure, or care to explain what you did. Did you just use the JET tool?
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Yes, I used the jet tool in Ubuntu 32 bit. Worked well. Though, as I said, there's always the risk of bricking and I don't want to give the illusion that there's no risks. I did brick that phone afterwards by running the RUU which claimed to have succeeded. That's why I said either go back to stock now or downgrade hboot as after downgrading, I find getting things back to stock is more than risky.
[AT&T, Rogers HTC One X, Telstra One XL] DvineLord:
i ran the 1.85->2.20 ota/ruu and i did feel improvements with the back-end updates. flashing boot.img separate is annoying though. now with the jb update bricking with supercid and only being able to use sense jb roms i probably wont run the jb ota/ruu until a less restrictive way is found or until all incompatible roms are updated or superseded.
[AT&T, Rogers HTC One X, Telstra One XL] 954wrecker:
Is the difference only when NOT running a custom ROM or is it different even when running a custom ROM?
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
And probably not enough of a difference to justify losing root for 3 months (or whatever it took) like so many did when 2.20 came out?
[AT&T, Rogers HTC One X, Telstra One XL] iElvis:
Except that if you like stock rooted, taking an OTA may cost you root for a while. That was the case with 2.20, as redpoint notes. Those who waited a few days were able to safely update to 2.2x bases without losing root.
[HTC Desire S] asgardr:
Good evening to all- people of good faith and hope...

I wanted to share with you statbar/eqs theme for roms from Venom Team,

assembled by your hummble narrator...

I created it just for myself, been using it for a while and in the end decided to give it

its own live

As apk form, it is supposed to work with viper roms only, due to the fact that there is a special piece of software

called `venom themes engine` implemented in to the system- allowing us to change certain

aspects of visible user interface

( one can learn more about it in any viper rom thread)

I want to stress that none of the icons that i`ve used are mine- or of my hand,

they were just found and gathered on my long searches through the internet.

Some of them were just adapted or moddified or used in conjunction with others.

All of them were either free or giveaway, but on that quest i`ve visited so many sites that

honestly do not even remember the names of the creators- accept very few,

so if you ever chance to find your work unthanked- forgive me please, write to me

and i`ll do my best to amend the fault...

Now i want to truly thank and give credits to all those without whom this little project

wouldn`t have any chances to hapen:

- Xylomon- for his amazing icon packs

- fandvd_d3iph3w- for his beautiful glass_icon_pack

- Creator of: LinuxLex8 mega icon pack which seems to be strong base for the theme

- jjcaster- for his: Shelby_Snake_icon(that I was searching a couple of hours for)

-Team Venom- for an amazing rom, themming kitchen and countless hours of work

-XDA- for spreading the light of knowledge and many other things- difficult to count

within this short line of text

- Others that i may have forgoten to mention here

whose work daily enriches our expeariences with android...

Last are not the least, for i treasure everyone equally...

Enjoy...:)

(and forgive my writting mistakes)

From now on, this little fruit of my searches belongs to the whole community

and everyone can do with it whatever one wishes...

As far as i am concerned everyone can freely distibute it, modify, change, use as a whole

or its parts in own projects or post it in other threads

as long as all people mentioned above are properly credited...

I do not take any credit for myself..

Let the younger brother of Linux be as free as his older brother is...
[HTC Desire S] jugg1es:
Posted a link to this on the venom rom thread. Nice work :thumbup:

Either write something worth reading or do something worth writing.

Benjamin Franklin
[HTC Desire S] asgardr:
It is great- for all of us noobs to have you around:)

....money will be found- when asked for,

But good men are not easy to come by....

Yamamoto Tsunetomo- "Hagakure"
[HTC Desire S] mark fly:
its a greats :thumbup::thumbup:
[HTC Desire S] jugg1es:
Try hitting the thanks button instead of filling the thread with thanks posts :rolleyes:

“What lies behind us and what lies before us are tiny matters compared to what lies within us.”* ~Ralph Waldo Emerson
[Atrix 4G Q&A, Help & Troubleshooting] gex_09:
So I have a bunch of friends with iPhones, and they threw me into a group chat (not that it matters but we're organizing a martini night). As you guys probably know as android users, this presents a problem as the group messages are received as individual texts, normally with a <no subject> header, and as a result, you can't reply to the chat, but have to respond to each member individually (or send a mass text each time).

I'm wondering if there's simply a way to group (on my end only) those contacts together, so that any message I receive from them shows up as a group chat, which I can then reply to all. I would still get the <no subject> headers, but at least this way the messages could be organized and I could read the conversation without having to look at each contact separately and compare the message with the timestamp from when it was sent.

The apps I've seen (like POWOW) can create chat groups, but it requires that my friends join the chat, or reply to some strange number each time, and it's really just an unnecessary hassle for them. I don't want that.

Anyone know of an app, or a way of grouping contacts together like this?

I'm on CM7 using the "Messaging" app.
[Atrix 4G Q&A, Help & Troubleshooting] LavLab:
Handcent has this feature. Free @ play store.

LāvLab / HostileSlothRecords
[Sprint Samsung Galaxy S III] clothednblack:
Welcome to JellyBam!

This isn't my work, but I am the host and the middle man for getting this here. Ported by (name kept out per the ported party)

Since you have to wipe everything, this is what you need to do to get ready.

Make a backup of your current rom

***Changelog can be found in post 3***

MMS fix is in post 2

MMS fix is in post 2

MMS fix is in post 2

Again........ MMS fix is in post 2

Below pertains to anyone not already running JellyBam 4.2.1 or a 4.2.1 rom.

Download a 4.2.1 rom!

(this is the safest way to ensure no issues going to JellyBam 4.2.1)

Wipe system, data, cache and dalvik

Flash it to get data set up and just stay on it till I'm done.

Download the Samsung addons (if you didn't already for JellyBam)

You can make a backup if you want

Of the 4.2.1

Download port JellyBam

Updated 2/6/12 with latest AOKP fixes

................. IMPORTANT.............................

(if you are already running JellyBam 4.2.1, you can try a dirty flash with just a cache and dalvik wipe At Your Own Risk)

................ SEE THERE ^^^^^^^....................

Wipe everything again

Flash JellyBam port

Flash Samsung addons

Reboot

Gapps is built in!!!

Remember that the boot ani will flash and seem to bootloop, let it finish, took mine 5 minutes

*****************************************

BIG THANKS TO MY TESTERS

Without you, we wouldn't be where we are today

Axximilli

MzGx09

Countryteazer

Thearch1tect

Astarling10

*****************************************

If I missed someone, please pm me, my mail box needs cleaning ;)

Thanks:

iGio90 (Rom Dev) - Bliss_ (Art and graphics)

b1uefalcon and the whole team for the base frameworks

TeamHacksung (CM10)

AOKP Team (AOKP)

Paranoid Android Team

bluefa1con (part of the framework of his P.A.C ROM)

TayyabKhalid97, Wis1152, Ricardo_ls, Uppon2, LuigiMak, Malo2000, LegendM, Lokicoon (Contributors)

Justin860 (Inverted Gapps + Themes)

GokhanMoral (Siyah Kernel)

The man that Ported this form me to share.