Turn on the n2DSXL and quickly press & hold the (SELECT) button. Does the
Luma3DS v10.2 configuration appears?
If that screen shows up, your n2DSXL stills has custom firmware. There is a known bug where
GodMode9 might not load from
Luma3DS chainloader if it is the only FIRM payload. See if you can get GodMode9 to launch by adding another payload on the SD card.
- sdmc:/
- luma/
- payloads/
- GodMode9.firm
- GodMode9 (copy).firm
***
As to the possible reasons why your n2DSXL isn't booting to HOME Menu,
- (1) You were using an EmuNAND setup. This secondary 3DS firmware created on the SD card is what bricked. The CTRTransfer and CTRTransfer (Type D9) done to the n2DSXL were targeting their repairs on the SysNAND (primary 3DS firmware on the onboard NAND). Check that the Luma3DS v10.2 configuration does not have the (x) Autoboot EmuNAND option selected.
- (2) Your n2DSXL is stuck in a bootloop state where the original crash caused a build up old memory to accumulate but fail to clear in the RAM. For the other 3DS and 2DS models, this can be simply fixed with the battery trick. Unfortunately, on the n2DSXL its battery is not easily accessible.
- (3) When CTRTransfer and CTRTransfer (Type D9) were performed, the 3DS + custom firmwares were reflashed using a bad SD card. If you did not take adequate measures following those extremely crucial steps 1–4 in the (Type D9)'s Instructions where a fake/faulty/dying SD card was not caught, rejected, and replaced with a good card beforehand, the reflash can result in horrendously softbricking the firmwares.
- (4) A miscellaneous hardware component such as the camera or WiFi module has died. The n2DSXL refuses to boot to HOME Menu if the motherboard fails to communicate with one or more of its accessory parts.