Skip to content

[BUG] sys/emunand ticket.db gets corrupted after manually reinstalling firmware #857

@cooolgamer

Description

@cooolgamer

So you want to report a bug?
Hold on, there are ways you could make things easier for us:

  • Give a clear description of the bug (what happened?).
  • Give us clear steps to reproduce (when/how did it happen?).
  • Give us info about your system (where did it happen?).
  • A photograph or even a short video of the bug happening is always helpful!

Info about your system
Include this info to make our work easier:

  • Console type (O3DS/N3DS)
  • Anything special about your console? (defects, custom modifications,...)
  • Bootloader (boot9strap/fastboot3ds)
  • Did you chainload GodMode9 via Luma?
  • Helpful hint: if you followed the Guide, boot9strap is your bootloader and Luma is your chainloader.

Help yourself
Especially for any kind of boot issue ("GodMode9 doesn't boot"), but also in many other cases these steps make a lot of sense and we will ask you to do them anyways:

  • Check your SD card (using h2testw, f.e.) or try a different one (you wouldn't believe how common failing/fake SD cards are, and what kinds of bugs are caused by them).
  • Switch to fastboot3DS using https://github.com/d0k3/OpenFirmInstaller.

Have you actually read this?
[X] I have read the information above

This is very specific and pretty rare, but when you want to manually do a ctrtransfer, so cleanup all ctrnand titles and install all firmware cias manually, there is a random chance that the ticket.db gets corrupted and everything fails to install because of this. I have no clue why this happens.
This was tested on emunand and sysnand on new and old 3ds.
This seems to happen after doing a lot of cia installation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions