D
100% agree with this one ^^^One has already been written, the other cannot be written until after they've explained exactly how RocketLauncher works. Which they won't do until they release RocketLauncher. Except they won't because the tool needs to be written, that can only be written once RocketLauncher is released. But they won't release RocketLauncher until....
tl;dr It's just not going to happen.
The devs already know that they are writing for "noobs without respect and patience"I don’t think post that encourages ugopawn leak should be written here. The usage of leaked software discourages the dev to release the hack, and it also illegal as it is copyrighted material. Please dont make the devs think they’re doing it for noobs without respect and patient, so don’t fill the thread with “u can leak” or “omg I can’t wait 2 bad ugopawn is for USA only.
100% agree with this one ^^^
RocketLauncher isn't happening since it needs a tool which makes the whitelist hack, but Apache will not do it because it isn't in its hands (and I presume that Robz nor Shutter ain't), and since the whole whitelist process is private nobody can work on such tool which will still being private until such tool is made (which is an enless circle).
Thanks to the leaked ugopw we can access to both homebrew and backups at least.
If they won't release the RocketLauncher and rest of tools at least they could release sources so other people can continue working
My take on this is that if you are passionate enough about this, you can try to make your own whitelist modifier. ApacheThunder is very talented because of his knowledge on how it works. If you want it now, all you can do is teach yourself and make your own (; of course, I really suggest waiting.
It definitely is a waste of time. Unfortunately at this point in time you only other option is to storm into ApacheThunder's home to see what's up, but I highly, highly do NOT reccomend that. The easiest thing to do now is wait and see what happensWhat he appears to be saying is that he's not able to do it & someone else needs to do it, without having access to the crucial information. I refuse to re-do work when people hoard it, because it's a waste of time.
Unfortunately at this point in time you only other option is to storm into ApacheThunder's home to see what's up, but I highly, highly do NOT reccomend that.
The easiest thing to do now is wait and see what happens
Even if it never happens, it would be better the devs not release it then having bricked dsi's.
and even if it is never released, the devs made no promises.
Who cares about bricks, everything starts rough, if more people start using it then more people will start developing and thus making it safer in the endTo everyone angry about it not being released-- chill out! Even if it never happens, it would be better the devs not release it then having bricked dsi's. I'm sure if it is going to be released it will be released sometime soon when it is safe, and even if it is never released, the devs made no promises. For now you can enjoy custom firmware on 3DS and Wii U from some very talented people.
But HOW?My take on this is that if you are passionate enough about this, you can try to make your own whitelist modifier. ApacheThunder is very talented because of his knowledge on how it works. If you want it now, all you can do is teach yourself and make your own (;
If we knew that, you'd already have LukeLauncher, and many others, of course (; lolBut HOW?
Learn C and/nor ASM, practice reverse engineering, read up on DS(i)Brew, etc. etc. Of course, you'll also need an incredible amount of free time. This stuff won't happen in a day or two.But HOW?
1. The exploit requires 1.4.0 firmware! Older or newer fw revisions do not work!
2. The exploit requires a flashcart that you are able to modify the internal rom it presents to the system.
3. Details on which cards will be compatible will be revealed at a later time.
So I guess it will never be released
It's just not going to happen.