This is a rather odd situation. Has anyone else had problems with the May 2016 Security Update.
Had a Pixel C since launch in December. Has worked flawlessly until May probably my best android I've had. I then installed the May 2016 update and then it started constantly rebooting at random intervals.
Did an RMA got a new Pixel C...restored account did updates through May (thinking it was just a fluke) AND then the boot loader or OS got corrupted and it just booted in the "No Command" screen.
I highly suspect this could have been fixed by manually flashing but my second device also had a pretty bad dead Pixel and a stock update realistically should not prevent it from booting so I am now performing another RMA.
Play support has been great as always and I'm not even really mad, sometimes things happen but if it is an issue with the May Update I'd rather not do this again.
Anyone else have a problem with this update?
Had a Pixel C since launch in December. Has worked flawlessly until May probably my best android I've had. I then installed the May 2016 update and then it started constantly rebooting at random intervals.
Did an RMA got a new Pixel C...restored account did updates through May (thinking it was just a fluke) AND then the boot loader or OS got corrupted and it just booted in the "No Command" screen.
I highly suspect this could have been fixed by manually flashing but my second device also had a pretty bad dead Pixel and a stock update realistically should not prevent it from booting so I am now performing another RMA.
Play support has been great as always and I'm not even really mad, sometimes things happen but if it is an issue with the May Update I'd rather not do this again.
Anyone else have a problem with this update?
Facebook
Twitter
Instagram