Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,120,091
  • Replies Replies 47,966
  • Likes Likes 66
Hello.

I am pretty new to CFW on the switch.
I just installed hekate (clicking launch -> CFW (SYSNAND) ) to my 6.2.0 switch and I tried installing some NSP files through goldleaf.
However, I get an error from goldleaf, static:
  • "Metadata could not be located in the NCA (3)" , and then crashes with an error 2168-0002 (0x4a8)
 
Hello.

I am pretty new to CFW on the switch.
I just installed hekate (clicking launch -> CFW (SYSNAND) ) to my 6.2.0 switch and I tried installing some NSP files through goldleaf.
However, I get an error from goldleaf, static:
  • "Metadata could not be located in the NCA (3)" , and then crashes with an error 2168-0002 (0x4a8)
Technically you did not install Hekate but that's not what's important here. I recommend giving ReiNX a shot and using Tinfoil to install your .NSP files
 
Thanks for the quick reply.
Will I have to update my switch 6.2.0 to a newer version to run the most current NSP files?

Also, can I remove somehow hekate and use reinix 2.1.1?

I used the method from the YouTube user Bones Jones
 
Thanks for the quick reply.
Will I have to update my switch 6.2.0 to a newer version to run the most current NSP files?

Also, can I remove somehow hekate and use reinix 2.1.1?

I used the method from the YouTube user Bones Jones
Newer games will require you to update your firmware however everything is playable on firmware 8.1 for the time being. Like I said, you never "installed" Hekate so there is nothing really to remove unless you are referring to the Hekate files on your SD card which you can remove as ReiNX has its own set of files that are completely different. And as a word of advice, never follow YouTube videos. They are outdated and thus full of misinformation.
 
  • Like
Reactions: Gamese
Im running an unpatched Switch with 4.1.0. When i update my EmuMMC to 8 or 9 can i use stock firmware 4.1.0 without burning fuses?
For all intents and purposes, assume emuMMC cannot burn fuses so to answer your question, yes it is possible however I do not recommend updating to firmware 9.0 right now as it is a bit unstable.
 
For all intents and purposes, assume emuMMC cannot burn fuses so to answer your question, yes it is possible however I do not recommend updating to firmware 9.0 right now as it is a bit unstable.
I've been reading your posts. So all I have to do is download ReinX and use that as a payload instead of hekate and everythig is good?
 
Hey guys
So I'm trying to boot into stock FW 9.0 using Hekate and after much Trial and Error the Switch finally boots, but I have 1 last issue I need to resolve:

As soon as the Switch boots, I get an error about the GameCard Reader not working, and , well, I need it to work lol.

As per the instruction here https://github.com/Atmosphere-NX/Atmosphere/releases/tag/0.9.4 I have added "nogc = 0" to my BCT.ini file, but it still doesn't work:/ See attached imaged
Gamecard cannot be read even though nogc is disabled.png

Could it be something as simple as the GC Reader not being able to update while a GameCard is in it?
 
Hey guys
So I'm trying to boot into stock FW 9.0 using Hekate and after much Trial and Error the Switch finally boots, but I have 1 last issue I need to resolve:

As soon as the Switch boots, I get an error about the GameCard Reader not working, and , well, I need it to work lol.

As per the instruction here https://github.com/Atmosphere-NX/Atmosphere/releases/tag/0.9.4 I have added "nogc = 0" to my BCT.ini file, but it still doesn't work:/ See attached imaged
View attachment 179758

Could it be something as simple as the GC Reader not being able to update while a GameCard is in it?
Are you sure that you are on FW 9.0? Because if you updated to 9.0, the gamecard slot also updated and can't be used on versions below 9.0
 
  • Like
Reactions: ragestaker21
Are you sure that you are on FW 9.0? Because if you updated to 9.0, the gamecard slot also updated and can't be used on versions below 9.0

Yeah, I am definitely on 9.0. I upgraded my FW a few days ago through official means but using a method that prevented the Switch from rebooting and burn my fuses. Under system settings, my FW is listed as 9.0.
 
Yeah, I am definitely on 9.0. I upgraded my FW a few days ago through official means but using a method that prevented the Switch from rebooting and burn my fuses. Under system settings, my FW is listed as 9.0.
If you boot with hekate, you need to disable autonogc in the hekate settings.
 
  • Like
Reactions: XaneTenshi
If you boot with hekate, you need to disable autonogc in the hekate settings.

Finally!!! This did the trick. Can't believe that was all it took. I guess the solution I was trying to use only works for Atmosphere and not stock FW then? Damnit lol, all in all, this took well over 3 hours...

Thanks
 
  • Like
Reactions: pLaYeR^^
Finally!!! This did the trick. Can't believe that was all it took. I guess the solution I was trying to use only works for Atmosphere and not stock FW then? Damnit lol, all in all, this took well over 3 hours...

Thanks
Hekate doesn’t use BCT.ini but the hekate ipl ini. BCT.ini is used by fusee primary.
 
Hello and good day, I have a switch it was 8.1.0 firmware, i updated yesterday to 9.0.0 and used the latest version of kosmos and atmosphere. Unfortunately I couldnt install any nsps at all. So i tried rolling back to 8.1.0 using this video guide: unfortunately my switch after turning it on again in rcm then launching sysnand the atmosphere logo shows up then the nintendo logo then it freezes for a bit then it gives me a huge error message, i tried using my nand backup today and then rebooting the switch does the same thing and gives me an error message, the error message is attached as a picture to this post. please help is my switch bricked or is there hope? It only starts up into rcm mode with hekate or whichever payload I use but it doesnt boot properly to my main menu.
69990463_3457465377600511_6824406723550248960_n.jpg
 
Hello and good day, I have a switch it was 8.1.0 firmware, i updated yesterday to 9.0.0 and used the latest version of kosmos and atmosphere. Unfortunately I couldnt install any nsps at all. So i tried rolling back to 8.1.0 using this video guide: unfortunately my switch after turning it on again in rcm then launching sysnand the atmosphere logo shows up then the nintendo logo then it freezes for a bit then it gives me a huge error message, i tried using my nand backup today and then rebooting the switch does the same thing and gives me an error message, the error message is attached as a picture to this post. please help is my switch bricked or is there hope? It only starts up into rcm mode with hekate or whichever payload I use but it doesnt boot properly to my main menu.View attachment 179778

If it’s getting you to the boot logo it’s gotta be something like a theme you had installed or something you have to delete to get past it or even background services, becauss I just literally downgraded with that same tutorial from9.0.0 sysnand to 8.1.0 so I could use emunand again and it went smooth first try no backup needed
 
I'm going to hack my hackable switch soon, I've ordered a decent 256gb microsd. I have a few questions:
-is fat32 really more stable than exfat or it's just a rumor?
-can I use the same microsd for both emunand and sysnand without having issues? Note that I want to go online with the sysnand.

Thanks!

Inviato dal mio SM-G960F utilizzando Tapatalk
 
I'm going to hack my hackable switch soon, I've ordered a decent 256gb microsd. I have a few questions:
-is fat32 really more stable than exfat or it's just a rumor?
-can I use the same microsd for both emunand and sysnand without having issues? Note that I want to go online with the sysnand.

Thanks!

Inviato dal mio SM-G960F utilizzando Tapatalk
Fat 32 is more secure yes but I use exfat always and never have problems plus I prefer it because I don’t have to split files into 4gb increments like fat 32 will have you doing or usb installs is the other route (computer to console install for fat32)

Second yes you can have emunand on the SD and boot normal os when you please and the filesystems remain separate from eachother so what you do on one won’t show on the other , I have sxos + atmosphere on one sd (atmosphere for edizon use), and the other sd card I have is just emunand and clean sysnand
 
Ok so, Just bought a "hackable"Switch and I have been reading around the forum for a couple of days...

Got SX OS Pro..... finished backing up my Virgin NAND with SX OS bootloader and now I'm ready to hack..

My OFW is currently 4.1.0, so I know I won't be able to play many games with it...


Question: Is there a way (and is it the best way?) to keep my OFW on 4.1.0 and let's say, install EmuNAND on 8.1.0 to be able to play newer gamer?

or,

EmuNAND won't accept a newer firmware than the OFW from the device??

if not, should I use ChoiDujourNX to install 8.1.0 since 9.0.0 is non hackable yet and then install EmuNAND also in 8.1.0?

and lastly, should I go up to 8.1.0 or is there a better FW a long the way that I should update and stay at??

Details: Trying not to get banned so quickly, will be playing mostly offline on EmuNAND, want to play some switch games, and some emulators.

Sorry for the long post.... If anyone can help I appreciate, thanks..
 

Site & Scene News

Popular threads in this forum