Hey I just found this crash in Majora's Mask 3D and I wanted to know if it is useful for running homebrew. Thanks. In case anyone wanted to know, I am on version 1.0 on Majora's Mask 3D. This crash can be replicated and is not random.
i know that feel, bro xDI'm starting to think these threads are just trolls. That or I need to take a break from this place, cause this shit bothers me more then it should.
Exactly. Like nintendo is going to let a game get published with a security hole big enough for some random kid with no experience or knowledge to accidently crack their system. I can understand people want to be involved, and I appreciate that. But you should know that if you don't understand how this stuff is being done, you're probably not being helpful. Like you said, I can find one page by yellows8 that has about twelve reasons this wouldn't work. It doesn't take much to do a bit of research. What kills me is people think a crash causes custom code to run, when it's actually the other way around.i know that feel, bro xD
This stuff has been discussed to death by pretty much everyone, yet still whenever somebody softlocks or hardlocks his game in some semi-bizarr way, they got to post about it since "thatsh how the big boysh did it" except that it isn't and just looks similar, which nobody seems to get...
Those threads still aren't going to vanish, because that's the face of 80% of the userbase here, kiddies who try to keep up with the scene and think they actually can finally contribute with that stuff, plainly ignoring to research what nature the crash has and simply asking here instead because "iz eazier then 4 minutes research" (no this isn't supposed to be hate, but the moderators of wiiu-hacking and 3ds-hacking can probably aggree on the "mainly people without any knownledge" part )
Exactly. Like nintendo is going to let a game get published with a security hole big enough for some random kid with no experience or knowledge to accidently crack their system. I can understand people want to be involved, and I appreciate that. But you should know that if you don't understand how this stuff is being done, you're probably not being helpful. Like you said, I can find one page by yellows8 that has about twelve reasons this wouldn't work. It doesn't take much to do a bit of research. What kills me is people think a crash causes custom code to run, when it's actually the other way around.
In this case, by all means. My irritation is a more general one. Where some kid crashes a game a gets all over excited and compelled to post the same thing that has bee n posted 3 freaking days in a row. I argued the specifics of the last two. Just wait a few more threads. You won't care what they've done lolWhat bugs me even more about this, is that it is no hardcrash but just a missing-file-exception, which you can see by simply staring at the "glitch", they just cut DLs door-opening animation from the 3DS-Version, since it has no use to the player anyway (during normal gameplay). EVERY crash-based exploit, yet (and you can count them on one hand) was based on exploits that are either searching for missing code that could be replaced by hand (on wii it was THAT since everything was stored on the SD or in unisolated strings where you could easily enter custom-code in the savefile) or using routines the console itself delivers to stay in another usermode the user isn't supposed to be in while being in thatever particular app they are in.
To make it shorter for the read-lazy customer: look at the crash, think about it, and you should immediatly know what happened in this case...
aside from buffer overflows which are irrelevant now, custom code is run through the fault of some software that causes it not to check for validation. The code then hijacks that softwares process causing that software to 'crash'.I think the problem isn't that people are assuming any crash can cause an exploit, it's that nobody explains correctly what each of these crashes do and why they work when the initial exploit is released. And so these threads get created and everyone bashes the OP and we end up with another cycle.
It should be titled "found a crash?" Then the first post says, "no one cares".maybe one of these should be refunctioned and stickied... or we need just a thread titled "found a crash? read this". maybe it could break the cycle
EDIT: i allready stopped caring what it is, anymore. i just felt the urge to tell the OP what i was talking about while raging xD
oh no i mean, they watch a video that shows how to be fierce deity link everywhere, where they show the crash if you go through a door, then decided it would be better to create the same video themselves, but more wobbly and shaky, and not including all the stuff about swapping a mask for a bottle etc, if your copying a video on youtube just link to the original video that is much better quality and shows the whole thingOh shit. I just assumed it was his vid. That's great lol