The delay is over: Android 7.1.1 for Nexus 6 coming Jan 2017.

[Chuckl]

What about the speaker phone issue?

Yes it's there. I never use my speakerphone.

 

[uncrx2003]

Do you have a link to an easy step-by-step for sideloading since I've never done it before?

Thanks

 

[VW Maverick]

Do you have a link to an easy step-by-step for sideloading since I've never done it before?

Thanks

I found this, but have not tried it myself. Use at your own risk:

How to download and install Android 7.1.1 Nougat on your Nexus or Pixel right now | Android Central

Mav.

 

[krishnansasikumar]

Do you have a link to an easy step-by-step for sideloading since I've never done it before?

Thanks

Its on the site where you can get the factory images from.

 

[uncrx2003]

After about 30 minutes playing with it, I was finally able to sideload it tonight. The bluetooth issue seems to be fixed. #hopefully

 

[bigmick777]

So I decided to try and sideload tonight and put up with the speakerphone issue (I dont use it very often).

So got ADB platform tools on my windows PC
Set phone to allow USB debugging
Downloaded 7.1.1 from developer.google
Connected via USB and the phone showed up in ADB DEVICES
Put phone into recovery then chose load from adb
then used ADB sideload xxx.zip referencing the download from google
On my phone it shows opening, verifying then come back with E:footer is wrong, E: signature verification failed and the install aborts.

Any ideas welcome - checked XDA and a few other sites and thought I was doing it correctly.

 

[Chuckl]

You downloaded the wrong image.

 

[bigmick777]

You downloaded the wrong image.

Ah right - I went for the factory image - I need the OTA ones then - now do you need to incrementally load the OTA 7.1.1 images - there are two available, suspect one is with Jan updates (N6F26Q) one Feb (N6F26R)?

So can you go direct to the 'R' one or do you have to load the 'Q' one first.

Thanks for your help!

 

[bigmick777]

In case it makes a difference I am currently running 7.0 Feb patches as received OTA from Google.

Update: sorted now. Jan wouldn't load as it said I had a later update. Feb 7.1.1 loaded fine using ADB.

 

[ODog2323]

Re: Nexus 6 to 7.1.1

Any ideas why I could still be on the October security patch with 7.0?? All stock, GPlay purchased N6 running on AT&T. I know there's some of us out here in the same boat.

Will we ever get these updates OTA? I'm thinking not, and I blame AT&T because it's easy!

 

[anon(3653)]

Re: Nexus 6 to 7.1.1

Any ideas why I could still be on the October security patch with 7.0?? All stock, GPlay purchased N6 running on AT&T. I know there's some of us out here in the same boat.

Will we ever get these updates OTA? I'm thinking not, and I blame AT&T because it's easy!

Not just ATT. I am on T-Mobile and experiencing the same thing.

 

[anon(9072051)]

Just curious: had you enrolled your phone in the 7.0 beta program at any point? I'm convinced that enrolling in the beta program screwed things up for me. I think October was the last security patch I got via OTA, too. I gave up waiting and have been sideloading since December.

 

[ODog2323]

Re: Nexus 6 to 7.1.1

As a matter of fact I was on the beta track.

 

[ProBird79]

Re: Nexus 6 to 7.1.1

Just curious: had you enrolled your phone in the 7.0 beta program at any point? I'm convinced that enrolling in the beta program screwed things up for me. I think October was the last security patch I got via OTA, too. I gave up waiting and have been sideloading since December.

As a matter of fact I was on the beta track.

I am in the same situation. Unfortunately the beta page no longer lists our devices so we can't opt out. I still have a best buy gift card on Android Pay so I'm going to use that then Root & ROM it.

 

[anon(9072051)]

Re: Nexus 6 to 7.1.1

Unfortunately the beta page no longer lists our devices so we can't opt out.

I don't think it would make any difference: I did un-enroll my phones from the program once Google confirmed that the Nexus 6 would not be eligible for any post-7.0 beta OTAs. I'm assuming that short circuiting OTA updates appeared as an unintended consequence of some flaw in the way the beta program manipulated account information.