FORUMS

[ROM][124602 - 2018-08-26] Unnamed Test

27 posts
Thanks Meter: 21
 
By KenMacD, Junior Member on 26th August 2018, 11:40 PM
Post Reply Email Thread
26th November 2018, 12:12 PM |#11  
Member
Thanks Meter: 10
 
More
Quote:
Originally Posted by Mstst2008

Please help to install new ROM for my smart TV to install apps from google play because my device didnt alow me to install any app from google play....
Please help me

You mean to say your tv is not allowing installation of apps found on google play running on your tv?
26th November 2018, 03:30 PM |#12  
Junior Member
Thanks Meter: 0
 
More
My smart tv running aptoide tv so i need install this app
play.google.com/store/apps/details?id=com.ispsgroups
So, please help me to modify the firmware to LG or Samsung firmware ...

---------- Post added at 04:30 PM ---------- Previous post was at 04:27 PM ----------

Quote:
Originally Posted by avvgopal

You mean to say your tv is not allowing installation of apps found on google play running on your tv?

My smart tv running aptoide tv so i need install this app
play.google.com/store/apps/details?id=com.ispsgroups
So, please help me to modify the firmware to LG or Samsung firmware ...
15th December 2018, 02:50 PM |#13  
miniminus's Avatar
Senior Member
Thanks Meter: 195
 
Donate to Me
More
THANKYOU @KenMacD !!!
managed to upload it via ssh with tftp, ( idea from @ironstorm about svp. but seems theres no sftp-server installed etc, but found there is a tftp ... )
so no usb sticks, or y-cables etc needed will give other people a guide here ...

1. You need a tftp server running, so get tftpd64 running and setup on ya pc (from here http://tftpd32.jounin.net/tftpd32_download.html)
2. my chromecast worked as such, just wasnt able to actual cast anything, so use the proper google app to set it up on WiFi if it isnt already
3. get chromecast into recovery, power up/down/up/down seems to induce it ! not sure like ironstorm what the proper procedure is !
4. then connect to it via SSH, i used PuTTY (ip will be different than when you initially set it up on Wifi with app)
5. then in PuTTY once connected /user/bin/tftp -g -f eureka_image.zip 192.168.x.x
6. then flash-image eureka_image.zip
7. once its finished ! .. reboot (powercycle)

and wahoo ! working chromecast again !!!

just to note, as i was worried .. althou we have no SSH etc when its running as norm.
we DO have SSH while in recovery/flashcast as above, it doesn't remove that, so its all good for next update, which can be done via this procedure too
16th March 2019, 01:12 AM |#14  
Junior Member
Thanks Meter: 4
 
More
I was able to resurrect my old Chromecast using the flashcast method, but I wasn't able to configure it. The Chromecast dongle would start up okay, but it needed to be setup. When I launched the Google "Home" app, it couldn't find the Chromecast. I eventually flashed an older eureka_image.zip (44433) and then the "Home" app was able to find the Chromecast, and I was able to set it up. Then I flashed this latest version (124602) and it continued to work.
24th February 2020, 03:31 AM |#15  
Junior Member
Thanks Meter: 1
 
More
Does this build still enable telnetd and/or sshd?

Edit: Looks like the answer is no, but you can still ssh into recovery.
28th April 2020, 08:46 PM |#16  
Member
Thanks Meter: 13
 
More
I checked this kernel with the latest OTA as well and it should still work theoretically by combining this kernel with new system (ota.159268) and libc from ota initrd. Maybe minor midifications on init.rc possibly to adjust some arguments on service calls.

But there is always that slight risk of unbootable system. The worse scenario possible is if the system image is not properly modified, allowing overwrite of recovery partition and loosing flashcast. But still doable by someone who still know what he is doing and still have that interest and time on this device.

I also posted another method recently of achieving the same, essentially by allowing whatever rootable kernel/system you have to boot completely and then mounting new modified system and initrd.libs over original mounts, and then restarting some services. But again the mod we do to system is important, so that unwillingly we don't let googles services to overwrite flashcast (cleanup those flash recovery executables update_engine and recovery.img on OTA system).

But beyond that since nothing is really flashed, there is less chance of a brick, but still allowing the old chromecast to use latest cast_engine and all related executables and binaries (just as an unrooted chromast on latest OTA).

Quote:
Originally Posted by KenMacD

Same here. Autoroot would be nice, but first step first was seeing if things would actually work.

This is a kernel build from eureka_linux, which is based on oss release 1.16. The init.rc was just updated to remove the dmtable stuff and mount it directly.

From here it's probably pretty easy to do a EurekaROM-like release.

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