Ok, I spent quite a bit of time figuring out the Wallaby upgrade from 4.01.16 (IIRC) to the Developer's Special 1.2. Unlock was easy. Everything done pretty much per the Wallaby_HT_Unlock2 page, and it worked pretty well once I figured out the basics.
I upgraded the radio stack, but, like a big dummy, I used the wrong stack. I used a 4.21 instead of 6.24.00 that should be used. :shock: :roll:
I figured this out after fiddling with it for a while, I noticed that the phone app wouldn't open. Then I noticed that it wouldn't create a partnership via A/S 3.7.1 (4034)
I am pretty confident that I can re-flash the stack, but I can't seem to get to it via A/S.
I have: rebooted PC, hard and soft reset Wallaby, removed HTC from Device Mgr in PC and let it reinstall.
Any help on how to reestablish ActiveSync would be greatly appreciated.
Thanks in Advance,
gg86
.
.
.
Disregard.
Not really sure what happened. It managed to set up as Guest on ActiveSync finally.
I did notice that my trackball had come unplugged. I wonder if there was some sort of conflct there. I dunno.
Thanks anyway, and this is a VERY useful forum.
.
.
.
did you read the instructions and save your origianal radio??
or just try again?
Try this for fixing your bootloader....
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
Stefan
I have the original stuff backed up, but once it mysteriously decided to connect with Active Sync again, all is well, so I don't need the backup even though I have it.
I was able to fix the radio stack by normal means.
Thanks a bunch for the help, folks.
I am Unlocked, updated, and making calls on Cingular network with a T-Mobile Wallaby.
.
.
.
Related
I have made strides today, I can now connect via activesync and browse my device, however when I get to bootloader, I still get GSM Fails...
I came across some documentation that talks about autorunning to load the radio stack, but it looks like those are german/non-usa radio stacks and they don't seem to work for me...
My device is functional (albeit running really slow) as a pda, but the phone portion is still completely hosed...
Can anybody recommend some next steps??? I have tried to download the CE from another machine and that doesn't work and of course the XDARite still doesn't work for me (if I knew I could just get somebody to xdarite to my card, I would do that, but I am not convinced that will fix my problems)...
Any comments???
(a "looking brighter") OMT
Your GSM is toasted
Dear Tod,
I'm afraid your GSM is toasted. Did you try using the repair.zip procedures in this forum. The other thing I'm afraid is that you are not able to find any US Radio stack from T-Mobile on the internet. You must have the correct RSU...CAB files of the old version before you upgrade than maybe you are be able to repair your GSM Error...
I tried the repair....
but the load fails and I presume that is due to a non-us or a non-tmobile rsu cab is being used....
Anybody else think of anything...
Todd
If you're on T-Mobile's network, since now you can ActiveSync, you may want to load T-Mobile's upgrade, (from their web) and run the whole thing through. That should upgrade your radio stack back to a GSM1900 version, and downgrade your ROM to the old version. If that doesn't work, your GSM hardware could be toast. After that, you can try xda developers' 1.1 ROM again.
Good Luck :shock:
Major problem with O2 upgrade. Can anyone help with recovering my O2 XDA.
I downloaded the OS and Radio Stack files from the O2 website (And read the instructions first)
Radio_Unit_Upgrade_v31703.exe
Radio_Stack_Upgrade_v421.zip
The Radio_Unit_Upgrade_v31703 went like a dream, no prob what so ever.
Once i had completed that, reset up the active sync connection i decided on the Radio Stack update - !! Disaster !!
After the reboot all i get on the screen are lines jumping about.
No number of soft or cold boots will bring it back to life.
The device is still recognised by active sync.
I have tried rerunning the Radio_Unit_Upgrade_v31703. This seems to work without hitch from the PC end. Only that the required cold boot of the XDA returns the same jumpy liney screen.
I did take an SD backup of the system before any changes were made.
Can some kind soul please help me dig myself and my only recently aquired XDA toy back out from this hole.
The model is an PW10A1
Did the radio stack upgrade complete? What happens when you try to flash the radio stack 4.21 again? Have you removed the sim card? Corrupt radio stacks are often a non reversable problem, if the xda is under warranty you might get a replacement from O2, after all it was their program that knackered the device.
Try this: Remove sim, Fully charge battery, soft reset, connect to activesync, run upgrade for radio stack again, follow instructions from there.
Ever since I flashed my rom with the 4.00.10 I have not been able to get my old image back on it nor flash a different rom image. Have I totally messed this thing up? This is the error that I get...
error getting connectiontype
Even though it connects with active sync just fine, it says it can't get connection type. How can I overcome this? I booted up to the bootloader diagnosis and tested the USB connection and it passed. I am a novice and should not have been messing with this and now I want my original rom back!
Please help me. What can I do to fix this problem on my XDA?
Desperate.
I Just Had to Walk Away and Come Back
Whew! I read some more and discovered the very small step that I had missed all weekend. Everything works now except my GPRS connection. I will read some more to fix that! Thank goodness for this forum!!
Okay, newbie upgrader here.
I've read a bunch in these forums, and it's been very helpful.
I upgraded my personal PPCPE (TMO) using their software, and it works great.
I was round my friend's house last night, and he has a PPCPE (AT&T).
Well, we downloaded the v30.09 firmware from Siemens website.
We backed up all the data.
We intalled the firmware.
At the end of the firmeware update, it said to turn the device off by using the hard reset button (that you have to unsccrew the stylus for.) and leave it off for a minute.
We did this.
It then said to turn it back on using the same reset button.
We did this.
However, we get the "Designed for Windows Mobile" logo, and the AT&T logo.
We get ROM versions:
G1.3.3
RA.33.02
A.30.09
After that nothing.
Having hastily given him my phone, I came home with his broken phone.
Well, having done a LOT of reading on this site, I got to use Jeff's tools to create a bootimage on an SD card, and I have been able to get the image flashed and loaded.
They device now boots.
However, I want to get the AT&T software on there as this is what's gonna make my buddy the most happy.
The image I have on there right now is SERv12.
Can somebody PLEASE tell me the best way to get this back to AT&T software running WM2003.
Thanks.
Okay, more info.
I have been successfully upgrading the ROM using the SD flash method.
I have been using Jeff's XDAtools to create the images.
I have been downloading ROM's from yorc and xdaweblink.
I have always tried versions without any software added to the ROM.
I have tried every version of 30.09 that I could get my hands on, even the one in the "SX56 upgrade utility" folder that the Siemens site created.
None have worked.
I have tried 4.00.05 ENG from yorc - didn't work (cool southpark screen though.)
I have tried 4.01.16 ENG from weblink - didn't work (Tmo verison)
I have tried 4.01.00 ENG beta from weblink - didn't work (Tmo beta version.)
I have tried A.30.07 ENG beta from weblink - didn't work (AT&T NFR version.)
I have tried 3.17.03 ENG O2-Euro from yorc -
When I say that the version don't work; here's what I mean.
I get the logo screen.
I get the three ROM versions in the bottom right.
The system then locks up and does not progress any further.
I have left the system on overnight with no difference.
The backlight comes on, but nothing else works.
I have tried the upgrades with and without a SIM card in place.
The phone was originally locked, but has subsequently been unlocked.
I have finally tried going back to A.20.17 from yorc - the original AT&T WM2002 version.
This version at least runs.
I still have the new radio stack running, but I am back to WM2002.
Does anyone have ANY idea how I might get this upgraded to WM2003.
My buddy want to run the MS Voice Command.
Also, with the updated Radio Stack, will he be able to connect continiously to the GPRS connection (sorry, I don't know too much about AT&T.) He really want the always-on internet.
Thanks for ANY advice given.
-=Nick=-
This happened to me using a mmc memory card to do the upgrade, it looked like it was doing everything ok, completed and gave the ok but on cold boot just hung, try another sd card, it just MIGHT work.
I'll look around for anohter SD card and see if that helps.
FYI, I've tried running the upgrade from the cradle/USB a couple of times, but that made no difference.
Also, since I was able to go back to WM2002 with the SD card, I can't see it being bad.
But thanks for the tip, I'll give it a go.
-=Nick=-
G'day fellas
I've got an O2 XDA, and just cooked up a ROM in the kitchen, flashed it to WM2003 4.01.12 ENG O2euro, which went fine. I then tried to update the Radio Stack, using O2 Latest Official Radio Stack RU 4.21 found here:
http://www.yorch.net/upgrades.htm I did this because the phone wasn't working at all, but I can only get a low signal where I am anyway.
It tried to update the Radio, went to 10% and then 'update failed'.
Now when I try to turn it just hangs on the load screen, and when I go into Wallaby Bootloader V5.17 I get 'GSM ERROR'!!
Is that the wrong radio stack for Australia? what on earth can I do now? It won't even boot up into the pocket PC.
Am I able to flash it or re-flash it again, just so I can get it working?
Please help... thanks.
You have the same problem as me. You can enter the OS but you will need to wait for a long time(~10min). Poor man, i think you can repair it only in the center, may be you will be luck if in your country there is center. Im moscow there is not. When you repaired xda, tell me ok. GOOD LUCK
Thanks for your reply, Long.
I have searched these forums extensively for an answer, and even if I was able to 'boot from SD' I don't think that would enable me to flash the radio again, only the ROM.
Yes there is a service centre here, and I would assume they are able to repair XDA's. I will take it there and hope that the repairs will not be expensive.
It's such a shame this happened, since this is my first Pocket PC, and I've only had it a few weeks. It's been a fantastic device (apart from the phone not working properly) and to think that it can stuff up so easily just by applying an 'official' update... :?
I would very much be curious as to how they would repair this at the service centre, so that we could possibly be able to fix this problem ourselves.