Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,160,162
  • Replies Replies 48,001
  • Likes Likes 66
With your Switch plugged in and in Goldleaf, what shows up under USB devices?

Edit: Also, are you running Zadig as admin?

I see this:

upload_2019-8-4_19-9-57.png


Also yes i'm running Zadig as administrator.
 
What happens if you uninstall the device?

After uninstalling it disappeared from device manager. After restarting Zadig it no longer shows Nintendo Switch (or libnx usb comms) in the dropdown. Nothing happened on the switch.
 
After uninstalling it disappeared from device manager. After restarting Zadig it no longer shows Nintendo Switch (or libnx usb comms) in the dropdown. Nothing happened on the switch.
Unplug the Switch and re-plug it in. If that doesn't work, reboot the computer.

Are you using this computer to push RCM payloads?
 
Unplug the Switch and re-plug it in. If that doesn't work, reboot the computer.

Are you using this computer to push RCM payloads?

Ok here's what happened:
  1. Unplugged USB
  2. Restarted computer
  3. After finished booting I plugged the USB back in (i'm still in Goldleaf btw)
  4. Windows notification pops up Nintendo Switch device was installed
  5. Open Zadig (admin). Same issue
  6. Open Device Manager. Looks the same as before:
upload_2019-8-4_19-28-26.png


Edit: Also yes I use this computer, USB, port, etc to go into RCM mode.
 
Ok here's what happened:
  1. Unplugged USB
  2. Restarted computer
  3. After finished booting I plugged the USB back in (i'm still in Goldleaf btw)
  4. Windows notification pops up Nintendo Switch device was installed
  5. Open Zadig (admin). Same issue
  6. Open Device Manager. Looks the same as before:
View attachment 175268

Edit: Also yes I use this computer, USB, port, etc to go into RCM mode.
Out of curiosity, what does Zadig show when the Switch is in RCM?

Also, are you using 32-bit Windows or 64-bit Windows?
 
Out of curiosity, what does Zadig show when the Switch is in RCM?

Also, are you using 32-bit Windows or 64-bit Windows?

I powered off my switch, and once Tegra showed that green RCM icon I see this on Zadig:

upload_2019-8-4_19-35-58.png


That seems like the only relevant device. After booting into CFW I see this:

upload_2019-8-4_19-38-16.png
 
Hm i'm not sure what i'm supposed to be doing. What's "DZ" Tinfoil and am I going to use the tinfoil.nro?
Tinfoil.nro from that website is DZ Tinfoil. I recommend it over Goldleaf. Goldleaf also just received a major update, so I have no idea what has changed.
 
Tinfoil.nro from that website is DZ Tinfoil. I recommend it over Goldleaf. Goldleaf also just received a major update, so I have no idea what has changed.

Ok after starting the Tinfoil app (from album) I got a tinfoil.io log in error. As for Zadig i'm guessing this is it? I don't see a Nintendo Switch device:

upload_2019-8-4_19-52-52.png
 
Looks like this:

View attachment 175272

Am I boned? I have no idea why the Switch driver isn't installing correctly.
In Zadig, go to Options and then Advanced Mode. Then, try installing the driver. What does the log say?

I have no idea what the problem is. Are you using 32-bit or 64-bit Windows?
 
In Zadig, go to Options and then Advanced Mode. Then, try installing the driver. What does the log say?

I have no idea what the problem is. Are you using 32-bit or 64-bit Windows?

I'm on Windows 10 64-bit. Below is the logs. I redacted some info with XXXXXX:

Zadig 2.4.720
Windows 10 64-bit (Build 17134)
ini file 'zadig.ini' not found - default parameters will be used
default driver set to 'WinUSB'
1 device found.
libwdi:debug [wdi_create_list] Hardware ID: USB\XXXXXX
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_FF&SubClass_FF&Prot_FF
libwdi:debug [wdi_create_list] Driverless USB device (12): USB\XXXXXX\SERIALNUMBER
libwdi:debug [wdi_create_list] Device description: 'libnx USB comms'
Using inf name: libnx_USB_comms.inf
Successfully extracted driver files.
Installing driver. Please wait...
libwdi:info [extract_binaries] successfully extracted driver files to C:\Users\Reese\usb_driver
libwdi:info [wdi_prepare_driver] successfully created 'C:\Users\Reese\usb_driver\libnx_USB_comms.inf'
libwdi:info [wdi_prepare_driver] Creating and self-signing a .cat file...
libwdi:debug [AddFileHash] 'libusb0.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\amd64\libusb0.dll'
libwdi:debug [AddFileHash] 'libusb0_x86.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\amd64\libusb0_x86.dll'
libwdi:debug [AddFileHash] 'libusbk.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\amd64\libusbk.dll'
libwdi:debug [AddFileHash] 'libusbk.sys': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\amd64\libusbk.sys'
libwdi:debug [AddFileHash] 'libusbk_x86.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\amd64\libusbk_x86.dll'
libwdi:debug [AddFileHash] 'wdfcoinstaller01011.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\amd64\wdfcoinstaller01011.dll'
libwdi:debug [AddFileHash] 'libnx_usb_comms.inf': INF type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\libnx_usb_comms.inf'
libwdi:debug [AddFileHash] 'libusb0.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\x86\libusb0.dll'
libwdi:debug [AddFileHash] 'libusb0_x86.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\x86\libusb0_x86.dll'
libwdi:debug [AddFileHash] 'libusbk.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\x86\libusbk.dll'
libwdi:debug [AddFileHash] 'libusbk.sys': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\x86\libusbk.sys'
libwdi:debug [AddFileHash] 'wdfcoinstaller01011.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\x86\wdfcoinstaller01011.dll'
libwdi:info [CreateCat] successfully created file 'C:\Users\Reese\usb_driver\libnx_USB_comms.cat'
libwdi:info [RemoveCertFromStore] deleted existing certificate 'CN=USB\XXXXXX (libwdi autogenerated)' from 'Root' store
libwdi:info [RemoveCertFromStore] deleted existing certificate 'CN=USB\XXXXXX (libwdi autogenerated)' from 'TrustedPublisher' store
libwdi:debug [CreateSelfSignedCert] set Enhanced Key Usage, URL and CPS
libwdi:debug [CreateSelfSignedCert] created new key container
libwdi:debug [CreateSelfSignedCert] generated new keypair
libwdi:info [CreateSelfSignedCert] created new self-signed certificate 'CN=USB\XXXXXX (libwdi autogenerated)'
libwdi:debug [SelfSignFile] successfully created certificate 'CN=USB\XXXXXX (libwdi autogenerated)'
libwdi:info [SelfSignFile] added certificate 'CN=USB\XXXXXX (libwdi autogenerated)' to 'Root' and 'TrustedPublisher' stores
libwdi:info [SelfSignFile] successfully signed file 'C:\Users\Reese\usb_driver\libnx_USB_comms.cat'
libwdi:info [SelfSignFile] successfully deleted private key
libwdi:debug [wdi_install_driver] using progress bar mode
libwdi:error [install_driver_internal] this application does not contain the required 64 bit installer
libwdi:error [install_driver_internal] please contact the application provider for a 64 bit compatible version
Driver Installation: FAILED (Requested resource not found)
1 device found.
libwdi:debug [wdi_create_list] Hardware ID: USB\XXXXXX
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_FF&SubClass_FF&Prot_FF
libwdi:debug [wdi_create_list] Driverless USB device (12): USB\XXXXXX\SERIALNUMBER
libwdi:debug [wdi_create_list] Device description: 'libnx USB comms'
 
I'm on Windows 10 64-bit. Below is the logs. I redacted some info with XXXXXX:

Zadig 2.4.720
Windows 10 64-bit (Build 17134)
ini file 'zadig.ini' not found - default parameters will be used
default driver set to 'WinUSB'
1 device found.
libwdi:debug [wdi_create_list] Hardware ID: USB\XXXXXX
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_FF&SubClass_FF&Prot_FF
libwdi:debug [wdi_create_list] Driverless USB device (12): USB\XXXXXX\SERIALNUMBER
libwdi:debug [wdi_create_list] Device description: 'libnx USB comms'
Using inf name: libnx_USB_comms.inf
Successfully extracted driver files.
Installing driver. Please wait...
libwdi:info [extract_binaries] successfully extracted driver files to C:\Users\Reese\usb_driver
libwdi:info [wdi_prepare_driver] successfully created 'C:\Users\Reese\usb_driver\libnx_USB_comms.inf'
libwdi:info [wdi_prepare_driver] Creating and self-signing a .cat file...
libwdi:debug [AddFileHash] 'libusb0.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\amd64\libusb0.dll'
libwdi:debug [AddFileHash] 'libusb0_x86.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\amd64\libusb0_x86.dll'
libwdi:debug [AddFileHash] 'libusbk.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\amd64\libusbk.dll'
libwdi:debug [AddFileHash] 'libusbk.sys': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\amd64\libusbk.sys'
libwdi:debug [AddFileHash] 'libusbk_x86.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\amd64\libusbk_x86.dll'
libwdi:debug [AddFileHash] 'wdfcoinstaller01011.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\amd64\wdfcoinstaller01011.dll'
libwdi:debug [AddFileHash] 'libnx_usb_comms.inf': INF type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\libnx_usb_comms.inf'
libwdi:debug [AddFileHash] 'libusb0.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\x86\libusb0.dll'
libwdi:debug [AddFileHash] 'libusb0_x86.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\x86\libusb0_x86.dll'
libwdi:debug [AddFileHash] 'libusbk.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\x86\libusbk.dll'
libwdi:debug [AddFileHash] 'libusbk.sys': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\x86\libusbk.sys'
libwdi:debug [AddFileHash] 'wdfcoinstaller01011.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\Users\Reese\usb_driver\x86\wdfcoinstaller01011.dll'
libwdi:info [CreateCat] successfully created file 'C:\Users\Reese\usb_driver\libnx_USB_comms.cat'
libwdi:info [RemoveCertFromStore] deleted existing certificate 'CN=USB\XXXXXX (libwdi autogenerated)' from 'Root' store
libwdi:info [RemoveCertFromStore] deleted existing certificate 'CN=USB\XXXXXX (libwdi autogenerated)' from 'TrustedPublisher' store
libwdi:debug [CreateSelfSignedCert] set Enhanced Key Usage, URL and CPS
libwdi:debug [CreateSelfSignedCert] created new key container
libwdi:debug [CreateSelfSignedCert] generated new keypair
libwdi:info [CreateSelfSignedCert] created new self-signed certificate 'CN=USB\XXXXXX (libwdi autogenerated)'
libwdi:debug [SelfSignFile] successfully created certificate 'CN=USB\XXXXXX (libwdi autogenerated)'
libwdi:info [SelfSignFile] added certificate 'CN=USB\XXXXXX (libwdi autogenerated)' to 'Root' and 'TrustedPublisher' stores
libwdi:info [SelfSignFile] successfully signed file 'C:\Users\Reese\usb_driver\libnx_USB_comms.cat'
libwdi:info [SelfSignFile] successfully deleted private key
libwdi:debug [wdi_install_driver] using progress bar mode
libwdi:error [install_driver_internal] this application does not contain the required 64 bit installer
libwdi:error [install_driver_internal] please contact the application provider for a 64 bit compatible version
Driver Installation: FAILED (Requested resource not found)
1 device found.
libwdi:debug [wdi_create_list] Hardware ID: USB\XXXXXX
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_FF&SubClass_FF&Prot_FF
libwdi:debug [wdi_create_list] Driverless USB device (12): USB\XXXXXX\SERIALNUMBER
libwdi:debug [wdi_create_list] Device description: 'libnx USB comms'
It's a longshot, but remove Zadig and redownload it here. Your version is slightly different from mine.

As for the problem in the logs, it's this: "this application does not contain the required 64 bit installer"
 
It's a longshot, but remove Zadig and redownload it here. Your version is slightly different from mine.

As for the problem in the logs, it's this: "this application does not contain the required 64 bit installer"

I downloaded it but now I see 0 devices in Zadig.

upload_2019-8-4_20-16-13.png
 

Site & Scene News

Popular threads in this forum