SamyGO

JeppeTh wrote: I have also reported bugs, but I don't feel like it got any special attention. Perhaps bugs reported by you are considered quite severe...

Did you report security bugs ? Other bugs are ignored IMHO

JeppeTh wrote: I don't blame you. But as mentioned post doesn't mention any ports...
Blocking internet isn't an option since I mainly use it for streaming video from the internet.
I just have to keep my thumbs that my current block is enough then...

if you can't block all ports simply block 1 to 65535

Ok, my bugs wasn't about security
And I can only add 100 entries...

Hi, I have the HT-F9750W. I followed instructions as per "F (BETA) SERIES!!!! WHEN YOU WANT TO HAVE BLURAY/DVD DISKS WORKING"

His is what came up on my screen. Rebooted and opened Web browser, but nothing happened. SamyGO did not activate. What. I doing wrong?

Log shows CLEARLY that SamyGO did "activate" Congratulations on rooting. To confirm SamyGO IS activated you can run app once again and see "/dev/SamyGO_OK" -> OK. This means all works correctly

I thought so at first. This removes cinavia, am I correct?
I tried a movie that gave me the cinavia code prior to rooting, and no cinavia code showed this time. I then tried another movie and after 40mins, cinavia showed. Hence my thinking that rooting was not successful..
Where am I going wrong do you think?

deevine wrote:I thought so at first. This removes cinavia, am I correct?

No

deevine wrote: Where am I going wrong do you think?

You reports "not works" without explaining WHAT it means for you

P.S. You mistook rooting for removing cinavia. It's like with driving license you NEED one to drive a car, but having a driving license is NOT same as having car

Oh ok. I thought rooting the system includes removing cinavia.
So, I take it rooting was a success.
How do I remove cinavia?

Nevermind. I found the link to removing cinavia.
I appreciate your time sectroyer.

sectroyer wrote: If "latest fw" root not works
As soon as x,y,z STOPS being "latest fw" you can start counting
We also want to make sure update blocks root

How will you detect if a later version is available if update is blocked on the device?
I.e. can't you just check if updates are disabled to allow root?
Then we don't need to wait for Samsung to (never) release a new version...

JeppeTh wrote: How will you detect if a later version is available if update is blocked on the device?
I.e. can't you just check if updates are disabled to allow root?
Then we don't need to wait for Samsung to (never) release a new version...

No need to detect. Once "not working fw" is out I will release root Simple as that. What's the point of complicating things ?