Hacking Post your ideas regarding how to hack the 3DS, here

  • Thread starter Thread starter Vulpes Abnocto
  • Start date Start date
  • Views Views 458,686
  • Replies Replies 1,786
  • Likes Likes 1
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??
 
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??

It means the executable image is corrupt, not a hack
 
  • Like
Reactions: 1 person
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??
This means we might be able to execute unsigned code if the header is still intact.
which leads to? haxx?
 
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.
No it doesn't.
 
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.
No it doesn't.
Sorry if you've already answered, but why is that?
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 header is probably encrypted, therefore needing to be decrypted to reverse engineer. Also, everything on the cart needs to be decrypted right? Please correct me if im wrong.
 
What interested me about this is even though the data was tampered with the program still loaded.
 
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.
No it doesn't.
Sorry if you've already answered, but why is that?
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?

It won't run the unsigned code because it checks the integrity of the game file

What interested me about this is even though the data was tampered with the program still loaded.
The program didn't load if it gave you that error message right away, that means it failed to boot the executable
 
Could easily be a hash function or something else, there are plenty of ways to detect if a file has been edited
 
There's more problems with the idea than just data integrity;
  • 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.
But yes, generally, file changes can be detected by checking a hash or a digital signature.
 
There's more problems with the idea than just data integrity;
  • 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.
But yes, generally, file changes can be detected by checking a hash or a digital signature.

Also very true
 
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 ?
 
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 ?
Maybe I'm misunderstanding you, but like you said, the files are signed for that specific system's use.
 

Site & Scene News

Popular threads in this forum