One more thing: free app memory was over 58 MB at startup! After I load everything up again it will be around 32 MB. Amazing how little app memory there is on this device.
Printable View
One more thing: free app memory was over 58 MB at startup! After I load everything up again it will be around 32 MB. Amazing how little app memory there is on this device.
before upgrading make sure to uninstall the current DM 4.7 you have now, reboot and install the new version
That would be good, and save the "wipes" I'd use those as a last resort, or use the function when instructed to do so on a upgrade..
If you wiped your device in advance of all this and had only one OS installed on your PC AND you used loader.exe I think it would only be looking for the files in that one OS you have installed on the PC. But I agree with Cruz that typically, wiping is not required. At any rate, I understand you've now got .75 back on the device which is actually FANTASTIC! I would suggest that you get a known good copy of .132 downloaded before you install it on your PC in the days ahead. I think the one posted on this forum is in good shape. Took a bit but happy to know it was all worth the effort. :)
Not sure what I was thinking as I typed last night. The actual name of the file that is missing is net.rim.blackberry.xml. I'm not even sure where that file would exist.
Whew! That was fun (not!).
It seems the install from the disk that came with the phone, and the upgrade that followed, didn't quite cut it. So I uninstalled DM 4.7, downloaded the latest version, and installed.
I then reinstalled .75 - from Verizon - and now .75 is back, ready to rock. I was able to restore my data and a few apps to verify. I'll give .132 a go tonight, after work.
All I've got to say is every one of you guys is awesome! I really do appreciate all your help getting this back to a stable state. I've actually been dealing with this issue for some time (some of you have been very helpful going all the way back to those probs), but it was getting worse. This time, I believe it's fixed!
So THANKS! :beerchug:
FYI, I tried to load .132 via DM this morning before work and it blew chunks. I didn't delete vendor.xml.
So, I'm back to where I started, but I think I've got a much better handle on things now. I currently have the App Error 523 message on the screen.
I think I'm going to try to load .132 via Loader.exe instead (yes thank you, I have since deleted the vendor file ;-)).
For those of you who don't know me, people love to use me as a tester. If anyone can blow up a system, it's me! :why:
Thanks bud, will do.
I had a perfect working version of .75 on there, but I really don't want to be stuck on that OS. Too many apps don't work very well on it. So, I'm not going to hesitate to load a better OS.
Sorry I didn't get back to you guys sooner, but after messing with this for 3 days, since early Sunday morning (note: I didn't even post until Monday), I was just fried.
toytooii, I've already uninstalled .132 from my PC. I wanted to make sure I got .75 running and stabilized before moving forward. I've reloaded most of my 3rd party apps and my data. Next, I'll make sure to get good backups of each before moving forward again.
Some observations:
As toytooii noted on page 1 of this post, your PC must be restarted after running any OS executable. OS upgrades failed every time I failed to reboot after an install or an uninstall of an OS. Remnants of the previous version(s) were always left behind.
DM comes with .75 release 94. The version of .75 on the Verizon site is rel 107 (9530AMEA_PBr4.1.7.0_rel107_PL4.0.0.94_A4.7.0.75.e xe). 94 causes some real issues with my device, and it does not include all the files necessary to install. 107 does, and is very stable.
After wiping my device, no remnants of any OS is left behind. After bricking the phone I had to wipe, and I tried to load .113, .132, and .141 onto my wiped device. Every one reported missing files. I wiped again after each of these failures, and tried to load .75 rel 94 from DM, and it failed. I had to load .75 rel 107, which contained all necessary files. I'm guessing I can upgrade from this base now.
After wiping (and doing correct install/uninstall procedure by rebooting) I tried to load .132. The vendor file is nothing more than an empty XML document, except in the case of .75 rel 107, where it is a full XML doc (this is one difference between rel 94 and rel 107). I couldn't load .132 in DM. I wonder if using DM requires the vendor file, and using Loader.exe doesn't want it?
That's all for now. Thank you all for your help, and for your time. I owe each of you a great debt of gratitude!
I'd say just use loader.exe in the future. It's much faster, in general. Never had all those missing file issues you've discussed and yes, release 107 of .75 is the official Verizon version. Also, I always delete the vendor.xml file and have never had any problem. With all the missing file issues you've discussed, I'm just curious if you've encountered any problems with your PC while using other programs. While this is totally off topic, that's the sort of thing I've bumped into when a hard drive or motherboard was about to fail. Anyway, hope everything works out. And now, as of today, you've got .148 to try out!
I am glad you got everything up and running!!! Check out the new complete guide that we have now (in my signature) ;)
Checked it out. There's some excellent info in there!
Just a quick update. I was able to successfully load .148 yesterday morning without any problems at all. Thanks to all of you who contributed to my issue!
Wirelessly posted (9530)
Glad to hear it :) nothing better than being able to feed the addiction.Quote:
Originally Posted by bgunckel
You know, I'm constantly amazed with the BBOS forums, how everybody always helps out.
I think it's fantastic, you guys are great.