Page 67 of 256
Re: [App] Rooting E/F on latest firmwares
Posted: Wed Dec 24, 2014 10:58 pm
by sectroyer
zoelechat wrote:Grafhkgb wrote:How can I do this? That the widget start a little bit later?
TV is the F8090!
Yeah on the same principle as "sleep 30" in rcSGO on MST, some delay(s) should be added somewhere in
/mtd_rwcommon/widgets/user/SamyGO_AutoStart/JavaScript/Main.js on non-MST, that's why I asked @prairie if he could share his already modded file which did the job...
IIRC on NON-MST it's !/run.sh in data.zip

Re: [App] Rooting E/F on latest firmwares
Posted: Thu Dec 25, 2014 1:14 am
by cloudmeyer
Still no luck..
i also tried the following:
JavaScipr\Main.js:
added
Code: Select all
function deletefile(filepath){
var command = "filePlugin.Delete('" + filepath + "')";
var result = eval(command);
log("Delete '" + filepath + "' ? " + status(result));
return result;
}
in function rootSamyGO(path)
first few lines now:
Code: Select all
logPara("*********************** Root SamyGO files **************************************");
exists("/mtd_rwcommon/SamyGO/rcSGO");
deletefile("/mtd_rwcommon/SamyGO/rcSGO");
exists("/mtd_rwcommon/SamyGO/rcSGO");
exists("/mtd_rwcommon/emps/empBrowserCommonPlugin/plugins/libSamyGOrun.so");
deletefile("/mtd_rwcommon/emps/empBrowserCommonPlugin/plugins/libSamyGOrun.so");
exists("/mtd_rwcommon/emps/empBrowserCommonPlugin/plugins/libSamyGOrun.so");
//currentStep += unzip(usbMountPath +"/SamyGO-F/data/data.zip", "/tmp/");
currentStep += unzip(usbMountPath +"/"+widgetName+"/data/data.zip", "/mtd_rwcommon/");
This should delete old samygo files if they are already existing. and it does
also modified your rcSGO little bit:
Code: Select all
#!/bin/sh
try=0
maxTries=60
success=0
echo "OK" > /dtv/SamyGO_OK
while [ $try -le $maxTries ] || [ $success -eq 0 ]
do
echo "Looking for SamyGO-F on:"
for i in /dtv/usb/sd*;
do
echo "$i";
if [ -e "$i/SamyGO_data/run.sh" ]
then
echo "SamyGO found on $i"
echo "OK after $try tries" > "$i/SamyGO1.txt"
/bin/sh "$i/SamyGO_data/run.sh" "$i" &
success=1
break 2
fi
done
sleep 1
done
With this, we try to run SamyGo over and over for about 60 Seconds.. if usb is fast, it works fast, if usb is slow we are waiting up to 60 seconds.
But i still have no working Samy...
Edit:
There is a file copied to "/mtd_rwcommon/emps/empBrowserCommonPlugin/plugins/libSamyGOrun.so".
What is its purpose? DO i need to run any kind of Browser to initialize samyGo?
Or is "/mtd/rwcommon/SamyGO/rcSGO" executed magically at boot time?
Re: [App] Rooting E/F on latest firmwares
Posted: Thu Dec 25, 2014 10:46 am
by sectroyer
cloudmeyer wrote:Still no luck..
But i still have no working Samy...
Wit this modified rcSGO how does the rooting log look?
Re: [App] Rooting E/F on latest firmwares
Posted: Thu Dec 25, 2014 12:21 pm
by iT00NZ
Hi! After few days my root stopped working. I don't unplug usb root. It's always attached into TV. What should I do now? How to fix it or check what's going on?
Re: [App] Rooting E/F on latest firmwares
Posted: Thu Dec 25, 2014 1:53 pm
by Grafhkgb
sectroyer wrote:IIRC on NON-MST it's !/run.sh in data.zip

This the the text from the run.sh:
Code: Select all
#!/bin/sh
for USB in ${1:- \
/dtv/usb/sd* } ; do
echo "checking $USB"
sleep 1
if [ -e "$USB/SamyGO_data/samyext4.img" ];
then
echo "OK" > "$USB/SamyGO2.txt"
samygo_data_dir="$USB/SamyGO_data"
fi
done
cd /tmp
if [ -z "$samygo_data_dir" ]
then
echo "SamyGO_data not found."
exit 1
fi
/bin/sh -x "$samygo_data_dir/run1.sh" >> /mtd_rwcommon/sam.log 2>&1
And where must I enter it?
Re: [App] Rooting E/F on latest firmwares
Posted: Thu Dec 25, 2014 4:34 pm
by lolametro
iT00NZ wrote:Hi! After few days my root stopped working. I don't unplug usb root. It's always attached into TV. What should I do now? How to fix it or check what's going on?
The same for me. I hate it

Re: [App] Rooting E/F on latest firmwares
Posted: Thu Dec 25, 2014 5:02 pm
by BlackHole
Good evening,
I successfully rooted a UE40F8000, PVRDecoder works as expected. I noticed that maintaining root privileges is dependent on the USB with root files being plugged in.
As you may have understood, I would like to keep both recordings and root files in that very USB; now, will formatting the drive invalidate root files? what approach do you use to store recordings?
More importantly, did the root files really need to be flashed at every reboot as I assumed?
Re: [App] Rooting E/F on latest firmwares
Posted: Thu Dec 25, 2014 5:20 pm
by zoelechat
BlackHole wrote:will formatting the drive invalidate root files?
I think the answer is in the question
BlackHole wrote:More importantly, did the root files really need to be flashed at every reboot as I assumed?
Flashed? If you meant that USB drive need to be plugged permanently, with rooting files on it, and especially on boot time: The answer is YES, it's generally admitted (see 1st post, in big red letters

) to NEVER unplug this prepared USB while TV is ON.
Read 3 posts from there to know which options you have to keep rooting files and other stuff on the same drive:
viewtopic.php?f=70&t=7982&start=600#p66252
Re: [App] Rooting E/F on latest firmwares
Posted: Thu Dec 25, 2014 6:34 pm
by cloudmeyer
sectroyer wrote:cloudmeyer wrote:Still no luck..
But i still have no working Samy...
Wit this modified rcSGO how does the rooting log look?
It shows that both files exist(rcsgo and this one .so plugin file)
then it deletes, then shows that both do not exist anymore.
Then its copying.
Everything is working as exptected but it seems like the USB run.sh is never startet OR the rcSGO is never started.
Edit:
Also the SamyGo1.txt is never created.
It really seems like rcSGO is never started.
Can you tell me Details how it should be started? Is it started by TV Firmware at boottime(like rc.d scripts on other linuxs)?
Re: [App] Rooting E/F on latest firmwares
Posted: Thu Dec 25, 2014 6:36 pm
by zoelechat
cloudmeyer wrote:Still no luck..
i also tried the following:
JavaScipr\Main.js:
added
Code: Select all
function deletefile(filepath){
var command = "filePlugin.Delete('" + filepath + "')";
var result = eval(command);
log("Delete '" + filepath + "' ? " + status(result));
return result;
}
in function rootSamyGO(path)
first few lines now:
Code: Select all
logPara("*********************** Root SamyGO files **************************************");
exists("/mtd_rwcommon/SamyGO/rcSGO");
deletefile("/mtd_rwcommon/SamyGO/rcSGO");
exists("/mtd_rwcommon/SamyGO/rcSGO");
exists("/mtd_rwcommon/emps/empBrowserCommonPlugin/plugins/libSamyGOrun.so");
deletefile("/mtd_rwcommon/emps/empBrowserCommonPlugin/plugins/libSamyGOrun.so");
exists("/mtd_rwcommon/emps/empBrowserCommonPlugin/plugins/libSamyGOrun.so");
//currentStep += unzip(usbMountPath +"/SamyGO-F/data/data.zip", "/tmp/");
currentStep += unzip(usbMountPath +"/"+widgetName+"/data/data.zip", "/mtd_rwcommon/");
This should delete old samygo files if they are already existing. and it does
also modified your rcSGO little bit:
Code: Select all
#!/bin/sh
try=0
maxTries=60
success=0
echo "OK" > /dtv/SamyGO_OK
while [ $try -le $maxTries ] || [ $success -eq 0 ]
do
echo "Looking for SamyGO-F on:"
for i in /dtv/usb/sd*;
do
echo "$i";
if [ -e "$i/SamyGO_data/run.sh" ]
then
echo "SamyGO found on $i"
echo "OK after $try tries" > "$i/SamyGO1.txt"
/bin/sh "$i/SamyGO_data/run.sh" "$i" &
success=1
break 2
fi
done
sleep 1
done
With this, we try to run SamyGo over and over for about 60 Seconds.. if usb is fast, it works fast, if usb is slow we are waiting up to 60 seconds.
But i still have no working Samy...
Edit:
There is a file copied to "/mtd_rwcommon/emps/empBrowserCommonPlugin/plugins/libSamyGOrun.so".
What is its purpose? DO i need to run any kind of Browser to initialize samyGo?
Or is "/mtd/rwcommon/SamyGO/rcSGO" executed magically at boot time?
Browser automatically loads every .so located in /mtd_rwcommon/emps/empBrowserCommonPlugin/plugins. Browser itself should be started automatically as well on boot time, but you can still try to force it to start from smarthub and see if something changes.
The first and only file to be launched (by libSamyGOrun.so, that's its main job) is rcSGO itself, so the "sleep" should be there and
only there. Moreover, there's no autostart widget on MST, so the Main.js you've edited is only part of
installation widget, so it has no meaning nor usefulness to edit it since installation (from screenshot) have already been reported successful.
One more option: Factory reset from service menu!

(and restart everything from scratch)
edit: you seem to have enough skill to investigate files by yourself, like I did (Devs are often light on details, more I have no F

)