[BostonDriver]

I'm in the middle of an OS upgrade (Sprint) for my 8130. Following the steps in the FAQ, things look[ed] fine. I'm stuck(?) on the 2ed to last step, "Wait for device initialization"

This is v4.3.x to v4.3.(latest from sprint), not v4.5. On the sticky 4.5 thread for the 8100, I read that

The process takes about 45 minutes to an hour depending on how much data you have to backup and restore during the process. Once it's done loading the new OS it will reboot (it may do this twice during the entire process.) You will see a white screen with an hourglass for up to 20 minutes at a time while the DM says "waiting for initialization."

I've been at this 2ed to last step for > 2 hours now. There have been no errors, the device looked like it rebooted once or twice. The progress bar is moving, slowly, but moving. The text above the progress bar says "Connecting to device". What does the progress bar actually mean? Is this how long thing will take, or simply how long before the Application Loader Wizard times out and give up?


Here are the steps that have check marks already:

Connect to device
Back up device data
Back up third-party applications
Connect to th device ROM
Read device system configuration
Load JVM and system software
Wait for device initialization
Read Java application configuration
Load Java applications

I'm still at:

Wait for device initialization

Last step I'm hoping to get to:

Restore device data

Any idea what's going on?

Thanks

[strike2tamu]

Not sure about the 8130, but my 8100 once the progress bar reaches the "e" in device it boots up.

[BostonDriver]

Originally Posted by strike2tamu

Not sure about the 8130, but my 8100 once the progress bar reaches the "e" in device it boots up.

I'm well past that.

I'm just past the > in the "Next >" button. It looks a bit more that 2/3 to 3/4 of the way to the end.

[BostonDriver]

I hit a "safe" key (I hope) and the display (in white) says

Connecting to desktop...

[BostonDriver]

Things simply hung in this state. I had to hit cancel. DM was shutdown and XP was told to stop the device. That went fine. The 8130 needed a battery pull.

The only step that was not done was the restore, which I did manually.

[strike2tamu]

Originally Posted by BostonDriver

Things simply hung in this state. I had to hit cancel. DM was shutdown and XP was told to stop the device. That went fine. The 8130 needed a battery pull.

The only step that was not done was the restore, which I did manually.

Cool, glad it worked out.