Hello... first time poster here... if i install CM9 ( when stable is released), will i still be able to receive OTA updates..?? Im so interested in a more stock android experience, but i also want to keep OTA updates. Currently i am rooted but havent flashed a rom or nothing, and i still get the OTA updates. Thanks in advance to anyone that answers.
Sent from my SAMSUNG-SGH-I747 using xda premium
No and with all the **** going on with Apple right now you want to avoid an OTA as much as possible.
Sent from my Samsung Galaxy S III via Tapatalk II.
CM will incorporate things like updated radios, but many updates won't apply to your version....
Sent from my AT&T Galaxy SIII (SGH-i747)
Well how about, lets say the jelly bean update or security updates specifically for ATT model.... will those updates go through??
Sent from my SAMSUNG-SGH-I747 using xda premium
uzii305 said:
Well how about, lets say the jelly bean update or security updates specifically for ATT model.... will those updates go through??
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Short answer: no. If you're running CM you're on a completely different build than the version of Android/Touchwiz that ships on the device.
Longer answer: Both CM and the build that ships with the device are obviously both derived from the same source: Google's Android. So if Google fixes security problems in Android, then theoretically the CM guys should be packaging those into the next update of CM. If there is a security flaw specifically in the AT&T version of the phone, then it was probably caused by something custom that AT&T built into Android, in which case you won't get that update - but you wouldn't need it because you wouldn't have had the custom code that caused the flaw in the first place. Does that make sense?
Like eagle said, when on a custom ROM you are on your own and you don'T depend on Samsung or your carrier for updates, you depend on the developpers of the ROM. So you will probably get JB faster with CyanogenMod than with Samsung so it doesn't matter.
Related
http://www.androidpolice.com/2011/1...on-their-nexus-s-phones-dogfooding-has-begun/
Already posted in this topic...
http://forum.xda-developers.com/showthread.php?t=1359413&page=6
But everyone isnt reading that topic, definitely deserved a new thread
So its almost complete
Sent from Oxygen 2.3.2 powered Nexus S 4G
Just curious, how long do previous iphone models get the latest iOS update when a new iphone comes out? Is it same day or shortly after?
I'm glad to see Google is closing the time between a Nexus device launch and past device getting the latest Android update.
onthecouchagain said:
Just curious, how long do previous iphone models get the latest iOS update when a new iphone comes out? Is it same day or shortly after?
I'm glad to see Google is closing the time between a Nexus device launch and past device getting the latest Android update.
Click to expand...
Click to collapse
Older IOS devices get it on the same day, or a couple of days before the new Iphone is released.
For Example IOS5 came out on Oct 12 this year and the Iphone 4S wasn't released until Oct 14..
its easy when they only have one or two other architectures to worry about. with the ns theres at least 3 i think
That's a good idea for an internal test. Can't wait!
Sent from my GT-I9100 using xda premium
well i tried my little ace up my sleeve. downgraded back to 2.3.4 stock prerooted, to see if i would get and no go lol. it just prompted me for gingerbread 2.3.7 updating. worth a shot i might try this everyday.
Not that it will likely matter for you but even your phone was first in line for the ota up to ics, you would almost certainly get the ota update up to 2.3.7 if you're sprint and 2.3.6 for gsm. prior to ota notification for 4.0
So if you're going to do revert to stock and hope you're first to get the ota thing, make sure it is actually the latest stock.
This just makes me all the more eager to get the ota on my phone.
i have an employee edition i9020....can u please tell me how should i turn my phone to stock to check for OTA
mohsin125 said:
i have an employee edition i9020....can u please tell me how should i turn my phone to stock to check for OTA
Click to expand...
Click to collapse
Somewhere in this thread is the stock rom images for your variant of nexus s.
REF] ALL Nexus S OTA Updates for ALL Variants, Plus Full ROM Packages
http://forum.xda-developers.com/showthread.php?t=1063664
Sent from my CM9 Alpha10 Linux S 4G using xda premium
alright...so once i flash the stock rom, will it be able to catch ota updates? or do i need to revert stock recovery too? finally what about root? should i unroot it to get the OTA?
And there is no employees edition of the phone. The limited edition phone ( battery cover) is not a "employees edition"
but i knw this one is the early model which was givn to employees
That's true. You will always get the next in line OTA. I remember that's how it was on my Nexus One.
mohsin125 said:
alright...so once i flash the stock rom, will it be able to catch ota updates? or do i need to revert stock recovery too? finally what about root? should i unroot it to get the OTA?
Click to expand...
Click to collapse
You get the OTA only on stock,non-rooted, out-of-the-box rom.
False. It does not matter if you're rooted. Or if custom recovery
Ima wait till its rooted and flashable
Sent from Oxygen 2.3.2 powered Nexus S 4G
With talks of 4.1 of 5.0 being announced this approaching week at Google I/O, and hopefully us Note users getting it, I'm a little concerned for those of us on an ICS kernel potentially infected with the ICS brick bug. Will it be safe for us to update our advices still through Kies on stock firmware?
I'm pretty sure that if Samsung decides to build 4.1 update for Note they will make sure to eliminate this problem, especially now when they're aware of it and know what and how causes it.
Akiainavas said:
I'm pretty sure that if Samsung decides to build 4.1 update for Note they will make sure to eliminate this problem, especially now when they're aware of it and know what and how causes it.
Click to expand...
Click to collapse
So, whenever the next update from Samsung comes out, be it 4.1, 5.0 or just some bug fixes for ICS 4.0, it should be safe to update?
Brad387 said:
So, whenever the next update from Samsung comes out, be it 4.1, 5.0 or just some bug fixes for ICS 4.0, it should be safe to update?
Click to expand...
Click to collapse
If it's an official update, yes. But, if it does mess up and you haven't done anything to void the warranty, Samsung would fix it (or should).
But, I don't know if we will get an update or not.
From reading entropy's thread and getting an idea of what's been done before on other devices, its likely that Samsung will simply release an updated kernel without the emmc format command, thereby bypassing the issue, rather than an actual firmware update to correct the flawed emmc bug. If this is the case I would suggest it would be safer to first downgrade the kernel to a safe stock gb kernel before performing the upgrade.
That's all supposition though, until Samsung release an official statement we won't know what avenue they are taking. I really don't see why they wouldn't release a firmware update, perhaps it would mean everyone having to send they're phones in for the update to be applied rather than being able to do it through kies ourselves.
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
Samsung not prividing 4.0.4 update to s2 as per phonearena.com. So it is sure they will not update our handset to 4.1 or 5.0
Sent from my GT-N7000 using Tapatalk 2
shantanubarik said:
Samsung not prividing 4.0.4 update to s2 as per phonearena.com. So it is sure they will not update our handset to 4.1 or 5.0
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Not necessarily... the s2 was released 6 months before the note. Update cycle is usually 18 months.
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
I received my note yesterday it was ISC by default lol, but facing some issue.
I am running the odexed version of the stock ROM with custom recovery. I am also running twrp (custom recovery).soo will I be Able to update to key lime pie without any problem?
albysajan said:
I am running the odexed version of the stock ROM with custom recovery. I am also running twrp (custom recovery).soo will I be Able to update to key lime pie without any problem?
Click to expand...
Click to collapse
[TL;DR] No.
Well, the stock ROMs are also odexed - I think the problem will be the zipaligning of the factory .apk files. Even though they are functionally equivalent to the originals, they will have different checksums than the originals, and thus every one of them that undergoes an update will fail the initial checksum verification.
Yes and no; when it goes out ota it won't flash properly because you have a custom recovery. However, wait half a day after the update comes and I'm sure someone will have a flashable version uploaded to these forums.
Sent from my Nexus 7 using xda app-developers app
I'm gonna update my answer above - I'm guilty of not reading your post carefully.
I had a look at
[ROM][Factory Image][4.2.2] Nakasi -::- Odex, Deodex, Rooted -::- teshxx (02/14/13)
and the dev does not mention "zipalign". Moreover, you said "odexed", which is closest to the Factory ROM as it is also odexed.
So long as teshxx literally did not touch either the .apk files, or their corresponding .odex files from the factory ROM, then the OTA won't fault out on initial checks because of those specific files on the odexed version of his ROM. (Disclaimer: I did not download his ROM and verify that this was the case).
It is possible that it will fail for other reasons though. Simply put, the OTAs are not intended for patching anything other than pure stock ROMs. (Also note that some root-aware apps modify /system; so even if you didn't directly alter things that will break an OTA, by granting these apps root privilege, it might happen anyway).
Who said the N7 was getting Key lime Pie? I think you are jumping the gun a bit since it hasn't officially been anounced. I am still waiting for JB for my TF101.
AW: [Q] Updating to keylime pie!
as if there is even the slightest chances for the nexus 7 not to get official klp...
Sent from my Galaxy Nexus using xda app-developers app
jadesse said:
Who said the N7 was getting Key lime Pie? I think you are jumping the gun a bit since it hasn't officially been anounced. I am still waiting for JB for my TF101.
Click to expand...
Click to collapse
Its a nexus device. We will be among the first 5 devices to get the new os, whatever they call it. That is one of the lead reasons for buying nexus devices.
Sent from my SGH-I727 using xda premium
I'm sure someone will have a flashable version uploaded to these forums.
rebel1699 said:
Its a nexus device. We will be among the first 5 devices to get the new os, whatever they call it. That is one of the lead reasons for buying nexus devices. Where as for you, you have to wait for google to release, then for asus to do what they want to it (bloatware, drivers,......) and then release it to the end user. All we have to wait on is for google to release for the grouper. Nexus devices get ours straight from google, and 100% aosp. I would imagine we will get it directly after N10, N4 and whatever new device may or may not debut.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Dang-it, i replied to myself instead of edit.
Sent from my SGH-I727 using xda premium
How about you wait for it to be released first, then weigh your options? This thread is absolutely pointless.
I have an AT&T LG G2. On my previous phone, after I accepted the OTA for 4.1.x to 4.3 on a Galaxy S3, it was a nightmare. I couldn't get su to run, and I got all kinds of security errors (apparently from KNOX), and not just for superuser. Even though I read several threads about it, I never was sure if it was 4.3 at fault -- which does seem to have some issues per Chaintech -- or if it was Samsung's KNOX, or both. So I certainly want to do my homework before I do that on my new LG.
Which is asking at least these questions:
Should I bother updating from 4.2.2 to 4.3 on the G2?
(I've read the technical differences, which seem to be incremental. I just want opinions here. For example, things like the new Camera UI may be irrelevant considering LG's customizations already in place with 4.2.2.)
If it isworth upgrading, will it retain root with an OTA? If it doesn't, what is the best way to go about restoring it in 4.3?
This firmware is probably the first I've ever seen, and that's a lot since first adopting the original T-Mobile G1, where I didn't want to replace the ROM. It's that slick. For now, I just need root and a custom recovery.
TIA.
Stay away until official release by att or lg
Sent from my LG-D800 using xda app-developers app
lingarajug said:
Stay away until official release by att or lg
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
Well, I'm not sure how much more official the Over-The-Air update from AT&T could be.
By the way there is no official 4.3 for g2 yet.
Sent from my LG-D800 using xda app-developers app
lingarajug said:
By the way there is no official 4.3 for g2 yet.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
Hmm, this seems to be the case, now I'm reading they may skip over 4.3 completely. This update it's offering to install is a bug fix and remains at 4.2.2. It's like 57MB, so I assumed it would be 4.3 as my Galaxy SIII got that a while back (and blew up, hence this whole thread).
I'll probably wait until KitKat comes out, then. I really like the LG ROM, and I just wanted root for backups, ad blocking, etc. I've run CyanogenMod since back when it was called JesusFreke, but then I'd have to reinstall everything and all that jazz. Question is, can I wait until Q1 2014.
Figuring that the stock one is so locked down, is it possible to take new features of an ota of the regular s5 and flash it to a dev edition one without messing up root? Things like updated boot, going from 4.4.x to 4.5, etc?
I recall but never fully understood that was the problem with the s4, they never sent out ota update for the dev edition....
Just debating getting an s5 dev edition, but don't want to be stuck with original firmware/software
Sent from my SM-G900V using Tapatalk
808phoneaddict said:
Figuring that the stock one is so locked down, is it possible to take new features of an ota of the regular s5 and flash it to a dev edition one without messing up root? Things like updated boot, going from 4.4.x to 4.5, etc?
I recall but never fully understood that was the problem with the s4, they never sent out ota update for the dev edition....
Just debating getting an s5 dev edition, but don't want to be stuck with original firmware/software
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
I believe you can upgrade from 4.4 to 4.5 but have to flash a unlocked bootloader like one from t-mobile or a international version. From what I gather from the Note 3 thread that's pretty much how they do it.
Well I know the s4 dev edition's problem was that they wouldn't update firmware for it, stuff like the boot (I forget which other things weren't able to get updated since they weren't sending out otas), which left the device with only it's original firmware
Sent from my SM-G900V using Tapatalk
You'll be able to do some stuff. Consider how cm releases updated firmware even though the carrier doesn't make a release. It's tough but possible.
Sent from my SM-N900V using Tapatalk