Related
I just tried WM2003 and came back to SER 1.2 without problems - I was told it's not possible without SD card. Am I so lucky?
Funny, I did the very same thing before reading it couldn't / shouldn't be done, makes me think though, what if it had all gone wrong!!!!!!
For those who have tried the WM2003, please advise me whether it's worth my risk (I'm still indecisive) :?
Just tried to upgrade from 1st version of WME2003 to the latest using the upgrade utility, no go. Goes into upgrade mode on PC & PPC, then progress bar screen on PPC goes to white, a few minutes later a error pop-up on PC telling me to reset & run utility again. When I do so same problem. I'm just curious what version on Activesync are you running & on OS on the Desktop
Thanks
erickbryce said:
Just tried to upgrade from 1st version of WME2003 to the latest using the upgrade utility, no go. Goes into upgrade mode on PC & PPC, then progress bar screen on PPC goes to white, a few minutes later a error pop-up on PC telling me to reset & run utility again. When I do so same problem. I'm just curious what version on Activesync are you running & on OS on the Desktop
Thanks
Click to expand...
Click to collapse
Hey Erick,
I had the same problem with the 1st version of WM2003. I was unable to do the upgrade with the utility. It would seem like the version 4.00.01 of WM2003 is far more mature in terms of this sort of functionality. For example, ActiveSync would not connect with the device in standby. This is not the case in the new version of 2003 which goes to show that maybe some processes were not running.
Going by what I experienced with the older WM2003, I did not try an RUU flash to test if the newer version worked, but I won't be surprised if it does. I was running ActiveSync 3.7 with WinXP Pro.
Thanks Sheran. So I guess it's SD card time This is an ActiveSync problem not an OS problem? What do you think? SD card should work right?
The reason I'm suggesting ActiveSync is I am unable to use any ROM utility to flash any ROM version now, which I was able to do before i.e. SERv1.1.
I believe I had the previous version of ActiveSync back then & now ActiveSync freaks-out when I try to use the upgrade utility for any ROM.
erickbryce said:
Thanks Sheran. So I guess it's SD card time This is an ActiveSync problem not an OS problem? What do you think? SD card should work right?
The reason I'm suggesting ActiveSync is I am unable to use any ROM utility to flash any ROM version now, which I was able to do before i.e. SERv1.1.
I believe I had the previous version of ActiveSync back then & now ActiveSync freaks-out when I try to use the upgrade utility for any ROM.
Click to expand...
Click to collapse
I'm thinking this has more to do with the WM2003 1st version (3.04 build 13083) OS rather than your PC OS or even your ActiveSync. I think the reason some people can use the ROM Upgrade Utility is because they are running the newer version of WM2003 (Ver 4.00.01 build 13100) which seems to work well with ActiveSync.
Unfortunately if you install the older version, until I'm told otherwise, the only way to get out of it is to do an SD Card flash.
Thanks again Sheran I tend to use the SD method, wanted to not have to wait for two write processes. Oh well back to the tried and true method, for now 8)
I was running the newer version (build 13100)
Activesync 3.7, Windows XP Proffesional
I did a cooked rom in one of the kitchens using a T-mobile ROM. I don't like the look or feel, don't have a linux machine so cannot use the special edition ROM.
My problem is my backup is corrupt and now I have created a new ROM in the yorch.net kitchen and downloaded Siemens ROM from their site and when I go to install it it says my SX 56 is not connected even though I look at active sync and everything works fine.
What can I do? :?:
You need to slow down and be more descriptive. Yorch does not have ATT's ROM on his site. How did you upgrade? Did you use an .exe or the OSToolset or the SD Card method? Take it one step at a time. How did your backup get corrupted?
I used the T-mobile or yorch's site to cook a new rom, I have been trying to unlock the phone and thought maybe that would give me something that the unlocker would work with.
I upgraded with an .exe
I backed up to an SD Card and when I shutdown my laptop while on the road some security program andjusted the file son the card so now I cannot restore.
I have tried using another ROM from the kitchen and the one from Siemens website upgrade and both times when I try to install I'm told there is no connection to my laptop. But I can see active sync working and saying it's connected.
Just get the 3.02 ROM from the kitchen, use the OSToolset to put it on an SD Card, and install it using the SD Card method. You won't need to have an active connection to your computer then.
Where do I find a kitchen with that rom for the ATT SX56?
I cannot access Jeff's & Yorch's site only has the newer T-Mobile and the PPC2003.
You will not find the Original SX56 ROM by itself. If you want to go back, download the old O2 3.02 ROM, install it, and then run the newest ROM upgrade from ATT.
I can use the O2 rom on a 900/1900 system? excuse me for my ignorance, but I don't want to fry my machine as this is my third one and I really want this one to work, long story.
As long as you don't update the radio stack of your device you are pretty much free to try any ROM you want. However, the intention is NOT to use the O2 ROM for anything other than having an old ROM on your device that the SX56 ROM you download from ATT will recognize as updatable. Hence, you will be able to put back the SX56 2002 ROM. As always, anything you do is at your own risk.
Thanks, I got it working and sombody gave me an image of the XDA developer rom for my unit and now it is unlocked and works great.
Sorry folks but I have already posted this and don't know how to delete the previous post. after I reviewed the previous post I don't think I made myself clear enough. Please accept my apologies. But would appreciate help on this.
I have read the majority of the info on XDAtools on the forum and installed I believe correctly. I currently run on Win98SE. I have installed Jeff summers version of XDA tools. And though I think I understand what I am doing I am not totally convinced. Before I embark on cooking roms and upgrading etc I would like to be able to do the following:
1: Dump my current rom from my device to my PC I can do this using
XDAtools OSImage. But have noticed that I can only appear to dump
this as NB1(windows CE(*.nb1) type files if I try to call this NBF I get
the following errors:
”error opening C:\program files\xdatools\bootloader_v5_15.nb0ea for
reading. the system cannot find the file specified”
”error opening source bootloader from C:\program
files\xdatools\bootloader_v5_15.nb0ea. error opening target device”
Is it possible to dump my ROM to a file called ‘xxxx.NBF’? or must I stick with *.NB1? this is not a problem as long as the NB1 file can be reloaded.
2: When I try to upgrade my ROM by using OSImage tool and selecting
source as:
‘C:\PROGRAM FILES\XDATOOLS\BINARIES\ATT160204.NB1’
Select destination as ‘device memory (via Programme A) ‘
When attempting to load an ‘NB1’ ROM from my PC to my device memory
(via Programme A) I always get the following message:
”Programme A not found - run with --register error opening target device”
I originally ran the ProgrammeA with ‘--register’ when first installed and tried numerous times since. Can someone please help as I am sure it is something simple I am missing. I only want to be able to use XDAtools to dump and restore ROMs.
I have tried searching for a solution but to no avail. Any help appreciated.
Thanks in advance John.
May you tell your current ROM version and device type?
Some ROMs do not accept the EXE or the XDAtools with NBF files upgrading methods. You may have to use the SD card flashing in this case.
Thanks Bis
Thank you Biso007 I am currently running A.30.09.ENG and my device type is an XDA1. But I believe the problem is associated with XDAtools ProgrammeA as it cannot find the specified files. Though I have followed all instructions for definition. There is probably something simple I am missing. You see I only want to be able to use XDAtools to dump and restore Roms without the need for SD/MMC cards.
Thanks John
Try downloading the XDATools from Jeff Summers site, it has all the missing bits, including the required batch file :
http://cuba.calyx.nl/~jsummers/XDA/XDAtools-Jeff.exe
That's from the sticky XDATools thread, probably read through there and you will find most questions answered if you continue to have problems.
Remember though that the SD card method is the preferred option, and if you burn any T-Mobile ROM's the SD card is *required* to reverse that.
Re: Thanks Bis
jdoherty76 said:
Thank you Biso007 I am currently running A.30.09.ENG and my device type is an XDA1. But I believe the problem is associated with XDAtools ProgrammeA as it cannot find the specified files.
Click to expand...
Click to collapse
XDAtools cannot work with WM 2003.
and you no need to backup A.30.09.ENG (ATT USA version WM2003), you can get it from online!
cgigate said:
XDAtools cannot work with WM 2003.
Click to expand...
Click to collapse
is that confirmed ??
Biso007 said:
cgigate said:
XDAtools cannot work with WM 2003.
Click to expand...
Click to collapse
is that confirmed ??
Click to expand...
Click to collapse
Yes, it for sure!
XDAtools only works with Pocket PC 2002 or some test version WM2003.(<4.0.11)
It cannot work with WM2003 official release (AT&T A.30 or T-mobile).
Thats weird, I am positive I used xdatools to program my sd card through reader writer after downloading the official WM2003 upgrade, in fact I must have used that method because I had to seperate out the radio stack and program just the ce rom, I have no other tools to do this.
XDAtools only works with Pocket PC 2002 or some test version WM2003.(<4.0.11)
Click to expand...
Click to collapse
I think you'll find that it only does *not* work with T-Mobile WM2003 ROMs. That's only because they lock up their OS to try and prevent us from changing ROMs. I don't think that's the case with any other manufacturer. I also think it doesn't make any difference whether it's WM2003 or WM2002, it solely depends on whether the manufacturer locks the OS.
Thank you cgigate & ebswift re XDAtools/WM2003
Thank you Cgigate and ebswift maybe this is why I am encountering problems with my download and restore of my ROM. I inadvertently choose a WM2003 AT&T rom to practice with. Maybe I should have chosen a PPC 2002 ROM to test??
I thought I had a problem with XDAtools and that I did not have all the correct links/files in place. Maybe I should dump my ROM and try restoring a PPC2002 and then re try my test. Thanks again guys.
i used xda tools with the AT&T WM2003 rom on my uk o2 xda with no problem. I wanted to keep my old radio stack as it was working fine and just used the os upgrade file, via SD card.
I would recommend updating activesync to 3.7 if you are doing it via the XDA cradle.
maltloaf
Did you use XDAtools to copy direct to device
Thank you Maltloaf, when you upgraded your rom did you use XDAtools directly from PC to device or copy the file onto your SD/MMC card and use the bootloader program to load ?? If so maybe you can answer the problem I am encountering. Thanks john
i have flashed twice (had to go back to 2002 for a short while)
both times using the SD card/bootloader method and I transferred the file onto the card using xdatools in the xda/cradle
Thank you Maltloaf
Thank you Maltloaf this seems to be clearer now, but in the context of upgrading etc XDAtools is only being used to copy the file from source to SD/MMC card. I was under the impression that XDAtools did not require the use of SD/MMC card. But maybe it's a matter of finding out what works for you. John
well xdatools should be able to flash directly to the xda as far as i know but it's always the safest way to do it sdcard style
Thanks to all
My thanks to all you helped with my recent questions. Thanks John
I am trying to test out XDAtools and using the WM2003 AT&T rom but keep encountering problems trying to load my rom via programmeA I have had some help from others (see below) but it seems that XDAtools cannot manipulate WM2003? Can this be confirmed and if so I'll abandon this test.
Thank you Cgigate and ebswift maybe this is why I am encountering problems with my download and restore of my ROM. I inadvertently choose a WM2003 AT&T rom to practice with. Maybe I should have chosen a PPC 2002 ROM to test??
I thought I had a problem with XDAtools and that I did not have all the correct links/files in place. Maybe I should dump my ROM and try restoring a PPC2002 and then re try my test. Thanks again guys.
it worked for me
For your info, I used XDATools and Program A to burn AT&T latest ROM. I then flashed back to XDA Developer's SE ROM in order to unlock my phone. When that was done, I reflashed the AT&T ROM. All without hasle.
Did you use bootloader or ProgrammeA ?
Thanks viERJA when you say flash do you mean copied to the SD/MMC card and used the bootloader to load ??
i had 4.00.05 before and used XDAtools to upgrade to 4.01.00 without problems.
well since if you copy the rom to a sdcard and upgrade the rom using the bootloader then xdatools cant really be incopatible with mw2003 since it's the bootloader which do the updating and xdatools does the same thing to the sdcard if you are updating to 2002 or 2003 to and from 2002 and 2003
Good point Rudegar
Good point Rudegar, therefore XDAtools is not being used in the context of elimination of the SD/MMC method. John
I cooked a WM 2003 SE ROM at Lumpistefan's but have been unable to get the exe file to install it. It keeps telling me about a communication error.
Has anyone had the same problem and found a fix? ActiveSynch appears to be working fine, and I have tried it on 2 PCs already.
Thanks
Found the answer in previous posting
Concernig your problem about Upgrade to WM2003SE. A mentiond 1000 times here in the forum, this causes from the t-mobile ROM installed on your device. You have to downgrade the ROM first to a "normal" ROM (like the Special Edition ROM) via SD-Card, and then you can upgrade via exe file to WM2003SE