With all of the (most likely false) articles coming out saying cupcake will be released this week (from what ive heard, good luck getting it by march) everyone is asking "Will rooted G1s get OTA updates?
No, you will not (if you have rooted your phone properly (this means you have JF's latest rom)) receive the OTA update. Technically you might receive it, but it will fail to install if you do. This was done on purpose because if it succeeded you would lose root. Shortly after the OTA updates are released, various members of the G1 "hacking" (yeah, term doesnt quite fit, but it will work for now) community will intercept it, tear it apart, remove all the mean mean code that steals our precious root, maybe add some fun new stuff and then release another modified rom in its place.
If you suddenly decide you do not want root anymore (I am guessing you are too lazy to download the update manually) you can use the RC29 downgrade nbh file found on various threads here, or in my wiki (see my signature) to go back to an official RC29 which would then let you receive OTA updates normally.
duhh lol this should be a board annocuments
I've heard some people saying they got the update but I dont see how that is possible. Wasnt google says like a 2 weeks ago that cupcake isnt close to being ready for the public? The only thing I can think of would be and update to support paid apps. I figured if cupcake was launching someone on here would have announced it.
Correct me if I'm wrong but wouldn't downgrading to RC29 while still rooted just give you RC29 with test keys still enabled? Wouldn't you also need to reflash your recovery partition as well to the stock one?
the rc29 will flash the recovery also the only thing you would be left with is the boot loader
Frankly, we'll all probably have a modified Cupcake before most G1 consumers actually have Cupcake. Google rolls out the updates really slowly. There's no reason to downgrade.
xile6 said:
the rc29 will flash the recovery also the only thing you would be left with is the boot loader
Click to expand...
Click to collapse
Good to know, my g1 has a bad wifi module and I need to restore it and send it back. I figured I would experiment with rooting the defective one first in case it went wrong.
Come to think of it, my wifi reception problem could be an antenna problem which could explain my weak 3g reception, or it might just be the 3g network...
speoples20 said:
I've heard some people saying they got the update but I dont see how that is possible. Wasnt google says like a 2 weeks ago that cupcake isnt close to being ready for the public? The only thing I can think of would be and update to support paid apps. I figured if cupcake was launching someone on here would have announced it.
Click to expand...
Click to collapse
there is going to be a video recorder FINALLY... rumors rumors lol
xile6 said:
the rc29 will flash the recovery also the only thing you would be left with is the boot loader
Click to expand...
Click to collapse
bzzzzzt. wrong answer . the RC29 nbh also flashes the bootloader.
MY bad i meant the Engineering SPL wouldnt that still be left?
hmm....so the new cupcake update coming out will close root again? that is so stupid, why wont they just let it be.
granted, like mentioned above, some of our famed and hard working G1 modders will probably have a modded rom with the whole cupcake update on it before everyone would have recieved the OTA anyway.
we'll see what happens i guess, but not for nothing, im really looking forward to the Cupcake updated features and abilities
im almost tempted to just revert back to RC29 just to get the official OTA and see how it is, but then again, whos to say it wont take months for me to get it.
As a note for all those who read my post and thought "yeah, I am lazy, I might as well downgrade and let the OTA's come." you might want to rethink it. If you downgrade, and the new OTA reflashes your system to not accept the RC29 downgrade, you might never get root again. And yes, this is entirely possible.
If you have root, I would not risk it for laziness or eagerness to have the latest OTA because history shows JF has had modified updates in less than 24 hours (I think they were all about 3-5 hours later) after the OTA's were first found.
i wholey agree with that. i definatly dont want to be locked out of root again. although i dont use it as much as others, root is good to have if needed to use it for something.
It would be stupid to downgrade to receive the ota. It took 1 month after the release just to get rc29. Waiting for someone to rip apart and modify the cupcake ota will be much quicker than to wait for the ota update yourself plus root access probably will be lost. Just say no to ota!
Anyways if people are so eager to see cupcake in action visit their local tmobile retailer I bet they will have it as soon as it gets out
Downgrade? Revert? Not an option now that I have root, no way I would chance losing it. Good heads up, I was pretty sure (actually was one of the ? i had) before rooting that this would occur. I spent some time here on XDA and realized that I could trust this forum and the devs to support the rooted community.
Thanks to all who make root possible and what it is on the G1!
All~G1 said:
Downgrade? Revert? Not an option now that I have root, no way I would chance losing it. Good heads up, I was pretty sure (actually was one of the ? i had) before rooting that this would occur. I spent some time here on XDA and realized that I could trust this forum and the devs to support the rooted community.
Thanks to all who make root possible and what it is on the G1!
Click to expand...
Click to collapse
well said ..... thanx much. XDA has helped me start learning this new language. As I stumble through, I find a surprising lack of b.s. and have learned quite a bit ... way thanx, to all ya all
my theory on when the next RC will drop.
They have been slow to get out updates, unless there is a exploit found.
When the bug was found everybody got rc 30 in a few days, I think that the new found downgrade route will speedup the next update to stop downgrading, if the tmob wants to keep the handset locked they will push for a speedy update to stop downgrades.
They also eluded that a beta was close but the holidays would alow it down but they did say it would be january, and if they are late people grumble and lose faith, for a phone that's sold on what it can become not what it is out of the box, losing faith means losing sales...
Bhang
xile6 said:
MY bad i meant the Engineering SPL wouldnt that still be left?
Click to expand...
Click to collapse
I am pretty sure flashing an NBH will bring you back to the original SPL. Someone correct me if I'm wrong.
They have been slow to get out updates, unless there is a exploit found.
When the bug was found everybody got rc 30 in a few days, I think that the new found downgrade route will speedup the next update to stop downgrading, if the tmob wants to keep the handset locked they will push for a speedy update to stop downgrades.
Click to expand...
Click to collapse
The problem that T-Mobile has now is that in order to stop downgrading, HTC would have to make a new SPL that blacklists the signature of RC29 NBH. Google can patch whatever they want, but I'll be able to downgrade immediately just by putting the NBH file on my sdcard and flash it via SPL
I'm curious as to why everyone assumes that the next update will make moves specifically to remove/block root for those who have it?
My understanding/interpretations of the press relases surrounding RC30 was that it was intended to fix the massive security risk in RC29. Perhaps I've missed something, but I've not seen anything that Google or T-Mobile have done specifically to counteract the "hacker" community, the blocking of the rooting method being "colateral damage" from the security fix. If the superuser method can be used to safely provide root access couldn't this be rolled Android itself? It's over my head but has this question been posed to powers that be at http://source.android.com/?
Related
I plan on rooting my phone in the next couple of days, but I was wondering if the HardSPL that you install during the "How To Root your G1" tutorial will cause any issues if I want to go back to the "official" g1 firmware from Tmobile. From reading about SPL, the stock SPL is from HTC but the HardSPL thats on the tutorial is modified. Would I replace the modified SPL if I want to go back to the official firmware?
If you look real hard, you can find a sticky about this!
But I'll be nice and sweet tonight, so here it is!
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=3e938d02f4c16b82&hl=en
vdl68 said:
If you look real hard, you can find a sticky about this!
But I'll be nice and sweet tonight, so here it is!
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=3e938d02f4c16b82&hl=en
Click to expand...
Click to collapse
Did you post in the wrong thread? That link is about rc33 OTA update. My question is about getting back to official firmware after rooting the phone and whether the HardSPL can stay or revert back to the original.
androidmonkey said:
Did you post in the wrong thread? That link is about rc33 OTA update. My question is about getting back to official firmware after rooting the phone and whether the HardSPL can stay or revert back to the original.
Click to expand...
Click to collapse
here: http://forum.xda-developers.com/showthread.php?t=455860
to go back to original everything just use the original spl in an update.zip and then use the DREAIMG.nbh from when you rooted your phone and you will have stock stuff like it just came out of the box
tubaking182 said:
here: http://forum.xda-developers.com/showthread.php?t=455860
to go back to original everything just use the original spl in an update.zip and then use the DREAIMG.nbh from when you rooted your phone and you will have stock stuff like it just came out of the box
Click to expand...
Click to collapse
So if I want to go back I would first install the rc29 then the original SPL, then upgrade to rc33?
Whats the purpose of using the HardSPL vs the original SPL?
no, do the original SPL THEN the .nbh you need to have root to flash an update.zip that is not signed with the proper keys, as for the benefits of hard SPL over the original go here and read
http://forum.xda-developers.com/showthread.php?t=455860
i took a look at all your posts and EVERYTHING you have said on the boards so far has been a question that is easily answered if you read. good luck on this phone i give you a week before i see a thread saying you bricked it
tubaking182 said:
i took a look at all your posts and EVERYTHING you have said on the boards so far has been a question that is easily answered if you read. good luck on this phone i give you a week before i see a thread saying you bricked it
Click to expand...
Click to collapse
Thanks. Some of the FAQs are not very clear. I'm not sure what you mean by EVERYTHING I've said on the board...
btw, are you hoping I brick my phone? So far I've read 4 different tutorials on how to root your phone. Each one has something different than the other. I'm just trying to get the facts straight before rooting my phone.
look for the thread "app that roots your phone" tell him in a PM that you want to beta test it, when i ran it or him on the last version he needed to fix the telnet script and he is pretty sure he got that working. i would give the link but since it is not my app it is not my place to give out the link.
i do not hope you brick your phone, but i see it as an inevitable thing, i know what i'm doing, i'm no guru but certainly not a n00b and i have managed to "brick" my phone just bout every day because i am always trying new things. the main thing to remember is that as long as when you turn your phone in you get the SPL or recovery then you do not have a true brick. i wish you the best in all your hacking but be forewarned that everything you try has the potential to render the phone unusable for a few hours till you figure out how to fix it. ALWAYS keep the DREAIMG.nbh on your sdcard and an update.zip that contains one of the many JF builds and you will never be too far from fixing your phone.
tubaking182 said:
i do not hope you brick your phone, but i see it as an inevitable thing, i know what i'm doing, i'm no guru but certainly not a n00b and i have managed to "brick" my phone just bout every day because i am always trying new things.
Click to expand...
Click to collapse
I understand. Hopefully I wont brick the phone but the nice thing about GSM phones is that I can jut pop my SIM card into my old phone if any issues come up with the G1. I just see people being mean to noobs when at some point in time they were noobs also.
The main reason I want to root the phone is to move the cache to my SD card. The onboard memory on the G1 is a joke. I knew the limitations when I bought the phone in October, but I thought for sure they would have come out with a update that lets you run apps from your SD card. Being a early adopter is fun
if you have less than a class 6 sdcard then moving the cache will have loads of lag, took 3 seconds to delete an email on my class 4. but if you just wanna move apps then you'll be fine
tubaking182 said:
if you have less than a class 6 sdcard then moving the cache will have loads of lag, took 3 seconds to delete an email on my class 4. but if you just wanna move apps then you'll be fine
Click to expand...
Click to collapse
Interesting. I may have to buy a microSDHC card since the microSD card that came with the phone has no rating on it. After reading about SDHC, it seems only SDHC has the 2,4,6 rating.
use the RC29 NBH, it flashes everything including bootloader, then use the official signed RC33 update (40mb) and you will be back to stock rc33
korndub said:
use the RC29 NBH, it flashes everything including bootloader, then use the official signed RC33 update (40mb) and you will be back to stock rc33
Click to expand...
Click to collapse
Thanks korndub
androidmonkey said:
I understand. Hopefully I wont brick the phone but the nice thing about GSM phones is that I can jut pop my SIM card into my old phone if any issues come up with the G1. I just see people being mean to noobs when at some point in time they were noobs also.
The main reason I want to root the phone is to move the cache to my SD card. The onboard memory on the G1 is a joke. I knew the limitations when I bought the phone in October, but I thought for sure they would have come out with a update that lets you run apps from your SD card. Being a early adopter is fun
Click to expand...
Click to collapse
i was a noob before i found xda.. but in the short time i have been here i have learned sooo much.. i love this site and my rooted/themed G1!
Welcome!
Hey all, Ill only ask this once, (Since after this time, Ill know for future updates and be on the right path =) )since this G1 is so new dev wise, its getting confusing when im studying everything all at once and only updated rooted once to the custom RC30. I saw the newer update is RC33, now when I apply that, is it required EACH TIME to wipe the device? Im asking cause it would be a pain to reinstall each app I had installed there to begin with. I know I wiped the 1st time I rooted and updated. So just wanted to check.
Also whats the new additions in these updates? Any good changelogs out there? I kinda like keeping the Tmobile US stuff on mine, but root access is awesome. =)
Thanks for any update tips out there atm.
Edit, My G1 is still on Firmware 1.1 is that a seperate update or how is everyone updating that with the custom stuff? Thanks. (And do I need that FW update before going RC33?)
Nope, you won't lose anything when you upgrade the firmware normally. Going from JF RC30 to JF RC33 should be fine
Check the stickied topic on the top of the forum to find out more:
http://forum.xda-developers.com/showthread.php?t=475381
The changelog is somewhere in there.
Thank you. =) I didnt read that one since it was talking about for UK users. Heh. Least it explained things a lil more. =DDD
What about the firmware? Seems Ill have to do the new radio too, but wondering.. is that radio one for US too or only uk? Since its in a UK thread. =/
Nah, it's not a UK topic. He just modifies the title when he adds something new. The radio should be for the US version. Just download the radio and JF RC33 and throw them on your microSD (one at a time obviously, named update.zip).
Firmware 1.1 is just like the base firmware number, you can ignore that. Firmware 1.5 (I think) is cupcake, so you get the idea.
Ok so the firmware is nothing major atm to update or would you still upset it? I havent looked into cupcake yet.
No, completely ignore the firmware number, the only numbers you want to look at are RC30, 33, etc...
Ok this is odd. I updated fine to RC33, however when I try to get back in recovery mode to apply the radio rom, it wont go into the recovery mode. It just keeps rebooting to the G1 screen when im holding the home button. Anyone seen that before or how to get back into the recovery mode?
Anyone have any ideas?
This is the update-link for the european version of Donut from T-Mobile!!! This is a Full-Update. You can update from any previous version of TMobile.
Link: http://android.clients.google.com/updates/kila_eu/signed-kila_eu-ota-15632.a5e2aac2.zip
Markus31415 said:
This is the update-link for the european version of Donut from T-Mobile!!! This is a Full-Update. You can update from any previous version of TMobile.
Link: http://android.clients.google.com/updates/kila_eu/signed-kila_eu-ota-15632.a5e2aac2.zip
Click to expand...
Click to collapse
what use is this? we have donut.
This is DONUT. Its the OTA Update T-Mobile releases in Europe.
Many thanks!
I have an old G1 off contract and wanted to see what TM were sending out. Much better than waiting for their OTA release schedule.
When I really get the feel of what the G1 can do I will play with some other updates from xda-dev but this one feels a bit safer whilst I build some knowledge!
Presumably rooting this will be a similar process to before? I do find navigating the threads on various releases, updates, hacks, etc on here a little confusing, never quite sure if what I have read is current knowledge or not! Hence the need for more time to get knowledge.
This went well; download to SD root, rename update.zip and power on holding end+home and the when logo is displayed, ALT+L then next icon, ALT+S to start the process. Watch the various reboots and finally Donut on TM G1 is running.
Cheers!
donty said:
Presumably rooting this will be a similar process to before? I do find navigating the threads on various releases, updates, hacks, etc on here a little confusing, never quite sure if what I have read is current knowledge or not! Hence the need for more time to get knowledge.
Click to expand...
Click to collapse
Rooting by downgrading to RC7 will still work. Instant-root by flashrec.apk won't.
Rooting about...
Thanks, I will need to check up what the rooting process is doing, I need to merge my linux knowledge with all this and see where things touch!
I don't want to hijack this and I will obviously search but if you have any specific/good sources I would be grateful for links or pointers.
Ok, just like all of you I have rooted, experimented to the limits and pushed them well little did i Know is that you cant reflash the 1.56 ruu so needless to say I ended up with a brick but luckily for us it will still connect in fastboot
so this is a solution to at least get it up and running
Pros-
Reactivate your phone since it will be formated
All functions will work
can still root, install .apk's use wifi etc
camera etc
so the pros are it will operate just like nothing ever happened now to the con's
YOU WILL HAVE TO DO THIS EVERYTIME YOU TURN OFF YOUR DEVICE
Ok here is how to fix it
Connect your phone to your PC
open command and navigate to your android tools folder
type in
fastboot devices
make sure it detects your device
should show the HTC logo on your phone
now simply type
fastboot oem boot
wait a couple minutes while your phone reboots
viola you phone is back to running again...just dont turn it off LOL
can you launch the RUU again and (hopfully) have it restore your phone correctly?
You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet
rayborn said:
You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet
Click to expand...
Click to collapse
hmmmm interesting man. honestly you should be able to rebuild all the / partitions. such as /misc and /radio. we need some linux junkies in this thread to tell us how to rebuild failed / partitions
This is amazing. Sure did work for me. I just wish there was a way to get it flash the original radio. I have only had this thing two weeks and would love to take it back and exchange it, but I am just paranoid since it shows radio 2.41.04.02.03.
wait, what exactly did you do to get your near-bricked phone?
you used the 1.56 RUU on your phone that had a 2.xxxxxx radio?
have you tried both of the RUU's? the original and 1.56?
My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution
did you try the 1.29 RUU?
yeah i tried every sprint hero ruu i promise you i left no stone unturned trying to fix this
BRILLIANT!
I can't tell you how impressed I am that somebody has found what i now consider to be the first step towards getting the RUU 110 error solved.
I still feel that the issue comes down to the lack of ADB that seems to happen once you get 110... maybe a driver issue on the phone vs. driver issue on the computer? after all the RUU starts failing on all the ADB commands when you check out the RUU logs...
sorry i can't help take it from there, i returned my phone to sprint inside of the 30-day window and just told them something i installed form the market "bricked" my phone...
I eagerly await your results though for a final step towards solution, as I am dreading the day i have to RUU my phone for whatever reason that may be, although I've been running a personally customized Pancake ROM for almost a week and totally happy with it so won't be doing anything until 2.1 is official...
R
rayborn said:
My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution
Click to expand...
Click to collapse
Same exact thing for myself. Multiple people said the way to go back to the stock radio was to use the RUU. I tried both RUU's and same results. Now I am just trying to decide what is better.
Live with this and hope for a better option to come or take back a "bricked" hero that shows Radio 2.41.04.02.03 and hope I don't end up getting charged later.
IMHO I think the best thing for you guys to do is wait for our 2.1 update, which will more than likely have a smiliar radio update. Then you can just say the update bricked the phone.
If we get the same radio version, then just take it back, if we get a different version then maybe we can find a file to edit the number to make it say what ever version you want it to say, something like editing Build.prop. Then Sprint has nothing to ask questions about. Should be out in a few weeks if the rumors are right. Maybe you can deal with this soultion until then.
As far as the don't turn your phone off issue, mines been up for 13 days. I hate turning it off, partially because of the missed emails and partially because I worry that it won't come back up.
Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?
SamXp said:
Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?
Click to expand...
Click to collapse
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?
mginther said:
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?
Click to expand...
Click to collapse
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen
tatonka_hero said:
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen
Click to expand...
Click to collapse
True, and if we elect to continue to use either a Fresh or Damageless version of an official 2.1 Sprint ROM, then we should be ok. But if we wanted to go to the Sprint ROM, there are going to be a lot of bricked phones if there isn't a way to understand what is going on when a 1.56 RUU is used over a phone with the 2.x Radio update.
Just wanted to pass along some more information in case anyone else is having this problem. I had reactivated an old phone temporarily since this one was bricked. This morning I reactivated my hero due to this semi fix and immediately I could call and textimg was fine, but i kept getting vision error 67 for data. Sprint reset my data about three times and it never worked. I tried updating my profile multiple times and it never worked. Finally I Ran the RUU again and sure enough after a reboot or an "oem boot" I had error 67again. I went ahead and updated my profile and this time it worked and data started working. Still hoping someing else comes along though.
well I think the issue here might be that it does not have the recovery backup on it after you do an RUU. I could be wrong but who knows? I would say install flashrec-1.1.3-20091107-2.apk on your phone once you are able to get it up and running then flash the recovery backup and restart. That could possibly fix the issue? I have the files if anyone needs them, I'm not sure how to upload them on here...
~Danny
I'm not sure if it's possible boot into recovery console using this method, but if you can, has anyone tried manually flashing the old radio in the same manner they flashed the new one to revert back and then RUU. Perhaps that may do the trick.
My phone isn't bricked so I can't try it out, but seems like it might be worth a shot in theory.
Here is the RUU for the OTA ATT 2.20 update.
Warning if you use this RUU you cannot go back to a lower RUU ( 1.85, etc ) or lower firmware as the HbOOTS are different! This is more for us that have already done the update. This will help us get back to stock if something goes foul.
There is no benefit for anyone to run this RUU as of now until root, etc is sorted out. Like I said for now mainly for us that already updated.
Thanks to scrolser for the link and DvineLord for initial find
Issues:*
1. If you update you will get a newer hboot, you may not be able to use other older ruu's such as 1.85, etc. Recommend immediately making a backup once rooted, unlocked, etc.*
2. Updating results in boot.IMG from custom roms not being flashed again. Have to flash the boot.IMG of custom Rom in fastboot as before.*
3. Radio.img will not flash on new hboot either must be done in fastboot same as boot.img.
HTC One X for AT&T ROM Update | 8.02.2012
Starting August 2nd 2012, HTC will be rolling out a system update for the HTC One X.
This update will only be available for AT&T HTC One X customers and will be sent to the device over the air. Once the release is ready, users will receive a notification on their device advising them of this update and provide instructions to receive and install it. Users can proactively check for this update by going to Home > All Apps > Settings > AT&T Software Update > Check for updates.
As an alternative solution, the system update can be downloaded to a PC and manually applied to the device. See the section at the bottom of these instructions for more information.
This system update includes:
New features:
NFC Capabilities
Additional content added to HTC Hub
Third party music applications accessible from the Car application.
Fixes/Updates:
Wi-Fi connectivity fixes
Improved Bluetooth automobile compatibility
3G/4G connectivity improvements
HTC Sense fixes
Contacts synchronization fix
Network time fix (clock displays 30 minutes off)
WARNING: During the upgrade process the device will reboot multiple times and show software upgrade screens. Do not remove the battery as this will stop the update and your device may be rendered inoperable!
Getting Started
Before you proceed with the update, make sure you have done the following:
Set aside approximately 20 minutes to allow the device to update, possibly longer based on Wi-Fi network speed
Connect the device to a charger
Ensure the battery is charged to at least 30%
Connect to a stable Wi-Fi network to download the software file.
Installation instructions
To manually perform the update, follow these steps below:
From the Home screen, tap All apps and then tap Settings.
Tap AT&T Software Update.
Tap Check for updates.
Tap OK to download the update.
After you select your method of download, you will be prompted with a Wi-Fi or Data fee warning message. If this is acceptable, tap OK to start the upgrade process.
Status of the download can be viewed in the Notifications pull down.
Once the download is complete, the user will be prompted to install from the Notifications pull down. Tap the System update to begin the upgrade process.
Tap OK to begin the update process to software version 2.20.502.7.
Device will reboot and begin installation. Users will not be able to use their device during the installation process (approximately 10 minutes).
System update complete. Tap OK to continue
Manual system update instructions:
If you are outside of AT&T/Wi-Fi coverage, or the update is not found, you may perform a manual system update.
Performing the system update manually will delete all information from the device. Ensure all information is backed up before proceeding. See the Help & How To section of this website for more information on backing up your device contents.
Performing the ROM Update:
Download and save the HTC One X™ for AT&T ROM update to your PC.
Connect your device to your PC via the supplied USB cable. NOTE: You must have HTC Sync Manager installed on your PC in order to run the update.
NOTE: If you do not have HTC Sync Manager installed already, you may download the software from http://www.htc.com/us/support/.
Ensure the device is properly recognized on the PC, then locate the HTC One X™ for AT&T ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
Follow all of the system update wizard instructions shown on your PC.
Once the update is complete, click Finish in the Wizard and the device will reboot.
Once the device reboots, the initial setup wizard will appear.
Once the initial setup process is complete, the device is ready for use.
Download
portions of this post copyright HTC 2012. All rights reserved to them.
kewl
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
.
Third party music applications accessible from the Car application.
Click to expand...
Click to collapse
WOOT.
Thank you for not using File Factory haha
"NFC capabilities"????
Sent from my HTC One X
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
XsMagical said:
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
Click to expand...
Click to collapse
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
slippers67 said:
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
Click to expand...
Click to collapse
yeah if you know what you're doing, but damn I'm going to miss the one stop flashing we used to have.
eraste said:
Here is the RUU for the OTA ATT 2.20 update.
Warning if you use this RUU you cannot go back to a lower RUU ( 1.85, etc ) or lower firmware as the HbOOTS are different! This is more for us that have already done the update. This will help us get back to stock if something goes foul.
There is no benefit for anyone to run this RUU as of now until root, etc is sorted out. Like I said for now mainly for us that already updated.
Thanks to scrolser for the link and DvineLord for initial find
Click to expand...
Click to collapse
I thought that was good?
XsMagical said:
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
Click to expand...
Click to collapse
This was to be helpful for us that already did OTA. I agree tho if one isint literate in the world of android wait to use this until all the things above are worked out.
scribed on my 2.20 HOX
slippers67 said:
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
Click to expand...
Click to collapse
yea thats fine if you know how, but why make everyones life harder when this upgrade is older then the asia 2.23.
its just going to make a lot of un needed posts to developers asking why the rom dont boot and so on. Run this ruu and it will cause more problems then anyone needs. As well as set you back from any S-Off development.
But that is my warning. Just saying, i cant see it from my house, my phone flashes
kernels just fine and always will. One Stop flashing.
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
gunnyman said:
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
Click to expand...
Click to collapse
I know i am, Ive been down this road several times in the past and i know what to flash and not to flash. That being said, I,m just trying to warn anyone that thinks the ruu is better then the rom alone...
gunnyman said:
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
Click to expand...
Click to collapse
I prefer ATT based things, not racist lol just prefer the ATT stuff it works better for me as I'm in America. I would like to think root, mount points, etc will be available so everyone can benefit. This is important because of your statement. Anyone needing a new phone now for some reason be it broken, screen etc will get this build. Not 1.85 anymore. I definitely don't think it needs to be backseated just because asia is 2.23. Us in America will be screwed as new phones ship with 2.20 not 2.23. I have faith lol who knows new hboot may have a flaw that finally allows s off.
scribed on my 2.20 HOX
To be honest I jumped on the update. It fixed a lot of the issues I had with 4.0.3 sense. I still have my unlock and I'm rooted. These times are like mini vacations from flashing. I also happen to have confidence in you devs, and also know that sooner or later (probably later) HTC will release source for this updated kernel and the dev will kick off again.
Although I don't envy you devs having to deal with people who don't read.
Thanks eraste for posting this as well as the guide for updating safely.
Sent from my HTC One X using Tapatalk 2
Nrod0784 said:
To be honest I jumped on the update. It fixed a lot of the issues I had with 4.0.3 sense. I still have my unlock and I'm rooted. These times are like mini vacations from flashing. I also happen to have confidence in you devs, and also know that sooner or later (probably later) HTC will release source for this updated kernel and the dev will kick off again.
Although I don't envy you devs having to deal with people who don't read.
Thanks eraste for posting this as well as the guide for updating safely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Anytime
scribed on my 2.20 HOX
eraste said:
I prefer ATT based things, not racist lol just prefer the ATT stuff it works better for me as I'm in America. I would like to think root, mount points, etc will be available so everyone can benefit. This is important because of your statement. Anyone needing a new phone now for some reason be it broken, screen etc will get this build. Not 1.85 anymore. I definitely don't think it needs to be backseated just because asia is 2.23. Us in America will be screwed as new phones ship with 2.20 not 2.23. I have faith lol who knows new hboot may have a flaw that finally allows s off.
scribed on my 2.20 HOX
Click to expand...
Click to collapse
Well I'm in america too! but i thought a warning would be nice, But what do i know
i think his warning was sufficient enough. he stated no benefits of flashing. unless you already did it prior. plus there are other threads who state warnings as well. people dont care or dont read and will flash anyway :laugh:
not taking sides i see what people do here that go against there better judgments or even when told not too :laugh:
Drop box just suspended my public links for excessive traffic lol lame. Changing hosts now sorry guys.
eraste said:
Drop box just suspended my public links for excessive traffic lol lame. Changing hosts now sorry guys.
Click to expand...
Click to collapse
whoa and i just downloaded too lol. just in time add to the RUU collection lol