Google Chromecast Rooted!

Post by **zenofex** » Sun Jul 28, 2013 2:21 pm

We've rooted the Google Chromecast!

More info can be found at http://blog.gtvhacker.com/2013/chromeca ... by-google/

Instructions for the process can be found on the GTVHacker Google Chromecast wiki page: http://wiki.gtvhacker.com/index.php/Goo ... it_Package

Thanks,
Zenofex

embracenext · Post by **embracenext** » Mon Jul 29, 2013 9:18 pm

Sorry if this is a noob question, but on your video of the chromecast hack, I saw on the left monitor you had CLI access. I read the wiki about the UART but it was stated that was only to log the boot process. How did you get past that to enter text to the device?

Thank you

smokestack · Post by **smokestack** » Thu Aug 01, 2013 1:07 pm

i am trying to find this powered cable with no luck. is there a good picture of what is looks like exactly. or a video on how to make one? any ideas?

coggy9 · Post by **coggy9** » Thu Aug 01, 2013 4:40 pm

smokestack wrote:i am trying to find this powered cable with no luck. is there a good picture of what is looks like exactly. or a video on how to make one? any ideas?

Use a cable like this one here: http://www.amazon.com/gp/product/B009YP ... UTF8&psc=1

stangri · Post by **stangri** » Mon Aug 19, 2013 9:39 am

Besides blocking dl.google.com in the hosts file or on the router, is there any other way to prevent OTA from installing on a freshly rooter Chromecast?

thanks!

gtvguy · Post by **gtvguy** » Fri Aug 23, 2013 8:50 pm

stangri wrote:Besides blocking dl.google.com in the hosts file or on the router, is there any other way to prevent OTA from installing on a freshly rooter Chromecast?

thanks!

Be careful! Blocking dl.google.com doesn't seem to effectively prevent the OTA update... The current gtvhacker exploit image is an old build (12072) that should not be flashed at this point if you want to keep root. You can flash an updated image based on build 12840 that has OTA blocking built in--get it here:
http://forum.xda-developers.com/showpos ... stcount=49

Basically, the creator of the new image updated the /system partition (but not the kernel) to 12840 and removed the /chrome/update_engine binary and replaced it with an empty script.