O2 UK Operator ID needed for messed up XDA IIs..

---

I downloaded the so-called "Launch ROM" for the XDA IIs from the SourceO2 web site, this has now stuck my XDA IIs in boot loader, I suspect because it copied over HimaClearJumpCode.exe. So right now I'm a bit stuffed..and yes I know I should have done a backup ops:

so does anyone have the O2 UK operator name/ID so I can try and get the iMate PDA2K ROM on there OR does anyone have he XDA IIs ROM backed up, that they can let me have??

Any help appreciated, as I am potentially the owner of a very expensive door stop...

hi i am in exactly the same position please help ....

---

ops:

Found the O2 UK Operator ID

---

Well, whilst fiddling around with the batch file, I got onto trying different operator IDs, and I found one that worked:

O2___001

I now have the iMate ROM on my XDAIIs, just hope I haven't broken too much :wink:

excellent !!! xda2s is also now up and running more info 4u

---

it is fair to say 2 years on i am still a novice

first impressions of imate rom = a stable quick o/s. vast improvment on the O2 effort. ( what r o2 playing at it seems they are continually wounding these great little devices with crippling software)

to resovle issues as above you will need -

xda3nbftool.exe ( found here as an attachment)

a rom of your choice i am running this one -

pda2k_wwe_12200_162_10600_SHIP.exe ( found here-http://forum.xda-developers.com/viewtopic.php?t=14854&postdays=0&postorder=asc&sta rt=25#77518 )

you will need this text to create a batch file to modify the extracted rom files on your pc before runing the upgrade ( simply run the upgrade package it will open itself and will then promt you to selcet next, at this point you navigate to the temp directory somthing like this-C:\Documents and Settings\yourname\Local Settings\Temp\pft34.tmp once you have found the folder which contains among others these files - radio_.nbf nk.nbf ms_.nbf you need to copy and past "xda3nbftool.exe" into this folder along with the text file created from the strings below. ( your almost there) when you get to this position you need to copy the "HimaGetDeviceData.exe" via activsync onto your device then using file explorer on your device navigate to the windows folder here you will see a new file called "device data" copy this and then paste it to your desktop and then print it out ! - on here you will see your device data and on some occasions the operators code. the operators code is important because you need to remove all instances of "O2ASI001" in the strings below and insert in their place your actual operators name. once you have inserted the correct name that applies to your device save the text file and then change its extension from ".txt" to ".bat" you will get a message mentioning stability just continue. one you have accomplished this simply double cllck your " .bat " file . after a little number crunching the whole thing stops thats it your now ready to resume with the upgrade that you extracted earlier..... ( as was pointed out to me above some o2 supplied xda2s dont show operator code using described method as for us two the following did work fine ( O2___001 )

good luck and please realise that what i have presented above is not my work it is a presentation of the facts i have harvested at length from this forum and it is with thanks to you all that my own xda2s is now a worthy companion.::

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

ROMs supply!

---

I have an mDA 3 (TMOBILE Germany), and I messed up things. Can anyone send me nbf files with their passwords (Extended ROM, OS and RADIO). I don't know if it'll help. I'm trying to write them to the PDA using er2003edit provided my softworkz.
Cheers

Re: excellent !!! xda2s is also now up and running more info

---

Hello,

I am running my O2 XDAIIs with the original O2 ROM on it. Is this NEW iMATE ROM any better? What advantages are there?

Cheers,

Dom

is the rom any better ?

---

hi - if you are happy with the usability of your individual device then i would suggest you stay with it. some of the reasons i was not happy with my original o2 rom are as follows,
1) - very slow to populate screens
2) - having loaded my software device became unstable and kept freezing. ( tomtom3 and other main stream renown applications)
3) - unable to answer the phone. ( would ring but couldnt be connected either by accepting via screen or buttons)

4) - system continually needed soft reset etc etc etc........

the list goes on and on if the only rom available to me was the o2 rom i simply would have had to return the device to my supplier as not fit for the purpose intended..... and failing a full refund sadly my xda 2s would have gone in the bin .

if yours works for you dont alter it as complications can be encountered if you not familier with the process of upgrade as i found to my horror - and subsequently had to read pages and pages of info from this site in order that i could repair my device a concise method of which is outlined above... i would appreciate anyone using the above method to leave feed back on the methods clarity and suggest any improvment they think would help others.

to everyone HAPPY 2005 !

Ok, thanks for the info.

I am experiencing many of the same problems you had so I will try the upgrade as experienced above and see if it makes a difference.

I will let you know how I get on.

Regards,

Dom

Ok, good news and bad news...

Good news:
Upgraded to the new i-mate ROM, looks quite nice. With any luck it will be better than that pile of rubbish that O2 are pumping out on these devices.

Bad news:
I tried to restore the O2 ROM (launch ROM from the SOURCEO2 website). I ran the HimaGetDeviceData.exe and there was no operator name/ID in the DeviceData.txt file. I ran the batch file as before (using the old data :S) but it seemed to corrupt the installation files. Dare-Devil as I am I ran the O2 install and it failed due to corrupt files so I then had to re-run the i-mate install to get the device working. (20 mins of my life I'll never get back)

This isn't a tragic scenario as the i-mate ROM is nice but it would be great to have the option of going back to the old O2 ROM incase they bring out a better version. Can anyone shed any light on this? Where am I going wrong?

Cheers,

Dom

SourceO2 ROM comes with the wrong tools

---

I think the ROM from the SourceO2 site comes with the wrong tools, I believe they are for the Himalaya not the Blue Angel. The iMate ROM comes with tools starting "BA" whereas the O2 ones start "Hima".

To be honest, I am not even sure the ROM file is correct. I am in exactly the same position as you : tried the SourceO2 ROM, got the stuck in the bootloader, and then had to use the iMate ROM, which is good, but again like you I would like to be able to go back to the O2 ROM if I wanted.