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 184.108.40.206 to 220.127.116.11---those folks at Crackberry make it sound so easy. I downloaded DM 4.7 and 18.104.22.168 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 22.214.171.124 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.