2007/8 isn't exactly newly created in my book. Are they bribing random forum members now, too?
Under 30 posts on each of those accounts. And yours is rather low too, how odd...
2007/8 isn't exactly newly created in my book. Are they bribing random forum members now, too?
some of these posts are completely unrelated, instead about nand dumping soldering leading to bootrom errors.
Under 30 posts on each of those accounts. And yours is rather low too, how odd...
No, they aren't. Read again.
More posts:
http://gbatemp.net/threads/help-wit...r4i-deluxe-3dslink.360502/page-3#post-4883307
http://gbatemp.net/threads/help-wit...r4i-deluxe-3dslink.360502/page-3#post-4883496
Should be enough for now.
Yeah I'm one of them, how did you not know?
Under 30 posts on each of those accounts. And yours is rather low too, how odd...
Except that non-pirates who used neimods launcher.dat to play legitimate games region-free are also affected.
So you are saying that Neimod created Gateway clone?
nope, not the clones, they are damaged by this news too. the third, new player on the flashcard scene.
how did you not know?

Let's' cut through the analysis
You seem to be a dick
I think you guys are confusing Normmatt with Neimod. Normmatt made the region-free patches not Neimod (totally different person, infact he is anti piracy).
No, they aren't. Read again.
More posts:
http://gbatemp.net/threads/help-wit...r4i-deluxe-3dslink.360502/page-3#post-4883307
http://gbatemp.net/threads/help-wit...r4i-deluxe-3dslink.360502/page-3#post-4883496
Should be enough for now.
Yeah I'm one of them MT shills, how did you not know?
Neimod (totally different person, infact he is anti piracy).
Since people don't quite know how to read, the "bricking code" doesn't care about the sum of your Launcher.dat, it checks the sum of ARM9 payload in memory. Granted its being loaded through a large ROP chain and rather unstable exploits, think about about this. There have been about ~30 reports of bricked consoles from clone cards (due to bricking only happening when a random number generator says so). Out of ALL of the times people have booted their clone cards since the latest firmware, there have been ~30 (reported) bricks.
Now think about the odds of the ARM9 payload originating from an unmodified GW launcher not matching the intended sum, and the odds of the "bricking code" deciding to check the payload the one time your payload doesn't match.
Just my two cents.
Hum... actually they have a sanity check I forgot about within their ROP chain as they perform a checksum before the payload runs and the bricking happens, so it cannot run a corrupted payload from a Launcher.dat, thus the code causing the brick cannot run as-is from the original Launcher.dat file if that one was to be corrupt.
sha256_update(0x002B3344, 0x002B3924, 0x00000BAC);

Ah screw this. I actually meant normatt's launcher.dat. Fixed it in my post.I think you guys are confusing Normmatt with Neimod. Normmatt made the region-free patches not Neimod (totally different person, infact he is anti piracy).
the claim being made here however is much stronger than that, namely that this is a cynical, malicious move from Gateway, instead of a consequence of the complexity of producing (by GW) and adapting (by cloners).
Since people don't quite know how to read, the "bricking code" doesn't care about the sum of your Launcher.dat, it checks the sum of ARM9 payload in memory. Granted its being loaded through a large ROP chain and rather unstable exploits, think about about this. There have been about ~30 reports of bricked consoles from clone cards (due to bricking only happening when a random number generator says so). Out of ALL of the times people have booted their clone cards since the latest firmware, there have been ~30 (reported) bricks.
Now think about the odds of the ARM9 payload originating from an unmodified GW launcher not matching the intended sum, and the odds of the "bricking code" deciding to check the payload the one time your payload doesn't match.
Just my two cents.
Hum... actually they have a sanity check I forgot about within their ROP chain as they perform a checksum before the payload runs and the bricking happens, so it cannot run a corrupted payload from a Launcher.dat, thus the code causing the brick cannot run as-is from the original Launcher.dat file if that one was to be corrupt.
sha256_update(0x002B3344, 0x002B3924, 0x00000BAC);
Mathieulh just debunked it:
So GW team has a sanity check that will not brick if you have a corrupt SD. That looks good to me.
I think that is beginning to explain why only clones are getting affected... GW Engineers are professionals xD
The suggestion that the respected Gateway team would put code in their firmware which deliberately reprograms the eMMC controller so the nand can't even be reflashed (via usual hardware methods posted here and elsewhere on the internet) is RIDICULOUS and very likely UNTRUE
It hardly seems like a consequence when it started happening all at once, how long again? after the firmware was released. Also if I'm not mistaken, there were reports from people who tried to flash their NAND backup back and failed (obv. there could still be other reasons for that)
Would you care to explain what this means in an easiest way, please?
Are you saying that, if the original/unmodified Gateway's launcher happens to get corrupted while being on the SD card, the brick can't occur due to this "sanity check"?
No. You could still have a corruption (or modification) in the ARM9 payload that runs afterwards and which is the one checked to decide between {} and {brick();}.