Database Users

WAS UNLOCKED - BUT NOW ITS NOT!!!

I had unlocked my XDA using a method whereby you made a call before the simlock notification came on..... and that seemed to work (I wont go into how you did - I am sure people have already done it)
however - I have now downloaded and upgraded my ROM.......
the the unlock trick doesnt work now - !!!!! it seems as though they have fixed the bug that was there before....
any Ideas about unlocking it again - I have downloaded the manipulator (which I read to be fantastic) - but I dont have the serial cable (bugger), and so wondered if there is anything I can try before buying the cable......
can I give someone my IMEI and they can supply me with the unlock code.... would that work???
ALSO
I had backed up all of my data with activesync before upgrading... all seems to be fine, however - the xda device is naming its own partnerships when synching..... and not the original name (which it needs to be to be able to restore the data)........
make sense?!??!
has anyone got any ideas how to rename the partnership (or delete) which is in the XDA and therefore rename it to the correct name. Im not recieving the dialog box which you get on the pc when you sync a new device - it is simply setting up its own name called POCKET_PC....
ARRRRGG!!!!!!!!
help!!!!

HELP! RSU update crashed! I tried it all: my MDA is dead!

Hello there,
I have a MDA from T-Mobile germany PW10A2 with an RUU version which was probably 3-13-12-GER and a RSU which was probably T360.
I dowloaded 2 update files on the site of T-mobile germany:
http://www.t-mobile.de/shop/handy/1,4855,2963-_50-0-99,00.html
- t_mobile_mda_ppc_update_v3_19_03.exe
- t_mobile_mda_gsm_gprs_update_v3_23.exe
Since I wrotte them an Email, no answer, and the page has been cancelled.
What have I done:
- I installed the PPC 3.19.03 through Activesync: no problem
- I then installed the GSM GPRS update: once it started updating on my MDA at 10% it kept stucked. After 20 mn I decided to interrupt.
Since that day I have the white screen with the litle keyboard down right and that's about it.
My boot loader is V5.15. when it runs it displays "WAIT", and then "GSM ERROR"
As suggested in this Forum, I bought an SD Card, and a card reader writter, I wrote the RUU file NK.nbf contained in the downloaded .exe file from T-mobile. I flashed my room (proposed when I cold reseted the Wallaby) and then : NOTHING HAS CHANGED !!!
I tried again with a cooked Rom flashing a NK.nb1 file and... I got the ROMKitchen splash screen and... nothig else.
The display stays all white, you can read "this ROM was cooked in the ROM Kitchen" all on top af the screen and in the lower right side I still have the keyboard Icon.
Now I'm really worried !
Does any one have a suggestion ?...I believe my problem is realy serious.
Pascal

Hate to tell u that mate, but if your device can't be recognized by ActiveSync, then the only action is to get the device to be repaired by a specialized center or replaced.
However, check this topic carefully .. it might help
http://forum.xda-developers.com/viewtopic.php?t=4123
Good luck

Good news bad news
I have an SX56 with att, I had the same problem. rsupgrade failing at 1%, hard reset, and then the device white screned. First, downgrade the rom. Find the old update program, open it with winzip (or winrar) and you should be able to extract the rom image. get http://wiki.xda-developers.com/wiki/XDAtools place the rom on an sd, softboot while holding down the power button. the device will now offer you the option to load the rom from the sd, do so. once this is done the device should display the old roms ID. If this works, format the SD card, create a directory 2577 copy the program RSUpgrade and associated files, rename it as autoexec insert the card in the phone, and you should be able to reflash the RSU, if this fails.... time to break out the jtag header or be ready to send the unit in

My MDA is dead and buried
Thanks to both of you guys, for your concern.
I had actualy already tried your proposed solutions (I had found in this forum except yours rszasz).
My MDA is less than 2 years old and I took it to a T-mobile shop in germany (during a business trip). They're proposing either to repair it, or to replace it (The guarantee is still runing).
After having flashed a cooked a rom in the kitchen, I still had the same problem, so in the perspective to bring it back to a T-mobile store, I reflashed the faulty file I had downloaded on the T-mobile Web site.
I hoppe they won't find out and make any trouble.
I like this MDA so much, I don't remember how it was without it !
All the best
Pascal

Re: My MDA is dead and buried
Pewinski said:
Thanks to both of you guys, for your concern.
I had actualy already tried your proposed solutions (I had found in this forum except yours rszasz).
My MDA is less than 2 years old and I took it to a T-mobile shop in germany (during a business trip). They're proposing either to repair it, or to replace it (The guarantee is still runing).
Pascal
Click to expand...
Click to collapse
send the phone to me, I could repair for you!

Thank's but it's under guarantee and I get it repaired or a new one for nothing.
Best regards

SIM LOCK

HELP .. HELP .. HELP ..
I know this subject is old but I could not what I need & how can I fix it
I have bought a pocket pc with phone edition from USA, and when I tried to insert my SIM card it asked me to but my PIN code, then ask me to but the unlock code (SIM code).
Now I am in Saudi Arabia.
WM2003
ROM Versino: 4.01.16 ENG
ROM Date: 02/04/04
Radio Version: 6.25.02
Protocol Version: 324e4
NOTE: I do not have a serial cable.
Thanks,
HFN[/b]

Check this: http://wiki.xda-developers.com/wiki/UnlockWiz
Hope it help you
Edit:
You have a WM 2003, this link work only for PPC2002

SIM Lock
DariusVE
Thank you for your help, I have tried this site, but It did not work because my device using WM2003 and also has no Wireless Modem feature.
Thank you.

Unlocking Quest
Here's my quest to unlock my T-Mobile PPCPE. I think some of this information might be useful to anyone confused about getting this
done.
First I called TMobile to request the unlock code. Since my account was up to date I figured no big deal right? WRong. My IMEI (or TMFT) number was not in their database so they could not give me an unlock code so they said. They told me to call the manufacturer of the device which they said was Microsoft. Knowing full well this was crap I called anyway.
The support guy got a good laugh; MS does not make devices
like this, they only provide the OS. He recommended I call Siemens.
So I did. Real nice guy named Jack had a good laugh as well. Not only could Siemens not tell me who really made my device (a third party made them for T-Mobile) but even if they had unlock codes they could not provide them because of contracts with TMobile. So I go back to TMobile.
The support people felt really bad about the run around and escalated really high up the chain (or so they said). AFter 48 hours I decided to take my own course. Having had good luck unlocking a Treo 600 through 'alternative means' I figured time to tackle the Pocket PC Phone Edition.
This was MUCH different and much harder to figure out.
After a good 12 hours and a whole slew of reading I finally figured out some stuff. Most of this may seem a no-brainer to some of the more educated XDA people out there but for us newbies maybe it will help.
----------------------------------------------------
The PDA side of the ppcpe and the radio/phone/gsm side are two totally different animals (not a surprise to some). When you refer to the 'operating system' you're talking about the ROM
like the XDA Developers special edition or any of the ROMs from the ROM kitchen at http://lumpistefans.dyndns.org/. The Radio or RSU (for Radio Stack UPgrade) is totally separate from this. The other variable is the bootloader version (Wallaby in my case).
Now my goal was just to use the XDAUnlock program. When I ran the program right from the defaults I got 'error getting unlock code.' All the posts I read said put on the special edition rom and you'll be fine but that did not do the trick. Still got the same error message.
Here's what I started out with:
ROM: 4.01.16 ENG
Radio: 6.25.02
Wallaby booatloader: 5.22
What finally worked:
Radio: 6.24.00
ROM: 3.17.03 ENG (xda special edition)
then upgraded bacdk to 4.01.16 ENG
Wallaby boot loader 5.15
How I did it
--------------
I meandered my way through this to eventual success and since the dratted device now works fine I'm leery about putting it all back to the old way and doing it all over again. Therefore use this process as a guide only, not a definitive instruction set. Also I walked through this as a troubleshooting exercise so some steps may not have been necessary. I eventually succeeded but maybe went the long way around to do it.
References
----------
- Bootloader utilities: Get to this by holding down the power button and pressing soft reset. You may have to hit the contacts button to get into the menu if you don't see it right away (like if you see a simple GSM OK message at the bottom of the bootloader display.
- Cold boot: the reset swtich on the right side bottom of the device with a picture of a red battery with an \ through it. This disconnects the batter from the mainboard and trashes all the data on the device except the Operating System in ROM.
What I grabbed
------------------
- XDATools
- XDARit
- ActiveSync (I used 3.7.1) and connection by USB cable
- Wallaby bootlolader version 5.15 files
- XDA Developers Special Edition ROM
- RSU 6.24.00 files
- XDAUnlock.exe
- SD Card (mine is 128 MB but I think as long as it's bigger than 64MB or your current memory in the device you're OK)
- pnewbootflash_40116.exe
All of these files are available here on xda-developers.com, just
search for them.
First back up everything. Not just using the sda backup tool, from the boot loader. You can do the SDA backup if you want, consider it backing up your data. You can also do the ActiveSync backup if you want to save your data. In my case all my data is stored in Domino so I don't
give a hoot about the data on the device. Your mileage may vary!
Second I'm doing ALL of this with no SIM chip in the device. THis may or may not be necessary.
Stick your SD card into the PDA. If it complains about wanting to format it go ahead and let it format the card unless you have stuff on it you want. I'd recommend dropping anything you want from the card onto safe media and just working with it as a blank the rest of the way through because it's easier to just wipe the card in between some steps.
Go to the bootloader utilities. Hit Contacts button and you'll get the boot loader option stuff. If the bootloader utilities you get to right away takes you to a menu with things like Boot+CE-->SD then you don't have to worry about hitting the contacts button. You only need Contacts button
if when you get to the bootloader screen you see nothing more than
some nice colors, the bootloader version and "GSM OK" message.
Take the Boot+CE-->SD option to back everything up. This will take a few minutes.
Once it's done pull the SD out ofthe ppcpe and stick it into your SD card reader.
Bring up xdarit and chose your removeable device.
If you have more than one MMC slot select the different ones until you get one that says 'wallaby' in the hex codes at the bottom of the XDARit screen. You'll be writing out two files, the first is the NB0 file (which is the bootloader) and the second is the NB1 file (which is the OS or ROM). Name these something like original.nb0 and 1.
Wipe the SD card (format FAT).
Stick the SD card back into the pda and soft reset, then cradle it.
Go to a DOS prompt and CD to where you put 'pnewbootflash_40116.exe.'
Type 'pnewbootflash_40116 nbl515.nb0' to write the wallaby 5.15 boot loader to the device. If when you downloaded the 5.15 bootloader you called it something else (like 'wallaby_boot_loader_V5.15.nb0'
you should of course use that name instead!
The output looks like this:
D:\XDAtools\binaries>pnewbootloader_40116 bl515.nb0
Copying D:\XDAtools\binaries\itsutils.dll to WCE:\windows\itsutils.dll
in FindFlashInfoOffset
protection found at 8c0d60f8
result: 00000000 00000000
Now..why did I downgrade the bootloader? At this stage I'm troubleshooting why I get the 'error getting unlock code' message running XDAUnlock. I've got three variables I know of, bootloader, ROM and Radio Stack. I chose to start with the bootloader because
some posts out there say boot loaders 5.17 and higher have some checksum that keeps certain ROMS from working properly. Perhaps if I'd started with the radio stack I'd have been done right away and saved a few hours but all the posts about possible device destruction made me start with the bootloader! Again, your results may vary!
Next I changed the ROM to the XDA Developers special edtion.
Make sure the SD card is in the PDA and cradle it.
Run OSIMagetool and load the ROM file in the first box, chose SD Card in the second box.
If you downloaded the special edition ROM you might
have some luck using the Installer that comes with it but apparently that
does not work with ActiveSync 3.7.1. I got messages that said it could not access the device or no connection etc. Instead I used OSImageTool to load the NK.NBF file included in the distribution. Note that to get to this file you DO have to unzip the EXE file you download!
Once complete pull the pda out of the cradle.
Hold power+soft reset to get the boot loader menu. This should show up as 5.15 now. It will automatically detect that the SD card contains a ROM that can be flashed to the device. If for some reason it does not automatically detect this maybe you have to hit Contacts. I did not have
to do that, it just told me to hit Action to download the ROM.
Hit Action button (aka the jog button) to write it to the device. This will take a few minutes, go grab a beer or two or three. I took the safe route and connected power to the device while writing the flash.
Once it's finished cold boot the device. I waited 2-3 minutes before re-engaging the battery.
Here's a gotcha. On the right side of the SIM there is a little switch. If the rubber door for the sim is not totally closed you can't get the device to boot. This switch is real small so it's very possible to miss it. You can see it fine if you take the back off the device (which I determined from a post here that told you how to get the battery out).
When it boots you should have the 5.15 wallaby booting the xda special edition. Follow the instructions to calibrate the screen and you're ready to move on.
Now if the radio is 6.25.02 xdaunlock won't work, it just generates the 'error getting unlock code' message. You have to downgrade the radio to have this work.
There's lots of posts around here that say don't screw with the radio because if it errors you've got a fried device. I imagine this is true so balance how bad you want to unlock the device against the possibility of totally frying the device. I've done two radio upgrades in my life on the PPCPE, both were OK but again, caution is advised.
Grab the 6.24 radio zip and unzip into a folder on your computer. Use activesync to copy the files to \windows on the device.
Execute the rsupdate.exe program to reprogram the radio to 6.24. WHen completed soft reset the device and go into start-settings-system-device info to make sure you're at 6.24 radio vesion.
Copy the xdaunlock.exe to the device and execute. It should say 'you're device appears to be SIM Locked, would you like to remedy this?" click Yes to unlock the device.
Now the device is unlocked. You can change the ROM to WM2003 now if you want (which I did). I imagine you can re-upgrade your bootloader
and radio stack if you want but I'm leaving well enough alone for now!

Hi ALL
I did unlock my phone thank you all.
Spicial thanks to "rhodwyn".
Best regards.

Works!!!
Thanks !!! Its working!!!

help in getting all the files needed....
Hi,
I would like to try this.... but where can I get the file pnewbootflash_40116.exe? Or is this a file that I'll create?
rhodwyn,
I would appreciate some help in getting most of the files.
Thanks in advance.

It worked for me too, thanks for the great solution, rhodwyn!

Thank you rhodwyn and everybody... my 2 cents
I love this site and I think that everybody does a great job. I found rhodwyn’s post to be very comprehensive and it is the one that ultimately helped me out this time. I don’t know if anybody is even interested anymore, but since I’ve been helped, I figured that I’ll try and help someone else. I assume that you’ve already read rhodwyn’s post.
I had the same starting configuration. I did everything that he suggested except for changing the bootloader and it worked perfectly. So, as he suspected it was enough to downgrade the radio stack and to load the special edition ROM. I subsequently upgraded my ROM and all is good (although I haven’t upgraded the radio stack and I’m not sure if I will).
I’ve read other posts about problems downgrading and upgrading the RSU and the 1% problem… I had a problem the first time I tried and I became very nervous, but I looked at rhodwyn’s post more closely and placed rsupdate.exe into PPC’s \windows folder and tried it again and was successful.

thanks
rhodwyn
10 minutes and done

Imei-Check unlocker reverse

I am going to unlock a MDA compact 3 with the imei-check unlocker and I was wondering if I could help to make a free unlock tool....
So which tools do I need...

Start here, and read the whole thread accurately:
http://forum.xda-developers.com/showthread.php?t=280819

SIMLock
So is this nice little Programm you developed in so many hard steps also capable of unlocking the new HTC Artemis (MDA Compact III)?? I would need to know that before bying such a nice device.
On the Homepage of the IMEI-Check the Artemis is cracked with the exact same programm you can download there, but i don't feel like paying for the Unlock key ^^ I read the whole Thread in the Hermes Forum but the Artemis isn't mentioned there, so i wonder if this C3v1Unlocker will work with this Key Unlock key you posted because this Key is surely computed for a Hermes based device... Answers appreciated And thanks for your Great work!

Samson711 said:
So is this nice little Programm you developed in so many hard steps also capable of unlocking the new HTC Artemis (MDA Compact III)??
Click to expand...
Click to collapse
no, it patches the Hermes radio will not be valid for Artemis... although should be a very similar patch, because both devices are quite the same.
Samson711 said:
i wonder if this C3v1Unlocker will work with this Key Unlock key you posted because this Key is surely computed for a Hermes based device...
Click to expand...
Click to collapse
The "unlock key" is only valid after patching the radio.

Ah, okay, i see. Is anybody already working on a Radio Patch for the Artemis? I imagine, if the Radio is patched, it should be possible to create a similar Program for the Artemis, once someone gets a key for his Artemis IMEI, or am i wrong with that?

I've been investigating about this, it is not correct what I said previously: the patched radio method used in Hermes or Universal will not work on Artemis.
On Artemis (and other OMAP based devices) the SIM & CID lock area is stored encrypted on Disk-on-Chip (DOC), on the first block of binary partition 1 which can be accessed with pdocread.
I guess imei-check reads this area and patches it (probably they have to load a "fake" bootloader in RAM first to get SecLevel=0, as they did with the activesync part of the Hermes unlocker).
I don't have Artemis and can't do much more, but if someone is interested in researching I will be watching this thread and try to help, so feel free to post tech questions here if you are serious about writing a free unlocker for the Artemis.

thagangsta said:
I am going to unlock a MDA compact 3 with the imei-check unlocker and I was wondering if I could help to make a free unlock tool....
So which tools do I need...
Click to expand...
Click to collapse
have you read this tread ? -> http://forum.xda-developers.com/showthread.php?t=274860
I have "reconstruct" what actually that utility do. Actually utility uses ITSME utilities to access phone, but on exactly adresses. First it reads some area form RADIO of the phone to the file. That area is 16K large and contains IMEI.
pdocread.exe -n 1 0x040000 0x4000 -b 0x4000 "pdocread.dat"
After that in temp file pdocread.dat at addresss 0x300C - 0x3013 is stored IMEI. One digit is for some CRC check, I think CRC8 but didn't check at all. So that "IMEI Wizard" changes IMEI in file pdocread.dat, calculates and changes CRC digit, and writes file back to the RADIO of the phone with command:
pdocwrite.exe -n 1 "pdocread.dat" 0x040000 0x4000 -b 0x4000
So simple and working.
When it doesn't work ? It doesn't work on new G4 phones, even WIZARD and PROPHET. It works on the same phones, but with old G3 chipset. And phone MUST be CID unlocked and RAPI enabled. The reason ultility fail to work on new G4 phones is that pdocwrite is not ready yet to work with that phones. I am looking for utility to change IMEI on P3300 (Artemis i think) or S200 (PROPHET) too.

IMEI Change?!
The "older" HTC Devices can all be unlocked without changing the IMEI i think, there has to be a way to unlock this phone without changing the IMEI of the unit. Apart from the unlocking process being illegal already, changing the IMEI of a Celluar Phone is even worse Maybe i got your post wrong and you do not intend to really change the IMEI, i dunno...

Samson711 said:
The "older" HTC Devices can all be unlocked without changing the IMEI i think, there has to be a way to unlock this phone without changing the IMEI of the unit. Apart from the unlocking process being illegal already, changing the IMEI of a Celluar Phone is even worse Maybe i got your post wrong and you do not intend to really change the IMEI, i dunno...
Click to expand...
Click to collapse
I DO intend to change IMEI. Who do you think are ? My mother ? What's next ? To pull my ears ?
Yes, we ALL know consequences from changing IMEI. And we ALL read well-written topic about it >> IMEI changing is going to get you sore!. << Did you ?
And did you know that is some countries you just MUST to change IMEI to use your phone ? I will save your time for searching and point one of hundreds topics about this >> To all TURKISH fellows and others a must read story !!! <<. And because of this I can't upgrade to better phone ... for now.
So .. if you don't offer anything constructive but just criticism - please, go to flame on some other topic. Or better - just shut up.

serious business!
Kircho cool down and tell me something
I may be coming to Turkey early next year (January, maybe). Please confirm that roaming with my current provider for a week is no problem? Or do I have to carry my receipt?

kircho,
Probably you've been confused because the company that sells SIM-Unlocker for the Artemis is called "imei-check", but we were discussing about SIM-Unlock here, not imei-changing.

Haha!
Lol, Kircho... how old are you??
I don't care what you do with you IMEI, believe me, i really don't! All i said is that i would love to have a method to disable SIM Lock without messing around with my units IMEI, thats all.
It was NO CRITICISM of your work, my knowledge with PDAs and Windows Mobile does not suffice to render any code to unlock a device and i am not flaming here. If this thing you figured out works for your device, thats cool and i am glad for you, i just wouldn't do it with my device, thats it...

victoradjei said:
Kircho cool down and tell me something
I may be coming to Turkey early next year (January, maybe). Please confirm that roaming with my current provider for a week is no problem? Or do I have to carry my receipt?
Click to expand...
Click to collapse
There is no problem with roaming. If your SIM card is issued by some forign operator like UK Vodafone or Dutch KPN - you can use any phone in Turkey with such card.

Pof
Do you know of a way to unlock extended rom on Artemis? I tried the wizard unlock. It appeared to work for a while but ultimately it has done strange things. The extended rom seems to be visible but not the files within...after a while even the visibility of extended rom is lost.
Thanks, a.

I again have a Artemis (dutch mda compact 3) and I can test with for 2 days...
Im gonna unlock it with the paid imei check software....
I have tried to enter bootloader but it won't enter...
How can I be helpfull to do make an unlock tool...

@apap: sorry I don't have an Artemis, and I don't know.
@thagangsta:
Have a look at this thread in order to understand how this was done in the Hermes:
Reverse engineering the HERMES imei-check unlocker
The bootloader commands for the Hermes are explained in these wiki pages, someone should start researching Artemis bootloader and put the commands on the wiki, it is very similar to Hermes.
Hermes Bootloader Information
Hermes Radio Bootloader and AT command interpreter
Some hints that may help you:
1. You can run the unlocker as many times as you want, it doesn't matter if you've already unlocked your device, the imei-check unlocker will behave the same.
2. In order for the USB monitor capture to be useful, you need to click on the "COMPLETE" tab and when you have captured it, export it as ANSI TEXT.
3. If the app fails (communication error) you need to create 2 admin users, 1 for running usb monitor and the other for running the unlocker. Use right click, "run as..." and then select the other admin user. You need to repeat this process several times until you can successfully get the log.
4. be careful on what you post here, as imei-check has intelectual property rights on their work. Do not "copy" their solution, but reimplement it in another way.

EHh Pof
Just read the thread for the hermes unlocking. I'm not a complete noob but i'm still stunned by the technical data.
Removed a unformiliar program a week ago called "- -" after canceling a imeicheck upgrade (had no valid .unl file)
Reading "First the imei-check unlocker transfers a CAB file to the device via ActiveSync which installs an application named "- -", which contains at least MIGsoft LTD security certificate (used to sign the NBH file with the bootloader upgrade) and runs some other stuff like this (not completed):"
This must mean the unlockers of the hermes and the artemis work in the same way.
Main Questions are:
Is an unlock for the Artemis using imei-check able to use SuperCID?
Which bootloader can we use that is able to flash all roms?
Which code can we use for unlocking.
Edit
I've found an crack for themida secured files. POF You've stated that the .unl files are themida protected could some people post their unl files.
Could be an easy solution......

Perjan said:
Removed a unformiliar program a week ago called "- -" after canceling a imeicheck upgrade (had no valid .unl file)
Click to expand...
Click to collapse
You can usb-sniff what is transfered over activesync without the need to pay for it, it is done before it requests .unl file. For sniff the rest of the process (which is done in bootloader mode without activesync) you need to pay for the unlocker.
Perjan said:
This must mean the unlockers of the hermes and the artemis work in the same way.
Click to expand...
Click to collapse
Yes, they must be very similar.
Perjan said:
Is an unlock for the Artemis using imei-check able to use SuperCID?
Click to expand...
Click to collapse
Yes, but it's not sticky (will loose it after 1st rom flash after applying unlocker). I have solution for this to make supercid sticky if you reverse the process.
Perjan said:
Which bootloader can we use that is able to flash all roms?
Click to expand...
Click to collapse
Most probably the earliest shipped bootloader version. See to which version of bootloader imei-check unlocker downgrades your device when run with the proper key.
Perjan said:
Which code can we use for unlocking.
Click to expand...
Click to collapse
You will see it when usb-sniffing the unlocker.
Perjan said:
I've found an crack for themida secured files. POF You've stated that the .unl files are themida protected could some people post their unl files.
Click to expand...
Click to collapse
Available cracks for themida are for older versions... this is not the way to go for sure, I also investigated and got nowhere.
About .unl files I don't know... I said exe unlocker file is packed with themida, never looked at .unl myself, I think its pointless because usb-sniffing is easier.
Good luck!

Just used the monitor with the unlocker but i'm not able to understand what it does and don't have a .unl file.
Here is the logfile ftp://xdaupload:[email protected]/Artemis/Mdacompac3_unlock_no_unl_file.ms2
Pof Could you help me further.

ms2 is not useful... export capture in ANSI text format please.
Edit -> Export and Save as type "ANSI Text files".

A new Universal owner

Edit: Phone flashed nicely. Did'nt want to make another post so that this would'nt be bumped to the top.
/Edit
Hello everyone!
Thanks to all the users and admins for this great forum. I've found a lot of useful tips here, like getting the Scandinavian letters to work, and I look forward to be a part of this community.
I've been using PDA's for quite a while but this is the first combined PDA/phone (unless you count smartphones, and a brief encouter with the Nokia 7710 which I hated )
My list of PDA's goes something like this: Palm M100, Palm 3C - a long pause without a PDA - got a M100 again - IPAQ 3850 - Pocket Loox 710 - XDA Exec
My list of phones would be about this: Nokia NMT 101, Nokia 1611, - Nokia 6110 - Nokia 7110 - Ericsson T65 - SE T68i - trial user for a nokia 7710 with TV - Motorola MPX220 - XDA Exec. Had some other phones too, but used them for a short while or bought them as spares.
I recently bought a used XDA Exec, the rom is 1.13.48 WWE which is ancient. The Exec seems very unresponsive and slow compared to any PDA I owned earlier also it seems prone to crash. I have some warranty left, so I'd prefer to keep an O2 ROM since then I'd have less to explain if I need to get this thing serviced.
I figured my best choise would be the "Xda_Exec_Upgrade_v1.30.162.exe" with a corporate install, since I'd rather be without the clutter as I wont use any O2 services.
A few questions:
1) My boot loader says "serial v1. 00" Should I upgrade it to 1.01? Any performace imrovements or less chance of bricking if I update it?
2) I downloaded the ROM from the O2 page, although I'm not in the UK nor do I have a O2 phone number. Is it safe for me two install the firmware or will I get a locked phone or country errors (got the fix for that just incase)?

ManWithHugePhone said:
A few questions:
1) My boot loader says "serial v1. 00" Should I upgrade it to 1.01? Any performace imrovements or less chance of bricking if I update it?
2) I downloaded the ROM from the O2 page, although I'm not in the UK nor do I have a O2 phone number. Is it safe for me two install the firmware or will I get a locked phone or country errors (got the fix for that just incase)?
Click to expand...
Click to collapse
1) For new ROM upgrade, bootloader v1.00 is good enough. Unless you have nothing better to do, you can play with v1.01
2) Those ROM you are talking about are grandfathers' time ROM. If you dare, try some of the ROMs cook by our fellow guys here.
- Helmi's, http://forum.xda-developers.com/showthread.php?t=286036
- Indra's http://forum.xda-developers.com/showthread.php?t=285488
- Ivan's http://forum.xda-developers.com/showthread.php?t=287270
In a ROM, besides the upgrading tools, the actual software is in 3 files
1. nk.nbf (M$ Part)
2. ms_.nbf (Extended ROM, sevice providers software), do not change this, just ignore by moving to another directory.
3. radio_.nbf (UMTS/3G/GSM part)
Steps,
1. Ensure your normal mode cable connected (not InfraRed) activesync works.
2. Backup you current Applications, Contacts with Outlook and whatever that is important to you!
3. You need to run/copy (exe type) or extract (zip/rar type). You will see a lot of files including the above 3 files.
4. You can upgrade all 3 or individually by moving any of the unwanted 3 files to another directory.
5. Set device to bootloader mode.
6. Use MaUpgradeUt_noID.exe (not ROMUpgradeUt.exe) to avoid country errors. Run it and just wait.
Splash screen (O2, Imate, Dopod, Qtek Logos) maybe the wrong one, but if you can live with it, it is ok. If you cannot, the is tools in this forum, use the search tool.
SIM locked is different thingy all together, have never tried unlocked tools. Use the search tool here for unlock software.
Good Luck

Thanks CWKJ for your feedback!
About the ROM, I know the one I'm thinking to upgrade to is almost a year old but as I said its mainly so that I don't get any warranty issues. I'm thinking that if I have to return the phone and it boots to a QTEK-splash screen then I would have a lot of explaining to do. The current ROM is just so slow that I can't live with it.
Once the warranty is over I'll gladly experiment some more. Especially if there are some nice crossbow components or wireless improvements.
CWKJ said:
Steps,
1. Ensure your normal mode cable connected (not InfraRed) activesync works.
2. Backup you current Applications, Contacts with Outlook and whatever that is important to you!
3. You need to run/copy (exe type) or extract (zip/rar type). You will see a lot of files including the above 3 files.
4. You can upgrade all 3 or individually by moving any of the unwanted 3 files to another directory.
5. Set device to bootloader mode.
6. Use MaUpgradeUt_noID.exe (not ROMUpgradeUt.exe) to avoid country errors. Run it and just wait.
[...]
SIM locked is different thingy all together, have never tried unlocked tools. Use the search tool here for unlock software.
Good Luck
Click to expand...
Click to collapse
Thanks for writing those steps to me. I did search thoroughly, and found many guides but yours is the most easy to follow. I'm having some problems with activesync on my laptop (although it works fine through bluetooth) so I guess I'll try it on my desktop, which probably is smarter anyway so that the computer does'nt go into standby or hibernate in the midst of the update
Edit: My phone is unlocked, I was just worried if the software update would lock it for me. But I guess its silly to worry in advance.

Notebook has battery and standby mode can be switch off. In case of power failure (it will be very unlucky if it happens), the upgrading still goes on. The same (continue upgrade with battery) will not happen for Desktop. LOL...
Make sure is cable connected USB activesync.
One more point to note, in Bootloader mode, it is connected, but you will not see the activesync in operation!
You can change the screen (but software version can be checked), you can flash back the old software.
You can use the free tools here to unlocked again.