Here’s the ChromeOS fix for the Lenovo Chromebook Duet 5
Google has updated the issue plaguing Lenovo Chromebook Duet 5 devices since the ChromeOS 117 update. Owners of this detachable tablet are currently three software versions behind most other devices. The issue stems from a USB-C firmware update causing the Duet 5 to be stuck in a boot loop.
On Thursday, the Google Issue Tracker was updated with a status explaining two possible fixes.
The general plan is for Google to remove the USB-C firmware update from the ChromeOS build. That would bring the affected Chromebooks back to the standard upgrade path, starting with ChromeOS 117.
Currently, Google is still working on that mitigation approach and hasn’t provided a date to expect this solution.
Of course, that will only help the Chromebooks that aren’t stuck in a boot loop due to the initial software update. Google pulled the update and says only a small number of Lenovo Chromebook Duet 5 tablets have been negatively affected. Those that have will use the ChromeOS recovery process to download an image without the USB firmware patch.
Note that the Duet 3 is also listed in the official update, although it wasn’t clear until now that these were affected.
- We will be able to unblock updates for both affected boards (Duet 3 and Duet 5).
- Anyone who has a device that is stuck in the “Something went wrong” screen will be able to download/boot a ChromeOS recovery image which will make their device bootable again. NOTE: if your device was at the “Something went wrong” screen then one of the two Type C ports may only be partially functional until the final fix is ready.
Additionally, the hardware vendor for the impacted USB-C port has identified a solution and provided it to Google. Testing the solution internally is positive, so once the ChromeOS software updates get sorted out, the USB firmware will be updated.
We have validated that the fix is able to fully recover the failing device that we had and are starting to kick off the processes needed to get this final fix out. Once the final fix is out then everyone’s Type C component should get updated to the newest version and anyone whose device was at the “Something went wrong” screen because of this issue should again have two functioning Type C ports
My hope is that the ChromeOS updates without the firmware causing problems will arrive within a week. Hopefully sooner. However, I’m sure Google will take the time to properly test all of the software related to this issue. That could take a little extra time but it would be worth the effort.
There is another device that may have a similar issue but I have no real knowledge. The Volteer board devices on Canary are now behind both the Dev channel and Beta channel. My Acer Spin 713 is way behind. It is normal for Canary devices to update daily or at least every few days. It has been maybe two months since the last update. https://issuetracker.google.com/issues/310471042
Really good to hear. I’m a big fan of the Lenovo duet 3 so have been waiting somewhat impatiently to see it brought up to the same release level as other Chromebooks.
My Diet 5 is currently on 118 and I’ve not had any issues.
My Duet 5 13Q76C is stuck on 116