[JM22681]

OK, I had this problem ever since the .151 and 5.0.0.140 beta's, everything .148 and before loaded fine in both loader.exe and DM. Here's what fixed it for me.

Don't mess around with your DM install, it won't help...

Install .151 or 5.0.0.140...

Copy the folder inside C:\Program Files\Common Files\Research In Motion\Shared\Loader Files to your desktop...

So now you should have a folder that looks like 9530-v4.7.0.************ blah blah blah or 9530-v5.0.0.************** on your desktop...

Install .148...

Go back to the folder it created for .148 inside C:\Program Files\Common Files\Research In Motion\Shared\Loader Files...

Delete the files inside 9530-v4.7.0.148_P4.0.0.181...

Copy the files inside the folder you created on your desktop, into 9530-v4.7.0.148_P4.0.0.181...

Re-run DM and you should be all set!

Someone should sticky this as it is a clear issue with .151 and 5.0.0.140. There's no reasong why you should need to pull your Internet connection or re-install DM!

[Alex015]

awesome thanks! i'll try this next time, i load a new OS. i just instaleld it on my desktop and it worked. seems to be only happening on my laptop

[howarmat]

OK, I had this problem ever since the .151 and 5.0.0.140 beta's, everything .148 and before loaded fine in both loader.exe and DM. Here's what fixed it for me.

Don't mess around with your DM install, it won't help...

Install .151 or 5.0.0.140...

Copy the folder inside C:\Program Files\Common Files\Research In Motion\Shared\Loader Files to your desktop...

So now you should have a folder that looks like 9530-v4.7.0.************ blah blah blah or 9530-v5.0.0.************** on your desktop...

Install .148...

Go back to the folder it created for .148 inside C:\Program Files\Common Files\Research In Motion\Shared\Loader Files...

Delete the files inside 9530-v4.7.0.148_P4.0.0.181...

Copy the files inside the folder you created on your desktop, into 9530-v4.7.0.148_P4.0.0.181...

Re-run DM and you should be all set!

Someone should sticky this as it is a clear issue with .151 and 5.0.0.140. There's no reasong why you should need to pull your Internet connection or re-install DM!

there is no reason why you should do whatever your post said to do either. I have never had to disconnect from the internet even to do my installs and all have been seen by loader.exe everytime

[paulwright1]

there is no reason why you should do whatever your post said to do either. I have never had to disconnect from the internet even to do my installs and all have been seen by loader.exe everytime

same here, never had a problem

[banderberg]

I got it on my phone, if you have the new DM, it was the first 4.7 option for me after i wiped my phone.

How do you wipe your phone?

[banderberg]

Thanks for the heads up on the hybrid 808Storming. Im still going to upgrade and then when the OS comes out add the hybrid. I broke my neck last night trying to figure out the reason and can't wait. I got it to work at 11am this morning. Thanks for all the help...this is why i love crackberry

What fixed it??? I hvae the same issue. App Loader just will not recognize the .151 files.

[banderberg]

I wonder if this has to do with the 5.0 desktop manager .. Was thinking maybe I'd wipe all the blackberry software form my PC and go back to the CD that came with the blackberry.

[kbluna]

I am having the same exact issue, I am going to try the folder replacing thing. Will let you know how it works.

[kbluna]

Well after hours of trying everything, the placing of 151 files into the 148 folder worked.

Posted from my CrackBerry at wapforums.crackberry.com

[rplakas]

I never had a problem installing an OS leaked or hybrid until after I installed 5.0.

I wanted to go back to .151 after 5.0, wiped with JL Commander and had the same problem as many here did with AppLoader and DM not seeing .151.

I tried this on 2 different XP machines one with DM 5.0 and the other with DM 4.5...and both could not see .151


In the end I copied the .151 files into the .148 folder and that worked.

Not sure why this happened by I think it has to do with 5.0 leaving something on the Storm..because even after I wiped it still had part of the 5.0 startup screen.

[howarmat]

Its working because DM thinks its actually 148 and not whatever OS you have just put copied into the java folder

[BerryBoy9530]

OK, I had this problem ever since the .151 and 5.0.0.140 beta's, everything .148 and before loaded fine in both loader.exe and DM. Here's what fixed it for me.

Don't mess around with your DM install, it won't help...

Install .151 or 5.0.0.140...

Copy the folder inside C:\Program Files\Common Files\Research In Motion\Shared\Loader Files to your desktop...

So now you should have a folder that looks like 9530-v4.7.0.************ blah blah blah or 9530-v5.0.0.************** on your desktop...

Install .148...

Go back to the folder it created for .148 inside C:\Program Files\Common Files\Research In Motion\Shared\Loader Files...

Delete the files inside 9530-v4.7.0.148_P4.0.0.181...

Copy the files inside the folder you created on your desktop, into 9530-v4.7.0.148_P4.0.0.181...

Re-run DM and you should be all set!

Someone should sticky this as it is a clear issue with .151 and 5.0.0.140. There's no reasong why you should need to pull your Internet connection or re-install DM!

Thanks A LOT dude. I've had the same problem as these guys and have been through so many forums. Been working on this crap since yesterday and it's really frustrating. After I tried your method, as soon as I copied and pasted the 151 files into the 148 folder, it recognized that there was new software available and started the update right away. I don't know why I didn't think of this before, since you go through with the same type of process when installing a hybrid. Thanks again.

[m.jed]

Thanks to JM22681's posted solution, I have finally been able to upgrade. I had upgraded to every OS from 83 - 151 including some of the later hybrids and while I had some problems in the past with AppLoader not recognizing, I could always fix it in about 1/2 hour or so. This was essentially 2 nights of work and going nowhere until I found this fix.

[picasso7]

OMG finally!!

although i wouldnt mind understanding the dynamics of why for some of us this is the only option to upgrade.

obviously it has something to do with the folder name (i.e. 9500-blah-blah)... but why is it not the same for everybody!?

could it be dependent on the mounted OS?