[App] ForceFirmware Back (FFB)

[juusso]

No way! Stop experimenting! Do not change folder name, do not use images from other firmwares except you know what you do. You get 100% bricked TV.
I checked your files and here is a hope for you. Wait.
I make detail step by step for you, because i have here some doubts. Could you please make/buy ExLink cable and connect it to TV? With cable you are insured if you brick TV.

[juusso]

ok, thank you, crubio for help. New version is available here.

FFBv0.3.2

- Added US models LNxxB7xxx/8xxx support (firmware T-CHE7AUSC)
- Added US model PNxxB8xx support (firmware T-CHE7AUSC)

Tester for LNxxB65x needed...

[juusso]

Hm... FFB is just for firmware, restricted by samsung, downgrading purposes. It does not add samygo support to unsupported models. Why do you want use FFB?

[erdem_ua]

juuso. I think we needed to change this program name. "Back" doesn't fit here much.
Force Firmware Flasher fits better doesn't it? ( FFF or Fx3 or F^3)

Also if this program "enables alternative firmware", we needed to remove that property, split this in 2 piece.
One program for just enabling alternative fw, (which is safe) and one for force update.

What you think about it?

[juusso]

juuso. I think we needed to change this program name. "Back" doesn't fit here much.
Force Firmware Flasher fits better doesn't it? ( FFF or Fx3 or F^3)

I do not care a lot about program`s name. It could be FFF too, why not,...

Also if this program "enables alternative firmware", we needed to remove that property, split this in 2 piece.

This program not simply enables alternative frmware as you said, it reboots directly to it (in condition - flashing was successful and no errors were). We could remove alternative fw option to activate post-FEB firmware (it goes as alternative after restart)...Who can say then, that FFB activates alternative firmware? I understand - you take care about safety of process. It is more safe to use FFB as playing with linux console, dexoring by phyton and so on if user just could copy/paste without knowing what does he do. Most of our users are on about very basic or zero linux knowledge level. So automatize firmware downgrading process from scratch to finish is that, what i`ve expected in februar 2010 after i flashed stupid post-FEB to my TV and i believe most of FFB users are happy with this. What about some TV brick we got after FFB0.2...Sure here was. But from v0.3 safety is improoved (mandatory restoring deleted u-boot usw, killing exeDSP) and i did not her about any brick yet.

One program for just enabling alternative fw, (which is safe) and one for force update.

Why should we use two apps instead one for downgrading? I think it`s irrational to use few apps if you want downgrade your firmware if it could be done by one app. Especially if there was no alternative fw on TV at all before (TV purchased after FEB2010)

I suggest leave this app as is, without splitting it to two separate apps.
Sure, we could release app for just forcing firmware flashing purposes, without forcing TV to boot to flashed firmware after restart.

On the other hand, FFB got its name because i thought exact about downgrade+switching to it at once... Ability to flash any not restricted firmware is alternative, not main usage of this app.

Finaly, we could make patch for bml5 to enable top debug console, because all kernels i have seen, after changing one byte got TOP debug menu enabled.

[erdem_ua]

Nop I mean, what if FFB used for just "activate disabled alternative software" via adding Version.x file.
For FFF, it's just upgrading device with new flash firmware (doesn't matter if its old or custom.)
I think it's easier to perceive it's function if it's alone application.
Of course FFF needed to be switch alternative partition to boot TV with newer partition...

I don't inspected but I think you put enough security checks in to program. For example what if I put a firmware with another name, like trying to burn T-CHL7DEUC instead of T-CHLCIPDEUC ? Does it brick our TV? Or just got error firmware mismatch ?

[juusso]

For example what if I put a firmware with another name, like trying to burn T-CHL7DEUC instead of T-CHLCIPDEUC ? Does it brick our TV? Or just got error firmware mismatch ?

You get error due firmware mismatch As i said, FFB checks for firmware version on TV and compares firmware version on USB. On any error FFB stops working and TV reboots on the same untouched firmware.