yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] Team-Eureka:
What is it?

This is a FlashCast mod to give your Chromecast a nearly stock OS. Although Team Eureka (obviously) believes that the features we've added to Eureka-ROM make it superior to the stock OS, we realize that it's not for everyone. Perhaps you want a clean base to develop from, or maybe you want want to try out a new feature from Google before Eureka-ROM is updated. Either way, the last thing we want to do is force you to use a ROM you don't want. To that end, this ROM is completely stock, save for two modifications:

update_engine is removed so that your vulnerable bootloader is preserved.

FlashCast is installed to the recovery partition instead of the stock recovery, to mitigate any bootloader updates Google may try to push through other methods.

Please note that this ROM contains no SSH, ADB, Telnet, or other means of remote shell access. In addition, it has no OTA system, so it is your responsibility to update to newer versions using FlashCast. We recommend that you use Eureka-ROM instead unless you have a specific reason for wanting a stock experience.

Where do I get it?

Build 44433 (latest version):

http://pdl.team-eureka.com/minimal/44433.zip

SHA256: 3cdebca7789d3024b036fdd2e82a06bbf6015d8fa2bf8f0a4f85fe819419cc73

MD5: c536136b76839fca00cf49dd220bb6a0

Build 27946:

http://pdl.team-eureka.com/minimal/27946.zip

SHA256: 56d35b1c06ed116aa3ee93f10fcf08b92b6a92c280a53d20c98a2d949d29b9f9

MD5: c74e4d3791847152ebde11e2090970eb

Build 26653:

http://pdl.team-eureka.com/minimal/26653.zip

SHA256: b1c62828e76b35da918aad438bc598c52c407e657431bc397664616e83d24fc9

MD5: 6db4d1c8fe7ab20268f4e99f3c70667f

Build 22062:

http://pdl.team-eureka.com/minimal/22062.zip

SHA256: cf6c2b4b1b2603abed51efc2cb39d7a6f882669946e8d879b5d1e4fd13156db9

MD5: cfaa7e4ca5f9686eb96dcb36e531c3f2

Build 19084:

http://pdl.team-eureka.com/minimal/19084.zip

SHA256: 74fa139c87c7affc5dab5f27cd1623845a89606d80fbfa7d5505bc137ece25a6

MD5: 271e628598dff919199e684921d158ff

Build 17977:

http://pdl.team-eureka.com/minimal/17977.zip

SHA256: fd5fd2daa40b5915f729e96e467c904a79f541196bb512679a61b3376cc49672

MD5: 54f4513432447156cd46fc868dffc487

Build 17250:

http://pdl.team-eureka.com/minimal/17250.zip

SHA256: 26d127c75d57d7aa4b8900cb27f3a3bba5f2690840f3e1dfa7c581bfb7c0aeec

MD5: c9adbd48d6e58113ec30ed8cd136bf16

Build 16664:

http://pdl.team-eureka.com/minimal/16664.zip

SHA256: 9a657d0b7945cf69c8127deb5a98f198a74cd959c09aae250f81ec3ad4a0f7e4

MD5: d961b63a2112294cfa6eefcf3eee205d

Build 16041:

http://pdl.team-eureka.com/minimal/16041.zip

SHA256: 212dfde7cd34a09a8699b9eb2064da34bac3f973cbce5bb7952ecdcdd1608c09

MD5: eac8b93a2da723fb29eb7ea7be4744cf

Build 15250:

http://pdl.team-eureka.com/minimal/15250.zip

SHA256: 54af712df8edf165de63d6f690642d234d12e8cd01889f877bf9fe93ef8a807a

MD5: e8a51bdbcd4e96da3a13b539ca314da4
[Google Chromecast] mathorv:
Just to clarify. It has Google Whitelist right?
[Google Chromecast] gulbrillo:
Yeah, all stock Google, no custom whitelist in this one.
[Google Chromecast] jsdecker10:
If we are currently still running the Eureka ROM based on 14975 and using the custom whitelist feature that you guys integrated into the 14975 Eureka ROM image, would it CURRENTLY be possible for us to take advantage of all these new apps that are going to be flooding the Google Play Store/Chrome(PC browser apps/extensions) Web Store, or MUST our Chromecast be the newest updated version 15250(with either a future Eureka ROM update to 15250, by flashing this "nearly stock OS build" 15250, or simply someone just has a stock, NON-rooted Chromecast that has taken all the OTA updates and has recently updated itself via an OTA to the newest stock 15250 firmware build) ? I understand that by using Eureka ROM's "custom whitelist" that you guys manually update the whitelist yourselves and it's obviously not physically possible to update your whitelist fast enough to keep up with the "stock Google whitelist," thus always lagging slightly behind the stock Google whitelist AND quite possibly accidentally leaving out some of the lesser-known Android apps and/or Chrome Apps and/or Chrome Extensions that have been added by Google to their stock whitelist, due to the simple fact that you guys just haven't learned of them yet or just haven't been told of them yet?

Basically, if one wants to be able to take advantage of all these new apps that will be flooding Google's stock Chromecast whitelist over the coming weeks/months, etc., to cover all our bases right now so that we're not either hoping that you guys find out about lesser-known apps such as, for a hypothetical example: XCompany's "FancySchmancy Chromecast Media Caster", should we use this upload that you posted so that we're on the newest 15250 and use the stock Google whitelist? Or is it still possible to take advantage of the new apps that the released SDK is gonna bring to us if we're on the older 14975 firmware and disabling your Eureka custom whitelist and instead using the stock Google whitelist? ie. [Eureka 14975 ROM]/[stock Google whitelist] ? :confused::confused::confused:
[Google Chromecast] jaydee 77:
Could this installed on ANY ChromeCast or just ROOTABLE Chromecasts?
[Google Chromecast] bunchies:
does this require a chromecast that has been already rooted?

or can i use this on my unrooted chromecast without the vulnerable bootloader?
[Google Chromecast] mathorv:
In order to install this Vanilla Chromecast 15250 with blocked OTA.

Chromecast has to be ROOTable and has to be flashed with [FLASHER][v1.1.1 - 2013-11-29] FlashCast

It works 100% THE SAME AS non rooted 15250 Chromium, nothing special about it. It's taste of 15250 for develpers and people bored with feature rich 14975.002 eureka mod.

BTW: Great idea for future development cycle - quick minimal releases before major releases.

EDIT:

Works as should and for sure Whitelist is by Google so Fling is not available, AllCast is working like a charm.
[Google Chromecast] bhiga:
No. It's not a whitelist issue as the Team-Eureka whitelist includes what's on the Google whitelist.

Apps built on the released SDK require:

On Chromecast: The "magic stuff" that is in the 15250 build (or newer)

On casting device (for Android): The "other magic stuff" that is in Google Play Services 4.2.34 (or newer)

Being present on Google whitelist (or Team Eureka whitelist)

Eureka-ROM v1.1 is built on 14975, so it fails condition 1 for new apps.

Stock Chromecasts should have auto-updated to 15250 already.

Installing this

stock

, root-preserving, non-updating, no features added ROM will give you:

All Google official apps, including the new releases built on the released SDK

That's it.

No unapproved/beta apps (at the time of this post this includes fling, vbukit, and Audiour)

No ADB, SSH or Telnet

None of the other Eureka-ROM features (static IP, alternate DNS, web panel, etc)
[Google Chromecast] ddggttff3:
1. Any new apps that use the new API will not be available in the current Eureka-ROM that is based on 14975. This is because the new API is not enabled in its Eureka_shell binary, which is the program on the device that literally runs almost every application.

2. Our custom whitelist is no longer a manual entry process, and auto updates when google pushes new applications. This means rooted devices now get apps just as fast as stock devices, as long as they are on a ROM version that supports said application.

3. Disabling the custom whitelist on the 14975 based rom will not allow you to use the V2 API apps, as I stated in #1

We are working on a new version of Eureka-ROM, but are just having a few small things hold us back. This is why the release is taking longer then normal, and as such, we released this minimal image for those who would like to update for the time being.
[Google Chromecast] ddggttff3:
Just posted build 16041 for you crack flashers out there, enjoy!
[Google Chromecast] jay0lee:
Can you post the Google ota link also for these?
[Google Chromecast] ddggttff3:
We do not post those publicly because we don't want users accidentally flashing the update and loosing the ability to root. Please shoot me a PM if you would like the direct link from google for the OTA.
[Google Chromecast] bhiga:
(Emphasis and typo fix added ;) ). Remember, FlashCast relies on an exploit that any unmodified Google OTA will patch, so applying a stock Google OTA won't just result in a tempory loss of root, it's a permanent and irreversible loss of root.

A new exploit would need to be found in order to get root back, and at least so far there doesn't seem to be one in sight.

So that's why Team Eureka is being overly cautious.
[Google Chromecast] ralphwiggum1:
Just wondering if this was sent out to Chromecasts? I just checked my version number and am on the latest. Unless something else happened (I've had frequent unable to boot messages a couple weeks ago and rebooting fixed them).. my Eureka ROM may have been wiped.
[Google Chromecast] bhiga:
No, this is strictly a download and manually flash thing.

What makes you think your Eureka ROM has been wiped? Can you no longer get to the web panel at http://ip_of_chromecast ?
[Google Chromecast] ralphwiggum1:
No web interface, and Chromecast app shows the latest.

The one I flashed manually was the one with the older FlashCast (which would be the first Eureka ROM). At some point I may have come back to stock without my knowledge.
[Google Chromecast] bhiga:
Spontaneously returning to stock is highly unlikely - the update parts are removed/disabled in Eureka-ROM and rooted stock ROM. And true stock ROMs aren't posted to avoid accidents.

There was a previous potential issue where interrupting an update could leave you in a partial state that seemed like a stock ROM, though. (Can't find the post...)

The $1M question is - does FlashCast still boot? If so, you are fine and can simply re-flash Eureka-ROM or rooted stock.
[Google Chromecast] SeBsZ:
I just posted a question here: http://xdaforums.com/showpost.php?p=51084756&postcount=575 which is exactly the same. I was on EurekaROM before and am now on 16041 stock firmware without my consent. I'm going to try flashing to see if I'm still rooted.
[Google Chromecast] Rooksx:
Can you still flash a different DNS with this ROM?
[Google Chromecast] Team-Eureka:
Yes you can flash the DNS modification packages that were released awhile ago.

Just posted OTA 16664, enjoy!
[Google Chromecast] Team-Eureka:
Build 17250 has been posted. Sorry for the delay. - dd
[Google Chromecast] Team-Eureka:
Build 17977 has been posted. - dd
[Google Chromecast] mathorv:
Hey! I know I am in minority and you guys are busy but is there any chance you can still build stock OS with updates disabled until you'll fix security vulnerability?.
[Google Chromecast] mathorv:
Could you at least make a statement that Stock OS with updates disabled is discontinued?
[Google Chromecast] ddggttff3:
Live has been busy. I will get around to making one for the latest OTA this weekend.
[Google Chromecast] Team-Eureka:
Build 19084 has been posted, sorry for the delay. -dd
[Google Chromecast] Team-Eureka:
22062 is up! - dd
[Google Chromecast] Team-Eureka:
26653 is up. I skipped 25525, but if anyone wants it let me know directly.

Also, I have copies of every Chromecast OTA between build 12819 all the way to 26653, so if anyone wants to take a look, feel free to PM me about that as well. - ddggttff3
[Google Chromecast] gamerZ1:
I have stock 26653 firmware from google can I flash your ROM to my chromecast?It was never rooted.
[Google Chromecast] mathorv:
gamerZ1

1. In order to flash Erureka-MOD or Eureka stock up disabled mod you need to root your chromecast

http://xdaforums.com/hardware-hacking/chromecast/root-hubcap-chromecast-root-release-t2855893

2. It's most likely not possible at the moment(read link above). Google updates are intentionally preventing rooting capabilities. So you would have to block google update servers on your router and wait.

3. Also before asking any other questions please read THE INDEX THREAD:

http://xdaforums.com/showthread.php?t=2382364
[Google Chromecast] Team-Eureka:
27946 has been posted! :)

- dd
[Google Chromecast] mathorv:
Is Team-Eureka development officially discontinued?
[Google Chromecast] oppy:
Kinda seems that way, doesn't it? I'm thinking about just flashing back to 100% stock - there doesn't seem to be any reason to keep root at this point. Especially with the whitelist issue.
[Google Chromecast] extrem0:
I think they stopped working on new features for Chromecast, but AFAIK they purposely opted for not update to a couple stock updates 3xxxx builds since they were bricking some devices. There are a few bad feedbacks about the last builds. People reported device bricking and other losing YouTube cast functionality.

IMO, one of the best eureka ROM feature is google auto update disabled.
[Google Chromecast] mathorv:
I know that TE intentionally skipped one iteration. But three updates have past. Chromecast with recovery is simply unbrickable. I am amazed why there are no new stock with updates disabled where it is no risk at all.

It's the same what I suggested before that eureka mod with eureka updates should be divided to stable and beta branches.

On the other hand I understand lack of commitment because of low interest in the project.
[Google Chromecast] extrem0:
Actually, I got one of my rooted Chromecast bricked in early builds (with recovery). Fortunately I got it hard unbricked by forcing it to boot from USB (where there was another recovery and a ROM to reflash it). I had to open the Chromecast and short two CPU pins. There's a tutorial made by [MENTION=2212097]ddggttff3[/MENTION] over there.
[Google Chromecast] ddggttff3:
the last release, 44433, has been posted. To create new builds in the future, I recommend using the Eureka-ROM repo from https://github.com/team-eureka/Eureka-ROM with the 02make-minimal.sh script.
[HTC EVO 3D] somekid15:
Anyone got the link for the kitkat test build of evervolv? The CDMA version btw
[HTC EVO 3D] hossman:
http://www.evervolv.com/get/ev_shooter-4.0.0-tester-neco.zip
[HTC EVO 3D] somekid15:
Thanks man
[Xperia Z1 Q&A, Help & Troubleshooting] shadow on the wall:
Hey everyone,

I spend a lot of time trying to root my wonderful new Xperia Z1, the problem is that I want to make a TA backup before I unlock the bootloader but I can´t find a method anywhere to root the phone without unlocking the bootloader. And as far as I know you can only backup TA with root access...

Do you have any good idea how I can solve this problem?

Thanks in advance

Edit: I´m running android 4.3 /.290
[Xperia Z1 Q&A, Help & Troubleshooting] eclyptos:
You didn't search very well. You can root your phone with Locked Bootlader with this method only, by NUT .

Link: http://xdaforums.com/showthread.php?t=2572988

then go with this one

Link: http://xdaforums.com/showthread.php?t=2628185
[Xperia Z1 Q&A, Help & Troubleshooting] shadow on the wall:
I found that aswell, but I was a little confused because the requirements say

So I guess it already has to be rooted with another firmware, but how I´m supposed to get that version on my phone without unlocked bootloader or root?
[Xperia Z1 Q&A, Help & Troubleshooting] eclyptos:
Sorry, i can't understand how you can miss all this stuff. Did you saw the Video Tutorial? There Shem explain everything, you have just to read carefully. Downgrade to .534 FW provided by NUT to not lost IMEI, Root with Bin4ry, update to .290 like the instruction saying then the same for .136.
[Xperia Z1 Q&A, Help & Troubleshooting] shadow on the wall:
Ok it worked now, sorry, I just had no idea how that should work, the video explained a lot.

Thanks for answering anyway :)
[Asus Transformer TF701] bklm1234:
I just got my tf701b from tiger direct. I did a system update check, hoping 4.3 is waiting for me. But none. I thought 4.3 was already out. How do I get it? I'm not planning on rooting yet. Thanks
[Asus Transformer TF701] zabih107:
U can manually download the 4.3 ota update from Asus site, specific to ur SKU (ex: US, WW, etc..) And unzip the first time and place it in the root of ur SD card ( where the alarm, download, music etc... Folders are) and then just restart ur tab, u should get notification for new update then install it and voila!
[Asus Transformer TF701] Snah001:
Depends on where you live!!

Do you live for example in Europe and you have a WW version then you should automatically get an update by OTA, when you live in the US and have a US version you shoud get an OTA too.

When you have a JP version you won't get one because it is not out in JP.

Check here if your version is available:

http://xdaforums.com/showthread.php?t=2554930
[Asus Transformer TF701] Ztruer:
update

Make shure that your SD card are FAT32 ;)
[Asus Transformer TF701] devilsaces:
I live in the US and didn't get an OTA as well. I just did a manual install as explained above. You can check your SKU by going to Settings -> About -> Software information -> build number. Mine says JSS15J.US_epad-10.26.1.18....... The US stands for US version obviously. You can have WW (worldwide) or JP (Japan) etc. Depending on where you live. Download the correct firmware accordingly. You might get an OTA if you wait long enough, if it's available in your area, but I'm not patient.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] rogvid700:
So I backed up my Galaxy Note 3 today and restored it to factory settings in order to re-root after unrooting via the SuperUser app method, however after unrooting, I changed my mind about going back and rooting it again, so I went straight to restore the data from the back up. I'm doing this in Kies 3 and when it asks me to "Select the Backup File To Restore" and I choose the "Select Folder" option and choose the correct backup folder from today, nothing happens in Kies.

I have tried selecting it multiple times and putting the file in different locations in hopes that would change something, but somehow Kies 3 is failing to select it or recognize it.

Keep in mind that I'm not getting any error messages or pop-up notifications whatsoever. Kies 3 simply doesn't respond to the folder I chose.

I have also tried uninstalling Kies 3, and re-installing it.

And yes, when I backed up my data, the backup was a success.

Any thoughts on how to fix it? Or other programs that might be able to read a Kies 3 backup file and do it for me? Thanks!
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] redrover69:
Good luck no one knows.
[Samsung Galaxy SL i9003] mactolorix:
[MENTION=4473033]LoLaTiOn[/MENTION] Hello master LoLaTiOn, I have a problem on my other device "Cherry Mobile Flare 2.0" I do not know how to port CWM on it, May you help me on porting it to our device "Cherry Mobile Flare 2.0" us?

Cherry Mobile Flare 2.0 Specs:

* 1.2GHz Quad Core Qualcomm Snapdragon MSM8225Q Processor

* Android 4.1 Jelly Bean

* 4-Inch 800x480 Pixel Capacitive Display or 233 Pixels per Inch

* 3-Point Multi-touch

* Adreno 203 GPU

* 512MB RAM

* 4GB Internal Storage

* 5 Megapixel Autofocus Main Camera with Dual LED Flash

* VGA Front Camera

* Dual Sim/Dual Standby

* WiFi and WiFi Hotspot

* 3G, EDGE, GPRS and GSM Networks

* GPS

* Bluetooth

* 3.5mm Audio Jack

* FM Radio

* 1,500 mAh Li-ion Battery

It would be so nice if you can help me Master. Thank you so much.
[Samsung Galaxy SL i9003] mactolorix:
[MENTION=2174433]Skin1980[/MENTION] :'( can you help me?
[Samsung Galaxy SL i9003] LoLaTiOn:
i found this for you > http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device

need device for try this good luck
[Samsung Galaxy SL i9003] CodexLink:
[MENTION=5601437]mactolorix[/MENTION]

Hi there are you from philippines?

That phone is in philippines...

Well iam in philippines too... :D

---------- Post added at 06:47 AM ---------- Previous post was at 06:46 AM ----------

It seems help me too from my polaroid tablet (2nd gadget)
[Samsung Galaxy SL i9003] mactolorix:
Yes, I'm from Philippines, hehe. You also? right? I'm having a problem on porting cwm on my device :(
[Samsung Galaxy SL i9003] CodexLink:
Country?

Yes, I'm from Philippines :D
[Samsung Galaxy SL i9003] mactolorix:
[MENTION=4473033]LoLaTiOn[/MENTION] I already got the files for the CWM of my device using the ONLINE CWM BUILDER, do I need to compile it first? Before flashing it to my device? I really dont know what to do next sir. Please help me, not just me but all of the Cherry Mobile Flare 2.0 will be needing a help from a pro like you. We really need CWM in order to fully customize our device sir.
[8125, K-JAM, P4300, MDA Vario General] totempole:
Hi all,

Before I say anything, I am using the 2.17 ROM. When talking to people I cannot adjust the call volume. Its always set to max no matter what I do with the volume slider or the volume icon on screen. It's so loud that the speaker gets distorted. I am afraid if it stays this way either my speaker will blow or I'll go deaf!

Any suggestions out there as to why this is?

Thanks.
[8125, K-JAM, P4300, MDA Vario General] meschle:
What device do you have? I gather thats a qtek rom. But we can help you more if we know if its a cingular/vario/imate etc... You may need to try the native rom to see if its a software or hardware problem. ;)
[8125, K-JAM, P4300, MDA Vario General] Mr.The.Spoon:
Are you sure you're adjusting the volume while you are talking? In-call volume can only be adjusted in the middle of a call. (This may seem obvious but I only realised this recently :oops: )
[8125, K-JAM, P4300, MDA Vario General] headblade:
I wish I had your problem...

Mine is the exact opposite!

My in-call slider does nothing. Sure, it moves up and down, (and yes, during a call) but it does not change the volume @ all!

Mine is stuck on 'almost inaudible' so i can barely hear anyone.

Tried 2.24 cooked T-mobile ROM, (that's when it started) and mr clean's rom hoping that would fix it...

No luck.

Anyone?
[8125, K-JAM, P4300, MDA Vario General] bugaboo:
I have the same problem with my HTC 8125 by cingular with WM 6.1 (Newbie's ROM IPL 2.25 - SPL 2.25 - GSM 02.69.11).

Please, if you know how to help out, or have had this or a similar problem let me know what to do. :confused:
[Galaxy Grand Duos i9082 Themes and Apps] Soureen:
I have made a tutorial on how to play any games at high gfx heres's the link : http://xdaforums.com/showthread.php?p=50070217
[7" Kindle Fire HD General] gregmay15:
Hello everyone,

I just rooted my 2013 kindle fire hd 7'' tonight. Was having fun with it installed 1market, apex launcher, and root uninstaller. Well, i had the bright idea to de-amazon-ify my kindle by removing all stock kindle apps from my kindle with root uninstaller. unfortunately i deleted a package called "kindle system" or something along those lines and now it ts just blank when it boots up. kindle splash screen still shows as if booting normally.

Any way to fix this or am i bricked until a custom rom is out? i wish there was a way to flash to stock...
[7" Kindle Fire HD General] jonathanlyng:
:eek:

it's dead.

you should have done your research before.It looks like you will be waiting for a long time,the 7'' HDX device is more popular among rom devs as they are fully functionnal tablets (as the pre-2013 HD models were), there might never be a genuine system recovery in the wild because of that.:confused:

that being said: you might have luck sending the device to amazon without disclosing what you did. Who knows

hopefully your story will serve as precautionnary tale to the G.P. around here, but I have doubts seeing how often those KFSOWI boot-looped stories come up.
[7" Kindle Fire HD General] gregmay15:
kindle bricked

Already tried that. They wanted the serial number which conveniently is NOT physically on the back of the device. i need to actually get into the system to see what the serial number was. Thanks for the response though!
[7" Kindle Fire HD General] Mineturtle33:
Try fastboot I believe you can use fastboot-getprop model to get information. abd may be able to accomplish something similar.