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

Kyonz · Dec 21, 2013

stewwmann said:
Very cool,I had not updated since v1 so I had to update Flashcast first, but everything went silky smooth....:laugh:

Good to hear! I'm hoping this release gives people enough of a reason to update their old devices as we bring in new features and ease of management

otaku888 · Dec 21, 2013

What a great surprise to wake up to. OTA went smoothly with no hiccups.

Thanks so much for your hard work and dedication!

:good::good::good::good:

Rooksx · Dec 21, 2013

I had set my Chromecast's DNS to Unlocator using the flash method before the update. After the update, I went through the web-based portal and disabled DCHP, set the DNS to Unlocator, applied updates and rebooted the device. However, I have not been able to load any Netflix content from countries other than my own (UK) on the Chromecast. Loading content from US, Denmark, Brazil works fine on my computer and my iPad.

I've checked the DNS settings on the web portal multiple times and it's definitely on Unlocator. I also tried switching to UnblockUS. Foreign Netflix content still doesn't load on the Chromecast although it works fine on my computer.

Can I still use the flash method to change the DNS to Unlocator or will that not work anymore?

Thanks

jules_winnfield · Dec 21, 2013

I can't access the web panel. Tried a few different browsers, disabled firewall and still nothing. I have Tplink router running ddwrt, chromecast has assigned a static ip address. Any ideas what I can do would be greatly appreciated.

Many thanks to Team Eureka for developing this ROM!

Kyonz · Dec 21, 2013

Rooksx said:
I had set my Chromecast's DNS to Unlocator using the flash method before the update. After the update, I went through the web-based portal and disabled DCHP, set the DNS to Unlocator, applied updates and rebooted the device. However, I have not been able to load any Netflix content from countries other than my own (UK) on the Chromecast. Loading content from US, Denmark, Brazil works fine on my computer and my iPad.

I've checked the DNS settings on the web portal multiple times and it's definitely on Unlocator. I also tried switching to UnblockUS. Foreign Netflix content still doesn't load on the Chromecast although it works fine on my computer.

Can I still use the flash method to change the DNS to Unlocator or will that not work anymore?

Thanks

Hi Rooksx,

I've just identified this as an issue and am working on resolving it - in the meantime you can definitely reflash the old method - and I'll have this update to fix in an OTA very shortly (soon as I can find out why it's broken - I blame ddggttff3)

I'll report back in the next 30mins with the results of my testing for anyone else.

---------- Post added at 01:11 AM ---------- Previous post was at 01:05 AM ----------

Just found the issue, it's related to permissions on the /data/eureka folder.

If you run "chmod 777 /data/eureka" it'll fix it - however I'm just checking if the web panel has enough permissions to execute this (or you may need to adb into the device to fix it) we'll have a fix for this out asap - however this will get you up and running immediately.

Edit: you can run "chmod 777 /data/eureka" from the debug panel to resolve this issue immediately until we are able to release a fix for it - sorry for the issue it appears to have hit us from a change in the latest OTA that we are building off that we never saw.

---------- Post added at 01:22 AM ---------- Previous post was at 01:11 AM ----------

jules_winnfield said:
I can't access the web panel. Tried a few different browsers, disabled firewall and still nothing. I have Tplink router running ddwrt, chromecast has assigned a static ip address. Any ideas what I can do would be greatly appreciated.

Many thanks to Team Eureka for developing this ROM!

Hi Jules,

It sounds like there might be something in your existing data partition that is stopping the panel from loading - or some sort of weirdity. I'd suggest that you reset the device and re-set it up (you can achieve this by holding down the reset button on the device for ~10 seconds - without the usb connected) and it will reset to defaults.

Let me know how you get on.

jules_winnfield · Dec 21, 2013

I did factory reset twice, both with the button on the device as advised and via the chromecast app. Still could not connect to the panel. I then reflashed the rom using the standard USB/FlashCast method given in the op and everything is fine now.

cadguycad · Dec 21, 2013

updated 2 chromecasts with this awesome rom.....thanks very much

ddggttff3 · Dec 21, 2013

Kyonz said:
I've just identified this as an issue and am working on resolving it - in the meantime you can definitely reflash the old method - and I'll have this update to fix in an OTA very shortly (soon as I can find out why it's broken - I blame ddggttff3)

Actually I think this one goes to both me and Kyonz

The actual bug is that we didn't have /data/eureka created and permissions set at the right place, which means if you make changes before it was created through our script, it would save but not update permissions, thus DNS was unable to read the config.

Either way, I just pushed build V1.1 with the fixes. This will fix all panel/config related issues

It will push vi OTA system, so you can reboot your device to force the update check, or just download and flash the file from OP.

cancunia · Dec 21, 2013

Instructions for Image Flasing via eureka_image

Firstly - A BIG THANKS for all of the effort that went into this work, it's truly amazing stuff,

It took a while for me to get the image onto my Chromecast, mostly because I hadn't followed the instructions on the first post exactly...

I reformatted the Jump Drive after flashing the Flashcast image instead of just copying the eureka_image.zip to it. I'm guessing that the Jump Drive get's formatted somehow specially by Flashcast? When I tried to flash eureka_image in this way, it simply didn't work.

Just in case anyone else is having some issues, I thought it might help to point out that if you follow the instructions to the letter it works a lot better.

VaNTHoM · Dec 21, 2013

Chromecast won't boot with the latest build

Hi Guy's,

I've had a working Chromecast, with 13300 firmware including OTA. I just wanted to use the CC, but was confronted with a black screen. When a rebooted, I saw the logo from Team Eureka, which wasn't there before, so I Thought it was OTA updated (yes!). But the CC wouldn't boot completely, it left me with a black screen, I tried updating to 14975 manually, but that just gave me the same result; boot the device, Team Eureka logo blinking twice, and than the screen stays black.

To be able to use the CC, I have flashed the previous version of 13300 without the OTA. (And its working again) I will try updating again when there will be a new version.

I just thought I would share this information, if you like I can post a install log. Since nobody else is facing any issues, I guess it's just my luck

ddggttff3 · Dec 21, 2013

VaNTHoM said:
Hi Guy's,

I've had a working Chromecast, with 13300 firmware including OTA. I just wanted to use the CC, but was confronted with a black screen. When a rebooted, I saw the logo from Team Eureka, which wasn't there before, so I Thought it was OTA updated (yes!). But the CC wouldn't boot completely, it left me with a black screen, I tried updating to 14975 manually, but that just gave me the same result; boot the device, Team Eureka logo blinking twice, and than the screen stays black.

To be able to use the CC, I have flashed the previous version of 13300 without the OTA. (And its working again) I will try updating again when there will be a new version.

I just thought I would share this information, if you like I can post a install log. Since nobody else is facing any issues, I guess it's just my luck

Well my guess is it has to do with how google now detects your display. They changed the code that detects what resolution to output at, and I feel that may be the cause of your issue

This bug was reported by other users on the official OTA, so chances are that's the issue. Have you tried unplugging it from the TV while its on, and then plugging it back into its HDMI port? You may also want to do a factory reset and re-set it up to see if it fixes it.

wptski · Dec 21, 2013

ddggttff3 said:
Either way, I just pushed build V1.1 with the fixes. This will fix all panel/config related issues It will push vi OTA system, so you can reboot your device to force the update check, or just download and flash the file from OP.

The CC will check for updates on boot up but is this OTA like the previous one where they were staggered as not to overload your server?

ddggttff3 · Dec 21, 2013

wptski said:
The CC will check for updates on boot up but is this OTA like the previous one where they were staggered as not to overload your server?

For this OTA, we are actually doing a all at once OTA to get it out to people for XMas, and to test our VPS. So far the server has been doing fine, and the thing has enough bandwidth to handle it. All OTA's after this tho will go back to the rollout code though.

VaNTHoM · Dec 21, 2013

ddggttff3 said:
Well my guess is it has to do with how google now detects your display. They changed the code that detects what resolution to output at, and I feel that may be the cause of your issue This bug was reported by other users on the official OTA, so chances are that's the issue. Have you tried unplugging it from the TV while its on, and then plugging it back into its HDMI port? You may also want to do a factory reset and re-set it up to see if it fixes it.

Thanks for your quick response! I took your advise and started with a factory reset, then flashed the 14975 firmware. But the result remains the same, also unplugging and plugging it back in with the TV on didn't resolve it.

I will look for the thread of the OTA, and monitor whats happening there, thank you for pointing me in the right direction. :good:

ddggttff3 · Dec 21, 2013

VaNTHoM said:
Thanks for your quick response! I took your advise and started with a factory reset, then flashed the 14975 firmware. But the result remains the same, also unplugging and plugging it back in with the TV on didn't resolve it.

I will look for the thread of the OTA, and monitor whats happening there, thank you for pointing me in the right direction. :good:

No problem, you might want to report the bug to google. I know last time they were asking users for info on their TV/Tuner to try and fix the bug. https://groups.google.com/forum/#!topic/chromebook-central/edt0UTQqKxY[1-25-true]

wptski · Dec 21, 2013

ddggttff3 said:
For this OTA, we are actually doing a all at once OTA to get it out to people for XMas, and to test our VPS. So far the server has been doing fine, and the thing has enough bandwidth to handle it. All OTA's after this tho will go back to the rollout code though.

I removed my CC from my TV and powered it up via wall wart and watched it a bit to see if I could see it reboot. I caught a reboot so it updated but I can't connect to it via its IP.

Before if TV source is selected repowered up, I'd see PWNED! but I don't now, has that changed? I checked with the CC app to recheck the IP address, it does have new build with new home screen, etc.

It seems to boot/reboot differently!

ddggttff3 · Dec 21, 2013

wptski said:
I removed my CC from my TV and powered it up via wall wart and watched it a bit to see if I could see it reboot. I caught a reboot so it updated but I can't connect to it via its IP.

Before if TV source is selected repowered up, I'd see PWNED! but I don't now, has that changed? I checked with the CC app to recheck the IP address, it does have new build with new home screen, etc.

It seems to boot/reboot differently!

If you unpowered it during its update process, you will have to re-flash the ROM using Flashcast on a jumpdrive. You should now have a team eureka boot animation on the device. Also, if you remove power during flashing theres a good chance that it was interrupted during the flash of the system partition, which means its corrupt.. I recommend re-flashing with flashcast to be safe if you dont see the team eureka boot animation.

Rooksx · Dec 21, 2013

Kyonz said:
Hi Rooksx,

I've just identified this as an issue and am working on resolving it - in the meantime you can definitely reflash the old method - and I'll have this update to fix in an OTA very shortly (soon as I can find out why it's broken - I blame ddggttff3)

I'll report back in the next 30mins with the results of my testing for anyone else.

---------- Post added at 01:11 AM ---------- Previous post was at 01:05 AM ----------

Just found the issue, it's related to permissions on the /data/eureka folder.

If you run "chmod 777 /data/eureka" it'll fix it - however I'm just checking if the web panel has enough permissions to execute this (or you may need to adb into the device to fix it) we'll have a fix for this out asap - however this will get you up and running immediately.

Edit: you can run "chmod 777 /data/eureka" from the debug panel to resolve this issue immediately until we are able to release a fix for it - sorry for the issue it appears to have hit us from a change in the latest OTA that we are building off that we never saw.

---------- Post added at 01:22 AM ---------- Previous post was at 01:11 AM ----------

Thanks that debug thingy worked. Although ota updating right now - fast work! Incidentally it doesn't seem you have to reboot to start the ota as I was in the middle of watching something when it started.

VaNTHoM · Dec 21, 2013

ddggttff3 said:
No problem, you might want to report the bug to google. I know last time they were asking users for info on their TV/Tuner to try and fix the bug.

It's my lucky day

I followed the link you provided to see how I could contribute, first post was a message saying it was solved! So I tried the simple instructions, and it did solve the problem :good:

These are the instructions:

1. Unplug the Chromecast from both HDMI and USB
2. Plug the Chromcast into USB and wait for it to boot (1 minute or ... so until the LED flashes in white)
3. Plug the Chromecast back into the HDMI

Thumbs up :good:

wptski · Dec 21, 2013

ddggttff3 said:
If you unpowered it during its update process, you will have to re-flash the ROM using Flashcast on a jumpdrive. You should now have a team eureka boot animation on the device. Also, if you remove power during flashing theres a chance that the update script never modded the image, which means you may be running the stock google ROM without the updated bootloader. I recommend re-flashing with flashcast to be safe if you dont see the team eureka boot animation.

Apparently I didn't wait long enough!

I manually flashed the update and all is normal but it does boot up faster than before.

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

Senior Member

Senior Member

Senior Member

New member

Senior Member

New member

Senior Member

Inactive Recognized Developer

Senior Member

Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Member

Inactive Recognized Developer

Senior Member

Inactive Recognized Developer

Senior Member

Member

Senior Member

Similar threads

Top Liked Posts