Dumping and Flashing images by hand - Revision history

Erdem ua: /* Manual flashing steps */

2010-03-08T15:53:32Z

‎Manual flashing steps

Erdem ua: Added Flashing via TVs Software

2010-01-10T00:36:30Z

Added Flashing via TVs Software

Kilroywashere: /* Manual flashing steps */

2009-12-06T13:50:14Z

‎Manual flashing steps

Erdem ua: /* For All Devices */

2009-12-06T13:17:11Z

‎For All Devices

Erdem ua: Added 'df' tool to understand drive/partition mapping

2009-12-06T13:16:14Z

Added 'df' tool to understand drive/partition mapping

Erdem ua: /* Manual flashing steps */

2009-12-06T13:01:43Z

‎Manual flashing steps

Erdem ua: Using cat and dd tool as flash dumpers...

2009-12-06T12:37:34Z

Using cat and dd tool as flash dumpers...

Erdem ua: moved Manually flashing images via telnet or console (without the need for XOR and CRC32) to Dumping and Flashing images by hand: Old title, "Manually flashing images via telnet or console (without the need for XOR and CRC32)" is too long for

2009-12-06T12:30:15Z

moved Manually flashing images via telnet or console (without the need for XOR and CRC32) to Dumping and Flashing images by hand: Old title, "Manually flashing images via telnet or console (without the need for XOR and CRC32)" is too long for

Dynamic1969 at 20:34, 30 November 2009

2009-11-30T20:34:53Z

Dynamic1969 at 02:00, 21 November 2009

2009-11-21T02:00:27Z

@@ Line 69: / Line 69: @@
 *(7) Erase the flash before flashing the new file
   bml.erase /dev/bml0/8
-*(8) Perform the actual step of flashing the file.
+*(8) Perform the actual step of flashing the file. exe.img file is needed to be non-encrypted. So you needed to decrypt exe.img.sec or exe.img.enc images before flashing!
   bml.restore /dev/bml0/8 /mtd_swu/exe.img
 ->Flashing progress will be shown 0% ... 100%. Don't interrupt this process!!
@@ Line 79: / Line 79: @@
 the exeDSP binary seems to expect a freshly initialized HW to start-up properly <br>
 <br>'''Attention:'''This process does not validate the correctness and validity of the file being flashed. THIS IS YOUR RESPONSIBILITY!!!
 ==Flashing via TVs Software==

@@ Line 77: / Line 77: @@
   /mtd_exe/rc.local
 -> If something went wrong and your exeDSP doesn't start up properly, then you can flash back your backup ".orig" image following steps 3-9.<br>-> Don't worry, if you see your screen upside down after re-starting exeDSP ;-) as
-the exeDSP binary seems to expect a freshly initialized HW to start-up properly <br><br>
+the exeDSP binary seems to expect a freshly initialized HW to start-up properly <br>
-<br><br>'''Attention:'''This process does not validate the correctness and validity of the file being flashed. THIS IS YOUR RESPONSIBILITY!!!
+<br>'''Attention:'''This process does not validate the correctness and validity of the file being flashed. THIS IS YOUR RESPONSIBILITY!!!
 --[[User:Dynamic1969|Dynamic1969]] 17:59, 3 October 2009 (UTC)

@@ Line 62: / Line 62: @@
   dd if=/dev/bml0/8 of=/mtd_swu/exe.img.orig
-*(5) Move backup image to a safe space ( e.g. USB ) and remove file from '''/mtd_swu'''
+*(5) Move backup image to a safe space ( e.g. USB )
   mv /mtd_swu/exe.img.orig /dtv/usb/sda1
 *(6) Copy Image to be flashed from your USB to /mtd_swu
   cp /dtv/usb/sda1/exe.img /mtd_swu

@@ Line 18: / Line 18: @@
 === For All Devices ===
-*It's better to conceive the structure of your TV by df tool.
+*It's better to conceive the structure of your TV by '''df''' tool.
-You can check it your "'''df'''" output. Here is mine on LE40B650T2W which uses T-CHL7DEUC firmware
+You can check your "'''df'''" output. Here is mine on LE40B650T2W which uses T-CHL7DEUC firmware
   # df

@@ Line 16: / Line 16: @@
 *EXE_DEVICE='''/dev/bml0/8'''
 *APPDATA_DEVICE='''/dev/bml0/9'''
 == Manual flashing steps ==

@@ Line 26: / Line 26: @@
 *(4) Take a backup of the current image in the flash.
   bml.dump /dev/bml0/8 /mtd_swu/exe.img.orig
-If you dont have bml.dump tool, than you can use '''dd''' or '''cat''' tool too.
+If you dont have bml.dump tool in your firmware, than you can use '''dd''' or '''cat''' tool too.
   cat /dev/bml0/8 > /mtd_swu/exe.img.orig
-or
   dd if=/dev/bml0/8 of=/mtd_swu/exe.img.orig
 *(5) Move backup image to a safe space ( e.g. USB ) and remove file from '''/mtd_swu'''

← Older revision	Revision as of 12:30, 6 December 2009
(No difference)

@@ Line 1: / Line 1: @@
 The steps outlined below allow the flashing of an image directly into the flash of your TV, without using the offical upgrade process of the TV.<br>The example shown below is for flashing a modified exe.img on a UExxB70xx.<br>
-There is no need to flash app_data Image, if you are just flashing modifications of the same exeDSP Version.
+There is no need to flash app_data Image, if you are just flashing modifications of the same exeDSP Version.<br>
 '''In any case you need to ensure that you erase the respective flash before overwriting it.'''
 == Device files used ==
@@ Line 32: / Line 32: @@
   cp /dtv/usb/sda1/exe.img /mtd_swu
 -> this is the safest way, even though flashing directly from USB-Device may also be possible, which I have not tested
-*(7) Perform the actual step of flashing the file.
+*(7) Erase the flash before flashing the new file
   bml.restore /dev/bml0/8 /mtd_swu/exe.img
 ->Flashing progress will be shown 0% ... 100%. Don't interrupt this process!!
-*(8) Mount the updated image( afterwards check out content and ensure it mounts without problems and looks ok from a content perspective. )
+*(9) Mount the updated image( afterwards check out content and ensure it mounts without problems and looks ok from a content perspective. )
   mount -t auto /dev/tbml8 /mtd_exe<br>
-*(9) Starting exeDSP<br>
+*(10) Starting exeDSP<br>
   /mtd_exe/rc.local
 -> If something went wrong and your exeDSP doesn't start up properly, then you can flash back your backup ".orig" image following steps 3-9.<br>-> Don't worry, if you see your screen upside down. That is just due to a variable not been set ;-)