[ian13550]

So I tried to upgrade my Bold from .190 (ATT) to .216 (AVEA). I pulled down the OS upgrade, installed it, deleted the vendor.xml and ran the loader.exe (I'm running DM 4.7). I had previously upgraded a few weeks ago from .167 (?) to .190 without issue using this same process.

Unfortunately, it looks like the install went badly. The loader times out before my phone reboots or comes back to life. My phone returned with the white screen and "error 507" message.

I downloaded the javaloader and ran the "-usb wipe" command and tried to reinstall the OS using the "loader.exe /nojvm" command which seems to have worked since it loaded the OS and apps back onto the phone. However, at device reboot, my Bold hasn't come back to life. While I do not have an error message, my Bold has a black screen with the red LED (solid) on.

It's been 30+ min in this state. Do I dare yank the battery or wait it out? My thought was that if things were normal I'd have a hourglass/clock ticking away as the OS loaded but no such luck...

Thanks --
Ian

[djkmann]

Install desktop manager 4.6 and try the upgrade again.

[thielsa]

Something to try that worked for me. I started the upgrade with the battery pulled out using the Desktop Manager, and after it started I plugged the battery back in and the upgrade went through. I saw this tip on a site and gave it a try. I was having the same issues as you prior. Good luck.

[ifonline]

Any chance you are running Windows on a Mac through virtualization?

[Shaun]

... are you connecting your device to your computer via an external USB hub?

[ian13550]

Originally Posted by ifonline

Any chance you are running Windows on a Mac through virtualization?

Actually -- yes I am. I didn't have issues moving from .167 to .190 this way...

I ended up pulling the battery and the phone properly reset itself and started up with .216 installed. I then restored my phone via the DM Restore function.

--Ian

[ifonline]

Originally Posted by ian13550

Actually -- yes I am. I didn't have issues moving from .167 to .190 this way...

I ended up pulling the battery and the phone properly reset itself and started up with .216 installed. I then restored my phone via the DM Restore function.

--Ian

I had the same issues. I ended up using a Windows laptop just to upgrade the OS. Virtualization and the BlackBerry don't play very well together, as you (and I) experienced.