hi,
i have a t-mobile mda.i tried to upgrade the software using the file
4.00.10 - official-tmo2003.rar.
it crashed after 10% of work.i disconnected the device as the message said,but i lost the radio section completely(no version)
when i enter the bootloader(v. 5.15) it saysGSM ERROR,
please tell me what can i do!
looking forward to hearing from you,
best regards,
dominik
i'd like to add that the activesync doesn't recognise my device.please help!!!
I suggest you start over by reflashing your ROM with the SD card method
then rerun the Radio stack upgrade from the device.
Take a look at the below thread:
http://xda-developers.com/forum/viewtopic.php?t=2057
BTW the SD card method is our recommended method
for ROM updates/upgrades so please tell your
family & friends!
Updating your Qtek ROM using the 'SD Card' or 'Bootloader' Method
http://xda-developers.com/forum/viewtopic.php?t=1717
HTH
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
any one?...my $300.00 paper weight needs help
is there anything i can do with wallaby bootloader....i dont have anything else.................
JUICEe said:
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
Click to expand...
Click to collapse
Can you please explain how you did/started the upgrade?
Yes, $300.00 paper weight !
you could get it fixed (hardwire repair)
Qman said:
JUICEe said:
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
Click to expand...
Click to collapse
Can you please explain how you did/started the upgrade?
Click to expand...
Click to collapse
copied the files ( monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.cp64, RSUpgrade) to windows dir, executed the rsu upgrade...uprgade started....2%....10%....16%...16%....16%....so i reset it, an thats where Im @
(i had the I had it cradled, connected to usb & power during it all)
Yeah, that's exactly what I did. I noticed you did a hard reset, which is also what I did. That may have been the death blow.
First of all, do not do ANYTHING in the Wallaby bootloader. If you start messing around in there, you're done.
Plug your phone into the power cord (even though the battery won't charge now, the phone will stay powered if you keep it plugged in).
Try to get the RSU files for the version you initially upgraded from (6.18 for the default T-mobile, or maybe 4.21 like I had from a 4.00.05 ROM upgrade package). Load those files into the Windows directory and then try running them.
Just FYI, I did a hard reboot and changed ROMs several times. I also messed with all kinds of GSM settings in the bootloader. In the end, my phone was toast. Unrecoverable. Fortunately, I got mine from T-mobile and they did an exchange. With my new phone, I'm just gonna wait for the official RSU before I try changing it
ok...too late about the Wallaby thing, that was the 1st thing i was messin with, wen i first loadit it it said "wait" 4 a looooong time, then finally said "gsm error"....but i started playin with it, an tried every option on there, but nothing happened @ all.
2nd: i cant load any thing into windows, because the xda never boots up, just sits @ the 1st screen
so i figured im gona have to get a usb r/w and a SD card :shock:
should i use XDArit.exe or XDAtools.exe
im i gona have problems, i think i have Wallaby 5.17 :idea:
JUICEe said:
Qman said:
JUICEe said:
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
Click to expand...
Click to collapse
Can you please explain how you did/started the upgrade?
Click to expand...
Click to collapse
copied the files ( monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.cp64, RSUpgrade) to windows dir, executed the rsu upgrade...uprgade started....2%....10%....16%...16%....16%....so i reset it, an thats where I'm @
(i had the I had it cradled, connected to usb & power during it all)
Click to expand...
Click to collapse
Ok you're still in good shape just try re-copying the files over and run RSUpgrade again, but what ever you do don't install the 4.21 Radio stack upgrade!
BTW I never upgrade my radio stack while my device is connected to my PC, I always disconnect and use the AC adapter.
HTH
Qman said:
JUICEe said:
Qman said:
JUICEe said:
:? i just tried to upgrade to radiostack 6.24 ... AND WHILE UPGRADING IT STOPPED @ 16%, AND NOW IT W LOAD UP AT ALL AFTER A SOFT & HARD RESET...what em i posed to do??? :!:
Click to expand...
Click to collapse
Can you please explain how you did/started the upgrade?
Click to expand...
Click to collapse
copied the files ( monitor_ul_bs.m0, monitor_ul_bs.map, RSUpgrade.cp64, RSUpgrade) to windows dir, executed the rsu upgrade...uprgade started....2%....10%....16%...16%....16%....so i reset it, an thats where I'm @
(i had the I had it cradled, connected to usb & power during it all)
Click to expand...
Click to collapse
Ok you're still in good shape just try re-copying the files over and run RSUpgrade again, but what ever you do don't install the 4.21 Radio stack upgrade!
BTW I never upgrade my radio stack while my device is connected to my PC, I always disconnect and use the AC adapter.
HTH
Click to expand...
Click to collapse
I figured that having it connected to usb was a bad idea, i just wasn't thinkn :roll: ...but how am i supposed to copy the files when i cant load up the XDA, and even when trying to connect to active sync, while the XDA is sittin, froze, on the boot screen- active sync doesnt recognize :|
Qman said:
BTW I never upgrade my radio stack while my device is connected to my PC, I always disconnect and use the AC adapter.
HTH
Click to expand...
Click to collapse
What ? I'm surprise!
JUICEe said:
I figured that having it connected to usb was a bad idea, i just wasn't thinking :roll: ...but how am i supposed to copy the files when i cant load up the XDA, and even when trying to connect to active sync, while the XDA is sitting, froze, on the boot screen- active sync doesn't recognize :|
Click to expand...
Click to collapse
At this point I suggest that if you have an PC card SD card reader reload
the OS and start over with the radio stack upgrade using the same upgrade method but this time upgrade to the AT&T radio stack because
its less likely to fail than the T-Mobile stack.
Also after the OS reload you would have to copy the needed radio stack files from your PC to your SD card then move them to your devices Windows folder.
BTW what radio stack were you upgrading from?
HTH
...AT&T radio stack because
its less likely to fail than the T-Mobile stack.
Also after the OS reload you would have to copy the needed radio stack files from your PC to your SD card then move them to your devices Windows folder.
BTW what radio stack were you upgrading from?
HTH[/quote]
IM NOT SURE BUT I THINK IT WAS 6.18
WILL THE ATT STACK WORK WELL ON MY T-MOBILE SERIVICE?
AND IM CONFUSED ABOUT HAVIN 2 HAVE TO COPY FILES TO THE SD THEN TO THE XDA...1ST, BECAUSE I NEVER USED AN SD W/R OR ANY OF THE SOFTWARE NEEDED TO USE IT, AND IF I RELOAD THE OS, CANT I JUST BOOT UP AND COPY THE STACK FILES THRU ACTIVE SYNC? OR WILL THE DEVICE STILL NOT BOOT UP ??
BTW:THANX :!:
JUICEe said:
...AT&T radio stack because
its less likely to fail than the T-Mobile stack.
Also after the OS reload you would have to copy the needed radio stack files from your PC to your SD card then move them to your devices Windows folder.
BTW what radio stack were you upgrading from?
HTH
Click to expand...
Click to collapse
I'M NOT SURE BUT I THINK IT WAS 6.18
WILL THE ATT STACK WORK WELL ON MY T-MOBILE SERVICE?
AND I'M CONFUSED ABOUT HAVING 2 HAVE TO COPY FILES TO THE SD THEN TO THE XDA...1ST, BECAUSE I NEVER USED AN SD W/R OR ANY OF THE SOFTWARE NEEDED TO USE IT, AND IF I RELOAD THE OS, CANT I JUST BOOT UP AND COPY THE STACK FILES THRU ACTIVE SYNC? OR WILL THE DEVICE STILL NOT BOOT UP ??
BTW:THANX :!:[/quote]
Yes the AT&T radio stack will work on your T-Mobile and its the one I use and recommend.
As far as reloading your OS from the SD card its what we call the SD card boot loader method and is by far the best way to upgrade your OS. Do a search on this forum for more info.
Yes your device will boot but since your radio is blown Activesync most likely wouldn't connect.
HTH
ok, thanks again...i guess im off to buy the reader/writer, and the card, from walmart, or radio shack whichever is cheaper...( DO I NEED A 64MB CARD, OR CAN I GET A 32MB?)
I'll repost after halloween, since i gota go to sum partys an release all my xda induced stress with good old friend beer
btw, lol, my girlfrien seen my xda while i was tryin to repeadidly boot it up, & as it was froozen on the boot screen, i have "rom is cooking" bootimage, an she was all " i guess u did fry ur phone" :shock: :twisted:
....so with XDAtools OSImagetool, will i be able to copy the r stack?
is the target x:\windows\
that easy?...god i hope :?
Yes you'll need at least a 64MB SD card.
BTW Fry's had one on sale earlier this week for $22.00.
HTH
re radio stack upgrade
I've been following this thread re radio stack upgrade to TMO. I have RS6.18.00 currently and see 6.24.00 at yorch.net's web site under upgrades. Questions:
1. Do you copy the 4 upgrade files to the /windows folder on the PDA to run the upgrade?
2. My phone is working fine with ROM4.00.21 and RS6.18.00, should I upgrade my radio stack to 6.24 or wait another month or two for TMO's offical build?
Kind of nervous given the threads I've read. btw, I bought a SD card reader/writer & flashed ROM via bootloader/XDATools method. Worked well.
Craig
Re: re radio stack upgrade
cshields1 said:
I've been following this thread re radio stack upgrade to TMO. I have RS6.18.00 currently and see 6.24.00 at yorch.net's web site under upgrades. Questions:
1. Do you copy the 4 upgrade files to the /windows folder on the PDA to run the upgrade?
2. My phone is working fine with ROM4.00.21 and RS6.18.00, should I upgrade my radio stack to 6.24 or wait another month or two for TMO's official build?
Kind of nervous given the threads I've read. btw, I bought a SD card reader/writer & flashed ROM via boot loader/XDA Tools method. Worked well.
Craig
Click to expand...
Click to collapse
I suggest upgrading to the AT&T Radio Stack first it has a higher upgrade success rate IMHO or just wait on the official T-Mobile lease.
As fas as how do you copy the files over, you can use Activesync Explorer or use your PC's SD card reader to copy them to your SD card then copy them from there.
HTH
back & hungover...
so i got me a sd reader & the card.....copyed 4.00.16 to it (b4 had 4.00.05 i think) loaded it via wallaby, everything looked fine (except my battery was practically dead, i had to race to get it off the charger reset and put it back on the charger) so the os was copyed fine, and wallaby told me to cold reset (that did mean a "hard", no?)...so i hard reset it, then after a few mins i stuck the pin bak in the lil ass hole, and nothing happened :evil: so i put it bak on the charger, an the boot screen appeared, with a new image and on bottom of screen it sed 4.00.16 ..........but then it just sat there, like b4 and wut i noticed, that i didnt mention b4, is wen its booting up, 1st shows the "4.00.16" then sits there for like 2 minutes, then pops up a "G" & "R" above the "4.00.16" respctivly.....
and i left the device on charger 4 a while, and tried to hard reset again and still wont boot after 2nd pin push :?: :?: :?:
and another thing i didnt mention b4, wen loadin wallaby, it sez gsm error, or did i mention that
i had an idea, maybe to install an older os 3.xx.xx??? but it seams the problem is the gsm wont load, or isnt ther, or damaged, i dont know, how can i load a working GSM on it :shock:
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
Hi after successfully upgrading my rom to wm2003 thanks to yorch.net i am having trouble with reception on the phone so i thought i would try a different rom but ' now i am getting an error message connection forcibly closed by remote host. Any help would be gratefully appreciated
Thanks Derek :?:
may you give more details ... like your device type (A or B), what ROM did you use for upgrade ... how did you upgrade (SD or EXE) ... etc so any one here can advice
It is an XDA 1 running
Rom Version4.00.10 ENG
Radio Version 4.01
Protocol Version 324e2
thanks
I used xdatools to load rom file and upgraded to rom via the usb cradle.. the rom file i used was made in yorch's kitchen.
version 4.00.05ppc2003 with xda config data
any help would be great
thanks
It's normal to get this message with TMO 4.00.10 and 4.00.16 if you tried to use XDAtools or EXE. You have to use the SD flashing method
Ok thanks for your help will try this when i get sd card
Derek
This has probably been answered before, but, I can't get my SX-56 to upgrade to WM2003SE. I get a communication error everytime.
"ERROR: GetDeviceData - An existing connection was forcibly closed by the remote host.
error getting devicedata"
Please help.
Other info follows:
Radio Stack: A.33.02
Protocol: 1.3.3
Hardware Version: PW10B1
Again, any help would be appreciated.
As mentioned 1000 times here in the forum:
Update from this ROM Version via EXE-File is not possible You have to downgrade first via SD-Card to another ROM Version (e.g. 3.17.03)
Stefan
So sorry. I saw a couple of references that I THINK said that, but I wasn't for sure. That really sucks because my Wallaby ruined my SD card, so I have to buy a new one before I can reflash. Why is it that if you have that build you can only reflash the ROM via SD? Or is that in here 1000 times also?
viper498 said:
That really sucks because my Wallaby ruined my SD card, so I have to buy a new one before I can reflash.
Click to expand...
Click to collapse
Why this? How has it happened? First time i ever heard,t hat a card is getting destroyed by the wallaby. Have you tried reformating the card?
viper498 said:
Why is it that if you have that build you can only reflash the ROM via SD?
Click to expand...
Click to collapse
It´s a limitation directly in the ROM. As much as i know in the moment it wasn´t further investigated how they realized this "option"
Stefan