Shell Programming and Scripting

Since you can dump/restore, you might be able to get this just by hex-editing. Change "AMER" to "ROW ". Note the space on the end, which makes the filesize not change. A newline would also work.

I was thinking about this before...but...as you can see, there is no place to replace ROW with AMER. (taken from full nand dump file)
By the way. Changing ROW/AMER in config.ini will change unit to RestOfWorld version permanently.
Changing it in firmware, will change unit till next firmware update.

PS. Config.ini looks always the same. I made dumps with firmware 2.5, 3.0, 3.5, 4.0.

I don't think that is the config file, I think you landed inside an executable.

I'll take a closer look at the big dump when I get home.

I'm sure everything is in config.ini.
Some time ago I had HDS5 factory ROW version.
I just copied 12kb config.ini from this unit and pasted it into HDS5-AMER version dump.
After that HDS5-AMER started as ROW version.

---------- Post updated at 06:12 PM ---------- Previous update was at 06:01 PM ----------


Anyway. Thank you very much for your help.
You are my only hope to solve my problem.

Maybe this will help a little:
Memory Technology Device (MTD) Subsystem for Linux.

Linux is magic for me, Im electronic engineer

Ps. It is 1.00am here in Poland... I have to go to sleep

Have you downloaded "big" dump?

It'll take ages for me to download that rom dump. Sweet dreams

---------- Post updated 09-23-11 at 10:28 AM ---------- Previous update was 09-22-11 at 05:21 PM ----------

is that 256kiloBYTE pagesize or 256kiloBIT page size? The ROM is not a multiple of either in size. (4K doesn't work either.) It's not a gigabyte in size, not even a "drivemaker's gigabyte". Instead it's almost exactly 0x42000000 bytes long, with 2,200 bytes of change ( total 0x42000898 ).

I don't understand why they'd have data areas in a ROM chip that're smaller than the chip's page size. Is there any physical structure to the data layout? Some sort of special hardware data area?

I'm unable to mount this image as a MTD device yet. I'd need 44 gigabytes of RAM to emulate a 1GB MTD. Instead I'm seeing if I can find the offsets of partitions inside it and rip them out.

I will try to read whole flash using different programmer settings.
It will take a while.

PS. This info:
# 1GB NAND has 256k ERASESIZE and 2k PAGESIZE OR 256k ERASESIZE and 4k PAGESIZE
is taken from update.sh script.

NAND chip used in HDS is Samsung K9G8G08U0M.
http://www.arm9board.net/download/FL...et/K9G8G08.pdf