[INFO] Nexus 5 OTA Help-Desk

Android The Greek

Senior Member
Mar 7, 2012
1,682
444
0
New Castle
I'm not alarmed at all that there are no OTA reports here. This thread was very well "hidden" in the second page and now it's sticky. I don't think too many came here to boast they got the OTA. There were some reports in the other threads and the URLs. That seems good enough.

When does it reach the devices? Well who knows why we don't see too many reporting, maybe N5 is not that "popular" among geeks that check news about new Androids every half an hour.

On top of that most were coming here with the quick fix (sideloading), probably many like me just downloaded it and went with flashing, didn't wait a few hours for the actual thing to come directly to the device.
If a person has experience with SDK or adb they can do it. If you don't you must learn through the painful process of reading and experiment like we all have done in the gingerbread days

Sent from my Nexus 5 using XDA Premium 4 mobile app
 

kraven001

Senior Member
Jan 2, 2011
471
152
0
Craiova
If a person has experience with SDK or adb they can do it. If you don't you must learn through the painful process of reading and experiment like we all have done in the gingerbread days

Sent from my Nexus 5 using XDA Premium 4 mobile app
Yeah , well, I remember actually reading a handful of posts reporting getting this OTA directly to their device. What is interesting that there is a lot discussion around keeping root, cleaning up to apply this, etc. which definitely is "outshadowing" any happy campers that would just say: "Suck on this, I was stock and it worked"!

As with the Defects thread, the hype and discussion is around the "issues" rather than the positives.

As far as sideloading, besides having some issues with drivers the process should be pretty straight forward for your average computer saavy person.
 

j831

Senior Member
Dec 3, 2013
67
23
0
I'm in the same boat as you, same set up, etc. How did you get on? Did you run into any problems?

Did you carry out step 1 in TWRP or use fastboot method?
Sorry if you already figured this out. Late reply.
I followed the steps I listed and everything went smoothly. I DID NOT carry out step 1 in TWRP. I used adb on my pc.
 

dmarg

New member
Nov 6, 2013
2
0
0
Just a heads up for anyone flashing from TWRP, wiping the cache takes an unusually long time and ify ou halt it during the wipe you'll corrupt your cache and need to reflash the cache.img from the stock image.

Also, the latest SuperSU 1.80 zip works in giving root on 4.4.1, but if you download it through ES downloader, it corrupts the file somehow. Took 3 tries before I realized that it was the problem!

Otherwise, 4.4.1 is a nice improvement, liking the camera updates a lot
Are you only supposed to wipe the cache? Leave everything else and this will result in not losing any of your apps or data?
 

QWIKSTRIKE

Senior Member
Aug 9, 2011
291
42
0
you can also try just typing adb sideload and then literally dragging the zip file into the command window
it doesnt need to be in the same directory..
This was a good idea but when I did this it still didn't work. It seems when the phone booted into recovery mode the win 8 OS did not recognize the phone and I had an exclamation mark in my drivers in device manager. After trying to load the latest win_usb.drivers it still did not work so I right clicked on the exclamation point and hit browse and installed the ADB3122013 drivers and bam went back to the comand prompt typed adb sideload and then draged the original downloaded file and hit enter....booom! I am now cooking with 4.41. For those that got errors after booting into recovery I suggest you check your device manager to see if the device registers.....mine registered when I did an adb devices, and displayed the serial number, However; when I booted into recovery everything seemed fine until it asked for the file that I wanted to upload....

After finding the exlamation point I plaed with usb driver and decided to load the ADB312 drivers and got rewarded with the update! I did this by going to the let me choose the driver on the machine rather than the browse driver feature. I already had the Latest Android SDK from the MSL install that I did. So to clarify you must choose let me install drivers on the machine rather than browse for drivers.
 
Last edited:

hpsauce37

Senior Member
Sep 10, 2010
970
62
28
im stock and trying to use the side-load method.

when i try to push the update and type the command in the cmd window it says 'cannot read 'update.zip'

any ideas what im doing wrong?
 

Lettuce!

Senior Member
Jan 30, 2013
50
39
0
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.



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.
 
Last edited:

efrant

Senior Moderator / Developers Relations
Staff member
Feb 12, 2009
11,467
10,968
253
Montreal
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) 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 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) 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) user volume and power buttons to boot into recovery (TWRP)
16) install ota.zip
17) install SuperSU-v1.80.zip
18) clear dalvik and cache
19) reboot 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.
Well done. That's exactly how to do it!
 
  • Like
Reactions: Lettuce!

El Daddy

Retired Forum Moderator
May 2, 2008
4,262
5,211
0
Roseville, MN
im stock and trying to use the side-load method.

when i try to push the update and type the command in the cmd window it says 'cannot read 'update.zip'

any ideas what im doing wrong?
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.
 
  • Like
Reactions: hpsauce37

El Daddy

Retired Forum Moderator
May 2, 2008
4,262
5,211
0
Roseville, MN
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) 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 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) 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) user volume and power buttons to boot into recovery (TWRP)
16) install ota.zip
17) install SuperSU-v1.80.zip
18) clear dalvik and cache
19) reboot phone

Nice! Would you mind if I linked to your post in the OP? I'm sure it will help others in the same situation.
 
  • Like
Reactions: Lettuce!

jumpman1229

Senior Member
Jun 24, 2011
627
36
0
So I am running stock with TWRP installed and also rooted. The only mods I have made are the volume boost found in the link below and vibration within Trickster Mod. I tried flashing KOT49E, but it failed. Any help would be greatly appreciated!

http://forum.xda-developers.com/showthread.php?t=2532788&highlight=speaker+volume+boost

EDIT: I froze Google Earth and unfroze it from within TiBu, so I know I have all the stock apps since that was the only one I froze.

Sent from my Nexus 5 using XDA Premium 4 mobile app
Anyone? I don't know what to do. Don't really want to set all my stuff up again =\

Sent from my Nexus 5 using XDA Premium 4 mobile app
 

cd69

Senior Member
Sep 19, 2012
368
118
0
I have stock + CWM + root + Xposed. I read the following steps in one of the pages in this thread. But I don't seem to find it now. Can you more experienced members tell me if the following steps work.

1. I uninstalled Xposed from within the app, rebooted.
2. copied the OTA ZIP to my phone via USB storage mode
3. rebooted into CWM
4. flashed the OTA ZIP
5. Rebooted in CWM, It asked if I wanted to restore root, I said yes.
6. done!

Thanks for your help guys.


Sent from my Nexus 5 using XDA Premium 4 mobile app
 

Hurizen

Senior Member
May 11, 2009
70
6
0
38
Moniga del Garda (Brescia)
As a note for those even more confused (like me), here's the step needed to update to 4.4.1 and keep root, for phones with this configuration:
Stock ROM, Stock Kernel, Rooted.

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
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
Note: 04) SuperSU file name is (now) UPDATE-SuperSU-v1.80.zip
Note: 18) Dalvik and cache get wiped with OTA so, this is optional, imho.

Thank you
 

unknown1205

Senior Member
Sep 16, 2008
505
89
0
San Francisco
if you guys are stock rooted, and flashing the OTA failed because you made some modifications to the system files. flash this stock, rooted 4.4.1 rom. i did it for my friend's phone and it worked perfectly. didnt have to lose anything on the phone. just wipe cache and flash away.
http://forum.xda-developers.com/showthread.php?t=2557523

if you want the updated radio. (optional) you can flash this. i didnt do this for my friend but you will still reap the benefits of 4.4.1 without it.
http://forum.xda-developers.com/showthread.php?t=2558080