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..
Related
Hi,
This probably the most asked question here yet I have one thing thats different to the others from what I have read.
I live in Australia, my 02 XDA ppc isnt sim locked or anything however my issue is related to the o/s I have ppc2002 I wanted to upgrade to 2003 and found a file for download and am unaware if this file is the correct file to download for upgrade to my XDA?
I also know I need a radiostack which will work on my XDa once it has been updated to 2003.
2003 file @ http://cuba.calyx.nl/~jsummers/XDA/PPC2003PE.nb1.zip
Radiostack which will work for me?????
Any help would be appreciated aswell as telling me what are the neccessary files on my PC to use to flash the ppc phone edition via my USB cradle also.
Any other info should be available with my profile.
Regards
A7MAD
Hi,
if ur phone works fine in making/receiveing calls, then all u need is a ROM upgrade. goto the kitchen at www.yorch.net and cook a ROM based on 4.00.05 ENG. select the file to be an exe file. download the file to ur PC and connect the xda to the cradle and make sure it's connected to power. run the exe and follow the instructions.
good luck
Hi,
Thanks Biso007 for all your info/help.
I am currently downloading the file that I 'cooked' as I type this out however one thing I was not sure about was in the string section was I to change the string to 4.00.05 as it was set on 3.16 ...
I did change it and its downloading I assume there should not be any issues.
If there is any concerns or if I did the wrong thing by that please inform me... BTW the file was made into an .exe.
Regards
A7MAD
Hi,
I visited www.yorch.net and 'cooked' my own ROM made it into an exe and have it downloaded right here it's a 4.05.00 rom flash but I have to ask what software can I use to flash the unit with because I do not have an SD card so I am stuck using my PC to do the flash, I have the official backup files for my ppc from 02's site so I am ok I guess if all else fails i will flash back to what I am currently using.
I wanted to flash the rom onto my ppc however what software can I use? I tried Microsofts Sync software I have 3.7 but it doesnt allow me to flash as it gives me an error message.
Message says:
"Your Device Information;
PW10A1:001
3.20
English
Your upgraded image info;
PW10A1:007
3.16
English
Please download the compatible utility and try again"
Any help would seriously be appreciated, but what is the compatible utility?
Regards
A7MAD
unfortunately this is a known issue with some ROMs that can't accept the exe method. you are stuck with the SD card upgrade.
Will adaptrom not work for this?
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.
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...
Hiya Peeps!
Ive seen various posts etc about the XDA and upgrading to WM2003. But whats the best method. Is the Siemens download good and working for this device?
I cant seem to find anything on any of the O2 sites with an "offical" o2 release.
Any guideance from those that know
Thanks!!
upgrading Siemens SX-56 to WM2003
Using the Siemens-provided upgrade program hosed my XDA and I had to send it back to Siemens to have them reflash it.
I was however able to use the OSImageTool program from this Web site to upgrade just the operating system (from my own experience and from what I've read on several sites, it's the radiostack upgrade that screws up the Siemens upgrade program).
I executed Siemens' upgrade program so that it unzipped its files into a new folder, but then I stopped the program and pointed the OSImageTool to that new folder to find the upgrade files.
best of luck -
ts
P.S. whatever you do, be sure to turn off the phone part of the XDA before beginning any kind of ROM upgrade. The first time I upgraded, my phone rang just as the process began and I ended up having to use bootloader and an SD card to get things working again!
I put the WM2003 .nbf file on my SD card and started the bootloader. But being new, what do I do after the bootloader has started? It's on screen showing Wallaby Bootloader V5.22 and at the bottom of the screen is "GSM OK." Now what? :shock: :?: Did I do something wrong?
I put the WM2003 .nbf file on my SD card and started the bootloader. But being new, what do I do after the bootloader has started? It's on screen showing Wallaby Bootloader V5.22 and at the bottom of the screen is "GSM OK." Now what? :shock: :?: Did I do something wrong?
The bootloader V5.22 seems not to recognize the .nbf files on the SD cards. You have to flash your bootloader first to make it 5.15 or 5.17 then use the SD upgrading method for a new ROM.
can i update my xda rom from o2 to win 2003? where do i find such utility?
Point your webbrowser to http://xda.weblink.net/ This is the fabulous ROM Kitchen of Makis and LumpiStefan.
Click on "Windows Mobile 2003" and select which tools you want to include in the ROM and choose a bootscreen.
Build your ROM as an EXE file and download it when ready.
The status is shown on top.
When the EXE is downloaded, remove the SD card and put your XDA in the cradle and run the EXE. Follow the instructions on screen and you have an XDA with Windows Mobile 2003 (WM2003).
Please note:
When upgraded you have to install all your software again and re-enter your Contacts and Calender entries.
Point your webbrowser to http://xda.weblink.net/ This is the fabulous ROM Kitchen of Makis and LumpiStefan.
Click on "Windows Mobile 2003" and select which tools you want to include in the ROM and choose a bootscreen.
Build your ROM as an EXE file and download it when ready.
The status is shown on top.
When the EXE is downloaded, remove the SD card and put your XDA in the cradle and run the EXE. Follow the instructions on screen and you have an XDA with Windows Mobile 2003 (WM2003).
Please note:
When upgraded you have to install all your software again and re-enter your Contacts and Calender entries.
will i be able to unlock
thanks for your help on the rom kitchen? I have a few questions:
1. At the moment I have developers SER in my XDA 1 and it is unlocked, after I upgrade it to TMobile 4.01.16 will it still be unlocked?
2. If it will be locked again on upgrade to WM 2003 what would be the procedure to unlock it over 2003 without a cable?
Thanks
Ghaffar
It will be still unlocked after the upgrade.....
So no problem with this.....
HTH
Stefan
Reverting back to Pocket PC 2002 SER
Thanks for the quick reply. Would it be possible to revert back to SER on Pocket PC 2002 after an upgrade to WM 2003?
Regards,
Ghaffar.
You can always revert to SER 1.2.
But it could be difficult, cause some some roms only allow installing a new ROM via SD-Card.
Try reading a little bit in the forum....
Stefan
It is possible to go back from WM2003.
I have done it the SD way.
First of all download the XDATools from this site.
Use the XDA OS Image tool to make a backup of your current OS.
Then use SD Backup on your XDA to make a backup of your "Working set" of applications and settings.
You now have a complete backup of your XDA.
I used a cardreader to make a Windows Backup of the SD Card.
Remove the SD from the XDA and perform an upgrade with your own cooked ROM from LumpiStefan.
In my case I could not downgrade using the SER1.2 via the cradle. I had to use the SD methode. Fortunately I had my backup of PocketPC2002, so I was able to flash back to my original XDA OS.