Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yes, but that's just when Google will stop hosting the tool that lets you reflash it. The tool works without Google's servers, and is already hosted elsewhere: https://github.com/luigimannoni/stadia-controller-flasher?ta...


Well, a community effort to reverse engineer the process and deobfuscate the javascript is keeping the tool alive. If they didn't step in to archive it, seemingly the cutoff would have been real.

It would have been a better testament to their commitment to prevent these controllers from becoming e-waste if Google just hosted an open source version of the flashing tool on their github from the start.


As far as I know, the reverse engineering/deobfuscation is only for the purpose of allowing third-party firmware to be flashed instead of the Google firmware for Bluetooth. If all you want to do is archive the tool for the latter, you merely have to copy the files from Google's site.


Oh right, I assumed it required Googles servers to sign the firmware for your specific unit or something.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: