Toggle sidebar

Homebrew SigHax Updates and Discussion Thread

  • Thread starter Thread starter adrifcastr
  • Start date Start date
  • Views Views 532,226
  • Replies Replies 3,813
  • Likes Likes 43
Plailect said:
Or if you just want to boot without needing an SD...
Click to expand...
The author of the Kecleon patch had this implemented a few months ago. At least they don't need to update it for b9s now. It's funny, because I swear AuroraWright said she wasn't interested in putting this in mainstream Luma. Glad she changed her mind :-)
 
Quantumcat said:
The author of the Kecleon patch had this implemented a few months ago. At least they don't need to update it for b9s now. It's funny, because I swear AuroraWright said she wasn't interested in putting this in mainstream Luma. Glad she changed her mind :-)
Click to expand...
But this still doesn't mean it's a clean system for tournaments. Since holding start, assuming you followed the new steps, will load up GodMode9, even without an SD Card.
 
Temptress Cerise said:
But this still doesn't mean it's a clean system for tournaments. Since holding start, assuming you followed the new steps, will load up GodMode9, even without an SD Card.
Click to expand...
Or will it? It is still the same chainload that loads additional payloads in luma folder, isn't it? If you don't have godmode9 or have something else beside it there, it'll give you an option or won't give you any. And it still reads them from SD.
 
So wait, 3 questions. Bit of a noob here...

1. What's the difference between Luma and Arm9loader? I thought Luma was the CFW and Arm9loader was... Well I'm not sure...
2. Can Arm9loader/Luma be patched by nintendo if they find a way?
3. So sighax, if I'm understanding this correctly, is a CFW that is basically impossible for nintendo to patch?
 
Snerik said:
So wait, 3 questions. Bit of a noob here...

1. What's the difference between Luma and Arm9loader? I thought Luma was the CFW and Arm9loader was... Well I'm not sure...
2. Can Arm9loader/Luma be patched by nintendo if they find a way?
3. So sighax, if I'm understanding this correctly, is a CFW that is basically impossible for nintendo to patch?
Click to expand...
1. Arm9LoaderHax is an implementation of a vulnerability in the New3DS firmware's arm9loader, which allows for arbitrary code execution. Boot9Strap/Sighax supercedes A9LH because it works earlier in the boot process.

Luma3DS is a custom firmware (well, runtime firmware patcher) that can be loaded at boot time using Boot9Strap (and previously A9LH).

2. It's possible for Nintendo to add code in a future firmware update that could detect Luma and/or restore the FIRM partitions, but they haven't done so as of yet. With the Sighax vulnerability, this can always be reverted using a hardmod.

3. Sighax is a vulnerability in the Boot ROM, which is permanently burned into the main CPU and cannot be changed. The only way Nintendo can fix this is with a hardware revision. (It's entirely possible that the New 2DS XL fixes this, but we'll have to wait and see.)
 
Last edited by GerbilSoft,
  • Like
Reactions: Deleted member 388912, fireframe, uyjulian and 3 others
GerbilSoft said:
1. Arm9LoaderHax is an implementation of a vulnerability in the New3DS firmware's arm9loader, which allows for arbitrary code execution. Boot9Strap/Sighax supercedes A9LH because it works earlier in the boot process.

Luma3DS is a custom firmware (well, runtime firmware patcher) that can be loaded at boot time using Boot9Strap (and previously A9LH).

2. It's possible for Nintendo to add code in a future firmware update that could detect Luma and/or restore the FIRM partitions, but they haven't done so as of yet. With the Sighax vulnerability, this can always be reverted using a hardmod.

3. Sighax is a vulnerability in the Boot ROM, which is permanently burned into the main CPU and cannot be changed. The only way Nintendo can fix this is with a hardware revision. (It's entirely possible that the New 2DS XL fixes this, but we'll have to wait and see.)
Click to expand...
I see, so sighax basically beats any other CFW, in terms of viability, because its irreversible. So is the main end goal of all this to add a counter measure in case Nintendo decides they want to patch the current exploits? Also what's stopping Nintendo from doing that right now? It should be well with in their ability at this point, right?
 
GerbilSoft said:
1. Arm9LoaderHax is an implementation of a vulnerability in the New3DS firmware's arm9loader, which allows for arbitrary code execution. Boot9Strap/Sighax supercedes A9LH because it works earlier in the boot process.

Luma3DS is a custom firmware (well, runtime firmware patcher) that can be loaded at boot time using Boot9Strap (and previously A9LH).

2. It's possible for Nintendo to add code in a future firmware update that could detect Luma and/or restore the FIRM partitions, but they haven't done so as of yet. With the Sighax vulnerability, this can always be reverted using a hardmod.

3. Sighax is a vulnerability in the Boot ROM, which is permanently burned into the main CPU and cannot be changed. The only way Nintendo can fix this is with a hardware revision. (It's entirely possible that the New 2DS XL fixes this, but we'll have to wait and see.)
Click to expand...

Help me out. https://sciresm.github.io/33-and-a-half-c3/ "A BLAST FROM THE PAST" slide mentions system firmware 0.14 (1.0.0-0) and on checks against sighax. So are the checks patched via Luma or are we using magic?
 
  • Like
Reactions: Joey23475
OrGoN3 said:
Help me out. https://sciresm.github.io/33-and-a-half-c3/ "A BLAST FROM THE PAST" slide mentions system firmware 0.14 (1.0.0-0) and on checks against sighax. So are the checks patched via Luma or are we using magic?
Click to expand...
As I understood, the mentioned check in system firmware 0.14 is not the sighax itself. It is a similar vulnerability in the early firmware. Because they couldn't do research on sighax directly (because no public bootrom), they used that firmware vulnerability to make a perfect signature and thus made sighax. In the end we don't use that early firmware vulnerability.
 
  • Like
Reactions: OrGoN3
wwylele said:
As I understood, the mentioned check in system firmware 0.14 is not the sighax itself. It is a similar vulnerability in the early firmware. Because they couldn't do research on sighax directly (because no public bootrom), they used that firmware vulnerability to make a perfect signature and thus made sighax. In the end we don't use that early firmware vulnerability.
Click to expand...

Lovely. Way for them to refer to it on the slides literally as SigHax. Sigh. Sometimes I just wonder with the 3DS scene. Anyways, thanks for the info!
 
I have already posted this question on an earlier post by me but only after I've edited it, so that might be the reason why there has been no answer yet because nothing popped up.
So here is my question:
I got 2 N3DSXL consoles. One had A9HL on it which has been updated to B9S (source console) and the other one was stock OFW on 11.4. I successfully got B9S on that system as well by following DSiWare game injection of the guide (target console).
@Plailect Why would I want to redo the system transfer after succeeding in DSiWare games injection) from target console back to source console? This is still unclear to me since I had installed Boot9Strap on the source console, so it is still there, isn't it? Using the source 3DS' microSD card, I can still access Godmode9. So where would be the point for the system to be transferred again? Is it possible to just reconfigure the target console by injecting FBI to H&S and then reinstalling needed cia titles (Luma updater 2, HBL etc.)?
Thanks for answering questions (I can wait a week, so there is no problem. It is just that I want to know why I would have to transfer back because after this transfer, the target console would have to be resetup like the source console would have to be now, right?
 
  • Like
Reactions: OrGoN3
droople said:
Does it mean that we now have the potential to play DS games on a 3DS without a flashcard?
Cheers,
Click to expand...

Umm....... https://gbatemp.net/threads/twloader-ctr-mode-nds-app.448375/

hurrz said:
I have already posted this question on an earlier post by me but only after I've edited it, so that might be the reason why there has been no answer yet because nothing popped up.
So here is my question:
I got 2 N3DSXL consoles. One had A9HL on it which has been updated to B9S (source console) and the other one was stock OFW on 11.4. I successfully got B9S on that system as well by following DSiWare game injection of the guide (target console).
@Plailect Why would I want to redo the system transfer after succeeding in DSiWare games injection) from target console back to source console? This is still unclear to me since I had installed Boot9Strap on the source console, so it is still there, isn't it? Using the source 3DS' microSD card, I can still access Godmode9. So where would be the point for the system to be transferred again? Is it possible to just reconfigure the target console by injecting FBI to H&S and then reinstalling needed cia titles (Luma updater 2, HBL etc.)?
Thanks for answering questions (I can wait a week, so there is no problem. It is just that I want to know why I would have to transfer back because after this transfer, the target console would have to be resetup like the source console would have to be now, right?
Click to expand...

Doing a system transfer also transfers your NNID (Nintendo Network ID). If you want it back on your source console, you have 2 options. (1) think of a good reason and call Nintendo to have them transfer is back, or (2) transfer your second system back to your first. This is only for retaining your NNID on your first console. Otherwise, there is no need. Transferring doesn't remove B9S.

So yes, you can inject FBI into H&S and go from there. The only reason to transfer back is so that your NNID gets tied to the source console again.

RustInPeace said:
Freshly getting a console ban, now I wonder if there would be a way to unban without utilizing that lcfs, whatever it is.
Click to expand...

Depends on the type of ban and why you got it.
 
  • Like
Reactions: hurrz

Site & Scene News

Go to forum More news

Popular threads in this forum

Why did the price of 3ds shoot up ?

Hacking Homebrew Project  BlazerTube - a YouTube 3DS revival using the REAL app!

Homebrew app Emulator  [Release] 3DS-CLI - Run a real RISC-V Linux environment on the Nintendo 3DS

Problems getting Homebrew to appear outside of the Homebrew Launcher (homebrew won't appear on the HOME menu)

Website for finding alternative games for 3DS

Hardware  2 Broken 3DSes, need help

Gaming  any good rpgs on 3ds?

Hacking  Modding Reassurance