FORUMS
Remove All Ads from XDA
H10 Turbo

[ROM] [r02 - 2015-12-13] Flashcast-AutoRoot

791 posts
Thanks Meter: 1,519
 
By ddggttff3, Inactive Recognized Developer / Recognized Contributor on 13th December 2015, 08:16 PM
Post Reply Email Thread
17th August 2017, 07:37 AM |#351  
bhiga's Avatar
Recognized Contributor
Thanks Meter: 1,027
 
Donate to Me
More
Quote:
Originally Posted by TheKyro

Hi, yesterdsay I decided to upgrade my chromecast v1 from "44433.001 [2015-11-15]" to "[ROM] [r02 - 2015-12-13] Flashcast-AutoRoot"

but now I am stuck with a red light
...
any idea what I can do here (I'm ready to revert to full stock) ?

Reflash Eureka ROM then (re-)read the initial post and the last few pages detailing what has changed that makes this not work directly anymore.

Sent from my SM-G900T using Tapatalk
 
 
11th September 2017, 05:46 PM |#352  
Gonna unroot mine I think, looks like nothing is coming to sort this. Done, unrooted and back on 22062 and waiting for it to update, spent ages looking for my Teensy and didn't even need it. All sorted and updated, forced the update with the below in powershell (as I didn't want to start installing Git/Bash), now on 1.26.92486

Quote:

Invoke-WebRequest -Method Post -ContentType "application/json" -Body '{"params": "ota foreground"}' -Uri "http://<chromecast-ip-address>:8008/setup/reboot" -Verbose -UserAgent "curl"

28th November 2017, 06:07 PM |#353  
Junior Member
Thanks Meter: 0
 
More
I ssh logged in and did entered in the text and it said it updated. When the cc rebooted said it was ver. 1.17. Since its currently a even higher version I let the cc reboot again during this boot I saw the eureka notification that it was updating but when it finished it just read Chromecast on the screen and stayed there. Light was white on the cc. Did I miss something or is mine just a brick now. I'd rather not buy another one but it's cyber week and I could get a v2 for $20 everywhere
28th November 2017, 06:18 PM |#354  
bhiga's Avatar
Recognized Contributor
Thanks Meter: 1,027
 
Donate to Me
More
Quote:
Originally Posted by chaos719

I ssh logged in and did entered in the text and it said it updated. When the cc rebooted said it was ver. 1.17. Since its currently a even higher version I let the cc reboot again during this boot I saw the eureka notification that it was updating but when it finished it just read Chromecast on the screen and stayed there. Light was white on the cc. Did I miss something or is mine just a brick now. I'd rather not buy another one but it's cyber week and I could get a v2 for $20 everywhere

Partition changes made autoroot no longer work on current firmware.
There were a few folks who got intermediate versions to work, but not sure if anyone took charge to see about getting it to continue working.
The Following User Says Thank You to bhiga For This Useful Post: [ View ] Gift bhiga Ad-Free
6th December 2017, 11:36 AM |#355  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by bhiga

Reflash Eureka ROM then (re-)read the initial post and the last few pages detailing what has changed that makes this not work directly anymore.

Sent from my SM-G900T using Tapatalk

Same problem. I tried to update, but it stuck al "Chromecast..." (for 6 hours). I tried to reflash eureka rom but after apearing the flashcast it screen went dark and red light on chromecast. I rebooted and now my options are:
- Normal boot shows "Chromecast..." forever
- Trying to reflash shows dark screen (with some grey pixels) on screen and red light on chromecast.

What can I try?
11th December 2017, 12:33 AM |#356  
Senior Member
Thanks Meter: 176
 
More
Flashed thru Juice using telnet... Success..
Downloaded Google OTA... Rebooted, saw Chrome spinning logo, rebooted again with Eureka logo and updating... Had white LED. Took about 5 minutes then rebooted again.
Now I have Chromecast... Logo in white and that's it! Did I kill my CC??
26th December 2017, 06:26 PM |#357  
Junior Member
Thanks Meter: 4
 
More
Anyone knows the sha1sum of the OTA version: 84838 ?
Or if anyone knows the exact google OTA link for that version of file please do send it.

something like.......
http://redirector.gvt1.com/edgedl/googletv-eureka/stable-channel/ota.84838.stable-channel.eureka-b3.<FILL_THE_BLANKS_HERE>.zip
or
http://cache.pack.google.com/edgedl/googletv-eureka/stable-channel/ota.84838.stable-channel.eureka-b3.<FILL_THE_BLANKS_HERE>.zip
26th December 2017, 10:08 PM |#358  
Junior Member
Thanks Meter: 4
 
More
Nevermind. Found what I was searching for.
58634c32e910f395736070dfd0d4146a86d1450d

http://redirector.gvt1.com/edgedl/go...6a86d1450d.zip


Quote:
Originally Posted by morchu

Anyone knows the sha1sum of the OTA version: 84838 ?
Or if anyone knows the exact google OTA link for that version of file please do send it.

27th December 2017, 12:28 PM |#359  
Junior Member
Thanks Meter: 4
 
More
It does not seem like any nand layout changes were made.

By the way, if anyone experimenting with compling kernel or re-packing boot images, isn't it a lot easier to flash flashcastrecovery to mtd@kernel and your experimental kernel to mtd@recovery, so that you check your experiments via "reboot recovery"? And once you got screwed with your experment kernel let it boot normal to your flashcast in mtd, without using usb. Probably can avoid the hassle of using usb-boots, when you may have to get to flashcast recovery boot many times during the process.

I am yet to try that because I am not sure whether there is any restrictions put by bootloader before booting regular boot image making it impossible to flash recovery from regular boot.

Quote:
Originally Posted by bhiga

Partition changes made autoroot no longer work on current firmware.

29th December 2017, 06:25 AM |#360  
Junior Member
Thanks Meter: 8
 
More
Stuck on "Chromecast..." [SOLVED]
My Chromecast updated after the Autoroot and I got stuck at the "Chromecast..." screen. No luck using Flashcash or Hubcap, even when I dragged out my old Teensy 2.0 and tried at least a dozen times to get it to take. I was close to giving up and assuming my Chromecast was cooked.

Then I tried a long-shot idea described elsewhere on this thread: power up and down fast many times, and eventually I got into recovery with the Flashcast logo on screen. I was able to ssh into the recovery partition, and then manually load up the stock Google image by using scp to copy each of the 3 image files to /tmp and flash them manually using:


flash_mtd_partition 'rootfs' ./system.img
flash_mtd_partition 'kernel' ./boot.img
flash_mtd_partition 'recovery' ./recovery.img
clear_data


It need to take an update from Google and reboot before being fully functional.
It's back to a stock unrooted Chromecast, but at least it works.
The Following User Says Thank You to gdude For This Useful Post: [ View ] Gift gdude Ad-Free
1st January 2018, 05:09 PM |#361  
Junior Member
Thanks Meter: 4
 
More
For folks who are interested to keep the root in the latest version, I was able to get it boot successfully. I made some random unnecessary changes. But the only change required (on top of the regular rooting changes) are

1. Do not use dmsetup to mount /system. This does check integrity of system partition and will fail.
Essentially in init.rc remove lines
exec /sbin/dmsetup create system -r /dmtable
mount squashfs /dev/mapper/system /system ro nodev noatime
and replace with the old way of mounting system
mount squashfs mtd@rootfs /system ro nodev noatime

2. Do not start process_monitor service
Delete line "start process_monitor" in init.rc
You can just delete /bin/process_monitor from system partition, and it should not execute the init.rc service as well.

3. I also changed the dump_msg service to oneshot in init.rc. But I don't think it matters.

I also did some other random changes, which are unnecessary. I will revert those changes when I get some time, but for now it is booting without any issues for me.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes