Re: [App] Rooting E/F on latest firmwares
Posted: Sun Aug 09, 2015 9:16 pm
Good, as simple as following the right procedure 

I downloaded another time the zips and formated USB stick ... still the same results.sectroyer wrote:Well rooting worked. The problem is with you SamyGO_data directoryProbably bad/broken samyext4.img!!!
Code: Select all
Starting Nmap 6.47 ( http://nmap.org ) at 2015-08-10 13:45 GMT (czas letni)
NSE: Loaded 118 scripts for scanning.
NSE: Script Pre-scanning.
Initiating ARP Ping Scan at 13:45
Scanning 192.168.1.51 [1 port]
Completed ARP Ping Scan at 13:45, 0.40s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 13:45
Completed Parallel DNS resolution of 1 host. at 13:45, 6.53s elapsed
Initiating SYN Stealth Scan at 13:45
Scanning 192.168.1.51 [1000 ports]
Discovered open port 443/tcp on 192.168.1.51
Completed SYN Stealth Scan at 13:45, 4.33s elapsed (1000 total ports)
Initiating Service scan at 13:45
Scanning 1 service on 192.168.1.51
Completed Service scan at 13:45, 12.13s elapsed (1 service on 1 host)
Initiating OS detection (try #1) against 192.168.1.51
NSE: Script scanning 192.168.1.51.
Initiating NSE at 13:45
Completed NSE at 13:45, 0.61s elapsed
Nmap scan report for 192.168.1.51
Host is up (0.0070s latency).
Not shown: 994 filtered ports
PORT STATE SERVICE VERSION
17/tcp closed qotd
256/tcp closed fw1-secureremote
264/tcp closed bgmp
443/tcp open ssl/http lighttpd
|_http-methods: OPTIONS GET HEAD POST
|_http-title: 404 - Not Found
| ssl-cert: Subject: commonName=server1/organizationName=Samsung SERI/stateOrProvinceName=Surrey/countryName=GB
| Issuer: commonName=CA root/organizationName=Samsung SERI/stateOrProvinceName=Surrey/countryName=GB
| Public Key type: rsa
| Public Key bits: 1024
| Not valid before: 1970-01-01T00:00:00+00:00
| Not valid after: 2030-01-01T00:00:00+00:00
| MD5: cfed beba 8b97 cd23 a4ea 2111 dd6f 0827
|_SHA-1: 4242 3dc7 c308 b648 7d0c 3630 542d a4af c462 33ca
|_ssl-date: 1970-01-01T00:01:03+00:00; -45y221d12h44m50s from local time.
1080/tcp closed socks
1723/tcp closed pptp
MAC Address: 5C:F6:DC:B3:D1:80 (Samsung Electronics Co.)
Device type: general purpose
Running: Linux 2.6.X|3.X
OS CPE: cpe:/o:linux:linux_kernel:2.6 cpe:/o:linux:linux_kernel:3
OS details: Linux 2.6.32 - 3.5
Uptime guess: 0.001 days (since Mon Aug 10 13:44:50 2015)
Network Distance: 1 hop
TCP Sequence Prediction: Difficulty=258 (Good luck!)
IP ID Sequence Generation: All zeros
TRACEROUTE
HOP RTT ADDRESS
1 7.02 ms 192.168.1.51
NSE: Script Post-scanning.
Read data files from: C:\Program Files (x86)\Nmap
OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 35.59 seconds
Raw packets sent: 2018 (90.390KB) | Rcvd: 23 (1.306KB)
The reason is not wifi speed but:gorgone wrote:my tv is on wifi
150mbit its fast enough to stream with pembos enigma2 streamer in HD
Rooting method is known to be sometimes ticklish if done through wifi1ST POST wrote:
!WARNING!!!! DON'T ASK FOR HELP WITHOUT ROOTING USING LAN CONNECTION!!!!!!! NO WIFI SUPPORT!!!!
Well you CAN use Wi-Fi for rooting your TV. It's NOT that it will do "something bad". Just if it doesn't do NOT ask for helpgorgone wrote:my tv is on wifi
150mbit its fast enough to stream with pembos enigma2 streamer in HD
Exactly. But be "sometimes" I would rather say in 90% of caseszoelechat wrote: Rooting method is known to be sometimes ticklish if done through wifi
Of course you DO "have crappy hardware"gorgone wrote:i dont have crappy hardwaremaybe cheap wlan routers are often the hidden problem...