I've recognized I've probably made a big mistake and have probably lost access to everything on my SD card and/or 3DS but,, I'm still hoping I can get a solution for this¿,,
Installed homebrew and several apps and games on a decent sized 16GB SD, everything was great, but I wanted to go bigger and used a 256GB Micro SD that was laying around.
The 256GB was relatively cheap and unbranded, and was bought from eBay, looking at it noW you can tell it was most likely fake, and it iS after multiple tests. It worked well on multiple mobile devices I owned though, so I didn't spare the thought that it was a bad card.
Made multiple copies of my existing files onto my desktop and moved original files from the smaller to larger SD.
Inserted it in the slot in it's adapter, pressed the power button, but all the system did was flash the blue light once and die out. Made sure the problem wasn't write protection or a dirty reader slot. Made sure a boot.firm file was present. It simply wouldn't boot. Taking it out allowed the 3DS to finally turn on, but putting the SD card back made it briefly freeze (was probably just reading the big ass thing), until all my games popped up on the menu.
Problem was it would display only a handful of my games' title screen (it's music and title icon that usually spins on the upper screen would work), while most others didn't (wouldn't show up or play sound at all). In Data management, the majority of my games would show a gray box with a question mark (where the title icon would show), no title name, and a 0 where the amount of blocks it took would take up. Exiting out of System settings even shut down the console. Attempting to play these 'blank' games resulted in an error stating "The SD card has been removed", leaving the choice to reboot the system (but instead of doing that, it would shut down).
A certain discord chat I was in wasn't much help, so I just let it be, because a couple days later I got a 32GB card, thinking I could just move the data onto something a little more reasonable sized. The same problems occurred, and after a bunch of attempts of moving the data back and forth I gave up.
Moved the files onto my desktop, (I think I deleted them), and cleared out my 32GB, thinking it was just simply corrupted files messed up by the fake micro. I just tried to re-homebrew the system again, (but I wasn't sure if you needed to remove CFW or something,,).
Tried to follow a guide when I saw the Nintendo 3DS folder was "corrupted and unreadable". Windows was able to fix it, but my 3ds would be unable to read the file. Deleting it and letting the system recreate the file would work, but removing and placing the SD into my PC would always register it was corrupted, along with it not being read at all.
Tried having my system read those other SD copies on different SD cards, they all failed to be read. I want to somehow salvage my game saves, but I have no idea if they're corrupted or something. Having those files on the micro SD was probably the worst mistake, so I wanted to try to format my console. But I'm not sure if it's safe to do so, with CFW and all, and I'm not sure it'll resolve this problem either. Overall, is there something I can do to fix this?¿
Installed homebrew and several apps and games on a decent sized 16GB SD, everything was great, but I wanted to go bigger and used a 256GB Micro SD that was laying around.
The 256GB was relatively cheap and unbranded, and was bought from eBay, looking at it noW you can tell it was most likely fake, and it iS after multiple tests. It worked well on multiple mobile devices I owned though, so I didn't spare the thought that it was a bad card.
Made multiple copies of my existing files onto my desktop and moved original files from the smaller to larger SD.
Inserted it in the slot in it's adapter, pressed the power button, but all the system did was flash the blue light once and die out. Made sure the problem wasn't write protection or a dirty reader slot. Made sure a boot.firm file was present. It simply wouldn't boot. Taking it out allowed the 3DS to finally turn on, but putting the SD card back made it briefly freeze (was probably just reading the big ass thing), until all my games popped up on the menu.
Problem was it would display only a handful of my games' title screen (it's music and title icon that usually spins on the upper screen would work), while most others didn't (wouldn't show up or play sound at all). In Data management, the majority of my games would show a gray box with a question mark (where the title icon would show), no title name, and a 0 where the amount of blocks it took would take up. Exiting out of System settings even shut down the console. Attempting to play these 'blank' games resulted in an error stating "The SD card has been removed", leaving the choice to reboot the system (but instead of doing that, it would shut down).
A certain discord chat I was in wasn't much help, so I just let it be, because a couple days later I got a 32GB card, thinking I could just move the data onto something a little more reasonable sized. The same problems occurred, and after a bunch of attempts of moving the data back and forth I gave up.
Moved the files onto my desktop, (I think I deleted them), and cleared out my 32GB, thinking it was just simply corrupted files messed up by the fake micro. I just tried to re-homebrew the system again, (but I wasn't sure if you needed to remove CFW or something,,).
Tried to follow a guide when I saw the Nintendo 3DS folder was "corrupted and unreadable". Windows was able to fix it, but my 3ds would be unable to read the file. Deleting it and letting the system recreate the file would work, but removing and placing the SD into my PC would always register it was corrupted, along with it not being read at all.
Tried having my system read those other SD copies on different SD cards, they all failed to be read. I want to somehow salvage my game saves, but I have no idea if they're corrupted or something. Having those files on the micro SD was probably the worst mistake, so I wanted to try to format my console. But I'm not sure if it's safe to do so, with CFW and all, and I'm not sure it'll resolve this problem either. Overall, is there something I can do to fix this?¿
