I have three 3DS consoles with CFW, all of them with GBA injects. GBAVCSM works without issues in two of them, however on the third one two errors appear when trying yo build the Cache. This is the first one, if I hit Skip or Rename, it keeps appearing; if I hit Overwrite the second error pops up and the screen goes back to the gm9 main screen and no Titles are built into the Cache. Any idea what could be causing this?
@d0k3 - The CTRTransfer from both GodMode9 and Decrypt9WIP are the foundations that this script is built upon.
@Quantumcat - Helped saved the day solving someone's terribly softbricked o2DS with the power of Decrypt9.
This led to learning firsthand what those differences are between the two programs in how they perform it.
She also shared the title id for Nintendo 3DS Camera for AUS region.
@AnalogMan - His Lazarus3DS and related NAND gm9 scripts are major influences in understanding key aspects about 3DS firmware recovery.
@Namesnipe - Shared the neat knowledge that individual tickets can be backed up from the ticket.db.
@CodyWGamer - Showcased that the [S:] SYSNAND VIRTUAL isn't something to be trifled with if one does not treat that drive with caution and care.
@KleinesSinchen - Demonstrated and verified that the twln.bin and twlp.binpartitions can be super bricked.
This interesting knowledge was the final piece of the puzzle in making this script possible by showing that parts of the NAND are manually reflashable (perhaps too easily).
@botik (BpyH64) - Found a way to quickly install 3DS titles using dummy CIAs. I borrowed his idea from the .cmd CMACs research.
@zoogie - The research data for the Bypass Profile Setup was borrowed from 2DSaver.
@aspargas2 - Added DISA/DIFF handling in GM9 v1.9.0, which makes it possible to edit (sys/ext)data files.
TL;DR - Basically, CTRTransfer is like a universal SysNAND image used for recovering from softbricks and region changing the firmware.
If you're familiar with computer operating systems, this is similar to Windows Recovery and Mac Time Machine.
***
This is a gm9 script for performing a variation of Decrypt9 CTRTransfer. Homebrew 3DS users are likely to be more familiar with standard or (built-in) GodMode9 CTRTransfer. While both types are used for repairing or region changing the 3DS firmware, there are stark differences in how they go about changing or correcting the CTRNAND.
Decrypt9 Method
A few console unique files such as the movable.sed, configsave.bin, LocalFriendCodeSeed_B, and SecureInfo_A/B are first extracted from the CTRNAND drive. Afterwards, Decrypt9 (the program) flashes the entire raw donor CTRNAND *.bin image file onto the CTRNAND partition. Those backed up files are moved back in the drive to their respective locations and CMAC hash corrections are done throughout such as for the *.db datebase files and user's extdata + sysdata.
GodMode9 Method
GodMode9 (the program) selectively replaces only the title folder and *.db files. This is to surgically fix the broken system apps while keeping the rest of the user's personal and console unique files intact. Once these folders and files are replaced as needed, this is followed by CMAC hash corrections for those *.db files.
To put this into a comparable life analogy of the two, GM9 CTRTransfer is like replacing worn houseware parts, patching holes for stone walls to a structurally sound but very old house, and renovating its dainty decorations, flooring, and walls. D9 CTRTransfer is like removing your furnishings and personal belongs out of the house, knocking that house down because it's deemed too decrepit, building a replica in its place, and then moving as much of your stuff back in, assuming you haven't forgotten leaving behind anything before the teardown.
GodMode9 is the safer and less intrusive of the two while fixing most general softbricks. Although Decrypt9 is arguably more effective at dealing with severe softbricks, the older app's implementation fails to back up and restore crucial files such as hardware calibration HWCAL0.dat and HWCAL1.dat, personal legit tickets, and [seed|nag|friend|nnid|etc.]save.bin.
With those differences in mind, this script was created with the goal of combining the Decrypt9 approach of flashing a clean slate CTRNAND drive while also maintaining as much of the user's original setup like that of GodMode9.
Files and folders that are partially or fully deleted off the [1:] SYSNAND CTRNAND.
For whatever reason, the 3DS or 2DS system you have had its setup accidentally erased. Perhaps you bought/received yours prehacked from a previous owner who was neglectful. As long as something called the essential.exefs is present and has not been tampered with, it's possible to create a fresh firmware setup.
Let's imagine you experienced a catastrophic softbrick which required remedying the issue by restoring the SysNAND with a personal image backup. However, luck would have it that the one and only SysNAND *.bin image you kept was trashed by an unknowingly fake SD card. To add further insult to injury, during your restoration of the corrupted image, your system has a very old and untrustworthy battery that dies on you during mid-restore. This incident bricks the CTRNAND partition where GodMode9 doesn't even acknowledge the presence of the drive. Again, this is recoverable so long as the essential.exefs is present and hasn't been tampered with.
Strange '?' files that are stubbornly stuck in CTRNAND or cannot be deleted/replaced by conventional means.
Despite H2testw checking the SD card for issues, updating the custom firmware & 3DS firmware, and troubleshooting for any and all hardware issues, your system has unexplainable boot issues, poor GUI functionality, or random crashes. You (surprise, surprise!) don't have the benefit of a clean, backed up SysNAND *.bin image to recovery from. Attempts at using standard CTRTransfer are not providing favorable results. You may very well have a broken file allocation table at hand. If those damaged files are limited to replaceable or non-unique items, this script will try maintaining anything that's salvageable.
The nand header (nand_hdr.bin), TWL partition table (twlmbr.bin), [New 3DS only] secret sector (sector0x96.bin), and/or bootloaders (firm0.bin & firm1.bin) were corrupted from careless firmware modding, A9LH downgrade softbrick, or Gateway3DS malicious brickcode running a firmware newer than 11.2. In order to bypass thebootrom 8046 and launch GodMode9, an ntrboot flashcart would be required such as the R4i Gold 3DS Plus (recommended) or R4iSDHC series (shittytimebomb).
This cannot fix hardware based BSoD where the nand chip is fried from a failed hardmod or physically damaged by other means such as spilled water.
Copy everything off your SD card over to a computer.
Recommended: If you have another SD card, preferably small sized (minimum 4 GB), use that spare one instead of your main card.
Reformat the card in [ FAT32 format | 32 KB cluster size | Primary partition | MBR disk ] settings with Windows File Explorer, guiformat if bigger than 32 GB, or MiniTool Partition Wizard (free edition).
Test the SD card for hardware problems; full Write + Verify the empty card with H2testw (Windows), F3 (Linux), F3X (Mac), or SD Insight (Android / Chrome OS).
A fake or faulty SD card will cause a secondary brick where the user's setup is permanently corrupted when backed up.
[GOOD] If the result comes back clean, delete the *.h2w test files and go to step 5. [BAD]If a problem was reported, replace the card and go back to step 1.
[GOOD] - Test finished without errors.
[BAD] - The media is likely to be defective.
Either move back your main setup or create a temporary test setup.
(1) Your setup must have GodMode9, the 3DSX versions of FBI, faketik, and Cthulhu, Homebrew Launcher, and Luma3DS.
(2) Extract files from [ .7z | .rar | .zip ] archives with 7-Zip or WinRAR.
During script run,do not press and hold the (B) buttonwhen the DSiWare games are being dumped and especially for the system tickets.
These are the two sections I could not idiot proof. If you try to cancel building a DSiWare CIA, it'll ask you to try again with the choice to cancel. For the system tickets, the script will fail to completely mount ticket.db.
Exit the script, and press (POWER) → Poweroff system. Turn the system back on, and hold the (SELECT) button to access Luma3DS v#.# configuration. Use these exact settings. Press (START) to save and exit. The system should boot to HOME Menu.
Note:In the off chance the 3DS fails to boot HOME Menu with the below (or similar) error, fixing this requires manually finding and deleting the (ext/sys)data subfolder that is causing the hang-up: Debugging "gamecoin"-type brick
Open the Nintendo 3DS Camera to access Homebrew Launcher. If region changing the 3DS firmware and there are no system titles shown in HOME Menu, press the { (L)-shoulder + (R)-shoulder } button combo to launch the camera applet → Nintendo 3DS Camera→ Homebrew Launcher.
Note: If you have a [ o3DS | o3DSXL | o2DS ] and it gets stuck with black screens, press the { (L)-shoulder + (DOWN) d-pad + (SELECT) } button combo to open Rosalina menu → Reboot. This should restart the system and open Homebrew Launcher.
Note: If the shoulder buttons and/or cameras are broken, rerun the Inject HBL to Camera with an inserted 3DS game cartridge.
Install the system tickets and DSiWare CIAs with FBI. Restore missing tickets for nonlegit titles with faketik. If you have a lot of games, mass unwrap them all with Cthulhu.
Update to the latest firmware version in System Settings → Other Settings → System Update.
The system legit tickets from step 13 must be installed. Fake or missing system tickets will prevent the firmware from updating.
Do not update via Recovery Mode. This can lead to a mismatch between what's installed in the title folder and database files: title.db, import.db, ticket.db.
Go back to the script to restore the DSiWare saves.
0xD8E08066 - The system tickets may fail to install due to something called the certs.db (certificates). Your setup at one point either corrupted it or erased & regenerated that file with a dummy nonfunctional copy. A replacement copy borrowed from the CTRTransfer image would then be required. The script can replace that file if you come across this issue. Do not use this option if the problem doesn't exist;certs.dbis partially involved with transiting 3DS online play.
0xD8E0806C- The backed up DSiWare titles may fail to install. This is likely to occur if the CTRTransfer was used to region change the firmware. To fix this, install a different DSiWare *.cia file that's not from that backed up set. I have no clue why this hiccup occurs...
0xD8E0806A- The backed up DSiWare legit game titles may fail to install. To fix this, either redownload these previously purchased games from Nintendo eShop or convert the dumped legit CIAs into standard CIAs.
Finding and restoring the KeyY.
If you have the Nintendo 3DS folder backed up from a previous profile that was removed from (1) Format System Memory and (2) NOT involved in a System Transfer, this script can brute force up to 256 iterations finding the lost KeyY in the movable.sed linked to a specific <ID0> subfolder. To read more how this works,
Assuming the rest of the KeyY string is correct, finding the 0x118 hex counter that matches the target <ID0> can take up to 1.5 hour to complete or as little as 1 minute. This depends on the search order (this script looks backwards, ex: 03 → 02) versus value of the "correct" hex counter relative to the starting search value (ex, "correct" value is 04 but script is looking backwards, which will take a long time to find and calculate).
Update March-21-2019: Version 1.1 includes backing up the user's original sysnand ctrnand data profile if the KeyY is fixed. Changing the KeyY will automatically delete the 1:/data/<ID0> that's in place due to mismatch in encryption upon the next HOME Menu boot. This would force the user to create a new profile. The script provides the option to correct the 1:/data/<ID0> to the new KeyY. However, certain previous items like Friends List will be corrupted; the Friend Code is directly derived from KeyY.
Update May-21-2019: Version 1.3 does bi-directional searching where it splits the effort in looking both backwards (ex: 03 → 02) and forwards (ex: 03 → 04). There is now the option to quit the search run by pressing and holding the (B) button long enough. A 200 MB free space safety check was implement in case the data folder is backed up.
Backing up the DSiWare CIAs and saves only. Update March-21-2019: Version 1.1 - You can use this script for the ease of moving or importing nonlegit DSiWare titles and their saves involved in System Transfer or library duping. Update April-27-2019: Version 1.2 - The TWL system titles are no longer backed up in order to prevent reinstalling bad copies. This is to prevent bricking the DS mode with fake tickets. Update May-21-2019: Version 1.3 - Saves are no longer restored by mass dumping everything so as to not leave behind orphaned files. Saves are individually restored by cross checking for installed titles.
Relisting or rebuilding the 3DS database files.
In the event the title.db and import.db found in 0:/Nintendo 3DS/<ID0>/<ID1>/dbs are corrupted, all games, DLCs, and updates would be forgotten.
HOME Menu: <blank>
System Settings → Data Management → Nintendo 3DS→ [Software|Downloadable Content]
Being asked to reset or delete all software and savedata.
Saved Software Titles has gray question marks [ ? ].
General Warnings 1. (Re-)installing a CIA over a previously installed game will overwrite and delete its save currently in place. The Rebuild 3DS Database options were designed to fix the import.db and title.db without losing the saves and to keep whatever legit tickets you might have acquired from real Nintendo eShop purchases and updates.
2. During the options' script runs,do not press the (B) button. There is no way to idiot proof the CIA building process. If you press (B) button, you are forced to manually rebuild those titles into CIAs if they were interrupted. Just plug the 3DS system to a AC charger, flip the clam shell closed to let the script do its thing, and leave it alone. Except for Option (C) and if everything goes smoothly without error, the script will turn off the 3DS/2DS to let you know to move onto the next part.
3. Each option has two parts (1 - starting , 2 - finalizing) with an intermediate step of installing CIAs. Do not mix and match the parts between different options.
4. Certain games have anti-cheat save protection that will erase itself if tampering or swapping is detected.
Option (A) - Quick
The fastest of the three where dummy CIAs are generated, and all installed titles (saves included) are relocated offside to a temporary title_<ID0> folder. Once the dummy CIAs are installed:
The original ticket.db is restored to keep the user's real tickets in place.
To prevent accidental reinstallations of the dummy CIAs, the cias (dummy)_<ID0> folder is deleted.
The titles are moved back to the title folder.
Their individual *.cmd header CMACs are corrected.
A minimum 256 MB of free space is required when making the dummy CIAs.
Installing dummy DLCs with lots of contents can make FBI appear to crash or become stuck frozen. However, the progress is rather really slow for these titles. Look at the top row's moving clock for proof; be patient and don't force shut off!
The sizes and blocks will be reported wrong in FBI and System Settings. There's no away around this annoyance except to use or redo rebuilding the database with one of the other two options.
If curiosity got the better of you, where you completed both parts (1a) Generate Dummy CIAs and (2a) Restore Setup, and you want to restore your SD setup just like how it was before having started Option (A), this is entirely reversible with the backed up files found in dbs_cmd_<ID0> folder.
Option (B) - Full
This is the slowest option when rebuilding the database. Alongside with Option (C), however, the final reported sizes and blocks in FBI and System Settings will be correct. For each title that is successfully backed up as a CIA, its <TID LOW> subfolder within title/<TID HIGH> folder will be deleted. In case of errors, outside files and titles that aren't made into CIAs are not deleted but moved over to a collection title_<ID0> folder for your later examination. If found, saves are decrypted and extracted to a separate saves_<ID0> folder regardless if their parent games were built into a CIA.
Once the CIAs are backed up, and the titles are reinstalled:
The original ticket.db is restored to keep the user's real tickets in place.
The saves are individually restored depending if the parent games were found to be reinstalled.
A minimum 4 GB of free space is required to account for building the largest possible CIAs.
To avoid misuse or misunderstanding, option (B) requires a certain action outside of the script. Read the option description on what to do before using (1b) Backup CIAs & Saves.
Unlike Option (A), the cias (proper)_<ID0> output folder is left alone. You can keep copies of those backed up CIAs on your computer.
If your SD card has less free space than the total amount of all the CIAs, use:
FBI → cias (proper)_<ID0> → <current directory> → Install and delete all CIAs
Option (C) - Manual
In case your SD card does not have 4 GB of free space, or you already have all your games, DLCs, and updates previously backed up as CIAs, this option requires your due diligence supplying a 1-to-1 collection of CIAs for all the titles installed in the Nintendo 3DS folder. A simple installed_titles_list.txt can be cross referenced by TitleIDs against those found at:
Once the saves are backed up, and the titles are reinstalled:
The original ticket.db is restored to keep the user's real tickets in place.
The saves are individually restored depending if the parent games were found to be reinstalled.
A minimum 512 MB of free space is required when backing up the saves.
Unlike Option (B), you're not tasked to do anything outside of the script.
The title folder will be left as-is once the saves are copied.
The two (2) DB files do not necessarily have to bad. While not recommended compared to Checkpoint or JKSM, you can use (1c) Backup Saves to extract copies of your (decrypted) saves. On a different 3DS system with a cloned SD setup, you can use the (2c) Restore Saves (with minor naming adjustments to saves_<ID0> folder) if you intend to import over the saves.Just make sure you remove theticket.dbout of saves_<ID0> if the saves are going on a different system!!
Remapping the Rosalina menu button combo.
If your 3DS system has broken buttons where the default { (L)-shoulder + (DOWN) d-pad + (SELECT) } can't be used, the combo can be remapped with one of these choices:
(L)-shoulder
(R)-shoulder
(Y)
(X)
(START)
(SELECT)
(UP) d-pad
(DOWN) d-pad
Once you can gain access to Rosalina menu, change the combo preference:
Miscellaneous options... → Change the menu combo → <input your new combo> → Save settings
Bypassing the new user profile setup.
3DS systems that have broken 3D slider switch will get stuck at the 3D Screen Check after performing a system reformat.
System Settings → Other Settings → Format System Memory
Those who have hacked their o2DS by following outdated 2.1.0 CTRTransfer downgrade guides may also get theirs stuck at that screen, albeit with a distorted appearance.
This pitfall scenario can be skipped with this script. Once HOME Menu is reached, filling out personal information and user agreements is still mandatory for access to online services and system updates.
Looking up the Parental Controls PIN number.
Did you forget the four-digit password to the Parental Controls? Did you receive or purchase a 3DS system that the previous owner didn't unlock? No problem!
Some details of this script, what it does, and why. Ending comment.
For "best" case brick scenarios where nothing is missing, this script will only replace import.db, title.db, and title folder.
In the 1:/ drive, only data, dbs, fastboot3ds, fixdata, private, ro, rw, ticket, title, tmp,__journal.nn_, and boot.firm will be backed up. Everything else will be overwritten/deleted.
The user's original ticket.dbis kept in place so that personal legit tickets can still be individually dumped if the user chooses to do so later.
GodMode9 does not appear to recognize personal legit tickets installed on a different or replacement ticket.db.
However, universal legit tickets like system titles can be installed on any ticket.db and still be recognized by GodMode9 .
Due to the two bulletin points above, this is the reason why Homebrew Launcher is injected in Nintendo 3DS Camera in order to install those system tickets in a round about way.
With that said, this script isn't appropriate for those region changing the firmware with broken shoulder buttons and broken cameras.
Anyone examining the script's code might be baffled as to why certain sections may seem very redundant. Let's just say trial and error has made this deliberately overprotective as possible.
This script wasn't made with speed in mind. Besides, repairing a firmware softbrick isn't a race. Much of the script has comments with pauses so anyone using the script can know what's going on at a given moment.
While I hope this script finds good use to those who may need it, I also wish that no one finds himself or herself of having to do so in the first place. But, shit happens.
Dose anyone know if i can use this to transfer my new 3ds xl same model same reagon data to another of the same model same reagon bucause my systum that i want to transfer has a cracked/unrespponceive touchscreen thankyou.
Dose anyone know if i can use this to transfer my new 3ds xl same model same reagon data to another of the same model same reagon bucause my systum that i want to transfer has a cracked/unrespponceive touchscreen thankyou.
No, CTRTransfer isn't the same as system transfer, when you do a ctrtransfer you do it to restore a 3ds that had a corrupt file system etc. and not to transfer between systems. Your best bet is the standard system transfer, if your 3ds (the one that has the data you want to transfer) isn't functional, then it won't work. Your other option in that case is try to decrypt data with ninfs but that requires having some system specific files dumped when the system was still functional and the 3ds had to be modded, otherwise, no.
It's been a while since Microsoft released the Xbox One, and despite its age, there haven't been any reliable softmod methods to hack the console. Until now. A post...
After several months of work, the Harbour Masters 64 team have released their first public build of 2Ship2Harkinian, a feature-rich Majora's Mask PC port. This comes...
With the vast success of Super Mario Maker and its Switch sequel Super Mario Maker 2, Nintendo fans have long been calling for "Maker" titles for other iconic genres...
Palmer Luckey is known for his pursuits into the world of virtual reality, having founded Oculus and designed the Rift VR headset. Prior to the $2 billion dollar...
Another day, another Nintendo DMCA takedown against fan-made content.
Just a few minutes ago, Nintendo issued a DMCA takedown notice against a widely known and...
After a little more than three years of exclusivity with the Epic Games Store, Square Enix has decided to bring their beloved Kingdom Hearts franchise to Steam. The...
The complete source code for the Super Nintendo Entertainment System (SNES) version of Doom has been released on archive.org. Although some of the code was partially...
Sony is once more attempting to reintroduce players to their older library of games by re-releasing classic PlayStation 2 titles onto the PlayStation Store. During...
Skyward Sword is a divisive title in the Zelda series. Hailed with praise at launch with a 93 Metacritic average, the game since received criticism for the...
The latest State of Play is here. This is PlayStation's Summer showcase, providing updates to new updates on upcoming games and brand new reveals. The 35-minute...
Palmer Luckey is known for his pursuits into the world of virtual reality, having founded Oculus and designed the Rift VR headset. Prior to the $2 billion dollar...
It's been a while since Microsoft released the Xbox One, and despite its age, there haven't been any reliable softmod methods to hack the console. Until now. A post...
After several months of work, the Harbour Masters 64 team have released their first public build of 2Ship2Harkinian, a feature-rich Majora's Mask PC port. This comes...
Another day, another Nintendo DMCA takedown against fan-made content.
Just a few minutes ago, Nintendo issued a DMCA takedown notice against a widely known and...
After a little more than three years of exclusivity with the Epic Games Store, Square Enix has decided to bring their beloved Kingdom Hearts franchise to Steam. The...
Sony is once more attempting to reintroduce players to their older library of games by re-releasing classic PlayStation 2 titles onto the PlayStation Store. During...
Nintendo have officially announced a Nintendo Direct for tomorrow, June 18th.
The show will focus on Switch titles releasing this year and they have explicitly...
With the vast success of Super Mario Maker and its Switch sequel Super Mario Maker 2, Nintendo fans have long been calling for "Maker" titles for other iconic genres...
The latest State of Play is here. This is PlayStation's Summer showcase, providing updates to new updates on upcoming games and brand new reveals. The 35-minute...
The complete source code for the Super Nintendo Entertainment System (SNES) version of Doom has been released on archive.org. Although some of the code was partially...