But you said "Probably a cfw or modification of a cfw since that will allow for the most stuff"
I'm going to include an existing CFW in the launcher I make. After that, I'll modify the CFW so that it's more stable. After that, and if there's enough demand, I'll make a new CFW.
While this sounds awesome, soon you will understand why no one wants to release a cfw for 3ds on gbatemp... I give it 2 more days before they start whining to you to hurry up and make a cfw so they can pirate their games.
I already understand perfectly, not just from here, but from other places I've tried to do things like this. This time, though, if people are going to complain that they don't believe me or that they want something RIGHT NOW, I'm just gonna ignore them.
Ok, i'm just going to say firstly: your title is misleading there's no new exploit
That's why I put [IN PROGRESS] in front of it. It's a work in progress. The result will be an exploit.
Secondly, i don't believe you possess the knowledge to do this. Even if you recruited 2 other people (who? people who know how wouldn't have needed you to tell them this).
You don't really know me or my background, so that's understandable. The people I recruited are people I personally know and have met in real life. Both of them are really good with C, and the do not keep up with the 3DS scene, and especially not the hacking scene. We collaborate because of this, since I know about the 3DS and can provide references and functions for code.
I have this similar thing where i look at exploit A and B then look at C and think something is possible to make; but the difference is you have to realize your limitations and not actually try and do it. Because if it's obvious like this, then someone smarter who can code and understand ARM ASM a lot more than you and me can already do it, and will do it.
Cool. If someone else does it before I do it, I'll still release a homebrew launcher and some other tools. It'll just be easier on me.
Fucking around with the 'most interesting stage' as you put it, is an easy way to brick the 3DS, ask yellows8.. please don't continue this unless i'm wrong and you truly understand what you are doing. I know it's exciting when you think of something that can definitely work, but hasn't been done, but you don't understand the finer details.
If I was just going around blindly trying to create something like this, I wouldn't even bother. I know what I'm doing and the steps necessary to do it.
Yifanlu doesn't even have a 3DS you know? He just did a quick pseudo-analysis of the whole thing and took details from other people - it's not even close to rebuilding what GW does. Smea's is more detailed but he doesn't say everything either. Once you are at the kernel level minor mistakes or modifications will brick the system, the people doing this stuff don't risk this anymore i'm guessing they got their debug methods.
He doesn't need one. Someone (I know who and I think they're amazing, but I'm busy at the moment and I'll link him later) provided the gateway payloads for all of the different firmware versions. He analyzed them and referenced the system functions on the 3DS, and reverse engineered them based on that.
tl;dr i dont think you are prepared or able to do this so please don't post about it especially before no work is done, this is just an (obvious) theory that is possible
I think I am prepared and able to do this, so I'm posting it here to keep the people that are interested updated.
You can check it out at
go.plxhack.us.
This page literally just contains the word "Moo." in the website code.
Just for the future though, open source would be great. Makes it easier to get stuff added/bugs fixed.
Of course I'm gonna make it open source.
But what is the point with this cfw? TS said it is for 4.5 only.. We already have cfw for 4.5. And that cfw was developed by the real leet ppl like yellows8. Ninjhax too boot from the gw exploit would be great though
The goal is to make the new CFW more stable and to be able to run it in later firmwares.