[How-To] Rollback on old FW...

Here is information about customize your B series firmware..:!:This forum is NOT FOR USER questions or problems but DEVELOPER.

User avatar
erdem_ua
SamyGO Admin
Posts: 3126
Joined: Thu Oct 01, 2009 6:02 am
Location: Istanbul, Turkey
Contact:

Re: Rollback on old FW...

Post by erdem_ua »

edelfalke wrote:It doesn't work for CI+ Device.
I have tested this howto on my UE40B7090 CI+ and my TV shoots down after 1-2 minutes and this at every start.
It was a very stressful Weekend to revert my tv back to 3001 FW.
It's "authld", signature checking daemon that check your exe.img and found that it's hacked. You needed to patch your FW with TV's firmware flash GUI. That will fix the problem. But I don't know if you have enough time for that.
edelfalke
Posts: 81
Joined: Sun Jan 10, 2010 12:29 pm

Re: Rollback on old FW...

Post by edelfalke »

The time before tv shuts down is definetly not enought (approx. 1 to 2 minutes).
TV shuts down before the usb key with FW is accepted in FW flash menu.
I don't want to brick my tv whether i start the flash and tv shuts down while flashing.
User avatar
erdem_ua
SamyGO Admin
Posts: 3126
Joined: Thu Oct 01, 2009 6:02 am
Location: Istanbul, Turkey
Contact:

Re: Rollback on old FW...

Post by erdem_ua »

If such a thing happens, It will be %100 percent Samsungs fault. :)
I think we could modify RSA Disable tool to Authld Disable tool that resolves such problems...
aquadran
Posts: 264
Joined: Fri Oct 16, 2009 9:35 pm
Location: Poland

Re: Rollback on old FW...

Post by aquadran »

antrabe wrote:I have le40b651T3W i had updated the firm by mistake to 3000 , then i activated telnet copyng the samygo folder in memory with the game. i can connect to telnet.

After that i tried to back firmware 2005 i follow all the steps with phytopn xor appdatimgenc and exeimgenc, then follow all the steps but dont happens nothing mi df its the same than in example

Filesystem Size Used Available Use% Mounted on
/dev/tbml6 3.1M 3.1M 0 100% /
none 10.0M 0 10.0M 0% /dtv
/dev/tbml7 896.0k 896.0k 0 100% /mtd_boot
none 10.0M 0 10.0M 0% /mtd_ram
/dev/stl0/14 11.0M 1.7M 9.2M 16% /mtd_rwarea
/dev/tbml8 60.0M 51.0M 8.9M 85% /mtd_
/dev/tbml9 28.6M 28.6M 0 100% /mtd_appdata
/dev/stl0/13 189.0M 179.5M 9.5M 95% /mtd_tlib
/dev/stl0/15 50.0M 2.0M 48.0M 4% /mtd_contents
/dev/stl0/16 87.9M 16.5M 71.4M 19% /mtd_down
/dev/stl0/12 149.0M 224.0k 148.8M 0% /mtd_wiselink
/dev/stl0/17 87.0M 176.0k 86.8M 0% /mtd_swu


then what im doing wrong?

When i write the last command i have to wait some time?
I found new firmware don't accept old not encrypted firmware. So you need do that manually from telnet only.
edelfalke
Posts: 81
Joined: Sun Jan 10, 2010 12:29 pm

Re: Rollback on old FW...

Post by edelfalke »

erdem_ua wrote:If such a thing happens, It will be %100 percent Samsungs fault. :)
I think we could modify RSA Disable tool to Authld Disable tool that resolves such problems...
@Erdem
could you create the Authld Disable tool for testing?

thanks
User avatar
erdem_ua
SamyGO Admin
Posts: 3126
Joined: Thu Oct 01, 2009 6:02 am
Location: Istanbul, Turkey
Contact:

Re: Rollback on old FW...

Post by erdem_ua »

No, Needed to inspect CI+ Linux image.
I think mprotect could easily make this. But I don't inspect CI+ kernel before and don't have an Idea if I can. Also I have a no time for such a thing this days.

Post Reply

Return to “[B] Firmware”