yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] Asphyx:
Thanks...I don't have a Netflix account so I couldn't test it myself...

I haven't gotten any new updates yet on my unit but I was late to get it last time around. If the new OTA doesn't work with the old then I'm not sure much can be done as it makes sense that the boot.img was always signed and checked before. Perhaps I'm wrong about that and a custom boot.img could be made to remove that sig check and allow autoroot to work. But I'm betting it's going to take changes to autoroot to accommodate the new reality as opposed to creating a new boot.img and replacing the one from the OTA.
[Google Chromecast] ghowse:
Just to add some more info, which may or may not be relevant ...

- I am in Australia, using a CC bought from a US supplier. My test above was using the Australian Netflix.

- The main reason for rooting for us here in Australia is/was the ability to save smartDNS addresses directly on the device, to allow US Netflix to be received. Netflix only came to Australia officially in 2015. US Netflix has arguably better and greater content than that offered in Australia.

- Of late, being able to get US Netflix has become more difficult. This applies to nearly all platforms, not just CC. A SmartDNS service or VPN are not guaranteed to work, however I can still get US Netflix on my PC Netflix client (last time I checked). These days I normally simply use Aussie Netflix unless I really feel like chasing up the latest info, static routes etc.

- the local tech community has an ongoing thread on the various attempts to circumvent Netflix geoblocking. See https://forums.whirlpool.net.au/forum-replies.cfm?t=2614016

Cheers
[Google Chromecast] thorburn.nathan:
I had not realized the eureka app wasnt updated since 2015 so I tried updating to fix the chirping sound bug that has since been fixed on the Chromecast updates and luckily had everything to revert back.
[Google Chromecast] Asphyx:
I think the series leaking out has caused some of the crackdown on the Netflix side...

Just FYI as to why I was asking about Netflix...

https://torrentfreak.com/netflix-use-of-google-drm-means-rooted-android-devices-are-banned-170515/
[Google Chromecast] Lizard:
Just a random thought, could it be Google implemented the 'Android Verified Boot' also for the Chromecast? See this post from Chainfire: https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606
[Google Chromecast] fink.nottle:
I've again got the chromecast black screen. I thought it was not going to auto-update any more. I used some instructions from a few pages ago, and managed to get it to 84839. It looks like it still auto-updated.
[Google Chromecast] Asphyx:
You are mistaken...No one said it would not update once Google came out with a new Firmware...
[Google Chromecast] fink.nottle:
Yes, it looks like it. Is it possible to disable autoupdates while a proper fix is determined ?
[Google Chromecast] Asphyx:
Sorry but no...The only options are wait until a permanent fix for Autoroot is found or go back to stock using the files in THIS THREAD

But note if you go back to stock you lose Root Access.
[Google Chromecast] m4f1050:
What I did was flash EurekaROM and that at least allows it to boot and if one or a few apps don't work, oh well, at least it boots up and works for the others.
[Google Chromecast] fink.nottle:
Isn't it possible to block updates at the router+device level ? If the ota server is different from regular google servers, it should be possible, right ?
[Google Chromecast] Asphyx:
It would depend on the router I suppose...

It's not like there is a hosts file you can use to block traffic.

The device checks for updates on it's own so unless you can alter the DNS to dead zone any traffic going to the OTA server I don't think it really is possible.
[Google Chromecast] fink.nottle:
That isn't too difficult for most *wrt routers. That may be a decent option until something better comes along. Although, there is that other stock with updates disabled thread. I wonder if that can be adapted to stay on the latest working version.
[Google Chromecast] m4f1050:
I would donate again if EurekaROM keeps up updating their ROM... Don't mind having that piece of mind that I can do anything to MY device...
[Google Chromecast] fink.nottle:
Do you know which ones don't work ? Any major ones ? Youtube, HBO, Hulu, Netflix ?
[Google Chromecast] m4f1050:
I don't use HBO, but Facebook, Youtube, Hulu, Netflix, Plex and Pandora still work, the only other one I use, Spotify, does not connect. So out of 7 that I use, 6 still work.

To answer your question, Youtube, Hulu and Netflix do still work on 44433.
[Google Chromecast] speakxj7:
a little late to the party here, but i've just been taking a wait-and-see approach, since only really one of my tv's see's heavy CC use, the other has an ATV on it anyway.

i don't mind going back to stock temporarily, including dumping the modified auto-root recovery (for the time being), vs loading some patched rom (especially if we can't yet control the timing of the OTA cycle in the patch-rom case), but that doesn't involve resetting the bootloader back to stock, right? i won't walk away from flashcast, as that's a one-way trip.

from flashcast one can always get back to any cool new developments. in practice i don't use the root capability etc, i just want the ability to re-purpose the device as a small linux device when google finally eol's the cc1 and/or i upgrade away from using it.

odds are, i'll just grab a cc2 for the one tv that really needs it, as a short term solution - but going back to stock (if i can keep the flashcast bootloader) costs me zero.

my main motivation for upgrading from eureka in the first place was a) a couple apps wouldn't cast to the older cast receiver firmware, and b) assistant support.
[Google Chromecast] m4f1050:
Why not EurekaROM? It has a nice Web GUI...
[Google Chromecast] speakxj7:
sure it's an option, but above are the reasons i left it in the first place.
[Google Chromecast] Asphyx:
Sorry but there is no TEMPORARY going back to stock...

Once you go back to stock you lose Root and any chance of rerooting the device.

So it's a matter of do you wait for a fix that may never come or just go back to stock and lose whatever advantage you might have had with a rooted device.

As I have said before, For the measly $25-35 bucks you can just go buy a new stock device to use in the meantime while you wait for a fix, Or go back to Eureka and hope nothing you use requires newer firmware.
[Google Chromecast] m4f1050:
Good advise! $35 for stock while fix comes out is definitely *THE* way to go. Me, I just use the latest EurekaROM... Hopefully they don't stop updating it. It is such a great idea, but I'm sure it's a PITA to get the latest OTA to behave correctly with the extras...
[Google Chromecast] Asphyx:
Well Eureka is a dead project as far as updates go. It was a pain to maintain and the Autoroot was created to replace it so the Dev could move onto other things and not be so tied up constantly patching and testing updates every time Google decided to update the firmware.

But it really doesn't matter how old the software gets as long as it still does what you need it to do.

In the end that is really what is important. So far people are reporting that everything they use still works. If anything were to break I guess it would be something like Netflix but so far from what people are saying that hasn't happened.

So despite no updates for Eureka, the device still seems to work and really in the end that is all that really anyone should care about.

At least with Eureka you know it won't update to the newer firmwares that don't currently work on a rooted device.

And I suppose that will hold people for awhile until a solution is found or we call it a loss ,go back to stock or Just buy a new device and keep the rooted one in case something else comes along to make it useful.
[Google Chromecast] m4f1050:
Since it's rooted, is there a way to update the apps ourselves? Maybe through ssh? I know I only have 1 app that doesn't work: Spotify. If I could get the latest Spotify and sftp into my Chromecast and update it, I wouldn't mind doing this every time I boot the device(s)...
[Google Chromecast] Asphyx:
Don't know about Spotify but I know Netflix is baked into the firmware itself...
[Google Chromecast] m4f1050:
So after it boots you can't change it, they load it from the firmware or memory or does it create an executable app? I am just talking out of my @$$ right now, just trying to figure out a way to overcome these older apps and updating them to newer ones...
[Google Chromecast] Asphyx:
Really no way to update them...

For one they aren't apps in the same sense of apps you can get for Android.

All they are is an On-Device version of the player/receivers that in most cases is loaded into the CCast from the Internet.

In the case of Netflix (and I suspect Spotify) instead of loading from the internet they are in the firmware.

Now that doesn't mean it isn't possible, I suppose the parts needed could be ripped from one of the newer roms and shoehorned into the device but I suspect it would require just making a more current Eureka update from the latest working firmware to hold us until Autoroot is fixed.

And even then I'm not sure that is possible.
[Google Chromecast] m4f1050:
Ah ok.. I'll wait in the hopes of an updated EurekaROM. I already said I would donate again if they continue support on the EurekaROM, such an *AWESOME* idea, I would not switch to Autoroot if it's in the same boat as Eureka... Autoroot is like having Eureka now, but with no GUI... meh...
[Google Chromecast] puppinoo:
Hi all and sorry for the newbie question.

I kept my Eureka rooted CC turned off for years.

Today I turned on and it updated to latest Eureka 44433.044433.00101 [2015-11-15].

I tried to realize if it's convenient to install Autoroot but I noticed it's having issues.

What's my best option?

1) Keep older 44433

2) Update to autoroot and face the Black screen issue.

3) Try to update mannually to a newer version 84839 or maybe 84838 (Without auto root? if possible I'd need help, maybe an how to).

Thanks for any advice.

puppinoo.
[Google Chromecast] mcpdigital:
Another semi-update from Google happened ? Suddenly all my CCs were back to the Chromecast.....

I did the same procedure (Kernel) replace with the 84839 version and they are back to live but with 84839. I had the impression that only the part that we modded was updated and no new version was installed. The non-rooted CC is at the same version using Home app for Android (84839).

The desktop app Chromecast shows 80438 (Kernel ?) for the rooted ones and 84839 for the non-rooted.

Am I the only one ?

Thanks

MCP
[Google Chromecast] Droid_JD:
Me too. Worked fine last night, this afternoon, "Chromecast...".

Wife not happy...
[Google Chromecast] TooYellow:
Crud, this just happened to me also. Stuck on the Chromecast... screen.

It was fun while it lasted but it's only $30 to buy a new one so maybe I'll just do that.
[Google Chromecast] ZaneChua:
Build 88007 just came out. Trying to get the OTA link for it.

EDIT:

http://redirector.gvt1.com/edgedl/g....21d42fb3e90192f4163119560ab06d0177431041.zip
[Google Chromecast] Droid_JD:
This is the stock image, right?

Still no fix for the newest "Chromecast..." ?
[Google Chromecast] Asphyx:
Do you have any idea why using the old boot.img no longer works?

What did they change this time?
[Google Chromecast] woody1:
I hate to ask this, but is this the end of the road for rooted devices? I'm debating whether I should just flash back to stock and forget about root. I'm afraid that my CC will be obsolete before we get a reliable rooted version working again. Opinions?
[Google Chromecast] Asphyx:
It's probably not the end of the road...

But you have to ask yourself how important is it to have a rooted device compared to working device?

My Rooted CCast was never used for more than the occasional presentation or stream. I never needed root to do any of that and nothing I use it for really requires any of the newer firmware perks. It was always used as a Tinkering unit and occasional target device.

So I'm in no rush to go back to stock, Could probably still use the device under the much older Eureka rom if I wanted, and my other CCast that gets used by family has not root. They sure haven't missed having root.

So it's up to you on what is important... Rooting a CCast is mostly a status thing not a real perk for most that don't need any DNS tricks.
[Google Chromecast] ghowse:
I too had the "Chromecast" message come up at bootup again.

I hope I haven't made a major mistake. I used the image from http://redirector.gvt1.com/edgedl/g....21d42fb3e90192f4163119560ab06d0177431041.zip with the procedure given previously. I am back up and running on 44433 again with Team Eureka web panel. I no longer have Flashcast AutoRoot.

Not sure exactly what to do from here.

Thanks

Geoff
[Google Chromecast] Asphyx:
Unless there is something you need that requires a newer Firmware, I would just hold on the Eureka so you can use the device in the meantime until someone figures out a way around the Autoroot breakage.

That is probably what I'm going to do once the update hits me.
[Google Chromecast] m4f1050:
Good advice... What I've been doing since I experienced the 1st black "Chromecast..." screen. ;)
[Google Chromecast] Droid_JD:
Does that firmware work with HBO /Showtime? I've had problems getting those to work with eureka in the past
[Google Chromecast] Asphyx:
No I believe they require newer firmware...But I don't have those services so don't take what I say as gospel.

I do remember they were added after Autoroot was established.
[Google Chromecast] selepo:
Back to stock

If I decide to go back to stock, is there an "official" back_to_stock.zip ?

Just want to make sure nobody has tampered with whatever I put on my network...
[Google Chromecast] Pietplezier:
Noooo, black screen with "Chromecast.." again.. I hope some smart guy will give us steps to fix this :) :)
[Google Chromecast] Mad07:
If you want to go back to stock, with no way return...

https://xdaforums.com/showpost.php?p=72094986&postcount=58
[Google Chromecast] fink.nottle:
Does anyone know the OTA server's dns ? I'm willing to try blocking it at the router level if someone knows the ota domain. It would only work if it's a domain specifically for chromecast, and not for other google services in general.
[Google Chromecast] Mad07:
I don't believe, that this file is only on one location available. If Google released an image for x thousands of devices there a a lot of locations, which you can received as DL location (via load Balancer)
[Google Chromecast] kapilsolanki:
OPPO neo5 16Gb custom rom install kaise kiya jata hai
[Google Chromecast] Mitsch79:
With 44333 you will not be able to use google play video for video streaming. That's why i just reverted to stock.

Gesendet von meinem GT-I9505 mit Tapatalk
[Google Chromecast] niphoet:
How did you revert back to stock? Thanks
[Google Chromecast] Mitsch79:
https://r.tapatalk.com/shareLink?ur...hare_fid=3793&share_type=t&share_pid=72094986

There is the "back to stock" zip Image i used to revert my CC.

You can flash it using flashcast v1. 3, like you would flash the eureka rom.

Gesendet von meinem GT-I9505 mit Tapatalk
[Google Chromecast] woody1:
I'm giving up and I'm getting ready to flash my CC back to stock. Before I do, does anybody want to trade a gen 2 CC for my rootable CC?
[Google Chromecast] ForbEx:
gived up. Flashed stock and now everything ok.
[Google Chromecast] m4f1050:
I would keep the rooted one and buy the gen 2 cc... It's like $30 now... WHAT IF they come up with a way of fixing the AutoRoot or if they decide to keep updating Eureka ROM? They did 44333 or whatever version, maybe they skip a few, but end up releasing one that works with most of the apps. I don't get it. I stay away from Apple because Android can root easier than Jailbreak an iOS, but now Google is following the Apple way? Jeez... Reminds me of the Toshiba AT305 ended up being my son's gaming tablet until they even stopped updating the OS on it! With root you can at least port other ROMs and give it more lifespan... SMH! All they care about is making $$$

Which leads me to a question I've had for a while, what is the major differences of the gen 1 and gen 2? Faster processor, better video? Because that could mean the end of gen 1 soon also....
[Google Chromecast] ghowse:
I just picked up a new CC2 for "stock/OTA updates". In everyday use, I can't detect any improvement over the CC1. My rooted CC1 can have a holiday after several years of solid use. It can be in reserve until a new AutoRoot patch (or another use) comes along.
[Google Chromecast] Srandista:
Yeah, I was also "forced" to revert to stock on one of my CC. Second one can rest in shelf, until we came with some solution to this situation. If not, EurekaROM is still valid solution to make sure, that rooted CC will stay rooted, even if its outdated.
[Google Chromecast] tdhite:
My take, and that is all it is: it is highly unlikely time will get spent on the gen 1 device. It is a losing cause (old device, verified boot, etc. all a long term cat and mouse game to overcome, even for Magisk).

Android is headed the way of Apple and creating much more difficult rooting abilities with consumer (though not necessarily dev) devices. Arm's hardware based security is at the heart of it and that is nearly (leaving room for exploitable bugs here) impossible to beat.

With that said, the Eureka devs open sourced their code. Anyone is therefore free to attempt updates and overcoming things. I dev a lot and can't honestly find the value in updating it just so root sticks on an old device.

Use your old devices as routers, or IoT gateways or some such thing if you keep them rooted by sticking with Eureka. No shelving needed.

All, JMO.
[Google Chromecast] Asphyx:
I can't blame or expect any Dev to waste valuable time working on a project that seems to have very little benefit other than being able to say "I'm Rooted!"

There are just so many more productive uses of their time IMO.

I personally have moved beyond the CCast and now use Android box devices that with a little tweaking can be used like a CCast with the added benefit of running Kodi and is even supported by the Windows Cast capability. And I can plug in hard drives, and Remote controls for a much better user experience.

You can find cheap versions of these boxes for a mere $20-30 US more than a CCast.

Or you can splurge like I did and get yourself one of those Zidoo 9S or 10 models that actually have an HDMI input for your Cable box making it work much like the old GoogleTV units.

CCast was great at the time and is still useful but technology has marched on and really sort of left CCast behind.

It's limited and not quite as good as the newer devices which is why Google decided to create Android TV in the first place. Trying to keep up with the competition that didn't exist when the CCast first came out.
[Google Chromecast] Mad07:
Thanks for ypir personal meaning.... I habe already an Android box beside, but the CC is still connected on a HDMI Port of the AV receiver and its much easier to handle-specialz for my Wife (WAF factor ;) as any other device. So that is not an option to replace the cc with a TV box...
[Google Chromecast] Srandista:
No change with 90308 firmware?
[Google Chromecast] tdhite:
Laying bets here . . . It will never change. Google can and will win this game. Not that it thrills me, it's simple reality.

Use your CC for general network utility (IoT gateway is my current favorite 'hack') plus whatever Eureka can do; buy something else; or go back to stock.

Most folks should just head back to stock and get a device usable for its intended purpose.

JMT.
[Google Chromecast] Srandista:
As I said previously, I already went back to stock on one om my CC, second is on EurekaROM, so it will stay rooted no matter what. I'm just curious, but as [MENTION=2212097]ddggttff3[/MENTION] mentioned previously, without new source code it probably won't be doable bypass new security measures. But Google is pretty late to release it, still no new release since 1.22.

https://drive.google.com/drive/folders/0B3j4zj2IQp7MZkplRzRvcERtaU0
[Google Chromecast] Mad07:
I can agree this one:

Still waiting for an announcement, that nothing will be done in future or for a further fix (hopefully the last one)
[Google Chromecast] aikhome:
It's probably been answered.... I flashed this thing into my CC with Eureka 27946.002, how do I flash " any official Google OTA sent to your device" in practice? At the moment CC boots into Eureka with Web interface, does this mean that /cache/install.sh did not do the job even though it reported "AutoRoot-Recovery: Process Complete! Cleaning and rebooting..."?

upd: tried again:

[aik@aik ~]$ ssh root@aikcast

/usr/bin/X11/xauth: not found

# busybox wget http://pdl.team-eureka.com/recovery/install.sh -O /cache/install.sh

Connecting to pdl.team-eureka.com (95.170.82.169:80)

install.sh 100% |*******************************************************************************************| 3381 0:00:00 ETA

# busybox chmod +x /cache/install.sh

# /cache/install.sh

AutoRoot-Recovery: Running AutoRoot-Recovery Installer!

0

AutoRoot-Recovery: Downloading now...

AutoRoot-Recovery: Recovery Downloaded Successfully!

AutoRoot-Recovery: Verifiying Recovery...

AutoRoot-Recovery: File Verified Successfully!

AutoRoot-Recovery: Downloading Google OTA...

AutoRoot-Recovery: Verifying Google OTA...

AutoRoot-Recovery: Google OTA Verified! Moving file...

AutoRoot-Recovery: Flashing Recovery...

AutoRoot-Recovery: Process Complete! Cleaning and rebooting...

packet_write_wait: Connection to 192.168.10.130 port 22: Broken pipe

It rebooted and web interface reports "Build Version: 27946.002 (06/04/2015)". Where did that OTA go to then?
[Google Chromecast] Asphyx:
The old bootloader worked because the old Boot.img didn't bother to check the validity of the system.img.

And the Rooting was done via modifying the system.img.

New boot checks to see that the system.img is from Google...So until some source can be found to modify the new boot.img not much progress is likely.
[Google Chromecast] Asphyx:
Did you try to download anything in those folders?

---------- Post added at 05:06 PM ---------- Previous post was at 05:05 PM ----------

Check those folders again and tell me what you see....
[Google Chromecast] TheKyro:
Hi, yesterdsay I decided to upgrade my chromecast v1 from "44433.001 [2015-11-15]" to "[ROM] [r02 - 2015-12-13] Flashcast-AutoRoot"

but now I am stuck with a red light

the content of flashcast.log (after having ssh'd with root:letmein credential) is:

Reading recovery parameters

SETUP FAILED: Unsupported Mode! This version of Flashcast can only be ran from the recovery parition of the Chromecast.

any idea what I can do here (I'm ready to revert to full stock) ?

Thanks
[Google Chromecast] bhiga:
Reflash Eureka ROM then (re-)read the initial post and the last few pages detailing what has changed that makes this not work directly anymore.
[Google Chromecast] theronkinator:
Gonna unroot mine I think, looks like nothing is coming to sort this. Done, unrooted and back on 22062 and waiting for it to update, spent ages looking for my Teensy and didn't even need it. All sorted and updated, forced the update with the below in powershell (as I didn't want to start installing Git/Bash), now on 1.26.92486
[Google Chromecast] chaos719:
I ssh logged in and did entered in the text and it said it updated. When the cc rebooted said it was ver. 1.17. Since its currently a even higher version I let the cc reboot again during this boot I saw the eureka notification that it was updating but when it finished it just read Chromecast on the screen and stayed there. Light was white on the cc. Did I miss something or is mine just a brick now. I'd rather not buy another one but it's cyber week and I could get a v2 for $20 everywhere
[Google Chromecast] bhiga:
Partition changes made autoroot no longer work on current firmware.

There were a few folks who got intermediate versions to work, but not sure if anyone took charge to see about getting it to continue working.