-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some sorta nand corruption #3
Comments
This is a correlation we've noticed on the DSiBrew Discord, the vast majority of people with this issue have used TWLNF to mount their NAND at one point. System update appears to fix this issue if they're on a lower firmware than 1.4.5. |
System update did not fix the issue on my end. |
To add on to this, it seems the cause of the problem is that twlnf will only save changes to the filesystem to the first FAT in the backup, ignoring the second one and possibly the third as well. To fix the bug, you need to make twlnf save any changs to all three |
Just as a sidenote, the issue also affected versions 1 and 1.01 of TempNand, the nand tool I coded (but not version 1.02) |
Weird, I used TWLnf and the Unlaunch installer worked perfectly... HiyaCFW installed easily. |
If anything has been changed in your nand, it's possible that all three FAT partitions will update themselves and get rid of the problem. In other words, it's won't affect ALL TWLnf users, just most of them |
Ahh, I've used it on three systems. Would it be useful to try to install unlaunch on the other two? |
I'm so sorry this tool caused such trouble, but I'm recently a bit busy on personal matters, so this might not be fixed in a foreseeable future, I'll be open to any reasonable pull requests though. |
So apparently if people have used TWLNF at one point, it has caused some sort of corruption in the Nand making it impossible to install UnLaunch and HiyaCfw. UnLaunch installer will hang on loading FAT, if twlnf was used at one point.
The text was updated successfully, but these errors were encountered: