Hacking SWITCH NOOB PARADISE - Ask questions here

[NotSolaxy]

Let’s try maintenance mode.

Power off the system by holding the power button for 15 seconds.
While holding both (vol +) AND (vol -) power on the Switch and hold on until it it comes up in maintenance mode.
We don’t want to do anything in maintenance mode. Just exit/reboot.

Didn't work.

 

[binkinator]

Didn't work.

if that doesn’t work, here’s a trick to reset requirements for a game via DBI

latest release here

 

[NotSolaxy]

if that doesn’t work, here’s a trick to reset requirements for a game via DBI

latest release here

It worked! Now I am gonna check if tinfoil works.

 

[binkinator]

It worked! Now I am gonna check if tinfoil works.

Awesome! Glad that’s sorted. Might have to do this for each game…

 

[NotSolaxy]

Oh my, I am still getting the "Checking if game can be played..." error and Awoo and Tinwoo aren't working either.
Not sure what to do now.

 

[binkinator]

Oh my, I am still getting the "Checking if game can be played..." error and Awoo and Tinwoo aren't working either.
Not sure what to do now.

This typically means the game was installed by a different user Profile than the one you are using. Usually can be solved by reinstalling…lets try using DBI…it’s a fantastic installer in its own right.

 

[NotSolaxy]

This typically means the game was installed by a different user Profile than the one you are using. Usually can be solved by reinstalling…lets try using DBI…it’s a fantastic installer in its own right.

Oh, I am talking about the game I am trying to install now.

 

[binkinator]

Oh, I am talking about the game I am trying to install now.

Try installing it with DBI

 

[NotSolaxy]

Try installing it with DBI

How would I be able to?

 

[NotSolaxy]

Hey so I updated my sigpatches and installed the tickets and it actually worked! The games work! Thank you for all your help. <3

 

[binkinator]

Hey so I updated my sigpatches and installed the tickets and it actually worked! The games work! Thank you for all your help. <3

You bet. Glad you’re sorted.

 

[steve_fox]

Ive hit an issue

I wanted to install Android so a few days ago i had to create a partition for it and so had to export all my data, created the new partitions and imported the data back.

I installed android which works fine and HOS was working but didn't attempt to play any of the games i had installed.

Last night i discovered that all but two of the installed games would not run so i deleted them all as set about the mammoth task of reinstalling them all.

On the very last game install, HOS crashed and sent me to Hekate which now gives me the error in the attached photo.

Stock Fw still works fine as does Android but i cant boot into CFW.

Can this be fixed or do i need to rebuild everything from scratch?

 

[binkinator]

Ive hit an issue

I wanted to install Android so a few days ago i had to create a partition for it and so had to export all my data, created the new partitions and imported the data back.

I installed android which works fine and HOS was working but didn't attempt to play any of the games i had installed.

Last night i discovered that all but two of the installed games would not run so i deleted them all as set about the mammoth task of reinstalling them all.

On the very last game install, HOS crashed and sent me to Hekate which now gives me the error in the attached photo.

Stock Fw still works fine as does Android but i cant boot into CFW.

Can this be fixed or do i need to rebuild everything from scratch?

Good news is HOS and the rest of your switch is good.

Try and reinstall /atmosphere/fusee.bin from GitHub (make sure you use the same version.) If that doesn’t work the it’s likely you mucked something up that would be complex to fix and it’s probably faster to just redo it from scratch. (If you need to grab your game saves you can do it with NXNandManager without having to boot into CFW.)

To be honest it’s better to do the partitioning up front in Hekate anyway, rather than trying to thread the needle with the clunky and finicky partitioning tools afterwards.

e: if you still have your FAT32 backup…even easier To do really quickly.

 

[steve_fox]

Good news is HOS and the rest of your switch is good.

Try and reinstall /atmosphere/fusee.bin from GitHub (make sure you use the same version.) If that doesn’t work the it’s likely you mucked something up that would be complex to fix and it’s probably faster to just redo it from scratch. (If you need to grab your game saves you can do it with NXNandManager without having to boot into CFW.)

To be honest it’s better to do the partitioning up front in Hekate anyway, rather than trying to thread the needle with the clunky and finicky partitioning tools afterwards.

e: if you still have your FAT32 backup…even easier To do really quickly.

when you say the FAT32 backup, do you mean the whole SD that i exported before partitioning for Android?

If you mean that then yes, i still have it.

 

[binkinator]

when you say the FAT32 backup, do you mean the whole SD that i exported before partitioning for Android?

If you mean that then yes, i still have it.

Perfect…yeah. I just mean the one partition with all your stuff on it that you can access via normal Windows Explorer. (Atmosphere/Hekate/Homebrew/configs). If you have your old emunand partition backed up you can pull your game saves as well. Thats really the whole shooting match. Just format everything and then grab the bulk of everything from backups….longest process will be waiting for data to copy over. You did yourself a big favor and are in a good spot. :-)

e: I do a complete bit-for-bit copy of my entire 400G sd card every couple of weeks and switch cards. Partly to give my sd cards a break but also so if I lose a card I’m only a few changes behind rather than losing everything. If you have that much ish on your card, and your time is valuable enough, you might be able justify a duplicate backup card.

 

[tlfrance]

Still makes absolutely no sense how you could have possibly followed the guide and ended up with those versions. They are incorrect and lead me to believe that your installation is unstable. Please go back through the guide again and get everything updated to Atmos 1.3.2 and Firmware 14.1.1. There is no sense in troubleshooting further until you get the foundational pieces correct.

It likely has little to do with any of this. Please fix yourinstallation first.

I've fix my issue. Just added this line "kip1patch=nosigchk" into the hekate ini file .

 

[raaamesh]

i have been using exfat since sx days, now in atmosphere for awhile still using exfat no problems. any reason to change to fat32

 

[Nightf0x]

can i use multiple cfws with my emunand ? if yes can someone point me to a guide or something TIA, as my friend modded my switch and kept the sysnand ofw and shallowsea cfw emunand, i would like to run atmos cfw

 

[877]

Dude…that’s pretty savant like discipline actually. Very impressive!

4.0.0-4.1.0 is the range of Firmware you can comfortably run on your Sysnand without burning any fuses or triggering the anti-downgrade mechanism. You have a backup of 4.1.0 so you’re good to go…as long as you’ve been running clean since your 3.0.2 days (but I have a lot of faith in you at this point.)

Now that we’ve arrived at this point though, you’re only as safe as your last mistake. If you’ve never gone online your are probably OK as we speak. Just turn AutoRCM off and you’re as good as a brand new unhacked machine. Nobody would be the wiser. AutoRCM would have prevented Sysnand fro, ever spinning up and being able to log anything.

unfortunately the test for all of this is to actually go online and then wait for however long to see if you don’t get banned. Hardly worth the effort IMO.

Why thank you!
Cool then, good news! I need to catch myself up on emunand/Sysnand, been a while and not 100% confident how it all works.

Wondering if I should run on emunand, even though I have no plans to go online?
And what is the best method of installing NSP's via USB cable?

Starting reading through forum now, thanks again!

 

[binkinator]

Why thank you!
Cool then, good news! I need to catch myself up on emunand/Sysnand, been a while and not 100% confident how it all works.

Spoiler: Emu/Sys nand

heavily plagiarized from here.
emuNAND vs emuMMC vs sysNAND

• sysNAND stands for System NAND, meaning the internal storage in your actual Switch.
• emuNAND stands for emulated NAND, this means that your entire NAND (system memory) will run off your microSD card with Custom Firmware (CFW). This NAND's contents (games, applications, saves, etc.) are completely separate from your sysNAND.
• emuMMC is the name for the currently used implementation of emuNAND on Switch. It has no difference from emuNAND besides name.

---

emuNAND CFW​

Pros of using emuNAND over sysNAND CFW:​

• Using homebrew applications such as save editors, or cheating in games offline without "dirtying" or affecting sysNAND, allowing sysNAND to be used online without ban risk.
• Any mistakes can be remedied by making another copy of your clean Sysnand. You would have to rely on your own backups if you were writing on the system copy.

Wondering if I should run on emunand, even though I have no plans to go online?

I recommend emunand…if a grenade blows up (brickware, mistake, whatever) it happens in a fake nand rather than your real ground zero. Yiu might change your mind later about going online or want to sell a pristine switch. You never know…

And what is the best method of installing NSP's via USB cable?

IMO DBI with USB 3.0 option on is king here. Tinwoo is a solid contender as well. Tinfoil is good too but can be finicky to get set up.

Starting reading through forum now, thanks again!

You bet! Good luck!