yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] Clockwork Utility:
How to mod an "updated Chromecast"

Had a brainwave

I have a feeling all that Google have done is "write protect the bootloader" when applying their internet based updates. Now

it maybe possible to boot your Flashcast with a usb, and script that changes the attributes on the bootloader files removing

the read only attributes on both the files and folders. Since you know the source of the bootloader directory structure

can you try to include in the first lines of your script to turn off read only before attempting a dump of the image you are

applying?

Have a hunch also that the Allcast.apk application Koushik Dutta created should work on a Flashcast enabled Chromecast because the autoupdate feature is switched off on the re-image of the device correct? Allcast

allows an android device to stream local content from his device
[Google Chromecast] Drabir Alam:
Let us know if it worked

Waiting with bated breath to know what happens
[Google Chromecast] smartphoneguy:
As has been said many times, Allcast no longer works because it is blocked on the server side. It doesn't matter what firmware you have, old, new, rooted, update blocked, etc. Will not work.

As to your first suggestion, I'm pretty sure it isn't that easy.
[Google Chromecast] tvall:
All Google has done is enable signature checking on kernels. Flashcast cannot boot because Google hasn't signed it.

In the exploitable bootloader, it allowed kernels to boot even if they aren't signed. I don't see how that could have been done by accident.

And on boot, the chromecast fetches a list of apps from Google. This is separate from any firmware updating. It is also done over SSL, so that adds an extra layer of complexity. We cannot just spoof a response, we have to use a SSL certificate the chromecast will accept. This can be done, but no one has started on it. I would, but I have a wedding and a move to a different state both about a week away.
[Google Chromecast] tchebb:
I'm sorry, but your "feelings" and "hunches" seem to be entirely disconnected from reality. The second-stage bootloader's write permissions have not been altered since the Chromecast's initial release. It has always been read-only to the normal stock kernel and writable to the recovery kernel. Additionally, it is intentionally made read-only in the FlashCast kernel because modifying it in any way would likely brick your device permanently. This is because the first-stage bootloader (which is baked into the SoC and can not be modified) does a signature check on the second-stage bootloader before every boot and will not boot the device if the signature verification fails. I can include anything I want in "the first lines of my script" and it will have absolutely no effect. FlashCast is unable to execute a single line of code (kernel or otherwise) on a patched device because the bootloader's signature check fails. If I were able to run FlashCast on a patched device, I could simply write the old, vulnerable bootloader back to the bootloader partition and be done with it.

AllCast does not work on any device with any firmware version at this time. I and others have stated this repeatedly elsewhere in this forum. The change is on the server-side, so the Chromecast's build version is irrelevant.
[Google Chromecast] ahecht:
Flashcast by itself doesn't root anything. If you just did the Flashcast setup and didn't then use Flashcast to flash a rooted image you would still have the stock firmware and your chromecast would receive OTA updates.
[Google Chromecast] kjwilso:
Are new Chomecasts updated?

Hi,

I have FlashCasted a few Chromcasts with my setup and they are all working fine with the PWNED image.

A friend of mine bought one and asked me to FlashCast it for him which should not be a problem since I have already done two with the setup I have.

This was a sealed Chromecast when I got it and I got my FlashCast image loaded and connected the cables and tried to FlashCast the device. When I connect it and hold the button it the USB drive starts to flash like its reading the image but then it stops and the light stays red. No images are displayed on the screen and it sits there forever never loading.

If I don't hold the button the Chromecast will boot without issue. I have tried formatting and downloading new FlashCast images and even other USB sticks.

Is this the behavior of a Chomecast that's been updated and can't be FlashCasted? Like I said this was a sealed in box ChromeCast when I got it and I know my setup worked before as I just FlashCasted another one last week.

Any ideas?

Thanks!
[Google Chromecast] tchebb:
Yes, that is the expected behavior for an patched device. Your friend may have bought a unit which was already running the new firmware from the factory. Unfortunately, there's nothing you can do at this time to root a patched unit.
[Google Chromecast] kjwilso:
Thanks for the reply. I assumed that was the case but was not 100% sure they were shipping with updated firmware yet. Sucks for him but what c can you do.
[Google Chromecast] hiep256:
Running chromecast image in qemu

Hi - is this possible? Any instructions on how to do this with the flashcast bin?

Many thanks,
[Google Chromecast] SherlockHolmes2013:
Can Chromecast be made to work like Miracast with screen mirroriing?
[Google Chromecast] jamesking420:
Are all flashcast drives the same? Like, if I make a flashcast USB stick using one chromecast, can I use it OK to flash another Chromecast?

Or are they locked to the device they were "created" on?

Thanks,

James
[Google Chromecast] tchebb:
They're not device-specific. Using one FlashCast drive with several devices will work just fine.
[Google Chromecast] iandroo888:
what do we do after its flashed now o.o ?
[Google Chromecast] eyetek:
I bought two Chromecast units factory sealed with consecutive serial numbers, I have installed Flashcast and flashed the Eureka image to the first device without problems. I went to go through the same process with the second device and I got the Flashcast screen but when it went to reboot from that screen it got stuck on the black screen with "Starting Chromecast..." and the USB stopped flashing and went dark.

I have tried to boot up the Chromecast on it's own and it gets stuck in the same spot.

I have tried to do a factory reset by holding down the button for over 30 seconds with no success, of course the Chromecast app does not recognize the device.

Any ideas?
[Google Chromecast] ddggttff3:
This is just a flashing tool used to flash other ROMS, not a firmware in its self.

Hmm, thats interesting. So when you try and boot it, it goes to the Starting Chromecast... and then a black screen? Is that with, or without, holding the button down?
[Google Chromecast] eyetek:
If I am using the USB to install Flashcast I get the Flashcast screen then it goes to a dark screen with "Starting Chromecast...." at the bottom of the screen and it stays there. The USB which was flashing up to that point goes dark and acts like it is no longer powered.

If I attempt to plug in the Chromecast into the TV and boot it with its power cord and no USB device it goes directly to the "Starting Chromecast..." and stays there.

Booting the device either way ends with the same dark screen with the "Starting Chromecast..." at the bottom and stays there until I unplug it.
[Google Chromecast] ddggttff3:
Strange, sounds like it may be a hardware issue, or it came from the factory with a improper flash. I'd wait tho to hear [MENTION=2789381]tchebb[/MENTION] has to say.
[Google Chromecast] eyetek:
Then that's what I will do....
[Google Chromecast] tchebb:
I have just released FlashCast version 1.1. A changelog and downloads are available on GitHub here.
[Google Chromecast] tchebb:
If you can still boot FlashCast from USB, try re-running it with the rooted image. There could have been some error flashing the first time. I'd also be interested to see the contents of the FlashCast log files on the drive. Would you mind posting the one from the flash which failed? (Probably the one with the highest number, unless you've used FlashCast again since.)
[Google Chromecast] eyetek:
I want to thank you first off, I was able to flash the rooted image to the chromecast! Not sure why the device always got stuck on the "Starting Chromecast..." but at this point all that matters is that it is rooted.

I saved the log file from the failed boot and will attach it for you to look at, would be interested to hear if you are able to see what the problem was.
[Google Chromecast] mcpdigital:
Installed it already. Everything seems fine. I had a doubt about installing flashcast 1.1 and then installing eureka_image.zip again, but I'm not sure it was needed. I did both installs.

Thank you.

MCP
[Google Chromecast] verby25:
need to flash a mod

Can someone tell me the steps ... what to do after I do flashcast?

It says: To root, you need to flash a mod

Do I need a second memory stick and put mod there?

Do I unplug first everything and put mod on flashcast usb and repeat as with flashcast?

Reading here I figure it out that I still have to 'do something' after I install flashcast.

sorry... I'm totally new into this and would appreciate any help.
[Google Chromecast] Bajanman:
After you get pass the flash cast. Then you need to put the drive back into the PC then. Load the rooted ROM on there.

Find it here: http://xdaforums.com/showthread.php?p=47203241

And go thru the steps again. But read the OP..
[Google Chromecast] ahecht:
How do we use the multiple mods feature? Do they not all have to be named eureka_image.zip if they're in the flashcast-mods directory?
[Google Chromecast] tchebb:
They do not. FlashCast will flash every mod in flashcast-mods in alphabetical order. Just make sure that a eureka_image.zip file isn't also present in the root directory, or else only it will be flashed.
[Google Chromecast] mcpdigital:
This is the cable I used
[Google Chromecast] ralphkaz:
can anyone confirm if this cable would work:

http://www.ebay.com/itm/Micro-USB-H..._USB_Cables_Hubs_Adapters&hash=item3cd7de661c

thank you!
[Google Chromecast] Bajanman:
Yes it should:thumbup:. This is the one I have:
[Google Chromecast] -Lawless:
All rooted and Romed. thanks!

Now just hoping XMBC may happen someday!
[Google Chromecast] Rolling Pank:
Pipo

Nice work !

Gonna have a try with my Pipo M6pro.

Thx~
[Google Chromecast] Zuckstone:
Don't think that will work without additional adapters.

It has USB A MALE

You need cable with:

micro USB female

micro USB male

USB A FEMALE You have to plug the Jump drive into it.

Look at photo Bajanman posted. That's what I have too.

This should work

http://www.ebay.com/itm/K1BO-USB-Type-A-Female-to-Micro-USB-Male-Host-OTG-with-Micro-USB-Female-Y-Cable-/251334351959?pt=US_Cell_Phone_PDA_Cables_Adapters&hash=item3a84b1dc57
[Google Chromecast] alvin90:
Hi guys..

IT newb here.. well I just flashed my chromecast, but when I plug in my chrome cast, it shows pawned.. then black screen.. I haven set up my chromecast yet.. something wrong happened? I cant do anything with my chromecast now..

---------- Post added at 02:06 AM ---------- Previous post was at 01:08 AM ----------

Plus the led white light keeps flashing, even when I plucked in the normal usb cable provided in the chromecast box.
[Google Chromecast] jamesking420:
Hi,

I have flashcast v1.0 on my jump drive. Is there a simple way to upgrade to v1.1, or is it a case of going through the whole process again?

Thanks!

James
[Google Chromecast] alvin90:
Found the problem, the mod works just nice, its my TV that is causing the problem. Black screen on my wide inch LG TV but works on my small little 3 yo Akira TV.
[Google Chromecast] Bajanman:
I was in the same boat as you. Just download the new 1.1 version. 1st. Delete the old Rom on there!

Then copy the new version on there. Then rename it to "eureka.zip" just as the same name as the previous version you had on there;):cool:. Then go thru the same steps too load the new Rom ver 1.1

Hope that helps you out...
[Google Chromecast] amadib:
[deleted] ..
[Google Chromecast] B-Blue:
So the upgrade process is totally different? I don't have to use win32diskimager to write the .bin file to my flashcast drive? I'm currently on v.1.0 and can't get it to update to v1.1.

Here's what I did:

1- Downloaded the latest version.

2- Renamed "flashcast-1.1.zip" to "eureka.zip" (I also tried "eureka_image.zip").

3- Plugged in USB-OTA cable (followed the instructions in the OP).

4- Red LED :(

What am I doing wrong? :confused:

EDIT: I also tried writing the .bin file inside flashcast-1.1.zip to my flashcast drive using win32diskimager, didn't work.
[Google Chromecast] MadBob:
I just followed the original flash instructions, wrote the BIN to the drive, EJECTED THE USB SAFELY (note this is crucial) then plugged it in with the button pressed.

After which I plugged back into PC and copied the KyoCast file, EJECTED THE USB SAFELY, and flashed the Whitelist workaround.

Now I also have Fling working.
[Google Chromecast] Bajanman:
Ok thought I was on the pwnd cast thread.

Anyway the same way you did it the first time is the same way this time also.

Yes you need to use the win32diskmanger. To transfer it to the usb. Then flash it thru the Chromecast and you should have a updated usb stick with flashcast 1.1. Which is needed to flash the new version found HERE:

http://xdaforums.com/showthread.php?p=47203241

Sorry for the confusion... hopefully everything goes smoothly for you now..
[Google Chromecast] mikeones42:
Initial flash failed

Not sure if I missed a step here... the instructions seem straight forward enough but I can't seem to get this flashed.

I downloaded the latest flash cast and dd copied the bin image to my usb drive.

dd bs=4M if=flashcast-1.1.bin of=/dev/sdb

The chromecast boots into flash cast and I see the status light stays white. After a minute the chromecast reboots, but it boots into firmware 12072. Here is the log from the USB. Do I need to rename the file to eureka? Not sure what I am missing.

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.9CKyve
Flashing mod at /tmp/tmp.9CKyve
Mounting cache (mtd4) at /tmp/tmp.TBaRoK
Removing temp-ota.zip and ota.zip from cache partition (/tmp/tmp.TBaRoK)
Unmounting /tmp/tmp.TBaRoK
Removing temporary mod directory /tmp/tmp.9CKyve
Mounting /dev/sda1 to /tmp/tmp.TFogo4
Opened log file /tmp/tmp.TFogo4/flashcast-logs/flashcast-1.log
SETUP FAILED: No images found on /dev/sda1
Unmounting and removing /tmp/tmp.TFogo4
[Google Chromecast] ddggttff3:
flashcast is just the tool that is used to flash things, it does not install any ROM by its self. you must use it with a firmware build, such as mine. Link: http://xdaforums.com/showthread.php?t=2515799
[Google Chromecast] thorflea:
Just ordered new Chromecast

Looks like they are comming shipped with the bootloader updated. I just gat a new one and Flashcast 1.1 says its not updateable. :(.

So bumbed about it. is there any hope?
[Google Chromecast] ddggttff3:
there is always hope, but currently there is no root method for devices that come updated.
[Google Chromecast] thorflea:
Just ordered new Chromecast

Thanks for the update. Do we know what they changed that prevents moding the Chromecast? Or is that the problem?

:crying:
[Google Chromecast] ddggttff3:
they enabled signature checks on all images which includes booting from USB, so only google can use USB booting.
[Google Chromecast] guy4jesuschrist:
There may be hope. You might be able to take it back and look through all of the stock at your local store(s), to find a box with a serial number within a certain range. I did some guesswork and found one on my third try.

For more clarification, please refer to my post here: http://xdaforums.com/showthread.php?p=47475311
[Google Chromecast] Sean09:
Read the thread and am stumped. Have 12072. Used the disk image to make a Usb of flashcast 1.1. Boots to flashcast welcome then led stays red and won't reboot. Confirmed the key is unreadable on a pc.

Did I miss something? Any ideas? I assume it's supposed to reboot at which point the key can be used on pc at which time I can install pwncast. Help please!

---------- Post added at 09:03 PM ---------- Previous post was at 08:19 PM ----------

It appears it just won't format my Usb key. Tried 2 now.

Edit, worked with the third key I tried no issue.
[Google Chromecast] tchebb:
Interesting. I haven't seen this issue reported before. Do you mind telling me what brand and model USB drives you were using that didn't work?
[Google Chromecast] Sean09:
The first was an 8gb staples branded one. Second was an old 1gb cruzer with a frosted end that flashes green when plugged in. Both were successful in converting and booting but wouldn't format. Once I tried the third it worked.

As a side note neither of the first two will flash the bin without an error anymore, and neither work Windows nor let me do anything in drive manager.
[Google Chromecast] lukian:
Can confirm Cruzer Mini 1.0GB (with green LED on the end) failed to format (and didn't seem to display anything on screen, but appears to have flashed at least one of my chromecasts).

A Kingston 4GB DataTraveller was 'formatted' properly by the process for adding an image zip.
[Google Chromecast] wptski:
That's exactly the same problem I had. Once the bin file is placed on a USB drive, you can't try to put the bin file it a second time as it errors and if it fails to flash your CC or you decide not to flash the CC, Windows can't format it. Nothing seems able to format the CC as FlashCast can.

I used a regular 1GB Cruzer.
[Google Chromecast] killall:
I would be surprised if GParted couldn't format it.
[Google Chromecast] tchebb:
The problem is Windows' poor handling of flash drive partitions. [MENTION=2212097]ddggttff3[/MENTION] figured out how to force Windows to reformat a FlashCast drive from the command line the other day. When he wakes up tomorrow, I'll see if I can get him to post instructions. Sorry for the inconvenience.
[Google Chromecast] Sean09:
Does that mean I may be able to recover the flash drives that didn't work?
[Google Chromecast] ddggttff3:
Have a Tutorial Video:

http://www.youtube.com/watch?v=NRsUuiuWQMM

Not my best work, but was somewhat rushed. Hope that's OK.

Commands Used in CMD:

diskpart
list disk
select disk * (where * is your jump drive disk number)
clean
convert mbr
create partition primary

Like I said in the video, make sure you select the drive letter of your jump drive! If you select the wrong disk you can accidentally wipe all of the data from your computer. Me, XDA, and team eureka are NOT responsible for any data loss.
[Google Chromecast] wptski:
Thanks and I was about ready to post a link to another Youtube video on "How To Do Just That" but your video is better! :good:
[Google Chromecast] Sean09:
Thanks for the tutorial, but neither of the first two flash drives are even showing up when I list them.

EDIT - from reading that might be because I am on XP. Will try 7 later.
[Google Chromecast] wptski:
Here's another much longer video on using Diskpart that I was going to post earlier. It has a few extra steps but I don't know if that means that it's any better.

https://www.youtube.com/watch?v=8TQ1RpToSsk
[Google Chromecast] cadguycad:
(im hoping this isnt a stupid question!)

Could google update the chromecast app on the playstore to affect rooted chromecast i.e to somehow block them or force a remote update to remove flashcast?

Just wondered after i blindly updated the app and was about to use it.

just to be clear i have no issues regarding this but wondering if this is technically possible for google.

thanks
[Google Chromecast] tchebb:
It is technically possible for Google to remotely update a device running the PwnedCast rooted ROM, but doing so would not be easy for Google (they couldn't go through their normal OTA framework since rooted ROMs disable that) and I doubt they'd bother, considering the relatively few rooted devices in existence. It also wouldn't require an update to the Play Store app; it could be done fully remotely. If you want to remove this possibility, you can flash KyoCast on top of the rooted ROM, which prevents the device from interacting with Google's servers in any meaningful way.
[Google Chromecast] wptski:
Did you ever get your all your flash drives back to a usable condition?
[Google Chromecast] mikeones42:
Hello,

I was able to get flashcast installed on a USB drive and I have PWN cast running on one CC. Now that I have the USB drive setup for flashcast, I though it would be pretty simple to flash a 2nd CC. Here is a run down on what I have tried to this point. Note, I am using the same USB drive that was used to flash the first CC.

1. Tried with the original USB to flash a 2nd CC. The FlashCast screen appeared briefly and the CC rebooted. The light on the CC stayed red and no log file was written to the USB drive.

2. Started from scratch and formatted the USB drive. The copied the bin file (flashcast-1.1.bin) back to the USB with dd.

3. Retried to flash the CC but this time I don't see the FlashCast screen. The USB drive label was not updated to "FLASCAST" and the only file that is on the USB drive is in the root folder named "init_partitions". When I try to boot the CC with this USB drive the light on the drive flashes once and the CC reboots after a few seconds.

Any thoughts on how to resolve this?

Thanks!
[Google Chromecast] bhiga:
First thing I would try is starting from scratch and putting FlashCast on the USB drive again via dd or win32diskimager
[Google Chromecast] wptski:
Yes, Flashcast on the USB drive is a one time use, if it works, it gets erased.
[Google Chromecast] tchebb:
That is not correct. FlashCast is intended to remain on the flash drive after flashing and be reusable. If it's not doing that, please file a bug report at FlashCast's GitHub repository.
[Google Chromecast] wptski:
Wait a minute! After Flashcast is put on the USB drive, Windows won't read it. After the Flashcast is installed on the CC, doesn't it format the USB drive, labels it as Flashcast, isn't the bin file erased? I assumed if the USB drive is formatted the bin file is erased when formatted.

After installing the PWNED! ROM, I didn't see anything besides the zip and a log file.
[Google Chromecast] tchebb:
FlashCast installs itself to partition two of the USB drive, which is actually located at the beginning of the drive. When it's first booted, it expands partition one to fill the rest of the drive and formats it as FAT32. Partition two is small enough that you won't notice the size difference of the FAT partition on any reasonably-sized flash drive. If you open any partitioning program and look at the flash drive with it, however, you'll be able to see the second partition, which holds the FlashCast binaries and root filesystem.
[Google Chromecast] wptski:
Hmmm, so it's still there and I assume unless DISKPART is used? I'm not clear on one point. The same USB drive that may have a (eureka_image.zip) and log file on it can be used to install Flashcast on another CC but would or wouldn't it install the zip file as well?
[Google Chromecast] tvall:
Flashcast is installed on the USB drive. Flashcast installs the eurika_image.zip on the chromecast.
[Google Chromecast] wptski:
My question is, does this mean that one can use the same USB drive, as is, to install Flashcast on another Chromecast and would it ignore or install the eureka_image.zip that's on it?
[Google Chromecast] tvall:
Flashcast isn't installed on the chromecast. Its written to a flash drive and used to install mods, distributed as zip files, on chromecasts.
[Google Chromecast] guy4jesuschrist:
I think the question being asked is, if a FlashCast prepared USB drive can be used more than once to set up another CC with FlashCast after already using it to set up one. Or, do you have to set up the drive again by formatting it, using dd to install the flashcast.bin to the USB drive again, and then set up the 2nd CC?
[Google Chromecast] wptski:
Why is the USB drive connected to the Chromecast at the first step then a zip is copied to it?

If there is a reason then whatever USB drive one use is now for that use only??