SamyGO

Posted: **Tue Dec 08, 2015 9:38 pm**

sectroyer wrote:

shan2812 wrote: ok, got it

Here is the output:

D:\nc>nc 192.168.0.88 3123
/bin/sh: can't access tty; job control turned off
VDLinux#> /sbin/insmod /tmp/antysfd.ko
insmod: can't insert '/tmp/antysfd.ko': invalid module format
VDLinux#> /bin/dmesg | /bin/busybox grep antysfd
VDLinux#>

Alsmost there... Change second command now try:

Code: Select all

/bin/dmesg | /bin/tail

Hi,

here is the output with the modified 2nd command:

Code: Select all

D:\nc>nc 192.168.0.88 3123
/bin/sh: can't access tty; job control turned off
VDLinux#> /sbin/insmod /tmp/antysfd.ko
insmod: can't insert '/tmp/antysfd.ko': invalid module format
VDLinux#> /bin/dmesg | /bin/tail
/bin/sh: /bin/tail: not found
VDLinux#>

Posted: **Wed Dec 09, 2015 11:20 am**

Hello, im new

and sorry for my english i?m a german user

i faild to root my tv.. i know i had the newest firmware but now i have blocked the domains at my router

IMG_4163.JPG

IMG_4162.JPG

is the new firmware not rootable or who is my problem?

Thank you

Posted: **Wed Dec 09, 2015 12:06 pm**

hi guys,

could someone tell me where to get the log file from? The root app seems to indicate that all went all and so did the patch.bat but can't seem to connect netcat and ftp. I did have temporary access to ftp but some reason my connections are now being rejected by the Tv IP!

Would like to upload the log for someone to help me but don't know where to find it from?

Thanks in advance.

Posted: **Wed Dec 09, 2015 2:29 pm**

Darksmile wrote:is the new firmware not rootable or who is my problem?

Now two reports about same firmware, moreover seeing its release date, it's highly likely that T-NT14UDEUC-1050.1 is no longer rootable.

Posted: **Wed Dec 09, 2015 2:41 pm**

Htchoicy wrote: Would like to upload the log for someone to help me but don't know where to find it from?
.

Disable OTN Support and block updates on router. That's your main problem

Posted: **Wed Dec 09, 2015 2:50 pm**

sectroyer wrote:
Htchoicy wrote: Would like to upload the log for someone to help me but don't know where to find it from?
.
Disable OTN Support and block updates on router. That's your main problem

Did all that. Really weird... Telnet and ftp working again, it only intermittently seems to work!
Thanks guys!

Posted: **Wed Dec 09, 2015 3:00 pm**

shan2812 wrote:
here is the output with the modified 2nd command:

Code: Select all

D:\nc>nc 192.168.0.88 3123
/bin/sh: can't access tty; job control turned off
VDLinux#> /sbin/insmod /tmp/antysfd.ko
insmod: can't insert '/tmp/antysfd.ko': invalid module format
VDLinux#> /bin/dmesg | /bin/tail
/bin/sh: /bin/tail: not found
VDLinux#>

Change second command to:

Code: Select all

/bin/dmesg | /bin/busybox tail

Posted: **Wed Dec 09, 2015 5:37 pm**

farfons wrote:
sectroyer wrote:
farfons wrote:i'm doing something wrong or root is impossible for my tv?
Yes you are "doing something wrong"
farfons wrote: nothing changed also with new commands
my sam.log reports always the invalid module format for jdb2.ko > http://ctrlv.it/id/3312/3648205951
This is new sam.log ? If yes it means you DO HAVE jdb2.ko file in /tmp/ Keep on trying commands in netcat and post photos
Always the same output, nothing
The netcat says always invalid module format and the dmesg doesn't reveal anything

I can't understand why always no output. I've repeated all commands as sectroyer says but with no result. the only output is with

Code: Select all

dmesg | tail

Posted: **Wed Dec 09, 2015 6:53 pm**

farfons wrote: I can't understand why always no output. I've repeated all commands as sectroyer says but with no result. the only output is with
Code: Select all
dmesg | tail

First command SHOULD show ONLY error. Second command:

Code: Select all

/bin/dmesg | /bin/busybox tail

should show "output" which you should paste here

Talking about it is pointless ONLY pasting matters!!!

Posted: **Wed Dec 09, 2015 7:31 pm**

zoelechat wrote:
Darksmile wrote:is the new firmware not rootable or who is my problem?
Now two reports about same firmware, moreover seeing its release date, it's highly likely that T-NT14UDEUC-1050.1 is no longer rootable.

Oh ok bad news

but okay thank you

SamyGO

[ROOT] H "Network" root (FW<=Oct.2015, no T-GFS)

Re: [!!!] Rooting H on latest firmwares

Re: [!!!] Rooting H on latest firmwares

Re: [!!!] Rooting H on latest firmwares

Re: [!!!] Rooting H on latest firmwares

Re: [!!!] Rooting H on latest firmwares

Re: [!!!] Rooting H on latest firmwares

Re: [!!!] Rooting H on latest firmwares

Re: [!!!] Rooting H on latest firmwares

Re: [!!!] Rooting H on latest firmwares

Re: [!!!] Rooting H on latest firmwares