It was a shock to meIt was but it's still a shock when it happens.
It was a shock to meIt was but it's still a shock when it happens.

next we are taking over rapture science !!!! (but in all seriousness, now that Sigchecks offsets and code is public, it most likely was invevitable)Welp, I guess this was inevitable.
please, if you are so scared and not confident enough to do it, please DON'T, wait for an in depth tutorial to do it, it would be really dumb if you bricked.I'm so super scared for a brick so can you explain me how injection works, I mean...
So rxTools.
I have the options:
- Inject EmuNAND partitions.
- Inject NAND files.
I think it's the NAND files one?
So I pressed A, and then I see 2 optionsto select NAND.
sysNAND
emuNAND
I'm so scared so I didn't do anything yet, haven't found a tutorial, can you explain?
Do you also have a dual nand on one SD? If so how do you plan on getting rid of the rednand aka cfw without needing to format the card?now this is what am waiting for, youre the man AHP. time to say good bye to my second nand aka cfwnand
There's at least a disassembly available on patois' github, with some amount of work someone well versed in ARM asm could probably reimplement features from it.Even though i doubt anyone will do the same with NTR, because no ARM9 code exec ^^'
i just backup my rxnand and reinject itDo you also have a dual nand on one SD? If so how do you plan on getting rid of the rednand aka cfw without needing to format the card?
They can still add new keys with those one-time-use RSA registers at boot which they used for the 6.x and 7.x keys. Considering the 6.x key has never been dumped they could probably get away with reusing that same method.
please, if you are so scared and not confident enough to do it, please DON'T, wait for an in depth tutorial to do it, it would be really dumb if you bricked.
well, as far as i know, no successful exploit of this flaw was done up to now to fetch the keys (might be wrong tho)Isn't the successful exploitation result for the first listing in http://3dbrew.org/wiki/3DS_System_Flaws#arm9loader literally "Recovery of 6.x save key/7.xNCCH key"?
My point was that they *might* be able to get away with it, although with that exploit out there it's pretty unlikely.Isn't the successful exploitation result for the first listing in http://3dbrew.org/wiki/3DS_System_Flaws#arm9loader literally "Recovery of 6.x save key/7.xNCCH key"?

Just going to say this, we have control over OTP registers for O3DS, so it REALLY is unlikely that we will have a problem with emunand loading on O3DS.
Edit : sure, we might have to update the code, but i don't think they can really block firmloader on O3DS at this point
i really doubt Roxas will drop rxTools support, but that is a possibility, but yeah, if you are afraid of not having access to lates emunand on O3DS, keep your gateway ^^I'm not concerned with this new rxtools being blocked completely and permenantly. My main concern is it being blocked by an update and no future support to release the updated rxtools.dat(which, in a way, is a permanent block). Gateway may take their time releasing updates, but their support is consistent.
Hey, do you do this through rxtools or emunand tools? If you weren't trying both I would but luckily you can try it first and let me know how it goesi just backup my rxnand and reinject it
and ofcourse i have to format it first
with emunand tools but i have listed/sorted nand emunand rednand backup and also some img backup so itll takes time. im on backing up progress anyway, will let you know if its going wellHey, do you do this through rxtools or emunand tools? If you weren't trying both I would but luckily you can try it first and let me know how it goes![]()
That's maybe the only thing that would keep people with an O3DS buying GW. With O3DS emuNAND virtually futureproof, especially once Pasta adds it and it can be updated by anyone, and Sky3DS already available for people on sysNAND 9.3+ there's little reason to buy one currently.maybe in the future GW will drop further sysnand firmware compatibility, if so it will take months (just a hunch, but at least 3-4 months) for the cardless emunand solution to adapt.
