wes58, on Jan 21 2010, 11:49, said:
The only reason I can think of is, if the path is not set correctly (by my application) to the dump folder where imgfs.bin was dumped.
The strange thing is that I tried today a few time on Windows 7 and XP and I didn't have a problem. I flashed to different roms on the phone modified latest from Secany and ported 6.5.5 and they both work. I will have to do more testing, but I am not sure how because it works for me.
Can you try attached file it should display some messages before it starts pkgTool.exe. You should see something like this "1. Path >>", "2. Par >>" and "3. Exe >> ". If you could write down what text was in those lines.
I found this is the main problem:
When the Dump ROM is progressing, there is an errer notify windows (pkgtool.exe meeting an error to exit. We are sorry to ...) .
I close the errer windows ,
After Dump ROM is finished,
I found there is a dump folder where a folder(name: .ROM) and a file(name:88f892ce-7f79-4718-bfc0-388c86c721a7.dsm) existed.
Only the .ROM folder and .DSM file not moved to the SYS folder.
After I moved the .ROM foler and the .DSM file to the SYS folder manually,Then run Build Rom again,everything is OK.
1.jpg 194.24K
75 downloads
If I make imgfs dump to modules, then run pkgtool manually. There is the runing log: (PKGTool.exe doesn't work fine)
[Core OS]
Windows Mobile-based Pocket PCs
[Versions]
SYS: 5.2.21883.5073
SYS: 5.2.0.5073
OEM: 5.2.0.5073
NET: 2.0.7045.0
[Language]
0804 - Chinese (People's Republic of China)
[DPI]
192
[Certificates]
CN=Microsoft Windows Mobile PCA, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
CN=Samsung Electronics Co. CA - Samsung Root
[Missing Manifests]
45116509-e364-4775-9098-c25f0b1fbac2.dsm
d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
73b84140-9d9d-3ed2-f5a5-3ddae45a1c85.dsm
723fb954-d931-4348-b672-82a188e587b5.dsm
3c0e4a75-7ea3-49cf-84e6-57285dc2a07f.dsm
f924d38b-0419-deaa-f151-ed8f0d511a07.dsm