Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,746,733
  • Replies Replies 9,314
  • Likes Likes 92
SAK "Swiss Army Knife" lets you patch games to lower firmware. Was useful when SX was abandoned at FW 11. Most newer titles don't won't nowadays tho.
If you load a game file (nsp,xci) into NXFileviewer, it will tell you the FW version required based on the SDK kit used to build the game. Usually going from major FW (ex: 21 to 20) is impossible.
this is why i find gex base game to be 20.1.0 but the update has a master key of 18, usually the base game should also have a master key but doesn't show on the nfo file. maybe someone could run it through a file viewer and report their findings. just for fun
 
  • Like
Reactions: BigOnYa
I definitely didn't use SAK, but maybe the uploader did

If they did they didn't mention downgrading the FW requirement and the NSP passed all the checks on DBI (all green text while installing) so idk
 
Last edited by UsernamesAreWeird,
GEX Trilogy d'ont work on 19.0.0, i try it
I read that Limited Run asked Nintendo to pull Gex Trilogy from eshop as it doesnt work on Switch 2 until Nintendo fix the emulator.

Why not make PS1 Gex Series forwarder through DuckStation while Limited Run not work. I think DuckStation makes graphic smoother and 4k better than remastered. :D
 
  • Like
Reactions: THYPLEX
I wonder if DBI patches the game somehow to make it run on a lower firmware or something? I think I've seen other users mentioning it in the past but I'm not sure how to get the real info whether it's possible or not to run a certain game on a lower firmware. @duckbill007 I wonder if you can help us out?
yes It does, there is a setting to enable exactly that.
 
there's a few different firmware version "requirements"

the most basic one is the 'required system version' as specified in the content meta. for some reason the system saves required system version to the title database (or w/e) separately and the value in the content meta is never read again after the initial install. tinfoil has the setting to choose if you want to bypass that check or not, dbi always does it because there is no downside to doing it. all it does is write the lowest possible value to required system version in the title database when installing a nsp instead of using the version specified in the content meta, the actual game files are untouched and signatures are not broken so it works without fs or loader patches

next is the master key encryption, it's trivial to decrypt a nsp and re-encrypt to a lower master key if you want. it will break signatures and require fs and loader patches to run. converting to a lower master key is not necessary if you use fusée to boot because it directly generates all the latest firmware supported master keys or something instead of getting just the ones supported by the actual firmware version. if you use hekate then you have to decrypt and encrypt to a lower master key, with fusée the game will install and run fine even if the master key is higher than your firmware, as long as...

and last is the sdk version the game was built on, you are not bypassing this unless you can decompile the game back to source and port it to a lower sdk. a game on a slightly higher sdk might work on a slightly lower firmware, or it might not. it probably depends on if the game actually uses new functions that are not supported in older sdk, or if the new sdk functions are significantly rewritten compared to the old sdk, but you should probably just update your firmware version to at least match the sdk version to avoid problems
 
Thank you :) Much appreciated.

Ok so after messing about I seem to get stuck while making I get the error 2 and when i check the export my file locations slightly differ
If you use the command make -j sometimes you can get error 2 just run again the make command and everything will end fine
 
  • Like
Reactions: Blythe93
If you use the command make -j sometimes you can get error 2 just run again the make command and everything will end fine
Hey,

thank you for your reply I did try that too as I saw in the notes it could fail and I got a different error.. here is what I get when i use the make command only
 

Attachments

  • make command only.PNG
    make command only.PNG
    8 KB · Views: 25
This is the commit d8a37b4b7 from the official repo build with latest libraries, I am attaching the Fusee.bin and sigpatches for this build.
 

Attachments

Site & Scene News

Popular threads in this forum