[ROM] [44433.001 - 2015-11-15] Eureka-ROM - Based on OTA 44433

Search This thread

loplo

Senior Member
Apr 5, 2010
229
16
localhost
I did it :))
IMG_20131221_173144.jpg
 
  • Like
Reactions: killall

jamesking420

Senior Member
Aug 4, 2009
385
39
Hey guys - great work!

A few suggestions...

Some sort of reference to the thread ROM version number (e.g, 1.1), along with the Build version number (eg 14975.002) on the chromecast web panel would be cool.

Do you have any plans to make the home screen more interesting? Eg, maybe the ability to set a custom home screen (rather than those photos), or some sort of portal type page where maybe we could see things like the weather, calendar invites, stock prices - like Google Now, but for Chromecast! (obviously I realise this would be done via baby steps at first!

I just rebooted 14975.001 - and it rebooted back in to the home screen and didn't seem to pick up an update to 14975.002...?

Thanks for all your work!

James
 

ddggttff3

Inactive Recognized Developer
Dec 13, 2009
815
1,543
Minnesota
Hey guys - great work!

A few suggestions...

Some sort of reference to the thread ROM version number (e.g, 1.1), along with the Build version number (eg 14975.002) on the chromecast web panel would be cool.

Do you have any plans to make the home screen more interesting? Eg, maybe the ability to set a custom home screen (rather than those photos), or some sort of portal type page where maybe we could see things like the weather, calendar invites, stock prices - like Google Now, but for Chromecast! (obviously I realise this would be done via baby steps at first!

I just rebooted 14975.001 - and it rebooted back in to the home screen and didn't seem to pick up an update to 14975.002...?

Thanks for all your work!

James

For the version thing, in the future on the home page under status we will have the panel check and tell the user if its the lastest build or not.

As for plans, yes we have more stuff in the works no worries ;) and the custom wallpapers is definitely on the list of things to work on.
 
  • Like
Reactions: loplo

wptski

Senior Member
Dec 8, 2011
1,371
157
Warren, MI
It happens, just always turn on your TV to make sure your device is not updating before unplugging it from power. :)
My CC is powered by the TV so it doesn't matter but this time I removed it and used the wall wart to get the update but this does bring up a question. Do we always have to select the CC as our input to see if it's updating before turning the TV OFF? I assume it will show that it's in the middle of a update?? Powering OFF during an update isn't good as I just have found out!
 

ddggttff3

Inactive Recognized Developer
Dec 13, 2009
815
1,543
Minnesota
My CC is powered by the TV so it doesn't matter but this time I removed it and used the wall wart to get the update but this does bring up a question. Do we always have to select the CC as our input to see if it's updating before turning the TV OFF? I assume it will show that it's in the middle of a update?? Powering OFF during an update isn't good as I just have found out!

You don't always have to, but its good to check during a OTA rollout. Also, this is probably one of the reasons why the official user manual for the device says to use the external power brick instead of the TV for power. That way you cant interrupt the update process.
 

wptski

Senior Member
Dec 8, 2011
1,371
157
Warren, MI
You don't always have to, but its good to check during a OTA rollout. Also, this is probably one of the reasons why the official user manual for the device says to use the external power brick instead of the TV for power. That way you cant interrupt the update process.
Or just disable OTA from the panel? What's the "Apply Updates" for? Does "Disable OTA" download but not apply?
 

Anakha56

Senior Member
Aug 10, 2008
927
132
Durban
It happens, just always turn on your TV to make sure your device is not updating before unplugging it from power. :)

Can I make a future request for OTA updates? Could we make it so that it could be a manual process? Mine is powered on and plugged in 24/7 but I would like to be in control for when the update applies. I would hate to be fiddling with my system and accidently power it down while it was doing a update. Just something to consider :).
 
  • Like
Reactions: guy4jesuschrist

ddggttff3

Inactive Recognized Developer
Dec 13, 2009
815
1,543
Minnesota
Can I make a future request for OTA updates? Could we make it so that it could be a manual process? Mine is powered on and plugged in 24/7 but I would like to be in control for when the update applies. I would hate to be fiddling with my system and accidently power it down while it was doing a update. Just something to consider :).

Thats why you can disable OTA updates. Just disable them and watch this thread, so if theres ever a update you just do it by using a flashcast jumpdrive.
 

guy4jesuschrist

Senior Member
May 24, 2011
461
138
Thats why you can disable OTA updates. Just disable them and watch this thread, so if theres ever a update you just do it by using a flashcast jumpdrive.

In a future update, is it possible to add the option to disable automatic updates, which would then display a "Check for an update" button in the Web Configuration Panel? This would allow the option of updating without the inconvenience of flashing manually with a FlashCast drive, and would make it safer for those who are powering their Chromecast via the TV's USB port instead of the power brick. No chance of accidentally corrupting the installation of a new update, if it's happening while on a different input and turning the TV off. Make sense?

Sent from my HTC One using Tapatalk
 

ddggttff3

Inactive Recognized Developer
Dec 13, 2009
815
1,543
Minnesota
In a future update, is it possible to add the option to disable automatic updates, which would then display a "Check for an update" button in the Web Configuration Panel? This would allow the option of updating without the inconvenience of flashing manually with a FlashCast drive, and would make it safer for those who are powering their Chromecast via the TV's USB port instead of the power brick. No chance of accidentally corrupting the installation of a new update, if it's happening while on a different input and turning the TV off. Make sense?

Sent from my HTC One using Tapatalk

No it does, and a force update check button was one of the ideas we were toying around with adding, which would pretty much do exactly what you are talking about.
 
  • Like
Reactions: guy4jesuschrist

aouni_tahech

Senior Member
Sep 20, 2011
181
52
For the version thing, in the future on the home page under status we will have the panel check and tell the user if its the lastest build or not.

As for plans, yes we have more stuff in the works no worries ;) and the custom wallpapers is definitely on the list of things to work on.

That's what I was going to ask for before I stopped at your above post. Thanks. Can't wait to have the ability to preview my own wallpapers on my TV.
 

ahecht

Senior Member
Oct 23, 2010
526
315
I had Flashcast and Pwndcast working fine on my Chromcast. I updated my flash drive to Flashcast 1.1.1 and tried to manually update to Eureka-ROM. However, after the Flashcast screen comes up the white light turns red after a few seconds. This is the log:

Code:
Reading recovery parameters
Looking for mods on /dev/sda1
Resetting crash counter and boot mode
Clearing OTAs
Copying /usr/share/flasher/remove-ota to /tmp/tmp.aRGbEu
Flashing mod at /tmp/tmp.aRGbEu
Mounting cache (mtd4) at /tmp/tmp.uvfrKt
Removing temp-ota.zip and ota.zip from cache partition (/tmp/tmp.uvfrKt)
Unmounting /tmp/tmp.uvfrKt
Removing temporary mod directory /tmp/tmp.aRGbEu
Mounting /dev/sda1 to /tmp/tmp.P1UmeJ
Using runtime directory /tmp/tmp.P1UmeJ/flashcast-data/1
Opened log file /tmp/tmp.P1UmeJ/flashcast-data/1/log.txt
Created large temp directory /tmp/tmp.P1UmeJ/flashcast-data/1/tmp
SETUP FAILED: No images found on /dev/sda1
Removing large temp directory
Unmounting and removing /tmp/tmp.P1UmeJ

EDIT: PEBKAC error. I misspelled eureka_image.zip. Works now, thanks!
 
Last edited:

wptski

Senior Member
Dec 8, 2011
1,371
157
Warren, MI
I had Flashcast and Pwndcast working fine on my Chromcast. I updated my flash drive to Flashcast 1.1.1 and tried to manually update to Eureka-ROM. However, after the Flashcast screen comes up the white light turns red after a few seconds. This is the log:

Code:
Reading recovery parameters
Looking for mods on /dev/sda1
Resetting crash counter and boot mode
Clearing OTAs
Copying /usr/share/flasher/remove-ota to /tmp/tmp.aRGbEu
Flashing mod at /tmp/tmp.aRGbEu
Mounting cache (mtd4) at /tmp/tmp.uvfrKt
Removing temp-ota.zip and ota.zip from cache partition (/tmp/tmp.uvfrKt)
Unmounting /tmp/tmp.uvfrKt
Removing temporary mod directory /tmp/tmp.aRGbEu
Mounting /dev/sda1 to /tmp/tmp.P1UmeJ
Using runtime directory /tmp/tmp.P1UmeJ/flashcast-data/1
Opened log file /tmp/tmp.P1UmeJ/flashcast-data/1/log.txt
Created large temp directory /tmp/tmp.P1UmeJ/flashcast-data/1/tmp
SETUP FAILED: No images found on /dev/sda1
Removing large temp directory
Unmounting and removing /tmp/tmp.P1UmeJ
I believe this has been posted before and happens when you haven't renamed the file to "eureka_image.zip".
 

Top Liked Posts

  • There are no posts matching your filters.
  • 147
    rQo4FcZ.png


    What is it?

    With over 4000 users, Eureka-ROM (formerly PwnedCast) is the de facto third-party Chromecast ROM. Maintained by Team Eureka, this ROM adds features such as SSH and Telnet access, DNS customization, and a web-based configuration panel to the stock Chromecast OS, while maintaining the stock OS's simplicity and ease-of-use.

    What does it do?

    Along with all the features of the stock OS, Eureka-ROM allows you to
    • Use SSH, ADB, or Telnet to access a root shell
    • Specify alternate DNS servers to overcome certain region-based restrictions
    • Use custom application whitelists to bypass Google's application registration requirements
    • Configure the device using a web-based control panel
      • View device status and network information
      • Enable or disable Team Eureka's OTA updates
      • Select which whitelist provider you want to use (Google, Team Eureka, or custom)
      • Enable or disable remote services
      • Set custom DNS servers
      • Reboot and reset your device

    Eureka-ROM also includes several internal changes:
    • Google's OTA updates are disabled, so your Chromecast won't patch itself.
    • Instead, OTA's are delivered by a custom Team Eureka update engine (more information).
    • A custom "Team Eureka" boot animation is installed so you can easily determine that your device is running Eureka-ROM.
    • The stock recovery image is replaced with FlashCast to further prevent any attempts by Google to patch your device.
    • The idle screen URL restriction is removed.
    • A custom kernel image is installed to enable the following features:
      • Interactive root UART console
      • In-OS USB device support
      • CIFS/Samba share support

    How do I use it?

    Installation

    1. Setup and Install FlashCast v1.2 on a USB drive. This step requires booting your Chromecast once in order to initialize FlashCast. Make sure to follow all the installation instructions given in the FlashCast thread.
    2. Rename the downloaded Eureka-ROM zip file to eureka_image.zip and place it in the root folder of the FlashCast USB drive.
    3. Plug the FlashCast USB drive into the Chromecast, hold down the button, and connect power to boot the device. If you attempt to use an earlier version of FlashCast, such as v1.0, the installation will fail.
    4. Flashing will take about 9 minutes, so be patient! As long as the Chromecast's LED is blinking white, flashing is in progress.
    5. When done flashing, the device will reboot.
    6. Enjoy!

    Usage

    The custom features of Eureka-ROM are configured through the web-based control panel. To access the panel, use a web browser on your computer or phone to connect to the device's IP address. You can determine the IP address using the Chromecast setup application.

    Who made it?

    The majority of the ROM consists of the stock OS image provided by Google. ROM-specific features were written by members of Team Eureka. We'd like to also thank the GTVHacker team for their initial exploitation and documentation of the Chromecast and the following individuals for their various contributions:
    • death2all110
    • ften
    • tvall
    • Anyone else we missed!

    Where do I get it?

    Releases
    44433.001 [2015-11-15] (latest version):
    http://pdl.team-eureka.com/ota/final/44433.001.zip
    SHA256: a905a61d78b700aebe03d155cdf1ca7ca69a91b73685006fde6d8f088bedbfef
    MD5: 280223014b97b1090c9ef98698a2bc7d

    Updated base firmware to 44433
    All new binaries using the new toolchain
    Default to Google Whitelist (on reset/fresh install)
    Add Userscript support! (runs /data/user_boot_script.sh on startup)
    Fixup a bug in the whitelist sync script
    Minor changes to WebUI panel backend code (fix some things)

    27946.002 [2015-04-06]:
    http://pdl.team-eureka.com/ota/27946.002.zip
    SHA256: deb031c8fa7ec9790077e0dadc7a986dff70f0822d3031f1b6573d112987d0d7
    MD5: 9e627a8788b28156b41e9401e938663d

    Fix a bug that broke the OTA service

    27946.001 [2015-04-05]:
    Download link removed due to a critical bug. Please use a later release instead.
    SHA256: aa75c65801d214632e0448026085b23b46011e2ffc6e53ea04ceb064b9cbee07
    MD5: 2e6e17a14484a8d5f182ae400865ca33

    Updated base firmware to 27946

    26653.001 [2015-02-21]:
    http://pdl.team-eureka.com/ota/26653.001.zip
    SHA256: c53db4f08140129aef70afab83383bc9db95d09d4e8b3f8df66bb6c305e4cab6
    MD5: 5d7f25f72e269d8d52e8fc64b2e5e255

    Updated base firmware to 26653
    Fixed the Force Update Feature (Thanks @fkrone!)
    Upgraded to SuperSpeed™ V2.0

    22062.001 [2014-12-07]:
    http://pdl.team-eureka.com/ota/22062.001.zip
    SHA256: 3d2def8229ddc2fdd103df500a49156b6d47e4b066fcc45de97c059b2b38f9f1
    MD5: 90c79ff4bc2f7af16e63543f8886194f

    Updated base firmware to 22062
    Improved the SuperSpeed™ technology
    Updated Busybox to version 1.21.1
    Updated webpanel (check repo for changes)

    19084.001 [2014-09-12]:
    http://pdl.team-eureka.com/ota/19084.001.zip
    SHA256: 9a8df71a608abef4433769798df7365da07784ecf64bd90257acef04e78fd475
    MD5: 2414b9f0fb603ec809cad2b6fec6909f

    Updated base firmware to 19084
    Added SuperSpeed™ magic to the flash process!

    17977.001 [2014-08-05]:
    http://pdl.team-eureka.com/ota/17977.001.zip
    SHA256: 5b350cb1161e7b8f5fcba19b03a1a71a38897372fa635d7c050921e97b850636
    MD5: 1a3a1f03cbcd6dff9453d0ae35af4e12

    Updated base firmware to 17977
    Updated Recovery Image to Flashcast V1.3

    17250.003 [2014-06-22]:
    http://pdl.team-eureka.com/ota/17250.003.zip
    SHA256: 4cc774c725a061050e1dd9023ef1a5cc26ef48360104e2ba17562de41030fccf
    MD5: 1c7c4c5d6ecb82d6ffe37af4a54ab26d

    Fixed a critical bug that caused the OTA system to not function

    17250.002 [2014-06-22]:
    Download link removed due to a critical bug. Please use a later release instead.
    SHA256: 1259cba5fce9b6e2e173f08e71be5603f7cff9cb2b2f344fcdbacc70219a5bb8
    MD5: b4478f4606cd8e0d3276531e7484e41e

    Updated base firmware to 17250
    Added the ability to change the device hostname from the Web Panel
    Added the ability to force an update check from the Web Panel
    Enhanced the OTA system to make sure updates are applied when downloaded
    Added Donator list to the Web Panel

    16664.004 [2014-05-04]:
    http://pdl.team-eureka.com/ota/16664.004.zip
    SHA256: be9009eddb2089b902d7f429b4e3fe29dd76acb176f207d90be8670c7b3f0a30
    MD5: 2af4b1ac869473c92095b3aa940ecea1

    Added support for Team-Eureka's v2 API whitelist. (Enables support for Android KitKat Screen Casting)
    Added support for a device to be a "developer" device when the Google whitelist is selected.

    16664.003 [2014-04-09]:
    http://pdl.team-eureka.com/ota/16664.003.zip
    SHA256: e4567d1ed9a38cd5bdd338d63ee633541d5e1d25dd5e80bfc11df0a3f93f7d40
    MD5: f354c80a7ba994a1adef98a8bdf1a29b

    Fixed a critical bug with SSL libraries that caused DRM content (Netflix/HBO-GO) to not play, or crash the device.

    16664.002 [2014-04-08]:
    Download link removed due to a critical bug. Please use a later release instead.
    SHA256: f0ec41755140587eb5cdff9237db66053f59ebce6668d58b9a4d64ed1e197f18
    MD5: ed98c926ece1b030873c5b64a801e475

    Fixed a permissions issue which caused an HTTP 500 error to be shown instead of the web panel.

    16664.001 [2014-04-08]:
    Download link removed due to a critical bug. Please use a later release instead.
    SHA256: e0dfa8eee51b50d87cfbb3d8a748dcd511f33d5186013a20e408cc111527e513
    MD5: 92a5468efa49a6e45e11fc4ff442e075

    First release using the new versioning scheme of basever.release. Also includes a number of internal changes:
    • An updated base image (build 16664)
    • A custom kernel build, which enables early-boot initramfs modifications to be made
    • An updated recovery partition based on FlashCast v1.2
    • A migration of SSH keys out of the /system partition so that it can be pre-packed in the future to significantly decrease flash times

    v2.0 [2014-02-14]:
    http://pdl.team-eureka.com/ota/15250.001.zip
    SHA256: 4b50ad1de4b75e8a509df3289687fec3fd2dab1dec3d4b8648dbcfa4e0c4ddb4
    MD5: ddbc4a5a6079dcd44422b0b5e88157cd

    Updated the base image to build 15250

    v1.1 [2013-12-21]:
    http://pdl.team-eureka.com/ota/14975.002.zip
    SHA256: a653139b6efa453dafc1b848c5498e556db36739e44f88a784df874861d1b1f4
    MD5: 32426753e7101c717ec9a3f245a31eb6

    Fixed a bug that caused config changes to be ignored

    v1.0 [2013-12-20]:
    http://pdl.team-eureka.com/ota/14975.001.zip
    SHA256: 2953f5bf3237e04670382547d958940f6c6362503b6ac1de4f45a2610db96d3d
    MD5: 5d30d112b21d6de2f715067f3ef6dcb4

    Initial release of Eureka-ROM, formerly PwnedCast

    Source

    Eureka-Panel: https://github.com/team-eureka/Eureka-Panel
    Eureka-ROM: https://github.com/team-eureka/Eureka-ROM
    Whitelist-CGI: https://github.com/team-eureka/Whitelist-CGI
    ChromeCast-OTA: https://github.com/team-eureka/ChromeCast-OTA
    EurekaSettings: https://github.com/team-eureka/EurekaSettings
    51
    Soo happy to have this out the door, hope everyone likes the work here - we've been working pretty hard on it over the last few weeks (sorry for the delays in getting this out to you all!)

    If anyone has any bugs to report please PM myself or ddggttff3

    Just so everyone knows there is a LOT of changes under the hood for this. It implements the EurekaSettings newly defined standards where configuration settings are held within ini files for user/system data and so settings in Eureka panel will be held in future OTA updates! (my favourite setting).

    Whitelisting now is hosted locally on the device and syncs the whitelist from Team Eureka servers so if our servers go offline your device doesn't (and of course you have the option to change this to use Google's whitelist servers, the local file (non syncing) or another web based whitelist of your choice (if anyone ever wants to set one up).

    I really hope you all love this as much as we love bringing it to you.
    36
    New OTA (44433.001) is now live and will start rolling out shortly! :)

    As for the side project of mine, that is still a few weeks out, but expect that to be my final gift to the Chromecast community once it's complete (it will be in a new thread). With that said, as of now expect no more Eureka-ROM updates, and it's been a pleasure to be a part of this community. :cowboy:
    31
    Just pushed out the first 15250 based OTA. It should hit everyones chromecast within the next 5 days. Sadly, this OTA does not include the new web panel, or the ability to set an ssh password. We are working on finishing those features up, and hope to have an OTA out within a month to add them. Due to so many new apps relying on this OTA, we decided to push one now that has all of the same features as the 14975 build.

    We are sorry for making users wait so long for a 15250 based ROM, and we hope you understand.
    29
    Hello,

    Thread cleaned. I hope everyone has had a chance to cool off.

    There was a massive amount of arguing, bickering, profanity and other assorted offensive language. There was also a good deal of entitlement and ETAish type postings.
    With the kind of attitudes I've seen on this thread recently, I'm surprised anyone comes to this site to make anything for us. Honestly, if you feel you can make a better rom or mod, then please do.
    People do this kind of stuff in their spare time for free and their lives do not revolve around giving us the latest and greatest goodies. Please be happy with what you get and if you're not, either make your own rom or go elsewhere.
    A lot of people forget none of these enhancements to our devices have to be made but some of you feel things are owed to you for some reason. No one owes you anything.

    If there's an issue with the rom, please let the developers know in a more respectful and polite manner. Bullying people to get things done does not accomplish anything except to make people work slower or give up on the project altogether. If there are bugs or fixes that need to be made, you have no choice but to be patient and to wait for them to be worked out. If you can't wait then, as I said, you can go elsewhere. Please don't use this or any other thread to vent your anger and frustration.
    It's not fair that a few people have to ruin the experience for the rest the users on this thread.
    Please try and be civil and respectful to one another.

    Regards...