yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] bhiga:
FlashCast doesn't really "root" Chromecast in the traditional manner. Instead, it is more of a flash utility. And (aside from Eureka-ROM updates, which uses its own internal version), you need FlashCast on the USB drive that you're using to flash with.

Hopefully you booted the FlashCast drive a second time to flash Eureka-ROM or another rooted image with stock updates enabled, otherwise your Chromecast likely has automatically updated and is no longer rootable (technically no longer FlashCast-able).

You can prepare another FlashCast drive on any root-capable Chromecast - it won't change anything on your Chromecast - the first boot simply prepares the FlashCast drive for flashing ROMs/mods.

See Mini-FAQ: Rooting with FlashCast for flowchart.
[Google Chromecast] Murmel2k:
Hi, thanks for your replies.

My Chromecast with Eureka-ROM is up and running. I'm only searching for a way to migrate my 64 GB Flashcast drive to a smaller one. AFAIK most of the addons are being flashed over the USB stick. For example I've used the stick to flash a DNS-mod, so that Chromecast works with the DNS-server of my router, instead of the Google ones.
[Google Chromecast] bhiga:
Since you have Eureka-ROM you can make most changes, including setting DNS, static IP, etc via its web panel at http://ip_of_Chromecast

there are few mods that need to be flashed with FlashCast nowadays.

As for your stick, it isn't "tied" to that specific Chromecast. There's nothing on it to migrate because there's nothing on it that is unique.

If you want to use a different stick, just create another FlashCast stick, then reformat your 64GB stick and use it for whatever you like.

-= this post enhanced with bonus mobile typos =-
[Google Chromecast] Murmel2k:
Same procedure as if I would want to root the chromecast? Except flashing Eureka again, I guess?
[Google Chromecast] bhiga:
Yes, just the first boot stage from the mini FAQ I linked.

Once the drive has the FAT32 partition it's ready to go for future flashing, no need to flash anything as you already have Eureka-ROM loaded.

-= this post enhanced with bonus mobile typos =-
[Google Chromecast] jjl468:
Hi, sorry if this seems like a silly question, but what is the point of rooting a Chromecast? I know the advantages of rooting an Android device and have done so with my Moto X, but I don't really see the point for the Chromecast. Does it let you play more file types, stream from more sources, etc...? My Chromecast is arriving this week and I'm going to use it to watch the occasional movie or TV show, so would there be any point in me flashing FlashCast?
[Google Chromecast] Prack:
Your chromecast will most likely not be rootable. Everything on the shelves now days are updated beyond the flashcast rootable firmware. :(
[Google Chromecast] jjl468:
:/ darn. Well, my question still stands. If my Chromecast just happened to be rootable, what would be the benefits of rooting it?
[Google Chromecast] bhiga:
These should help... I hope. :)

Root Mini-FAQ: What's the big deal with root?

Chromecast Frequently Asked Questions
[Google Chromecast] jjl468:
Thanks :). Sadly, I don't think rooting is something that I'd want to do, even if it were available as I don't understand half of the features listed (I only know about ADB and whitelists, and I don't even think I could use those to my advantage)
[Google Chromecast] reef2009:
Root s/n 4203XXXXXXXX ??

Hi guys I've read this topic but cant fin't my answer.

In the OP there is only written about a s/n in the 3000xxxxx range to be vulnarible.

I got my Chromcast lately with S/N i4203xxxxxxx.

Is there a way to root? I also did connect it to my tv etc. so....

Is there any change to get it rooted?
[Google Chromecast] Prack:
Nope sorry bro, if I had to guess my chromecast at home new in box from launch day is the last one that's rootable lol.
[Google Chromecast] bhiga:
[MENTION=2823721]reef2009[/MENTION],

Currently, only those shipped with the original vulnerable bootloader (build 12072) can be rooted.

All Chromecasts (with 1 or 2 remarkable exceptions) with serial numbers starting 3923 and higher shipped from the factory with builds newer than 12072, so no flashing a rooted ROM via FlashCast because the Chromecast itself won't run FlashCast.

4203 > 3923 so, no deal.

See the Rootable Serial Numbers thread for more info.
[Google Chromecast] FatalIll:
Let's say I have a rooted ChromeCast with Eureka version 15250.001on it. I want to update it, how?

If I need to repeat the installation process, is it problem that I no longer have a flash cast a formatted flash drive?
[Google Chromecast] bhiga:
Answered your first question in the other thread you asked it in

As for needing a FlashCast stick, you shouldn't need one unless the Team Eureka OTA update doesn't work for some reason.

Make sure you do not lose power during the update process! It can take up to about 10 minutes, so be patient.
[Google Chromecast] DroidShift79:
Hi Folks,

just before I brick my new european-amazon chromecast, i would like you to make some things clear for me.

I know my serial is higher then said in the OP but it wasn't put in the TV yet.

i got that OTG cable and an thumb drive ready.

is there any thing i can run OFF tv to check if the device is rootable?

What if I want to set up a FLASHCAST Drive, anyway?

Will the chromecast format the stick anyway or will it deny it?

So far any reason for a brick? (kill chromecast forever?)

if not what when i put eureka file on the stick then and flash it?

Will I end up with a paper weight then or won't it only be rooted?
[Google Chromecast] rekids:
Follow this post to see the firmware version before connecting it to a WiFi of any sort.

http://xdaforums.com/showthread.php?p=52020396

This is for another topic but following the instructions in the post will allow you see the info of your CC before you go any farther to see what the firmware version is.
[Google Chromecast] DroidShift79:
THX. I'll look it up.

Anyway could the Chromecast be bricked like I can never use it when trying to root or does root simply fail and the device stays alive without root.
[Google Chromecast] bhiga:
There's no harm in trying. Either FlashCast will boot and you have the option to flash a rooted ROM, or FlashCast will not boot and you have a "normal" Chromecast.
[Google Chromecast] fkrone:
I bet it won't work. As far as I know every european model is not rootable (at the moment ;) ). You can try it. If it does not work you're Chromecast won't brick.
[Google Chromecast] tchebb:
I have just released FlashCast version 1.3. A changelog and downloads are available on GitHub here.
[Google Chromecast] Marioaguado:
Hello I'm already running flashcast 1.2 any way to update it without using the USB drive? Or otg cable?
[Google Chromecast] persianrisk:
If I flash this do I have to re-flash eurka again?
[Google Chromecast] bhiga:
FlashCast lives on the USB stick, so you need the stick.

If you're running Eureka-ROM, it has its own embedded FlashCast that it updates on its own with its OTA updates.

No. FlashCast is just the flashing utility, much like ODIN is for Samsung devices.
[Google Chromecast] persianrisk:
Great thank you. I don't need to do anything then, and thank you for the update and hard work.
[Google Chromecast] persianrisk:
Hi everyone, this is what I used to root my chromecast, and it worked well! (USB 2.0 A Female To Micro B Male Host OTG Adapter Cable)

http://www.ebay.com/itm/181144487284?_trksid=p2059210.m2749.l2649&ssPageName=STRK:MEBIDX:IT

On the other hand stay AWAY from this one. I think it's a massively produced fake flying around ebay as the power source for them don't work I think ( Micro USB Host Dual OTG Hub Cable)

http://www.ebay.com/itm/Micro-USB-H...Readers_USB_Host_Adapters&hash=item2a3fb7f1ed

Just my 2 cents. Take care.
[Google Chromecast] bhiga:
All thanks to Team Eureka. They work hard, I just answer questions when I have a chance. :)

On the second one the listing notes that the power is for the OTG

devices

only, it does not provide power back upstream to the OTG host, which is required for Chromecast. So it probably works for self-powered devices like the Lenovo tablet, but it will not work for Chromecast.
[Google Chromecast] persianrisk:
Oh thanks for clearing it up...see I wouldn't have gotten that...a bit confusing for us beginners...
[Google Chromecast] bhiga:
To be fair, the listing detail says power for "OTG ports" so it's easy to assume that Chromecast's port is an OTG port too (because it is) and not make the assumption that it's only the hub's OTG ports. :)
[Google Chromecast] sdnick484:
I have a launch cast sitting in its box as well. Been debating rooting it; I just haven't gotten around to it. Are there any compelling apps that require root at this point?
[Google Chromecast] bhiga:
Apps, not really at the moment, but being able to control the whitelist, DNS and IP settings is more than enough reason for me. And you can also enable SSH/Telnet/ADB too.

If none of those appeal to you, consider trading without someone who does want/value those features. Don't let root go to waste. :)
[Google Chromecast] Prack:
Yup if you don't want to root sell it to someone for a few extra bucks and buy another.
[Google Chromecast] matze19999:
I had my chromecast nevertheless connected to the internet. Can I evertheless use flashcast? :(
[Google Chromecast] rekids:
If it has updated (connected to internet) nope no root at this time. Maybe later, maybe not.

Chromecasts are setup from Google to update to latest firmware each time internet connection is available. So every time it boots it checks to see if there is internet connection if there is them it checks for firmware updates available and updates if there is a newer firmware version available.
[Google Chromecast] Senorclean:
I just picked up an Australian chromecast - serial starting in 4507. I assume it's not rootable, but is it worth trying? (I have powered OTG cables)
[Google Chromecast] bhiga:
Since you have all the required hardware you could try for peace of mind but I wouldn't hold my breath. ;)
[Google Chromecast] Senorclean:
Yeah - I gave it a try - it was obviously reading from the drive for a while, and then threw a 'startup problems' help screen. I guess that means it's not vulnerable.

Oh well, I guess root isn't really necessary, but it would be nice!
[Google Chromecast] bhiga:
Yeah, that means it did a reset rather than boot FlashCast. Maybe we'll get some exciting news at DefCon.
[Google Chromecast] helpmeplis:
Got a question here. Will any powered otg cable work? The one linked will not ship to Puerto Rico. Could anyone recommend a couple from amazon?
[Google Chromecast] rekids:
http://www.amazon.com/gp/aw/d/B009YPYORM

This is the one I got and it works well and not a cheaply made one that falls apart right away. So far I have been very pleased with it.
[Google Chromecast] persianrisk:
This worked for me just perfectly:

m.ebay.com/itm?itemId=181144487284
[Google Chromecast] helpmeplis:
Thanks for the suggestions. Bought the one from eBay because it doesn't have a 9.99$ s/h charge hehe
[Google Chromecast] persianrisk:
No probs at all ;) Hope you enjoy rooting your cast
[Google Chromecast] DirkStorck:
I try to flash Ereka-ROM to my new Chromecast

If I do the steps like in the installation instruction the LED is blinking white and than goes to red and stays red.

My serial number starts with 4220. Maybe thats the problem ?!? :/
[Google Chromecast] eKeith:
Correct. See http://xdaforums.com/showthread.php?t=2537022
[Google Chromecast] gunvalk:
Thanks
[Google Chromecast] OldGaf:
FYI.... I use an old PC running pfsense as my router and getting this to work with unblockus is a snap.... less the 5 min (no VPN needed).

( Page I found this on)

For the unbehaving Chromecast, with its hard-coded Google DNS, we are forced to add a NAT rule to reroute all DNS requests.

In Firewall | NAT | Port Forward, add a new rule with these settings:

RDR: Unchecked

Interface: LAN

Protocol: UDP/TCP

Source: IP of your Chromecast

Source port: any

Destination: any

Destination port: DNS (53)

Redirect target IP: the DNS server of unblock-us or similar service

Redirect target port: DNS (53)

I like this as it does not make everything in the house use unblockus... just the chromecast.
[Google Chromecast] leonelfolmer:
Doubt about to reset

Hi, I have a doubt about it. I have a Chromecast begins with SN 3814, but is updated with the build 17977, if I reset the Chromecast would be possible to use FlashCast v1.3?
[Google Chromecast] tchebb:
No. Resetting a Chromecast only reverts its configuration (things like the saved Wi-Fi networks). It does not downgrade the OS to the original build, so after the reset you would still be on 17977, which is not supported by FlashCast.
[Google Chromecast] rekids:
No the unit already updated all a reset does is quite user inputted info.
[Google Chromecast] leonelfolmer:
Please, tell me if it is possible modify the content files via hardware changes? I mean, access the content via some modification in the hardware.
[Google Chromecast] rekids:
SOC memory is not accessible by any means I know of since JTAG has been disabled, and any software stored on the NAND has to pass the signature check to run.

The signature has since updated after 12072 thus 12072 will no longer run once it has been updated. That's the short of it.

Correct me if I am wrong tchebb.
[Google Chromecast] leonelfolmer:
You know if there is any progress to get root on new devices? or if that will be impossible?
[Google Chromecast] rekids:
;) rumor has it there may be one released at the Vegas show this year wait and see. I am sure if it is Google will plug quickly
[Google Chromecast] idone:
Hi.

Rooted via hubcap and running latest eureka ota.

My question is: Does flashcast need to be plugged into hdmi for it to setup the usb stick?

Powering it on my bench and holding down cc's button the cc's led stays red (I've held button for minutes) and never reboots or setus up flashcast usb.

Same usb drive that I used for hubcap's img. I tried version 1.2 and 1.3 of flashcast img.

Thanks in advance for any replies.
[Google Chromecast] tchebb:
FlashCast should still boot without HDMI connected. In fact, that's how I do all of my testing during development. It sounds like the FlashCast image didn't get copied properly to your USB drive. Make sure that you're using dd, Win32DiskImager, or a similar utility to copy the image, and try re-copying it if you haven't already.
[Google Chromecast] idone:
[MENTION=2789381]tchebb[/MENTION] thanks for your reply!

I ended up grabbing an extension cable and connecting to the tv after multiple more unsuccessfull attempts.

Powering it with cc's button held produced a screen with 10-11 dots left of center.. after minutes of holding the button/and releasing the button they persisted and cc led remained red no matter how much time elapsed.

After powering up cc with the usb stick connected (no button pressed, till at cc's main screen) then holding cc's button for 20 or so seconds till it reset itself to red light(recovery) it finally set up flashcast usb and the stick is now recognized by pc and ready for mods.

Thanks for your work on this device! It really is appreciated.
[Google Chromecast] Srandista:
Ok, so after successful root of my CC with HubCap, I though, that would be rather good to prepare my USB for eventual mods, with FlashCast. So, I download FlashCast from this thread, used Win32DiskImager again, to write FlashCast.bin to USB, and connect it to rooted CC (I hope, that I didn't screw anything with this). After reset of CC, I insert USB to PC, and it's now called FlashCast, which is good, I thing.

My question is now, can I store on my USB more than one file, and when I want be flash something, just rename one of these files to correct name, and FlashCast will ignore other files? Or I have to have always just one file with correct name?

And is there some way, to check version number of FlashCast on rooted CC?
[Google Chromecast] idone:
There is good documentation to explain what file names and directories flashcast will act upon, as well as source code to see exactly how everything shall be carried out.

https://github.com/team-eureka/flashcast-flasher/tree/master/docs

You can check version of cc in cc setup app or by connecting to it's ip in a web browser thats on the same lan.
[Google Chromecast] Srandista:
So, I already tried, that is safe to have multiple files in USB, important is a name of a file.

And about my second question, I don't mean version of CC, but version of FlashCast on CC. Is there a way, how to check that?
[Google Chromecast] tchebb:
You're free to use a FlashCast USB drive to store files just like any other USB drive. FlashCast will ignore all the files on the drive except for the ones named eureka_image.zip, eureka_image, flashcast-data, flashcast-mods, and, Chromecast-Rooted-System-GTVHacker-cj_000-July27-635PM.bin (that one's for compatibility reasons). Even these special files only matter when you're actually booting a Chromecast off the USB drive, though. Any computers you use the USB drive with can't even tell that it has FlashCast installed, so they will treat it exactly like a regular USB drive.

As for the version number, we aren't yet capable of displaying it on the TV. If you SSH into the Chromecast after booting FlashCast, however, you'll see the version number in the header (e.g. "Welcome to FlashCast version 1.3!").

Thanks for asking!
[Google Chromecast] Srandista:
One more question. If I want to make a new mod/change existing mod for FlashCast, I don't need to take into account verification of package, like with apk's on Android, right? If I want for example change DNS servers in DNS mod, I can just extract package, change IP's in conf file, repack it and upload it in FlashCast, correct?
[Google Chromecast] tchebb:
That's correct. The developer documentation that [MENTION=319373]idone[/MENTION] linked to has detailed information about writing and packaging mods.
[Google Chromecast] DC_MTP:
I just picked up a "RECERTIFIED" chromecast. I hooked it up to my network and notice it wanted to download an "update" so I quickly pulled it out and turn my router off. ...so seems like to me its on an older firmware but i have no way of knowing what build number. what can I do to attempt root?

my serial number begins with 392910 and right below it there is a new sticker placed on my box ( begins with GA3A)
[Google Chromecast] bhiga:
Serial is meaningless on a recertified unit. I had to use the 16xxx HubCap image. I doubt any recertified units ship with 12097.

One should work unless they've updated the repair centers (not unlikely) and exhausted the stock in the channel (unlikely).
[Google Chromecast] DC_MTP:
so seems like the only way to check will require the purchase of a teensy and sadly I can't afford one right now :( barely managed to get the recertified chromecast for $15 on a Groupon deal.
[Google Chromecast] bhiga:
Depending on where you live there might be someone around with a Teensy who's willing to root or trade.

If you have they parts you could try the original FlashCast exploit, just in case you got lucky.
[Google Chromecast] rootbeer001:
i just got my groupon recertified chromecast, and was able to check the build #: 15098. can't be rooted easily, unless any is in the louisville, ky area and has a teensy and OTG.
[Google Chromecast] TheSwede86:
(Sorry for reposting this, posted this in the "[ROM] [19084.001 - 2014-09-12] Eureka-ROM - Based on OTA 19084" ROM" thread first but guess its more applicable to this post)

Hi!

Just tried to root and flash the custom rom (19084.001) to my Chromecast (17977).

I did these steps here:

http://xdaforums.com/hard...lease-t2855893

and they all worked out fine, now I have a "Team Eureka" logo at the startup of my CC but the USB-drive which I wrote the .bin to does not show up in Windows, enabling me to put the 19084.001 ROM onto it.

I had to manually partition the unused space on the USB and tried putting the renamed 19084.001-zip (renamed to eureka_image.zip) there but the USB seems to try to root my Chromecast again and then responds with a solid red LED.

Edit1:

I am able to go to Team Eureka's configuration page for my CC and see there:

"ROM Version:" (the space after the ":" is blank)

and also:

"Build version: 17977.001"

Edit2:

http://dl-1.va.us.xda-developers.com...&ts=1412365304

Following this I actually see a small row of dots to the upper right of the center of my screen, although my primary problem is that I can't "see" or access the USB-stick in Windows.

I tried with another USB and did the flash process again (only with the USB, not with Teensy) and it "worked", restarted and could still access my CC and get to the Team Eureka web-interface but my computer can't detect that USB either. I still get the "Team Eureka" logo on startup and then it reverts to my "original" CC (No internet connection found). Also the case with a third USB I tried, none are detected in Windows but I can still see the "Team Eureka" logo at the CC:s startup and log into the "Team Eureka" web interface.

Would be grateful for any assistance and sorry if I missed something completely obvious / TheSwede86
[Google Chromecast] fkrone:
First of all: the links are broken in this thread. Please do only post in one thread if you have a problem, otherwise people may get confused and angry ;)

You don't need to apply the 19084.001 update if you have Eureka OTAs enabled in the web panel. If not, enable it, apply changes and restart your Chromecast. It should install the update a few minutes later.

If you want to use Flashcast to manually apply the update:

"Burn" the Flashcast image on the USB drive (as you did with HubCap), boot your Chromecast with the stick, attach it back to your PC and you should be able to copy the 19084.001 update to it and flash this to your Chromecast (OP describes the steps better than me in short). Do not partition your stick manually after applying Flashcast. This is not how Flashcast will work (but don't ask me why, some "magic" behind the whole thing).
[Google Chromecast] TheSwede86:
First of all thank you for answering. Yes, I know I should not "crosspost" but I didn't know which thread (i.e. this one or the "ROM"-one) it would be most suitable for. I have now edited and removed my post from the other thread :)

Just so I don't do anything stupid, this is what I see on my "Status" page in the Team Eureka web-interface:

"Build version: 17977.001 (24/7/2014)"

System status:

"Device name: Asdf"

"Serial: 4217********"

"Rom version:" [blank after ":"]

"CPU Temp: 30"

If I go to "Settings" I have "Team Eureka OTA: Enabled" and "Team Eureka" is on the "whitelist", does this automatically mean if I know connect my router to the internet again that Google's own OTA updates are in the blacklist (which I can't see anything about) and the CC should upgrade itself with the latest Team Eureka firmware?

Ah so that is what I did wrong, I have always burnt the "hubcap-flashcast" to my USBs (even after I have correctly done that step with Teensy++) and hoped that after it has "flashed" Flashcast the USB will be accessible in Windows.
[Google Chromecast] fkrone:
If you have Eureka ROM installed, the Eureka OTAs are used (http://ota.team-eureka.com/). Google OTAs are disabled on Eureka ROM.
[Google Chromecast] TheSwede86:
Thanks for your reply, found this link which said that it also had the Eureka ROM installed, was worried with the "ROM Version:" text that I didn't have any ROM and that Google's OTA could still be a thing.

Although now the "ROM Version:" field reads "Update available" but it does not seem to download and install it (tried rebooting). CC does not update itself, still on 17977.001 but my CC gets "We had a problem updating your Chromecast to the latest version" on my TV. Don't know if "all" people with Eureka ROM get that error since Google's OTA are blocked but still, it seems not to download the latest ROM from Team Eureka.
[Google Chromecast] fkrone:
If you boot up your Chromecast Eureka Updater tries to connect to Eureka OTA server. For me it fails the first time. After 5 minutes it checks again. This time it should download the update (around 100MB) and install it by itself. Just give your Chromecast some time.