Related
Upgrading Extended ROM from Imate to TMobile Extended ROM, Easy As 123 Please follow the Steps
1. Get hexeditor
2. Download TMobile 1.60 and extract it to get ms_.nbf
3. Download I-Mate Ruu15283WWE and extract to get ms_.nbf
4. Open Both Files in hexeditor, please remember both files so you will get confused.
5. if you are having T-mobile and want to upgrade to I-mate Extended ROM you have to do the following in reverse.
6. Copy "2d 43 44 4c 00 00 00 00 " (-CDL....) and paste it to T-Mobile ms_.nbf, location "2d 54 4d 4f 42 49 4c 45" (-TMOBILE) , This is the Version.
7. Copy "62 34 34 39 38 64 31 34" (b4498d14) and paste it to T-Mobile ms_.nbf, location "65 38 34 31 37 61 63" (e8417acd), this is the CountryID
8. Save the T-mobile File to c:\New folder\ms_.nbf
9. Include in the New Folder "HimaClearJumpCode.exe","HimaGetDeviceData.exe", and "HimaUpgradeUt.exe".
10. Start to run the "HimaUpgradeUt.exe" and it will start updating your mobile.
Have fun and enjoy your new extended rom.
8)
ROM Version : 1.52.00WWE
ROM Date: 10/23/03
Radio version: 1.06.01
Protocol version : 1337.16
ExtROM version : 1.60.06
Next i will try to update my I-mate 1.52 nk.nbf to T-mobile nk.nbf but not the radio because radio will not work with my area.
Thanks!!!!
Let me try it!
the 8 hex digit number is not the country code, it is the sum of crc's of 256k blocks of data of the file.
see http://www.xs4all.nl/~itsme/projects/xda/xdaii-update-format.html
for a tool to calculate it.
soon an adaptrom version will follow.
a warning though: if an upgrade fails, you may be left with an unbootable device. you can use xda2dmp to fix this in most cases. ( I hope )
also DO NOT consider trying out 'HimaClearJumpCode.exe', it will make your device unbootable. and you will have to figure out how to use xda2dmp to fix it.
Update I-MATE ROM to T-MOBILE or backward ?
Hello,
I have an I-MATE and sometime ago updated to T-MOBILE ROM 1.6
Later on I-MATE released their own ROM update and when I tried to install it, even knowing that it is "lower" version - I got message that "Country Code ID is incorrect" (I am sure it is already known issue for XDA II community )
1. Is it make since to go waist a time and try go back in lower I-MATE ROM?
2. and if 1 is YES, how to change Country Code ID so installation of I-MATE will proceed further?
I would really appreciate reply from XDS developers.
Thank you
Paul
I did test it.
This method not only allow to install the extended rom it self , but allow the machine to flash the full set of rom!
Moreover, after flash the new rom, it will keep the country id of the new rom, not the old rom.
I found the bug, the problem is that the language of the device is reported as 'WWE'
maybe you can change one of the language identifiers in the binary of HimeUpgradeUt.exe.
or as I just noticed. the update tool in the Update.rar attachement in this thread http://forum.xda-developers.com/viewtopic.php?t=4785 has a updated version of the upgrade tool, which does know 'WWE'.
More interesting things :
1.All rom files (extended / radio / ce rom) has countryid inside the files. However if the ms_.nbf passed the countryid check, the rest of the rom will be allowed to flash, even the country id is wrong.
2.If you just want to upgrade a radio that not belongs to that countryid, just rename the company name of the radio rom by hexeditor to the machine's countryid (it is in the first few lines of the radio.nbf),
3. I can't find the country id inside the nk.nbf but it seems himaupgradeut.exe may not regonize a nb.nbf from different upgrade set.
For safe , use the himaupgradeut.exe comes with nk.nbf to upgrade the cerom
4. If you want to upgrade the CE ROM will different countryid, you must upgrade the extended with modified countryid too.
For example, I want to upgrade the CEROM to T-Mobile 1.60 CE ROM, but I want to keep the O2 1.52 extended rom, I have to
a. mod the T-Mobile extended rom's country ID / CRC to O2 countryid /CRC
b. upgrade the moded t-mobile extended rom with himaupgradeut.exe
c. Your device is now recognized a a t-mobile device. Use T-Mobile's himaupgradeut.exe to upgrade the CE rom to T-Mobile 1.60.
d. mode the o2 extneded rom's country ID / CRC to T-Mobile's countryid /CRC
e. upgrade the moded o2 extended rom with himaupgradeut.exe
It looks like very stupid, so we need want a new adapt rom and we love XDA-developers 8) .
1: also the checksums is only verified for the nk.nbf
3: nk.nbf is encrypted, decrypt it with xda2nbftool. then you can see the countryid.
4: I saw that the extended rom, is where HimaGetDeviceData gets the language/country id from.
"XDA developer Itsme" the 8 hex digit number is not the country code, it is the sum of crc's of 256k blocks of data of the file.
Click to expand...
Click to collapse
ahhh ic.. :?
killercheung said:
It looks like very stupid, so we need want a new adapt rom and we love XDA-developers 8) .
Click to expand...
Click to collapse
I agree with this :wink:
I try to search difference between nk.nbf and the other version nk.nbf, the Qtek2020 ver 1.60 nk.nbf is almost the same as I-Mate 1.52 nk.nbf, but with T-Mobile, it is totally different.
I will still try untill my unit becomes a paper weight, just to get that countryID error. it should be flexible like the old one.
XDA developer Itsme said:
I found the bug, the problem is that the language of the device is reported as 'WWE'
maybe you can change one of the language identifiers in the binary of HimeUpgradeUt.exe.
or as I just noticed. the update tool in the Update.rar attachement in this thread http://forum.xda-developers.com/viewtopic.php?t=4785 has a updated version of the upgrade tool, which does know 'WWE'.
Click to expand...
Click to collapse
i get the update.rar from the files of I-mate 1.52.. I think the version is WWE. :roll:
XDA developer Itsme said:
1: also the checksums is only verified for the nk.nbf
3: nk.nbf is encrypted, decrypt it with xda2nbftool. then you can see the countryid.
4: I saw that the extended rom, is where HimaGetDeviceData gets the language/country id from.
Click to expand...
Click to collapse
Where can I possibly get this file "xda2nbftool"
Suceed!!!!!.. because I update Already my I-mate 1.52WWE Extended ROM to T-mobile 1.60 Extended ROM, I successfully update all the upgrade within T-mobile 1.60 (nk.nbf, ms_.nbf, radio_.nbf), The CountryID error didn't appear anymore, the upgrade that I done with Extended ROM change my Country ID to what ever Extended ROM I update my device, the countryID is in extended rom(ms_.nbf) , now everybody can change thier unit to whatever update they want.
Thanks for the Help of XDA-Developer Team. More power 8)
another thing I noticed is that the password used for the nk.nbf encryption is different for each upgrade tool version:
v0500 uses password 'HTC'
v0600 uses password '921211'
so, yet another update to my xda2nbftool
now also has an option to change the crcsum in the file.
Thanks for XDA developer Itsme again
Finally I can change countryid of a TMOBILE rom to flash on an O2 Device.
However I found that himaupgradeut.exe v0500 come with the TMOBILE can't flash the rom (It reported MODEL ID error), but v0600 is OK.
I got an XDA2 , it will report country ID error when use TMobile's upgrade utility, but I want to upgrade the CE ROM to TMOBILE 1.60 WWE version.
Here is what I did :
1. decrypt the T-Mobile 1.60 CE image
run "xda2nbftool -d nk.nbf nk.nba HTC"
Because T-Mobile 160 upgrade rom is come with himaupgradeut v0500, therefore the decrypt code is "HTC"
2. Use HEX Editor change the nk.nba countryid from T-MOBILE to O2 (It is in the first line of the rom)
3. update the crc checksum of the nk.nba
run "xda2nbftool -c nk.nba -u"
4. encrypt the T-Mobile 1.60 CE image. Because I cannot use himaupgradeut v0500 to update, I have to use v0600 and the encrypt code is 921211
run "xda2nbftool -e nk.nba nk.nbf 921211"
5. Run the himaugradeut.exe v0600 to upgrade your rom!
I got one more question.
Is that the rom content inside the decrypted nk.nba identical to the rom dump by xda2dump ?
Because I tried to copy a xda2dump version of XDA2 Chinese 1.52 rom and copy the content from address 0x1000h ( Something like D300A0E300F0 in HEX code) to the end, and overwrite the 0x411150h - the end of a TMOBILE 1.60 nk.nba with the chinese rom content , and fill the end of the file to 0x1f80030h with 00 . I can flash the rom to the device without any problem, but it stop in the 1st boot screen.
The chinese is working with the bootloader SD card upgrade method.
What's wrong with me?
Thanks.
XDA developer Itsme said:
another thing I noticed is that the password used for the nk.nbf encryption is different for each upgrade tool version:
v0500 uses password 'HTC'
v0600 uses password '921211'
so, yet another update to my xda2nbftool
now also has an option to change the crcsum in the file.
Click to expand...
Click to collapse
Hello XDA developer Itsme, can you send me this file/site "xda2nbftool", because i can not access it here, i think the site is forbiden here, thanks in advance
here are the tools attached
XDA developer Itsme said:
here are the tools attached
Click to expand...
Click to collapse
Thanks... :lol:
killercheung: it is almost the same. the decypted file has a 64 byte header, followed by the rom found with xda2dump at offset 0x80040000.
I don't think you can mix roms like you describe.
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
Can you use the ROM upgrade from the orange website to upgrade an unlocked O2 XDA2?? I hate the O2 stuff but I am concerned that i will trash my XDA if I do this. Any help/advice much appreciated.
Also if I can't do that how do i change the "Desktop" theme on the XDA2?
dcs's post will help you through this process, this post can be found here
My company got a good deal on these without sim cards and a bunch of us bought one.
But they all came setup for O2 and we all use Orange.
I detest O2 with a passion so I wanted to change the XDA to have SPV software.
I tried Flashing my Rom with an Orange one modified to work on O2 and it totally killed my XDAii, so much so that I could'nt even get it to restore with the official O2 upgrade.
Here's how I turned my XDAii into an Orange SPV m1000
Eventually I got it back using a 1.72 I-mate ROM I found on this site, no other setup I tried would work.
After Doing that I re-ran the orange spv setup again and copied the files it unpacked from the temp folder, onto a folder on my desktop(without my XDA in the cradle).
I installed the extended rom tools on my rescued XDA, made the extended ROM visible and unlocked, I then copied everything in there onto an SD card(just incase), I then deleted all of the files in the extended rom.
Next I installed ER2003EDIT on my PC and opened the ms_nbf that I had copied out of the temp folder.
In ER2003EDIT I went to the file tab and extracted all of the files to a directory on another SD card in my PC's Card reader.
I then put the SD card with the Orange files into my XDA and copied all the files into the extended ROM.
Then I hardware reset the device, once it booted back up it ran the new files in the extended ROM.
After it rebooted again all the orange software and settings were correctly set up on my XDA.
After that I just ran the sim lock remover and popped my sim card in.
I've since done this for 3 other people in my office and it's worked fine on each attempt with no hassles.
When I attempt to open the Orange ROM ms_.nbf file using ER2003Edit I get an error because none of the know passwords work.
What password should I be using?
Try 0x20040304 for NK.nbf, 0x20040305 for ms_.nbf and 0x20040306 for Radio_.nbf. Also make sure you use the specific type in the drop down and not the auto-detect option.
No joy with those, I get 'Error accessing image files' ?
Which ROM is it?
This one. All I was after was the extended rom's contents.
Strange ... I just did the following:
Downloaded the file and extracted all files to a folder.
Started ER2003Edit.
Used File/Open ROM Image.
In the Open File Dialogue, I selected WM2003 Extended ROM (ms_.nbf) in the Files of type drop down list.
I selected ms_.nbf and clicked Open.
I was asked for a password and entered 0x20040305 and it opened successfully.
I'll re-download and test, thanks
No probs Perhaps you have an old version of ER2003Edit too?
Just tested and works fine now, thanks
ER2003Edit is v1.2.20, is that the latest?
That's good
Yes, it's the latest.
totaly los
having read your post on how to turn my xda11 from o2 to orange spv would i lose me tom tom navigator as i no longer have the cd ????? if i did a complete back up of my xda 11 first change it to and orange spv could i restore my tom tom navigation softwear ??? helpppppppp
Re: totaly los
trev said:
having read your post on how to turn my xda11 from o2 to orange spv would i lose me tom tom navigator as i no longer have the cd ????? if i did a complete back up of my xda 11 first change it to and orange spv could i restore my tom tom navigation softwear ??? helpppppppp
Click to expand...
Click to collapse
If your tomtom isn't on the rom, you'll lose it as far as I'm aware.
How upto date is your version? you could always download an upto date version, have a search for it on a torrent site like suprnova :wink:
Dear Fellas,
Where can I get a step by step ROM upgrade instruction to upgrade/flash my XDA II into WM2003SE? I have been through the forum, but still can not find a basic guide to do the upgrade.
I have downloaded "Customized_WM2003SE_Asian_Edition_Version2.zip" from ZeroXtreme. What can I do with this file? How can I start it?
Anyone can help me pleaseeee.......Thanks a lot.
Rgds,
Fendie
Ahoy there matey!
this is what you do:
1. decide on what version you want to use.
2. get them roms. (E.g. read through DCS's post on the ORIGINAL WMSE)
currently there are three versions of the WMSE namely 2.02,2.06, and 2.20.
3. check your device data for language and operator:
use getdevicedata.exe from the upgrade files, copy it to your device's windows directory, then tap on it.... it will produce a log file, copy the log file to your desktop pc, then use notepad.exe to view it.
look for the language setting e.g. WWE, CHT... etc.
look for operator settings e.g. O2, Qtek... etc.
now check your downloaded NK.nbf, MS.nbf and radio.nbf to see if they have the same settings as your device..... you can use ER2003edit.exe which can be downloaded from wiki.xda-developers.com.
if the files have the same settings, thats good... if not... change it so that they would be the same as your device.... better yet use DCS's batch file for easier conversion... (note, DCS's 2.02 rom is set to WWE,O2)
now... assuming you had made all the preparations... (language, operator settings, and that you have a complete set of roms e.g. NK.nbf, MS.nbf and radio.nbf)
put them all in one directory along with the other files that came with the upgrade package.
make sure you have a full battery before proceeding with the upgrade.
plug the charger to tha cradle and the cradle to the comnputer.
click on himalaya upgrade program.... then the program will run, put the device in the cradle and watch the screen for further instructions
goodluck...
be sure to read on DCS's post regarding upgrades for a more detailed info.
assuming everything goes well; during the upgrade do NOT take out the unit from the cradle; go watch tv or something...if you receive an error message; don't fret. the forum hosts a lot of topics on how to revive your unit...
and if your xda dies during the upgrade; make sure your tray tables are in their upright position, put your head between your legs and kiss your arse goodbye
what do guys suggest the ROM i use?
which one is the most stable?
mate, i noticed that you're from the philippines. i'm based in thailand i used the rom posted by zeroextreme; it's the wm2003 se asian rom. pretty stable that one; after upgrading my unit's power consumption improved noticeably. although as expected some apps may not display well when using landscape mode (those're the apps not designed for wm2003 use). but overall the rom upgrade was well worth it. stable and no hick ups; been using it for more than 2 weeks now i think.
others may have useful tips on the other roms they used for upgrading; not to mention experiences.
cheers
acid.... try 2.02.t1 they say its more stable than 2.06.
thanks mga kababayan!
Z-man said:
Ahoy there matey!
this is what you do:
1. decide on what version you want to use.
2. get them roms. (E.g. read through DCS's post on the ORIGINAL WMSE)
currently there are three versions of the WMSE namely 2.02,2.06, and 2.20.
3. check your device data for language and operator:
use getdevicedata.exe from the upgrade files, copy it to your device's windows directory, then tap on it.... it will produce a log file, copy the log file to your desktop pc, then use notepad.exe to view it.
look for the language setting e.g. WWE, CHT... etc.
look for operator settings e.g. O2, Qtek... etc.
now check your downloaded NK.nbf, MS.nbf and radio.nbf to see if they have the same settings as your device..... you can use ER2003edit.exe which can be downloaded from wiki.xda-developers.com.
if the files have the same settings, thats good... if not... change it so that they would be the same as your device.... better yet use DCS's batch file for easier conversion... (note, DCS's 2.02 rom is set to WWE,O2)
now... assuming you had made all the preparations... (language, operator settings, and that you have a complete set of roms e.g. NK.nbf, MS.nbf and radio.nbf)
put them all in one directory along with the other files that came with the upgrade package.
make sure you have a full battery before proceeding with the upgrade.
plug the charger to tha cradle and the cradle to the comnputer.
click on himalaya upgrade program.... then the program will run, put the device in the cradle and watch the screen for further instructions
goodluck...
be sure to read on DCS's post regarding upgrades for a more detailed info.
Click to expand...
Click to collapse
Hi Z-Man,
Thanks for your response. But still do not understand in some areas
I just got MS.nbf and some *.CAB files from the extended ROM of ZeroXtreme. There are no NK.nbf and Radio.nbf. Is it because it's an Extended ROM? Where can I get the "non-extended" ROM?
And I don't really understand on DCS's post.
Sorry, I am really really newbie.....
Many thanks.
Rgds,
Fendie
ms.nbf is the extended ROM, you still need to get the radio.nbf and nk.nbf
download the file here:
HIMALAYA_WM2003SE.zip and Operator update.zip:
http://forum.xda-developers.com/viewtopic.php?t=13588
extract all files to one directory... and add the ms.nbf that you have
you didnt mention the operator and languange settings of your device... check your device info....
then use DCS's batch file to convert the settings.... by default, DCS uses WWE and O2.
make sure all the nbf's are set to the same settings...
then begin upgrade
Himalya Romkitchen is still valid for SE
I am upgrading my qtek2020 and changing the operator from VODAFONE to O2. I have downloaded the O2 software from the my-xda.com site for xda2. but when i run the program it gives me the error message (Country ID Error) shown in the attached image, although it is the right software for the device but different operator O2 not VODAFONE (previously installed).
I have opened the nk.nbf file in 'windows mobile 2003 - rom editor' from this website and have tried the different operator providers listed on the rom (QTEK, O2, CDL, TMOBILE). But none of them work.
Does ne one know how to get the o2 rom to install or how to change the rom to show vodafone or does ne one have the vodafone/compatible xda2 rom and can upload it.
ALL HELP MUCH APPRECIATED
Cheers Steve
sticky
http://forum.xda-developers.com/showthread.php?t=228852
HimaUpgradeUt_Noid.exe from the ftp for short
got it sorted
Thanks for your reply, I was able to fix the problem by changing the operator id from o2 to qtek on each of the files nk.nbf, radio_.nbf and ms_.nbf using 2003 rom image editor.