Verizon Apache wm6 rom says 'no radio installed' - Networking

I recently put windows mobile 6 on my Wizard, and I told my friend about the ability to do it. He found a wm6 rom somewhere and managed to screw it up. I found a windows mobile 6 rom (somewhere, idk which one) that installed correctly.
Output in the boot process: (not familiar with the apache, no idea what this means)
Code:
h/w 2 r none
m-12
u-4 d 3.50.00 wwe
When I try to use or check the settings on the phone portion of the device, I get "A wireless radio must be attached to use the phone."
I believe this means I need to update my radio. If so, I don't know which piece of software and which version to use or where to find it.
help please!
thanks,
Brewer

Related

USA RSU Fix...help!

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.

Fixing "GSM Error" in Wallaby Bootloader 5.15?

G'day All,
Got an XDA I here that's giving me the "white screen of death" It will start into the Bootloader (5.15) with the Action/Reset/power combo - But comes up with "GSM Error" which I understand means that the Radio Stack has died.
Ironically, this has actually occurred without playing with this unit at all!! (Just normal service!)
Does anyone know of a technique (SD card or otherwise) to restore the Radio Stack and get past this problem?
Cheers!
Andy
I just fixed a unit yesterday that had the same problem.
What I did was keep pressing the record & Contacts buttons until the welcome screen came up after that was completed. (Note this went on for
about 10 min.)
I then connected it to my PC logged on as a Guest via ActiveSync the used ActiveSync Explorer and copied the needed Radio Stack files over in the Windows root folder and ran the RSUpgrade.exe and reinstalled the Radio Stack. Your success rate may very.
Needed Radio Stack files:
RSUpgrade.exe
RSUpgrade.cp64
monitor_ul_bs.map
monitor_ul_bs.m0
FYI not knowing what OS was on the unit I upgraded it first to the AT&T pre-release WM2003 thats available on MPX200.org via the boot loader method and then used the included A.33.01 RS files to reinstall the RS.
BTW the link to the above pre-release can be found on the front page of this forum.
Good luck and HTH
Hi, i've tried extracting the files and i've got:
Orilgsm.005
000setup.999
MONITO~1.002
MONITO~1.003
RSUPGR~1.000
RSUPGR~1.001
RSUPGR~1.004
What can i do to get the four files u suggest?
Ta
MJ
Recovering from a cactus Radio Stack
Thanks for that..
Catch is though that the unit doesn't want to present a "Welcome Screen".. or boot into PPC? Just a white screen with blue strip at the top and the keyboard selector at the bottom right.
ActiveSync won't recognise the unit either...
You mention "Record / Contacts" buttons.. Could you possibly give me more details on this? If I can get the unit talking with ActiveSync again, then all should be fine reloading the Stack.. But it just doesn't seem to boot properly...
Any thoughts greatly appreciated!
Cheers.
Andy
looks like you're extracting em on a filesystem that can only handle 8.3 filenames, like dos etc
try in w95 - xp or on a mac
maltloaf
You need to either extract the hole ROM upgrade file
or run it, once its finished 'unpacking' the files cancel out of it. It should leave everything in place in C:\Program Files\SX56 upgrade utility\english
HTH
i also have the same problem as this.
some people tell me the radio stack can not be fixed.?
i cant see why if u can flash the rom...
if u get this fixed id love to know.
djkus said:
i also have the same problem as this.
some people tell me the radio stack can not be fixed.?
i cant see why if u can flash the rom...
if u get this fixed id love to know.
Click to expand...
Click to collapse
Call it luck, I worked on one a fews weeks ago for days without success!

Upgrading to 2003 / Need help with ROM error

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.

Rogers Canada Mobile 2003 Upgrade (not SE)

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

Trying to upgrade my Artemis (WM6 Official ESN) to TouchFlo or WM6.5

Hi, to everybody:
I have got a HTC P3300 device (Artemis) purchased in Spain in 2006, unlocked, so I've got no problems on that.
It's was updated by me to WM6 Professional (OS CE 5.2.1620, Build 18125.0.4.2) using official ROM for free devices.
ROM Ver.
ROM Ver: 3.13.412.1 ESN
Date: 8/28/2007
Radio ver: 02.94.90
Protocol ver: 4.1.13.44
ExtROM ver: 3.13.412.102
Now I would like to upgrade it to a cooked ROM like Shady's new ones with WM6.5 or another one with TouchFlo but I can't, altough I've tried almost everything. I'm not a newbie and I work like developer so I understand the most I read but now I'm completely lost; let me explain to you.
My laptop has Windows 7 Ultimate (32bit) installed and I know that this OS(and Vista) have problems so I also tried on XP Professional SP2 without success.
I tried to upgrade the device using the exe directly and trough USPL (from this site and others) but nothing works. I always get the same 2 errors; normally when I use USPL I have error 260 (connection) because the device doesn't go to bootloader screen and if I restart the device into bootloader manually, if the update process starts (not always), it reaches less than 5 or 10% returning a 270 error with message "File corrupt".
I read a lots of in this forum and similar ones checking steps one by one, even trying to update/install USB drivers for Vista but nothing works. When I use USPL, screen goes to black and "unkonwn device" plugged in to USB port is detected on the system so I think the problem is the program can't put the device in correct state, but if I activate bootloader by my self "Sync Device" appears in devices manager but I cannot go futher as I said before.
Do I must make a downgraded to original WM5 and start from it (maybe a problem with loader version)or there's anything that I forgot?. If someone knows a link or think that I missed some step, please help me.
Any kind of help would be appreciated so much. Thank you in advanced
Solved!
OK, here I am!.
Finnally I solved the problem. The issue was that I had have to "do a hard reset before" try to update the ROM. I read somewhere that an application locked the device avoiding the ROM upgrade. I just went to settings > system > emtpty memory and since then I was able to upgrade like the posts said .
Best regards
LoKatEs said:
OK, here I am!.
Finnally I solved the problem.
Click to expand...
Click to collapse
6 minutes between your first and second post and u say: finally i solved the prob!
hahaha
good to hear its working again
Can you post a link for the WM 6.5 version, i found two files, but couldn't install
in the rom section u can find a few wm 6.5 versions.
unlock your phone with USPL and then follow the installation instructions of the roms posted
shady313 and babbelut roms are the most current ones based on 6.5
neither of them have touchflo support though but babbelut rom has spb shell, a different kind of touch cube system
mvenneker said:
babbelut rom has spb shell, a different kind of touch cube system
Click to expand...
Click to collapse
which is really awesome!
its a shame i prefer the 6.1 simple style otherwise i would of kept his rom

Categories

Resources