Saved searches
Use saved searches to filter your results more quickly
Cancel Create saved search
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to start server on Mac #4
lesca opened this issue Feb 24, 2021 · 14 comments
Failed to start server on Mac #4
lesca opened this issue Feb 24, 2021 · 14 comments
Comments
lesca commented Feb 24, 2021
Click «Start Server» the error comes up in the terminal:
It looks like the script cannot find the device, no matter whether I connect my switch or not.
Exception in thread Thread-1: Traceback (most recent call last): File "/Users/lesca/opt/anaconda3/lib/python3.8/threading.py", line 932, in _bootstrap_inner self.run() File "/Users/lesca/opt/anaconda3/lib/python3.8/threading.py", line 870, in run self._target(*self._args, **self._kwargs) File "dbibackend", line 170, in start_server connect_to_switch() File "dbibackend", line 149, in connect_to_switch dev = usb.core.find(idVendor=0x057E, idProduct=0x3000) File "/Users/lesca/opt/anaconda3/lib/python3.8/site-packages/usb/core.py", line 1299, in find raise NoBackendError('No backend available') usb.core.NoBackendError: No backend available The text was updated successfully, but these errors were encountered:
lesca commented Feb 24, 2021 •
OS Version: 10.15.7
Python Version: 3.8.5
`# pip freeze output
libusb==1.0.23b7
pyusb==1.1.1
usb==0.0.83.dev0
lunixoid commented Feb 24, 2021 •
@lesca ,
Thank you. Could you try to install native libusb? F.e. via brew:
$ brew install libusb
lesca commented Feb 25, 2021
Thanks @lunixoid , much better now. It now shows «waiting for switch» after clicking the «start server» button.
But once I connect switch, by selecting «Install title from usb» from DBI, I got message below from console:
It happens every time I connect switch to my Mac.
Switch side, shows «waiting for dbibackend to be run . » but nothing happens.
Mac side, the dbibackend stops output new «waiting for switch» message.
Traceback (most recent call last): File "/Users/lesca/opt/anaconda3/lib/python3.8/threading.py", line 932, in _bootstrap_inner self.run() File "/Users/lesca/opt/anaconda3/lib/python3.8/threading.py", line 870, in run self._target(*self._args, **self._kwargs) File "dbibackend", line 170, in start_server connect_to_switch() File "dbibackend", line 156, in connect_to_switch dev.set_configuration() File "/Users/lesca/opt/anaconda3/lib/python3.8/site-packages/usb/core.py", line 905, in set_configuration self._ctx.managed_set_configuration(self, configuration) File "/Users/lesca/opt/anaconda3/lib/python3.8/site-packages/usb/core.py", line 113, in wrapper return f(self, *args, **kwargs) File "/Users/lesca/opt/anaconda3/lib/python3.8/site-packages/usb/core.py", line 159, in managed_set_configuration self.backend.set_configuration(self.handle, cfg.bConfigurationValue) File "/Users/lesca/opt/anaconda3/lib/python3.8/site-packages/usb/backend/libusb1.py", line 812, in set_configuration _check(self.lib.libusb_set_configuration(dev_handle.handle, config_value)) File "/Users/lesca/opt/anaconda3/lib/python3.8/site-packages/usb/backend/libusb1.py", line 604, in _check raise USBError(_strerror(ret), ret, _libusb_errno[ret]) usb.core.USBError: [Errno 19] No such device (it may have been disconnected) lunixoid commented Feb 26, 2021
Seems libusb lose switch. Could you try another type-c cable or adapter?
Spaider15 commented May 26, 2021
faced with the same problem, first run server then plug in switch
lunixoid commented May 26, 2021
@Spaider15
Thank you. Could you provide information about your environment like above?
Also please check your USB cable or try another one.
lunixoid commented Jun 28, 2021
Close outdated issue.
lunixoid closed this as completed Jun 28, 2021
erralb commented Sep 17, 2021 •
I’m having a similar issue :
python3 dbibackend-master/dbibackend/dbibackend.py ./games Waiting for switch Waiting for switch Waiting for switch Waiting for switch Waiting for switch Waiting for switch Waiting for switch Waiting for switch Waiting for switch Traceback (most recent call last): File "/Users/pierre/Switch/dbibackend-master/dbibackend/dbibackend.py", line 210, in main() File "/Users/pierre/Switch/dbibackend-master/dbibackend/dbibackend.py", line 204, in main connect_to_switch(), File "/Users/pierre/Switch/dbibackend-master/dbibackend/dbibackend.py", line 173, in connect_to_switch switch_context = UsbContext(vid=0x057E, pid=0x3000) File "/Users/pierre/Switch/dbibackend-master/dbibackend/dbibackend.py", line 42, in __init__ dev.set_configuration() File "/usr/local/lib/python3.9/site-packages/usb/core.py", line 915, in set_configuration self._ctx.managed_set_configuration(self, configuration) File "/usr/local/lib/python3.9/site-packages/usb/core.py", line 113, in wrapper return f(self, *args, **kwargs) File "/usr/local/lib/python3.9/site-packages/usb/core.py", line 159, in managed_set_configuration self.backend.set_configuration(self.handle, cfg.bConfigurationValue) File "/usr/local/lib/python3.9/site-packages/usb/backend/libusb1.py", line 812, in set_configuration _check(self.lib.libusb_set_configuration(dev_handle.handle, config_value)) File "/usr/local/lib/python3.9/site-packages/usb/backend/libusb1.py", line 604, in _check raise USBError(_strerror(ret), ret, _libusb_errno[ret]) usb.core.USBError: [Errno 19] No such device (it may have been disconnected) Weird thing is it works sometimes and sometimes not. I tried different cables
DBI v654
La solución definitiva para la instalación de archivos NSP/NSZ/XCI con varias caractericas avanzadas para potenciar tu experiencia con Nintendo Switch.
DBI soporta instalación vía MTP, USB (usando el script dbibackend o la herramienta dbi-nsw), red (sando tu propio servidor http) o memorias USB externas.
Instalación
Descarga la última versión de la aplicación desde esta misma página de forma completamente gratuita, descomprime el archivo descargado y copia los archivo dbi.nro y dbi.config a tu tarjeta SD en la ruta /switch/DBI/.
DBI puede ser ejecutado tanto en modo applet (desde Album) o en modo aplicación (título). Aun así, está diseñada para utilizarse en primera instancia en modo applet.
Si has lanzado DBI de forma satisfactoria en modo applet verás una pantalla con fondo azul. En modo aplicación el fondo será negro.
Usage
Interface
- Browse SD Card — installation of .NSP / .NSZ / .XCI files from your SD card.
- Browse USB0 Drive — installation of .NSP / .NSZ / .XCI files from an external FAT32 or exFAT formatted USB drive (will only appear if a USB drive is connected)
- Install title from USB — installation of .NSP / .NSZ / .XCI from a PC via USB 2.0 or 3.0 cable using the included dbibackend script. Main menu hotkey for this option: Y button.
- Install title from Gamecard — install a game from gamecard to the console’s internal NAND or SD card (will only appear if a gamecard is inserted)
- Home server — install games over your local network (HTTP) using a LAN USB adapter or WiFi network. For full details see Home server
- Browse installed applications — view installed titles including base, update, DLC and whether or not a LayeredFS mod is present. Displays your total play time and how many times you’ve launched the title. Check file integrity for errors, transfer game data between internal NAND and SD card, delete individual or multiple titles and their LayeredFS mods with one click, individually remove updates and DLC and use the Reset Required version function to restore the system update check for the selected game back to base. Main menu hotkey for this option: L button.
- Cleanup orphaned files — removes all orphaned installed content, tickets and pending firmware updates from the system with one click.
- Browse tickets — view and manually delete system tickets for games.
- Run MTP responder — enables DBI’s internal MTP server to connect the Switch to a PC or to an Android device (Some tested phone/tablet devices: Pixel 3, Xiaomi Mi A1, Lenovo Tab 4 7 «TB-7304X). On your device you will be presented with several virtual drives for installation and many advanced features for file management on your SD card and NAND. Please see Run MTP Responder for a full overview.
- Exit — exit from the program. Main menu hotkey for this option: + button
The bottom left corner of DBI displays the total amount of data on your currently on your SD card along with the full capacity. The bottom right corner gives you the same information for your NAND’s usable space in HOS.
Bottom center (dbi: XXX) is the DBI version number — you should always use the most recent version.
Browse SD Card / Browse USB0 Drive
Select this option if you want to install games, updates and DLC from files that exist on your SD card or external USB drive. Press A to open the folder and B to go back. After opening the folder containing your installation files use the X button to select single or multiple files for installation. The Y button inverts your selections and the color of the name of the selected files will change from white to light blue.
Press the A button to confirm. A window with installation options will appear:
- Total transfer size — the total amount of data (.NSP / .NSZ / .XCI files) selected for installation.
- Total install size — the amount of free space required to install the selected files.
- Install target — data installation location: NAND — internal memory of the Nintendo Switch console, SD — SD card, AUTO — by default this will install to your SD card but if you don’t have enough space the installation will fall back to NAND (internal memory).
- Delete after install — deletes installation files (.NSP / .NSZ / .XCI files) from the source after they have been successfully installed; for this to work, the «Read-only» attribute must be removed from files if present. By default, files are not deleted. The option is visible only when installing from an SD card / external USB drive.
- Turn off screen — turns off the screen during installation to conserve battery, after installation successfully completes the screen will automatically turn back on. This option only works in handheld mode.
- Select Start install to begin the installation. After a successful installation Installation Complete. Press B to return will appear.
DBI will automatically and immediately remove old updates when installing a new update for a game, so you don’t have to worry about the extra space they occupy.
Install title from USB
If you cannot use DBI’s MTP responder this is another convenient method for installing titles over USB. Installing over USB allows you to transfer files directly from your PC for example, which avoids the inconvenience and of having to first move the file to your SD card and then install it. Compared to using the MTP responder this mode will also allow direct installation of .XCI files.
Main menu hotkey for this option: Y button.
In order to use this option you will first require dbibackend ( dbibackend.exe for Windows, dbibackend from dbibackend.tar.xz for all). Launch dbibackend, select the files to install, select Start server, connect a USB-C cable from your PC to your Switch and select Install title from USB in DBI.
From here you will select and install your files on the Switch in the same fashion as using Browse SD Card / Browse USB0 Drive
To quickly send files or folders with games for installation, right-click on them, select Send from dbibackend and the installation files will be immediately placed in dbibackend’s queue. To configure this in Windows, press Win + R , enter shell: sendto and create a shortcut for dbibackend.exe in the folder.
Home server
The «Home server» option will appear if the Network install sources section has been configured in dbi.config (more about this file below). You can specify the name of the option as required in the configuration file
To install games over your network, edit the dbi.config file located in the /switch/DBI/ folder, following the example:
; Network install sources [Network sources] ; =| Home server=ApacheHTTP|http://192.168.1.47/Nintendo/Switch/ Install any other HTTP server with DirectoryListing enabled on your PC: Apache, Mongoose, Python SimpleHTTP, sheret, rclone, etc.
Example for nginx on Windows: edit the file /nginx/conf/nginx.conf , registering the address of your Switch in location , instead of the 127.0.0.1 specified in the example (or your entire subnet like 192.168.1.1/24 or 192.168.0.0/16); it can be found on Switch in System Preferences > Internet:
location / < root html; index index.html index.htm; >location /Nintendo/Switch/
Save the config, run nginx.exe , allow the program to access the network, then copy the desired game to the local /nginx/html/Nintendo/Switch/ folder on your PC, and on the Switch select “Home server”. You will now be presented with the usual interface for installing files and you can start installing files over the network. You can stop the web server via nginx -s stop.
For the server address in dbi.config, you can also use a domain name, for example, your remote VPS — suggested to use with HTTP Basic authentication e.g.: http://user:password@host:port/Nintendo/Switch/
ApacheHTTP|Network repo|http://127.0.0.1/Nintendo/Switch/ ApacheHTTP|WWW VPS repo|http://www.myveryownswitchvpsdomain.su/Nintendo/Switch/ Generate the htpasswd file, put it in /nginx/conf/, then adjust the nginx.conf file as follows:
location /Nintendo/Switch/
Login «switch», password «pwd»:
switch:N/omUzCtg+qoee+x4ttjgIls9jk= Browse installed applications
In Browse installed applications you can see a list of installed programs, updates and DLC with their occupied space, version (display version and hex version), their titleID, the total game time and the number of launches, the presence of installed LayeredFS mods for the game (for Atmosphére). Main menu hotkey for this option: L button:
The total number of installed applications (e.g. games and homebrew nsps) is displayed at the top of the screen. Any installed data can be transferred between internal NAND and SD card, it is possible to individually select and uninstall multiple games (b) / updates (u) / DLC (d)together with their associated LayeredFS mods (l) (detected at /atmosphere/contents/ ) or you can individually select updates and DLC for deletion. The Reset Required version function will force restore the system update check for the selected game back to base (this is also done automatically with installation or removal of game updates):
By pressing the R button you can sort the game list as you prefer — alphabetically (default) or by last usage. Press the A button to enter the menu of the selected game, the — button deletes the game and its (non-personalized) ticket, the D-pad selects games, the left stick scrolls through the list of games and the ZR and ZL buttons flip through the list of games screen by screen.
You can also check (verify) games for their integrity by selecting the file to check and then selecting Check integrity
Cleanup orphaned files
Cleanup orphaned files automatically cleans unnecessary game files, files from interrupted game installations, downloaded (officially) OFW firmware updates and all unused game tickets if found.
Browse tickets
View and delete game tickets. Ticket (or encrypted title key) is special encrypted unique information about the rights to launch the content of the game which is installed in the system during the installation of each game (000 at the end of titleID) / update (800 at the end of titleID) / each DLC. + means the presence of an installed game, [c] — common-ticket (installed game dump or update), [p] — personalized-ticket (game purchased from the eShop)
You may be able to resolve certain errors with this for example if you know exactly what you are doing. You can remove individual tickets from a specific game and/or its update/DLC.
In most case it’s better not to touch anything here in order to avoid errors in starting games.
Run MTP responder
Run MTP responder run the built-in DBI MTP server to connect to your PC or Android device via USB-C OTG (phone / tablet / other devices). Main menu hotkey for this option: X button (same button to exit MTP mode). After successfully connecting the USB cable to the PC and starting the MTP server in DBI, you’ll see the following on your computer:
1: External SD Card, for viewing, copying and deleting files and folders from/to a PC and from/to your SD card. Drop a file larger than 4GB onto the SD card and DBI will automatically split the file into an archived folder, which allows the Switch to see it as a single file, with this you can for example very easily add a >4GB .xci for use in SX OS, or add a >4GB movie for watching in pPlay.
2: NAND User, viewing, copying files and folders on a PC from the Switch’s internal memory to its USER system partition (this partition is read-only).
3: NAND System, viewing, copying files and folders on a PC from the internal memory of the Switch to its SYSTEM system partition (the partition is read-only).
4: Installed games, to view installed games.
В Installed games all installed games are displayed from both in NAND (internal memory of the Switch) and SD card. To dump installed games to your PC in .NSP format, just copy the folder with the name of the game from Installed games to your PC. A common ticket with completely cleared personal information is generated based on your personalized ticket. Your dump will be in separated files — the game itself, the update and DLC. If cheats or mods have been installed for the game, they will be located in the Mods & Cheats folder. You can also dump a single combined multicontent file containing the game itself, the update and all DLC. This file is located right at the root of the Installed gamessection. The generated DBI InstalledApplications.csv is also stored here, with a table of the list of installed games, their TitleID and the current version.
5: MicroSD install Drop or copy your NSP or NSZ files in this folder. When the transfer is complete the game will be installed on the SD cardof your console. When installing NSZ files, keep in mind that their actual size may differ greatly from their original size after installation: so if for example you start with 2GB free on your memory card and you do not have enough space to install an NSZ of 1GB in size, that is because NSZ files are compressed and must be decompressed for installation.
6: NAND install: Drop or copy your NSP or NSZ files in this folder. When the transfer is complete the game will be installed on the internal memory of your console. When installing NSZ files, keep in mind that their actual size may differ greatly from their original size after installation: so if for example you start with 2GB free on your memory card and you do not have enough space to install an NSZ of 1GB in size, that is because NSZ files are compressed and must be decompressed for installation.
7: Saves: Access to all game saves — in accounts (Account), system programs (System), in Background Content Asymmetric synchronized delivery and Transmission (BCAT, for example: events in ACNH), temporary (Temporary), cache (Cache, for example: addons in DOOM), system BCAT (SystemBCAT), — stored in the internal memory of the Switch; in the Installed games folder — save for the currently installed games, Uninstalled games — save from deleted games that were previously launched. From here, you can make a backup of them by copying them to a PC, and also delete unnecessary ones — for this, open the folder with the name of the game you need, then delete the folder with the nickname of your account / Device-save. In order to restore the save, copy them to the appropriate folder from your PC. DBI does not require pre-launching the game to restore a save, however this only applies to regular saves. BCAT or Cache saves require a pre-launch of the game before restoring.
8: Album: access to screenshots and videos (Album), similar to Nintendo’s feature added OFW 11.0.0.
9: Gamecard: with a gamecard inserted into the Switch you can dump to .XCI or trimmed .XCI on the PC, along with the update built into it if it exists. The personal RSA certificate automatically removed and is dumped separately.
After activating the MTP server on the Switch a window will appear with your account nickname and its UID, as well as the number of game saves:
To turn off the MTP server and exit to the main menu, press the X button.
Exit
Exit — exit from the program in HOS, either to hbmenu or bypassing hbmenu directly to the homescreen (this is configured in dbi.config). If DBI was launched from a title / forwarder, the program will restart or remain on a black screen.
Errors and warnings
Warnings
- «HASH MISMATCH» — usually this is NOT an ERROR and the game was simply converted from an .XCI and everything is in order. Sometimes if there are problems with the integrity of the file, download it, rehash it, transferring data via a USB cable / port / during the installation process between the PC and the Switch. If the game still does not start or starts with an error, try reinstalling it again, check or replace the USB cable / SD card / change the USB port.
- DELTA SKIPPED — this is NOT an ERROR but a notification that unnecessary and unused delta fragments in the update file were skipped during installation.
- «No tickets found. Possibly this NSP was converted from XCI.» — this is NOT an ERROR and the performance of the game will not be affected. This informs you that the files do not include tickets, they may have been dumped from an .XCI file or converted to Standard Crypto.
- «WARNING» title marked as Application but has AddonContent — this is NOT an ERROR and usually it indicates a non-standard .NSP homebrew game, for example if an AddonContent flag (DLC) was added to the Application title (main game, v0). If the application starts and works then everything is in order.
ERRORs
- «Can not find file for ncaid» — The installation file of the game is corrupt (it does not contain the required .nca from the .cnmt list).
- «Invalid PFS0 magic!» — download the installation file of the game and check its integrity, this file is corrupt.
- «Received less data than expected» or Installation aborted — data transfer error, recheck and if necessary replace the USB cable / USB port between the Switch and the PC. Also make sure you have the most recent version of the DBI installed.
- «std::bad_alloc» — rename the file without special characters and Cyrillic in the name and path to it, plus make sure that you are using the latest version of DBI and that the latest supported version of OFW and CFW is installed on the console.
- «Nothing to install» in the file selection window — rename the file without special characters, hieroglyphs or Cyrillic in the name and path to it.
- «INVALID LENGTH» — check the USB-C cable connection to your USB port, try with another USB-C cable, check the integrity of the game file and the SD card for errors, when installing via MTP — try to run DBI in application mode (title override) holding the R button while launching a title.
- «[FAILED] Unknown error» when installing .tik (ticket) — add the latest sigpatches for Atmosphére.
- «605: Content or placeholder path not exists» or «SOME CONTENTS ARE MISSING» — broken file system on your SD card, or a non-working / low-quality flash drive. Check it in chkdsk and h2testw, if there are no errors reformat to FAT32.
- WARNING! Extra buffers exceeded, when installing via MTP — try to run DBI in application mode (title override) holding the R button while launching a title or alternatively via NSP forwarder and use a faster microSD card with a different USB cable / port.
- No tickets found but they are required — incorrect (incomplete, no ticket but with titlerights) dump of the game, use another one.
- SOME CONTENTS ARE MISSING. APPLICATION WILL BE UNUSABLE — container is incomplete, check the integrity of the game installation file.
dbi.config
The dbi.config file was added starting with version 253. It is located next to DBI.nro and replaces the old flags files dbi.default.ascii and dbi.network.config and also adds several new options for easy customization of settings for the user.
Let’s take a look at its contents:
; General settings [General] ; Use libnx's default font for ASCII symbols DefaultASCII=true ; Use libusbhsfs for access to USB mass storage drives connected to switch or dock UseLibUsbHsFS=true ; Direct exit to homescreen ExitToHomeScreen=true ; Visibility of main menu items [MainMenu] ; Browse and install files from MicroSD card BrowseSD=true ; Browse and install files from USB flash drives and HDD USBHost=true ; Browse and install files from PC via dbibackend BackendInstall=true ; Install game from inserted game cartridge GameCard=true ; Browse and install files from configured network sources Network=true ; Browse installed applications BrowseApps=true ; Clean up files left from bad installs/old updates/unused tickets and so on Cleanup=true ; View where you can view or delete installed tickets Tickets=true ; MTP responder MTP=true ; Install options [Install] ; Check NCA hash during install CheckHash=true ; MTP options [MTP] ; Log all files, id disabled transfer shows only for files >= 4M LogAllFiles=false ; Show or not NSP that includes base game, latest update and all DLC in single multi-title file ShowCombinedNSP=true ; Show or not virtual "Mods & cheats" folder that redirects to sdmc:/atmosphere/contents/TITLEID ShowMAC=true ; Show user defined shortcuts to MircoSD folders as separate storages CustomStorages=true ;Enable or disable various MTP storages [MTP Storages] 1: External SD Card=true 2: Nand USER=true 3: Nand SYSTEM=true 4: Installed games=true 5: MicroSD install=true 6: NAND install=true 7: Saves=true 8: Album=true 9: Gamecard=true ; Network install sources [Network sources] ; name>= | ;Home server=ApacheHTTP|http://192.168.1.47/Nintendo/Switch/ [MTP custom storages] ; name>= ;Homebrew=sdmc:/switch
General settings
- DefaultASCII — true includes a standard font, false includes an alternative font
- UseLibUsbHsFS — true enables libusbhsfs library for working with external USB drives via USB-OTG on Switch, false disables it.
- ExitToHomeScreen — if false, the exit from DBI occurs in the hbmenu, if true, to the Switch’s home menu
MainMenu
Shows the corresponding menu items.
true — display in main menu, false — hide from main menu
- BrowseSD — item «Browse SD card, to install games from Sd card
- USBHost — item «Browse USB0 Drive, to install games from an external USB
- BackendInstall — item «Install title from USB, for installing games from PC via backend
- GameCard — item «Install title from Gamecard, to install the contents of the cartridge in the memory of the console
- Network — item «Home server, to install games from a home web server
- BrowseApps — item «Browse installed applications, to manage installed applications
- Cleanup — item «Cleanup orphaned files, to clean up» orphaned «files from the memory card
- Tickets — item «Browse tickets, to manage tickets
- MTP — item «Run MTP responder, to start MTP
Install
- CheckHash — if true, hashes of .nca files are checked when installing games on the Switch, if false, no.
MTP
- LogAllFiles — false disables logging of all files when working with MTP; if true, all files are logged, even those that are less than 4MB.
- ShowCombinedNSPInInstalledGames — false disables display of combined (multi-title .NSP-file) titles.
- ShowMACInInstalledGames — false turns off the display of the virtual directory «Mods & cheats» in the Installed games item in the MTP, redirecting along the path /atmosphere/contents/%titleid_game% to the memory card.
- CustomStorages — show or hide storages, listed on MTP custom storages section
MTP Storages
Show relevant items when MTP Responder is running on PC / Android, by default all items are enabled for display.
true — display in MTP on PC, false — no
The item names correspond to the titles of the sections
Network sources
Names and addresses are set for installing games over the network (via WiFi / LAN adapter)
MTP custom storages
Custom items for MTP mode for quick access to folders on your memory card. Format: = , for example: Homebrew = sdmc: / switch . In MTP mode, a Homebrew folder will appear, referring to the switch folder on your memory card
Other possibilities
Mounting the content of installed titles via MTP
Go to «Browse installed applications» -> Choose apps you need to mount with X -> Press A -> «Mount contents via MTP«
Que novedades incluye la versión v654
Released 20 de Diciembre del 2023
- Bug corregido.
Crea una cuenta o identifícate con la tuya, si ya la tienes, para poder descargar el archivo.
Información del archivo
- Descargas 141
- Enviado 3 de Mayo del 2021
- Actualizado 20 de Diciembre del 2023
- Tamaño del archivo 12.2 MB
No te pierdas nada, síguenos en Twitter o Mastodon! ¿Tienes alguna duda, petición o aporte? Utiliza el foro!
Contenido similar
nxdumptool es una aplicación para realizar dumpeos de juegos de Nintendo Switch desde la propia consola.
Principales características de nxdumptool
Genera volcados completos de imágenes de cartuchos (XCI) con eliminación opcional de certificados y recorte opcional.
Genera paquetes de presentación de Nintendo (NSP) instalables a partir de aplicaciones base, actualizaciones y DLC almacenados en la tarjeta de juego insertada, la tarjeta SD y los dispositivos de almacenamiento eMMC.
Compatible con carros multijuego.
Cálculo de la suma de comprobación CRC32 para los volcados XCI/NSP.
Verificación completa del volcado XCI mediante la base de datos XML de NSWDB.COM (NSWreleases.xml).
Base de datos XML y actualización in-app a través de libcurl.
Volcado preciso de la partición HFS0 en bruto, utilizando la cabecera HFS0 raíz de la tarjeta de juego.
Volcado de datos de archivos de partición HFS0.
Navegador de archivos de partición HFS0 con soporte de volcado manual de archivos.
Programa de volcado de datos de archivos de sección NCA ExeFS.
Programa NCA ExeFS section file browser con soporte de volcado manual de archivos.
Programa NCA RomFS section file dumping.
Programa NCA RomFS section file browser con soporte de volcado manual de archivos.
Volcado manual del certificado de la tarjeta de juego.
Comprobación del espacio libre en la tarjeta SD.
Soporte de división de archivos para todas las operaciones.
Recuperación de los metadatos de la tarjeta de juego utilizando los servicios NCM y NS.
Cálculo de la velocidad de volcado, cálculo de ETA y barra de progreso.
Las operaciones relacionadas con los títulos SD/eMMC instalados requieren un archivo de claves ubicado en «sdmc:/switch/prod.keys».Usa Lockpick_RCM para generarlas.
nxdumptool es una aplicación creada por DarkMatterCore.
NXMP es un reproductor de video para Nintendo Switch basado en MPV. NXMP soporta los formatos de vídeo más populares, así como streaming vía HTTP y FTP, y decodificadores Enigma2.
Instalación
Edit config.ini
[Main] startpath=/switch/nxmp [Network] [Enigma2] La red tiene una sintásis (puedes añadir las fuentes que quieras)
[Network] source=TESTFtp|ftp://user:pass@192.168.1.10:21/path/ source=TestHTTP|http://192.168.1.10/path/ Enigma2 tiene sintásis
[Enigma2] e2address=http://192.168.1.10/ Copia la carpeta nxmp a la tarjeta sd de Switch (/switch/nxmp)
Uso
Mapeo de botones
A seleccionar (reproducir / pausar durante la reproducción) B atrás (detener durante la reproducción) Y Menú principal X muestra OSD (durante la reproducción) R L ZR ZL (buscar +/- durante la reproducción) + Salir de NXMP Botón R Stick Toggle Masterlock (durante la reproducción, solo funcionará el botón A) Dpad Right (durante la reproducción muestra el menú derecho) Dpad Left (durante la reproducción, cierre el menú derecho) R Stick Up / Down Desplazamiento rápido en la lista de archivos FAQ
Pregunta: ¿Mi archivo 4K no funciona? ¿Por qué?
Respuesta Tenga en cuenta que actualmente las aplicaciones Homebrew no pueden acceder al decodificador HW, por lo que todo se hace con la CPU, el archivo 4K es demasiado pesado para ser decodificado
P: ¿Qué es Enigma2?
R: Enigma2 es una aplicación utilizada en receptores de transmisión de video digital (DVB-S, DVB-C, DVB-T) basados en Linux o decodificadores de TV y receptores de televisión de protocolo de Internet.
NXMP ha sido creada por proconsule.
XLink Kai: Evolution VII te permite conectarte con otros usuarios de consola de todo el mundo y jugar gratis a juegos en línea haciendo creer a tu consola que los usuarios a los que se conecta a través de Internet forman parte de una red de área local.
Esta es la base de los juegos system-link, en los que los amigos se reunían en la misma casa y jugaban con dos o más consolas. Con XLink Kai: Evo VII, ahora tienes la opción de poner a prueba tus habilidades con cualquier persona del mundo. En cuanto a los aspectos técnicos del tunelado de paquetes de red, no te aburriremos con eso.
Principales características de XLink Kai: Evolution VII
Compatible con PS2, PS3, PS4, Gamecube, Switch, Xbox, Xbox 360 y Xbox One. 2 modos de juego (Messenger y Arena). Sin WinPCap. Chat integrado en todas las áreas. No requiere redireccionamiento de puertos en casi todas las configuraciones de red. Voicechat de PC a PC y de PC a XBox Dashboard mediante el códec SPEEX. Interfaz de usuario extremadamente sencilla y global. Actualización automática al inicio. Compatible con varias consolas. Compatible con redes inalámbricas (no todas las configuraciones de red inalámbrica). Algoritmos de compresión superiores para reducir el retardo. Compatible con residencias universitarias y proxies como el ISP italiano FastWeb. Clanes de confianza y torneos / ladder arenas. Funcionalidad remota a través de tableros homebrew (sólo para usuarios de XBox). Muchas más funciones por descubrir. XLink Kai es una aplicación creada por el Team XLink.
IPS Patch Creator es una aplicación para Windows que nos permite crear nuestros propios parches IPS para Switch.
La aplicación ha sido creada por mrdude 2478.
Sys-Patch es un módulo de sistema tipo script que parchea fs, es, ldr y nifm en el arranque.
Configuración
sys-patch presenta una configuración simple. Puede editarse manualmente o actualizarse mediante la superposición.
El archivo de configuración se encuentra en /config/sys-patch/config.ini. El archivo se genera una vez que el módulo se ejecuta por primera vez.
[options] patch_sysmmc=1 ; 1=(default) patch sysmmc, 0=don’t patch sysmmc patch_emummc=1 ; 1=(default) patch emummc, 0=don’t patch emummc enable_logging=1 ; 1=(default) output /config/sys-patch/log.ini 0=no log version_skip=1 ; 1=(default) skips out of date patterns, 0=search all patterns Overlay
El overlay se puede utilizar para cambiar las opciones de configuración y ver qué parches se han aplicado.
Sin parche significa que el parche no se aplicó (probablemente no se encontró). Parcheado (verde) significa que fue parcheado por sys-patch. Parcheado (amarillo) significa que ya fue parcheado, probablemente por sigpatches o una construcción personalizada de Atmosphere. ¿Qué se está parcheando?
He aquí un breve resumen de lo que se está parcheando:
fs es ldr nifm fs y es necesitan nuevos parches después de cada nueva versión de firmware. ldr necesita nuevos parches después de cada nueva versión de Atmosphere. el parche nifm ctest permite que el dispositivo se conecte a una red sin necesidad de conectarse a un servidor.
Los parches se aplican en el arranque. Una vez hecho, el sys-module deja de ejecutarse. La huella de memoria (16kib) y el tamaño binario (~50kib) son ambos muy pequeños.
PREGUNTAS FRECUENTES:
Si ya estoy usando sigpatches, ¿tiene sentido usar esto? Sí, en 3 situaciones. Es necesario crear un nuevo parche ldr después de cada actualización de Atmosphere. A veces, se lanza una nueva actualización silenciosa de Atmosphere. Esta herramienta siempre parcheará ldr sin tener que actualizar los parches. Construir Atmosphere desde src requerirá que generes un nuevo parche ldr para ese Atmosphere construido a medida. Esto es bastante fácil debido a los scripts / herramientas públicas que existen por ahí, sin embargo esto siempre será capaz de parchear ldr. Si olvidas actualizar tus parches cuando actualizas tu firmware / Atmosphere, este sys-module debería ser capaz de parchear todo. Así que puede ser utilizado como un fall back. ¿Significa esto que debo dejar de descargar / utilizar sigpatches? No, personalmente recomendaría seguir utilizando sigpatches. La razón es que si esta herramienta se rompe alguna vez, es probable que no sea rápido para arreglarlo. sys-patch ha sido creado por ITotalJustice.
- Política de privacidad
- Contactar
DBI problem on new pc, I cannot seem to make it work no matter what I do
So on my new pc, I tried installing the driver via zadig, at first it saw DBI and then after installing the driver it now sees it as «nintendo switch». Install via usb on backend does not work, and MTP responder only says server started but I can’t see the usual nintendo switch folders (like none at all, I only see local C, D E which are my regular drives).
Need help please.
Locked post. New comments cannot be posted.
Homebrew Question DBI — USB install doesn’t work anymore on 2 out of 3 USB port
Joined Feb 1, 2007 Messages 161 Trophies 1 XP 1,497 Country
Today I experienced a strange behavior with DBI installer where I can’t install NSP via USB anymore, on my usual port that I use.
I do realize last night there was a quite major windows 10 update, perhaps something changed, but I’m puzzled what is it.
what is more confusing is that after trying all 3 USB ports, luckily one of the port works for USB install (I usually use it for wireless mouse adapter).
when I run dbibackend.exe server, one usb port doesn’t detect at all, one port somehow detect the server but failed during installation (switch connection lost), the third USB port works fine.
cable is fine, switch is still charging when I plug it to all of the ports.
btw, I checked on the failed USB port, MTP transfer works fine. I can still access the SD card and delete files.
Perhaps anybody can guide me on how to solve/debug this issue?
I checked with zadig, the driver is still detected as libusbK when I run dbi.
i’m using DBI version 269.
thanks in advance for the help!
Last edited by arabtm, Jun 11, 2021
duckbill007
Well-Known Member
Member
Joined May 5, 2011 Messages 667 Trophies 1 XP 2,319 Country
As for me, I have zero experience with windows.
On Linux I never have any issues with usb, mtp and python.
arabtm
Well-Known Member
OP
Member
Joined Feb 1, 2007 Messages 161 Trophies 1 XP 1,497 Country
As for me, I have zero experience with windows.
On Linux I never have any issues with usb, mtp and python.
oh. bummer ^^’
thank you for replying though
perhaps someone else might help me with this issue.
btw, I want to try the latest DBI 286, but the dbibackend is not .exe in github repo. is it the same as the previous versions?
Last edited by arabtm, Jun 12, 2021
arabtm
Well-Known Member
OP
Member
Joined Feb 1, 2007 Messages 161 Trophies 1 XP 1,497 Country
so after fiddling around, I found the solution where I simply install tinfoil driver and reg file from here:
I assume the windows update messes with the reg file and/or it somehow remove the libusbK driver.
hope this helps if anyone else is having this problem
case closed!
xs4all
Well-Known Member
Member
Joined Jun 9, 2008 Messages 717 Trophies 1 Location 37°16’55.2″N 115°47’58.6″W XP 2,720 Country
so after fiddling around, I found the solution where I simply install tinfoil driver and reg file from here:
I assume the windows update messes with the reg file and/or it somehow remove the libusbK driver.
hope this helps if anyone else is having this problem
case closed!
Can confirm this fixed my issue as well, since this was my first use of DBI, device manager shows it’s connected as DBI with a «!» mark saying drivers are not installed.
Long story short, been a SX OS user since day one, upgraded the FW that broke SX OS, I was kidding myself a new update will come out soon, so a few days ago, upgraded to Atmosphere, it was a painless and simple process. I was up and running in no time using my old emuNAND. Since I got the process of booting into Atmosphere worked out using the SX OS dongle, I started fresh, wiped my sd card and created a new emuNAND, needed to find a new nsp/xci installer, I came across DBI, great software.
ADDED NOTES:
Just wanted to add that in MTP mode, prior to the driver install, works fine. The ability to drag and drop the files to install is a great feature without the need for the backend app that is required on the PC side for install title on usb option connected to the PC.
So if your using thr MTP option to install, then you dont need to worry about the driver install since that is only related to the install title on usb option.