Skip to content
isdahl.org

1. Install NetUsb360

NetUsb360 lets the console use a USB Ethernet adapter instead of its own 100 Mbit/s network port. Skip this part if you don’t use an adapter. If you do, install it first: it has to be the first plugin that loads.

You need dashboard/kernel 17559 and a console that loads plugins with DashLaunch or RGLoader. See Before you start.

  1. Check your adapter. The driver picks the chipset from the adapter’s USB IDs, not its brand name. Check the chipset before you buy: adapters with the same name can use different chips in later revisions.

    Chipset USB ID Example adapters Notes
    ASIX AX88179 0B95:1790 rev 1 TP-Link UE306 Used for all the speed results
    ASIX AX88179A / AX88179B 0B95:1790 rev 2
    ASIX AX88772D 0B95:1790 rev 3
    ASIX AX88279 0B95:1790 rev 4
    ASIX AX88178A 0B95:178A
    ASIX AX88178 0B95:1780 The original devkit adapter chip
    Realtek RTL8153 / RTL8153B 0BDA:8153 Hardware versions 3–6 and 8–9
    Realtek RTL8153 2357:0601 TP-Link UE300 New in 1.1

    A USB 3.0 or gigabit adapter works, but the Xbox’s USB 2.0 port sets the speed limit.

  2. Download the driver. Get it from the latest NetUsb360 release. Each release has two builds, both for a retail kernel 17559:

    File What it is Use it when
    NetUsb360.xex Standard build. All experimental options are off. You want the safe choice.
    NetUsb360-acksmall.xex Adds ACK batching: small packets, mostly TCP acknowledgements, share a USB transfer. Experimental. You have an original AX88179 adapter (such as the TP-Link UE306) and want the fastest uploads to the Xbox.

    With the acksmall build, long, unlimited transfers from the Xbox to a PC have not been fully checked yet, and a freeze was seen once in that direction. If your console freezes during downloads from the Xbox, go back to NetUsb360.xex.

  3. Copy it to the console. NetUsb360’s own guide uses Hdd:\Plugins\NetUsb360.xex as its example. If you’re also installing NetDisc360, you can put it on the root of your USB drive instead, next to NetDisc360’s plugins, as NetDisc360’s install guide does. The example files use that place.

    Keep a copy of your old launch.ini and driver so you can switch back.

  4. Load it as the first plugin.

    In launch.ini, put it in plugin1 and move your other plugins down, so it loads before xbdm.xex. Use the path where you put the file. NetUsb360’s own example:

    launch.ini
    [Plugins]
    plugin1 = Hdd:\Plugins\NetUsb360.xex
    plugin2 = Hdd:\Plugins\xbdm.xex

    Installing NetDisc360 too? Its two plugins come right after NetUsb360, and other plugins such as xbdm.xex after those. Example files has the whole [Plugins] section.

    Coming from CUsbEnet? Put NetUsb360.xex in its place, and don’t load both. NetUsb360 used to be called UsbNet360: an old UsbNet360.xex works the same, so keep it, or rename it and change launch.ini to match.

  5. Plug in the adapter and restart. Plug the adapter into a USB port on the Xbox, connect it to your router or switch with a network cable, and restart the console.

  6. Check the network. Aurora, FastFTP360 and your other apps now use the adapter. The IP address they show comes from your router as usual.

Installing the driver doesn’t touch the NAND. To remove it, take it out of launch.ini or rgloader.ini.

NetUsb360 install docsWhich file to use, loading it with DashLaunch or RGLoader, and how to remove it.