Stupid theory but what of you could put a game into the cartridge to trick the ds that its a game while playing the games from the sd card..?
wha?Stupid theory but what of you could put a game into the cartridge to trick the ds that its a game while playing the games from the sd card..?
A little find, I managed to get the 3DS to display "An error has occurred meh" when I hex edited a app on my SD Card. All I did was remove some random hex, even so the app however still boots but errors after the 3DS screen. Thoughts on this??
This means we might be able to execute unsigned code if the header is still intact.A little find, I managed to get the 3DS to display "An error has occurred meh" when I hex edited a app on my SD Card. All I did was remove some random hex, even so the app however still boots but errors after the 3DS screen. Thoughts on this??
which leads to? haxx?This means we might be able to execute unsigned code if the header is still intact.A little find, I managed to get the 3DS to display "An error has occurred meh" when I hex edited a app on my SD Card. All I did was remove some random hex, even so the app however still boots but errors after the 3DS screen. Thoughts on this??
No it doesn't.This means we might be able to execute unsigned code if the header is still intact.A little find, I managed to get the 3DS to display "An error has occurred meh" when I hex edited a app on my SD Card. All I did was remove some random hex, even so the app however still boots but errors after the 3DS screen. Thoughts on this??
Sorry if you've already answered, but why is that?No it doesn't.This means we might be able to execute unsigned code if the header is still intact.A little find, I managed to get the 3DS to display "An error has occurred meh" when I hex edited a app on my SD Card. All I did was remove some random hex, even so the app however still boots but errors after the 3DS screen. Thoughts on this??
Just a friendly reminder, this is not EoF, guys. Don't treat this topic as such.
Sorry if you've already answered, but why is that?No it doesn't.This means we might be able to execute unsigned code if the header is still intact.A little find, I managed to get the 3DS to display "An error has occurred meh" when I hex edited a app on my SD Card. All I did was remove some random hex, even so the app however still boots but errors after the 3DS screen. Thoughts on this??
If you have the decryption part in there, shouldn't it be able to run other code?
Wait, is it because we need to encrypt the code ourselves?
The program didn't load if it gave you that error message right away, that means it failed to boot the executableWhat interested me about this is even though the data was tampered with the program still loaded.
There's more problems with the idea than just data integrity;But yes, generally, file changes can be detected by checking a hash or a digital signature.
- Executables on the SD card are encrypted and signed, if you hex edit encrypted code how will you know where and what it gets decrypted to?
- The 3DS recovers from the error and displays a message on the home screen. This is a good indicator that it's not exploitable at all.
Maybe I'm misunderstanding you, but like you said, the files are signed for that specific system's use.probably suggested but :
since every 3DS signs with its own unique code all of the sd's encrypted contents should appear differently when compared
but if you find files or parts of files that are identical on 2 consoles then maybe you could study the file and change parts to cause a loading of custom files ?