[MDA, XDA, 1010 Software Upgrading] Freshster:
My bad experience is your reward . . .

Here is my long-winded explaination of my experience upgrading to this version 4.00.10 with radio stack 6.24.00. Sorry for being long-winded, but maybe this will help someone in the same situation that I was in. Or maybe it will just be educational for other people.

The previous versions that were installed:

Microsoft Pocket PC Version 4.20.1081 (Build 13100)

ROM Kitchen version	4.00.05

ROM date	6/05/03

Radio Version	6.18.00

Protocol Version	324e4

Upgraded working versions (after a headache of a time):

Microsoft Pocket PC Version 4.20.1081 (Build 13100)

ROM version	4.00.10

ROM date	6/20/03

Radio Version	6.24.00

Protocol Version	324e4

Here goes nothing:

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.

Fearing that I had fried the radio stack, I then downgraded my CE ROM to TMO 3.14.40 version to see if that would help by allowing the ROM to tmupdate itself and correctly flash the radio stack back to 6.18.00. I was finally able to boot fully back into CE, but when tmupdate ran, it was unsuccessful in flashing the radio stack back to 6.18.00. It kept failing at 2% complete and told me "Upgrade was unsuccessful, hit OK to reboot device." Each time I rebooted the device it would come up with tmupdate again and attempt the radio stack upgrade all over again, but unsuccessfully each time.

After trying this 3 times, I figured I needed to remove the tmupdate from the STARTUP folder so that I could at least communicate to the device with Activesync, and then maybe I could try the upgrade again to version 4.00.10 with radio stack 6.24.00. I deleted the tmupdate shortcut from the STARTUP directory and attempted the 4.00.10 and radio stack 6.24.00 upgrade again. This was unsuccessful since the upgrade program would freeze at the warning screen after you hit the next button to start the radio upgrade. My guess, is that since it couldn't negotiate the version of the radio stack that was currently installed on the device, then it could not continue.

I then figured out that the radio stack upgrade could be applied seperately from the ROM upgrade. I figured this out by noticing that the radio stack upgrade was located in the \WINDOWS directory and was being called by tmupdate (also located in the \WINDOWS directory). Since the 6.18.00 radio stack was not being applied successfully, I decided to try and upgrade the radio stack to 6.24.00 MANUALLY! This proved to be VERY EASY, and worked successfully!

There are two files included in the ROM (EXE) image that are responsible for upgrading the radio stack. These files are located in the ENGLISH directory and are called "RSUpgrade.exe" and "RSUpgrade.cp64." First, I copied the two files "RSUpgrade.exe" and "RSUpgrade.cp64" from the ROM (EXE) upgrade image into the \WINDOWS directory on the device. This overwrites the previous versions of "RSUpgrade.exe" and "RSUpgrade.cp64." After those two files are replaced with the upgraded versions, all you have to do is execute the file "RSUpgrade.exe" to begin the upgrade of the radio stack. I have not tried this with the ATT radio stack, but it seems that it should work the same way. Let me know if anyone tries this.

Once the radio stack was upgraded successfully to 6.24.00, I was able to SD flash the nk.nbf image onto the device.

My results are a fully working TMO with ROM 4.00.10 and RS 6.24.00.

:lol:

-DEF™