Hacking RELEASE Sigpatches for Atmosphere (fusee-primary only!)

Status
Not open for further replies.
Hey bud, I tried exactly what you said to do by downloading the new Hekate 5.3.3 and extracted the zip file. I put the files on my sd folder, but the same issue still occures..

Delete your atmosphere, sept and bootloader folders. Download everything fresh from github, don't use anything you have on your computer right now.

I recommend to use this guide as reference (this one covers sigpatches as well unlike other guides): https://birbchirp.gitbook.io/switchguide/cfw-guides/atmosphere/atmosphere-installation
 
  • Like
Reactions: Ichigo-Bankai
Just updated my atmosphere and added the new sigpatches. Now I get an error when booting. "Fatal error: (NXBOOT): Messing default patch for KIP 010000000...".
Any Ideas? :(
 
  • Like
Reactions: Ichigo-Bankai
Hi guys,
i'm kinda new to this whole hacking Nintendo switch thing
just hacked it and patched it with these new sigpatches
my OS version is 10.2.0 and atmosphere is 0.14.4
the thing is my switch no longer can pair with my pro controller
any idea how to make it work?

some notes:
1- pro controller is recognizable through wired connection
2- the pro controller itself is totally okay and i verified its functionality
3 - when i start my Nintendo switch without RCM (i didn't AutoRCM it for some reasons) the pro controller is recognizable wireless
4- every other functions work just fine (it totally supports joycons attached or wireless and i play games)
5- i'm not in airplane mode :)
6- yes i use fusee-primary as the injector (well i usually inject hekate first and then go to fusee-primary from there) :)
7- my pro controller is an official Nintendo product and its not counterfeit, i recently charged it and its battery is almost full of charge.

any help would be appreciated since i really am far from the switch and it is on dock most of the time
could it be atmosphere not being stable on 10.2.0 yet?


ps : i have another question as well, as i mentioned i didnt make my switch AutoRCM so everytime i shut it off i need to put a jig in right joycon rail to make it go to RCM is it somehow harmful? and what you overally suggest? should i make it AutoRCM or not?
 
Last edited by Hossein,
I have a question about the bootloader folder.. its a simple question but maybe a long reply on the question.. How is the bootloader created? I'm asking this to learn more about this whole jailbreak thing.. I'm kinda new to jailbreaking.

--------------------- MERGED ---------------------------

Hi guys,
i'm kinda new to this whole hacking Nintendo switch thing
just hacked it and patched it with these new sigpatches
my OS version is 10.2.0 and atmosphere is 0.14.4
the thing is my switch no longer can pair with my pro controller
any idea how to make it work?

some notes:
1- pro controller is recognizable through wired connection
2- the pro controller itself is totally okay and i verified its functionality
3 - when i start my Nintendo switch without RCM (i didn't AutoRCM it for some reasons) the pro controller is recognizable wireless
4- every other functions work just fine (it totally supports joycons attached or wireless and i play games)
5- i'm not in airplane mode :)
6- yes i use fusee-primary as the injector (well i usually inject hekate first and then go to fusee-primary from there) :)
7- my pro controller is an official Nintendo product and its not counterfeit, i recently charged it and its battery is almost full of charge.

any help would be appreciated since i really am far from the switch and it is on dock most of the time
could it be atmosphere not being stable on 10.2.0 yet?


ps : i have another question as well, as i mentioned i didnt make my switch AutoRCM so everytime i shut it off i need to put a jig in right joycon rail to make it go to RCM is it somehow harmful? and what you overally suggest? should i make it AutoRCM or not?
Try to connect your pro controller while your switch is in the dock.. connect your controller wired with the dock. I ran into the same issue when I bought thw pro controller. It works perfect now..
 
I have a question about the bootloader folder.. its a simple question but maybe a long reply on the question.. How is the bootloader created? I'm asking this to learn more about this whole jailbreak thing.. I'm kinda new to jailbreaking.

--------------------- MERGED ---------------------------


Try to connect your pro controller while your switch is in the dock.. connect your controller wired with the dock. I ran into the same issue when I bought thw pro controller. It works perfect now..

thank you kindly
i did that and still i cant play wireless with it ( i want to play wireless with it)
it was fine before hacking
and it is still fine when start switch without RCM
 
thank you kindly
i did that and still i cant play wireless with it ( i want to play wireless with it)
it was fine before hacking
and it is still fine when start switch without RCM

are you in airplane mode? you will need to enable the wireless controller option in the full airplane mode in setting.
that was something that got me at the start.
 
I have a cheaper version of a switch controller. Mine worked like this;

1.) Put switch into the dock
2.) Put your C-cable in your dock and connect it to your controller.
3.) Hit the on button for like 4 seconds to turn on your controller.
4.) Let it synchronize with your switch. It may be necessary to repeat turning on the controller.
5.) It will connect on some point. If this turned out not to be the case look at step 6.)
6.) This works for me sometimes; if you are removing your joycons while your switch is on, (leave them in the rail. Don't remove it from the whole console.) A screen will appear that asks you on how you wish to play on your switch and hit L/R Button. Try to turn on your pro controller.

This always works for me when my controller is acting retarted.
 
How are you launching Hekate? Phone/computer/dongle/etc?
Through the pc

--------------------- MERGED ---------------------------

Just updated my atmosphere and added the new sigpatches. Now I get an error when booting. "Fatal error: (NXBOOT): Messing default patch for KIP 010000000...".
Any Ideas? :(
I've had the same issue.. try to delete the atmosphere and sept folder. Download a brand new folder from github.. place the atmosphere and sept folder on your sd card.

--------------------- MERGED ---------------------------

Just updated my atmosphere and added the new sigpatches. Now I get an error when booting. "Fatal error: (NXBOOT): Messing default patch for KIP 010000000...".
Any Ideas? :(


https://birbchirp.gitbook.io/switchguide/cfw-guides/atmosphere/atmosphere-installation
 
are you in airplane mode? you will need to enable the wireless controller option in the full airplane mode in setting.
that was something that got me at the start.
No I am not
And I did that before still the same
 
I have a cheaper version of a switch controller. Mine worked like this;

1.) Put switch into the dock
2.) Put your C-cable in your dock and connect it to your controller.
3.) Hit the on button for like 4 seconds to turn on your controller.
4.) Let it synchronize with your switch. It may be necessary to repeat turning on the controller.
5.) It will connect on some point. If this turned out not to be the case look at step 6.)
6.) This works for me sometimes; if you are removing your joycons while your switch is on, (leave them in the rail. Don't remove it from the whole console.) A screen will appear that asks you on how you wish to play on your switch and hit L/R Button. Try to turn on your pro controller.

This always works for me when my controller is acting retarted.
I will try the half joycon thing
But the method above does'nt work for me
As soon as I detach the controller wire it never synced, and a question mark appears on the controller Icon
 
I will try the half joycon thing
But the method above does'nt work for me
As soon as I detach the controller wire it never synced, and a question mark appears on the controller Icon

Hmmm.. sounds like a software problem I guess.. I'm not a pro in this kind of things, since I'm still learning this all myself.. I never had a question mark appearing on my screen.. I'll do some research for you and be back to you in a while.. give me 1+- hour

--------------------- MERGED ---------------------------

I will try the half joycon thing
But the method above does'nt work for me
As soon as I detach the controller wire it never synced, and a question mark appears on the controller Icon
There is a sync button on your pro controller.. did you tried that yet?

Oherwise there is an app that makes it possible to connect more bluetooth controllers to the switch.. maybe try that as well? Its called something with mission... try to look it up in the store.
 
Last edited by Ichigo-Bankai,
What are the side effects of these patches? I heard from somewhere that sigpatches could have a lot of downsides to them.
 
What are the side effects of these patches? I heard from somewhere that sigpatches could have a lot of downsides to them.

The side effects are that it makes your switch work properly with the latest Atmosphere custom rom. Exactly what downsides are you referring to? If you are running a hacked switch then these sigpatches are necessary.
 
Hmmm.. sounds like a software problem I guess.. I'm not a pro in this kind of things, since I'm still learning this all myself.. I never had a question mark appearing on my screen.. I'll do some research for you and be back to you in a while.. give me 1+- hour

--------------------- MERGED ---------------------------


There is a sync button on your pro controller.. did you tried that yet?

Oherwise there is an app that makes it possible to connect more bluetooth controllers to the switch.. maybe try that as well? Its called something with mission... try to look it up in the store.

Thanks, well yup I did the sync button the first thing, No luck. The thing is joycons support wireless connection pretty well
This is really frustrating, I hate not knowing what's happening

--------------------- MERGED ---------------------------

What are the side effects of these patches? I heard from somewhere that sigpatches could have a lot of downsides to them.
The atmosphere itself, is a white hacker thing. You can't install pirated games etc. On your hacked switch unless you use these sigpatches.
For normal users I don't see any logical reason to hack their switches but not patching em up.
And I didn't hear any particular downside myself. But hacking always have downsides starting with not being able to go online at least in a riskless way and other stuffs some may risk the functionality of the console itself.
 
Last edited by Hossein,
Thanks, well yup I did the sync button the first thing, No luck. The thing is joycons support wireless connection pretty well
This is really frustrating, I hate not knowing what's happening

--------------------- MERGED ---------------------------


The atmosphere itself, is a white hacker thing. You can't install pirated games etc. On your hacked switch unless you use these sigpatches.
For normal users I don't see any logical reason to hack their switches but not patching em up.
And I didn't hear any particular downside myself. But hacking always have downsides starting with not being able to go online at least in a riskless way and other stuffs some may risk the functionality of the console itself.

Try to disconnect the joy cons completely and follow the steps again.. if nothing is working, pm me.
 
ok my system crashed with cling wrap enabled. now I can't load any of my forwarders or install any. is this line still needed?
kip1=atmosphere/kips/ams_mitm.kip
 
Delete your atmosphere, sept and bootloader folders. Download everything fresh from github, don't use anything you have on your computer right now.

I recommend to use this guide as reference (this one covers sigpatches as well unlike other guides): https://birbchirp.gitbook.io/switchguide/cfw-guides/atmosphere/atmosphere-installation


Hey Tokiwa,

Is there a way to auto boot into Fusee-Primary?
I can only choose between CFW sysMMC, CFW emuMMC stock and Fusee..

Any reply will be appreciated :)
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum