Hacking SWITCH NOOB PARADISE - Ask questions here

[HE1NZ]

It can get complicated, indeed. As for DBI, installing LIBUSBK driver for DBI can be really finicky at times and I know I had some trouble with it as well, but if I remember correctly, you need to:

1. Connect the Switch to the PC.
2. Run dbibackend.exe, select one of your games/updates/DLC files (just to test the connection between Switch and PC) and start the server.
3. Run DBI on Switch and select "Install title from DBI backend". If it works, it works! But it probably won't, so proceed with the next step.
4. Run Zadig.
5. Hopefully, DBI will be listed in the dropdown menu (make sure that your start the server in dbibackend).
6. If it's there, click on the install driver button (LIBUSBK driver should be selected).
7. After that, you'll probably need to restart the server in dbibackend.exe and restart your DBI app on Switch. Hopefully, it should work now.

If it doesn't work on first try, keep trying. I might have missed a step or two, but that should be it.

Thanks, but downloading games onto SD card and installing and deleting it there, like a CIA file on 3DS, works great for me. I won't bother with connecting to PC anymore.

 

[bupeapoop]

For most of the people it's whenever a game that you want to play requires higher firmware. If you've installed some games right now and you think they'll keep you busy, you can skip on updating your setup for as long as you're entertained.

So I'm guessing this will only occur whenever you're playing a newer titles? So for example I'm currently running hekate v6.1.1 and Atmosphère 1.7.0, Do these tend to release updates side by side? If one updates, can you expect the other to be updated at the same time?

Any games currently out at the moment should run on the current version of both hekate and Atmosphere? It's only newer games that are come out after the release of both Hekate v6.1.1 and Atmosphere 1.7.0 that I should expect to update both applications?

Will it throw up an error when playing the game? Will this usually be the time you know it's time to update without manually checking from time to time?

In theory, compared to the sigpatches, sys-patch needs to be updated only whenever something major breaks. I'd advise that you check in either sigpatches or sys-patch thread to see if something major broke with the latest firmware update.

Can you confirm an example of something major breaking? With it automtically running and updating in the background, how would I know something has majorly fucked up for it to worth investigating further to ensure the issue can be resolved?

Most of the time, nothing will happen. Games will continue to work as usual, they won't magically stop working after a while.
The only issue might be if developers of Hekate and Atmosphere have found some major bug in their older releases (that you also have on your system) and they've released a fix for that. Still, I believe that most of the major issues were ironed out by now and both of them are pretty stable, so there shouldn't be any concern for the end users like us.

Thank you for clarifying. This is good to know going forward.

Post automatically merged: Apr 19, 2024

Also a question relating to DBI, I'm not sure whether I've made life more difficult for myself, but with all my backup games, I've created two folders, sometimes three folders. These are Base Game, Update, and occasionally DLCs from time to time.

When installing using DBI, do I need to remove each of the files from these folders and place them in a main folder in order for DBI To install all 3 files? Or can DBI install the files held within each folder?

Lastly, I doubt DBI does not know which file to install first. The first being the Base Game, followed by the Update and then the DLCs. Do I need to manually enter the following to each file name so it knows each file to install first. Here's an example:

• 1 - Base Game
• 2 - Update
• 3 - DLC 1
• 4 - DLC 2

Then for the next Game, can I then go as follows:

• 5 - Base Game
• 6- Update
• 7 - DLC 1
• 8 - DLC 2

This is under the assumption that I'm getting DPI to install the games automatically in sequence. If I have to install each file manually and simply wait until the file has installed before proceeding to the next file then I'd imagine labelling each game with a number makes zero odds.

The only thing that really is important I'm assuming is removing all the files from each of the folders into one folder such as 'Backup Game', where I then have the Base Game, Update and DLCs?

 

[Dust2dust]

Thanks, but downloading games onto SD card and installing and deleting it there, like a CIA file on 3DS, works great for me. I won't bother with connecting to PC anymore.

But how do you put your nsp/xci files on the SD card in the first place? If you eject your SD card and plug it in your PC to copy the files, and then you re-insert the SD card in your Switch, then you like living on the edge. The SD card slot on the Switch is known to be flaky, and might break if you keep removing and inserting the SD card too often. If you can transfer your files with Hekate (USB tools), that would be a safe alternative. Otherwise, I'd suggest to not give up and fix that issue you have with USB connection through DBI. Many people succeeded, why shouldn't you? I haven't removed my SD card from my Switch in years, and I don't intend to change that.

Post automatically merged: Apr 19, 2024

Also a question relating to DBI, I'm not sure whether I've made life more difficult for myself, but with all my backup games, I've created two folders, sometimes three folders. These are Base Game, Update, and occasionally DLCs from time to time.

When installing using DBI, do I need to remove each of the files from these folders and place them in a main folder in order for DBI To install all 3 files? Or can DBI install the files held within each folder?

Lastly, I doubt DBI does not know which file to install first. The first being the Base Game, followed by the Update and then the DLCs. Do I need to manually enter the following to each file name so it knows each file to install first. Here's an example:

• 1 - Base Game
• 2 - Update
• 3 - DLC 1
• 4 - DLC 2

Then for the next Game, can I then go as follows:

• 5 - Base Game
• 6- Update
• 7 - DLC 1
• 8 - DLC 2

This is under the assumption that I'm getting DPI to install the games automatically in sequence. If I have to install each file manually and simply wait until the file has installed before proceeding to the next file then I'd imagine labelling each game with a number makes zero odds.

The only thing that really is important I'm assuming is removing all the files from each of the folders into one folder such as 'Backup Game', where I then have the Base Game, Update and DLCs?

You're over thinking it. DBI will install whatever you tell it to install, the order doesn't matter at all. And if you install an update for a game already installed on your Switch that had an old update installed, it will gracefully overwrite the old update, no worry. I'm not sure what you mean by 2 or 3 folders? Folders on your PC? As I said DBI, will just install whatever you tell it to install, through MTP method or DBI backend. Everything (that you want to install) can be in one folder. Make your life easy.

 

[HE1NZ]

But how do you put your nsp/xci files on the SD card in the first place? If you eject your SD card and plug it in your PC to copy the files, and then you re-insert the SD card in your Switch, then you like living on the edge. The SD card slot on the Switch is known to be flaky, and might break if you keep removing and inserting the SD card too often. If you can transfer your files with Hekate (USB tools), that would be a safe alternative. Otherwise, I'd suggest to not give up and fix that issue you have with USB connection through DBI. Many people succeeded, why shouldn't you? I haven't removed my SD card from my Switch in years, and I don't intend to change that.

Never had any SD card slots die out. Just being careful I guess. Hard to imagine Switch having worse slots than DS flashcart SD slots and those never died on me.

I'd have to go through 3-4 apps to get USB connection to work. Wether it will work or not is completely random. DBI worked two years ago, it didn't when I tried yesterday.

 

[Dust2dust]

Never had any SD card slots die out. Just being careful I guess. Hard to imagine Switch having worse slots than DS flashcart SD slots and those never died on me.

I'd have to go through 3-4 apps to get USB connection to work. Wether it will work or not is completely random. DBI worked two years ago, it didn't when I tried yesterday.

Well, it's your hardware, you can do whatever you think is good for you. Your USB connections issues could also be related to the quality of your cable. Do you have some others you could try? I've been using the USB cable that came with my Switch Pro controller for years without a single issue.

 

[Blythe93]

Do these tend to release updates side by side? If one updates, can you expect the other to be updated at the same time?

Indeed. They both need to release a support for the firmware you're updating to. Hekate's usually the first, followed by Atmosphere.

Any games currently out at the moment should run on the current version of both hekate and Atmosphere? It's only newer games that are come out after the release of both Hekate v6.1.1 and Atmosphere 1.7.0 that I should expect to update both applications?

Indeed. New games sometimes do not require the newest firmware available as they were made on a lower firmware. An update may require you to update your firmware, though. I'm unaware of any game that requires firmware 18.0.0 at the moment, so most (if not all) of them should work on 17.0.1 for example.

As for updating Hekate and Atmosphere, I'd say that one should try to be on the latest version of Atmosphere in order to avoid possible bugs and issues. Of course, if there are sigpatches available for the latest version of Atmosphere and latest firmware. Hekate on the other hand, I don't think so? For example, prior to Hekate 6.1.1 and Atmosphere 1.7.0, I was on Hekate 6.0.7 and Atmosphere 1.6.2, meaning that I skipped Hekate 6.1.0.

Depending on what sys-modules and homebrew apps you have, you might want to stay on lower firmware as well, as those tend to break from time to time whenever a new firmware and Atmosphere version drops. So, do your homework and check if it's safe to update to the version you're updating to.

Will it throw up an error when playing the game? Will this usually be the time you know it's time to update without manually checking from time to time?

If you want to play the latest games, most likely it'll be as good as time as any for you to update your setup. Just make sure that everything else you've installed works on the latest version.

Also a question relating to DBI, I'm not sure whether I've made life more difficult for myself, but with all my backup games, I've created two folders, sometimes three folders. These are Base Game, Update, and occasionally DLCs from time to time.

I keep everything that I'd usually install from that certain game in the same folder. Meaning, base game, latest update and DLC are all in the same folder. I do make an "Optional" folder for the stuff that I usually don't need on my Switch (multiplayer content, language packs, older updates etc.)

When installing using DBI, do I need to remove each of the files from these folders and place them in a main folder in order for DBI To install all 3 files? Or can DBI install the files held within each folder?

Well, if you're using dbibackend and you specify a game folder that you'd like to install, it won't get everything from subfolders as well. That's why I keep everything that I'd usually install in a main folder, and keep the optional stuff in a separate folder. Some games have too many DLC files so I might opt to put those inside a folder as well just to make things a bit more organized.

Lastly, I doubt DBI does not know which file to install first. The first being the Base Game, followed by the Update and then the DLCs. Do I need to manually enter the following to each file name so it knows each file to install first.

Nope. DBI does it job well.

 

[GhostTikTak]

I've realised I need a bigger SD card, so I'm following the rentry guide for migrating my emunand. My problem is I don't remember if I set it up as a file based or partition based emunand, and so I'm not sure which migration method to use.

How can I check which method I used to create my emunand?

 

[Draxzelex]

I've realised I need a bigger SD card, so I'm following the rentry guide for migrating my emunand. My problem is I don't remember if I set it up as a file based or partition based emunand, and so I'm not sure which migration method to use.

How can I check which method I used to create my emunand?

If there's a large roughly 30 GB file on your SD card that isn't your eMMC backup, then that's your file-based emuMMC taking up all that space. You can use a partition manager to check your SD card to see if it has been partitioned which is a sign of a partition-based emuMMC. Or you can use Hekate to check which type it is under Info & Selection.

 

[GhostTikTak]

If there's a large roughly 30 GB file on your SD card that isn't your eMMC backup, then that's your file-based emuMMC taking up all that space. You can use a partition manager to check your SD card to see if it has been partitioned which is a sign of a partition-based emuMMC. Or you can use Hekate to check which type it is under Info & Selection.

Cheers, thanks!

 

[enochlinux]

*Sigh.*

I rebuilt my switch from scratch. Fully formatted the stock firmware, reinstalled via the rentry guide.

I am running DBI normally, not in applet mode. I STILL CAN'T DOWNLOAD ANY NSPs EXCEPT METAL GEAR.

Should i try my games in NXI (? or is it NRO?) format? That is legitimately the only other thing I can think to do.

Post automatically merged: Apr 22, 2024

I should clarify:

The issue is still DBI's USB error.

 

[RedColoredStars]

Never had any SD card slots die out. Just being careful I guess. Hard to imagine Switch having worse slots than DS flashcart SD slots and those never died on me.

I'd have to go through 3-4 apps to get USB connection to work. Wether it will work or not is completely random. DBI worked two years ago, it didn't when I tried yesterday.

It's pretty well known that the sd card slot in the Switch is fragile and prone to breaking. It's up to you but as was stated, since you're already using the PC to copy the files to the sd card, why not just connect your Switch to the PC instead? I wouldn't recommend the dbi backend method at all though. MTI responder method requires only DBI. No other apps on your Switch or PC. Simply plug your Switch into your PC and it shows up as a drive. Then just drag and drop to install.

Post automatically merged: Apr 22, 2024

*Sigh.*

I rebuilt my switch from scratch. Fully formatted the stock firmware, reinstalled via the rentry guide.

I am running DBI normally, not in applet mode. I STILL CAN'T DOWNLOAD ANY NSPs EXCEPT METAL GEAR.

Should i try my games in NXI (? or is it NRO?) format? That is legitimately the only other thing I can think to do.

Post automatically merged: Apr 22, 2024

I should clarify:

The issue is still DBI's USB error.

Which DBI error? I went back 8 pages and didn't see anything about it. And what exactly do you mean you can't download any nsps? DBI does not download nsps.

 

[enochlinux]

Which DBI error? I went back 8 pages and didn't see anything about it. And what exactly do you mean you can't download any nsps? DBI does not download nsps.

Sorry. Meant install NSP off my PC.
And I mean 'USB connection failed'. I have tried every port and several USBC cables.

 

[RedColoredStars]

Sorry. Meant install NSP off my PC.
And I mean 'USB connection failed'. I have tried every port and several USBC cables.

Which DBI method? DBI Backend or MTP Responder? If you've used the backend, try uninstalling the driver from your pc, rebooting, and then trying MTP Responder without any additional driver installed.

 

[enochlinux]

Which DBI method? DBI Backend or MTP Responder? If you've used the backend, try uninstalling the driver from your pc, rebooting, and then trying MTP Responder without any additional driver installed.

Backend. Do you have a tutorial on how to set up MTP on linux?

 

[emuman100]

I have an Erista unpatched switch running 8.0.0 that was updated with ChoiDujourNX many times and uses ReiNX. I'd like to update it to 17.0.0 and use Atmosphere instead.

I read somewhere that if you used ChoiDujourNX to update, it would corrupt your BOOT0/1 and that either if you used Atmosphere or updated your firmware with Daybreak, it wouldn't boot. The solution would be to restore your backed up BOOT0/1. Is this true or has anyone had success just updating with Daybreak?

My plan is to:

1. Use Hekate to make a backup of the current BOOT0/1 and raw GPP and Lockpick RCM to backup keys again.
2. Install Atmosphere and sigpatches for 17.0.0 and make sure everything still works on 8.0.0.
3. Use Daybreak to update sysNAND firmware to 17.0.0.

This should be pretty safe?

The reason why I want to update to 17.0.0 is that I don't know if Super Mario Wonder can run on 16.0.0. I used to use NSCB and keys to patch games to remove the firmware requirement, but doesn't DBI do that automatically?

Lastly, I made my original backup on an exFAT SD card, so it's the full size. How can I split it for FAT32?

Thanks!

 

[Hayato213]

I have an Erista unpatched switch running 8.0.0 that was updated with ChoiDujourNX many times and uses ReiNX. I'd like to update it to 17.0.0 and use Atmosphere instead.

I read somewhere that if you used ChoiDujourNX to update, it would corrupt your BOOT0/1 and that either if you used Atmosphere or updated your firmware with Daybreak, it wouldn't boot. The solution would be to restore your backed up BOOT0/1. Is this true or has anyone had success just updating with Daybreak?

My plan is to:

1. Use Hekate to make a backup of the current BOOT0/1 and raw GPP and Lockpick RCM to backup keys again.
2. Install Atmosphere and sigpatches for 17.0.0 and make sure everything still works on 8.0.0.
3. Use Daybreak to update sysNAND firmware to 17.0.0.

This should be pretty safe?

The reason why I want to update to 17.0.0 is that I don't know if Super Mario Wonder can run on 16.0.0. I used to use NSCB and keys to patch games to remove the firmware requirement, but doesn't DBI do that automatically?

Lastly, I made my original backup on an exFAT SD card, so it's the full size. How can I split it for FAT32?

Thanks!

That is correct, you can make a backup of your 8.0.0 NAND with Hekate and switch over to Atmosphere and use daybreak to update to 17.0.1 if you want.

 

[emuman100]

That is correct, you can make a backup of your 8.0.0 NAND with Hekate and switch over to Atmosphere and use daybreak to update to 17.0.1 if you want.

Thanks! When I update with Daybreak, will I still stay in autorcm? I haven't used Daybreak on an Erista unpatched, so I don't know if it gives the option like ChoiDujourNX did. But, I suppose I keep that enabled in Hekate first?

 

[Hayato213]

Thanks! When I update with Daybreak, will I still stay in autorcm? I haven't used Daybreak on an Erista unpatched, so I don't know if it gives the option like ChoiDujourNX did. But, I suppose I keep that enabled in Hekate first?

It will stay in autorcm if autorcm is on.

 

[Dust2dust]

Backend. Do you have a tutorial on how to set up MTP on linux?

MTP should work out of the box on Linux. At least, it did for me. I'm using Ubuntu 22.04. And DBI backend also works flawlessly on my system. It does need python3, though. I usually just enter "sudo python3 dbibackend" to launch it, and it automatically waits for a USB connection to the Switch. I normally use the backend to transfer games, as I'm used to it. But I tried the MTP method too, and it works.

 

[RedColoredStars]

Backend. Do you have a tutorial on how to set up MTP on linux?

MTP should work out of the box on Linux. At least, it did for me.

Sorry, don't use Linux and never will. Dust2dust says it works out of box on Linux but if not, I then suggest a dual boot setup with Linux and Windows.