yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] elborak:
Weird. I've had no such problem with multiple Pro Micros. Just shorted reset to ground and it went through the normal bootloader process and displayed the usual "Arduino Leonardo bootloader (COMn)" in the Windows device manager.

In fact I just tried it again to confirm. Not sure if you did something different or whether your Pro Micro is somehow atypical. What did you use to program the exploit hex file originally?
[Google Chromecast] megaphat:
Possible. It was some $7 ebay special.

Arduino Builder.
[Google Chromecast] jaydee 77:
Did this work for anyone?

I've tried this with a PS2YES! programmer without any luck.
[Google Chromecast] RowtronX:
Rooting help

I tried finding the solution, but I am having no luck

Teensy 2.0 w/ 16664.hex

Chromecast Serial 38**** with an updated firmware from packaging, but I'm not sure what it is.

First and foremost, thanks for the root method. I have successfully rooted 2 chromecasts.

My issue is... when I hold the reset button and plug in the Chromecast, I get a white LED, then a dim red. My Teensy does not power up. I am wondering what the issue is? The LED works for sure because I've tested it with the blink LED in the Teensy program.
[Google Chromecast] ghowse:
Suggest you power up Teensy first, then plug in the CC while holding down the button. Release the CC button just after the LED goes off (about 1.0-1.5 sec). I have rooted 3 CCs this way. I found that the timing of the CC button release was the critical step. Just keep trying.
[Google Chromecast] elborak:
Why not confirm what firmware the CC is running?
[Google Chromecast] RowtronX:
Sorry guys!!! my ish got upgraded :'((((
[Google Chromecast] linuxbman:
I'm having the same problem with my Leonardo clone. What was the programmer you used? I'd like to get more use out of this board.
[Google Chromecast] new2and:
Thanks, Chromecast Rooted

For anyone that's interested, I used the Leonardo_1664.zip hex files on the Pro Micro board. I used the Arduino Builder to get the hex files onto the board. For the drop down, the board type I used was Arduino Micro.

I followed the video in post one (I didn't worry too much about the lights) but it worked first time with no problems.

Much thanks to Team Eureka for all their hard work, moesus for his nice write up (post #630) & elborak for the Leonardo_1664.hex file (post #589).
[Google Chromecast] LondonS3:
Found out I had flashed the wrong version image for my chromecast the first time and was unable to re-flash my pro micro to the other image either, so mine has been sitting unused, waiting for the next time I feel like wasting some more frustrating hours working on it!

I have seen a lot of talk about FTDI disabling usb to serial hardware with a Windows driver update they released late august/early September, claiming they were only breaking counterfeit equipment. Could this issue affect these chips?

More info:

http://arstechnica.com/information-...usb-serial-chips-beloved-of-hardware-hackers/

http://www.theregister.co.uk/2014/10/23/ftdi_turning_counterfeit_chips_into_bricks/
[Google Chromecast] dwarf_t0ssn:
Was wondering the same. The drivers in question have been removed from Windows Update, though, so all should be well. No idea if they were ever deployed or affected anyone with a clone.
[Google Chromecast] elborak:
These are all ATMega32U4 based boards, which have builtin USB (hence the ability to mimic a USB hub which the exploit relies on). Therefore no FTDI chips. Your problems are pilot error, not chip/board/driver problems.

You should be able to reprogram just fine with avrdude.
[Google Chromecast] by3times1minus1:
So the 12940 hex worked fine for the one I got with FW 12940 (obviously), but the other 2 CC's with FW 15098 required me to use the 16664 hex actually (similar to what another user on here reported earlier). I kept getting a solid red light after trying the 12940 hex on both of those. Anyway, I got all 3 of mine rooted in a short amount of time once I got everything set up.

Took a long time to get the parts in from China and probably just as long to figure out the Arduino Pro Micro. The hardest part was figuring out how to reset it back to the bootloader once I had uploaded a hex file to it already. Don't know if I was doing something wrong, but it would only show up as a USB device instead of a serial/COM port after flashing the first hex unless I got it into the bootloader. This helped me understand it a little better though. You only have 8 seconds to reflash it once you get it back into the bootloader, so it would greatly help if you had an extra set of hands (it took me several tries to do it by myself with my set up).

Thanks so much [MENTION=2640163]elborak[/MENTION] and [MENTION=2131337]moesus[/MENTION] for your help with the hex files and guide for the Arduino Pro Micro respectively. The LEDs worked great with the new hex files. Couldn't have done it without your guidance and help.

I was having the same issue as you guys and didn't know what to do. I grabbed a jumper of an old IDE hard drive and used that to short the reset to ground pins on my Micro Pro. I'm new to Arduino, so that took me quite a bit of time to research and discover. I did it twice in succession within 750msecs to get into the bootloader for 8 seconds. Within that 8 seconds, I had to use AX Loader to flash the other hex on there. Gotta be quick! Otherwise it boots back up as a USB device and loads the old code you had on there already. See the link above for more details.
[Google Chromecast] LondonS3:
Thanks for the info and to get that worry out of the way :)

As much as I tried, was unable to flash with avrdude in linux which is why I booted in to windows and used the AX loader program (or was called something similar) which was posted earlier in this thread which worked as soon as as I chose aduino leonardo board from the drop down menu.

I had found the reset instructions and tried that many times with the double tap but without success. Was rushing to beat the 8 second loader time but couldn't get it to come up as a COM port again after the initial flash and without that the program wouldn't attempt to flash again.

---------- Post added at 12:56 PM ---------- Previous post was at 12:52 PM ----------

I take it you did this under Windows? I had found those instructions too but still couldn't get the COM port to show again. The LED's would flash off briefly when gnd and rst were connected so was able to see it was doing something on the board at least.
[Google Chromecast] by3times1minus1:
Yes on my Windows 7 HTPC (you can imagine how difficult that was to use suboptimal wireless devices to be quick enough). My main computer is a macbook pro, which I haven't tried doing anything Arduino related on. It took my several tries to get the new hex loaded in the 8 second window, so keep trying the double tap/short and you'll eventually get everything lined up to go within the given time.
[Google Chromecast] elborak:
Just to make sure you're understanding (not 100% clear from your description), you don't leave ground & reset connected, you just short them momentarily. That should enter bootloader mode for 8 seconds.
[Google Chromecast] crnkoj:
Actually need to short them twice momentarily, than its bootloader mode. Can do that even when the board is already connected to the pc via USB (at least on mine)
[Google Chromecast] elborak:
That depends on the model of board & what bootloader is installed (see https://learn.sparkfun.com/tutorials/pro-micro--fio-v3-hookup-guide/troubleshooting-and-faq). With the ones I have (purchased from various AliExpress vendors), it's not the case.
[Google Chromecast] cat2115:
Hi,

If I buy CC at bestbuy, can I still root it? If so, after root, can i install xbmc in CC? thx
[Google Chromecast] bhiga:
Maybe. It will depend on whether the unit already has the 19084 firmware build or newer from the factory.

I would look for one that hasn't been opened (check the seal) and has the lowest starting 4 places of the serial number just to be sure.

Chromecast would be a client to XBMC. XBMC itself needs to run elsewhere, unless someone's found a way to run XBMC directly on Chromecast recently.
[Google Chromecast] elborak:
So far as I know, no one has yet reported seeing 19084 firmware on a CC out of the box.
[Google Chromecast] stonejag:
Happy to report a successful root with a freshly-unboxed CC (bought from Amazon UK) that arrived running fw revision 15098.

Used a Teensy 2++ (handy really, I've been meaning to buy one for something else!) and HubCap - all went fine once I realised there was a HubCap-specific Flashcast image to dd over to my USB stick, and that you didn't have to manually add a Eureka revision! Was thoroughly confused up to that point.

I'll add it to the main thread on rootable serial numbers, but interesting to note that my serial starts 3C30 - think that's a new record.

Many thanks for all the work put in to make this! :good:

Stone
[Google Chromecast] bhiga:
The rootable serial numbers realty only applies to the original root method. Well, at least until we start seeing units with 19084 or newer from the factory.
[Google Chromecast] youxiaojie:
what is the responds of written teensy when plugged into PC?

Hello, I root my used CC with SN 3927 and 14650 version rom following the instraction.teensy used regular 16664 files.but during the whole process the CC always keep bright red and the teensy 2.0 blink for a while .when the teensy became dark,i change teensy to usb disc with a light (R/W indicator).and then i push the button of CC,nothing happened.CC neither read nor write usb disk,which can be proofed by the dark usb disk light. I doubt my teensy 2.0 has something wrong. When I connected the teensy with pc, it shows usb-hub with a yellow "!". How about others' teensy?:confused:
[Google Chromecast] elborak:
The serial number means nothing with the current root. What version of firmware is running on your CC?
[Google Chromecast] Mad07:
Does you've flash the teensy successfully on the PC?

I don't believe, because a) ifthe teensy contains the right flash, the teensy is blinking also if the Data wire not corrct to the CC e.g. brocken.

Please try following: insert the teensy in an USB Port , press the black button on the teensy and the PC should be busy for a while to add the needed driver.

After the driver are installed,start the small flash-programm for the teensy and the program should recognise the HW
[Google Chromecast] youxiaojie:
now 14650,13300 before update uncarefully

---------- Post added at 01:08 PM ---------- Previous post was at 12:49 PM ----------

I burnt many programms from ide, serial, blink led,all are ok.but not try to compile source of 16664 .
[Google Chromecast] elborak:
I don't understand this. How could you have accidentally updated to an intermediate version? Either you should have what your CC shipped with, or it should have updated to the latest version (which isn't presently rootable).
[Google Chromecast] by3times1minus1:
The only thing I can think of is maybe he updated it long ago to 14650 when it was the most current FW? And since then he has prevented it from connecting to the internet ever again to wait to root it or something? I dunno...that's all I can come up with. Possibly a communication gap/misunderstanding though.
[Google Chromecast] elborak:
Possible, I suppose, but very unlikely. 14650 came out in December of 2013, and a Chromecast which can't connect to the Internet is nothing but a funny-shaped paperweight.
[Google Chromecast] youxiaojie:
yes.after try it once,i have never let it connect to internet. unplug the network cable. can you answer my question on teensy 2?
[Google Chromecast] elborak:
I used a different board to root, so sorry, no answer.
[Google Chromecast] ghowse:
Are you sure the Chromecast has not been successfully rooted during your trials? You can check by entering the CC IP address in a browser and seeing if the Team Eureka config page is shown. WARNING: ONLY DO THIS CHECK WITH YOUR INTERNET DISCONNECTED. YOU MUST PREVENT AN OTA UPDATE FROM GOOGLE!!!
[Google Chromecast] youxiaojie:
yeah. after first use,i try it when the net cable unpluged.
[Google Chromecast] youxiaojie:
a good news,changing a computer,refeshing again,ok.yellow ! disappear.but root chromecast still fail.having changed 3 different usb disk.
[Google Chromecast] :
I just rooted my CC from an old unopened box, I had to use plusplus_16664.hex for some reason but it worked.

Then I checked the Eureka-ROM thread to see what I could do with my new toy and not much apparently.

So how can I go back to stock ? Is it even possible ?

Thanks
[Google Chromecast] elborak:
That's not good news. The error on the simulated USB hub indicates that it's working as designed.
[Google Chromecast] Dabman:
Any idea how to root updated chromecast? (19084)

Can be even with hardware ingerention.
[Google Chromecast] by3times1minus1:
have you not read any part of this thread? 19084 is currently not rootable. this is why it's suggested to root straight out of the box without letting the CC connect to the net and autoupdate to the newest FW.
[Google Chromecast] youxiaojie:
fail to root...defeated by chromrcast.used as paperweight and wait new method.
[Google Chromecast] ghowse:
I don't know what you are waiting for. There will not be a new method for pre-19084 Chromecasts because the current method works perfectly well if you have the correct hardware and follow the simple steps.

If you have failed so far, most likely your problem is one or more of the following:

- you have let it get the OTA upgrade to 19084

- your powered OTG cable is not wired correctly

- your programmer board is not 100% compatible with the HubCap HEX files

- you are not explicitly following the steps outline on Page 1 of this thread

- you have not correctly transferred the firmware image to your USB stick
[Google Chromecast] youxiaojie:
I use teensy 2 board, changing usb disk after teensy 2 blinked,and click button on CC,the CC never read usb disk.the cracked firm will never be installed.
[Google Chromecast] cantenna:
FYI for Canadians trying to buy a Micro USB Host OTG Cable with Micro USB Power Importer520 is selling on Amazon.ca:

Importer520 Micro USB Host OTG Cable with Micro USB Power For Huawei Ascend Y M866 (U.S.Cellular)

*This retailer is sending out regular USB otg cable to fulfill orders for USB otg micro powered cables.

Beware! Check reviews before buying!
[Google Chromecast] jocarog:
Does the light on CC changes to white? You have to count 30 seconds after teensy starts blinking... then it'll stop blinking and go solid. Chrome cast light should go white, that's when you unplug the teensy and plug USB flash drive then press reset only once, do not hold... after that you should see the eureka team splash screen
[Google Chromecast] Mad07:
[MENTION=4778658]cantenna[/MENTION]

Where does you living? Germany?

If yes and your CC does not contain the latest unrootable FW, you can send me the CC by post ( plus cost of return),so I can root the CC for you if you like.
[Google Chromecast] ghowse:
If you want to send it to Australia, I will have a go at rooting for you with my system which has been 100% successful on 6 occasions. Just make sure you are not already OTA upgraded to 19084. You haven't mentioned that you checked this yet?
[Google Chromecast] youxiaojie:
no,my CC does not changed to white.

---------- Post added at 05:19 PM ---------- Previous post was at 05:04 PM ----------

I live in beijing, china.The official guide is using teensy 2 plus plus,which has the led change.another example,http://chromecast.wonderhowto.com/how-to/root-your-chromecast-0157253 used teensy 2,which has not led change.
[Google Chromecast] :
so there is now way to go back to stock ???
[Google Chromecast] tvall:
there are ways to go back to stock, and it can be done just as easily as flashing a flashcast mod if someone were to make one.

if i remember correctly, team eureka and the other devs are intentionally not doing so because it is irreversible (you can go from eureka to stock, but if you ever go back to stock, chances are that chromecast will never ever again see root or any awesome future mods of any kind, unless we get really really lucky and someone 2 years from now still cares about the chromecast and finds another hole), and the only downside to eureka rom over stock is a day to maybe a week lag in updates.

If you really really really REALLY want to never be able to root your chromecast again, someone on #teameureka irc might help.
[Google Chromecast] shaunhoop1981:
Thanks for quick reply I am now one happy man as missed my opportunity to root before thanks
[Google Chromecast] jumoog:
i have a AT90USB162 here from old PS3 projects ;)

can you compile it for me please?
[Google Chromecast] thenrz:
This is excellent! I just happen to have a few teensies laying around from modding ps3s. Now if only I could find my otg cable... :)

Thanks for the hard work! I'll be sure to post a screenie when I get the time to find my otg cable and get this process in action.
[Google Chromecast] sabret00the:
Thanks guys, gonna check this out.
[Google Chromecast] killer23d:
It would be a good idea to let the OP knows what you have since there are a few AT90USB162 devices out there. I have a BlackCat USB (FlashCat) and is looking into a way to port the hex file to it.

Of course, if GTVHacker can provide the source so that they can compile it would be great.
[Google Chromecast] Lizard:
I also thought about that, but you turn on the Chromecast with the reset button pressed to get into recovery (?) mode. After that the teensy will do it's magic. So it's not needed to turn off WLAN. If you want to be sure it won't hurt of course.
[Google Chromecast] dave7802:
Question.

I have all the cables an the teeny device.

My question is before I gather all my resources,

I have a OTG micro to USB

I also have a HDMI to micro USB

As Chromecast has one micro USB port.

How are you to connect power and teeny then USB storage?

Is a USB hub suficent? Or is a split on the OTG needed I.e. 2 ports one for power an one for USB device.

I don't have a OTG with two ports. But if its needed I could make one. Just a question in advance before I start.

Thanks for any advice
[Google Chromecast] ddggttff3:
you will need a powered OTG cable. As stated in the OP, a USB hub will NOT work with this exploit as the teensy needs to be directly connected to the chromecast
[Google Chromecast] neoskyriper:
sa ne fonctionne pas sur les chromecast 17250?
[Google Chromecast] jumoog:
you can compile for my AT90USB162 please?
[Google Chromecast] Sharkman707:
How can I get to the Team Eureka website like in the video to check if my CC is rooted? I followed all the steps and set it up on the TV and phone app. I just want to check that it is rooted.
[Google Chromecast] Luxferro:
Go to the IP address of your chromecast in your browser.
[Google Chromecast] Sharkman707:
Thank You
[Google Chromecast] nolook:
i just did it without a powered usb OTG cable but did use a usb y cable i got with a usb hard drive and it worked! ... used a usb female to female adapter too... thanks for this exploit OP
[Google Chromecast] II.J2G.II:
source code release

Anyone got an idea when the source code will be released, ? i don't think i want to buy a Teensy when i have 7 Minimus 32 AVR's sitting here doing jack :fingers-crossed:
[Google Chromecast] dave7802:
Same issue as you, Am guessing you got yours resolved, I just cannot get the Tennys board to do its "Stuff"

Am sure the Device is in its "Recovery" Mode as the LED is red and stays red, Nothing on the display.

Tried reflashing teeny about 20x

Even used the LED Blinker to confirm OTG is working correct.

(Works in phone too)

Just one of these nights where nothing works :p
[Google Chromecast] TamCore:
This post showed me what I was doing wrong. But now I'm stuck at the step where FlashCast should flash my ChromeCast. It's doing something (the ChromeCast gets very hot after some time), but shows nothing on the screen and isn't doing what it's supposed to do. Even when I reboot my ChromeCast manually after an hour, it's still the original ChromeCast ROM without root :(
[Google Chromecast] bhiga:
[MENTION=3397724]explorer-10[/MENTION] [MENTION=5390562]Bink Feed[/MENTION] [MENTION=4798472]YevOmega[/MENTION] and everyone else with the question...

See FAQ Part 2, 1.d

Side note: FAQ and related threads have been updated. Thanks guys!!

Yeah, a standard OTG should work if you inject power via an appropriate Y-cable

that does not have embedded logic

(ie, not a hub, no matter how stupid the hub is).
[Google Chromecast] killer23d:
I will try this Y-cable that I made for the HTC:

http://xdaforums.com/showthread.php?t=1828032
[Google Chromecast] YevOmega:
I still don't see the full picture. So it lets you use apps not approved by Google for use on Chromecast, but which apps? Doesn't Cast have to be integrated into an app for one to be able to cast to the Chromecast? Consequently, wouldn't only approved apps have the functionality?

TL;DR - Does Eureka allow more options for streaming local files?

---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------

So this can only be done with a Teensy? Are there any ways to get this to work using an Arduino Mega 2560 instead?
[Google Chromecast] :
Ill keep the Eureka-Rom then, thank you for all the informations !
[Google Chromecast] cantenna:
Thanks for the offer. I actually rooted my chrome cast build15908 last night using the 16xxx.hex plus plus file. :)

Why do you say non-rootable? Is the latest CC update patched to prevent teensy root? I saw some posts about it.

I live in Canada, eh?

Also, had to create my own otg powered cable

---------- Post added at 03:06 PM ---------- Previous post was at 03:04 PM ----------

Thanks guys and Eurkea team for sharing your exploit and knowledge.

Anyone do anything really outside the box yet with there rooted chrome cast? What about uploading a hosts.txt file dump from adaway?
[Google Chromecast] Mad07:
with the last OTA update from Google ( build 19084) there is in this moment no known way to get a root access ( from that what I've read till now).

That's the reason, that the CC should not see any byte from the Internet, before the CC is rooted and contains the Eureka Rom ;)

Yes, this file was working on my side too, with the same Stock FW
[Google Chromecast] cantenna:
Wow, guess I got lucky! I'll probably buy another chrome cast and root it while I still can then.
[Google Chromecast] yaw hide:
I just bought a Chromecast with serial number 41....

Is it possible to root?

I dont want to buy any extras incase my chromecast is screwed...

Thanks!
[Google Chromecast] ghowse:
Probably, but the only positive check is to set it up (WITH INTERNET DISABLED!!) and check the version. If it is pre-19084, it is rootable. If you check with internet enabled, it will immediately get an OTA upgrade and block the ability to root.
[Google Chromecast] cantenna:
I just bought another and rooted it!
[Google Chromecast] jocarog:
OK somehow I got a 19084 firmware rooted, I got it thru Groupon and it was a refurbished device, I have used a teensy 2++ and the 16+++ hex file... if there is any logs I can send you let me know
[Google Chromecast] jocarog:
Proof:
[Google Chromecast] theronkinator:
No you didn't, just the Team Eureka rom your chromecast updates to once rooted is that version.
[Google Chromecast] jocarog:
Ah! Don't want to mislead people then, but that's the version that it came with... but I didn't get a screen shot before... thanks for the clarification...
[Google Chromecast] ghowse:
Well if that's the case, Team Eureka would be very interested in talking to you.
[Google Chromecast] ghowse:
Dear Team Eureka developers

Reports just coming through in Australia http://forums.whirlpool.net.au/forum-replies.cfm?t=2287174&p=54&u=52420 that ver 22062 update is out. One user on stock 22062 is reporting that the update has broken Netflix (ie geoblocked). No details at this stage. Could be just his router setup.
[Google Chromecast] elborak:
Wouldn't it make more sense to post this in a Eureka thread rather than a root thread?
[Google Chromecast] ghowse:
OK, I will.