- Joined
- Apr 22, 2012
- Messages
- 3,595
- Trophies
- 1
- Age
- 41
- Location
- Somewhere, out there...
- XP
- 3,184
- Country
The last one will actually get released soon.Gaytewait features list:
-We are working on GBA/DSi VC game support and should be released soon
-We are working on cheat support and should be released soon
-We are working on 9.5+ EmuNAND for N3DS and should be released soon
-We are working on a brick code for DSTwo+ users and should be released soon
GAYTEWAIT Team
Yeah but it's not the feature that everybody is still waiting for... :/ I think cheat support and 9.5+ Emunand is priorityThe last one will actually get released soon.
Gaytewait word is homophobic content for you??@Keylogger Reported for homophobic comment
Gateway Cheat support is still coming soon. I emailed them asking for an ETA, they actually said any day now (as of today) and are in the final step of testing it
I seriously hope for DSi/GBA support, I could care less about Cheats since Save Editors are like tortillas now.
9.5+ Emunand for N3DS users would be really incredible, but a long shot, so I say that will still wait quite some time.
I'm sure they have.Has any CFW dev been looking into this? support for emunand +9.5?
First two are possible with CFW already.Gaytewait features list:
-We are working on GBA/DSi VC game support and should be released soon
-We are working on cheat support and should be released soon
-We are working on 9.5+ EmuNAND for N3DS and should be released soon
-We are working on a brick code for DSTwo+ users and should be released soon
GAYTEWAIT Team
Of course it's encryption related, Nintendo would have to make a major fuck up for anyone to obtain the new keys.I'm sure they have.
But nothing so far, I think it might have something to do with the new encryption or something related to it.
Watch someone build a real Filsamech and infiltrate NOA.Of course it's encryption related, Nintendo would have to make a major fuck up for anyone to obtain the new keys.
But it will still eat your battery because it's a DSTwo.Gateway better get on top of this.
With the DSTWO+ having support for 3DS/DS/GBA/SNES, they are at a huge loss here.
If they manage to come up with a way to block the DSTWO+, they will block 3DS support entirely for the card, which will make the DSTWO+ more like a normal DSTWO.
I even say that I am tempted to get a DSTWO+ support just because of the 3DS/DS combo.
That way I could finally have only one flashcard in my 3DS inserted at all times and enjoy whatever the fuck I want without switching it.
I'm sure they have.
But nothing so far, I think it might have something to do with the new encryption or something related to it.
The arm9loader was updated.
Old version of firm generated and initialized keyX for keyslots 0x15, 0x16, 0x18-0x1F. This version keeps the old algorithm for keyslots 0x11, 0x15, 0x18.
For keyslots 0x16, 0x19-0x1F it uses a new key for keyslot 0x11, but the actual algorithm has not been changed. This time the keyslot 0x11 seed is loaded from (nand_sector96+0x10) instead of (nand_sector96+0). They also changed the initialization vector for the 0x19-0x1F key-generation to a new hardcoded key.
Since we don't know the decrypted value at (nand_sector96+0x10), we don't know the new key for keyslot 0x11, and we cannot generate keys for the updated keyslots 0x16, 0x19-0x1F. Thus they plugged their hole and we can no longer decrypt arm9-binary without an arm9 code-execution exploit compatible with 9.6.0-X or <tricks where some of these *require* nand-modding>.
On panic, arm9loader now clears keyslots 0x15, 0x16, 0x18, 0x19, 0x19-0x1F. Previous versions only cleared 0-7, 0x15, 0x16.