@ConfusedNDazed, you don't owe me or anyone anything. Here's my stance about accepting donations.
I would not try to cohere or guilt trip someone into doing something they're not comforting with. I'm going to be honest with you about performing CTRTransfer (Type D9). As much as I've tried to write and edit the Instructions
to be as simple to follow as possible, I don't consider the software repair solution to be user friendly or easy for homebrew beginners.
It has lots of steps involving upfront prep work ensuring the SD card is up to standard and post work after reflashing the ctrtransfer image. I've seen others skip the later steps where stuff like the DS(i) mode was left broken, and one person who reflash theirs under a suspected faulty SD card with very negative consequences... That user's 3DS firmware was softbricked more than when he started.
About trust allowing CTRTransfer (Type D9) with Lvl3 write privileges,
If you later decide to try CTRTransfer (Type D9) but don't like the results or the script happens to crash in mid reflash,
step 8 in the Instructions
asks to backup the SysNAND *.bin image. All changes done by CTRTransfer (Type D9) and post work related homebrew apps can be reverse by restoring that sysnand.
If the n3DS can't be salvageable or you no longer wish to continue with what may end up being a goose chase, Nintendo still sells 2DS/3DS systems. Their refurbished units are just as good / indistinguishable from brand new ones.
If you decide to DIY fix yours by replacing the motherboard after determining it's hardware faulty,
Or, hire someone else to repair the n3DS. May need to be done as special request.
- wiigotem - He's the same seller of the n3DS mobo from above.
- testerfan - Might need to supply him with a replacement n3DS motherboard. Maybe board reflow service?
The tickets (TIK files) are dumped to a folder named in this format like this.
- <date>_<serial>_system tickets_(<region>)_000
After installing tickets, install the TWL system & any DSiWare CIAs in the other folder,