Page 1 of 2
Trying to Re-Enable root
Posted: Sun Dec 11, 2016 10:29 pm
by smart_lover
In
launcher.sh file located in
/mtd_rocommon/WebBrowser/bin there is following code:
Code: Select all
/mtd_rocommon/WebBrowser/bin/BrowserLauncher
UI_URL=file:///mtd_rocommon/WebBrowser/WebkitUI/Index.html
disable
Can I use
Code: Select all
curl -sL "http://192.168.10.15:545/helloworld" -o /dev/null
at first line before
/mtd_rocommon/WebBrowser/bin/BrowserLauncher? Is it harmful?
When I want to update
launcher.sh file located in
/mtd_rocommon/WebBrowser/bin with FTP, It fails. Why?
With a little research I realized that I have to umount something. And when I use
umount /mtd_rocommon 2>&1 I got following error:
Code: Select all
umount: can't umount /mtd_rocommon: Device or resource busy
How can I umount mtd_rocommon?
Note:I am looking for a way to return root access in case of losing it with injecting some codes in this script. Is this code runnable even without root access at TV startup?
Re: Trying to Re-Enable root
Posted: Sun Dec 11, 2016 10:54 pm
by wluczykijwf
The partition is read only (system file type squashfs)
You're tread on the wrong paths imho
Re: Trying to Re-Enable root
Posted: Mon Dec 12, 2016 11:04 am
by smart_lover
wluczykijwf wrote:The partition is read only (system file type squashfs)
You're tread on the wrong paths imho
How can I make this partition editable?
Wrong paths? Please give me more info.
Re: Trying to Re-Enable root
Posted: Mon Dec 12, 2016 11:09 am
by juusso
Do not touch rootfs. You get bootloop if hash calculations does not match. Authuld does some checking during boot and compares hashes against original ones inside tv. It is enough to uncompress rootfs and compress it back w/o any change. Timestamp is different, hash different -?bootlop.
Unless you patch out authuld itself.
Re: Trying to Re-Enable root
Posted: Mon Dec 12, 2016 12:46 pm
by smart_lover
juusso wrote:Do not touch rootfs. You get bootloop if hash calculations does not match. Authuld does some checking during boot and compares hashes against original ones inside tv. It is enough to uncompress rootfs and compress it back w/o any change. Timestamp is different, hash different -?bootlop.
Unless you patch out authuld itself.
Thanks for your warning,I'll forget about it!
Re: Trying to Re-Enable root
Posted: Mon Dec 12, 2016 1:07 pm
by wluczykijwf
Now you treading on the good paths
Re: Trying to Re-Enable root
Posted: Mon Dec 12, 2016 1:48 pm
by smart_lover
wluczykijwf wrote:Now you treading on the good paths
Thanks!
Re: Trying to Re-Enable root
Posted: Sat Dec 24, 2016 1:21 pm
by smart_lover
juusso wrote:Do not touch rootfs. You get bootloop if hash calculations does not match. Authuld does some checking during boot and compares hashes against original ones inside tv. It is enough to uncompress rootfs and compress it back w/o any change. Timestamp is different, hash different -?bootlop.
Unless you patch out authuld itself.
Script removed because it might be harmful.
Re: Trying to Re-Enable root
Posted: Sat Dec 24, 2016 2:07 pm
by juusso
If you have confirmation, that this script (and related files like TestWidget.zip..) have been tested on same series TV like yours, then yes, otherwise - no, i`m not sure if TV will survive mtd_appext customisation. Pls ask dude you got files from for more information.
Re: Trying to Re-Enable root
Posted: Sat Dec 24, 2016 3:20 pm
by smart_lover
juusso wrote:If you have confirmation, that this script (and related files like TestWidget.zip..) have been tested on same series TV like yours, then yes, otherwise - no, i`m not sure if TV will survive mtd_appext customisation. Pls ask dude you got files from for more information.
He told me its OK! but when I run
I got
"umount: can't umount /mtd_appext: Device or resource busy" error!
How can I run umount command?