[ROOT] Rooting E/F on latest firmwares

[d3v3loper]

Yes. Me finally too!

I meant my TV finally got rooted.
Maybe my TV got weird through the tries with the "<FW1118"-App.
Had to do a factory reset and try it again for 2 times. Now i can move my recordings to my homeserver.

[PrinzEugen]

Anyone tried new firmware ??

VERSION : 2103.4
2015.01.12

[tvtv]

My name does show up in the donate list, although id rather it was masked and not shown in full...

That aside...

Im confused/overwelmed, and need help... Maybe i need to try the FAT USB instead of FAT32, as everytime ive tried FAT32 the usb just gets recognised as a drive to open pictures etc, rather than firmware and nothing gets installed... granted i probably way using an old version.

My first question is, do we know if this following can yet be rooted?

MODEL CODE:UE40F670
SOFTWARE VERSION: T-MST12DEUC-2102.2

Ideally i just need to be able to install Oscam so that it will play files I include in SmartTV links, maybe that would have no effect, im not sure... DVBT2 work, but DVBS2 currently dont... im not sure why... And the ability to export recoding may be good too.... I dont need everything, the TV already comes with alot

Regards,
keep up the good work

L E

[zoelechat]

Im confused/overwelmed, and need help... Maybe i need to try the FAT USB instead of FAT32, as everytime ive tried FAT32 the usb just gets recognised as a drive to open pictures etc, rather than firmware and nothing gets installed... granted i probably way using an old version.

If ever you encounter problems on step to make installation widget appear in Smarthub, here's a report collection:

* Reboot the tv and don't plug the usb drive.
* Open Smart Hub > Apps > More Apps and then put the usb drive and exit from the screen for new device found.
* SamyGO -F widget will appears after that.

finally, i managed to install samygo. after 5 or more attemps the app appeared under "more apps".

The installation widget only shows up when plugging flash usb drive under more apps section.

Biggest hangup seemed to be getting the app to appear in the smarthub. Took several unplug/re-plug cycles while viewing the "more apps" section before the widget appeared.

My first question is, do we know if this following can yet be rooted?

MODEL CODE:UE40F670
SOFTWARE VERSION: T-MST12DEUC-2102.2

Yes, no problem

Ideally i just need to be able to install Oscam

No oscam on MST.

[Onyx]

OK, I just tried on F8500 FW 2104 (non MST). Was able to FTP and telnet just fine. However, the new method (as compared to the old Skype method) seems not so user friendly.

sectroyer -- can you please confirm this is true: after root, if I want to have samba, I need to run the SamyGO app each time. This means setting the app to autorun so app launches/reinstalls. Also means I have to keep the USB plugged in all the time. So far I haven't been able to figure out another method. Old Skype method used to be more "user friendly" -- I could turn on the TV and the app loads in the background and then samba also mounts automatically.

Please confirm. Thanks for the good work.

[sectroyer]

However, the new method (as compared to the old Skype method) seems not so user friendly.

No, new method is MUCH MORE user friendly

sectroyer -- can you please confirm this is true: after root, if I want to have samba, I need to run the SamyGO app each time. This means setting the app to autorun so app launches/reinstalls. Also means I have to keep the USB plugged in all the time. So far I haven't been able to figure out another method.

That's exactly how it suppose to work. It will work differently ONLY if you know how to do it

Old Skype method used to be more "user friendly" -- I could turn on the TV and the app loads in the background and then samba also mounts automatically.
Please confirm. Thanks for the good work.

No old method was much less "user friendly" because if user did "something wrong" there was no way to "unbrick" the TV. Now it is enough to unplug USB. That's much more "user friendly" Anyway any suggestions on how to make it EVEN MORE "user friendly"/"user error resistant" are always welcome

[Onyx]

No old method was much less "user friendly" because if user did "something wrong" there was no way to "unbrick" the TV. Now it is enough to unplug USB. That's much more "user friendly" Anyway any suggestions on how to make it EVEN MORE "user friendly"/"user error resistant" are always welcome

Thanks for clarifying! I think I should have pointed out that what I meant by "user friendly" was in terms of not having the USB stick plugged in all the time.

Is there a way to copy the SamyGO scripts and files to the TV's drive itself, sectroyer? That would be an awesome way to make things cleaner . Would also free up a USB port .

Thanks for the good work again!

[sectroyer]

Thanks for clarifying! I think I should have pointed out that what I meant by "user friendly" was in terms of not having the USB stick plugged in all the time.

I know what you meant Believe if you brick your TV you will surely consider "having the USB stick plugged in all the time" as a VERY "user friendly method.

Is there a way to copy the SamyGO scripts and files to the TV's drive itself, sectroyer?

Yes there is a way Everybody who knows how to NOT brick their TV already know it

[Onyx]

I know what you meant Believe if you brick your TV you will surely consider "having the USB stick plugged in all the time" as a VERY "user friendly method.

Haha .

[cmuc05]

That are bad news.

Anyway, here is the ouput from dmesg:

Code: Select all

root@tv:/mnt # insmod /mnt/lib/modules/g_file_storage.ko file=/dtv/nfs/pvrimage,/dtv/vusb
root@tv:/mnt # dmesg | grep g_file_storage
g_file_storage gadget: File-backed Storage Gadget, version: 20 November 2008
g_file_storage gadget: Number of LUNs=2
g_file_storage gadget-lun0: ro=0, file: /dtv/nfs/pvrimage
g_file_storage gadget-lun1: ro=0, file: /dtv/vusb
g_file_storage mod ld

If there is a working g_file_storage.ko for the ES 6300 please let me know

For me it worked

Again the Virtual USB stuff on T-MST10 ES 6300. I tried no the dummy_hcd-ko and g_mass_storage.ko.
Same result than with g_file_storage.ko


insmod $MOD_DIR/kernel/drivers/mstar/usb/gadget/dummy_hcd.ko

dmesg output:

Code: Select all

dummy_hcd dummy_hcd: USB Host+Gadget Emulator, driver 02 May 2005
dummy_hcd dummy_hcd: Dummy host controller
drivers/mstar/usb/core/inode.c: creating file '004'
dummy_hcd dummy_hcd: new USB bus registered, assigned bus number 4
usb usb4: default language 0x0409
usb usb4: udev 1, busnum 4, minor = 384
usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: Dummy host controller
usb usb4: Manufacturer: Linux 2.6.35.13 dummy_hcd
usb usb4: SerialNumber: dummy_hcd
usb usb4: usb_probe_device
usb usb4: configuration #1 chosen from 1 choice
usb usb4: adding 4-0:1.0 (config #1, interface 0)
hub 4-0:1.0: usb_probe_interface
hub 4-0:1.0: usb_probe_interface - got id
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 1 port detected
hub 4-0:1.0: standalone hub
hub 4-0:1.0: individual port power switching
hub 4-0:1.0: global over-current protection
hub 4-0:1.0: power on to power good time: 0ms
hub 4-0:1.0: local power source is good
hub 4-0:1.0: no over-current condition exists
hub 4-0:1.0: enabling power on all ports
hub 4-0:1.0: enabling power on all ports
drivers/mstar/usb/core/inode.c: creating file '001'
dummy_hcd mod ld
hub 4-0:1.0: state 7 ports 1 chg 0000 evt 0000

insmod $MOD_DIR/kernel/drivers/mstar/usb/gadget/g_mass_storage.ko file=/dtv/usb/sdw1/pvrimage

dmesg output:

Code: Select all

g_mass_storage gadget: Mass Storage Function, version: 2009/09/11
g_mass_storage gadget: Number of LUNs=1
 lun0: LUN: removable file: /dtv/usb/sdw1/pvrimage
g_mass_storage gadget: Mass Storage Gadget, version: 2009/09/11
g_mass_storage gadget: g_mass_storage ready
hub 4-0:1.0: state 7 ports 1 chg 0000 evt 0002
g_mass_storage mod ld
hub 4-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
hub 4-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
==9==> hub_port_init 1
hub 4-0:1.0: unable to enumerate USB device on port 1
hub 4-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 4-0:1.0: reset change on port 1
hub 4-0:1.0: state 7 ports 1 chg 0000 evt 0002

With high probability the line with "hub 4-0:1.0: unable to enumerate USB device on port 1" is the problem. People in the www wrote, they have this problem because of a hardware problem. One post I found was, that his kernel was hard coded to only have two USB Busses. Maybe this is the problem of enemeration. And if so, how can that be handeled with the samsung kernel?

I hope someone finds out how to make the virtual usb stuff working on T-MST10

@sectroyer: Do you have a running virtual usb on a T-MST10? Because you said "For me it works" ...