i was able to fix apploader could not detect blackberry OS software
after installing.i have been flashing blackberry phone using apploader or blackberry desktop manager
and never had any problem before.recently i had an issue with apploader and blackberry desktop manager was not able to detect the OS software i installed.i cross checked it to make sure that vendor.xml
file was deleted permanently but still could not detect the OS and this got me worried as the phone has already been wiped using BBSAK
with the error 507
showing on the screen.i uninstall and re-install the firmware but still could not work.at the end of it all, i was able to resolve the issue and flash the blackberry phone
with apploader after deleting another vendor.xml file that was hidden in an unexpected path.so if you have been having this problem, i will share with you on how to fix apploader not detecting blackberry OS software after installed
if you are having this problem, please there is no need to format your computer because it would not solve the issue.it may work for you at first after formatting but it would happen again,again and again until you do the right thing, which is what i want to share with you.
i also thought of formatting my computer but had to look for a solution to resolve it and since then, when ever i have same problem, all i just need to do is to go to the hidden path and delete the second vendor.xml
and that will resolve it, so follow this step to get it done
how to fix apploader not detecting blackberry OS
after installing new blackberry firmware, we are suppose to delete vendor.xml
file from PROGRAM=>COMMON FILES=>RESEARCH IN MOTION=>APPLOADER
. i know you must have done that already and apploader could not load the firmware.if that is the case, then
==> go to this path on your computer C:/USERS/YOURNAME/APPDATA/ROAMING/RESEARCH IN MOTION/BLACKBERRY/LOADER XML
.this path may be hidden because it is part of the folders that are made to be hidden by default, so you will have to first check to see if it is hidden.
to do this, open my computer.at the top left corner, you will see ORGANIZE
, click it, from the option choose folder and search option
.a window will popup
from the popup window, click on VIEW
.from the view option, scroll down to where you will see HIDDEN FILES AND FOLDER AND TICK SHOW HIDDEN FILES, FOLDERS, AND DRIVES and click apply and OK it
==> now to search for the hidden vendor.xml, go to C:/USERS/YOURNAME/APPDATA/ROAMING/RESEARCH IN MOTION/BLACKBERRY/LOADER XML
there you will see the hidden vendor.xml, just delete it and open apploader again and viola, it will load the blackberry firmware you installed.that was how i resolve the issue, so how did you resolve yours?
to view the latest post update you are not seeing right now.
more articles update is posted on gurubest
every day,so don't be the last to get update to your email.Subscribe by email
DON'T FORGET TO SHARE WITH YOUR FRIENDS ON FACEBOOK BY CLICKING THE SHARE BUTTON
My bb 9860 began to misbehave when I did factory reset. It got stucked at 70% while rebooting after I reinstalled the os. Gradually, I did everything in the book to get it to work to no avail. I used BBSAK to wipe it to no avail.ReplyDelete
All I can remember was that I eventually left the phone dormant for many months, waiting for a good time to revisit it with hardwork. When I picked it again , it was stucked at the terrible white screen error: “No application Linked (Factory OS)”.
I began the ritual to find a way to format it and make it work, trying many method till I came to a post. This was how I solve my problem… I downloaded the “Full Procedure.bat” file (Google it) and used option “7” when I ran it. Actually step 7 comprises of step 2, 3 and 6 all at once. Then I ran Loader.exe for the OS, with my vendor file deleted from the two different folders as explained above, and my battery not inserted but with the phone connected by USB cable to my computer… when it reaches the “reconnecting to JVM” stage, I quickly reinsert the battery gently before the usual error occur when reconnecting to JVM” stage do fail (telling you to RETRY again)… Instead the battery booted the bb and the installation crossed that hurdle.
However in the reboot after installation (which took almost 30 minutes) I waited for what seemed like eternity for the the installation to be complete! After, all was well! Hahahahahaha... buuullllllll man!
thanks for sharing your experience. glad you finally fixed your devices. hoe to see more comments like this. regardsDelete