Hacking SWITCH NOOB PARADISE - Ask questions here

[shutupsitdown]

I just followed sdsetup guides.

Kosmos (v11.7/v8.2) minimum and I added sigs patches, briccmii and biskeydump. Then I added Lockpick.nro to \switch
Hekate 4.6

URL to pick these again:
/console?switch#atmosphere;atmos_musthave;atmos_bootlogo;atmos_fusee;atmos_sigpatch;hbmenu;tinfoil;fusee-primary;hekate;briccmii;biskeydump;

I've copied the SD files to the root of a 200GB SDXC exFAT. The switch is running 4.0.1. Dumps and backups went well. When launched the CFW, I got the Nintendo logo then a lot of black. After more than a minute, the Nintendo logo came back, and it make me set the switch up, time, date, user account, etc. I couldn't tell if I was running CFW or not. Then it wanted the SDXC update. Then I got to visit System to see it was just 4.0.1, with no AWS version so I assume it's original FW. Not sure what to do at this point. I'm guessing it's crashing but nothing prints on the screen. I had the RCM jig until set up wanted the red joycon to go in. So that might not be good thing. What should I try next? Should I reformat to FAT32?

 

[Adran_Marit]

I just followed sdsetup guides.

Kosmos (v11.7/v8.2) minimum and I added sigs patches, briccmii and biskeydump. Then I added Lockpick.nro to \switch
Hekate 4.6

URL to pick these again:
/console?switch#atmosphere;atmos_musthave;atmos_bootlogo;atmos_fusee;atmos_sigpatch;hbmenu;tinfoil;fusee-primary;hekate;briccmii;biskeydump;

I've copied the SD files to the root of a 200GB SDXC exFAT. The switch is running 4.0.1. Dumps and backups went well. When launched the CFW, I got the Nintendo logo then a lot of black. After more than a minute, the Nintendo logo came back, and it make me set the switch up, time, date, user account, etc. I couldn't tell if I was running CFW or not. Then it wanted the SDXC update. Then I got to visit System to see it was just 4.0.1, with no AWS version so I assume it's original FW. Not sure what to do at this point. I'm guessing it's crashing but nothing prints on the screen. I had the RCM jig until set up wanted the red joycon to go in. So that might not be good thing. What should I try next? Should I reformat to FAT32?

See if you can access the homebrew menu (launch album) if you can then you are in CFW. However to add the exfat support you need to update your system firmware. You can do this officially or using choidujourNX. Both are viable options and all cfw works on 6.2. I also recommend you follow the guide I linked above to make a backup if you haven't done so yet

 

[WRO]

What are these sigs patches, briccmii and biskeydump?

I do not recall doing this on my system. Is it necessary for unbricking?

 

[Adran_Marit]

What are these sigs patches, briccmii and biskeydump?

I do not recall doing this on my system. Is it necessary for unbricking?

sigpatches are used for atmosphere to play backups

briccmii is a variant autoRCM installer

Biskeydump is for dumping your nand unique keys, these are the keys used for unbricking/rebuilding your nand if you mess up and if you don't have them and you bork your system. you're in for a bad time

 

[WRO]

BÖRK Ha Ha Ha. I wonder if a Swede made that terminology popular. I only ever recall seeing brick.

Well, SigPatches I have, because games work fine.

Not interested in autoRCM.

You mean fuses.bin + tsec_keys.bin?

(edit)

Can I inject ReiNX payload by itself on my Switch without Hekate now that I made a backup of everything I needed?

How can I delete an update file on my Switch that was meant for the same game but different version. Have not
encountered this yet. But, it is certainly possible. And I do not want dead space on my SD card...

Also can I swap SD cards as long as I have a copy of the Nintendo folder in the other SD card?

 

[Adran_Marit]

BÖRK Ha Ha Ha. I wonder if a Swede made that terminology popular. I only ever recall seeing brick.

Well, SigPatches I have, because games work fine.

Not interested in autoRCM.

You mean fuses.bin + tsec_keys.bin?

(edit)

Can I inject ReiNX payload by itself on my Switch without Hekate now that I made a backup of everything I needed?

How can I delete an update file on my Switch that was meant for the same game but different version. Have not
encountered this yet. But, it is certainly possible. And I do not want dead space on my SD card...

Also can I swap SD cards as long as I have a copy of the Nintendo folder in the other SD card?

No idea XD

sigpatches are included in reinx, the ones he are talking about are for atmosphere

Biskeydump is separate yet again. Hekate can dump the fuses.bin and tsec. biskeydump are a series of keys you need if you ever need to restore/rebuild/access your nand with hacdiskmount. Again you can follow the guide linked above for how to dump them

You can inject reiNX by itself if you want

Delete data from system settings or devmenu

yea or you can let it create a new one

 

[WRO]

No idea XD

sigpatches are included in reinx, the ones he are talking about are for atmosphere

Biskeydump is separate yet again. Hekate can dump the fuses.bin and tsec. biskeydump are a series of keys you need if you ever need to restore/rebuild/access your nand with hacdiskmount. Again you can follow the guide linked above for how to dump them

You can inject reiNX by itself if you want

Delete data from system settings or devmenu

yea or you can let it create a new one

Interesting. Well I am running Atmosphere right now. I dislike ReiNX boot-up logo.
I thought ReiNX was easier to install, but I guess I had the sigpatches all along.

I guess I will read about Biskeydump again, might of glazed through it and devmenu.

Thank you.

 

[WRO]

When converting XCIs to NSPs with 4NXCI. Is it normal get warnings at first.

I got [WARN] Fail to match key etc...

But, the NSP created work fine on my Switch.

 

[Adran_Marit]

When converting XCIs to NSPs with 4NXCI. Is it normal get warnings at first.

I got [WARN] Fail to match key etc...

But, the NSP created work fine on my Switch.

warnings are fine

 

[Calzy_G]

Where to start?

Hi to anyone reading this. I have a couple of questions if someone can help me out. Currently running 4.1, never used homebrew or any kind of hacks. I have a 128GB micro SD but I don't have the exFAT update as the card is new. I have the new xkit RCM ONE loader on the way.

I know the first thing I should do is a NAND dump and get my personal keys. I think I read that this is possible using Hekate and exFAT, despit my system not having the exFAT driver installed, is this correct? Also, I have seen the dumping guide, is this still the one to follow?

After the NAND dump, my plan is to get an SXOS license and setup the hidden EmuNAND partition. From there I plan to keep Horizon on 4.1 and update EmuNAND to 6.2. Is this the right way to go without burning fuses? as I don't want to use auto RCM.

The end game is to have split .XCI files on a FAT32 card and that's it.

Thank you for any information.

 

[RomanC]

+Draxzelex

Thank you. Now I can play in de-DE. Ha ha ha.

Does 4NXCI also work with NS-Atmosphere or just ReiNX? Because XCI2NSP has a terrible GUI...

(update)

4NXCI does indeed work on NSA. If are on 6.2.0 extracted prod.keys from Lockpick becomes your
keys.txt + keys.dat + keys.ini (They are the same file, do not understand why. :|)

Can I inject ReiNX payload by itself on my Switch without Hekate now that I made a backup of everything I needed?
(Still need answering this one ^)

How can I delete an update file on my Switch that was meant for the same game but different version. Have not
encountered this yet. But, it is certainly possible. And I do not want dead space on my SD card...

--------------------- MERGED ---------------------------

+RomanC

Che Boludo. I think that is normal behaviour. You need to inject payload everytime you power-off or after battery discharges...

--------------------- MERGED ---------------------------

+RomanC

Nevermind. I just tried on my Switch. Games should appear but they cannot be played because it has no license.
Must inject payload to play your games every time.

Thank you for the help, and I loved the "boludo" there! Gracias amigo!

 

[Sparky076]

My second console is on 4.1. Is there any reason to keep it on 4.1, and not update it to 6.2? How can I update it to read Micro XCSD cards?

 

[JumpGamer09]

I'm on 6.2 running Atmosphere, having once updated my Switch from 5.0.2 using ChoiDujour. According to my fuse info in RCM mode, it appears that I have 8 burnt fuses.

I like to know what are causes of burnt fuses besides upgrading the filmware? Does turning off AutoRCM burn fuses? If so, I remember turning off AutoRCM a couple of times before which may explain the high burnt fuses count.

There are 32 fuses total correct? What are the cons of burning these fuses other than being unable to downgrade my Switch later?

 

[Hutch80]

Hello everyone. I am trying to dump keys on my Switch (tinfoil is asking for it) but kezplex and lockpick both fail at doing so. I am on the latest SX CFW. Any ideas? Thx!

 

[daijobu]

Hi guys. I've been using SX OS 2.0 for months with no issue. This morning I tried updating to beta 2.4. I put the boot.dat in the root of the SD card and booted up TegraRCMGUI.exe as usual and injected the payload. It said "payload injected" like normal but my Switch screen remained black (I have always kept my switch in autoRCM mode so I didn't manually go into it). But now the switch is completely unresponsive and doesn't turn on (probably due to having autoRCM). When I connect it to the PC again and open the TegraRCM exe, it doesn't detect the switch in RCM mode. I tried to manually put the switch in RCM mode several times but still no detection when I connect to the PC.
What's really weird too is that now connecting my switch to the PC through usb cable takes a while before the PC recognizes that a device is plugged in and makes that beeping sound.
Anyone knows what's going on? I've backed up my NAND before but hopefully I don't need to restore it already, but is this a soft brick, and if so why did it happen?

 

[Draxzelex]

Where to start?

Hi to anyone reading this. I have a couple of questions if someone can help me out. Currently running 4.1, never used homebrew or any kind of hacks. I have a 128GB micro SD but I don't have the exFAT update as the card is new. I have the new xkit RCM ONE loader on the way.

I know the first thing I should do is a NAND dump and get my personal keys. I think I read that this is possible using Hekate and exFAT, despit my system not having the exFAT driver installed, is this correct? Also, I have seen the dumping guide, is this still the one to follow?

After the NAND dump, my plan is to get an SXOS license and setup the hidden EmuNAND partition. From there I plan to keep Horizon on 4.1 and update EmuNAND to 6.2. Is this the right way to go without burning fuses? as I don't want to use auto RCM.

The end game is to have split .XCI files on a FAT32 card and that's it.

Thank you for any information.

Yes, it is possible to use exFAT with Hekate on a Switch that doesn't support exFAT because Hekate is loaded outside of Horizon.

Also EmuNAND won't risk burning fuses no matter how high its firmware is because you cannot boot into it with the normal bootloader which burns fuses. To boot into EmuNAND, you need to use SX Loader which disables the fuse check as of now so AutoRCM is not necessary if you never update SysNAND. And to update EmuNAND, you're going to have to use the homebrew application ChoiDujourNX as the purpose of EmuNAND is to keep it offline.

My second console is on 4.1. Is there any reason to keep it on 4.1, and not update it to 6.2? How can I update it to read Micro XCSD cards?

You can use the homebrew application ChoiDujourNX to patch a firmware to have exFAT support. However to do so, you have to format the SD card to FAT32 which you can just use instead of exFAT and FAT32 is objectively better than exFAT. Aside from not having to worry about adding exFAT support, FAT32 won't corrupt your SD card unlike exFAT. Plus there are numerous ways to bypass the 4 GB limit on FAT32 most notably with USB installation which is faster than regular installation.

I'm on 6.2 running Atmosphere, having once updated my Switch from 5.0.2 using ChoiDujour. According to my fuse info in RCM mode, it appears that I have 8 burnt fuses.

I like to know what are causes of burnt fuses besides upgrading the filmware? Does turning off AutoRCM burn fuses? If so, I remember turning off AutoRCM a couple of times before which may explain the high burnt fuses count.

There are 32 fuses total correct? What are the cons of burning these fuses other than being unable to downgrade my Switch later?

What burns fuses is when you use the normal bootloader while running a firmware higher than your fuse count. The bootloader sees this and burns fuses to compensate. This is why AutoRCM is enabled to prevent the user from turning the console on with the normal bootloader. Without AutoRCM, the next time you turn on your console with a firmware higher than the fuse count, your fuses will be burnt. The only purpose of fuses is to prevent downgrading so if there is an exploit released for lower firmwares, you won't be able to take advantage of them.

Hello everyone. I am trying to dump keys on my Switch (tinfoil is asking for it) but kezplex and lockpick both fail at doing so. I am on the latest SX CFW. Any ideas? Thx!

If you are using EmuNAND, neither kezplez nor lockpick will work. They have to be used with SysNAND.

Hi guys. I've been using SX OS 2.0 for months with no issue. This morning I tried updating to beta 2.4. I put the boot.dat in the root of the SD card and booted up TegraRCMGUI.exe as usual and injected the payload. It said "payload injected" like normal but my Switch screen remained black (I have always kept my switch in autoRCM mode so I didn't manually go into it). But now the switch is completely unresponsive and doesn't turn on (probably due to having autoRCM). When I connect it to the PC again and open the TegraRCM exe, it doesn't detect the switch in RCM mode. I tried to manually put the switch in RCM mode several times but still no detection.
Anyone knows what's going on? I've backed up my NAND before but hopefully I don't need to restore it already, but is this a soft brick, and if so why did it happen?

Even if you bricked the console, it would still go into RCM as RCM is part of the hardware of the console and its insanely hard to remove this feature aside from killing the battery. What may have happened is that your computer stopped detecting the console being in RCM which a simple restart can fix. I also recommend switching to TegraRCMSmash over TegraRCMGUI as the GUI has been known to have bugs exclusive to it but not found in the original program.

 

[CapCaveman]

Urgent question: my Switch is a launch unit (1.0.0), but I only have a 128GB microSDXC card.

OFW (Horizon) won’t even recognize that card. Will I still be able to use it to backup the sysNAND after booting into RCM and injecting CTCaer-Hekate?

Can I then load a CFW and use ChoiDuJourNX to update the emuNAND? Or do I need a smaller HC card for the entire process?

2/3 While ChoiDujour is theoretically less detectable, that doesn't mean its the preferred way to update; it just means its less detectable, that's it. Combine the facts that it doesn't support 6.2 and that it is a very long process to update without burning fuses using ChoiDujour and you will easily see that people will trade detectability for user-friendliness
4. AutoRCM is a brick but a fairly reversible one. What it does is corrupts boot0 of your console which is a part of the NAND. Since boot0 is corrutped, the only way to uncorrupt it would be with something that writes/repairs boot0 such as a system update. If AutoRCM was removed when the battery dies, people might have less reservations about it. That's because AutoRCM reduces the charge rate in RCM. Normally, one shouldn't charge the console in RCM but if the battery dies, it can only charge in RCM since it doesn't even have enough battery to accept a payload and boot CFW/OFW (Horizon).
5. CFW do not come an "ignore update" function. There is only one homebrew application with a feature close to the one you are describing which is Tinfoil. Not even SX OS has such a valuable feature. And this feature does not ignore all firmware requirements. But more importantly, Smash doesn't require 6.2 in the slightest. The base game requires 5.1. The updates may require 6.2 but 1.1, at least, has been patched to work on 5.1 and above.

2/3. Ah, I see. It’s just that you said using regular Choi was your personal recommendation, so I was willing to try that method. Since I have a bunch of jigs (SX Pro, R4S, RCMclip), I could probably use the official update method and then “brick” into RCM after it’s completed, but I’ll have to look up a video so I don’t end up messing up and burning fuses by accident.

4. So, just to make it clear: if AutoRCM is on, even if the battery dies/the Switch is turned off completely, AutoRCM still won’t be disabled? Only an official update in OFW/Horizon will do that?

5. I’ve read about the different firmware checks and learned that the “ignore” function of Tinfoil only works for the updates, not the native requirement of the games (which, in the case of Smash, is 5.1.0, as you mentioned). Is there really a point in not updating to the latest system version if I’m not burning fuses and have a clean sysNAND backup? It seems fairly safe to do so, right?

 

[JumpGamer09]

So is 7 the expected number of burnt fuses on system version 6.2.0? If I were to ever disable AutoRCM and turn on my Switch with the normal bootloader again, my Switch would burn another fuse?

 

[WiseFool]

Just read that Reinx has updated with warmboot support. What exactly is meant by warmboot?

Sent from my Nexus 6P using Tapatalk

 

[NFates]

Once I install one exFAT update, I don't need to keep choosing the exFAT version of every update on ChoiDujour, right?