SamyGO

From log i can say, that you have wrong rootfs on usb, try make another USB flash disk. How did you manage rootfs partition? You have to make it on linux mashine, all commands as root: gparted to make partitions on USB, format to ext3 second partition of USB and the first to fat32, extract rootfs.tar.gz from Open Embedded as root to ext3 (second) partition. After job is finish, unmount USB partitions before disconnecting from linux PC (it can be linux bootable live cd)

I`m sure you have made something wrong. Carefully read wiki. Drivers for USB are loading corectly and USB must be recognized.
Kernel you are booting seems to be good from this log. To boot it, your command is Second: to TOP debug you can enter (if it works at all):
debug (as you make) and after:
1198282 enter
1198282 enter

Or its good to - after debug pres key combination on keyboard: ctrl+c
it drops you to shell, where commands can be executed.
Remember me, is your watchdog off?
I think you have to rewrite rootfs partition (bml0/6), but the problem is, that your TV is CI+ and authuld. Dumps from exact same tv as yours are required.
Anyone
Could anyone make an share dumps from TV LN40B630? All partitions needed!

Please, do not shout, i`m just trying help you. And i suggest you give me more detailed answers to my questions to have me whole picture clear and find out the solution. I won`t ask you many times the same question. I do not need repair your tv, its yours and you need get it repaired, not me.

Sad but I needed to warn that user for make it calm down. Post also removed. People needed to show some respect. Specially for having free support...

Well shouting or being rude in any way to other users (especially if they are trying to help) is not a nice thing to do
(haven't seen his post).
On the other hand it is obvious that flipper currently is under a lot of pressure from his parents for breaking their TV
and I could understand that this could lead you to a state of panic where your mannors go downhill (still not right, but
on some level understandable).

That beeing said I address flipper:
juuso pointed you to the culprit of your problem.
The TV boots up just fine until it tries mounting the root partition.
The only error you have left is:

VFS: Cannot open root device "sda2" or unknown-block(0,0)

This happens for different reasons and almost always because of a incorrectly compiled kernel
(wrong fstab would be another cause but this is irrelevant here).

I would try to reconfigure the kernel and make sure that ext3 is compiled in as are the scsi drivers
(if unsure which one, you could for a testrun compile in quite a lot of them).
Also describe the problem on linux forums, where people compile and hack their kernels on a daily
basis. This error is quite common and by no means samsung-tv-specific, so you will get a lot of good
answers there. I'm quite sure it has something to do with your kernel configuration (because this
happenend quite a lot to me while compiling custom kernels) but I can't tell you what exactly is missing
(like I said my guess would be a missing/or only "moduled" and not loaded ext3-filesystem and/or scsi drivers).
Hit the linux-expert-forums (linuxquestions should be good), pose your question and try to figure
out what is missing.

If you overcome this error, the rest shouldn't be an impossible task.

Good luck,
and maybe show your parents this forum
so that they know there is real hope for their TV

cu
Cyberdemon

Another thing to try:
Search in to kernel sources for the code that outputs:
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
and insert a delay right after it (usleep(10000) or something like this).
Some USB devices take very long to start up, so the kernel tries to
access the flash drive when it isn't ready yet. The usleep gives it a little
more time to become ready (don't know if the OE kernel supports rootdelay/rootwait).
You can also find a clever place within the usb-storage code to insert the delay.

Here is very simple solution for full working kernel.
We need dump of /dev/bml0/5 (kernel) partition and with help of mkimage we get kernel, which is native kernel for his TV, for tftpboot. Read my post here.. Especial this:

After few researches we used mkimage tool on linux computer and changed this tbml5 dump this way :

Code: Select all

mkimage -A arm -O linux -T kernel -a 0x60008000 -e 0x60008000 -C none -n "Original Samsung Kernel" -d ./tbml5 uImage

The question is - who can make such dump of /dev/bml0/5
After that i can make uImage.

And one last (but relatively easy) thing to try:
Empty your usb stick, remove all partitions and then try to create
a filesystem directly on /dev/sdX (instead of /dev/sdX1).
The number behind /sda etc. is the partition number, if your device
always gets mounted as /dtv/usb/sda1 it may afterwards get mounted
as /dtv/usb/sda (which the original kernel is expecting). So if you are
able to get a filesystem on /dev/sdX (where sdX is your flash drive device)
and copy a firmware upgrade onto it, it may be that the TV executes the update.

1) Your TV is trying to execute "emergency upgrade" (/mtd_boot/usb - ?) script. That's a good thing; it means that kernel, boot, and root partitions are most likelly in working order. With a little luck, only EXE and APPDATA partitions are needed to be restored. One simple thing to try is:
- put (prefferably Samsung original/unmodified/unpatched) firmware files on usb drive (freshly reformated to FAT32; make sure there is T-CHE6AUSC/ directory on the pendrive - with run.sh.enc, or run.sh file within it);
- turn on TV with USB drive plugged in;
- observe the result on serial console;
- if the run.sh/run.sh.enc file is found on the pendrive (in /dtv/usb/sda1, /dtv/usb/sda, /dtv/usb/sda2, or /dtv/usb/sda3, possibly in the "T-CHE6AUSC/" dir), TV will try to execute it to perfom the "emegrency" upgrade/reflash;
2) try 1) steps with the different USB pendrive/harddrive (there are known issuess with _some_ USB storage devices in Samsung 2009/B-Series TVs);
3) Shell on serial console: is the USB kernel booting really needed to gain shell access on your TV model? IMO, there is a good chance, ^C keypress in the right moment may be sufficient (after enabling serial input with 'd', 'e', 'b', 'u', 'g' kepresses first).