curl request for latest firmware about stadia-controller-flasher HOT 10 OPEN

Corrected the URL above. I forgot we already had A latest.

from stadia-controller-flasher.

I totally forgot that over the years I've been trying to capture every update that I saw. Here's a few more older ones

More dogfood builds
http://edgedl.me.gvt1.com/edgedl/googletv-eureka/stable-channel/ota.269117.stable-channel.gotham-pvt-b.d98aee34c392bf64f198f3f5a24018961f72d461.bin
http://edgedl.me.gvt1.com/edgedl/googletv-eureka/stable-channel/ota.269117.stable-channel.gotham-pvt-a.1131ce3771b3da5429417d4d1935b7d2b9943fad.bin

Older stable release http://edgedl.me.gvt1.com/edgedl/googletv-eureka/stable-channel/ota.259108.stable-channel.gotham-pvt-b.0f4b0353c57c9e62f7e4d5a8a847853f7381aa6b.bin

from stadia-controller-flasher.

Here's the B slot for latest release building from that request

http://edgedl.me.gvt1.com/edgedl/googletv-eureka/stable-channel/ota.282115.stable-channel.gotham-pvt-b.b252d0d5a16538621abfb09609746cabc0f33292.bin

from stadia-controller-flasher.

Also I can't take full credit for the URL you got or this. You can thank @tchebb !

I'm just happy to spread the info.

from stadia-controller-flasher.

I'm currently figuring out what change is needed to grab the other dogfood.

from stadia-controller-flasher.

Thanks, that's literally a gold mine and probably it's quite easy to stick the actual firmware URLs onto the current web app.

Just out of curiosity, this is the latest official consumer build, but is there a way to actually request the unreleased build 316328?

On another note, I do imagine their endpoints will cease working in the future and keeping the firmwares in the repo will probably anger some people over at Google.

So ultimately I guess it should be a "Bring/backup-your-own-firmware" type of utility

from stadia-controller-flasher.

I mean at a certain point it's hardware they don't care about anymore.

And yes that's what I meant above trying to figure out how to modify the curl request to pull in the unreleased. I've tried changing stable to a few things but haven't got it yet. I asked the guy I mentioned above who created it and just waiting for a response.

from stadia-controller-flasher.

@luigimannoni which images need to be pulled here? Just the latest firmware and that's it? Does it need to be configurable and if so, how will this be handled by the end user?

Will you be adding the processing of flags via the user interface?

• '?device_type='
• '?firmware_source' - for alternative sources
  • local and remote?
• '?persistent' - for cache?

How will this affect your github pages? Have you taken this into consideration (like will you pull them during the github action process)?

from stadia-controller-flasher.

I'd rather prefer if the flasher downloads the images automatically from the google servers and flash whatever the user selects on the interface as I am certain if firmwares are not removed a DMCA will hit the repo some time in the future and everything goes down with it.

I'm open to suggestions but I think there should be a list of sources on code and the ability to select a file. Lets assume if someone dumped their firmware and want to reflash or if they have downloaded a file already, then they should be able to choose whatever they want.
Also it is possible in 3/4 months google will remove firmwares from their servers so in the long term makes sense to select the firmware file via interface.

So in short, both deploy and binary packages don't need to contain images, I understand that this means the interface needs to be rebuilt from scratch to add new functionality as customisation is difficult with the minified code in the current app, see #6

I'll have think probably this evening and give it a try to migrate all the app into a re-usable framework

from stadia-controller-flasher.

The DMCA is very much a threat indeed and Google will problably remove the firmware as they fired almost everyone involved in the Stadia project so I don't see anyone maintaining that logic.

And your requirements make perfect sense:

• flasher downloads the images automatically
• list of sources on code and the ability to select a file
• deploy and binary packages "should not" need to contain images
• local file firmware capability

from stadia-controller-flasher.