08-11-2013 09:53 PM
237 1234 ...
tools
  1. Jerry Hildenbrand's Avatar
    It could be any number of things. Usually see it on some corporate versions of XP. The GUI was built so people have an easy way to do it, without copying files or remembering which batch scripts to run. Issues with the .net framework, path errors, permissions, etc. can cause the GUI to fail.

    That's why the commands themselves aren't written in the application, and are done through scripts instead. While it's not as easy or elegant, at least this way people like yourself can still sideload their apps without having to install and set up the SDK.

    protip:
    use reloader.bat to upgrade an app through sideloading
    Always make sure only one apk (the one you want loaded) is in the payload folder at any time.
    11-27-2010 04:53 PM
  2. fadi1973's Avatar
    i installed the swm
    this message apper each time i run the swm
    unable to find a version of the runtime to run this applecation
    soo how can i fix this problem
    12-01-2010 03:18 AM
  3. Jerry Hildenbrand's Avatar
    i installed the swm
    this message apper each time i run the swm
    unable to find a version of the runtime to run this applecation
    soo how can i fix this problem
    Make sure you have the .NET4 runtimes (from Microsoft) installed. Link is in first post
    12-02-2010 01:53 PM
  4. PPYEAH's Avatar
    This is what i get from pressing the "Test path issue"
    Can someone tell me what to do next?
    I used to have the Windows Vista and the old version of the SWM. It worked great on my Samsung Galaxy S captivate.
    After I switch to Windows 7. I have never able to get this work again.

    Plz help, thank you



    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
    at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
    at System.Diagnostics.Process.Start()
    at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
    at AC_SWM.frmDiag.Button2_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)


    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    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:/AC_SWMv1.1_10_30_BETA/AC_SWM/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.1 built by: RTMRel
    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.1 built by: RTMRel
    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.
    12-09-2010 06:08 PM
  5. Jerry Hildenbrand's Avatar
    This is what i get from pressing the "Test path issue"
    Can someone tell me what to do next?
    I used to have the Windows Vista and the old version of the SWM. It worked great on my Samsung Galaxy S captivate.
    After I switch to Windows 7. I have never able to get this work again.

    Plz help, thank you



    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
    at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
    at System.Diagnostics.Process.Start()
    at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
    at AC_SWM.frmDiag.Button2_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)


    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    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:/AC_SWMv1.1_10_30_BETA/AC_SWM/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.1 built by: RTMRel
    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.1 built by: RTMRel
    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.
    Make sure you have .NET4 correctly installed. It's from Microsoft. Link in first post
    12-09-2010 11:21 PM
  6. yuurin's Avatar
    it says "success"
    and I pressed any key to continue
    but i didn't see the app in my phone
    12-12-2010 12:43 AM
  7. Jerry Hildenbrand's Avatar
    it says "success"
    and I pressed any key to continue
    but i didn't see the app in my phone
    Which app? I'll try it here
    12-14-2010 08:33 PM
  8. 2monkeyman's Avatar
    My problem is that when I try to install an app, everything works until the end, the diagnostics are fine, but the error says I have insufficient storage, I just factory reset my captivate phone, so why doesnt it work?
    12-14-2010 09:32 PM
  9. josh.mitchell's Avatar
    Hi can anyone help me sort out a couple things? i was trying to install the fmradio app on my galaxy s running the insantiy rom XXJPO and first my phone just errored and reset no there is an error coming up that states [INSTALL_PARSE_FAILED_NO_CERTIFICATES] What am i doing wrong?
    12-18-2010 12:56 AM
  10. irezloe217's Avatar
    So Phil...It says it was a success installing the new Gingerbread keyboard for 2.1. I'm unrooted, and on a Captivate. From my understanding this APK should work, but after I sideload it, nothing shows up anywhere. Do I have to install/activate the APK on the phone?

    Edit: Totally figured it out. It didn't pop up as an option when I was composing a message, and had to turn it on under the actual settings in running apps (for anyone else having the same issue).

    Thanks for such a wonderful program Phil!
    12-18-2010 08:56 AM
  11. anon77519's Avatar
    I installed Sideload Wonder on my laptop. It worked fine on my captivate. I installed 15+ apps. My boss got the captivate so I took my laptop to work hooked up my boss phone and the first app installed fine then ever since I get the error insufficient storage. I hooked my captivate back up and now my phone gives the same ererror.

    sideload wonder still works fine to install apps on my phone from my desktop pc. It's just my laptop is having problems.


    Any ideas what's wrong?

    Thanks
    Jim
    12-19-2010 09:42 PM
  12. jadoug122's Avatar
    Been trying for a couple of weeks now. Thanks and Aloha!
    12-20-2010 01:48 AM
  13. stevemedia's Avatar
    Hi,
    First post but I have been reading reams and reams of useful info for a while now. Thanks to all.
    Mind you, even after all the reading I can only get as far as:-

    'loader.bat' is not recognized as an internal or external command,
    operable program or batch file.

    C:\Documents and Settings\Main User\Desktop\AC-SWM-v1.0\AC-SWM\payload>cd ..

    C:\Documents and Settings\Main User\Desktop\AC-SWM-v1.0\AC-SWM>loader.bat
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    Android Central Sideload Wonder Machine v. 1.1
    Make sure your phone is plugged in, and
    USB debugging is enabled on your phone
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

    List of devices attached
    644213c9dada device

    You should see the serial number of your Android
    phone above. If so, continue. If not, make sure
    you have installed the USB driver for your phone,
    and make sure that USB debugging is enabled.

    Press any key to continue . . ."

    And this is where I am lost.
    The "644213c9dada " is not the same as the Serial number in battery compartment of my Samsung I5801. It's "RVIZ966404M".
    Can anyone help me with this, why the difference? More importantly, is it ok to proceed?
    best wishes
    Steve
    12-23-2010 10:46 AM
  14. snipedinthehead's Avatar
    Here's the error I got when looking for the proper files:

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
    at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
    at System.Diagnostics.Process.Start()
    at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
    at AC_SWM.frmDiag.Button2_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)


    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///D:/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:///D:/AC_SWM/AC_SWM.exe
    ----------------------------------------
    Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.30319.1 built by: RTMRel
    CodeBase: file:///D:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
    ----------------------------------------
    System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///D:/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:///D:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///D:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///D:/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.



    Also, any idea where I can find the USB driver for a Sony Xperia 10xa? This sideloader sounds fantastic, but I can't get any use out of it, because I can't even find the proper driver! Also, I've tried installing about 2 or 3 drivers, each of which is supposedly the correct one, but every time it shows up as a Mass USB storage.
    12-23-2010 04:39 PM
  15. deadxxtruth's Avatar
    So before I had trouble with this program because it just wouldn't find my phone but when I installed android sdk manager, that fixed it but for some reason now SWM isn't picking my phone up again and it's not finding it at all. Is there anything you can help me with?
    12-26-2010 04:50 PM
  16. lizagirl5's Avatar
    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 went through this process 100 times making sure I had everything where is should be and got the "no payload" error every time. When I hit diagnostic in the program- it simply said no payload installed. Just as a last ditch effort, I just created a new folder called payload in the AC_SWM folder and it actually worked perfectly. if that helps. awesome awesome awesome program! Thanks!
    12-27-2010 05:16 AM
  17. frogman's Avatar
    Please help. So I downloaded the Samsung captivate driver from Samsung's Software page (The driver is called "SGH-i897_Captivate_USB_Drivers_5_02_0_2.zip".). After installing my phone appears in the Device Manager as "ADB Interface > SAMSUNG Android Composite ADB Interface" and I am able to connect my phone and once I mount my phone, I can move items via Mass Storage just fine. It does mount 2. So the phone is being recognized by the computer and everything appears fine here.

    Next I downloaded the file "AC-SWM-v1.0.zip" and extracted the files to my desktop and place it in the C drive.

    I setup my phone with the following settings:
    1.Applications - Development - USB debugging
    2.Application > USB Setting - Mass Storage
    3.I plugged in my phone via the USB cable. Phone was detected and connected.
    4.I then double-click on "AndroidCentral-SWN.exe"
    5.I found my .apk files and hit the Install button.
    6.The message I get is the following:

    List of devices attached
    I89786099b38 Offline

    What am I doing wrong and why my device is offline? Thank you
    12-28-2010 09:42 AM
  18. toadfacedfrump's Avatar
    Hello all, and thank you to the excellent developers of this program. Using the steps outlined earlier in this thread, as well as the original thread introducing the SWM, I thought I was finally stumped with a computer device. Then I ran across the lady with the paths issue, which helped me greatly. But still no go. Then I did something seemingly irrelevant and simple, and eureka, sideloading apps with no problem.

    What did I do? I insured all my apk files were in the SWM folder, then I simply went to the huge effort of plugging my USB cable into the back USB ports on my PC, and yep, that is when the loading occurred. I remember someone else mentioning this earlier, and it was that simple for me too. If your paths are correct, go to the trouble to plug the USB cable into your PC's motherboard USB ports, because for some unknown reason, it does make a difference. That difference for me was the ability to actually sideload versus not. Can someone with more skill than I shed some light on exactly why this made such a huge difference, front USB ports versus rear motherboard ports please?

    I hope this helps someone avoid the hours of aggravation I had getting it to work correctly. But I've usually found that many hours of aggravation are solved by something very simple. That's why I love computers and all OS's, they are a great challenge when something you know should work refuses to do so.

    Again, thank you to the developers of this excellent software. And AT&T, as much as I love them, need to stop locking down OUR devices. We pay the high bills for our toys, they should let us have the option to use them as we want and it was designed for without rooting it for God's sake.
    12-30-2010 12:33 PM
  19. xperiaz's Avatar
    First off, anyone looking for the Xperia x10 drivers, I found them here:

    Sony Ericsson - Developer World - Downloads - Download - Dw-x10drivers

    Thing is, I first installed the drivers from SEUS, and now whenever I plug my Xperia X10 into the USB port, it only ever gets recognized as a SE Mass Storage Device. I've uninstalled it from device manager, restarted the computer, and it gets recogized all over again as SE Mass Storage Device.

    When I try to update the driver, it says it cant find a better driver than the one I already have.

    Please Help!!

    Thanx in advance!!
    01-02-2011 12:24 PM
  20. toadfacedfrump's Avatar
    First off, anyone looking for the Xperia x10 drivers, I found them here:

    Sony Ericsson - Developer World - Downloads - Download - Dw-x10drivers

    Thing is, I first installed the drivers from SEUS, and now whenever I plug my Xperia X10 into the USB port, it only ever gets recognized as a SE Mass Storage Device. I've uninstalled it from device manager, restarted the computer, and it gets recogized all over again as SE Mass Storage Device.

    When I try to update the driver, it says it cant find a better driver than the one I already have.

    Please Help!!

    Thanx in advance!!
    When you say you uninstalled it, do you mean the device or drivers please? Have you tried uninstalling just the drivers for the Xperia? If not, try that and then reboot. When rebooting, have the Xperia disconnected from the computer, then once booted up attach the Xperia and point the driver install utility to the drivers you downloaded from SEUS and have it install them. Hopefully, that should take care of that problem. I say hopefully because Windows is a pain when it comes to drivers, the OS thinks it knows best, even though you know you want these alternate drivers.

    As far as the mass storage problem, I can only think you may have it enabled on the Xperia and/or USB debugging isn't checked within Android (Settings/Applications/Development/USB debugging)? I'm not much help in this area, sorry. I can't even locate USB mass storage settings on my Captivate, still not as used to it as my old BB Curve.

    Good luck and let us know how it goes please, and hopefully someone with more expertise than I will teach us both something.
    01-02-2011 02:26 PM
  21. GarretW.Captivated's Avatar
    Hi, I'm new here, and my Samsung captivate is great! But when i try to sideload, it says, "error: device not found." Why?
    01-02-2011 04:27 PM
  22. xperiaz's Avatar
    Yes, I do have USB debugging enabled on the phone. (AT&T Xperia X10)

    When I say uninstalled, I mean from device manager. I delete SEMC Mass Storage Device from Device Manager, restart and the cycle repeats.

    I restart computer, plug in Xperia phone with USB debugging enabled, and Windows (I'm running WinXp 32-bit) AUTOMATICALLY installs the drivers for my phone and it instantly gets recognized as a SEMC Mass Storage Device. I dont get any option for anything when I plug it in. And BTW, I AM using a port in the rear of my computer.

    What happens is I start SWM inside of its folder, on the root of C: drive. I do a path diagnostic check and it checks fine, but the USB diagnostic fails. And if I just go ahead and run the program, no serial number shows up so I cant proceed any further from there.
    01-03-2011 09:36 AM
  23. toadfacedfrump's Avatar
    Sounds like one of the problems I encountered too. I think you'll have to wait on bill or someone else to help you here, because it could be just about anything. And its probably something very simple. Luckily for me, it was making sure my apk files were in the SWM folder and connecting the USB cable to my rear ports. I did a test just to confirm the rear vs front ports on my PC, and sure enough, front ports get me nowhere, but rear ports let me load to my hearts content.
    Sorry I was no help, but keep trying because you will finally get it with help here and trial and error.
    01-03-2011 12:52 PM
  24. toadfacedfrump's Avatar
    You probably read my posts since we have the same phone. If not, follow the SWM setup to the letter, then start trying little things. The wonderdul lady who figured out the paths issue saved the day for me. After reading her post, I made sure my apk files were within the SWM folder on the root C drive and then connected my USB cable to the rear ports on my PC, and those 2 simple things ended hours of failure for me. You could double check those 2 things. Hope that helps.
    01-03-2011 01:02 PM
  25. jpinks's Avatar
    This is wierd I know it worked before here is the error message details. I was trying to do the diagnostics to make sure it saw everything and this is what happens. Still getting the no space on phone error on my other pc. Phone has 10gig free and memory card has 13gig free

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
    at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
    at System.Diagnostics.Process.Start()
    at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
    at AC_SWM.frmDiag.Button1_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)


    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    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:/AC_SWM/AC_SWM/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.1 built by: RTMRel
    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.1 built by: RTMRel
    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.
    01-04-2011 11:27 PM
237 1234 ...
LINK TO POST COPIED TO CLIPBOARD