yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] stevexyz0:
Thanks. Should have mentioned up front, that's the first thing I did. I checked and ran the updates suggested. However, just got it to work! As another poster suggested, I waited until I got to the "adb sideload <filename>" screen, unplugged/replugged the USB cable, and now it's working!

$ ./adb devices
List of devices attached
ZX1G225VL8	device

$ ./adb version
Android Debug Bridge version 1.0.32
$ ./adb reboot bootloader
$ ./adb devices
List of devices attached

Note it does not appear to recognize the device once I've booted into the bootloader or recovery screen, even though it did before.

$ ./adb sideload ff9e83169f322ffc83b2e94357dd501fd789cab3.signed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
loading: 'ff9e83169f322ffc83b2e94357dd501fd789cab3.signed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip'
error: device not found

Still gives the error trying to sideload but then I unplugged/replugged the cable

$ ./adb sideload ff9e83169f322ffc83b2e94357dd501fd789cab3.signed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
serving: 'ff9e83169f322ffc83b2e94357dd501fd789cab3.signed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip' (~50%)

And now the update is running!
[Nexus 6  General] LordGeek:
Rather strange issue here .. I have read this thread over and over, checked WugFresh FAQ's .. for some strange reason, my phone will NOT install the OTA period !!

Detection of the device is no problem at all, all commands run successfully with WugFresh NRT v2.0.4 .. but once device is ready for the OTA, the device continuously shows (no matter how or how many times I do this):

Now send the package you want to apply

to the device with "adb sideload <filename>"...

Finding update package...

Opening update package...

Verifying update package...

Installing update...

Verifying current system...

/dev/block/platform/msm_sdcc.l/by-name/system has been remounted R/W; reflash device to reenable OTA updates

E:Error in /sideload/package.zip

(Status 7)

Installation aborted

Now, I have the AT&T variant of the Nexus 6 .. the device is network unlocked only .. everything else on here is pure stock 5.0.1.

I have even tried doing the reflash of the stock loader before trying the OTA, and still receive the same error.

Any hints as to what might be happening here ?
[Nexus 6  General] david279:
reflash the system.img
[Nexus 6  General] vvveith:
Question?

Is your bootloader unlocked?
[Nexus 6  General] LordGeek:
No.. not unlocked. However, I did also try the way asking if I was unlocked to reinstall the NRT's stock image. That didn't work either !

---------- Post added at 09:58 AM ---------- Previous post was at 09:43 AM ----------

If I reflash the system.img .. isn't that going to basically wipe my phone ?
[Nexus 6  General] david279:
No it wont
[Nexus 6  General] mxair2001:
So I flashed the OTA last night successfully and thought everything was good, so I went to bed. Get up this morning and start messing around with it and notice that it says my device is 32GB now. I have a 64GB CW, and it shows 64GB in the bootloader, but since this 5.1 OTA it shows available storage at 23GB (which I first noticed when I had it plugged into the computer).

Anyone else experience this? And how do I fix it?
[Nexus 6  General] Mega Montana:
found this

http://xdaforums.com/showpost.php?p=58201783&postcount=106
[Nexus 6  General] edved:
Using Wugfresh to sideload the ota.zip file and while unplugging and plugging it in again leads me to the point where it tells me it's...

verify update package.

installing update.

error in sideload/package.zip (status) 7!

This is the furthest I've got.
[Nexus 6  General] juggies:
I get the same thing except manually no toolkit.
[Nexus 6  General] javon27:
Same thing here. Even after flashing 5.01 system.img...

Anybody have a clue what we need to do?
[Nexus 6  General] nathan57971:
side loaded the OTA using wug fresh without any issues, complete stock, never rooted and locked bootloader
[Nexus 6  General] edved:
I've also reverted to 5.01 system.img.

This has been a long day.
[Nexus 6  General] juggies:
Okay so, I've got it working.

Essentially I just did a flash-all.sh from the 5.0.1 system image, then booted up for the first time. Didn't complete any initial setup and rebooted into the bootloader and then sideloaded no problem.
[Nexus 6  General] javon27:
I really hate to do that... But I guess, since I'm addicted to having the latest Android...
[Nexus 6  General] rome425:
I've reflashed system.img from 5.01

and reverted back to original kernel and it worked.
[Nexus 6  General] mxair2001:
Awesome! How did I miss that? I was just in that thread last night as I was having issues with the OTA at first. Anyways, thanks for the link!
[Nexus 6  General] edved:
Uh? You did what? This?

5.0 (LRX21O) to 5.1?
[Nexus 6  General] vvveith:
Same here.

Same here, but alas, No T Mobile WiFi calling. In fact, I don't see any appearance changes at all. Don't really see anything new in settings either. Going to take phone out for test drive while I take my dog for exercise/ Will report back. So far though, I'm not impressed.
[Nexus 6  General] rome425:
LRX22C to LMY47D
[Nexus 6  General] edved:
Gotcha. Thanks.

---------- Post added at 03:21 PM ---------- Previous post was at 03:10 PM ----------

I keep getting this!!!

serving: 'E:\ff9e83169f322ffc83b2e94357dd501fd789cab3.signed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip' (~47%)

Total xfer: 1.01x

Status 7 error! :(
[Nexus 6  General] LordGeek:
I'm continuously receiving that same error .. no matter what people are suggesting up here for a fix to get the OTA installed.

Dumb question, since no one has seems to have mention this at all ..

How many people in here have successfully installed the OTA on a AT&T Branded Nexus 6 ?
[Nexus 6  General] gee2012:
My fastboot and adb drivers are installed correctly and still i get i get `error: device not found` when trying to flash the OTA with adb sideload ugh. Anyone having ideas?

All Stock and unlocked bootloader.
[Nexus 6  General] AmesCell:
I was getting that. Unplugged USB and plugged back in. Worked.
[Nexus 6  General] jeffrey81:
Can i update with nexus tool kit and root it ??
[Nexus 6  General] biggiestuff:
look in device manager if you're on PC. see if it has an exclamation mark. If it does hit update driver, browse on your pc, let me select from a list, choose android adb device, ignore the warning and accept. It should see your device then.
[Nexus 6  General] sabbotage:
Anyone that's having issues, just throw the update zip on your SD card and flash it through stock recovery. That's much easier than ADB sideload if you're having issues doing it that way.
[Nexus 6  General] edved:
I've tried that way as well and my N6 didn't cooperate!
[Nexus 6  General] gee2012:
Thanks mate, that did the trick :good:
[Nexus 6  General] javon27:
No luck installing OTA

I did everything. I even wiped and flashed 5.01 again. I still got the error that it aborted (status 7). If I could, I would've flashed the update manually, but I don't know how...

So should I just wait on a update.zip?
[Nexus 6  General] edved:
Feel your pain brudder!
[Nexus 6  General] javon27:
Factory image is up!!!

https://developers.google.com/android/nexus/images
[Nexus 6  General] edved:
good job! Manually done?
[Nexus 6  General] Herohtar:
I have a couple of questions... my Nexus 6 (direct from Motorola, running on Verizon) was stock LRX22C, but had been rooted with CF-Root, and I ended up using the Nexus Root Toolkit with the "no wipe" option to get back into a state that could use the OTA. I was then able to successfully sideload the LMY47D OTA. However, I noticed that ambient display wasn't behaving the same after the update; in 5.0.1 it would turn on the display any time the phone was picked up or even slightly moved as well as pulse on/off with notifications, but now it only turns the display on once when a notification arrives and picking up/moving the phone doesn't activate the display at all. Is this a change with 5.1 that others are experiencing, or did my upgrade method break something?

Also, I'm still somewhat new to rooting the Nexus 6; can 5.1 still be rooted with the same tools I used before, or do they need to be updated somehow?

Thanks!
[Nexus 6  General] rubber guard:
Thanks [MENTION=296513]edved[/MENTION].

What's the normal turnaround time for someone to release a stock rooted ROM for those of us with custom recovery/root.

Tis
[Nexus 6  General] hsomnus:
I side loaded the update and then unlocked the boot loader and rooted...all using Wugs tool kit. You just have to change your build to SHAMU-SHAMU:Android*.*.*-Any Build after you flash the ota package but before unlocking. Everything is running fine.
[Nexus 6  General] javon27:
It's very well possible that the update may have tweaked how ambient display works.

Also, as far as I know, the Nexus Root Toolkit should still work in rooting 5.1. However, it may benefit you in learning how to do it manually. Since your device is already unlocked, all you need to do is reboot to your bootloader and fastboot flash a custom recovery, like TWRP. Then copy SuperSU update zip to your phone and flash from recovery.
[Nexus 6  General] stevexyz0:
Mine's the same -- purchased from Motorola, running on VZW. Just upgraded to 5.1 this morning, stock everything, not rooted. Ambient display is working the same as it did before -- picking up the phone does activate it. Sometimes you have to shake it a bit though.
[Nexus 6  General] rdbutler624:
Motorola purchased Nexus 6

This may be kind of a dumb question but here goes....

I purchased my Nexus 6 from Moto and have loved it and not bothered unlocking, rooting, romming, etc.; haven't felt the need to. I just popped my Verizon sim in and have been loving it since day 1. Question is how will I get the OTA? Will VZW push it out to my phone? Will Motorola? Will Google? Or, am I forced to do it on my own?
[Nexus 6  General] :
Google pushes updates to Nexus devices.
[Nexus 6  General] rdbutler624:
Thanks. I knew I would get a quick answer on here.
[Nexus 6  General] :
No problem, you're welcome. :) Although, if it seems you haven't received the OTA after a couple weeks, try pulling your Sim out and rebooting. Let it boot without Sim and sit for a bit and the OTA may appear.
[Nexus 6  General] jeffrey81:
Can i flash the zip file on twrp?
[Nexus 6  General] Tankslappa:
System mounted R/W

I'm also getting the system mounted R/W error when trying to use adb sideload.

Verifying current system...

/dev/block/platform/msm_sdcc.l/by-name/system has been remounted R/W; reflash device to reenable OTA updates

I've checked in EX File explorer, and it's RO.

I went into terminal and checked with mount | grep system, and it also shows /system ext4 ro

So it looks like the standard recovery is mounting it as RW!.. Helpful!

So now I'm stuck.
[Nexus 6  General] codycook:
Same here... Status 7 :(
[Nexus 6  General] MunkinDrunky:
I unzipped the google factory image for 5.1 and tooka look inside. Can I simply flash from fastboot- the radio image and system image? I want the newer radio and 5.1, but not have to overwrite my user data. Is cache image important, or rather necessary? Edit:nvmd about the cache, ans is no, I'd wipe that anyway flashing kernels.

What about the bootloader image (not boot image)-I believe I read it was unchanged? I am rooted and reroot would be no problem.
[Nexus 6  General] jakelauer:
I tried doing this following these steps:

Unzipped the file

Browsed to the folder in question inside META-INF

Removed that line from the file

Saved the file

Replaced that file in the zip with the edited one

Attempted to flash the zip in TWRP

TWRP gave me the following error:

Any ideas?
[Nexus 6  General] YankInDaSouth:
OK, I am officially at a loss here. Tried adb side loading the ota this morning and got stuck in a google splash screen bootloop ... so I flashed the 5..0.1 factory images. Just flashed the 5.1 factory images and I'm loping again:confused: My phone refuses to run 5.1 :(
[Nexus 6  General] Tankslappa:
I thought I'd use NRT to flash my Nexus 6 back to completely stock 5.0.1 (I was rooted)...

And even that's not working!

target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.121s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.507s]
finished. total time: 0.632s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s

target reported max download size of 536870912 bytes
sending 'radio' (67169 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.090s]
finished. total time: 3.197s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s

target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1679613116 bytes
error: update package missing system.img

I think I'm going to give up now... Got better things to do... The pains of the early adopter...
[Nexus 6  General] edif30:
attempting this now. I have not seen any indication that root is not possible in 5.1 so in theory all I'd need to do is root and then flash TWRP and im back in business but on 5.1 and my data intact?
[Nexus 6  General] jeffrey81:
OK I have root unlocked custom recovery. I have the stock image from Google site and the ota file.. I have to flash ota file with twrp or flash the stock image with nexus toolkit keeping twrp and flash SuperSU.zip to root it again.. What is the right thing to do??
[Nexus 6  General] mikeadamz:
I ran into this.. I just flashed the 5.1 factory images and everything worked.. See: http://xdaforums.com/nexus-6/genera...-data-loss-t3053158/post59402819#post59402819 for more info
[Nexus 6  General] El Daddy:
Well you cannot flash a factory image if you bootloader is locked. Flashing an image will not lock your bootloader. The only way to lock it again is the command "fastboot oem lock"

Since the 5.1 image is out. Just download that and edit the flash all script, removing the "-w" flag. Otherwise you can flash each image one by one leaving our the userdata.img.
[Nexus 6  General] codycook:
Did you modify your build.prop to stop the tethering problem? I did, would explain why it is failing... but I had since factory defaulted. I wonder where the flag is for that.
[Nexus 6  General] edif30:
Yup my BL is unlocked ATM. I was just curious of the bootloader within the flash all script. If that was locked or unlocked. I will look into what the -w switch is so I understand better.

Edit -- Duh it wipes data.
[Nexus 6  General] raakaysh:
I don't think you will able to flash OTA with TWRP installed. You must have the stock kernel and recovery at least.
[Nexus 6  General] :
There are several options available. The best one is the one that works best for you. Please take a bit of time and read the first page or two of this thread as many of the questions being asked have already been answered. Personally, I don't use toolkits.
[Nexus 6  General] varkreddy:
I had the same issue. I flashed stock kernel and recovery. Rebooted and unroofed from super su and then flashed system.IMG. Tried NRT to side load but adb doesn't recognize after the recovery is temporarily flashed by NRT. I have to revoke ADB permissions and reset adb . I think flash of temporary recovery is resetting adb permission
[Nexus 6  General] Tankslappa:
Nope... Nothing odd except I was rooted. Even recovery was standard.

So I thought I'd try to just flash system.img to make sure... NRT rebooted it into bootloader, and the PC just sat there saying it was copying system over... I waited 20 minutes, nothing had happened, so I just rebooted the phone and terminated NRT...

Seems that there are lots of things not right... Looks like I'm going to have to do a full nuke flash, and I just can't be arsed right now!

Ooooh, hang on... Just noticed that although I thought the writing of system.img had failed, my phone was no longer rooted... So I gave the OTA sideload another go, and it seems to be doing something now... It got past the verifying update and verifying the current system... It's now patching the current system...

Fingers crossed.

BTW, I've never had a tethering problem... Use my N7 tethered via bluetooth all the time. I guess the my network in the UK isn't being quite that petty yet (I've got 2GB allowance, why should they care what device uses it).
[Nexus 6  General] edif30:
Just thinking outside the box here... Since I can flash all the .img individually... I can just flash the system.img, cache.img, and boot.img then TWRP will remain in tact? Or does flashing the system.img require the stock recovery initially?
[Nexus 6  General] codycook:
I modified my build.prop because AT&T actually enforces it on Android 5 in US and I don't have a tether plan (i could, but I have unlimited, and my work pays for it, so the hacks work fine now)...

If at any time you remounted your /system, which would involve rooting, then you can't use OTA apparently. Tooooooo many changes.

I'm going to go home and reimage to 5.1 later using factory. Such impatience.
[Nexus 6  General] El Daddy:
You probably can, but I have not tried it with 5.0+ so I'm not positive. If you go that route, make sure you flash the radio.img too.
[Nexus 6  General] SmallPsych:
Thank you SO MUCH!!! This worked!!!
[Nexus 6  General] edif30:
I figured I'd just flash TWRP after... So I updated the script to remove the -w. This is the result.

crapple$ ./flash-all.sh

target reported max download size of 536870912 bytes

sending 'bootloader' (3807 KB)...

OKAY [ 0.122s]

writing 'bootloader'...

(bootloader) flashing partition ...

(bootloader) This may take a few seconds if a

(bootloader) different partition table is being

(bootloader) flashed since we need to backup

(bootloader) and restore a few partitions

(bootloader) Flashing primary GPT image...

(bootloader) Flashing backup GPT image...

(bootloader) flashing aboot ...

(bootloader) flashing sbl1 ...

(bootloader) flashing rpm ...

(bootloader) flashing tz ...

(bootloader) flashing sdi ...

(bootloader) flashing logo ...

OKAY [ 0.379s]

finished. total time: 0.501s

rebooting into bootloader...

OKAY [ 0.001s]

finished. total time: 0.001s

< waiting for device >

target reported max download size of 536870912 bytes

sending 'radio' (85422 KB)...

OKAY [ 2.720s]

writing 'radio'...

(bootloader) flashing modem ...

(bootloader) flashing mdm1m9kefs1 ...

(bootloader) flashing mdm1m9kefs2 ...

(bootloader) flashing mdm1m9kefs3 ...

(bootloader) flashing versions ...

OKAY [ 1.674s]

finished. total time: 4.394s

rebooting into bootloader...

OKAY [ 0.001s]

finished. total time: 0.001s

target reported max download size of 536870912 bytes

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

fastboot(865,0xa16511a8) malloc: *** mach_vm_map(size=1779851264) failed (error code=3)

*** error: can't allocate region

*** set a breakpoint in malloc_error_break to debug

failed to allocate 1778070480 bytes

error: update package missing system.img

Any ideas?

EDIT*** I found a solution and will post a comment below... It will be a bit long as I want to state each step I took and what I had to do based on my machine environment. I honestly can't believe its up and working because I swore I wasn't doing this right. Stand by for my post.
[Nexus 6  General] YankInDaSouth:
Think I may be officially bricked ... tried to sideload the OTA this morning with no luck (looped at Google splash screen). So I flashed the 5.0.1 images and went about my day. Came home and flashed the 5.1 images and looped at the Google splash again ... continued to tinker and play. Long story short, in my idiocy I oem locked. Now I can't flash any .img files cause I am locked, can't unlock because I can't boot into Android and uncheck the stupid box in dev options and trying to sideload the ota .zip again yields: "/dev/block/platform/msm_sdcc.1/by-name/system has been removed R/W; reflash device to reenable OTA updates E:Error in sideload/package.zip (Status 7)" ...

Think I screwed the pooch on this one :(
[Nexus 6  General] efrant:
Hmmm. Did you use an editor that preserves the linux line breaks? If you use something like notepad on Windows, it won't work. You need to edit the file using something like Notepad++

A better solution would just to install the driver once your phone goes into recovery to select the update. Windows needs to install the drivers for your device multiple time, e.g., once when booted normally, once when booted with USB debugging on, once when booted into recovery, once when booted into adb sideload, etc., etc.

Sometimes, the flash-all does that for some reason. Since your bootloader and radio are flashed, you just need to flash the boot and system images (and the recovery if you want the stock recovery). So, extract those files from the zip, and flash them one at a time, i.e., "fastboot flash system system.img" and "fastboot flash boot boot.img"
[Nexus 6  General] efrant:
What happens when you type "fastboot oem unlock" when in the bootloader?
[Nexus 6  General] YankInDaSouth:
I get

C:\Android\sdk\platform-tools>fastboot oem unlock

...

(bootloader) Check 'Allow OEM Unlock' in Developer Options.

FAILED (remote failure)

finished. total time: 0.000s

C:\Android\sdk\platform-tools>
[Nexus 6  General] oak:
May not be completely your fault. For me, "OEM unlocking", in developer options, is not sticking. It turns itself off every boot. I am OEM unlocked, so maybe this is normal behavior?? Never noticed before. Sorry for you trouble and hope you work it out.
[Nexus 6  General] efrant:
Can you boot into recovery? Maybe if you wipe in recovery, it will reset the "Allow OEM Unlock" setting. Also, see below.

I haven't quite figured out that setting yet. When I first got my N6, I booted into the bootloader as soon as I took it out of the box and executed "fastboot oem unlock" and it worked. Didn't change any settings, as I never even booted into Android. This leads me to believe that if userdata is wiped, it may allow you to unlock as it would clear that setting.