Database Users

T Mobile Pocket PC and Siemens Sx56 Unlocking

HI too all in this forum i am new one in this
please guide me step by step the procedure to unlock it
Device Information
Rom Version: 3.14.40 ENG
Rom Date: 11/26/02
Radio Version: 6.18
Protocol version: 324e4
Model No: PW10B1
Plateform: Pocket Pc
and when i enter the test mode by pressing 3 button power+action+reset
they show
wallaby
bootloader
v5.15
Gsm ok
please guide me step by step
wbr
Ahsan MOosai
wbr
Ahsan Moosani

unlocking it
Hi to you too,pal! Well don't have to enter the test mode.
First try to install the xda unlock exe file fm this site,and then open it fm your ppc.
If the attept fails,find and download the special rom or rom kitchen,to overwrite a new rom which provides the use of any network.
Finally I've discovered a tip,on sx56.When is asking for SID lock code not PIN,type the number zero eight times.

Moosani said:
HI too all in this forum i am new one in this
please guide me step by step the procedure to unlock it
Device Information
Rom Version: 3.14.40 ENG
Rom Date: 11/26/02
Radio Version: 6.18
Protocol version: 324e4
Model No: PW10B1
Plateform: Pocket Pc
and when i enter the test mode by pressing 3 button power+action+reset
they show
wallaby
bootloader
v5.15
Gsm ok
please guide me step by step
wbr
Ahsan MOosai
wbr
Ahsan Moosani
Click to expand...
Click to collapse
I just unlocked my TMO XDA 1 ... it was painful! Here's a lesson's learned checklist.
1. Get a SD card reader/writer. ~$20 @ CompUSA.
2. Get a 64M SD Card for Bootloader flashing your unit.
3. Build a 3.17.03.exe ROM image at Yorch kitchen.
4. Backup current CE+boot to your 64M SD card. Enter Bootloader, wait for a "GSM OK" message to appear, press contact button next to speaker. Scroll down to Boot+CE->SD, select. This will copy current ROM to SD card.
5. Take this sd card, put in sd card reader/writer and using OSImageTool.exe (part of XDAtools), copy card to pc folder called CurrentROM or similar.
4. Remove sim & sd card from unit.
5. Put in cradle & connect to pc. Using a guest partnership is okay.
6. Run the 3.17.03.exe file. Mine failed. Couldn't read device config. Said to check USB/serial cable connection.
7. Went back to Yorch kitch, created 3.17.03.nb1 file, downloaded it, copied to SD card via sd card reader/writer & OSImageTool.
8. Insert this sd card into your unit, enter Bootloader & it will ask if you want to load this O/S, do so. This worked for me. Do a hard reset after successfully completion and when it comes up, it states unit is sim locked, do you want to change this, tap Yes. I copied XDAunlock.exe to unit, via A/S to confirm unit was really unlocked. XDAunlock confirmed unit was unlocked.
9. Problem, flashing to 3.17.03 put phone model to PW10A1, mine is PW10B1. Any .exe ROM upgrade software will not work. They "see" a model A and they're configured to install software for a model B ... at least in the USA.
10. To get around this, I put a ROM4.00.21.nb1 on the SD card via sd writer, upgraded unit's ROM via Bootloader. This was successful and model was put to PW10B1.
11. Then I ran my ROM4.01.00.exe which completely finished installing the RSU & ROM on my unit. The advanced copy of TMO's ROM4.01.00, RS6.24.01 is combined into an .exe. I'm sure .nb1 and .nbf exist.
I'm running an unlocked TMO XDA 1 and just packaged it for selling. Good luck.

i send the xdaunlock file in my ppc and open it but they show error erro to getting code , i send the file with infra red and open it in start>programes>filexplorer>mydocuments
but show error
i have only usb cable and infra red
please guide me
and its hard to purchase com cable from any other site just give me schematic and pinouts for cable i will make it by my own
wbr
Ahsan Moosani

Your ROM version is too old: if you install the XDA-developers Special Edition ROM it will provide you with some new features, and resolve your SIMlock problem as well.
Note that this will involve cold-booting your device, so backup all your information first.

how i update to rom because i have only usb cable which comes in box
there is any other way to make cable because it is hard to purchase for me give me schematic and pinouts etc.
wbr
Ahsan Moosani

you don't need a serial cable to flash your xda. just got to the kitchen at www.yorch.net. cook a ROM based on 3.17 and select the exe method. down load the file to ur PC and connect the xda to the cradle and make sure it's connected to power. run the exe file and follow the instructions.
good luck

@Biso007
thanks for reply me
but how download the file i find many things but not 3.17
could u give me complete link to download
thanks in adv.
wbr
Ahsan Moosani

XDA-developers-SER-v12
i download this from another site
this is the right thing to cook my palm on 3.17 check it
please before done any thing i want confirmation
i dont want to loose my palm

Thats the one, go ahead, make sure you back up your data first.

i received new phone from america and its locked
i did not make any things in it now they need to make backup
or not
wbr Ahsan Moosani

3.14 T-Mobile
g32e4
6.18
I want to use my phone in Vodafone in Spain. So I need to unlock.
I have the unlock tool from XDA but it says 'error getting unlock code'
this is due because it is incompatible with the version of ROM/Software I have on my PDA.
Now, I have a small problem. I dont have the USB cables, (I want t buy them but I cant find them ANYWHERE...if any of you know...that would be of MAJOR help.)
Is there a way around that? Is there a tool for my version?

Can I do this via my SD Card?
http://www.romkitchen.de/
Is this site worth trusting? What would I select to make my phone unlocked? I see on that site a rom for Spain's Telefonica (which I could easily make the switch to, and I wouldnt need to unlock phone?)
Can anyone explain to me the process?
Thanks!

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...

XDA 1 not working

Hi,
I was upgrading the software upgarde on my device. I successfully upgraded the Pocket PC software on the O2 XDA, but when I tried to upgrade the GSM radio/GPRS software of the O2 XDa, it gave some error and after this my device is not starting at all. The only mistake I did was that "I did not remove the SIM card before upgrading the GSM radio/GPRS software" The device does not start even after cold booting the same. When I start the device, the O2 screen comes and after a quite long time the main window does come but I cannot do anything. I tried to tap on contacts, time, tasks but nothing happens. I can see the windows logo wall paper but cannot do anything. Please help on how I can restore back my O2 as a cold reset also does not work. :?
Thanks and Regards
Jinesh

There's many topics about your question in the forum. Search it! Try to search with this keywords: 1% error, repair.zip

There's many topics about your question in the forum. Search it! Try to search with this keywords: 1% error, repair.zip

Hi,
I have tried all the available options but it still does not work. To restore the ROM how do I get access to the O2 cause niether serial nor USB is detecting it.
Please help.
regards
Jinesh

SD card install guide
Ok here you go, its a little outdated but its what I still use:
Qman's how to use XDArit to write nk.nb1 or nk.nbf to your SD card aka the Bootloader Method!
1. Place XDArit and the nk.nb1 or nk.nbf file in the same folder and start XDArit.
2. Select your SD card (disk drive) from the drop down menu.
3. Select Write to SD
Notice that the Windows CE box is already checked so just click the browse button at the end of that window.
4. Select your (nk.nb1 or nk.nbf) image and then Open
Notice by default XDArit will open looking for a *.nb1 file but if you're going to use a .nbf file you'll have to manually change the "Files of Type" to *.nbf
Notice that nk.nbo / nk.nbo was automatically added as your boot-loader and its check box is unchecked so leave it that way and click OK. XDArit should start writing to the card.
When XDArit has finished writing the image put the SD-card into the XDA and hold the power button and soft reset. You'll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a "Soft Boot/Reset".
Click to expand...
Click to collapse

Thanks Chief, I will try out and let you know.
regards
Jinesh

Hi Rudegar,
I tried the procedure given by you. I was able to write to the flash successfully. After writing to the flash it gave a message "Checksum OK, Please cold reboot to reset".
I did a cold reboot. After starting the O2, it showed the O2 logo screen and after quite a long time, it asked me wether I want to format the SD card or not. After that it took me to the default screen of XDA wher eit showed options like "Add today's date, Contacts, Schedule etc etc. but upon tapping any of the options the O2 behaves erratically. If I tap on today's date it takes me somewhere else. Inshort it does not work.
I again did a cold reboot and now the device is in its original position i.e not going after the O2 logo where it gets stuck up.
One thing I would like to mention is that all these activities have been done putting the O2 on the cardle only as the battery is totally discharged and the device turns on only after putting it on cradle. Even after the cold reboot it does not start unless I put it on the cradle whichis connected to the mains. Is it Ok with this or am I doing something wrong? The battery does not charge and hence I have to do it in this way.
Please suggest what wrong am I doing? Any suggestions from anyone will be welcome.
regards
Jinesh

Hi,
Someone posted the original O2 ROM on this site and I downloaded the same after which I was partially succesful in flashing the ROM and reviving my dead O2 back to half life. :roll:
I burned the ROM on
to my SD Card and flashed the ROM on to my O2. After
successfully flashing the ROM I rebooted the device.
The device now starts Windows but it takes atleast 15
minutes to start. I get the today screen. WHen I cick
on start the start menu appears after a delay of 10
seconds and all applications run normal, however all
this happens only on the Cradle only.
When I go into the Battery Settings it shows "Battery
Status Unknown".
Also none of the phone functions work. The SIM card is
not recognized and in device information it does
dispaly the "IMEI number" and the "Protocl Version"
I am only able to use inbuilt phone applications.
Is there some problem with my battery cause it is not
charging even on the cradle.
Device Information does not show Radio Version, Protocl Version & IMEI number at all.
Can anyone please help me?

hello all,
it means that your radio stack are dead. Currently, We don't have any real method to fix this problem. When the radio stack is error, you can not upgrade it or do anything to make it work. We can only upgrade or downgrade the radio stack if it works. Also if you try to upgrade the radio stack, we realy need to flash the chip using a speceial tool or need the sd card which build in radio stack with we can only flash in bootloaading mode. Howerver, in some case, we can fix it but .... I think it is just lucky or the xda error when battery problem.... in this case, just disconnect the battery few minutes and connect it again by pressing the battery hole.
Regards,
Hoanghon
p.s. I have dead xda. I killed it when I upgraded the RADIO STACK. Therefore, if you are really need to upgrade the radio stack, I recommend use the official upgrade for secuirity. or just upgrade the rom only.
Note:
To eliminating the error, you need to upgrade the rom or the radio stack, you need to check if the rom fix the radio stack or the stack you are trying to upgrade it fix the rom or not.(ie, Tmobile Rom have to use it radio stack built for Tmobile pocket pc...... I know that in some case when we mix between the radio stack and OS it works but I don't think it work propertly. Anyhow the mixing bettween radio stack and OS is very dangerous if it doesn't suppport then you have to reflash the radio stack or rom(the OS is Okay but the keep upgrading the radio stack may cause the radio stack killed)

WE NEED SERIAL CABLE FOR PDA ANY HELP PLS!!!
Hi Jineshd we
have the same problem and we are sure that the only way is to do SD uptade
and U said U have a serial cable to Yours device. With that we can be able to download flash gsm rom from working device and put it back via SD card to ours. Pls tell me where can I get a serial cable or some schema how to prepare it and I will try to repair ours dead pdas. Its our only chance
rgds
Lukasz

Hi,
Thanks all for the replies.
Can anyone tell me how doI repair the radio stack?
Regards
Jinesh

no way without having special RSU rom update on SD card and run it from bootloader or dissembling the device and reprograming GSM rom on special rom/bios programing socket. (Here on forum is user Cgigate from Toronto CA who can do it but I cant contact him)

Using XDATOOLS on SX56

To unlock my device I installed the XDA Special Edition ROM on my SX56 by running the executable. My device is a PW10B1 (printed on the back of the device). Unfortunately, after installing the XDA ROM, my device information says the device is a PW10A1. Now this seems to be causing a problem. I want to get WM 2003 back on the device but running the AUTO update tool (Executable with the Wm20003 update) errors out saying that my device is a PW10A1 and not a PW10B1. First signs of panic.. Ok. So I decided to search for the original PPC2002 ROM for At&T and I found it. But its a .nbf file. So I downloaded XDATools hoping to write the image to the device memory or to the SD Card. However I cant seem to access the device from the Destination Browse Button of the XDATools App. The browse dialog that comes up does not include the "Mobile Device" listed under "My Computer". In my windows explorer I can see it listed. How do I get XDATools to wite it to the device rom directly?
Any help would be appreciated

If I cannot flash the XDA directly using XDAtools, are there some PPC 2002 ROM Executable Updates (At&T 2002) available that will bring my SX56 back to PW10B1?

Try using adaptrom.....
http://wiki.xda-developers.com/wiki/adaptROM
HTH
Stefan

Adaptrom will let me put the Wm2003 update on the phone but the problem is, it will leave the phone as a PW10A1 and not convert it to a PW10B1...I need to convert the ROM back to its original state.. I will try to put the original Image on an SD Card and see if I can boot off that..

ROM Upgrade

Hi,
I have a T-Mobile Pocket PC Phone 2003.
Rom version: 4.01.16 ENG
Rom date: 02/04/04
Radio version: 6.25.02
Protocol version: 324e4
Wallaby Bootloader: V5.22
I am in a GSM 1800Mhz region while the phone has only 900/1900Mhz. I have read various reports that with a Firmware upgrade I can make the phone Tri-Band capable meaning 900/1800/1900Mhz. There have also been reports that this is a hardware feature which will not be effected by software upgradation. But I wanna still try. Firstly the phone was Simlocked by T-Mobile which I managed to unlock with a code given by their SimUnlock dept. believe it or not.
The problems / issues I am facing with this phone are:
1. Downloaded the XDAROM.exe with adaptROM.exe Program A.exe etc in it but it always stops at the dreaded -
ERROR: GetDeviceData - An existing connection was forcibly closed by the remote host.
error getting devicedata
For the above I have tried all the suggestions on this forum like hard booting (battery off/on), Select GSM900 in Wallaby Mode then reset, Remove Sim Card then Reset, Switch off Radio (which I presume is GSM) in Wallaby then reset. All options lead to the same error.
2. Tried backing up the current ROM in Bootloader Mode which it does and asks me to press the Action key. But when I reboot the device or remove the SD Card and plug it into a PC it says Card not formatted. The SD card
works under normal conditions transferring data to and fro and storing data.
3. Read that I can copy the .NB1 (update file) onto a SD card and on rebooting it should ask if I want to Flash the device with this new data but it never asks and reboots completely.
4. Wallaby mode is also supposed to Flash the device via USB if I press the record key I tried but the computer and device never connect.
5. Device does not ActiveSync always on docking very often I may need to reboot the PC and or the Device for them to talk.
6. Tried XDAUnlock. exe which gave me 'error getting unlock code'.
Any ideas people? Any help would be greatly appreciated.
Andrew with no clever lines

In no particular order:
(1) 1800 MHz is a hardware feature. At best, playing with the firmware will make the phone think it can operate at 1800MHz, but it really can't without hardware changes. But hey, you already know that.
(2) When you dump the ROM to an SD card, it is dumped as an image, which overwrites any FAT formatting on the card. This is why you're getting the "Card not formatted" message on the PC. You need special PC software (XDATools -- available on this website, or XDArit) to access the ROM image on the card with the PC.
(3) In order to upgrade the XDA with an SD card, the firmware needs to be placed on the SD card as an image (the same format as #2 above). If you just did a PC file copy you used the wrong method. XDATools also does this function.
(4) Why are you trying to use XDAUnlock.exe when you've already unlocked your phone with the code from T-Mobile?

Hi,
Thanks I did finally realise what every one took for granted in this site that the ROM dumps on the SD were written in a proprietory image format not FAT format.
Am trying the entire exercise coz have read at enough places on the site that the phone can be cracked to be tri-band which is what I need for it to roam India. We have only 900Mhz at select locations and the rest is 1800Mhz. Can only but be hopeful.
The chronology for the unlock bit was off on my mail.
Basically I cant perform any updates to the phone via the adaptROM method because I feel Wallaby 5.22 has protection built into it and shuts down the connection. If I try to Downgrade the Wallaby to V5.15 using the bootloaderfix included XDATools I get the error listed below.
'C:\bootload\pput.exe' is not recognized as an internal or external command,
operable program or batch file.
ERROR: ITReadProcessMemory - Unspecified error
Unable to find flash info offset, cannot disable bootloader writeprotect
If I use XDArit V1.02 route to write via SD I get Failed to open Device \\.\PhysicalDrive7
Anyone got the older version of XDArit ??
Help people.
Thanks,
Andrew

I'm not as familiar with Bootloader version issues. My (old) unit was Version 5.15. I just got a replacement for it after I busted the screen, and the new one is Version 5.22. Maybe I'll learn more about bootloaders...
But LumpiStefan says he hasn't had problems using the SD card method with 5.22. I haven't played with the new phone yet, since it came with WM03.
Wouldn't it be easier for you to spend $100 (or so) on an unlocked 900/1800 phone?