[Google Chromecast] Maxwell2k:
Wow, this REALLY was a pain in the ... but it works!

It finally worked here, too. Had the cables ready but no Teensy, just a lot of different Arduinos (UNO, Micro, Mega etc.),

so I was happy to see people seemed to have done it with the Aduino Pro Micro. But it just didn't work for me. AX Loader

just didn't want to upload the Hex file and Flip just didn't like to talk to my devices. UNO files were a fail for me too, I even

burned the hex files directly with a ISP, to no avail.

I got it finally working on the Arduino Pro Micro with a combination of some posts here.

My way: Burn the hex with avrdude like [MENTION=264349]richuk[/MENTION] did, just with the original Teensy files (the regular ones).

What I did:

- Get the Arduino IDE and install. Make sure your Arduino Pro Micro gets detected properly in Device Manager

- Get AX Loader and extract to a folder of your choice, like C:\AX Loader

- Put one of the regular Teensy files in that directory based on the firmware your CC has, mine needed "regular_16664.hex"

- Open a command prompt and CD to that directory like: cd "C:\AX Loader"

- Now you need to know the Com Port your Micro uses when you reset it. The Micro uses as Comport for some seconds called

"Leonardo Bootloader" on reset, after that it will be redetected by your system as a normal Micro with a different port number.

This is important! Mine had "23" when it is idle with its sketch loaded and "24" when I reset it.

- So my command line to burn the hex was:

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

- With COM24 being replaced by the comport YOUR Micro uses and the right Teensy filename when you reset it.

- Here comes the catch: You need to send that command line right after you reset your Micro (just short RST and GND Pins),

when it sits in "Bootloader" state.

- If you do it right, you should see something like this on your command line output.

Programmer Type : butterfly
Description : Atmel AppNote AVR109 Boot Loader

Connecting to programmer: .
Found programmer: Id = "CATERIN"; type = S
Software Version = 1.0; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=128 bytes.

Programmer supports the following devices:
Device code: 0x44

avrdude: devcode selected: 0x44
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9587
avrdude: safemode: lfuse reads as FF
avrdude: safemode: hfuse reads as D8
avrdude: safemode: efuse reads as CB
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed

To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "regular_16664.hex"
avrdude: input file regular_16664.hex auto detected as Intel Hex
avrdude: writing flash (8740 bytes):

Writing | ################################################## | 100% 0.89s

avrdude: 8740 bytes of flash written
avrdude: verifying flash memory against regular_16664.hex:
avrdude: load data flash data from input file regular_16664.hex:
avrdude: input file regular_16664.hex auto detected as Intel Hex
avrdude: input file regular_16664.hex contains 8740 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 0.27s

avrdude: verifying ...
avrdude: 8740 bytes of flash verified

avrdude: safemode: lfuse reads as FF
avrdude: safemode: hfuse reads as D8
avrdude: safemode: efuse reads as CB
avrdude: safemode: Fuses OK

avrdude done. Thank you.

NOW you can continue with the instructions on page one of this thread, have fun.

Hints and thoughts:

- Important is, you have an avrdude.conf file where the avrdude.exe is. Doing this command line in the "\hardware\tools\avr\bin"

directory from your Arduino IDE does not have such a file.

- You cannot do too much wrong sending the command line, just reset Micro, wait one or two seconds, send the command line

in your prompt

- I assume the Bootloader from the Micro can be different for other, depending in which state their Micro is.

- After burning the hex file to your Micro, it will be a "Generic USB Hub" in device manager. Somebody know how to get the Micro

to "normal" state after rooting a million CCs?

Good luck guys and million thanks to the root devleopers!

My system is a W7 64 bit by the way.

Cheers