The preceding posts indicate that the card has already been formatted and tested. The only thing that hasn't been tried is booting the unit with an SD card that has nothing but boot.firm.Also the card have to be empty and preferable if it was newly formatted. I suspect this haven't been done?
That means my suggestion with just Luma wouldn't hurtThe preceding posts indicate that the card has already been formatted and tested. The only thing that hasn't been tried is booting the unit with an SD card that has nothing but boot.firm.
IIRC, CTGP-7 renames your existing "boot.firm" to "boot.firm.bak" and downloads an updated one when updating Luma through it. could be that, it could also be some other updater or OP creating the backup on their own.To be honest, I've never heard of this error before. I don't even know why you would have a "boot.firm.bak" and why your 3DS would prompt you to select it. (Are there other things you can select aside from boot.firm.bak?)
It messes with files on the NAND..? That seems very invasive.IIRC, CTGP-7 renames your existing "boot.firm" to "boot.firm.bak" and downloads an updated one when updating Luma through it.
oh, I didn't see that the .bak was on the NAND, my bad.It messes with files on the NAND..? That seems very invasive.
So I copied everything off the SD card and just put boot.firm and boot.3dsx in there.That means my suggestion with just Luma wouldn't hurt
Good question. But all your apps and saves are stored in the "Nintendo 3DS" folder, so you can just copy that to your card and then do https://3ds.guide/finalizing-setup . Whatever's causing the problem is almost certainly not in the "Nintendo 3DS" folder.Now, there's only one question - what's the culprit on the SD card that makes my 3DS refuse to boot?
How does one brick a console when they have said it works without the sd card in it? Bricks would mean they cannot boot or make use of the console at all.maybe you bricked it? i'm not all that experienced with the 3DS at the moment as all i know how to do is homebrew a 3DS, install CIAs and download new homebrew. oh, and update Luma3DS. actually, is that a thing you tried? if not, then try it!
0004013000003802 refer to firmware 9.3.0-21-K so what did you do?
YES! That's exactly what I did. I wanted to re-install rverse, because Pretendo's Juxtaposition wasn't working.Did you muck about with Pretendo?
That's the installation guide... While it might get my 3DS to boot again, it doesn't explain how to remove it so I can install rverse again.
Notice the file with the same name as the error title id?That's the installation guide... While it might get my 3DS to boot again, it doesn't explain how to remove it so I can install rverse again.
Why not just delete (or rename) the associated files in the Luma folder as described in that link?While it might get my 3DS to boot again, it doesn't explain how to remove it so I can install rverse again.
Now I got a new problem... it boots with my SD card without a problem, but NOTHING has loaded - not the theme, not the games, not ANYTHING except the DSiWare which was already present.Notice the file with the same name as the error title id?
So what did you do!? Did you copy your old "Nintendo 3DS" folder back to your SD card? Did you delete or rename the old "Nintendo 3DS" folder before you did that, like I suggested? Are we supposed to guess?!Now I got a new problem... it boots with my SD card without a problem, but NOTHING has loaded - not the theme, not the games, not ANYTHING except the DSiWare which was already present.
The homebrew launcher loads with all the apps still present, however.