yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] Kurre:
From the OP:

That really should give you a hint ;) go through the loader tutorials and you'll learn how to use that software..after that you should be able to continue..and it'll only take few minutes to read and test it. Instructions (in the OP) even say which file to use etc.

Sent from my Nexus 4
[Google Chromecast] samteeee:
Thank you for your reply.

Do I need the "LED Blink" or just the "Teensy Loader" for flashing the Root package?

Thank you.
[Google Chromecast] neoskyriper:
help me please

there's there a people who know the French for help me thank you
[Google Chromecast] samteeee:
At step 2, I connect the Teensy 2.0 after flashing the root package, and connect the CC while holding the restart button to powered OTG, Teensy start flashing orange and CC solid red. But after 30 second or more the Teensy stops flashing! and CC with button still holding remains red!

Did I do something wrong? Maybe didn't flash the root package correctly?!

any input is much appreciated.

A big Thank You to all the Devs and behind the seen guys and fellow forumers that always help each other.

Just got my Brand new CC Canada Version ROOTED.

The Serial Number starts: 4107*************
[Google Chromecast] P00r:
You do not need to hold the button, only press it to start the process, I believe you are resetting it...

Just did it, using a teensy 2.0, everything worked almost from the start, had more issue playing with cable to get a working USB powered cable than with the actual hack, this is ome of the nicest hack I have seen, truly work of art :)
[Google Chromecast] ClarkyCat:
Hi, yes I used the github code. You need to also download the LUFA framework. LUFA supports quite a few different boards: https://github.com/abcminiuser/lufa/tree/master/LUFA/Drivers/Board/AVR8. I had to add support for the A* LEDs - all these boards seem to have their LEDs on different pins.

I'm using Arch linux - the gcc cross-compiler and avrdude are standard packages.

Cheers,

Tim
[Google Chromecast] miniminus:
arr ok, so you added it in via some LUFA package rework...

all i can see for any referance is ""#define LEDS_LED1 (1 << 6)""

but cannot see how this relates to pin 26 ADC9(thats D6 on their diagram, but it seems that its actually digital line 12 ) on the teensy ...

https://www.pjrc.com/teensy/schematic.html

be nice to get it on pin18 (D3), or pin25 (D4)

http://arduino.cc/en/Hacking/PinMapping32u4
[Google Chromecast] webstas:
Not working all i get is a barcode on my tv,

i have a teensie2 programmed and plugged into my y cable and my chromecast plugged into my y cable then i hold down the chromecast button and plug in the power.

the chromecast light flashes white then goes dim red, then on the screen it shows a barcode.
[Google Chromecast] ddggttff3:
Your chromecast may have already been updated to the latest OTA which seems to have blocked the exploit.
[Google Chromecast] webstas:
NOOOOO!!!! Damn you Google.

Has anyone else seen the barcode of doom?
[Google Chromecast] samteeee:
GREETINGS:

Just wanted to tell you guys from Canada my "HubCap" Root experience with CC Canadian Version(Amazon.ca).

I ordered "Teensy 2.0" from Sparkfun Electronics in Sweden for $15.95 + $2.99 shipping, the lowest I found and took 10 days.

The CC obviously was Brand new in the package and never updated, S/N: 4107********. I proceeded to use the 12940 image

as per the OP to no avail ! Tried it for 3 times but resulted to no Root. So by chance tried the 16664 image and Boom the first try

on both steps went through fast and Rooted with no trouble.

Just thought if any Canadian trying to root a Canadian CC, might want to try this if they run in to any troubles.
[Google Chromecast] Asphyx:
I'm betting that the NIB method may work for older released Boxed models but perhaps a version has made it into stores which requires the 16XXX hex instead.

Anyone having issues should try both
[Google Chromecast] samteeee:
Agreed.
[Google Chromecast] XeKToReX:
I had to use the 16XXX hex on my BNIB CC in AU also.
[Google Chromecast] Roamin64:
I speak French. I will help you via private message.

Translation : Je vais t'aider par message privé.
[Google Chromecast] Srandista:
Did you already receive Teensy from AliExpress? I'm still waiting for it, so I want to know, if its just me, or if its same for you.
[Google Chromecast] miniminus:
right ok, im a bit new to this

BUT after a bit of reading about, I HAVE worked out how its selecting the Pins ..

it IS the line i said before ""#define LEDS_LED1 (1 << 6)"", which selects the PIN,

and then ""DDRB |= LEDS_ALL_LEDS"" ""PORTB |= LEDS_ALL_LEDS;"" for selecting port !

so that would be Port B6 or PB6 or phsyical pin 26

PLUS also found out that LUFA does already have support for the "Sparkfun ATMEGA8U2 breakout board"

which is set up for PORTB.4 ! which is its pin PB4, which would needs a LED adding to it ...

SOOO just need to complie it with that MCU selected and then physically add LED's in :)

or try and reconfigure it to use the already present RX, and TX LED's on my clone Sparkfun "Pro Micro board",

which is set up like a Leonardo with a RX and TX just not a 3rd led (which LUFA also has a setup for !)

so its just a case of now compiling some HEX's and trying :) !!!
[Google Chromecast] TRoN_1:
I am trying to get my chromecast rooted but I have a problem with my programmer. Not sure if this is the forum to get help for my problem, but here goes...

I have a board with an atmega32u4 chip on it. It came from an rc drone(says MiruPCB 1.8 on back). It has a red and a green led. When I plug it into usb port the red led stays on and the green flashes quickly and Device Manager says Teensy USB Serial(COM6) for a few seconds. Then the green led flashes 4 times,pause and repeats and in device manager it says USB Serial Port(COM5). I tried Teensy Loader 1.17 but cant program the board(says to press button to active). The board does not have a button. Not sure if that button on Teensy boards is a reset but I soldered a wire to the reset pad on this board and it resets when I ground it. Is this a bootloader problem or am I using the wrong software to program this board?

Thanks

TRoN
[Google Chromecast] miniminus:
red LED sounds like power LED, and the other one is probably RX or TX LED ...

its set up with a Teensy bootloader (thats why its popping up as such on initial plug in)

then the program onbaird kicks in and its running that ..

to get it into boot loader mode, and so you can program it, depends on the bootloader thats on it ...

you done the right thing with the reset button .. you may need to double tap so it stays in bootloader mode for longer

so you can then program the hex file .. you just have to be quick an get it when its in the bootloader mode ...

once programmed, the PC should see it as a "usb hub" or maybe just not recognised ....
[Google Chromecast] TRoN_1:
Thanks for the quick reply. What should I use to program the hex.? Can I over write the bootloader or erase the chip to factory settings?
[Google Chromecast] TRoN_1:
Ok, finally got this board to program. Its an Arduino micro. I loaded the blink sketch example with Arduino 1.05-r2 and changed the delay values a few times and the led flashes correctly. Now how can I load regular_16664.hex with Arduino 1.05-r2? Do I have to convert the hex to a sketch?
[Google Chromecast] miniminus:
ive been using xLoader which is a GUI front end for avrdude ...

http://russemotto.com/xloader/

you have to add Leonardo(32U4);atmega32U4;avr109;57600 in the devices.txt file

and you may have to update avrdude.exe, and .conf from from arduino ...

as listed in the comment on that link ...

im still having probs compiling the source, with more LED option .. just wont compile to a 'generic-usbhub' on PC

always "unkown device" and not working ! :( LEDs are working thou ! ....

im using winAVR package ... it finishes with no errors etc ..
[Google Chromecast] Caustic68:
I managed to load the regular 12940 hex onto my arduino Leonardo with Builder but now I'm unable to connect to the Leonardo anymore. When I plug it in it shows boot loader for a few seconds then its gone. Any help is much appreciated. Thanks
[Google Chromecast] miniminus:
thats "normal" should then show up as a "generic usb hub"
[Google Chromecast] TRoN_1:
I did what Maxwell2k did and it seems to have programmed correctly. Now to try rooting...but first to make that silly Y cable.

avrdude -p atmega32u4 -c avr109 -P COM6 -U flash:w:regular_16664.hex -v

You need to send that command right after resetting the atmega when it is in bootloader mode for a few seconds.
[Google Chromecast] miniminus:
thats basically what xLoader does, but in a GUI ! so a little more user friendly ..
[Google Chromecast] TRoN_1:
True. But xLoader failed no matter what I did. Maybe my timing was off. Thanks for the help.

Oh one more question, will the led on this board work like on the Teensy when rooting the CC?
[Google Chromecast] Caustic68:
Ok good to here but how do I flash the regular 16664 hex now? 12940 didn't work.
[Google Chromecast] XeKToReX:
Mine just had the power LED on the Pro Micro, no status,

You run the same command as you did to flash the 12940 hex after you reset it (bridge GND + RST) when it's in bootloader mode.
[Google Chromecast] lunico:
Hi is the CC still rootable or Google has already sent the upgrade to the CC kept online ?
[Google Chromecast] fattire:
Well FWIW just started up my CC after not having done so in a few days and it just upgraded to Firmware Version 19084. I had no plans to root this thing, but checked the last page or so and didn't see any mention of it. If you haven't rooted and plan to, I'm sure this update is going to close the hole, so don't do any updates..

Update: I stand corrected- a search of this thread for "19084" shows lots of references starting on the 4th of Sept and at least one report that it closed the hole. So there you go.
[Google Chromecast] uspino:
Stuck in firmware 16041 - Help!

I rooted my 2 other Chromecasts, but I had one more laying around for quite a while. I realized it's still on 16041 firmware. I can't root it with HubCap; tried both 12940 and 16664 files, before and after initial setup (with no Internet connection to avoid the latest 19084 upgrade).

Any help? Is there a way to upgrade my firmware from 16041 to 17977 so I can use HubCup? Thanks!
[Google Chromecast] TRoN_1:
I don't think you need to upgrade to 17977 to root it. I finally got my Arduido Micro board going yesterday only to find out my CC took the update. I was sure I unplugged it before the update. :( Let's hope another root method is discovered.
[Google Chromecast] Caustic68:
Thanks for the help everyone. I've had success. Turns out my biggest problem was my home made cable and getting everything plugged into the proper place. Next question, is there a way to get the Leonardo back to being detected properly and not as a USB hub? I'd like to be able to flash with the arduino IDE and not just when in boot loader mode.
[Google Chromecast] Max|XDA:
The Bootloader is also used with the Arduino software to load a sketch, the only thing you did was load the CC hack in stead of the normal sketches and nothing else changed.

Just use the Arduino software to load a sketch (e.g.Blinky) and it will behave like the sketch (Blink)
[Google Chromecast] Caustic68:
The catch is, after flashing the CC hack, it becomes unavailable to the Arduino software. What I had to do is flash the test program blink in CLI in the few seconds after restarting it. It then becomes visible with a com port again.
[Google Chromecast] fs1023:
Deleted. It was a bit OTT, have had a bad day. Sorry if I offended anyone who has previously helped.
[Google Chromecast] miniminus:
in your opinion, plus why did you feel the need to attempt the root, and then flood the forum !! ? you knew all the costings at the start !
[Google Chromecast] neoskyriper:
merci beaucoup
[Google Chromecast] Max|XDA:
The auto reset probably wouldn't work but resetting the Arduino after the compile part is over should have worked.

Thanks for letting me know:)
[Google Chromecast] cyablo:
I flashed the 16664 Hex File from nivramdu94 with DFU-Programmer to my Arduino UNO R3, did a reset but the Arduino does not show up as a Generic USB-Hub so exploiting the CC does also not work. The Arduino COM Port is also gone then, so something did happen. It dont know what is wrong, i tried mutliple times. Flashing with DFU seemed to wirk fine:

I also tried Arduino Builder Software which seems to do nothing because the R3 behaves like with the Original Firmware.

Edit: Also tried Amtel Flip Software for flashing wich run trough fine, but no Generic USB Hub. Looks like the HEX files do not work.

Edit 2: I did compile the Source by myself to proofcheck, it compiled withouth Errors. My Hex has a different Checksum but also does not work. So there has to be something with the Code itself but im not experienced enough for this :(
[Google Chromecast] VillainDivine:
Hey guys. So i have already rooted my chromecast but i am getting a " oops, we are having issues updating your chromecast to the latest version. Some featurea may not work."

Why would it say this if i am rooted? Im able to access the team eureka web panel uaing my ip address. I though this rom prohibited google from trying to update my chromecast?

Any help would be greatly appreciated.
[Google Chromecast] miniminus:
im just glad it IS stopping the update !!!

a silly message is of no concern to me :) (at present!)
[Google Chromecast] freddy0872:
Wondering about this message as well.

Chromecast App keeps telling me the chromecast needs setup. Will keep my eye on it as time goes on
[Google Chromecast] TRoN_1:
I got my hands on a new CC with 15098 firmware. I tried many times but no success. The board I have is an Arduino Micro(clone maybe). When I plug it into PC, it goes to bootloader mode for about 6 seconds(green led flashes then stops) then executes whatever hex was uploaded(tried blink test and worked fine). So when I flash with regular_16664.hex and plug it into powered usb Y cable to attempt root, it first goes into bootloader mode. Could that be the reason my cc won't root(cc led stays red forever)?
[Google Chromecast] bhiga:
Are you sure you're using the correct hex files? There are different ones for Teensy 2.0 and 2.0++
[Google Chromecast] ghowse:
My guess is that we will keep getting that message until Eureka 19084 is rolled out. As far as I can see it has no effect on my CC. Everything still working fine.
[Google Chromecast] ddggttff3:
The message should be removed now. For more info, refer to the ROM thread.
[Google Chromecast] TRoN_1:
Is it normal for my Adruino Micro(clone I believe) to reset every time I connect my cc for rooting? The same thing happens when I connect it to my PC, goes to bootloader mode for 6 seconds then runs what's in memory.
[Google Chromecast] lunico:
Hi my CC try to update the 17977 build and I still didn't receive the cable....! Do you think the next build will prevent from rooting? Do I need to stop the Google auto update?
[Google Chromecast] Asphyx:
We KNOW the next update you will get will prevent Rooting so you had better unplug it until your cabe gets there and before you power it up again make sure to disconnect the Internet from your router until you have completed the rooting and are sure you have Eureka installed and running because if the CCast has any connection to the Internet you could get updated and lose the ability to root.
[Google Chromecast] miniminus:
yes when initially powering up the Arduino is goes through the bootloader mode, then after that runs the programmed code ...

the newer type, like pro micros (mine etc) have a much shorter bootloder section (750ms)

and to get these into a bootloder mode for longer to program then you rest them twice quickly.. that then puts it into a "normal" bootloader mode for 6-8 seconds ..

me... i STILL cannot get LUFA to compile properly with WinAVR :(

will compile with no errors, new LED settings work, but the USB side of it dont :(

(when plugging into pc again, its unrecognised, and not a genric usb hub !)

so summit int compiling properly

which LUFA build did you use ? im using lufa-LUFA-140302 ...

what else could be effecting the USB section of compiling ??
[Google Chromecast] ClarkyCat:
Yes, that was the version I used.

Did you add your new board to Board.h and LEDs.h?

I'm not sure you need to compile LUFA itself, you just reference it and the board you added in the HubCap makefile.

Tim
[Google Chromecast] TRoN_1:
When I connect my cc while holding the button to the Y cable for rooting, the Arduino resets and goes into bootloader mode for about 6 seconds. I am wondering if that is the reason the cc led stays red and doesn't update. Sometimes if I release the cc button after attaching to cable, it goes red for a few seconds then flashes white. I know the cable is an otg and verified by using it on my Galaxy S4.
[Google Chromecast] TRoN_1:
Finally! It seems that using a different dev board requires different prodedure and timing. With my board, there was NO WAY root would work with the original procedure described. I flashed mine with astar32u4_16664.hex and the green led flashed correctly when I finally got it going. The steps I took however were quite different.
[Google Chromecast] Asphyx:
Perhaps making a Hubcap for Arduino thread with proper instructions for those boards would be a good idea?

This way those who are trying to use those boards might not get confused with what is expected on a Teensy but may not happen on an arduino?

Not that I mind you posting in this thread, Just thinking those trying this differently might be better served with their own thread and procedure list.

Just to keep the confusion level down.
[Google Chromecast] Nitrogenus:
UPDATE

I finally received everything I needed, and now my CC is rooted and working flawlessly.

Thanks again!
[Google Chromecast] miniminus:
yes added to both .h files, and adjusted makefile accordingly ..

i even set up and complied for the already set up boards, teensy, and Lenardo...

both act the same ... (using the original teensy file from hubcap, puts my board into USB hub, so i know its not my board)

i cannot even re-create the original properly :(

so if its not my LUFA reference library version, must be my compiler ...

im tryng with WinAVR ....

yes the 6 second bootloader delay, is bootloader specific....

but you say you have got it going now anyhows ? ..
[Google Chromecast] Roamin64:
I've finally managed to root my canadian CC 42XX using a atmega32u4 chip flashed with teensy 2 16667. I am using a homemade frankencable and was having issues with the CC not turning white, and since my atmega32u4 was on a arduino pro micro board that i've flashed using ISP it didn't have a proper LED to output status. It turns out that my cable was not built properly because the power connector should not have the data lines connected. Once disconnected the CC turned white on every try. I then had to use 2 flash drives because the first one just didn't work and I had no TV output. The 2nd one showed the rooting screen and all went smooth afterwards.

Thanks to all involved!

neoskyriper (the user that doesn't speak much english) has the following problem that his teensy 2++ will blink and all , but will never turn white. Since my board didn't have LEDs , I cannot know for sure if the atmega would flash its LED if the OTG cable is not correct, but maybe his cable is not good and that's why its not turning white even though it flashes. Any ideas for his case?
[Google Chromecast] Asphyx:
Teensy LED never turns white...But the one on the CCast does...

When the teensy stops blinking then just replace the teensy with the USB drive you created using the hubcap-flashcast.bin and press the button on the CCast
[Google Chromecast] Roamin64:
Ooops I did mean that his CC doesn'T turn white after the teensy blinking. not the teensy LED.
[Google Chromecast] corp769:
I have a 3910 device with firmware 13300 on it, it was updated once about a year or so ago, and haven't had it on-line since. I have tried both the 12940 and 16664 images, both from source and the download, to no available on the teensy 2. The LED on the chromecast stays red at all times, no matter what when trying to perform the root on the device, and I end up staring at a black screen on my monitor the whole time.

Here is a boot log reflecting the same output from both images - http://pastebin.com/q5VGX5C6

I have tried a total of four USB flash devices, as well as two OTG cables, one from amazon and the other home-made. All connections have been verified in the cables multiple times with my multimeter, and I have double checked the partitions created when using dd to flash the USB devices. Everything looks good, yet the chromecast fails to boot after I unplug the teensy, swap it, and press the reset button (nothing happens when pressed). I have tried unplugging the chromecast and holding reset, then reapplying power, and you will see in the boot log where it started to read the USB device and failed.

Has anyone else experienced this?
[Google Chromecast] TRoN_1:
The way I made sure my home made OTG cable was good was to connect a mouse and usb flash drive to my Galaxy S4. Both functioned correctly so the cable was good. As for rooting my CC, I tried and tried with the posted instructions but it would not work. What I finally did...

1- connect the CC to tv(new CC with 15098 firmware). Disabled wifi just to be sure.

2- connect the Y otg cable to CC and arduino micro(flashed with astar32u4_16664.hex so the led would function correctly)

3- hold CC button and apply power to the Y cable(which of course powers the arduino and CC)

when arduino powers up it goes to bootloader mode for 6 seconds(green led flashes) then green led stays on(no activity).

4- release CC button just before CC led goes from white to red(you may have to adjust this timing). If held too long, the CC led turns red and stays like that forever and the arduino led stays green(no activity). After releasing CC button the CC led goes red a few seconds, then flashes white for an instant, then red a few secs. then white for 3 or 4 seconds then repeats this sequence(no image on tv).

5- Upon seeing this flashing led sequence I hit the CC button for maybe a second and something magical happened. For the first time after many many attempts, the arduino green led began to flash(not at all like bootloader mode). The CC led went red and stayed red, then after 20 seconds or so it turned white and stayed on. I believe at that point I saw the Eureka message on the tv(or maybe just after the usb drive was connected). I quickly unplugged the arduino and inserted my 8GB usb drive(which was formatted with hubcap bin) and the usb led began to flash!! After the firmware update was complete the CC rebooted. At this point you should remove the usb flash or it will re flash on reboot.

I now have a rooted CC. I will reconnect it to my tv and it will stay there collecting dust for another few months.

Hope this helps someone.
[Google Chromecast] JesusFreak316:
I can confirm it works with an Arduino Leonardo using xLoader to flash the regular_1664.hex and following the standard instructions. The lights didn't flash correctly but it all still worked.
[Google Chromecast] ghowse:
All back to normal now. I'm seeing Build No 19084.001

Thanks again.
[Google Chromecast] waiters:
Is there any way to go back to 100% stock after rooting and installing eureka rom?
[Google Chromecast] rbeavers:
Does the teensy led light up ? One of my mini USB cables would not work, with the OTG cable.

---------- Post added at 09:29 AM ---------- Previous post was at 09:27 AM ----------

"Should be if needed." A few post back.
[Google Chromecast] fldc:
Nah, tried to compile and run the code on a couple of different R3:s here also without any success, no usb connection what so ever. :)
[Google Chromecast] brusarp:
Yeah, good! Can you explain step-by-step your procedure? (What means that the lights didn't flash correctly? How do you check the correct timings?...) Thank you!