The fix has been put in abode bristles months afterwards it was aboriginal reported.
Google has anchored a bug that acquired some Google Pixel 2 accessories to abort back aflame Android 8.1 Oreo. The affair aboriginal appeared aftermost October with the rollout of the again new software, and was apparent back some users approved to install it via Fastboot.
There were reports that accessories had artlessly bootless to install the firmware, while some claimed it had bricked/soft bricked their handsets. Google pulled the Android 8.1 branch images anon afterwards this happened to anticipate added problems, but it has taken until now for a able fix to be put in place.
As appear by XDA Developers, Google has appear a new accomplish in the Android Open Source Project (AOSP) which addresses the issue.
“The Pixel 2 arrangement images absolution was a bit of a adversity because anyone application an old adaptation of Fastboot would blindly beam too few partitions, potentially bricking their device,” it says in the commit.
“This change lets us add a band to the android-info.txt book for a accessory with a new partition.”
Redditors are now flinging sh*t at anniversary other discussing whether it was account aggravating to beam the firmware in the aboriginal place, back Pixel owners could accept aloof waited to get it over-the-air. For what it’s worth, I anticipate if Google about posts new firmware, you can’t accusation bodies for aflame them, and I accede a fix should accept accustomed sooner.
That’s my view, what’s yours? Hit me up in the comments.
Up next: I’m done with 18:9 displays, accord me a Pixel 2
- Google has addressed a botheration that acquired some Pixel 2 accessories to abort back aflame Android 8.1 Oreo.
- The affair was aboriginal apparent aftermost October and it is said to accept bricked some devices.
- Google discussed the affair and its resolution in a contempo AOSP commit.
Comments
Post a Comment