Installing .NSP files that are on the SD card no longer work with Adubbz Tinfoil on firmwares 7.X. However USB, and presumably network install, still work.Does original Tinfoil not work on 7.0.1?
Goldleaf is so unstable and unpredictable for me, but Tinfoil always worked like a charm until I updated.
Installing .NSP files that are on the SD card no longer work with Adubbz Tinfoil on firmwares 7.X. However USB, and presumably network install, still work.
In case you were not aware, the developer behind Goldleaf isn't considered the best for the job of making a title manager. Its part of the reason why Blawar/vertigo (Discord handle) renamed his title installer DZ to Tinfoil. Anyways XorTroll has a habit of not updating projects as well as adding unnecessary functions to currently existing applications. Its what makes his tools sub-par when there are alternatives.Thanks!
What’s up with Goldleaf? It’s a mess! It crashes more often than it doesn’t installing on 7.0.1.
Yes I did. My guess is that the metadata that says which game is actually installed, is contained on the switch memory and not on the sdcard, which is why they’re not detected ?Did you transfer over the Emutendo folder from the 200 GB SD card to your 400 GB SD card?
Are you using FAT32 with a cluster/allocation size set to 32K or default?card.
I know its not hacking related, but why on earth wont my joycons charge when hooked up on the main device (but not plugged in the dock) ?
Did you install EmuNAND previously as a hidden partition? If that's the case, then you will need to copy and paste the image from your 200 GB SD card to the 400 GB SD card.Yes I did. My guess is that the metadata that says which game is actually installed, is contained on the switch memory and not on the sdcard, which is why they’re not detected ?
Maybe try SX OS V2.6 in case you haven't tried that yet.Default cluster, FAT32.
I managed to boot it with Atmos (Kosmos), via hekate_ctcaer_4.9.1.bin, only it says something about "the game card could not be read", so I can't play my games. (Don't know yet about NSPs or anything)
What am I missing to get Atmos working properly if it says that?
I used: https://www.sdsetup.com/console?switch with Kosmos Defaults.
Also I updated to 7.0.1, I choose exFAT for exFAT support, and that seems to work great.
The SX OS payload.bin shows the splash screen and then goes black, seemingly turning off the console, if I have to guess.
2.6.1 Beta should be able to handle 6.2 and 7.0.1 as a (choi) updated FW, so I don't get it...?
I didn't brick the system, it just doesn't boot with SX OS, I should've tried Atmos earlier to confirm this...
How can I get to boot SX OS with 7.0.1?
I'm not using EmuNAND fwiw. (I use two seperate eMMC boards to simulate that)
Not enough digits to determine if it is truly hackable or not. Check the full serial number yourself against this thread. If its not patched, try formatting your SD card to FAT32. If its patched, you're SOL.I'm trying to hack my switch, and supposedly is hackable by serial number starting at XAW100...
I do have 7.0.1 firmware version.
I tried with SX Pro but I continuosly get stuck at the selection screen, where my screen becomes unresponsive.
Then I tried the fuse-gelee with android phone and OTC USB cable, the phone logs the payload has been sent, but I don't see any changes on the switch menu. I got so far as making a nand backup yestarday.
Team xecuter web page has been down all week and I haven't been able to contact them for support, I also tried the SXLoader to inject the payload with my phone in case of the fat chance I got a damaged dongle (it's not damaged).
On the other hand, if I pursue the fuse-gelee method, I've been following the hombrew sdsetup instructions, where you acgually autoban yourself, but wonder if I do the hack in a separate sd card and keep the hacked games and files in a separate card, what are the chances of banning if I play offline with the hack sd, and change sd card before going online?
Wouldn't the hack evidence be on the sd card, along with games and save states?
Blue screens are usually due to a mismatch between boot0/boot1 and the firmware. Line them up again with ChoiDujour.I'm trying to recover a Switch. It goes to BSOD when trying to power on. I can run biskeydump successfully via RCM, but Hekate just stays at a black screen. It was already BSOD when I got it, so I'm not sure what caused it. I also don't have any backups since it was already dead.
First off all, there are two different applications with that name, ChoiDujour and ChoiDujourNX. ChoiDujour is a Windows program while ChoiDujourNX is a homebrew application for the Switch. Please learn the difference to avoid confusing people as there are differences between the two such as ChoiDujour only supporting up to firmware 6.1 while ChoiDujourNX works on all firmwares.There's a ton of games I can't play because I'm still on OFW 4.1.0
Do I understand this correctly?
If I upgrade to 6 or 7 via ChoiDuJour or whatever it's called, I can never turn my Switch off, or run out of battery, because when it restarts my fuses will burn?
Maybe try SX OS V2.6 in case you haven't tried that yet.
If you're not using MacOS or certain builds of Windows 10, its as easy as copying and pasting the entire contents of your SD card.To preface, I'm in the midst of converting my console over from exFAT to FAT32 and am currently running SXOS 2.6.1.
I wanted to run RetroArch at it's most optimal performance and saw that it required certain patches that now exist in SXOS 2.6.1, what should I do if I want to keep using the same jig setup I've been using to boot the Switch but also want to try using Atmosphere/ReiNX in conjunction with the ability to use SXOS when I want to?
I am using MacOS, but I'm also running a Virtual Machine (Parallels) for Windows 10, so I figure that there probably won't be any issues. I'm currently in the middle of the long transfer (5ish hours left, since I have about 180GB of content to copy over).If you're not using MacOS or certain builds of Windows 10, its as easy as copying and pasting the entire contents of your SD card.
Well there is a bit of an issue with having both Atmosphere and ReiNX on one SD card if your firmware is 7.X. Since both use the new sept payload to launch, you can only boot one of them at a time on that firmware. You can use SX OS in conjunction with either one since SX OS does not use sept to launch on firmwares 7.X but for dual-booting Atmosphere and ReiNX, you're gonna have a bad time.I am using MacOS, but I'm also running a Virtual Machine (Parallels) for Windows 10, so I figure that there probably won't be any issues. I'm currently in the middle of the long transfer (5ish hours left, since I have about 180GB of content to copy over).
Sorry if I wasn't clear on the details, but how can I run Atmosphere/ReiNX/SXOS with the choice to switch between them from the setup that I have now? I heard that there were some options to do this, but I'm not sure where to go to get all the latest updates on the software I need to download to accomplish this.
hello im new to this hope someone can help me out.
I have a switch with FW 1.0.0 downloaded the new Kosmo from SDSetup(FW1.0.0 support right?). Put it on the SD use hekate payload. It boots with splashscreen from Kosmo but its boot into 1.0.0 and nothing In my Album folder. Do I need update to 7.0.0 for this to work?