Homebrew SigHax Updates and Discussion Thread

  • Thread starter Thread starter adrifcastr
  • Start date Start date
  • Views Views 532,122
  • Replies Replies 3,813
  • Likes Likes 43
@blujay you show proof yet? I not believe you

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

Is no problem show more for proof:
0x8000: 21 32 A0 E3 00 10 D3 E5 01 10 C1 E3 00 10 C3 E5 D3 00 A0 E3 00 F0 2F E1 4C D0 9F E5 D2 00 A0 E3
Hmmm... the Russians have been hacking bootroms too. :ninja:

that post is in a different thread and a year old
 
Last edited by zoogie,
"The disadvantage is, that's not as dynamic is A9LH due to it not being a payload on SD, that can easily be exchanged. (Unless your FIRM would load patches from sd. Which then wouldn't really make a lot of sense to use this exploit)
Therefore it's harder to update - basically like an A9LH update (not the payload but the actual FIRM write).
You risk bricking each time you write to the FIRM"





Is this still true for updating the 3ds on the new bs9 method in the 3ds.guide? Imagine we've all got sighax now and we're on 11.4 and they release 11.5 will we brick if we update??
 
"The disadvantage is, that's not as dynamic is A9LH due to it not being a payload on SD, that can easily be exchanged. (Unless your FIRM would load patches from sd. Which then wouldn't really make a lot of sense to use this exploit)
Therefore it's harder to update - basically like an A9LH update (not the payload but the actual FIRM write).
You risk bricking each time you write to the FIRM"




Is this still true for updating the 3ds on the new bs9 method in the 3ds.guide? Imagine we've all got sighax now and we're on 11.4 and they release 11.5 will we brick if we update??

b9s runs the boot.firm from the sd card or if missing, ctrnand. So it is not directly written to firm. We won't brick from a system update
 
"The disadvantage is, that's not as dynamic is A9LH due to it not being a payload on SD, that can easily be exchanged. (Unless your FIRM would load patches from sd. Which then wouldn't really make a lot of sense to use this exploit)
Therefore it's harder to update - basically like an A9LH update (not the payload but the actual FIRM write).
You risk bricking each time you write to the FIRM"





Is this still true for updating the 3ds on the new bs9 method in the 3ds.guide? Imagine we've all got sighax now and we're on 11.4 and they release 11.5 will we brick if we update??

Then, what's the point of doing this update?
 
"The disadvantage is, that's not as dynamic is A9LH due to it not being a payload on SD, that can easily be exchanged. (Unless your FIRM would load patches from sd. Which then wouldn't really make a lot of sense to use this exploit)
Therefore it's harder to update - basically like an A9LH update (not the payload but the actual FIRM write).
You risk bricking each time you write to the FIRM"




Is this still true for updating the 3ds on the new bs9 method in the 3ds.guide? Imagine we've all got sighax now and we're on 11.4 and they release 11.5 will we brick if we update??
B9S chainloads from SD/CTRNAND just like A9LH did, and the same FIRM protections that protected A9LH also protects B9S.
 
"The disadvantage is, that's not as dynamic is A9LH due to it not being a payload on SD, that can easily be exchanged. (Unless your FIRM would load patches from sd. Which then wouldn't really make a lot of sense to use this exploit)
Therefore it's harder to update - basically like an A9LH update (not the payload but the actual FIRM write).
You risk bricking each time you write to the FIRM"




Is this still true for updating the 3ds on the new bs9 method in the 3ds.guide? Imagine we've all got sighax now and we're on 11.4 and they release 11.5 will we brick if we update??

I believe sighax writes to FIRM each time you want to update the payload where as boot9strap as others have stated will check SD then CTRNAND just like A9LH did.

Man... this whole sighax releasing within the same time window as B9S has kinda split the community on what is what... ah well...
 
I believe sighax writes to FIRM each time you want to update the payload where as boot9strap as others have stated will check SD then CTRNAND just like A9LH did.

Man... this whole sighax releasing within the same time window as B9S has kinda split the community on what is what... ah well...
Sighax is the exploit, B9S is a sighax firm. Yes, you could install Luma or whatever as a sighax firm as well, but acting like B9S is some completely different entrypoint is weird.
 
Last edited by Cuphat,
  • Like
Reactions: RustInPeace
Sighax is the exploit, B9S is a sighax firm. Yes, you could install Luma or whatever as a sighax firm as well, but acting like B9S is some completely different entrypoint is weird.
I love how you keep posting that information. At this point its becoming colloquial that sighax is the derrek release, and boot9strap is the community release.
 
  • Like
Reactions: hurrz
I love how you keep posting that information. At this point its becoming colloquial that sighax is the derrek release, and boot9strap is the community release.
AFAIK, the only thing derrek released was an installer. In fact, you could use derrek's installer to install Boot9Strap.

derrek's installer should be compared to SafeB9SInstaller. Both install sighax'd firms. B9S itself just happens to be a sighax'd firm that includes an additional exploit and loads firms from SD/CTRNAND.
 
Last edited by Cuphat,
AFAIK, the only thing derrek released was an installer. In fact, you could use derrek's installer to install Boot9Strap.

derrek's installer should be compared to SafeB9SInstaller. Both install sighax'd firms. B9S itself just happens to be a sighax'd firm that includes an additional exploit and loads firms from SD/CTRNAND.

This is exactly correct.
 
Yes that's correct, but we all understand what they mean, and I'm fairly certain you do to. At some point it's just annoying seeing the same people make the same corrections over and over.
 
Yes that's correct, but we all understand what they mean, and I'm fairly certain you do to. At some point it's just annoying seeing the same people make the same corrections over and over.

Yes, I was just confirming their statement. While referring to Boot9Strap and sighax as separate things is incorrect from a technical perspective, it is obvious that everyone understands what you mean when you say one or the other. This was always going to be an issue though just due to the confusing nature (to users) of boot9strap being built on sighax.
 
I'd like to ask a question. Is there any way I can get Ctrbootmanager to work with .3dsx files while I've got sighax installed? From what I've heard, menuhax support has been dropped. How else am I going to be able to load any .3dsx files directly while booting into NATIVE_FIRM?

I'd really like to see a .firm program made in which loads the arm11 components that are needed to boot .3dsx files.
Just install the Homebrew Launcher CIA.
 
I don't know enough about how DS flash cards work to answer about them. I just read that you had to have certain ability to flash firmware/kernel to the card and only certain cards have the right hardware and our understanding about how it works for us to make it work. You'll have to wait for it release or someone more knowledgeable to shed some light on it.
I'll wait then, but if acekard is more likely to work, I think I'll rush to buy it, do you have or had one? Anyways, I think a DS flashcard would be great to play again those amazing DS games.
 
Yes, I was just confirming their statement. While referring to Boot9Strap and sighax as separate things is incorrect from a technical perspective, it is obvious that everyone understands what you mean when you say one or the other. This was always going to be an issue though just due to the confusing nature (to users) of boot9strap being built on sighax.
I accidentally didn't quote the person above you, who I was talking to and not you. I blame my router which is having a heart attack right now.
 

Site & Scene News

Popular threads in this forum