On Fri, Mar 07, 2008 at 05:56:55AM -0500, Michael Miller wrote:
> I found several webpages about this and apparently RIM has a standard
> response, "A critical Java process has terminated, and the device cannot
> continue to operate in a normal manner."
> Here is a link to a thread on pinstack:
> 
> http://blackberryforums.pinstack.com/1326-jvm_error_523_-_need_help.html

I'm afraid I haven't run into this 523 error before, so I probably won't be
much help to you.

Have you tried all the Windows tools?  Can you connect using the Blackberry
Desktop software?  Can you do a backup from there?  If so, you should be
able to run the strings command on the backup file (.ipd file) and retrieve the
information you need that way.


> I need to see if I can get the address book DB off my black berry.  I error
> out of barrybackup with:
> GUI:
> *Error -101 Timeout in usb_bulk_read
> *
> terminal:
> 
> *Bad packet size. Packet: 26. DataSize(): 26. Required size: 44
>     00000000: 00 00 1a 00 09 ff 00 07 52 49 4d 20 44 65 73 6b  ........RIM
> Desk
>     00000010: 74 6f 70 00 00 00 00 00 02 00                    top.......
> 
> Barry::BadSize caught in ScanAndConnect: Bad packet size. Packet: 26.
> DataSize(): 26. Required size: 44
> Controller: error setting desktop mode
> Sent packet:
>     00000000: 00 00 18 00 07 ff 00 07 52 49 4d 20 44 65 73 6b  ........RIM
> Desk
>     00000010: 74 6f 70 00 00 00 00 00                          top.....
> 
> Response packet:*


This error usually occurs for me (or something similar) when the device thinks
it is already in Desktop mode.  Replugging the device is how I fix it, but
obviously that doesn't sound like a solution for you.


> This is the same error I get with btool and all of the commands. Bcharge can
> find and reset the voltage and btool can connect to the device and (attempt)
> to read the data, but it always gives the packet size error.  Breset just
> fails the reset.
> 
> Do you guys have any idea about this or how to proceed?

I believe that the Windows Desktop software is still your best bet for
handling unusual protocol situations like you're experiencing.

Sorry I can't be more help.

- Chris


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Barry-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to