Even with a faulty or non-functioning camera?GodMode9 and Luma3DS settings as well as safe mode work fine.
Interesting.. Thanks for the info!Disconnecting the bad camera makes the system boot up normally (obviously without the super stable 3D as it needs the camera for head tracking).
Old3DS (XL) don't have that problem. In neither model a disconnected camera will prevent booting.
OP sorta jumped the gun with opening the 3DS and unplugging the inside components before exhausting his options with the software side. But that's done now..Usually the abrupt shutoff is caused by torn cables to the upper screen assembly (might be very small damage). When they start tearing they must be replaced. Replacement of upper LCD and loudspeaker cable is needed (both, since they are both worn). Loudspeakers are soldered to the cable, so make your soldering equipment ready. Not a hard soldering job. Way harder is routing the new cables through the hinge without breaking them.
I'm pretty sure i spent 2 or 3 days trying every software solution that was suggested to me before opening it for the first time thoOP sorta jumped the gun with opening the 3DS and unplugging the inside components before exhausting his options with the software side. But that's done now..
What do you mean by "create the Luma folder"? Are you talking about the Boot.firm file or the payloads? In either case it can't create either if they're not present on the sd card..Also, if it was a faulty SD Card reader, would it still be able to create the luma folder inside the SD Card?
The folder is created after i try to boot the 3ds with the boot filesSince i can now post links, here's a screenshot of the luma folder i mentioned after trying to boot the 3ds with boot.firm and boot.3dsx only.
Wild guess: You are missing config.bin (config.ini for latest Luma3DS). Luma tries to create it after creating the SD:/luma folder. Since Luma settings also turn on the screen backlights, the console shuts off.As i mentioned before:
The folder is created after i try to boot the 3ds with the boot files
This is interesting, i tried creating the config.bin (i'm using the luma version i previously had) as a blank file and of course nothing changed. But, when i used this website to create the file, the blue light stayed on for much longer! Except when i try to boot holding SELECT.Wild guess: You are missing config.bin (config.ini for latest Luma3DS). Luma tries to create it after creating the SD:/luma folder. Since Luma settings also turn on the screen backlights, the console shuts off.
Provide a file SD:/luma/config.bin (config.ini), the console will try to boot (blue light stays on longer) and turn off once the normal operating system wants to initialize backlight.
The issue is most likely exactly what Sinchen described in that case, the cables going to the top part of the 3DS are not making a proper connection. While you could still try carefully reconnecting those cables, continuing to push them in while locking the connector to be sure, and also cleaning the connectors on both ends with alcohol, at this point it's unfortunately more likely that the issue lies deeper in those cables, being either that they have been damaged or are simply worn out from age and use.This is interesting, i tried creating the config.bin (i'm using the luma version i previously had) as a blank file and of course nothing changed. But, when i used this website to create the file, the blue light stayed on for much longer! Except when i try to boot holding SELECT.
Since i don't know what the configurations on the website do, i used the default ones, but this gives me hope
EDIT: tried putting the godmode and the rest of the files from the guide in the SD Card, now the speakers make a pop sound when it turns off.. god damnit.