You would need a clean eMMC backup made before hacking to clean your console. Without that, there is no way to keep it clean.Is it possible to return to stock while keeping hekate and "clean" it?
You would need a clean eMMC backup made before hacking to clean your console. Without that, there is no way to keep it clean.Is it possible to return to stock while keeping hekate and "clean" it?
I never made a backup of my saves before firmware update so I'm not sure if that's a necessary step, but if it puts your mind at ease, sure do.
Updating your sysNAND firmware and dumping it afterwards so that you can update your emuNAND is one way of doing the update, probably a preferred one if you want to play games you own online on stock firmware. You should know that you can get firmware files from a certain website that we aren't allowed to link here (quick Google search is all it takes) as well and just update your emuNAND firmware via Daybreak.
With that said, whenever you're updating your firmware, always make sure that you uninstall the custom theme (if you have one, update Hekate and Atmosphere after that. followed by updating emuNAND's firmware via Daybreak. I'd also suggest getting the latest sigpatches and/or sys-patch module (which requires Tesla + nx-ovlloader) as well, as you'll need those for game backups to work. To block Nintendo servers, set up DNS MITM.
In case you've cleared your prodinfo sometime in the past, you'll need to undo it. Otherwise, Atmosphere will crash as soon as you connect to the Internet.
I believe that, even if it's banned, your Switch can and will receive firmware updates so blocking Nintendo servers prevents your Switch from updating unintentionally as well.I already have Nintendo's servers blocked and my Switch is banned, so doesn't really matter either way.
If you've cleared your prodinfo sometime in the past, you'll need to undo it. Otherwise, Atmosphere will crash as soon as you connect to the Internet. Also, don't forget to update your fuse.bin payload. With that said, I believe that you're good to go. Here's a written guide if you need it (I recommend the PC method).1. Uninstall custom theme.
2. Update Hekate and Atmosphere.
3. Update emuNAND with Daybreak.
4. Update sigpatches.
Anything I'm missing?
Thanks for reply. Can I this same method to update Hekate too? Just I need to connect the device to the computer via hekate USB Tools and I replace files?You can, you can move file to the sd card using hekate mount feature and update firmware via daybreak.
Post automatically merged:
I believe that you can do that, just make sure to update the Hekate's payload as well afterwards.Thanks for reply. Can I this same method to update Hekate too? Just I need to connect the device to the computer via hekate USB Tools and I replace files?
YesThanks for reply. Can I this same method to update Hekate too? Just I need to connect the device to the computer via hekate USB Tools and I replace files?
You need to be on FW 17+.Tried to install Mario vs Donkey Kong with DBI and got this error: cannot parse meta data. old fimrware
Thanks, what's the best way to update emunand?You need to be on FW 17+.
Yesterday I updated everything via Hekate and DaybreakThanks, what's the best way to update emunand?
Follow this guide in order to update your CFW (I recommend using the PC method) and follow this guide in order to update your emuNAND's firmware.Thanks, what's the best way to update emunand?
Only issue I have with DBI on each and every first try is that it won't connect to the dbibackend.exe without installing the LIBUSBK driver with Zadig. I'm not sure if these are the correct steps, but give it a try:First, MTP responder did not read the cable everytime I plugged in (I tried so many times with different ports and cables). Sometime it works and sometimes not. I am using a laptop so I do not know if it affects the detection. FYI, MTP responder shows that I need to plug in the cable or press B to exit (and no “switch” drive on my laptop)
I believe that you need to enable USB 3.0 support in Atmosphere's system_settings.ini file. You can find the template in the atmosphere/config_templates folder and you can copy it over to atmosphere/config folder instead. Un-comment this line:Second, the transfer speed is so slow (on average 14mb/s). I am using usb 3.0 port and cable as well, but the MTP shows “actual speed: usb 2.0 high speed”. I changed ports and cables (I literally tried 5-6 cables lol) and it remains the same. FYI, I am using Sandisk ultra 512gb sd card
; usb30_force_enabled = u8!0x0
(remove the semicolon) and change u8!0x0
to u8!0x1
. If that doesn't work, try u8!0x0
instead as some people reported that it works the other way around for some reason.It should be decent, yes. Sadly, I have no experience with it so I can't really help you out with it as I've been using DBI since the moment I got into Switch hacking scene.In a case like this, does it make sense? And if i want a faster speed, is there any alternative except DBI? (I did some research and there is one called Awoo. Is it good and safe?)
Probably not if the source you've downloaded you NSP files can be trusted. The game works because there's probably nothing wrong with it. Those errors say that the file you've installed was tempered with, which is the usual thing when you do an XCI to NSP conversion, I guess. They can't pass the NCA verification. The other files you've installed passed the verification and should be as safe as they can be to be installed.Last question (which I think should be the most important). After I installed the game, I can see some status on MTP responder, some games would be like “[Transfer ok] [Signature: ok]” which I believe it is a good sign!
HOWEVER, some status indicate
[Transfer ok] [Signature: Invalid] or
[Transfer ok] [Signature: XCI -> NSP],
When I check the game version, it is updated and I can successfully open the game and play (no error or crash, at least for now). So I am wondering if these types of signature would harm/destroy the game? Is that something I should worry about?
Thanks you so much for the response!Follow this guide in order to update your CFW (I recommend using the PC method) and follow this guide in order to update your emuNAND's firmware.
Few other things to keep in mind:
- If you're using a custom theme, uninstall it before updating firmware. You can redownload it and reapply it once you're done.
- If you've blanked your prodinfo in the past (i.e. used Incognito or similar), you'll need to restore it as the Atmosphere will crash on firmware 17.0.0+. Use DNS MITM instead in order to block Nintendo servers.
- You don't need to dump firmware files from your sysNAND in order to update your emuNAND. Firmware files can be easily found on a certain site we aren't allowed to link to (a quick Google search is all it takes to find it) and, once you download and extract them, copy them over to the e.g. firmware folder on the root of the SD card (any name will do as long as you can easily find the files later on). Only after you update your CFW (i.e. Hekate and Atmosphere), proceed to update the emuNAND's firmware via Daybreak.
- After updating your Hekate and Atmosphere to the latest versions, don't forget to update your fuse.bin and hekate_ctcaer_x.x.x.bin payloads.
- Also, grab the latest sigpatches and/or sys-patch module (which requires Tesla + nx-ovlloader) because these are required for games to work.
Post automatically merged:
Only issue I have with DBI on each and every first try is that it won't connect to the dbibackend.exe without installing the LIBUSBK driver with Zadig. I'm not sure if these are the correct steps, but give it a try:
In case you can't make it work, I'll check once on PC and give you the correct steps. Good luck!
- Connect the Switch to the PC.
- Run dbibackend.exe, select one of your games/updates/DLC files (just to test the connection between Switch and PC) and start the server.
- Run DBI on Switch and select "Install title from DBI backend". If it works, it works! If it doesn't work, proceed with the next step.
- Run Zadig.
- Hopefully, DBI will be listed in the dropdown menu (make sure that your start the server in dbibackend).
- If it's there, click on the install driver button (LIBUSBK driver should be selected).
- After that, you'll probably need to restart the server in dbibackend.exe and restart your DBI app on Switch. Hopefully, it should work fine from now on.
I believe that you need to enable USB 3.0 support in Atmosphere's system_settings.ini file. You can find the template in the atmosphere/config_templates folder and you can copy it over to atmosphere/config folder instead. Un-comment this line:; usb30_force_enabled = u8!0x0
(remove the semicolon) and changeu8!0x0
tou8!0x1
. If that doesn't work, tryu8!0x0
instead as some people reported that it works the other way around for some reason.
It should be decent, yes. Sadly, I have no experience with it so I can't really help you out with it as I've been using DBI since the moment I got into Switch hacking scene.
Probably not if the source you've downloaded you NSP files can be trusted. The game works because there's probably nothing wrong with it. Those errors say that the file you've installed was tempered with, which is the usual thing when you do an XCI to NSP conversion, I guess. They can't pass the NCA verification. The other files you've installed passed the verification and should be as safe as they can be to be installed.
Nope, but sys-patch does. You can use either sigpatches or sys-patch module. Or both. The choice is yours.Sigpatches now require Tesla?
Followed your tutorial - Thanks much! Animal crossing is still not launching (same error code), but I did archive it off my console then unlink my nintendo account. I'm going to try reinstalling the NSP. If that does not work, then... I don't know.That error appears with some of the games that try to connect to the Nintendo servers and fail, probably due to them being blocked.
OK. Um.Followed your tutorial - Thanks much! Animal crossing is still not launching (same error code), but I did archive it off my console then unlink my nintendo account. I'm going to try reinstalling the NSP. If that does not work, then... I don't know.
I tried deleting the soft. It just keeps freezing!!!What do I do? Should I delete the original off the switch's "home screen" then reinstall? Should I be installing off my computer? That would be my guess...