08-05-2013 10:18 AM
I have a Torch 9800, ever since I upgraded the OS (6.0 bundle 2647) the Appworld works sometimes directly after a re-install - but mostly does not either then or at all. The icon is there, both in home directory and 'switch application' directory, but selecting it brings me back to home screen. I've done a hard reset, rebooted, deleted and re-installed, all in various combinations and still the same.
So I can't update or add any apps, which is very frustrating! Any ideas? Can I take the OS back, if so how?
08-05-2013 02:33 PM
Hi and Welcome to the Community!!
I cannot tell for sure if you have done EXACTLY this sequence:
1) Remove AppWorld from your BB
2) Do a Batt-Pull reboot (power on, remove battery, wait, insert battery, wait), even if redundant to the one you did in step 1.
3) Install (on your BB) a fresh copy of AppWorld
4) Do another Batt-Pull reboot
5) See if it now works.
You also might try Safe Mode to determine if some other app is interfering:
It may take you multiple attempts to get the ESC key sequence (press/release/hold) correct, so be patient. When successfully into Safe Mode, see what happens.
If the behavior ceases, then think carefully...what happened just before this behavior started? A new app? An update? A Theme? Something else? Think carefully as the smallest change could be causal...and attempt to undo whatever that was.
But if the behavior continues in Safe Mode, then you may need to consider more drastic actions -- WIPE, OS Reload (in case the update you did got somehow corrupted), BBSAK Wipe/Reload, and the "Bare Bones" OS Reload Process. To prepare, you should be sure that you have a full backup to your PC...please review the Backup link in my auto-sig on this post for instructions.
Good luck and let us know!
08-05-2013 04:34 PM
I experienced the same issue with my Torch during the last 2 years installing different AW versions. I believe the issue is not with AW but somehow some app on my phone is starting AW during a reboot. BlackBerry would surely have figured this 2 year old issue out but they can’t duplicate this issue without the offending app present and I have too many ones to see which one is the offender. It looks like many Torch people sit in the same boat like us, i.e. have the same app present causing this issue.
So here is my 40 minute work around which is a wipe but with auto restore of all data and apps. It will also fix non appearing AW icons or unresponsive icons when battery pulls and reinstalls of AW fail.
Make sure you have loaded the AW version of your choice with any of the icon issues present.
Here were my initial conditions:
I did not run any other programs on my PC while I updated my BB phone.
I had installed the newest DTM (Desktop Manager) software, e.g. 7.1.
I had a copy of my current device software on my PC, e.g. OS 18.104.22.1686.
I made a full backup of my current data and apps.
I had installed the newest AW version, e.g. 22.214.171.124 but with any icon issue present .
I copied important BBM messages because they will not be restored and saved associated pictures.
Here is my work-around story.
I selected 'Update' on DTM under 'Device' on the home screen getting this message:
An updated BlackBerry Desktop Software component must be installed before you can continue.
(If you did not get this message jump to 'I reconnected my phone..." below.)
I selected ‘Install’ and then a Windows Installer Window popped up.
Please wait while Windows configures BlackBerry Device Software Updater.
Existing BlackBerry software has been detected on your computer and must be closed before proceeding. Disconnect your device and click OK to close the applications. Otherwise click Cancel to stop the installation.
I disconnect my phone and clicked OK.
DTM retired and then restarted after the BlackBerry Desktop Software component installation was complete. (If not, restart it yourself).
I reconnected my phone and selected 'Update' on DTM under 'Device' again on the home screen. Then I got this message:
There are no BlackBerry Device Software updates available. (Good, I was up-to-date).
I unchecked 'Keep me subscribed to email notifications' and selected 'View other versions':
I selected 'Install' using the currently installed version with the default checkmark beside it.
Now I had to wait 30 minutes till I got an ‘Installation complete’ message.
I disconnected my phone and made sure my radio was back on (usually it is turned on by the restore process but sometimes it is not). I then followed the start up sequence and then found a ‘working’ AW icon which I selected. I skipped the AW reboot request and went straight to update my BBID. (You need the radio on to get success with BBID registration). I rebooted and all was well.
You might have got a message of a ‘corrupt back up file’. BB means the 'back up file for your BBM' because your BBID is not loaded yet. Ignore this message it will disappear after your BBM is up and running. It is not the data backup file of your phone which is corrupt but the BBM contact file which your phone will recover from the BBID cloud location later.
I hope this will method will help with resolving your icon issue. Unfortunately, if you download more apps and have to reboot the above icon issues might reappear and one has to spend another 40 minutes again. This method is a work-around not a fix for this issue. Anybody out there with a know-how to fix it let us users know!
In the meantime I am waiting for the new BB10 Torch (A10, Z15, you name it! ). I hope for a big 5" screen with a slick keyboard. XMAS is coming soon and many Torch contracts will expire ....till then ....work around.....
08-07-2013 06:47 AM
Tried the 1st options suggested, AppWorld continues not to work in full or safe mode. So I'll give the 2nd solution a go.
It all started when I updated the OS to current version, so I'd like to take it back to original OS version, any ideas on how that may be achieved?
08-07-2013 09:30 AM
I can't tell you what OS level you had before, nor what level you have now. But I can give you a process to install whatever you desire, if you can determine what that is.
Please refer to this official download portal as you proceed. It is sorted first by carrier -- so if all you want are the OS levels your carrier supports, your search will be quick. However, some carriers are much slower than others to release updates. To truly seek out the most up-to-date OS package for your BB, you must dig through and find all carriers that support your specific model BB, and then compare the OS levels that they support.
From a PC, you can install any compatible (e.g., for your exact BB Model Number) OS package to a BB via this procedure:
Note that while written for "reload" and the Storm, it can be used to upgrade, downgrade, or reload any BB device model -- it all depends on the OS package you download and install to your PC. After installing the OS package to your PC, please remeber to delete, on your PC, all copies of VENDOR.XML...there will be at least one, and perhaps 2, and they will be located in or similarly to (it changes based on your Windows version) these folders:
Be sure that you remove, from your PC, any other BB device OS packages as having more than one installed to the PC can cause conflicts with this procedure.
You may also want to investigate the use of BBSAK (bbsak.org) to perform the wipe it is capable of.
You may also want to try the "Bare Bones OS Reload Procedure" to attempt to narrow down the precise causal item:
When the behavior presents, you know the culprit...the last thing you loaded.
If the behavior does not re-present, then you know that either step 1 or 2 cured it.
If the behavior presents no matter what, then you likely have a hardware level issue for which no amount of OS or software can cure.
You may also need the use of these tricks:
If you are on MAC, you are limited to only your carriers sanctioned OS packages...but can still use any levels that they currently sanction. See this procedure:
Good luck and let us know!
08-07-2013 11:11 AM
My procedure suggests to install the 'current OS version' in Line:
"I selected 'Install' using the currently installed version with the default checkmark beside it."
However, if one has other OS versions loaded on one's PC one can select any other version before one hits the 'Install' button.
So follow the advice from sdgardne to get the OS version of your choice and select it instead of the 'current version' once you get to the window with the 'Install" button.
I also had AW issues with OS6 Bundle 2467 and now Bundle 3049 but never went back to try older Bundle 2391 or 695 versions available with my ISP Bell which I certainly will try out the next time the AW icon screws up again.
You might have a point that your previous OS version was not affected by newer AW versions. Try it and let us know.
08-08-2013 04:31 AM
I spent far too long with the thing last night, however it now works!
Following the various trains of thought and advice here the eventual solution was to re-install an earlier version of operating system. It seems that there was a conflict between my carrier and the operating system that had got installed, so installing the latest carrier OS (seen as a downgrade by the system) cured it. Now it all works as it should.
It has also cured some other symptoms I hadn't recognsed, like the touch screen not being enabled to select contacts' different phone numbers.
So thanks guys for your attentions, it certainly guided me in the right direction.
08-08-2013 09:43 AM
It seems that there was a conflict between my carrier and the operating system that had got installed, so installing the latest carrier OS (seen as a downgrade by the system) cured it.
That would be quite strange indeed. As long as the OS package is, per the filename, intended for your specific device model number, then you should be able to use any OS package from any carrier...there is nothing magical about the OS package coming from your carrier rather than another.
Rather, what I would deduce is that there may have been something wrong with the OS package you installed...either it had a problem during the install (happens quite frequently), or the package itself had an issue (quite rare, but not impossible). The "bare bones" process above was intended to allow you to find, from any carrier, the newest OS package you could find that could run stably.
But, in any event, you found something that works well enough for you, and that is success.