Homebrew SigHax Updates and Discussion Thread

  • Thread starter Thread starter adrifcastr
  • Start date Start date
  • Views Views 532,071
  • Replies Replies 3,813
  • Likes Likes 43
Yes I know they are different, I never said they weren't. I'm just saying everyone using the term sighax at this point essential mean the derrek release stuff, and when saying boot9strap they mean the community tools for sighax as a whole.
I'm more annoyed with the repeated corrections made by the same people constantly in this thread. After a certain point it just starts to add more replies to an already large thread that just aren't needed.
 
  • Like
Reactions: Quantumcat
@Plailect Hey Plailect! Great guide! May I ask you something please? I have a bricked N3DS (my issue is here https://github.com/Plailect/sysDowngrader/issues/18 ) do you know if it is possible to recover it with Hardmod + Sighax? It's on a franken state between 11.0 and 9.2. Also, do you know something about NTRBootHax? Thanks in advance
Remember that Plailect just puts together the info, he doesn't create all the tools.
 
@Plailect Hey Plailect! Great guide! May I ask you something please? I have a bricked N3DS (my issue is here https://github.com/Plailect/sysDowngrader/issues/18 ) do you know if it is possible to recover it with Hardmod + Sighax? It's on a franken state between 11.0 and 9.2. Also, do you know something about NTRBootHax? Thanks in advance

Using a hardmod would require that you know what is in your FIRM partitions (11.0 or 9.2 FIRM). You could try both using https://3ds.guide/installing-boot9strap-(hardmod). NTRBootHax (or whatever it ends up being called) would also work, and wouldn't even require you to know the contents of the firm partitions because you could decrypt them.

Remember that Plailect just puts together the info, he doesn't create all the tools.

I'm still in the loop and know stuff :ha:
 
the same reason why I stayed on RxTools for so long. Not necessary for me at the time.
Yeah, and you know what happened when people held onto rxtools for so long? Things started to break and then a myriad of threads started poping up with people having issues asking for fixes. Not saying you specifically did that, but it's that kind of mentality by a mass amount of people that causes that type of chaos.
 
Using a hardmod would require that you know what is in your FIRM partitions (11.0 or 9.2 FIRM). You could try both using https://3ds.guide/installing-boot9strap-(hardmod). NTRBootHax (or whatever it ends up being called) would also work, and wouldn't even require you to know the contents of the firm partitions because you could decrypt them.

I'm still in the loop and know stuff :ha:

In that moment, your guide used DSiWareHax to donwgrade the FIRM first, so I have to try with 11.0, 10.7 and 9.2 FIRM right? To sum up, I extract the corrupted NAND, run the B9S installer 3 times with the 3 firms and flash them until it works right? If it doesn't work it will just not boot?
 
  • Like
Reactions: Quantumcat
Yeah, and you know what happened when people held onto rxtools for so long? Things started to break and then a myriad of threads started poping up with people having issues asking for fixes. Not saying you specifically did that, but it's that kind of mentality by a mass amount of people that causes that type of chaos.
can you name something that "broke"? Everything I had an issue with was because I didn't install something properly, or something with one of those special games using special memory mode. (not smash)

Also, menuhax didn't cause any issues for me since i almost never turned my 3ds off.
 
Last edited by TimX24968B,
can you name something that "broke"? Everything I had an issue with was because I didn't install something properly, or something with one of those special games using special memory mode. (not smash)

Also, menuhax didn't cause any issues for me since i almost never turned my 3ds off.
iirc 11.4 completely broke rxtools for good. So everyone still using rxtools started posting threads about being unable to boot emuNAND and "Please help I think I bricked emuNAND"
Even though the community has been saying for months that rxTools was a dead project and a firmware update could easily wreck rxTools.
So many threads where the end result was just "Upgrade to a recent CFW like luma"
And now with luma also dropping a9lh/menuhax support, those who still use menuhax and a9lh will eventually see a day where luma stops working for them as well and will be forced to go the B9S route.
 
iirc 11.4 completely broke rxtools for good. So everyone still using rxtools started posting threads about being unable to boot emuNAND and "Please help I think I bricked emuNAND"
Even though the community has been saying for months that rxTools was a dead project and a firmware update could easily wreck rxTools.
So many threads where the end result was just "Upgrade to a recent CFW like luma"
And now with luma also dropping a9lh/menuhax support, those who still use menuhax and a9lh will eventually see a day where luma stops working for them as well and will be forced to go the B9S route.
well 11.4 was a definite end to it, but thats not an issue i was talking about. Once I find an update that doesn't work for A9LH, then I will switch.
 

Site & Scene News

Popular threads in this forum