[INFO] Nexus 5 OTA Help-Desk

Search This thread

Wh1t3Rose

Senior Member
Sep 4, 2012
3,421
2,340
253
28
ATL
snthtk.darktech.org
..

194px-Nexus5.svg.png



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.

http://forum.xda-developers.com/google-nexus-5/general/info-rooted-user-learn-to-update-t2927876

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

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!


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

  • From 4.4.4 KTU84P
  • Current Bootloader: HHZ11k
  • Current Radio M8974A-2.0.50.1.16
  • Stock Kernel: 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
  • Current Radio:M8974A-2.0.50.1.13
  • Stock Kernel: 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.



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.

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: http://android.clients.google.com/p...d-ota-LMY47D-from-LRX22C-radio-restricted.zip

5.1 LMY47D from 5.0 LRX21O: http://android.clients.google.com/p...d-ota-LMY47D-from-LRX21O-radio-restricted.zip


Legacy OTA's


5.0.1 LRX22C from 5.0 LRX210: http://goo.gl/eoV0GE

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

5.0 LRX21O-from-4.4.4 r2 KTU84Q: http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84Q.67fdc56d.zip
Thanks @pppp6071

5.0 LRX21O-from-4.4.4 KTU84P: http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip
Thanks @saberdragon18


4.4.4-KTU84P-from-4.4.3-KTU84M:[/COLOR][/B] http://android.clients.google.com/p...ed-hammerhead-KTU84P-from-KTU84M.c08cce45.zip Thanks @sucro

http://forum.xda-developers.com/showpost.php?p=46289250&postcount=1 Thanks @oldblue910



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
You are completely stock. Unlocked/locked bootloader. No root permissions.
Continue to Section A

Scenario #2
You are stock, with root. Custom Recovery without any modifications or deletions.
Continue to Section B

Scenario #3
You are stock, with Xposed Framework installed.
Continue to Section C

Scenario #4
You are stock, with a custom kernel and/or old radio and no other modifications.
Continue to Section D,1

Scenario #5
You are stock with any modifications to /system/ including removed system apk(s) and a custom kernel.
Continue to Section D,2 or See 2nd Post (Special Scenario #1) **Special Scenario #1 is not updated yet**

Scenario #6
You are running a Custom ROM
Continue to Section D,3


Section A: adb sideload

NOTE: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 adb
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.

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

(For Flashing 4.4.4 OTAs and Below ONLY!)

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.

Section C: Uninstalling Xposed Framework

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 to Section A on stock recovery (5.0 and above) and Section B on custom recovery (4.4.4 and below).

Thanks @Hammer_Of_The_Gods & @C3C076

Section D: Let’s get back to stock


1) 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.0

Fastboot commands used in this section would be:

Code:
fastboot flash boot boot.img
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.23.img
fastboot flash recovery recovery.img
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.img


2) Replace 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.img
Note: These must be the exact versions that shipped with the rom.

Fastboot commands used in this section would be:

Code:
fastboot flash boot boot.img
fastboot flash system system.img
3) 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:

Section A if you are running stock recovery.
Section B if 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.

FAQ

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 recovery

Q: I'm seeing a status 7 error when trying to install the OTA
A: 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 permissions

Q: 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.


UPDATED: 6/19/14 - Updated for KTU84P
 
Last edited:

Wh1t3Rose

Senior Member
Sep 4, 2012
3,421
2,340
253
28
ATL
snthtk.darktech.org
..

Special Scenario #1

If you are running the stock ROM, rooted, with a custom kernel, and you want to retain root after the OTA; follow this great detailed walkthrough by @Lettuce!

If it helps you, make sure you thank him on the original post, located here:

http://forum.xda-developers.com/showpost.php?p=48212456&postcount=268
1) downloaded factory image from https://developers.google.com/android/nexus/images#hammerhead
2) extract the tgz, the tar within that, then extract the the zip within that to get the system.img and boot.img files
3) moved these two files into the adb folder (for the fastboot/adb method)
4) download Latest SuperSU from http://download.chainfire.eu/supersu
5) put SuperSU.zip on your phone's internal storage
6) download the 4.4.1 OTA update zip from http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
7) rename it to ota.zip
8) move ota.zip onto your phone's internal storage
9) boot into bootloader
10) open command prompt from your adb folder
11) connect USB cable
12) type 'fastboot devices' to check the connection
13) type 'fastboot flash system system.img'
14) type 'fastboot flash boot boot.img'
15) use volume and power buttons to boot into recovery (TWRP)
16) install ota.zip
17) install latest SuperSu.zip
18) clear dalvik and cache
19) reboot phone
UPDATED: 1/25/15
 
Last edited:

david31262

Senior Member
May 14, 2008
141
12
0
Scenario #2: Will I receive a message ?

Thanks for this thread. It's just what I've been trying to figure out.

So, if I'm Scenario #2, will I received a message on the phone when the OTA is available? Can I let it download then install through TWRP ?

If I'm reading correctly, the custom recovery will not let it install automatically (and maybe I don't want it to since it could wipe out TWRP). On reboot will TWRP prompt me to root the phone (that's how I got to root the first time).
 

El Daddy

Retired Forum Moderator
May 2, 2008
4,262
5,211
263
Roseville, MN
Thanks for this thread. It's just what I've been trying to figure out.

So, if I'm Scenario #2, will I received a message on the phone when the OTA is available? Can I let it download then install through TWRP ?

If I'm reading correctly, the custom recovery will not let it install automatically (and maybe I don't want it to since it could wipe out TWRP). On reboot will TWRP prompt me to root the phone (that's how I got to root the first time).

I believe the new versions of recovery will ask to keep the custom recovery and/or root. We'll see how the custom recoveries handle the OTA on the N5 and I'll update the post accordingly.




If you're rooted, but with stock ROM, do you know for sure OTA updates won't go through? Thanks.

It all depends on how you gained root access. If you used cf-super boot it will not go through because it modifies the kernel.

Sent from my Nexus 5 using Tapatalk
 

El Daddy

Retired Forum Moderator
May 2, 2008
4,262
5,211
263
Roseville, MN
What about cf auto root? From the description it looks like that only adds the root apps and nothing else.







WHen you say cf-super boot you mean installing SuperSU through TWRP right? Thanks.

Cf-auto root and super su should be fine as they don't modify the kernel.

Sent from my Nexus 5 using Tapatalk
 

maxal

Senior Member
Jan 17, 2012
1,282
266
103
Southampton
Hi I would just like to confirm if the Nexus 5 is like my old HTC One in that I would receive OTA updates on a stock rom and stock recovery with a unlocked bootloader.
 

Synyster06Gates

Senior Member
Jan 17, 2011
585
109
0
Leander, Texas
Nexus 5 OTA Help-Desk​

Scenario #3
You are stock, with custom kernel, any modifications or removed system apk(s)
Continue to Section C

Scenario #4
You are running a Custom ROM
Continue to Section C

Section C: Let’s get back to stock

You have two options to do this:

Option #1 Flash the KRT16M stock image. Follow @abaaaabbbb63 guide if you need help.

If you want to keep data intact flash only the boot.img, system.img, and recovery.img (optional)

OR

Option #2 Replace the stock images or .apk(s) you removed or modified.
Note: These must be the exact versions that shipped with the rom.


Just to be sure, flashing only boot.img and system.img will keep my apps and all user data, correct? I can live without the center clock mod and battery % for now.
 

Synyster06Gates

Senior Member
Jan 17, 2011
585
109
0
Leander, Texas
Try pressing the menu button in apn's and reset to default.

Sent from my Nexus 5 using Tapatalk

Tried that. Says it's done, nothing comes up.

I tried searching for network as well but that didn't work either. The wifi works, but no network.

I restored a backup I made last night and it still isn't working. Any ideas?

Tried to do a system wipe then restore again

E: Unable to mount '/cache'
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 286
    ..

    194px-Nexus5.svg.png



    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.

    http://forum.xda-developers.com/google-nexus-5/general/info-rooted-user-learn-to-update-t2927876

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

    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!


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

    • From 4.4.4 KTU84P
    • Current Bootloader: HHZ11k
    • Current Radio M8974A-2.0.50.1.16
    • Stock Kernel: 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
    • Current Radio:M8974A-2.0.50.1.13
    • Stock Kernel: 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.



    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.

    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: http://android.clients.google.com/p...d-ota-LMY47D-from-LRX22C-radio-restricted.zip

    5.1 LMY47D from 5.0 LRX21O: http://android.clients.google.com/p...d-ota-LMY47D-from-LRX21O-radio-restricted.zip


    Legacy OTA's


    5.0.1 LRX22C from 5.0 LRX210: http://goo.gl/eoV0GE

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

    5.0 LRX21O-from-4.4.4 r2 KTU84Q: http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84Q.67fdc56d.zip
    Thanks @pppp6071

    5.0 LRX21O-from-4.4.4 KTU84P: http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip
    Thanks @saberdragon18


    4.4.4-KTU84P-from-4.4.3-KTU84M:[/COLOR][/B] http://android.clients.google.com/p...ed-hammerhead-KTU84P-from-KTU84M.c08cce45.zip Thanks @sucro

    http://forum.xda-developers.com/showpost.php?p=46289250&postcount=1 Thanks @oldblue910



    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
    You are completely stock. Unlocked/locked bootloader. No root permissions.
    Continue to Section A

    Scenario #2
    You are stock, with root. Custom Recovery without any modifications or deletions.
    Continue to Section B

    Scenario #3
    You are stock, with Xposed Framework installed.
    Continue to Section C

    Scenario #4
    You are stock, with a custom kernel and/or old radio and no other modifications.
    Continue to Section D,1

    Scenario #5
    You are stock with any modifications to /system/ including removed system apk(s) and a custom kernel.
    Continue to Section D,2 or See 2nd Post (Special Scenario #1) **Special Scenario #1 is not updated yet**

    Scenario #6
    You are running a Custom ROM
    Continue to Section D,3


    Section A: adb sideload

    NOTE: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 adb
    5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
    6) When completed, select reboot.

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

    (For Flashing 4.4.4 OTAs and Below ONLY!)

    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.

    Section C: Uninstalling Xposed Framework

    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 to Section A on stock recovery (5.0 and above) and Section B on custom recovery (4.4.4 and below).

    Thanks @Hammer_Of_The_Gods & @C3C076

    Section D: Let’s get back to stock


    1) 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.0

    Fastboot commands used in this section would be:

    Code:
    fastboot flash boot boot.img
    fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.23.img
    fastboot flash recovery recovery.img
    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.img


    2) Replace 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.img
    Note: These must be the exact versions that shipped with the rom.

    Fastboot commands used in this section would be:

    Code:
    fastboot flash boot boot.img
    fastboot flash system system.img
    3) 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:

    Section A if you are running stock recovery.
    Section B if 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.

    FAQ

    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 recovery

    Q: I'm seeing a status 7 error when trying to install the OTA
    A: 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 permissions

    Q: 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.


    UPDATED: 6/19/14 - Updated for KTU84P
    46
    ..

    Special Scenario #1

    If you are running the stock ROM, rooted, with a custom kernel, and you want to retain root after the OTA; follow this great detailed walkthrough by @Lettuce!

    If it helps you, make sure you thank him on the original post, located here:

    http://forum.xda-developers.com/showpost.php?p=48212456&postcount=268
    1) downloaded factory image from https://developers.google.com/android/nexus/images#hammerhead
    2) extract the tgz, the tar within that, then extract the the zip within that to get the system.img and boot.img files
    3) moved these two files into the adb folder (for the fastboot/adb method)
    4) download Latest SuperSU from http://download.chainfire.eu/supersu
    5) put SuperSU.zip on your phone's internal storage
    6) download the 4.4.1 OTA update zip from http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
    7) rename it to ota.zip
    8) move ota.zip onto your phone's internal storage
    9) boot into bootloader
    10) open command prompt from your adb folder
    11) connect USB cable
    12) type 'fastboot devices' to check the connection
    13) type 'fastboot flash system system.img'
    14) type 'fastboot flash boot boot.img'
    15) use volume and power buttons to boot into recovery (TWRP)
    16) install ota.zip
    17) install latest SuperSu.zip
    18) clear dalvik and cache
    19) reboot phone
    UPDATED: 1/25/15
    30
    Ok guys so finally took the plunge and decided to update.

    For those confused (like me) I thought I'd type out step by step instructions that I did.

    Pre-conditions: UK Nexus 5 (D281), rooted, TWRP 2.6.3.4, stock ROM, franco kernel r16, no mods, nothing frozen or removed

    1) downloaded factory image from https://developers.google.com/android/nexus/images#hammerhead
    2) extracted the tgz, then extracted the tar, then extracted the zip to get the system.img and boot.img files
    3) moved these two files into my adb folder (for the fastboot/adb method)
    4) downloaded SuperSU-v1.80.zip from http://download.chainfire.eu/supersu
    5) put SuperSU-v1.80.zip on my internal storage
    6) downloaded the 4.4.1 OTA update zip from http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
    7) renamed it to ota.zip (biggest filename in the world before!)
    8) moved ota.zip onto my internal storage
    9) rebooted phone into bootloader
    10) opened command prompt from within your adb folder
    11) connected USB cable
    12) typed 'fastboot devices' to check the connection
    13) typed 'fastboot flash system system.img'
    14) typed 'fastboot flash boot boot.img'
    15) used the volume and power buttons to boot into recovery (TWRP)
    16) installed ota.zip
    17) installed SuperSU-v1.80.zip
    18) cleared dalvik and cache
    19) rebooted phone

    It then went through that process of first boot and optimising 120-or-so apps but I lost no apps or data, everything was right where I left it. Didn't lose root access. To be honest didn't encounter any problems.

    E02tvKm.png


    There seems to be some negative reports about the updated baseband giving poor signal and slow speeds so I'll leave that for now.

    Thanks everyone for all your help and support.
    25
    Heres the file name

    Screenshot_2014_06_03_22_54_26.png
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone