LGVX6000 got powercycled and not restarting | developer.brewmp.com LGVX6000 got powercycled and not restarting | developer.brewmp.com

Developer

LGVX6000 got powercycled and not restarting

Forums:

I got a serious issue.
My application crashed on VX6000 and it powercycled. It turns on but its getting stuck on Verizon splash screen. Could anyone please explain what to do.
I tried removing battery and inserting it after 10 mins, I tried charging the phone, but still it is getting stuck on the first screen.

Since I'm here in India, I cannot get it repaired. I'm running on a deadline for submission of project, getting a replacement or repair will delay it.

Please tell me if is there any other way to fix it.

Thanks

I got this problem a while back. It happened when we were writing to a log file for debuggin. I guess the file got to big and crashed the phone.
After that we couldn't get the phone to get past the Verizon splash screen. We tried everything possible, but couldn't get the phone to work ever again.
We finally gave up and decided to buy a new VX6000.
It's one of the many, many problems and set backs for the VX6000. Not only is it REALLY slow, but the memory heap is at 350K(OS takes 150K), and it breaks really easily.

I got this problem a while back. It happened when we were writing to a log file for debuggin. I guess the file got to big and crashed the phone.
After that we couldn't get the phone to get past the Verizon splash screen. We tried everything possible, but couldn't get the phone to work ever again.
We finally gave up and decided to buy a new VX6000.
It's one of the many, many problems and set backs for the VX6000. Not only is it REALLY slow, but the memory heap is at 350K(OS takes 150K), and it breaks really easily.

Hi,
I also faced the problem a year back. Finaly i went to buy a new phone.

Hi,
I also faced the problem a year back. Finaly i went to buy a new phone.

My VX6000 was recently bricked too - after getting an error while using the AppLoader. C'est la vie

My VX6000 was recently bricked too - after getting an error while using the AppLoader. C'est la vie

I'm also getting a similar problem in Motorola V710. Any Idea how to recover?

I'm also getting a similar problem in Motorola V710. Any Idea how to recover?

usually the EFS gets corrupted and the phone gets stuck in a loop, requiring a reset of the EFS, which qualcomm might be able to do or some helpful verizon store, they can reset the devices EFS to a default state, if its not completely frozen.
minimize writing to the phones EFS as much as possible, as well as the number of apps, i found out the hard way a few years ago, if you put more than 20 apps or so on the 6000, it takes so long to boot up the watchdog kicks in and resets it, so it never restarts.

usually the EFS gets corrupted and the phone gets stuck in a loop, requiring a reset of the EFS, which qualcomm might be able to do or some helpful verizon store, they can reset the devices EFS to a default state, if its not completely frozen.
minimize writing to the phones EFS as much as possible, as well as the number of apps, i found out the hard way a few years ago, if you put more than 20 apps or so on the 6000, it takes so long to boot up the watchdog kicks in and resets it, so it never restarts.

charliex wrote:
minimize writing to the phones EFS as much as possible, as well as the number of apps, i found out the hard way a few years ago.
Yet True Brew Testing requires us to load the phone with files until the EFS is full to create the environment where file writing and reading loses integrity. Thus giving us the possibility of bricking the phone and having to spend more money buying a new phone while the phone companies reap the benefits.
If only there was a BREW api function that can tell us whether reading/writing is possible or not. That would make everything so much easier for all of us.

charliex wrote:
minimize writing to the phones EFS as much as possible, as well as the number of apps, i found out the hard way a few years ago.
Yet True Brew Testing requires us to load the phone with files until the EFS is full to create the environment where file writing and reading loses integrity. Thus giving us the possibility of bricking the phone and having to spend more money buying a new phone while the phone companies reap the benefits.
If only there was a BREW api function that can tell us whether reading/writing is possible or not. That would make everything so much easier for all of us.

yep maxfiles is not a good tool, there are other ways to test low space and failed file functions.

yep maxfiles is not a good tool, there are other ways to test low space and failed file functions.