• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

4.4.2 update

So,if they roll out updates gradually,how have some people got 2 updates and others,like myself don't have 1 yet ?.

Whats a VM ?
 
So,if they roll out updates gradually,how have some people got 2 updates and others,like myself don't have 1 yet ?.

Whats a VM ?

VM=voicemail

As far as the other question, that is exactly why Google does staged updates. 4.4.1 must have introduced some bugs, which they then patched with a second update less than a week later. That also helps to explain why people aren't getting the 4.4.1 then 4.4.2, but rather jumping 4.4.1 entirely and going straight to 4.4.2

Google acted quickly and patched bugs, but some users are getting upset because they didnt get the buggy update first? Now isnt always better, let others be the guinnea pigs once in a while. ;)
 
Got the 4.2.2 OTA here in UK.

Strangely I only saw the 4.2.2 update of 54mb and nothing of a larger 4.4.1 file. I wonder if it's been dropped or was stealthed in beforehand..?
 
Got the 4.2.2 OTA here in UK.

Strangely I only saw the 4.2.2 update of 54mb and nothing of a larger 4.4.1 file. I wonder if it's been dropped or was stealthed in beforehand..?

4.2.2 by itself was only something like 1.7MB

You got both updates rolled into 1 (4.4.1+4.4.2)
 
I thought I could not get ota when rooted. I am rooted and installed 441 from zip file in custom recovery and just got the 442 ota notif.
 
I thought I could not get ota when rooted. I am rooted and installed 441 from zip file in custom recovery and just got the 442 ota notif.

You can get OTA's if you're rooted, though they'll likely break root unless your using SuperSU Pro's survival mode. If you're on the stock rom, you'll get pinged for the update. However, if you've modified the system partition in any way due to your rooting, or don't have the kernel, radio, or bootloader that match your os version, the update will fail in recovery.
 
All I did is applied root the old fashion way manually and installed free supersu. Did not change anything else.
Tried the ota but gave me an error but don't remember which on.
Trying manual through teaamwin recovery with zip file and getting error "system/bin/debuggerd" has unexpected content.
Is there any way to install the update without reflashing system.img? I don't Can I just delete that file?
 
All I did is applied root the old fashion way manually and installed free supersu. Did not change anything else.
Tried the ota but gave me an error but don't remember which on.
Trying manual through teaamwin recovery with zip file and getting error "system/bin/debuggerd" has unexpected content.
Is there any way to install the update without reflashing system.img? I don't Can I just delete that file?

I usually get errors similar to that, and the safest thing to do is just reflash the system.img. I'd rather not mess with anything in the system folder that I'm not sure with and send my device into a perpetual bootloop.
 
I usually get errors similar to that, and the safest thing to do is just reflash the system.img. I'd rather not mess with anything in the system folder that I'm not sure with and send my device into a perpetual bootloop.
oops I missed a part. By reflashing system.img I will have to reinstall all my apps right? I eddited that file with a text editor and it is all written in Chinese.
 
For those who haven't received the OTA yet try turning on Wi-Fi and wait and see if you get the update cause it requires Wi-Fi to download
 
I just got the 4.4.2 update today on att. I went from 4.4 to 4.4.2 . I can confirm that the speaker is so much loader. The phone rang right after it finished updating and I literally jumped out of my skin. The camera is much improved. Shutter and auto focus are much faster now. Literally everything about the camera is improved.
 
I'm pleased with the camera, finally some shots of my son playing where I can actually see him.

I'm undecided on the speaker volume level, but as I said I wasn't bothered by it anyway.

No other previous issues so nothing else to report!
 
Went to 4.4.2 today

Camera shutter is much faster
Volume during YouTube or while on speaker phone is much louder, as is the volume of the phone itself and all that.

However I'm getting a replacement because the audio for Video is still terrible. Sounds like muffled hissing during video playback. Some have said it must have something to do with noise cancelation.
Hopefully the replacement doesn't have this issue.
 
I'm so very confused.

I'm on stock 4.4.1 ROM rooted with Franco r20 and CWM Recovery.

Today I got prompted to OTA update to 4.4.2 and I laughed a bit. I figured I had a good backup, so I gave it a shot.

I rebooted into CWM and prompted me to accept the installation.... installed... rebooted, kept root, and Franco kernel.

I looked at the build and it's 4.4.2 KOT49H with the .23 baseband.

I thought this wasn't possible and I'd have to do all sorts of flashing of .imgs in adb and such. What happened? Anyone else have this experience? Is there a feature in CWM that allows it to install the OTA without a problem?
 
I'm so very confused.

I'm on stock 4.4.1 ROM rooted with Franco r20 and CWM Recovery.

Today I got prompted to OTA update to 4.4.2 and I laughed a bit. I figured I had a good backup, so I gave it a shot.

I rebooted into CWM and prompted me to accept the installation.... installed... rebooted, kept root, and Franco kernel.

I looked at the build and it's 4.4.2 KOT49H with the .23 baseband.

I thought this wasn't possible and I'd have to do all sorts of flashing of .imgs in adb and such. What happened? Anyone else have this experience? Is there a feature in CWM that allows it to install the OTA without a problem?

Normally this would have failed. However the update to 4.4.2 was so specific to the system partition, that it would be allowed to be taken because you hadn't modified any of the areas being overwritten. There was no kernel patch with this update, which is why it allowed the ota to be taken with a custom one.

If you had franco kernel on 4.4 and tried to go right to 4.4.2, it would have failed because there would have been a kernel patch in that update.
 
I agree it is slightly unfair that we purchase the newest Nexus and still don't get new updates first. Still stuck on 4.4, patiently waiting for 4.4.2. Hopefully tomorrow! But anyway, it does dissapoint me to know that Nexus 4s and 7s are already running 4.4.2 while I'm still rocking OG KitKat.
 
I agree it is slightly unfair that we purchase the newest Nexus and still don't get new updates first. Still stuck on 4.4, patiently waiting for 4.4.2. Hopefully tomorrow! But anyway, it does dissapoint me to know that Nexus 4s and 7s are already running 4.4.2 while I'm still rocking OG KitKat.

Nexus devices get the updates first.

Updates roll out over a 1-2 week period by random lottery by your device ID

If you have a nexus 5 you're in a lottery with all the other nexus 5s for the update. At the same time the nexus 4 and nexus 7s have their own separate lottery for each device. It starts out that roughly 1% of devices get it the first day, and it ramps up to 100% over the following week. This is to ensure the safety of the update.

The update comes out at the same time for every nexus. If you haven't gotten it yet your device ID hasn't been chosen in the lottery
 
I agree it is slightly unfair that we purchase the newest Nexus and still don't get new updates first. Still stuck on 4.4, patiently waiting for 4.4.2. Hopefully tomorrow! But anyway, it does dissapoint me to know that Nexus 4s and 7s are already running 4.4.2 while I'm still rocking OG KitKat.

If a Nexus device is within the 18 month window that Google promises updates for, then it doesn't favor one device over another unless and issue is device specific due to hardware. If you're on a device that gets the update, the over their air update is passed out randomly. However there are two officially supported ways of installing it manually. You can sideload the ota file through the stock recovery, or flash the factory image through the bootloader. It doesn't take longer than 5 minutes to do either and can even be automated through toolkits if you're really nervous or lazy.
 
Back
Top Bottom