My Exec used to connect to my linksys WAP no probs but since I upgraded the Exec radio to 1.06 it repeatedly tries to connect and then returns to the 'available'
No settings have been changed on the WAP or the Exec so I'm assuming something has broken on 1.06 radio. Also, the Wireless status screen just remains on 'scanning network...'
Is there a thread on here describing where to obtain just the 1.09 radio update? I did a search but as people often add the radio version to their signature I ended up with 697 matches...
Thanks for reading...
neildo.
if u browse thru the ftp server you should seen the radio file your looking for.
it is highly unlikely that an update will degrade performance of your device.
da1 said:
if u browse thru the ftp server you should seen the radio file your looking for.
it is highly unlikely that an update will degrade performance of your device.
Click to expand...
Click to collapse
Thanks. I found the file but trying to upgrade it comes back with the incompatible country error....
I'm downloading the recent complete O2 update file and attempting to extract just the 1.09.00 radio file from it.
Will report the outcome.
neildo.
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.
I upgraded to SER last week. I love the update, but I've had a lot of problems connecting via GPRS. Specifically, I'm now asked for a username and password where I wasn't before. The phone seems to make a connection if I don't enter anything, but can never get to a server. Seems like a problem with nameservers, but I've checked over the settings a couple of time. Is there some way to fix this problem? Has anyone else encountered similar issues? Also, would it be possible to return to my old ATT rom without relocking my phone? Sorry if these questions are pretty basic.
Try the new ppc2003 4.00.05 rom. I have it with attws in the US and it works flawlessly. If you are not leaving ATTWS dont worry about having your sim locked right now. Get a card reader and do everything via sd card flashing. you will not have all the problems you see people having in this forum.
thanks for the advice. which one are you using, with or without radio update?
thanks
valheru said:
Try the new ppc2003 4.00.05 rom. I have it with attws in the US and it works flawlessly. If you are not leaving ATTWS dont worry about having your sim locked right now. Get a card reader and do everything via sd card flashing. you will not have all the problems you see people having in this forum.
Click to expand...
Click to collapse
I use the ATTWS Radio A.20.10 and the T-Mobile WME 2003 4.00.10 and the combination is working well in the Los ANgeles area on the ATTWS network.
It sounds like you tried to setup your network connection the way ATTWS reccomends in WME 2002. This will not work! Forget about the proxy settings, they do not work on WME 2003 (I haven't tested on 4.00.10 but I did test on 4.00.01 and 4.00.05). The proper settings are:
1. Create a new connection
2. Name it whatever you want
3. Slecte Cellular Line (GPRS)
4. Set the access point to "PROXY"
5. select finish, you are done
It should work just fine with always on GPRS.
where can I locate that radio stack?
thanks
barjohn said:
I use the ATTWS Radio A.20.10 and the T-Mobile WME 2003 4.00.10 and the combination is working well in the Los ANgeles area on the ATTWS network.
It sounds like you tried to setup your network connection the way ATTWS reccomends in WME 2002. This will not work! Forget about the proxy settings, they do not work on WME 2003 (I haven't tested on 4.00.10 but I did test on 4.00.01 and 4.00.05). The proper settings are:
1. Create a new connection
2. Name it whatever you want
3. Slecte Cellular Line (GPRS)
4. Set the access point to "PROXY"
5. select finish, you are done
It should work just fine with always on GPRS.
Click to expand...
Click to collapse
That radio stack is part of the current WME2002 release from the Siemens' web site. Download it and install the whole thing, then using the SD card method just update the WIndows CE portion to 4.00.10. If you have already upgraded the Windows CE portion, then you must copy the 4 files (2-RSUPGrade and 2 Monitor_UL_bs) files to the devices \windows directory and execute the RSUpgrade.exe (not the cps). YOu should see several threads on how to do this throughout the ROM Updates Forum.
Do be careful as RSUpgrades are the most dangerous and tricky and we have seen more problems in that area than any other.
I have upgarded long time back my Qtek to T-mobile test only ROM.
ROM version 4.00.21
ROM date 8/11/03
Radio version 4.210.00
protocol version 32S54
it is begomming very slow plus the reception of teh phone is so bad.
am trying to change teh ROM version but the system is giving me this error please help:
ERROR: GetDeviceData - An existing connection was forcibly closed by the remote host.
cannot execute the remote communication program. please make sure that the usb/serial cable is properly connected
Tmobile ROMs can't be flashed through USB .. you have to use SD methode.
This slowness is a known bug in older WM2003 ROMs ... either to use a recent ROM like 4.01.16 or A30.09 .... or to install the fix named "clear_notify.exe" in your \windows\startup directory
Bad signal could be out of the RSU 4.21 ... depends on your network and the device type you can use a better RSU ... but it's a very risky action!!!
I have a sx56 and I recently updated the rom to 2003 via the kitchen. I now would like to update my radio stack. I don't have an active sync cable so i need to do it through my sd card. Is this possible? Can someone tell me the best RS to use. I also need directions on how to go about downloading and installing the new radio stack. Also is there any way to upgrade to 2003se without active sync. My phone info is as follows:
unlocked AT&T sx 56 used on t-mobile
pw10b1
ROM 4.01.16 ENG
Radio version A.33.02
protocal version 1.3.3
thanks
Why do you want to upgrade your RadioStack? If it´s all working, i would stay....
Anyway, on the FTP are some RadioStacks, that are designed to run directly on your device.
# Extract the downloaded ZIP-File and copy all files to the /Windows directory of your device.
# Copy the RSUpgrade.exe additional to the /windows/startup directory.
# Make an soft reset of your device.
Without ActiveSync, there is no possibility to upgrade to WM2003SE....
Stefan
Thanks for the quick reply. I don't get great signal strength on my phone and figured a new radiostack might help. But before I take chances upgrading, will a new radiostack help with signal strength?
It may help, but it must not.
You have to choose one of the 6.xx Radio Stacks.
If the upgrade fails, your phone might end as paper weight. That's the risc you have to handle with....
Stefan
DON'T TRY TO UPGRADE RADIO STACKS!!! DANGEROUS!!!
Guys, don't even think of it. Today I killed my wallaby. I had a radio 6.24.00 and I wasn't glad because of poor signal strength in places where other phones work great. I downloaded from xda ftp a radio stack upgrade soft to a version 6.25. Followed the instructions and started the procedure. On 60% it said do try again. I tryed and second time it stopped the procedure of upgrade at the very beginning. So, my phone doesn't work any more. I dont know what is that soft for if it kills the wallby phones. I wish I didn't do that.
i have failed miserably in the attempt to get wifi working properly on my 8125 with the new IMATE rom flashed.
i downloaded the original cinular rom from the ftp and am going to flash it back. I notice 2 files on the ftp, a zip and an rar, i assume they are both the same .nba file because of size?
I am going to use aWizard to flash it back. I am not sure how the splash image portion should be done, and i want to make sure i do everything right.
Anyone done this yet?
Once i do it i will post my results on the 3 routers i have curently, and my success at logging into them with the wizard with the SAME settings ive been trying with the imate rom.
Anxious for any responses. thanks.
Dan
good luck. I have been using the 2.16.9.1 WWE rom on my cingular 8125 since the day the imate rom was noticed on clubimate's site. I have connected to 2 different access points (Netgear WG302 and a dlink xxx??) The netgear uses WPA TKIP and the dlink does not use any encryption. Both work flawlessly. did you install any original cingular cabs when you were using the I-Mate rom?
Re: To FIX WIFI, Going to reflash cingular ROM & test. O
danrw84 said:
i have failed miserably in the attempt to get wifi working properly on my 8125 with the new IMATE rom flashed.
i downloaded the original cinular rom from the ftp and am going to flash it back. I notice 2 files on the ftp, a zip and an rar, i assume they are both the same .nba file because of size?
I am going to use aWizard to flash it back. I am not sure how the splash image portion should be done, and i want to make sure i do everything right.
Anyone done this yet?
Once i do it i will post my results on the 3 routers i have curently, and my success at logging into them with the wizard with the SAME settings ive been trying with the imate rom.
Anxious for any responses. thanks.
Dan
Click to expand...
Click to collapse
I had same problem after upgrading MDA pro with new iMate rom 1.30
I use d-link DSL-G604T wifi router; can connect to home network but when try to surf the web from ppc it always connect through gprs; no access if phone is off.
Manually enter IP address could solve the issue?
ethorn said:
good luck. I have been using the 2.16.9.1 WWE rom on my cingular 8125 since the day the imate rom was noticed on clubimate's site. I have connected to 2 different access points (Netgear WG302 and a dlink xxx??) The netgear uses WPA TKIP and the dlink does not use any encryption. Both work flawlessly. did you install any original cingular cabs when you were using the I-Mate rom?
Click to expand...
Click to collapse
Same rom for me too. I can detect the routers but cannot connect...
I just ran K-JAM_WWE_216901_2169101_020710_ship.exe, let that instal, and also let the customizations install. Nothing else.
Any ideas?
is it not detecting, not getting an IP, or getting an IP but not getting out?
ethorn said:
is it not detecting, not getting an IP, or getting an IP but not getting out?
Click to expand...
Click to collapse
I have the same problem. In fact I started a thread about it a couple days ago. It connects, but doesn't allow data to pass (I do get IP Addy). I also can't use passthrough on the laptop.
I loaded a very few of the Cingular cabs and actually narrowed it down to one of two that totally killed my WiFi connection. However, if you find the thread I made, I also found a registry entry referring to a preferred connection, and MEdia Net was in there (I'm thinking is the problem, but don't know how to change).
Used aWizard and sucessfuly installed the Cingular ROM i got from the XDA ftp site.
WiFi works like a charm, with the same settings that the unit had with the new IMATE ROM. This is very upsetting!
Anyone have any clue why this is?
Also - since I am not using the IMATE ROM anymore, any way to restore the original boot screens, delete the HTC one, and the IMATE screen and replace it with the Cingular? Reason I ask is i need to exchange this phone within my 30 day return period because the keyboard is loose.
Thanks