so what do i do now that its on? (im sorta a noob in this aspect, have never had done a mod incorrectly up to this point)

— Posts automatically merged - Please don't double post! —

sorry lemme rephrase, what do i do if i want to continue hacking it at this point?

 

so what if i follow the finalization guide to the letter but godmode9 doesnt open when holding start during boot?

 

Accidentally turned on the write protect lock?

 

Hey i never post on these forums, but i made an account just to say thank you to the Jdbye and the Turdpusher dude. i did something super dumb that i knew better than to do, and bricked a console. Yall saved me, just followed what you had to say to a T, and all those links, just wanted to express my graditude.

 

Do a scan for bad clusters: chkdsk /F /R X: in a command prompt. If it successfully detects and remaps some clusters, you can format the card and try putting the files on again and it should hopefully work.

 

The card is FAT32 formatted, right?

 

Check if the SD card you're using is fake or dying.

1. Copy everything off the SD card to a computer.
2. Quadruple reformat.
3. Full Write + Verify the empty card in H2testw. Do not skip.

Report back the test results.

 

4. Battery trick (unless this is a New 2DS XL).
5. Without the SD card and gamecart inserted, turn on the 2DS system and hold the (SELECT) button.
​

Possible Outcomes

(A) If boot9strap custom firmware is installed and CTRNAND Luma3DS has been setup, you should see these.

• Top Screen: Luma3DS v#.# configuration
  • v7.1 (or newer)
• Bottom Screen: Booted from CTRNAND via B9S

(B) If arm9loaderhax custom firmware is installed and CTRNAND Luma3DS has been setup, you should instead see this.

• Top Screen: Luma3DS v#.# configuration
  • v7.0.5 (or older)

(C) If B9S or A9LH CFW is installed but CTRNAND Luma3DS is missing, the 2DS should turn on with a single blue LED blink and then turn off.

• Despite having custom firmware, failure to boot Luma3DS from the SD card may be due to broken card slot reader.

(D) The 2DS turns on and stays on with black screens. Either the custom firmware is no longer installed, the 3DS firmware has softbricked, and/or there is an unspecified hardware failure.

• For old series systems [o2DS / o3DS / o3DSXL], common boot failure can be caused by disconnected WiFi module.
• Due to their age, another consideration is that old series system are experiencing increasingly higher rates of motherboard failure as their SMD components wear out (ie, GPU/CPU/SoC, RAM, PMIC).

​