Currently, if TWL MBR is corrupt, the error shows "Error: MBR MBR is corrupt", while CTR MBR being incorrect shows "Error: CTR MBR is corrupt". This changes this to match the error style given for CTR MBR errors.
Don't actually merge this, a better solution is being worked on that overhauls the NAND validation function to allow checking for multiple problems, as well as to fix a few other bugs that affect devkits.
Currently, if TWL MBR is corrupt, the error shows "Error: MBR MBR is corrupt", while CTR MBR being incorrect shows "Error: CTR MBR is corrupt". This changes this to match the error style given for CTR MBR errors.