This seems like a VERY slow rollout, any rumors of problems making them slow it down?

[Wiley_11]

the folks at Google are a band of effin idiots

If Apple functioned on par with Google, they'd be out of business and the iPhone would be a niche product, like the Nexus 6.

Not bad market share for effin idiots.



Nexus 6 is a niche product, And I love mine!

 

[sulla1965]

I have tried flashing my Nexus from Lyz28M and every time it comes back as img file not found. I've used the wugfresh, I've tried the SDK ive tried following the command prompt and still each time it will take the radio and bootloader but than when it comes to loading the image file it errors out... What am I doing wrong

Posted via the Android Central App

If you flash manually, it will work. The key is having all the proper files to flash. 7 files in all. 5 files, boot.img cache.img recovery.img system.img userdata.img are all in image-shamu-lmy47e.zip However you also need 2 other files. Bootloader.img and radio.img. Those are found in the shamu-lmy47e. However they have long file names, simply rename them to bootloader.img and radio.img. Now make a folder containing all 7 files. Open command prompt Just make sure include the proper location path to the file you put the 7 files into. Now flash each individually.

fastboot flash bootloader
fastboot reboot-bootloader
fastboot flash radio
fastboot reboot-bootloader
fastboot flash system
fastboot flash userdata
fastboot flash boot
fastboot flash recovery
fastboot erase cache
fastboot flash cache

Select recovery
power volume up
wipe data/factory reset
reboot into stock

 

[tonyr6]

If 5.1 was not so bad I would have waited but I had a lot of issues from slow Wifi, bad call quality and terrible standby time that I had to flash 6.0. This is why there is no 5.2 as they want to get the horror that is Lollipop so 6.0 is a new version. The bad thing is that they take "forever" to push the update and flashing the factory image is very difficult. I did it but it was not easy way to many errors about system.img and bootloader error junk but I did it thanks to this site. Just remember that the file names are a bit different because it is telling you how to flash the M preview and that +FSG is uppercase. Also once it installs don't sign into anything and check if you are getting your full storage.

If it is cut in half then you have to:

Reboot into the bootloader and type this:

fastboot format userdata
fastboot format cache
fastboot reboot

This is why it it important to check first as I had everything set up and restored on my Nexus 6 and relized I only had 8GB of storage left. I was peeved that I had to start all over again.

Now when I used wugfresh on my Nexus 7 (2013) even flashing the factory image and telling to keep data everything upgraded fine. However wugfresh refused to even unlock the bootloader on my Nexus 6. It is completely useless on my Nexus 6 but my Nexus 7 it works great.

 

[maverick7526]

If 5.1 was not so bad I would have waited but I had a lot of issues from slow Wifi, bad call quality and terrible standby time that I had to flash 6.0. This is why there is no 5.2 as they want to get the horror that is Lollipop so 6.0 is a new version. The bad thing is that they take "forever" to push the update and flashing the factory image is very difficult. I did it but it was not easy way to many errors about system.img and bootloader error junk but I did it thanks to this site. Just remember that the file names are a bit different because it is telling you how to flash the M preview and that +FSG is uppercase. Also once it installs don't sign into anything and check if you are getting your full storage.

If it is cut in half then you have to:


This is why it it important to check first as I had everything set up and restored on my Nexus 6 and relized I only had 8GB of storage left. I was peeved that I had to start all over again.

Now when I used wugfresh on my Nexus 7 (2013) even flashing the factory image and telling to keep data everything upgraded fine. However wugfresh refused to even unlock the bootloader on my Nexus 6. It is completely useless on my Nexus 6 but my Nexus 7 it works great.

Did you click that option in dev options? I had that issue of wug not unlocking my bootloader, and it was because I forgot to check OEM unlocking in options.

Posted via the Android Central App

 

[bulabula]

My notification came in this afternoon. I will update it tonight when I get home.

Sent from either my Nexus 5/6/7

 

[anon(9072051)]

My notification came in this afternoon.

Which carrier?

 

[bulabula]

Today it's Cricket. But I don't think it means anything??? Last week it was on Verizon and Tmo.

Sent from either my Nexus 5/6/7

 

[anon(9072051)]

Last week it was on Verizon and Tmo.

Well, no 6.0 OTA from T-Mobile yet. They're still "testing." Far as I know, T-Mobile's still getting everyone updated to 5.1.1 LYZ28M.

 

[metalgirl3]

No 6.0 update from AT&T yet either.

Sent from my Nexus 6 using Tapatalk

 

[300mag111]

Bit the bullet and did a factory reset on my Nexus 6 with cricket Sim and got ota update right away.

Sent from my Nexus 6 using Tapatalk

 

[EJT]

I got impatient and sideloaded. So far 6.0 is awesome.

 

[tonyr6]

My mother and fathers Nexus 5 phone got 6.0 OTA and standby battery life is now night and day. She forgot to charge her phone last night and it was still at high power what she calls blue (Powertoggles battery meter). Before with crappy 5.1 her phone would sometimes be dead the next day and she had to use her battery backup charger.

 

[bulabula]

I had the same experience with my Nexus 5. The jury is still out on my Nexus 6.

Sent from my Nexus 6 using Tapatalk

 

[Vance14]

hmm, three weeks since the announcement/release and still no OTA for most people, it seems. This really is the slowest OTA rollout for a Nexus device I have seen.

 

[grover5]

hmm, three weeks since the announcement/release and still no OTA for most people, it seems. This really is the slowest OTA rollout for a Nexus device I have seen.

I agree. It does seem to be extremely slow. I'm still waiting for mine on T-Mobile.

Posted via the Android Central App

 

[cozzy123]

The ota is still listed as testing on T-Mobile's site. wonder what is going on. Wish Google and T-Mobile would talk about it

Posted via the Android Central App

 

[ottscay]

I agree. It does seem to be extremely slow. I'm still waiting for mine on T-Mobile.

Posted via the Android Central App

This is about how long it took me to get the Lolipop update on my N5 (I think it was about a month). OTAs aren't trivial when sending it to lots of different devices, and in the case of the N6 on lots of different carrier-specific versions of 5.1.

 

[yankeesusa]

The flashing process has been the same since the first Nexus.

Its been exactly one week since the factory images have been available. No OTA has been available.

There is no correlation between few people getting OTA's being a "bad sign".

No Nexus 6 OTA has been found as it hasn't been released or pushed to a device yet.

Patience.

Actually their is an ota zip that was grabbed from someone that got the ota. Check Android police and other sites. That's how I updated mine. Through adb and zip file.

Posted via the Android Central App

 

[yankeesusa]

The ota is still listed as testing on T-Mobile's site. wonder what is going on. Wish Google and T-Mobile would talk about it

Posted via the Android Central App

Yea, I saw that. The thing is that with 6.0 there is now 1 build for ALL phones. I have it on my nexus 6 and I'm on t-mobile. I have Wi-Fi calling, volte and native visual voicemail writing just fine.

Posted via the Android Central App

 

[yankeesusa]

I haven't even gotten the latest stage fright update. Those shouldn't even be on a scheduled roll out.

Posted via the Android Central App

I got my ota stage fright. Then I just used adb and ran the ota zip manually. Been on it for weeks.

Posted via the Android Central App