White light and bad decisions = Bricked New 2DS XL

anotherthing

Well-Known Member
OP
Member
Joined
Mar 30, 2023
Messages
252
Trophies
0
Age
52
XP
341
Country
United States
Hello, fine people!

I was recently attempting to update Luma3DS, and managed to brick my New 2DS XL. The problem was that it was reading the Luma from the CTRNAND rather than the SD card. So, after reading too little on the subject apparently, and thinking that the result of what I read was that if it couldn't read the boot.firm from the CTRNAND, it would look for it on the SD card. So, I used GodMode9 to rename the boot.firm on the CTRNAND to boot.firm.old. Upon rebooting, I got the White LED of Doom. I tried booting in to Safe Mode, which does the same White LED of Doom. Since there's no boot.firm being read, I can't do the Start-Power thing to get back to GodMode9.

So, I decided that since I have an Ace3DS X card, I would do the ntrboot thing and just go about re-installing Luma that way. Following the guide here:

https://3ds.hacks.guide/installing-boot9strap-(ntrboot)

I know where the sweet spot is on the New 2DS XL, it's just above the A Button. When I do the X-Select-Start-Power with the magnet in the right spot, the blue power light comes on, but the White LED of Doom stays off. If the magnet isn't there, that LED lights up as you'd expect. However, it doesn't boot in to boot9strap. I followed the guide verbatim there. I've also tried using sthetix's 6 month old collection of files for it before I decided to follow the guide. Both result in the same thing. The blue LED lights up, the white one stays dark, but the boot9strap menu doesn't appear on the screen. When I remove my fingers from the device, the blue light eventually goes out.

I got the Ace3DS X card from nds-card.com's Amazon affiliated store several months ago. This card supposedly already has the ntxboot already flashed in it's "3DS Mode". So, I'm kind of at a loss here. The Ace3DS X card has the ntrboot_flasher_nds.nds in the root, and the directory of ntrboot with boot9strap_ntr.form in it. Is there something I'm missing? Could it be that Ace3DS X card lacks the flashed ntrboothax thing? I'm stumped here.

EDIT: SOLVED! It wasn't reading the boot.firm from the SD card because the SD card was funky to the 2DS.
 
Last edited by anotherthing,

master801

Well-Known Member
Member
Joined
Feb 24, 2011
Messages
1,159
Trophies
1
XP
2,507
Country
United States
Why are you not just putting boot.firm on the SD card, since it no longer exists on the NAND? Make sure to use about the same version of Luma as before or it may not boot.

Are sure you're switching the Ace3DS X into 3DS mode..?
ace3dsx01-jpg.103718
 

anotherthing

Well-Known Member
OP
Member
Joined
Mar 30, 2023
Messages
252
Trophies
0
Age
52
XP
341
Country
United States
Why are you not just putting boot.firm on the SD card, since it no longer exists on the NAND? Make sure to use about the same version of Luma as before or it may not boot.

The SD card does have boot.firm on it as well as the boot.3dsx file in the root. Originally the goal of renaming it was to force it to fall back to the SD card boot.firm. I did try it again after putting 12.0.1 back on there, and it still does the White LED of Doom.

Are sure you're switching the Ace3DS X into 3DS mode..?
Oh yeah. If you have it in NDS mode, you get the White LED of Doom. With the switch in 3DS mode, it does the power light, no White LED of Doom, but the screen doesn't come on and the boot9strap doesn't pop up.
Post automatically merged:

The contents of the SD card in the flashcart are irrelevant in ntrboot.
Okay, so does ntrboot make the 3DS look for a boot.firm at the root of the SD card? If that's the case, I don't think it's doing that at all. It's doing something because the White LED isn't lighting up when I do the X-Select-Start-Power thing with the Ace3DS X card in there.
 
Last edited by anotherthing,

master801

Well-Known Member
Member
Joined
Feb 24, 2011
Messages
1,159
Trophies
1
XP
2,507
Country
United States
The SD card does have boot.firm on it as well as the boot.3dsx file in the root. Originally the goal of renaming it was to force it to fall back to the SD card boot.firm. I did try it again after putting 12.0.1 back on there, and it still does the White LED of Doom.


Oh yeah. If you have it in NDS mode, you get the White LED of Doom. With the switch in 3DS mode, it does the power light, no White LED of Doom, but the screen doesn't come on and the boot9strap doesn't pop up.
Post automatically merged:


Okay, so does ntrboot make the 3DS look for a boot.firm at the root of the SD card? If that's the case, I don't think it's doing that at all. It's doing something because the White LED isn't lighting up when I do the X-Select-Start-Power thing with the Ace3DS X card in there.
Try a different SD card formatted to FAT32 32KB in the 3DS.

Everything (boot.firm, boot.3dsx, boot9strap/boot9strap.firm, boot9strap/boot9strap.firm.sha) should be going onto the 3DS' SD card.
 

anotherthing

Well-Known Member
OP
Member
Joined
Mar 30, 2023
Messages
252
Trophies
0
Age
52
XP
341
Country
United States
It does not look in the SD card in the flashcart; it only looks at the SD card in the 3DS.
Right. But does ntrboot cause the 3DS to look for a boot.firm in the root of the 3DS's SD card? Because it doesn't seem like it's doing that, because it doesn't just go to the Home Menu when you pull the magnet off. Instead, it powers down.

Try a different SD card formatted to FAT32 32KB in the 3DS.
I'm doing that now. It's either the Ace3DS X not doing it's thing, or there's something up with the original SD card that's in the 3DS that's causing it to "not see" the boot.firm that's on there. If it's supposed to fall back to the SD card if the CTRNAND doesn't have a boot.firm, it's most certainly not doing that. That SD card in the 3DS has had a boot.firm the entire time. In fact, the only reason I noticed that it was using the boot.firm on the CTRNAND is because I tried updating the Luma3DS and it kept using 12.0.1 when I updated it on the SD card to 13.0.2 both manually and with Universal Updater.
Post automatically merged:

Try a different SD card formatted to FAT32 32KB in the 3DS.
And we have success! It was the SD card. I thought there was something fishy this morning when I was playing around with the New 2DS XL and the power light would come on, but the orange "disk" light wouldn't come on, nor would the screens. That was the SD card as well. I popped it in to the computer, diskchecked it and got the 2DS to boot. The battery died in the New 2DS XL the last time I used it, so I'm guessing it really screwed up the SD card.
 
Last edited by anotherthing,
  • Like
Reactions: eyeliner

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • Sicklyboy @ Sicklyboy:
    Which all things considered is a great price
  • K3Nv2 @ K3Nv2:
    I took it with me to a medical appointment and the nurse was like that's a big charger :creep:
  • Sicklyboy @ Sicklyboy:
    That's not the only thing here that's big ;) (it's the medical bill because the US healthcare system is an absolute joke)
  • K3Nv2 @ K3Nv2:
    Luckily I get to whore myself to insurance which billing departments have no idea on how to handle
  • K3Nv2 @ K3Nv2:
    What he's covered? Make his life stressful anyway
  • Sicklyboy @ Sicklyboy:
    I love how insurance companies can deny procedures because they deem it not medically necessary despite the procedure being ordered by a doctor
  • K3Nv2 @ K3Nv2:
    Going with that right now with a dental claim morons put the wrong company name and rejected claims been on hold an hour for the claims department
  • K3Nv2 @ K3Nv2:
    @Sicklyboy, BTW is it better to go usb or bt for these mini Pcs figure you may know since you play with rack systems so much
  • Sicklyboy @ Sicklyboy:
    Counting my blessings that my insurance hasn't caused me really any headache (yet, at least) despite the fact that I've been getting way more appointments and what not recently due
  • Sicklyboy @ Sicklyboy:
    @K3Nv2, what do you mean, what are you trying to do?
  • K3Nv2 @ K3Nv2:
    Just looking at a built in mouse pad keyboard combo
  • K3Nv2 @ K3Nv2:
    I loose the dongle constantly but they may have better connection with usb frequency
  • Sicklyboy @ Sicklyboy:
    Imo Bluetooth is always a option of last resort for me
  • Sicklyboy @ Sicklyboy:
    Except for phones because it tends to be pretty reliable there
  • K3Nv2 @ K3Nv2:
    I got a bad habit of taking out usb transmitter and loosing it because they can't you know print names on the damn things
  • Sicklyboy @ Sicklyboy:
    But any desktop OS, I've never had anything but frustration trying to get Bluetooth devices to work reliably and stable. It might pair and connect once, and then next time I go to use it I have to delete and re-pair it again
  • K3Nv2 @ K3Nv2:
    5.3 has been so good I think 6 is really going to make it stable
  • K3Nv2 @ K3Nv2:
    I remember how shit 3 was
  • Sicklyboy @ Sicklyboy:
    Ptouch labeler aren't terribly expensive, label shit yourself fam. This is the one I own and there are cheaper ones too https://www.amazon.com/Brother-P-Touch-PTH110BP-Portable-included/dp/B09QXYND6S
  • Sicklyboy @ Sicklyboy:
    Solves part of the problem, mixing up which dongle is which. Then you just have to not lose them lol
  • K3Nv2 @ K3Nv2:
    Double D would be proud
    +1
  • Sicklyboy @ Sicklyboy:
    Even my Xbox One controller I have it paired to my desktop over Bluetooth, it USUALLY works but sometimes it refuses to connect and I have to delete and re-pair it. Maddening
  • K3Nv2 @ K3Nv2:
    Gigabytes built in mobo bt/wifi pairs pretty decent
  • Sicklyboy @ Sicklyboy:
    That's what I'm using :(
  • K3Nv2 @ K3Nv2:
    Ran a driver update in device manager?
    K3Nv2 @ K3Nv2: Ran a driver update in device manager?