sharatf

Ok. So I've done some research on this and thought I'd put it on the forum here in case anyone else faces a similar problem. If you get error codes 535/547 then in all likeliness you're looking at a hardware failure The flash memory module is been almost permanently corrupted. Your only option is to get the handset replaced. Regards, Sharat

Hi, I've been facing an irritating problem with my recently acquired BB 8830 (Verizon) The phone belonged to a friend who'd just came down from USA, and was in a very good condition, physically. Unfortunately, for my friend, while upgrading his BB OS thru the Desktop Manager, it got stuck and had been showing him 507 Error. He wasn't keen on fixing the problem (didn't know how to go about it) so I offered to buy it at a good price (for me ) So let me breakdown the whole issue from here on: As most of you know, 507 error means there's no OS in the phone. So I went ahead and downloaded the latest DM and 4.5 OS (4.5.0.138) from the Blackberry & Verizon sites, respectively. Using only the AppLoader (not thru DM) I managed to access the BB and loaded the OS successfully, although I must mention that when it tried to reboot itself it went into a loop. I just pulled the battery & rebooted the system and it showed me the "Verizon Wireless" welcome screen and went to the home page without any issues. I setup the phone (without email) and was very happy about it all, until it suddenly rebooted itself 10 minutes later & went it a reboot loop without ever booting up Once again I pulled-battery-restarted the phone for it to get back to the home screen, but 10 minutes later it went into a loop again. Thinking that the OS maybe the issue, I upgraded the OS to 4.5.0.175 thru the DM. Same success story as the previous attempt and I was at the Home screen soon. BUT the reboot loop came back So this time I downgraded the OS to 4.2.2.196 from Tata Indicom thru the App Loader. Again it was a successful load and everything seemed stable for nearly 20 mins when it went to the reboot loop again The different BB OS I've installed in order are: Verizon 4.5.0.138 thru App Loader Verizon 4.5.0.175 thru Desktop Manager upgrade Tata Indicom 4.2.2.196 thru App Loader Over this entire course, I've also encountered the following errors: JVM Error 535 JVM Error 547 App Error 523 App Error 524 App Error 200 Each time I just pulled-battery-restarted the phone to correct the errors. The biggest problem is the phone can't seem get out of it's own reboot loop unless I pull the battery. I'm worried there may be a hardware problem, but not sure what to do. As it stands, I'm stuck BIG TIME! :'( Could someone please help me out on how to rectify this instability of my BB 8830? Thanks in advance.

Hi, Thank you all for your prompt responses. It's helped me understand the system a little better I've also read elsewhere in this forum that and easier way to activate my Droid on Tata Indicom would be thru Prepaid rather than Postpaid connections. Is that true? Also, does anyone have an idea on when Reliance will start accepting phones like my Droid? Thank you all once again. Truly appreciate it

Hi, I recently returned from USA along with my much loved Motorola Droid. I was under the impression that CDMA operators (Reliance, Tata, MTS, etc.) here will accept foreign ESN phones, so was very excited about the same. But I've been facing problems on this front for the past couple of weeks ever since I started approaching all the operators here in Kerala. Reliance folks said that they don't accept foreign ESN at all. But the Tata guys were much more receptive. They were ready to load my phone on their network. Unfortunately, when they tried to load my ESN, they said that it's not in their database and could not be done As an alternative, they said they were willing to give me another ESN (from their database - some scrapped phone), which I'd have to change on my Droid myself, and they'd activate the same. But as some of you may already know, this can't be done (so far) on the Moto Droid. I humbly request the "Masters" of this forum to help me out with a possible solution to get my droid working on ANY of our CDMA networks. Thanks