Homebrew OOT 3D Exploit Working On Downloaded Copies?

  • Thread starter Thread starter FM360
  • Start date Start date
  • Views Views 2,646
  • Replies Replies 17

FM360

Kappa
Member
Joined
Mar 8, 2015
Messages
270
Reaction score
155
Trophies
1
XP
450
Country
Iran
I have been wondering if this exploit works on downloaded versions of the game. I am thinking that it could because you can freely edit the save data of downloaded games on the SD card using a hex editor. Im just wondering.
 
I have been wondering if this exploit works on downloaded versions of the game. I am thinking that it could because you can freely edit the save data of downloaded games on the SD card using a hex editor. Im just wondering.

no, because the saves are not signed
 
And what does that mean? (I'm a noob)
Every eShop related files are signed (encrypted). You'd need a console unique key to decrypt them.
Tho it could theoretically work if you own both versions and use the official software to transfer files between eShop- and retail games
 
  • Like
Reactions: Zidapi
Every eShop related files are signed (encrypted). You'd need a console unique key to decrypt them.
Tho it could theoretically work if you own both versions and use the official software to transfer files between eShop- and retail games


Is there any way I can retrieve my console's key?
 
And what does that mean? (I'm a noob)
Signing a file generates a long hex number that is used to verify that a given file has not changed. Any time a single bit in a file changes, the signature completely changes. This allows an OS to check for tampering. (in this case, the 3ds knowing you've been screwing with it's saves)
This signing process (and encryption) must be done on a 3ds because the algorithim to sign files lies hidden somewhere on the 3ds SOC most likely.

You can get around this be using the savedatafiler dev tool to decrypt and modify saves (it's warez - can't link here). Google for it and how to use it.
 
Signing a file generates a long hex number that is used to verify that a given file has not changed. Any time a single bit in a file changes, the signature completely changes. This allows an OS to check for tampering. (in this case, the 3ds knowing you've been screwing with it's saves)
This signing process (and encryption) must be done on a 3ds because the algorithim to sign files lies hidden somewhere on the 3ds SOC most likely.

You can get around this be using the savedatafiler dev tool to decrypt and modify saves (it's warez - can't link here). Google for it and how to use it.


You know I can't install CFW on my N3ds right?
 
Well there isn't, I have a save that don't load up corrupted. But link spawns in a void a and the game crashes unusefully.
 

Site & Scene News

Popular threads in this forum