Even if you have the files in the right place that doesn't mean they didn't get corrupted during download/transfer. Download fresh ones and try again.Alright I'll post a screenshot aswell
Even if you have the files in the right place that doesn't mean they didn't get corrupted during download/transfer. Download fresh ones and try again.Alright I'll post a screenshot aswell
Yeah, I went back and checked the guide and saw that. I edited my post already.No, it's not, it's only used when installing boot9strap itself or when using boot9strap to dump the bootroms/OTP. It's not needed for normal usage after install.
Is it fine to remove the boot9strap folder and it's contents after installing? Or are those necessary files?
I ask because there was no list of required folders in the updating from a9lh to sighax part of the guide.
They are different implementations of the same thing. I wouldn't recommend switching to base sighax because of the high brick chance just stay with b9s.How can I go from B9S to Sighax
Yes, but nightly builds are currently broken. Stable should be ok.Is it possible to update luma with luma updater after installiert boot9strap?
You have to use the updated luma installerIs it possible to update luma with luma updater after installiert boot9strap?
You have to use the updated luma installer
yes v2.0 is the new oneso i have to install a new luma updater cia ?
That's pretty much the gist of it. This is a much cleaner environment for developers, and additionally allows any user to dump Boot9 and their OTP on any version (allowing for title decryption on a PC and the death of xorpads). Additionally, boot9strap is installable on any version with just a hardmod (or dsiware).If I understand the slides from SciresM correctly, sighax is an exploit in the boot9 checksum parser that lets people bypass the signature check at booting stage. Any firmware with sighax will bypass the check and thus be loaded successfully. B9S utilizes sighax to make its firmware "valid", and that firmware uses NDMA exploit to run some code that then loads an payload (like CFWs). The payload should have bootrom privilege right? How does it benefit CFWs from a player's view?