Hacking [WIP] KARL3DS - Kernel access on N3DS via Ninjhax + Loadcode

  • Thread starter Thread starter Rokkubro
  • Start date Start date
  • Views Views 936,717
  • Replies Replies 4,457
  • Likes Likes 43
Status
Not open for further replies.
53dc76cf3d.png

The new crypto code works wonderfully... Xeno-what now?

wow
 
Any update?

I think if there was, they'd probably have posted it. But I understand being excited and having a hard time waiting. I think we're all eagerly anticipating news, but keeping in mind this is something these guys/gals aren't being paid for and they probably have jobs/school taking up most of their time we need to be patient and realize there will be a fair bit of waiting involved.
 
  • Like
Reactions: Zidapi
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.
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)

Edit: I should probably mention that the panics were because I did something dumb and didn't notice. I AM SO SMART S-M-R-T
 
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.
 
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.

We have plans to extend the duration in which we can stay on 9.5 emuNAND as long as we possibly can.
 
A bit offtopic, but there's no way to return to home menu or settings after running ninjhax and bootstrap (arm11), right?

What I'd like to do is use the ARM11 kernel access to enable updating to any version using nim (patch URLs as demonstrated by yifan_lu), from any version that ninjhax supports. But doing that requires returning to either home menu or entering system settings after.

Is there any reference on running the kernel exploit from CN directly available at all?
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum