SamyGO

its gives not control to ssh and you cant do nothing with that

I have installed (using server method since USB didn't work) SamyGO widget. Launched it and it showed that everything installed correctly. However no SamyGO I have UE46EH5450 with 00.1040 firmware installed.

I'm new to the topic, So I hope I can give useful feedback and haven't done some stupid noob failure

I think it didn't worked for me, too. I've done all the steps from the opening post. Installed skype. I saw and klicked the "install SamyGo-E"-widget. After removing the USBstick there is a widget SamyGO-E now. It says "SamyGO Installed! Press return to exit." So I think I've done everything right. But I can not connect to the TV (UE46ES5700, FW: T_MST10PDEUC-1040.2) via Telnet or FTP.

I think this should work because I tried the root-method described in the wiki here: http://wiki.samygo.tv/index.php5/Rooting_the_ES-series. Everything worked with the wiki-root-method. I could connect via Telnet and FTP. Maybe the described "SamyGO widget from USB" is not compatible with my firmware.

Maybe USBstick method is incompatible with this firmware version. Hope there will be some more info soon

I have TMST10PDEUC-1040.2 in my 40ES5500 tv. Samygo widgey form usb is working 100%. Tested perfectly: ftp,telnet,etc

I tried it once more and it worked For some strange reason reformating (FAT32 formated USB drive to FAT32 ) helped. Now the only problem is that mount -o bind doesn't seem to do anything

I have noticed something strange. After rooting the tv doesn't start the DLNA server (in other words port 52235 is closed). Does anyone know how to fix it?

Has anyone who has 1040 firmware tried the alternative method for widget autostart from this source?
viewtopic.php?f=49&t=5797&start=270#p49574

is it also working on this firmware?

thank you in advance.

Hello Gents,

I've got UE50ES7000 with T-ECPDEUC-2005.0 firmware. After a longer while I managed to get the SamyGO-E Install widget on SmartHub. I did it and I got through the FTP to the telly. Today, after reading all these 29 pages of thread, I managed to connect through the telnet protocol on 2023 port. However, the telnet works partially as there is a command line as below:

/bin/sh: can't access tty; job control turned off
VDLinux#>

However, if I put any command, I don't get any result. The netcat also seems to be working but I didn't download the right Windows client yet. FTP works without any problems. The autostart also works quite quickly and SamyGO is online.
Now I'll try to install oscam but my main questions are:

1) is there a full support for telnet? I don't want to run anything if I don't have a full control over the telnet protocol.
2) did I do something in a wrong way that the telnet works like that? What else should I install in order to have a full root access?

przemoka wrote:1) is there a full support for telnet? I don't want to run anything if I don't have a full control over the telnet protocol.
2) did I do something in a wrong way that the telnet works like that? What else should I install in order to have a full root access?

1) Try port 23
2) No, it seems to behave normally. You may have Telnet access on 23/1023/2023 ports and output mostly depends on how you connect to it (Netcat, Putty, Telnet...). Not sure of *FULL* Telnet though