Chrome OS 80 Stable Channel release pulled 8 hours after being deployed (Update: It’s available)
Updated below: As of right now if you check the official list of Chrome OS versions for all supported devices, you’ll see something different that you saw yesterday. The most current software is now back to Chrome OS 79 across the board, after Chrome OS 80 was widely released yesterday:
Clearly, something isn’t quite right with Chrome OS 80 since Google pulled the update. Chrome OS 80 was available for roughly 8 hours, based on the timestamps of these version changes:
If you did the upgrade to Chrome OS 80 like I did, you won’t be automatically reverted to 79. I’m researching to find out what showstopper issues might be in the software update. However, I did receive this tweet from Derek, indicating some issues he’s already seeing.
I replied to Derek directly but I’ll share that response here.
For those on Chrome OS 80, you can go back to Chrome OS 79 if you’d like but it’s a manual process. You’ll have to use the Chrome OS Recovery tool with a USB stick or memory card and download the firmware for Chrome OS 79. Using the tool, you can then install the prior version. This is why I always carry a USB stick with me.
I’m choosing not to do this, and frankly, I don’t recommend it for most people. Chances are that Google will resolve this issue in a relatively timely manner with a new Chrome OS 80 version. I’m not sure it’s worth the time and effort for the manual recovery unless there’s a specific bug that has a major impact on your Chromebook use.
Update at 2:44pm ET 3/3/2020: 17 hours (almost to the second) after the release was pulled, Chrome OS 80 is again available and rolling out to all supported devices. Given the timestamp between the versions, I suspect there wasn’t any major software issues, but instead, this was due to the release being accidentally reverted. Regardless, it’s available again!
If you just updated to M80 you may be able to do a ‘Rollback’ or ‘Powerwash and Revert’ to get back to M79 without having to perform a full recovery.
To roll ChromeOS back to the previous version without a recovery image:
Sign out of your Chromebook.
When the sign-in screen appears, press and hold Ctrl + Alt + Shift + R.
When the box for “Reset this Chrome device” opens, press and hold Ctrl + Alt + Shift + R again.
Click Powerwash and Revert, then follow the instructions that appear.
Once you click on it, your device will be returned to the previously installed version of Chrome OS. All user accounts and local data will be removed.
Source: https://www.samsung.com/us/support/answer/ANS00077449/
I used this successfully a couple of years ago to rollback from an unstable Chrome version,.
I think I also discovered a bug in Chrome 80. Pixel Slate owner. Before updating to 80, I decided to “disconnect” my phone first because I had problems in the past. I then upgraded to 80, then powerwashed (because it had been a while). Upon setting everything up, I discovered that I could no longer add a connected device indicating that I wasn’t allowed to do this by my “administrator”. This is a personal computer, never had any issues before. I contacted support and they “escalated” this problem after not finding a solution. The support agent agreed it was likely a bug in Chrome OS 80.
I believe this has already been resolved as I received the update shortly before seeing this. Everything appears to be working as expected on my Pixelbook. J
Ever since this update, every two hours or so I receive a notification from the Amazon Music app indicating the last song that app played, even though that app does not have permission for notifications.
You guys need to slow down, stop jumping the gun, stop making assumptions about stuff, and report facts only. As it stands, this is NOT a reputable place to look to for Chrome OS news. Not even close. I hope sincerely that no one foolishly rolled back their OS due to the insanity posted on this website.
Stop guessing. It does nothing for your credibility. Though in this day and age it seems like clicks are all that matter to any site and any “journalist”.
Appreciate the feedback, Scott. A couple clarifications: I’m the only writer here, there’s not other “guys”. 😉 Second, and more importantly, I’m not sure I understand your “stop making assumptions about stuff, and report facts only” comment. The facts are clear and substantiated by timestamps and official Google Chrome OS data. The release started, was pulled, and later pushed out again, as written. And as far as rolling back to Chrome OS 79, I specifically said I recommend most people do not. Some have because they can’t print or watch online video with Chrome OS 80. That’s their choice, of course. Cheers!
I think we’re mixing terms here which might lead to some confusion.
A ‘full recovery’ using the Chromebook Recovery Utility is very different from a ‘rollback’ or ‘powerwash & revert’.
The former completely overwrites your entire internal storage device with new OEM partitions, sizes, and installs the pinned stable version of the OS.
The latter just powerwashes your device and boots the previously installed OS version that was on the alternate boot pair.
I had all sorts of program problems that were apparently related to the buggy OS 80. My favorite note-taking program, Simplenote, went bonkers and started operating in all sorts of strange ways. Other programs started acting buggy, too. My RECENT file got double entries of everything, from screen shots to downloads. I power-washed twice — without any improvement. I got the new 80 update on Monday (March 2). After I installed it, all my problems . . . stopped. I use a Lenovo Yoga C630 chromebook (which I love.)