How to create your own sigpatches.

****************************************************************************************
:switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch:
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 and Atmosphère can be downloaded from Sigpatches for Atmosphere (Hekate, fss0, fusee & package3) thread here on GBATemp :D

@mrdude is working on new set of programs running in Windows and will not need Python at all, keep an eye on his thread.
And @dogcsty is working on a Homebrew capable of generate the sigpatches on the console directly.
Booth applications are getting almost end-user maturity.

@mrdude release the Sigpatch IPS Creator New store, allowing to generate any new patches for any firmware and Atmosphère without need of updating the software.

For using the new Sigpatch IPS Creator you need:

  1. Download the latest version from github.
    Now is on:
    New version on downloads section
  2. Right click the recent downloaded file, and select properties:
    1661373682261.png
    , then unblock the file:
    1661373835973.png
    , this is a «security» measure of windows, marking down the downloaded files as insecure even if they are safe.
  3. Extract the file to a folder on your hard drive, by example c:\IPSCreator
    1662496908803.png
  1. At the first run of "IPS_Patch_Creator.exe " you may get a warning:
    1661374018518.png
    because is a «unrecognized app» meaning MrDude has not payed thousands of dollars to Microsoft for «authenticate» the app, so you should press «Run anyway» button to run the program. If you don't trust you can use a real antivirus (no defender) and check the file.
  2. At the first start of the program, you are welcomed with a few configurations:
    1661374242114.png
    By now you can choose the defaults and press «Save» button.
    This configurations are for future firmwares, more explanation on the post by MrDude. After press «Save» you are asked to save the config
    1661374387434.png
    press yes to commit the config to disk.
  1. The program require you to provide the encryption set of keys for the console. There are several ways to get them:
    1. using Lockpick_RCM, follow the guide:https://gbatemp.net/threads/how-to-get-switch-keys-for-hactool-xci-decrypting.506978/ OR https://nh-server.github.io/switch-guide/user_guide/emummc/making_emummc/
    2. Inside the program on the «Help» -> «Online Information», there are a set of cypher URLs one of them is very useful.
    3. Using web search.
    4. The versions 1.5.8 or newer are capable of generate the Needed keys from a folder containing the most recent firmware, for that se the step 3.
  2. When you run the program without the needed keys, it prompts:
    1661377417544.png
    , if you press "yes" a KEYS.DAT file is created for you on the tools sub-folder, you can edit the file and put the values or use the KeyData tab to write the values of your PROD.KEYS file:
    1661377600726.png
  3. if you like the program can generate the needed keys, you need to provide a folder with the most recent firmware files, first go to KeyData Tabulator and press the «KeyGen» button, you are asked for a folder with the firmware files.
    1719709460505.png
You can use the tabs «Loader», «ES», «ES2», «FS» and «NFIM» to create the patches.
On each tab there is a button named «Make Patch», you can use the button to browse for the needed files or folder, also you can drag and drop to that button the files or folder from an explorer window.
On each you can generate a different set of patches:

Loader
On this tab you can generate the patches set for Atmosphère.
Loader Patch are Required for:
  • Running NRO Forwarders and Installed homebrews.
  • Running Installed XCI games.

Loader patch not required to:
  • Run (some) previously installed NSP. (if valid tickets exist)
  • Run non installed homebrew.
  • Install NSP/XCI - (but will not run these if a valid ticket does not exist).
In order to create the patches, you need to provide the path to fusee-secondary.bin or package3 file. Could be an official one or compiled by yourself.
Only Atmosphère 0.8.5 and newer are supported.
1662498674563.png

The generated patches are on the folder \atmosphere\kip_patches\loader_patches and the file \bootloader\patches.ini relative to the folder where IPS Patch Creator is run.

ES & ES2
ES patches stand for Eticket Services.
ES Patches are required to:
  • These are needed for run and install raw and untouched NSP files either dumped from Nintendo's CDN or someone's console.
  • ES patches are additionally needed to run pirated commercial NSPs.
ES Patches are NOT required to:
  • Run installed XCI
  • Run installed NRO forwarders.
  • Run homebrew
  • Install XCI files.
For creating the patches, you need to provide the path to the folder with the files of a firmware for console.
Works only for firmware 9.0.1 and above.

Both tabs generate the same sigpatches, using different algorithms, ES uses an algorithm what patches only on a spot, is traditionally know as «Alternate».
ES2 uses the original algorithm which patches on three different spots. Both of them works the same and is up to you which one to use, is more a manner of preference because they are equivalent.
1662500122439.png

The sigpatches are generated on the sub-folder \atmosphere\exefs_patches\es_patches\ where the IPS Patch Creator is run.

FS
FS is short for fs_nosigchk.
FS Patches required to:
  • Run installed XCI/NRO forwarders, and will give a corruption error when trying to run the installed XCI or NRO forwarder if no fs patches are applied or are wrong (you will also need to reinstall the game or nro forwarder if this happens).
  • The FS patches allow the usage of converted NSP files, such as homebrew on NSP files or converted XCI files.
  • FS patches are required to install/run NSP and XCI (without needing to convert the header) files.
Fs Patches not required to:
  • Run installed NSP files with valid tickets.
  • Run Homebrew
  • Install NSP/XCI - (with a valid header)
Only firmware 9.0.1 and above is supported.
1662500405307.png

The generated IPS files are on the sub-folder \atmosphere\kip_patches\fs_patches and the file \bootloader\patches.ini

NFIM
The NFIM patches, know as nfim_ctest, where «ctest» is short for Connection Test, are patches for skip the internet connection test, So you can play on a LAN without being online.
All current firmware versions are supported.
1662500667281.png

The patches are generated on the sub-folder \atmosphere\exefs_patches\nfim_ctest\

Once all the patches you want are generated, you can copy the folders atmosphere and bootloader to the root of your SD Card.

A very helpful feature is the possibility of upload the patches to your console using FTP, before you can use, you need to config the connection data:
1661379908766.png
,
1661379931932.png
,
1661379974097.png
once you put the correct IP address of your console and the user/password to connect you can push "save".

Then use the ftp feature to send the patches:
1662500827396.png
.



If you like to generate the patches directly on the console, @dogcsty is working on a Homebrew for that.

----To Do: add steps for the Homebrew ----


:switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch::switch:
****************************************************************************************

With these new applications the use of the Old Python scripts is deprecated and useful only for historians :D

If you really want run the scripts you can use the
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».
1659196452425.png

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 bitstring

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 «AutoIPS-Patcher.zip» on a local folder, for example, «C:\AUTOIPS», must look like:
1659196724938.png


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 of keys.dat

Tip from @User154 ,
you can get your prod.keys files using Lockpick_RCM, follow 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:
1659197200014.png

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.
record_1.png

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.
W09lAnk.jpg
TESTED AND WORKS LIKE A CHARM!


The next examples shows the result of the executions:
1659197808475.png



1659197914104.png


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:
1659317316418.png

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.

-Edit 3-
Adding new homebrew app.

-Edit 4-
Creating steps for the new App., To do: steps for console homebrew.

-Edit 5-
New download URL and KeyData Generation.
 

Attachments

  • 1661377712209.png
    1661377712209.png
    36.2 KB · Views: 237
  • 1661380064400.png
    1661380064400.png
    27 KB · Views: 228
  • 1661380748979.png
    1661380748979.png
    12.6 KB · Views: 243
  • Sigpatch-IPS-Creator_1.5.7_Yandex.png
    Sigpatch-IPS-Creator_1.5.7_Yandex.png
    3.3 KB · Views: 48
Last edited by impeeza,

taffyponty

Well-Known Member
Newcomer
Joined
Jul 15, 2023
Messages
65
Trophies
0
Age
38
XP
114
Country
Germany
"In order to create the patches, you need to provide the path to fusee-secondary.bin or package3 file. Could be an official one or compiled by yourself.
Only Atmosphère 0.8.5 and newer are supported."

I'm lost on this step. I have no fusee-secondary.bin.
so I don't know how I proceed with creating the patches?
 

impeeza

¡Kabito!
OP
Member
Joined
Apr 5, 2011
Messages
7,594
Trophies
4
Age
46
Location
At my chair.
XP
25,171
Country
Colombia
"In order to create the patches, you need to provide the path to fusee-secondary.bin or package3 file. Could be an official one or compiled by yourself.
Only Atmosphère 0.8.5 and newer are supported."

I'm lost on this step. I have no fusee-secondary.bin.
so I don't know how I proceed with creating the patches?
fuse-secondary.bin was renamed PACKAGE3 since atmosphère 1.0.0 release that's the why there is a "or" on :

fusee-secondary.bin or package3 file

happy making of patches.
 
  • Like
Reactions: 4d1xlaan

rave420

Well-Known Member
Member
Joined
Dec 21, 2010
Messages
278
Trophies
1
XP
220
Country
Canada
I admit I have little idea what I am doing, but was able to successfully create a set of patches for HOS FW 17 with my own keys (I usually download the patches from "that" site). If someone can humor me, what does "IPS" and "KIP" stand for? Is this still relevant for the latest version of Atmosphere? One of the commits over on github mentions removing the "Parsing of IPS patches", and I don't fully understand the matter at hand.

Reason I am asking for some clarification, I would hate to update my setup to the latest HOS & Atmosphere, and have all of my cartridge installs stop working and having to re-dump them (some 60 cards, 2 full days of work). Not even sure if this is the right thread to ask. Do I even need the patches made by this program if I am also using sys-patch?
 

petspeed

Well-Known Member
Member
Joined
Nov 13, 2009
Messages
1,203
Trophies
1
Age
50
XP
2,055
Country
Denmark
I admit I have little idea what I am doing, but was able to successfully create a set of patches for HOS FW 17 with my own keys (I usually download the patches from "that" site). If someone can humor me, what does "IPS" and "KIP" stand for? Is this still relevant for the latest version of Atmosphere? One of the commits over on github mentions removing the "Parsing of IPS patches", and I don't fully understand the matter at hand.

Reason I am asking for some clarification, I would hate to update my setup to the latest HOS & Atmosphere, and have all of my cartridge installs stop working and having to re-dump them (some 60 cards, 2 full days of work). Not even sure if this is the right thread to ask. Do I even need the patches made by this program if I am also using sys-patch?
You don't need sigpatches if you use sys-patch but it doesn't Hurt to have both
If you play your games directly from gamecarts you don't need patches at all
 
  • Like
Reactions: impeeza

RedColoredStars

Well-Known Member
Member
Joined
Aug 14, 2022
Messages
1,508
Trophies
2
Location
Angoche
XP
2,019
Country
Mozambique
So I gave this a shot and the folders only contain 1 or two ips files each and the patches.ini only includes the info for FW 18. Is that all that is actually needed if a person is on the latest FW are aren't going to be downgrading? I ask because the sigpatch packs that can be downloaded here and elsewhere all contain far more files and an ini file for all FWs.
 

impeeza

¡Kabito!
OP
Member
Joined
Apr 5, 2011
Messages
7,594
Trophies
4
Age
46
Location
At my chair.
XP
25,171
Country
Colombia
So I gave this a shot and the folders only contain 1 or two ips files each and the patches.ini only includes the info for FW 18. Is that all that is actually needed if a person is on the latest FW are aren't going to be downgrading? I ask because the sigpatch packs that can be downloaded here and elsewhere all contain far more files and an ini file for all FWs.
The program create on each run the patches for that PACKAGE3/Firmware folder you selected, if you like the ones for ALL firmwares you need to execute the process for each and all the firmwares, some of us already did that and are on the OP.
 

RedColoredStars

Well-Known Member
Member
Joined
Aug 14, 2022
Messages
1,508
Trophies
2
Location
Angoche
XP
2,019
Country
Mozambique
The program create on each run the patches for that PACKAGE3/Firmware folder you selected, if you like the ones for ALL firmwares you need to execute the process for each and all the firmwares, some of us already did that and are on the OP.

Thanks for the reply. What I'm more asking is, is it necessary to have all? Or only the ones for the FW a person is on?
 

impeeza

¡Kabito!
OP
Member
Joined
Apr 5, 2011
Messages
7,594
Trophies
4
Age
46
Location
At my chair.
XP
25,171
Country
Colombia
Thanks for the reply. What I'm more asking is, is it necessary to have all? Or only the ones for the FW a person is on?
you only need the patches for the current Firmware and the current Atmosphère, the ones on Sigpatches thread have all because not everyone is on the same firmware/Atmosphère :D
 
  • Like
Reactions: RedColoredStars

Mars04

Member
Newcomer
Joined
Apr 22, 2024
Messages
9
Trophies
0
XP
63
Country
South Africa
Hi, I just tried for the first time myself to make sigpatches and followed you guide.(Thanks for that) But by generating the patches in the app(V1.5.7), I each time get the error "unable to decrypt, did you update your keys" and "try adjusting the XX size limits in config settings if firmware is greater then 15.0.0"... Only the loader patch I could generate without issues.

So first I copied all requested data from my prod.keys file to Keydata template. My own prod.keys file (generated with lockpick.rcm) didn't contain the package1_key files, so I filled that one on with the package1_key file data that I found online(3 cats).

So I really have no clue what I had to do different. Is it the size limits issue? And if so, how large must I set the limits? As I tried that by one patch and then results also came back as not working.

I copied the data values over one line by one line. I used packag3 file to make loader patch and I used the FW 18.0.1 files to try to make the other patches.

I also tried with older firmware 17.0.0 and 18.0.0, but same result.

Thanks in advance
 

Attachments

  • ES_error.JPG
    ES_error.JPG
    119 KB · Views: 16
  • NFIM_error.JPG
    NFIM_error.JPG
    118.7 KB · Views: 16
  • FS_error_part2.JPG
    FS_error_part2.JPG
    131.7 KB · Views: 16
  • FS_error_part1.JPG
    FS_error_part1.JPG
    129 KB · Views: 14
  • ES2_error.JPG
    ES2_error.JPG
    118.4 KB · Views: 18
Last edited by Mars04,

impeeza

¡Kabito!
OP
Member
Joined
Apr 5, 2011
Messages
7,594
Trophies
4
Age
46
Location
At my chair.
XP
25,171
Country
Colombia
Hi, I just tried for the first time myself to make sigpatches and followed you guide.(Thanks for that) But by generating the patches in the app(V1.5.7), I each time get the error "unable to decrypt, did you update your keys" and "try adjusting the XX size limits in config settings if firmware is greater then 15.0.0"... Only the loader patch I could generate without issues.

So first I copied all requested data from my prod.keys file to Keydata template. My own prod.keys file (generated with lockpick.rcm) didn't contain the package1_key files, so I filled that one on with the package1_key file data that I found online(3 cats).

So I really have no clue what I had to do different. Is it the size limits issue? And if so, how large must I set the limits? As I tried that by one patch and then results also came back as not working.

I copied the data values over one line by one line. I used packag3 file to make loader patch and I used the FW 18.0.1 files to try to make the other patches.

I also tried with older firmware 17.0.0 and 18.0.0, but same result.

Thanks in advance
You need latest version of software, please get it from:

https://gbatemp.net/threads/autoips-sig-patcher.574126/post-10391613
Post automatically merged:

and do not forget the LATEST keys.
 

Mars04

Member
Newcomer
Joined
Apr 22, 2024
Messages
9
Trophies
0
XP
63
Country
South Africa
You need latest version of software, please get it from:

https://gbatemp.net/threads/autoips-sig-patcher.574126/post-10391613
Post automatically merged:

and do not forget the LATEST keys.
Hi,

I did use the latest version of software (v1.5.7) as described above. I also did used my latest keys which I got from lockpick 3 days ago on my switch...

I just fill in only the template details, right? So not entire prod.keys file? And the default nca sizes stay default, right?

And do I add the package 1 details from another prod.keys if it wasn't in my personal device file? Or do I leave that out?

And I do fill in by keydata where the template is, the description lines with the values right? Not only the values number/letter strings and deleting description line?

And I don't know if it matters but I have a Mariko V2, with picofly modchip.

I really tried all combinations yesterday, even tried with older firmwares, nothing worked. I really don't get it😞
Post automatically merged:

Hi,

I did use the latest version of software (v1.5.7) as described above. I also did used my latest keys which I got from lockpick 3 days ago on my switch...

I just fill in only the template details, right? So not entire prod.keys file? And the default nca sizes stay default, right?

And do I add the package 1 details from another prod.keys if it wasn't in my personal device file? Or do I leave that out?

And I do fill in by keydata where the template is, the description lines with the values right? Not only the values number/letter strings and deleting description line?

And I don't know if it matters but I have a Mariko V2, with picofly modchip.

I really tried all combinations yesterday, even tried with older firmwares, nothing worked. I really don't get it😞
I got it finally working. I wasn't aware I also needed the latest lockpick.rcm, which gave me then another prod.keys file with 4 extra lines needed.(key_area_key_application_10,11 and package2_key_10 and 11)

I have just one question left. I tried making sigpatches one time with the package1_key00-05 lines(copied them from 3cats) included in my KeyData and one time without the package1 lines included. Both seem to have generated working patches...

But which should be the most trustworthy?

Thanks for all help and pointing me in the right direction:)
 
Last edited by Mars04,

Dimensio

Well-Known Member
Newcomer
Joined
Aug 28, 2009
Messages
71
Trophies
1
XP
306
Country
United States
Does this still work with 18.1.0? I tried it last night and while loader, ES and NFIM all worked, FS failed with

Unable to decrypt the FS files​
It's possible that you need to update keys.dat with the latest key to decrypt the files, or you may need to adjust the FS NCA settings in the config page.​

Using 1.5.7 and the most recent lockpick rcm that I could find.
 

impeeza

¡Kabito!
OP
Member
Joined
Apr 5, 2011
Messages
7,594
Trophies
4
Age
46
Location
At my chair.
XP
25,171
Country
Colombia
Does this still work with 18.1.0? I tried it last night and while loader, ES and NFIM all worked, FS failed with

Unable to decrypt the FS files​
It's possible that you need to update keys.dat with the latest key to decrypt the files, or you may need to adjust the FS NCA settings in the config page.​

Using 1.5.7 and the most recent lockpick rcm that I could find.
Download the most recent from:

https://disk.yandex.com/d/LEKGKbfDw-_pjA

backup and remove all old files/folder of your Ips patch creator, extract the recently downloaded zip and copy the keys the new one have a new set of values on the wildcards database and NCA Sizes
 

Dimensio

Well-Known Member
Newcomer
Joined
Aug 28, 2009
Messages
71
Trophies
1
XP
306
Country
United States
Download the most recent from:

https://disk.yandex.com/d/LEKGKbfDw-_pjA

backup and remove all old files/folder of your Ips patch creator, extract the recently downloaded zip and copy the keys the new one have a new set of values on the wildcards database and NCA Sizes
That is the version that I used. I extracted it to a completely empty directory and used a newly generated prod.keys file from what I believe is the latest lockpick.rcm.
Post automatically merged:

Just tried it with firmware 18.0.0 (this is my first attempt at creating my own sigpatches) and got the same error, so this is apparently not an issue with the newest firmware.
 
Last edited by Dimensio,
  • Love
Reactions: impeeza

OLineGuy

Well-Known Member
Member
Joined
Jan 31, 2008
Messages
665
Trophies
1
XP
1,871
Country
United States
That is the version that I used. I extracted it to a completely empty directory and used a newly generated prod.keys file from what I believe is the latest lockpick.rcm.
Post automatically merged:

Just tried it with firmware 18.0.0 (this is my first attempt at creating my own sigpatches) and got the same error, so this is apparently not an issue with the newest firmware.
open ur prod keys in txt editor and what does it say the latest master key number is? should be 11 i believe
 

impeeza

¡Kabito!
OP
Member
Joined
Apr 5, 2011
Messages
7,594
Trophies
4
Age
46
Location
At my chair.
XP
25,171
Country
Colombia
Buddy, the only help I can think is: I just remade the process:
  1. from https://disk.yandex.com/d/LEKGKbfDw-_pjA I downloaded the file:
    1718203517023.png

  2. Then extracted that file to a NEW folder on my PC:
    1718203539719.png

  3. Executed the IPS_Patch_Creator.exe, the first time you are asked for confirm the size of the NCA Sizes
    1718203618297.png

  4. Click «Save», Then you are asked to «Update Config», click «YES»
    1718203678703.png

  5. Finally you are asked to create a template file, click «YES»
    1718203701742.png

  6. Go to «KeyData» Tab
    1718203723978.png

  7. Copy and paste the contents of your PROD.KEYS file on it, then press «Write Keys» button.
    1718203738322.png

  8. I Got a copy of the Firmware on Zip way, the Firmware 18.1.0 have the checksums:
    • SHA256: C81D47786A44C5A81B48EEE2E6E0BAEA4ECBE109712E15E02258C46F78A7BF5B *FIRMWARE.18.0.1.ZIP
    • MD5: f8b3c0b18f4c432d637715517f9a0889 *Firmware.18.0.1.zip
  9. Then I extracted the contents to a folder on my PC
    1718204073094.png

  10. Lastly using the button «Make Patch» create the set of patches you like
    1718203748053.png
  11. You can click the button and browse to the FW folder location or drag and drop the folder IN TO THE BUTTON.
  12. All steps worked for me just fine.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    SylverReZ @ SylverReZ: If you're too impatient with Echoes of Wisdom, use an emulator. :P +1