Database Users

Who can give me their T-Mobile number so I can dl the upgrad

hi,
Sum1 here who a T-Mobile subscriber? I have a T-Mobile PocketPC that I need to unlock tho I'm not a T-Mobile subcriber. I need a T-Mobile mobile number to get the upgrade at http://www.t-mobile.com/products/handhelds/pocketpc/download_popup.asp
Or if someone already downloded the upgrade where can I download it without keying-in the mobile number? Thanks.
BTW, I have a question, if I download the upgrade, can I now use the XDAunlock.exe file here (is my ROM automatically updated)? My ROM version now is 3.14.40 ENG. I'm having trouble with the ROM updater here since im not linux literate.
Email me at [email protected]. Thanks a lot

I already downloaded the TMobile upgrade. Can somebody tell me if this upgrade will indeed upgrade my ROM to the correct ROM version with wirelss modem feature to I can use the XDAunlock.exe to unlock my xda? Thanks

The answer is NO, the latest TMO upgrade is 4.01.00 and it has no wmodem.exe application. If you need to unlock your device, go to www.xda-developers.com/XDAunlock/ and use the tool there.
If it doesn't work, try the kitchen at www.yorch.net and cook a new 3.17 based ROM and flash your XDA and unlock it, then you can upgrade to TMO 4.01.00 later.
BTW, the TMO upgrade affects the RSU part. So, unless you are a TMO user you better use the .nbf file only with either SD card or use the XDAtools to flash your device.
Good luck.

Hi Biso,
How can I "cook" a rom? http://kitchen.romanweb.com/kitchen/index.php when I go to that website, the only thing needed to be selected are the 3.17.03 ENG O2-Euro (6656 kB available) and XDA-developers AutoConfig data (113 kB) under it. and the unlocking option right? This wil be the first to use my pocket pc device, which option should I select under How would you like your ROM?
installer EXE
zipped NK.nb1 (SD-card flashing)
zipped NK.nbf (advanced users)
and should I do anything on the NBF header string?
Thanks man.
If I use the intaller EXE file, how will I "flash" it on my device? What are the differences between using the exe,nk.nb1 and nk.nbf? Thanks again.

I notice that above the page there is an indication, by default when I go to the page (without checking or unchecking anything) the top of the page states:
space in ROM: 6656 kB
used: 7729 kB
free: -1072 kB
*overload*
Should I limit my ROM on 6656 kB (meaning that I have to uncheck other options)? My deveice is an XDA 1. Thank you.

Hi ...
Yes, you have to uncheck some optional s/w till the guage line is "Green".
If you are not familiar with the SD method, just select the EXE type. It will generate a 15 MB exe file which you should download it to your PC. Connect your XDA to your PC throught the cradle and ActiveSync and run the exe file while the cradle is connected to the power supply and follow the instructions on the screen.
Good luck.

Thanks man for the quick reply.
Sorry I'm getting confused. Should I transfer the exe file to the device and run the exe file on the device?
Thanks again

The exe file runs from your desktop, your xda will need to be synced with your pc before running the exe.

Thanks so this is what I have to do:
First sync my device (cradle connected to the power supply) and after synching, run the exe file on my desktop computer (no need to transfer on my device or anything?). That's it?
Is this fail-proof? Will it not damage my device if ever there was an interruption or sumthing? How can I make sure that I can go fail-proof? Kinda worried coz I just got hold of my xda 1 (T-Mobile edition), I'm a palm user before. Thanks
BTW, my PocketPC Version is 3.0.12039 (Build 11178). ROM version 3.14.40 ENG. I don't know if my PocketPC is 2002 or 2003. I'll be using the yorch.net ROM (http://kitchen.romanweb.com/kitchen/index.php). All compatible?

ROM 3.14 is a PPC2002 one and all ROMs on Yorch.net is WM2003 except the 3.17 one.
Just to ensure it's a safe process, remove the SIM and SD card from the device and stop any running applications on your PC.
Good luck ...

Thans Biso. How bout a step by step guide? Pls pls pls? Id really appreciate it man.
Like
1. Sync the device (Power connected to the cradle)
2. Run the Rom Exe file
3. etc.
Just to be sure. BTW, is the exe file really just 150KB? Is that all I need to unlock my device?

Hi ...
There is nothing really needed more than what you just wrote:
1. Connect the XDA to the cradle and sync while the power is connected.
2. Run the EXE file and follow the instructions on the screen.
BTW, the EXE file should be at least 15 MB, seems your ROM was not "cooked" well .... try again

Ohh ok. I downloaded twice and all I got was 150kb. how will I know that the ROM i got is "cooked" well so I can be free of troubles. Can you just give me a link to the right/"well cooked" ROM? Thanks man.
One more thing, should I run the ROM EXE file while my device is synching or after the synch?

it's still 150 kb. Here's what it says when I view the log
./mkrom.sh: ../../kitchen.local/mkrom-inc.sh: No such file or directoryno files for configid 26220739Cannot fit files in given sectionsError splitting files

seems there is something wrong with the kitchen work space ... it happens sometimes ... no big issue.
You may try this kitchen as well http://lumpistefan.dyndns.org/
P.S: run the EXE file after the device is synced

which one should I pick? Pocket PC 2002 ROM or Windows Mobile 2003 ROM. And what's the difference. Sorry for my ignorance. Thanks for the replies.

Biso,
Can I use an MMC card for flashing? I MIGHT be able to borrow an MMC card. Also, I dont have a card reader but I have a digital camera which I can use to transfer the ROM image from my desktop computer to the card. Would you think it would work? Thanks again man.

will the exe file below work for me?
http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
and
http://www.xs4all.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
This is my Device's Information
ROM version: 3.14.40ENG
ROM date: 11/26/02
Radio version: 6.18
Protocol version: 324e4
Pocket PC Version 3.0.12039 (Build 11178) (Don't know if this is 2002 or 2003 pocketpc)
Pls reply. thanks

Hi ...
1. As the figure tells, WM2003 is the latest than PPC2002.
2. I can recommend to use TMO 4.01.00 as I have it on my device for almost 3 months now with no problems so far (few things have to be tweaked tho), but I heard good news about AT&T 30.09 ROM as well.
3. I can't confirm that MMC can replace SD card. I saw some threads on this but no final results.
4. The answer is NO, the only way to move the NBF file to the SD card is either a card writer or by using XDAtools with the XDA cradle. I don't think the card will be recognized by the bootloader otherwise.
5. SER-V12 is a PPC2002 ROM and useful only if you need to unlock your device (which I believe it's already unlocked).

No I just want to unlock the device, that's it I don;t really want a ROM upgrade, just so happens that I need to have a ROM upgrade to unlock the device
SO I can use the SER-V12? Thanks a lot.

Help please using XDAtools as I am a dummy!!!

Sorry folks but I have already posted this and don't know how to delete the previous post. after I reviewed the previous post I don't think I made myself clear enough. Please accept my apologies. But would appreciate help on this.
I have read the majority of the info on XDAtools on the forum and installed I believe correctly. I currently run on Win98SE. I have installed Jeff summers version of XDA tools. And though I think I understand what I am doing I am not totally convinced. Before I embark on cooking roms and upgrading etc I would like to be able to do the following:
1: Dump my current rom from my device to my PC I can do this using
XDAtools OSImage. But have noticed that I can only appear to dump
this as NB1(windows CE(*.nb1) type files if I try to call this NBF I get
the following errors:
”error opening C:\program files\xdatools\bootloader_v5_15.nb0ea for
reading. the system cannot find the file specified”
”error opening source bootloader from C:\program
files\xdatools\bootloader_v5_15.nb0ea. error opening target device”
Is it possible to dump my ROM to a file called ‘xxxx.NBF’? or must I stick with *.NB1? this is not a problem as long as the NB1 file can be reloaded.
2: When I try to upgrade my ROM by using OSImage tool and selecting
source as:
‘C:\PROGRAM FILES\XDATOOLS\BINARIES\ATT160204.NB1’
Select destination as ‘device memory (via Programme A) ‘
When attempting to load an ‘NB1’ ROM from my PC to my device memory
(via Programme A) I always get the following message:
”Programme A not found - run with --register error opening target device”
I originally ran the ProgrammeA with ‘--register’ when first installed and tried numerous times since. Can someone please help as I am sure it is something simple I am missing. I only want to be able to use XDAtools to dump and restore ROMs.
I have tried searching for a solution but to no avail. Any help appreciated.
Thanks in advance John.

May you tell your current ROM version and device type?
Some ROMs do not accept the EXE or the XDAtools with NBF files upgrading methods. You may have to use the SD card flashing in this case.

Thanks Bis
Thank you Biso007 I am currently running A.30.09.ENG and my device type is an XDA1. But I believe the problem is associated with XDAtools ProgrammeA as it cannot find the specified files. Though I have followed all instructions for definition. There is probably something simple I am missing. You see I only want to be able to use XDAtools to dump and restore Roms without the need for SD/MMC cards.
Thanks John

Try downloading the XDATools from Jeff Summers site, it has all the missing bits, including the required batch file :
http://cuba.calyx.nl/~jsummers/XDA/XDAtools-Jeff.exe
That's from the sticky XDATools thread, probably read through there and you will find most questions answered if you continue to have problems.
Remember though that the SD card method is the preferred option, and if you burn any T-Mobile ROM's the SD card is *required* to reverse that.

Re: Thanks Bis
jdoherty76 said:
Thank you Biso007 I am currently running A.30.09.ENG and my device type is an XDA1. But I believe the problem is associated with XDAtools ProgrammeA as it cannot find the specified files.
Click to expand...
Click to collapse
XDAtools cannot work with WM 2003.
and you no need to backup A.30.09.ENG (ATT USA version WM2003), you can get it from online!

cgigate said:
XDAtools cannot work with WM 2003.
Click to expand...
Click to collapse
is that confirmed ??

Biso007 said:
cgigate said:
XDAtools cannot work with WM 2003.
Click to expand...
Click to collapse
is that confirmed ??
Click to expand...
Click to collapse
Yes, it for sure!
XDAtools only works with Pocket PC 2002 or some test version WM2003.(<4.0.11)
It cannot work with WM2003 official release (AT&T A.30 or T-mobile).

Thats weird, I am positive I used xdatools to program my sd card through reader writer after downloading the official WM2003 upgrade, in fact I must have used that method because I had to seperate out the radio stack and program just the ce rom, I have no other tools to do this.

XDAtools only works with Pocket PC 2002 or some test version WM2003.(<4.0.11)
Click to expand...
Click to collapse
I think you'll find that it only does *not* work with T-Mobile WM2003 ROMs. That's only because they lock up their OS to try and prevent us from changing ROMs. I don't think that's the case with any other manufacturer. I also think it doesn't make any difference whether it's WM2003 or WM2002, it solely depends on whether the manufacturer locks the OS.

Thank you cgigate & ebswift re XDAtools/WM2003
Thank you Cgigate and ebswift maybe this is why I am encountering problems with my download and restore of my ROM. I inadvertently choose a WM2003 AT&T rom to practice with. Maybe I should have chosen a PPC 2002 ROM to test??
I thought I had a problem with XDAtools and that I did not have all the correct links/files in place. Maybe I should dump my ROM and try restoring a PPC2002 and then re try my test. Thanks again guys.

i used xda tools with the AT&T WM2003 rom on my uk o2 xda with no problem. I wanted to keep my old radio stack as it was working fine and just used the os upgrade file, via SD card.
I would recommend updating activesync to 3.7 if you are doing it via the XDA cradle.
maltloaf

Did you use XDAtools to copy direct to device
Thank you Maltloaf, when you upgraded your rom did you use XDAtools directly from PC to device or copy the file onto your SD/MMC card and use the bootloader program to load ?? If so maybe you can answer the problem I am encountering. Thanks john

i have flashed twice (had to go back to 2002 for a short while)
both times using the SD card/bootloader method and I transferred the file onto the card using xdatools in the xda/cradle

Thank you Maltloaf
Thank you Maltloaf this seems to be clearer now, but in the context of upgrading etc XDAtools is only being used to copy the file from source to SD/MMC card. I was under the impression that XDAtools did not require the use of SD/MMC card. But maybe it's a matter of finding out what works for you. John

well xdatools should be able to flash directly to the xda as far as i know but it's always the safest way to do it sdcard style

Thanks to all
My thanks to all you helped with my recent questions. Thanks John

Burning ROM - phone not working

Hi, I'm hoping to get some help with cooking and burning ROMs to my o2 XDA.
My original product specs are:
ROM Version: 3.20.06 ENG
Radio version: 4.21.01
I cooked and then downloaded 4.01.00 ENG from Lumpi Stefan's site, then ran the rom.exe file that it produced for me. Everything worked fine, and then I rebooted my XDA. Upon first boot the phone appeared to work, but after performing a soft-reset because the XDA froze, all of the phone functionality appears to be not working.
When I do a hard-reset I get: Wallaby Bootloader v6.22 - GSM OK which I think looks good as far as the phone functionality is concerned. Looks like it's the OS that's on the XDA which is causing the phone difficulties.
I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started!
I don't have an SD card, and am in dire straits about getting my phone to work. Is it possible at all to get this to work, or perhaps to go back to my original ROM (I backed it up to orig.nb1) using XDAtools. Anytime I try to burn the .nb1 file back to my XDA it fails. Or is the ONLY way to get an SD card and use the Bootloader technique? I even tried downloading the 3.17.03 ROM upgrade directly from the o2 sitebut it fails.
Any help will be GREATLY appreciated.
Thank you.

[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![/qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.

[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![\qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.

Thanks, I will try. ActiveSync still works...
I notice you are running the same ROM version as me - sis your radio still work?

Can you verify that I am trying to Flash the ROM correctly?
1. Confirm that I have orig.nb1 - yes, it's there - backup of original ROM before I started this whole dilemma.
2. Ensure that XDA is Activesync'd - yes, as "Pocket_PC" - all working okay.
3. Right click on orig.nb1 and select "burn"
4. OSImageTool.exe then pops up and copies orig.nb1 to Programme A.
5. A DOS box then appears saying "ERROR: GetConnectionType - A
ote host. error getting connectiontype".
6. Programme A then runs and after pressing "next" a couple of times, I get an error - "Error 011: Cannot execute the remote communication program. Pleace make sure that the USB cable is properly connected."
And that's basically it.
I have tried different variances of this, but all without success.
Help!
BTW, I'm logged in to MSN Messenger now, could you let me know when you're online - or anyone else, for that matter. My address is [email protected]

This message means that the current ROM in your XDA can't be flashed through Program A ... not a big issue, for unknown reason it happened with me few times ... but now you have to use SD card to flash your ROM.

Here is an update...
I have played around some more with the XDA with no success. I have now bought a 64MB SD card and am unsure as to how the ROM image on my PC gets onto the SD card. This is how I have been doing it:
1) Insert SD card into XDA
2) Place XDA into cradle
3) XDA then ActiveSync’s to the PC
4) Run OSImageTool.exe and select the following –
a. Source: “C:\Documents and Settings\Paul\Desktop\orig.nb1”
b. Destination: “XDA SD card slot – unknown size”
5) Then I press “copy” and I see the progress bar go across to 100%. After this appears to finish, the program just sits there not telling me it’s finished. I assume that it’s all okay and I then close the program
6) Take XDA off cradle and hold power button down whilst doing a warm-reset
7) The following appears: “Wallaby Bootloader v6.22 – GSM OK” – nothing else happens, and from what I have read it is supposed to ask if I want to perform a ROM upgrade. However, I can get into the diagnostic and flash tools by pressing the action button etc, but nothing is in there to upgrade the ROM.
Does the fact the OSImageTool destination says “XDA SD card slot – unknown size” matter? I’m assuming not because when I have transferred the ROM using the above steps, the XDA asks if I want to format the card; meaning that the transfer worked okay. Do I have to have an SD card reader/writer on my PC to get the ROM onto the SD card?
I have read a little about a Bootloader patch – do I need to run this, and how do I get it onto the XDA – using the same method?
I would be very appreciative of any help that can fix this, as all I want to do is get my three-day old XDA working again!
Any other comments and help in relation to solving this hair-challenging issue would be great!
Thanks,
Paul…

Ok ... from what you wrote it seems your doing it correctly. However, I have doubts on the file orig.nb1 you are using ... maybe it wasn't copied properly.
Try to cook any ROM (TMO 4.01.00 is good) at Stefan kitchen and you can cook it as .nbf or EXE then extract the .nbf file using winzip or winrar.
Follow the same steps and let me know.
Good luck ...

Is bootloader v6.222 okay - will it allow me to overwrite my current ROM with this new ROM that you are suggesting? I have read that I may have to downgrade my bootloader to do the SD ROM writing thing.

I can't confirm that my self ... I used SD with 5.17 and 6.22 without problems but maybe it's my luck
Cook the 4.01.00 as EXE and try it as is or extract the .nbf file and use the SD method.

Okay I'll give that a go now... Will let you know how I go...

Nope - didn't work. I'm not getting a screen in the bootloader to update the ROM via SD - if I press the action button I get into dignostics...
Is this a bootloader issue, and if so, how do I downgrade?

Also just tried the following:
C:\Program Files\XDAtools\binaries>pnewbootloader bootloader_v5_15.nb0
And got the following error message:
Unable to find flash info offset, cannot disable bootloader writeprotect
Any ideas?

I don't get it ... you cooked and downloaded and tried a new nbf file for TMO 4.01.00 in less than 15 minutes ??!!!!
what is the nbf file size ??

Yes, I used Winzip to extract NK.nbf. It is 31,745kb.
I am now cooking on Lumpi's site a zipped NK.nbf file and will try that too...

PW10B1's ID as PW10A1

For some odd reason my T-Mobile PW10B1 (as labeled on the back of the device) is identified as PW10A1 in Device Information. I never paid any attention to that, but I got an error 012 when trying to upgrade to T-Mobile W2003. I'm currently running 3.17.03 (the XDA-developers Special Edition ROM v1.2), so perhaps prior upgrade affected the stock ID change from B to A.
How do I change it back to PW10B1, or how do I go about installing W2003 on my messed up device.
Thanks,
Marcin

Marcin,
i have the same with my AT&T. however i'm able to upgrade it to WM2003. the only thing confusing me that after upgrade it is stuck on splash screen, no further load. i tried different methods and versions... no results...
if you find the answer, please let me know

I can fix the problem!

Marcin, all you need to do is get an sd card and reader writer, you can then do the sd method of flashing which bypasses version checking. You will need xdatools also, just pass your mouse over xdatools link and you can download it from there.

very helpful
Nice advice, cgigate...that was very helpful...

cruisin,
I am in the same situation as marcin.
Please confirm my understandingof the bootloading from SD:
1. Using the SD+card reader, I copy the W2003 NK.NBF file to the SD.
2. Insert the SD card into the XDA
3. Goto the bootloader mode (power + soft reset) and press the middle of the rocker key.
4. After the ex counter increases.. at the end, press hard reset.
5. After 60 sec press hard reset again
If this is correct then why do I need the XDATools for?

Copying the file to sd will not work, it needs to be in a special format for the xda to boot the rom burning procedure, you will need xdatools. At the end you push the unscrewed end of the stylus into the tiny hole bottome right of xda, then again after 60 seconds and you should have a working system.

cruisin-thru
Thanks cruisin-thru.
I want to be very clear before starting the upgrade, so..Do I use the OSImageTool to special format for the XDA to boot from the SD?
Thanks again for your patience!
BTW: I did steps 1 to 4 of "unlock Wiz/Wallaby/SER/Backup and
now I (like marcin, have my T-Mobile PW10B1 identified as
PW10A1). I have yet to do the steps 5, 6 and 7. If I do these
steps. Will the identification be corrected?

so..Do I use the OSImageTool to special format for the XDA to boot from the SD?
Click to expand...
Click to collapse
yes after osimagetool have copied the rom to the sdcard the card should be unreadble to anything but the xda's bootloader

Upgrade to W2003
It is my great pleasure to have great and helpful people who advised and suported me in my XDA fiddling adventures. I have now upgraded to W2003 and unlock my phone to use any provider I wish.
Thanks to all!
Melody

Help me please !!
I have a XDA PW10A1 without the instalation cd-rom where do i find the drivers for my XDA ....... please help me !!!

Valikos, the only installation you should need is activesync which is freely downloadable from the microsoft web page.

Yes but!
If i have Win98 SE my computer do not see my xda , there are not drivers for 98 ? ....

Just make sure you have the latest ActiveSync version which is 3.7.1 ... sometimes uninstall then re-install solves this issue.

ok .. another question .... i have all my contacts in to a motorola accompli 008 and like the xda i don't have the instalation cd and no drivers , where do i find the drivers for this one , because i have more that 200 contacts in this one and i wold like to transfer all contacts in the xda

XDA tools problem

hy there,
when i was updating a qtek1010 to wm2003SE rom, that was cooked in romkitchen, the upgrade stoped at 99%.
now i can only get into the bootloader.
bootloader version : 5.15
i've searched, and now i'm trying to upgrade from SD MMC, when i'm using OSImageTool.exe , i open the nk.nbf, destination SD MMC, then it displays this error, (NK.nbf:incorrect filesize(33554463), file should be exactly 32505888 bytes. error opening input file)
What should I do???
Thanks

Download an other ROM. THE NK.nbf-Fiel you have is the WM2003SE ROM. This file can not be written through XDA-Tools.
Download anoteher WM2003 or PPC2002 ROM, flash your device via SD-Card and the run the exe File of the WM2003SE-ROM.....
Stefan

thanks so much, it worked
but now, when i put the sdd in the qtek1010, on the bootloader nothing apears.. only :
WALLABY
Bootloader
V5.15
GSM OK
and when i press action button it displays a diagnostics list like "ram, display, touch etc..."
what am i doing wrong?
what can i do?
i've putted the sdd card in a HP photosmart to copy the .nb1 file.. is this wrong?
thanks,
Luis Martins Portugal

Looks like the ROM isn´t written correct to the card.
Otherwise it will show directly in bootloader that you can install the new ROM.
I´m nearly sure the HP Photosmart causes this problem. Do you have access to another SD-Card writer?
Stefan

ok, i'll buy a card reader and try again
thanks Stefan
i'll post here the results.
gretz

Just to ensure. You have copied the ROM using XDA Tools to the SD Card, or?
Normal paste & copy does not work......
Stefan