09-01-2013 11:18 AM
09-04-2013 04:30 PM
From what I see in this thread, you have left out a critical step in your process (deleting the VENDOR.XML files). In order to use an OS package from a different carrier, then you must do that...if you don't, then the installed (to your PC) BBOS package is totally ignored, and instead you can only obtain what your carrier supports. To override the automatic process, you must carefully follow all of this.
The simplest way is to, on a PC (you cannot do this on MAC):
1) Make sure you have a current and complete backup of your BB...you can find complete instructions via the link in my auto-sig below.
2) Uninstall, from your PC, any BB OS packages
3) Make sure you have the BB Desktop Software already installed
4) Download and install, to your PC, the BB OS package you desire:
5) Delete, on your PC, all copies of VENDOR.XML...there will be at least one, and perhaps 2, and they will be located in or similarly to (it changes based on your Windows version) these folders:
6a) For changing your installed BB OS level (upgrade or downgrade), you can launch the Desktop Software and connect your BB...the software should offer you the OS package you installed to your PC.
6b) Or, for reloading your currently installed BB OS level as well as for changing it, bypass the Desktop Software and use LOADER.EXE directly, by proceeding to step 2 in this process:
If, during the processes of 6a or 6b, your BB presents a "507" error, simply unplug the USB cord from the BB and re-insert it...don't do anything else...this should allow the install to continue.
Good luck and let us know!
09-05-2013 10:10 AM
09-05-2013 02:18 PM
09-05-2013 04:15 PM
09-05-2013 05:17 PM
Well, a couple of things...and apologies in advance for being ultra-picky here, but done correctly, this process definitely works...done wrongly, it doesn't work...and it is very easy to make a mistake during it...so we need to figure out what may have accidentally gone wrong...
Deleted the Vendor file
Only one VENDOR.XML file? In most of the more recent (e.g., since sometime early in the OS7 range) levels, there are always two of those to delete...and if either remains, then the installed OS package is ignored, and the automatic process instead kicks in.
Normally, it's called LOADER.EXE...are you sure you ran the correct thing? It is located in the AppLoader folder, but the actual executable is LOADER.EXE.
waited for all the process to come to an end and after that the OS installed was still .714.
Did it make any offers or provide an information during the process? Any indication, before it finished (indeed, usually at the very start) of the OS level it was going to work with? If not, then it ignored the installed OS package, and instead did the automatic process, which may well mean that your carrier (as per VendorID) supports nothing newer than .714.
Didn't use the BBDM because it didn't find the new .1033 update.
All that the Desktop Software does is call LOADER.EXE...so if the desktop software failed to find what you'd installed to your PC, then the expectation for directly running LOADER.EXE would be no different.
But most likely as I mentioned it before the file presented as a new update .1033 is the very old one .714.
I don't think I understand those words...
Normally, if the manual process is skipped (as appears to be happening for you), that is for one (or more) of the following reasons:
From all you have said, the package you have installed to your PC is being ignored, and the automatic process is taking over...why that is so is likely due to one of the above reasons.
Good luck and let us know