yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] JayDee78:
I am really surprised on how few have actually rooted their devices...

http://ota.team-eureka.com/

~200 new devices added since release, and i have done 6 in total.

I know that people might think root "gives to little" right now, but why miss the train...
[Google Chromecast] extrem0:
Lol. I checked that early today and thought the same.

I think this is because many people think that they don't need root and/or they don't want to (or can't) buy a teensy.

But only 4 days has passed. Maybe many are still waiting for their teensy arrive.
[Google Chromecast] Srandista:
Like here. Since I'm living in Europe, delivery time is longer, then to US.

But my Chromecast is from yesterday offline and I'm waiting just to receive my Teensy board, to be able to root it.
[Google Chromecast] dargo7:
Root gone weird

Well I had some weird time rooting my CC

I was using Teensy 2 and I did everything according to plan, but during the upload of the image to CC I got red LED colour, so I thought I had to reset it. When I did it I checked if I was able to get into the Team Eureka panel and to my suprise I could.

Next it I had some problems with CC as I was able to cast any files locally, from my mobile or PC (using Bubbleupnp) but I couldnt manage to cast anything from the web (youtube or infinititracks).

So my last hope was to do the factory reset, which I did, but I forgot to unplug the flashdrive with the rom image (have no idea if that is any important at that moment).

And in the end I got to see the TE boot animation (after the first flash I wasnt able to see it) and everything works as it should.

Has anyone had similar problems?

I guess since I am able to log into TE Chromecast panel I managed somehow to root it, or am I wrong (I know it sounds like a noob question :) )
[Google Chromecast] :
this is not what I asked. You need to forget the Chromecast completly and read my question again. What is inside the Teensy that makes it so special ?

---------- Post added at 08:43 AM ---------- Previous post was at 08:35 AM ----------

miss the train of what ? You can get mini Android PC quad core/1GB RAM/ 8GB ROM + uSD card slot, 2 USB port with a remote for $59.00

Its pretty cool to do if you already have the Chromecast and the Teensy, but that's it.

Every time someone ask what you can do with a rooted CC, you either get a) no answer or b) a link to a pathetic page that gives links to more useless informations.
[Google Chromecast] peca89:
Well, these are the reasons why I'm still not rooting mine:

I'm not buying $17 hardware to root $35 hardware. Chromecast is not officially avalible in my country, so selling Teensy after rooting would be very hard. I will consider rooting once source code is available. Then I could probably compile it for temporary use on Arduino Uno's 16U2 I already own using DFU.

Will Eureka ROM get updates in future at the same frequency as Google updates?

I never liked irreversible actions? Can I return to stock bootloader and ROM?

Why? Web interface is cool, but why do you need it? SSH is cool, but what useful opportunity does it give? Why restarting using Web when you can restart using Chromecast app? Why restart at all? Why should temperature interest me except for being cool to know? Why do I need opportunity to whitelist apps which do not exist currently?

Please correct me if I'm missing something, but the current only really usefull advantage of being root is custom DNS, but that is useful only to somebody who is willing to pay for custom DNS...I'm not.

These are the functions I would like to see on Chromecast, that MIGHT be possible to achieve using rooted device:

Support for wired Ethernet adapter via USB Host

Sending HDMI-CEC command to return to input source it switched

from

after stopping playback. I do not know the command, but I know it exists as my TV does that when connected to Canon camera

SMB/CIFS streaming from local network

AC3/DTS passthrough

I've got a lot more ideas :)
[Google Chromecast] Silenus21:
Yeah the lack of new users is the teensy requirements.
[Google Chromecast] TheMorlince:
I actually posted a link and info in my local cities subreddit. Trying to get people together for a mass rooting event. A few interested people, but that's a good way to get others to root since I bet the $17 dollar teensy is a big detriment, let alone the ota cable. Just the hassle of having to source and buy the individual things may deter folks.

Those things you want, whether possible or not will not be really interesting for some people to develop if there is not a good base of people that would use it. The more people that root, the more cool things we will get. At least that's the way I see it.
[Google Chromecast] ddggttff3:
First off, while I agree it would be nice to have more features just remember Team-Eureka only has 3 members, all of which have full time commitments.

Also, some of these things have been done already...

Support for wired Ethernet adapter via USB Host

Kernel has USB Enabled, can add Ethernet drivers by compiling your own kernel.

Sending HDMI-CEC command to return to input source it switched

from

after stopping playback. I do not know the command, but I know it exists as my TV does that when connected to Canon camera

To do this extensive work would need to be done on interfacing with the GPU driver

SMB/CIFS streaming from local network

CIFS Support was added to the kernel. If you are command line savi, mount to /data/test, then use curl to stream using fling. If you want to make a GUI for this, I will send you more info.

AC3/DTS passthrough

More fun driver stuff, we have not touched this

I've got a lot more ideas :)

While these features are nice, its kind of impossible for just us 3 people to keep up with demand. If you want some of these features, why not root and try to add them yourself? Everyone can have a wish list, but this is XDA. Why not try to add the features you want?
[Google Chromecast] GusCaplan:
More In Depth

Hello,

Great tutorial! I was wondering specifically the teensy did to the chromecast and is there a way of "porting it" to arduino? (I could do that bit myself)
[Google Chromecast] pwvandeursen:
Won't sell mine yet, but if you send your unit to me in the Netherlands I will be more than happy to root it for you. Just rooted 2 devices with succes!
[Google Chromecast] gdude:
Root seems like a nice "just in case" option. It would be more useful it we could directly write text or image to the screen from locally running code in some easy way.

Getting the parts together, and the opportunity to use them, may be taking some people time. That includes me (I can't remember where I put my USB OTG cable with a Y-connector). As long as I keep my Chromecast unplugged, I figure there is no big rush.
[Google Chromecast] BlueCop:
I just wanted to say a huge thanks to everyone who worked on this.

I plan to add a lot of new functionality to the chromecast. :) I will try to port to AT90USB162 for people when sources are posted.

Thanks again guys! keep up the great work.

I am astounded by the complaints in the thread. I don't understand that mindset. We can do something today we couldn't do a week ago because of this release. If you aren't grateful for that then you shouldn't be posting imho.
[Google Chromecast] Asphyx:
Actually if you are doing an already updated device the red light stays lit and solid while it loads the OS so the only indication is to look at the monitor the CCast is plugged into.

1 - That Teensy does a hell of a lot more than just root your CCast. Without going into great detail it can do lots of VERY COOL things. Do a google search for USB HID Security for just one aspect of the Teensy's Power.

2 - Yes from what I have seen Eureka gets an update for every update that Google makes. The Devs have been very good about that. It may mean a slight delay of a few days to get it in some cases (the Devs do have lives and rent to pay you know!) but rarely have I seen Google add anything significant to an update that wasn't already known about and added to the custom Whitelist of Eureka (Screen Mirroring comes to mind!)

Once the source code is released I suspect you will be able to load up the Root Hex into the Arduino system for further fun and games.

No I think any discussion of it might give them a hint on what is going on with the Teensy and lead them to an effective means of patching it!

This is why I am glad the source hasn't been released to the public yet because any info that is out there is info Google doesn't have to reverse engineer on their own.

Just a note on the HDMI-CEC feature...I'm not sure HDMI-CEC protocol actually supports such a command. The routing function of CEC is really just a closed circuit switcher. The CCast doesn't know a thing about what inputs are available or even which input it is plugged into. When it makes a switch of input it is nothing more than a software version of a switch that says COME TO ME and the TV complies.

In order to go back to the previously used input the CCast would have to KNOW what input it was on before it took over and there is no functionality for this in the HDMI-CEC specs. Since the CCast could not know what input to return to the TV would have to know this and the proper command would need to be built into the TV to do that.

But don't expect to ever see that happen as it would wreak havoc for other devices in the HDMI-CEC chain.

HDMI-CEC for all intents and purposes is a LOOK AT ME function not a LOOK AT THAT function.

Don't expect to ever see something like this until such time as you also see a LAST INPUT button on your TV Remote. Cause then at least that command will be present in the TV for any CEC device to trigger.

The Example cited by the OP is not using CEC at all it is using Deck Control Which is probably a much better way for the CCast to be integrated with a TV monitor and also give you control of the stream via the TV remote.

But that is something Google should consider as it would drastically change the way CCast works and do it in a much more proper way than is being done now.
[Google Chromecast] rydako:
I'm still waiting on my teensy and cable /coupler. Teensy should arrive today, cable tomorrow or the day after, and thats only because i managed to find someone willing to sell the teensy in nz, if i had to import it'd be another two weeks... For those of us who don't live in the US, getting ahold of the teensy and otg y connector can take a while.
[Google Chromecast] X3r0X:
Flashed it with my Arduino Leonardo thx guys!
[Google Chromecast] bunchies:
Nice, so this is doable with other hardware

I don't have a teensy and after hearing about it I want one anyways but being able to use something else is great to hear
[Google Chromecast] X3r0X:
As its the same chip Atmega32U4 why shouldn't it work?

You have to use the regular file.
[Google Chromecast] bunchies:
i haven't looked at the specs of that specific adruino board yet
[Google Chromecast] X3r0X:
no offense, just saying :)

Good luck with that guys, keep in mind the led indicator works only on teensy.
[Google Chromecast] az1324:
Because they have different bootloaders (arduino is 8x larger) and if the application happens to overlap the bootloader memory because it wasn't told to avoid it when compiled then it wouldn't be compatible. But based on the reports I guess it doesn't have this issue.
[Google Chromecast] compuguy1088:
Where did you get a ota y cable? Sparkfun?
[Google Chromecast] theronkinator:
They're one of the biggest technology companies on the planet, you can bet they'll figure it whether some kid talks about it on the internet or not.
[Google Chromecast] SomeGuy2008:
Just got my CC the other day (kinda new to cc). Just ordered Teensy++ yesterday should have it in a few days. But much like other cc users im still trying to figure out what real benefit there is to having a rooted cc. I could see that it might be worth playing with more (rooted) if the cc had an interface similar to appletv. But then again its meant to be a casting client not so much a media center AIO device I guess. I know the hardware inside the cc is somewhat limited. I'm sure as time goes on more and more development will be done with it in the rooted realm, so we will see what the future has in store for the cc.

~SomeGuy2008
[Google Chromecast] bhiga:
FAQ, Part 2, 1.d and Root Mini-FAQ list things.

Does root get you a lot more? No, but it does give you more control and in the Chromecast world of Google updates the firmware automatically without confirmation or the ability to postpone, sometimes even breaking stuff (ask the folks with 720p-only TVs), that can mean a lot.

Chromecast is designed to be a closed-ecosystem device, so I wouldn't expect a huge root development front. Perhaps that will change now that more devices can be rooted. Still - it's much like the malware scene - it's not entirely that MacOS is immune to malware - it's simply a smaller market so why rob the corner bakery when you can rob an entire bank?

IIRC that number represents how many have "phoned home" recently. I have 4 active now, and 2 sitting idle. 2 were active and 4 were idle for a long time. Will have two more once I HubCap these other two.
[Google Chromecast] II.J2G.II:
Source

No Source yet @_@ it would be nice if some hex was compiled for other AVR's boards, i'm sure there would be a lot more trying this then .. just a thought :D ... Water, Water Everywhere . . . And Not A Drop To Drink
[Google Chromecast] frap129:
Mind linking to the forum post? In theory it should work because they have the same micro controller, but there are other factors such as the bootloader. Maybe he used DFU to force the Teensy bootloader.
[Google Chromecast] Luxferro:
Are you sure about that? Just a quick look at some CEC specs shows some basic commands it can do: http://xtreamerdev.googlecode.com/files/CEC_Specs.pdf (found link in wikipedia). Check out section 'CEC 11', then 'CEC Table 8'. Seems all you'd need to do is query who is the active stream before the CC becomes active stream, store that address, then do a route change when done.

<Request Active Source> 0x85 ;query who's active source
...Parse data, store info...
<Active Source> 0x82 ; become active source
<Routing Change> 0x80 ; switch back to original source

I'm no expert, but HDMI-CEC can do a lot if not crippled by manufacturers implementations of it. For example, I used to use an HTPC with a CEC dongle and Event Ghost. You could basically program Event Ghost to do whatever you wanted over the CEC bus. Check the status of the TV, if powered on, turn on AVR, switch to X input, ect. Why would I do that? Well normally my HTPC would be sleeping, but if it had a scheduled recording it would wake up to record it. If I didn't put in a query to check the status of my TV it would power on all my devices thinking I'm going to watch TV. With the check it would only power on my receiver if my TV was on, and my TV only turned on if I manually turned it on.
[Google Chromecast] Asphyx:
Right so why help them by giving them hints of where to look?

---------- Post added at 10:58 PM ---------- Previous post was at 10:49 PM ----------

The issue is getting the CCast to store the address. Who should do it? the receiver app? the Hardware itself when it goes to default screen?

But you mentioned the biggest hurdle...The TV's don't really support the entire spectrum of commands that are available.

Also remember that an HTPC is still a full fledged PC!

CCast is Hardly that sophisticated.

But if it CAN be done the truth is it SHOULD be done by the Receiver apps itself not the CCAST device.

When the Receiver apps senses end of stream it should trigger the proper CEC command to return to previous status. Most don't because the expectation is you will decide to play something else and not want to unload the app.

it has to be done by the receiver app otherwise you are waiting for 10 Minutes while the default Kick App wait period of the hardware to kick in and take you back to default screen before you would get sent back to previous input.

Now imagine a state where you disconnected from one App after using another. Where will the information come from the app you were on or the new one? Where does the CCast switch back to?

So it's a complete mess to implement in the way the CCast works because Google leaves most of the programming up to the Receiver app makers to support control and any programming needed it to do what you want based on App state.
[Google Chromecast] Luxferro:
You're just making excuses. They were talking about adding features for customizing the chromecast rom. There's no reason something that simple can't be baked in. It will either work, or it won't and you're in the same boat you're in now - stuck manually switching inputs.

And while lots of functions of CEC are left out by manufacturers, those are mandatory and the basics of how CEC works. Says so in section CEC 11, if you took a few minutes to read it.
[Galaxy S 4 Q&A, Help & Troubleshooting] Reconde:
Well I was recently trying to update a ROM on my Galaxy S4. I had just finished wiping system, data, cache, and dalvik, and after I rebooted the phone. Now it is stuck on the Samsung Custom screen. Please help!
[Galaxy S 4 Q&A, Help & Troubleshooting] lolo9393:
Just switch it off by long press on power off button or removing battery. Then go to download mode by 3 buttons combo and flash a new rom with odin.
[Galaxy S 4 Q&A, Help & Troubleshooting] debbuger:
You wiped system thats why its not booting.flash stock rom with odin to restore it
[Galaxy S 4 Q&A, Help & Troubleshooting] Reconde:
Thank you guys for the reply. This worked
[Shield Tablet Q&A, Help & Troubleshooting] MRobbo80:
need a quick answer thanks
[Shield Tablet Q&A, Help & Troubleshooting] perun:
Switch off tablet. Wait 20 sec. Now press vol down + power. Now from menu find recovery and press power button. Or if you have root download quick reboot from market.
[Shield Tablet Q&A, Help & Troubleshooting] markymark567:
If you need a quick answer why not just google it?
[Shield Tablet Q&A, Help & Troubleshooting] abnormaIity:
To expand on the second post. Hold the volume down button and press the power button and let go, holding both down will just load the tablet. Once your in the bootloader, use the volume buttons to select recovery and hit the power button to launch recovery.
[Huawei Ascend P7] mickliq:
Is anyone working on CM11 for the P7? Seems like a great device for stock KitKat?
[Huawei Ascend P7] PrimuSSaintS:
Would like to know that too :D can't wait to get CM11 :)
[Huawei Ascend P7] Ziolek67:
Any news about this custom rom for P7 ?

Huawei Ascend P7-10 by Tapatalk2
[Huawei Ascend P7] 87insane:
Want this or other costum Rom like cm too!
[Huawei Ascend P7] 87insane:
http://xdaforums.com/showthread.php?p=56321341
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Raistlin1:
My tab 10.1 is on stock ICS 4.0.4 and Netflix app says it's not compatible with this device.

Any ideas or help or links on how I can get netflix working on it?

Thanks

NM, found an apk of an older version and installed that and it works.
[ONE Q&A, Help & Troubleshooting] skyhonor:
I have downloaded the 33R OTA on my computer. I'm using TWRP. Can someone please give me steps to update? Thank you.
[ONE Q&A, Help & Troubleshooting] zephiK:
You put the zip onto your phone and then boot into TWRP and then flash it.

Or you can go boot into TWRP and adb sideload it.

The dragging zip onto the phone is probably easier for you.
[ONE Q&A, Help & Troubleshooting] skyhonor:
Thank you!
[ONE Q&A, Help & Troubleshooting] TheAtheistReverend:
Did installing through TWRP break root for you? It appears to have broken mine.
[ONE Q&A, Help & Troubleshooting] zephiK:
If it did, boot back into TWRP and flash SuperSU 2.02 and you'll have root again.
[ONE Q&A, Help & Troubleshooting] skyhonor:
Yes it did break root. At the end of the flash, you will be prompted to install SuperSU again. When the phone reboots, go back to your App Drawer and look for SuperSU installer. Press it and install. :) You regain root.

Does anyone know if it is safe to use franco.kernel r14 after update to 33R? Thanks
[ONE Q&A, Help & Troubleshooting] TheAtheistReverend:
Did work :victory:

Thanks!
[ONE Q&A, Help & Troubleshooting] zephiK:
Yup its safe, r13 was safe to boot 33R as well but you might as well get r14. The fixes in r14 are worth having.
[ONE Q&A, Help & Troubleshooting] skyhonor:
Thank you so much!
[ONE Q&A, Help & Troubleshooting] MasterThiefGarrett:
What are the fixes?

I'm either blind or stupid, can't find it...
[ONE Q&A, Help & Troubleshooting] playya:
http://kernels.franco-lnx.net/OnePlusOne/4.4/appfiles/changelog.xml
[One (M8) Q&A, Help & Troubleshooting] narikki:
Hey guys,

So this morning I got prompted to update to 4.4.3 (i think it was that version). anyways i clicked okay to install it, so i left my phone and came back.

when i looked at it, it just was a black screen and was stuck. I reset it and now i can only go to the stock recovery mode or it just boots up to a black screen.

What can i do? if i plug it into the computer it cant install the MTP driver.

Thanks for your help!
[One (M8) Q&A, Help & Troubleshooting] pawslo1984:
Pm me i can help if u want but better is to talk on Hangouts [emoji6]
[One (M8) Q&A, Help & Troubleshooting] narikki:
Thanks for the help!!!!
[One (M8) Q&A, Help & Troubleshooting] Tej XFire:
You could have waited for a few mins before taking any action. The OTA update process clearly states that you should not disturb the device and/or use it when the updates are being installed. Looks like its software bricked. Try a reset from the stock recovery. I'm sure nothing would happen, as the OS would have been corrupted. At this point, I recommend you to get it fixed via HTC. :good:
[One (M8) Q&A, Help & Troubleshooting] pawslo1984:
Welcome [emoji6]
[P3300, MDA Compact III General] wkienhuis:
I've a dutch version of de artemis (compact 3) and I've sync problems (activesync 4.2). In the beginning everything went well. But after a while, when I want to sync again, the activesync icon turns around in the green colour but gives an error: "activesync cannot connect to mobile device". I've tried everything to solve it. The only way was to hardreset. After that I could sync again. But now, a few days later, it's the same story again. Can somebody help me?
[G3 Q&A, Help & Troubleshooting] tarponpesca:
Hello friends,

I come across this forum as conceptualized ask for help to solve a problem I'm experiencing with my LG G3. I have a LG G3 D855 asiatica oringe and how much like customizations made ​​some changes, nothing that had not already been done on other devices I've ever had and never had a problem. Once you have downloaded the root Xposed, and some modules framework, using usually came after that, more to my surprise when making a frustrated attempt to install a font that I downloaded from this forum and try to install the app IFont, I realized that the machine began to take much to restart and the worst is that this delay was increasing and even though I desistalado some applications and the source itself, I realized that this delay only increased. Just to give you an idea, the last time I tried to restart took 48 minutes. I tried to go into recovery mode in various ways, in no more managed to get him into recovery. I tried to restore factory settings through and he was not called for more black screen and only the LED flashing blue and red. Please if anyone can help me I earnestly beg you pass me an email: tarponpesca@hotmail.com or answer right here.

Grateful.
[G3 Q&A, Help & Troubleshooting] dex.:
try to get into recovery by powering the phone off. remove and reinsert battery. plug USB lead into USB 2 port on the computer. press and hold the volume up button. keep the button pressed while you plug in the usb lead to the phone. that normally gets in to recovery. (does not always work with a USB 3 port for me).

then flash kdz in "normal mode" using the instructions in another thread. or use the LG more support tool. (sorry, not able to search for the correct threads at the moment, need to log off for a couple of hours...)
[G3 Q&A, Help & Troubleshooting] tarponpesca:
Tutorial flash kdz

Please could you pass me a tutorial on how to flash via kdz?

Grateful.