Good response, Just makes sense to me to deny the code as quickly as possible if it wasn't true, which I haven't seen from them yet for myself.
Hacking Gateway will fix any bricked 3DS for free, as long as you're not lying!
- Thread starter Soul_Alchemist
- Start date
- Views 104,685
- Replies 711
- Likes 3
Yes, if they deny it and it's true; they've killed their credibility and future sales. If they don't end up denying it it's likely because someone
They carefully make sure not to mention it. Make of that what you will.
No, some well known hackers (plural) said it is indeed a bricking code.
Reread my post. I'm not denying that people's console got bsod. I'm saying that we don't know what's causing the bsod. You already came to a conclusion without thinking about other possibilities. Your quick to point the finger without lifting a finger. Anything can happen when you use unofficial software/hardware. This goes for both Gateway and Clones.
You're acting like Gateway didn't do shit, when it's already been confirmed that they planted a bomb in their firmware.
Stop fanboying so much, please.
If gateway continues this way i'll play all the games i want which i can run with 1.2 or 2.01b then sell the card someone else who understands the risks and wait for another card, MT card possibly till ninty starts selling their products again in my country. I would have never thought i'd regret buying gateway this soon. To soon.
Thanks for the nickname. I'll use it proudly.
Now show me this alleged confirmation of the "bomb" in the firmware. And please don't quote others as fact. That's hearsay.
- Joined
- Oct 24, 2002
- Messages
- 2,954
- Trophies
- 2
- Age
- 44
- Location
- England U.K.
- Website
- www.gbatemp.net
- XP
- 867
- Country
i really cannot believe the things you lot are allowed to get away with on these message boards now....
i hope you dont act the same way in real life as you do on here
i hope you dont act the same way in real life as you do on here
Thanks for the nickname. I'll use it proudly.
Now show me this alleged confirmation of the "bomb" in the firmware. And please don't quote others as fact. That's hearsay.
Even if the hackers decompile all the 1.8 mb of code included on launcher.dat, de-obfuscate the decompiled code, highlight the codes that does the bricking job, explains how it works, most people - some commercial programmers included - won't understand what's happening there. It's low level programming that we're talking here, direct access to some controllers included on 3DS.
Algorithm wise it can be as simple as:
Check launcher.dat checksum
if checksum not equal expected checksum
go to end
if checksum equal expected
start 3ds_sys_menu_hacking routines
...
if( random_time and checksum for a portion not expected )
give eMMC controller size = 0
zero eMMC from pos_1 to pos_2
end-if
...
But the actual implementation will never be as simple as this, and maybe because of this, the launcher.dat file from gateway is bricking consoles, because it's not simple, and some bugs or situations escaped from the gateway's testers radar. And I'm trying to think about the bright side of this bricking code situation.
Also some of the "others" that found the bricking codes in gateway files are actually people that handles these kind of programs - console bricking codes included - from a long time.
There's not going to be another card unless someone finds a new exploit that works past 4.5--the user base for 4.5 is slowly shrinking and in a few months to a year it will be pointless to sell any devices that require a max firmware of 4.5.
If they found the imaginary bricking code test then they could amend the call to display something on the screen instead of reprogramming eMMC controller - then release this launcher.dat for everyone to use.
They haven't found the imaginary bricking code test though.
So they can't do that.
So they should shut the fuxk up
That's BS. They have no way to know that that's the only bricking code in there. It would be irresponsible to replace that code with a message when they have no way to know that there's not some other bricking code that they haven't found yet and which could trigger when the first code is removed.
Yeah that's the usual evasive shit argument being played for the last week
FUD spreading - that's what it is
http://en.wikipedia.org/wiki/Fear,_uncertainty_and_doubt
Gateway have introduced code to prevent accidental system updates - probably involves eMMC reprogramming - maybe the reprogramming is supposed to be reset when you exit emuNand - but they missed corner cases (when the console is put to sleep at a certain moment for example) - where the reset call doesn't get executed - that's also me guessing - but I think my guessing is better than the shit guessing that we've had so far to explain the (small number of) bricks happening with clones PLUS gateway cards
Actually, it is now clear the meat of or at least some crucial details about the nature of the brick have been unaccurately reported and (of course) repeated.
Now, this means we must call into question the expertise of those who described (informally) what the supposedly intentional brick code actually does.
It is now clear from testing that the controller actually still reports the right size for the nand, so at least this detail was either totally made up, or whoever thought the brick did do after analyzing it isn't as skilled as they thought they were and claim to be.
Either way, it means we can not implicitly trust that these "respected devs" who had made the claims are infallible. Indeed, we must reject that in light of the fact that they were wrong about the nature of the brick (code).
Now, this means we must call into question the expertise of those who described (informally) what the supposedly intentional brick code actually does.
It is now clear from testing that the controller actually still reports the right size for the nand, so at least this detail was either totally made up, or whoever thought the brick did do after analyzing it isn't as skilled as they thought they were and claim to be.
Either way, it means we can not implicitly trust that these "respected devs" who had made the claims are infallible. Indeed, we must reject that in light of the fact that they were wrong about the nature of the brick (code).
Gateway auto-boots into Emunand, why is an anti-update code needed for it? Isn't the main point of emunand to update it? I don't think that guess is an accurate one.
Hi justinkb
I think you are correct - and I was wondering how long it would take for some one to actually test the claims about the NAND size being recognised as zero.
Where did you read that btw?
The gateway people themselves posted that they were trialing anti-update code - which was causing bricking (oh wow - that sounds familiar) - they said on their website that the code wouldn't be released to the public until 100% safe - maybe they released it too early - or maybe they released what they thought was a safe subset of the code which appeared in all their tests to be ok. - but they forgot that 3DS pirate yoofs shut their consoles off in all sorts of arbitrary ways and in arbitrary situations - that their testing suite didn't cover
