Thursday, March 4

Verizon Wireless and the BlackBerry Tour 9630, Part II

Sometimes, you rant. That's what I keep telling myself, every time I rant.

Anyway, before I can move on to other topics, I need to post the second part to this whole "Error 552" issue and clear up something regarding Verizon Wireless.

First, Verizon. In my previous blog post, I took Verizon Wireless to task for two reasons. First, I criticized them for not knowing how to fix my BlackBerry error, and dogmatically insisting they had to send me a new phone because "an Error 552 can't be fixed." On this count, they're still, misinformed.

The second thing I was fuming about was their policy that the contract I had with them wasn't just for ME and my money, it was for my lines. Any attempt to move any line to another provider, even though I was willing to leave my contract untouched otherwise and pay the full amount, was considered an early termination of the contract and thus subject to heavy fees.

Dave Graveline told me that, while he understood how that seemed unfair to me, Verizon Wireless' policy here was essentially the same as every other wireless provider. All of them lock you up by controlling your number, because they know that your number is what you care about. If they let you move it, even if you "promise" to keep paying for the contract, once your number is out the door they have no leverage on you.

Subsequently, I noticed that Verizon Wireless TV ads were including the fact that the contract is with the LINE in their small print. I suppose, given that they are disclosing this, and given that every other wireless service provider has the same draconian policy, I have to agree that Verizon Wireless is NOT the devil, and if you want to do business with them, they are no worse than anyone else.

I do, however, still believe the practice stinks. I just can't criticize them, if no one else is any different.

Now, on to the matter of the BlackBerry Tour 9630.

Here, I have some good news. After digging around a bit in the RIM support documents, I found a page that said the Error 552 crashes had been escalated to a higher priority and a fix was anticipated soon. On some BlackBerry fan sites, I saw messages hinting that version of the operating system would fix the 552s.

For some time, we'd heard from people running the 5.x OS that the problem was fixed there, but if your carrier hasn't upgraded your model to 5.x and you're still stuck on a 4.x OS, there is little you can do. Sure, I know you can get a "leaked" copy of the newer operating system and modify the installation files so it will install on any BlackBerry model from any carrier, but I don't want to swim TOO far out of the shark cage.

On the same fan sites, I saw a method for fixing the Error 552 condition. You see, the reason Verizon Wireless can't fix it is that the phone won't boot up. Since it won't boot up, they can't connect to it with Desktop Manager to reload the system software. And that's as far as their techs would go. But it turns out that the "fix" for this is INCREDIBLY simple. Just remove the battery.

Yes, that's it. Just remove the battery. Then open the Desktop Manager on your PC and connect the USB cable. The BlackBerry won't even try to boot ( has no battery! hurr, hurr). But it WILL connect with Desktop Manager using the power from the USB cable. At that point, it's a relatively simple matter to reload the system software. There is one important tip, however. Once the system files begin to install to your phone, you must carefully put the battery back in. Don't bother with putting the cover back on until later, and do NOT do ANYTHING that disconnects the USB cable. If you fail to put the battery back in, or you disconnect the cable, you'll get to start this process over. Once the system software has loaded, the phone will reboot (that's why the battery had to be replaced!). After booting, it will connect with the Desktop Manager again and complete the process.

This, of course, wipes your BlackBerry. If you have a backup, you're okay. And even you don't, you should be syncing your BlackBerry with SOMETHING (I use Google Sync to sync with my Google Contacts and Calendar), so it's quick enough to recover that data. Having to install your third party apps again is a bit of a pain, but BlackBerry App World keeps track of the ones you've bought through them, making it easy to recover them. Any of the apps that were free...are still free. Download them again.

Between the time that I had my meltdown with Verizon Wireless and the time that magically appeared for download, I "bricked" my BlackBerry Tour 9630 with Error 552 on two occasions. Both times, I used this technique to recover and it worked perfectly. When it happened for the second time, Desktop Manager told me there was an update for my operating system. It was the magic version. I downloaded it, of course, and installed it on the phone.

Since that time, not a single error. No 552s, no 503s...nothing. The phone has been completely stable. So, I have to take back where I called the BlackBerry Tour 9630 "broken, a bad design, and a piece of crap." Yes, a LOT of them have defective trackballs. If yours does, keep taking it back until you get one that's fixed. Now that I have one that works properly, I am kicking myself for tolerating a bad one for those months that I did. And, yes, there was something about the Tour 9630 that made this Error 552 crash happen more often than it did with other models. Perhaps it was the extra memory? I don't know. But it seems that the problem is gone for good.

And if it's not, then I know how to fix it.

The question is, why don't the techs at Verizon Wireless?

No comments: