If you were one of the lucky developers to get an ADT-1 at Google I/O this year, or from the form for developers, you’ve probably wanted to use it as a replacement for your Chromecast. By default the ADT-1 only supports casting to a select few applications:
- Google+ Photos
- Google Play Movies and TV (Android and iOS only)
- Google Play Music
- Mirror your Android device screen to ADT-1
We can fix this with a simple modification to your ADT-1 using a custom ClockworkMod Recovery and a simple text editor.
Enable USB Debugging
You’ll need to enabled USB debugging before you can do anything.
- Go to the home screen
- Go to Settings > About
- Click on the Build Number 8 times (until it says you’re a developer)
- Go back to the home screen
- Go to Settings > Developer options > Debugging
- Change USB debugging to On
Flash CWM Recovery
Enabling Chromecast for other applications (such as Plex and Songza) is pretty easy. We first need to reboot into the bootloader and flash a custom recovery:
adb reboot bootloader fastboot flash recovery cwm_molly_recovery_lpx13d.img
You’ll need to reboot into the recovery now, click the back button to highlight the Recovery Kernel option (less than 1 second to switch) then hold the button down for over a second to select it.
Once you’re in the recovery you can choose to do a backup in case you can’t get things fixed up.
Mount the System Partition
We’ll need to mount the /system partition to a new folder, the one that is already mounted is from the recovery drive.
adb shell $ mkdir /main_system $ mount -o rw /dev/block/platform/sdhci-tegra.3/by-name/system /main_system
Download and Modify build.prop
We need to download the current boot.prop, and also back it up.
adb shell $ cd /main_system $ cp build.prop build.prop.bak
On your system (not in adb shell)
adb pull /main_system/build.prop
Modify build.prop, you want to change the following:
And then push things back up to the ADT-1 and fix permissions
adb push build.prop /main_system/build.prop adb shell $ cd /main_system $ chmod 0644 build.prop
That’s it, you can reboot now:
Stuck in a Boot Loop?
If you get stuck in a boot loop the permissions probably weren’t fixed on the build.prop, or another setting was changed. You can reboot into the bootloader by holding down the rear button while powering on, then choosing the recovery kernel option again. Once there you can remount the system partition again and try fixing the permissions using chmod.