Database Users

Hosed my Radio stack trying to update to new TMOBILE version

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.

Help I think I blew up my new jasjar

ok
I was updating the radio, when the power went out....
did I ruin, my jasjar
what can I do, all the screen says is serial on the top and v1.00 on the bottom
now what ?????

Reconnect it and reflash the full rom for your device. It should connect and work ok. I think the roms for each network etc are all available on this site.
I had this recently when I updated my o2 rom. I downloaded the rom file and ran it but active sync kicked up and I got the screen like you said - couldn't get out of it at all, but when I tried running the rom install again it worked and went through ok.
You could try the radio reflash again, but it's looking like you need the full rom first.

well like everything else in my life, it not that easy
when I connect to active syn, it tell me unknown device connected
it is like a hi fi brian treaser

connect the device. You will see usb message on the screen and activesync WILL NOT connect. Then execute the update again....

I had this a few weeks ago, try a hard reset, press the two keys with the lines accross them at the top of the keyboard, and at the same time press the reset key. when it comes back up with the grey screen select the option to continue and re-dock the PDA to re-start the install, it worked for me - good luck - Mike

Problems after WM6 Upgrade :(

After (I think) successfully upgrading to WM6, I've had a few problems...
1) I can't seem to soft reset anymore (holding down Power at the top + the reset button)...it seems the only way I can now reset my unit is by physically removing the battery...
2) I can't access the bootloader SERIAL mode...I can access the options for the kernel hive and formatting storage, but no success being able to get into USB mode to reflash my unit
Any help or suggestions would be greatly appreciated - I only bought this phone on Friday

1. This was hard reset in WM2003 - for soft reset just press the reset button
2. You need to press and hold power+reset+record(WMP) buttons at the same time
I suggest you read WIKI first before asking questions which are answered a million times

Thank you for the prompt reply.
I can understand your frustration with many people constantly asking these questions, but please don't make me feel like an idiot when I've actually read the Wiki and tried Googling the problem prior to posting.
To clarify, I know *how* to access the SERIAL option (I had to do it to upgrade from 2003 to WM6 to begin with). My point is that holding Reset+Power+Record doesn't work anymore. It just continues the boot process and goes straight to the Windows Mobile splash screen. The reset button, in and of itself, does nothing at all. I've tried everything from just tapping it a few times to pressing and holding it for upwards of 30 seconds...but it doesn't seem to do anything for me.

Try to hold and press power+record+cam buttons then press reset while holding those buttons.

Yeah, it does nothing...I have a feeling that the actual reset button is no longer working on the unit...not sure if that's to do with the upgrade to WM6, or if it's a hardware problem and just happens to be coincidence :-/

don't take xplode's advise wrongly. it's just that reading AND understanding the WIKI is important especially for beginners like yourself.
if you think you've successfully upgraded to WM6, it's probably because of the "Congratulations" message that was displayed... well, you're almost there, though not quite.
try to fully understand the no/yes/yes instruction in the WIKI... the reset+power+record combination is NOT what you should be doing. it has been replaced by another... here's the thread that could guide you... http://forum.xda-developers.com/showthread.php?t=327978&highlight=kitl
and here's the pertinent wiki page...
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4
good luck and welcome to the BA community.

Anyway if this that you try to explain is that the hardware buttons no longer work, you can try the MTTY method, if you have read the wiki you already know what exactly to do

Thanks raymonds, I will try not to, but I just don't want people thinking I'm yet another new member that doesn't read anything before posting, because I know how much I hate that too...I tried reading up on my problems for 4 hours last night before deciding to post because I couldn't find anything else to help.
I have successfully upgraded to WM6 and went through the no/yes/yes steps - the issue is that I want to go back to WM2003 or WM5...they seemed far less problematic for my phone for some reason..one problem I'm facing now is that my BA, pure and simple, no longer recognizes that I have a cellular carrier at all, making it essentially useless as a phone. When I try to go into SIM Manager, it hangs for a while, then goes into the screen saying that only emergency calls can be made...but when I try to put in my PIN, it says "Unknown SIM error", though the SIM works fine in my other phone...
I'm trying to use the Power/Reset/Record to either try reflashing in the hopes that'll resolve my issues, or downgrade...either way, it's not allowing me to do so, and I obviously can't do this while the phone is booted into WM6. It just seems like the reset button is no longer working, since neither combination that uses it (Power+Reset or Power+Camera+Reset) works anymore.

try to downgrade with MAUpgradeUT_NOID.exe, and then reupgrade, another thing you can do is to reflash the radio rom. The MTTY method resets bootloader settings which may be the solution to your problem.
MTTY under Windows XP is explained HERE

xplode, mtty requires one to do the power+reset+record combination, which he currently cannot do.
is this a second-hand unit?

Hm, there was another way to put your device into bootloader mode but i have never tryed it, in most of the WM2003 upgrades there was EnterBL.exe, and when you copy it to the device and execute it the device goes to bootloader mode...
but it also creates problems - read here
Also i had problems in the past with the latest version of MTTY (1.45) and used previous one 1.01 which worked like a charm

Sweet - thanks xplode and raymonds for your time.
Unfortunately I can't try these as I am at work right now, but I do appreciate the suggestions and will try them as soon as I get home.
If I can't get it to work, oh well - off to the service depot and a (probably) expensive lesson learned.

Please keep us updated, about your issue

Thanks guys...
So, I'm taking it that the radio stack is now corrupt, since it's no longer even showing a version number on my BA. I tried the methods xplode suggested - when I enter the unit into KITL mode, I take it I'm supposed to use USB Active as the transport method, since MTTY won't recognize a device otherwise, and my phone just boots into Windows from that point.
When I try to run MTTY though, all it does is display "kITLª" over and over again...I'm not sure if that's normal, or even how to enter a prompt of some kind...
I'm starting to wonder if maybe I should just take it to the depot, pay the $75 I was quoted, and learn my lesson... :-/
Any other suggestions, or am I just totally doing what you suggested wrong?

You do not need to enter KITL because this is used to debug your WM build using Platform builder
Just try to put your device to botloader mode and then use MTTY to instruct the bootloader what to do, or just reflash radio and then new rom

Dead/Dying phone? Need help asap :(

I don't know if the phone is bricked or what. Was in the store tonight, tried to text message my wife who I couldn't find and the phone was all locked up.
Soft reset, and only the date/time loaded, nothing would run. Soft reset again, and the phone didn't load past the bright splash screen. Tried soft reseting a bunch more times, nada. Did a hard reset, first one didn't work. I think it was the 3rd hard reset that took. Phone seemed like it was back to basic WM5, would be okay. Went home, put it on the charger.
Went to take it off the charger to reload data, and it won't turn on. Soft reset, freezes at bright splash screen. Hard reset, same thing.
Is my phone bricked? Anything that I can do to revive it? Or am I SOL?
Cingy/ATT 8525 w/WM5
(By "bright splash screen" I mean when the splash screen flashes brightly. It increases brightness, but just stays that way.)
Any help greatly appreciated.

I managed to load the official WM6 ROM (spl 2.03) via the built-in bootloader. I have radio, ROM, and GSM. It boots through the ATT animation, then freezes. It leaves a black screen with a blue and green static bar running horizontally across the screen about 1/4" thick.
I don't know how to get Hard-SPL loaded on the device because the only way I can see the device is when it's in the built-in bootloader mode.

will attempt PB/KITL I guess, though I can't at this point get the phone to display the KITL info.

No KITL in the ATT WM6 ROM.
Managed to get ATT WM6 ROM through the setup, after the "customization (bloatware)" it reset, and now it sticks on the bootup animation.
So close, I have SSPL and Hard SPL on the micro SD, if only I could get to the damn file manager. If I could somehow cancel out the customization process grrr.
On power charger, I seem to be able to get through the setup after a hard reset okay. It just won't boot after the reset.
Any ideas. I gotta get a few hours sleep. Sorry if this dialog to myself is in the wrong area, I didn't notice the "bricked hermes" thread was in the upgrades, etc area.

viatorx said:
No KITL in the ATT WM6 ROM.
Managed to get ATT WM6 ROM through the setup, after the "customization (bloatware)" it reset, and now it sticks on the bootup animation.
So close, I have SSPL and Hard SPL on the micro SD, if only I could get to the damn file manager. If I could somehow cancel out the customization process grrr.
On power charger, I seem to be able to get through the setup after a hard reset okay. It just won't boot after the reset.
Any ideas. I gotta get a few hours sleep. Sorry if this dialog to myself is in the wrong area, I didn't notice the "bricked hermes" thread was in the upgrades, etc area.
Click to expand...
Click to collapse
Not sure I fully grasp what's happening here, but if you want to stop the customisation then hard reset and when it goes to the loading cusimisation stage shove the stylus in the hole to do a soft reset and it will stop it loading.
Mike

Alright, thanks, will give that a try.
I managed to run the official ATT WM6 ROM and flash it without a hiccup (twice), and task 28 in bootloader says no bad blocks. So I am confused how I can flash an "official" ROM successfully and the device still won't work. Am starting to suspect hardware failure apart from memory.

Thanks a million mate, that worked. Phone boots now, already have SSPL installed. Need to update .net and activesync for Hard-SPL 7 to run I guess. Then I have more options.

Woot! I unbricked my phone
Once I was able to hard reset and cancel the "customization" I ran SSPL, then Hard-SPL 7, then I Super-CIDed the device.
I haven't tweaked the data settings yet, but I can send/receive phone calls. Which is a coup, because this is my main line.
It runs sluggishly. I don't know if that is the ROM or the device. It won't boot if it's plugged into USB, and after flashing Hard-SPL it isn't a recognized device by windows, won't connect to activesync.
I am treating the phone gingerly right now, will try and unload the ATT wap settings cab and restore my pim.
At least now I have the option to install another ROM if it bricks on me again.
I really should have flashed Hard-SPL the DAY, the MINUTE after the warranty was up. Lesson learned.

Or not.
ATT ROM locked up on me, decided to try Schaps 4.40. Won't load past WinMo "tap screen to setup" screen. Guess I'll try something else.

For a stable WM6 rom try TNT SE. It is REALLY stable but does come with some 3rd party apps. Thought you might like to get it working though first then try the other roms and in my experiance I haven't found many other roms that were THIS stable...
Hope you get it working...
For a disassembly guide try this site - http://michael-channon.spaces.live.com/PersonalSpace.aspx?_c02_owner=1
Its a bloody good place to go for all things to do with hardware and Mike is a true guru with hardware problems...
Cheers...

Unlocking my phone for the first time!

Well I'm going to unlock my phone (Sprint Touch) for the first time. I'm trying NFSFAN's wm6.5 ROM. Wish me luck. Hopefully my reading comprehension skills are up to the task so I don't skip a step and blow something up.
---
Question 1:
When I'm going to run the unlock utility, should ActiveSync actually say that it is connected to the phone? When I get to the rainbow screen ("Serial") then plug in the usb wire, the phone switches to "USB" and I hear the "something's connected" noise in XP. ActiveSync, however, still says "Not connected"
...I seem to be stuck here, at the beginning. At least my phone still works
One comment: the NFSFAN 6.5 ROM FAQ seems to want me to run the unlocker with the phone at the Rainbow screen. The PPCGeeks thread by IMCoKeMaN seems to say that you just run the unlocker with the phone normally attached to ActiveSync without unraring or Rainbow mode... Who is right? Am I just confused?

It seems like ActiveSync actually connects to the activesync program on the phone, so when you are in the rainbow screen, it connects without the OS being involved and AS won't show as being connected. If I remember, running the unlocker will put it in rainbow mode and you don't have to do that first. But it has been a long time since I unlocked mine and I forgot the details. I do remember I followed IMCoKeMaN's directions to the letter. Good Luck! It is scary to start, but these guys have got this stuff down to a science!
David

for the unlocker you go throught activesync. then to flash NFSFAN's ROM put the phone into bootloader. You can flash the rom using activesync but i've just got into the habit of using manual bootloader.

Knave,
Please let me know if the W6.5 works well on the HTC Touch (Sprint). I am a bit reluctant to try it yet, but if you can do it successfully, and report on how it does, then maybe I'll follow your lead.
Thanks
QA

So, I'm trying again. This time I plugged the phone in while it was turned on on the standard home screen. I let ActiveSync show that it was connected, and I ran RomUpdateUtility.exe. I click thru a couple screens, the phone automatically goes over to the rainbow screen, and then the status bar screen. It sits at 0% for about a minute.
...and I get another ERROR[262]: Update Error.
I turn the phone back on and it reboots fine (I guess it never actually started writing to the Phone's memory, just like in my initial post.)

One thing before you start, qanda, do you know about Dashwire? It's a way to backup all your phone contacts & info to the web before you wipe the memory. I guess there maybe different backup services out there, but I like to use one just to be safe.
Ah hah! Now it's (ALMOST) working... Here's some stream-of-consciousness directions I'm typing as I do the flash procedure.
1. Plug in phone (phone is turned on, in the normal home screen state)
2. Make sure ActiveSync says you're connected.
3. Run the unlocker (the Vogue_unlocker_MFG_2.31.exe file). Do *not* extract the downloaded file and run the RUU.exe file yourself. It doesn't work that way. You just follow the directions here in the "DOS" looking window that pops up. It does something to the phone, tells you to unplug & replug, ... Eventually a ROM loading program starts & you follow those directions. Then you go back to the "DOS" looking window.
4. Phone automatically reboots and gets to the Windows Mobile initialization screen (tap here & there, etc). Then the phone starts loading the customization stuff automatically. (I was getting a bit worried here that it was stuck on the Windows Mobile 6.1 boot screen -- seemed to take an extra minute or two, but it eventually came up.)
5. Now I guess the phone is *UNLOCKED* but still running the stock Sprint WinMo6.1 OS. I can confirm that when I do the PWR-CameraButton-Stylus reset to the rainbow screen, I see the SPL-2.31.CoKe text in the red bar.
6. Next, I'm going to try loading the NFSFAN 6.5 ROM...
7. I'm back to following the instructions in the thread by codybear *explicitly*: unplug phone, 3-button-reboot to rainbow mode (displaying SERIAL), plug in phone (now displaying USB), run the RUU.exe inside the directory where I decompressed the NSFFAN ROM. Clicked thru the RUU.exe program & phone goes to percent-loading status screen. Phone reboots itself at 100%.
8. Phone reboots *slowly*, the Sprint Splash animation is replaced by an HTC animation. Whew! after several minutes I see a WinMo6.5 setup screen. I do the setup & it autoload customizations. Phone automatically reboots.
9. Still following codybear's thread, I do the RED-GREEN-Stylus hard reset. (You have to hold down the buttons until you see the grey Hard Reset Warning Screen.) ... another SLOW reboot & I go thru the WinMo6.5 tap-screen setup again
10. Like codybear says, I install the Sprint DCD cab that I had copied onto my memory card. Phone wants to reboot again, so I OK it. (Sprint has one DCD cab and another cab for MMS, so I do both.)
----
Directions are now complete. Unfortunately when I try to do something with data service I get a "Error Code 1012 Data Provisioning Failure". It's late now, so I'll try to fix it tomorrow. This might help: http://forum.ppcgeeks.com/showthread.php?t=35433

Now I got everything working. I fixed the final error -- the "Error Code 1012 Data Provisioning Failure".
I initially tried running the IOTA thing via:
Run IOTA by going to Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start
...nothing happened. The I found this thread:
http://forum.xda-developers.com/showthread.php?t=410357
I did the RegEdit thing like it describes, setting the HKEY_LOCAL_MACHINE/Software/OEM/DIM/EnableCurrentUserName value to 0. Then I reran IOTA, and all is well.
Then I reinstalled Dashwire, it sync'ed my contacts up & I'm back to normal!
Woohah!
btw...RegEdit is on the NSFFAN ROM under Start Menu-> System Tools