08-01-2012 05:59 PM
I am using a Sprint Blackberry Bold 9650 from America on Vodacom in South Africa. I have been using it for a year without any problems. Afew days ago, randomly, I wasnt connected to BIS. I have tried EVERYTHING. The first time i spoke to a Vodacom Consultant, she told me to do a battery pull, didnt work. Also went to Host Routing Table, didnt work. Eventually she said i must update my OS. After i did this, im even worse off. Now there are no entries in the Host Routing Table and i only have 5 service books.
I have cleared the Event Log and done a security wipe. I also downgraded back to the OS i was using.
I have called Vodacom numerous times and done everything they have suggested. Now this evening, one of their consultants said he couldnt send me the Service Books and that they do not support my model on the GSM network because it was brought in from America (but it has been working for more than a year?!)
Please, do you have any suggestions of what i can do? Vodacom doesnt want to help me because the phone wasnt sold to me by them, even though They are supplying me with my BIS and airtime...
Solved! Go to Solution.
08-01-2012 06:35 PM
Please understand that this is a volunteer-supported, user-to-user community...as such, everyone also has lives to live...it is considered customary to wait 24 hours before "bumping" your thread.
In any event...you have a significant challenge ahead. From all I can tell, your BB model is not natively supported by the Vodacom SA network. Which means that their network will not deliver the proper Service Books to your BB so that it can function on their network. And, for some reason (there's no way to know "why"), those are gone from your BB, which is why it no longer works.
What to do? Well, unless the 9650 was supported by them a year ago, then some "magic" was worked by someone to get it to work on their network. That magic needs to be worked again. Basically, you have to find a working (on the Vodacom SA network) BB and extract the SBs from it, then import them to your BB. And, even then, there's no guarantee that it will work at all. It can be quite challenging to use a non-native BB on a carrier network.
Again, there's no way to know why it stopped working...only that it did, and from what you describe, it's the fact of missing Service Books that is the culprit.
08-01-2012 07:03 PM
08-01-2012 07:09 PM
08-01-2012 07:24 PM
08-01-2012 07:34 PM