Help [Official] OTA update thread

TexasBadger · Mar 12, 2015

SprintDM is needed to connect to the Sprint network, and to keep a N6 in global (faster) mode regardless of network. Verizon Backup, on the other hand, is useless crap. I know this because I gave it a fair trial back when I was a Verizon customer.

codesplice · Mar 12, 2015

Fair enough, but it seems to me that 32KB is a small price to pay for Verizon to hand over control of updates so that it will actually get treated like a Nexus (instead of a second-class Nexus).

TheAmazingDave · Mar 12, 2015

I had the issue too. It turns out, when in ADB sideload in stock recovery, it puts the phone in a "different" mode which the regular ADB driver doesn't pick up. I had to right-click on Nexus 6 in the device manager, click update driver, and reinstall the ADB driver while the phone was in sideload mode. Regular ADB driver picked it right back up after that.

SAL8116 said:
Who's your carrier?

T-Mo

EarlyMon · Mar 12, 2015

codesplice said:
Fair enough, but it seems to me that 32KB is a small price to pay for Verizon to hand over control of updates so that it will actually get treated like a Nexus (instead of a second-class Nexus).

So, you think that Verizon is going to have no say in updates when they have a core app included?

Interesting if true.

codesplice · Mar 12, 2015

EarlyMon said:
So, you think that Verizon is going to have no say in updates when they have a core app included?

Interesting if true.

I don't know about "no say", but my understanding is that all the N6s (in North America, at least) are getting the exact same update - a single OTA to take them all from LRX22C -> LMY47D. It's a pretty big deal (in my eyes) to have Verizon's update included in that.

EarlyMon · Mar 12, 2015

codesplice said:
I don't know about "no say", but my understanding is that all the N6s (in North America, at least) are getting the exact same update - a single OTA to take them all from LRX22C -> LMY47D. It's a pretty big deal (in my eyes) to have Verizon's update included in that.

I have the same understanding about all NA updates as well. And every Nexus owner on Verizon has to be happy to be freed from them.

But the "no say" part must be answered, don't you think?

codesplice · Mar 12, 2015

EarlyMon said:
But the "no say" part must be answered, don't you think?

Absolutely, I'm curious to see how the updates work out in the long-run.

9878 · Mar 12, 2015

TheAmazingDave said:
I had the issue too. It turns out, when in ADB sideload in stock recovery, it puts the phone in a "different" mode which the regular ADB driver doesn't pick up. I had to right-click on Nexus 6 in the device manager, click update driver, and reinstall the ADB driver while the phone was in sideload mode. Regular ADB driver picked it right back up after that.

T-Mo

SAL8116 said: ↑ I am getting mine OTA now in San Antonio on Sprint.

TheAmazingDave · Mar 12, 2015

Yeah, I think I used the sprint OTA package. Whatever was available through AndroidPolice above.

Moot point now, much better to use the factory firmware package. You can extract it, and flash the core system files without wiping data with Fastboot.

Might just do that tonight anyway.

steveu694 · Mar 12, 2015

Anyone know of a wifi calling update? I have zero signal at my apartment

marctronixx · Mar 12, 2015

Get a femtocell for your place...

rhray · Mar 12, 2015

I love 5.1. Thanks for the article on the performance boost not being the placebo effect. Makes sense. I do see a performance boost and also battery savings. And on T-Mobile, the new radio is working fantastic. My phone would jump around from H to 3g to LTE all the time at my apartment, now it at least stays at LTE. It was also nice to go to bed last night and the battery level flatlined until the morning which is unheard of on unrooted stock with all the features on the phone syncing all the time. LOVE IT .... except, now I'm getting double texts from more that one contact who are on different carriers. Going to do some research tonight and thinking about taking the new factory images and reflashing and starting over if I can't fix this

**Edit** Hopefully this helps someone else with duplicate text messages and I think it even may be relevant to T-Mobile in the DFW area. In Settings --> More --> Cellular network, there is an option to flip on or off called "enhanced 4G LTE Mode". I imagine this is for the HD Voice or whatnot which is brand new to 5.1. As soon as I flipped that option, the duplicate SMS stopped. Previous to that, I tried everything from disabling the Messaging app to turning off SMS within hangouts to changing the APN servers, and nothing worked until I turned off that Enhanced 4G LTE Mode option.

I imagine that T-Mobile is still ironing out that network upgrade or it doesn't play well with 5.1 just yet.

Dwight H · Mar 15, 2015

Good Morning,

I have been trying to sideload the Nexus 6 5.0.1 to 5.1 OTA update and keep hitting a snag I could use some guidance with please.

I've been running into a variation of the Nexus 6 on 5.0.1 not being seen by my Windows 7 x64 computer after booting into Recovery problem. ADB Devices shows nothing. Under normal mode operation ADB Devices shows my device number.

I tried the Koosh universal ADB driver route with no change in behavior.

Does anyone have any ideas on how I can get past this?

Thanks in advance!

Dwight

rhray · Mar 15, 2015

Dwight H said:
I've been running into a variation of the Nexus 6 on 5.0.1 not being seen by my Windows 7 x64 computer after booting into Recovery problem. ADB Devices shows nothing. Under normal mode operation ADB Devices shows my device number.

I had the same issue, I recommend just flashing the full images now that they are posted to the google site: https://developers.google.com/android/nexus/images

If that is not an option, have the phone in recovery mode (the yellow text with black background) plugged into the computer with the "Device Manager" screen open on your windows computer. I kept on losing ADB at this point until I unplugged the usb cord on the side that plugs into the computer and plugged it back in again, at that time windows made a PNP sound then I refreshed the device manager screen and the unknown android device popped up. At this point, click into the unknown device, then update the driver and choose something like "browse my computer for existing driver" or whatever it is, from the list, select the koosh driver and you should be good to commence the sideload.

TheAmazingDave · Mar 15, 2015

rhray said:
I had the same issue, I recommend just flashing the full images now that they are posted to the google site: https://developers.google.com/android/nexus/images

If that is not an option, have the phone in recovery mode (the yellow text with black background) plugged into the computer with the "Device Manager" screen open on your windows computer. I kept on losing ADB at this point until I unplugged the usb cord on the side that plugs into the computer and plugged it back in again, at that time windows made a PNP sound then I refreshed the device manager screen and the unknown android device popped up. At this point, click into the unknown device, then update the driver and choose something like "browse my computer for existing driver" or whatever it is, from the list, select the koosh driver and you should be good to commence the sideload.

You have to do that regardless of driver. I use the Google drivers on Windows 8.1. Works a treat.

I agree though that flashing a factory image is the better way now that they're posted.

lunatic59 · Mar 15, 2015

If you're rooted, I don't thin the OTA will work anyway. I just flashed the factory images, but for some reason the flash-all script wouldn't recognize the contents of the update package. I had to unzip it and flash the .img files individually.

Robert7107 · Mar 15, 2015

Anyone know when at&t will release 5.1 "?

Dwight H · Mar 15, 2015

Success side loading my Google Nexus 6 from 5.0.1 to 5.1 with the OTA update (from Windows 7 x64)!

I ended up uninstalling the Koosh ADB Universal Driver set
Uninstalled the Android SDK
Reinstalled the Android SDK and updated it current via SDK Manager...Tools are 24.1.2
Went back and installed the Google USB driver...Revision 11
Connected the Nexus 6 in Debug Mode with OEM Unlock
ADB reboot bootloader
Saw the phone disappear from Windows 7 Device Manager
Unplugged the computer end of the USB cable and put it back in
Saw the device show up in Device Manager with a yellow alert
Right clicked and updated...cleared that error
Then changed the phone to Recovery Mode
Repeated the unplug USB cable / plug in USB cable (still computer end)
Repeated right click to update driver in Device Manager
Finally I could adb sideload ff9e83169f322ffc83b2e94357dd501fd789cab3.signed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip

Now the device is up on Android 5.1 and everything seems to work exactly as expected.

Than you for the help!

lunatic59 · Mar 16, 2015

Robert7107 said:
Anyone know when at&t will release 5.1 "?

The update will come from Google. Carriers are not involved.

jj14x · Mar 16, 2015

codesplice said:
Fair enough, but it seems to me that 32KB is a small price to pay for Verizon to hand over control of updates so that it will actually get treated like a Nexus (instead of a second-class Nexus).

Big Red may have other plans

http://www.androidpolice.com/2015/0...s-6-probably-wont-go-out-to-existing-devices/

codesplice · Mar 16, 2015

jj14x said:
Big Red may have other plans
http://www.androidpolice.com/2015/0...s-6-probably-wont-go-out-to-existing-devices/

As mentioned in that article, there is precedence for releasing a newer "from factory" build on later production runs - it doesn't necessarily mean that VZW is going to take over the OTAs for their N6s, though it will make future OTAs more complicated (since there will need to be separate OTAs for devices on LMY47D and LMY47E). It'll be interesting to see how that plays out.

codesplice · Mar 17, 2015

And the factory image for that weird slightly-newer LMY47E build is up: https://developers.google.com/android/nexus/images#shamulmy47e

Still not quite sure what's up there, but at least it's not just a super-secret leak anymore.

TheAmazingDave · Mar 17, 2015

Maybe it has T-Mo WiFi calling...

One can dream, right?

rhray · Mar 17, 2015

TheAmazingDave said:
Maybe it has T-Mo WiFi calling...

One can dream, right?

Ha! One could imagine, I also think it isn't out of the realm of possibility that Google could through out a Factory image just out there to see who will flash anything, even something without a version number change, just for funsies.

marctronixx · Mar 17, 2015

OTA update pushed to my stock non-rooted virgin nex 6 around 5 ish pacific. Sprint user, Los Angeles.

Help [Official] OTA update thread

Android Enthusiast

Elite Recognized Moderator

Android Expert

The PearlyMon

Elite Recognized Moderator

The PearlyMon

Elite Recognized Moderator

Member

Android Expert

Android Enthusiast

Well-Known Member

Lurker

Well-Known Member

Android Expert

Moderati ergo sum

Android Enthusiast

Lurker

Moderati ergo sum

Android Expert

Elite Recognized Moderator

Elite Recognized Moderator

Android Expert

Well-Known Member

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads