Mike, who'd previously let us know about that leaked out 6.1 update has been watching Motorola's site like a ravenous hawk hovering over a field mouse. That mouse has finally popped out of its hole: head on over to Motorola's site for the official Motorola Q9h 6.1 Update (opens in new tab).
You're going to need the standard complement of update tools before you get going: Windows XP or Vista, internet connectivity (the software just might be calling home to check to see if your Q9h is legit), and a full backup before you update. Like all ROM updates, this one will wipe your device, so get prepared.
Welcome to the sliding panel glory of Windows Mobile 6.1 on the Q9h everybody. I've been in here for awhile, and let me tell you: jump on in, the water's fine.
Download the installer directly here. Thanks, Mike!
Installation completed without a hitch. Love the new interface for the home screen. I'll have to check out any other improvements later.
Now all we need is the wm6.1 for the Samsung Blackjack2 SGH-i717/SGH-i716.
You'd think with the two devices having very similar specs that the release of a ROM update for one would be followed shortly by the other.
Correction: Samsung Blackjack2 is SGH-i617/i616.
I am having problems installing the update. I get to the beginning of the Motorola Software Update program and none of my phone's info shows up. ActiveSync runs but the MSU software doesn't even recognize my phone.
Woohoo!!! Thank you Jesus!!!
I have a Q9h unlocked and using it on Tmobile, will doing the upgrade to 6.1 lock the phone back to ATT?? If so is there a way around this??
Our website are the reliable wow gold and wow power leveling or wow gold
I have a Q9 phone and I cannot get Facebook.com on it. I went into the store @ Altel and they told me that it does not get it. For some reason I believe they did not want to take the time.
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.