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-Developer DOES not work, why?

I have a SX56 and the carrier is AT&T USA. The following is the device information:
Rom Version: A.20.17 ENG
Radio Version: A.20.10
I needed to unlock this phone so I could switch carriers to T-Mobile, the rest is a waste of time, the following is what I have expereinced:
1- I read about a dozen articles in the forum with different problems, so that I get the hang of things before even I proceeded with anything
2- I then read the material under XDA-developer and downloaded two files:
-- XDAunlock.exe which does not expand, the error message from XP pro is as follows:XDAunlock.exe is not a valid win32 application!
-- XDA-developers-SER-v12.exe; I executed this file, it established a connection through my USB cradle and proceeded to upload the new image.....!!!!
This is where things are stock; the message on the screen is Loading while the commiunications has stopped. So here is what I did:
1- Back to the forum and found a document on the similar problem, I tried the Softreset+On button and I do get GSM ok an Versin 5.15, My screen is distorted with line going through it, just like the article that I found
2- Downloaded XDAtools-jeff.exe to see how I can rebuild this bootloader on the SX56, epanded the contents and run:
pnewbootloader.exe bl515.nb0 in a dos window, the window is non-responsive.
Bottom-line: The Sx56 has lost communications with the PC, its screen is frozen while updating and is totaly distorted. Is there help avaiable on this site is with instruction that I could follow if any!!!
Where do I go from here? Please help.
Thanks

Xdaunlock is a pocket pc app and does not run on the desktop, it should have been copied to your xda and executed from there using explorer to find it then double tap. There is nothing wrong with your bootloader so the bootloader patch does not apply to you. You need an sd card and sd reader writer, you then need to use xdatools to write a rom to the sd card, once you have done this you need only put the sd card in the xda, push the stylus in reset hole while holding power, you will be asked to press action key to program rom, you will then have a working xda.

If I'm understanding you correctly, then the reason the not valid win32 app. is because you need to install this to the phone by copying to the device. It cannot run from the desktop computer.
Also as far as the bootloader part, I'm not well versed in the bootloader but in my experience whenever I've updated my sx-56 to a new rom I've had limited success with the computer run updates. I suggest you get a secure digital card reader and search this board for the step by step instructions on how to use xdatools.jeff to copy the new rom to the sd card and then enter the wallaby boot loader to update directly from the sd card not from the computer. I hope this helps a little.
Mike

ROMs and getting it onto the PPC

OK I have the tmo PPC its already got 2003 on it and I know the loader is 5.15, other info that might be needed.
ROM 4.01.16 ENG
Radio 6.25.02
OK I want to get my own cooked ROM onto this, I know I know use the SD card method, well I don't have one and after getting this thing can't get one for a while either. I have the cradle that it comes with and have put software into etc, I have tried some unlock ROM software to find it didn't work etc etc. after cooking ROM and running it it tells me in a DOS window:
Error getconntiontype - An Existing connecitonwas forcibly closed by the remote host.
error getting connectiontype
so basicly I need to find a way to get this into my PPC via activesync or something. sorry for bad post a little tired but I think people will understand and be able to help me or tell me I need SD card and wait until I get one.

I think you can use xdatools to flash the rom direct from xda memory, choose the nbf file as source then choose the xda device memory as destination from the drop down box in destination section.

OK tried that but can't access the PPC with xdatools so that won't work. thats for trying though.

TMO ROMs are known to resist exe flashing ... use the SD method and you are lucky to have the boo loader 5.15

Well glad to know that my boot loader is a good one, now to find a SD card I can borrow to do this with, should I use a 32 or 64 or does it really matter as long as it holds the file.

64 megabytes is needed really, I have had a problem with 32 meg, it looks like it is programmed but when i flash it there is always a problem.

macgyver33 talked about having a 2003 version. Can anyone tell me where to get it? I mean european one (900-1800 MHz). Or at least the PDA part of it? And yet haven't found quiet an exact explanation of "SD method" - any suggestions? Thanx a lot!

Bootloader v.5.17 locked
BL v.5.17 + TMO ROM. I am not able to downgrade the bootloader or change ROM.
I've tried using:
Cooked ROM.EXE - No way
(Error: GetConnectionType - An existing connection was forcibly closed by the remote host. Error getting connectiontype)
XDA OS Image Tool - No way
(Error: Same as above)
ITSTools - pnewbootloader - No way
(Error: Unable to find flash info offset, cannot disable bootloader writeprotect)
SD Method - No way
In bootloader mode (soft-reset while pressing on/off button), I have no options: Even with an SD card with OS image inside, there's no way to start ROM download as there is no option to choose...
Any idea?
Thx

Check this thread

Thanks Biso007.
No way. My XDA doesn't load the bootloader in a proper way:
1. Inserted th SD card in his slot
2. Answered "No" to format the card
3. Soft-reset while pressing on/off button (so to enter in bootloader mode)
4. Display turns off
5. No Wallaby Bootloader screen, so no action to take...
6. Wait... Nothing.
7. I've also tried to press the "Action" button so to start the SD downloading... Nothing
8. Wait... Nothing.
6. It needs another soft-reset to exit this state (a not working bootloader mode, I suppose)
7. It turns on "normally".
Any further idea? :-(
Thanks

if I'm not wrong, I couldn't see that you ran the 5.17 patch first ... without it your device will never detect the SD file ... chech the thread again

Stuck on bootloader menu after error upgrading ROM

Help,
Is there a way to get the OS and boot img for my o2 XDA to put on my SD card so i can recover it?
I'm stuck on the boot-loader screen (version 5.22) i can not use active sync as it comes up as unrecognized device, im at my wits end, i just want to get my phone working again. is there any place i can get the O2 ROM file from? or anything that can be done, or do i have a useless brick now?
i tried upgrading with the developers ROM using the auto install, it got to the "it will take 5 mins to upgrade" screen then active sync lost connection, there was nothing showing in the progress bar, when i tried to restart, active sync could not connect. now im stuck with the boot-loader menu after a soft reset.

Sorry for the double post,
Right sorted the problem out, got a cooked ROM from a different site as no link i clicked on here was still active.
I found out that if you Format the SD card to Fat32 when in bootloader it doesn't recognize the ROM, so a format to just FAT under windows XP sorted it out, and now I'm back up and running again, though now i cant get my phone unlocked to Vodafone as the XDAunlock returns "error getting code" message. here are my Device info
Rom version 3.17.03
Radio version 4.21.X1
Protcal version 32S54

problem resolved by updating the Radio stack to 6.24 (placing the files onto the device and upgrading from there) once that had done, i had no signal, so downgraded it back to 4.21 and now I'm fully functional

Where did you get the ROM?
I have a similar problem with an XDA which failed whilst being flashed via active sync and now will not start apart from via bootloader. Where did you get the ROM that you mention please?
Thanks
Geezer

use this ROM from http://www.romkitchen.de/ choose one that u will use to cook, PC2002 or WM2003/SE, (WM2003SE cannot use SD Card, only can use activesyn) then downgrade bootloader from v5.22 to v5.15,
using MMC (flash SD) continue to special rom 1.2, 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
for the complete, read this web :
http://www.romkitchen.de/
http://www.romkitchen.de/tools/
http://www.romkitchen.de/tools/manual_unlock.htm
*read careffuly and try it, you can read my post, almost similiar problem but i can solve it by read one by one,hehehhe.. never give-up, ok ^_^V

any help with magician rom?

OK I found this thread and this is what I need to do but I don't follow any of this. what is the ROm image and how do I cook? I'm totally lost and My phone is wrecked or bricked as you say???