yashsingh1/xdaforums huggingface dataset:
[MDA II, XDA II, 2060 ROM Development] gerald8297:
A new hope is born

Impressive discoery by dcs.

Anyway, can anyone confirm that this method is usable or workable for downgrading imate ver1.72WWE to Asia Rom 1.60 WWE.

One major doubt that, if the xda2 is in 1.72 and presumably it was wrong operator coded CDL, so the changes (suggestion by dcs) should take place on the 1.72 imate rom again or the 1.60 Asia Rom.

I once tried to change the 1.60 Rom using er2000edit to set the operator name to CDL instead of O2. The first upgrade screen was passed successfully but i was blocked in the 2nd screen which left me cold dead xda2 with 1.06 serial.

I guess much research shall be done before pursing this method. Anyhow it was a good finding. :lol:
[MDA II, XDA II, 2060 ROM Development] merlin_uk:
This method does work…

I too was in a position were I could not upgrade or downgrade my O2 XDAII ROM because the operator code on the device had been changed to CDL…

Following dcs’s method sorts this nasty problem out once and for all – I can now downgrade, upgrade to any version of ROM I want!!!

Nice one dcs!!
[MDA II, XDA II, 2060 ROM Development] little_frog:
I have exactly the same problem like yours. Thanks to dcs for your hard work.
[MDA II, XDA II, 2060 ROM Development] dcs:
I have updated the post slightly to (hopefully) lessen confusion about operator and language values used.
[MDA II, XDA II, 2060 ROM Development] M4io:
maybe incorporate this post in wiki.xda-developers.com ?
[MDA II, XDA II, 2060 ROM Development] dcs:
Answer to gerald8297 post - A new hope is born

Theoretically it shouldn't matter which version of the upgrade you run first.

The first upgrade is done purely to set your device operator and language values back to the values they should be (or the values you want them to be), and the nbf headers will have to match the values currently defined in your device.

The second upgrade is done to actually install the version of software you want onto your device. The nbf headers should be configured to match the (now correct) operator and language values defined in the device. Also the ms_.nbf file should be checked to ensure the extra block of data isn't going to set your device back to an unwanted value.

You say that your previous attempt at a downgrade failed at the second screen. Do you mean that the OS was installed, but it failed at the extended ROM part? If so, did you edit all 3 nbf file with ER2003Edit to set the operator before running the upgrade? If you only edited the NK.nbf file it would explain what happened. If this is the case, and you are stuck on the bootloader screen, you should be able to reset your device and rerun the upgrade.

It looks like you used the same i-mate 1.172.00WWE upgrade as I did in which case your device has been set to operator CDL and language WWE.

Good luck!
[MDA II, XDA II, 2060 ROM Development] dcs:
I have updated the post by adding some summary points at the end. These, hopefully will provide a better overall understanding.
[MDA II, XDA II, 2060 ROM Development] malkekoen:
FINALLY!!!!! IT WORKED!!! Thanks 102035492304923049 million times, dcs. This is the manual to use!
[MDA II, XDA II, 2060 ROM Development] dcs:
Excellent! I am very pleased. :D
[MDA II, XDA II, 2060 ROM Development] dcs:
Updates Made

I have made a few changes to the post to try and make things a little clearer :)
[MDA II, XDA II, 2060 ROM Development] dcs:
IMPORTANT

Updated with information about downgrading restriction.
[MDA II, XDA II, 2060 ROM Development] i3oyi3astos:
dcs,

I am now at step 13 :)

I edited ms_.nba ONLY using the hex editor. The 74th block is set the CDL so i changed it to O2 and put a null value on the 76th block where L of CDL used to be.

WWE remains as WWE. I am about to proceed but just a few questions.

(1)since this is my first upgrade, i need only run this once right?

(2) is ms_.nba the only file i need to edit or i also need to edit the Radio_.nba and NK.nba files?

So after upgrading... my xda2 should be 1.72 WWE and 1.17 radio right?

Thanks for all the updates on your post. Things are getting a bit clearer.
[MDA II, XDA II, 2060 ROM Development] dcs:
(1) As it is your first upgrade, you should only need to run it once, as long as the your device information (retrieved in DeviceData.txt) is already set to the values you want (in your case, O2 and WWE). Two upgrades are required only if the device information is incorrect to start with.

(2) Only the ms_.nba file requires editing with the hex editor.

You can see what versions of OS, Extended ROM, and Radio you are upgrading to in step 14, before you click the Upgrade button.

Hopefully, all should progress OK now :)
[MDA II, XDA II, 2060 ROM Development] edsub:
@dcs: This topic is getting better and better.

I would vote to have your info instead on the wiki pages instead of the info that is there now on upgrading.

Because there is a risk of others still wanting to stick to the old info, for starters you may want to setup a new wiki page that is linked to from the old 'upgrade' wiki page.

Its quite simple to create a wiki page, as I have just experienced for a subject on IIWPO.
[MDA II, XDA II, 2060 ROM Development] Z-man:
I have stumbled upon sumthing last night.....

1. Waxx's Rom would make my XDA2 a CDL Device right? (I upgraded without modification of Waxx's ROM)

2. Waxx's ROM uses O2 headers (verified through ER2003edit) and the extra code on MS_.nbf says its CDL

3. If I loaded Waxx's ROM (which I did) it would turn my unit from an O2 to CDL.... correct? I could not verify since my GETDEVICE Data does not work... I dunno why.

4. Here comes the weird part..... I followed your instructions to modify my operator to become O2 again..... (change headers and offset 74).... If I understand it correctly, I should change Waxx's ROM headers from O2 to CDL ( to pass the operator test..am I correct?) and I should change OFFSET 74 to O2... correct?

5. When I tried upgrading.... (all headers = CDL, Offset = O2).... the upgrade failed.... error 120 (country code error...me thinks)....

6. I tried changing all headers to O2 and offset was still set to O2..... tried a second time..... and it worked.... get device data works now.... and it says I have an O2 machine

7. IMO Radio rom 1.17 is better than 1.14..... thanks for your help mr DCS, Mr Waxx, Mr. Gollum
[MDA II, XDA II, 2060 ROM Development] dcs:
I think the error must have been related to the problem with HimaGetDeviceData, because everything you did was correct and your assumptions were also correct. Perhaps the first attempt failed, but at the same time it sorted out the HimaGetDeviceData, and also got as far as setting your device to O2?

Difficult to say what happened exactly, but main thing is you are up and running :) - Well Done!
[MDA II, XDA II, 2060 ROM Development] i3oyi3astos:
hi again DCS,

I was just about to continue with the upgrade, when the program was initiated, it told me that i am upgrading to a 1.14 radio version.

(1) Where can i get a 1.17 Radio version to work with my device. Do i update this separately or I should just replace the radio ROM 1.14 with the 1.17, WITHOUT going back to step 1 of your instructions.

e.g. xda2nbftool (changing to .nba, then reinitiating the hexeditor and re-encrypt the files.)

(2) I forgot to clarify if a hard reset is necessary prior to upgrading?

Please advise :)

Thanks
[MDA II, XDA II, 2060 ROM Development] Z-man:
hey i3oyi3astos, check out one of GOLLUM's post.... he uploaded a 1.17 RADIO ROM..... modify the header so that it would be the same as the others that you are gonna use.... use er2003edit to do that.... its easier...... the password is in one of DCS's posts....

YOu do not have to do a hard re-set prior to upgrade.... just dump the XDA2 in the cradle and run the upgrade..... make sure you have a fully charged battery..... also, i keep my power adaptor connected to the cradle during upgrade.

and one more thing... if you have an SD or MMC card with atleast 64Mb, try to back-up your 1.66 incase sumthing goes wrong..... that way you could still dump the contents back to your unit :)

goodluck matey!
[MDA II, XDA II, 2060 ROM Development] i3oyi3astos:
Just finished my upgrade. It took about 1 hour for the thing to complete :)

Few points:

(1) I did notice that my bootscreen is now Imate instead of O2, how can i change this.

(2) Programs does not include an Auto Configure

(3) There is no Running Programs icon in the programs list.

(4) Where can i see if the operator ID was set to O2 instead of CDL?

Nevertheless, thanks for all the tips guys, especially DCS, maybe a little help again for these things enumerated? Thanks :)
[MDA II, XDA II, 2060 ROM Development] Z-man:
congrats dude!!! :)

1. if you would look carefully in waxx's upgrade files, there is the o2.cab.... put it in your xda then tap on the file.... it will change the splash screen to o2 :)

2. about the auto configure... yes there isnt any.... but you can do a work around by copying some files form your previous extended ROM... the files are: 6inone.cab, globe.cab and O2ASIAGlobe_AP_20040211.sa.CAB after copying the files to your device, tap on in in the follwing order: 6inone, globe, o2asia.... ( you can skip step one if you intend to use step 2)

if your operator is smart, copy 6inone, smart, and o2 O2ASIASmart_AP_20040211.sa.CAB :)

3. if you wanna check if you are using o2 or CDL, do the step that DCL indicated with the GetDeviceData.exe

Enjoy!
[MDA II, XDA II, 2060 ROM Development] i3oyi3astos:
z-man,

I dont think i backed up the extended ROM. But i made an xbackup :)

Will that help?

Anyway can you send me the config files or upload them here? Im using Globe Telecom but just the same, please send me all the files.

How about the "RUNNING PROGRAMS"? i dont seem to have it

BTW, splash screen is now O2, thanks for the heads up.

Thanks a lot
[MDA II, XDA II, 2060 ROM Development] Z-man:
here ya go dude:.... I dont use "running programs" but you can remedy that by going to memory then running programs tab.

or use task switch i'll post all here
[MDA II, XDA II, 2060 ROM Development] i3oyi3astos:
thanks man.

There are 4 files, one is switch.cab, what is this for?

what is TASK SWITCH, is this the switch.cab? what does it do?
[MDA II, XDA II, 2060 ROM Development] Z-man:
task switch is a task manager... I use it to move around multiple applications and to close some applications :)

I would like to acknowledge mr Harald-Rene Flasch for his work on Switch.

Many thanks to you sir!
[MDA II, XDA II, 2060 ROM Development] i3oyi3astos:
yahooo !!!!!! :D

Everything is back to normal now. Z-man, thanks for the add-ons, i did install the switch program, its quite useful.

A work around I did for the "absent" Running Programs lnk is in the SPB pocket plus today screen plug-in, i just put an icon for the Main Memory Indicator, tap on the memory icon and it opens the shortcut to Main, storage memory and the Running Programs TAB.

Still havent noticed the increase in signal strength, but i will test it later. My signal is usually low when im in the can, so ill keep you guys posted.

Incidentally, does someone here know how to add the running programs link to the extrom? Or how to make one?

Thanks again to Wax, DCS and Z-Man. :D
[MDA II, XDA II, 2060 ROM Development] :
how 2

DCS ROTE:Start a command prompt session and set your current directory to the folder used in step 2.

Hi DCS once again i´m whith some problems i´m now at step 6 and i dont understand what do you mean by :(Start a command prompt session) wear and how do i do this? Once more thanks 4 help Best regards: Bruno Alves
[MDA II, XDA II, 2060 ROM Development] dcs:
Re: how 2

On your PC, either use start/programs/accessories/command prompt or you can use start/run and then type cmd.exe and click OK. Both of these will open up a command prompt window.
[MDA II, XDA II, 2060 ROM Development] :
Error 101: Connection error

My Xda dead again. And I can't do anything coz when I try to upgrade again there Error msg 101: Connection error. The screen display is i-mate :cry:
[MDA II, XDA II, 2060 ROM Development] davewoodman:
Recovery from bootloader

Further to Edsub's comments earler, I was faced with a 'stuck at bootloader' problem when attempting to upgrade to O2's latest ROMS, I could not get the upgrade to restart at all - no matter what was done the installer bombed-out with the infamous "ERROR 101."

This amused me not at all, until I tried the one thing that enabled the upgrade to take - with the device disconnected, I started the process, then connected the device and reset to bootloader. Off went the installer, and all was well.

This may just be a problem with the v1.01 bootloader, but I give this information in case it is of use to others.

Dave.
[MDA II, XDA II, 2060 ROM Development] dcs:
Re: Recovery from bootloader

Thanks for the info Dave. I am not quite sure why it didn't restart at first and why it should then decide to - The 1.01 version of bootloader is the least problematic.
[MDA II, XDA II, 2060 ROM Development] ACATTAN:
Thank you dcs!

Hi,

I just wanted to say thank you, dcs, for the wonderful step-by-step explanation. I just followed your explanation and upgraded my QTEK 2020 to the latest O2 version. I changed the provider ID to remain 'Qtek', and it just went perfect! :D

Thank's again

Ariel
[MDA II, XDA II, 2060 ROM Development] dcs:
Re: Thank you dcs!

That's great news :D And thank you too :)
[MDA II, XDA II, 2060 ROM Development] vlassi:
rom upgrade

i still get the country code error, anyone have a complete file, just to download and install? my brain hurts
[MDA II, XDA II, 2060 ROM Development] ducga:
Hi, after i finished editing ms_.nba and saved it, I returned to Command Prompt and typed

xda2nbftool ....

xda2nbftool -x ms_.nba ms_.nbf 0x20040305

Then the screen apeared :

WARNING: buffer not multiple of 4

How to fix this prob?

Thx a million.
[MDA II, XDA II, 2060 ROM Development] buzz_lightyear:
Hi,

try it this way:

1. Get this or any other ROM: http://www.t-mobile.nl/global/media/zip/HI_TMNL_17200_190_11700_Ship.exe

2. Get this modified upgrade utility: http://xdaforums.com/download.php?id=685

3. Unpack ROM and modified utility into same directory on your PC

4. Delete "HimaGetDeviceData.exe" and "HimaClearJumpCode.exe"

5. Put your XDA II into bootloader mode by pressing power, joystik and reset at the same time.

5. Connect XDA II's craddle directly to your PC. Not through any USB hub.

6. Put XDA II into craddle

7. Run HimaUpgradeUt.exe

8. Wait... till it finish it's job
[MDA II, XDA II, 2060 ROM Development] :
I need help with part 6, As you can see not that good with dos.
[MDA II, XDA II, 2060 ROM Development] dcs:
On your PC, either use start/programs/accessories/command prompt or you can use start/run and then type cmd.exe and click OK. Both of these will open up a command prompt window.

As an example of changing directory, assuming that your files are in a folder called ROMUpdate on the C: drive, then to change to the folder containing all the files type in cd \ROMUpdate.

Once you think you are in the correct directory, type dir to list all the files to confirm your are in the correct place.
[MDA II, XDA II, 2060 ROM Development] ajb_111:
dcs your efforts are very appreciated

I am computer literate but no means a comuter expert. I was very nervous about upgrading but was not happy with Qtek version 1.66 and in truth wanted blackberry capability. I took the plunge and followed exactly the 17 steps in dcs post. I upgraded without any country code problems and so far the unit looks to be working fine.

DCS - your instructions were clear and with some computer skills relatively easy to follow. The process took me about 5 hours with reading and just being carefull. I do caution people that if any stage is unclear clarify first exactly what to do before continueing - the consequences can be grave.

My device data text file after upgrade is

U S B 3 2 1 . 7 2 . 0 0 W W E

P H 1 0

Q t e k

W W E

1 . 7 2 . 1 8 1

1 . 1 7 . 0 0

I am amazed that it worked - again great job to all that allow us "users" the ability to get a little more involved that just regular computer use.

I thank you

AJB
[MDA II, XDA II, 2060 ROM Development] dcs:
Re: dcs your efforts are very appreciated

Thank you very much for your constructive comments and advice :).

And well done! :)
[MDA II, XDA II, 2060 ROM Development] :
Hi,

I found that you don't have to change the country ID.

When update fails you can still upgrade.

Just use the upgrade utility when device is in bootloader.

Make sure you hard resetted the device by removing the battery for 10 minutes.

Then plug battery in

Run the Upgrade Utility, and wait till it's getting the device info, this should take about a minute (or two).

No error's anymore :D
[MDA II, XDA II, 2060 ROM Development] Slapper Boy:
I concur. Same thing happened to me. I did just as above and things continued without problem.
[MDA II, XDA II, 2060 ROM Development] sprint:
Thanks alot

THANKS ALOT !!! THE REST IS THE FLAME .
[MDA II, XDA II, 2060 ROM Development] buzz_lightyear:
:o)

...and have a nice day...

buzz
[MDA II, XDA II, 2060 ROM Development] sprint:
Hello

:lol: I spend a couple hours on that forum for the info about

"country error" . And only with your posting I realise how to fix that .

Thanks
[MDA II, XDA II, 2060 ROM Development] socheat:
Upgrade ROM to thelatest

Too complecated, is there any way easier that?

Thanks
[MDA II, XDA II, 2060 ROM Development] buzz_lightyear:
If it's too complicated, why don't you let some service center do the job?

It's just few simple steps. If you are too lazy to do it, just don't do it.

Totaly simple solution... :o)

buzz
[MDA II, XDA II, 2060 ROM Development] socheat:
Udate ROM

Thanks your message

I am not lazy but not have experience about that.
[MDA II, XDA II, 2060 ROM Development] :
Where can I download these tools now?

I can't download the tools and source code from this site. Such as this link http://wiki.xda-developers.com/wiki/XDAtools, always get HTTP 404 error.

Can anyone help me? Many thanks!
[MDA II, XDA II, 2060 ROM Development] Gnuig:
Thanks!!!

DCS -> Thanks a billion!!!

I finally managed to figure out how to 'cook' my own ext. rom (in addition to fixing the language warning) with new radio, new NK file (not really sure what it does...and I really didn´t bother to find out) as well as a new ext. rom file (ms_.nbf).

You have really done your research well, and I must commend you!

My new ext. rom now contains a mix of the latest O2 ext. rom stuff (choose the 181 version - didn't keep any of the cool desktop though) since I needed Orange mms settings, because of a non working version from my previous upgrade to 1.72 (I did mess around with it a lot before here... but I never felt mms worked as it should). I think my latest fix has done it.

Anyway, to make a long story short... You are the man :wink:

Sincerely,

Gnuig, Denmark
[MDA II, XDA II, 2060 ROM Development] edsub:
the XDATools ARE available.

1. Search the forum

2. use the Wiki pages (and the forum thread on how to use them as the normal links dont work currently.

BTW dcs's procedure IS the simple & secure way, specially designed for both experienced & novice users

Where has the time gone in which people first search and then ask?
[MDA II, XDA II, 2060 ROM Development] :
During upgrading!!!

My Xda from Imate Rom when up to Xda_II_172187_Final is ok when I did follow your post but yesterday when I backup by Xbackup It became last Rom. I dont know why? Today I try to up to Xda_II_172187_Final and try to repare country ID code but when I executed HimaGetDeviceData.exe on my device and run but DeviceData.txt in my Device only show text "U" after that I try follow old way but nothing happend still country ID code error when I run HimaUpgradeUt.exe.

Tell me when use XVI32 to fix in row 74 and 94 what string I have to type in???

Help me!

Thanks you very much!!!
[MDA II, XDA II, 2060 ROM Development] haveric:
wow thanks goes out to wiki and DCS

I now run 2003se :D
[MDA II, XDA II, 2060 ROM Development] vgiangi:
any one can suggest me the way to exit bootloader without flashing any rom ?

thanks
[MDA II, XDA II, 2060 ROM Development] buzz_lightyear:
reset...

buzz
[MDA II, XDA II, 2060 ROM Development] luna:
help

Hi dsc ,

I tried to install the 1.72 upgrade .

I got the USB/SERIAL screen :(

I tried to reset my device twice and I'm still getting that screen :cry:

What should I do now :?:

Thanks
[MDA II, XDA II, 2060 ROM Development] dcs:
Re: help

Sounds like you are in bootloader mode. Put your device back in the cradle. Make sure the cradle is connected directly to a USB port on your PC and not to a hub. Make sure the power supply is connected to the cradle. Re-start the upgrade. It should work OK.
[MDA II, XDA II, 2060 ROM Development] luna:
Re: help

Hi dsc ,

Hey I finally manage to upgrade successfully .

Thanks for your help .

After upgrading I got another small problem .

I tried to install some software/programs into my ppc , it states that my active sync is not found on the computer , but I can see it . And it'll also state that 'cannot find the CEAppMgr Installer Programme on this PC' .

Hope you can help me with this .

Thanks alot
[MDA II, XDA II, 2060 ROM Development] dcs:
If you haven't done so, try re-booting your pc.
[MDA II, XDA II, 2060 ROM Development] Looking Glass:
Upgrade Paths

Hi everibody!

In the way to upgrading to SE (whatever the manufacturer) I've been trying to apply dcs procedure, but failed to obtain a valid "DeviceData.txt" file. All I got in the file is a single "U", no WWE, no carrier, etc.

Any idea about what is going on?

HimaGetDeviceData.exe failure?

:?:
[MDA II, XDA II, 2060 ROM Development] @ngel:
Re: Upgrade Paths

Hi Glass, you must open DeviceData.txt on your PC (notepad). :wink:
[MDA II, XDA II, 2060 ROM Development] Software Guru:
Error 120 Country ID Error - N-8-1-N-1 / N-8-1-1-1

:(

I apologise if this has ben answered before but I am trying to amend the country code from CDL to O2 and keep getting the error above.

I have followed the tutorial below by dcs to the letter

http://xdaforums.com/viewtopic.php?t=12101

but I still get the same error, I have checked the ms_nba file and the values show as O2 and WWE

What am I doing wrong, I want to upgrade my ROM to WM2003 SE but this error is holding me back

My PDA specs are as follows

O2 XDA2

ROM Version - 1.72.00 WWE

ROM Date - 03/15/04

Radio Version - 1.14.00

Protocol Version - 1337.24

ExtRom Version - 1.72.126

If someone has successfully amended to O2 can they send me the files zipped up and I will see if they work for me

Thanks
[MDA II, XDA II, 2060 ROM Development] [Krueger]Dr.Stein:
Errors

Okay here's the skinny. I believe there are two parts to this problem.

One the user is not complying to the procedure in changing the codes.

Two the user has previously upgraded using a foreign HimaUpgradeUT along with a foreign Extended ROM ms.nbf file (filled with own modified CABs).

I have included the ms_.nbf file without an operator ID to be entered accordingly. It also does not have any modified Extended ROM CABs to be inserted to your heart's content (you can do this later together with the WM2003SE upgrade). However I have included the splash screens for O2 but changeable to your whim and fancy. Save your ms_.nbf ROM file.

After all that is done run the HimaUpgradeUT.exe that came with the zipped file. Do not add the nk and radio nbfs. Warning data loss.

Now run your own cooked WM2003SE ROMs.
[MDA II, XDA II, 2060 ROM Development] [Krueger]Dr.Stein:
Errors

Or you can simply remove HimaGetDeviceData.exe and upgrade if you can live with the foreign ID in your Himalaya.

U S B 3 2 2 . 0 6 . 0 0 W W E P H 1 0 O 2 W W E 1 . 1 2 . 9 2 4 W W E 1 . 1 8 . 0 0

Mine was previously changed to Qtek but I changed it back to O2.
[MDA II, XDA II, 2060 ROM Development] Software Guru:
Thanks for the file Dr Stein, however I am still getting the same error

I must be stupid or something

I will take yur suggestion and remove the HimaGetDeviceData.exe, I tried

this and I was able to proceed without any country code error

Thanks for your help in this matter