Ok, so I went out today, and searched for a different brand MicroSD card. Unfortunately, I wasn't able to find a Samsung or Sandisk MicroSD card. However, I found a 32Gb ADATA card.
I formatted the card with SD Card Formatter and Windows File Explorer, and then ran H2testw and CrystalDiskMark on it. Here are the results. Oh, and it didn't get way too hot so I guess it's ok about that.
I might not be an expert on this stuff but it seems strange to me that it got so low on reading/writing when it said that it had a speed of up to 50Mb per second. However, I'm pretty sure that it's an original one since I compared the read/write speeds on this card with the results obtained by other people and they are the same.
That looks to be an authentic ADATA Premier series SD card.
Your write speed of ~20 MB/s is well over the expected Class 10.
Speed up to 50 MB (megabytes) per second most likely refers to read speeds under ideal setup. Your read speed of ~21 MB/s for a 1 GB test file is kinda low; this can be explained if you have an older computer that has an SD card reader with a slow bus speed.
Your card should be plenty fast for the n3DS.
I just ran the "Fix KeyY" script on CTRTransfer D9. Using the New ADATA Sd card it worked! Here are the results.
Now that it completed that successfully, I believe I should run the "Rebuild 3DS database" script, but, what should I select on there? Option "A" (Quick) or Option "B" (Full)?
Option (A) - Quick was designed for those who have LOTS of installed titles, like [ 64 GB / 128 GB / 200 GB / 256 GB / etc... ]. It is the fastest of the three when rebuilding the SD card's
title.db and
import.db. It has the drawback of showing the wrong sizes & used blocks in
Data Management and FBI's
Titles; this is more of a minor annoyance but something to keep in mind. Also, it doesn't check for data corruption that might have occurred to your installed titles' .APP contents. You can manually reverse the changes done in
Option (A) as the script backups the *.db and *.cmd files.
Option (B) - Full is the slowest but the most thorough. This option will backup your installed titles into CIAs and then delete them if they were successfully dumped. Titles that fail to get backed up into CIAs are pulled aside for later examination; it's assumed failed dumps mean those titles has been corrupted. The saves are decrypted and extracted regardless if their games were dumped into CIAs. The reported blocks / sizes will be correct.
Option (B) requires a minimum of 4 GB of free space to run. As was mentioned earlier in this thread, it requires a special user action as a safety measure in order to use
(1b) Backup CIAs & Saves. You should carefully read the script's top screen description and instructions.
- For titles that failed to get dumped into CIAs, you have to supply their replacement CIAs.
Option (C) - Manual is basically
Option (B) without backing up CIAs and deleting titles. All it does is extract and decrypt the saves. A text list of Title IDs is produced for you to provide your own backed up CIAs if you already have them on computer or external hard drive.
Option (C) will give the same result of
Option (B).
***
- All of them require you to run their respective part (1), install the CIAs collection, and then finish with part (2) to restore the saves / setup.
- Unfortunately, the only way to fix or relist the 3DS database (ie, import.db and title.db) is to reinstall the CIAs.
You can't go straight to installing the game CIAs because this will overwrite and delete their saves.
***
I personally recommend you go with
Option (B) due to the multiple bad incidences that occurred with the previous Kingston SD card, and also because your
Nintendo 3DS library isn't so large where it would take forever.
