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.
I have upgraded the Program a and B from myxda
All was OK until I got to about to complete the RSU upgrade when Iwas asked about the passward usually asked when you switch the phone ON.
After two atempts it did not recognised the passward and rebooted to a clear screen with a top bar and rigth hand bottom keybord screeen which is there for 20min or so and then resets itself.
I have tryed many things and what I can get is a bootloader reporting GSM Error and Key Card wrong but all is finshing with this same clear screen+top bar+keyboard.
Could some cluee person help me before I have to surender to a Telstra tech?
Thanks
I've had my Qtek 9000 for a week. I've spent most of that week installing software, and getting it setup (using a lot of useful info from this site).
This afternoon it locked up, and wouldn't respond to any button presses (including the on/off button)
Soft resets result in it powering backon, but stopping at the boot screen, after displaying the ROM versions in red text.
Eventually, I tried a hard-reset. Same thing happens - process goes ok until it displays the ROM version, when it just sits there. I've tried removing the SD card and SIM card and hard-resetting. No Joy.
I had just installed OzVGA, and was testing it when this occurred, but that is probably just a coincidence (surely a hardreset should fix anything bad that happened there?)
I hadn't at any point played with the ROM.
What should I try next?
And, does anyone know if I'm going to be able to get support for this in the US from Qtek? (I bought it in the UK), new
Thanks in advance.
-Steve
RE
Have you try taking out the battery, leave it for a while, put back the battery and do a hard reset?
It may work
Re: RE
FOSA said:
Have you try taking out the battery, leave it for a while, put back the battery and do a hard reset?
It may work
Click to expand...
Click to collapse
Unfortunately, no such luck
I'd tried that before, but the battery was only out for a short time. This time it was been out for at least 15 minutes.
Does anyone know if there's any kind of hardware or diagnostic test mode it can be booted into?
-Steve
How about updating/upgrading thr ROM?
This might work. you'll have to reinstall everything again, though
Jorgee said:
How about updating/upgrading thr ROM?
This might work. you'll have to reinstall everything again, though
Click to expand...
Click to collapse
Thanks - I may try that tomorrow. However, I'm a little concerned that updating it with a new ROM might invalidate the warranty (especially if it's not a QTEK ROM)
I was hoping that there was some kind of hidden 'diagnostic mode' I could try first, before taking that step. I've also been looking everywhere on the web, and I can't find anyone else that this has happened to. This makes me think it may be a hardware problem, though the way it just 'happened' seems more like s/ware.
Anyway, I'm out today so this will have to wait until tomorrow. My biggest concern at the moment is how I'm going to get any warranty support in the US. All I have at the moment is a very expensive brick!
-Steve
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Jorgee said:
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Click to expand...
Click to collapse
Thanks - but no improvement. I do get the 'serial' screen (with v1.00 displayed at the bottom), but when I do _+_+reset from there, it just goes back to the 'normal' Qtek boot screen and sits there.
Unfortunately, not having access to the OS, I don't know exactly the ROM versions etc. However, the info displayed in red text on the Qtek boot screen (where it hangs) is as follows. How do you interpret this?
R 1.03.00
G 42.36.P8
D 1.13.64 WWE
Thanks for your help - I'm hoping I can get this resolved without having to find out how to get support from Qtek!
-Steve
thefixer said:
Jorgee said:
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Click to expand...
Click to collapse
Thanks - but no improvement. I do get the 'serial' screen (with v1.00 displayed at the bottom), but when I do _+_+reset from there, it just goes back to the 'normal' Qtek boot screen and sits there.
Unfortunately, not having access to the OS, I don't know exactly the ROM versions etc. However, the info displayed in red text on the Qtek boot screen (where it hangs) is as follows. How do you interpret this?
R 1.03.00
G 42.36.P8
D 1.13.64 WWE
Thanks for your help - I'm hoping I can get this resolved without having to find out how to get support from Qtek!
-Steve
Click to expand...
Click to collapse
You have a WWE (English QTEK ROM) but since you cannot enter bootloader mode, I don't think you will be able to update. You might have to return your device to where you bought it
Jorgee said:
You have a WWE (English QTEK ROM) but since you cannot enter bootloader mode, I don't think you will be able to update. You might have to return your device to where you bought it
Click to expand...
Click to collapse
Jorgee,
I notice (in the HTC 'confidential' manual I just downloaded) that there is a diagnostic program. Apparently, I put it on an SD card, and do Power+Backlight+reset to invoke it.
Do you know if that diagnostic tool is available anywhere on here, or elsewhere on the web?
Also - I wqas trying to find exactly how to enter 'bootloader' mode (after I have the 'serial' screen). Should it boot differently from here when doing a hware reset (_+_+reset)?
Regards
Steve
Actually, when you see SERIAL, that means you are already in bootloader mode. One question, what ROM do you wanna update to? QTEK, IMATE, MDA, O2?
Do the following once you get the SERIAL ON THE SCREEN:
1. Open active SYNC, then choose FILE>CONNECTION SETTINGS, then remove the check on the USB option.
2. Connect the phone to the computer with the sync cable. This should change the SERIAL on the device to say USB.
3. Run the ROM Upgrade (whichever it is you chose).
This shoulod update your device. If you are able to enter bootloader mode (SERIAL) this means that probably your ROM (OS) is damaged. Just update it even to the same verison then it should work.
If you get Country ID error while trying to update or any other error, just inform me, i'll walk you through the process.
Jorgee said:
Actually, when you see SERIAL, that means you are already in bootloader mode. One question, what ROM do you wanna update to? QTEK, IMATE, MDA, O2?
Do the following once you get the SERIAL ON THE SCREEN:
1. Open active SYNC, then choose FILE>CONNECTION SETTINGS, then remove the check on the USB option.
2. Connect the phone to the computer with the sync cable. This should change the SERIAL on the device to say USB.
3. Run the ROM Upgrade (whichever it is you chose).
This shoulod update your device. If you are able to enter bootloader mode (SERIAL) this means that probably your ROM (OS) is damaged. Just update it even to the same verison then it should work.
If you get Country ID error while trying to update or any other error, just inform me, i'll walk you through the process.
Click to expand...
Click to collapse
Hi Jorgee,
I'd prefer to go for the QTEK Rom (I'm assuming, from the info I posted above that I currently have 1.13.64 WWE). I'd like to go for the same or later version of this, but looking on the ftp site here I can't see ay QTEK ROM upgraders.
I have checked that when I plug in the USB I get 'USB' appearing on the screen, so I'm hoping that a ROM upgrade will at least work, even if it doesn't fix my problem.
One other thing that concerns me. When I plug into USB (with either a PC or the AC charger) the LEDs aren't lighting to indicate it's charging. Obviously, when during the flash upgrade I should make sure I have a reasonably charged battery. However, I don't know if I do (or even if it's currently charging).
-Steve
I guess leave it charged using the AC adapter for an hours, then here's the QTEK ROM.
ftp://xdaupload:[email protected]/Universal
Under Shipped ROM's you should see the QTEK.
If you cannot find it, tell me, ill send it to you. Trying to avoid this because it is almost 60MB in size
Jorgee said:
I guess leave it charged using the AC adapter for an hours, then here's the QTEK ROM.
ftp://xdaupload:[email protected]/Universal
Under Shipped ROM's you should see the QTEK.
If you cannot find it, tell me, ill send it to you. Trying to avoid this because it is almost 60MB in size
Click to expand...
Click to collapse
Thanks - I'd already found it on the devbuzz site, and am currently giving the unit an hour or two's charge before trying this. Wish me luck!!
-Steve
OK, here's what happened when I tried to update with the same Qtek firmware:
Initial dialog (that shows old and new (to be installed) firmware versions had blanks for all three firmware versions currently installed.
Started the upgrade, and left it running (couldn't bear the tension of watching!). Came back, and found the following error message displayed:
"Error 113: Extended ROM Update Error"
The update tool indicated that I should 'try again'. I'm currently re-charging the unit, and hoping (against hope) that this error was caused by insufficent battery charge.
-Steve
Okay, but maybe it just didn't update the extended ROM but the OS rom has been updated properly. After this error, try the __ + __ + reset button and see if it does boot fine.
Jorgee said:
Okay, but maybe it just didn't update the extended ROM but the OS rom has been updated properly. After this error, try the __ + __ + reset button and see if it does boot fine.
Click to expand...
Click to collapse
No luck.
I've also tried re-flashing a second time, but this time I watched it to see what happens
As the radio firmware is flashing, a message to that effect is shown on the Qtek screen. Once that is finished, the upgrade tool starts the extended ROM flash. At that time the Qtek's screen goes completely blank. The, after a minute or two, the upgrade tool reports that the extended ROM failed to upgrade.
I am assuming that normally, while flashing the extended ROM, there's a message on the phone's screen to say what's going on?
I'm also wondering whether to have a go at flashing the ROM in one of the other ways?
-Steve
I heard sometimes just flashing the Radio only might work.... Then after that you can flash the rest. Just extract the contents of the ROM to a directory. Take note of the ff:
Radio : radio_.nbf
OS : nk_.nbf
Ext : ms_.nbf
I just rename/move/delete the MS and NK files then run the update
Jorgee said:
I heard sometimes just flashing the Radio only might work.... Then after that you can flash the rest. Just extract the contents of the ROM to a directory. Take note of the ff:
Radio : radio_.nbf
OS : nk_.nbf
Ext : ms_.nbf
I just rename/move/delete the MS and NK files then run the update
Click to expand...
Click to collapse
Thanks Jorgee. Still no real success, but I think I might be getting closer.
I've tried the above (using both the original romupdate_ut.exe and MaUpgradeUt_noID.exe - same results with both).
I've tried each of the three files individually (using the ones from the shipped ROM, as downloaded above)
radio_.nbf always seems to flash ok
ms_.nbf always fails right at the start, and nothing appears on the phone's screen
nk.nbf almost worked. It started, and got up to 87% (tried this 3 times), with the update showing on both the phone screen and PC. Then it failed with error 112, leaving the '87% complete' message on the phone's screen.
Soft or hard reboots still result in us just ending up 'hung' at the boot screen.
Once again, thanks for your help so far. However, I am beginning to give up hope!
-Steve
I have the same problem with my Dopod 900 at post http://forum.xda-developers.com/viewtopic.php?p=207524#207524
But mine is no problem with EXTRom Upgrade
Waiting for your advise!
Thanks
truongia said:
I have the same problem with my Dopod 900 at post http://forum.xda-developers.com/viewtopic.php?p=207524#207524
But mine is no problem with EXTRom Upgrade
Waiting for your advise!
Thanks
Click to expand...
Click to collapse
I wish I had a solution!!! I've spent about 20 hours trying to get this thing to boot!
One question though - how did you get the 'boot option' menu up (allowing you to clear the registry etc). I might try that on mine (I had assumed that a hard reset ALWAYS cleared the registry.
Given that I was playing around with ozvga before this happened, there's a small chance that might help (though I think not; as I can't see how that would also stop the flash update working)
-Steve
Hi guys
I'm using an orange switzerland branded m5000, and I use buzz's unlocker yesterday to remove the SIM Lock on it. Appears top have worked fine, as I can use my wifes SIM card in it now(different provider).
However, I'm now trying to flash AKU 3.2 (Ivan's version) to my device. I let it connect to my PC with activesync, then start the RUU.exe. The screen that shows me the current versions, and what I'm upgrading to appears, and I click next. Then the small window with "gathering information from device" appears, and stays there. After about 30 seconds, my m5000 spontaneously reboots. Consequently, after another minute or two, I get a 101 connection error from the RUU.exe.
What am I doing wrong here?
Besides: My device currently (post-unlocking) claims to be running Radio V. 0.00.00, and the AKU3.2 upgarde screen claims it will only upgrade the CE Version, is this right? Am I now forever stuck of Radio V 0?
It worked now, please ignore
Ok, it worked. I dl'ed and flashed the 3.2 JasJar Rom first, and then Ivans beta14 worked. It's really quite a noticeable speed up. Thanks to everyone who spent their precious time developing these things.
Now all I have to do is get my providers MMS and GPRS and 3G settings back to normal.
Hi, had a problem flashing my bro in law's Titan.
I unlocked the titan with the titan unlocker by Olipro and flashed with the round 4 reloaded (loaded) rom (dcd 3.2.6)
unlocked fine, installed the rom to 100% rebooted phone and its stuck on the Bell screen. (its after the HTC screen and after the screen that shows versions, which it does show D. version 3.2.6) any ideas how to get it to where i can flash it again?
Does it have a compatible v3.x radio installed as well? I recommend 3.42.40 personally, but just about any v3.x radio will work.
BTC
Tzetsin said:
Hi, had a problem flashing my bro in law's Titan.
I unlocked the titan with the titan unlocker by Olipro and flashed with the round 4 reloaded (loaded) rom (dcd 3.2.6)
unlocked fine, installed the rom to 100% rebooted phone and its stuck on the Bell screen. (its after the HTC screen and after the screen that shows versions, which it does show D. version 3.2.6) any ideas how to get it to where i can flash it again?
Click to expand...
Click to collapse
Ok, solved the problem by pressing the power button, camera button and reset button all at the same time. This of course enabled the bootloader on the phone. installed another rom which gave me the same result, stuck at carrier screen. This is of course because i didnt know i had to upgrade the radio first. Got the phone running again by updating the rom with the one at the HTC website for my carrier.
Now i'm trying to update the radio. there isnt alot of instruction out there, but i did find this http://wiki.xda-developers.com/index.php?pagename=Radio only upgrade instructions Although after following the instructions, the universal rom upgrade tool never connects to my phone. I tried the vista fix here http://forum.xda-developers.com/showthread.php?t=313001 But being that its over 2 years old, i'm guessing its now useless as when i try to update with the files there my OS says my drivers are more current and wont allow me to install them.
So now i'm stuck at the "how to upgrade my titan's radio" stage. Anyone have better instructions? (or can tell me what i'm doing wrong?
what i've done
downloaded radio version 3.42.40 as BTC suggested
downloaded "universalRUU" and extracted it to its own folder
copied the radio's file "TITAIMG.nbh" into the UniversalRUU folder
reset my phone into the bootloader screen
ran the ROMUpgradeUt.exe from the UniversalRUU folder
pressed "next"
it says "checking information on your device" and hangs there forever.
if i press update anyway, it continues to the last screen where i can press "finish" and thats it. nothing happens. which part am i missing? the phone is DEFINATLY connected to windows at that point, so it should be able to detect it, but it doesnt seem like it even tries as there is no system pausing or stuttering like it might be trying to do something.
thanks for the help so far.
Solved the problem on my own, as well as the other couple problems i ran into.
Updated the Titan WIKI to reflect my solutions and clarify some key points.