Database Users

unlocking problems

Hi !
My device (PW10B1
3.14) doesn't unlock !
xdaunlock util says can't find code
trying to upgrade to developers 1.2 failed cause it's ver. 3.14
kitchen packs are available for ver. 3.17 and up
don't have a serial cable so didn't try other stuff
what do I do ?
Thanks guys,
Gili.

gilicomps said:
xdaunlock util says can't find code
Click to expand...
Click to collapse
Xdaunlock requires the wmodem in PPC2002. This is available in ROM 3.17.03
gilicomps said:
trying to upgrade to developers 1.2 failed cause it's ver. 3.14
kitchen packs are available for ver. 3.17 and up
Click to expand...
Click to collapse
Why does it fail? How are you trying to upgrade?
Normally you can update to all versions....
Stefan

it says that it's for ver 3.17 and I have 3.14
so it won't let me upgrade

using exe
when tried using sd image and didn't work (don't recognize my sd)
the question is if there's an exe upgrade for 3.14 ?

Re: using exe
gilicomps said:
when tried using sd image and didn't work (don't recognize my sd)
the question is if there's an exe upgrade for 3.14 ?
Click to expand...
Click to collapse
How do you try it?
You mus copy the ROM-file via XDA-Tools to your SD-Card.
After inserting the card in your device a windows popup will format your card. Donßt agree to this.
Enter bootloader by pressing the powerbutton and perform a softreset.
Bootloader will automaticly detect, that there is a ROM-Image on the Card.
You have to press the Actionbutton to do it.
It should work....
A few days ago there was a link to a step-by-step description how to upgrade.
Search for it...
HTH
Stefan

d/l new OSImageTool it asks for source nb1 (and doesn't find anywhere ..)
and destination (Can't set to my flash card)
So I don't really know how to transfer the image

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

T-Mobile Rom.... Can't do anything else... Help

Since updating to the T-Mobile Rom for my XDA, nearly everythiung has gone wrong.
And when I tried to downgrade it.... Nothing happens.
I used to use a modified Program A to upload it to my phone but it continues to say that the USB devide gets remotely stopped. the only thing that I can think is that my phone is cancelling the upgrade/downgrade.
I have also tried using a copy of the XDATools program to try and:
Upload another Rom.
Copy the rom to an SD card so I can use the bootloader method.
Change the Bootloader so I can use the SD card method.
None of there are working.
Help :-(
I really want to go back to the ATT rom, it might have the annoying thing with the sound but at least it doesn't mess up as much, doesn't format my SD/MMC cards and lets the alarms actually work for me.

if i'm not wrong, it seems you upgraded using the TMO exe file which updated both ROM & RSU.
check ur boot loader version, if it's 5.22 or higher, i think you need to dowgrade to 5.15 ... use the exe file that comes with the XDAtools in the binaries directory .. its name is fixbootloader.exe .. it should update ur boot loader to 5.15 by which you can use XDAtools or the SD method.

Tried that. I do have XDA tools on my machine and used that program but my CDA still has the bootleader of 5.22
And both of my machines don't like trying to update my XDA :-(
This Rom is the most annoying one I have tried mainly becaise now I can't go back to even my original one that I backed from the XDA when I got it.
Am I stuck with this ROM?

omg, i think i am having the same problem. In my case, since ive installed the new rom, i cannot sync with activesync, well very slow anyway. Activesync on my pc stops responding for a while and suddenly it says connected. However when i then run the executable created by the kitchen, it just flashes a command line window for a second.
When I try XDA-toolz with an nbf file, i get the following message:
ERROR: GetConnectionType - An existing connection was forcibly closed by the rem
ote host.
error getting connectiontype
Click to expand...
Click to collapse
Please someone help, because i am really stuck now.

I checked, my bootloader is 5.14, so that shouldnt be the problem, perhaps i need to reinstall activesync, or perhaps lumpistefans kitchen cooks up bad roms. :?:

Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!

Biso007 said:
Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!
Click to expand...
Click to collapse
I dont understand how i can have a wrong rsu? I didnt update it , as far as i know , i just updated the pda part. I only saw programme A.
Activesync does recognise my xda, because i can synchronize and explore my device. It does however take a long time before activesync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling activesync, this didnt help.

prowling said:
ActiveSync does recognise my XDA, because i can synchronize and explore my device. It does however take a long time before ActiveSync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling ActiveSync, this didnt help.
Click to expand...
Click to collapse
If there is something wrong with the RSU it will defeinitly slow the USB performance, not neceassary by wrong RSU flashing ... otherwise, check the pins of your cradle or the 22-pin connector of the XDA ... maybe one or more pins are bent or weared.

Tried upgrading the radiop stack and although the reception is slightly better... It still won't let me upload,
and its a new cable too :-(
Oh well looks like I am stuck with it.

Another way to upgrade firmware
Are there other ways to upgrade the bootloader from SD card from within the device or even to upgrade the OS from within the phone itself?
You know... as a last alternative?

You can use SD reader/writer from the PC using XDAtools ... once the .nbf file is on the SD card, use the normal SD flashing method.
Or you can use another XDA device from a friend to copy the file to your SD card

I am having the same problem. I have TMO 4.01.16 and since I installed I can't down/upgrade my ROM through EXE or XDA tools, it says my device isn't connected, but I can still connect with Active Sync and all that jazz

ha ha
I can fix all your problems!

How?

Finally got it to work, Although it was a little bit of effort to do so.
I went back to the kitchen and downloaded a NB1 cooked rom with the "B" Signature. Then I basically ran the TMobile Setup again...
Once the setup files were on my computer I overwrote their .NB1 file with the one I just cooked.
But.... I forgot to change the file for the Radio Stack.
The machine worked except for the phone and as something is still stopping me. *it was my first reboot* It wouldn't let me use a new radio stack.
Ended up that i kept on going in to the bootloader and eventually turned my radio off altoghether before trying an update.
Now I am back to a decent rom... (Cooked and modded version of the ATT Wireless rom) and I am almost really happy.
Now to figure out how to stop the annoying sounds starting off really low.
But til then... I'm 90% happy

Thespus2002 said:
How?
Click to expand...
Click to collapse
Use the Sd Method flashing!!
Tmobile roms won't let you upgrade from the usb, here's the link and it will guide you how to flash your device from the SD good luck
http://forum.xda-developers.com/viewtopic.php?t=3274

The way I described.. I had to use the USB method.
my current bootloader (6.22) will not allow me to boot from an SD card.
And XDATools will not allow me to downgrade it... Yet

on ur PC at \xdatools\binaries run this command: pnewbootloader.exe bootloader_5_15.nb0

Wish it was that easy. The phone still appears to be locked in the rom so I can't update the Bootloader. I keep getting a message that says.
Unable to flash in to offset, cannotg disable bootloader write protect.