08-11-2013 09:53 PM
...
1. TANKS
06-17-2011 08:04 PM
2. looks like an interesting program, going to give it a try.
06-19-2011 01:13 PM
3. The SWM should work for anyone with Windows XP or higher, and on any phone. Of course issues will come up for some, and that's what this post is here for.

There's a good bit of troubleshooting you can do yourself, and some is built into the latest version of the program. Here's the common issues, and how to fix them.

http://forum.androidcentral.com/atta...10_30_beta.zip
This version fixes the path issues users running Windows XP have been seeing

File path errors
The SWM looks for its files and support libraries in specific places. I did it this way, as the only other alternative is writing to the registry. To make sure the program can find the files:
1. The SWM folder has to be placed on the top level of your C:\ drive. Running it from your downloads folder, or your desktop is not going to work. Unzip the downloaded file, and drag the whole AC_SWM folder over to C:\
2. Some computers "block" files downloaded from the internet. That's Windows security, and it's a good thing. Right click on each of the files in the AC_SWM folder, and see if there is a button to "unblock" in the properties dialog.
3. In the program itself, there is a button labeled "Diagnostics". Clicking it will open a new window with two choices -- USB diagnostics and Path diagnostics. Run the path diagnostics and the program will check to see if the right files are in the right places. If you see an error you can't resolve, sing out and we can determine why.

The SWM needs a properly functioning adb driver for your phone to work. Adb stands for "Android Debug Bridge" -- it's what takes your keystrokes (or data from a program like the SWM) and converts them into commands that your phone can understand. This isn't a SWM specific issue, all programs that run on your Windows PC and communicate with your phone need this driver installed.

You get this driver from your phone manufacturer. If you're not sure you have the driver for your phone installed, jump into the forum specific for your device and ask around. Remember, you're not the only one looking for the driver, so don't be afraid to ask our in-house device pro's for help if you can't find what you're looking for. If all else fails, look for a thread about rooting your phone in it's hacking forum -- the first step in hacking a phone is getting the driver installed

The next thing to check is the way your phone is connected. If you can open the SD card folder to drag and drop files, the SWM isn't going to work. Since there is only one cable to connect, we get a choice of how to use it. Make sure you don't have any mass storage, or USB modem specific settings in use. Usually the setting to only charge your phone is the one you want.

Any application that can set your phone to mass storage automatically can interfere with the SWM. I'm looking at you, doubleTwist and WinAmp. If you're using any app that does this, check your settings to disable it.

USB debugging has to be enabled on your phone. Tap menu>settings>applications>development, then enable USB debugging

Once your sure your driver is installed and the Windows Device Manager shows no errors, USB debugging is enabled, and your phone isn't in mass storage mode you can check your connection and driver status in the program itself. Click the Diagnostics button, then run the USB diagnostics program. A command window will open, a small routine will run, and you'll see your phone serial number if all is good, and you'll see nothing or a series of ???????? is all isn't good. Unless you see your phone serial number, the SWM isn't going to work. If you've done everything you can think of, sing out. We'll get you straight.

.NET 4
Unhandled exceptions when trying to open the program usually mean you don't have Microsoft's .NET v4 framework installed correctly. Download it here:
and make sure it installs with no errors.

This is a work in progress. more to come
I just wish they would allow us to sideload without going through all this bs
06-19-2011 11:35 PM
4. Cool
06-20-2011 08:30 AM
5. thanks guys, hope this works!
06-21-2011 07:54 AM
6. Thanks!
06-21-2011 02:20 PM
7. Can't get inspire to work
06-24-2011 04:04 PM
8. it helps, i installed x-plane to my lg optimus one and it works
06-24-2011 07:02 PM
9. goooood my frind
07-01-2011 07:14 AM
10. thanks for all the hard work on making this!
07-01-2011 08:33 AM
11. Samsung Captivate AT&T

Trying now....
07-01-2011 02:26 PM
12. Wrkd for me!!!
07-01-2011 03:38 PM
13. Thanks for this.
07-01-2011 04:08 PM
14. It worked, thanks!
07-02-2011 08:00 AM
15. The SWM should work for anyone with Windows XP or higher, and on any phone. Of course issues will come up for some, and that's what this post is here for.

There's a good bit of troubleshooting you can do yourself, and some is built into the latest version of the program. Here's the common issues, and how to fix them.

http://forum.androidcentral.com/atta...10_30_beta.zip
This version fixes the path issues users running Windows XP have been seeing

File path errors
The SWM looks for its files and support libraries in specific places. I did it this way, as the only other alternative is writing to the registry. To make sure the program can find the files:
1. The SWM folder has to be placed on the top level of your C:\ drive. Running it from your downloads folder, or your desktop is not going to work. Unzip the downloaded file, and drag the whole AC_SWM folder over to C:\
2. Some computers "block" files downloaded from the internet. That's Windows security, and it's a good thing. Right click on each of the files in the AC_SWM folder, and see if there is a button to "unblock" in the properties dialog.
3. In the program itself, there is a button labeled "Diagnostics". Clicking it will open a new window with two choices -- USB diagnostics and Path diagnostics. Run the path diagnostics and the program will check to see if the right files are in the right places. If you see an error you can't resolve, sing out and we can determine why.

The SWM needs a properly functioning adb driver for your phone to work. Adb stands for "Android Debug Bridge" -- it's what takes your keystrokes (or data from a program like the SWM) and converts them into commands that your phone can understand. This isn't a SWM specific issue, all programs that run on your Windows PC and communicate with your phone need this driver installed.

You get this driver from your phone manufacturer. If you're not sure you have the driver for your phone installed, jump into the forum specific for your device and ask around. Remember, you're not the only one looking for the driver, so don't be afraid to ask our in-house device pro's for help if you can't find what you're looking for. If all else fails, look for a thread about rooting your phone in it's hacking forum -- the first step in hacking a phone is getting the driver installed

The next thing to check is the way your phone is connected. If you can open the SD card folder to drag and drop files, the SWM isn't going to work. Since there is only one cable to connect, we get a choice of how to use it. Make sure you don't have any mass storage, or USB modem specific settings in use. Usually the setting to only charge your phone is the one you want.

Any application that can set your phone to mass storage automatically can interfere with the SWM. I'm looking at you, doubleTwist and WinAmp. If you're using any app that does this, check your settings to disable it.

USB debugging has to be enabled on your phone. Tap menu>settings>applications>development, then enable USB debugging

Once your sure your driver is installed and the Windows Device Manager shows no errors, USB debugging is enabled, and your phone isn't in mass storage mode you can check your connection and driver status in the program itself. Click the Diagnostics button, then run the USB diagnostics program. A command window will open, a small routine will run, and you'll see your phone serial number if all is good, and you'll see nothing or a series of ???????? is all isn't good. Unless you see your phone serial number, the SWM isn't going to work. If you've done everything you can think of, sing out. We'll get you straight.

.NET 4
Unhandled exceptions when trying to open the program usually mean you don't have Microsoft's .NET v4 framework installed correctly. Download it here:
and make sure it installs with no errors.

This is a work in progress. more to come
07-06-2011 02:45 PM
16. Hi!

So happy to have found the SWM! I have downloaded it successfully on my husband's Samsung Captivate, but I am having tremendous difficulty getting it to work with my Motorola Flipout.
I downloaded the device driver for Motorola, my computer indicates the driver is installed, but when I troubleshoot, SWM does not find my phone.
Please advise what I am doing wrong. I am very sad without my SWM working for my phone

Thank you!
Cara
07-09-2011 09:29 PM
17. Let's fix it.

Make sure you have the latest version. Hit the about button in the program -- you're looking for the words BETA_BUILD 1.1_10_30 in orange lettering, in the upper right of the window. If they aren't there, hit the download link above.

Open the app, and press the diagnostics button, then the black folder button to check the file paths. See what it tells you.
I tried several times to install this on my win7-64 machine, reloaded the drivers, turned off my firewall, everything i could think of... No-Go, tried it on my Netbook (32 bit) and worked like a dream!!! Thanks much!
07-10-2011 05:38 PM
18. Okay, PLEASE help me here. I've been going off the bloody wall trying to get an update on my samsung captivate for swype. I got the froyo update through Kies mini, swype started acting nuts with a pop-up message every time I select a different word than what it suggested. I'm sure you know of that. Anyway,

I tried updating my swipe with the SWM (yes all of the troubleshooting is clear). but I keep getting this message about inconsistent certificates (attached is a screenshot) So, please for the love of all things sane, could someone post a link to a good .apk of swype that is stable, and not crazy that I can sideload on a non-rooted samsung captivate so I can enjoy my phone?? Is that too much to ask?

Sorry this is long and wordy, just really need help.
07-11-2011 10:54 PM
19. Hi there! after a hard long work finally I got the "installing aplication" mesage... but it stays so that way for long and nothing happens...just that screen.... so i had to unpluge it, and every try is the same thing...does it take that really long or is there something wrong? Thanks in advance....
07-27-2011 05:46 PM
20. I have everything installed and SWM files on my C drive, and the window is up to choose the APK file. When I go into the C drive and select SWM file it opens to payload which then opens to NOTHING. I can't figure out why and it's driving me nuts. I did both diagnostics and they both come back fine. PLEASE HELP!
07-29-2011 11:24 PM
21. ee the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\AC_SWM\payload\to_install.apk'.
at Microsoft.VisualBasic.FileSystem.FileCopy(String Source, String Destination)
at AC_SWM.frmMain.btnChoose_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.235 (RTMGDR.030319-2300)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
AC_SWM
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Jordon/Desktop/AC_SWM.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.232 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.235 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

That is what I am getting on my HTC Inspire tryin to get Netflix installed...I WANT NETFLIX!!!
08-06-2011 03:09 PM
22. ee the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\AC_SWM\payload\to_install.apk'.

<snip>

That is what I am getting on my HTC Inspire tryin to get Netflix installed...I WANT NETFLIX!!!
Re-read the instructions. It looks like you didn't install the files to the root of your C drive.
08-06-2011 03:35 PM
23. Re-read the instructions. It looks like you didn't install the files to the root of your C drive.
I'm getting the same message. I installed using the windows installer. I browsed to the folder on my windows machine to see what was in the payload folder and there is just a single file called "placeholder"....

EDIT: Just checked the zip file option, and its the same, payload folder is missing files
08-07-2011 11:04 AM
24. Hi gbhil,

I DL'ed the sideloader and I still can't get this app I am developing to work. I am using a Coby Kryos
MID 7022 capacitive touch 4GB storage and 4g. I have a 16 GB microSD card. I have the device
set to allow debugging, allow mock locations and unknown sources. I am using the Marmalade
developer kit with VS2010 as the compiler and it is set to GCC cross compile for ARM. The app
works fine in the simulator and emulator but I get it over to the tablet but copying it and the icon
show a lock on it. The Marmalade deploy tool will not work either. I am getting this error from all
the different ways I've tried to intall it from the PC....I'll show you the sideloaders output but the
bold and underlined section is what all windows based deployment keeps telling me.

Code:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Android Central Sideload Wonder Machine v. 1.1
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Installing application

1182 KB/s (1872461 bytes in 1.546s)
pkg: /data/local/tmp/to_install.apk

Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]

If you do not see an error, everything was
successful and your application is installed.
After exiting the program, you may unplug
Press any key to continue . . .
Supposedly according the the folks at Marmalade, you do not need any certificates
for debugging purposes but yet I get this error consistantly.

Any help would be appreciated
08-10-2011 10:37 PM
25. Hi gbhil,

I DL'ed the sideloader and I still can't get this app I am developing to work. I am using a Coby Kryos
MID 7022 capacitive touch 4GB storage and 4g. I have a 16 GB microSD card. I have the device
set to allow debugging, allow mock locations and unknown sources. I am using the Marmalade
developer kit with VS2010 as the compiler and it is set to GCC cross compile for ARM. The app
works fine in the simulator and emulator but I get it over to the tablet but copying it and the icon
show a lock on it. The Marmalade deploy tool will not work either. I am getting this error from all
the different ways I've tried to intall it from the PC....I'll show you the sideloaders output but the
bold and underlined section is what all windows based deployment keeps telling me.

Code:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Android Central Sideload Wonder Machine v. 1.1
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Installing application

1182 KB/s (1872461 bytes in 1.546s)
pkg: /data/local/tmp/to_install.apk

Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]

If you do not see an error, everything was
successful and your application is installed.
After exiting the program, you may unplug
Press any key to continue . . .