......by replacing your own ticket.db with other console's ticket.db using CTRNAND transfer, theoretically. You still have to find out a console with a ticket.db including zero bad ticket, and then use it to dump CTRNAND transfer image. You cannot use Plailect's Guide's all the 2.1.0 images and 9.2.0 images because they have already contained bad tickets such as FBI / Sysupdater / HBLauncher 's ticket. Steps: 1. Find a exploitable console with a pure clean ticket.db. 2. Boot Decrypt9WIP and dump CTRNAND transfer image (ctrtransfer.bin). 3. Put the ctrtransfer.bin to the Target Console you want to remove the bad tickets. 4. Boot Decrypt9WIP on the Target Console and do Auto CTRNAND Transfer (you can do it in either SysNAND or EmuNAND). Don't skip NAND backup step! 5. After Auto CTRNAND Transfer finished, dump ticket.db. 6. Restore original NAND then inject the dumped ticket.db into the NAND. Done. Q: What is bad ticket? A: Tickets generated in ticket.db by installing unsigned CIA, including all piracies & all homebrews in CIA format. Q: Why this method but not FBI 2.X ticket deleting? A: FBI 2.X cannot delete leftovers of bad tickets - it does disable the bad tickets, but leftovers still can be browsed by ticket.db viewers e.g. GroovyCIA.