If you only plan on using the Teensy for this exploit, then there is no difference between the devices.Is there any advantage to having the 2++ device over the v2 for this project only?
If you only plan on using the Teensy for this exploit, then there is no difference between the devices.Is there any advantage to having the 2++ device over the v2 for this project only?
Thanks for confirming. Just ordered the basic one from PJRC. For UK people that works out at £15.68 delivered - nice to see a company providing the standard airmail option.If you only plan on using the Teensy for this exploit, then there is no difference between the devices.
Nope, for this root there is no advantage to using one over the other.Is there any advantage to having the 2++ device over the v2 for this project only?
Control of the device...It`s nice to hear thats Chromecast can be rootet at new Firmware but what can my chromecast when its rootet ?
Have I any more support for DTS in MKV Files ? or What is my win when i rooted it ?
Is there any advantage to having the 2++ device over the v2 for this project only?
When the exploit releases, it will work in two scenarios:Concerning the recommendation to update to build 16664; is it because there's nothing to exploit in earlier versions, or is it just that the current tools only will work with 16664 or higher?
I'm abroad right now, brought my CC just in case something like this was announced, wondering if I should update it via mobile broadband despite the heavy roaming fees, or take a gamble that a tool working with lower build numbers will be released later.
When the exploit releases, it will work in two scenarios:
New In Box Chromecasts (US devices verified, International to be tested soon)
Chromecasts on 16664 or higher (as all of these builds share the same bootloader)
12840/12940 should be covered by the out of box firmware rootAh, I see. New in box as in any CC that has never been configured, or as in the ones you'd find in a store right now, with whatever build version they have?
Got a grey imported US one with build 12840, only booted it to query it for the build number![]()
Great! Then I'll just wait until I get back home again. I'm a Swede in Russia, probably it would cost me more to download the update than I paid for the CC, so I'm more than happy to be able to wait12840/12940 should be covered by the out of box firmware root![]()
Already answered here: http://forum.xda-developers.com/showpost.php?p=54885650&postcount=9Hi will the teensy 3.1 work as well. saw the requirement 2.0 but dont know if that is at least 2.0 or specifically 2.0.
thanks
Patrick
Is it safe to say that the Video posted does not contain ALL the steps needed to root the device as I suspect some software must be loaded to the Teensy first for it to do it's Magic?When the exploit releases, it will work in two scenarios:
New In Box Chromecasts (US devices verified, International to be tested soon)
Chromecasts on 16664 or higher (as all of these builds share the same bootloader)
From what I know about the Teensy, I would be very suprised if there was no programming of the Teensy involved.Is it safe to say that the Video posted does not contain ALL the steps needed to root the device as I suspect some software must be loaded to the Teensy first for it to do it's Magic?
(not asking for details here the fewer the better until you make an actual release just trying to wrap my head around the Teensy since it's a new device to me.)
And just a fair warning to others who want to do this and/or are waiting for a Teensy to arrive...
If you already have the right version OS on CCast you really should Unplug it until you have achieved Root because Google Devs knowing the Teensy is part of the key to this might find some way to plug it up while we wait...
Better safe than sorry!
Yep thats kind of what I thought...I have never really played with one but looking at their site seems like it might have some good entertainment value outside of this hack.From what I know about the Teensy, I would be very suprised if there was no programming of the Teensy involved.
No not really...If the device can see the internet to load the receiver apps (so it can be used) then it sees enough to update...Does anyone know a way of blocking OTA updates from the router as then i can still use my chrome cast whilst i wait, the url etc of the updates i need to block should be sufficient as i know my way around IPtables