Misc How did smea know "how" to hack the 3ds ?

  • Thread starter Thread starter Dathuss
  • Start date Start date
  • Views Views 3,318
  • Replies Replies 5
  • Likes Likes 2

Dathuss

Well-Known Member
Newcomer
Joined
Mar 29, 2018
Messages
49
Reaction score
7
Trophies
0
XP
322
Country
France
Hey all, I'm just curious how did smealum, in the first place, know what to do ?? Let me reformulate. I mean, cool, you got a way to execute arbitrary code, now how do you know what to execute ? As the 3ds runs on ARMv8, you can execute assembly code, but how did smea know, for example, how to open a file, call the keyboard handler, write to the nand... I know it's through syscalls, and looking at the source code of ctrulib and dissassembling myself some program code, the syntax for a syscall looks like this : get the syscall buffer, in the first element of said buffer, input a constant that represents the action of the syscall, then in the next elements, input the parameters, then call `swi 0x32`. But how did he know this ?? Did he just reverse engineer some game's source code, or through trial and error, or is the 3ds kernel similar to an open source kernel ? I'm curious.
 
  • Like
Reactions: cearp and zfreeman
As far as syscalls go, Nintendo SDK's documentation likely was a huge help. Since devs need to use the syscalls, they have to be explained. And basically all 3DS hackers had access to it in one way or another.
 
  • Like
Reactions: Dathuss
As far as syscalls go, Nintendo SDK's documentation likely was a huge help. Since devs need to use the syscalls, they have to be explained. And basically all 3DS hackers had access to it in one way or another.
Oh I forgot about the SDK. It looks pretty obvious now.
 

Site & Scene News

Popular threads in this forum