It's here!

​

Info

@Normmatt has created a way to run B9S .firm files from bootrom via a DSi Flashcard and a magnet! This works on every 3DS on any firmware version.

For installation without a PC, user @TheCyberQuake has created a pack which will automatically install B9S and copy over essential starter homebrew from the flashcard's SD to the 3DS's. This will mainly be used for PC-less B9S installations. If you have a PC with you, use 3ds.guide. Read more here: https://gbatemp.net/threads/481141/

How does this work?

This works because of a flaw in the bootrom. Before the bootrom boots the NAND, it checks to see if Start+Select+X is held down, and if the shell is closed. If these requirements are met, it will boot an NDS cartridge from the bootrom. This give that cartridge bootrom access. You might be wondering how you'd hold down buttons while the shell is closed, and why you need a magnet. If you put a magnet in a specific spot on the 3DS, it will go into sleep mode. Using this, you can boot the NDS cartridge with the buttons held down while in sleep mode! Using a reflashable flashcard, you can boot B9SInstaller using the flashcard, and easily install it on your 3DS.

The 2DS doesn't need a magnet since a switch puts it to sleep instead of a magnet.

What does this mean?

1. Any 3DS model on any firmware can be hacked with minimal effort
2. You can unbrick any 3DS model from any type of brick.
   - Remember, you don't need a NAND backup for this. Just do a CTRTransfer.
   - This does not apply to MCU bricks.
3. Even consoles with fried NAND, or even the NAND chip physically removed, can use this

This is incredibly impressive stuff, and will most likely be released soon! edit: now!

FAQ

Q: Can Nintendo patch this?
A: Nope! Not without a new hardware revision.

Q: My flashcard is blocked by my firmware! Can I still use this?
A: Yes! The flashcard blacklist is not enabled on the bootrom.

Q: Why can't this work with my flashcard?
A: The installation requires you to flash NTRBoot to the flashcard's nand. Most DS flashcards, such as the original R4, have a ROM, which is not flashable.

Q: Can I install NTRBoot on my flashcard without another 3DS system?
A: If you can run NDS roms on your 3DS with it, then yes. If it's blocked on your 3DS version, then you'll need another 3DS system to use it.

Q: Will my 3DS flashcard work?
A: No, only the NDSi flashcards listed above.

Q: Will any other flash cards work?
A: Only the ones listed in the OP. However keep in mind that flashcards such as the DSTT, Supercard DS2 and R4 SDHC Dualcore are planned to be supported in the future.

Q: I tried to do this with my cartridge and it didn't work?
A: It doesn't work with regular DS cards.

Q: Can I unbrick from a ____ brick?
A: Considering the card has access to the bootrom, yes! This can unbrick any brick (except MCU), unless you've taken a knife to the motherboard.

Q: Can I install B9S on the latest firmware with this?
A: Again, since the card has access to the bootrom, you can do this easily! Just plug in your flashcard, boot up using the magnet and button combination, and install.

Q: Does this work on the New Nintendo 2DS XL?
A: Yes!

Release
Guide
Free NTRBoot Flashing
Free B9S Installations

Here is SciresM's post about this

Please see SciresM's presentation on bootromhax.​

 

[Lindorel]

Flash the flashcard, prepare your 3DS's SD, put the magnet on and the flashcard in, and boot while holding the button combination

When you don't use NTRBoot, does the 3DS boot up like normal?

You need reflash the FC with 1.3 flasher (b9s and Luma 8.1 is necessary).

 

[annson24]

Another great news from HandskmeMatt, 24 more flashchips are now supported.

Spoiler

I added 24 more flash chips to support (they use the identical erase & program commands as each other, however they differ in block sectors that require erasing. The most common boot block sector layout is: 16K, 8K, 8K, 32K, 64K, some only use a a single block, etc..

Supported flash chips so far:

* 0x051F "ATMEL AT49BV001A(N)"
* 0x1A37 "AMIC A29L800T"
* 0x3437 "AMIC A29L400T"
* 0x49C2 "MACRONIX MX29LV160BB"
* 0x5BC2 "MACRONIX MX29LV800B"
* 0x80BF "SST SST39LF/VF400A"
* 0x9B37 "AMIC A29L800U"
* 0xA01F "ATMEL AT49BV8192*"
* 0xA31F "ATMEL AT49BV8192*T"
* 0xA7C2 "MACRONIX MX29LV320T"
* 0xA8C2 "MACRONIX MX29LV320B"
* 0xB537 "AMIC A29L400U"
* 0xBA01 "SPANSION Am29LV400BB"
* 0xBA04 "SPANSION MBM29LV400BC"
* 0xBA1C "EON EN29LV400AB"
* 0xBA4A "ESI ES29LV400DB"
* 0xBAC2 "MACRONIX MX29LV400B"
* 0xB91C "EON EN29LV400AT"
* 0xC11F "ATMEL AT49BV802*"
* 0xC298 "TOSHIBA TC58FVT160A"
* 0xC31F "ATMEL AT49BV802*T"
* 0xC420 "ST M29W160BT"
* 0xC4C2 "MACRONIX MX29LV160BT"
* 0xEF20 "ST M29W400B"

The rest of the known flash chips require different write commands as specified in their data sheets, these flash chips are:

0x922C: http://www.dataman.com/media/datasheet/Micron/mt28f160c3_3.pdf (8x4K-Word Blocks) (similar/same to above)
0x9320: http://pdf.datasheetcatalog.com/datasheet/stmicroelectronics/7585.pdf (8x4K-Word Blocks) (^) ```

There are also the following flash chips I couldn't find data sheets for:

0x9020: ST M28W160(B)T (can't find datasheet)
0x9089: INTEL 28F160B3T (can't find specific datasheet)
0x9120: ST M28W160(B)B (can't find datasheet)
0x9189: INTEL 28F160B3B (can't find specific datasheet)
0x9289: INTEL 28F800B3T (can't find specific datasheet)
0x9389: INTEL 28F800B3B (can't find specific datasheet)
0x9689: INTEL 28F320B3T (can't find specific datasheet)
0x9789: INTEL 28F320B3B (can't find specific datasheet)

https://github.com/kitling/flashcart_core/pull/43#issuecomment-326266839

Now it's only a matter of time before kitling push another update on ntrboot_flasher

Sent from my SM-G950F using Tapatalk

 

[Viymes]

It works now, no idea why just reinserted the SD card a few times and replaced the files once.

 

[mvmiranda]

Ok! Just saw a new commit and I compiled a new build.
@Raugo tested and it worked for him.

@annson24 @Ramses @spkuja, you guys wanna test?

 

[annson24]

Ok! Just saw a new commit and I compiled a new build.
@Raugo tested and it worked for him.

@annson24 @Ramses @spkuja, you guys wanna test?

Oh definitely. [emoji2]

Sent from my SM-G950F using Tapatalk

 

[mvmiranda]

Oh definitely. [emoji2]

Sent from my SM-G950F using Tapatalk

File sent!

Well, funny thing is that my Ak2i HW-81 is not being "detected" by this build.
If I use 0.1.2 or 0.1.3 both detect my cart.

PS: it's already flashed with ntrboot firmware.

 

[RustInPeace]

Through means I'm still surprised over, I've acquired money to buy any of the supported flashcarts. But playing Mr. Krabs and seeing that DSTT is the cheapest that will get official support, does the one sold on NDS-card contain a compatible flash chip?

 

[failzers]

Flash the flashcard, prepare your 3DS's SD, put the magnet on and the flashcard in, and boot while holding the button combination

When you don't use NTRBoot, does the 3DS boot up like normal?

That doesn't actually talking about unbricking it tho. I meant the process of unbricking, not how to boot ntrboot.

 

[annson24]

That doesn't actually talking about unbricking it tho. I meant the process of unbricking, not how to boot ntrboot.

The easiest way is to boot gm9 with ntrboot. But seeing as it still has a bug with screeninit. The safestway I could think of is boot luma3ds from ntrboot and chainload gm9 with luma. Then do a ctrnand restore.

Sent from my SM-G950F using Tapatalk

 

[Alex S]

Another great news from HandskmeMatt, 24 more flashchips are now supported.

Spoiler

I added 24 more flash chips to support (they use the identical erase & program commands as each other, however they differ in block sectors that require erasing. The most common boot block sector layout is: 16K, 8K, 8K, 32K, 64K, some only use a a single block, etc..

Supported flash chips so far:

* 0x051F "ATMEL AT49BV001A(N)"
* 0x1A37 "AMIC A29L800T"
* 0x3437 "AMIC A29L400T"
* 0x49C2 "MACRONIX MX29LV160BB"
* 0x5BC2 "MACRONIX MX29LV800B"
* 0x80BF "SST SST39LF/VF400A"
* 0x9B37 "AMIC A29L800U"
* 0xA01F "ATMEL AT49BV8192*"
* 0xA31F "ATMEL AT49BV8192*T"
* 0xA7C2 "MACRONIX MX29LV320T"
* 0xA8C2 "MACRONIX MX29LV320B"
* 0xB537 "AMIC A29L400U"
* 0xBA01 "SPANSION Am29LV400BB"
* 0xBA04 "SPANSION MBM29LV400BC"
* 0xBA1C "EON EN29LV400AB"
* 0xBA4A "ESI ES29LV400DB"
* 0xBAC2 "MACRONIX MX29LV400B"
* 0xB91C "EON EN29LV400AT"
* 0xC11F "ATMEL AT49BV802*"
* 0xC298 "TOSHIBA TC58FVT160A"
* 0xC31F "ATMEL AT49BV802*T"
* 0xC420 "ST M29W160BT"
* 0xC4C2 "MACRONIX MX29LV160BT"
* 0xEF20 "ST M29W400B"

The rest of the known flash chips require different write commands as specified in their data sheets, these flash chips are:

0x922C: http://www.dataman.com/media/datasheet/Micron/mt28f160c3_3.pdf (8x4K-Word Blocks) (similar/same to above)
0x9320: http://pdf.datasheetcatalog.com/datasheet/stmicroelectronics/7585.pdf (8x4K-Word Blocks) (^) ```

There are also the following flash chips I couldn't find data sheets for:

0x9020: ST M28W160(B)T (can't find datasheet)
0x9089: INTEL 28F160B3T (can't find specific datasheet)
0x9120: ST M28W160(B)B (can't find datasheet)
0x9189: INTEL 28F160B3B (can't find specific datasheet)
0x9289: INTEL 28F800B3T (can't find specific datasheet)
0x9389: INTEL 28F800B3B (can't find specific datasheet)
0x9689: INTEL 28F320B3T (can't find specific datasheet)
0x9789: INTEL 28F320B3B (can't find specific datasheet)

https://github.com/kitling/flashcart_core/pull/43#issuecomment-326266839

Now it's only a matter of time before kitling push another update on ntrboot_flasher

Sent from my SM-G950F using Tapatalk

So does this mean DSTWO support is coming faster than expected? Im pretty sure my dstwo uses an amtel chip. (Or actel not exactly sure)

 

[oji]

Another great news from HandskmeMatt, 24 more flashchips are now supported.

Spoiler

I added 24 more flash chips to support (they use the identical erase & program commands as each other, however they differ in block sectors that require erasing. The most common boot block sector layout is: 16K, 8K, 8K, 32K, 64K, some only use a a single block, etc..

Supported flash chips so far:

* 0x051F "ATMEL AT49BV001A(N)"
* 0x1A37 "AMIC A29L800T"
* 0x3437 "AMIC A29L400T"
* 0x49C2 "MACRONIX MX29LV160BB"
* 0x5BC2 "MACRONIX MX29LV800B"
* 0x80BF "SST SST39LF/VF400A"
* 0x9B37 "AMIC A29L800U"
* 0xA01F "ATMEL AT49BV8192*"
* 0xA31F "ATMEL AT49BV8192*T"
* 0xA7C2 "MACRONIX MX29LV320T"
* 0xA8C2 "MACRONIX MX29LV320B"
* 0xB537 "AMIC A29L400U"
* 0xBA01 "SPANSION Am29LV400BB"
* 0xBA04 "SPANSION MBM29LV400BC"
* 0xBA1C "EON EN29LV400AB"
* 0xBA4A "ESI ES29LV400DB"
* 0xBAC2 "MACRONIX MX29LV400B"
* 0xB91C "EON EN29LV400AT"
* 0xC11F "ATMEL AT49BV802*"
* 0xC298 "TOSHIBA TC58FVT160A"
* 0xC31F "ATMEL AT49BV802*T"
* 0xC420 "ST M29W160BT"
* 0xC4C2 "MACRONIX MX29LV160BT"
* 0xEF20 "ST M29W400B"

The rest of the known flash chips require different write commands as specified in their data sheets, these flash chips are:

0x922C: http://www.dataman.com/media/datasheet/Micron/mt28f160c3_3.pdf (8x4K-Word Blocks) (similar/same to above)
0x9320: http://pdf.datasheetcatalog.com/datasheet/stmicroelectronics/7585.pdf (8x4K-Word Blocks) (^) ```

There are also the following flash chips I couldn't find data sheets for:

0x9020: ST M28W160(B)T (can't find datasheet)
0x9089: INTEL 28F160B3T (can't find specific datasheet)
0x9120: ST M28W160(B)B (can't find datasheet)
0x9189: INTEL 28F160B3B (can't find specific datasheet)
0x9289: INTEL 28F800B3T (can't find specific datasheet)
0x9389: INTEL 28F800B3B (can't find specific datasheet)
0x9689: INTEL 28F320B3T (can't find specific datasheet)
0x9789: INTEL 28F320B3B (can't find specific datasheet)

https://github.com/kitling/flashcart_core/pull/43#issuecomment-326266839

Now it's only a matter of time before kitling push another update on ntrboot_flasher

Sent from my SM-G950F using Tapatalk

Hope, my card will be added too, it's based on ATMEL AT49BV1614T

 

[Ramses]

Ok! Just saw a new commit and I compiled a new build.
@Raugo tested and it worked for him.

@annson24 @Ramses @spkuja, you guys wanna test?

Sure, but im kind of embarrassed as to how to PROPERLY flash my DSTT... so if you can provide me instructions as to how to do it, i'll do it, Also like I said: my situation is that my 3DS is bricked and I just have my old DS, so I don't know if whats going on will work :/

 

[annson24]

Sure, but im kind of embarrassed as to how to PROPERLY flash my DSTT... so if you can provide me instructions as to how to do it, i'll do it, Also like I said: my situation is that my 3DS is bricked and I just have my old DS, so I don't know if whats going on will work :/

Unfortunately starlord, DSTTs needs a 2nd hacked 3ds.

Sent from my SM-G950F using Tapatalk

 

[Raugo]

Sure, but im kind of embarrassed as to how to PROPERLY flash my DSTT... so if you can provide me instructions as to how to do it, i'll do it, Also like I said: my situation is that my 3DS is bricked and I just have my old DS, so I don't know if whats going on will work :/

For now you need a 3DS with cfw to flash it. Maybe with a dump of the flash with the ntrboot intalled you can use dsttflashwriter to install it buy I'm not sure.

 

[zakeblast]

Alright, so.... completely new problem.
I got my New 3DS (Downgraded without using emunand for OTP) to boot Luma and chainload into GM9, but now only the ABXY/start/select buttons work, everything else wont work at all.
So unless theres a program to CTRtransfer without using D-pad, i dont know how i can get around this problem.

 

[mvmiranda]

Alright, so.... completely new problem.
I got my New 3DS (Downgraded without using emunand for OTP) to boot Luma and chainload into GM9, but now only the ABXY/start/select buttons work, everything else wont work at all.
So unless theres a program to CTRtransfer without using D-pad, i dont know how i can get around this problem.

Well, have you tried to "clean" your touch screen?
I've seen odd behaviors when there's some "dust" or "particle" at the very edge (beneath, actually) acting as if the touch was pressed.

Just give it a shot!

 

[zakeblast]

Well, have you tried to "clean" your touch screen?
I've seen odd behaviors when there's some "dust" or "particle" at the very edge (beneath, actually) acting as if the touch was pressed.

Just give it a shot!

So, I took it apart just to make sure it wasn't a loose connection, and I did not believe my eyes.
The Circle pad cable, AND the cable which I assume lead to the D-pad, were both disconnected.
reconnected them, and it's working just fine now!

EDIT: Home button still isnt working, no clue where that connection is...

 

[spkuja]

Ok! Just saw a new commit and I compiled a new build.
@Raugo tested and it worked for him.

@annson24 @Ramses @spkuja, you guys wanna test?

Yes, please!

 

[jolly1991]

Oh definitely. [emoji2]

Sent from my SM-G950F using Tapatalk

Yes please, thanks

 

[LuigiXL]

Sorry wrong thread!