N2DS SD card data management corruption?

Discussion in '3DS - Flashcards & Custom Firmwares' started by Androidian, Aug 24, 2019.

  1. NoSnake221

    NoSnake221 Advanced Member

    Newcomer
    1
    Sep 2, 2019
    Canada
    Tazmily
    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.
     

    Attached Files:

    Last edited by NoSnake221, Sep 7, 2019
  2. NoSnake221

    NoSnake221 Advanced Member

    Newcomer
    1
    Sep 2, 2019
    Canada
    Tazmily
    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)?
     

    Attached Files:

  3. TurdPooCharger

    TurdPooCharger Meh

    Member
    12
    Jan 1, 2018
    United States
    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.

    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.
     
    Last edited by TurdPooCharger, Sep 8, 2019
  4. NoSnake221

    NoSnake221 Advanced Member

    Newcomer
    1
    Sep 2, 2019
    Canada
    Tazmily
    I went to "Rebuild 3DS Database" Using the option "B" and starting of course with "1b", but my concern is that on the upper screen it says "NOTE: to prevent unintentional misuse, the user is tasked in removing 'import.db' & 'title.db' from '0:/Nintendo 3DS/<ID0>/<ID1>/dbs'." I believe that deleting those two files would be after option "B" "1b" finishes successfully, right?
     
  5. TurdPooCharger

    TurdPooCharger Meh

    Member
    12
    Jan 1, 2018
    United States
    Try running (1b) Backup CIAs & Saves as-is and see what happens. :)

    Be sure to read the instructions on the next screen so you know what to expect and certain things you have to do when the real run happens.

    There's no point keeping or reusing the old copies because fresh CIA installations would build a new set of import.db and title.db.

    ***

    If you're concerned about using Option (B), you can keep a backup copy of the Nintendo 3DS folder on your computer.
     
  6. NoSnake221

    NoSnake221 Advanced Member

    Newcomer
    1
    Sep 2, 2019
    Canada
    Tazmily
    Alright, I tried to run 1b and it gave the error shown on the image :unsure:
     

    Attached Files:

  7. TurdPooCharger

    TurdPooCharger Meh

    Member
    12
    Jan 1, 2018
    United States
    As demonstrated firsthand, the safety mechanism worked exactly as intended.

    The person who originally started this thread and used the Option (B) also ran into this back in Page 1.

    Now that you read both descriptions and instructions, you should have no problem understanding why it's like that and what to do to get (1b) to run.
     
  8. NoSnake221

    NoSnake221 Advanced Member

    Newcomer
    1
    Sep 2, 2019
    Canada
    Tazmily
    Well, I read all the instructions and that, however, I might not have followed correctly the 2nd step ("Set the volume slider to lowest screen brightness"). Isn't that just going to the home menu and changing the screen brightness to "1"?
     
  9. TurdPooCharger

    TurdPooCharger Meh

    Member
    12
    Jan 1, 2018
    United States
    Try the volume slider switch in GodMode9.
     
  10. NoSnake221

    NoSnake221 Advanced Member

    Newcomer
    1
    Sep 2, 2019
    Canada
    Tazmily
    No luck...
     
  11. TurdPooCharger

    TurdPooCharger Meh

    Member
    12
    Jan 1, 2018
    United States
    You don't notice the change in screen brightness?
     
  12. NoSnake221

    NoSnake221 Advanced Member

    Newcomer
    1
    Sep 2, 2019
    Canada
    Tazmily
    Yes, when I move the volume slider on GM9, there is a change in the screen brightness, and I moved the volume slider all down to minimum screen brightness (and minimum volume) but it still gives back the same error..
     
  13. TurdPooCharger

    TurdPooCharger Meh

    Member
    12
    Jan 1, 2018
    United States
    You read the description but didn't catch it all. :/

    As was already pointed out earlier,
     
  14. NoSnake221

    NoSnake221 Advanced Member

    Newcomer
    1
    Sep 2, 2019
    Canada
    Tazmily
    Oh, ok. I'll delete those files and try again

    — Posts automatically merged - Please don't double post! —

    I just tried that out but it turns out the SD card doesn't have 4Gb of free space. It has 3,96 :rofl:

    ----

    There's a SysNAND backup image on 'gm9/out' that is taking more than 1Gb of space. I can delete that, right?
     
  15. TurdPooCharger

    TurdPooCharger Meh

    Member
    12
    Jan 1, 2018
    United States
    Cut and paste it over to computer.
     
  16. NoSnake221

    NoSnake221 Advanced Member

    Newcomer
    1
    Sep 2, 2019
    Canada
    Tazmily
    Okay, it returned "Storage test success." I pressed "A" and folded the 3DS closed. The script is now running.

    ----

    I would like to know... the fact that that it should be folded closed is just a safety measure, is it for the battery not to drain so fast, or is it part of the script requirements?
     
  17. TurdPooCharger

    TurdPooCharger Meh

    Member
    12
    Jan 1, 2018
    United States
    Code:
        ~ INSTRUCTIONS ~ Rebuild 3DS Database (Full) ~  
     1. Plug in the AC charger to keep the system charged.
     2. Set the volume slider to lowest screen brightness.
     3. Wait for 'Storage test success.' and press (A).  
     4. Fold it closed if system has a clam shell design.
     5. DO NOT PRESS (B) AT ANY MOMENT! This interupts the
        CIA & SAV processes. The system will shut off when
        done. If an error occurs, see 'missing_titles.txt'.
     6. FBI > 'cias (proper)_<ID0>' > 'Install all CIAs' or
        'Install and delete all CIAs' for limited SD space.
     7. Run the '(2b) Restore Saves' option to complete.
     8. Checkpoint/JKSM - Backup all saves + extdata. This
     bypasses anti-cheat save protection for certain games.
     9. faketik - Restore tickets for nonlegit titles.  
     10. Cthulhu - Unwrap all HOME Menu software.    
    
    Steps 1 and 2 are to reduce battery drainage and to make sure the n3DS stays on for the entire duration until (1b) finishes. It would suck for the n3DS to prematurely turn off in the middle of dumping a CIA or deleting the title (ie, high risk of corrupting the SD card).

    Step 3 is to ensure your SD card has enough space to build the CIAs no matter how big the games are. You wouldn't want the script to suddenly quit because you ran out of memory.

    Steps 4 and 5 - Leave it alone. Go do something else. Watching random lines of code scrolling through the screen isn't that fascinating. When the dumping process is done, you'll know when the n3DS turns itself off (unless there were problems found).

    Steps 6 and 7* - Self explanatory.

    Steps 8 to 10 - These are slightly out of order. Refer back to posts #6 and #14.
     
    Last edited by TurdPooCharger, Sep 8, 2019
  18. NoSnake221

    NoSnake221 Advanced Member

    Newcomer
    1
    Sep 2, 2019
    Canada
    Tazmily
    Alright, then after it finishes, I'll go launch FBI through the HB launcher and follow steps 6 to 10.
     
  19. NoSnake221

    NoSnake221 Advanced Member

    Newcomer
    1
    Sep 2, 2019
    Canada
    Tazmily
    Okay, so I ran into a problem. When the "Rebuild 3DS database, option 'B', '1b'" script had succeeded, I went and used Rosalina Menu to switch the HB launcher to the "Face Raiders" program for following step 6. The HB launcher opened but the FBI .3dsx file was corrupted, so I downloaded a new one and entered the HB launcher again. Now it was showing as it should, but when I tried to open FBI, the screen just freezes and that's it..

    ----

    Ah, no problem. Just switched it to Download play and it's working fine.
     
    Last edited by NoSnake221, Sep 8, 2019
  20. NoSnake221

    NoSnake221 Advanced Member

    Newcomer
    1
    Sep 2, 2019
    Canada
    Tazmily
    However, I can't seem to find ''cias (proper)_<ID0>' on FBI :mellow:
     
Loading...