b5fan wrote:
I looked at the NK.BIN from the download site. It does not appear to be the same type of NK.BIN file as for the Omnitech. I am not able to view any of the contents. I'm going to do some more research to see if it might be a different kind of file that was just renamed NK.BIN to throw off people like us.
Also, the possibilities are not completely endless. I still can't get WinCE5 on the old Omni. If I were a programmer that had access to Visual Basic and Platform Builder, I might be able to do more.
b5fan, hope this helps:
http://www.hpcfactor.com/forums/forums/ ... =3&start=1I have been working on building a new ROM for the Plenio VXA-2100 GPS running WINCE 4.2
** special thanks to hpcmonex for her site and tutorial.
I have successfully created one minor tweak to the registry file and successfully uploaded the image once, but I haven't been able to add files or do major changes to the ROM.
I am looking for some help with adding softkb.dll and changing the registry to activate the SIP keyboard.
Here is the background on the unit and the steps that I have taken so far.
The ROM tools (bksamsung/bkondisk) designed to dump NAND ROM's do not work on the Plenio units. You can dump the kernal (nk.exe) from the 8Meg nor flash using Grabit.
Luckily Plenio has a nk.bin file on their support site that you can use.
Download the latest nk.bin from
http://www.dvssales.com/support/Downloads_files/NK.bin Note that this ROM is for VXA-3000 but if you want to load it into the VXA-2100 then rename it to NK2100_.bin. (I have done this on my VXA-2100 with no issues, but the next time you upgrade the ROM you will need to name the file nk.bin since you now have the VXA-3000 ROM loaded)
My understanding is the the 3000 and 2100 are identical except the GPS antenna on the 2100 is detachable.
The ROM Dumping tools will not work on the downloaded file without removing some leading bytes.
I opened the nk.bin file with a HEX editor and removed everything before BOOOFF (28 bytes I think) and save the file under a new name, I used nk_edited.bin.
(thanks to andrewnprice on ppcwarez for this tip!)
The output of viewbin now looks like this.
ViewBin... nk_edited.bin
Image Start = 0x8C200000, length = 0x010F2050
Start address = 0x8C201000
Checking record #83 for potential TOC (ROMOFFSET = 0x00000000)
Found pTOC = 0x8d2f0544
ROMOFFSET = 0x00000000
Done.
Using the following I converted the file to RAW format
cvrtbin nk_edited.bin -r -a 8c200000 -w 32 -l 010f2050 nk_edited.bin
Then finally - Dumped the files contained in the ROM.
dumprom -d c:\tmp\vxa-3000 nk_edited.nb0
I now now have all of the files in the ROM extracted.
Using the perl scripts from hpcmonex's site I converted the default.fdf to default.reg and made a minor change to some text in one of the time zones.
I checked to make sure that the modified default.fdf file was the same size as the original and I then used binmod to put the default.fdf back into the bin file.
Loaded up the nk.bin file using the OS update tool in the Plenio and all was good.
binmod -i nk_edited.bin -r default.fdf
BinMod V1.0 built Apr 5 2006 11:32:47
Checking record #83 for potential TOC (ROMOFFSET = 0x00000000)
Found pTOC = 0x8d2f0544
rom offset = 0x00000000
Found 'default.fdf' in the image! - located at 8ce19d40, size 00007d26 compressed
Assuming pagesize of 00001000 for compression!
New file compressed = 00007d26, uncompressed = 000266c3
Original record checksum: 0x128a191
New record checksum: 0x128a191
New data written to image!
Original record checksum: 0x90a78
New record checksum: 0x90a78
TOC updated!
Done!
My challenge now is that I can not make any other changes to default.fdf and get the nk.bin to load on the GPS.
I have also tried the following tools to make changes, but I get the same results.
Adding default.fdf with dumpromx
dumpromx -v -f default.fdf -a default.fdf nk_edited.nb0
img 00000000 : hdr=8d2f0544 base=8c200000 commandlineoffset=8c200000
block 1 added buf=00440020 010f2050
ERROR: could not find pointer for ofs 00000000
Successful file default.fdf inserting
default.fdf.nb saved successfully
xipbin edited.nb0 0 edited.bin 0
Hooray, now all we need is some patience!
Input: Offset 0x00000000 in EDITED.NB0
Output: Offset 0x00000000 in EDITED.BIN
(0x is okay here because I say so)
....................................................................
My apologies: operation completed successfully. Maybe I can do worse next time!
Can anyone point me in the right direction to be able to make more substantial changes to default.fdf and successfully get them into a working nk.bin file? I suspect that I have an incorrect offset or checksum issue that I don't have enough experience to figure out.
Any help appreciated.
Paul