





OTA Help-Desk



* 5.1.1 LMY48B Available*



* 5.1 LMY47I Available*

*5.1 LMY47D Available*









This thread is only for OTA help and nothing else!



Flash stock recovery before proceeding





.

NOTE: If You are a rooted non-stock user I suggest you look at @rootSU's thread before proceeding as his method for rooted users is far less prone to cause issues .

First, let's talk about what an OTA is:



In order for the OTA to apply successfully without intervention; you must be completely stock

From 4.4.4 KTU84P

Current Bootloader: HHZ11k

HHZ11k Current Radio M8974A-2.0.50.1.16

M8974A-2.0.50.1.16 Stock Kernel : 3.4.0-gd59db4e

: 3.4.0-gd59db4e All /system apps present

No modifications to existing /system files of ANY kind.

From 4.4.3 KTU84M

Current Bootloader: HHZ11k

HHZ11k Current Radio :M8974A-2.0.50.1.13

:M8974A-2.0.50.1.13 Stock Kernel : 3.4.0-gd59db4e

: 3.4.0-gd59db4e All /system apps present

No modifications to existing /system files of ANY kind.

Note: Literally any modification will break the OTA. Xposed, DPI, build.prop, volume mod, etc. ANYTHING!

Seriously, I'm not joking guys.

Current OTA's

5.1.1 LMY48B from LMY47D:

https://dl.dropboxusercontent.com/u/33560221/OTA_update_from_lmy47d_to_lmy48b.zip

5.1 LMY47I from 5.0.1 LRX22C: http://

android.clients.google.com/packages/ota/google_hammerhead/90bd789f499ea5ad33510c568ec920aae7214d34.signed-hammerhead-ota-LMY47I-from-LRX22C-radio-restricted.zip

5.1 LMY47D from 5.0.1 LRX22C

5.1 LMY47D from 5.0 LRX21O

Legacy OTA's

http://android.clients.google.com/packages/ota/google_hammerhead/6dadaf477bab65f42f5681b03bd535f431594b95.signed-hammerhead-LRX22C-from-KTU84P.6dadaf47.zip



These are the most common scenarios. If you aren't sure where you fit, feel free to ask.

NOTE: Starting with Android 5.0 (LRX21O) you MUST sideload the OTA in a STOCK RECOVERY. No exceptions.

Scenario #1

Scenario #2

Scenario #3

Scenario #4

Scenario #5

**Special Scenario #1 is not updated yet**

Scenario #6

Section A: adb sideload

Section B: Flashing in a Custom Recovery (TWRP- CWM)

(For Flashing 4.4.4 OTAs and Below ONLY!)

Section C: Uninstalling Xposed Framework

Section D: Let’s get back to stock

1)

Code: fastboot flash boot boot.img fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.23.img fastboot flash recovery recovery.img

2)

Code: fastboot flash boot boot.img fastboot flash system system.img

3)

FAQ

UPDATED: 6/19/14 - Updated for KTU84P

..An OTA (Over the Air) update is the method of updating your phone's software. When the OTA is downloaded to your phone it will prompt you to reboot and install. It is not a complete image, but a series of patches to the OS. Patches in the OTA can include: bootloader, radio, system, recovery and kernel. While it's installing, the script checks the files it is patching to make sure the original files are correct. If everything is correct, the update will finish successfully. If it's not, the process will stop. That's why it is critical to make sure everything is in its "out of the box" state. Don't worry though. It is easy to get your phone back to a state where you will have it up and running, with the latest software.We are also able to manually flash this file. When the URL of the OTA is discovered, you can download it and use adb or a custom recovery to apply it.Now that you have read the important info above, Let's update your Nexus 5!If you meet the above criteria, the OTA will complete successfully.If you don’t meet the criteria or don’t want to wait for the OTA to hit your device then see below.Thanks @ pppp6071 Thanks @ saberdragon18 4.4.4-KTU84P-from-4.4.3-KTU84M:[/COLOR][/B] http://android.clients.google.com/pa...M.c08cce45.zip Thanks @ sucro http://forum.xda-developers.com/show...50&postcount=1 Thanks @ oldblue910 You are completely stock. Unlocked/locked bootloader. No root permissions.Continue to SectionYou are stock, with root. Custom Recovery without any modifications or deletions.Continue to SectionYou are stock, with Xposed Framework installed.Continue to SectionYou are stock, with a custom kernel and/or old radio and no other modifications.Continue to SectionYou are stock with any modifications to /system/ including removed system apk(s) and a custom kernel.Continue to Sectionor See 2nd Post (Special Scenario #1)You are running a Custom ROMContinue to SectionNOTE:Make sure you have the latest version of adb. It seems people are having issues with older versions. It's attached at the bottom of this. Also Starting with Android 5.0 you must sideload the OTA through a stock recovery. Custom recoveries for now will error out.1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'4) When in recovery, you’ll see an android laying down. Press and hold POWER, and then press volume up and release. The menu will appear. Select “apply update from adb5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.6) When completed, select reboot.1) Download the OTA.zip and copy to your phone.2) Boot into recovery.3) Flash the OTA just like you would a ROM.4) Reboot.Use the Xposed Framework Installer to remove the framework before applying the OTA.Go into Xposed Framework, Framework-> Uninstall (it will restore the original file "app_process") then reboot.NOTE: If you just uninstall Xposed Framework (the app itself), even after a reboot the "app_process" file (in /system/bin) is still the modified one by Xposed Framework, the original file is not restored.Xposed Installer and info can be found here. Once Xposed is uninstalled; jump back up toon stock recovery (5.0 and above) andon custom recovery (4.4.4 and below).Thanks @ Hammer_Of_The_Gods & @ C3C076 Flash the stock boot.img and/or radio.img (whatever is applicable) from the factory image using fastboot. Also flash recovery.img if updating to 5.0Fastboot commands used in this section would be:NOTE: Some custom kernels will modify files in /system/ If this is the case you will see a status 7 error and the file modified. The easiest way to fix this is to flash the system.imgReplace the stock kernel or .apk(s) you removed or modified.If you don't have a backup of removed or modified apk(s) flash the system.imgNote: These must be the exact versions that shipped with the rom.Fastboot commands used in this section would be:Flash the KOT49H stock image. Follow abaaaabbbb63's guide if you need help.--------------------------------------------------------------------------------------------------------------------After completing the steps needed to return to “stock” make sure you meet all the criteria at the top of the page then revert to:Sectionif you are running stock recovery.Sectionif you are running a custom recovery (for 4.4.4 OTAs and below only).Feel free to ask any questions you may have. I’ll do my best to answer them as quickly as possible. Perhaps others may answer them as well. Please read to see if your question has been answered before asking.Q: When in Recovery/Bootloader the phone isn't listed in Windows Device Manager.A: Uninstall all current N5 drivers and install the Universal Naked driver. Turn on USB Debugging in Developer Settings and boot to recoveryQ: I'm seeing a status 7 error when trying to install the OTAA: Look at the error closely. It will describe on the file it is failing at. Post the file path so we can help resolve the issue.Q: The ota applied successfully but I lost my custom recovery and I want to re-root. How do I get root back?A: Flash the custom recovery of your choice in fastboot and use it to regain root permissionsQ: I've tried everything, but I'm still getting status 7 errors.A: Unfortunately you may have to start from scratch. Follow Section C1.Q: I flashed a .zip file that modified (insert mod here.) Will I the OTA install successfully?A: No, any modification at all will cause the OTA to fail.Q: Why do I get a "cannot read update.zip" error when trying to sideload?A: If you named the file update.zip, the actual name would be update.zip.zip. Windows auto names extensions by default. That could be your problem. If not try another usb cable or a different usb port. If that still doesn't work, make sure you type exactly what you renamed the file. You may have made a typo. It is also case-sensitive.