I have nothing to prove, I await the evidence of the existence of this brick() function. If it fails to materialize, we have to question the motivations of those who make these wild claims.
- Status
I have nothing to prove, I await the evidence of the existence of this brick() function. If it fails to materialize, we have to question the motivations of those who make these wild claims.
It's not for him/her to prove - the burden of proof is on the (mostly german?) guys making the incredible claim that Gateway have really bad bricking code in their offical firmware
I'll say again what I posted above
I want a disassembly of the arm code that does the actual eMMC reprogramming - shouldn't be too complicated if they are just setting a few registers to zero.
Forget the rest for now (random number test, checksum) - just THAT piece of code would be enough evidence for me.
I want the address offset too btw.
Otherwise those german guys are bull-shitting
sigh proof proof proof
we all know that the 3ds brick has a very very very very tiny chance to brick when you use the exploit to create/start up the (emu)nand, more with r4ietc. and less with gateway but they both brick and we dont know what the code is er where the code is.
we all know that the 3ds brick has a very very very very tiny chance to brick when you use the exploit to create/start up the (emu)nand, more with r4ietc. and less with gateway but they both brick and we dont know what the code is er where the code is.
Yeah I don't think they're exactly lurking this thread right now. Probably have better/more useful things to do.
Yeah like spreading more false rumors without proof.
this might have been the same way (the rumored way) nintendo could've done it but to actually brick someones 3DS IS DOWNRIGHT DISGUSTING what if it was a genuine gateway card but the checksum fucks up in someway?
The write code for an eMMC controller has been discovered or it hasn't been discovered - in disassembly it's not such a long sequence of codes - until this gets posted (anywhere - not just here you understand) it's all bullshit
This is probably true, but it certainly does not help me feel safe. However unlikely it is that a Gateway user will inadvertently use the code, it shouldn't brick the system. They could have destroyed the flash card at a later date, simply corrupted the NAND (and left it fixable), or given a random chance for the above. A Permanent paperweight doesn't help anybody.
And as for all the people who don't believe: Better safe than sorry. But better calm and collected than panicking is good too.
Ofcourse there are more clones bricking, the code is intent to just affect clones. But the problem is there is a chance it will affect gw users. You wont be saying the same thing if it happens to you outside of your own fault with a gw card. No matter how small of a chance....
They don't have to post here - have they posted something similar (the actual code dump for the eMMC writes) ANYWHERE?
fine then think in loops there is no such code but there are bricking 3ds's so that means ther has to be a code but there is no code...
and more 2.0b2/3.1 is now out for 3-4 weeks and the last 2 days there are bricking 3ds's so why were there no bricking 3ds before the last 2-3 days?
and more 2.0b2/3.1 is now out for 3-4 weeks and the last 2 days there are bricking 3ds's so why were there no bricking 3ds before the last 2-3 days?
Until we get evidence of these wild claims, I'll flesh out the most likely scenario right now to set the gullible readers here straight.
At some point reports started surfacing about BOOTROM errors and MT-card team smelled a golden opportunity and decided to capitalize on rabid fanboy adoration of 'scene pioneers' that frequent these forums, finally giving them a opportunity to use these (well earned) good reputations for financial gain. Before this happened, they couldn't exactly either a) endorse MT-card, since they would be endorsing piracy - let alone b) come out as the developers of said card, as that would be even worse for obvious reasons.
Given the relatively complex nature of creating 'homebrew' by ROP-chaining, not to mention the moderate difficulty the cloners must have in adapting Gateway's firmware to be compatible with their FPGAs, it's far more likely there is no malice on the part of Gateway. So unless we get any evidence for this, take these claims with a gigantic grain of salt, use your brain and follow the money.
At some point reports started surfacing about BOOTROM errors and MT-card team smelled a golden opportunity and decided to capitalize on rabid fanboy adoration of 'scene pioneers' that frequent these forums, finally giving them a opportunity to use these (well earned) good reputations for financial gain. Before this happened, they couldn't exactly either a) endorse MT-card, since they would be endorsing piracy - let alone b) come out as the developers of said card, as that would be even worse for obvious reasons.
Given the relatively complex nature of creating 'homebrew' by ROP-chaining, not to mention the moderate difficulty the cloners must have in adapting Gateway's firmware to be compatible with their FPGAs, it's far more likely there is no malice on the part of Gateway. So unless we get any evidence for this, take these claims with a gigantic grain of salt, use your brain and follow the money.
- Status
Similar threads
- No one is chatting at the moment.
-
-
-
@
Xdqwerty:
Is it safe to update a modded ps3?
Can I play online in pirated games? (with ps3hen either enabled or not) -
-
-
-
-
-
@
Xdqwerty:
@salazarcosplay, I used apollo save tool to activate my ps3 offline so i could play a game that wasnt working
-
S @ salazarcosplay:from what I understood. you load up the piratged game. you the clear the syscalls, then you play
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
