yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] corp769:
Whoops, forgot to mention that. The teensy lights up as it should when it is plugged in, and all cables are verified as working. It blinks slow, then fast, and when I press the chromecast button after plugging in my USB device, it stops spewing out messages in my screen output. According to the output, this happens:

Can this be verified as normal operation? I haven't gotten around to looking through the source code yet, tonight I will most likely compile from scratch and have a go at this again.
[Google Chromecast] JesusFreak316:
Sure. The most annoying part was managing to get the Leonardo flashed.

I used http://russemotto.com/xloader/

As one of the comments says:

This is a nice little program! I especially like that you’ve included the arguments to avrdude in the .txt file, which lets you expand it later without needing to rewrite it.
Here are a couple of tips for those commenting:
1. There is a “devices.txt” file in the program’s working directory. This text file contains the names of the boards, the processor types, the bootloader protocol, and the baud rate for programming.
Example: Uno(ATmega328);m328p;stk500;57600;
To program an Arduino Leonardo, you need to do some extra work. Add the following line to devices.txt:
Leonardo(32U4);atmega32U4;avr109;57600
Then replace avrdude.exe and avrdude.conf with the ones from the latest Arduino IDE.
You’ll also need to change any instances of “stk500″ in devices.txt to “stk500v1,” and you’ll need to put the Leonardo in bootloader mode before starting the upload. You can do this pretty easily by toggling the reset line low (just press the button!) on the Leo before uploading.
Perhaps in a future version, the author can add in the Leonardo trick – open the COM port at 1200 baud and then close it again. That resets the AVR and puts it bootloader mode for 8 seconds.

The replacement files are in the Arduino software directory. Just search for them. I also zipped up my XLoader folder for convenience.

Once you have your Leonardo connected and all the drivers installed, you should have two com ports. One is for normal use, and the other is for the bootloader. Press the reset button on the Leonardo and flash the hex file with XLoader.

Once you have that, it's just a matter of trying to follow the steps in the video repeatedly until it works. I didn't change anything.
[Google Chromecast] KenMacD:
Did an install using a pro micro board and it worked fine. The LEDs on the board didn't activate, but everything still worked.

The command I used in Linux to write the image to the board was:

avrdude -v -v -v -v -patmega32u4 -cavr109 -P/dev/ttyACM0 -b57600 -D -Uflash:w:`pwd`/regular_16664.hex:i

The board doesn't have a reset button. I think you can get it in programming mode by opening the serial port at 9600, but it was easier to just short the reset and ground pins (RST+GND) twice with a screwdriver. (Google "SparkFun Pro Micro Hardware Overview" for more info).
[Google Chromecast] brusarp:
Thank you very much! When I can get some free time I'll surely try it. Thank you again!
[Google Chromecast] tapan15in:
Can I root my cc which is currently on 19084??
[Google Chromecast] fkrone:
This is not possible at the moment. HubCap is fixed with 19084 and no other root method is available at the moment.
[Google Chromecast] tapan15in:
[MENTION=4110873]fkrone[/MENTION] thanks bro. I am new to this device rooting process. So I guess I need to wait when they release another tooth method for this firmware.
[Google Chromecast] Srandista:
Or buy a new one, and root it straight away, before connecting to internet ;)
[Google Chromecast] akarol:
Is it normal for both of my CCs to say UPDATE AVAILABLE on the Eureka IP site?
[Google Chromecast] Asphyx:
yes just give it time the Updates happen on a rollout over the course of a couple of days.
[Google Chromecast] BlueCop:
You can also force the update.

http://xdaforums.com/showpost.php?p=55427554&postcount=2
[Google Chromecast] idone:
Great work [MENTION=1007992]everyone[/MENTION] involved. Worked first try from pro micro atmega32u4 fed by 4.5v from switching power supply (cc wasn't even plugged into tv). ota updated itself within minutes of powering it up, everything went off without a hitch.

Thanks again!
[Google Chromecast] kaoss_11:
just rooted 2 of my chromecast. very simple and easy process. bought another chromecast from bestbuy yesterday
[Google Chromecast] ghowse:
It would be interesting to know when people are starting to get new-in-box 19084 builds. I would assume there would be months of rootable CCs still in the supply chain.
[Google Chromecast] FirmShark:
Still having issues with this. Tried all sorts but it isn't working. Can someone please shed some light for me? I'll even pay you for your help!

Anyone able to shed any light? I think it might be that my 42xx serial number can't be done even though it is on 17977. The OTG has been verified as working as I can use it on my Nexus 5.
[Google Chromecast] TRoN_1:
The CC I rooted was a 42xx on firmware 15098. Try my procedure(post #519). I tried every which way and that stupid CC led would stay red forever(after 15 minutes or so, that's forever!).
[Google Chromecast] FirmShark:
Been trying that for the past 2 hours since you posted and still not got anywhere. I have tried different combinations of presses on the reset button as well. Beginning to think either my Teensy2++ is faulty or the CC just can't be rooted even though I've had it off the network for 3 months now waiting on this exploit :/
[Google Chromecast] Max|XDA:
Have you tried both of the plusplus rom versions?

(i would try with the newer one)

What happens in Windows device manager if you connect the Teensy2++ to your computers usb port?, does it show an "unknown device" or a "hub"?

Is this a Teensy that you ordered for this?

(maby a bad fake?), whats on the chip)
[Google Chromecast] FirmShark:
Tried both plusplus versions. The teensy2++ displays as a USB input device. Its a genuine teensy from hobbytronics (uk supplier for pjrc).
[Google Chromecast] Battletux:
Any ideas why Netflix has suddenly stopped working? Was fine for about 3 fays after I rooted but now gives an error.
[Google Chromecast] fkrone:
Maybe your Chromecast is still on Eureka-ROM Build 17977.001. Netflix changed some things so the new build 19084.001 is required for Netflix. You either wait till the update is available to your device (OTAs for Eureka-ROM are rolled out in stages) or flash the new build manually via FlashCast.
[Google Chromecast] Battletux:
Awesome, thank you.
[Google Chromecast] KenMacD:
[MENTION=3006041]FirmShark[/MENTION]: Do you have a Linux machine you can plug the teensy in to? If so plug it in and check dmesg. You should see a whole pile of USB messages and the error "hub has too many ports". This will verify that the teensy is doing what it should.
[Google Chromecast] FirmShark:
I'll check this when I am home later! Thanks.
[Google Chromecast] Battletux:
This was exactly the issue. A quick reflash and it's all working again. Thanks for the quick response.
[Google Chromecast] ghowse:
Just checking .... hope this is not a dumb question: After flashing Eureka ROM, what does factory reset from the Eureka menu actually do? I'm assuming it does not wipe Eureka and somehow reinstate the stock CC firmware? I'm 99.9% sure that all it would do is wipe the wifi credentials and set other options to Eureka defaults .... but I'm just checking to be sure.

Thanks
[Google Chromecast] jamesking420:
You're correct, it will not reinstate stock firmware. It will do what you said :)
[Google Chromecast] ghowse:
Thanks, that's great. I rooted and factory reset a CC for a fellow in another city and was concerned that it would arrive back to him in the same condition as it was when he sent it to me. Now I'm relieved and he will be pleased. Thanks again.
[Google Chromecast] FirmShark:
Just checked this just now. I am getting the error "hub has too many ports". Is there anything else I can check?
[Google Chromecast] ClearD:
Gonna say it's working. That's how the exploit works, USB hub port overflow.
[Google Chromecast] mcbyte_it:
THANKS GUYS... YOU ARE #1 :)

just followed the steps with an Arduino Leonard Pro Micro, a powered OTG, and my chromecast (17977), and it worked from the first time. Rebooted, and it even updated to latest 19084 by Eureka...
[Google Chromecast] moesus:
Please delete.
[Google Chromecast] FirmShark:
I am aware of this. This was just checking to see that the Teensy was actually doing its job. So it is looking more than likely that my CC doesn't want to do anything with it. Re-confirmed that the CC is on the correct firmware. The OTG cable is definitely working as it should as I use it everyday for my Nexus 5.
[Google Chromecast] KenMacD:
Sorry [MENTION=3006041]FirmShark[/MENTION], that was my big idea. It looks like the teensy is acting like it should so I'm at a loss as to why it's not working for you. You're using the same micro-usb to usb cable (if you need one with your OTG) that you tested with? You probably are, but you're following the order correctly? The video shows plugging in the chromecast first (but them removes it). The chromecast has to be plugged in last.
[Google Chromecast] FirmShark:
Yeah the same cables and even tried different cables.

I've tried all variations of the orders of plugging things in that people have tried. I think it might be the CC that doesn't want to root at all. Tried holding the button for different lengths of time, re-pressing it at key points. It always either stays in boot loader mode (constant red light) or it boots to the setup page. Verified this by leaving it plugged into my TV.

Almost tempted to just re-enable the CC and leave it as it is.
[Google Chromecast] whitepaw:
Having the exact same issue. Teensy 2.0 not a single flash of the LED on the teensy and the chromecast either boots or goes to constant red light. I tried unplugging and replugging with different intervals of pressing the CC Resetbutton without any success. It will just not starting the process. When testing the OTG Cable on my s5 everything works fine so it's not the cable.
[Google Chromecast] bhiga:
That's correct. Factory reset just wipes the settings. It doesn't touch the ROM.

Just to be sure here, the last thing you're doing is connecting power to the entire rig,

while

holding the button down on Chromecast, right? Once power is connected and you see light on Chromecast, you should release the button.

If the button is not down when power is connected, Chromecast will boot normally.

If the button is down after power is connected, Chromecast will eventually go into reset mode.

You need it to go into bootloader mode, with button held down at application of power.
[Google Chromecast] whitepaw:
I did that. But I just found out what my problem seems to be. Chromecast must have updated itself to the latest Version 19084 which according to a posts here does not work anymore.

To bad, but thanks anyway!
[Google Chromecast] FirmShark:
Yeah the CC is def in bootloader mode.
[Google Chromecast] pwvandeursen:
Since the new vesion can no longer be rooted, how do I check what sw the CC has without having it update to the new version.

i.e. I want to buy a couple more through our local ebay in the Netherlands, but need to know which version they have before I buy it. At home I can just turn of internet and link to the CC and check with the app, but not everybody will be able or will be willing to do that before selling

thanks
[Google Chromecast] Srandista:
Unfortunately, checking in Chromecast app on WiFi with disconnected internet is only option to check version without update. Otherwise, you just have to buy new, sealed device.
[Google Chromecast] pwvandeursen:
do we know what serial numbers are the last to definitely be the correct version (for if we are buying boxed units?)
[Google Chromecast] Asphyx:
Serial number is no longer relevant to rooting only what version of the OS you have!

But you do need a Powered OTG cable and teensy 2.0 or Arduino board to get root and that means you can't use the CCast or connect it to the internet in any way or it will update and you will lose the chance to root!
[Google Chromecast] pwvandeursen:
Yes I have the HW and already rooted a couple. Just trying to get clear which units I should or should not buy. So I also understand it is related to the OS version. however Google will start to roll out units with the latest version already installed. from what serial number will that be? i.e. which versions will be unrootable, even if they are unboxed, or will they always remain rootable? I don't think that will be the case right.
[Google Chromecast] Asphyx:
No one can say until they actually start shipping with the 19xxx OS

But I bet it will be awhile (at least until X-Mas) before they sell out enough to come across one.

They sure aren't going to pull them off the shelves just to stop rooting.
[Google Chromecast] theronkinator:
My Pro Micro finally arrived, rooted perfectly using the regular Teensy files, had an issue with the first memory stick (instantly said start up issues when I clicked the CC's button), but second one worked fine.
[Google Chromecast] diggmc:
Just a quick note to say Thank You to the entire Eureka-Team for the hard work and dedication to improving the CC's functionality!

I've been waiting weeks now for a USB-Y cable to show up from Ebay. After re-watching the demo video, I successfully rooted my CC (S#: 3701xx) in just a few minutes.
[Google Chromecast] Restorer:
The OTA update duly arrived yesterday on my newly rooted CC. Big thanks again to the Eureka team and everything you are doing :good:.
[Google Chromecast] pwvandeursen:
one last question regarding the newest SW version by google. anybody know when that version the 19xxx was pushed out bu google? i.e. any units disconnected before that date should still be useable right?
[Google Chromecast] whitepaw:
According to Google that was around the 4th of September.

https://productforums.google.com/d/msg/chromecast/FOIWpJydK9Y/Unq4IPCZLTkJ

Every CC which was disconnected since then should be fine.
[Google Chromecast] Srandista:
Accordind to this thread it was released at September 4th.
[Google Chromecast] luchtgitaar:
n00b is n00b

Oke guys,

I've been Googling for an hour, but I am not getting anywhere and I'm such a noob I don't even know if it's possible with my setup. I only have a cheap Arduino Pro Micro (http://www.ebay.nl/itm/310634777706?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649).

Is it even possible to write the hex to that board via USB? I just can't get the board reconized in Arduino Builder. Is it possible (I have no idea what COM ports are for example) and can someone post a quick tutorial if its possible.

Edit: Damn. I even didn't install the drivers. I will look into it further.
[Google Chromecast] reiteravi:
searched but couldnt find

ran the root process with red led all along

when rebooted i could see the eureka page from browser

no other sign if rooted though

as it was not like in first post how can u tell ?

if i ssh i get the root prompt (#)

am i safe ?

should i let it get online ?
[Google Chromecast] Asphyx:
Reboot it (power down and up) and watch the screen...You should see a team Eureka logo on bootup.

I suspect if you get SSH and webpage you are rooted and safe to connect but double check just to be sure.
[Google Chromecast] reiteravi:
i do see eureka logo so i'll let it go online

i'll keep my second one safe 4 now though

thanks
[Google Chromecast] Luxferro:
Don;t keep holding down the chromecast button (if you are). let go when you see the teensy doing stuff. I had the same result as you when I held it down the whole time. Worked when I let go soon as the teensy LED was doing stuff.
[Google Chromecast] TamCore:
Now I'm getting a white led on the ChromeCast, but when I continue with the next step, the only thing my ChromeCast does is changing it's led color from white to red. But besides this, there are no signs of activity. Not even something on the screen.
[Google Chromecast] captaintrip:
Great news, thanks a lot :)

Do you plan to release the sources?

I would also like to use my arduino.uno ..
[Google Chromecast] The-Kevster:
Don't think it will port to the UNO due to lack of USB support. It will need to be a ATmega32u4 based board such as the Leonardo or Pro Micro which can be found on ebay.

Porting it to the Teensy 3/3.1 would also be useful.
[Google Chromecast] abuttino:
How long will this last? Think Google can get it patched in the next update?
[Google Chromecast] captaintrip:
At least the arduino UNO smd rev 3 in front of me has an ATmega16U2, which should work fine because on 32U2 the whole flash isn't used.

Correct me if i'm wrong...
[Google Chromecast] JayDee78:
It´s been said that google will likely patch this within days and push out an update...
[Google Chromecast] Luxferro:
I didn't have mine hooked to a screen, so not sure. But it did take a little bit before it rebooted itself and had a white led at that point. Let it do its thing for 5-10minutes
[Google Chromecast] TamCore:
It's "doing" it's thing now for more than 30 minutes. I don't expect that there'll be a positive result in the next hour :x
[Google Chromecast] YevOmega:
Hey all. What can we do with a rooted Chromecast that we can't do anyway?
[Google Chromecast] Luxferro:
Yeah, that doesn't sound good. Maybe try a different USB flash drive if your Chromecast ends up okay.
[Google Chromecast] ClearD:
For all those asking what it can do that an unrooted one can't, please use search. This question has been answered in other threads in the Chromecast subforum over and over and over. Check the eureka rom thread, as that's the primary rom, for what benefits it adds to the unit.
[Google Chromecast] brizey:
Board is ordered and chromecast is unplugged.

While I am working on rooting it, I guess the best thing to do is to turn off my WLAN until I get a custom ROM with the OTA updater removed? (Or I guess, turn off internet access completely?) Figure Google will patch this pretty quickly.
[Google Chromecast] TamCore:
Already tried a few different usb sticks. Same result. Even after a dozen of tries my ChromeCast is booting it's unrooted firmware without any problems.
[Google Chromecast] Bronto9:
According to the data sheet(http://www.atmel.com/Images/7799S.pdf) the atmega 16u2 has half the flash memory, SDRAM and EEPROM compared to the 32u2, so it might not be possible.

For now I've waiting for the source code release to see if someone can find a way to make it working on the Uno, otherwise I'll buy a teensy.

EDIT: the file for the teensy is 24 KB big, so it doesn't fit the 16u2 16 KB memory(as far as I can tell, I'm not an expert about those things).
[Google Chromecast] captaintrip:
24 KB in HEX format - this includes checksums, addresses and so on... so i guess the flashsize would not be the problem
[Google Chromecast] X3r0X:
I have an arduino with Atmega32U4 and a teensy with AT90USB162.

Would it work if I flash the hex file to the arduino?

Greetz
[Google Chromecast] ceckin:
It requires 8 740 bytes or 9K, so it would fit on a 16K AVR, the problem might be the pins and as such you have to wait for a source and recompile for your board. OSC is also something important and as such if you don't have a Teensy - wait for the source.
[Google Chromecast] shaunhoop1981:
Right everything has flashed perfect on boot up I get the team eureka boot logo does my device also now have the team eureka ROM installed or do I need to now flash separately
[Google Chromecast] ddggttff3:
It now also has Eureka-ROM installed, so you should be good to go!
[Google Chromecast] Max|XDA:
At the Mediamarkt they are only €35,- and those are pretty much failsafe the older versions..
[Google Chromecast] FirmShark:
Just picked up a Arduino Micro today to see if it would work better than the Teensy2++ and I still have the same problem. I reckon the CC just doesn't want to be rooted :/
[Google Chromecast] OrBy:
I have everything on order to do this root but just checked my CC and it seems it got the update before I was able to reset it and put it offline. Is there any chance that HubCap may be updated in the future to include the newer 19xxx firmware or did they really close the hole and I may as well buy a new un-updated CC?
[Google Chromecast] Srandista:
Honestly, it took nearly a year to discover a new bug in CC, which could be used for rooting device. I'm certain, that they are trying to find a new bug, but it really can take forever to find one. I recomend you to buy a new one, and root it before initial setup.
[Google Chromecast] elborak:
I was able to use a Micro with no problem. You need to rebuild the hex file with the appropriate BOARD setting if you want the LEDs to flash, but otherwise the original hex file should work fine. Not sure where you're going wrong.
[Google Chromecast] FirmShark:
I'm not too bothered about a flashing LED.

I have even tried following the video to the letter. Had it playing on my n5 while I matched the same steps for the same lengths of time. Still no success.
[Google Chromecast] elborak:
The flashing LEDs are not important, unless you're trying to figure out why the process isn't working. Then it's great feedback to let you know you got the timing right on the Chromecast button. What revision is your Chromecast currently running?

You were able to get the Micro flashed successfully (and confirmed that it shows up as a hub with an error in WIndows)?
[Google Chromecast] FirmShark:
I am running 17977 firmware. The micro is verified as a usb hub and has been flashed with the correct file.
[Google Chromecast] elborak:
So you're past step 2:

1. Get all the needed hardware (compatible board & USB OTG cable with power).

2. Get it flashed correctly with the right version hex file.

3. Get the Chromecast to load the exploit payload.

4. Load Eureka to the Chromecast from your flash drive.

Here's a hex file compiled for the Leonardo/Micro, firmware >= 16664. Give this a try. It shouldn't magically make things work, but it should let you know that you've got the timing right for step 3. The only tricky part I noted was getting the timing right on when to release the CC button. Too early, and it goes to blinking white. For me, what worked was releasing it just after the CC turned red, but it took a few minutes of trial & error.
[Google Chromecast] Asphyx:
I think we might be in for a long wait before we see another root exploit....Unless some mistake creeps into a Google update.

The fact they have seemingly patched the hole that allowed the Teensy to work is going to make it hard to find a way to trigger any new exploit...

But this is XDA...Nothing is ever impossible with the folks who frequent here! LOL

That said I highly suggest anyone who wants root should take your advice and go buy a NIB model and root it before the Christmas Rush clears all the old stock from the shelves and 19XXX CCasts start showing up in the NIB Boxes!

It's only $35 USD so it's not like it is going to break your bank!
[Google Chromecast] FirmShark:
Re-flashed using your hex file. Still can't get it to do it. Tried again at releasing at different times. Even tried holding the button for short periods to long periods of time.
[Google Chromecast] brusarp:
:good: Yes!!! It works!

Made with the help of [MENTION=1970090]JesusFreak316[/MENTION] and all of [MENTION=5639408]Team-Eureka[/MENTION]

Info:

- Brand new Amazon CC with serial 4305 and original FW 15098

- Arduino Leonardo with modded xLoader (thanks again to [MENTION=1970090]JesusFreak316[/MENTION])

- self made OTG-Y powered cable

- 1 gb USB pen

- regular_16664.hex

- follow the Youtube demo while doing

- led on Arduino doesn't blink but is simplest to watch the CC's one!! ;)

Thanks again!