More Reading

Post navigation

44 Comments

  • Terrific! It worked, but with a couple of major caveats. I was getting the device not found error during the sideload attempt (but not before that point), due to Windows 8 locking down which drivers were being installed. I found the following two instruction sets from other web pages (primarily http://forum.xda-developers.com/showthread.php?t=1392310) critical to making this work. If you, too, have Windows 8 x64 (Pro, for me), you’ll probably need to take these steps, too:

    —

    Q. I have Windows 8 and cannot install the drivers

    How to Disable Driver Signature Enforcement in Windows 8:

    From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
    Click ‘More PC Settings’.
    Click ‘General’.
    Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
    Wait a bit.
    Click ‘Troubleshoot’.
    Click ‘Advanced Options’
    Click ‘Windows Startup Settings’
    Click Restart.

    When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. The one that worked for me was PDANet for Android (Win8 compatible): http://pdanet.co/bin/PdaNetA4013.exe

    Overwrite the old files and accept the security warnings. It may give you an error and automatically uninstall PDANet, but the drivers will stay on your system.

    Reboot again once the driver is installed and all will be well and you can proceed with the instructions fully as instructed in the main post above.

    Now FINALLY enjoy 4.2.2 on your Verizon Galaxy Nexus!!!

  • hmmm, my adb is working, but my androidSDK doesn’t seem to have the adb sideload command. I just installed the new one too. I search the SDK site for adb commands and sideload is not listed anywhere. Was it removed? Any ideas?

  • Ok. I’m getting frustrated. Everything works fine UP TO when I type adb sideload…..it comes back saying error: device not found. Sure enough, when I type adb devices, nothing is listed. however, when I type adb devices at the start of this process, it’s found!!! Any thoughts?

  • On my GSM GNex I get to step 17 and in the device manager I see “Other devices” come back with “Galaxy Nexus” with a yellow ! over it. I’m on Windows 7 64-bit.

    Ideas? I really want to get this working! Thanks.

  • I rooted my gnex then reflashed stock recovery/relocked bootloader and then used this to apply the update 😀

  • Any update on the device ID not registering through the USB driver, requiring a manual edit of the “winusb.inf” file? I have tried unsuccessfully to add my hardware ID to the “winusb.inf” file and need some guidance.

    • I had the same problem after searching for hours i finally got this:

      add the following to android_winusb :

      [Google.NTx86]

      ; !– snip other devices… –!

      ; Google Nexus 7
      ; !– snip existing device IDs –!
      ; This is the HardwareID shown in Device Manager for the “Nexus”
      ; device when in Recovery mode
      %CompositeAdbInterface% = USB_Install, USBVID_18D1&PID_D001

      Then uninstall the “Not identified” Nexus 7 through device manager then reinstall driver with the modified android_winusb file.

      Hope it helps:)

  • Doesn’t work for me on Win 8 64 bit. adb appears to be working up until when i try to sideload the update. nothing happens and i just get a bunch of messages in command prompt. Any ideas?

  • Ok i just followed a guide on installing the sdk and getting adb running…i checked and my adb was running…i turned on usb debugging and connected my nexus 7 but after typing in “adb devices”, my serial number and the word “device” does not show up….my computer recognizes my devices as Nexus 7, anybody help me out here?

  • “error: device not found”. Yet I just booted into recovery mode without any problems via the usb cable. Any ideas?

    • Ditto. i think it’s a driver issue though. the first try it failed to install a driver but i didn’t notice it until after i ran “adb sideload…” which gave me same error. So i went through it again. It didn’t try to install any drivers the next go round. but the same error.

      • OK: got it to work. it was a driver issue of some kind. i ended up downloading and installing the Nexus 7 Toolkit from XDA. from there chose option to install drivers. rebooted pc and 7. tried Kellex steps above, viola, 4.2.2

    • no need to download the toolkit just add the following to android_winusb :

      [Google.NTx86]

      ; !– snip other devices… –!

      ; Google Nexus 7
      ; !– snip existing device IDs –!
      ; This is the HardwareID shown in Device Manager for the “Nexus”
      ; device when in Recovery mode
      %CompositeAdbInterface% = USB_Install, USBVID_18D1&PID_D001

      Then uninstall the “Not identified” Nexus 7 through device manager then reinstall driver with the modified android_winusb file.

      Hope it helps:)

    • I skipped a generation of Android, so for me this stopped working after the Droid Incredible, IE this didn’t work when I came back to Android with the Galaxy Nexus.

      At least now you don’t need an unlocked bootloader to apply updates like you did with the GN.

      Just flashed to my N4, locked/stock/no-root whatever, worked great except one minor detail:

      Getting into stock recovery (android lying down, red exclamation point), it’s press power button first, then volume up, then release.

      This might be obvious to some, but having never done this, I had to Google for an answer when it didn’t work.

  • Does this work only with the stock ROMS or does it work with any of the custom ones as well?

    Does it work for downgrades if you have the files?

    • Maybe, but why would you want to?

      Umm… do people make those files? An update file does not simply tell it “activate version x”, but rather, it deletes and replaces new files. If you happen to have a file that deletes all of the new files and replaces them with old ones, then sure, this will work. But I don’t believe you have that kind of file.

      • I thought you could get stock images, not just updates.

        The update adding multiple users I would’ve backed down until stuff became more stable with it.

  • Anyone try this using a Windows 7 machine? Willing to give this a shot but see it was done on Windows 8.

  • “but try to keep in mind that some like Nexus phones and tablets because of constant updates and a 100% stock version of Android. ” And you keep in mind that these people you speak of have no clue how enter recovery much less use adb sideload.

    • Not true. I used to root and ROM and overclock back in the Droid 1 & 2 days. I did it mostly to make up for the deficiencies of Android, or to make my Droid 1 fast enough to play FF7 smoothly. With the Droid 2 I rooted and ran ROM’s to remove the Verizon Bloat. With my Verizon Galaxy Nexus I ran ROM’s because VZW sucks at pushing updates in a timely manner.

      Not an issue with my Nexus 4 & 7. All I really want is a stock ROM that is updated quickly. That’s why I ran “Shiny” on my GNex.

      TL;DR

      You’re wrong, some people just want stock and fast updates. I just pushed the 4.2.2 update to my stock/unrooted N7 on my Linux Mint box.

    • Custom ROMs are a pain in the ass. Something is always broken, and something else always breaks with a new update. For the people who don’t want to ride the endless merry-go-round of broken features, but want root, stock works fantastic.

      I use 100% stock and know my way around adb very well from my days of flashing ROMs and kernels.

  • But.. but.. isn’t the point of buying a Nexus so you don’t have to do things like this 🙂

Comments are closed.

Random reads.

back to top