yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] yuval gur:
Hi!

the FlashCast looks grate but I have a problem... I have already connected my CC to the internet.

I tought about something, can someone dump a FlashCast usb drive into a ISO file or a zip file and than I can use a program like RUFUS http://rufus.akeo.ie/ to create the FlashCast usb.

Is it possible?

Will i be able to root my CC than?

Yuval
[Google Chromecast] bhiga:
The FlashCast .bin file is already bootable (by Chromecast) so RUFUS is unnecessary. Just use win32diskimager to write the .bin to the FlashCast stick and boot it on Chromecast.

Since your Chromecast has already connected to the Internet it is highly unlikely that it is still vulnerable, but there is no harm in trying.

The key is in the Chromecast more than FlashCast (no offense to [MENTION=2789381]tchebb[/MENTION]) - if it has vulnerable bootloader, it will run the FlashCast code and you can root unless there is some other problem like a bad OTG cable, bad USB stick, misnamed or corrupt image zip.

If the bootloader is not vulnerable (has been updated OTA, or was already updated at factory) then FlashCast cannot run and you cannot have root.
[Google Chromecast] txpatrol:
Are there any tricks to diagnosing a rom loading problem? I can get flashcast installed and get to the point where I've loaded and renamed the rom .zip on to the flash drive, but when I try to boot Chromecast, I briefly get a white light and then red and then get the flashcast screen with the message about the white or red light.....but the light stay red indefinitely.

I'm trying to install the latest Eureka rom.

I've scanned most of these threads trying to find a solution and am having no luck. :(

I notice that when I try to install the rom and it fails, when I plug the flash drive back in, there's now a flashcast-data folder with a log folder in that. This is what's in the log file:

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.fd5lzR
Flashing mod at /tmp/tmp.fd5lzR
Mounting cache (mtd4) at /tmp/tmp.bb4o4d
Removing temp-ota.zip and ota.zip from cache partition (/tmp/tmp.bb4o4d)
Unmounting /tmp/tmp.bb4o4d
Removing temporary mod directory /tmp/tmp.fd5lzR
Mounting /dev/sda1 to /tmp/tmp.vVzn3F
Using runtime directory /tmp/tmp.vVzn3F/flashcast-data/1
Opened log file /tmp/tmp.vVzn3F/flashcast-data/1/log.txt
Created large temp directory /tmp/tmp.vVzn3F/flashcast-data/1/tmp
SETUP FAILED: No images found on /dev/sda1
Removing large temp directory
Unmounting and removing /tmp/tmp.vVzn3F

I've seen reference to this being caused by not properly renaming "eureka_image.zip". I've verified that several times and copied it straight out of this thread just to be safe.

Edit: This is brand new unit, just broke the seal this morning. Never been online. Serial starts with 37311.

Double Edit: SOLVED! I had file extensions shown in windows, but not on the flash drive for some reason. So renaming it after I copied, I was ending up with a .zip.zip. Fixed that problem and it's loading now. :thumbsup:
[Google Chromecast] frantisek.nesveda:
This may be a little late, but how exactly did you connect your flash drive and power to your Chromecast?

I had a similar problem, LED staying red all the time and nothing showing on the screen, but then I found out what was the problem.

I have an unpowered USB OTG cable and a USB adapter plug (two ends male, one end female, connected together). The problem was that I had the wrong male end plugged to the USB OTG cable and the wrong male end plugged to the power adapter, when I switched them, flashcast booted and everything worked well.

Pictures for clarification:

Sorry for the quality.

Right:

Wrong:

By the way, my serial number is 3905101ZGK3H and it came with build 12072, so I am able to root just fine and now I'm running Eureka ROM without problems.

Bought in the Czech Republic on czc.cz, but it is probably just a resold US version, as it came with a US adapter.

For Czech people: On czc.cz in Prague 4 (Háje) they have at least 10 other Chromecast units, probably from the same batch, that could probably be rootable. If you want to buy it, you should be quick, as the salesman said they are sold very fast.

Hope this post helps someone.
[Google Chromecast] necroscopev:
Please do post the pictures! Maybe it is just something really dumb I am doing backwards!
[Google Chromecast] bhiga:
Main things until Frantisek posts pictures:

The female (port) end of the OTG adapter must "face" the USB stick - in other words, if you trace the connection away from the OTG adapter's

port

, you should hit the USB stick.

The male port end of the OTG adapter must "face" the Chromecast and in most cases, must be

directly

connected to the Chromecast with no other cables in between. The OTG plug has specific pin connections that don't translate past extensions or other cables.

The data lines must connect between the OTG adapter and the USB stick. If there is a Y-cable involved, usually the power-only male connector is red, or if the male connectors are not color-coded, the power-only connector branches off from the power+data connector, or if they split in a true Y, the power-only connector usually has a thinner wire compared to the power+data wire.
[Google Chromecast] frantisek.nesveda:
Yes, that's exactly where the problem was and how I solved it. This is a good explanation, thanks.

Also, I added photos to the previous post (3 posts back). Sorry for the delay.
[Google Chromecast] bhiga:
Posted a Mini-FAQ for common FlashCast issues. Also includes flowcharts for the picture-minded. :)
[Google Chromecast] BewareAlbatross:
Ebay has them down to $90. I guess given the difficulty of acquiring them there's going to be a heavy markup... But hey $10 off from $100 is $10 off, thought it was worth mentioning. I'm thinking about buying one just to get into the dev here and play with stuff. Been a lurker for years but I've never really got into actually talking to folks and I'd really love to start.
[Google Chromecast] anpf:
3C01xx serial number

all the newer sticks have 3C01 serial numbers :rolleyes: ...any chance to root this in future? tried a couple of things to make it happen,but now chance....:crying:
[Google Chromecast] wptski:
That's been asked many times and the answer is that nobody knows.
[Google Chromecast] Creig:
Argh!

I simply cannot seem to get Flashcast to properly format my USB drive. I've followed the directions, I've watched the Youtube vid, I've tried to read as many posts as possible. All to no avail. Perhaps somebody could jump in here and tell me what I'm doing wrong.

I purchased a powered OTG cable from Amazon. I believe it was one that was linked in one of the tutorials. I have a very early serial Chromecast (3613) that I just recently opened up. It has never been hooked up to my computer or the internet. So I should be good to go. Yet I cannot seem to even get Flashcast set up properly.

1) I installed Win32 Disk Imager

2) I downloaded Flashcast v1.1.1

3) I used Win32 Disk Imager to flash the flashcast-1.1.1.bin file to my 1GB jump drive

4) Using a micro-usb charger, I hooked the USB drive to the OTG cable, plugged the OTG cable into the power and connected the OTG to my Chromcast while holding down the button.

5) The Chromecast light started pink, then went to red. While it was red, my jump drive light flashed showing activity.

6) After about 10 seconds, the Chromecast light turned white and the activity on my jump drive stopped.

7) The Chromecast light then turns red again and STAYS RED. No further activity showing on my jump drive LED.

According to the video, it appears that after step 6, the Chromecast light turns white and there is still USB drive activity. That does not happen with mine. I cannot access the drive in my computer as it tells me the drive is not formatted. If I look at the drive manager, it appears that there is a 20MB partition on the drive. But I cannot access it. I have tried two different USB drives, a 1GB and a 16GB, I have tried it on a Windows Vista and an XP machine. I simply cannot get it to work.

What am I doing wrong?!? Is there any other way of formatting the drive properly so that I can move on to updating my Chromecast with the Eureka ROM?
[Google Chromecast] wptski:
Read the Rootable thread as your CC may not be in the range of rootable serial numbers.
[Google Chromecast] Creig:
"Anything with serial number starting 3921 and below. These should be root capable"

It's definitely in the range. Mine is 3613 and the earliest in that thread were 3617 and 3615.
[Google Chromecast] bhiga:
You let the button go after Flashcast appeared right?

Does the USB stick mount on a computer after the initial run?

You can also check my Rooting with Flashcast Mini-FAQ (find one of my signatures) flowchart.

Sent from a device with no keyboard. Please forgive typos, they may not be my own.
[Google Chromecast] Creig:
Yes. Once the Flashcast appeared, I let the button go. After the Chromecast led switches back to red, it stays there forever. I tried removing the thumb drive and putting it back in my computer, but I am unable to do anything with it as it is reported as unformatted. I've also tried following the video tutorial and letting go of the button once the thumb drive activity light starts flashing. Same result.
[Google Chromecast] bhiga:
I had that behavior with a USB stick that was "on the way out" (going bad).

Try a different stick if you have one. Otherwise try testing your stick with Chkflsh

http://mikelab.kiev.ua/index_en.php?page=PROGRAMS/chkflsh_en

Be sure to right click and Run as Administrator.

Sent from a device with no keyboard. Please forgive typos, they may not be my own.
[Google Chromecast] Creig:
I attempted to flash my Chromecast with both my old 1GB USB drive and a new 16GB Sandisk just to eliminate the possibility of a bad flash drive. So I doubt that's the issue here. But I will run the scan when I get home after work just to make sure.
[Google Chromecast] wptski:
There was a post "somewhere" about some very low serial numbers being prototypes. I wonder if your problem might be that you have one of them??
[Google Chromecast] bhiga:
Hmm... That leaves

faulty/inadequate power (unlikely, but still worth testing)

I remember that too, ahh, found the thread

ddggttff3 said all Chromecasts should be rev 3.30 and therefore the same platform.
[Google Chromecast] Creig:
No love in Mudville yet. I ran the ChkFlsh utility on my 1GB thumb drive. The full pattern set. No errors. I tried a different power supply. No difference.

When I hold down the button on the Chromecast and plug in the power, I get the few colored squares near the middle-right of the TV screen. Then they go away and display the FlashCast red/white screen. And the Chromecast led stays red after the 10 second period. When I remove the flash drive and just plug the Chromecast into the TV, it boots into what I assume is the stock Chromecast setup screen.

Is there any other utility I can use to flash the .bin file for Flashcast other than Win32 Disk Imager? I'm thinking that a different utility may fix the problem.
[Google Chromecast] bhiga:
Colored dots are good, so is the fact that FlashCast comes up. That means your Chromecast should be rootable.

Really sounds like it's trying - but for whatever reason it's failing on the format.

So don't give up just yet! :)

More ideas:

One or two others said they had to hold the button down through the entire process (which usually should not be the case), for whatever reason. It's worth a try at least.

Try writing the USB stick on a different USB port (or computer if you can).

It could be an iffy OTG cable. Oops, I had meant to say that in the last post but got interrupted and forgot...

So... If you have the right parts, try an alternate OTG.

Try a different stick writing method. Rooting with FlashCast Mini-FAQ has a flowchart and links to a method to write the USB stick with dd from Android that you can try.

Keep going, we're so close!!
[Google Chromecast] Creig:
Thank you for sticking with me on this. Just to be specific, this is the OTG cable I purchased to flash my Chromecast:

http://www.amazon.com/gp/product/B00CXAC1ZW

1) I tried holding the button down for 30 seconds after applying power, to no avail.

2) I tried multiple ports on my computer to flash the thumb drive (Vista 64 bit)

3) I tried flashing the drive from an older computer (XP 32 bit)

4) I just tried a different program to flash the drive - USB Image Tool found on Alex's coding playground. Same problem.

I flash the .bin file and end up with a 20mb partition on my drive that is not recognized by my computer and I cannot access anything else on the drive. It had originally been FAT32. I believe this behavior is normal. For some reason, my Chromecast simply does not want to accept the image.

I'm wondering now if my OTG cable is the culprit. It gives power to the Chromecast, it shows USB drive activity once the Chromecast starts. If it does both of those, I have to assume it's working properly. But I've tried two different USB drives, two different computers and now two different programs to flash the .bin file. The only things I haven't tried multiples of is the OTG cable and the Chromecast itself.

Edit - Do I have to start with an earlier version of Flashcast or can I flash my stock Chromecast right to version 1.1.1? I just tried re-downloading the .bin on the off chance that it was corrupted on my computer. Still no go.

Edit 2 - OMG! Finally! The re-downloaded .bin didn't work when flashed on my 1GB drive while using the USB Image Tool. Just to be thorough, I tried my 16GB Sandisk again and for some reason it seems to have gone through! Windows now recognizes my drive as Flashcast!

I proceeded with the flash instructions, allowed the Chromecast to flash for 10 minutes. When I rebooted the Chromecast, the startup screen changed from the standard Google animation to the Eureeka animation.

I assume that I'm done? Finally? :)
[Google Chromecast] bhiga:
LOL I took way too long to respond.

YES!! You're good to go now!!! :D :good:

Remainder is irrelevant now, but I'm leaving it in case it helps someone else...

Yup, looks like the exact same cable I've been using, though I got mine off eBay, probably all comes from the same place.

You're correct in your assumption about writing the disk image. It sounds like that's happening normally. It writes the 20 MB unreadable (to Windows) partition. FlashCast's first boot is supposed to partition and format the remainder of the space as FAT32. Seems that's the process that is failing for some reason. The logfile would normally help us diagnose, but it gets written to the FAT32 partition which at this point doesn't exist yet. :rolleyes:

It shouldn't matter, but I'm grasping at straws so... maybe it's a power sequence.

Here's how I've been doing mine:

Disconnect power from OTG cable if connected

Plug OTG cable into Chromecast

Plug USB stick into OTG cable

Hold down button while plugging power into OTG cable

It takes a little bit of dexterity to plug the MicroUSB in one-handed, but I can do it pretty reliably if I hold the power MicroUSB with thumb and forefinger, put the OTG connector in the palm of my hand and bring the power connector close enough so they're touching and stay aligned (but not connected) before using the other hand to hold the button.

Beyond that, I'm really stumped and we'll need tchebb to to help with diagnosing from ADB via wireless connection (the WiFi connect info is displayed on the FlashCast screen).​
[Google Chromecast] Creig:
Just to try and be helpful to anybody else having issues flashing the Flashget .bin file, I was finally successful by using the USB Image Tool/ at Alex's coding playground. So that would be an alternative to using the usually recommended Win32 Disk Imager.
[Google Chromecast] Creig:
Thanks a lot for your help bhiga!
[Google Chromecast] brs608:
I just got screwed. Somehow or another while trying to update from pwncast 13300, CC has reset and updated itself to stock build 15250. No root exploits found since release of SDK?
[Google Chromecast] wptski:
Did you flash the Eureka ROM? There is a stripped down new version posted so if you used that one, the Chromecast app will show the newer version.
[Google Chromecast] brs608:
Nope. Wasn't able to flash it. Originally flashed pwwnedcast. Just got my powered otg cable today , so I wanted to update it. The USB stick I used had since been reformatted, so I made one w 1.1.1. Tried to boot from USB and didn't work. Just the startup issues splash screen. Tried a few different times. I guess one time I may have let it boot regularly and didn't see pwnedcast screen somewhere in this process. Unhooked internet and booted up, checked w the app and saw build 15250.
[Google Chromecast] bhiga:
Are you certain you had PwnedCast installed?

Once it's there, it's there and it'll survive reboots and factory resets, so it's not like you can let or even force it to boot to a normal auto-Google-updating ROM. You'd have to load a standard auto-Google-updating ROM onto the stick and flash it with FlashCast for that to happen.

Unless Google found a sneaky way to update outside of the standard method which is removed from PwnedCast and Eureka-ROM.
[Google Chromecast] brs608:
I was getting the pwnedcast splashscreen at the minimum.
[Google Chromecast] bhiga:
Then it should have auto-updated to Eureka-ROM, and Team Eureka is now pushing the 15250 update to Eureka-ROM so...

Try going to http://ip_address_of_your_Chromecast and see if you get the Eureka web panel. If so, you're still rooted. :)
[Google Chromecast] ddggttff3:
Do you remember which specific pwnedcast build of mine you were running? Also, when did you flash the chromecast with pwnedcast? did you leave this device plugged in all the time, or only when in use? Did you ever use the chromecast setup application on the device while on the pwnedcast ROM?

I will do some testing on my end to see if I can figure out what happened.
[Google Chromecast] brs608:
I'll dig around shorty. I think the file was 13300.zip

---------- Post added at 12:25 AM ---------- Previous post was at 12:21 AM ----------

When I first got the chromecast was between tgiving and Xmas. Flashed pwnedcast and stuck it back in the box as a "family gift". Then it sat up until about 3 days ago. Fired it up and watched a couple episodes of true detective on hbogo. Started looking at xda on Tuesday to see the latest for the CC. ordered otg cable on Wednesday from amazon. Cable came in so I made a new flashcast USB this afternoon and tried to boot from USB without success

---------- Post added at 12:30 AM ---------- Previous post was at 12:25 AM ----------
[Google Chromecast] bhiga:
Definitely check if the web panel is available first. Maybe you just got lucky and yours was one of the first to update to the 15250 build of Eureka-ROM.

Otherwise...

If you boot holding the button with no USB stick attached, do you get the multicolored dots on the TV? (BTW the dots are single pixels so it'll be mostly a black screen)

If so, your bootloader should still be vulnerable and you can try proceeding through the steps on Rooting with FlashCast Mini-FAQ.
[Google Chromecast] tchebb:
Unfortunately, we only started pushing the 15250 Eureka-ROM build after [MENTION=5558034]brs608[/MENTION] made his post. Personally, I can't think of any way that a vulnerable Chromecast running PwnedCast 13300 could have been automatically updated to an official OTA, so I'm very interested in seeing what happened here.

If you didn't have a powered OTG cable previously, how did you initially flash PwnedCast?
[Google Chromecast] brs608:
I tried to access the webpanel and couldnt. Thats what prompted me to upgrade from the build I had. Tried again after I had problems just to see. Didn't work. I was just trying to boot from USB to format so I could load the newest eureka ROM and flash. Never made it that far. Tried Alex's USB tool and win32diskimager just in case. As for the cable originally, I made one. But once finished I removed the power input to be an unpowered otg to use offshore w my nexus 7.
[Google Chromecast] bhiga:
:( Freaky. :confused: and :eek:
[Google Chromecast] tchebb:
And you're absolute sure that PwnedCast was there initially? You saw the "PWNED" boot animation?
[Google Chromecast] brs608:
Yes. I've been having the pwned bootani since before Xmas. And was there Tuesday until now. I don't leave it constantly powered due to an HDMI port on my TV going out. Only plugin CC and usb when I'm actively using.
[Google Chromecast] tchebb:
We've been discussing your issue, and we think we know what happened:

Before [MENTION=2212097]ddggttff3[/MENTION] released PwnedCast, he maintained a separate, untitled ROM. The second (and final) release of this ROM had the "PWNED" boot animation, but did not have the custom recovery that PwnedCast has. Since your Chromecast didn't have the custom recovery (indicated by the "startup issues splash screen" you mentioned), we assume that this is the ROM you initially tried to flash when you purchased the device.

We believe, however, that instead of downloading the full ROM mod as you intended, you mistakenly downloaded the "Custom Boot Animation" mod under the "Extras" section. After flashing this mod with FlashCast, you would have seen the "PWNED" boot animation; however, nothing else would have been modified and Google's updater would have still been present. So when you turned the device on three days ago, the updater performed it's regular check for updates, found one, and updated the device normally, patching the bootloader in the process.

This is the only possible course of events we've been able to come up with that would have resulted in what you report. If you have reason to believe this isn't what happened, please let us know.
[Google Chromecast] brs608:
Its quite possible. I will post the file that I have saved on PC after I finish packing for vacation.
[Google Chromecast] brs608:
By the time I was done I passed.out. I'll post the file next weekend
[Google Chromecast] ruscik:
Hello all. Having issues with chrome cast.

So got it serial starts 3922. As result went for a root attempt. Built a USB otg. Cable works as tested with my nexus 7. Done the instructions so did a write of flasher 1.1.1 to my USB stick using win32diskimager. All good. Boot it all up with button pressed in, get white led that changes to red asap. Stays red about 10 seconds then white and device reboots. All good. Next step put eureka rom on card, as before start with button pressed in. Chromecast boots to red flasher screen with info if White led all ok flashing if red well problem. Have white led for about 10 min then device reboots. All good so far. When it does that I can see word Chromecast on screen (bottom) for 2-3s then my TV switches to power saving as it does not see him input anymore. Led on Chromecast Stays White. When I force display to come back on nothing is displayed and seconds later sleep mode again. If I reboot Chromecast I see same word at bottom as before and TV goes to sleep. Any idea why?
[Google Chromecast] bhiga:
Sounds like your flash went fine.

What TV do you have?

Is HDMI CEC control (Simplink, BRAVIA Sync, Viera Link, etc) enabled for that input?

Is there a receiver or other device between the Chromecast HDMI and the TV's HDMI port?

Are you using wall power or plugged into a TV USB port? Wall power is recommended in general and especially for troubleshooting.
[Google Chromecast] ruscik:
Very old LCD. Phillips with just hdmi ports (not fancy). It does not even autoswitch to a live port you have to select which hdmi manually. Using pc's USB 3.0 with additional power supply to it for tablet charging. Will try with power supply.

Had a look at log on USB key and last entry is restarting

---------- Post added at 12:29 AM ---------- Previous post was at 12:17 AM ----------

No, no change with power supply

---------- Post added at 12:35 AM ---------- Previous post was at 12:29 AM ----------

Got it working. With so old Ltd TV make sure you power it on/off during 1st setup so it forces chrome cast to match to advertised default resolution of TV (not what chrome cast is wishing)

Sent on the move from HTC One