Just curious why a d9 CTRTransfer? Wouldn't GodMode9 be able to do it?Another day, another brick. For no SysNAND *.bin backup and empty [1:] SYSNAND CTRNAND, fixing this requires CTRTransfer (Type D9).
Just curious why a d9 CTRTransfer? Wouldn't GodMode9 be able to do it?Another day, another brick. For no SysNAND *.bin backup and empty [1:] SYSNAND CTRNAND, fixing this requires CTRTransfer (Type D9).
What do you suggest I do to fix this? Im open to anything thatll help.Just curious why a d9 CTRTransfer? Wouldn't GodMode9 be able to do it?
Do what @TurdPooCharger suggested but I'm pretty sure a gm9 CTRTransfer would workWhat do you suggest I do to fix this? Im open to anything thatll help.
Do what @TurdPooCharger suggested but I'm pretty sure a gm9 CTRTransfer would work
Can you describe how you're stuck?alright, in the guide by him, he directs you to https://3ds.hacks.guide/ctrtransfer.html which is using gm9 and im stuck at the second part
Can you describe how you're stuck?
So you've already transfered the image to ctrnand?When i select CTRTransfer ticket copy under Scripts from Phailect's guide, it errors and says it cant find the ticket backup.
When i try to transfer image to CTRNAND from the file i had to download at the beginning of the guide it cant find "ticket.db certs.db title.db import.db tmp_t.db tmp_i.db".
The (Type D9) I'm referring to isn't the CTRTransfer done in Decrypt9. It's the gm9 script that does the Decrypt9 approach of CTRTransfer in GodMode9 with added improvements.Just curious why a d9 CTRTransfer? Wouldn't GodMode9 be able to do it?
Since you deleted everything in the [1:] SYSNAND CTRNAND, there are no tickets to dump from the original ticket.db.Im at part 2 step 17 in this guide https://3ds.hacks.guide/ctrtransfer.html but it cant find the tickets. What now?
Oh ok, thanks for clarifyingThe (Type D9) I'm referring to isn't the CTRTransfer done in Decrypt9. It's the gm9 script that does the Decrypt9 approach of CTRTransfer in GodMode9 with added improvements.
Standard CTRTransfer or GM9 CTRTransfer is more focused on fixing softbricks that occurred in normal usage in NATIVE_FIRM (3DS mode). It doesn't restore certain console unique files that were deleted that could be added back in from the essential.exefs. CTRTransfer (Type D9) does this automatically if it detects these files are missing.
The (Type D9) I'm referring to isn't the CTRTransfer done in Decrypt9. It's the gm9 script that does the Decrypt9 approach of CTRTransfer in GodMode9 with added improvements.
Standard CTRTransfer or GM9 CTRTransfer is more focused on fixing softbricks that occurred in normal usage in NATIVE_FIRM (3DS mode). It doesn't restore certain console unique files that were deleted that could be added back in from the essential.exefs. CTRTransfer (Type D9) does this automatically if it detects these files are missing.
Since you deleted everything in the [1:] SYSNAND CTRNAND, there are no tickets to dump from the original ticket.db.
Not standard CTRTransfer; perform CTRTransfer (Type D9) - CTRTransfer.
I don't understand what you mean by this.Im trying to do this but when i transfer the CTRNAND to sysNAND it cant open 1:/dbs/ticket.db, 1:/dbs/certs.db, 1:/dbs/title.dbs, 1:/dbs/import.db, 1:/dbs/tmp_t.db and 1:/dbs/tmp_i.db
I don't understand what you mean by this.
Don't run CTRTransfer in Decrypt9 (the program).
Use the v1.4 of that script found below in that link. It'll be in a ZIP archive.
- CTRTransfer (Type D9) v1.4.zip
- CTRTransfer (Type D9).gm9
That's because you deleted the old ticket.db. CTRTransfer replaces that *.db file an renames the previous one to ticket.bak, so that the legit tickets for eShop purchases and updates can be dumped. No ticket.bak, no CTRTransfer Ticket Copy.fixed my previous problem, but when i go into Plailect's Guide>CTRTransfer Ticket Copy, it says no user tickets found
Ok, what should i do to get tickets back onto my device?That's because you deleted the old ticket.db. CTRTransfer replaces that *.db file an renames the previous one to ticket.bak, so that the legit tickets for eShop purchases and updates can be dumped. No ticket.bak, no CTRTransfer Ticket Copy.
The donor ticket.db borrowed from the ctrtransfer *.bin image contains a complete set of legit system tickets. System tickets are universally legit or usable across 3DS systems. You need legit tickets for system titles or else Nintendo will refuse to allow your 3DS to System Update to 11.13. If you used standard CTRTransfer, no need to worry about system titles found on the 3DS firmware as GodMode9 takes care of that by substituting/replacing it with the borrowed ticket.db.Ok, what should i do to get tickets back onto my device?
The donor ticket.db borrowed from the ctrtransfer *.bin image contains a complete set of legit system tickets. System tickets are universally legit or usable across 3DS systems. You need legit tickets for system titles or else Nintendo will refuse to allow your 3DS to System Update to 11.13. If you used standard CTRTransfer, no need to worry about system titles found on the 3DS firmware as GodMode9 takes care of that by substituting/replacing it with the borrowed ticket.db.
The other set of tickets most people are concerned about are their private legit tickets. These are the ones given to you from the Nintendo eShop for real purchased titles, downloads, and updates. Legit private tickets can't be restored unless you were to go back on Nintendo eShop and redownload every single one of your bought games and DLCs. Updates titles (0004000e) should be free to redownload.
For those who pirated their games & titles where they have illegitimate tickets (or if you don't really care about restoring your legit tickets), you can use faketik app to automatically regenerate or reinstall fake tickets as was mentioned by @Confusion_18 in post #29.
This is the telltale sign of missing tickets.
***
What you should be primarily focused on is whether or not the CTRTransfer brought your 3DS back to a working state where it can boot to HOME Menu.