Page 4 of 5
Re: Enter to TV with Ex-Link on 3000.2 FW
Posted: Sat Mar 20, 2010 8:59 am
by juusso
One of reasons why we don`t have possibility login to shell with Ex-Link could be jumper in motherboard of TV. Like in computer. Like service jumper. I remember one PC with jumpered m/b, i couldn`t install any OS until i searched out and removed this jumper. I know, it seems incongruous... For example earlier firmwares didn`t check position of jumper, but 3000.2 does. I haven`t seen inside of my TV, there are just my reasoning.
P.s. I disassembled TV, there isn`t any hidden jumpers...
Re: Enter to TV with Ex-Link on 3000.2 FW
Posted: Sat Mar 20, 2010 1:07 pm
by erdem_ua
A reset button is available on some models, and its removed from some others. But you can reset bios via this jumper (or by short circuiting terminals)
Re: Enter to TV with Ex-Link on 3000.2 FW
Posted: Sat Mar 20, 2010 1:39 pm
by juusso
yah, but this procedure doesn`t help login to shell or revert fw back...
Re: Enter to TV with Ex-Link on 3000.2 FW
Posted: Sun Mar 21, 2010 5:19 pm
by juusso
i found this manual on internet
http://ars.samsung.com/customer/usa/jsp ... ROD_ID=154
there isn`t our model listed, but i think its a good information to find out the solution
Re: Enter to TV with Ex-Link on 3000.2 FW
Posted: Thu Mar 25, 2010 8:46 am
by juusso
we can continue at
http://forum.samygo.tv/viewtopic.php?f=2&t=512&start=0
there is a How To by "piet-snot" to get back SMB, UPNP Telnet and all other cute things !!!
Re: Enter to TV with Ex-Link on 3000.2 FW
Posted: Sun Aug 15, 2010 10:30 am
by juusso
Hi,
I`m sucessfuly reverted back from 3000.2 to earler firmware via manual flashing of exe.img and appdata.img, and now i`m using gdb trick. Finaly i decided, that it`s time for flashing u-boot partition to have serial acces via ExLink cable to have backdoor if something will wrong. I found
this message from erdem_ua:
erdem_ua wrote:Here is mine, flash this to your
second partition. Please check if your second partition is empty. Dump it and open the dump with hex editor on your pc. Here is
my hex editor
Aquadran said that all b series uboot is compatible except PCI device/ethernet like devices...
I wish it's works.
After please try to boot from USB key. If you are successful, than don't scare from making your TV bricked
I have few questions to make the picture clear.
1. Do i have to use
bml tool to restore the second partition (tbml2) with the image attached in erdem`s post?
2. Do i have to make the steps from first post in this
forum. E.g.:
1. mtd_boot /MicomCtrl 23
2. killall -9 exeDSP
3. umount /mtd_exe
umount /mtd_appdata
(in my case i think i have umount /mtd_boot or i`m wrong?)
.....
7.bml.erase /dev/bml0/2
8.bml.restore /dev/bml0/2 /mtd_swu/tbml2
....
I can`t check what partition number is u-boot,
df-h output is
Code: Select all
# df -h
Filesystem Size Used Available Use% Mounted on
/dev/tbml6 3.1M 3.1M 0 100% /
none 10.0M 8.0k 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 2.0M 8.9M 19% /mtd_rwarea
/dev/tbml8 60.0M 51.2M 8.8M 85% /mtd_exe
/dev/tbml9 28.6M 28.6M 0 100% /mtd_appdata
/dev/stl0/13 189.0M 81.8M 107.3M 43% /mtd_tlib
/dev/stl0/15 50.0M 6.8M 43.1M 14% /mtd_contents
/dev/stl0/16 87.9M 14.6M 73.3M 17% /mtd_down
/dev/stl0/12 149.0M 224.0k 148.8M 0% /mtd_wiselink
/dev/stl0/17 87.0M 73.8M 13.2M 85% /mtd_swu
/dev/sda1 37.3G 15.4G 21.9G 41% /dtv/usb/sda1
Should i leave /dev/tbml7 untouched?
My TV is CI non plus. Le40B653T5WXBT. Thank you in advance.
p.s. i checked wiki article:
Dumping_and_Flashing_images_by_hand, there is nohing about u-boot. I only gues, that this procedure is equal for all other partitions, not just for exeDSP and appdata...
Re: Enter to TV with Ex-Link on 3000.2 FW
Posted: Sun Aug 15, 2010 12:24 pm
by erdem_ua
You cannot see uboot partition with "df" command.
With (1) & (2), you can repair your uboot partition successfully.
uboot partition make you enable to load external firmwares.
You don't needed to flash tbml7 or any other partitions...
Regards
Re: Enter to TV with Ex-Link on 3000.2 FW
Posted: Sun Aug 15, 2010 4:11 pm
by juusso
This is what i did (from manual (1) and (2) steps +:
Code: Select all
1. bml.dump /dev/bml0/2 /mtd_swu/uboot.img.orig
2. copied erdems tbml2 to /mtd_swu/
3. bml.erase /dev/bml0/2
4. bml.restore /dev/bml0/2 /mtd_swu/tbml2
It seems Tv boots well. My original tbml0/2 was definitely empty, i checked dump with HEX editor.
Now i can enter u-boot menu.
Code: Select all
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2010.08.15 21:45:50 =~=~=~=~=~=~=~=~=~=~=~=
>> ONBOOT :: 0x59a50219 0x12821282
U-Boot 1.1.6 (Dec 12 2008 - 15:55:34)
DRAM: 128 MB
**************** device info *******************
nPgsPerSLCBlk = 128
nPgsPerMLCBlk = 256
nSctsPerPg = 8
nNumOfUsBlks = 994
OneNAND[booting] mode / clk = S / 50Mhz
*************************************************
TinyBML[0] open success
env_relocate_spec
Success loading partition
Environment Data loading success!!
No ethernet found.
In: serial
Out: serial
Err: serial
Net: RTL8139#0
Hit any key to stop autoboot: 2 1 0
===============================
===============================
BOOTROM DEBUG SESSION
===============================
1. ENVIRONMENT SETUP
2. SHOW PARTITION
===============================
0. JUMP TO UBOOT PROMPT
r. REBOOT
===============================
===============================
SELECT COMMAND: 2
<< CS0 PARTITION INFORMATION >>
======================================================================================
description load addr id attr first_blk no_blks
======================================================================================
0 : boot loader 0x60100000 (0x00000000) SLC (0x9001) 0 1
--------------------------------------------------------------------------------------
1 : u-boot 0x60200000 (0x00000001) SLC (0xd401) 1 1
--------------------------------------------------------------------------------------
2 : u-boot env 0x60300000 (0x00000002) SLC (0x9001) 2 1
--------------------------------------------------------------------------------------
3 : update util 0x60400000 (0x00000003) SLC (0x9001) 3 1
--------------------------------------------------------------------------------------
4 : kernel image 0x61000000 (0x00000004) SLC (0xd001) 4 8
--------------------------------------------------------------------------------------
5 : root file system 0x61400000 (0x00000005) SLC (0x9001) 12 8
--------------------------------------------------------------------------------------
6 : boot modules 0x61800000 (0x00000006) SLC (0x9001) 20 4
--------------------------------------------------------------------------------------
7 : driver+exeDSP 1 0x70000000 (0x00000007) MLC (0xa001) 24 60
--------------------------------------------------------------------------------------
8 : appdata+cmmLib 1 0x78000000 (0x00000008) MLC (0xa001) 84 45
--------------------------------------------------------------------------------------
9 : driver+exeDSP 2 0xffffffff (0x00000009) MLC (0xa001) 129 60
--------------------------------------------------------------------------------------
10 : appdata+cmmLib 2 0xffffffff (0x0000000a) MLC (0xa001) 189 45
--------------------------------------------------------------------------------------
11 : mtd_wiselink rw 0xffffffff (0x00000014) MLC (0x2101) 234 180
--------------------------------------------------------------------------------------
12 : mtd_tlib rw 0xffffffff (0x00000015) MLC (0xa101) 414 220
--------------------------------------------------------------------------------------
13 : mtd_rwarea rw 0xffffffff (0x00000016) MLC (0x2101) 634 42
--------------------------------------------------------------------------------------
14 : mtd_contents rw 0xffffffff (0x00000017) MLC (0x2101) 676 81
--------------------------------------------------------------------------------------
15 : mtd_infolink rw 0xffffffff (0x00000018) MLC (0xa101) 757 119
--------------------------------------------------------------------------------------
16 : OTA rw 0xffffffff (0x00000019) MLC (0x2101) 876 118
--------------------------------------------------------------------------------------
======================================================================================
<< CS1 PARTITION INFORMATION >>
======================================================================================
Device[1] not opened
===============================
===============================
BOOTROM DEBUG SESSION
===============================
1. ENVIRONMENT SETUP
2. SHOW PARTITION
===============================
0. JUMP TO UBOOT PROMPT
r. REBOOT
===============================
===============================
SELECT COMMAND: 1
------------------------------
- ENVIRONMENT SETUP -
------------------------------
1. BOOTING COMMAND = bbm load fkernel;go 60008000
2. BOOTING DELAY = 2
3. TARGET IP = 10.88.23.246
4. SERVER IP = 10.88.27.160
5. GATEWAY IP = 10.88.23.1
6. ETHERNET ADDRESS = 10:14:12:13:16:17
7. BOOTING ARGS = root=139:6 rw ethaddr=10:14:12:13:16:11 ip=10.88.23.246 :10.88.27.160:10.88.24.1:255.255.255.0::eth0 console=ttyS1
8. UPDATE BOOTING ARGS
------------------------------
s. SAVE ENVIRONMENT
x. EXIT
------------------------------
SELECT COMMAND: x
===============================
===============================
BOOTROM DEBUG SESSION
===============================
1. ENVIRONMENT SETUP
2. SHOW PARTITION
===============================
0. JUMP TO UBOOT PROMPT
r. REBOOT
===============================
===============================
SELECT COMMAND: r
Why i still can`t enter
TOP debug menu with d.e.b.u.g and 1198282 1198282, if my tbml0/2 was rewritten with good one?