Related
Hi Folks,
o2 Germany has now published an upgrade to ROM version 1.60.52 GER.
http://hilfe.o2online.de/srvs/DATA/...download/xda_software/neu/xda_16052ger_o2.exe
THIS VERSION IS GERMAN ONLY (ALTHOUGH INSTALLER IS IN ENGLISH), SO ONLY UPGRADE WHEN YOU HAVE A GOOD COMMAND OF THE GERMAN LANGUAGE OR INTEND TO STUDY ANOTHER FOREIGN LANGUAGE!
o2 kept us waiting for a long time, but it looks like it was worth waiting and some old problems (like HZ-Indicator; Bluetooth etc.) have been fixed (at least they tried to!).
Have fun, any comments on the new version are highly appreciated!
bobpopo
Hi!
when i extract extended ROM image file, it can't be accesed by ROM editor from Wiki.. what's wrong?
now that we have thsi update, the question is: do we get a wm2k3se update and if so, when?
Um... is the language in german, or in english, or can it be switched to english?
First Upgrade leads to "Country Error" - Downgrade
After reading some postings in a German forum I already knew about the problem for those using XDAII with T-Mobile ROM 1.60.00 GER:
The update program won't start, displaying "Country error" (or sth. like that). This problem is solved by downgrading to T-Mobile 1.03.00 (which can be downloaded on the same page as the upgrade). After that upgrade works fine, leading to:
ROM-Version: 1.60.00GER
ROM-Date: 12/03/03
Radio-Stack: 1.10.00
Protokoll-Vers: 1337.18
ExtROM-Vers: 1.60.52 (attached)
Compared to the German T-Mobile 1.60 ROM, the radio stack seems to be improved (from 1.06.01 to 1.10.00) and the o2 ExtROm was updated (from 1.03.27 to 1.60.52). Also some good news for the o2 subscribers in Germany using the XDAII: The Homezone control seems to be fixed -until now I did not spot any problems.
Enjoy (and report bugs)...
HI Is this safe to use on the UK XDA II?
Should I wait until the uk release?
The only thing that I am waiting for mainly is a Bluetooth handsfree profile.
@oliven_99
How's your german... 'cause this is a true german update ;-)
links für downgrade pls
"The update program won't start, displaying "Country error" (or sth. like that). This problem is solved by downgrading to T-Mobile 1.03.00 (which can be downloaded on the same page as the upgrade). After that upgrade works fine "
Where can we download T-Mobile 1.03.00
Pls post the link for the german T-Mobile 1.03.00 downgrade because I also got the Country Error!
http://www.t-mobile.de/downloads/company/t-mobile/mda_2_ver_10305.zip
But remember: Downgrade and Upgrade is in German!
It works
Many Thanks!
Does anyone knoews why the ext. ROM Version 1.60.52 GER can not be opened, edited with Windows Mobile 2003 ROM Editor from Wiki?
Homezone Indicator
Cool!!!
The homezone indicator seems now to work stable!
Well done, O2 Germany
CAUTION!!!
Today I got shocked when I tried to modify the ExtROM and almost ruined it. After the common way with ER2003edit did not work out, I tried to downgrade the ExtROM to 1.03.05 (T-Mobile) with the old HimaUpgradeUt that came with that version.
After doing that, the XDA did not work anymore, just showing "serial USB 1.1". After that I tried to flash my cooked ExtROM (merger out of the latest ExtROM and some other cabs), what left my XDA still without function. Then slowly panic arose and I flashed the latest, complete upgrade (1.60.52) again, what led to a standard & working XDAII.
Now I am happy that I did not ruin the device, but still looking for a way to modify the ExtROM. Maybe it is time for those who really know what they are doing to give a little hint to the masses, how this can be solved...
INSTRUCTIONS: Homecooked (locked) ExtROM with o2 GER 1.60.52
Okay, finally I figured out, how to flash the new version with my own ExtROM:
If you are upgrading your XDAII from the MDAII 1.60 ROM, please prepare your XDAII for flashing by downgrading to MDAII 1.03 ROM as explained above. Otherwise you will get a country error.
1. download xda_16052ger_o2.exe from o2 Germany
http://hilfe.o2online.de/srvs/DATA/...download/xda_software/neu/xda_16052ger_o2.exe
2. download ER2003Edit
http://wiki.xda-developers.com/wiki/ER2003Edit
3. download tool Decode extended ROM below (thanks Jos!)
4. use WinRAR to extract the upgrade files from xda_16052ger_o2.exe (you'll get six files: 3 Hima* and 3 *.nbf)
5. unzip files from Decode extended ROM to a separate folder and add ms_.nbf (from step 4) and run decode.bat
6. after decoding, you can open the file ms_.nbf with ER2003Edit, modify the ExtROM-Files and splash images.
7. after modifying, save and run encode.bat, but only perform the encoding step, afterwards copy ms_.nbf back to the files extracted in step 4
8. now start HimaUpgradeUt.exe and flash XDAII as usual, but with your individual ExtROM
(According O2 this step can take up to 1 1/2 hours!)
This upgrade worked out with my German XDAII with (locked) ExtROM. In former versions of the upgrade utility it was possible, to upgrade the ExtROM only, one just had to remove the unwanted *.nbf before upgrading. But now it looks like only a full upgrade will lead to a working XDAII. Otherwise it will be dead but can be recoverd by giving a full upgrade with all three parts.
I will certainly only be held liable for ruining my own XDAII - what you do to your gemstone is on your own risk. There might be easier ways, please drop a note if you find one...
New splash screen...
Just to make it complete:
While installing the new ROM I noticed that there is a second splash image, which is changed to the old one after executing O2DECustomize.sa.CAB. As I liked that new splash screen better, I have changed it within the cab file and removed some other useless example files.
Just replace the old O2DECustomize.sa.CAB in your ExtROM with the one below or copy to and execute on your XDAII to change splash screen (will stay until the next hardreset).
The RSB-Converter is just a tool that I found while waiting for ages to get a trial key for ACDSee. Take this tool if you want to convert your individual splash screeen to the required RSB format. Find further information on creating individual splash screen here:
http://forum.xda-developers.com/viewtopic.php?t=3759&highlight=splash1+nb
After creating your favorite splash image (as *.bmp, 24 bit) cut 13 pixel from the left side of the picture and paste it to the right side (after moving the big part to the left). If you don't do that your splash won't fit the screen properly.
Hi all
For those how what to save close to 2MB space in their ext-rom I have a set of updated files
O2_DE_custimized has additional the settings made in
Broadcast_GER
MIDI_GER_reg
O2_AP_DE_20040118
O2_DE
version_AKU1 which you don't need anymore.
removed is O2 movie, spash images, and O2 ringtone
additonal the regfile makes the ext-rom visible and activates cleartype by default.
CameraRD132_GER removed help file and button graphic
ClearVue233_GER removed ads/demo files
regards, Alex
At the german forum "ppc-welt-community" a user reported, that he tried the update with his xda1 an the upgrate worked.
I doubt about this...what do you mean? Should it be possible to upgrade the xda1?
:?
Hey, I found the entry in the forum, there is no way written that somebody actually manged it or was so stupid to try it.
I think it won't even start, as the bootloader are not the same and the UpgradeUtility will (hopefully) not start at all.
There is an upgrade to WindwosMobile2003 for XDAI this is what he writes about, this is not the upgrade which is here talked about.
Alex
Re: New splash screen...
bobopopo said:
The RSB-Converter is just a tool that I found while waiting for ages to get a trial key for ACDSee. Take this tool if you want to convert your individual splash screeen to the required RSB format.
Click to expand...
Click to collapse
Tried to convert a *.rsb File and got:
"RSB Version not supported"
is there anything i do wrong or cant the program convert all files?
any ideas.....
Re: New splash screen...
Know that I had the same problem, doesn´t always work. But it is so long ago, that I cannot remember clearly, sorry...
pbelcl said:
bobopopo said:
The RSB-Converter is just a tool that I found while waiting for ages to get a trial key for ACDSee. Take this tool if you want to convert your individual splash screeen to the required RSB format.
Click to expand...
Click to collapse
Tried to convert a *.rsb File and got:
"RSB Version not supported"
is there anything i do wrong or cant the program convert all files?
any ideas.....
Click to expand...
Click to collapse
Hi guys,
a new version of ER2003Edit is available from the wiki page:
http://wiki.xda-developers.com/wiki/ER2003Edit
New features and improvements:
- provides support for the new upgrade tool version (0.9.1.0) used by the latest T-Mobile and O2 updates
- supports editing of the header information (DeviceID, Operator and Language) in order to circumvent the country code error
- some other fixes and improvements
Best regards,
softworkz
Thnx dude! At last we got a program to modify the header. I guess this makes a lot of XDA owners very happy.
Great work!
Late...
Thanks Softworkz, great work again. It really looks like an even more powerful tool, but there seems to be a little bug (or I am doing something wrong):
After upgrading ER2003Edit to the new version, I cannot open the ms_.nbf anymore. When I try to open the file, ER2003Edit always crashes, although I left the file unbmodified.
Downgraded to the old version again and there it works, although I have to decode and encode the files by myself.
Any suggestions?
No problems opening the ms_.nbf here after doing the upgrade. Running Win XP sp1.
Try uninstalling the old one completely then install the new one...
Works great!
Late...
is it a misunderstanding between header-information and encryping ???
I think Er2003edit does not do the encryption/decryption so far.
Hey Softworkz...
this would be a great improvement as I guess all coming
extended roms will be encrypted.
Alex
Tried uninstalling and re-install but that didn't help. As far as I remember, Softworkz tool is not able to edit encrypted ms_.nbf.
But on my machine (Win XP pro 2002 SP1) the program always crashes when opening an non-encrypted ms_.nbf...
I will use the old one as a workaround, I don't need to change the header so this should be fine.
some programming tips:
It should not be very difficult to implement the xor decryption, just xor each DWORD in the file with 0x25863614 after loading it in memory, and before saving it back to the file.
also, if you verify the header checksum after loading the file, you should be able to detect that the file you are loading is actually a decrypted nbf file.
and another check to see if at offset 0x70040 there is a valid bootsector, with
the 'MSWIN4.1' and 'FAT16' strings should prevent it from crashing on invalid files.
Ouch, I just found out that the wrong version of xda2tools.dll was included with the setup. I have made available a new version (1.2.20) to fix this. (see wiki page)
Some details about ER2003Edit:
You do not need to uninstall old versions before installing newer ER2003Edit versions.
The new version (1.2.x) is able to perform XOR-De-/Encryption. When opening an extended ROM file ER2003Edit first checks if it is encrypted by looking for the presence of the dashes in the header.
If those are present in the right places ER2003Edit opens the file as usual. If the dashes are absent ER2003Edit tries to decrypt with all of the three XOR-Passwords (). If none of those passwords produces a file with a correct header a prompt is shown which lets you enter your own password.
The decrypted (or a copy of the unencrypted) ROM file is saved to the temp folder. When saving with ER2003Edit the file is encrypted again (in case the original file was encrypted) and is saved to the original location overwriting the initial file.
Itsme: The "dash-check" was used because the CRC-check in your code was always true (didn't look into it further).
The new version supports auto-detection of the ROM type in order to edit the header of the other 2 ROM files (NK and Radio_), too. The "error accessing image files" message is now suppressed for these files.
Nevertheless modifying the header of those files is useless and I didn't figure out how to access the file structure in those files (doesn't look like a FAT image).
Best regards,
softworks
Okay, that explains the problems I experienced. As soon as I am back home I will give it a try. If it works it will be a nice & powerful tool...
==> seems to work perfectly. So there are no more obstacles. Next stage will be an Upgrade to 1.66.xx... :shock:
ok, now it works.
currently, a non-matching crc value only results in a printed warning, maybe I/you could add an extra parameter to the file processing functions, which get the result of the crc-check.
or maybe even better, raise an exception, for the warnings.
ER2003 crashes opening new O2 extended ROM Files
Hi softworkz,
first off all thanks for your great work!
Using the new version of er2003 i cant open the ms_.nbf file of the latest O2 upgrade (1.60.52). It crashes every time. Opening and editing my self created ext. ROM based on T-Mobile Update 1.60.07 works great.
Whats wrong with my installation? If you wish i can send u my Win XP error report.
Escargotet
Sorry for posting, was 2 stupid to read forum first!
Sorry for posting, was 2 stupid to read forum first!
Hi all
Please help to clarify as there are some inconsistances...
(or I am wrong, but will run into this problem)
Er2003edit will try to modify the header information in the NK and Radio_mbf but this will not be successfull and I still will get the Country ID error, is that right ???
As far as bobopopo expierenced the new upgrade utility will not run parts of the upgrade but rather leave the machine useless.
So there is a missing link...
Alex
itsme said:
ok, now it works.
currently, a non-matching crc value only results in a printed warning, maybe I/you could add an extra parameter to the file processing functions, which get the result of the crc-check.
or maybe even better, raise an exception, for the warnings.
Click to expand...
Click to collapse
The CRC check does not work in your code. XORing with a wrong password results in the following message:
WARNING: this does not look like a nbf header, possible you provided the wrong password
But this gets printed as a result of the "dash-check". If the crc-check would fail, a different message would be printed:
WARNING: checksum is not ok, possibly you provided the wrong password
But this message never gets printed because (filecrc != crcsum) never occurs (for whatever reason).
Xant said:
Hi all
Er2003edit will try to modify the header information in the NK and Radio_mbf but this will not be successfull and I still will get the Country ID error, is that right ???
Click to expand...
Click to collapse
No. Er2003Edit can open NK and radio ROM files and edit the header. Er2003Edit automatically re-encrypts the newer ROM files (XOR-Method).
Er2003Edit decrypts older ROM files (DES-Encrpytion), lets you edit the header and save the file but it does not re-encrypt these ones (use xda2nbftool). A message is displayed in this case to remind you to encrypt the file.
Xant said:
As far as bobopopo expierenced the new upgrade utility will not run parts of the upgrade but rather leave the machine useless.
Click to expand...
Click to collapse
AFAIK the upgrade tool will only look at the extended ROM's operator field. Anyone please correct me if I'm wrong about that.
softworkz said:
Xant said:
As far as bobopopo expierenced the new upgrade utility will not run parts of the upgrade but rather leave the machine useless.
Click to expand...
Click to collapse
AFAIK the upgrade tool will only look at the extended ROM's operator field. Anyone please correct me if I'm wrong about that.
Click to expand...
Click to collapse
I confirm what bobopopo claims, i tried only flashing the ms_.nbf, and it totally messed up my machine (stuck in bootloader), i had to reflash all three to get it to work again
nargalzius said:
softworkz said:
Xant said:
As far as bobopopo expierenced the new upgrade utility will not run parts of the upgrade but rather leave the machine useless.
Click to expand...
Click to collapse
AFAIK the upgrade tool will only look at the extended ROM's operator field. Anyone please correct me if I'm wrong about that.
Click to expand...
Click to collapse
I confirm what bobopopo claims, i tried only flashing the ms_.nbf, and it totally messed up my machine (stuck in bootloader), i had to reflash all three to get it to work again
Click to expand...
Click to collapse
I knew about this. I was just stating that the header of NK and Radio is irrelevant for the upgrade tool and is not responsible for the country code error.
SPV M1000
Does it work with SPV M1000 version
loade ER2003 started it and stay on the ROM info screen :?
Hi,
just a tip for opening the latest ROM files with ER2003Edit:
ER2003Edit has a file type selector in the file open box which is by default set to autodetect.
in autodetect mode ER2003Edit tries all encryption passwords it knows for any type of ROM (NK,Radio,ms_)
when using autodetect mode and your ROM does not get detected and you enter the correct password manually, you will receive an "Error accessing image files" message
To prevent this message choose the correct type of ROM (ms_.nbf) from the file type selector of the file open dialog and enter the password
ER2003Edit can open and edit all types of ROM files now in order to let you change the language and device type settings (to prevent country code error)
Tip: Opening ROM files is always faster when you do not use autodetect mode!
BTW here are the passwords for the ITA-Rom:
ms_.nbf: 0x20040305
nk.nbf: 0x20040304
radio_.nbf 0x20040306
A new version of ER2003Edit will have these passwords built in, but I currently do have no time for a new release just to include the passwords.
Enjoy!
fantastic
thank you very much
Works
Thanks
Softworks, are the the old passwords hardcoded into the app?
I reckon on your next update, maybe you could just make the app read an XML (or text, whatever) file with the passwords. So you can easily just add passwords in the future onto the text without having to recompile a newer version.
Also, since when talking about XDAII files, we're only talking about 3 filenames which never change. Maybe you could make a load process to simply check the filename which has been opened and use the corresponding "file process" to open it. Sort of like instead of autodetect when you open files. Have a simple check that checks wether one clicked either of the 3 files, then have a script that mimmicks selecting manually the filetype instead of "autodetect." That should eliminate the "nuances" of opening files (especially helpful for us n00bs hehe)
Cheers,
Carlo
Sorry, Iwould like to ask how / where to find the password of the images?
Thanks!
Hi All,
I have images which can't open by ER2003edit V1.2.20, it say the password is incorrect. Anyone can help or teach?
The rom image is from O2, the rom version is 1.60 or higher.
Thanks!
Can someone help me out too, it won n't seem to work with me.
d.zee said:
Can someone help me out too, it won n't seem to work with me.
Click to expand...
Click to collapse
Cant find them either.... Please help
See here:
http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
Here is a patched version of ER2003Edit.exe that has the new 3 passwords. Auto detection now works. :lol:
Just unzip then copy it over installed ER2003Edit.exe usually found in
C:\Program Files\softworkz\ER2003Edit\ER2003Edit.exe
RE
Hi!
Thanks. It works.
:lol:
PDA: O2 XDA II
ROM Version: 2.06.00WWE
Radio Version: 1.18.00
ExtROM Version: 1.12.924WWE (from IIs)
OS: Windows Mobile 2003 Second Edition
OS Version: 4.21.1088 (Build 14132)
Any reason I am getting shcksum errors?
I chenaged the content of ms_.nbf save it, and tried to flash it, but I gor error 122 - checksum error?
Any known reason for that?
Looks like I am out of my depth but its worth a try
I have a blueangle and have worked out that there are more tools on in Himalaya than for us.
I have further worked out that the upgrade works in the same way.
So I would think that this tool does, Well I am either wrong or just dumb.
Is my undersatnding correct that this application would only have the paswords for the at that time Known rom realeases.
Is my understanding that even with a password out of a xda3nbtool this toll will not work if you add it in the dialog.
Thus I seem to find that if I fill in the device name, op and lang as well as pasword I fail, same is true if leave them blank.
Please help me out or point me in the correct direction
Thanks
Hi,
does anyone know a program or a howto for editing Asus MyPal ROM Updates? In fact I only have to add a single file.
Thanks for any response
Martin
First I appologize for the delay in the availability of this ROM. I was out of town on some business, and the site was down again for a certain time.
To get down to the details, this ROM is the complete set of all three .nbf files, I chose the 2.06 NK.nbf because the cleartype fonts are way better than the 2.02. The radio stack included is version 1.18, and the extended ROM (ms_.nbf) is a customized 2.06.100a, which is a mixture of the extended ROM that dcs posted, the one that came with the 2.06 ROM from the mystery guy and the official Asian 1.60.44 ROM.
I had to remove a couple of the Asian telco provider settings because there was no more space left in the extended ROM since the new versions of the software had larger file sizes than before, and the AutoConfig for Asian telcos alone takes up a lot of space too.
I still included the Extended ROM Viewer and almost all of the newer versions of the software included in the extended ROMs posted by dcs and the mystery guy.
The following telco providers were removed (due to their file sizes being the largest):
1. 1010
2. One2Free
The Socket SDIO Wi-Fi that were available in the previous ROM I posted were also removed due to the lack of space, the SPB GPRS Monitor that was provided as part of one of the extended ROMs posted was also removed. The thumbpad driver is in the extended ROM but does not auto-install, since some times it causes problems, you may install it separately by just clicking on the cab file.
The files removed are included in the .ZIP file so that they may be installed separately if desired.
I would like to thank dcs,mamaich, the mystery man and all other developers who contributed to this endeavor.
RE
Hi ZeroXtreme!
Thank you very much!
Could you post the breakdown of the content here?
Thank you again
Nice work ZeroXtreme
ZeroExtreme is my hero !
Customized ROM Content
NK.nbf = 2.06 (Mystery Man)
Radio_.nbf = 1.18 (dcs)
ms_.nbf = 2.06.100a (Mixed with dcs ms_.nbf, Mystery Man ROM and official Asian 1.60.44)
Extended ROM Contents:
CameraRC141_WWE.sa.CAB
MIDI561.sa.CAB
CprogHook.WM2003_2577.CAB
LoadDialogInit_MS_10150402.sa.CAB
MMS_v2.0.0.13_BA_WWE_0831.CAB
Caller_ID_WWE_RC10.CAB
EmailWiz_v1.01.0003_NL_1027.CAB
IntelliDialer_T-Mobile_WWE_RC10.CAB
IntelliPad_TMO_WWE_B12.CAB
Version_OU.sa.CAB
ClearVue3.4.381WWE_0616_Ozonup.sa.CAB
Extended_ROM_viewer.CAB
sales_service.CAB
hk_html.CAB
BTPSKeyUpdate_003.exe
Autoconfig.txt
Autoconfig.exe
Autoconfig.exe
TPDisable.exe
TPEnable.exe
Also all of the Asian telco settings except the ones listed in the first post that were removed.
it'a Chinese version or English version?
cool thak a lots
Version
vbexpert said:
it'a Chinese version or English version?
Click to expand...
Click to collapse
Its an english version all the way.
Problem...
Hi Zero,
Would like to check with you.. I got this problem. After flashing everything, some how..after booting up.. there is this error.. "Connection Flash Manager" stating "Saved data is corrupted, System will erase all data to fix this error!" But even after i click yes.. the problem will still arise no matter when i softreset. Any idea what is going on?
Thanks
Ranma
Re: Problem...
RaNmA_ said:
Hi Zero,
Would like to check with you.. I got this problem. After flashing everything, some how..after booting up.. there is this error.. "Connection Flash Manager" stating "Saved data is corrupted, System will erase all data to fix this error!" But even after i click yes.. the problem will still arise no matter when i softreset. Any idea what is going on?
Thanks
Ranma
Click to expand...
Click to collapse
I am not too clear about the problem, you flashed your device with the ROM I posted?
This did not happen to me during the multiple times I flashed my device and my dad's device.
I am a bit puzzled here, can anyone help in this matter? ANy similar experiences?
It's so difficult to download! :? I must have tried at least 6 to 7 times. Each time it just stop there.
hi people, i m new to this forum and new to xda2. Just wondering, how do u guys download and load up all the upgrades? hope u pros can give me some pointers.... thanks in advance
Finally managed to download the file. Do I need to do anything before installing the new ROM?
I had once tried to upgrade my unit (blame it on initial enthusiasm, I'd seen all these talks about upgrading to newer ROM versions everywhere on the net that I downloaded an upgrade 2 weeks before I actually bought my device) with a ROM version I had downloaded from O2's UK (The unit was bought from singapore/Honkgkong...Asia ROM presumably)site which naturally and the consequenses were very depressing , I was left with a dead machine on my hands and nobody I knew could be of any help. Anyway that had been taken care of a couple of days back when it reflashed at an authorised service centre.
Well that being that , now that its working fine and now that I see all this talk about windows mobile 2003 SE here I have this irresistable urge to try upgrading mu unit to run SE.
A couple of things before I try to get adventurous
1)How do I do a backup of of EVERYTHING ON MY MACHINE ( Original BASIC/Just out of the box/First time run software included ) So that I don't have to take a week off work just to get the unit reflashed.
2) How do I do a restore all of the backed up data on my device if the 2003SE upgrade doesnt work? From what I have learnt , it isnt anything like a regular computer where just about anyone can format boot and reload windows if it crashes.
I figure a dead PPC is like a regular computer with a dead bios.
I can understand that this post is about 5 times the length of a usual post here but I just had to get all my backup plans in place before I jump off a cliff.
you can use either the x-backup in the xda itself and making a complete back up to your sd or mmc card or make a backup via active sync on the tools menu
where is the download link??
Anonymous said:
where is the download link??
Click to expand...
Click to collapse
You have to log in to see the download link :wink:
I have an xda II australian model, i want windows media player 10, can i use the chinese rom??
This is gonna be my first time to update the ROM of my device so some questions:
Did you include upgrade instructions on the zip?
How do I disable some of the .cab files on the extended rom? I dont like some of them.
Had any probs with this rom on Globe?
~ishtangli
What's the BT software on the new rom? Widcomm or MS?
Hi Guys,
i downloaded the himalaya update for win mobile 2003. Now I have a problem. The phone which was 1.72.01GER, extROM 1.72.184, radio - 1.17.00 now has become 2.02.t1WWE, radio 1.18 (NO EXTROM version),but the extended ROM is still in german and will not let the new version install. I have to rest the PDA to use it. But most of it seems to work well. I have tried to install the 1.72.181 WWE version, but I get langage id errors (I tried GER, WWE).
There was a note with the installation that said do not let TDxxxx.exe run, in config.txt. I have no idea were to find the file.
please help.
Could it possible to erase all of the rom and install a new version altogether? or erase the ext rom alone? If yes then HOW????
I am not using O2's services in India.
Thanks a million.
Hope what i have written makes some sense.
tykumar said:
Hi Guys,
i downloaded the himalaya update for win mobile 2003. Now I have a problem. The phone which was 1.72.01GER, extROM 1.72.184, radio - 1.17.00 now has become 2.02.t1WWE, radio 1.18 (NO EXTROM version),but the extended ROM is still in german and will not let the new version install. I have to rest the PDA to use it. But most of it seems to work well. I have tried to install the 1.72.181 WWE version, but I get langage id errors (I tried GER, WWE).
There was a note with the installation that said do not let TDxxxx.exe run, in config.txt. I have no idea were to find the file.
please help.
Could it possible to erase all of the rom and install a new version altogether? or erase the ext rom alone? If yes then HOW????
I am not using O2's services in India.
Thanks a million.
Hope what i have written makes some sense.
Click to expand...
Click to collapse
Search around for ExtROM posted by ZeroExtreme, DCS or SIN. It's probably zipped up or in .EXE file. But the final file you are looking for is ms_.nbf.
Put it together with your ROM nk.nbf file and re-run the upgrade again.
You can skip the RADIO .nbf file to save some time.
thanks Henry. Will try your solution and let you know.