Hacking SWITCH NOOB PARADISE - Ask questions here

[lexluth0r]

My switch froze while installing a game using tinfoil (had to hard reset) now it says sd card is corrupt and it will not install games properly. So my question is do I copy over the files on the sd card format and recopy over all the files or should I just start from new?

 

[Draxzelex]

My switch froze while installing a game using tinfoil (had to hard reset) now it says sd card is corrupt and it will not install games properly. So my question is do I copy over the files on the sd card format and recopy over all the files or should I just start from new?

How was your SD card formatted? Was it exFAT?

Hi all! My launch day Switch has been collecting dust for a long time now. I can't even remember what firmware it used to be on, but it was a firmware that was compatible with SX OS at the time, which is now dead if I'm reading correctly?

My friend updated my firmware the last time they borrowed it and I am now on 13.2.0.

1. Is this firmware hackable or which firmware should I upgrade to? I forget if downgrading is an option, but I remember it not being possible from what I recall.
2. What custom software are people using to play their backup games these days? Atmosphere or is there something better? Would love any and all links to step-by-step guides.
3. What is the preferred format for backup games? I was using .xci, but I recall .nsp and .nsz just hitting the scene. Not sure if there are more popular options these days.

Thanks in advance!

1. Consoles aren't determined hackable by the firmware; its determined by the hardware. Consoles manufactured before June 2018 are unpatched and therefore hackable via the present exploit which is Fusee Gelee
2. The only CFW being supported nowadays is Atmosphere
3. You can use both .XCI and .NSP files with Atmosphere but they have to be installed

 

[Shadow#1]

How can i install youtube on atmosphere?

Get the patched version via tinfoil

 

[raphzthename]

How was your SD card formatted? Was it exFAT?

1. Consoles aren't determined hackable by the firmware; its determined by the hardware. Consoles manufactured before June 2018 are unpatched and therefore hackable via the present exploit which is Fusee Gelee
2. The only CFW being supported nowadays is Atmosphere
3. You can use both .XCI and .NSP files with Atmosphere but they have to be installed

Thank you!

A couple follow-up questions:

1. Since the hackability is determined by hardware, is it safe to assume that I can update to the newest firmware? Just want to be sure that firmware upgrades won't break anything with Atmosphere.
2. What are the differences (pros and cons) of the two formats?

 

[Draxzelex]

Thank you!

A couple follow-up questions:

1. Since the hackability is determined by hardware, is it safe to assume that I can update to the newest firmware? Just want to be sure that firmware upgrades won't break anything with Atmosphere.
2. What are the differences (pros and cons) of the two formats?

1. The latest firmware was just released so not all tools have been updated to support it and thus is quite unstable. I wouldn't recommend updating to the latest firmware at this time
2. .NSP files are games from the eShop while .XCI files are dumps from cartridges. Normally, the difference is you would install .NSP files and mount .XCI files as a cartridge but since Atmosphere doesn't support mounting .XCI files, the differences between the two are negligible to the end-user. If you're a purist, then you would stick to using .NSP files assuming you only use Atmosphere but installing either an .NSP or .XCI file achieves the same result in the end.

 

[Shadow#1]

1. The latest firmware was just released so not all tools have been updated to support it and thus is quite unstable. I wouldn't recommend updating to the latest firmware at this time
2. .NSP files are games from the eShop while .XCI files are dumps from cartridges. Normally, the difference is you would install .NSP files and mount .XCI files as a cartridge but since Atmosphere doesn't support mounting .XCI files, the differences between the two are negligible to the end-user. If you're a purist, then you would stick to using .NSP files assuming you only use Atmosphere but installing either an .NSP or .XCI file achieves the same result in the end.

What tools r still broken?

 

[raphzthename]

When using Web Fusée Launcher to send the payload, I get the following errors on my Switch:

Missing LP0 (sleep) lib!
Missing Minerva lib!

Update bootloader folder!

Press any key...

Then on the Tools tab, the only option I see is AutoRCM. At the bottom of the screen, it also shows Nyx is missing!

How can I fix this so that I can backup my NAND?

 

[Shadow#1]

When using Web Fusée Launcher to send the payload, I get the following errors on my Switch:

Missing LP0 (sleep) lib!
Missing Minerva lib!

Update bootloader folder!

Press any key...

Then on the Tools tab, the only option I see is AutoRCM. At the bottom of the screen, it also shows Nyx is missing!

How can I fix this so that I can backup my NAND?

Update your atmosphere and hekate

 

[Hayato213]

When using Web Fusée Launcher to send the payload, I get the following errors on my Switch:

Missing LP0 (sleep) lib!
Missing Minerva lib!

Update bootloader folder!

Press any key...

Then on the Tools tab, the only option I see is AutoRCM. At the bottom of the screen, it also shows Nyx is missing!

How can I fix this so that I can backup my NAND?

You are missing hekate files on SD

https://github.com/CTCaer/hekate/releases/tag/v5.9.0

 

[raphzthename]

Thanks @Shadow#1, @Hayato213, and @Draxzelex for the quick help! I was able to successfully backup my NAND.

I'm now having trouble running the lockpick payload though. I downloaded the latest Lockpick_RCM.bin and placed it at the root of my sdcard:

Using the Lockpick RCM method in Web Fusée Launcher, the result shows:

Requesting access to device...
Preparing to launch Lockpick_RCM.bin...

It does not progress further than this and my Switch screen remains black. I selected the hekate payload just to check that my Switch is in RCM mode, and it was able to launch.

Is there anything else I need other than the Lockpick_RCM.bin? Should I place it somewhere other than the root of my sdcard?

 

[Shadow#1]

Thanks @Shadow#1, @Hayato213, and @Draxzelex for the quick help! I was able to successfully backup my NAND.

I'm now having trouble running the lockpick payload though. I downloaded the latest Lockpick_RCM.bin and placed it at the root of my sdcard:
View attachment 334776

Using the Lockpick RCM method in Web Fusée Launcher, the result shows:

Requesting access to device...
Preparing to launch Lockpick_RCM.bin...

It does not progress further than this and my Switch screen remains black. I selected the hekate payload just to check that my Switch is in RCM mode, and it was able to launch.

Is there anything else I need other than the Lockpick_RCM.bin? Should I place it somewhere other than the root of my sdcard?

U can boot payloads via hekate

 

[raphzthename]

U can boot payloads via hekate

Thanks for the tip!

When I click on Payloads through hekate, it doesn't seem to find the Lockpick_RCM.bin. Should it be somewhere other than the root of my sdcard?

 

[Shadow#1]

Bootloader/payloads

 

[binkinator]

@raphzthename

If you’re running FW 15.0.0 make sure you’re using this version of Lockpick_RCM in order to get the new 0E key.

https://github.com/dezem/Lockpick_RCM

 

[Dust2dust]

@raphzthename

If you’re running FW 15.0.0 make sure you’re using this version of Lockpick_RCM in order to get the new 0E key.

https://github.com/dezem/Lockpick_RCM

@linuxares also built a version from the latest source. I tested it today, and it worked fine. It can be found here.

 

[Shadow#1]

@linuxares also built a version from the latest source. I tested it today, and it worked fine. It can be found here.

Um

 

[binkinator]

Um

I just “liked” the linked post…

 

[Shadow#1]

I just “liked” the linked post…

View attachment 334791

Post the file here?

 

[raphzthename]

Bootloader/payloads

Thanks again! Saving Lockpick_RCM.bin to /bootloader/payloads did the trick.

Would like to understand a bit about what these keys are. After backing up the keys, I have these files in /switch:

dev.keys
prod.keys

I don't have any titles installed, so I'm guessing that's why I don't have title.keys?

 

[Shadow#1]

Thanks again! Saving Lockpick_RCM.bin to /bootloader/payloads did the trick.

Would like to understand a bit about what these keys are. After backing up the keys, I have these files in /switch:

dev.keys
prod.keys

I don't have any titles installed, so I'm guessing that's why I don't have title.keys?

Uea go to sysnand and install a title let's say an easy one youtube