Related
Ok so I trashed my ppc doing the radio update. Since I did the exact thing that Freshster did here is a cut and paste of my problem
" So, I tried running this TMO 4.00.10 upgrade in order to upgrade the radio stack to 6.24.00. While it was doing the radio stack upgrade, it failed at 13% complete. The error told me to "reset the device normally, wait for the radio stack to repair itself, reset the device again normally, then try to run the upgrade again."
After I did the normal reset that it told me to do, my screen got stuck on the ROM Kitchen boot screen and only showed a G, R, and 4.00.05 at the bottom corner, without showing a radio version or protocol version number. The led would not light up anymore. It did not flash green to show that it had signal, and it would not even show orange when it was connected to a charger. "
At this point Im SOL until tomorrow b/c I dont have a SD reader, my question is, can I upgrade the radio via the SD and hopefully get things going again? Or do I just attempt to reload a whole new rom and rsu via the SD card tomorrow. Thanks in advance for your help.
This is just a suggestion, I don't know if it will work.
1. Bootup in the Wallaby Boot Loader (hold power button while soft reset)
2. Press Calender button to bring up radio stack selections
3. Select turn off GSM
4. Reset and see if it will boot up when it doesn't have radio turned on
5. If it will, then set in active sync in guest mode
6. copy the RSUpgrade files to your window directory on the device using the explorer option in active sync
7. copy the two monitor files monitor_ul_bs.map and .m0 to the windows directory
8. reomove the device from the active sync
9. using the explorer on the device find the RSUpgrade executable in the windows directory and double click
10. this should start the radio upgrade going again
GOOD LUCK!
Thanks for the suggestion, I tried it but now luck. The pda stays stuck on the rom kitchen boot up screen. Thanks again.
OK, I had the exact same problem. You have to be patient, when you reset the device you'll get the R blank / G blank because the existing radio stack has now been trashed. eventually the PPC OS will boot. At this point reset again, wait for CE to boot & then reset again, The point is keep resetting the PPC every time you get the R Blank & G blank screen and wait for CE to boot. ON each reset the radio stack upgrade is working in the back ground. After 4 or 5 resets mine came up with R 6.24. at this point I connected the PPC back to Activesync & reran the upgrade & it went through just fine & installed the T-Mobile WM2003 ROM
Pdageek1 is right on the money! But I'll add one more step, remove your SIM card. HTH
I will try this on my way to work. I have another question, is the unit still charging when its on the base even though the charge light is not on? Thanks
I had same problem, if you flash with old t-mo rom it boots up everytime and will allow you to reflash radio stack.
http://www.t-mobile.com/pocketpcupgrade
hello pdageek and thanks for the suggestions. I have left my unit on at the splash screen with the blank g and r for about 5 2 minute sessions with no luck. Im hesitant to leave it on too long and have it eat up my battery. How long in total did it take your pda to boot up with the corrupt radio upgrade?
Sirseymore, the problem I have right now is that I cant even get it past the splash screen, since the OS is not booting up I cant see the unti via active sync.
You can't just it leave setting there with the blank screen you have to keep
doing the soft resets, until it boots!
Also to speed things up a bit during some of your soft resets try holding the volume control button, it similar to holding the hand of a sick person.
I know it sounds funny but hey what the hell, I did it! :wink:
One last note it also might help if you do a hard reset while holding the volume conrol buttom. I know that also sounds funny but hey I did that too! :wink:
HTH
Thanks for all your suggestions everyone. I ended up loade the latest tmobile rom via the loader, I let the pda sit at the Tmobile splash screen for 15 minutes until it booted into CE. Next I copied the necessary files for the RSU into the windows folder, ran the executable and all is working now.
Once again thanks for all the great people in this forum.
bimmer10 said:
Thanks for all your suggestions everyone. I ended up loade the latest tmobile rom via the loader, I let the pda sit at the Tmobile splash screen for 15 minutes until it booted into CE. Next I copied the necessary files for the RSU into the windows folder, ran the executable and all is working now.
Once again thanks for all the great people in this forum.
Click to expand...
Click to collapse
When you say Latest tmobile rom do you mean the 4.00.10 or the latest rom off of Tmobile's Website?
I got the same problem as you did blank g and r
Let me know Thanks, Allen
I'm in the same boat. I was running 4.00.05/stock 6.18 RS on T-Mobile USA.
I decided to try to do the Radio Stack upgrade by copying the extracted rsupgrade and monitor files to the device, and running them. It hung at 13%, so I soft-reset, and it hung at the blank G, blank R, 4.00.05 screen.
I tried turning GSM off in the bootloader, and have removed my SIM card. No luck.
Then, I flashed to the 4.00.10 ROM via bootloader, and I'm still sitting at the G/R screen. I have soft reset a few times, but that hasn't gotten me anywhere. I haven't left it for longer than 3 minutes or so before I get so anxious that I try another soft reset.
There seem to be two bodies of opinion here - those that say you should keep soft resetting until CE boots, and those that say just to leave it and wait for CE to boot (15+ minutes).
Is there any consensus among those that have recovered from now-infamous blank G/R screen? Should we wait, or should we keep soft-resetting?
JoshB said:
I'm in the same boat. I was running 4.00.05/stock 6.18 RS on T-Mobile USA.
I decided to try to do the Radio Stack upgrade by copying the extracted rsupgrade and monitor files to the device, and running them. It hung at 13%, so I soft-reset, and it hung at the blank G, blank R, 4.00.05 screen.
I tried turning GSM off in the bootloader, and have removed my SIM card. No luck.
Then, I flashed to the 4.00.10 ROM via bootloader, and I'm still sitting at the G/R screen. I have soft reset a few times, but that hasn't gotten me anywhere. I haven't left it for longer than 3 minutes or so before I get so anxious that I try another soft reset.
There seem to be two bodies of opinion here - those that say you should keep soft resetting until CE boots, and those that say just to leave it and wait for CE to boot (15+ minutes).
Is there any consensus among those that have recovered from now-infamous blank G/R screen? Should we wait, or should we keep soft-resetting?
Click to expand...
Click to collapse
Well i just got mine working FINALLY, what i did was flashed the rom to 4.00.10 and then did a soft reset let it sit for 15 minutes and then it came to the Align screen blah blah blah So just be patient and let the device sit for 15 minutes or so
Good Luck
Reflect said:
Well i just got mine working FINALLY, what i did was flashed the rom to 4.00.10 and then did a soft reset let it sit for 15 minutes and then it came to the Align screen blah blah blah So just be patient and let the device sit for 15 minutes or so
Good Luck
Click to expand...
Click to collapse
I let mine sit, and after about 15 minutes, it did finally come back up. I was able to copy the files and manually run the 6.24 RS upgrade, and I think everything is going to be OK now.. *crosses fingers*
I let mine sit, and after about 15 minutes, it did finally come back up. I was able to copy the files and manually run the 6.24 RS upgrade, and I think everything is going to be OK now.. *crosses fingers*
Click to expand...
Click to collapse
Well mine is working very good i havent came acoss any errors yet All i did was do the regular upgrade to 4.00.10 and got to 13% on Radio Stack Upgrade when it errored so i took it out did a few Soft Reset's no luck so i flashed the 4.00.10 Rom through the wallaby bootloader got it up waited patiently for CE to load... loaded after about 15 minutes at that time it was running terribly slow and when i got it up i had no service because i had no Radio Stack so i then loaded up this old radio stack well not so old but it was version 4.21 i then soft reset the device started the 4.00.10 install it went through the Radio Stack then the Rom update with absolutley NO errors or conflicts so everything is working great..
Heres something to keep in mind DONT Upgrade To Tmobile Rom 4.00.10 With the radio stack version A.20.10 Or you will be doing what i had to do!
i want to say thanks to all the great people out there posting
Thanks, Allen
JoshB said:
There seem to be two bodies of opinion here - those that say you should keep soft resetting until CE boots, and those that say just to leave it and wait for CE to boot (15+ minutes).
Is there any consensus among those that have recovered from now-infamous blank G/R screen? Should we wait, or should we keep soft-resetting?
Click to expand...
Click to collapse
My suggestion is this when you're in deep dodo, try it all! :wink:
Because as your seeing what works for some doesn't always
work for others.
Reflect, sorry I wasnt able to answer the specifics of the rom earlier, I was talking about th 4.00.10 version. Im glad you were able to fix the problem. :wink:
After waiting the 15 minutes to recover from the blank G/R screen, and successfully upgrading the Radio Stack to 6.24 and the ROM to 4.00.10, I've been using it for a day or so now, and I am pleased with the new ROM and radio stack.
Biggest plus for me is that GPRS now stays "always-on", even when the unit is turned off/suspended. I also like the fact that AIM 2.0, and PDF/PowerPoint viewers are included in the ROM.
As far as stability, I have had a couple of lockups (cleared by soft resets), and one spontaneous soft reset, but these could have been caused by software that I have installed (SpB GPRS Monitor, StocksAndWeatherToday, Journal Bar, Battery Bar, PocketNav, AE Uptime, Fonix VoiceDial Premium, Resco Explorer 2003).
I have had a couple of instances where the GPRS connection stops transferring any data, but still shows as connected. Since there's no way to turn off GPRS (SpB GPRS Monitor has a Disconnect button, but it doesn't seem to work), I can clear this condition by turning the phone off (not the unit, but the phone/radio) then turning it back on and reconnecting GPRS.
Thanks to everyone on this forum for your help, support, and ideas! This is a great amateur developer community.
JoshB
P.S. - Reflect, sorry I didn't answer your IM. I was in bed...
OK, I am going to try this once more since I can't stand having a useless phone...lol
I *had* the 4.00.05 ROM and the newest at&t radio stack on my T-Mobile phone (with TM service).
Attempted to install the T-Mobile 4.00.10 rom and associated radio stack via the .exe method over that, and it failed.
After that, I tried reverting back to the old T-Mobile 3.14 rom, via the sd card method. That seems to have loaded, but the GSM is still screwed.
Currently, when I start up the phone, I get the Welcome to T-Mobile startup screen, with 3.14 in the bottom corner. After a minute the G with no number after it is there, and below that, instead of an R is a U? (Maybe because I don't have the sim card in?) With no number. Then I get the "bing" sound, and it goes to a blank screen.
Reading through the posts here, it sounds like I should write the 4.00.10 ROM to the unit with the SD card, then wait for it to start up?
Should I have the sim card in?
When should I try the soft-resetting?
Just as an update, so far so good. I wrote the 4.00.10 rom to the unit with the sd card. Did a hard reset like it told me to. Now starts up with the T-Mobile Test only Not for sale screen. Shows 4.00.10, G with nothing after it, and R with nothing after it. It now stays at this screen though, instead of going to the blank screen. I guess this is a good sign, I am in a position others have been in. Yay! Waiting on it now to do something...anything, and I will attempt the radio fix.
Hello everyone.
Im having serious trouble with my MDA i updated just yesterday. Somehow it hung up at 60%. Waited for about 15 Minutes but nothing happened. So restart, but MDA was dead.
I managed it ti load the CE and ROM with an SD from another MDA into the broken one. Went well, the device boots, after 15 minutes, but everything goes very slow.
So managed it to upload the cab file of the RSU on another SD, inserted it, executed, but at 1% it just fails to flash and want to restart the MDA.
I also tested the method someone mentioned with the autorun.exe, didnt help.
In the wallaby bootloader i saw that there is an option to Backup the GSM ROM to SD, but then it wants some kind of "PC Monitor". Thought it might be some kind of hyperterminal connection, but turned out not to be.
So, does anybody here have a clue what to do???
GSM ERROR
Hello there
I've suffered the same problem as many others did.
I suggest one final solution before giving up and believing it's a dead motherboard.
the solution I believe is:
1- Using a working XDA and through the bootloader click on contacts button to get to the flash menu then click on the option for copying rom and GSM to SD.
2- after complete copy use the same SD card in your device (at bootloader)
3- tell me what you get..
Re: GSM ERROR
smiley said:
1- Using a working XDA and through the bootloader click on contacts button to get to the flash menu then click on the option for copying rom and GSM to SD
Click to expand...
Click to collapse
Gives me the already mentioned "Please connect RS232 and run PC Monitor" Screen...
If you are sure you have followed all procedure re: 1% screen of death mentioned in various threads in this forum, then you're best bet is to return the unit the your distributor/ service centre for repair.
I had this problem and posted my experiences on several threads. I spent the first 2-3 weeks trying different things without any luck. THen one day, I just return the unit the distributor and they repaired in two days. I was told they had to replace the GSM main board.
My problem was caused by T Mobile radio stack upgrade ( I did not use SD method, so the installation installed Tmobile radio stack on my 900/1800 xda. It worked fine until I accidentally 'checked' the 1900 option...
Just my two cents
HELP.... I was unable to upload my sx56 with the new 2003. I crashed my ROM... Any ideas on how to restore.
Rock
Tell me what you see from the display.
I can help!
Froozen SX56 while upgrading the ROM
Unfortunately my system crashed when i was upgrading my ROM this is for a AT&T SX56 Pocket PC which I wanted to unlocked so that I could use it with T-Mobile SIM card. Now the screen says :
Upgrading
It will take about 5 minutes...
I was trying to upgrade it with the xda-developer rom verison.
I dont have any backup also for this device please help and I do have a SD card and SD card reader also.
If the bootloader not be erased, you could still use SD to restore OS.
If the bootloader already damaged, the only solution is hardware solution.
I can help you to resolve all problems
How to restore using the SD please tell me.
I do get the bootloader mode when i pressed the power , navigator and reset button on the pda
shri62 said:
How to restore using the SD please tell me.
I do get the bootloader mode when i pressed the power , navigator and reset button on the pda
Click to expand...
Click to collapse
using Xdrit to write the OS to SD card via SD writer.
you can get Xdrit from xda-developers.com (do some search).
Need real help
cgigate said:
I can help you to resolve all problems
Click to expand...
Click to collapse
I had this stupid RadioStack crash that resulted in GSM ERROR that made my device unable to recharge the battery or run mobile function, so the status now is a ppc which has no phone and should always be conected to AC
when I consulted the Agent service tey claimed it's a motherboard error that would require a new baord, which'll cost me around 300$.
could you please help me!!
Cgaigate, is it possible to restore a corrupt radio stack using jtag, if you have the capability I can let people know.
GSM ERROR - RADIO STACK CRASH
Hi Smiley,
I crashed my Radio Stack, too. Has anyone an idea? Is it possible to repair? By myself?
I heard cgigate could help?
Bye
Yep - "GSM Error" in Wallaby Bootloader 5.15
Anyone got any ideas on fixing this one?
Cheers!
Andy
I upgrade my ROM to Pocket PC2003 (T-mobile.nbf) image that worked with no problems using the XDA OS Image tool. It copied over using programme A and following the upgrade I carried our a Radio Stack upgrade to 4.21 supplied by O2. I now have a problem as the phone wont work. I tried re copying the immage again but just before programme A runs a cmd.exe box apears and I get the following message 'ERROR: GetConnectionType - An existing connection was forcibly closed by the remote host.
error getting connectiontype
Programme A then tells me my device is not connected and to check the USB connection. Can any body please help me. All I want is to get my XDA phone up and working again.
Which network are you using, it may be that the bandswitch has chosen 900/1900 which would prevent orange and t-mobile from working, if this is the case enter bootloader, then push the key below the antenna, choose 900/1800 then reboot.
I'm on the O2 (pay as you go) network. There were no problems with my phone and the T-mobile image until I performed the O2 Radio Stack upgrade. I hade already performed this upgrade on my old operating system, before I copied over the T-mobile image. I had no problems with the old OS and the Radio Stack upgrade.
Seamus, if you burn the original O2 rom back to the phone, you will be able to return it to O2 if it is the radio stack upgrade that killed the phone, they should fix it for free.
Hello guys Need some help from the pros
I currently purchased this phone its a Siemis Sx56 AT&T. As i was updating 2 unlock the phone with a dump of another sx56 aT&T that was uncloked (via sd card) it stop in the middle of the proces of uploading the boot of the sd card. Now the phone:
1. Will not start
2. Can not boot the phone to wallaby
3. cooked a rom and tried 2 boot 2 wallaby with no luck
4. 1/2 read & read with no way of knowing what i'm doing wrong
5. how can i repair my bootloader (I used the one in xdtools with no luck)
Than U guys in advance
Luv the Info in the forum.
Adrian
Atlanta GA USA
I dragged my Mini s out of the draw thinking it dead for the past few months, after using the battery jump start trick got her up and running again. now, after using mobile 6 on my other HTC i wanted to upgrade on this one, nothing fancy just bog standard mobile 6. its an O2 G4 model, I also checked it with the wizard service tool. I then used the hard SPL G$ tool to unlock it, that went fine. the device repowered and worked. I then tried to load in windows mobile 6 from this thread
http://forum.xda-developers.com/showthread.php?t=355591
after its started the flash I got an error message saying "error 300 invalid update tool" please get a newer tool, I have tried to run it again and now get the message " error 2641 cannot connect " and now all I have is an XDA with a red, green and blue screen showing IPL2.21.0001, SPL 2.21,0lip and "usb" in the bottom left corner
is it bricked? can I recover it, I will be gutted if it is bricked as I followed the instructions to the letter
btw I havnt disconnected it from the USB at all, just leaving it there until I get somne advice from here
update, bit the bullet and unplugged, soft reset and its all as it should be, on windows mobile 5.
so my question now is why didnt the Rom update in the link above work? or am I just a noob doing it wrong...
try downloading another rom and flash it again...even if it isn't connected in activesync ignore that and flash away...if that still doesn't work try your original rom wm5 and then flash a wm6 again...it's not bricked(see below)
stevescoots said:
I dragged my Mini s out of the draw thinking it dead for the past few months, after using the battery jump start trick got her up and running again. now, after using mobile 6 on my other HTC i wanted to upgrade on this one, nothing fancy just bog standard mobile 6. its an O2 G4 model, I also checked it with the wizard service tool. I then used the hard SPL G$ tool to unlock it, that went fine. the device repowered and worked. I then tried to load in windows mobile 6 from this thread
http://forum.xda-developers.com/showthread.php?t=355591
after its started the flash I got an error message saying "error 300 invalid update tool" please get a newer tool, I have tried to run it again and now get the message " error 2641 cannot connect " and now all I have is an XDA with a red, green and blue screen showing IPL2.21.0001, SPL 2.21,0lip and "usb" in the bottom left corner
is it bricked? can I recover it, I will be gutted if it is bricked as I followed the instructions to the letter
btw I havnt disconnected it from the USB at all, just leaving it there until I get somne advice from here
Click to expand...
Click to collapse
Download this RUU ,extract it and replace all the files in the folder with the RUU files in the Rom and run the RUU,it'll flash successfully .
stevescoots said:
update, bit the bullet and unplugged, soft reset and its all as it should be, on windows mobile 5.
so my question now is why didnt the Rom update in the link above work? or am I just a noob doing it wrong...
Click to expand...
Click to collapse
Your ROM Update may not have worked because, maybe it was not built for the G4 Wizard. so try anyother ROM
xda2_hasseb most of the WM6 roms available for download on xda-developers are G4 safe as they don't conntain ipl and spl flash....so you can safely flash a Windows Mobile 6 rom without bricking your Wizard
'XDA Mobile 6 Release 5 FINAL' is the latest custom build wm6 rom,build for both the devices,it can be flashed to both the devices G3 and G4 safely,its one of the most favourite roms.
Thakx xardas_90, i knew they didnt had the IPL and SPL with them but i didnt knew that it was IPL & SPL not the ROM it self that caused the Bricking of the G$ WIzards i thought Windows ROM for G3 and G4 were different but THANKS for the info. TC
Thanks for the advice, got it done and works a treat, except no data transfer or sms or net conncetion, still soldiering on, at best it will work, at worst, well i guess my son gets a hand me down lol
stevescoots said:
Thanks for the advice, got it done and works a treat, except no data transfer or sms or net conncetion, still soldiering on, at best it will work, at worst, well i guess my son gets a hand me down lol
Click to expand...
Click to collapse
You need to get GPRS/MMS settings configured,get these settings from your carrier,only then you'll be able to connect to internet/SMS/MMS, or check out the 'XDA Mobile 6 Release 5 FINAL' rom thread,you might find the appropriate GPRS/MMS settings there of your concerned network.