Boot0/boot1 is also necessary on top of rawnand.Is a backup of your rawnand enough in case of a brick?
Boot0/boot1 is also necessary on top of rawnand.Is a backup of your rawnand enough in case of a brick?
Right, I'll back up those too after I disable autorcmBoot0/boot1 is also necessary on top of rawnand.
Okay so maybe I declared success a little too quickly.lol
1. I have a backup ncp file and put it in the tinfoil/nsp folder and when I try to install it (Title Managment \ Install NSP) I get the following error.
“An error occurred: OpenDirectory:135: Failed to open directory /tinfoil/nsp/. Error code 0x00000202
Press and button to exit”
SD card is a 128GB brand name, not a fake and is formatted as exfat, could that be the problem?
I also can't see any content in the tinfoil/nsp folder browsing through NX Shell on the Switch itself. It says 0 bytes. When I look at the SD card in Windows though, the file is there. Weird.
2. I decided to give AutoRCM a try. I turned it on in Reinx. I then tested it by powering off my console. I used the power button on the console itself from the home screen. When I tried to turn it back on nothing happened. Black screen. I panicked for a bit. So I decided to use my payload injector and jig again. And doing that got the console to boot. So I went back into Reinx settings and turned AutoRCM back off.
3. I also tried out 90DNS to block Nintendo servers, I thought it would be handy to use FTP and home brew shop. However. A couple games started trying to update, Fortnite and Minecradt. They had a “x” on stage bottom of the Download bar on the bottom of the icon on the home screen. When I saw that I clicked on them and got and error (sorry I didn’t write it down) so I cancelled the download. If 90DNS was working that shouldn’t have happened right? So I’m back in airplane mode.
1. I tested it a year and a half ago when I first got my switch. I don’t recall which tool I used but if you know of one I can test again. I got it from Best Buy and paid quite a bit at the time, but I know that doesn’t guarantee anything. I’m assuming I should backup all the content before testing it again.
- How did you test if it was fake? If its displayed as 0 KB in NX-Shell, that sounds like a very tell-tale sign of a fake SD card.
- That's how AutoRCM works. It 'bricks' the console so it boots into RCM AUTOmatically. Otherwise, you will have to use a jig or otherwise to boot into RCM
- .NSP files contain data that tells the Switch updates are ready to be downloaded. If you ever successfully installed one of these, especially one that needs a higher firmware, it likely told the console there was an update available to download. Of course, the update failed because you had 90DNS. Also, Airplane Mode is not sufficient as it can get disabled if you enter sleep or switch between docked and handheld modes. The only way to prevent accidental connections to Nintendo are by deleting the WiFi settings and enabling Airplane Mode.
1. I tested it a year and a half ago when I first got my switch. I don’t recall which tool I used but if you know of one I can test again. I got it from Best Buy and paid quite a bit at the time, but I know that doesn’t guarantee anything. I’m assuming I should backup all the content before testing it again.
Also it’s only the nsp folder in NX shell that shows zero bytes. The rest of the nro files and everything else are all showing up. It’s just the nsp file I can’t see. I’ve only tried one. Maybe I should try another backup?
I also didn’t do whatever these steps are (from the tinfoil github page). Am I missing an install step? Tinfoil was park of the original zip file I put on my SD card from the NS Atmosphe website. It also had a few other things like NX Shell, the retro arch emulator etc.
“
2. Okay. Not sure I get it then but I’ll just leave it off for now. I have a portable injector and the jig seems really well made so not too concerned on the rails. I thought AutoRCM would mean I no longer needed to use the injector or jig every time I power off and on but I’m probably missing something.
- Install FS sig patches, there are two ways of doing this:
3. These were games I already had on my Switch before trying out the Reinx mod. I bought minecradt a long time ago through the eshop and fortnight was through eshop too. Most of my other games are physical game carts.
Okay so it’s recommended to stay totally offline and essentially not use FTP, network install or home brew store? If I get banned I’m not that concerned. It would be nice not to be banned of course but I don’t really ever play online anyway. I’m more worried about constantly taking the SD card in an out that damaging the rails. It would suck to get a corrupt card. That is why I prefer network transfer. I’m assuming there is not USB C to regular USB (computer) way if transferring?
Yes, that is how we are able to update without burning fuses after all. The same works for booting lower firmwares than the fuse count meaning we can downgrade to any firmware we want. In most scenarios, downgrading is useless if your bypassing the fuse count since you have to use the RCM exploit in order to do so. However, it is useful for loading firmwares that are better supported with CFW. For example, someone struggling loading CFW on firmware 6.0 should just downgrade to a lower firmware such as 5.1 which has better compatibility until 6.0 receives better support.
Why not, Switches don't transfer hacked data to each other.
1. Got it. I’ll try a different nsp and see what happens. So I don’t need any title id’s or anything? I.e. “Install FS sig patches”? All I need is tinfoil itself and the nsp in the right folder? No other missing steps right?
- Is the name of the .NSP under 64 characters and using alphanumeric code only? That may be another issue. The last thing you can try is using another source for the .NSP file
- AutoRCM removes the need for a jig, not the injector.
- https://gbatemp.net/threads/how-to-...icrosd-card-as-an-usb-disk-on-your-pc.503701/
I think I confused you more. Substitute bootloaders such as Hekate and ReiNX bypass the fuse count as well as prevent fuses from being burnt. So if you enter RCM (which you can do automatically with AutoRCM) and load one of these, you can run any firmware you want. When running a higher firmware than the fuse count, the Switch will instantaneously burn fuses on the next non-RCM boot. This is why AutoRCM is preferred if you're updating without burning fuses; so the console won't perform a non-RCM boot. When running a lower firmware than the fuse count, the console is bricked with or without AutoRCM so you don't have to worry about burning fuses. However if you can enter RCM and use one of those substitute bootloaders I mentioned, you will be able to load a lower firmware than your fuse count. So as you can see, these substitute bootloaders allow you to load any firmware you want so long as you enter RCM (which is what the exploit depends upon). Due to this, its riskier to run a higher firmware than your fuse count than a lower firmware than your fuse count.Sigh...Alright I get what you are saying, but that means I must have totally misunderstood the whole idea of preserving fuses through AutoRCM and Hekate. I thought the purpose of preserving fuses was so that, in my case for example, I would be able to downgrade to 4.1.0, because my fuses count is 5 (which should be the fuse count that matches that FW). If we can downgrade to any firmware regardless of fuses, then what even is the point of trying sooo hard not to burn them???
The only advantage I can make of this, is that if you downgrade to, for example 3.0, and your fuses matches that Firmware, you could boot into it using the Official Nintendo Bootloader and circumvent RCM mode. But what would you even accomplish with this? The entire purpose behind downgrading FW is so you can better hack your console but even with a 3.0 Switch, you'd still be limited in what you can do hacking-wise. Yes, you'd get access to the HomeBrew Launcher through the web exploit, but that's about it. No CFW, no Signature patches, no nothing. And in my case, with 4.1, I wouldn't even get access to the HomeBrew Launcher:/
You don't need FS_nosigchk (aka "sig patches") to install games. Those are only needed for homebrew/custom .NSP files because the signature patch is designed to bypass content not signed by Nintendo such as homebrew.1. Got it. I’ll try a different nsp and see what happens. So I don’t need any title id’s or anything? I.e. “Install FS sig patches”? All I need is tinfoil itself and the nsp in the right folder? No other missing steps right?
2. Got it. I’ll just leave AutoRCM off then in my use case. The jig is literally part of the injector I’m using so it’s easy. Thanks again.
3. Sweet, that’s what I’ll use then!
I'm gonna be completely honest with you; I have never seen nor heard of an issue like this. I have no idea how to proceed let alone troubleshoot such a dilemma. So I will list various generic fixes you can try.So I tried another NSP file and tinfoil gave the same error. I think there is something wrong with my install. In the tinfoil folder the "folders" look like files and I can't go into them to see the nsp files inside of them. All the other folders are working as expected. Weird.
![]()
![]()
Okay ya I just had a crap / old install of tinfoil. I tried the latest version, deleted my tinfoil folder. Installed the new version, launched tinfoil and the folders were created and all is working now.I'm gonna be completely honest with you; I have never seen nor heard of an issue like this. I have no idea how to proceed let alone troubleshoot such a dilemma. So I will list various generic fixes you can try.
- Try other builds of Tinfoil which you can find here: https://bsnx.lavatech.top/tinfoil/
- Use other SD cards if available and experiment with both FAT32 and exFAT if the size of the file doesn't exceed 4 GB
- Format the SD card with external formatting programs such as Rufus or SD Formatter
- Experiment with creating the folders yourself on multiple operating systems as well as deleting the folders and running Tinfoil once to generate the folders by itself
- Transfer the .NSP file using other means such as FTP or memloader
Yes, order doesn't matter however to ensure success, you can do it in the order of games -> updates -> DLC.Okay ya I just had a crap / old install of tinfoil. I tried the latest version, deleted my tinfoil folder. Installed the new version, launched tinfoil and the folders were created and all is working now.
For update files, I just install them the same way as the main games right? I'm assuming I should install the game first then the update or can I install both at the same time?
There is work being done to use the NES app without linking an account but there is no ETA on when that will be available. Until then, you will have to link an account to use it. Also I believe unlinking should still be possible if you call Nintendo and give them a satisfactory reason such as a losing the Switch, having it stolen, or selling it to a friend. You can also update to firmware 6.0 without burning a fuse if you use ChoiDujourNX.
Hekate V4.1 now automatically powers off the console if the Switch has AutoRCM installed and entered RCM from Horizon. It will send Hekate normally if it entered RCM from a fully powered down state.
The current exploit is based on the hardware of the console, not the software; that's why firmware is no longer irrelevant to hacking the console much like the 3DS. The way we determine hardware is by looking at the serial number. There is a pinned thread in this section that is full of patched and unpatched serial numbers. I would recommend you checking that thread out before you purchase a Switch if you plan to use CFW/homebrew.
If they have a 56K ohm resistor built it, they should be safe.
Not sure there was never any bricking risk from dongles/modchips before but yes, you should be fine loading SX OS. And the only advantage SX Pro has over modchips is the license that it comes preloaded with.
Its as simple as changing the files on the SD card since CFW cannot be installed but is temporary.
Why not just use something like memloader or FTP?
If you want to go online as safely as possible, I would recommend uninstalling it. Outside of that, the other con is that you cannot boot pure OFW without RCM if AutoRCM is installed; meaning you cannot use the console without sending a payload first. In exchange you don't need a jig or otherwise to boot into RCM which can be good for the pins of the Switch.
People are working on bypassing the linked account requirement on the NES so if you're willing to wait, you don't have to update to 6.0 since the app can be installed on firmware 5.1. Also if you update to 6.0 and burn a fuse, you will most likely be stuck with using Fusee Gelee for a very, very long time as there is no sign of any other exploits working on that firmware. Personally, I wouldn't update to 6.0 and link an account to use the NES app since RetroNX works...most of the time. But the choice at the end of the day is yours.Thx for the reply. I'm on 5.1.0 ofw now and not hacked yet. Linking an account means I have to update to 6.0. If I do it over Nintendo then I will burn the fuse. If I do it over ChoiDujourNX I save the fuse but means I need to go online using a hacked switch.
The question now whether I want to risk being banned or risk burning fuse.
Which one is recommend?
Also is it worth all this just to use the NES app or future games will also require a linked account?
Thanks.
Not surprised that creport doesn't work with SX OS. They're modules are not meant to be modified and only load their own proprietary components. This is just one of the many issues with closed-source projects. I'm honestly surprised they didn't just steal creport and implement it into their own CFW.just wondering something about creport
I'm on 4.1.0 with SX OS 1.9
just now I got few crashes while trying to run kezplez-nx and edizon (forgot to note the error number, but that's not the issue). and then I try to look at the error history in the settings and to my surprise I find nothing in there. is that normal? what kind of error that should be in there
and does that mean that now I have some errors waiting to be sent to nintendo server once I connect to the internet?
I did put the modified creport on sdcard:/sxos/titles/0100000000000036 a while back because why notbut since I couldn't find any logs in sdcard:/atmosphere/crash_reports then is it safe to assume the mod creport does not work?
Look up Checkpoint and EdiZon.After procrastinating since the launch, I finally set up my switch and installed SX OS.
I want a savegame backup homebrew and recommendation of emulators and homebrews please!
Pokemon is around the corner, so I deffo need a savegame backup manager so I can hack poke saves
IN SHORT: Need save game backup manager and homebrew recommendations please !
Download autoxbins which will connect automatically to xbins' FTP server and allow you to download the 5.1 system firmware files. You may also need to disable your antivirus since being an FTP client will flag it as malware. It is completely safe and I use it all the time.I want to update to 5.1.0 via choidujournx but I don't want to download and extract an update partition from a dodgy xci. Would anyone be kind enough to prviate messgae link or share with me a safe back up or just the correct and files I need so I don't screw this process up? thanks
All games installed into your console will be lost when you perform a factory reset. All games installed into your SD card will not be removed, however the real/fake tickets (aka "signature patches) used to launch them will be wiped from your console prompting them to be reinstalled.OK I also have a noob question. and could not find an answer in the search option.
I'm running a super banned switch with 5.1.0 firmware. Installed a bunch of NSP games. in europe we now also can finally "unlink" our account through the website. so I want to factory reset my switch.
the question: will I loose all my installed NSP games (installed on the SD card) after resetting my switch? or can I just take out the SD card, factory reset the switch. plug the SD back in and on we go?