yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] Rooksx:
Will have to put on my dunce cap here but would really appreciate some help with changing the DNS as I'm a total noob with all this Telnet, Busybox, SSH etc. I had Eureka ROM on my Chromecast, but it seems like a lot of streaming services no longer work with that ROM.

So I installed this Autoroot and let the Google OTA update install. The services available in my country (UK) now work, but services from other countries don't - I get error messages saying there's a technical problem when I try to cast content. The problem is not with my Smart DNS provider as the services work on my computer and tablet, so it seems like the Chromecast is using the default Google DNS even though my Eureka settings were set to use the Smart DNS.

I've tried to use busybox vi to create a dns.conf file in /data that has the DNS settings. I think I've created the file successfully as I could see the DNS settings when I tried to edit the file again, but still no joy with casting the content. Some step-by-step assistance would be much appreciated, thanks.
[Google Chromecast] mrdude2478:
For people that use spotify connect with this - I have modded this file to stop you getting ads.

system/chrome/plugins/libspotify.so

I don't have a chromecast, but I do have android TV and this binary uses similar code to call the ads - so I have patched the part of the code that deals with these ads.

You can download and test this (remember and backup your old file first).

https://mega.nz/#!50AHCIgQ!flV7C6WmrlIQljlgnGgIx_8YBnWo2hvLVG3aO3KUebY

Here's a modded android (ad patched) apk (to tested spotify connect with):

https://mega.nz/#!tpQjFKyK!UtetubwTmCI7Iz1w-GY6ueNvdryL160oVBp9Mj-io9o

Anyway - enjoy!
[Google Chromecast] Rooksx:
Bump? I don't think DNS can be customised anymore.
[Google Chromecast] cjkpkg:
I had the exact same error...booting now!!!!

---------- Post added at 02:28 PM ---------- Previous post was at 02:18 PM ----------

Woo Hoo! back in business!!! thank you so much!!! didnt want to have to plunk down $70 on a new chromecast if I didnt have to.
[Google Chromecast] Asphyx:
It can be customized but I'm not sure that it helps at all cause I suspect Google or the App developers have bypassed the DNS for geolocation purposes.
[Google Chromecast] da_mas_man:
Unable to upload

I'm new to XDA. Thanks, the modded APK works great. When I try to send the modded .so file to the chromecast through TELNET and tftpserver, I can download the original. But I cant upload the modded version of the .so file. Error message that File system is read-only.

please any advice would be nice. Has anyone had the same problem?
[Google Chromecast] calvinbui:
Chromecast uses a SquashFS file system (read-only). It is impossible to mount it as RW.

You have to extract it, make changes, mksquashfs it, then flash it back to your chromecast.

AFAIK there aren't any guides on how to do this.
[Google Chromecast] da_mas_man:
Thanks for letting me know. I guess it's even harder than I thought.

Much appreciated
[Google Chromecast] Pietplezier:
How to save the /etc/resolv.conf file?

What i do:

busybox vi resolv.conf

Edit the dns ip

save and quit.

But after a chromecast reboot, it's back to the old dns ip. The data wont be saved. Tips?
[Google Chromecast] thebase:
Hi , tried lot of time but it look like my cc is not able to reboot to recovery anymore.,

Tried via telnet and ssh it do all the script, at the end got this error msg

First block failed verification at byte 8 of 10743808. Wrote 11 replacement blocks to recovery.

then reboot to normal state, i'm stuck on 27946.002 tried also with flashcast usb but Always boot to normal state.

Any idea on how to resolve and update to last build?

Many Thanks,

Base
[Google Chromecast] sumthinphishy:
Stuck in FlashCast 1.3 - No Way Out!

I know this thread has been dead for a while, but I'm hoping someone might take a look through the tumbleweeds and be able to offer some advice. I have had my ChromeCast rooted since the beginning (before FlashCast with my Teensy 2.0). I was running most current version of Eureka, auto-updated. Everything had been fine, but recently started having some issues streaming from some online services and wanted to update and found this thread. I executed the commands, all of that went fine initially, but the CC flashed white for over 2 hours. When I checked the flashcast log I saw the same 'Input/Output Error on /dev/mtdblock6' that others reported earlier. The solution seemed to be to reload FlashCast -- I have tried and tried, but I just seem to be stuck in a loop. No matter how many times I reboot the CC, or try to get the 'bin' file to re-load it doesn't, and I see the same process of trying to update to OTA and fail when replacing stock recovery. I seem to be stuck. I was going to try to go back to the Teensy, but couldn't find the hex files.

Anybody got any advice on how to get through this? And yes, I have read every post in this thread, and almost all of them in the FlashCast thread, and I'm just at a loss now. Honestly, don't even really care about root, just want a functioning stock chromecast, and not sure how to get there from here. I can still ssh to the chromecast and view the logs, but don't know what to do from there. Any help would be greatly appreciated! Thanks!

ETA: Even though I had issued reboot commands and pulled power multiple times, I could not get anywhere. Finally, issued 'reboot recovery' command from FlashCast console. Chromecast rebooted, and I saw stock screen come up and start updating. Killed power. From there, I was able to re-run FlashCast, reflash latest Eureka-ROM and this time the Auto-Root process successfully completed, updated the latest OTA and rooted that. All good. Fixed my streaming issues too -- thanks for the great work devs!
[Google Chromecast] Rooksx:
So I tried using static routes to block the Google DNSs (8.8.8.8, 8.8.4.4). Unfortunately while the Chromecast could connect to the wifi network, it could not connect to the internet. I tried unblocking the DNSs and the device worked fine, so it looks like Google has done something that prevents the Chromecast from accessing the internet unless you're using their DNS.

The one thing that has worked is VPN. Was able to access the non-UK services.
[Google Chromecast] Rooksx:
It works! I had been working with two Chromecasts, I had created the dns.conf file in the Data directory on one but had not done so with the other. Eureka-ROM was originally installed on both before I updated to Autoroot.

I'd pretty much given up so had removed the static routing, but kept the router's DNS pointed at my Smart DNS provider. On a whim I tried Chromecasting Vudu from the Chromecast that does not have the dns.conf file and it worked, as did Comedy Central.

I then factory reset the Chromecast that had the dns.conf file and this now works as well. The dns.conf file isn't in data but casting non-UK content works fine.

The key difference is that I changed from a router that does not let you change the DNS to one that does, so all the devices on my network now use the Smart DNS.

I
[Google Chromecast] Pietplezier:
Thanks! But the readme is to short for me, can you provide a readme with smaller steps?
[Google Chromecast] ForbEx:
Everything is ok for me, moved from 44433.001. Used telnet everytime. Updated to latest version and telnet works like a charm. Thanks.
[Google Chromecast] fink.nottle:
This is great. This is the first time I've done something useful with the rooted chromecast. Do you have the instructions on patching the lib so that we can do it with newer versions in the future ?
[Google Chromecast] fink.nottle:
Yes it works. I've only used it in conjunction with a patched spotify app, but I guess it would work with regular spotify too since the app is just a remote. I can see the original lib on chromecast, but I'm not sure what the easiest way to get it out is. scp doesn't work. Maybe I'll have to use wget/curl for upload.
[Google Chromecast] fink.nottle:
Seems to have it, but not sure if it's usable

Usage: ftpd [-wvS] [-t N] [-T N] [DIR]

Anonymous FTP server

ftpd should be used as an inetd service.

ftpd's line for inetd.conf:

21 stream tcp nowait root ftpd ftpd /files/to/serve

It also can be ran from tcpsvd:

tcpsvd -vE 0.0.0.0 21 ftpd /files/to/serve

-w	Allow upload

-v	Log errors to stderr. -vv: verbose log

-S	Log errors to syslog. -SS: verbose log

-t,-T	Idle and absolute timeouts

DIR	Change root to this directory

tcpsvd is not a binary on the system.
[Google Chromecast] fink.nottle:
It prints the help message. Maybe I need to edit the inetd conf file and run the inetd daemon ?
[Google Chromecast] fink.nottle:
Even with that, it doesn't work. I get "421 Service not available, remote server has closed connection" although inetd starts without any errors.
[Google Chromecast] clubs07:
Is it just me or is the autoroot unable to handle the latest update? My Chromecast hangs on the white Chromecast screen after the latest update. I revert back to Eureka to make my CC work again. Tried updating again with Autoroot and the same result. It used to work well untill a week ago.
[Google Chromecast] fortis91:
Looks like I'm having the same issue, I have 2 that is hanging. Haven't touched these in awhile, how do you revert back to Eureka?
[Google Chromecast] clubs07:
I flashed Flashcast Flasher 1.3 and the latest Eureka.
[Google Chromecast] fortis91:
Thanks. I'll try to revive them over the weekend. Is there a path back to stock
[Google Chromecast] Asphyx:
Mine is working just fine...
[Google Chromecast] clubs07:
I think we need to flash a stock firmware with auto update enabled. There is a thread from Team Eureka with few stock firmware posted but they all have auto update disabled.

I am thinking of unrooting as well.

Can you let me know which firmware you are on?

I reverted back to Eureka firmware twice and used autoroot to update. It hanged at Chromecast text with the black background in both of my attempts after installing the latest updates. I had to go back to Eureka build which is currently useless since I can't stream anything from most of the apps.
[Google Chromecast] Asphyx:
firmware 1.22.80438
[Google Chromecast] clubs07:
Thanks. That is the latest OTA update. I don't know why some devices fail with that update and others work.

I will try autoroot again later and see if my CC manages to update correctly this time.
[Google Chromecast] clubs07:
deleted..
[Google Chromecast] clubs07:
I finally managed to update successfully to the latest firmware.

Once I reverted back to Eureka, I did a factory reset and used Flashcast AutoRoot to update to the latest firmware.

This time it successfully updated without any issues.

I hope this helps you as well
[Google Chromecast] fortis91:
Followed your lead...

Recovered using FlashCast and Eureka then factory reset and ran Flashcast-Autoroot which successfully updated to 1.22.80438.

By any chance were you getting preview updates? I left that off this time.

Thanks again for the info.
[Google Chromecast] ahecht:
This should be a stock Google OTA: http://cache.pack.google.com/edgedl....ef7fdf1f7153dacecc77b7d1a3bb22a97e27ec7e.zip

It was referenced in the install script for FlashCast AutoRoot, but I haven't tried it yet.
[Google Chromecast] clubs07:
You're welcome. Happy to hear it worked for you too.

I didn't opt in for the preview updates I wasn't getting them.

---------- Post added at 07:06 AM ---------- Previous post was at 07:01 AM ----------

Thanks. Now that I managed to update successfully to the latest firmware with Autoroot again, I will be keeping my CC rooted. But I will download the stock firmware just in case I want to unroot in the future.
[Google Chromecast] jasonweisman12:
How to reset chromecast

I had Flashcast Autoroot CC and it's no longer working. When I restart there is a black screen saying "Chromecast...". Can someone provide instructions to either restore Flashcast or factory reset the device?
[Google Chromecast] efrant:
I'm in the same boat. I tried creating a new FlashCast USB drive but since my Chromecast won't boot, it doesn't format the USB drive. Not sure there's anything we can do.
[Google Chromecast] sahilg009:
Yup same here

black screen saying Chromecast...

looks like my chromecast is dead now forever
[Google Chromecast] tdhite:
The easiest method to factory reset the device is press and hold the hardware button (next to the USB port) until it goes to reset mode. Hopefully you will see the reset starting, subsequently the Eureka boot splash suggesting it is updating firmware. It takes a while, just leave it all alone.

With that said, I keep my CC in my travel bag (don't need it for home use) and read this thread before plugging it in to update it (I do that now and then, obviously). Noting that:

I shut of the outside internet connection to my home (just turned the WAN connection off on my router);

I booted the Chromecast (takes a while with no internet connect, and arguably not necessary, just factory reset at powerup);

I factory reset it (hardware button approach);

Upon reboot, it showed the Eureka bootspash, suggesting it was trying to update firmware;

I re-enabled the WAN connection on my router (enabled Internet connection);

Powered on/off the CC;

Upon reboot, it updated normally -- now on firmware 1.22.80438 (so fully up to date).

Turn off auto-updates if you can, never trust others to install firmware without your knowledge. Obviously it pays to read threads like this before updating to see if others indeed found issues (just don't be one of those ;) ). BTW, if you see any screen at all (Chromecast... or whatever), obviously the device booted, the question is at that point whether it's in a low level bootstrap mode or not. I'm not sure about that, but hopefully a reset at that point still works.

Hope that helps someone else. :cowboy:
[Google Chromecast] jasonweisman12:
No luck

Appreciate the response but no luck. Maybe time to junk the CC.
[Google Chromecast] skalagix:
Same issue for me. Autoroot was fine for a few weeks then stuck on black Chromecast... boot screen. Holding down the reset button will induce a Flashcast screen boot-up on the next power-up but it doesn't seem to recognize eureka_image.zip on my powered OTG USB cable.

The notification LED on the Flashcast screen ends up turning red meaning there's an error, but I don't know where to pull an error dump when the Chromecast won't even boot to connect to the internet.
[Google Chromecast] tdhite:
Only thing I can think of is to see if adbd is running. If so, possibly you could adb shell in.

On a side rant, seems one could sue Google if they intentionally harmed your device via tricked upgrade processing, but at 35 bucks, surely not worth the pain. ;) Maybe a class action would be fun just because they deserve it if so. I might argue conversion in such a case, but hey, who knows.
[Google Chromecast] Asphyx:
I have to ask (since my CCast is working and updating without issue)...

Are the ones experiencing problems in the US or other parts?

Are you using some VPN that Google could be blocking from getting updates?

Did you hack anything else (such as a custom DNS.conf) that might be getting in the way of getting the update?
[Google Chromecast] efrant:
Yes, outside of the U.S. I'm located in Canada.

No, I wasn't using a VPN or anything.

No, didn't hack anything else. It was "stock" Flascast-AutoRoot.
[Google Chromecast] Asphyx:
I just think there might be a possibility that Google did something to the update system for Out of US located units.
[Google Chromecast] adammw:
Had the same problem myself last week when they pushed out the beta updates (in AU so not just limited to US), took a fair bit of investigation since nobody on here had worked it out yet. I ended up restoring back to a known good firmware, only for it to auto-update and then end up in the same boat. However, what I did was save the previous OTA.zip that worked while it was updating (recovery has ssh enabled, root@flashcast), and reflash the kernel partition after the update so it uses the old kernel with the new system image. This seems to work, in that the auto-update *thinks* it's running updated code, and works (until a new update comes out of course).

Ideally, someone will work out what's changed (my guess is binaries that the auto-root uses isn't compatible with the new libs and kernel), and fix the auto-root so we can get auto-update working again.
[Google Chromecast] Asphyx:
Actually so far the only two who have replied to my question are both Outside the US.

I am in the US and my CCast is updating and working just fine!

So I suspect that something changed about Updates outside of the US that may be breaking in the Autoroot.
[Google Chromecast] fortis91:
I'm in the US. No custom setting with my devices.

On a side note, I reflashed one of my devices again with Flashcast and can't get it to work properly. The update seems OK as the device reboots and display on the TV initially then the display just goes blank, no signal.
[Google Chromecast] Asphyx:
That sounds different than what others are going through...

You actually get a boot...
[Google Chromecast] o1hitman1o:
I am in the US and having the same issue. Auto updated yesterday and is now stuck at Chromecast... Screen.
[Google Chromecast] aMasheep:
Flashing this on phones?

Would it be possible to flash this on an old phone and achieve a chromecast-like device? More specifically on an old Sony xperia arc s (with hdmi out) running 4.0.4?
[Google Chromecast] bhiga:
No. If you did manage to flash it, I'm quite certain you'll brick your phone. Better to sell your phone and spend the ~$30 on a real Chromecast.
[Google Chromecast] aMasheep:
Yep, I under stand. It would have been a fun project at least..

Thanks for the answer!
[Google Chromecast] bhiga:
There were some "turn your Android device into a Chromecast" projects in the early Chromecast days, but as far as I know they all got killed/abandoned/broken with the updates to the Chromecast SDK. Long story short, the Chromecast environment is too volatile to keep up with and the forced-update architecture makes it easy for "big G" to kill any emulator with a small update. More cat-and-mouse than Sylvester and Speedy Gonzales (Looney Tunes reference). :)
[Google Chromecast] aMasheep:
Yeah those broke.. Have been looking in to it. I better just buy a ChromeCast. Anyways, thanks for your hjelp! And that reference was smooth haha :good: :p
[Google Chromecast] fink.nottle:
Same here. Looks like the update came in today (US) and borked it. Any way to fix it ?
[Google Chromecast] ahecht:
I was able to fix mine by flashing Eureka and then reflashing autoroot, but getting it into the flashcast mode took a couple dozen tries. Seems like the timing between plugging it in and pressing the button has to be just right.
[Google Chromecast] bhiga:
It's always worked for me to hold down the button then plug in power. It's easier if you connect the power adapter to a surge protector or another switchable outlet.
[Google Chromecast] fink.nottle:
I managed to fix it too by doing flashcast -> eureka -> flashcast-autoroot
[Google Chromecast] tvall:
oh, looks like its not just me then. good to know
[Google Chromecast] fortis91:
I fixed 2 using Flashcast, one is ok. The other boots up with eureka on the TV then the display goes away, no signal. Any fix for this?
[Google Chromecast] Asphyx:
Ok, this finally hit my unit...

Fix was easy but does require the original Hubcap Eureka image on a USB stick. You do not need to re-root the device or use the Teensy to recover....

Unplug the unit, Using the Powered OTG cable, Put your USB Eureka Image into the cable and the Power.

Then plug it into the unit and let Eureka re-flash.

When it is done, Telnet into the unit and re-do the Autoroot.

It took a few tries before it would work again (got a solid red led). So you may have to re-do the routine a few times.

Eventually got a good boot and then it said it had to do an update which worked.

Not sure what the issue was but it is fixable!

Fortis - retry autorooting the one that has the screen problem...If Eureka is booting then the Telnet should still be available.
[Google Chromecast] fortis91:
Unfortunately I did a factory reset so the device is not connected to my network. Any other way to communicate with it?
[Google Chromecast] Asphyx:
To connect to network simply use Google Home to set up the device.

If that doesn't work.....

Just reflash the Eureka with a USB drive.

(You will need the powered OTG cable and the Eureka image on a USB drive.)

It should reflash Eureka and even if the screen is not working the Telnet and web server built into Eureka should.
[Google Chromecast] fortis91:
Can't use Google Home to setup, doesn't show up.

After re-flashing a few times it does not appear as if the device is completely booting up, it does show the Eureka logo briefly but it goes away.

During flashing FLASHCAST network is available but as soon as the device finish flashing and reboot the network goes away so there's no way to connect to it.

Here's the last log from flashcast:

Reading recovery parameters
Looking for mods on /dev/sda1
Clearing OTAs
Copying /usr/share/flasher/remove-ota to /tmp/tmp.fHBXJT
Flashing mod at /tmp/tmp.fHBXJT
Mounting cache (mtd4) at /tmp/tmp.ZQ5ch8
Removing temp-ota.zip and ota.zip from cache partition (/tmp/tmp.ZQ5ch8)
Unmounting /tmp/tmp.ZQ5ch8
Removing temporary mod directory /tmp/tmp.fHBXJT
Mounting /dev/sda1 to /tmp/tmp.EsohJQ
Removing old temporary directories
Using runtime directory /tmp/tmp.EsohJQ/flashcast-data/6
Opened log file /tmp/tmp.EsohJQ/flashcast-data/6/log.txt
Created large temp directory /tmp/tmp.EsohJQ/flashcast-data/6/tmp
Found eureka_image.zip, using
Extracting /tmp/tmp.EsohJQ/eureka_image.zip (zip) to /tmp/tmp.rWXZDA
Archive: /tmp/tmp.EsohJQ/eureka_image.zip
inflating: boot.img
inflating: imager.sh
inflating: recovery.img
inflating: system.img
Flashing mod at /tmp/tmp.rWXZDA
EurekaROM-44433.001: Imager.sh now running
EurekaROM-44433.001: Flashing Kernel...
Flashing ./boot.img to kernel (mtd2)
EurekaROM-44433.001: Flashing Recovery...
Flashing ./recovery.img to recovery (mtd6)
EurekaROM-44433.001: Flashing System...
Flashing ./system.img to rootfs (mtd3)
EurekaROM-44433.001: Script Finished!
Removing temporary mod directory /tmp/tmp.rWXZDA
Flashing succeeded
Rebooting
Removing large temp directory
Unmounting and removing /tmp/tmp.EsohJQ
[Google Chromecast] Asphyx:
You shouldn't be using Flashcast first off...

Use the Eureka Image from the Hubcap release.

All you need to do is put the USB into the OTG (with Power) and plug it into the unit after Power and USB is connected.

The unit should eventually flash white if the flash is working. If you look at the screen, you should see the page that says it is flashing.

That should put Eureka on the device. Once it is there, connect it to the Network if it doesn't connect automatically with Home.

I'm pretty sure you need to have setup the network in order for Autoroot to work since it downloads the package from the network.

If you can't even get a screen using the Hubcap Eureka image then the unit is probably faulty.
[Google Chromecast] fortis91:
Either I'm doing something wrong or my device is just defective...

Formatted a new USB and dowloaded image from https://xdaforums.com/showthread.php?t=2578653

Both the device as you said, the screen say it was flashing the image and will reboot after completing, it stayed up for while. Once it rebooted, I'm back in the same situation again.
[Google Chromecast] Asphyx:
You are using the wrong image!

Use the one in this package https://xdaforums.com/android-tv/chromecast/root-hubcap-chromecast-root-release-t2855893

The image is the hubcap-flashcast.bin file inside the Hubcap Zip.

Use Win32Diskimager or dd (Linux) to burn the image onto the USB drive.
[Google Chromecast] fortis91:
Download link is dead... trying to find another.

Thanks.
[Google Chromecast] Asphyx:
Link works fine..Scroll down...

http://download.gtvhacker.com/file/chromecast/HubCap.zip
[Google Chromecast] fortis91:
Thank you, link does work. For whatever reason I'm getting DNS errors with home internet. Downloaded using mobile data.

First couple attempts yielded same result...I'll keep working at it.