LE46B650 "bricked"...u-Boot??

[juusso]

No telnet over exlink, just console, which on ci+ is restricted. If you had enough time then you could unlock it first from top debug menu (if accessible??? ) and just then you would able to remove wrong file. For sure working Top debug menu is needed.
Why do I have sense here is no debug access over exlink as well?

[juusso]

Dont waste your time, warranty expires soon.

[juusso]

what do you need to be explaned? Enter:

Code: Select all

debug

in console and if you see

Code: Select all

[SERIAL INPUT MANAGE] 1-th ENABLE Magic serial input match!
[SERIAL INPUT MANAGE] 2-th ENABLE Magic serial input match!
[SERIAL INPUT MANAGE] 3-th ENABLE Magic serial input match!
[SERIAL INPUT MANAGE] 4-th ENABLE Magic serial input match!
[SERIAL INPUT MANAGE] 5-th ENABLE Magic serial input match!
[SERIAL INPUT MANAGE] serial input ENABLE!!!!!

that means, you have console unlocked.
Now you can type (and see on terminal what do you type also, else than before, by typing debug)

Code: Select all

1198282

then press enter. After this repeat:

Code: Select all

1198282

press Enter.
If you see:

Code: Select all

====================================
[ TOP Debug Menu]
------------------------------------

This means you`re in right place.

[juusso]

Mb price is about 100 euro. But it makes sense to tell story... not the truth. It always worked until now

[geo650]

Geo650, few pairs of eyes is allways better than one I noticed he said "after telnet", but...

From debug log of IggI's TV here we know kernel kills system down due some hash file error. This means kernel does not allow to mount rootfs.

I think IggI wrote - "no telnet access" already?

How much time does it take from tv boot until it reboots? Few seconds?

Why are you so sure there are no way to recover this TV? Of course, I advice calling service first, but I think there is a chance to fix it by hand. The script I was writing about needs not more than 1ms to do its job and it might work. Why? Look again on logs:
1.

Code: Select all

/mtd_rwarea/PartitionSwitch_1_0  is detected...

This means for me that /mtd_rwarea is visible at the moment. Ok, this doesn't help for now, but please trace more...

2.

Code: Select all

--- Kernel loading end ----
Application is started.

Does it mean that exeDSP started just now? I think we have all partitions visible now. Then...

3.

Code: Select all

Module injector V1.2
...

So TV executes SamyGO.sh script now, right? As our "victim" wrote, module injector is called after starting telnetd, right? Can telnet daemon be started now? I think it can. Don't you? Certainly, we have to hurry up before injectso will kill the system. This is the external script (or ultrafast typewriter) made for.

Then there is something wrong with injecting and we have kernel panic. But the problem starts on the line with "injectso" command, right? I hope there are no errors outside SamyGO.sh script made.