Develop Bugs

ER2003EDIT CANNOT OPEN I-MATE NEW ROM

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
*************************

xda2s rom problem

i had a big problem with my new xda2s
i bought from states and it appear to be with an asian rom
and i tried to do a rom upgrade with an imate pda2k(languege addtion)
with this mistake i also retrospectively found that my process was wrong (active sync was on , usb port was connected to hub..........
no the phone is dead
all what it shows is usb v2.06 when on the cardle and serial v 2.06 when off cardle
no hard or soft reset
now heeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeelp
i tried mda3 rom change from german to english but did not work it give me country id error.
and to make the problem complete i don't know my rom version or radio version ?????????
can anyone help me or at least give an idea where to get it fix here in canada????????

Download the english rom from the following link and try to reflash your rom;
ftp://ftp.clubimate.com/support/PDA2k_CDLWWE_11222_169_10200_SHIP.zip

What is the operator id
what operator id did u use. its not o2 for the xdaIIs. its something else. let me know too if u find out

Hi, i have downloaded that rom,... now available from "ftp://ftp.clubimate.com/Temp/" by the way. And i am getting counrty id error? Would you be able to help? Im pretty new to all this.
Regards, Ben.

XDA IIs Asian Rom Operator Code & Steps for Changing
the opeartor code for XDA IIs Asian Rom is
O2ASI001
Step by Step Insatructions how do change it:
1. Download the rom files and extract to a folder say XDAROM
2. Now create a file using notepad and save it as .bat file (remember the .bat extension, NOT .txt)
3. Add the contents below to the bat file
Code:
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -so O2ASI001 ms_.nba
xda3nbftool -so O2ASI001 nk.nba
xda3nbftool -so O2ASI001 radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
Now save this file in the folder where you have extracted your rom images in this example it is XDAROM.
4. You need xda3nbftool.exe which i have uploaded, download it and copy it to your XDAROM folder.
5. Now simply run the bat file and u r done.
6. Connect your device with the usb and run BaUpgradeUt.exe file in the folder XDAROM.
that it you r done!
enjoy
jeet

thanx a tonne jeet...
hey jeet,
seriously thanx to u for providing the operator id as I didnt have it so I couldn't upgrade that xdaIIs. and overall that set was of my brother-in-law. his mood was really upset when his phone got stuck in bootloader mode. finally it was done today and u should have seen his face when his phone started. my jiju's really thankful.
-thanx jeet...
happy new yr

Dead MDA III
Hello... I have a T-Mobile (UK) MDA III which I managed to break by trying to update the firmware.
Now it is stuck in Bootloader mode! I have tried re-flashing the O2 XDA IIs firmware, but it still does not work (Operator Code Error).
Does anyone know of a way to re-flash this unit with the very latest code?
Many thanks

Uni Rom kitchen problem

after I've edit the rom of Wm6 , it'll auto off at slashscreen after flash
please correct me if anything wrong ..
here's my steps :
HTC64 Extended ROM Tool , decode the rom and then...
prepare_imgfs.exe nk.fat -nosplit
viewimgfs imgfs_raw_data.bin
BuildImgfs
set _FLATRELEASEDIR=.
rgucomp -o dump\default.hv -nologo > default.rgu
rgucomp -o dump\user.hv -nologo > user.hv
then I've added other wince.nls and fonts in "dump" directory .
and edit default.rgu , user.hv by ultraedit . added "REGEDIT4" at the first line , added some lines on initflashfiles.dat.
then repack :
copy default.rgu boot.rgu
set _FLATRELEASEDIR=.
rgucomp -b
attrib -s -r -h dump\default.hv
copy boot.hv dump\default.hv
attrib -s -r -h dump\user.hv
copy user.hv dump\user.hv
BuildImgfs
make_imgfs nk.fat -nosplit
use HTC64 Extended ROM Tool encode again . and flash .
any problems in these step ? Please correct me , Thanks alot !!

Building roms
Hi,
Ha... here you are,
will try this tomorrow.
Leo
Leies said:
after I've edit the rom of Wm6 , it'll auto off at slashscreen after flash
please correct me if anything wrong ..
here's my steps :
HTC64 Extended ROM Tool , decode the rom and then...
prepare_imgfs.exe nk.fat -nosplit
viewimgfs imgfs_raw_data.bin
BuildImgfs
set _FLATRELEASEDIR=.
rgucomp -o dump\default.hv -nologo > default.rgu
rgucomp -o dump\user.hv -nologo > user.hv
then I've added other wince.nls and fonts in "dump" directory .
and edit default.rgu , user.hv by ultraedit . added "REGEDIT4" at the first line , added some lines on initflashfiles.dat.
then repack :
copy default.rgu boot.rgu
set _FLATRELEASEDIR=.
rgucomp -b
attrib -s -r -h dump\default.hv
copy boot.hv dump\default.hv
attrib -s -r -h dump\user.hv
copy user.hv dump\user.hv
BuildImgfs
make_imgfs nk.fat -nosplit
use HTC64 Extended ROM Tool encode again . and flash .
any problems in these step ? Please correct me , Thanks alot !!
Click to expand...
Click to collapse

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?