View Full Version : dumprom produces bad files from blueangel and ipaqhx4700 rom
teddy
7th April 2005, 01:07 PM
I'm working on a polish localization for some PDAs. What I already got is:
1) extract files from rom using dumprom & xda os image tool
2) extract resources from dll and exe files
3) compile mui files from resources
4) translate them into polish using MS LocStudio
5) activate mui usage on PPC2003
Everything works ok for qtec2020 rom, but the first step fails for BlueAngel and HP Ipaq hx4700 because most files that dumprom extracts from ROM image are corrupted.
Enyone has an idea why the files are corrupted?
Thanks for any hints
mamaich
8th April 2005, 05:27 AM
there may be only 1 reason - you incorrectly dump image or extract files with dumprom.
I've extracted all files from BA ROMs and ROMs of several other devices without problems. Even the first XIP of 2005 ROM dumped fine. The only problem that caused Restorator 2004 (I use it to edit resources) to stop recognising resources was a bug in Restorator. This dumb program looks for resources only in ".rsrc" section, and most extracted files have them in ".data".
buzz_lightyear
8th April 2005, 06:35 AM
there may be only 1 reason - you incorrectly dump image or extract files with dumprom.
I've extracted all files from BA ROMs and ROMs of several other devices without problems. Even the first XIP of 2005 ROM dumped fine. The only problem that caused Restorator 2004 (I use it to edit resources) to stop recognising resources was a bug in Restorator. This dumb program looks for resources only in ".rsrc" section, and most extracted files have them in ".data".
hi mamaich,
how did you dump first xip? I can't get it working...
thanx
buzz
mamaich
8th April 2005, 08:50 AM
how did you dump first xip? I can't get it working...Take ROM image, copy everything starting from 0x1C0000 address and to the end of file to some file. And run dumprom on it.
The data from 0x1c0000 looks like:
00001C0000: FE 03 00 EA 00 00 00 00 │ 00 00 00 00 00 00 00 00 ъ
00001C0010: 00 00 00 00 00 00 00 00 │ 00 00 00 00 00 00 00 00
00001C0020: 00 00 00 00 00 00 00 00 │ 00 00 00 00 00 00 00 00
00001C0030: 00 00 00 00 00 00 00 00 │ 00 00 00 00 00 00 00 00
00001C0040: 45 43 45 43 C4 49 33 80 │ C4 49 17 00 00 00 00 00 ECEC─I3А─I
00001C0050: 00 00 00 00 00 00 00 00 │ 00 00 00 00 00 00 00 00
Dumprom would crash, but it would produce:
device.exe filesys.exe nk.exe busenum.dll cecompr.dll
ceddk.dll certmod.dll coredll.dll crypt32.dll devmgr.dll
diskcache.dll fatfsd.dll fatutil.dll fsdmgr.dll fsreplxfilt.dll
hd.dll imgfs.dll msflash.dll mspart.dll osaxst0.dll pm.dll
regenum.dll relfsd.dll 1626e49a-abc6-48a6-bcad-05c134149131.dsm
723fb954-d931-4348-b672-82a188e587b5.dsm boot.hv
sysroots.p7b boot.rgu mxip_initdb.vol
The files have import table broken, but after some playing they can be analyzed in IDA.
mamaich
8th April 2005, 08:59 AM
To fix import table in DLL you need to manualy edit PE-file directory. It is shifted 4 bytes. For example in fatfsd.dll:
╔═ Name RVA Size ═╗
║ Export C07586C1 0000FDB0 ║
║ Import 0000041A 0000F984 ║
║ Resource 0000003C 00000000 ║
║ Exception 00000000 00012000 ║
║ Security 00000690 00000000 ║
║ Fixups 00000000 00000000 ║
║ Debug 00000000 00000000 ║
║ Description 0000001C 00000000 ║
║ MIPS GP 00000000 00000000 ║
║ TLS 00000000 00000000 ║
║ Load config 00000000 00000000 ║
║ Bound Import 00000000 00000000 ║
║ Import Table 00000000 00000000 ║
║ Delay Import 00000000 00000000 ║
║ COM Runtime 00000000 00000000 ║
║ (reserved) 00000000 00000000 ║
╚════════════════════════════════╝
Here Export RVA is 0000FDB0 (written in size), Size = 0000041A (written in import's RVA), imports RVA is 0000F984 size = 0000003C, the same is for resources. This is for WM2005 dumped images only. For 2003 OS dumprom always produce correct files (except for relocs missing in XIP)
buzz_lightyear
8th April 2005, 11:25 AM
@mamaich
THANX 4 reply... EXCELLENT as always...
buzz
teddy
10th April 2005, 12:29 PM
there may be only 1 reason - you incorrectly dump image or extract files with dumprom.
I've extracted all files from BA ROMs and ROMs of several other devices without problems. Even the first XIP of 2005 ROM dumped fine. The only problem that caused Restorator 2004 (I use it to edit resources) to stop recognising resources was a bug in Restorator. This dumb program looks for resources only in ".rsrc" section, and most extracted files have them in ".data".
I use XDA OS image tool to copy ROM to my PC. Then I use dumprom like that:
dumprom -4 -d files pda2k.nb1
Is it correct?
I've found that for example addrstor.dll is missing about 3kb of data. I'm sure that i'm doing something wrong but i don't know why. The same method works ok for qtec2020 and i-mate jam.
Thank U in advance for any hints
mamaich
11th April 2005, 01:20 AM
You are using dumprom correctly.
I've looked inside addrstor.dll. It does not contain any resources. And in XDA2 ROM it also does not have any resources in 2K3SE ROM. Resources are present only in first edition ROM.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.