Hardware 3DS updated to 8.0.0

[Snailface]

http://www.3dbrew.org/wiki/8.0.0-18

"masterkey.bin"

Nintendo has to be trolling now.

 

[Coto]

This update is a big middle finger from nintendo to gateway.

 

[Thirty3Three]

This update is a big middle finger from nintendo to gateway.

How so?

 

[phanteon]

http://www.3dbrew.org/wiki/8.0.0-18

"masterkey.bin"

Nintendo has to be trolling now.

no 8.x encryption found this far, right?

 

[Snailface]

no 8.x encryption found this far, right?

No, but the unhacked 7.1 sdk encryption is spreading like cancer throughout the system.

 

[Coto]

How so?

Critical run-time (booting, return to) home menu modules are signed, with a fake encryption 4.5< units won't boot up at all, or wil have sporadic freezes.

 

[Thirty3Three]

Critical run-time (booting, return to) home menu modules are signed, with a fake encryption 4.5< units won't boot up at all, or wil have sporadic freezes.

Interesting. So you're saying this affects users using emunand, attempting to boot into the latest firmware via emunand?

 

[Coto]

Interesting. So you're saying this affects users using emunand, attempting to boot into the latest firmware via emunand?

Well i'm saying what's listed on 3dsbrew. But yes, that is mostly correct.

 

[VMM]

I see people talking about using a new encryption key, but why would Nintendo do that if the encryption used on 7.2 hasn't been cracked yet?

 

[Tomobobo]

Nintendo can easily change their keys so they might as well do it to try and thwart homebrew and piracy. Also hacking teams aren't the only people looking for exploits. If nintendo finds and patches a hole that's a lot better than letting someone else find it.

 

[Apache Thunder]

From what I can see on 3DBrew:

Due to ErrDisp being updated, this likely breaks booting 8.0.0-18 on physical <=v4.x systems where the key-data for the v7.0 NCCH crypto wasn't initialized correctly.

Whether or not this impacts Gateways announced fix for 7.x games and eshop/settings menu remains to be seen. It all depends on how they fixed it. If they simply figured out the new keys and used the same system as before, then they are SOL with this and need to find a while new fix for this problem.

If they actually managed to "initialize" the keys correctly instead of relying on the 4.5 keys to boot the emunand, then it's a non-issue. But I don't think this is the case. Smealum could chime in on this. He developed his own Emunand so he might better know what the implications are. We might not really know for sure until Gatway responds.

 

[b17bomber]

I was able to dump an 8.0 nand with my hard mod and splice it into emunand. I can confirm emunand 8.0 will not load.

 

[bartimeaus91]

Due to ErrDisp being updated, this likely breaks booting 8.0.0-18 on physical <=v4.x systems where the key-data for the v7.0 NCCH crypto wasn't initialized correctly

Correct me if I am wrong, this seems to mean that booting emuNand 8.0.0-18 won't work on 4.x systems. BUT.. this is only applicable if v7.0 NCCH crypto was still not fixed. In essence, with GW2.2 you could have booted into emunand 7.2 with settings and eshop not working but if you now try to boot into emunand 8.0, it won't boot at all.



In Gateway's latest post, they said they have

We have recently reached a major milestone regarding the 7.x encryption. We can say with certainty that we will soon be running 7.x games and 7.x applications

So this would mean that it would solve the issue of booting into emuNand 8.0 as well right?

 

[Apache Thunder]

Well that depends on the technical details, which of coarse Gateway won't divulge yet. Does the 6x games use different keys then the the games prior to v5 or v4?. If so, whatever they did to make them work on 7/7.1 won't work for v8 and the entire emunand will remain unusable. Currently Emunand is needed for having the latest firmware benefits without actually having the latest version properly installed. So this is definitely something designed as a direct response to Gateway's emunand.

 

[bartimeaus91]

Well that depends on the technical details, which of coarse Gateway won't divulge yet. Does the 6x games use different keys then the the games prior to v5 or v4?. If so, whatever they did to make them work on 7/7.1 won't work for v8 and the entire emunand will remain unusable. Currently Emunand is needed for having the latest firmware benefits without actually having the latest version properly installed. So this is definitely something designed as a direct response to Gateway's emunand.

AFAIK, the 6.x games didn't really use different NCCH keys, they used different KeyY keys which affect the save file.

So technically since GW said they will be getting the eShop and games working, that would mean they have found a way to fix the 7.0 NCCH keys which would result ability to boot emuNand 8.0

 

[Rinnux]

I'm not too worried about this. Even if this does mean the death of gateway, it's not like there is a shortage of games available to us.

 

[GamerzHell9137]

Guess Nintendo doesn't care about DS flashcards anymore, its about gateway now and nothing else.

 

[b17bomber]

Would some of the "hidden stuff" have anything to do with what Square-Enix just revealed? Dragon Quest X will be completely loaded from the cloud.

http://www.gonintendo.com/s/232679-...treaming-version-of-the-game-pricing-detailed

 

[CFallenleaf]

Im curious about the masterkey.bin...... If its what it sounds(emphasis on sounds cause who knows what it really is) like it is did nintendo just fuck up?

 

[magypsy3]

Now if gateway manages to fix this all I will really be impressed.