Hacking Any other luma3ds payloads other then GodMode9

bfoos

Well-Known Member
Member
Joined
Dec 5, 2006
Messages
347
Trophies
0
Age
47
Location
Upstate, NY
Website
Visit site
XP
323
Country
United States
So how am I supposed to get around the bug?
You can simply make a copy of your current gm9 .firm in the luma payloads directory to get around the bug. Or as suggested by @BaamAlex and I completely second his recommendation... Switch from boot9strap to fastboot3ds as it is vastly superior!
 
  • Like
Reactions: BaamAlex

Lexar4GB

Member
OP
Newcomer
Joined
May 8, 2019
Messages
5
Trophies
0
Age
20
XP
70
Country
United States
You can simply make a copy of your current gm9 .firm in the luma payloads directory to get around the bug. Or as suggested by @BaamAlex and I completely second his recommendation... Switch from boot9strap to fastboot3ds as it is vastly superior!
But I am using sighax
 

nl255

Well-Known Member
Member
Joined
Apr 9, 2004
Messages
2,965
Trophies
0
XP
2,244
Country
But I am using sighax

It doesn't matter, as long as you can boot .firm payloads (or even a9lh .bin payloads) you can install fastboot3ds using OpenFirmInstaller and it can do anything b9s/sighax can do including dump boot9.bin/boot11.bin/otp.bin. It can also load .firm payloads from anywhere on the SD card (as long as the path isn't insanely long, of course).

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

Both boot9strap and fastboot3ds are sighax .FIRM bootloaders...

I believe that "sighax" is referring to the sighax.com installer and payload. You know, the one that is not recommended because it can easily cause a brick (fixable with a ntrboot flash cart) due to a lack of sanity checking that both the b9s installer and openfirminstaller/fastboot3ds have.
 
Last edited by nl255,
Joined
Jan 1, 2018
Messages
7,292
Trophies
0
XP
5,813
Country
United States
I believe that "sighax" is referring to the sighax.com installer and payload. You know, the one that is not recommended because it can easily cause a brick (fixable with a ntrboot flash cart) due to a lack of sanity checking that both the b9s installer and openfirminstaller/fastboot3ds have.
sighax refers to any .FIRM payload that can be installed on the FIRM0 and/or FIRM1 partition(s) found on the NAND where it can successfully boot itself or chainload boot to another .FIRM payload found on the SD card or CTRNAND.

The safety check to prevent gateway brick is due to having two (2) FIRM0/1 partitions. If say someone used a Gateway 3DS flashcart running on 3DS firmware newer than 11.2 ended up bricking one of those FIRM partitions, that 3DS system will default to the other intact copy when the ARM CPU bootrom goes looking for the next valid or backup .FIRM payload. I'm not sure if running Gateway 3DS again will go after bricking the second FIRM partition.

The sanity check is that system updating on open firmware installs or updates the .FIRM payloads on those FIRM0 and FIRM1 partitions. Luma3DS prevents modifications done to the partitions.

NOT RECOMMENDED. Average 3DS users, please do not mess with the FIRM0/1 partitions. The information presented below should not be tried or duplicated on your 3DS systems. Atypical setups are possible but should be avoided and can present difficulties unbricking if sometime goes wrong.
Luma3DS and GodMode9 could be directly installed to FIRM0 and/or FIRM1.

Keep in mind not all .FIRM payloads are sighax compatible. For example, the late Rei-Six custom firmware does not work when placed in FIRM0/1; it requires chainload booting from another .FIRM payload (typically boot9strap or fastboot3ds).
 
Last edited by TurdPooCharger,

nl255

Well-Known Member
Member
Joined
Apr 9, 2004
Messages
2,965
Trophies
0
XP
2,244
Country
sighax refers to any .FIRM payload that can be installed on the FIRM0 and/or FIRM1 partition(s) found on the NAND where it can successfully boot itself or chainload boot to another .FIRM payload found on the SD card or CTRNAND.

The safety check to prevent gateway brick is due to having two (2) FIRM0/1 partitions. If say someone used a Gateway 3DS flashcart running on 3DS firmware newer than 11.2 ended up bricking one of those FIRM partitions, that 3DS system will default to the other intact copy when the ARM CPU bootrom goes looking for the next valid or backup .FIRM payload. I'm not sure if running Gateway 3DS again will go after bricking the second FIRM partition.

The sanity check is that system updating on open firmware installs or updates the .FIRM payloads on those FIRM0 and FIRM1 partitions. Luma3DS prevents modifications done to the partitions.

NOT RECOMMENDED. Average 3DS users, please do not mess with the FIRM0/1 partitions. The information presented below should not be tried or duplicated on your 3DS systems. Atypical setups are possible but should be avoided and can present difficulties unbricking if sometime goes wrong.
Luma3DS and GodMode9 could be directly installed to FIRM0 and/or FIRM1.

Keep in mind not all .FIRM payloads are sighax compatible. For example, the late Rei-Six custom firmware does not work when placed in FIRM0/1; it requires chainload booting from another .FIRM payload (typically boot9strap or fastboot3ds).

No, sighax also can refer to derrek's installer and implementation (which I don't think supports bootrom dumping) however his installer doesn't do any kind of checking on the .firm file, it just flashes it. Here is a quote from a reddit thread that goes into more detail - note that at the time it was written fastboot3ds did not exist.

Sighax itself is a bootrom exploit that is unpatchable unless Nintendo decides to change their hardware. There are 2 different releases right now: derrek's Sighax installer and SciresM's Boot9strap.

Boot9strap is a different implementation of sighax combines with a couple other exploits, but acheives the same end result; installing/running custom firmware. Both allow you to run paylods in .firm format (.bin format payloads are no longer supported) as well as being able to launch CFW and hax such as Luma right away on boot, skipping over Nintendo's checks and such. B9S generally takes a slightly longer time to boot than A9LH, while sighax is slightly shorter, but neither makes much of a noticeable difference. However, these observations haven't been thoroughly tested, so your results will likely vary. This is just what I've noticed with my testing, as well as a few other posts on the matter.
 
Joined
Jan 1, 2018
Messages
7,292
Trophies
0
XP
5,813
Country
United States
No, sighax also can refer to derrek's installer and implementation (which I don't think supports bootrom dumping) however his installer doesn't do any kind of checking on the .firm file, it just flashes it. Here is a quote from a reddit thread that goes into more detail - note that at the time it was written fastboot3ds did not exist.

-snip-
Oh, I was referring to the end result of sighax and not so much how the .FIRM payload was installed to the FIRM0/FIRM1 partitions in the first place. This independent creation/discovery of sighax (derrek) and boot9strap (SciresM) plays out in a similar fashion to the invention of Calculus (Newton vs Leibniz).

I'll admit I did not recognize derrek as someone who is attributed to sighax/B9S since most people learned to hack their 3DS through 3ds.guide instead of sighax.com, so they notice SciresM when they go to download the SafeB9SInstaller and boot9strap.firm payload.

Some snippets I found that stood out while researching the differences.


L11on said:
Hedgeberg and SciresM version is different and it's more like a workaround execution rather than using your dumped bootrom, you can check his github for the explanation, also it's more new user friendly. Anyways derrek just released his version because he knew Hedgeberg and SciresM version was coming out, which makes him an ass and that's why b9s is on the 3ds.guide and will be supported by the community while sighax maybe not so much.


Note that this guide is NOT affiliated with sighax.com. That site's installer, created by derrekr6, has been known to BRICK devices, and will not be supported here.

SigHax/B9S Success Results

Boot9Strap
937 successful installs
8 bricked installs
0.85% chance of bricking

-snip-

Derrek's SigHax Installer 0.1

13 successful installs
13 bricked installs
50% chance of bricking

Derrek's SigHax Installer 0.2
37 successful installs
22 bricked installs
37% chance of bricking

-snip-

What it's called these days or who was technically the first to shared their findings should be a moot point.

Funny enough, I do know of derrek by a different work. He's one of the devs behind fastboot3ds!
 
Last edited by TurdPooCharger,
  • Like
Reactions: Alexander1970

Koldur

Virtual Boy Ambassador
Member
Joined
Feb 2, 2008
Messages
280
Trophies
0
XP
922
Country
Netherlands
You can simply make a copy of your current gm9 .firm in the luma payloads directory to get around the bug. Or as suggested by @BaamAlex and I completely second his recommendation... Switch from boot9strap to fastboot3ds as it is vastly superior!

Interestingm why is fastboot3ds superior? Why isn't it recommended by most guides to use? Are there any risks compared to using boot9stap?
 

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
16,988
Trophies
2
XP
15,984
Country
United States
Interestingm why is fastboot3ds superior? Why isn't it recommended by most guides to use? Are there any risks compared to using boot9stap?
Honestly, there isn't much of a difference between B9S and fastboot, and there probably isn't any real reason to switch from one to the other.

To fix the GodMode9 screen init issue when using B9S+Luma3DS, just make sure you have more than one payload in the payloads folder (until GodMode9 releases a fix). If you have nothing else to put in the payloads folder, you can just put a second copy of GodMode9 with a different name in there.
 

BaamAlex

S̶̥͝l̷̹̀͗e̶̼̖̩̅͊e̷̛̦͉̦p̷̘͌͝i̵͇̠̞̿̌n̷̰͚͌̓͝g̷̦̲̍̆͝
Member
Joined
Jul 23, 2018
Messages
4,101
Trophies
1
Age
26
XP
3,377
Country
Germany

bfoos

Well-Known Member
Member
Joined
Dec 5, 2006
Messages
347
Trophies
0
Age
47
Location
Upstate, NY
Website
Visit site
XP
323
Country
United States
Interestingm why is fastboot3ds superior? Why isn't it recommended by most guides to use? Are there any risks compared to using boot9stap?
For me, fastboot3ds is superior because it makes use of boot slots which are user configurable so say for instance you are on the latest version of Luma3ds (10.2) and you want to maybe mess around with some CTRPF plugins in .3gx form. You would need to use a modified, older version of Luma3ds based on 10.0 or 10.1.3 which their creators say to place on the root of your SD card. That would revert (your SD boot at least) to an older version of Luma. Sure, CTRNAND Luma would still be 10.2 but to boot to it, you would have to either remove your SD card or rename the older luma boot.firm. That's just kludgy at best and confusing at worst. Fastboot3ds solves those issues by allowing you to customize a bunch of boot slots to your liking. So, you can just put the older plugin loading boot.firm in another directory and leave Luma3ds 10.2 alone, then create and customize a boot slot for it. I boot into 10.1.3 plugin loader by holding R+A for instance.

Plus, it solves the godmode9 blackscreen issue that I know is right now tripping some poor soul up who's nearing the end of the 3ds.hacks.guide guide. There is also a small caveat to my setup or just mixing versions of Luma. Every time you boot into a different revision of Luma, you will need to setup Lumaconfig.
 

Koldur

Virtual Boy Ambassador
Member
Joined
Feb 2, 2008
Messages
280
Trophies
0
XP
922
Country
Netherlands
For me, fastboot3ds is superior because it makes use of boot slots which are user configurable so say for instance you are on the latest version of Luma3ds (10.2) and you want to maybe mess around with some CTRPF plugins in .3gx form. You would need to use a modified, older version of Luma3ds based on 10.0 or 10.1.3 which their creators say to place on the root of your SD card. That would revert (your SD boot at least) to an older version of Luma. Sure, CTRNAND Luma would still be 10.2 but to boot to it, you would have to either remove your SD card or rename the older luma boot.firm. That's just kludgy at best and confusing at worst. Fastboot3ds solves those issues by allowing you to customize a bunch of boot slots to your liking. So, you can just put the older plugin loading boot.firm in another directory and leave Luma3ds 10.2 alone, then create and customize a boot slot for it. I boot into 10.1.3 plugin loader by holding R+A for instance.

Plus, it solves the godmode9 blackscreen issue that I know is right now tripping some poor soul up who's nearing the end of the 3ds.hacks.guide guide. There is also a small caveat to my setup or just mixing versions of Luma. Every time you boot into a different revision of Luma, you will need to setup Lumaconfig.

Thanks for the explanation, sounds like the best version for those use cases indeed! In my personal case, I prefer godmode9.

It will frustrate the people helping out in Discord more than the people using the guide I guess ;) But very annoying if you do not know about that of course!
 

bfoos

Well-Known Member
Member
Joined
Dec 5, 2006
Messages
347
Trophies
0
Age
47
Location
Upstate, NY
Website
Visit site
XP
323
Country
United States
Thanks for the explanation, sounds like the best version for those use cases indeed! In my personal case, I prefer godmode9.

It will frustrate the people helping out in Discord more than the people using the guide I guess ;) But very annoying if you do not know about that of course!
Godmode9 is still used with fastboot3ds. It's just moved out of the luma/payloads directory and into gm9/payloads if you follow the fastboot3ds/Openfirminstaller instructions. And the great thing about fastboot3ds is you can put your payloads anywhere you want and set your boot slots up accordingly,

My setup:
Hold on boot...

Home=Fastboot3ds
Start=GodMode9
Select=LumaConfig
R+A=Luma3ds 10.1.3-Plugin-Loader
No Button=Luma3ds 10.2

It's just my personal preference, I prefer it over boot9strap chainloading.
 
Last edited by bfoos,
  • Like
Reactions: Koldur and peteruk
General chit-chat
Help Users
    kenenthk @ kenenthk: @WG481, We have a deep gay love for each other we're both in the closet about that's why