SamyGO

nephilim1973 wrote:In the ContentyLibraryMANAGER, I was able to run RSA-Disabler...
After that, I was able to upgrade to the new firmware 3002.2 (patched with SamyGo firmware patcher 0.24)

Ah, it is common mistake in loading "games" from Children category I did this mistake few times too.

nephilim1973 wrote: Please tell me, how I could test, if RSA-Disabler is working for my device.

RSA-Disabler works!

nephilim1973 wrote:I will do almost every testing for you, if it helps.

Could you check if TV accept`s 3000G firmware? Something is changed in Samsungs politic...

Check if you have telnet w/o load any "telnet-enabler" game?
Check if /samygo.sh script works an so on...

I stil do not know how to load RSA dissabler from console...

nephilim1973 wrote: PS: Probably (I do not know) the firmware patcher leave the files untouched and I did an upgrade to ne normal 3002.2 ??
This is possible, cause my "advanced mode telnet start script" is not working...

Yah...it begins... Can you compare exe.img.sec before patching and after. Are files different? Can you dexore firmware files using python.py for getting unxored exe.img?
Check is this hack made in patched exe.img or not?

Ok, it was my mistake, about 3000G, i ment, you have to check if any firmware upgrade is possible (to lower firmware?) or TV rejects USB as no upgrade file found...

It seems, patcher did its job fine. And the reason of not working samygo.sh could be programm you made script - do not use notepad, winword and so on (windows editors), you need edit files in unix format (ANSI). I can recommend akelpad, N++.
Congratulations, you have hacked your TV with the latest 2010y firmware. I have to check if is it possible for other models or just yours.

i believe

About samygo.sh. Is it chmoded to 755? Strange that you don`t get it working.

Here is another way to modify /mtd_boot/rc.local. Take a look here. You could modify unsquashed boot partition, but i do not know if it is possible on CI+ due authult and other restrictions. If you add call to /samygo.sh here, you can`t use patched firmware (or use if you know, that it doesn`t call this file too - it seems you have now such situation).
I would recomend to restore u-boot (here isn`t possibility to stop u-boot on CI+, but anyway) and get access to console via ExLink cable (bought or sold) with restoring kernel and fnw before you flash modified boot partition.

nephilim1973 wrote:

Code: Select all

-rwxr-xr-x    1 root     0            1019 Jan  1  1980 SamyGO.sh

It? s strange... I believe, that another rc.local is used while booting TV...
In almost every first directory to ROOT, there is an rc.local existing...

Which one is the right for the boot process ???

EDIT:


ARRRGH !!!

Have tried the command for telnetd out of SamyGO.sh manually...

Code: Select all

# export KF_LOG=/dev/null ;/mtd_rwarea/SamyGO.sh&
# mount: Mounting devpts on /dev/pts failed: Device or resource busy
/mtd_rwarea/SamyGO.sh: /mtd_rwarea/SamyGO.sh: 5: telnetd: not found

NOW it?s comes clearer and clearer to me...
F**K!

AFAIK, At latest firmwares, Samsung placed some booby-traps. On one version, exeDSP kills telnetd after it's launch. So telnetd disabled on TV again. At later firmwares, telnetd completely removed too.
I wanted to say that you has need working u-boot code and full TV flash backup if you have telnet access or your TV is close to bricked. And it's bad idea to update fw to 3002 I think. Better to keep older one in alternative section. (DO NOT UPDATE TV with 3002 or never twice or your older FW will be lost.) So please revert it, because there is new protection mechanism at latest firmwares. (They put signatures to avoid to flash hacked firmwares on it.)
After reverting back (if you can) instead of 3002 fw, use hacked 3001 fw with updated version number by hand. I think this approach works better...

Or could we put 2006 firmware with 3003 version number? Needed to try that. It might work.

nephilim1973 wrote:In the ContentyLibraryMANAGER, I was able to run RSA-Disabler...
After that, I was able to upgrade to the new firmware 3002.2 (patched with SamyGo firmware patcher 0.24)

Please tell me, how I could test, if RSA-Disabler is working for my device.
I will do almost every testing for you, if it helps.

Regards.

PS: Probably (I do not know) the firmware patcher leave the files untouched and I did an upgrade to ne normal 3002.2 ??
This is possible, cause my "advanced mode telnet start script" is not working...

And it's better to check firmware before flash if it's good or not. You don't need any tool for that. Use Samygo patcher script under python shell. Wiki has explanations about it.