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.
Ever since flashing my sprint mogul with the 2.40 bootloader, radio 3.27, and dcd 2.2.6 I've been having problems accessing activesync & the usb connection in the bootloader. Ive tried toggling the advanced connections thing under the settings tab, but that hasnt helped. I feel its caused by either olipro or my usb port somehow hosed right after flashing. It seems to be that the port died, but it just seems so suspicious right after flashing. I have tried 4 computers and each have problems recognizing the usb device. It detects, but cannot assign drivers to it and ends up calling it an unknown device.
Also, do you guys have any issues when hitting the reset button? More often than not, when i reset my mogul will enter the tricolor bootloader screen eventhough i did not touch the power+camera button. I also havent found a reliable way to exit the bootloader other than hitting the reset button until it randomly resets back into loading my dcd firmware.
Any help would be greatly appreciated. It's unnerving nott being able to use activesync or even flash my bootloader back into stock. please help!
I still havent had the activesync issues fixed enenthough i read the thread about using the cab that changes your mobile from using generic rnds to usb serial mode. I would rather know how to stop the erratic olipro behavior. If i hit the reset button on my phone right now, it will likely reset into the bootloader. I dont need to hold the pwr and camera buttons. To get out, it seems i need to have a power cable plugged in and then keep hitting reset until it randomly deceides to boot into the dcd firmware. Ive never seen such bizarre behavior that i can reproduce so cosistently. Any ideas? Please help me, its getting very frustrating. :-(
http://www.youtube.com/watch?v=VjWmmx8ij5Y
This is a youtube video showing what I am experiencing.
I am running olipro 2.40
radio 3.27.00
dcd 2.2.6 which is based off the leacked 3.16 firmware
Basically its a video of me entering the bootloader when i hit the reset button and then me trying to exit the bootloader by hitting the reset button until my mogul randomly restarts into the dcd firmware.
Also, this might belong under the titan upgrading section. If so, could a mod move this thread please?
I've had similar problems but they started when I did the upgrade to the leaked 6.0 + GPS ROM from HTC. Later I installed Olipro and it didn't change anything
i had something close to this.But mine also had charging issue.Turns out the 6800 inherited the same usb issues as the 6700.My pins weren't making contact always.I actually had my unit replaced cause of this.I thought it was a wm6.1 issue as well.but it wasn't.
@ aph
I did install the leaked stock 6.1 right before, but i didnt have issues until dcd 2.2.4. i upgraded to 2.2.6 through the sd card. maybe if we flash back to the non-leaked firmware and upgrade again? Maybe the leaked firmware overwrote someinfo that the latest firmwares dont touch upon?
would you guys mind helping me downgrade my mogul back to stock? just a set of guidelines would be nice. i dont wannt to accidentily flash something in the wrong order and hose my install.
Hi,
I'm facing a problem with my customer O2 phone. It's showing "No Service with "!" mark. I have upgraded everything .. but nothing changes ..
It's a hardware problem or Software problem ??
Thank You
ive got the same problem.... can anyone help please.
You need to reflash using the 'radio ROM.nbf' file.
My magician's radio, stops working after the unit reboots after doing a ROM update. The radio works immediately after the inital splash screen (before the extended rom autorun). After this, the radio doesn't work.
If I skip the extended ROM instal, by rebooting the device prematurely, the radio still doesn't work.
I've tried many different ROM numbers. I've even downgraded to the stock ones that came with the unit.
Any suggestions?
Hint: My radio only works immediately after a hard reset, but not after rebooting using the extended ROM (customization). (aborting the customization, the radio doesn't work anyway).
it could be barred IMEI
What now works for me, is enabling, then disabling 'Flight-mode" on the phone.
I urgently need help with my BA
I attempted to upgrade to Beta version:WM6.1 CEOS 20262.Build 19949 Aku1.2
by sun dream and now its stuck in the bootloader screen, I have gone through the wiki of BA and have done various suggestions on how to hard reset my device but nothing seems to be working. Any help extended will greatly be appreciated. Thanks and More Power to all you guys!
Flash again. If no progress - flash different ROM. Never forget about proper HR after each flash.
hey out there,
i do have some problems with my Blue Angel the last days, i flashed a new rom
1.15.00
1337.45
V.6.01.09 DVH
and had Problems with active sync, seemed like it didn't get an Ip adress.
so i flashed sunwell 6.1 and i was able to synch but radio rom was missing and i wasn't able to do calls at all. Hard/soft resetted reflashed flashed other roms, but now i stuck directly after the Bootloader screen when showing windows mobile 6 logo.
It makes an annoying "Bling" and it's reacting on commands, Stylus or Power button, but i didn't finish starting even after 10 min. I flashed some other roms.
same problem. any suggestions?
sorry for abusing this thread but i didn't wanted to start a new "wuhuhuhuhu i bricked my friends BA" thread.
thanks florian
edit.
if starting now it shows Radio and GSM None
hm...formatted with mtty restarted
put sim inside.
displaying R,G NONE when booting.
soft resetted, displayed right data.
Booted, finally working whyever.
I've tried just about everything and it keeps messing up. Here's what happened:
I got this phone in April from a local craigslist ad. The battery he gave me was old and only lasted half a day, so I ordered one off Ebay (big mistake!). I put it in and it has worked fine for the last 8 months. But one day last week, I went 2 days without charging the phone. Apparently the battery was in the phone the whole time while it drained to 0% (never had let it do that before). When I tried to turn the screen on, it wouldn't. I plugged it in, saw that it had 0 battery left, and left it there to charge.
Ever since then, whenever I've tried to make a call it would either:
-Freeze
-"Dialing..." forever
-Make the call but when I want to end, the sound goes off but the counter keeps going. I can't make anymore calls until I restart the phone
But if I restart the phone, 90% of the time it will show "No GSM" on startup and the phone will not connect to AT&T.
Also, in device information, the radio version does not show up.
Before anything started messing up, I was running Schap's v4.31 WM6 and I think radio version 1.3-something
I have tried:
-official WM5 ROM from AT&T (installed but No GSM error)
-official WM6 ROM from AT&T (always gets stuck at 11% and doesn't install)
-Schap's v4.31 installs fine every time but I get No GSM error
-Radio 1.47.00.10 installs and will work for 1 or 2 calls but then freezes and the No GSM error comes back when I restart
-Radio 1.48.00.00 installs and will work for 1 or 2 calls but then freezes and the No GSM error comes back when I restart
-Radio 1.54.07.00 is stuck at 0% and stays there for hours
-Radio 1.54.30.10 tells me I have the wrong device ID
I'm posting here as a last resort after spending a week on this forum reading on how to fix this phone.
Any ideas or is it toast?
I think about the only thing to try would be to reflash the shipped radio rom. You may need to find out what that 1.3-something actually was and reflash. May fix the problem.
No guarantees though s this is the radio rom and its a mongrel of a thing, causes the most bricks.
Good luck...
Was having similar problems with the radio. No GSM at boot up and could not access phone once booted. No matter what radio I try it gets stuck flashing at 0%. I took the sim out and rebooted the phone. It booted much faster and now the device id tells me this:
Operator Version: PDAviet.net
ROM Version : DVH_V27_BS
ROM Date : 10/30/08
Radio Version : 1.54.07.00
Protocol Version : 32.86.u.7020.23h
ExtROM version : Black(Basic).
Before with the sim installed I got nothing under radio version and protocol version. I can open the phone now but it says The sim card is missing.....Emergency Calls Only. I have been reading for days and days through the XDA guides and Wiki stuff and nothing seems to work. After a try flashing a radio and it gets stuck, I have to use mtty.exe and use set 16 0 to reboot OS. Every now and then the phone will not respond with mtty.exe and I use a sd card with a Splash1, Splash2 and OS only to revive the phone. What should I do next?
Joe