Homebrew SigHax Updates and Discussion Thread

  • Thread starter Thread starter adrifcastr
  • Start date Start date
  • Views Views 532,174
  • Replies Replies 3,813
  • Likes Likes 43
For the fifth time, they temporarily replace arm9loaderhax(_si).bin with a nintendo made payload that removes a9lh. The now useless arm9loaderhax(_si).bin would be restored to what it was originally to avoid legal trouble due to altering user-placed files without the users' consent.

--------------------- MERGED ---------------------------


They can't be sued for removing/replacing user-placed files on NAND. They can for doing the same to SD cards.
Just double checked the 3dbrew page. Under enhanced-arm9loaderhax, it says
Since this is a combination of a trick with the arm9-bootrom + arm9loaderhax, and since you have to manually write FIRM to the firm0/firm1 NAND partitions, this can't be completely fixed.
and under arm9loaderhax,
Writing an incorrect key to NAND will cause arm9loader to decrypt the ARM9 kernel as garbage and then jump to it.

This allows a hardware-based attack where you can boot into an older exploited firmware, fill all memory with NOP sleds/jump-instructions, and then reboot into executing garbage.
 
sdcard is still your property. all it takes is one system with a modified a9lh that deals with that case badly and that could cause a brick.

the safe way is a firm protection bypass.
 
Just double checked the 3dbrew page. Under enhanced-arm9loaderhax, it says and under arm9loaderhax,
They aren't fixing a9lh. They are uninstalling it. There's a difference.

--------------------- MERGED ---------------------------

sdcard is still your property. all it takes is one system with a modified a9lh that deals with that case badly and that could cause a brick.

the safe way is a firm protection bypass.
The nintendo-made a9lh payload would replace firm0 and firm1 entirely.
 
You can't muck around user file. That's a CFAA violation. Even to temporarily replace it. They still accessed your system without your authorization. Of course they could change their EULA to try to make it legal first, but either way they'll be sued.
If that's true, they DO need to bypass firm0/firm1 protection.
 

Site & Scene News

Popular threads in this forum