Hacking SWITCH NOOB PARADISE - Ask questions here

[Temaps]

Hello,
What are the best emulators for the switch ? I've come across multiple "fights" where people would say that retroarch is the best and other people would say it is better to instead take the best emulator and not rely on retroarch so as to be able to choose the one with the most compatibility.
I also read (few days ago) a website saying something (sorry this is vague in my brain) about the fact that retroarch should not be started from... main menu or homebrew launcher (don't remember) or it would crash (found quite the same information in https://gbatemp.net/threads/retroarch-switch.492920/ section Disclamers point 3).
I have not investigated yet what is "tile redirection" and if it is still necessary as this seems to be linked to a full memory access that is now performed by simply holding R button on the switch while launching retroarch ?

What I have found so far :

• https://wiki.gbatemp.net/wiki/List_of_Switch_homebrew_emulators : Good ressource but no choice, should it be considered that those are the best ? Is it up to date ?
• https://emulation.gametechwiki.com/index.php/Emulators_on_Switch : gives a lot of choices with recommandations based on criteria such as accuracy, active etc... It seems to indicate in the end that Retroarch is the best choice as most of its "cores" are considered recommended which according to https://emulation.gametechwiki.com/index.php/Recommended_emulators is a key point.
• https://gbatemp.net/threads/retroarch-switch.492920/ : Just if retroarch is the best choice, this seems to be the most up to date guide.

As I'd like to play my ds games (a bit afraid about compatibility of games that requires touchscreen...) it seems that Retroarch will be the good choice as it would even include "cores" to play other retro games such as N64 etc... ?

 

[binkinator]

Quick question. I am trying to figure out how to "reset" my chip. I know on some revisions there are 2 pads on it and you simply bridge them. My chip doesn't appear to have those pads. Atleast not in the same location. Is there another way to reset it? I'm using the V5 chip in a V2 switch. When I boot without an SD card I get the drumpy boot.dat? logo if that helps at all.

Picture attached of back of chip.

I’ve not encountered this yet.

You can reset it by booting hwflyNX-toolbox.bin located here:

https://github.com/hwfly-nx/hwfly-toolbox


Here are some wild “out there” suggestions:


1) put a jig in the right joycon?
2) leave it powered on until the battery drains.


If you’ve bricked it, check out sthetix here:

https://www.sthetix.info/flashing-updating-unbricking-the-chip/

 

[dehydrated_lemur]

Thanks I didn't brick it but I'm reading I might need to reset it after taking the new update? Not sure.

Also so that means if my battery ever dies on me the chip will reset?

 

[binkinator]

Hello,
What are the best emulators for the switch ? I've come across multiple "fights" where people would say that retroarch is the best and other people would say it is better to instead take the best emulator and not rely on retroarch so as to be able to choose the one with the most compatibility.
I also read (few days ago) a website saying something (sorry this is vague in my brain) about the fact that retroarch should not be started from... main menu or homebrew launcher (don't remember) or it would crash (found quite the same information in https://gbatemp.net/threads/retroarch-switch.492920/ section Disclamers point 3).
I have not investigated yet what is "tile redirection" and if it is still necessary as this seems to be linked to a full memory access that is now performed by simply holding R button on the switch while launching retroarch ?

What I have found so far :

• https://wiki.gbatemp.net/wiki/List_of_Switch_homebrew_emulators : Good ressource but no choice, should it be considered that those are the best ? Is it up to date ?
• https://emulation.gametechwiki.com/index.php/Emulators_on_Switch : gives a lot of choices with recommandations based on criteria such as accuracy, active etc... It seems to indicate in the end that Retroarch is the best choice as most of its "cores" are considered recommended which according to https://emulation.gametechwiki.com/index.php/Recommended_emulators is a key point.
• https://gbatemp.net/threads/retroarch-switch.492920/ : Just if retroarch is the best choice, this seems to be the most up to date guide.

As I'd like to play my ds games (a bit afraid about compatibility of games that requires touchscreen...) it seems that Retroarch will be the good choice as it would even include "cores" to play other retro games such as N64 etc... ?

High level, Retroarch is a good starting point for just about everything. It’s a great generalist and will work great for playing DS games. There are cases such as ppsspp where the standalone performs better for some games so purists will argue this is a case for using standalone only. Standalone can also be a little bit easier to configure as the Retroarch ecosystem can be daunting. IMO you should bite the bullet and install Retroarch and it will serve most of your retro gaming needs. If you run into an edge case situation where a game you really want to play isn’t working, try the standalone and see if it works any better. There‘s nothing that says you can’t run both!

Title override is holding down R while launching an official game. This will launch home brew menu in full memory mode at which point you can launch the Retroarch nro inside its menu system. Using a Retroarch forwarder has the same effect since it is launched “as a title” with full memory available.

Thanks I didn't brick it but I'm reading I might need to reset it after taking the new update? Not sure.

You mean the new Ninty 16.0.0 firmware? If so, the current Atmosphere will not work. We are all waiting for the new release be we can upgrade.

Also so that means if my battery ever dies on me the chip will reset?

It might have to retrain after completely losing battery. It shouldn’t impact anything though if it does. I keep mine on a charger so I haven’t seen this in action yet.

 

[dehydrated_lemur]

Yes I mean the new 16 update. I was told that after taking the update and updating atmosphere we need to reset the hwfly also. I did not update. I'm in no rush.

 

[binkinator]

Yes I mean the new 16 update. I was told that after taking the update and updating atmosphere we need to reset the hwfly also. I did not update. I'm in no rush.

Everything is hypothetical until we get the release in hand. Should be F.U.n.

 

[dehydrated_lemur]

lol. yeah you right thanks.

You're like the switch legend.

 

[wikisa]

I've received switch with the hwfly, I followed up rentry guide and now I've succesfully booted to the atmoshpere. I've created emuNand and updated OS it to the newest possible version for current atmosphere - 15.0.1. But can I also update OFW on sysnand to 16.0? Those are on separate storages, so there shouldn't be any issue to have atmosphere with 15.0.1 on emuNand and 16.0 on sysnand, right?

Post automatically merged: Feb 22, 2023

I've received switch with the hwfly, I followed up rentry guide and now I've succesfully booted to the atmoshpere. I've created emuNand and updated OS it to the newest possible version for current atmosphere - 15.0.1. But can I also update OFW on sysnand to 16.0? Those are on separate storages, so there shouldn't be any issue to have atmosphere with 15.0.1 on emuNand and 16.0 on sysnand, right?

Also, can I increase somehow the dead zone for left analog stick? I've noticed that even if I'm not touching it the cursor is just going down in Hekate, so probably I've got analog drifting.

 

[binkinator]

I've received switch with the hwfly, I followed up rentry guide and now I've succesfully booted to the atmoshpere. I've created emuNand and updated OS it to the newest possible version for current atmosphere - 15.0.1. But can I also update OFW on sysnand to 16.0? Those are on separate storages, so there shouldn't be any issue to have atmosphere with 15.0.1 on emuNand and 16.0 on sysnand, right?

Post automatically merged: Feb 22, 2023

Also, can I increase somehow the dead zone for left analog stick? I've noticed that even if I'm not touching it the cursor is just going down in Hekate, so probably I've got analog drifting.

Do not upgrade to 16.0.0 on your CFW. Upgrading on OFW is fine but not required…there are no games that require it today.

You are describing drift. You should replace your joysticks or try the paper trick.

 

[wikisa]

Do not upgrade to 16.0.0 on your CFW. Upgrading on OFW is fine but not required…there are no games that require it today.

You are describing drift. You should replace your joysticks or try the paper trick.

Probably I described a drift, but in the "Calibrate control sticks" screen, and in games the joysticks works perfectly, only in hekate the cursor is going slightly down, so my bet was that in the HOS there is larger dead zone and in Hekate there is less dead zone. So there aren't magic setting in hekate that will increase the dead zone in it?

// edited: Okay, I've probably found it at the github issue of hekate (cannot post the links but the issue #411 in github). I'll try that

 

[binkinator]

Probably I described a drift, but in the "Calibrate control sticks" screen, and in games the joysticks works perfectly, only in hekate the cursor is going slightly down, so my bet was that in the HOS there is larger dead zone and in Hekate there is less dead zone. So there aren't magic setting in hekate that will increase the dead zone in it?

// edited: Okay, I've probably found it at the github issue of hekate (cannot post the links but the issue #411 in github). I'll try that

Oh neat! Wasn’t even aware of this. Great find!

for those that are curious:

https://github.com/CTCaer/hekate/issues/411


The dead zone in hekate is that simple thing

jc_drv_ctx.cx_max = jc_pad->lstick_x + 0x72;
jc_drv_ctx.cx_min = jc_pad->lstick_x - 0x72;
jc_drv_ctx.cy_max = jc_pad->lstick_y + 0x72;
jc_drv_ctx.cy_min = jc_pad->lstick_y - 0x72;

A 114 (0x72) units buffer.

 

[wikisa]

hmmm, after upgrading OFW to 16.0 and when I'm trying to boot atmosphere on CFW with 15.0.1 I've got:

A fatal error occurred when running Fusee.
Failed to locate warmboot firmware!

I initialy thought that SD card gets formated after update, but when I view in on pc:

So I bet emunand is on 29,16GB partition and it is should be there on 15.0.1 (I updated on OFW to 16.0). Am I missing something?

 

[binkinator]

hmmm, after upgrading OFW to 16.0 and when I'm trying to boot atmosphere on CFW with 15.0.1 I've got:

A fatal error occurred when running Fusee.
Failed to locate warmboot firmware!

I initialy thought that SD card gets formated after update, but when I view in on pc:

View attachment 354873

So I bet emunand is on 29,16GB partition and it is should be there on 15.0.1 (I updated on OFW to 16.0). Am I missing something?

yes, the 29.16GB is absolutely the Emunand and it does not get touched during an OFW update.

Are you on a V1 or a V2?

You can still boot OFW, correct?

 

[wikisa]

yes, I can still boot into OFW, i'm on switch lite with hwfly

 

[binkinator]

yes, I can still boot into OFW, i'm on switch lite with hwfly

I upgraded my V1 and have no issues getting into CFW. Let me do my V2. I‘m guessing it’s trying to interact with boot 0/1. We might be stuck waiting on the Atmosphere/Hekate upgrade on V2. Give me a second.

my V1 can not boot into OFW anymore. Ungh.



Waiting for my V2 to finish updating Fortnite and then I’ll try that one too. Might not be able to go Online for a bit until the new Atmosphere is released. Good times.

 

[TheJinKazama]

Do not upgrade to 16.0.0 on your CFW. Upgrading on OFW is fine but not required…there are no games that require it today.

You are describing drift. You should replace your joysticks or try the paper trick.

I’m a confused n00b… I asked about updating stock and CFW last night and someone suggested not updating at all.

I play online and offline cartridge games on stock and offline SD backups on CFW. This is a V1 Switch which I use an RCM jig with.

 

[Hayato213]

I’m a confused n00b… I asked about updating stock and CFW last night and someone suggested not updating at all.

I play online and offline cartridge games on stock and offline SD backups on CFW. This is a V1 Switch which I use an RCM jig with.

There is no CFW for firmware 16.0.0 at the moment, that why it is recommend to update if you are 15.0.1.

 

[binkinator]

OK, I upgraded my V2 and after a short bout of my glitch taking a reaaaaallly long time to do it's thing (HWFLY V5)

This is what I got while booting with the payload=/bootloader/payloads/fusee.bin option:


hitting power to reboot ends with me having to hold the power button for 12 seconds to reboot.

So we’re done here, huh? Not so fast!

This is what I got while booting with the fss0=/atmosphere/package3 option:



hitting VOL just gives me this:



that‘s no good…

but

let’s try the power button to continue next time…



oh? What’s this?



Wahoooo!

so that’s the workaround, folks…

check my dns:mitm:



shields are up!

How about serial number blanking with exosphere.ini?



looking good!

games still boot up and are playable…



I feel like a winner!

The only issue I’ve found thus far is that when it goes to sleep…it doesn’t wake back up properly and you have to hold the power button for 12 seconds to hard reset.


Here’s the stanza in my V2’s /bootloader/hekate_ipl.ini file that worked for me:

[Atmosphere fss0]
fss0=atmosphere/package3
emummcforce=1
kip1=atmosphere/kips/loader.kip
kip1patch=nosigchk
kip1=atmosphere/kip_patches/*
icon=bootloader/res/icon_switch.bmp

note: if you get an error about kips make sure you have the latest Sigpatches installed:

https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/
(thanks @wikisa for this fix)

 

[dehydrated_lemur]

OK, I upgraded my V2 and after a short bout of my glitch taking a reaaaaallly long time to do it's thing (HWFLY V5)

This is what I got while booting with the payload=/bootloader/payloads/fusee.bin option:

View attachment 354898
hitting power to reboot ends with me having to hold the power button for 12 seconds to reboot.

So we’re done here, huh? Not so fast!

This is what I got while booting with the fss0=/atmosphere/package3 option:

View attachment 354899

hitting VOL just gives me this:

View attachment 354900

that‘s no good…

but

let’s try the power button to continue next time…

View attachment 354906

oh? What’s this?

View attachment 354901

Wahoooo!

so that’s the workaround, folks…

check my dns:mitm:

View attachment 354909

shields are up!

How about serial number blanking with exosphere.ini?

View attachment 354910

looking good!

games still boot up and are playable…

View attachment 354912

I feel like a winner!

The only issue I’ve found thus far is that when it goes to sleep…it doesn’t wake back up properly and you have to hold the power button for 12 seconds to hard reset.


Here’s the stanza in my V2’s /bootloader/hekate_ipl.ini file that worked for me:

You are on 16.0 now?

 

[wikisa]

OK, I upgraded my V2 and after a short bout of my glitch taking a reaaaaallly long time to do it's thing (HWFLY V5)

This is what I got while booting with the payload=/bootloader/payloads/fusee.bin option:

View attachment 354898
hitting power to reboot ends with me having to hold the power button for 12 seconds to reboot.

So we’re done here, huh? Not so fast!

This is what I got while booting with the fss0=/atmosphere/package3 option:

View attachment 354899

hitting VOL just gives me this:

View attachment 354900

that‘s no good…

but

let’s try the power button to continue next time…

View attachment 354906

oh? What’s this?

View attachment 354901

Wahoooo!

so that’s the workaround, folks…

check my dns:mitm:

View attachment 354909

shields are up!

How about serial number blanking with exosphere.ini?

View attachment 354910

looking good!

games still boot up and are playable…

View attachment 354912

I feel like a winner!

The only issue I’ve found thus far is that when it goes to sleep…it doesn’t wake back up properly and you have to hold the power button for 12 seconds to hard reset.


Here’s the stanza in my V2’s /bootloader/hekate_ipl.ini file that worked for me:

I tried your /bootloader/hekate_ipl.ini but i've got error thats atmosphere/kips/loader.kip is missing. Where could I download it with also atmosphere/kip_patches, because when i google for it the things I only found are 404 on github

// okay I got it from https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/ after choosing CFW it succesfully boot back to the 15.0.1 emuNand! Thank you binkinator, you're the hero! I'm also have to hard reset after sleep, but thats better than nothing