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

  • Thread starter Thread starter Rokkubro
  • Start date Start date
  • Views Views 936,291
  • Replies Replies 4,457
  • Likes Likes 43
Status
Not open for further replies.
Also when I set destination to NAND (I tried both NAND and then SD just to humor myself... got the same error) It says "Free Space: 0 bytes (0.00MB)".


Bit off-topic to this thread, but this should be fixed now. I figured out how to grant it access to NAND info.
 
  • Like
Reactions: urherenow
i would love to have the mset back in n3ds and old 3ds to be able to boot mset from 9.2 instead of 4.5 :), good work guys :), are you going to release everything as a package or when the mset is good to the end user you are going to release that to prepare ppls consoles to the final release?
 
  • Like
Reactions: Margen67
i would love to have the mset back in n3ds and old 3ds to be able to boot mset from 9.2 instead of 4.5 :), good work guys :), are you going to release everything as a package or when the mset is good to the end user you are going to release that to prepare ppls consoles to the final release?

Well to get mset set up again you'll need some may to launch KARL3DS aside from mset, ie Cubic Ninja or OoT. So we'll likely have something set up from within our CFW to enable mset.
 
Could you please explain why the code you have published for the ARM9 bootstrap is a simple disassembly of the code from Gateway V3?!

Why didn't you simply release your original code that you had done...
Why have you not supported N3DS either, for some reason you have left the ARM11 and ARM9 sections without their correct patch locations.
 
  • Like
Reactions: Margen67
Could you please explain why the code you have published for the ARM9 bootstrap is a simple disassembly of the code from Gateway V3?!

Why didn't you simply release your original code that you had done...
Why have you not supported N3DS either, for some reason you have left the ARM11 and ARM9 sections without their correct patch locations.


Maybe if people actually start developing things with bootstrap, we'll put out New 3DS offsets and stuff. Until then, what difference does it make? We went through hell to get that information, we're not about to release it for nobody.​
 
  • Like
Reactions: TotalInsanity4
What do you mean hell, you only needed to decode the save from OOT and decrypt the the extra payload at offset 0x1E000 in the save!
 
  • Like
Reactions: Margen67
We made that argument over a week ago and still nothing's been made with bootstrap, so...


What do you mean hell, you only needed to decode the save from OOT and decrypt the the extra payload at offset 0x1E000 in the save!
We did it ourself before OOT was hacked though? And if that's so easy, why would we need to do it for you? Jeez, do it yourself.
 
Could you please explain why the code you have published for the ARM9 bootstrap is a simple disassembly of the code from Gateway V3?!

What did you want it to be disassembled from? And you're actually quite wrong, our code is derived partially from Gateway's code, but it primarily originates from yifan_lu's arm11_kernel branch for memchunk hax and other small pieces from Gateway's payload which yifan_lu opted to leave out of his ARM9 writeup. ARM9 bootstrap is basically 80% my work. And it's open, so who cares where it originated from? I'd rather have a cleartext arm9 exploit than having to sandwich random code into a launcher.dat.

EDIT: And honestly the N3DS offsets are out there in one way or another, if you want it to work on N3DS just get it done and make a PR.


Nothing public*
Dammit can we at least say that if a developer hasn't publicly mentioned they've done it that it's never been done? There's a difference between private and unknown.
 
Could you please explain why the code you have published for the ARM9 bootstrap is a simple disassembly of the code from Gateway V3?!

Why didn't you simply release your original code that you had done...
Why have you not supported N3DS either, for some reason you have left the ARM11 and ARM9 sections without their correct patch locations.
Time to add to my ignore list.
 
80% is a bit much... more like 8%
You have taken the code from yifan (GW v3) and added old firmware addresses to it.

When do you think you will port rxTools over to it?

Yes, if something hasn't see the light of the publics day then yes it's still vapourware!
 
80% is a bit much... more like 8%
You have taken the code from yifan (GW v3) and added old firmware addresses to it.

When do you think you will port rxTools over to it?

Yes, if something hasn't see the light of the publics day then yes it's still vapourware!
not really vaporware while the devs are still actively working on it.....just unreleased, i dont see why they would port it to Rxtools, they are alternatives of pretty much the same thing (obviously different in some respects but both intend to be a CFW solution), like asking when linux will be ported to windows
 
80% is a bit much... more like 8%
You have taken the code from yifan (GW v3) and added old firmware addresses to it.

When do you think you will port rxTools over to it?

Yes, if something hasn't see the light of the publics day then yes it's still vapourware!

And we released it publicly for anyone to use! If you have problems with it, don't use it.
 
Why did it take so long to release, you've been sitting on this for ages!
Are you going to release stuff quicker now, you must sitting on a whole host of stuff?!
 
  • Like
Reactions: Margen67
Why did it take so long to release, you've been sitting on this for ages!
Are you going to release stuff quicker now, you must sitting on a whole host of stuff?!

Back off man they do not have to release anything! your toxicity is not welcome here. this is the kind of crap that makes dev's stop. if you have a problem with how they are doing things do it yourself.
 
Why did it take so long to release, you've been sitting on this for ages!
Are you going to release stuff quicker now, you must sitting on a whole host of stuff?!

What's public now is what is done and stable. Everything else will be released when it's feature-complete and cleaned up. As we stated in the OP, this is mostly a research project for us. A release is more of a nice (and not fully guaranteed) side effect. There's still a lot of work to be done almost everywhere.
 
  • Like
Reactions: Alkéryn
Why did it take so long to release, you've been sitting on this for ages!
Are you going to release stuff quicker now, you must sitting on a whole host of stuff?!

Purposely negative/destructive people like you are so draining and aren't even all that bothersome. Go find another thread to troll.
 
  • Like
Reactions: Alkéryn
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum