Yea -> dont workWell it counts for something considering that nobody has been able to get proper xorpads from what I've seen.
Yea -> dont workWell it counts for something considering that nobody has been able to get proper xorpads from what I've seen.
Well it counts for something considering that nobody has been able to get proper xorpads from what I've seen.
Well it counts for something considering that nobody has been able to get proper xorpads from what I've seen.
You can generate fine xorpads wirh new 3ds + cubic ninja + decrypt9. There isarm9 on new3ds -> cubic ninjaYes, because nobody generated the 9.3 keyX, because nobody has ARM9 on N3DS (except few ones)
You can generate fine xorpads wirh new 3ds + cubic ninja + decrypt9. There isarm9 on new3ds -> cubic ninja
I thought it wont work every time but it work. Is it working or not?Decrypt9 Launcher.dat? It blackscreens using on new3DS

Decrypt9 Launcher.dat? It blackscreens using on new3DS
No not the normal D9 launcher dat.
This one... https://gbatemp.net/threads/creating-a-north-american-non-xl-new-3ds.381775/page-10#post-5426550
Apparently it works.
Can someone test itOur crypto stuff supports New 3DS encryption schemes, I don't believe Decrypt9 does (yet).
![]()
The new crypto code works wonderfully... Xeno-what now?
Any update?
Any update?

This made me laugh way harder than it should. I've had similar thoughts with my iPhone. (god I love kernel panics. pls give me more sir)I currently want to throw my N3DS at a wall due to the unfortunate circumstance in which my process decides to either commit suicide or stall out my N3DS.
I thought it wont work every time but it work. Is it working or not?
Just curious, given recent events with 9.6 on New3DS, has thought been given to "manual system transfers"/eshop access on lower firmwares? Are these things possible? I have still been using an O3DS as my daily driver while waiting for developments to allow me to move my setup to my waiting New3DS.
It seems like most of the steps of a "manual system transfer" have already been figured out, except once the "movable.sed" file is extracted from an O3DS, it then needs to be reencrypted and injected with the keys from the New3DS to work properly. After that, given NAND access (which has been achieved on New3DS), it seems to be a simple matter of moving over the remaining "data" files from the original NAND.
I was just wondering what ideas people had about this so far as I'm sure it affects many users with pre-9.6 New3DS systems.








