13
Feb
image

Good news, everyone! The Nexus 4 Android 4.2.2 OTA (JDQ39) is finally here, surprisingly late in the update cycle, following the Nexus 10 and older Nexus devices, such as both variants of the Nexus 7 and both variants of the Galaxy Nexus. Chances are you probably don't have the coveted update notification just yet, but who wants to wait if you can sideload it manually? Rooted, unrooted, stock or custom recovery - it matters not.

What's New?

To see what's new in Android 4.2.2, see New Android 4.2.2 Features: Toggle From Quick Settings, Better App Download Notifications, and Some New Sounds!

There is also a new radio in this update.

Heads up: The new radio removes LTE Band 4 support.

Prerequisites

Your device should be running build JOP40D before trying to install the update manually. If you for some reason don't have JOP40D, Google has it available in factory image form here.

For those ready to download and install manually, the process is easy. If you

  • have a custom recovery, just download the zip (linked below), move it to your device, and flash as usual
  • have the stock recovery or a custom recovery that supports sideloading, keep the zip file on your computer and follow a few easy instructions below

Manual Instructions

Disclaimer: Android Police isn't responsible for any harm to your device - proceed at your own risk.

Step 1.

Reboot your Nexus 4, holding the Volume Down button while it boots up. Once you see the fastboot menu and "Start," press Volume Up to navigate to "Recovery" and press the power button. Once you see an Android with a red exclamation point icon, hold Power and press Volume Up a few times, which will bring you to a new menu. Navigate to "apply update from adb."

wm_20130213_163021

Step 2.

Connect your Nexus 4 to your computer with a USB cable.

Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).

Open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the zip file you've downloaded.

Type in the following:

 adb sideload de8b8d101614.signed-occam-JDQ39-from-JOP40D.de8b8d10.zip

You should see a progress bar, which will eventually hit 100%. At this point, your device is installing the update.

Step 3.

Reboot and enjoy! You are now running Android 4.2.2 on your Nexus 4.

wm_n4 4.2.2

Download

Here's the OTA, hosted on Google's servers: build JDQ39.

MD5: 1c752738f65acfd48f2d3b6e6e11a654

File size: 51.0 MB (53,529,568 bytes)

Thanks, Jdban101, @Coentje44, and everyone else who sent us a tip!

Artem Russakovskii
Artem is a die-hard Android fan, passionate tech blogger, obsessive-compulsive editor, bug hunting programmer, and the founder of Android Police.
Most of the time, you will find Artem either hacking away at code or thinking of the next 15 blog posts.

  • T54

    Does this break LTE support in Canada?

    • Terry Cameron

      Yes

      • Esmail Sewid

        Why would they break the LTE support. I wonder if its going to carry over into the U.S. on Att and Tmobile

        • Chronus719

          They would likely kill LTE support because somebody somewhere got mad at them for keeping the feature accesible even though they hadn't paid licensing fees for LTE on the modem they used.

          • Esmail Sewid

            Screw you too FCC

    • Daniel Pogue

      Broke it for me...

      • Bob G

        Did you try the other options instead of "LTE Only"?
        The other options seem to not revert back to "WCDMA preferred".

        • Rohin Galhotra

          They do if you leave and then go back.

    • http://www.androidpolice.com/ Artem Russakovskii

      I bet it's somewhere here https://gist.github.com/archon810/4773040, but I can't track down which change did it.

      • http://twitter.com/Kartik_N Kartik Nagarajan

        If someone is on 4.2.1 and in an LTE zone, can you try flashing the .48 radio from this thread and see if it still works. I'm just outside the coverage area for Rogers so I can't test whether it can be fixed by downgrading the radio.

        thread: http://forum.xda-developers.com/showthread.php?t=2087227

        • http://www.androidpolice.com/ Artem Russakovskii

          Ok, so it was in the radio. Probably not in those changelogs after all then.

  • Jason Banich

    Why oh why did I uninstall currents! It won't verify

    • Michael Katz

      So download currents from the play store, move it to system and try again.

      • Jason Banich

        Exactly what I am trying :)

        • Greg Sanders

          Remember I think you can freeze currents if you just want to save battery.

          • Jason Banich

            Yeah, that's what I should have done :)

    • mikeym0p

      Hey I dont blame you! haha

  • mikeym0p

    I keep getting a status 7 error: asset failed: apply patch check /system/bin/thermald
    Does anyone know what to remove from the script in the .zip to remove the 'verifying system' part of the install process?

    • Jason Banich

      Stock kernel is here, give it a shot http://forum.xda-developers.com/showthread.php?t=2024982

    • http://www.androidpolice.com/ Artem Russakovskii

      Definitely - you need to be stock enough that the incremental updates in this zip all apply cleanly.

      • mikeym0p

        I little research shows it's because franco raised the thermal throttle. Hopefully this is replaced with the stock kernel Jason linked otherwise I'll have some tinkering to do.

        • Jason Banich

          Seems to have cleared it up for me (I had a slightly different issue, but very similar). I got past verifying and am now on "Patching system files"

          • mikeym0p

            I checked the zip, it didn't include the file I need. I flashed and still failed. Even the stock roms dont modify /system/bin/thermald. Looks like I have to factory wipe :( when you finish updating would you mind uploading the file? Maybe it'll accept it even though it's newer.

          • Jason Banich

            Shit, just saw this.

            I have 2 files I flashed, one from the link I gave you, and one from another thread. Both are supposedly stock kernel. I think the one I didn't link to you has some thermald stuff perhaps:

            One I linked: https://dl.dropbox.com/u/12733318/Temp/Stock%20Kenrel%20Try%202.zip

            Second one:https://dl.dropbox.com/u/12733318/Temp/N4_421_stock_kernel_and_components.zip

          • mikeym0p

            The second one did the trick! I got a thermald file from a friend with a stock n4 and then it flagged my build.prop for some reason so I took it and mms.apk from an odexed stock rom of 4.2.0. Thanks for the help!

          • Guest

            The second one did the trick! I got a thermald file from a friend with a stock n4 and then it flagged my build.prop for some reason so I took it and mms.apk from an odexed stock rom of 4.2.0. Thanks for the help!

    • http://www.facebook.com/people/Taleim-Edwards/570782716 Taleim Edwards

      Yep. Had same issue on my nexus 7. Need to reflash stock kernel, then flash update.

  • Greek_Ice

    Waiting for an AOKP update, but thanks for the heads up AP.

  • http://twitter.com/Jiggy_Hux Jiggy Jesus

    Every time I try to got to the recovery mode menu it never works

    • Guest

      Same here. Recovery just shows the red triangle and the words No Command below that...

      I can't power / volume up to get into adb mode...

      • jm9843

        It's finicky. Just keep pressing PWR+VolUp together repeatedly.

    • http://www.androidpolice.com/ Artem Russakovskii

      Try holding Power and then pressing up a few times. I have a custom recovery, but I think it should work. If not, I'm curious to know the combination.

  • Karl Smith

    You need to OEM Unlock before you can get into the recovery menu, right?

    • jm9843

      Nope. OEM unlock would be necessary if you wanted to flash a custom recovery. The latter supports unsigned packages (like community roms).

    • http://www.androidpolice.com/ Artem Russakovskii

      As jm9843 said, this works with the stock recovery, locked or unlocked, because it's a Google-signed OTA file.

  • http://twitter.com/RaspberryDuff Matt

    Does anybody know if binaries have changed for this release compared to 4.2.1?

  • http://www.androidpolice.com/ Artem Russakovskii

    Trying to fight with my Win7x64 machine not seeing the Nexus 4 at the moment due to a driver issue. Damn you, Google, your USB driver doesn't have Nexus 4 support.

    • Jason Banich

      Make sure drivers are installed using the toolkit: http://goo.im/devs/mskip/toolkit/google_nexus4/Google_Nexus_4_ToolKit_v1.3.0.exe

      And try switching from MTP to camera and back and forth, for some reason that fixed the issue when I had it yesterday

      • http://www.androidpolice.com/ Artem Russakovskii

        I use this toolkit actually, and installed the drivers through it too. But nada. Maybe I need to reboot.

      • http://www.androidpolice.com/ Artem Russakovskii

        Yup, a reboot fixed it. Now I can see the Nexus 4 (again?).

    • JordanMcRae

      working for me. I think I used toolkit drivers I think. I also had to put the .zip file in my /platform-tools folder for it to work. Normal?

      • http://www.androidpolice.com/ Artem Russakovskii

        Was adb just not being seen otherwise? You probably just don't have the platform-tools folder in your PATH.

        • JordanMcRae

          Ya it wasn't being seen. But all good now.

  • JordanMcRae

    Don't think this change was noticed, the up button in messaging is the whole contact name and number now when in a conversation.

    • http://www.androidpolice.com/ Artem Russakovskii

      That's actually a system-wide change. I think Ron will bring this up in his GTKA 4.2.2 article. I saw the exact change in the dev changelog that enabled this.

      • JordanMcRae

        Awesome! Thanks

    • Bob G

      That was already in 4.2.1

      • mikeym0p

        They extended the button past the app icon in 4.2.2.

  • Chronus719

    Keep getting an error on system/app/wallet. Tried restoring to factory, but that didn't seem to help things.

    • Chronus719

      Fixed it. Trying to restore to factory from Settings/Apps won't work, so you'll need to pull the stock Nexus 4 Wallet APK from XDA and move it in to System/App if you want it to pass. This probably applies to anyone who tried to screw around with Wallet on a Rev 11 Nexus 4 since it was initially pulling a secure element failure.

  • Douglas Roberts

    I'll believe it when I see it. And I'll believe it even more if it fixes this problem: http://things-linux.blogspot.com/2013/01/time-frame-of-nexus-4-wifi-bug-issues.html

  • http://www.androidpolice.com/ Artem Russakovskii

    Props to Koush for the latest version of CWM Touch.

    - it has the sideload function
    - it told me I lost root and offered to fix it after the flash
    - it told me the stock recovery will overwrite CWM and offered to fix it as well

    <3

    • cy_n_ic

      Nice! Seems idiot proof. I been using twrp and it also has sideload. The others im not sure

    • Chronus719

      Yeah, I noticed that when I went from 4.2 to 4.2.1 on my Nexus 4. Pretty awesome stuff.

    • Greg Sanders

      Oh my. I guess CWM has improved a lot since I last used it.

      Maybe this means I'll unlock bootloader now, since upgrading to newer official version is painless too!

    • http://profiles.google.com/marcusleejh Marcus Lee

      I brought this up to Wugfresh's attention because the FAQ for his toolkit said we couldn't receive OTAs and preserve root + recovery if we used a custom recovery.

      He didn't seem impressed :-(

    • mikeym0p

      It actually had the recovery interception for a while. It'll even flag CM roms if they include a CWM update. It prompted me to disable the feature.

  • cy_n_ic

    I just want the radio. Wonder if anyone will pack it up by itself. Would save alot of time flashing stock then the update then nand back to custom rom.

  • http://twitter.com/expertontech Tylar Overturf

    Radio and Bootloader zips made by me here: http://forum.xda-developers.com/showthread.php?t=2147194

    The modem.img can be flashed in fastboot if thats your thing.

  • Guest

    Btw, these instructions don't work... "No Command"

    • blumpenstein

      if you have never used adb sideload before, that probably means you have an outdated version of adb.

    • boogie_monster

      if "No Command" appears on the dead Android with Red Exclamation Triangle above it, you have to press Power Button and Volume up at the same time so the menu appears then navigate to Update from ADB

    • http://www.androidpolice.com/ Artem Russakovskii

      The instructions indicate that you need to connect the Nexus 4 to the PC at step 2. So at step 1 it should be unplugged. Then you'll see the Exclamation mark Android and in step 1, it says what to do. If you have it plugged in, you may see the exclamation point that also says No Command. Either way, the solution is the same, as specified in step 1.

  • Greg Sanders

    Getting drivers etc to work the first time is such a frigging pain.

  • Metallinatus

    I just realized that although the Nexus 4 and the Galaxy Nexus are on the same Android version, the GNex's kernel (3.0.31-g9f818de) is much older than the N4 one....

    • deltatux

      That's because the kernel was kept the same with the Nexus S and Galaxy Nexus Android 4.1 release. There's really no need for actual change for the underlying kernel unless there's a big Android architectural change. Google just merged security fixes or driver changes into the current kernel released in Android 4.2.

      For some SoC manufacturers, they're the ones who release the kernels because they must be compiled and optimized specifically with a SoC as there's not yet a stable unified ARM Linux kernel as that's still in active development. The first unified ARM kernel release is pegged for 3.8 and that's just initial support with better support in future Linux kernels.

  • http://www.facebook.com/Dustin.aka.D Dustin Allen

    sweet...so now my phone AND wireless charger can make a sound when I put it on the pad...

  • mikeym0p

    Hey Artem. I noticed that the notification shade will occasionally open slower in 4.2.2. I think they forced the notification shade animation to match the vsync so it'll slide slower instead of lagging. What do you think?

  • http://twitter.com/USSENTERNCC1701 USSENTERNCC1701E

    Well that was blasted brutal, forgot I had an older radio, damn near fully reverted the phone to stock, was just about to give up and write over even data when I remembered the radio.

  • ali

    i keep getting the "error device not found" as if my computer is rejecting the connection with the Nexus 4..any help please?

  • http://twitter.com/sagarmakkar Balvinder Makkar

    has anyone got this update OTA?

  • Gary Wilkinson

    If I do this from a stock rom this won't stop it receiving future updates OTA will it? (I severely doubt it will but just checking)

  • Yousphere

    updating remove root ?

  • Julian Jeong

    I can not turn off camera sound in this 4.2.2

  • ehitburns

    waiting for the SDK and 4.2.2 to download...my nexus says "now send the package you want to apply..." and it scares me so much...

  • http://www.themmteam.com RealtorRyan

    for Mac users... don't forget the "./" in front of adb in the terminal. so it should look like this:

    ./adb sideload de8b8d101614.signed-occam-JDQ39-from-JOP40D.de8b8d10.zip

  • Charlie

    Is there a way to skip verifying system apps? I can not update due to Google Earth. I have restored Earth as a system app from a system dump, tried downloading it from Play and moving it, etc. No matter what I try the update fails every time. Really frustrating!!

  • Vic Starman

    Doesn't work by simply downloading the zip and flashing. I'm rooted and running faux 123 kernel. Stock ROM. Thought i didn't have to connect to the pc (windows 7)?
    When i use clockwork mod recovery the zip flash fails.
    Advice?
    Thx!

  • Han

    Does updating process to 4.2.2 reset all to factory default or only update android kernel ?

  • http://profiles.google.com/andhos Amjad Mohamed

    Guys, I'm getting this error when I run the adb sideload command: error: insufficient permissions for device. Any idea?

  • Eric Coffman

    Dang it. I got to step 2 and plugged in the cable. Ran the adb command. That failed because it said it can't find the device. :(

    I wonder why that is... When I plug it in outside of this setup, I am connected with the message "connected as media device."

  • Eric Coffman

    Removed double post.

  • Moobarak Tailor

    cant update.... keep getting error message.... "assert failed:apply_patch_check("EMMC:/dev/block/platform/msm.sdcc.1/by-name/boot:6311....etc Any help guys. Tried every single method available. was running faux 123 kernel with stock rom. running stock with stock kernel now.

    • Hovan

      Did you fix it? Same problem here

    • https://play.google.com/store/apps/developer?id=iWizard Bikram Agarwal

      I'm getting this today while trying to upgrade to 4.4.3. Had you resolved it?

  • Venkat

    Updated my nexus 4 to 4.2.2 through wifi but after update baseband says unknown and sim is not detected what should I do now

  • Vikash

    I have updated my nexus 4 to android 4.2.2 through OTA. If i reset my device to factory settings will it have 4.2.2 or do i have to update again?

  • Jimish

    Update aborted while Installing Android 4.2.2 JellyBean on Galaxy Nexus.

    The transfer was smooth, but soon the process aborted on its own and asked me to reboot the phone.

    Does anyone has any suggestion to overcome this problem

    • JImish

      I forgot to mention that I am using non rooted Galaxy Nexus (Yakjuxw), 4.2.1, JOP40D

Quantcast