Another bricked bold.

So far so good with my Bold after 1 week today.

However my wife wanted one and decided to get one on Tuesday. Well last night she got the JV 517 error. So that's it her Bold is dead. She had some grief off Rogers with getting a replacement which I dont see how they can give any grief when it's so new. However a replacement will be obtained today.

I read a post on here regarding the soft reboot as a possible cause. My wife generally always does a soft re boot. I am wondering if this could be related. I have only ever done a battery pull on mine so far. I did try to do the soft re bott the other day but it wouldn't and so I resorted to the battery pull.

I'm yet to see if this is one of the common errors but apparently is caused by a corrupt flash memory.

I had the same issue last night.

I bought a new 9900 last Friday. Mine was stolen the night before.

I did a soft reset, and then the error JV 517 came up. Wouldn't reset, so i had to wait until i got home. Plugged it in and it reloaded with BB desktop manager.

I called rogers to see what the deal is and the rep was very helpful.

This error means the hardware is defective, they should replace the phone right away.

If its within 30 days they should send you a brand new one, if over 30 days they will send you a refurbish (still pretty much brand new)

He sent it out today and i will get it next week. He said the Mexico 4 phones are often defective.

I just got it last week and called the store i bought it from and he said he could only send it out for repair. The Rogers rep said i could of gone to any store and they would replace it on the spot. They classify it DOA if this happens within 30 days.

Hope this was helpful.

Good luck.

thanks

I don't like the sound of that. The box on my UK phone is Mexico 4 :( I will keep my hopes up.

I've done more of those than physical battery pulls due to using an a case that's difficult to remove and put back on, as well as the battery door being rather difficult to pry off.

That being said, I did a soft reset once and had to reload the device OS after it went into a reboot loop. Soft resets are not the cause but will allow the problem to manifest itself, thereby giving the impression that it (soft resetting) could be the cause.

Sorry for your loss