Please bear with me. 2 days since my last post in this thread and 3 pages to look through, 16 emails, and 2 visitor messages (even though I've stated I will delete support request messages there, lol). I'm only one guy who develops this program during my spare time

Most of those issues have been solved for others, or by others, earlier in the thread. However, given the thread has grown in size so quickly and contains info based on v1.4 and early versions, I can see how things could be confusing. One thing I would like to clarify: if PreBrew works on your device, WebOS Quick Install will; they use the same install and uninstall methods.

To that end, I've added a very brief setup guide on Tutorials webOS Installing An Ipk - WebOS Internals (feel free to clarify my wording and add whatever notes you guys may feel is appropriate, it is a wiki after all Also, here's a quick guide for troubleshooting (some of it's a rehash from the FAQs post):


Troubleshooting
I've unzipped the file, what do I do next?
Nothing! Don not, I repeat, DO NOT, unzip/unrar the .jar file. The nature of a JAR file is that it is both an archive and an executable program. We only wanna use the executable program aspect.

How do I run the program?
Windows

• Double-clicking on the .jar should work. If it doesn't, reinstall Java 1.6

Mac OS X

• According to this document, OS X 10.5 Update 1 is when Macs got Java SE 6 (aka Java 1.6). This is required for WebOS Quick Install to run correctly.
• For some MacOS versions that don't support the above release of Java 1.6, you want to try SoyLatte.
• Also, run /Application/Utilities/Java/Java Preferences. Then click and drag Jave SE 6 to top of both list, and exit the program. This will set Java 1.6 as the default version to use and should have no ill side effects.

Ubuntu

• To install the current version of Java, enter the following in terminal:
  sudo apt-get install sun-java6-jre
• To run the .jar, right click, choose "Open with" and select "Sun Java X.X runtime"

For more info, see How to Run a .Jar Java File: 11 steps - wikiHow

I already WebOSDoctor downloaded. Do I have to download it again?
Nope, you can just move your existing copy to the same folder as WebOS Quick Install and the program will run.

I'm seeing this screen. What do I do next?
Nothing, close that window! That's WebOSDoctor. You don't want to run that unless you want to reset your Pre to factor WebOS 1.03 settings (and wiping all your data).

In WebOS Quick Install, clicking menu Tools->Device Management does absolutely nothing
This means WebOS Quick Install is unable to access the WebOSDoctor.jar file. Possibly corrupted jar file. You'll want to delete the WebOSDoctor.jar file then redownload from this link. Put that downloaded file in the same folder as WebOS Quick Install.

I'm getting "ERROR: No device found."
Common error. Two reasons this could occur:

1. Mis-matched your choice of device. In WebOS Quick Install, click menu File->Options. If your target is the WebOS emulator on your computer, choose "Emulator"; if your target is a real device, like a Palm Pre, choose "USB Device".
2. Your device and/or computer are not configured correctly. WebOS Quick Install depends on both your device being ready for the connection as well as your computer being ready for the connection.
   • Novacom needs to be installed on your computer. In WebOS Quick Install, click menu File->Options. Click the "Attempt Novacom (re)installation" button.
     • Alternatively, Windows users can manually install Novacom via this method.
     • Linux users can download Novacom here. Read this guide if your Linux distribution doesn't use Debian files.
     • A computer restart is highly recommended.
     • Windows users can verify Novacom is running by going StartMenu->Run...->"services.msc" and looking for a "Palm Novacom" entry and making sure it's started.
   • WebOS device needs to have DevMode.
     • This can be done by typing "upupdowndownleftrightleftrightbastart", opening the DeveloperMode app, and enabling the feature.
     • Some circumstances can cause the the toggle to show as enabled even when its disabled. To solve this problem, disable it then re-enable it.
     • Some people report OTA updates reset DevMode. Keep that in mind when updating.
   • When you plugin your device, choose "Just Charge"