Hacking SWITCH NOOB PARADISE - Ask questions here

[Draxzelex]

I'm not sure what's the problem but I'm going to ask here either way.

I recently updated my Switch to 12.0.1 (I shouldn't have but oh well) and also everything CFW wise - Atmosphere 0.19.1 & hekate 5.5.5. I did a clean install, formatted my SD card and created emuMMC again. Everything seems to be working well but I noticed, Reboot function from the Switch sometimes won't work? It does reboot the system but every now and then it just stays at blank/black screen after either the Atmosphere logo or Switch logo. I have to turn it off completely and re-send the payload for me to be able to boot. It is very odd.

It only happens when I reboot it using the Switch power menu. If I use Reboot to Payload from hbmenu or from NXThemes Installer it works fine. Not sure what the problem is, I re-did all my installation 3 times already just to make sure and downloaded directly from Atmosphere's and hekate's Github but it still occurs. I even disabled the themes and plugins. I'm actually lost.

My initial thought is that maybe is something wrong with the reboot_to_payload.bin file. Depending if you want to use fusee or Hekate, I would download the latest version of either, rename it to reboot_to_payload.bin, then use that file to replace the one currently in the /atmosphere folder

 

[C7XL]

My initial thought is that maybe is something wrong with the reboot_to_payload.bin file. Depending if you want to use fusee or Hekate, I would download the latest version of either, rename it to reboot_to_payload.bin, then use that file to replace the one currently in the /atmosphere folder

Yea, that what I thought so too that's why I re-did my setup 3 almost 4 times and made sure I rename all the files correctly. I want to use Hekate that's why I rename it to reboot_payload.bin everytime. It's just very odd that this happens.

EDIT: So I decided to downgrade back to HOS 10.2.0 since I found out NRO forwarders doesn't work on Atmosphère 0.19.1 and the USB changes from HOS 11.0.0, might as well stay on HOS 10.2.0 for a while until I really need to update.

 

[Draxzelex]

Yea, that what I thought so too that's why I re-did my setup 3 almost 4 times and made sure I rename all the files correctly. I want to use Hekate that's why I rename it to reboot_payload.bin everytime. It's just very odd that this happens.

Then I can't really think of anything else that could cause the issue. Assuming your SD card is formatted to FAT32, then corruption isn't a likely cause either. It might be worth opening an issue on the Atmosphere GitHub page.

 

[TheGreek Boy]

Hi im trying to run caffeine with pegascape on 3.0.0 and all the time i have the error 2207-0248... And when i try the hb menu i have error 2162-0002 when i launch the album.. i dont know what the problem is

 

[smudgester]

So, not wanting to make the same firmware update mistake I made last time, I am currently not accepting the prompt to install the latest update.

However, what I don't understand is ... my Switch is on a wired connection and is using the 90DNS IP addresses for its primary and secondary DNS yet the Switch is still able to detect new firmware is available. I was under the impression that using 90DNS was meant to stop this ?

However, when I use the "90DNS tester" homebrew app it says there are still some Nintendo domains unblocked ? Though when I try again it says they are all blocked and yet I am still prompted to do a system update whenever I start a game

Is there a more fool proof of blocking system updates - that don't involve disabling the internet connection completely - other than 90DNS ?

 

[Adran_Marit]

So, not wanting to make the same firmware update mistake I made last time, I am currently not accepting the prompt to install the latest update.

However, what I don't understand is ... my Switch is on a wired connection and is using the 90DNS IP addresses for its primary and secondary DNS yet the Switch is still able to detect new firmware is available. I was under the impression that using 90DNS was meant to stop this ? However, when I use the "90DNS tester" homebrew app it says there are still some Nintendo domains unblocked ?

incognito and atmospheres dns redirect also work

 

[smudgester]

incognito and atmospheres dns redirect also work

Is atmosphere dns redirect the thing at the top of https://nh-server.github.io/switch-guide/extras/blocking_updates/#instructions-90dns ?

And regarding incognito ... my Switch (even without a jig and with - pressed while powering up) boots straight into atmosphere. How do get it go back to RCM mode so that I can inject the incognito payload ?

 

[neontiger]

Have you checked to see if the SD card is fake or not?

Yes for both of them and they're not, bought them from reliable Amazon stores in the UK, all new not refurbished.

I would probably just update the nand, unless you are using pegascape or something

I will consider updating the NAND, I would be interested in PegaScape's RCM method but as things turned out that will be the least of my concerns.
Is there an option to create emuNAND on a second, updated Switch and then use the same SD card on mine?

 

[Draxzelex]

Yes for both of them and they're not, bought them from reliable Amazon stores in the UK, all new not refurbished.

That is not what I meant. A reliable reseller doesn't automatically make an SD card real. Amazon has sold plenty of fake SD cards before. It is definitely worth testing the legitimacy of your SD card.

 

[neontiger]

That is not what I meant. A reliable reseller doesn't automatically make an SD card real. Amazon has sold plenty of fake SD cards before. It is definitely worth testing the legitimacy of your SD card.

The store is an authorised Sandisk reseller, other than that there doesn't seem to be anything suspicious on the product's shape or appearance.

 

[Draxzelex]

The store is an authorised Sandisk reseller, other than that there doesn't seem to be anything suspicious on the product's shape or appearance.

Again, you cannot verify if an SD card is fake or not based on who sold it. You have to use a program such as h2testw or FakeFlashTest.

 

[Nathanas]

Hi guys. Well...I'm exhausted. Haven't been on the old switch for a few months and I thought I'd be a smarty pants and update atmosphere.....long story short I cooked my cfw and couldn't boot atmosphere. Tried reinstalling etc but eventually after hours of gruelling work I just started from scratch and did a brand new install from https://nh-server.github.io/switch-guide/

Aaaaand that didn't work. I now have a proper looking hekate but when I boot emunand I get a "panic occured" message.

Do I need to update my ofw to latest? I'm still on 10.1.

Any help greatly appreciated!

 

[Draxzelex]

Hi guys. Well...I'm exhausted. Haven't been on the old switch for a few months and I thought I'd be a smarty pants and update atmosphere.....long story short I cooked my cfw and couldn't boot atmosphere. Tried reinstalling etc but eventually after hours of gruelling work I just started from scratch and did a brand new install from https://nh-server.github.io/switch-guide/

Aaaaand that didn't work. I now have a proper looking hekate but when I boot emunand I get a "panic occured" message.

Do I need to update my ofw to latest? I'm still on 10.1.

Any help greatly appreciated!

You definitely should not need to update let alone update to the latest period because that is something that would need to be addressed in Atmosphere. I don't see people getting good results by following the guide you posted so I recommend following this one instead.

 

[smudgester]

When I first hacked my Switch, I followed the Github guide without any issues at all.

 

[Ibcap]

Is atmosphere dns redirect the thing at the top of https://nh-server.github.io/switch-guide/extras/blocking_updates/#instructions-90dns ?

And regarding incognito ... my Switch (even without a jig and with - pressed while powering up) boots straight into atmosphere. How do get it go back to RCM mode so that I can inject the incognito payload ?

Yes the thing at the top is dns redirection. IDK why they still recommend 90dns on there when the dns mitm is much more secure and gives better results. As for your second question, do you have a modchip? A normal unit requires pushing a payload to enter cfw and you have to be in rcm to push the payload. Also this is all irrelevant to incognito anyway, incognito isnt a payload, that was just an old unsupported fork someone made. Incognito is a feature that exists within tinfoil.

 

[smudgester]

Yes the thing at the top is dns redirection. IDK why they still recommend 90dns on there when the dns mitm is much more secure and gives better results

Thanks - that seems simple enough to do - just updating a text file on the SD card (or adding if it is not there already)

As for your second question, do you have a modchip? A normal unit requires pushing a payload to enter cfw and you have to be in rcm to push the payload. Also this is all irrelevant to incognito anyway, incognito isnt a payload, that was just an old unsupported fork someone made. Incognito is a feature that exists within tinfoil.

Don't have a modchip - but pretty sure, now I come to think of it, that it has auto rcm enabled AND has a default payload selected. Just can't remember how you, temporarily, disable both those things.

But then if it exists in Tinfoil then that's even easier ... do you just select Incognito -> Serial Number and delete it ? Obviously making a note of it first

 

[Ibcap]

Thanks - that seems simple enough to do - just updating a text file on the SD card (or adding if it is not there already)



Don't have a modchip - but pretty sure, now I come to think of it, that it has auto rcm enabled AND has a default payload selected. Just can't remember how you, temporarily, disable both those things.

But then if it exists in Tinfoil then that's even easier

You HAVE to inject a payload manually when booting your console to get into cfw. You cant autoinject a payload without a modchip. First the console goes to rcm, then you inject a payload via a dongle/pc/phone, then you get to cfw. You cant skip any of those steps.

 

[smudgester]

You HAVE to inject a payload manually when booting your console to get into cfw. You cant autoinject a payload without a modchip. First the console goes to rcm, then you inject a payload via a dongle/pc/phone, then you get to cfw. You cant skip any of those steps.

Well whatever my Switch is doing - WITHOUT A MODCHIP OR ANY JIG IN THE CONTROLLER SLOT - it is definitely booting straight into Atmosphere when it is told to restart

 

[Ibcap]

Well whatever my Switch is doing - WITHOUT A MODCHIP OR ANY JIG IN THE CONTROLLER SLOT - it is definitely booting straight into Atmosphere when it is told to restart

Reboot via atmosphere isnt the same as cold booting from a shutdown, rebooting will use a specific payload from the atmosphere folder. Booting the console normally doesnt do this.

 

[Nathanas]

You definitely should not need to update let alone update to the latest period because that is something that would need to be addressed in Atmosphere. I don't see people getting good results by following the guide you posted so I recommend following this one instead.

Thanks for your prompt reply. It seems something as simple as reading the error message in the hekate/Atmos boot screen is something to pay attention to. It told me to use the archive bit fixer in Hecate and presto we are working beautifully again.