[mcmorj]

Hello All

I finally managed to upgrade my 8900 to version 5 OS from 4.6 and eagerly awaited loading goodies from Blackberry app world only to find no icon available. After reading a few posts I removed appworld via the PC desktop & USB connection. The phone rebooted and since then - will not work.

The symptoms are the red LED flashes once then flashes four times. Then once then four times - and this is all it does until I remove the battery.

It will then start the load after I replace the battery (blackberry appears on the screen with the little loader bar below). It gets about 75% of the way and the screen goes black. The red LED comes on, then the screen shows blackberry for a second then the red LED blinks once and so on.

If I connect the phone to the PC via USB the desktop App says "there are problems" would you like to to repair your phone? I say "yes" and we are back to the LED flashing once then four times and so on. The PC also then fails to recognise the blackberry.

I have also tried loader.exe in program files (x86)/common files / research in motion / apploader directory. Makes no difference.

I have tried removing the SD card and the O2 SIM, the battery in and out, holding in the power button and inserting the battery etc. I end up at the same thing - a red LED flashing once then four times then repeating...

Any help or suggestions gratefully received....!

[aiharkness]

Maybe you have already looked at the following, but if not then see How to Reload the Operating System on a Nuked or Bricked BlackBerry | CrackBerry.com

If it were me I would try wiping with JL_CMDR and get to the 507 error, and then try installing the OS again.

[mcmorj]

Thanks Ira - I have not read this guidance before and shall certainly be doing so.

I will update with the outcome on this thread.
Many thanks
Joe

[mcmorj]

Ok I looked at the crackberry link about a nuked Blackberry and it does not really relate to the problems I am having - My Blackberry goes into a "mode" if thats the word, where the USB connection is not recognised and therefore you cannot reload it.

Whatever way I have approached reloading, I quickly end up at the same thing, the "USB Device not recognised" message on the PC and my Blackberry Red LED blinking once, then four times then once then four times and so on.... so what doe's this evident LED blinking message mean....?! Anyone any ideas?

P.S. When I initially connect the phone via USB I get a USB device ID (and not unknown) but after the Red LED starts blinking - nothing.....

[tsac]

Ok , so you need to really read the instructions this time. The issue your getting IS covered in the instructions. It tells you to "catch" the BB in between reboots to be able to reload the OS.
This is a common issue and you just need to follow what aiharkness gave you.

[mcmorj]

Hello,

I have followed the instructions and have highlighted the DIFFERENCES in what I am getting as opposed to what is described in the Instructions.

When I start the Loader (WIndows 7 by the way) I get [Communication Port Selection] as *BLANK* - no COM1: or anything. When I then attach the phone, I DO NOT get USB:unknown - I get USB-PIN: 21B008DB

Whenver I click [Next] The message appears

"Trying USB-PIN : 21B008DB: Connecting to the device [Intel]

The phone then resumes this LED flashing 4/1 series. If I remove and re-insert the USB (having pressed [Next]), I get the windows message "USB Device not recognised" (whilst it flashes).

[aiharkness]

I don't know what else to do, except try wiping the device with JL_CMDER or BBSAK, but you will probably be dealing with the same timing problem to connect to the device, assuming the problem is simply software and not hardware.

You are not experiencing an endless rebooting loop, correct? The device starts to boot when you insert the battery, but then doesn't complete and the device ends up blinking the pattern you describe? I suspect the device may be broken. I was hoping not, and that the link I posted would put you on a track to fixing it.


Note that the timing is critical to catch the device when it is in the initial start-up part of it's reboot sequence, as mentioned in the article. I remember back in the day reading that it would take some people many, many tries to get it. If you only tried a few times, it won't hurt to try again. How many before giving up? I'm guessing a dozen, maybe up to 20. If you don't get it by then, you probably never will, or the device is really broken.

One last idea. See if you can boot in safe mode. If you can, then I believe that tells you for certain the problem is software and not hardware. First thing is do a backup. Then go back to trying to trying to do a clean reload of the device software.