I'm new to this forum and it seems like a great resource. I have seen this question answered but the answers are still above my head in terms of complexity. I've got an AT&T branded SX56 running 2002 and an XDA-Developers ROM (I think). It is unlocked, I am guessing through the use of an XDA Developers tool for unlocking. I'm in Colorado and using the phone with T-mobile. My question is this, I'd like to upgrade to 2003 and have downloaded the file to do so from Siemens website for free, which is great. It had some nice enhancements and I thought I'd upgrade to it. So, I downloaded/installed the new ActiveSync v3.71 and then tried to run the upgrade. I got the same message many have gotten apparently saying that the ROM Image is not compatible. The specs are;
current
Model PW10A1
ROM 3.17
English
upgraded
Model PW10B1
ROM A.30
English
In reading through the posts it seems that I need to upgrade the ROM of the device, but I still get lost looking at "cooking a ROM", etc and what exactly I need to do. Making this a little more urgent is the fact that after I tried to upgrade the phone (which gave me the ROM error) my internet connection on the phone (which was working fine) suddenly doesn't work with explorer or outlook on my phone giving me an error "Trouble Connecting; Unable to connect with current settings" even though I didn't change the settings and they look exactly as they did before. So, I feel like I've messed something else up on the phone even though it didn't get to install the whole upgrade.
So, any advice for a novice? Thanks in advance, I appreciate any help you can give.
Best regards,
chefandy
the official AT&T release for WM2003 is an exe file contains both ROM & RSU upgrade, and it aparently designed for PW10B devices (900/1900 MHz).
i think the first part of the faulty upgrade (usually RSU) affected your device ... i really hope not
chech your device info and tell us what's there. if u can still get to the boot loader screen and activesync can still connect to the device, then it's not a severe damage. I think successful RSU upgrade with the right stack would solve it.
I'm not sure what the boot loader screen is, but the device still syncs just fine and seems to be working ok except for the internet connection issue. The funny part is that I can connect to the GPRS connection by going to the connections screen, but then when I transfer to Outlook or Explorer they do not recognize the connection as something they can use.
Is the Siemens upgrade I downloaded (http://www.my-siemens.com/MySiemens...C%2FMC%2FSX56POCKETPCPHONE%2Fdanda%2F,00.html) different from the AT&T upgrade you mention? I also saw there was a T-mobile upgrade to 2003 but it was not available when I tried to download it from tmobile.com. Thanks!
That's great! .. ... It seems I misunderstood your issue ... I thought you lost the RSU part.
I think something wrong happens to the registry values ... you see, there is a reference for each defined connection in the registry which all applications that may require to connect to GPRS or WAP or MMS can refer to.
I suggest that you delet ALL connections and start the setting from scratch ... I can't guarantee it will work since some applications may be required to be uninstalled and reinstalled to use the new connections references (if it has smart uninstaller!!).
The last resort is a hard reset which will bring the registry to the original setup.
Well, I did what you suggested and started with a new connection and it worked :lol: Thanks!
Now I'm back to the original question about whether or not I can safely upgrade to WM2003 or not? Thanks again for all your help.
The answer is YES! ... it's easy to upgrade ur ROM to WM2003 if u know what ur doing.
spend some time reading this forum on how to cook a new ROM from the kitchen ... and it's better to get yourself SD card for flashing and backup.
Related
I have officially screwed up my RSU. I can boot into CE just fine, but there is no radio stack to speak of. After having many partial attempts, there's just nothing there. I've tried everything (or so it seems). I can do an activesync connection, btw.
Whenever I try to run PROGRAMME A, it just hangs. I hit the next button and *nothing* happens. That's any program a, whether from ATT or Tmobile.
Hi there,
Did oyu try installing the Radio Stack Programma A thingy from another windows installation? Another pc? Perhaps that will work.
Os course... you could be trying to install a version which is not suited for your GSM provider/GSM hardware. Look for info at your GSM provider website. It's hard is not impossible for anyone here to tell you which version should work for your device.
Cya,
Oz
Yeah...I tried it on my laptop too. The problem seems to be program b, which rewrites the RSU. It simply won't do it for some reason. This shouldn't be the case.
Come on....someone must have some stupid trick to re-flash the radio stack. I remember seeing solutions to the "1% problem," but all of those solutions were with the non-US radio stacks. :-/ I didn't buy my phone from Tmo, so I have no warrenty to speak of.
which rom and ruu were you using? seems like you were using the .exe correct? which unit/network are you on? this might help you get some help. be specific with the problem, etc.
What versions (ROM and Radio Stack) were you using prior to running the EXE upgrade?
What versions are currently installed?
And which radio stack are you trying to upgrade to?
I was using 4.00.005 and the newest ATTWS ROM before, and I was trying to go to Yorch's newest Tmobile beta, the one that includes the RSU.
Right now I have the most recent official Tmobile ROM and no radio stack on there.
Ejdmoo:
After decompressing the rar file, look for the two RSUpgrade files; one is .cp64 and the other is .exe. Copy them via Activesync to the windows directory on your TMo PPCPE. Then execute the RSUpgrade.exe file. That should reflash the new radio stack. It worked for me. Good luck!
David
I am in the same boat as ejdmoo, and had the same roms installed and all that good stuff...still no go with fixing the radio stack. One thing I noticed is that I removed the .cp64 file from the \windows directory and it still tried to update and failed at 1%. I don't think the version of the .cp64 file matters since it is not getting that far.
Another issue that popped up after the failed update is th unit does not charge, it will only run on AC, and it does not show a status in the power app under settings. Bout you ejdmoo?
Come to think of it, I am having the same power/charge problems. Also, I have tried copying the RSUpgrade.exe program to the device multiple times and from multiple sources. Also, I copied some of the other required files (something map and .c64 file), still didn't work. I think it *must* have to do with the RSUpgrade.exe, but I wouldn't know why.
FYI...I'm going on vacation this week (luckily I have a backup phone), but I expect this to be fixed when I get back! :!:
C:\Program Files\SX56 upgrade utility>adaptrom
ERROR: GetConnectionType - An existing connection was forcibly closed by the remote host.
error getting connectiontype
Click to expand...
Click to collapse
This is what adaptrom returns now, this is when the tmo is connected and browsable via AS. Anyone have any ideas why this would be happening?
Since my unit will be replaced I am willing to do some scary things with it, so if any of the xda-devolopers want me to try something let me know. I have an sd reader/writer and a usb cable but no serial cable.
ejdmoo said:
Come on....someone must have some stupid trick to re-flash the radio stack. I remember seeing solutions to the "1% problem," but all of those solutions were with the non-US radio stacks. :-/ I didn't buy my phone from Tmo, so I have no warranty to speak of.
Click to expand...
Click to collapse
Been there seen that!
Here is hope I fixed it:
First go to the below site and download and install the v4.21 ENG radio stack upgrade. Now here's the tricky part but I must warn you I did all three and really don't know which one did it, might have been a combo of all three.
1. Entered bootloader mode and selected the 900 band and re-booted.
2. Removed the SIM card and rebooted
3. Entered bootloader mode and turned off the radio.
Note you'll know when you got it right because you'll have a stable Active Sync connection. So after each of the above steps see how stable Active Sync is before trying the next step.
Reran the T-Mobile upgrade (PC install) and all went go well.
02 Radio Stack Upgrade v4.21 (1.54MB) Download.
http://www.o2.co.uk/business/productsservices/xda/romupgradedownload/0,,113,00.html
I'm not sure in which order you want me to do what...?
I had the same problem, but a hard reset fixed it for me.
David
For all of you having the same problem I have been having after upgrading to the O2 4.21 RSU here is what I have found makes the loading of the RSUpgrade files into the \windows directory work. You need to also copy the monitor_ul_bs.m0 and monitor_ul_bs.map files to the windows directory. Then when you execute the RSUpgrade.exe it works.
barjohn you are a genius!!! I can't believe I never thought of moving the other files before...you rock I am now in possesion of a fully working WM2003 T-Mobile PPC PE!!!
Thank You barjohn!!
mdavidm said:
I had the same problem, but a hard reset fixed it for me.
David
Click to expand...
Click to collapse
Boy I forgot about doing the hard reset, what step was that?
It must have came right after the Radio stack upgrade, Right!
So it appears that what works for some doesn't work for others, strange business!
I read barjohn's fix were he manually copied some missing files into the windows folder and that solved it for him, I guess we were just lucky! :?
barjohn said:
For all of you having the same problem I have been having after upgrading to the 4.21 RSO2U here is what I have found makes the loading of the RSUpgrade files into the \windows directory work. You need to also copy the monitor_ul_bs.m0 and monitor_ul_bs.map files to the windows directory. Then when you execute the RSUpgrade.exe it works.
Click to expand...
Click to collapse
So it would be save to say that one should just copy the above files into the Windows folder first before starting the initial upgrade and forgo all of the other headaches, agreed!
Qman,
That's a great idea, but then we would miss out on the thrill of thinking we have transformed a great electronic device into a $400 paperweight! What fun is it if everything works out on the first try? Have fun!
David
Well Ive officially made my tmobile ppc a $400 paper weight. I was running the Kitchen rom with ATT radio stack and I attempted to update the RSU to the latest tmobile version to see if it improved the signal meter using the method mentioned here. I copied the files suggested here via activesync to the windows folder on my ppc and ran the exe, the upgrade stopped at 13% and that was it. Unfortunately I dont have a SD reader so Im high and dry until tomorrow. I can access the bootloader and I get the GSM error and thats it.
After alot of *****ing and customer service that did not have a clue that the supplied the SX56 and software. I finally found some intelligent life at Rogers and was provided this link to the Rogers Mobile 2003 upgrade for those Canadians that still need it.
Here is the required link >>>>>
http://downloads.rogers.com/wireless/products/phones/siemens/Siemens_SX56_Software_Upgrade.exe <<<<
ROM Version: 30.07 ENG
ROM Date: 05/04/04
Radio Version: A.33.03
Protocol Version: 1.3.3
Model No.: PW10B1
Additionaly , please find screen shots enclosed to assist you through the install.
<<SX56 PPC 2003 Upgrade.doc>>
Thanks... but a problem
Thanks for this link. I was successfully able to download this update from the site: however.... the software will not update my phone
I am using the phone on rogers, but this phone is one that i purchased that was originall At&T from the USA.
I downloaded a ROM from here, it is a PPC2002 version, with a whole bunch of toys, looks cooked, but not by me. I used this to unlock the radio.
I would like to upgrade to 2003. This image will not load and i dont know whether i should try cooking another one and loading it, or if there is a way to get this one on there. Having an OS endorsed by my carrier is somewhat comforting, but i dont know if this is at all legitimate.
I get the following error after clicking the first NEXT in the upgrade process:
ERROR 012 CHECK ERROR
The rom image that you are trying to upgrade is not compatible with your PPC phone. Please compare the devidce and upgrade information below
Current device info:
MODEL PW10A1
ROM 3.17
Your Upgraded Image Info:
MODEL PW10B1
Rom R.30
Please download the compatible utility and try again.
Perhaps i am out of luck?
Thanks
Ian
Trick
The trick I used to get around this, is start the installer you downloaded, it will create a directory x:\program files\SX56 upgrade utility. Copy all the files from this directory to a safe place, then cancel the installer.
In there there will be a NK.NBF file. Use the XDATool OSImage tool to make a SD card image, then on the XDA hold down the power button and soft reset to then do the install of the new ROM image. Covered elsewhere on this site many times...
After that, copy the RSU*.* and monitor*.* files from the above directory to the devices \windows directory and run RSupgrade.exe to upgrade the radio stack.
Worked for me. :lol:
Meathooks.
Questions
I apologize if this seems like stupid questions but: What is the difference, if any, between PPC 2003 and WM 2003?
I downloaded and installed (or attempted to anyway) the 2003 update from the Siemens website - the one for Rogers users. I, unknowing the problems other have had, attempted to install straight from the .exe file. The radio stack updated sucessfully but the unit hung when attempting to update the ROM. The program asked for a soft-reset and to run the installation program again. When I did this the unit would not power on and my computer didn't recognize that the SX56 was even attached... anyhow, couldn't get anything to work after numerous attempts. The people at Siemens told me to send the unit back to Rogers. I did. Rogers just forwards the unit to Siemens anyway and now I've been without it for 2 weeks. argh.... When i do get the unit back (which I'm starting to think may be never!) i will try again with the recommended use of XDAtools instead of straight from the EXE file. Even though I won't go through that again i'd like to know if anyone else has had this problem and if they have found the reason for it and a way to install straight from the EXE file without any problems.
Thanks,
Sean
Difference
No difference bwn the two, the proper term is Windows Mobile 2003.
Meathooks.
Re: Thanks... but a problem
bimmian said:
Thanks for this link. I was successfully able to download this update from the site: however.... the software will not update my phone
Click to expand...
Click to collapse
No prob for the upgrade, sorry I did not get back to you earlier (out of the loop for a while), but Meathooks is right, this is the way I had to go as well. Worked great and have not found any bugs so far.
I have another XDA as well. THis one i actually bought from Rogers (for $1000) before knowing that these can be had on ebay for $200 - so i got a second one (my ATT phone) when my cat chewed the antenna on my Rogers phone.
The rogers took the update no problem, straight from the EXE file as in the attached WORD document above.
The rom on the rogers phone was R.2???? something before the update.
Why are some of the ROM versions called R.2 or R.3 and some are just called 3.17 or whatnot?
As for my ATT (primary) phone, does anyone recommend using the rogers provided update over using the one i cooked yesterday or visa versa?
Thanks
Ian
Hi!
I got a major problem when i upgrading my Qtek1010 to PPC 2003..
It works really good until the machine goes on suspend or i try to reboot.
I can't get it to restart, it's like the "on button" is broken. If i press soft reset the machine boots up really fine OR if i open and close the sim card holder...
Does anybody have a clue over what's wrong? I have been trying to find the answer on the forum but with no luck...
/Mike
Have you KSE Truefax on your device?
Than this is the problem....
HTH
Stefan
hmm, another error..
Thanks for the help, the phone is working now, except for one thing.. GPRS!!
Vodafone has made som upgrade on GPRS so QTEK want's me to send the phone to service... There should be a way to solve this without sending the phone... Do you have any idea? Maybe it's the radio that needs upgrading?
do you have the right settings for vodaphone where you live ?
often you have to manualy setup such settings in connections after a rom upgrade
you can try search for which settings vodaphone use
I've tested different settings, but i don't think that's the problem. i think that i have to use the right radiostack or something like that to get it to work..
Hey guys,
Newbie here
I have a himalya(XDAII)
Rom Vers. 1.66.00 WWE
Radio 1.10.00
I want 2 know whether i should upgrade to WM5 or not
I mean is it really worth it or not
Can any one help and guide me step by step
[/b]
...
Well the upgrade to WM 5.0 is not so easy and clear (for newbie) as the upgrade for WM2003SE. I mean the additional installations of postinstallfixes,DOCtools,RAMdisk,MMS,etc(all things must be installed separately,while 2003se's ROM is completely prepared). Anyway try the web server made by our King of Himalaya (BL) http://buzzdev.net
it is described there a lot about,or try the discussion board for WM5 especially.
I want to notice you for few recommended steps:
1. what size of RAMdisk do you want to use? (My recommendation is 64/64).
2. flash ROM image patched with current RAMdisk size (Use HimaUpgradeUt_noID)
3. install DOCtools to raise up your Storage space
4. do a hard-reset(for DOCtools)
5. after start-up install PostInstallFixes(shipped in zip with ROM image)
6. install RAMdisk with your preffered size
7. Install MMS
8. beware of installation of old software(some software is not able to run under WM5)
If you will have any question,I can maybe help.
Thanx
wat i really want 2 know is whether upgrading 2 WM5 would be worth the trouble or not.....i mean is the OS really that gr8??
i'm a new user of O2 and dont want 2 fiddle 2 much with my fone coz i might wreck it!!
i'll only do an upgrade if WM5 provides me with some additional utilities otherwise i'm quite happy with WM2003...
...
Well there are 3 major problems with WM5:
-I am still unable to establish ActiveSync connection via USB(you need at least ASv4.0)(I am using BT for connection)
-The camera software is really crap and portation from 2003se is not yet done
-Sometimes there's a problem with phone(call answer,establish,end etc.)
Anything else is really good and better than before. The system is running rock-solid without crashes. The biggest + is that this PPC system is also possible to install(and run)Smartphone applications. Don't be afraid of upgrading. Just beware of bootloader upgrade and you can't wreck it. When the flashing procedure will be unsuccessful,just start the upgrade again and it must working. But read all things carefully about upgrade,what is DOCtools,what is RAMdisk etc. that you can purely understand it.
I've tried it twice and went back to WM2003se twice.
I found it annoying that my camera and record buttons stopped working.
Other than that WM2005 was a nice OS to use.
Pity there isn't a final release for the XDA II.
...
It can't be official for Himalaya,coz the hardware isn't designed for WM5. Especially the memory system(128RAM,32Flash). This new OS has a different memory organisation,that uses Flash for all things including installed software while RAM is used only for running system and apps. Therefore you will need this combination at least:128Flash,64RAM. Himalaya basically offer 128RAM for running(too much)and 32MB as a storage(too low).
...
chazam said:
I've tried it twice and went back to WM2003se twice.
I found it annoying that my camera and record buttons stopped working.
Other than that WM2005 was a nice OS to use.
Pity there isn't a final release for the XDA II.
Click to expand...
Click to collapse
I didn't notice any problem with buttons. It is also working the AEBPlus utility problemless. The flashback know I also. Once tried Magneto,flashed back to 2003se. And again and again and again...coz a lot of problems I've had with the system. Then I've studying buzzdev.net and step-by-step solved problems. Now I have it totally and it's running great.
Hi
I'm running WM2005 at the minute, but want to go back to WM2003SE, as I'm having problems syncing with hardware at work.
Only problem is, since I changed laptops, I can't get my XDA2 to connect with my PC at all! I've tried installing latest ActiveSync 4 from Microsoft site on my home PC (thinking there are fewer things to stop it syncing on the home PC), so that I can go back to WM2003SE.
However, 2 problems:
- 1) still can't make a connection with the PC - don't even have the Code 28 problem anymore (http://support.microsoft.com/kb/264693/en-us) as the system installs a Network Adaptor device driver called "Windows Mobile-based Device"
- 2) once I do connect, unsure of how to go back to WM2003SE - thinking I could simply run the Xda_II_172181_Final.exe ROM file that I downloaded from O2 UK.
If anyone can shed any light, would be greatly appreciated. I'm new to this, so go easy on me!
Would like to be able to continue running with my Vodafone SIM once this is sorted.
Thanks.
...
As I wrote:
>1. I am still unable to connect via USB. I am using Bluetooth. Maybe I need SP2 for WinXP. Don't know. AS4 is using the connection with WM5 little bit differently as 2003se. This connection goes via network connection,not directly. Try this link:
http://www.microsoft.com/windowsmobile/help/activesync/default.mspx
>2. For flashing another ROM image:Just use HimaUpgradeUt_noID.exe with current OS image file nk.nbf to flash. These files you can download at the FTP of this server. The nk.nbf filename is the same for all ROM images,therefore be sure of version. Copy these 2 files to same directory,put your Himalaya to bootloader mode and start the exefile.
Re: ...
TomasNM said:
chazam said:
I've tried it twice and went back to WM2003se twice.
I found it annoying that my camera and record buttons stopped working.
Other than that WM2005 was a nice OS to use.
Pity there isn't a final release for the XDA II.
Click to expand...
Click to collapse
I didn't notice any problem with buttons. It is also working the AEBPlus utility problemless. The flashback know I also. Once tried Magneto,flashed back to 2003se. And again and again and again...coz a lot of problems I've had with the system. Then I've studying buzzdev.net and step-by-step solved problems. Now I have it totally and it's running great.
Click to expand...
Click to collapse
Hmm...
Perhaps i should have a good read of the buzzdev forums and try again.
Other than that I'm going to be due an Upgrade in fecuary so i might just stick with 2003se and get a WM5 sevice when my upgrade comes. 8)
I'm glad i got the XDA II. I was using a P900 but having a pocket PC phoner seems better for me.
...
Well the WM5 system for XDA II will never have an official release. When I was buying my MDA II,I've had two choises(MDA II vs.P900). Some + was for MDA,some for SE. In total that was two equable devices. I bought my Himalaya due the price was a little bit lower. Now the SE-P900 costs in a second hand 200Euro and MDA II 400Euro. MDA II is much better than P900. The hardware and as well the software. Now I know,that it was my good choice to take MDA II instead of P900. Now when it is possible to use UNofficial Magneto is the Himalaya back on the top.
Hi guys I have 2 questions,
1: I have a MDA Compact 2 that has customised firmware by my employer, some application automatically install when its first turned on after a reset , I have just bought a second one as a spare, is there a way of cloning the firmware from the first one to the new spare?
2: is there a way of using the MDA as a Modem on my pc? We have web and talk but wool prefer to get internet via my laptop?
thanks
1. What brand are you in? T-mobile German, Czech? Which one?
2. Flash wm6, there is an easy way of sharing the MDA Compact II internet connection for PC.
its T-Mobile UK, i cant risk going to WM6 becuase of the mod's by my employer, it runs custom software.
If its been modified by extended rom only to install custom software/settings etc then you can just use Total Commander and browse to \Extended_Rom\ then copy all the files out of it. then on the other device, skip the original customization by soft reseting when its says its about to start, then install the list of extracted cabs from the business device.
For a bit more involved, you can take all the extracted files, build them into an image and then flash them to the other device overwriting the tmobile stuff so they'll always be on there.
If you pair the laptop with the phone, it should detect the presence of a bluetooth modem (not on AKU 3+ tho) which you can then use on the laptop as a new connection dialling *99#
Hi thanks for the reply, I have followed the instructions from here,
http://www.htcwiki.com/page/Use+my+MDA+as+a+Modem?t=anon
but I am having a problem, when it says select access point name I do have any to chose, it just says none?
Any ideas
i have tryied ot on none but it dont work
I think its general.t-mobile.uk
but it wont let me type anything in?
hundleton1 said:
but it wont let me type anything in?
Click to expand...
Click to collapse
no it wouldnt, it should contain the list of connections already presence on the device. i dont have an aku2 anymore on mine so i cant check it out in more detail.