Homebrew Homebrew app Guide to Setting up DBI Installer over USB?

[linuxares]

Benchmarks <> real world. You also have to consider the overhead of the MTP protocol and HOS drivers.

and the need of enabling usb 3

 

[naddel81]

and the need of enabling usb 3

done.

 

[Maupiti]

iirc, last time I used DBI with MTP, that’s about what I got 30-40 Mb/s , (but noticed that can depend on the game, faster or slower), with my 400 Go Sandisk , I’m always stunned , with people complaining about speed, for “pirated content “,

 

[DARKFiB3R]

I'm having trouble getting my Switch connected to my PC with DBI

I've been talking with @impeeza via PM, and he has given me loads of help (Thank you ), but I'm still stuck.

It's difficult to condense our conversation and all the steps I have taken, but I will try to explain where I am at the moment.

Sorry for the long post...

---

This all started with my SD card becoming "corrupted" after transferring cheats via USB using haze (aka USB File Transfer).

I say "corrupted" because 4 out of the 5 games I had installed would no longer start, but everything else seemed fine.

There were a few error beeps from my PC while transferring the cheat files, but no error messages on screen.

I tried transferring the files again manually by putting the SD card in my PC.

It seems lots of files had not transferred via haze USB File Transfer, but copied over fine manually.

Previously installed games were still corrupted.

I tried uninstalling the games via the Switch, and reinstalling them via DBI. Games still corrupted.

I manually removed all the cheat files I had transferred.
I uninstalled and reinstalled the games again.
I tried installing a different game.
All with no joy.

So...

I backed up my saves using JKSV
I partitioned/formatted my SD card using Hekate (it would not auto backup the SD card)
I still have my main backups from when I moved from SXOS to DeepSea, so fuck it, lets go...
I created a new emunand, and transferred the latest build of DeepSea to the SD card
I put DBI v527 on the SD card, but now that is not working!
I updated DBI and the backend to v598, but still no joy.

At that stage…..

---

If I connected the Switch to the PC via USB while in Recovery mode:
Device Manager: libusbK Usb Devices > Nintendo Switch APX Mode
Zadig: List All Devices > APX (it has the driver libusbK v3.0.7.0 installed, and says I can update to v3.1.0.0)
Windows explorer: Nothing

Via Hekate > USB Tools > SD Card:
Device Manager: Portable Devices > H:\
Device Manager: Portable Devices > SWITCH SD
Zadig: List All Devices > Nothing relating to the Switch
Windows explorer: I can see the SD card and transfer files.

Via the DeepSea home screen:
Device Manager: libusbK Usb Devices > Nintendo Switch
Zadig: List All Devices > Nintendo Switch (it has the driver libusbK v3.0.7.0 installed, and says I can update to v3.1.0.0)
Windows Explorer: Nothing

Via DBI > Install title from Backend:
I hear the USB disconnect sound
Device Manager: Nothing related to the Switch
Zadig: Nothing related to the Switch
Windows Explorer: Nothing

Via DBI > Run MTP responder:
I hear the USB disconnect sound
Device Manager: Nothing related to the Switch
Zadig: Nothing related to the Switch
Windows Explorer: Nothing

Via USB File Transfer (haze):
Device Manager: libusbK Usb Devices > Nintendo Switch
Zadig: List All Devices > Nintendo Switch (it has the driver libusbK v3.0.7.0 installed, and says I can update to v3.1.0.0)
Windows Explorer: Nothing

---

After talking with @impeeza, I checked my SD card using H2testw, which reported being fine.

I then removed the following drivers using Device Cleanup Tool…

Connected the Switch while on the SeepSea homescreen.

PC...
No prompt to install new drivers.
Device Cleanup tool: Click refresh > Does not show any of the drivers I just removed.
Device Manager: Shows libusbK Usb Devices > Nintendo Switch

On Switch...
DBI > Run MTP responder...

On PC...
I hear the Device Disconnected sound.
Device Manager: (Greyed out) libusbK Usb Devices > Nintendo Switch
Device Cleanup tool: Now shows libusbK Usb Devices > Nintendo Switch

---

I wonder if using device manager to remove AND delete the drivers would be better?

On PC...
Device Manager > Uninstall and Delete driver (libusbK Usb Devices > Nintendo Switch).
Reconnect Switch to PC.
No prompt for driver install?!
Device Manager: Nothing
Device Cleanup tool: Nothing
Zadig: Nintendo Switch (Driver HidUsb v10.blah.blah.blah)

On Switch...
DBI > Run MTP responder...

On PC...
I hear the Device Disconnected sound.
Device Manager: Nothing
Device Cleanup tool: USB Input Device
Zadig: Nothing

On Switch…
Run USB File Transfer (haze)
Device Manager: libusbK Usb Devices > Nintendo Switch
Uninstall and delete
Close haze
DBI Installer > MTP > Nothing

Run haze
Device Manager: libusbK Usb Devices > Nintendo Switch (homebrew mode) Did it say homebrew mode last time?
Uninstall and delete
Close haze
Run haze
Device manager > Portable Devices > Nintendo Switch
Zadig > Nintendo Switch > Driver WUDFWpdMtp v10.0.1041

Close haze
Device manager: Nothing
Zadig: Nintendo Switch > Driver WUDFWpdMtp v10.0.1041

Run MTP responder
Device manager: Nothing
Zadig: Nothing

---

I'm thinking I should remove the driver WUDFWpdMtp v10.0.1041

But I'm worried that it's maybe a driver also used for other things?

Or maybe I should use just Zadig to replace one or both of these drivers at this point?

USB File Transfer (haze)

Home Screen

---

I did not remove or replace those drivers.

Run haze again
Device manager: Portable Devices > Nintendo Switch
Uninstall device via Device Manager (no option to delete driver)
Zadig: Nothing (oh shit?)

Disconnect Switch > reconnect
haze still running
No prompt to install anything
Device manager: Portable Devices > Nintendo Switch
Zadig: Nintendo Switch > Driver WUDFWpdMtp v10.0.1041

Zadig: Replace driver with libusbK (v3.1.0.0)
PC freeze > heart attack > driver installed successfully

Device manager: Portable Devices > Nintendo Switch
Zadig: Nintendo Switch > libusbK (v3.1.0.0)

Run MTP Responder.
Device manager: Nothing
Zadig: Nothing

Run DBI installer.
Device manager: Nothing
Zadig: Nothing

Back to Home Screen.
Device manager: Nothing
Zadig: Nintendo Switch > HidUsb (v10.0.19041.3031).
Zadig warns about replacing HidUsb driver

---

I did not replace the HidUsb driver yet.

Restart PC > No change

Hekate > USB Mass Storage.
Device Manager: Disk Drives > hekate SSD RAW USB Device
Device Manager: Portable Devices > H:\
Device Manager: Portable Devices > SWITCH SD
Zadig.
UMS > Driver = USBSTOR

---

Ok, so I haven't really managed to condense that much at all lol, apart from removing Impeeza's comments.

Again, sorry for the long-arse post, but I really hope someone can help, because my head is spinning at this point, and I'm not sure what to try next.

 

[DARKFiB3R]

Anyone? Please?

 

[Hayato213]

Anyone? Please?

Libuskb is the correct one.

 

[BaamAlex]

Correct me if i'm wrong. But why do you need drivers for dbi? Just connect your console with your pc, open dbi and press x. Don't go into any of the options. Just x.

 

[impeeza]

Correct me if i'm wrong. But why do you need drivers for dbi? Just connect your console with your pc, open dbi and press x. Don't go into any of the options. Just x.

That's correct, but sometimes the MTP Devices drivers can get messed UP, you need to recreate them.

DBI uses or MTP or Homebrew mode this last also need drivers.

 

[DARKFiB3R]

Correct me if i'm wrong. But why do you need drivers for dbi? Just connect your console with your pc, open dbi and press x. Don't go into any of the options. Just x.

Pressing X launches MTP Responder.

I hear the USB disconnect sound from my PC

Device manager > View > Devices by connection
Device manager > View > Show hidden devices

Post automatically merged: Jul 28, 2023

Is this a clue to my problem?

Post automatically merged: Jul 28, 2023

On Deepsea Home Screen:
Zadig > Nintendo Switch > Driver: libsubK 3.1
Extract driver files via Zadig

Device manager:
Unknown USB Device > Update Driver > point to extracted files (include sub folders)
"The best drivers are already installed"
FUUUUUUUUUUUUU

Post automatically merged: Jul 28, 2023

Forgot to mention a previous step I had taken (I think)....

Run haze
Zadig > Nintendo Switch > Driver: WUDFWpdMtp v10.0.1041
Replaced WUDFWpdMtp v10.0.1041 with libsubK 3.1

No change

 

[DARKFiB3R]

I FIXED IT

My fucking OFW was on 4.1.0!!!!

I have no idea how this could have happened. Did I manage to downgrade it at some point?

Everything was working fine before using Haze to transfer cheat files.

Before I realised my OFW was (only now?) on 4.1.0, I had decided to wipe the SD card

(Deleted all partitions on the SD card using Windows Disk Manager > Formatted and overwrote using SD Card Formatter)

Partitioned with Hekate > Created emuMMC > Installed DeepSea

Still no joy

Noticed other issues: Tesla Overlay would not stay enabled, DBI couldn't see USB keys etc.

Tried to install an .nsp from the SD card using DBI and got the error "Cannot parse nca. Old firmware"

Added SigPatches > edited hekate_ipl.ini (kip1patch=nosigchk)

Still nothing

Then I noticed it said FW 4.1.0 at the top of the DBI screen. WHAT?

Updated OFW with Daybreak and everything works again


Thanks to everyone who tried to help

 

[impeeza]

I FIXED IT

My fucking OFW was on 4.1.0!!!!

I have no idea how this could have happened. Did I manage to downgrade it at some point?

Everything was working fine before using Haze to transfer cheat files.

Before I realised my OFW was (only now?) on 4.1.0, I had decided to wipe the SD card

(Deleted all partitions on the SD card using Windows Disk Manager > Formatted and overwrote using SD Card Formatter)

Partitioned with Hekate > Created emuMMC > Installed DeepSea

Still no joy

Noticed other issues: Tesla Overlay would not stay enabled, DBI couldn't see USB keys etc.

Tried to install an .nsp from the SD card using DBI and got the error "Cannot parse nca. Old firmware"

Added SigPatches > edited hekate_ipl.ini (kip1patch=nosigchk)

Still nothing

Then I noticed it said FW 4.1.0 at the top of the DBI screen. WHAT?

Updated OFW with Daybreak and everything works again


Thanks to everyone who tried to help

By the way may be you was on a status like my main console.

When I buy it, the very first thing I did was: run hekate, backup the sysnad, created a (then) EmuNAND partition, and NEVER again touched the SysNAND, with the time I even converted the EmuNAND partition to File Based EmuNAND and still use it.

If for any reason I boot on SysNAND the initialization wizard will show.

Maybe you rely on EmuNANDs for long time and forgot your SysNAND.

 

[DARKFiB3R]

So if you boot into the sysNAND, then that old FW version now affects the updated emuNAND/MMC, CFW?

But if you don't, then it's fine?

Still, I'm pretty sure I have updated the OFW many times over the years.

Very confused.

I should probably stop messing with shit when I'm drunk

 

[Ryab]

For me, tinfoil is ugly one as hell and so clumsy, but DBI is a truly *nix way masterpiece with it's clean, lightweight and very useful text GUI, just like an old Adubbz installer was long time ago, in a far galaxy.

DBI just works. I've tried other title installers and they have all given me issues. DBI has always worked and has all the features I need + more.

 

[impeeza]

So if you boot into the sysNAND, then that old FW version now affects the updated emuNAND/MMC, CFW?

But if you don't, then it's fine?

Still, I'm pretty sure I have updated the OFW many times over the years.

Very confused.

I should probably stop messing with shit when I'm drunk

Don't Worry, that are some basic concepts:

Your console have a EMMC Chip inside that chip your have the NAND (storage) and a filesystem (encrypted) which is the one holding all partitions and files of the console bootloader and Operative System (HOS) all the partitions and files are so called SysNAND.

When you create a copy of that SysNAND and using Atmosphère you emulate the physical one from files (or partition) on your SD Card that is called EmuNAND.

Using a config file you can instruct to Atmosphère if load the HOS from your EMMC chip or your emulated one.

When you load Atmosphère on a console you are running CFW (Custom FirmWare) instead of let the console boot normally which is called OFW (Official FirmWare)

You can load CFW from your Emulated NAND (EmuNAND) and that run completely independent of the files on your EMMC chip, so any change on your EmuNAND doesn't affect your EMMC Chip.

The confusion can be raised when you load CFW on your SysNAND after you have your SD card setup to run CFW on a EmuNAND because all the Atmosphère's files, config, sysmodules and homebrew is the same! and if your SysNAND as in your case is too old then some homebrew or Sysmodules could not be compatible with old Firmware.

Another problem can arise with the Cartdrige reader but is issue for other day

 

[M7L7NK7]

After updating I now get

Write: USB connection failed

 

[Dust2dust]

After updating I now get

Write: USB connection failed

With the new v616? I just installed a couple games with it, and didn't have any problems. I used the backend, though. Maybe the MTP responder would be a different story?

 

[M7L7NK7]

Yeah with backend. Even trying an older version has the same result now, no idea

 

[Dust2dust]

Yeah with backend. Even trying an older version has the same result now, no idea

Are you on the new firmware 16.1.0? I'm still on 16.0.3 here. Maybe some incompatibility with the latest firmware. In the meantime, you can still try other installers.

 

[impeeza]

Are you on the new firmware 16.1.0? I'm still on 16.0.3 here. Maybe some incompatibility with the latest firmware. In the meantime, you can still try other installers.

Or try the MTP mode is neat and needs no other application on PC

 

[M7L7NK7]

How does it work, so it mounts the sd and you drag the file to it and it automatically installs to it?