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

  • Thread starter Thread starter Rokkubro
  • Start date Start date
  • Views Views 936,975
  • Replies Replies 4,457
  • Likes Likes 43
Status
Not open for further replies.
I don't think it needs to be difficult. If anything it should be more clear in the context of the 3DS. "Custom firmware" should refer to modified FIRM.
I know what it means, and anyone who reads this now knows what it means, but gamesquest1 tells it like it is:
unfortunately most people seem to think, cfw = rom loader

It's like the whole "jailbreak" name declarable. iDevices started that, then we got PS3 'jailbreak' devices. It's just a name, in the PS3 case a dumb name. I'm just suggesting a way to help out on a PR front so that new users who see these posts doesn't think that this is what they've been holding out for.

I'll say nothing further on the to topic as it appears I'm causing too much commotion. (SEE: the two posts above)
 
people came with the jailbreak term for ps3 because geohot( the most famous iphone jailbreaker) dit it and it was done via a smartphone.
 
people came with the jailbreak term for ps3 because geohot( the most famous iphone jailbreaker) dit it and it was done via a smartphone.

Actually people used the term jailbreak to mean breaking out of jail, or to 'break free of any restrictions'

It has been applied in the world of computer science since as early as 2004?

I don't think there's any mention of the term in computing prior to that, but I could be wrong.

It's mentioned in a book 'Security Warrior', which was published early 2004.
maxresdefault.jpg
 
Apparently I'm not listed as part of the "team" but...



Wait what!? can we have a 60 fps video taken :nds:

From the video after triggering the DS Profile:

Code:
firmloader by Dazzozo and Relys
one!
 
pying ARM11 payload
erwriting ARM11 exception vectors
 
k Arm11
ccdd
cdd
 
xpected 0x44836
one
xpected 0x44837
xpected 0x44846
complete
 
Loadding FIRM
Magic: FIRM
Hash: 2b37e4f23bf47dd17aed718444232d9cd608c52
 
S0: offset 0x200, size 0x33600, addr 0x1ff00000
S0: hash 0cba5d2fbab506cc3f6f34a60bd5b1baf5d7506d
S1: offset 0x33900, size 0x31000, addr 0x1ff80000
S1: hash 748ec1dc2a3126ecfca82fcfd4aa8fadd3f5be27
S2: offset 0x64800, size 0x84800, addr 0x8006800
S2: hash 01b60b4b[not visible]2379f16cf8372bd6568e
S3: offset 0x0, s[not visible] 0x0
S3: hash da39a3ee[not visible]5601890afd80709
Loaded FIRM
Handing over to f[not visible]01b01c
 
DevMenu isn't signed with production keys, so it normally can't run on retail hardware.


So its considered a CFW? To me I assumed, and going back to the ps3 days of CFW, that its suppose to take over where the sysnand was running, completely written over the sysnand, emunand was a redirect (I believe).
 
So its considered a CFW? To me I assumed, and going back to the ps3 days of CFW, that its suppose to take over where the sysnand was running, completely written over the sysnand, emunand was a redirect (I believe).

The patches required to get it to run are FIRM patches, so yes, this is a CFW, but DevMenu itself isn't.
 
So its considered a CFW? To me I assumed, and going back to the ps3 days of CFW, that its suppose to take over where the sysnand was running, completely written over the sysnand, emunand was a redirect (I believe).
Well honestly any kind of hack launching a firmware with higher privileges than normal can be called a CFW. You literally run a CFW eventhough it doesn't sit all patched in your nand.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum