when i try to mount a file i get an error that goes "Could not find a part of the path c:\users\michael\desktop\payload\to_install.apk" anyone know what could have started causing this?
Related
i just tried to install pocket legends on my phone
hd2 running the HTC desire HD 4.3 build.
after an hour of downloading i got an error like:
installation error - 18.
does anyone know what this error is and how i can fix it?
i would really appreciate it because this game looks so awesome.
try unmounting your sdcard first before installing.
fixed it i had to delete some file from the android secure folder.
then i had to run usb debugging now it works again
Can you describe what you did exactly?
I got the same error and can't fix it..
I got this weird problem with installation, hopefully somebody will know how to solve this here.
I've installed developer's preview before (on the same laptop) with no problem, even uninstalled and re-installed with no trouble. This time, when I tried to re-install (fresh install on a different partition, not upgrade), I got a tcpip.sys 0x0000098 error. So after that, I tried "sfc /scannow" in command prompt, but it showed no error in system files.
Anybody have a clue on what to do next?
I'm running Windows 7 Home Premium x68, trying to install Windows Developer's Preview x68. Let me know if I need to provide additional information.
Just thought I would share my experience in case anyone else was having the same problem
My problems were related to Flashtool 0.6.9.1 on linux <ubuntu oneiric> and the androidsdk_r18-linux trying to flash an x10 mini
Flashtool always loaded with errors related to libusb-1.0 and always hung at the "INFO - Please connect your device into flashmode." line and never proceeded to flash
the android-sdk-linux problem was that I couldn't even start the android tool due to some java errors which included: "java.lang.UnsatisfiedLinkError: no swt-gtk-3550 or swt-gtk in swt.library.path, java.library.path or the jar file"
Having spent half a day trying to reinstall various java packages and change PATH variables both these problems were down to a very simple tmp as noexec mount issue. I found the answer over in an ubuntu forum.
I am currently kicking myself but I'm so happy that everything finally works I thought I'd share this here in case there is anyone else with these problems.
a simple temporary fix (instead of changing fstab) is:
sudo mount -o remount,exec /tmp
Posting here cos I couldn't seem to post it in the Flashtool X10 thread, something about 10 helpful posts?
The device is recognized and works well with adb push and pull, no problems. I've noticed though, that any time I try to use an ADB install, or uninstall or I try to launch an application I'm developing from within eclipse (which I'm assuming is just an install script that is coded in)... it sends success messages in the console, but after it says "Starting Activity..." nothing ever happens. Has anyone else experienced this, and is there a simple solution? I've updated ADB and everything else that I could through eclipse, but nothing seems to fix it.
When I try to flash something via ADB on my computer it doesn't work because I get an error message that multiple terminals are open. I'm not good with command line stuff on the computer and usually figure out a way around it so I can flash what I need to, but the next time I need to flash something I'm in the same boat again with the same error message. Is there a way to close everything that is supposedly running so I don't get that error?
jhs39 said:
When I try to flash something via ADB on my computer it doesn't work because I get an error message that multiple terminals are open. I'm not good with command line stuff on the computer and usually figure out a way around it so I can flash what I need to, but the next time I need to flash something I'm in the same boat again with the same error message. Is there a way to close everything that is supposedly running so I don't get that error?
Click to expand...
Click to collapse
Hello,
What's the output of:
adb devices
Also, can you paste the exact error displayed on the command prompt?
You could try:
adb kill-server
Which kill the adb.exe process
Then:
adb start-server
Cheers...
Updated Android platform tools and when I flashed the latest bootloader didn't get that error again. The update must have cleared up the problem. Hopefully it won't happen again. Is there something you are supposed to do after flashing to ensure that the terminal doesn't rename open in the background in windows?
jhs39 said:
Updated Android platform tools and when I flashed the latest bootloader didn't get that error again. The update must have cleared up the problem. Hopefully it won't happen again. Is there something you are supposed to do after flashing to ensure that the terminal doesn't rename open in the background in windows?
Click to expand...
Click to collapse
Hello,
By "rename" you meant "remain" ?
I don't think so... But you can right click on your windows taskbar and open task manager.
Look at processes and see if ADB.exe is still running. You can also tic:
"Show processes for all users" and see here...
Cheers...