None that are uptodate or obsolete no.Any other luma3ds payloads other then GodMode9
Add a second older gm9 firm to the payload folder. It should be stated thats whats needed atm.So how am I supposed to get around the bug?
Install Fastboot3DSSo 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!So how am I supposed to get around the bug?
But I am using sighaxYou 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!
Both boot9strap and fastboot3ds are sighax .FIRM bootloaders...But I am using sighax
But I am using sighax
Both boot9strap and fastboot3ds are sighax .FIRM bootloaders...
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.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).
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).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-
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-
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!
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.Interestingm why is fastboot3ds superior? Why isn't it recommended by most guides to use? Are there any risks compared to using boot9stap?
Who in the name of fuck, has 300 titles in his/her home menu?This is a good payload to have it lets you play gba games without having to load the 3ds sys menu. And yoi don't need to worry about the 300 title limit ect.
https://gbatemp.net/threads/open_agb_firm-discussion-thread.570844/
Loads of people here are constantly complaining about the title limit. Why they need so many games that they will probably never play I have no ideaWho in the name of fuck, has 300 titles in his/her home menu?
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.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.
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,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!