Troubleshooting issues with the Sideload Wonder Machine for Windows
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.
First, be sure you have the latest version
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:
- 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:\
- 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.
- 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.
USB, device not found, and device offline errors
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.
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
Last edited by Jerry Hildenbrand; 11-05-2010 at 04:52 PM.(‿)
- 11-06-2010, 01:53 PM #2
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.(‿)
- 11-06-2010, 04:07 PM #4
- 11-07-2010, 12:12 AM #5
- 11-07-2010, 12:33 AM #6
- 11-08-2010, 06:25 PM #7
- 11-10-2010, 01:55 AM #8
Wellp after a lot of searching it seems to me like the problem lies with BusyBox. I say that because I've installed the SDK for Android and when I go into adb shell and type in sh pm, I get that same error
"sh: Can't open pm"
This makes it seem like wherever the adb is starting from is actually incorrect--what I mean by that is when I drill down to /system/bin and run that command: sh pm-- it works just fine.
Does that make sense or am I just going crazy? Any ideas on how to reset the adb shell to go to /system/bin instead of wherever it goes because of busybox? I'd appreciate it. Thanks.
Your system (on the phone) isn;t seeing /system/bin/pm as a script. How it happened, I have no idea. But I know (probably) how to fix it since you're rooted.
adb pull /system/bin/pm C:\wherever\you\want\to\save\it. adb pull /system/bin/am C:\wherever\you\want\to\save\it.
Open the files and make sure the first line is
Mount your system R/W and push the files back to /system/bin/
Download root explorer from market (couple 4? bucks)
Open it, and navigate to /system/bin
long press on the file pm and choose to edit as text
Check the first line like above, make changes if needed.
Do the same for the am file
If this doesn't work, we'll try more.(‿)
- 11-10-2010, 12:48 PM #10
Well that seems to have done the trick. I ended up getting a bunch of permission denied errors when I tried to push back the changes so I just bought root explorer out of frustration. Thanks for your help, it's much appreciated. Any idea as to what happened or what could have caused this? Should that line
have been in the pm and am files already? Any idea whether or not busybox is responsible?
Either way thanks for your help and now I can sideload both ways!
- 11-11-2010, 02:31 PM #12
- 11-13-2010, 11:24 AM #13
- 11-15-2010, 09:59 AM #15
Not so fast...
First, let me say thank you for providing the application in the first place. I am truly grateful as my main goal was to install an application WITHOUT rooting the phone.
However, I wanted to point out that your advice regarding the beta version might not stand true for all users/systems. As the other poster said, in my case it gave an error, about not finding the payload to install.
I am using Windows Vista 64-bit system and I was trying to sideload on a Samsung Captivate. The beta version did not work. However, THE ORIGINAL, truly wonderful Sideload Wonder Machine did!!! So please keep that version on the site along with the beta one.
- 11-15-2010, 06:38 PM #16
- 11-16-2010, 03:13 PM #18
- 5 Posts
Put the *.apk in the same folder as all the SWM files
I'm not 100% sure my experience below is applicable here, but you might want to try reading through my post at http://forum.androidcentral.com/t-ca...ost383071.html
I got many of the same errors as some of you mentioned and I got SWM to work after making sure the *.apk file was in the same folder as all of the other SWM files. I discussed all of the other errors I encountered, too, and how I fixed those. Good luck!
-- AmsDiane- Lady with a Samsung Captivate (Galaxy S)
- 11-17-2010, 09:58 PM #19
- 11-24-2010, 05:49 PM #20
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.(‿)
- 11-25-2010, 01:04 AM #22
- 11-25-2010, 10:28 AM #24
- 11-27-2010, 04:19 PM #25