ER2003EDIT CANNOT OPEN I-MATE NEW ROM - Upgrading, Modifying and Unlocking

hi softworkz or any body
tried open new i-mate image rom with new er2003 and got message:
"Neither 'HTC' nor '921211' nor '0x25863614' nor '0x12345678' seems to be a correct password for the file. If you are sure this is a WM2003 update file you can try to enter an alternative password:"
is there something to be done?
shayon

Use the following:
NK.nbf - 0x20040304
ms_.nbf -0x20040305
radio_.nbf - 0x20040306
http://forum.xda-developers.com/viewtopic.php?t=7392

@Frog
Have you ever try it? can it be done?

Use ER2003 1.16 to open the ROM files, but i dont know how to cook ext-ROM because it differs from the O2 and T-Mobile ROM. Hope someone help on this matter.
Thanks

The extended rom is encoded
to decode try this:
Code:
xda2nbftool -x ms_.nbf ms.nba 0x25863614
del ms_.nbf
ren ms.nba ms_.nbf
to encode again try this:
Code:
ren ms_.nbf ms.nba
xda2nbftool -x ms.nba ms_.nbf 0x25863614
del ms.nba

frog said:
Use the following:
NK.nbf - 0x20040304
ms_.nbf -0x20040305
radio_.nbf - 0x20040306
http://forum.xda-developers.com/viewtopic.php?t=7392
Click to expand...
Click to collapse
guys. it is not working
here :
*********************************************************
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba 0x25863614
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba 0x12345678
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba 921211
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba HTC
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba 0x20040305
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba 0x20040304
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbftool -x ms_.nbf ms.nba 0x20040306
WARNING: this does not look like a nbf header, possible you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf
Usage: xda2nbftool [-u] { -c | -e | -d } inputfile outputfile password
-c : calculate crcsum of file
-u : updates the calculated checksum
-e : encrypt inputfile
-d : decrypt inputfile
-x : xor inputfile with password ( should be a number )
-sd : change devicetype
-so : change operatorname
-sl : change language
-sv : change version
-v : verbose
HimaUpgradeUt v0400, v0500 use password HTC
HimaUpgradeUt v0600 uses password 921211
HimaUpgradeUt v0910 uses xor with 0x89124137, 0x25863614 or 0x12345678
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba HTC
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba 921211
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba 0x25863614
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba 0x12345678
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba 0x20040304
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba 0x20040305
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>xda2nbf -d ms_.nbf ms_.nba 0x20040306
WARNING: this does not look like a nbf header, possible you provided the wrong p
assword
WARNING: checksum is not ok, possibly you provided the wrong password
C:\DOCUME~1\fofo\Desktop\XDA>
*************************************************************
i renamed the xda2nbftool.exe to xda2nbf.exe for faster work.
as u can see, i tried all the possible syntaxs, none works....
If anyone has any idea what is going on, please help, i read somewhre on the forum that er2003 V 1.2 is acting up, and that 1.16 is better, i cannot find 1.16 & sure 1.2 is not working, it keeps asking for a password, which I tried all the given ones in the forum, no luck.
awaiting one's responce.
Thank you.

keyboard file
*************************

Related

Problems on editing a rom of ASUS P525! Help!

Sir,
Are there anyone who can tell me how to change the CRC checksum after i had edited the rom (galaxy.cap) of ASUS P525 ?
xda3nbftool -x galaxy.cap nk.nba 0xA87BC0DF
prepare_imgfs.exe nk.nba -nosplit
viewimgfs.exe imgfs_raw_data.bin
*****add files*****
BuildImgfs.exe
make_imgfs.exe nk.nba -nosplit
xda3nbftool -c -u NK.nba
xda3nbftool -x NK.nba galaxy.cap 0xA87BC0DF
However it stop on checksum unit . "CheckSum Error! upgate fail "
Are there any misktakes i had made?
please do help me !!
Please Help
Hi,
I´m trying to learn how to cook my own Asus P525 ROM, and it´s very difficult, because some people don´t want or don´t like to share his knowledge.
Well, I´ve tried to do the same process as you but when I put this:
xda3nbftool.exe -x Galaxy.cap nk.nba 0xA87BC0DF
I received a error message with tell me tha ist not a nbf header or the password in not correct.
Can you help me?
Thanks in advance
Fernando

a problem with dumprom and HTC (Windows Mobile 6 Extract)

HI
i downloaded WM6CB and extract it now i have 2 nbf file
nk.nbf 64MB Size
ms.nbf 10MB Size (Empty_Extended_rom)
i want to extract these
I tested dumprom.exe and HTC64 Extended ROM Tool.exe but i can't extract these
if i use dumprom then i can't extract it when i use HTC64 and i use dumprom with nk.fat file argument then i can extract some files and get this error
Code:
9073265c - 907338b6 L0000125a o32 region_2 rva=00042000 vsize=000027f0 real=01f9
2000 psize=0000125a f=40002040 for coredll.dll
907338b8 - 907351b9 L00001901 filedata boot.hv
907351bc - 907380a4 L00002ee8 filedata default.hv
907380a4 - 907380a4 L00000000 rom_00 end
907380a4 - 9443fc00 unknown
i used this arguments
For NBF File
dumprom nk.nbf -d mydirectory\
dumprom -5 nk.nbf -d mydirectory\
For FAT File
dumprom -5 nk.fat -d mydirectory\
dumprom nk.fat -d mydirectory\
And I can't Extract Empty Rom with this way
I want to extract windows mobile 6
Please help me for further information
Thanks
Regards

Is there som cookers here?

In the past I cooked some ROM for my old device Trinity P3600 like this:
http://forum.xda-developers.com/showthread.php?t=367317
Now I want to buy an excalibur and i want to try to cook a ROM for this device.
is there any body with wich I can exchange ideas and experiences?
for examples. How can I extract the XIP in this device?
There is already some cooked rom for this device?
I'm tryng to port the last Vox ROM (ake 0.4.4) in the excalibur.
Some cookers come here?
Ok.
I discovered something
For extract IMGFS:
With NBHTool extract Windows.nb afther with Tadzio tool:
Code:
rename windows.nb os.nb
copy Os.nb Os.nb.payload
ImgfsFromNb os.nb.payload imgfs.bin
ImgfsToDump imgfs.bin
For extract XIP:
Code:
RomMaster os.nb -v 0 -w 5 -b 0x00217800 -x -o xip.bin
mk xip
dumprom xip.bin -5 -d XIP >NUL
Someone interested?

[Cooking] About XIP and initflashfiles.dat

I'm triyng to cook a wm6 ROM, only for fun.
I extracted the XIP with this command:
Code:
RomMaster os.nb -v 0 -w 5 -b 0x00217800 -x -o xip.bin
mk xip
dumprom xip.bin -5 -d XIP >NUL
strangely I found the initflashfiles.dat in XIP section and not in IMGFS section.
This send in error the buildos.exe.
How Can I solve?
I've to move initflashfiles to OEM/OEMLANG?
Another question.
THe newest utility from Bepe (Buildxip) Does it work fine with excalibur?
Anyone can help me?

Cook a rom for Vox (pb : initflashfiles.dat)

Hi,
I try to cook a rom based on an official rom for Vox (HTC FRA 1.34).
I would understand all steps of cooking, i have already made this :
1 - Extract RUU_Vox_HTC_FRA_1.34.406.1_4.1.13.54_03.10.90_Ship.exe to RUU_signed.nbh (7-zip)
2 - Extract RUU_signed.nbh to IPL.nb/PrimarySpalsh.nb/Radio.nb/SPL.nb/Windows.nb (nbhtool.exe)
3 - Dump rom Windows.nb with prepare_imgfs.exe and viewimgfs.exe
4 - Move dump files in OEM/SYS folders with PKGTool
If i understood well, i must extract XIP from Windows.nb, before cook.
I have tried some soft like nbsplit/rommaster/buildxip, but i have errors, could someone help me for this step ?
Thanks.
And sorry for my poor english.
fireburned said:
Hi,
I try to cook a rom based on an official rom for Vox (HTC FRA 1.34).
I would understand all steps of cooking, i have already made this :
1 - Extract RUU_Vox_HTC_FRA_1.34.406.1_4.1.13.54_03.10.90_Ship.exe to RUU_signed.nbh (7-zip)
2 - Extract RUU_signed.nbh to IPL.nb/PrimarySpalsh.nb/Radio.nb/SPL.nb/Windows.nb (nbhtool.exe)
3 - Dump rom Windows.nb with prepare_imgfs.exe and viewimgfs.exe
4 - Move dump files in OEM/SYS folders with PKGTool
If i understood well, i must extract XIP from Windows.nb, before cook.
I have tried some soft like nbsplit/rommaster/buildxip, but i have errors, could someone help me for this step ?
Thanks.
And sorry for my poor english.
Click to expand...
Click to collapse
have u try msflshtool
Thanks for this idea.
I test it, with this command :
msflshtool.exe Windows.nb -d
I obtain 3 files :
- Windows.nb.part0
- Windows.nb.part1
- Windows.nb.part2
Here is the part info :
Code:
***********************************************************
msflsh50dump v0.1 code by blueboy
***********************************************************
partinfo
part <0> offset <00000400> size <00217400>
part <1> offset <00217800> size <00333000>
part <2> offset <0054A800> size <03586800>
end
What is the newt step ?
Thanks you.
fireburned said:
Thanks for this idea.
I test it, with this command :
msflshtool.exe Windows.nb -d
I obtain 3 files :
- Windows.nb.part0
- Windows.nb.part1
- Windows.nb.part2
Here is the part info :
Code:
***********************************************************
msflsh50dump v0.1 code by blueboy
***********************************************************
partinfo
part <0> offset <00000400> size <00217400>
part <1> offset <00217800> size <00333000>
part <2> offset <0054A800> size <03586800>
end
What is the newt step ?
Thanks you.
Click to expand...
Click to collapse
usually it is in part0 or part1 ... use xipport to see which have the boot.hv & boot.rgu ... u only need those files ... around 20-40Kb files
Then u can put it in ROM folder in ur Kitchen
Thank you cruzzmz for your replies
I used XIPort to extract Windows.nb.part0/Windows.nb.part1.
I obtain this :
Code:
Windows.nb.part0
OUT\
PARTHDR.txt
ROMHDR.txt
\FILES
boot.hv
boot.hv.imageinfo.txt
ceconfig.h
ceconfig.h.imageinfo.txt
default.hv
default.hv.imageinfo.txt
initobj.dat
initobj.dat.imageinfo.txt
user.hv
user.hv.imageinfo.txt
\MODULES
busenum.dll
cecompr.dll
ceddk.dll
cereg.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
imgfs.dll
mmtimer.dll
mspart.dll
nk.exe
OMAP850_SDHC.dll
ONDisk.dll
packageinfoapi.dll
pm.dll
ramdisk.dll
rawfs.dll
regenum.dll
romfilter.dll
sdbus.dll
sdmemory.dll
serial.dll
uldrui.dll
updateapp.exe
busenum.dll.txt
cecompr.dll.txt
ceddk.dll.txt
cereg.dll.txt
certmod.dll.txt
coredll.dll.txt
device.exe.txt
devmgr.dll.txt
diskcache.dll.txt
encfilt.dll.txt
fatfsd.dll.txt
fatutil.dll.txt
filesys.exe.txt
fsdmgr.dll.txt
imgfs.dll.txt
mmtimer.dll.txt
mspart.dll.txt
nk.exe.txt
OMAP850_SDHC.dll.txt
ONDisk.dll.txt
packageinfoapi.dll.txt
pm.dll.txt
ramdisk.dll.txt
rawfs.dll.txt
regenum.dll.txt
romfilter.dll.txt
sdbus.dll.txt
sdmemory.dll.txt
serial.dll.txt
uldrui.dll.txt
updateapp.exe.txt
Windows.nb.part1
OUT\
PARTHDR.txt
ROMHDR.txt
\FILES
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm.imageinfo.txt
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm.imageinfo.txt
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm.imageinfo.txt
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm.imageinfo.txt
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu.imageinfo.txt
boot.hv
boot.hv.imageinfo.txt
boot.rgu
boot.rgu.imageinfo.txt
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm.imageinfo.txt
initflashfiles.dat
initflashfiles.dat.imageinfo.txt
mxip_initdb.vol
mxip_initdb.vol.imageinfo.txt
mxip_lang.vol
mxip_lang.vol.imageinfo.txt
wince.nls
wince.nls.imageinfo.txt
\MODULES
busenum.dll
cachefilt.dll
cecompr.dll
ceddk.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
fsreplxfilt.dll
hd.dll
HtcFsdspy.dll
imgfs.dll
mspart.dll
nk.exe
ONDisk.dll
osaxst0.dll
pm.dll
ps2fatutil.dll
regenum.dll
busenum.dll.txt
cachefilt.dll.txt
cecompr.dll.txt
ceddk.dll.txt
certmod.dll.txt
coredll.dll.txt
device.exe.txt
devmgr.dll.txt
diskcache.dll.txt
encfilt.dll.txt
fatfsd.dll.txt
fatutil.dll.txt
filesys.exe.txt
fsdmgr.dll.txt
fsreplxfilt.dll.txt
hd.dll.txt
HtcFsdspy.dll.txt
imgfs.dll.txt
mspart.dll.txt
nk.exe.txt
ONDisk.dll.txt
osaxst0.dll.txt
pm.dll.txt
ps2fatutil.dll.txt
regenum.dll.txt
The good files are in Windows.nb.part1 ?
Next step : copy boot.hv/boot.rgu in ROM/XIP folder ?
Thank you very much !
And another question, i have "missing files" when i use PKGTool :
Code:
[Missing Manifests]
(Maybe):\ROM\XIP\b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
(Maybe):\ROM\XIP\7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
(Maybe):\ROM\XIP\42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
(Maybe):\ROM\XIP\e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
(Maybe):\ROM\XIP\966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
It's a problem ?
fireburned said:
And another question, i have "missing files" when i use PKGTool :
Code:
[Missing Manifests]
(Maybe):\ROM\XIP\b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
(Maybe):\ROM\XIP\7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
(Maybe):\ROM\XIP\42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
(Maybe):\ROM\XIP\e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
(Maybe):\ROM\XIP\966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
It's a problem ?
Click to expand...
Click to collapse
dont think it is a problem as long as when u do buildOS u dont get any error (hint: if there is error check the temp folder open log.txt)
I created a *.bat file wich does this :
1- nbhextract "RUU_Signed.nbh" to "00_IPL.nb 01_SPL.nb 02_MainSplash.bmp 02_MainSplash.nb 03_GSM.nb 04_OS.nb"
2- dumprom.exe 04_OS.nb wich extract files in "Temp" folder :
Code:
boot.bin
msflsh.bin
romhdr.bin
\Imgfs (1599 objects)
\XIP (37 objects)
3- pkgtool.exe : Temp\Imgfs => Temp\Imgfs\OEM and SYS
4- move Temp\Imgfs\OEM and SYS in root kitchen directory
My problem :
* When i try to re-"BuildOS" (to test if my dump works), i have an error : Error, last status: "Creating initflashfiles.dat..."
I have found a file "initflashfiles.dat" in my ROM\XIP foler. What is the problem ?
Thanks you.
Help me please... I tried... But i'm blocked...
fireburned said:
I created a *.bat file wich does this :
1- nbhextract "RUU_Signed.nbh" to "00_IPL.nb 01_SPL.nb 02_MainSplash.bmp 02_MainSplash.nb 03_GSM.nb 04_OS.nb"
2- dumprom.exe 04_OS.nb wich extract files in "Temp" folder :
Code:
boot.bin
msflsh.bin
romhdr.bin
\Imgfs (1599 objects)
\XIP (37 objects)
3- pkgtool.exe : Temp\Imgfs => Temp\Imgfs\OEM and SYS
4- move Temp\Imgfs\OEM and SYS in root kitchen directory
My problem :
* When i try to re-"BuildOS" (to test if my dump works), i have an error : Error, last status: "Creating initflashfiles.dat..."
I have found a file "initflashfiles.dat" in my ROM\XIP foler. What is the problem ?
Thanks you.
Click to expand...
Click to collapse
I dont seem to hv that file on my ROM\XIP folder, maybe u can try deleting all files inside XIP except for boot.hv & boot.rgu
then try buildOS again
BTW what is the size of both files?
I deleted all files in XIP folder, except boot.hv/boot.rgu
boot.hv = 40 Ko
boot.rgu = 27 Ko
Again, BuildOS fails : Error, last status: "Creating initflashfiles.dat..."
When i search in OEM and SYS folders, i don't have a "initflashfiles.dat" file.
An idea ?
fireburned said:
I deleted all files in XIP folder, except boot.hv/boot.rgu
boot.hv = 40 Ko
boot.rgu = 27 Ko
Again, BuildOS fails : Error, last status: "Creating initflashfiles.dat..."
When i search in OEM and SYS folders, i don't have a "initflashfiles.dat" file.
An idea ?
Click to expand...
Click to collapse
dunno if this can help
If you did something like the following sequence:
typho5 -x nk.nbf
prepare_imgfs.exe 80040000-OS_0.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
Then the initflashfiles.dat should definitely be in the 'dump' folder.
Did you remember the -nosplit option for prepare_imgfs.exe?
Edit: Just a thought. The initflashfiles.dat is hidden plus the .dat extension is normally used by system files, so could it be something so simple as the fact that your explorer is not showing hidden and/or system files?
Click to expand...
Click to collapse
seems like the initflashfiles.dat is in the dump folder after u do a viewimgfs
You can put initflashfile.dat inside imgfs (for example OEM/OEM_LANG_XXX) and delete it from XIP.
Buildos.exe from Bepe search initflashfiles.dat insiede IMGFS:
cruzzmz : I tried your solution
Code:
typho5 -x nk.nbf
prepare_imgfs.exe 80040000-OS_0.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
But, in dump folder, i haven't initflashfiles.dat
I tested several solutions, and each time, initflashfiles.dat is in my XIP folder.
cicciocant : I tried to put initflashfiles.dat in dump folder, and run PKGTool, but file is not copy to OEM_Lang_XXXX folder (missing dsm ???), and BuildOS fails, with same error.
I tested to put initflashfiles.dat in OEM_Lang_XXXX manualy, and i have an other error when i try to BuildOS : "initflashfiles.dat is a directory not a file! copying the File!!!"
In my XIP folder, i have :
Code:
busenum.dll
cachefilt.dll
cecompr.dll
ceddk.dll
certmod.dll
coredll.dll
device.exe
devmgr.dll
diskcache.dll
encfilt.dll
fatfsd.dll
fatutil.dll
filesys.exe
fsdmgr.dll
fsreplxfilt.dll
hd.dll
HtcFsdspy.dll
imgfs.dll
mspart.dll
nk.exe
ONDisk.dll
osaxst0.dll
pm.dll
ps2fatutil.dll
regenum.dll
42d1aab7-6dfa-4c03-9797-d66f7620883d.dsm
7da1c1a8-1fd2-4a18-a081-84e4825266b1.dsm
966f2a5f-b510-8a60-28bc-6c06a3376c66.dsm
b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm
b5332311-48f1-4b76-ad70-8efa5db8fa3a.rgu
boot.hv
boot.rgu
e7cdacc2-b776-1926-fd10-4b8c9b712e9b.dsm
initflashfiles.dat
mxip_initdb.vol
mxip_lang.vol
wince.nls
An idea ?
And thanks for your help.
seems like my rom that i cooked doesnt have initflashfiles.dat in the XIP folder.
Maybe you can try ask around in hypercore kitchen thread
Thanks cruzzmz, i posted my question.

Categories

Resources