Homebrew Clarification Thread - What is going on?

[Nikki_swap]

‏@JustPingo
Everything is gonna take a little but longer as I have to write a motherfucking unexpected ROP.

From Pingo's Twitter

if you keep doing that, you will have a bad time,

 

[Mrrraou]

‏@JustPingo
Everything is gonna take a little but longer as I have to write a motherfucking unexpected ROP.

From Pingo's Twitter

That's for snshax.

 

[Adrien835]

Who told you about this ? If it's not one of the developers, then it's not true.

tmtc normaly

 

[demonotaku]

That's for snshax.

Still more information then what Days meant; its the only information I can actually find

 

[Mrrraou]

tmtc normaly

Bah j'aimerais bien savoir quand même, pour que je puisse confirmer si l'info est vraie. But if the source is not trustworthy or doesn't know anything at all about it, then I don't know why it should be trusted.

 

[dankzegriefer]

Keep ROPing.

--------------------- MERGED ---------------------------

Bah j'aimerais bien savoir quand même, pour que je puisse confirmer si l'info est vraie. But if the source is not trustworthy or doesn't know anything at all about it, then I don't know why it should be trusted.

English?

 

[PixelTheKWolf]

Uh..does anyone mind telling me what is going on? no offense, ive just been out of the loop for a while. mind expaining whats going on, someone? and yes, i just read the main threat

 

[Mrrraou]

Keep ROPing.

--------------------- MERGED ---------------------------


English?

"I would still like to know, so I can check that info with the devs."

 

[demonotaku]

Uh..does anyone mind telling me what is going on? no offense, ive just been out of the loop for a while. mind expaining whats going on, someone? and yes, i just read the main threat

Absolutly nothing; except SNSHax got delayed due to a ROP needing to be made, Gateway claiming they are working on a exploit and the 3 developers working on there version of the memchunkhax2 exploit

 

[PixelTheKWolf]

Absolutly nothing; except SNSHax got delayed due to a ROP needing to be made, Gateway claiming they are working on a exploit and the 3 developers working on there version of the Nun2 exploit

Ah, thanks for explaining.

 

[Mrrraou]

Absolutly nothing; except SNSHax got delayed due to a ROP needing to be made, Gateway claiming they are working on a exploit and the 3 developers working on there version of the memchunkhax2 exploit

Well actually, 4.

 

[demonotaku]

Well actually, 4.

4? I been loosing track of Developers after Steveice10 joined

 

[PixelTheKWolf]

Well actually, 4.

Wait, so all four people are working on 4 different versions? i understand the different 3ds versions, but are they using the same source or something along those lines?

 

[Mrrraou]

4? I been loosing track of Developers after Steveice10 joined

TuxSH, julian20, mid-kid and Steveice10. Working together.

 

[Deleted-236924]

I've got a question, if emunand 9.6 or higher cannot happen after all, what happens to 9.6+ support for GW on N3DS?
If their fix is to let their users downgrade then I understand why emunand 9.6 or higher wouldn't be possible. But if they are truly running completely off 9.3-10.3 without having to downgrade, then what happens to N3DS users on 9.6+?
Maybe it's possible to get emunand 9.6+ to work but only if sysnand is also 9.6+?

From 3dbrew:

If the error was fixed in 9.5, then wouldn't that make it impossible to have emunand 9.5 or higher? As of right now we're able to have emunand 9.5 it's just 9.6+ that won't work.
Surely it must have been something that changed in 9.6 and not 9.5, unless thing don't work the way I think they do.

maybe, they will use this entrypoint for the downgrade stuff

Not a .nds, but maybe as a flashable firmware.

Please read the OP.

Is the blue card even firmware-updateable? GW's "solution" to running the blue card on higher firmwares was to get their users to install the oldest version of TWL whitelist, couldn't they just have made a firmware update for blue card to make it work on higher firmwares?

Of course an user who only has a higher firmware 3DS wouldn't be able to run the blue card to update it, but then again so would 9.3-10.3 users.

Or maybe it -can- be updated and GW was just too lazy to make a firmware update for it because downgrading TWL whitelist works the same.

 

[Mrrraou]

I've got a question, if emunand 9.6 or higher cannot happen after all, what happens to 9.6+ support for GW on N3DS?
If their fix is to let their users downgrade then I understand why emunand 9.6 or higher wouldn't be possible. But if they are truly running completely off 9.3-10.3 without having to downgrade, then what happens to N3DS users on 9.6+?
Maybe it's possible to get emunand 9.6+ to work but only if sysnand is also 9.6+?


If the error was fixed in 9.5, then wouldn't that make it impossible to have emunand 9.5 or higher? As of right now we're able to have emunand 9.5 it's just 9.6+ that won't work.
Surely it must have been something that changed in 9.6 and not 9.5, unless thing don't work the way I think they do.




Is the blue card even firmware-updateable? GW's "solution" to running the blue card on higher firmwares was to get their users to install the oldest version of TWL whitelist, couldn't they just have made a firmware update for blue card to make it work on higher firmwares?

Of course an user who only has a higher firmware 3DS wouldn't be able to run the blue card to update it, but then again so would 9.3-10.3 users.

Or maybe it -can- be updated and GW was just too lazy to make a firmware update for it because downgrading TWL whitelist works the same.

It was totally fixed in 9.6. And no, sysNAND 9.6+ doesn't mean you can have 9.6+ emuNAND.
I don't really know if it's upgradable or not. And I think it was easier for them to release bluecardfix.cia

 

[julian20]

TuxSH, julian20, mid-kid and Steveice10. Working together.

That's right and i will now finally go sleep

 

[Yami_Industries]

can someone give me an update on whats going on with memchunkhax2 or is a recent update of whats happening on the first post?

 

[Aroth]

If the error was fixed in 9.5, then wouldn't that make it impossible to have emunand 9.5 or higher? As of right now we're able to have emunand 9.5 it's just 9.6+ that won't work.
Surely it must have been something that changed in 9.6 and not 9.5, unless thing don't work the way I think they do.

It was totally fixed in 9.6. And no, sysNAND 9.6+ doesn't mean you can have 9.6+ emuNAND.

The change to clear the keyslots was implemented in 9.5, but that wouldn't have any effect on us since we already knew the keys from when they were leaked. What 9.6 changed was the introduction of a completely new keyslot with a new key that we do not know yet, and because 9.5 made the keyslots clear immediately after they were used we are unable to just read/grab them.

 

[probablygay]

can someone give me an update on whats going on with memchunkhax2 or is a recent update of whats happening on the first post?

heres an update just wait