Printable View
Anyone see a problem where the device hangs, you do a battery pull (stay with me it gets more unique) and the device stops responding when the BlackBerry boot progress bar reaches roughly 25%? I've done this several times and it always stops at the same spot.
I've tried wiping with JL and it isn't even able to connect to the device.
Thanks,
Jason
I know exactly what you are talking about. The status bar hangs out around 25% for who knows how long. Just be patient and you will be fine. There is no fix for this, I believe this is just how the 191 loads.Quote:
Originally Posted by jasonwomack
Yup, took ages for the first boot for me too. After that it boots rather quick.
Thanks for the encouragement but it's been over 24 hours now and it's still sitting at that 25% mark.Quote:
Originally Posted by Seanren78
Anyone else seen this?
24 hours?!? Try a battery pull and see if that helps out.Quote:
Originally Posted by jasonwomack
I've done that several times.....Did I mention that even JL_Commander won't connect to this Storm?Quote:
Originally Posted by Seanren78
Hello jasonwomack,
Welcome to BBOS.
I think I have understood your OP to mean that you have completed several battery pulls. If that is the case then I would be inclined to say that your Download of the OS is corrupt.
I would take the following steps.
1. Remove the OS that you Downloaded from your PC
2. Wipe the device clean ( Hope you had a backup of the device)
3. Download a copy of the OS in which you want to load to your device.
If the OS is one of the 5.0 series of OS's, be sure to remove the RIM Internal App tools for your PC.
4. Install the fresh OS onto your device.
Hope this helps. If you have anymore questions please feel free to ask.
Quote:
Originally Posted by MePascal
I appreciate everyones help but I think we're not meshing on the information. I installed 191 when it was first leaked and posted to blackberryos.com a couple weeks ago. That installation went perfectly and I ran my Storm for over a week on it before experiencing this hang. While it's certainly possible that the installation of the OS on the device has become corrupted, the installation source is good (in fact I've used it to install on another 9530.)
What is new to me is this 25% hang on the device and inability to connect to it with JL (which precludes me from trying the steps you outlined above.)
This sounds feel it might just be a bad device (especially since no one else seems to have encountered this problem) but one Verizon is unlikely to repair with a beta OS on it.
Thanks again for all of the responses,
Jason
sorry so late may not help now. ivehad this prob. with mine twice. go into the loader app on your computer. pull your battery for a min and put back in when the pin pops up none click ok. reload the software. it took a couple times for mine to work. just as you would with a bricked bb