Not sure if you have tried this* but use this link to recover your dead blackberry:
This is a sad day. On Friday (4 short days ago!) I received in the mail an 8830WE Verizon that I bought on Ebay. I was excited to see if Blackberry-ing was for me* and then thought Id wait for Verizon to get a new Curve or Bold-like device. I had great fun over the weekend sending and receiving email* Synching with my gmail account* making shopping lists on Mara Tick* and generally enjoying the great capabilities of the Blackberry. I guess I got a little cocky on Sunday night when I thought* Why not upgrade my OS from 188.8.131.52 to 184.108.40.206---those folks at Crackberry make it sound so easy. I downloaded DM 4.7 and 220.127.116.11 from Verizon* copied everything to the DM* and now after trying to do the install* it hung with the status bar unmoving for a couple hours.
.......I now have a Berry with two red LED flashes* a pause* two more* etc. No white screen ever* just the sad flashing. It stalled (for hours) after erasing the files and while it was trying to load JVM.
Since then* my husband (who is quite techy but no Blackberry experience) has followed every suggested fix here and on some other forums* battery removal* hitting next at the magic moment* all to no avail.
We have tried all this with DM 4.7 and 4.5 and with the 18.104.22.168 system software from Verizon (which is my carrier) and with the 4.5.0 system software from Sprint (with the vendor.xml file removed).
When the Application Loader starts* we get the USB-PIN: UNKNOWN message* but it seems to be happy to continue.
We get to Erasing Applications through the DM* and that seems to go successfully. Then to the Loading system software task bar* which gets half-way and stops there and the message above the task bar changes to Loading JVM and system software. Then it will sit there as long as we let it (all night* for example).
When we try to load the OS with the App Loader directly it gets stuck on wait for device initialization* and the progress bar does not even get started (weve left it trying all night).
When we try starting the App loader from the command line with the command
this has exactly the same result.
We have also tried using jl_cmder but this doesnt connect to the device.
Is this fatal??? Ill be so sad. Not to metion I have no other phone so now Im incommunicado from the world. Sorry for the long post. All serious fixes considered!! Thanks.
I am not sure what is wrong here but here are a load of links that may help you. I hope that one does the trick
BlackBerry 101: How to Reload the Operating System on a Nuked BlackBerry | CrackBerry.com
Livelink - Redirection
How To: ReInstall OS When Computer Wont Recognize The Device Is Connected - PinStack.com
i have the same problem here.
i had to use my laptop and it came back my pc is windows 7 64 bit i think that was my problem. used my laptop xp 32 bit and it worked fine i got the white screen back
Yeah* that was one of the place we started. But thanks!
Thanks for the links.
I dont understand what to do with the BlueRoom link* but weve tried the other solutions in your list.
Also* we dont get any error codes* it just hangs (and the screen of the blackberry stays black). And we are already using XP* which seems better for this than Vista* I guess.
But thank you for the suggestions.
After removing DM 4.7 and OS 4.5 from my PC* both of which I decided not to use based on various posts in these forum* the process gets a little further before it dies. Getting to the Applications loader via Windows XP command line interface* the first few steps of the apps loader complete before the loader dies saying Unable to complete the loading operation* fatal error A:0x0000000E. I dont know if this represents progress or is a red herring. It seems like plenty of other folks have been in this situation (none of the step-by-step instructions on CB fix their Berry) and I cant tell if they eventually fix it or they go buy an iPhone.......just kidding. I dont want an iPhone* I want my 8830WE to be resurrected. Ill keep working on this* with any help yall can give.
I dont know if this may be a glitch with DM4.7 or not. I had problems with that version* and then I downgraded to DM4.6. Ive had no issues since then. You might want to give that a try.
Yes* based on another posters suggestion I did the whole thing over again (a billion times!) using DM 4.6. I think Im done trying at this point* dont know what Ill do for a phone now. Thanks for the suggestion* though.I dont know if this may be a glitch with DM4.7 or not. I had problems with that version* and then I downgraded to DM4.6. Ive had no issues since then. You might want to give that a try.
Sorry it didnt help. Maybe an earlier version of DM would work? Dont give up.
Well* thank you to all who offered help--but I do think Im at the end of the line. Ive done it all* with every version of the DM and the OS and every combination thereof* on three different Windows machines* with XP and Vista* with the same (or variations on the theme) unhappy result. I suppose I could send it back to RIM to be flashed* but I think the cost of that with shipping is more than the device is worth. My purpose in buying a used Blackberry was to avoid signing another two year contract with Verizon or possibly to save my phone upgrade until Verizon has a newer Blackberry device. 8830WEs are easy to come by on Ebay; maybe Ill get another cheap and leave it alone!
I really am sorry you couldnt get this to work* but maybe that is why 8830s are easy to find on ebay.
i have a 8320 and when i get to the wait for device initialization step* i get an error message that my device is not connected. when the progress bar gets to this step i hear the USB connect/disconnect beeps on my computer repeatedly. CAN ANYONE HELP? please comment on here or on my own thread for more info.
There are currently 1 users browsing this thread. (0 members and 1 guests)