JVM Error 529...?

[Krypto]

Psychosys, you don't need to exchange the phone, however if it keeps up, my guess is that you have a bad app installation. You can try reinstalling your apps, or if that doesn't help, you can try reloading or upgrading your OS.

[PassTheSunChips]

Curve 8530 working fine since Dec.
Installed Bloomberg Mobile yesterday.
Spontaneously rebooted today and I got the 529 error.
Able to boot past that, but my media card was then not recognized.
Tried rebooting, pulled battery, no luck.
Pulled media card (while powered on) and reinserted, it now comes up.

[chechencreative]

Originally Posted by Shlooky

try this... pull the battery, wait 5 seconds, put the battery back in and when it's booting, press and hold the escape key.
This will boot your Storm in safe mode, perhaps there is an app that is corrupted or something. If it does boot, your OS should be fine.

hello guys, my nameis George, i search solution for cod ERROR 529, and you post
i used for me for anwer my Problem jajaja Yeah man my 8320 BB is live, That fine man Thanks.

[blackbob919]

This error results when the blackberry is powered off without being shut down properly. The filesystem is not saved to flash in a consistent state. Just as you shouldn't power off your PC without first shutting it down same goes for the blackberry. When you reboot 529 is displayed when it detects such a dirty filesystem. It then attempts to recover the filesystem (just like your PC) and usually can do it with no problems. But (just like your PC) sometimes it can be beyond repair and a format is required.

So don't pull the battery without powering off first. It's a quick way to reboot yes and you might get away with it many times but eventually you will be learning all about the reformat feature.

[DJM1947]

Originally Posted by blackbob919

This error results when the blackberry is powered off without being shut down properly. The filesystem is not saved to flash in a consistent state. Just as you shouldn't power off your PC without first shutting it down same goes for the blackberry. When you reboot 529 is displayed when it detects such a dirty filesystem. It then attempts to recover the filesystem (just like your PC) and usually can do it with no problems. But (just like your PC) sometimes it can be beyond repair and a format is required.

So don't pull the battery without powering off first. It's a quick way to reboot yes and you might get away with it many times but eventually you will be learning all about the reformat feature.

Although this could be one of the causes for the 529 error, your statement makes it sound like it is "the" cause. Many times this error appears following a random self reboot by the phone often caused by conflicts between different applications.

[blackbob919]

Originally Posted by DJM1947

Although this could be one of the causes for the 529 error, your statement makes it sound like it is "the" cause. Many times this error appears following a random self reboot by the phone often caused by conflicts between different applications.

A reboot is in effect the device powering itself off and back on again. From the blackberry OS perspective there is no difference. "This error results when the blackberry is powered off without being shut down properly." An unplanned reboot, whether due to the OS panicking, hardware failure or for whatever reason, is not a proper shutdown. Just as pulling the battery is not.

[DJM1947]

Originally Posted by blackbob919

A reboot is in effect the device powering itself off and back on again. From the blackberry OS perspective there is no difference. "This error results when the blackberry is powered off without being shut down properly." An unplanned reboot, whether due to the OS panicking, hardware failure or for whatever reason, is not a proper shutdown. Just as pulling the battery is not.

Although what you propose may be a possible outcome, the probability of it occuring is extremely small. There are literally millions of blackberries being rebooted each day (sometimes multiple times for individual devices) by a battery pull or software such as quickpull, but only a few instances of 529 errors.

Additionally, what I was pointing out is that software conflicts often account for the reboot, not a battery pull. I suspect that the software conflicts may be more of a cause for the error than the reboot itself.

[blackbob919]

Originally Posted by DJM1947

Although what you propose may be a possible outcome, the probability of it occuring is extremely small. There are literally millions of blackberries being rebooted each day (sometimes multiple times for individual devices) by a battery pull or software such as quickpull, but only a few instances of 529 errors.

Additionally, what I was pointing out is that software conflicts often account for the reboot, not a battery pull. I suspect that the software conflicts may be more of a cause for the error than the reboot itself.

The probability of getting a 529 error if you pull the battery before the OS has had a chance to completely write memory resident persistent objects to flash persistent store is not extremely small, it's a certainty. That is why the battery should not be pulled to reboot a running system in general, since a busy app could be dumping objects to the store at any time, but it's an especially bad idea to do it while in the process of installing software or updates or syncing with the desktop. Just because people pull battery to reboot all the time doesn't make it wise. The only time I've had to do it was when the OS was unresponsive in which case there's no alternative.

I've seen the 529 error a number of times. I've seen it when a forced update from my carrier failed to install correctly requiring me to pull and I've seen it when I had a flaky battery that caused frequent unplanned reboots. In each case there was a failure to shutdown properly that resulted in an object inconsistency in the store. I know that was the result because that's what the 529 error means.

You guys can speculate about software conflicts and other exotic theories all you wish, but I've explained what 529 means and how it can be evoked for the interested.

[DJM1947]

Originally Posted by blackbob919

The probability of getting a 529 error if you pull the battery before the OS has had a chance to completely write memory resident persistent objects to flash persistent store is not extremely small, it's a certainty. That is why the battery should not be pulled to reboot a running system in general, since a busy app could be dumping objects to the store at any time, but it's an especially bad idea to do it while in the process of installing software or updates or syncing with the desktop. Just because people pull battery to reboot all the time doesn't make it wise. The only time I've had to do it was when the OS was unresponsive in which case there's no alternative.

I've seen the 529 error a number of times. I've seen it when a forced update from my carrier failed to install correctly requiring me to pull and I've seen it when I had a flaky battery that caused frequent unplanned reboots. In each case there was a failure to shutdown properly that resulted in an object inconsistency in the store. I know that was the result because that's what the 529 error means.

You guys can speculate about software conflicts and other exotic theories all you wish, but I've explained what 529 means and how it can be evoked for the interested.

I understand what you are saying, but disagree that is is mostly due to a battery pull. For example, if you read the posts in this thread most of the 529 errors are resulting from spontanious reboots that seem to result from software issues. Many of the people have been able to isolate the issue to specific software installations within the previous 12 to 24 hours.

I have had various blackberries since 2002 and performed battery pulls or quickpull type reboots during that time and never experienced a 529 error. In the 22 months that I have had my 9530 (the same phone) I have performed a battery pull or quickpull on average at least once a week and about two to three times following an OS installation. I have installed virtually every OS for the 9530 since the original 65 and many hybrids. Although conceptually your premis sounds plausable, I still believe the risk is so low that a battey pull can be considered safe.

Why on earth would someone pull the battery in the middle of an update, app installation or while syncing or connected to DM?? Some common sense is called for in this life!!