Enterprise Activation (Options->Advanced)
ALT+CNFG - Settings for Enterprise Activation
Address BookALT+VALD - Validate the data structure and look for inconsistencies
ALT+RBLD - Force a data structure rebuild
from the Options menu, type the following (No ALT+ required)
RSET - Will prompt to erase & reload for a reload of the Address book from the BES
(n.b. this will wipe all entries, but you can goto SIM Phone Book & copy entries back afterwards)
Browser
ALT+RBVS - View web page source code
Calendar
Open up a Calendar item
ALT+VIEW Inside any Calendar item Show extra info for a Calendar event
(including message ID - handy for BES log troubleshooting)
from the Options menu, type the following (No ALT+ required)
SYNC - Enable Calendar slow sync
RSET - Will prompt for a reload of the calendar from the BES
RCFG - Request BES configuration
SCFG - Send device configuration
DCFG - Get CICAL configuration
SUPD - Enable detailed Cal. report for backup
SUPS - Disable detailed Cal. report for backup
SUPN - Disable Cal. report database
LUID - Enable view by UID
SRSL - Show Reminder status log
MessagingALT+VIEW - For messages, displays the RefId and FolderId for that particular message. For PIM items, displays only the RefId.
Search Application
ALT+ADVM Search Application Enabled Advanced Global Search
Home Screen
ALT(left)+Shift(right)+Del - Restart the Blackberry (only for full-keyboard Blackberries)
ALT+JKVV - Display cause of PDP reject
ALT+CAP+ H - Displays the Help Me screen
ALT + EACE - Displays the Help Me screen
ALT + ESCR - Displays the Help Me screen
ALT + NMLL - Switches the signal strength from bars to a numeric value.
ALT + LGLG - Displays the Java™ event log.
WLAN (WLAN wizard screen)
ALT-SMON WLAN - Enable simulated Wizard mode
ALT-SMOF WLAN - Disable simulated Wizard mode
Theme (from theme menu)
ALT-THMN - Change to no theme (B&W)
ALT-THMD - Change to default theme
Date/Time (Date/Time menu - No ALT+ required)
LOLO - Date/Time Show Network time values
SIM Card (Options->Advanced->SIM card - No ALT+ required)
MEPD - Display MEP info
MEP1 - Disable SIM personalization
MEP2 - Disable Network personalization
MEP3 - Disable Network subset personalization
MEP4 - Disable Service provider personalization
MEP5 - Disable Corporate personalization
Status (Options->Status)
BUYR - Data & Voice Usage
TEST - start a device test (Keyboard, GPS, RF, Audio (Handset,headset,bluetooth, Misc)
Saturday, October 16, 2010
JVM Error 102 - Blackberry Bold 9700
I recently has an issue with my blackberry 9700 Bold. I found that my device not coming up properly and throwing an exception JVM Error 102 with a small reset button. If you click on reset button you land on same page. I found that one of the .Cod file got corrupted and the only way to recover it to wipe all your data and reinstall again.
Here are some common JVM error and their explanations:
102 -- Invalid code in file system The system has checked the .COD files in the handheld for modification, and determined that there is a problem with one or more .COD files. If all loads fail, it could indicate a build process error where there was a problem signing the codfiles. If some user action to the device caused this problem, the reset cycle will be continuous since the code in the filesystem has been corrupted. The only recovery method is to wipe the device and restore a new system
506 Uncaught Exception An uncaught Java exception was thrown in the initial VM Java thread thus ending the only live thread in the system. The eventlog contains the traceback for the exception.
507 Unsatisfied Link A dependency on a .COD file could not be satisfied because the .COD file is missing.
508 Invalid object A problem has been detected with a debugger command to the VM.
509 VM_PPO_INFINITE_LOOP: infinite loop in PPO phase of GC The maximum iteration count for the PPO phase of a GC must be the maximum number of file handles in the system. This error indicates that the iteration count has exceeded that count and hence there is a flaw in the PPO loop or a corrupted file system. The extra hex integer in the error string is the flash id of the current record where the infinite loop was detected.
What it comes down to is that the JVM 102 error means that a .cod file on your phone seems to be corrupt, so the phone refuses to load it. Why wipe everything for one bad file? You might not need to!
Another Approach is:
1) Open web browser and type www.att.com/bbdownloads
2) Select you handset device from the drop-down and click next , you will seesoftware for Bold will appear at the bottom.
3) Install As per the region you located.
4) Connect your phone to your PC using the USB cable that came with it.
5) Run the loader.exe which by default after installation lies at C:\Program Files\Common Files\Research In Motion\AppLoader.
6) while installing you have to make sure to select a radio button, which asked to you wipe your data ( I am assuming that you take continuously back up and you have your backup copy handly ).
7) If you get an exception , you need to repeat same by removing the battery.
After following above step I am able to recover my Blackberry properly.
Here are some common JVM error and their explanations:
102 -- Invalid code in file system The system has checked the .COD files in the handheld for modification, and determined that there is a problem with one or more .COD files. If all loads fail, it could indicate a build process error where there was a problem signing the codfiles. If some user action to the device caused this problem, the reset cycle will be continuous since the code in the filesystem has been corrupted. The only recovery method is to wipe the device and restore a new system
506 Uncaught Exception An uncaught Java exception was thrown in the initial VM Java thread thus ending the only live thread in the system. The eventlog contains the traceback for the exception.
507 Unsatisfied Link A dependency on a .COD file could not be satisfied because the .COD file is missing.
508 Invalid object A problem has been detected with a debugger command to the VM.
509 VM_PPO_INFINITE_LOOP: infinite loop in PPO phase of GC The maximum iteration count for the PPO phase of a GC must be the maximum number of file handles in the system. This error indicates that the iteration count has exceeded that count and hence there is a flaw in the PPO loop or a corrupted file system. The extra hex integer in the error string is the flash id of the current record where the infinite loop was detected.
What it comes down to is that the JVM 102 error means that a .cod file on your phone seems to be corrupt, so the phone refuses to load it. Why wipe everything for one bad file? You might not need to!
- Download JL_Cmder
- Connect your phone to your PC using the USB cable that came with it.
- Run JL_Cmder and select option 2 (event log)
- Scroll to the bottom of the log and look for "JVM Error 102." The line before it should tell you exactly what file is causing the error. It might look something like this. Save the file name; you will need it later.
- Go to Start > Run, and type "cmd" then press Enter.
- Change directory to the JL_Cmder installation folder.
e.g., type: cd "C:\Program Files\JL_Cmder\" and press enter - Type the following command to remove the offending file:
javaloader.exe -u erase -f FILENAME
where FILENAME is the name of the .cod file. - Disconnect your phone from your PC and restart it.
Another Approach is:
1) Open web browser and type www.att.com/bbdownloads
2) Select you handset device from the drop-down and click next , you will seesoftware for Bold will appear at the bottom.
3) Install As per the region you located.
4) Connect your phone to your PC using the USB cable that came with it.
5) Run the loader.exe which by default after installation lies at C:\Program Files\Common Files\Research In Motion\AppLoader.
6) while installing you have to make sure to select a radio button, which asked to you wipe your data ( I am assuming that you take continuously back up and you have your backup copy handly ).
7) If you get an exception , you need to repeat same by removing the battery.
After following above step I am able to recover my Blackberry properly.
Subscribe to:
Comments (Atom)