@Voultar I just watched your video. When you went through the process of fixing the cold boot title, was that the first time you did it to that console, which fixed it or was that a recreation, after you already fixed it?
I am asking because I noticed the Current Cold Boot Title the recovery menu showed was already correct.
Can you send me the log directory of this console please? What you describe sounds like a third new cause and we are eager to find out what it is.
But kooldev would be the ultimate resource for that. I am pretty sure no one outside Nintendo knows more about the FS. But I forgot what his nick on gbatemp is.
EDIT: sorry I didn't read carefully @V10lator yes, it is possible that the OTP was involved in the IV, but I don't remember for sure. But I thinks the take away is we would need to do an IOSU patch, which I am sure someone in the community could pull off and we would need to find a way to deal with the SLC cache.
But playing with the SLC cache would require flashing through the Hardmod, which is very annoying and slow or testing with the emulator, which I can't get to work at the moment. Maybe Gary could help me with the emulator, but I don't want to bugger him to much and the SLC cache isn't on my priority list. I really first want to add the NAND dumper to the recovery menu.
I just took a look at the recovery_menu code and it seems that it is just calling some function provided by the os: https://github.com/GaryOderNichts/r...9e34b843cc3078b8/ios_mcp/source/imports.h#L36
I wonder what else this function might do.
@Voultar when you fixed the console, did you went straight to fixing the cold boot title or did you try if maybe just launching the recovery menu somehow fixed the problem (although I don't know how it would). But just to make sure there isn't anything strange going on and we are going down the wrong road.
I am asking because I noticed the Current Cold Boot Title the recovery menu showed was already correct.
Can you send me the log directory of this console please? What you describe sounds like a third new cause and we are eager to find out what it is.
The key for the USB devices is in the seeprom and the seeprom is writable. But the key alsone is not enough, you also need the right IV and the IV was generated in a way I couldn't control (at least not in a straight forward way). At least that's how I remember it. So you would need to modify IOSU to spoof the IV and while you are at it the key, so you don't need to change to seeprom)
But kooldev would be the ultimate resource for that. I am pretty sure no one outside Nintendo knows more about the FS. But I forgot what his nick on gbatemp is.
EDIT: sorry I didn't read carefully @V10lator yes, it is possible that the OTP was involved in the IV, but I don't remember for sure. But I thinks the take away is we would need to do an IOSU patch, which I am sure someone in the community could pull off and we would need to find a way to deal with the SLC cache.
But playing with the SLC cache would require flashing through the Hardmod, which is very annoying and slow or testing with the emulator, which I can't get to work at the moment. Maybe Gary could help me with the emulator, but I don't want to bugger him to much and the SLC cache isn't on my priority list. I really first want to add the NAND dumper to the recovery menu.
Post automatically merged:
I just took a look at the recovery_menu code and it seems that it is just calling some function provided by the os: https://github.com/GaryOderNichts/r...9e34b843cc3078b8/ios_mcp/source/imports.h#L36
I wonder what else this function might do.
@Voultar when you fixed the console, did you went straight to fixing the cold boot title or did you try if maybe just launching the recovery menu somehow fixed the problem (although I don't know how it would). But just to make sure there isn't anything strange going on and we are going down the wrong road.
Last edited by SDIO,
