Hacking GW: Status update 7.X Games

  • Thread starter Thread starter Deleted User
  • Start date Start date
  • Views Views 23,032
  • Replies Replies 98
  • Likes Likes 10
as soon as i get eshop access back i'm going to download every single update patch for every single game hahaha :)

Just curious... Recently, I launched Gateway Menu and it asked me to update the card, and so I did. Has anyone else gotten the same thing? The update didnt make any noticeable changes and it didnt fix the 7.x encryption.
hi broski, if you ran the 2.1 omega firmware (if you put that launcher.dat on your big sd card) then yes, your gateway would have told you to update the gateway card.

the 7.x encryption is not broken yet, as in, this news says they will release that soon :) so wait a bit :) maybe a month or two, maybe less
 
  • Like
Reactions: Herobroski
as soon as i get eshop access back i'm going to download every single update patch for every single game hahaha :)


hi broski, if you ran the 2.1 omega firmware (if you put that launcher.dat on your big sd card) then yes, your gateway would have told you to update the gateway card.

the 7.x encryption is not broken yet, as in, this news says they will release that soon :) so wait a bit :) maybe a month or two, maybe less
That makes no sense because I placed the 2.2 omega firmware on the sd card. Im using the 2.2 version. And today it randomly asked me to update.
 
That makes no sense because I placed the 2.2 omega firmware on the sd card. Im using the 2.2 version. And today it randomly asked me to update.

You were holding the "R" button when you entered Gateway mode. It brings up the update gateway screen regardless if you updated or not.
 
There's one thing that's going to plague all users: If you used a game that takes use of the 7.X keys, like Pokémon X/Y, and you go play it on the 7.2 emunand once the fix is released, you'll have to wipe your save and restart because the keys won't match.
 
There's one thing that's going to plague all users: If you used a game that takes use of the 7.X keys, like Pokémon X/Y, and you go play it on the 7.2 emunand once the fix is released, you'll have to wipe your save and restart because the keys won't match.

Well if they found away of getting 'through', far enough to getting the game to work; ie: finding some sort of entry point without changing the keys - as in getting these games to run without changing the keys, then the saves will work. Who knows how they've counteracted the protection, eh?
 
There's one thing that's going to plague all users: If you used a game that takes use of the 7.X keys, like Pokémon X/Y, and you go play it on the 7.2 emunand once the fix is released, you'll have to wipe your save and restart because the keys won't match.

That's been there since 6.x-save games are supported IIRC. It's a problem with the save encryption, not the ROM encryption I think.
 
There's one thing that's going to plague all users: If you used a game that takes use of the 7.X keys, like Pokémon X/Y, and you go play it on the 7.2 emunand once the fix is released, you'll have to wipe your save and restart because the keys won't match.
Not necessarily, yeah. If they do something about only the rom encryption and leave the save encryption as it currently is, it should be fine. The keys used for that are different.
 
I don't think that's right. Wouldn't that make people on legit firmwares also need to wipe their saves. That would be unacceptable...
 
People who played X/Y on 6.1 firmware don't suddenly lose their save when they update the console to 7.2. I don't think this will become an issue. It's only when you try to play a game that saved while on 7.2 on a older firmware like 4.5 that causes problems.

Just note that if you save your games on the future Gateway update that fixes this, this would mean not being able to play the game again on older Gateway versions without losing your save. That's assuming Gateway also figured out how to use newer save encryption in emunand that don't rely on the base 4.5 firmware it was booted from. Otherwise the current situation with save files doesn't really change.

Which means if you save your game while on 7.2+ emunand firmware, you still lose the save if you try to play the game that is on a legit 7.x firmware. As in a console that had been properly updated to 7.2+.
 
People who played X/Y on 6.1 firmware don't suddenly lose their save when they update the console to 7.2. I don't think this will become an issue. It's only when you try to play a game that saved while on 7.2 on a older firmware like 4.5 that causes problems.

Just note that if you save your games on the future Gateway update that fixes this, this would mean not being able to play the game again on older Gateway versions without losing your save. That's assuming Gateway also figured out how to use newer save encryption in emunand that don't rely on the base 4.5 firmware it was booted from. Otherwise the current situation with save files doesn't really change.

Which means if you save your game while on 7.2+ emunand firmware, you still lose the save if you try to play the game that is on a legit 7.x firmware. As in a console that had been properly updated to 7.2+.

We'll just have to wait and see. Kinda of hoping they will have save key cross compatibility. Like 6.x keys working while at the same time allowing for previous games that were saved with 4.x to work as well. Or 3dz and 3ds save compatibility.


**************************************************************************************

"There’s a bunch of other (interesting) developments going on besides the 7.x encryption fix at the moment"

Maybe eshop dump ability? There's this new eRip person. Perhaps he's part of GW in some way. Idk. Just randomly guessing.
 
Because the new encryption can only be used by games that are compiled with SDK7+ from what I know.

In theory they can use the new encryption on any content, even content compiled/built with older SDKs, after all it's just the matter of a NCCH flag.
In practice it seems that for whatever reason, Nintendo has only been encrypting content compiled/built with SDK 7+ with the new keys, why ? No idea but it's not a technical limitation.
 
In theory they can use the new encryption on any content, even content compiled/built with older SDKs, after all it's just the matter of a NCCH flag.
In practice it seems that for whatever reason, Nintendo has only been encrypting content compiled/built with SDK 7+ with the new keys, why ? No idea but it's not a technical limitation.


I always found that strange. I'd have thought they'd enforce the new 7.x NCCH encryption on all new games but as you said they seem to tie it to the sdk version for some unknown reason.
 
I always found that strange. I'd have thought they'd enforce the new 7.x NCCH encryption on all new games but as you said they seem to tie it to the sdk version for some unknown reason.

Could be they're charging more for an "AP SDK".
 
Maybe it's because of the time it takes to manufacture cartridges. They have to finalize the ROM several months before release, and the SDK thing was just a coincidence.
 

Site & Scene News

Popular threads in this forum