Jump to content

NS-USBLoader 0.3.2

Conéctate para seguir esto  

1 Screenshot

NS-USBloader is a PC-side TinFoil (USB and Network) and GoldLeaf (USB) NSP installer. Replacement for default usb_install_pc.py, remote_install_pc.py (never ever use this. even if you brave. no idea why it works.) and GoldTree.

With GUI and cookies. Wokrs on Windows, macOS and Linux.

System requirements

JRE 8u60 or higher.


How to start it on..


  • Install JRE/JDK 8u60 or higher (openJDK is good. Oracle's one is also good). JavaFX not needed, if you're interested (it's embedded).
root # java -jar /path/to/NS-USBloader.jar


  • Double-click on downloaded .jar file. Follow instructions. Or see 'Linux' section.
  • Set 'Security & Privacy' settings if needed.
  • If you use different MacOS (not Mojave) - check release section for another JAR file.


  • Download Zadig
  • Open TinFoil. Set 'Title Management' -> 'Usb install NSP'
  • Connect NS to PC
  • Open Zadig
  • Click 'Options' and select 'List All Devices'
  • Select NS in dropdown, select 'libusbK (v3.0.7.0)' (version may vary), click 'Install WCID Driver'
  • Check that in device list of you system you have 'libusbK USB Devices' folder and your NS inside of it
  • Download and install Java JRE (8+)
  • Get this application (JAR file) double-click on on it (alternatively open 'cmd', go to place where jar located and execute via java -jar thisAppName.jar)

And how to use it?

The first thing you should do it install TinFoil (Adubbz) or GoldLeaf (XorTroll) on your NS. I recommend using TinFoil, but it ups to you. Take a look on app, find where is the option to install from USB and/or Network. Maybe this article will be helpful.

Here is the version of 'not perfect but anyway' tinfoil I use. Ok, I'm almost sure that this version has bugs. I don't remember where I downloaded it. But it works for me somehow.

Let's rephrase, if you have working version of TinFoil DO NOT use this one. Ok. let's begin.

There are three tabs. Firs one is main.

First tab.

At the top of you selecting from drop-down application and protocol that you're going to use. For GoldLeaf only USB is available. Lamp icon stands for switching themes (light or dark).

Then you may drag-n-drop folder with NSPs OR files to application or use 'Select NSP files' button. Multiple selection for files available. Click it again and select files from another folder it you want, it will be added into the table.


There you can select checkbox for files that will be send to application (TF/GL). Since GoldLeaf allow you only one file transmission per time, only one file is available for selection. Also you can use space to select/un-select files and 'delete' button for deleting. By right-mouse-click you can see context menu where you can delete one OR all items from the table.

Second tab.

Here you can configure settings for network file transmission. Usually you shouldn't change anything. But it you're cool hacker, go ahead! The most interesting option here is 'Don't serve requests'. Architecture of the TinFoil networking is working interesting way. When you select in TF network NSP transfer, application will wait at port 2000 for the information about where should it take files from. Like ''. Usually NS-USBloader serves requests by implementing simplified HTTP server and bringing it up and so on. But if this option selected, you can define path to remote location of the files. For example if you set in settings 'shared.lan:80/ROMS/NS/' and add in table file 'my file.nsp' then NS-USBloader will simply tell TinFoil "Hey, go take files from 'shared.lan:80/ROMS/NS/my+file.nsp' ". Of course you have to bring 'shared.lan' host up and make file accessible from such address. All this requires more investigation. BTW, the issue could be that NS-USBloader encodes 'space' char as '+' and some web-servers understand 'space' as '%20D'. It could be fixed in later versions of NS-USBloader if I go deeper in it or you leave me feedback with information/request. As I said, this feature is interesting, but I guess won't be popular.

Third tab.

That's where all logs dropped. Verbose information about transmissions comes here.

Why when 'Net' once started it never ends?

Because there is HTTP server inside of application. It can't determine the moment when all transmissions finished (unless they failed). So you have to look on your NS screen and 'Interrupt' is once done.

by Dmitry Isaeko.

Que novedades incluye la versión 0.3.2


  • Speed issue fixed for TF NET installations.
  • Progress bar works for TF NET installations.
  • Progress bar behaviour changed for USB installations. Simplified (simpler code for decorations -> a bit faster files installations).
  • Minor changes to TF side.
  • 'Don't serve requests' option is working now as expected.