do not udpate Rocket League he he heAccording to the nfo the latest update for Rocket League (v1.8.8 v5767168) requires 17.0.0
Not that it is a reason to update
do not udpate Rocket League he he heAccording to the nfo the latest update for Rocket League (v1.8.8 v5767168) requires 17.0.0
Not that it is a reason to update
According to the nfo the latest update for Rocket League (v1.8.8 v5767168) requires 17.0.0
Not that it is a reason to update
hello do you think you could help me with the error in nxdump tool error findkeyinprocessmemory: unable to locate key'headere_key_source in process memory thanksdo not udpate Rocket League he he he
do you have latest prod.keys file? you need PickLock 1.9.11 to generate it.hello do you think you could help me with the error in nxdump tool error findkeyinprocessmemory: unable to locate key'headere_key_source in process memory thanks
Yes I did all of that I generated the product keys and everything and no matter what I do I get that error that I showed you That says it couldn't find the process header keydo you have latest prod.keys file? you need PickLock 1.9.11 to generate it.
Just so you know it works fine on the cfW emunand but not on the system nand that I accidently updated to the 17.0 fwYes I did all of that I generated the product keys and everything and no matter what I do I get that error that I showed you That says it couldn't find the process header key
Yes notice that you said pick lock 1.9.11 where do I get that from I have pick lock 1.9.10Yes I did all of that I generated the product keys and everything and no matter what I do I get that error that I showed you That says it couldn't find the process header key
Post automatically merged:
Just so you know it works fine on the cfW emunand but not on the system nand that I accidently updated to the 17.0 fw
yeahI generated sigpatch and work,only fs patch not work
hey i found the picklock rcm 1.9.11 on a french website and an update to tegra explorer installed these ran picklock 1.9.11 the nxdump tool i was originally using no longer works but i found an updated version called nxdt_poc.nro which is 2.0 of nx dump tool and it works just fine thank you for all your help i am up and running for the most part now the only issues are when i need to use the cfw sysnand i need to put it in flight mode because the internet is crashing my system the program causing it is a system program called nim the id is 0100000000000025 but for now the work around is flight mode and i also need to uninstall my themes before going into cfw sysnand as there is no theme support right now hopefully these things will be fixed but at least i have functioning work arounds again thank you so much i will definiatly be more careful in the future and not just push buttonsYes I did all of that I generated the product keys and everything and no matter what I do I get that error that I showed you That says it couldn't find the process header key
Post automatically merged:
Just so you know it works fine on the cfW emunand but not on the system nand that I accidently updated to the 17.0 fw
Post automatically merged:
Yes notice that you said pick lock 1.9.11 where do I get that from I have pick lock 1.9.10
you didn't need to french sites here on gbatemp there is the official link to PickLock 1.9.11hey i found the picklock rcm 1.9.11 on a french website and an update to tegra explorer installed these ran picklock 1.9.11 the nxdump tool i was originally using no longer works but i found an updated version called nxdt_poc.nro which is 2.0 of nx dump tool and it works just fine thank you for all your help i am up and running for the most part now the only issues are when i need to use the cfw sysnand i need to put it in flight mode because the internet is crashing my system the program causing it is a system program called nim the id is 0100000000000025 but for now the work around is flight mode and i also need to uninstall my themes before going into cfw sysnand as there is no theme support right now hopefully these things will be fixed but at least i have functioning work arounds again thank you so much i will definiatly be more careful in the future and not just push buttons
Judging by the to-do list of Atmosphere, I’d say it added plenty….more on the under the hood stuff rather than anything useful. Enough to give SciresM a huge headache as well as other devs.Why? FW 17 brings nothing to the table.
I think that was the intention. It WAS a big update despite speculation to the contrary. The big updates were to under the hood kinda things rather than anything an end user would notice. From my understanding, they changed quite a bit how the Switch works.Relax, I was merely asking how long it takes on average for new sigpatches to be releases after an update. I wasn't asking with the intention of having these people hurry up or anything like that.
Good to know. I guess there are issues this time then. Wasn't aware this was such a big update. Goes to show that not everyone reads changelogs, I guess...
That’s what I do. Use EmuNAND for CFW and daily driver, stock nand to download updates, and SysNAND CFW simply to dump them. I never install anything onto SysNAND because at least if something messes up on EmuNAND, I can just make a new one. Can’t exactly do that with SysNAND. It’s a more involved process. Gives me peace of mind. Been doing that since the Wii days.By example some people still use a CFW for piracy and have a EmuNAND for it and have a EmuNAND for the best CFW Ever: Atmosphère, and kept their SysNAND on original FW. so you can setup Hekate to boot any of them and Atmosphère take cares of avoid burnt fuses or panic because burnt fuses count.
oh i didnt know that when i googled it the french one was the only one that came up and the nxdumptool link you posted that is the one i updated to thank you again so much for your helpyou didn't need to french sites here on gbatemp there is the official link to PickLock 1.9.11
Post automatically merged:
And latest release of NxDumpTool ( https://github.com/DarkMatterCore/nxdumptool/releases ) is FW 17 compatible.
https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10271469If I don't tell bullshit fs patch is now ready to do.
https://github.com/mrdude2478/IPS_Patch_Creator
The update of the soft was yesterday on GitHub, the post you mention was Wednesday.
Still the package isn't done. The ldr partition isn't patched yet. Even the dev (mrdude) say so.The update of the soft was yesterday on GitHub, the post you mention was Wednesday.
goodmorning at all,
i have found this: https://github.com/exelix11/dvr-patches/releases
but i don't know if it right..
This is a exefs patche use for contents sysdvr.It doesn't use for install or run game.goodmorning at all,
i have found this: https://github.com/exelix11/dvr-patches/releases
but i don't know if it right...
Firmware is made up from hundreds of compressed different files. The sigpatches look at the sha256 value of the unpacked file that we want patch, and then jump to the address (shown in the ips patch) in the decompressed file and then patch it with a new arm64 instruction.Can someone elaborate on what the difference is between these sigpatches. Why do different parts of the system need a different sigpatch?
In my understanding signed software uses a asymmetric cryptography validate the binaries.
So that would mean that different parts are signed with different private keys? And therefor we have to patch these different parts?