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

Search This thread

fink.nottle

Senior Member
Mar 25, 2015
59
7
does busybox have a ftpd

Seems to have it, but not sure if it's usable

Usage: ftpd [-wvS] [-t N] [-T N] [DIR]

Anonymous FTP server

ftpd should be used as an inetd service.
ftpd's line for inetd.conf:
21 stream tcp nowait root ftpd ftpd /files/to/serve
It also can be ran from tcpsvd:
tcpsvd -vE 0.0.0.0 21 ftpd /files/to/serve

-w Allow upload
-v Log errors to stderr. -vv: verbose log
-S Log errors to syslog. -SS: verbose log
-t,-T Idle and absolute timeouts
DIR Change root to this directory

tcpsvd is not a binary on the system.
 

clubs07

Senior Member
Aug 11, 2009
60
13
Is it just me or is the autoroot unable to handle the latest update? My Chromecast hangs on the white Chromecast screen after the latest update. I revert back to Eureka to make my CC work again. Tried updating again with Autoroot and the same result. It used to work well untill a week ago.
 
  • Like
Reactions: ntravs

fortis91

Member
Dec 21, 2010
28
5
Looks like I'm having the same issue, I have 2 that is hanging. Haven't touched these in awhile, how do you revert back to Eureka?
 
  • Like
Reactions: ntravs

clubs07

Senior Member
Aug 11, 2009
60
13
I think we need to flash a stock firmware with auto update enabled. There is a thread from Team Eureka with few stock firmware posted but they all have auto update disabled.
I am thinking of unrooting as well.

Thanks. I'll try to revive them over the weekend. Is there a path back to stock

Sent from my Nexus 4 using XDA-Developers Legacy app

Can you let me know which firmware you are on?
I reverted back to Eureka firmware twice and used autoroot to update. It hanged at Chromecast text with the black background in both of my attempts after installing the latest updates. I had to go back to Eureka build which is currently useless since I can't stream anything from most of the apps.

Mine is working just fine...
 

Asphyx

Senior Member
Dec 19, 2007
2,158
378
Android Wear
Google Pixel Watch
I think we need to flash a stock firmware with auto update enabled. There is a thread from Team Eureka with few stock firmware posted but they all have auto update disabled.
I am thinking of unrooting as well.



Can you let me know which firmware you are on?
I reverted back to Eureka firmware twice and used autoroot to update. It hanged at Chromecast text with the black background in both of my attempts after installing the latest updates. I had to go back to Eureka build which is currently useless since I can't stream anything from most of the apps.
firmware 1.22.80438
 

clubs07

Senior Member
Aug 11, 2009
60
13
I finally managed to update successfully to the latest firmware.
Once I reverted back to Eureka, I did a factory reset and used Flashcast AutoRoot to update to the latest firmware.
This time it successfully updated without any issues.
I hope this helps you as well


Thanks. I'll try to revive them over the weekend. Is there a path back to stock

Sent from my Nexus 4 using XDA-Developers Legacy app
 

fortis91

Member
Dec 21, 2010
28
5
Followed your lead...
Recovered using FlashCast and Eureka then factory reset and ran Flashcast-Autoroot which successfully updated to 1.22.80438.
By any chance were you getting preview updates? I left that off this time.

Thanks again for the info.
 

ahecht

Senior Member
Oct 23, 2010
526
315
Last edited:

clubs07

Senior Member
Aug 11, 2009
60
13
You're welcome. Happy to hear it worked for you too.
I didn't opt in for the preview updates I wasn't getting them.

Followed your lead...
Recovered using FlashCast and Eureka then factory reset and ran Flashcast-Autoroot which successfully updated to 1.22.80438.
By any chance were you getting preview updates? I left that off this time.

Thanks again for the info.


---------- Post added at 07:06 AM ---------- Previous post was at 07:01 AM ----------

Thanks. Now that I managed to update successfully to the latest firmware with Autoroot again, I will be keeping my CC rooted. But I will download the stock firmware just in case I want to unroot in the future.


This should be a stock Google OTA: http://cache.pack.google.com/edgedl....ef7fdf1f7153dacecc77b7d1a3bb22a97e27ec7e.zip

It was referenced in the install script for FlashCast AutoRoot, but I haven't tried it yet.
 

jasonweisman12

New member
Apr 1, 2017
2
0
How to reset chromecast

I had Flashcast Autoroot CC and it's no longer working. When I restart there is a black screen saying "Chromecast...". Can someone provide instructions to either restore Flashcast or factory reset the device?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 35
    What is it?

    This is my final gift to the Chromecast community, called Flashcast-AutoRoot. This is a special recovery image for the Chomecast v1 device that will allow it to take official Google OTA's, and then root them during the flashing process. This means you get to keep root, while staying up to date with Google images!

    Features:

    • Auto roots any official Google OTA sent to your device
    • Supports automatic Recovery Image updates
    • Spawns a root telnet server
    • Supports a custom startup script
    • DHCP and Custom DNS
    Q and A:

    Q: How do I setup a custom startup script?

    A: Just write your script to a file at /data/user_boot_script.sh, and set the executable bit for the file. Once done, it will be loaded on next boot.

    Q: How do I setup custom DNS servers?

    A: Put the IP addresses of the DNS servers in a file at /data/dns.conf, one per line. On next boot these will be used for DNS requests. Note if you are coming from EurekaROM, it will already have your old settings in place. :)

    Q: How do I setup the EurekaROM Web Panel?

    A: By default this ROM has no Web Panel, but this can be added by bootstrapping onto the custom startup script, but I will leave this up to you. ;)

    Q: Can Google unroot my device in the future?

    A: Technically yes, but they would have a hard time doing so. To get technical, the bootloader partition can't be updated from the stock OS due to the kernel hard-setting it to "ro". While the recovery image can be flashed from the OS, the root process replaces the included recovery image with it's self to prevent any update. The recovery is also unable to update the bootloader partition, so you should always be able to re-flash using a OTG cable. With that said, I have also put in an update method so I can push updates to the recovery image if needed, but at this time I have no plans on doing so unless required, so use this image at your own risk.

    Installation:
    To install this, all you need to do is SSH/Telnet into an already rooted Chromecast, and run the following commands:
    Code:
    busybox wget http://pdl.team-eureka.com/recovery/install.sh -O /cache/install.sh
    busybox chmod +x /cache/install.sh
    /cache/install.sh
    Note:
    If this is ran on a different ROM than Eureka-ROM there may be an error when ran, but rest assured the flashing process will still work. :)

    GPL/Source:
    https://github.com/team-eureka/flashcast-flasher/tree/newmode-alpha
    15
    I will take a look into this over the next day or so and see if I can get a fix out, or find a way around the issue.

    EDIT: I believe I found a method to fix this, will update if/when the fix is deployed.

    EDIT2: Sadly I was unable to find a way to fix this, it looks like the new bootloader uses a new kernel layout, or has some check in the kernel and not initramfs preventing boot :( Until a GPL is out for release 1.23 I can't verify this or really dig for any potential workaround.
    8
    Deleting, I think you already provided it with the boot.img from 1.22 if I understood correctly. Thanks

    ZaneChua, updated using the modded 1.23 with 1.22 Kernel. It worked, it is now on the 80438 version.
    Let´s hope the next update won´t mess with it again. Until then we have to wait.
    Just to clarify. I started with the Hubcap Eureka and then I took the risk and entered the commands only, no script no factory reset.
    Now it is easy to copy and paste to the telnet terminal.
    I will leave the file that I used in my server for a day so users can install. It is a small hosting plan so not that much bandwidth available.
    *** Remember, I did that and it worked, but I'm not responsible for any damage this can make to your CC ****
    An thanks to ZaneChua for finding the 1.22 Kernel (boot.img)
    Copy and Paste in you telnet:

    Code:
    busybox wget http://pdl.team-eureka.com/recovery/releases/autoroot-recovery-r02.img -O /data/temp/root-recovery.img
    busybox wget http://mcpdigital.com/android/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip -O /data/temp/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip
    busybox cp /data/temp/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip /cache/ota.zip
    flash_image --scan-all recovery /data/temp/root-recovery.img
    // *** WAIT FOR 5 SECONDS 
    reboot recovery
    Update: Did the same procedure in other 2 CCs.
    So now I went from stuck at Chromecast.... straight to the update:
    Step1: create a HubCap Eureka USB from image
    Step2: install the HubCap (OTG+USB, Reset Button, and Power) * no need to root CC again so it is like the second step of the original Eureka.
    Step3: wait until it updates itself from 17977 to 44333 , it shouldnt take long
    Step4: telnet your CC and run the busybox commands as showed by ZaneChua
    Step5: enjoy

    MCP
    6
    Just so it doesn't affect you mcpdigital.

    I made a hosted version.

    To install this, all you need to do is SSH/Telnet into an already rooted Chromecast, and run the following commands:
    Code:
    busybox wget http://chromecastfix.centralus.cloudapp.azure.com/install.sh -O /cache/install.sh
    busybox chmod +x /cache/install.sh
    /cache/install.sh
    6
    That looks like it comes from Eureka and not Google....
    Is it as simple as maybe Eureka just got a bad copy of the firmware?
    Or have you tried that already?

    Did you see the link? It's from Google. Not Eureka. The chromecast device codename is eureka.


    Following adammw's suggestion.

    He didn't really give instructions or anything to help you do this though. Something in the boot.img has changed and therefore breaks autoroot. I decided to use the boot.img from 1.22.80438 to replace the original one in 1.23.84839.

    You need to reinstall eureka rom and be on a clean installation of eureka rom. Means you need to do a factory reset before you try any of the steps below.

    You can find the new OTA from: https://drive.google.com/open?id=0B3jenDHaF8AJMFZMbHVMNmFyeFE
    The script is slightly changed to : https://gist.github.com/zanechua/672f741de2add4186e59dd1973663305

    You still need to modify the script, host it on your own http server and modify the script accordingly.

    You could however do it manually but this may/may not break your chromecast. I'm not at fault here if you do.

    I HAVE NOT PERSONALLY TESTED THE FOLLOWING COMMANDS. THESE COMMANDS ARE FOR EXPERTS ONLY. IF YOU HAVE NO IDEA WHAT THESE COMMANDS DO, DO NOT DO IT. THIS CIRCUMVENTS A LOT OF CHECKS IN THE SCRIPT.

    The commands would be:
    busybox wget http://pdl.team-eureka.com/recovery/releases/autoroot-recovery-r02.img -O /data/temp/root-recovery.img
    busybox wget http://fromsomewhere/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip -O /data/temp/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip
    busybox cp /data/temp/ota.84839.stable-channel.eureka-b3.750d75cf2b18b7140aeef16fc90d6f7eaed4a376.zip /cache/ota.zip
    flash_image --scan-all recovery /data/temp/root-recovery.img
    (Wait 5 seconds after flashing of the recovery)
    reboot