Just last week we saw a root method surface for the Chromecast, and just like that, Google is closing the door. Google released build 12840 as an over-the-air update a few days ago, and one of the enhancements is to close the root method. Of course, you might not see that as an enhancement if you were looking to root your Chromecast.
Now it might not be all doom and gloom as XDA member tchebb has posted a couple of methods you can try to stop the OTA from hitting your device. The first thing you need to do is check to see if you’re device has been updated. Just open the Chromecast app on your phone or tablet and tap on the specific Chromecast device. The current build number will be listed at the bottom. If your Chromecast didn’t get the update, then hit the break for instructions.
THE FOLLOWING METHODS ARE UNTESTED AND ARE NOT GUARANTEED TO WORK OR LEAVE YOUR CHROMECAST IN A WORKING STATE. PERFORM THEM AT YOUR OWN RISK.
After telnetting into your rooted Chromecast or otherwise obtaining a root shell, you can try these two possible methods
- Rename otacerts.zip to otacerts.zip.bak in /system/etc/security/. This may remove the OTA signing keys and cause the Chromecast to reject any OTAs. However, I do not know whether this file is actually used or whether is simply a remnant from Chromecast’s Android base.
- Replace /chrome/update_engine with an empty, executable, shell script (make sure to make a backup copy first). I am very unsure of this method, since it is simply going off the name of the update_engine binary. If update_engine happens to perform some task core to the system, doing this will leave your device in an unusable state. If this happens, simply re-rooting using GTVHacker’s USB image should restore your system to how it was.
As tchebb mentions, this one might be a little risky. If you’re feeling brave, be sure to hit the source link for more information.
source: XDA
Come comment on this article: Root method blocked with latest Chromecast update (build 12840)
Powered by WPeMatico
