****************************************************************************************
@mrdude is working on new set of programs running in Windows and will not need Python at all, keep an eye on his thread, the first test is one to generate Atmosphère loader patches, KUDOS MrDude!!!!!
The program is available on post #237 of the IPS's Patches thread: https://gbatemp.net/threads/info-on-sha-256-hashes-on-fs-patches.581550/post-9898161
****************************************************************************************
Hello there, with all the fuss created by the DCMA plea of the N to iTotalJustice, I think this little compendium will help somebody.
This steps help you to build a new version of sigpatches if new firmware or Atmosphère is released or if you compile Atmosphère from source and make changes like add a new bootlogo @binkinator explain us how to do that on https://gbatemp.net/threads/custom-boot-logo-for-switch.569031/post-9839714
First at all thank you very much to @mrdude for his hard work, really to him belong all the credit.
On the thread Info on SHA-256 hashes on FS patches mrdude explain how the patches are created and share with all of us his work and his scripts to create new sigpatches.
For that scripts works you need Python, first step get python:
After you have a Python environment working, open a command line (CMD.EXE) and execute the next commands, in order to get the prerequisites of the scripts:
Download the latest version of the scripts on the thread (https://gbatemp.net/threads/info-on-sha-256-hashes-on-fs-patches.581550/post-9783677) for now they are on the post # 205.
Uncompress the file «
Then copy your prod.keys file to the folder «
Tip from @User154 , you can get your prod.keys files using the guide: https://nh-server.github.io/switch-guide/user_guide/emummc/making_emummc/
Get the files for the firmware you want to create, darthsternie it's you pal, or you can use NXDumpTool, TegraExplorer or GoldLeaf to dump the current firmware to the SD Card on your console. Extract all files to a local path, by example, «C:\FW1412», your folder must look like:
Download the latest Atmosphère files from https://github.com/Atmosphere-NX/Atmosphere/releases , and extract «atmosphere\package3» to a local path, by example: «C:\ATM132».
On a command line go to the folder where you extract AutoIPS and execute the command «Python MENU.PY»:
I recommend to select the option «7» in order to enable information on screen.
Then you can select the option «1» to generate sigpatches for Atmosphère, when asked for the «
You can use the option «2» to generate sigpatches for the firmware, when asked for the firmware path, use the one where you extract firmware files, on this example: «C:\FW1412».
Tip from @masagrator, also you can drag from a File Explorer window the folder of firmware and the package3 file to the command line window, then the full path is written for you on the command line, avoiding typos.
For Windows 10 and Windows 11 this ONLY works if you start the CMD as normal user, if your CMD.EXE was started as Administrator, do not work because explorer ALWAYS run as standard user and a standard user window can not send data to a Administrator one.
Tip from @subcon959 : if you put package3 in the scripts folder and then put the firmware files in a folder called firmware and put that in the scripts folder too, then you can just press enter when the menu asks for them instead of dragging or typing anything.
TESTED AND WORKS LIKE A CHARM!
The next examples shows the result of the executions:
If everything goes well you end with the folder «c:\AutoIPS\scripts\output» inside that folder should be a folder named «Atmosphere» that folder should be copied to the root of your SD card; and a file called «patches.ini» which goes to the «SD:/BOOTLOADER» path of your SD Card.
Its possible to see a bunch of Warnings «[WARN]» about to match key, some like:
are WARNINGS and you need no to worry about that, it's just you have more keys on the Keys.dat file than needed so ignore them.
If you get errors, verify the location of the «KEYS.DAT» file and the path you give for the Atmosphère files and firmware folder. DO NOT ADD EMPTY SPACES AT END OF THE PATHS.
-Edit 1:-
Correcting a typo and adding suggestions from other users; the great of this community!
And trying to be sure the credit goes to @mrdude him is the one what make the hard work and investigation.
-Edit 2-
add a video of dragging names and UAC restriction. and the good news from MrDude.
@mrdude is working on new set of programs running in Windows and will not need Python at all, keep an eye on his thread, the first test is one to generate Atmosphère loader patches, KUDOS MrDude!!!!!
The program is available on post #237 of the IPS's Patches thread: https://gbatemp.net/threads/info-on-sha-256-hashes-on-fs-patches.581550/post-9898161
****************************************************************************************
Hello there, with all the fuss created by the DCMA plea of the N to iTotalJustice, I think this little compendium will help somebody.
For now the sigpatches for all firmware up to 14.1.2 and Atmosphère 1.03.2 still can be downloaded from Sigpatches for Atmosphere (Hekate, fss0, fusee & package3) thread here on GBATemp 
This steps help you to build a new version of sigpatches if new firmware or Atmosphère is released or if you compile Atmosphère from source and make changes like add a new bootlogo @binkinator explain us how to do that on https://gbatemp.net/threads/custom-boot-logo-for-switch.569031/post-9839714
First at all thank you very much to @mrdude for his hard work, really to him belong all the credit.
On the thread Info on SHA-256 hashes on FS patches mrdude explain how the patches are created and share with all of us his work and his scripts to create new sigpatches.
For that scripts works you need Python, first step get python:
Download and install Python, for Windows you can use https://www.python.org/downloads/, but be sure of select the option «Add Python 3.XX to PATH».
After you have a Python environment working, open a command line (CMD.EXE) and execute the next commands, in order to get the prerequisites of the scripts:
Code:
python.exe -m pip install --upgrade pip
pip install bitstringDownload the latest version of the scripts on the thread (https://gbatemp.net/threads/info-on-sha-256-hashes-on-fs-patches.581550/post-9783677) for now they are on the post # 205.
Uncompress the file «
AutoIPS-Patcher.zip» on a local folder, for example, «C:\AUTOIPS», must look like:Then copy your prod.keys file to the folder «
c:\AutoIPS\scripts\» and rename it «keys.dat» IMPORTANT IF YOU USE EXPLORER BE SURE THE EXTENSIONS AREN'T HIDDEN, SO YOU DON'T END WITH keys.dat.keys file instead o keys.datTip from @User154 , you can get your prod.keys files using the guide: https://nh-server.github.io/switch-guide/user_guide/emummc/making_emummc/
Get the files for the firmware you want to create, darthsternie it's you pal, or you can use NXDumpTool, TegraExplorer or GoldLeaf to dump the current firmware to the SD Card on your console. Extract all files to a local path, by example, «C:\FW1412», your folder must look like:
Download the latest Atmosphère files from https://github.com/Atmosphere-NX/Atmosphere/releases , and extract «atmosphere\package3» to a local path, by example: «C:\ATM132».
On a command line go to the folder where you extract AutoIPS and execute the command «Python MENU.PY»:
Bash:
C:\AutoIPS>python menu.py
=========================================================================
Make sure you have keys.dat in the scripts folder. Menu/Scripts by MrDude
=========================================================================
1.Make Atmosphere-NX Loader Patch
2.Make ES Patch and FS Patches
3.Make ES Patch
4.Make Alt Beta ES Patch
5.Make ES NFIM Patch
6.Make FS Patches
7.Toggle Debug info
8.NCA info
9.Exit/Quit
What would you like to do?I recommend to select the option «7» in order to enable information on screen.
Then you can select the option «1» to generate sigpatches for Atmosphère, when asked for the «
fusee-secondary.bin or package3» files, write down the path where Atmosphère was extracted, on this example: «c:\ATM132\package3».You can use the option «2» to generate sigpatches for the firmware, when asked for the firmware path, use the one where you extract firmware files, on this example: «C:\FW1412».
Tip from @masagrator, also you can drag from a File Explorer window the folder of firmware and the package3 file to the command line window, then the full path is written for you on the command line, avoiding typos.
For Windows 10 and Windows 11 this ONLY works if you start the CMD as normal user, if your CMD.EXE was started as Administrator, do not work because explorer ALWAYS run as standard user and a standard user window can not send data to a Administrator one.
Tip from @subcon959 : if you put package3 in the scripts folder and then put the firmware files in a folder called firmware and put that in the scripts folder too, then you can just press enter when the menu asks for them instead of dragging or typing anything.
The next examples shows the result of the executions:
If everything goes well you end with the folder «c:\AutoIPS\scripts\output» inside that folder should be a folder named «Atmosphere» that folder should be copied to the root of your SD card; and a file called «patches.ini» which goes to the «SD:/BOOTLOADER» path of your SD Card.
Its possible to see a bunch of Warnings «[WARN]» about to match key, some like:
are WARNINGS and you need no to worry about that, it's just you have more keys on the Keys.dat file than needed so ignore them.
If you get errors, verify the location of the «KEYS.DAT» file and the path you give for the Atmosphère files and firmware folder. DO NOT ADD EMPTY SPACES AT END OF THE PATHS.
-Edit 1:-
Correcting a typo and adding suggestions from other users; the great of this community!
And trying to be sure the credit goes to @mrdude him is the one what make the hard work and investigation.
-Edit 2-
add a video of dragging names and UAC restriction. and the good news from MrDude.
Last edited by impeeza,
