12-31-2013 02:41 PM
Only solution the worked for me was for Blackberry to authorize hardware repair in Tennessee (uner warranty). Since you have a used model, that may not work. Worth contacting BB to request that. NO software upgrades from Desktop seemed to work either. However, so software improved the service but not solve completely. NO one discloses what exact hardware has to be changed.
01-01-2014 08:16 AM
Blackberry support will not give me any complimentary help and referred me to paid 'incident based support'. This would almost certainly cost more than the price of a new smartphone or tablet if they recommend returning it for repair so I'm not inclined to go there.
I'm currently exploring other options such as using autoloader to load earlier versions of OS as described on Crackberry site. One thing is not clear yet, do I need to put PB in developer mode before using autoloader? I obviously can't do that as it is not booting fully yet. Still, at this point I don't have much to lose so I'll just try it.
02-27-2014 08:10 AM
I hadn't looked at the playbook since my last post 2 months ago but decided to have one more attempt to salvage it before buying a cheap generic Android tablet. I'm pleased to say that I now have a working PB again. I'm adding this post as it may be relevant to others with a similar problem.
The PB had been turned off for nearly 2 months. I plugged in the rapid travel charger and it displayed the flashing green led indicationg charging, something I had not been able to achieve earlier. It was left in this state for 48 hours and then switched on. It was still failing to boot. I then used the command line utility CFP.EXE with the command "cfp nuke" which clears setup data. The PB then booted and went through the "as new" setup menus. Part way through the os update process it paused with a message saying there was a low battery and setup would contiue when 20% charge was reached.
At this point I scoured the forums again and came across a post for the same problem where someone had disconnected the battery cable from the pcb (two tiny screws), re-connected and the level had jumped to 100%. They put it down to apoor connection. I tried the same thing - and it worked!
My conclusions from all this are:
The setup information was corrupted, possible due to battery failure part way through setup.
The PB was unable to boot in this state.
The battery charging software is unable to work from a low charge which is a well documented fault..
The battery charging software has a bug which can prevent it giving the correct battery level after an OS update..
I think disconnecting and re-connecting the battery connector may reset the battery level indicator to read the correct value of 100%. I think this is more likely than a poor connection.
I still think I may have a problem with battery charging and/or level indicating. It took 12 hours to go from 86% to 87% on the "rapid charger". I just repeating the exercise with the USB charger.
Hope the above can be of use to someone. Incidentally, I find the best way of removing the back cover is to use an old credit card with an edge filed to a wedge profile.
02-27-2014 11:36 AM
I have seen the romavale of battery connector and re connect fix a few PlayBooks.
BESAdmin's, please make a signature with your BES environment info.
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V