The exploit is run using the installer.nds......all your other card specific files remain the same
games that need 7.0 will need time to come out ? since I guess they couldn't change the update they need working in mid development ? or can they?
Would it be possible to just change the flag for 7.x keys, if the FW is patched to accept modified files
Or are the 7.x keys actually used to decrypt the game/apps
And now it begins. No flashcard company can do a shit against that. They would need to decap the SoC, which i don't think they will do. The part of the NATIVE_FIRM, which generates the key for that, is in internal memory and therefore not even a RAM dumping setup do a shit here.
Nintendo did his homework this time. As long, as the system is secure against exploits, there is no chance. Currently it doesn't look like there is anything exploitable...
Yep, all because of the GatewayWhy not? They have enough money for that, and if they do it, they could find new exploits and make more money.
And now it begins. No flashcard company can do a shit against that. They would need to decap the SoC, which i don't think they will do. The part of the NATIVE_FIRM, which generates the key for that, is in internal memory and therefore not even a RAM dumping setup do a shit here.
Nintendo did his homework this time. As long, as the system is secure against exploits, there is no chance. Currently it doesn't look like there is anything exploitable...
Actually, you don't need to dump the generated key from ram, if you can read/write to memory all you need is to gain code execution by patching instructions before the ones that clear the keyslot is executed, then you simply use your own code to generate the key and output it to wherever.
That's assuming you do have a working hardware RAM setup.
Why not? They have enough money for that, and if they do it, they could find new exploits and make more money.
[...] so, for those that care about pokebank and are on emunand, you won't get to use your free month unless you use another 3DS.
And then Nintendo releases 8.x which uses a different key and fixes the exploitThe only way I can see to get around this problem is for someone to make a CFW (which is far, FAR away). It would need to be based off of 7.X and yet be able to run unsigned code.
Its going to be a LOOOOOONG wait.
That is unless an exploit is found for 7.X+, lol.
It's almost guaranteed to have the same issue considering it came out after the EU one.Can some one check the us pokebank app now that it's out?
You would be able to transfer from BW2->Bank yeah, but Bank->XY requires Bank to read the XY save data. If said save data was created with 4.X chances are very high it will read as corrupt on 7.1 realNAND, and even if it doesn't, after you save the save file will be corrupt on 4.X. And then there's the protection that prevents you from messing with save files that may trigger if you restore NAND.or, if someone can confirm that it would work, do the following:
mount the hardware mod;
backup the 4.x realnand;
update realnand to 7.x;
download the pokebank;
transfer the pokes from BW/BW2 to the global link (and I assume we don't need the X/Y cartridge at all to do it);
backup the 7.x realnand for the future;
restore the 4.x realnand;
enter X/Y in emunand and transfer the pokes into the game.