Windows Won't Recognize Switch as APX Device

Discussion in 'Switch - Exploits, Custom Firmwares & Soft Mods' started by itsharman, Apr 27, 2018.

  1. Could be the cable? What cable are you using and have you tried others?

    Also try running lsusb in the terminal and look for a "Nvidia device"
     
    itsharman likes this.
  2. itsharman
    OP

    itsharman Member

    Newcomer
    3
    Apr 25, 2018
    United States
    I got it running :D
    IMG-2528.JPG

    When the Switch is in RCM mode, only then does Ubuntu recognize it as an Nvidia device. When the Switch is in normal mode, Ubuntu does not recognize the Switch at all (not even like a Nintendo device, as Windows does). Thanks for all the help man!
     
  3. BadBoyXxX

    BadBoyXxX GBAtemp Regular

    Member
    1
    Mar 8, 2016
    Gambia, The
    need usb 3.0 for do it? have only usb 2.0
     
  4. deaos

    deaos Member

    Newcomer
    1
    Dec 30, 2015
    Iceland
    I have the same problem as well, I tried using th USB 3.0 slot and even behind the motherboard. Windows Device Manager is calling it Unknown USB Device ( Device Descriptor Request Failed).,,
     
  5. BadBoyXxX

    BadBoyXxX GBAtemp Regular

    Member
    1
    Mar 8, 2016
    Gambia, The
    now i have installed a driver but i have this problem

    Requesting access to device...
    Using uploaded payload "payload.bin"
    Preparing to launch uploaded...
    Connected to NVIDIA Corp. APX
    Device ID: c08001140000000cc3b6296401101062
    Sending payload...
    Payload sent!
    Switching to higher buffer...
    Trigging vulnerability...
     
  6. mcmrc1

    mcmrc1 Member

    Newcomer
    2
    Mar 11, 2018
    Germany
    I had the same issue. Try using another usb cable also microusb to usb c adapter works for me :) ! Or just try replug the cable on the switch ! Not the PC...

    I testet all Ports on my PC. USB 2 and 3 front and back but every time win 10 just found a unrecogniseable device.
    After i repluged on the switch the cable some times it worked fine ;) Seems i had a shitty cable.

    With my microusb to usb c adapter it is working now everytime :)

    Dont forget to install the the libusbk driver via Zadig over the apx win driver :)
     
  7. BadBoyXxX

    BadBoyXxX GBAtemp Regular

    Member
    1
    Mar 8, 2016
    Gambia, The
    I have the cable from the controll pro from my switch and where i can find the drivers?
     
  8. mcmrc1

    mcmrc1 Member

    Newcomer
    2
    Mar 11, 2018
    Germany
    h t t p s://zadig.akeo.ie/

    After your switch get recognizes as APX device -> Start Zadig -> Choose the APX -> change the driver to libusbk and install it.
    Now you can send payloads :)
     

    Attached Files:

    shomalon likes this.
  9. Draxzelex

    Draxzelex GBAtemp Guru

    Member
    18
    Aug 6, 2017
    United States
    New York City
    Literally had the same problem. The only thing that made it work was plugging it in again and again. As far as I know, there's no fix outside of repetition.
     
    mcmrc1 likes this.
  10. deaos

    deaos Member

    Newcomer
    1
    Dec 30, 2015
    Iceland
    Connecting directly to the motherboard behind can do the job, also try to change the cable.
    Those 2 things solved my problems...
     
  11. symish

    symish Advanced Member

    Newcomer
    2
    Jun 19, 2018
    Italy

    same issue here...Im desperate, at the benning it worked like a charm...now device not recognised everytime
     
  12. JanewayParisLzdKid

    JanewayParisLzdKid Newbie

    Newcomer
    1
    May 23, 2018
    Canada
    So I have this problem too. Device descriptor not recognized. I've tried Windows 10, 8, Ubuntu, the RCM Android App and SX Pro. Nothing works. Both RCM or normal mode, device descriptor failed.
    A friend came over the other day with his switch. All my methods worked for him no problem. The same cables and everything worked for him and not me.

    After weeks of trying everything I've come to the conclusion that it's hardware related. I've heard of people breaking something in the charging port or blowing a fuse related to the port.
    Whatever it is, there is no fix for us unless we send it in for repair.

    When a USB device is plugged into a port, it sends a device ID to the OS so the OS knows what it is, what drivers to load, etc.
    My switch simply doesn't send an ID back to the OS. So no matter what I plug it into, I get the same results.

    What I find interesting is that I can still dock it and play on my tv. The HDMI and charging still work.
    I'm guessing the dock doesn't request the Device ID like everything else does.
    I was hopeful that maybe the SX Pro doesn't bother with a Device ID check, but it doesn't work, so I'm guessing it does.

    My one big guess is that I plugged my switch into a 3rd party USB-C hub (The ones most Mac users would need) when it was new before all the articles about how it's bad for you switch were released.
    I'm guessing that the bad hub somehow triggered a fuse.

    Either I get my switch repaired or I wait for non-rcm/usb port exploit.
    Well, that's what I WOULD say if I hadn't just bought a used switch, tablet only, on ebay yesterday.
     
  13. nastys

    nastys ナースティス

    Member
    8
    Aug 5, 2014
    Italy
    Earth
    USB 2.0 works for me on Ubuntu 18.04 LTS without any patches.
     
  14. symish

    symish Advanced Member

    Newcomer
    2
    Jun 19, 2018
    Italy
    ùI found a solution in my case. When I connect it, I keep pressing the power button for 10 seconds, then I relese it and press the power button once again. After that my PC recognises my Switch
     
  15. Nuru

    Nuru Newbie

    Newcomer
    1
    Nov 5, 2018
    Spain
    Same problem here. Screen goes black, I need to hard reset if I want to turn it on again, but it seems to not get into RCM mode.

    Did you find out a solution?

    Thanks!
     
Loading...