Hi guys, i just prepared some short how to, works on latest firmwares too, but only for D6 series arm models.
Designed for "restricted" recent firmwares, but works on not restricted as well.

Until i get more confirmations, method is marked as "unsafe and dangerous",
because if TV bricks, here is only Service repair possible. If you decide to use this,
make on your own responsibility.
After you get TV hacked, don't touch/mtd_rwarea/start.sh - any error of this script leads in to the brick. No repair at home possible, neither over Exlink, nor over eeprom reset or any other known methods. Formatting of /mtd_rwarea doesnt help either.

If you need some extra startup options, you have to modify/mtd_rwarea/SamyGO.sh, because if it fails, it`s not critical.You don`t need to start widget SamyGO in SmartHub, it won`t work! This is normal behavior the hospitality hack doesn`t overcome this limitation. If you start widget, nothing hapens, just screen goes black for the moment. Don`t touch widget, you don`t need to execute it, just enough to have widget installed - all required files and processes are being executed in other, not widget, way.

The wiki talks about specific models (ARM) and firmwares (T-GAS*, T-GAS6*), while the title of this topic is pretty generic (D6 series).
So what is correct, wiki or topic title?
And what about that red warning on the wiki page? Does this still apply if the hack was tested?

If wiki is correct (ARM only), what are the chances to have this for Mstar?

Hello, i have the same behavior on ue32d6100 (Firmware 1015). On selecting "Clone USB to TV" i get a message that the tv will restart after success. After the automatic reboot i turn the TV off again and switch to the second usb stick. Clone, restart, turn of, remove usb stick, turn on again.

After that i do not have FTP access. What could be wrong? Can i see what happens on booting without having an Ex-Link Cable?

After setting up the usb sticks again (with unmounting) everything is working fine. Thanks
Beside that i turned the TV off after cloning from usb (instead of following the message "Completed successfully. Reboot after clicking ok") Perhaps this did the trick.