I am unable to use qpst. install says unable to register several files with computer. program runs but can't find a server. any ideas?
reinstall QPST and make sure you have administrative privileges on the account that you are installing on.
I have reinstalled several times. every time it gives me the same error. I am the admin, as I am the sole user. I tried reinstalling all files in the wiki several times. The program does run, it just doesn't find a server. it is able to recognize my phone, I can't do anything with it though. i am using vista FYI
Is your internet connection on with your PC when your opening QPST?
yes. I use dsl
Being the only account on a vista machine does not mean you are the admin, and further more the admin account is hidden. If you install anything and I mean anything at all, get used to right clicking on an installer and choosing the command "run as administrator". Or unhide the admin account and do all installs from there and use the other account for day to day use. This is the method I use. I had problems running so many programs when I first got vista. There are also options to run programs in XP compatibility mode, like when I use webjal.
Read this if you want to unlock admin in vista Or just make sure you right click and run as administrator. This also fixed many issues I had with BuildOS too.
very interesting...thanks for the tip...Im reading up on it now....those sneaky SOB's
I unlocked the admin and logged into it. I reinstalled all the files and still ran into the same problem. I almost wonder if its because i'm running a lap top
the following files fail to self-register during install
PhoneLib.dll
PhonePropLib3.dll
PhonePropLib4.dll
SerialPortLib.dll
QPSTProxyComponents.dll
all of these are in C:\Program Files\QPST\bin
I am on a Dell laptop running vista, and I only installed qpst after I learned the admin account trick, so I can offer no other help. Sorry man!
Edit, what build are you using and where was it acquired?
im using 215 from the wiki
I am using that version from that source also. What is your machine's specs? 64 bit? 32 bit? home or pro? etc... Lets try to get all this information down so we can see whats different.
im running the 32 bit version of vista on a duo core pentium. its an acer laptop. i'm surprised i can't find anything on this on the internet. I think that windows updates may have gotten me. maby its time for the cure all format the hard drive.
My Dell desktop does not recognized my Fascinate after upgrading to Windows 7 Service Pack 1.
I can't use ODEN any more, can't even mount the SD card anymore.
Really stuck big time.
HELP HELP HELP!!!
Still stuck and feel like getting rid of my phone and verizon all together.
Whats wrong with microsoft and samsung, I know another guy that couldn't print after upgrading to SP1.
its possible that the samsung drivers are not installed.
Sent from my SCH-I500 using XDA Premium App
Definitely start by uninstalling the drivers, and then reinstalling the latest version (for the extra paranoid, run something like driver sweeper before reinstalling). Also, try different ports on your computer/make sure you're using the official cable that came with your Fascinate.
If that doesn't work let us know (along with anything else you've tried, just to save us from telling you to do things you've already done!).
Also, just for future reference, this should go in the Q&A section- Development is meant for postings of ROMs and other similar things (there's a high probability your post could get rocketed off the front page before anyone even notices it in this section!).
Agreed, try upgrading your drivers. If that does not work initially, reboot into CWM with the phone plugged in, that usually forces Windows to detect the device drivers again and install them (always works for me when Windows *forgets* the Samsung drivers).
As the poster said above, this should have been posted in Q&A or General, and not development. I have reported the post so that a mod can move your thread to the appropriate section.
i have this problem before.
With debugging on, power phone off, plug into computer and power phone on. That should allow the computer to see your phone
Click to expand...
Click to collapse
androidcentral
Here another thing to try- shut down computer, and then unplug the power chord from the back. Let it sit, then plug it in and boot it up.
That's what worked for me.
Sent from my SCH-I500 using XDA App
I've run into this issue several times, and have found a few solutions.
Several times, it took completely removing the drivers and reinstalling them. By completely removing them, I mean uninstalling them through add/remove programs and then by searching through the registry for the many traces that the driver uninstall misses. And there are many... like hundreds. And there are all kinds of permission problems on those registry keys that you need to fix, one by one, before they can be deleted. It's a major PITA that takes hours to do. But once it's done, I was able to reinstall the drivers and the phone was recognized fine.
Another issue I ran into was a possibly faulty USB cable. Just recently, Windows just stopped recognizing the phone, and in trying different ports, I happened to notice Windows was detecting the bare cable (as in it wasn't plugged into the phone). I could plug the cable alone in, and Windows would recognize it as an "unrecognized USB device". I tried a different cable and it saw the phone fine.
So, first thing to check is your cable. Does Windows detect it when you just plug in the cable by itself? If so, try a different one.
If nothing else works, and you want to remove the drivers totally, let us know and I'll walk you through the steps to remove all those bloody registry keys, but it's not fun...
ChrisDDD said:
I've run into this issue several times, and have found a few solutions.
Several times, it took completely removing the drivers and reinstalling them. By completely removing them, I mean uninstalling them through add/remove programs and then by searching through the registry for the many traces that the driver uninstall misses. And there are many... like hundreds. And there are all kinds of permission problems on those registry keys that you need to fix, one by one, before they can be deleted. It's a major PITA that takes hours to do.
Click to expand...
Click to collapse
Revo Uninstaller is an ideal solution for totally cleaning stuff out. Pick the most aggressive sweep, and after the factory uninataller finishes, it isolates and removes all the leftover registry keys, files, and folders associated with the uninstalled item. Found it to be a godsend as a PC tech in a big school district with way more computers to manage than I had time.
The free version is more than adequate.
Materialized into existence through the act of observation.
Here is my observation, my USB mass storage doesn't get recognized on the computer hardly ever (it was a miracle and an event to be celebrated if it happened), and I talked to some people in IRC about it. GizmoDroid had me trying lots of different things. Eventually I just installed ADB, and to my surprise, ADB always sees the phone just fine. So, I think the Samsung drivers need tweaked a bit because they definitely work, but something about them just doesn't work correctly with Windows (or with anything, but has samsung ever put out any software that was up to our standards?).
My suggestion is to install and learn ADB, not hard at all with the given tutorials. Even easier if you have experience with Linux. It always, always works for me.
tbeas said:
My suggestion is to install and learn ADB, not hard at all with the given tutorials. Even easier if you have experience with Linux. It always, always works for me.
Click to expand...
Click to collapse
ADB would work as an alternative to USB mass storage for the most part (which shouldn't need the Samsung drivers), but it isn't an alternative to being able to use Odin!
agsded said:
Revo Uninstaller is an ideal solution for totally cleaning stuff out. Pick the most aggressive sweep, and after the factory uninataller finishes, it isolates and removes all the leftover registry keys, files, and folders associated with the uninstalled item. Found it to be a godsend as a PC tech in a big school district with way more computers to manage than I had time.
Click to expand...
Click to collapse
Cool, thanks, I'll definitely check that out. I had set up some macros to repeat the process of setting ownership of each key and deleting it, but it still took hours.
tbeas said:
Here is my observation, my USB mass storage doesn't get recognized on the computer hardly ever
Click to expand...
Click to collapse
The OP can correct me if I'm wrong, but this isn't just a mass storage problem, the phone itself isn't recognized as anything at all, so that means mass storage doesn't work, Odin won't pick it up, nor will ADB. Connect the phone, and at best, Windows sees an "unrecognized USB device", at worst, it sees nothing at all, as if the phone wasn't even connected.
Mine will go invisible to Odin at times, also. I will go to heimdall at that point and it will usually be visible there. I keep both programs around partially for that reason, and partially cause of how granular heimdall is.
Materialized into existence through the act of observation.
Delete
KitsuneKnight said:
ADB would work as an alternative to USB mass storage for the most part (which shouldn't need the Samsung drivers), but it isn't an alternative to being able to use Odin!
Click to expand...
Click to collapse
Adb 100% needs the Samsung drivers.
Sent from my SCH-I500 using XDA App
suppliesidejesus said:
Adb 100% needs the Samsung drivers.
Click to expand...
Click to collapse
The drivers might not be necessary if connecting to the phone with ADB over TCPIP, which you can set using a terminal emulator on the phone.
Don't know if you need to log in as SU or not, but these are the commands:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
These set the adb daemon to listen over the port 5555, then stop and restart the daemon.
Then on the computer, you'd type:
adb connect 192.168.1.xxx:5555
Then:
adb shell
And it should connect.
Not that this would solve the Odin issue, but it's at least one way to get stuff on/off the phone when the drivers crap out.
zzd4nzz said:
-Uninstall Samsung Drivers
-Uninstall USB Root Hub
-Restart Computer (On boot up, the computer will automatically install USB Root Hub)
-Install Samsung Drivers
-Hold down Vol - while plugging into phone to get into download mode
-Odin will hopefully recognize the phone.
Click to expand...
Click to collapse
Thanks to all you guys,
But! I tried every thing, uninstall samsung, uninstall usb hub, reinstall drivers.
I am ready to just sell my fascinate and get an Straight Talk phone to have peace of mind.
Please Help
http://forum.xda-developers.com/showthread.php?t=1065727
Which rom and kernel are you using?
I tried running viperMOD PrimeTime v4.1 (viperMOD PrimeTime v4.1.exe) on my Win7 and my Comodo Firewall reports that it detected a malicious file "[email protected]". I assume it blocks the execution, because nothing happens even if let it run. Can anybody confirm this is a false report? I'd like to have a confirmation before I disable Comodo and run the rooting tool again.
Edit: Scanning the files with MSE, and doing a computer full scan, reveals nothing.
Downloaded & executed on my win7 pc. Avira antivirus didn't mind. Think you're safe, probably.
Sent from my Dell Streak using xda premium
piokon said:
I tried running viperMOD PrimeTime v4.1 (viperMOD PrimeTime v4.1.exe) on my Win7 and my Comodo Firewall reports that it detected a malicious file "[email protected]". I assume it blocks the execution, because nothing happens even if let it run. Can anybody confirm this is a false report? I'd like to have a confirmation before I disable Comodo and run the rooting tool again.
Click to expand...
Click to collapse
All those rooting apps use non standard procedures that can be considered by some antivirus apps as dangerous. But no problem here.
Installed successfully, after telling Comodo the file was a false alarm.
One note for detail freaks like me that I wanted to post in the main dev thread but cannot due to not having 10 post (perhaps somebody can transfer it there): for step "9) If you see MTP USB Device on the next screen under ASUS Android MTP Device...", I did not see "ASUS Android MTP Device" anywhere, my system was identifying the device already as Transformer TF-201. Clicked next and everything went just fine, RootKeeper confirms root.
Guys / Gals
I was able to fix my problem of not being able to connect my phone, a Samsung Note 3, and the error I got was from Microsoft MTP. I believe it is Media Transport Protocol. I searched for days; this was a pain in the neck problem. iPhone users seem to have the same issue. I have seen a couple of solutions suggested here on XDA, but they did not work for me. One solution advised to remove the drivers via Windows, mine is Win 7 btw, Devices and Printers screen, they stated to make sure to check the remove driver checkbox. But MTP does not have any such checkbox that I see in my setup. Maybe we are different Windows versions or something. Regardless, what worked for me was to reinstall Windows using the Upgrade option right after you select install. This procedure does not usually damage your personal files; but like every other post here:
1- Do back up everything.
2- I am not responsible for any damaged files, computers, anything.!.!.! Ok?
I backed up my files on an external drive. The only thing I had to reinstall was VMware Workstation 11, and afterwards I was able to launch it fine. In fact I am typing this post from the Ubuntu guest within the restored Win 7. During the install I noticed Windows took some time "repairing .Net". So maybe folks who have more knowledge of Microsoft products can look into this as a quicker fix?
After you are done, test your phone's connectivity and if it is working, create a restore point as soon as the install is done since Windows is going to install a slew of updates right after. You can label restore points something like "Phone Driver Works" or anything else, which implies a successful milestone.
Send me an email if any of this is unclear. I am so glad this is fixed for me. I'll post some of the links, which helped me figure this out.