ROM Hack [Release] 3DS_CTR_Decryptor-VOiD

  • Thread starter Thread starter Relys
  • Start date Start date
  • Views Views 649,146
  • Replies Replies 2,226
  • Likes Likes 30
what is the difference of this decryptor and previous? Anyway someone cna upload a .exe or something, i don't know how to complie XD
 
Exactly! The system is fully open now. :) Nothing left to decrypt.
Also, does this mean that we can finally decrypt DSiWare? If so, from the SD decryptor, or the Title Key decryptor?

In relation to the signature checks, is there anything in the NAND or firmware that can be edited to disable them? If so, it might mean that real CFW could finally be possible!
 
  • Like
Reactions: The Cringe
Also, does this mean that we can finally decrypt DSiWare? If so, from the SD decryptor, or the Title Key decryptor?

In relation to the signature checks, is there anything in the NAND or firmware that can be edited to disable them? If so, it might mean that real CFW could finally be possible!
pretty sure trying to write a modded FW to sysnand would just brick your console, unless there is some sort of early on exploit triggered
 
pretty sure trying to write a modded FW to sysnand would just brick your console, unless there is some sort of early on exploit triggered
How about writing a modded firmware to the emuNAND? Or would that just lead to a black screen after loading it from the Gateway menu like the newer firmwares before the 7.x keys were implemented?
 
  • Like
Reactions: The Cringe
How about writing a modded firmware to the emuNAND? Or would that just lead to a black screen after loading it from the Gateway menu like the newer firmwares before the 7.x keys were implemented?
tbh im probably not the best guy to ask....but i assume gateway are now modding the emunand nand partition as emunand will no longer work if flashed to sysnand.....so im assuming the disabled signature checks probably extend to emunand too.....but as i said im probably not the most informed on the current capabilities etc
 
Also, does this mean that we can finally decrypt DSiWare? If so, from the SD decryptor, or the Title Key decryptor?

In relation to the signature checks, is there anything in the NAND or firmware that can be edited to disable them? If so, it might mean that real CFW could finally be possible!
DSi-downloaded DSiWare can be decrypted, but 3DS-downloaded DSiWare can't (yet).
 
Thanks for this release. I only have one thing to ask the local Python tamers: please, modify the scripts to add a selection for the output: only 3ds, only cia (not implemented at all yet), both. It would be much appreciated.
I have just tested all the new stuff and successfully built .3ds right from Nintendo’s CDN. Magnificent.
 
  • Like
Reactions: cearp
Thanks for this release. I only have one thing to ask the local Python tamers: please, modify the scripts to add a selection for the output: only 3ds, only cia (not implemented at all yet), both. It would be much appreciated.
I have just tested all the new stuff and successfully built .3ds right from Nintendo’s CDN. Magnificent.

yes, having cia output is very important!
this is amazing right now, but some things should natively be 'cia' i believe, like eshop stuff.
having a choice to output 3ds/cia, or both would be great.

maybe it is as simple as changing the makerom command found in the python script -
mRomCmd = 'makerom -f cci -rsf rom.rsf -o ' + titleid + '.3ds -nomodtid'


also in the python script, i see this on line 132...
romrsf4 = '\n\nSystemControlInfo:\n SaveDataSize: 512KB\n'

the save file for card 2 games is always set to 512KB?... that's not true... right? or am i missing something?
 
  • Like
Reactions: octopus
also in the python script, i see this on line 132...
romrsf4 = '\n\nSystemControlInfo:\n SaveDataSize: 512KB\n'

the save file for card 2 games is always set to 512KB?... that's not true... right? or am i missing something?


That line is only used when card1 is set. Like the comment says at the top, the scripts are shitty and hard to follow. I hacked them together early on and never cleaned them up.

EDIT: It doesn't actually affect the save size, IIRC. It's just to stop makerom from complaining. But I'm not 100% on that, it's been a while since I've looked at this stuff.
 
  • Like
Reactions: cearp
so makerom wants A savesize, but it doesn't make a different to what it is?
don't you ever need the 'stack size' in your rsf? i found updates were fine without an rsf, the only eshop game i tried needed save size, and the 1 app i tested needed save size AND stack size
 
so makerom wants A savesize, but it doesn't make a different to what it is?
don't you ever need the 'stack size' in your rsf? i found updates were fine without an rsf, the only eshop game i tried needed save size, and the 1 app i tested needed save size AND stack size
CCI creation can be kinda troublesome because of that. It's would be easier to create CIAs.
 

Site & Scene News

Popular threads in this forum