Well, I've done it again. Had .113 running for a couple of weeks but was afraid to upgrade OS because I was having some issues with Data backups. Finally got a solid data backup yesterday, so I decided it was time to try v5.
Removed the OS that was installed on the PC and ran the Leaked .132 executable, deleted the vendor.xml file, and then instantiated Loader.exe. This process nuked my phone, so I tried to deal with that, finally getting Verizon .75 back on.
Decided to wipe with JL Commander and then try again. Loader failed again. With the phone in the nuked state, and trying to get Loader to perform the upgrade, it reports that there are no additional apps to install. I can't move on.
Downloaded DM v5.0 and installed it. It recognized .141 (note: I always uninstall previous OS version in Add/Remove Programs and then install new OS to PC by running the executable) and almost got through the entire installation. However, the 2nd device init never happened, as DM seemed to lose its conn to the phone. I clicked on the screen and saw that I had App Error 523.
Tried this numerous times with various OS's (.113, .132, .141, and even .75 again). I always get the 523 error, always in DM (note: Loader.exe is not working at all). I wiped again, this time using CrackUtil (CU) and saw the 507 error (reload software). I tried .132 again and got the 523 error.
A quick check of the files on the phone through CU showed the .132 files were on the phone, so I thought I would try to install it again, thinking it would "repair" the OS for me. Nope - 523 error.
So, I'm stuck in this perpetual state of either a 523 app error or wiping and having no OS on the phone. And, Loader.exe is not helping.
Starting to get frustrated. I'm at work, w/o the phone, but I would appreciate any advice. I'll be on later, around 5 PM MST.
use the 4.5 DM. The 4.7 DM is very buggy and the 5.0 still has flaws to be worked out.
Also, try removing the SD card and then see if you can reload the OS to your device. Haven't encountered the 523 issue on the Storm too frequently but it was a huge issue on the Pearl and a few other models. There's a slew of chatter on the web and lots of proposed solutions to try (too much to post here) but do a google search on "Blackberry Storm 523" and you'll find endless posts about what worked/didn't for others who encountered this issue. Please post the solution if you find one that worked.
One other reminder (slightly off topic but perhaps important).
Although using "add/remove" in control panel appears to remove your old OS from the PC, it removes ONLY what it initially put on the PC. So, if you've been running hybrid.exe or made other loader file changes (Swap a Radio, built hybrids,etc.) it really doesn't get taken off the PC completely.
To be certain you have absolutely removed all of the old OS from your pc, do the following:
Control Panel > add/remove programs> remove all your old OS from the PC.
Now , look at Cprogram files>common files>Pesearch in Motion>shared> loader files
Open loader files - it should be empty. If not, delete it completely. THEN,REBOOT YOUR PC.
Reinstall the device software (eg. leaked .132) on your PC.
Delete the vedor.xml file from C: > program files>common files>research in Motion>Apploader
Give it another try.
Last edited by toytooii; 05-18-2009 at 10:47 AM.
Hey BG sorry to hear about the issue
If B's suggestions don't work then try this
I have read in several spots that people got the issue resolved by selecting no to the back up option on loader. And since you just completed a back up then you can manually restore your data once you get it up and running.
I taken a stab in the dark here but i'm thinking your on vista..
I ran into app 523 a while ago when a friend at work wanted to upgrade his 8830.
As far as I can tell your right it kind of spins its wheels and for a while and times out.
BBOS is correct ditch 4.7 and grab 4.5 not 5.0.
Start over . Fresh DM move your data backup somewhere safe I think your 3rd parties are toast..
Download and prepare to install a complete os only no hybrid. .132 or .141.
Rewipe and try again. The hybrids take quite a bit longer fr your phone to load.
That should work...then re run apploader with the hybrid java file upgrade.
If you do it in a two step process it should work. Not ideal but should work.
Put out a quick post when you're getting started and let us know how you're doing
Thanks, I'll try that.
Originally Posted by BlackberryOS
Interesting. I hadn't heard about the card issue. I did Google App Error 523 and found many hits. That's where I got all the experiments that I tried :doh:
Originally Posted by toytooii
I'll research it a little more though. Thank you!
Excellent suggestion. I did go that route though. You're right: since I've already backed up my data - and my 3rd party apps - there's no need to do it during the upgrade. It does make sense, since the upgrade seems to work up to the point of the last step, where it fails again; it's got to be a bad file, right?
Originally Posted by bmtenney
I'm actually on Windows XP.
Originally Posted by smcoldbb
I like the suggestion about starting over and not using 5.0. Should be able to get my apps and data back via my recent backups.
I've been trying to load leaked software, not the hybrids yet. I figured once I've got a solid OS install, then I'll begin the upgrade process to a hybrid.
Not sure what happened, but my phone has been in a really crappy state ever since I tried to install .114 hybrid v3.5 over v3. It just bricks every time now. Hopefully, going back to DM 4.5 will give the phone a new lease on life. I'll begin there tonight.
Thanks for the great responses guys!
Originally Posted by bgunckel
Bruce be sure to keep us up to date on how it goes when you get home
The card issue came up in a few of the hits from my Google search. Also lots of mention about themes and 3rd party apps as well as certain MMS attachments. But, let's get your device operational first...and then maybe the source of the problem can be determined.
In addition to everyting else you might try...
Since you have loaded hybrids onto your PC in the past, please follow the suggestion in post #3 regarding complete removal of previous OS installations on your PC. If you haven't done this, you'll be surprised by what is lurking in the loader files even though you have run Control Panel and believed you had removed the various OS from your PC.
I've encountered OS installation corruption in the past and came to recognize that control panel doesn't remove certain files added/modified to the loader files after the intitial installation of the base OS...and also found that some installations to the PC aren't completed until after a PC reboot. My guess is that it has to do with incomplete registry modifications on the PC. (for example, I've noticed .132 hangs during the PC installation process----not always, but on occasion. Following the above steps prevents it from hanging and assures a complete install) ...couldn't hurt to do and just eliminates another potential source of problems.
Hope you figure this one out.
Last edited by toytooii; 05-18-2009 at 11:31 AM.
Tags for this Thread