Page 101 of 157
Re: [!!!] Rooting H on latest firmwares
Posted: Fri Feb 12, 2016 10:09 am
by sectroyer
You problem is with insmod_qca. I think it's NOT right for your TV... Have you disabled all quick-on/off options as described in first post ?
BTW. Between tries better power off your TV from cable

Re: [!!!] Rooting H on latest firmwares
Posted: Fri Feb 12, 2016 10:23 am
by ssidquest
Menu->System->General->Samsung Instant ON - This option set to "OFF" when I did the rooting.
Menu->System->General->Quickly Power OFF Samsung - I cannot see this option in my model.
I will power off the TV from the outlet and try to root again. What should I look for to know if it is successful?
Would there by any manual way to root? Like via serial or something?
Thanks!
Re: [!!!] Rooting H on latest firmwares
Posted: Fri Feb 12, 2016 11:15 am
by sectroyer
ssidquest wrote:What should I look for to know if it is successful?
insmod_qca.sh WITHOUT runSamyGO.sh

Also I am NOT sure if you didn't mess up with Main.js since looks you have different wifi vendor might be insmod_bcm
ssidquest wrote:Would there by any manual way to root? Like via serial or something?
No:)
Re: [!!!] Rooting H on latest firmwares
Posted: Fri Feb 12, 2016 11:41 am
by ssidquest
sectroyer wrote:insmod_qca.sh WITHOUT runSamyGO.sh

Also I am NOT sure if you didn't mess up with Main.js since looks you have different wifi vendor might be insmod_bcm

You are correct, the WIFI chipset is broadcom. I saw it from the service menu. How should I proceed?
Should I use InstallSamyGO-H/data/data_bcm.zip?
The script SHOULD do this automatically.
Thanks.
Re: [!!!] Rooting H on latest firmwares
Posted: Fri Feb 12, 2016 1:49 pm
by ssidquest
I did not do anything with the Main.js file but I became curious about it when you mentioned it.
Screenshot of the very first run of the script:
Upon checking the it, I saw that during the first run, it extracted the data.zip to the networkPath by default because both of these statements failed (I guess):
Code: Select all
if(copy(networkPath + "/insmod_qca.sh",usbMountPath+"/"))
{
skypeNotFound = true;
currentStep += 1;
}
else if(copy(networkPath + "/insmod_bcm.sh",usbMountPath+"/"))
{
skypeNotFound = true;
data_zip="data_bcm.zip";
currentStep += 1;
}
thus, it used the declared variable at line 13, putting the insmod_qca script in the system by default:
During the succeeding run, it continued to use the insmod_qca.sh because it already exists in the system. (As you can see in my
post in the previous page)
The script mod in this
post seems to be an ideal solution.
But most probably you have a better one. Could you suggest on how should I correct this?
Re: [!!!] Rooting H on latest firmwares
Posted: Fri Feb 12, 2016 9:39 pm
by sectroyer
yeah change data_zip to:
then it might work
Re: [!!!] Rooting H on latest firmwares
Posted: Sat Feb 13, 2016 6:02 am
by ssidquest
Okay I was able to telnet to port 3123. But still cannot do FTP and Telnet on thes standard ports (21 and 23 respectively).
I also got the same error when I ran the patch.bat
And also the same files:
insmod_qca.sh
Code: Select all
echo " insmod_qca.sh begin"
echo 1 > /dtv/NET_OK
/bin/sh /mtd_rwarea/network/runSamyGO.sh &
insmod /mtd_cmmlib/WIFI_LIB/QCA/cfg80211.ko
insmod /mtd_cmmlib/WIFI_LIB/QCA/ath6kl_usb.ko ath6kl_p2p=0x19 debug_quirks=0x200 reg_domain=0x37
echo " insmod_qca.sh end"
network_type_info.txt
wifi_vendor.txt
EDIT:
I shut it down and checked the USB again. I got these files
Re: [!!!] Rooting H on latest firmwares
Posted: Sat Feb 13, 2016 9:40 am
by sectroyer
Okay TV rooted. Your problems are normal. telnet to port 3123 and run this:
and then quickly:
If you do NOT see any reaction from those commands repeat the procedure BUT use netcat instead of telnet

Re: [!!!] Rooting H on latest firmwares
Posted: Sat Feb 13, 2016 10:23 am
by ssidquest
Hi sectroyer,
Here's the log from insmoding antysfd.ko using netcat (last block of text)
Re: [!!!] Rooting H on latest firmwares
Posted: Sat Feb 13, 2016 1:04 pm
by ssidquest
Another thing, I am not getting ssh, ftp and telnet.
I connected through 3123 and ran:
TV is not listening on port 21, 22, and 23.
I cannot get a persistent root. Whenever I reboot, I cannot telnet back to the TV through 3123.
Note: The rooting USB is always connected when I turn on the TV. I don't remove it while the TV is powered ON.
What do you think is the reason why I cannot get a persistent root?
I am connected through the serial port all through out the rooting process and noticed that I am being flooded by this log:
Code: Select all
[SFD][ERR] !!! Failed to find sign padding (size:921224)
[SFD][BLOCK] [UEP] File /dtv/bin/busybox is not signed!. sign it.
##### send signal SIG : 15, busybox(23405)->busybox(23405) __send_signal
[SFD][BLOCK] Process with PID 23405 has been blocked!
##### deliver signal SIG : 9, busybox(23405) get_signal_to_deliver
[SFD][ERR] !!! Failed to find sign padding (size:921224)
[SFD][BLOCK] [UEP] File /dtv/bin/busybox is not signed!. sign it.
##### send signal SIG : 15, busybox(23406)->busybox(23406) __send_signal
[SFD][BLOCK] Process with PID 23406 has been blocked!
##### deliver signal SIG : 9, busybox(23406) get_signal_to_deliver
Thanks.