Homebrew SigHax Updates and Discussion Thread

  • Thread starter Thread starter adrifcastr
  • Start date Start date
  • Views Views 532,183
  • Replies Replies 3,813
  • Likes Likes 43
That's not exactly true, it only works if you accurately know which FIRM is in the FIRM0 partition, which means this wont be able to fix any bricks (unless you have an OTP backup + boot9, in that case you can extract the console unique keys and encrypt it properly)

You are right, I didn't think about bricked consoles. I edited my post accordingly.
For working consoles you can look up the installed FIRM version - and for "semi-working" consoles you could "brute-force" it.
 
Will it boot faster? Because with a9lh loads firm0 and firm1 and sighax will potentially boot only firm0.
 
That's what I meant! I can see how it will improve some things, but can't see how it could be better in some way to the user who already use A9LH. It will be the best for a new install, I'm sure, but don't think it'll be just like A9LH was to menuhax.

There isn't much point to upgrading a9lh to sighax. The biggest advantage other than ease of installation is the smaller footprint in nand. We could replace arm9loader with a custom sighax arm9loader that does what arm9loaderhax does, without the now redundant usage of two whole firms, one of which decrypts to garbage. We could reuse those firms for their intended use. Just with patches ;)
 
I just hope that sighax will be completed before the 11.4.0-37 update of destruction. And there's gonna be a reason why that update is called the "11.4 Update of Destruction".

11.4 will implement FIRM0 and FIRM1 integrity checks. It will scan for extra payload files in FIRM0 and FIRM1, as well as checking their MD5 hash with the files. If either the extra files is returned with a true value, or the MD5 hash check is returned with a false value, it will deny ARM11 from booting. So the only way to get passed this, is for sighax to be installed and for Luma3DS to disable the FIRM0 and FIRM1 integrity checks upon boot (which will only be possible if Luma3DS is installed with sighax). So in other words, if you have arm9loaderhax installed, you're screwed if you update to that firmware. Not to also mention, 11.4 update of destruction will patch soundhax as well.
 
Last edited by Platinum Lucario,
I just hope that sighax will be completed before the 11.4.0-37 update of destruction. And there's gonna be a reason why that update is called the "11.4 Update of Destruction".

11.4 will implement FIRM0 and FIRM1 integrity checks. It will scan for extra payload files in FIRM0 and FIRM1, as well as checking their MD5 hash with the files. If either the extra files is returned with a true value, or the MD5 hash check is returned with a false value, it will deny ARM11 from booting. So the only way to get passed this, is for sighax to be installed and for Luma3DS to disable the FIRM0 and FIRM1 integrity checks upon boot (which will only be possible if Luma3DS is installed with sighax). So in other words, if you have arm9loaderhax installed, you're screwed if you update to that firmware. Not to also mention, 11.4 update of destruction will patch soundhax as well.

Lmao at your futuristic conspiracy, soundhax - you mean primary exploits for HB?
 
I just hope that sighax will be completed before the 11.4.0-37 update of destruction. And there's gonna be a reason why that update is called the "11.4 Update of Destruction".

11.4 will implement FIRM0 and FIRM1 integrity checks. It will scan for extra payload files in FIRM0 and FIRM1, as well as checking their MD5 hash with the files. If either the extra files is returned with a true value, or the MD5 hash check is returned with a false value, it will deny ARM11 from booting. So the only way to get passed this, is for sighax to be installed and for Luma3DS to disable the FIRM0 and FIRM1 integrity checks upon boot (which will only be possible if Luma3DS is installed with sighax). So in other words, if you have arm9loaderhax installed, you're screwed if you update to that firmware. Not to also mention, 11.4 update of destruction will patch soundhax as well.
I recall seeing a response to this in one of the other threads:
It doesn't work like that. The a9lh payload runs before the firmware (and yes, that includes the arm9 kernel) even boots. Thus any such checks can simply be patched out.
 
I just hope that sighax will be completed before the 11.4.0-37 update of destruction. And there's gonna be a reason why that update is called the "11.4 Update of Destruction".

11.4 will implement FIRM0 and FIRM1 integrity checks. It will scan for extra payload files in FIRM0 and FIRM1, as well as checking their MD5 hash with the files. If either the extra files is returned with a true value, or the MD5 hash check is returned with a false value, it will deny ARM11 from booting. So the only way to get passed this, is for sighax to be installed and for Luma3DS to disable the FIRM0 and FIRM1 integrity checks upon boot (which will only be possible if Luma3DS is installed with sighax). So in other words, if you have arm9loaderhax installed, you're screwed if you update to that firmware. Not to also mention, 11.4 update of destruction will patch soundhax as well.
Source?
 
I'm a bit confused.

After reading the OP it seems to me that sighax isn't released alreade.
Then on the other had i read about people installing it.
So what's the matter now is it released or not?
 
I'm a bit confused.

After reading the OP it seems to me that sighax isn't released alreade.
Then on the other had i read about people installing it.
So what's the matter now is it released or not?
Are you sure they weren't confusing a9lh?
 
I'm a bit confused.

After reading the OP it seems to me that sighax isn't released alreade.
Then on the other had i read about people installing it.
So what's the matter now is it released or not?
afaik thre is no public implementation of sighax yet, since we havent got the bootroms til now.
 

Site & Scene News

Popular threads in this forum