11-27-2013 03:50 PM
Experiencing this for a week now, no solid reply through twitter from BBhelp.
I get use the music or games backdoor to get in, but nothing through the mainscreen.
Updated to OS 10.2.0.429 today to no avail.
There seem to be some backdoor options , like fiddling with content controls etc. tried all this, nothing helps.
Anyone on here that has a solution except a complete wipe and reinstall, which was common practice with my previous Bold9700 and which i hoped would not continue into the Z10.
Already 2nd phone, 1st one locked SIM cards randomly so this one was kept by BB UK support and i received a new one, all went well untill this quite familiar problem (seeing the posts on internet) popped up.
Done a full back up this evening just in case, but i remember the hassle i had with the 9700 which had a java error and frooze like every forthnight.
Any help would be more than greatly appreciated.
Solved! Go to Solution.
11-27-2013 05:27 PM
Welcome to http://supportforums.blackberry.com/
You just made an update to OS 10.2.0.429
I recommend that you restart the z10 for the blackberry world works.
If the problem persists apply a hard reset by pressing the volume button + and - and the power button for 30 seconds.
11-27-2013 05:36 PM
11-27-2013 06:05 PM
Apparently it's signal problem
Try to access the blackberry world connected to a wi-fi network
11-28-2013 12:27 AM
11-28-2013 06:51 AM
I have exactly the same problem as JanBroersma is experiencing. I tried to solve it with by installing a backup (October) but no change:
BBW cannot be reached!
So I request a bit of proper support, please....
11-28-2013 09:07 AM
The following is not really a solution but a temporary fix. Download the following BlackBerry World bar file en sideload this on your BlackBerry. This a an official BlackBerry World bar file. But we still have to wait for a real fix.
HowTo sideloading: http://www.bbhub.nl/4330/how-to-sideloaden-via-de-
11-28-2013 09:52 AM
Thanks, I will try, although sideloading is not really my cup of tea.
By the way, I saw on the t-mobile.nl customersupport-forum that there are some fellow-victims struggling with this "bug".