[Reed McLay]

Several members have reported this error message when attempting to recover a non-functional device.

We need the combined intelligence of our membership to address this problem.

The message occures midway through a forced OS download using the /NOJVM switch when using AppLoader.

Has anybody seen a resolution to this issue?

edit:

I have had this same problem with my 8130. but i was able to finally get it to connect what i did was i left my battery out of my bb until it switched from load jvm and system software to wait for device initalization. as soon as it switched from one to the other i put my battery back in the bb and it finished loading.

I hope this may help others as it did for me and if not i just thought i would pass along this bit of information

[Reed McLay]

...My BB was immersed in a neighborhood swimming pool for approximately 5 seconds. Livid at myself, I panicked and tried to turn it on; Nothing. I then proceeded to remove the battery, sim card, & sd card and let it dry on a table in the heat. When it was time to go home (approx. 20 later), I wrapped all of the pieces separately in a towel. Upon arriving home I laid all the pieces out to let them dry. After a couple of hours (STUPID!, I know) I tried to turn it on again. I got the alternating blinking lights and the white screen with the hourglass. The hourglass ran for several minutes and not sure what was going on, I turned it off and turned it on again. Again, the white screen and the hourglass. After it ran about five minutes I repeated the same. This time it would not come on. It was at this time that I found this forum. I took the battery and cards out again and sealed them in a ziploc bag with those 3 of those packets used to keep medications/etc. dry in storage/shipment. The ziploc bag I then placed in a tupperware container. I let this set for a couple of days. After putting everything back together, still nothing. Black screen, no lights. I tried my wife's battery, still nothing. I put my battery in her BB and it worked just fine. So, evidently the battery is okay. After reading more of this forum and others on this site, I decided that it must have shorted the last time I turned it on. Hopeless, I was about to give up. Then I was just messing around with the battery and I got the light to blink. After some more playing around, I have gotten it to stay solid. However, neither the application launch or the desktop manager can find it still.

Is there any hope? Does the fact that the light comes on now mean ANYTHING?

Thanks in advance for any guidance you can offer.

... ... ...

[Reed McLay]

...
With the 8100 I have that was just laying around, seemingly Kaput, and that was having this cycling on/off situation I thought what the heck I'll take another stab at it with the 4.6

When I grab the USB connection at the beginning of the install, which then finally stops the phone from cycling, I then carry on. When I get to the "Updating your device" dialogue box I watch as it completes the: "Load JVM and system restore" while "erasing previous applications" and then the "loading software" processes.

Then as it wants to move to the next line: "Wait for device initialization"...

the 8100 now resumes it continuous loop on/off (power-up/power-down) routine. The PC repeats and repeats it's typical USB connect/disconnect sound.

The status indicator at the bottom of the dialogue box reads: "Connecting to JVM"

Finally it gives up (ie: gives me the finger) and reads: "Unable to reconnect to the device during a multi-stage load operation.

It would be great to revive the Berry, though if it's time to bury the berry then so be it.

Thanking all! If there is a fix or work-around then I'm willing to try again...

--------------

Just tried it one more time, same result...

... ... ...

[Reed McLay]

Same with PVT and Slackberry, help please!

... ... ...

[Reed McLay]

Trying to restore my os on bb 8330 ... following your instructions... once I've used the app loader and select the installs I want I get the following message "unable to reconnect to the device during a multi-stage load operation"

... ... ...

[PvT]

Thank you Reed for the new thread.

Seen many posts in two other threads with people having had the same problem half way through the re-install. ie: Recovering a dead Berry (by you) and Kevins 101 on operating system reload.

My quick recap: In some of our cases an issue where the phone cycles on and off, allowing for a one second opportunity to gain a USB connection in order to proceed with the install. Unfortunately ending at the "Wait for device initialization"... & "Connecting to JVM" stage where the phone jumps back into it's continuous on/off loop.

Would be interesting to hear if anyone resolved it and then, in their celebration, never got around to posting the fix.

Let's give these BB's another chance at life.

Thanks again,

Peter

[Branta]

@Reed@PvT With the 8100 I have that was just laying around, seemingly Kaput, and that was having this cycling on/off situation I thought what the heck I'll take another stab at it with the 4.6

Is there a clue here? 8100 with 4.6 (Bold OS?) PvT might be able to confirm whether that is fat fingers in the original info, or really a flaky and desperate alliance of OS and device.
Could we be looking at a new message which replaces more familiar text in the older builds?

[PvT]

branta: Is there a clue here? 8100 with 4.6 (Bold OS?) PvT might be able to confirm whether that is fat fingers in the original info, or really a flaky and desperate alliance of OS and device.
Could we be looking at a new message which replaces more familiar text in the older builds?

Oh, the 4.6 reference was to an earlier suggestion of using the 4.6 desktop software with XP, not the device software. Thanks for checkin though, all input is appreciated. Could always be missing something. ie: the quote below.

I'll be trying again this afternoon with some new suggestions the FM aka: RM, has posted here.

Thanks!

[Reed McLay]

Unable to reconnect ...

It helps to go directly to the source.

BlackBerry Technical Support has published a paper addressing this issue.

The root cause may be in the USB post device properties.

[Branta]

Just a note that some notebooks have a low power limit to the USBs. Dell used to be well known for current limiting (I think 5mA at 5v), and probably a few others have similar restrictions. Might be worth a try on a proper desktop computer with more robust USB power handling.

[Pete6]

Just a note that some notebooks have a low power limit to the USBs. Dell used to be well known for current limiting (I think 5mA at 5v), and probably a few others have similar restrictions. Might be worth a try on a proper desktop computer with more robust USB power handling.

The USB spec is actually 500mA (half an AMP) at +5Volts. You point is nonetheless valid.

[Branta]

The USB spec is actually 500mA (half an AMP) at +5Volts. You point is nonetheless valid.

That was exactly my point. IIRC the USBs on some notebook machines were current limited way below the full spec, I had 5mA in mind but that might be confusion with the 500mA spec.

I think (again from memory) there were even a few notebooks with USBs in 2 different blocks (eg side and rear) where one block was restricted and the other was full spec, or the total current was 'for the block' and it could be drawn in full through one socket, or shared between the pair. OTOH its getting near midnight here and my brain might be shutting down... I never actually measured the current but I know it used to be a PITA with USB hard disks (2.5") which needed to connect to 2 ports to draw enough power, but a single cable was enough from a desktop USB. My new Dell D doesn't seem to have the same limits.

[Sarcasm Detector]

the last time i saw this error was on my Curve over the weekend.

i had done a javaloader wipe so that i got a white screen with 507 (or 207 i dont remember exactly).

I let the curve sit in that stage till it was completely discharged.

I managed to recharge it partially by jump starting it.

did an apploader /nojvm which seems to start with another wipe. the curve ran out of juice 40% into it.

at this point i had a completely nuked curve. jump starting it now showed a black screen with a LED that pulsed twice every 10 secs or so.

I let it charge for 30 minutes this time (with DM turned off) then started DM. Started application loader which immdediatly restarted the previous apploader /nojvm. it took it 3 secs to get to the 40% where it left off and continued on with no problem.

OS Vista x64 SP1
DM 4.6 b15
latest drivers for MoBo.

[Sarcasm Detector]

Unable to reconnect ...

It helps to go directly to the source.

BlackBerry Technical Support has published a paper addressing this issue.

The root cause may be in the USB post device properties.
Cause
There are multiple causes for this issue.

There is insufficient power for the loading operation to complete on the BlackBerry smartphone.
The connection between the USB port of the BlackBerry smartphone and the computer's USB port is unsustainable.
The USB drivers failed to initialize during BlackBerry smartphone initialization.

obviously my issue was the bolded part.

[GoochBerry]

I have tried changing the Device Manager properties and I am still getting the same error. I am working off of a laptop computer, do you think I should try a desktop? I don't have access to one that easy I would have to see where I can go .

[PvT]

Unable to reconnect ...

It helps to go directly to the source.

BlackBerry Technical Support has published a paper addressing this issue.

The root cause may be in the USB post device properties.

I've tried again with this 8100 that's been layin around that I thought I could breath life into.

My quick recap: In some of our cases an issue where the phone cycles on and off, allowing for a one second opportunity to gain a USB connection in order to proceed with the install. Unfortunately ending at the "Wait for device initialization"... & "Connecting to JVM" stage where the phone jumps back into it's continuous on/off loop.

Now I have followed the most recent suggestion that comes from Blackberry support (Thank you FM Reed McLay for posting it on the other thread) Direct link to that post: http://forums.crackberry.com/f3/how-...tml#post733307

I have done everything suggested to date and truly have tried everything suggested on the aforementioned link. (Working with a desktop computer) The phone still jumps out of its idle stage and goes back into the continuous on & off sequence (whilst USB connection disconnecting & reconnection every few seconds). I was even able to try another battery as yesterday I invited a colleague to come over with his sick 8100, which I did a system restore on (I'm pretty familiar with the process now), which was successfull though his phones issue seems to truly be a Hardware issue (a different problem than what this 8100 is going through... it just keeps clicking commands, as if the trackball is clicking on it's own. Calling people randomly, sending emails, advancing when you want to go back...) He is an electronics technician and had already opened the phone to clean everything he could think of including the ball etc.

I tried his battery in my pearl, I still have the same deadlock. I may have to accept the circumstances and move on...

This is a good thread as it can and has helped many people revive their berries, just not me... yet

[nartac]

Thank you for this thread. I have a Pearl 8110 that is doing exactly the same thing. Tried every which way but couldn't get OS to load due to the connecting and disconnecting of the USB. It seems the unit is in continuous cycle of on and off.

As I understand that there is a built in battery which may be giving the unit enough power to continue to run this cycle. I suspect (like a PC battery) that if we remove the battery and then reinstall it, it will rejump or reset the CMOS or whatever the unit has and will start out fresh again. In theory, this sound logical but in real life, a PC battery is easy to pull but not the phone battery as it's quite minute and requires precision soldering skill which I don't have. My hope is that I will let my pearl sit for a week or two without the battery and hopefully the juice from the last battery insert will dissipate from the capacitor or the little built in battery (which I doubt would drain) and hopefully we will be in business again.

[PvT]

My hope is that I will let my pearl sit for a week or two without the battery and hopefully the juice from the last battery insert will dissipate from the capacitor or the little built in battery (which I doubt would drain) and hopefully we will be in business again.

Hey, why not, I'll try that... I'll try anything new that I haven't tried yet.

[palingpinter]

I got the same problem and now my pearl is back to life. I've posted what I did here:
forums.crackberry.com/showthread.php?p=770078&posted=1#post770078

================================================== =====================================
I got a faulty 8100 from eBay for £25 including P&P. The fault was:

• It shows an error message: Uncaught exception: java.lang.NullPointerException
• It keeps restarting

The steps I did to bring my 8100 back to life:

• The first thing I did was wiping the 8100 using JL_comander.
• After that, I reinstalled the OS. While reinstalling the OS, I got an error message on my DM: Unable to reconnect to the device during a multi-stage load operation.
• I knew that the problem was related to insufficient power, therefore I just swap the USB connection to the USB port that generates more power to solve the connection problems.
• I was able to reinstall the OS after swaping the USB port.
• I was able to make calls, send/receive text etc while the 8100 was still connected to the USB port. However, it switched off and keeped restarting after I disconnected the USB port.
• I checked the battery and I found that the battery was fine.
• I assumed that the problem was related to the electrical connection between the battery and the mainboard. I then dismantled the pearl, cleaned the mainboard using a brush, wiped the all the electrical connections using a cotton bud wetted with alcohol. I left the mainboard until the alcohol fully evaporated.
• Put everything back and fully charged the battery
• Switch the 8100 on.....and it works....

[stirish]

I have the same issue with my 9000.

Tried every conceivable combination of suggestions from the various forums online including buying a new battery but its the same issue.

It loads until the 'Waiting for device initialization', I hear the USB connect/disconnect sound, then the bb screen lights up with a battery with a blue thunderstroke through it.

I am also trying this on a laptop, not through a USB hub but directly into the main USB connection next to the power inlet.

The JL_CMDER doenst connect either, gives me an 'unable to open port' error.

It seems that this is a common enough error however no-one has confirmed a solution to the issue.

Any help/suggestions are appreciated.

[exelant]

Just a note that some notebooks have a low power limit to the USBs. Dell used to be well known for current limiting (I think 5mA at 5v), and probably a few others have similar restrictions. Might be worth a try on a proper desktop computer with more robust USB power handling.

We generally try to avoid using usb hubs when loading an OS, but would using a powered usb hub overcome the low power limit that some notebooks have?

Posted from my CrackBerry at wapforums.crackberry.com

[jb421]

I have had this same problem with my 8130. but i was able to finally get it to connect what i did was i left my battery out of my bb until it switched from load jvm and system software to wait for device initalization. as soon as it switched from one to the other i put my battery back in the bb and it finished loading.

I hope this may help others as it did for me and if not i just thought i would pass along this bit of information

[d8da]

I just tried the upgrade on my 8320 from t-mobile and experiencing this same issue. I'm reviewing the thread(s) and all related info and will report back how I get through this. If anyone has quick suggestions let me know.

Just me and my crackberry getting to know each other...

[PvT]

Just me and my crackberry getting to know each other...

Just remember that while the two of you are getting to know each other over there, that here in CB you are not alone.

Keep this thread posted with all the juicy details on how you make out



Posted from my CrackBerry at wapforums.crackberry.com

[JonReedy]

Well I joined this forum in hopes of finding some insight into my problem with my 8830. Here is my original post where I was then pointed to the orginal thread regarded the force OS reload.

Hi guys,

Looking for a little help here. My BB 8830 WE has worked absolutely flawlessly for a year and a month...one month past the warranty and today it decided not to charge anymore and eventually when it ran out of juice will not charge nor boot up.

Originally I thought that it might be the mini usb connector since they are prone, so I brought it into a repair specialist for this purpose but asked to have the unit tested with a full battery to see if it will boot still since I was feeling skeptical. The phone connected and was recognized to his pc, so the usb couldnt have been too loose. Sure enough, no boot. So then he flashed and reloaded the OS...still no boot. His theory is that the "amplifier" for boot is fried...

The phone shows a red LED for about 5 seconds then off for 5...then eventually nothing. Absolutely will not boot under any circumstances.

Has anyone ever experienced this? Has anyone ever had any success with an "amplifier" replacement if this truly is the issue? I have not installed any aps, nor changed habits in any way whatsoever, this was completely random.

So then I delved into that thread head first and tried everything step by step with multiple attempts and complete thoroughness. Now I've come to this thread and am ending up at the exact same spot as PVT. I've tried new batteries, power management properties, new ports, new computers, no battery, ... essentially everything.

PVT I see that you mentioned you would try leaving the battery out back in september, did you ever have any luck with that?