Homebrew SigHax Updates and Discussion Thread

  • Thread starter Thread starter adrifcastr
  • Start date Start date
  • Views Views 532,025
  • Replies Replies 3,813
  • Likes Likes 43
OH! That makes sense! I do have my brothers N3DS thankfully who lets me use it if I want to and his has A9LH. I'll just wait till Sighax is released and do it then.
Agreed! That's why I was asking if he/she had access to an O3DS or something with CFW, it would save from soldering, but if not then that's that.

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



There you go, that will save you a ton of work! Just be patient and wait for sighax.
Got ya!
 
I have a codename for SigHax:
Project CTRJ

What's that? CTR is 3DS and J is jailbreak. So it's the 3DS Jailbreak (unless an updated 3DS Hardware is released, it can't be patched, so it's jailbreak for good).
 
Nice one!

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

But honestly, would Nintendo be cared to patch sighax? I mean designing a whole new model just to patch something...
Hardware, no, they won't remove it. Software, they will patch the exploit used once sighax is released.
 
  • Like
Reactions: Kyousak
Once you have sighax installed, yes you could redirect sighax updates to a custom server; you can patch out signature checks for it.
you can be almost certain sighax will ultimately really just be used as a fake signed a9lh FIRM (essentially using the same tried and tested chain loading method to load a cfw from the SD card), I don't see any real practical reason to try split the userbase between the 2 methods, it serves no purpose other than to start sighax master race meme's

and I think its fairly clear most people who want sighax would already be on a updated system with no a9lh, so any requests to redirect updates would almost certainly be trying to ask if they can just setup a Nintendo server proxy to install sighax on a stock system, which is not possible for several reasons, and playing devils advocate and explaining impractical potential setups that still wouldn't do what these people are expecting will probably just confuse them into thinking they can get sighax from stock FW by redirecting the Nintendo site to nuntendo.hax
 
Last edited by gamesquest1,
you can be almost certain sighax will ultimately really just be used as a fake signed a9lh FIRM (essentially using the same tried and tested chain loading method to load a cfw from the SD card), I don't see any real practical reason to try split the userbase between the 2 methods, it serves no purpose other than to start sighax master race meme's

and I think its fairly clear most people who want sighax would already be on a updated system with no a9lh, so any requests to redirect updates would almost certainly be trying to ask if they can just setup a Nintendo server proxy to install sighax on a stock system, which is not possible for several reason
True, but if they have some sort of sighax update, redirecting the update server for a sighax- hosting one would be very convenient.
 
True, but if they have some sort of sighax update, redirecting the update server for a sighax- hosting one would be very convenient.
given the recent account hacks etc and the CFW repo's being compromised having a server capable of pushing remote updates to all hacked systems would be a disaster waiting to happen as it also would open up the possibility of the site being compromised and someone pushing a brick update remotely to all systems running sighax (sure people would have to accept the update, but I'm sure a lot of people would without batting an eyelid).....while in a dream world it might be nice the chainloading method is "safer" in the sense that the FIRM partition isn't changed during updates, so a bad cfw build couldn't lead to a brick (unless its doing something risky to the nand)
 
Last edited by gamesquest1,
given the recent account hacks etc and the CFW repo's being compromised having a server capable of pushing remote updates to all hacked systems would be a disaster waiting to happen as it also would open up the possibility of the site being compromised and someone pushing a brick update remotely to all systems running sighax (sure people would have to accept the update, but I'm sure a lot of people would without batting an eyelid).....while in a dream world it might be nice the chainloading method is "safer" in the sense that the FIRM partition isn't changed during updates, so a bad cfw build couldn't lead to a brick (unless its doing something risky to the nand)
As long as people do the same they do currently, making sure updating is safe before they do it, my point stands. A server redirect patch would never force updates on you, that would be insane and nobody would use the patch.
 
Last edited by Deleted member 414991,
no, sighax is exploiting a bug in how bootrom checks signatures, the normal OS would not fall for these fake signed firms

Even if the normal OS did accept a Sighaxed FIRM, you wouldn't be able to spoof the update server because you don't have the SSL certificates.

At least, I hope Nintendo's not that stupid.
 
I'll update the OP, but with a disclaimer, how the heck do I turn the letters red?

Fourth option from left to right .

But I have a guess that you can just use (color=) and (/color) with [] instead of (). Good old phpBB

Edit: I just now realized that I had like 5 more pages to read beyond you comment lol.
 
Last edited by gkoelho,

Site & Scene News

Popular threads in this forum