Database Users

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

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

You can reflash the RSU on the SX56

OK. This will have to be short and by memory but the good news is the details are all here in the forums. Thanks to everyone for the bits, I just stitched them together after spending hours of experimenting with my useless SX56.
After using the PPC 2003 on my ATT SX56 for a number of months I decided to dump it and go back to the PPC2002 version. I had problems with battery life, ring volumn, reception, dropped calls and some of my application would not work.
I was successful in using the ATT SX56 upgrade on the Siemens site once. I did it a second time because I was unsure if some binaries got loaded (it appears that this image does not have the standard ActiveX controls which I got elsewhere).
During the second install everything went wrong. I was left with a dead PPC with no useful ROMS. Period. All I could get to load was the Wallaby 5.15 bootloader.
So this is what I did. Note only try this as a last resort before sending in your PPC PE to Siemens for a reflash as I was about to do. This may work for other carriers but you will need their versions of the files mentioned here.
ONLY DO THIS IF YOU ARE GOING TO THROW YOUR PPC AWAY
Brain Dead PPC with GSM Error and no ActiveSync
First you will need a SD reader/writer for your PC and and SD card. This first step will give you a somewhat usable ROM for the PPC side. We will deal with the GSM side in a bit.
First get hold of the Siemens PPC 2002 update and install it on your PC. (it will probably fail to your PPC since if you are reading this ActiveSync won't work, if it does you probaly don't need to read this thread)
It will probably hang on the warning screen. If it does just go to the task manager and end it. All you want at this point is the files anyway. They will be installed in Program Files\SX56 Upgrade utility
Get a clean SD card and copy the NK.nbf file from the english subdirectory to the card. Stick the card in your PPC SD slot and get the bootloader running. (soft reset + volumn button). It will load a new ROM into memory after you select the action (rocker switch at bottom of PPC).
After this you can softboot the PPC. It will probably ask to reformat the SD card. Let it do that as you don't need the NK file anymore and you will need a clean SD card.
PPC without Start Icon and no GSM
Now your PPC won't have a start icon and you will also not be able to use the pointer as the PPC will not have performed setup. Don't even try. All you can do is bring up the contacts and calendar to frustrate you.
Next we will get the repair.zip file (search for it in the forums). While it is made for the XDA we will use it only to give us back a functional PPC. Follow the instructions to copy the subdirectory and file to the SD card and reset the machine.
1% Problem
You will now find yourself at the famous 1% problem but you will have a Start icon again, which is a good thing.
Do not acknowledge the error by selecting OK. Let it be there but instead sneak behind and hit the start icon. Bring up the file manager and go to the windows/startup folder. Delete upgrade program. Do a softboot.
Working PDA but no Radio Stack
Now you will have PPC again but it will be slow and you will have no radio stack yet. Now to fix that. Go to your PC in the SX56 upgrade/english directory and copy these four files to the Windows directory on your PPC.
monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.exe, RSUpgrade.cp64.
Once copied leaving your PPC in the charging cradle run RSUpgrade.exe from the PPC windows directory. It should upgrade all your ROMS and you should be back in business.
The only file I could not update was the rilgsm.dll. It was locked and would not let me mess with it or copy another on top of it. Perhaps another attempt at the upgrade program would fix this but I am gun shy right now and I have a working system again.
Chris

Dear Chris,
THanks for your clearly poitining out steps to fix the phone. Can you please help me where to download the repair.zip. or drop my email: [email protected].
Thanks!
hoanghon

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)

Problems!!

If i want to upgrade my wallaby i get an error message in the communications procedure. I have downloaded my ROM from lumpy's kitchen and ive tried to upgrade it many times right now.
Can anyone give me an advise how i could hardflash the ROM of my device?

I think you get an communication error when trying to flash via ActiveSync.
You have to flash via bootloader....
http://wiki.xda-developers.com/index.php?pagename=Wallaby
Here you get furthe rinformation about how to do it....
HTH
Stefan

Nothing yet
Ive tried to Bootload te rom, but after the message "connect your USB now" the device does not react anymore.
I have tried to run the application rom but this says that active sync does not recognize a device.
What should i do next?
Thanks for the quick respond!!

Even if i make a bacup to SD this doesnt work. There no explaination how to hard flash the device! Can you give me an advise???

What have you done exatcly, and where is the problem?
It's not really clear for me.
For Flashing via SD-Card there is no USB connection necessary....
STefan

I have tried to flash with the bootloader. When i push on the on/off putton and do soft reset i see the question "connect to USB now". If i connect and i start the rom nothing happens.
Afterwards i have tried to put the rom on my SD card. I have tried to do this OSimagetools. The pc does recognize the SD card in my wallaby. I also dont have a cardreader.
Is there a way to flash my wallaby in the bootloader-mode with the USB connection?
What do i have to do for it?
Thanks

Strange.
You should see device displays a background that consists of four equally sized vertical bars, colored (from top to bottom) white, red, green and blue. On top of this, it says:
WALLABY
Bootloader
V5.14
WAIT
After a few seconds, the WAIT is replaced by GSM OK. Both messages are in the blue bar, but have a white background.
What do you get?
What is labeld on your rear sticker of the device? (modell) ?
Stefan

Its model: PW10A1
SN: HT220cc15300
PN: 99HJ00007-00
Step 1)I have seen the horizontal bars. And its version 5.18. Ive also seen the "GSM OK"- notification.
Step1a)If i connect it afterwards to my USB nothing happens. The computer does not recognize the Wallaby.
Step2) If i hold the On/Off button i get the message "Connect to USB now" If i do this, activesync does recognize my device and i cannot install the ROM.
Step3) after step 1 i press the contacts button and i see 6 ways to backup my rom or GSM. I have backedup my GSM and ROM to SD. But this has no use for me.
Greetz,

Ok. Now I see.....
First of all, you have an totaly unknown Bootloader (5.18) to me, so i hope all steps will work....
You require a SD-Card with >= 64 MB
XDATools ftp://[email protected]/Wallaby/Tools/XDATools.zip
Your downloaded ROM from my kitchen
step1) Boot your XDA up normal and connect via active sync (guest partnership is ok)
step2) Copy all your data of your sd-Card to your local PC otherwise all data on it will be gone
step3) Enter bootloader of your device by pressing On/Off and doing a softreset
step4) After the Message GSM OK press the Contact Button of your device
step5) Navigate with the pad to "CE+BOOT TO SD"
step6) Confirm this with the Action Key (Press the middle of the Navigate-Pad)
step7) After finishing enter again bootloader by holding On/Off and doing a soft reset
step8) Bootloader should tell you something tah OS is detected on your SD-Card
If No -> Problem
If Yes -> continue
step9) Boot your XDA up normal and connect via active sync (guest partnership is ok)
step10) Install XDATools on your PC
step11) in a dos -box (cmd) go to the directoy where osimagetool is located
step12) enter command: "osimagetool -r xdasdslot -w original.nbf"
step13) enter command: "osimagetool --register"
step14) extract the downloaded ROM using winzip
step15) Run osimagetool
step16) Select the nbf-file in the english-folder of the extracted lROM as source and XDASlot as destination
step17) After finishing enter again bootloader by holding On/Off and doing a soft reset
step18) Bootloader should tell you something tah OS is detected on your SD-Card
step19) Press Action Key to install the ROM
step20) After finishing do a hard reset
step21) Now your ROM should be installed on your device.
step22) Locate the created file original.nbf and compress it using winzip
step23) Upload the compressed file to ftp://xdaupload:[email protected]/Wallaby/Uploads
step24) Enjoy your new ROM
That should be alll .....
;-)
HTH
Stefan

Thanks, But when i extract the rom to a folder, OS Imagetools cannot find the nbf-file. There is no nbf-file in the extracter-rom-folder. I can only find an nb-file.
There is a file called "NK" which says that its an NBF-file(properties). The file is 32MB large. I have tried to select this file (step 16), but the file is not being recognized. Even if i change the extension of the filename. The OSimage does not support this file.
I Have tried this with 3 ROM's : 2003 SE, 2003 and 2002 neither of them contain the nbf-file in the english folder.
Do you have an advice? I think i am very close right now!!
Thanks,

I have sucseeded to install 2002, but 2003 SE wont be recognized. It says its an usupported file.
Has this anyting to do with the fact that i renamed the file? If so can you tell me how to change the file back??
I have downgraded my wallaby to PPC 2002 right now.
Thanks Lumpi!!

WM2003SE couls only be installed via Exe-File. It can not be flashed with the osimagetool.
Stefan