Nah, this doesn't directly touch Luma, so it doesn't have to be forked or anything and allows everyone to use the official branches.
That is true.you said that it is more secure thus meaning that it doesn't have the same console ID like the others using the arm9.bin
No, it's a module.modified arm9loaderhax.bin?
Find a way to dump an existing module from your own 3DS (maybe Decrypt9 or braindump related),
edit the device ID,
place it in the luma folder with the relevant .cetk file.
(I assume)
I'll be seeing you all on the other side once you catch up. This is in no relation to @Nanquitas's patch, but is inspired by it. Also, stop following enMTW; you all gon' get banned even more.
To those that made this possible, you know who you are. Kudos.
Yes. That's the point of this. At least somebody gets it.Are you retarded?
the thing is that it's related to @Nanquitas fork how do you insert that in a module (i never understand modules)
and .cetk is the file of a module ?????
Yeah, I was reading and it was saying about firmware.bin a matching cetk fileread these two:
(go down to firms/modules):
https://github.com/AuroraWright/Luma3DS/wiki/Options-and-usage
then read the definitions for the firm parts:
https://github.com/d0k3/Decrypt9WIP
it may give us a better idea of what we need to rip out, related to 3Dbrew references.
I don't have anything to release. There probably won't ever be a release from the people that figured this out, but it's simple enough. What is actually done is public knowledge.if only you would just release this and be a +1UP
Yeah, I was reading and it was saying about firmware.bin a matching cetk file
hmmm...
I don't have anything to release. There probably won't ever be a release from the people that figured this out, but it's simple enough. What is actually done is public knowledge.
Right but you have a module - Cant you just release it and credit everyone who helped out? :lI don't have anything to release. There probably won't ever be a release from the people that figured this out, but it's simple enough. What is actually done is public knowledge.
Awesome. Passing along this message from the man himself.Yes. That's the point of this. At least somebody gets it.
it's more then likely listen on 3dbrew, the info is all there, i'm sure, you just have to put it together.We can find DeviceID in ARM9 ITCM (https://www.3dbrew.org/wiki/Memory_layout)
and in CTCert (https://www.3dbrew.org/wiki/CTCert)
where is said public knowledge?
Exactly - Like if you really wanna help the community dont be a dick and hide back info - Let the community know.I dont know why people make this threads only for being... "superior" to the rest of the people instead of sharing knowledge. Fucking moron, should be closed.
Frankly, I have to agree 100%.I dont know why people make this threads only for being... "superior" to the rest of the people instead of sharing knowledge. Fucking moron, should be closed.
ARM9 ITCM: This is the u32 DeviceId.We can find DeviceID in ARM9 ITCM (https://www.3dbrew.org/wiki/Memory_layout)
and in CTCert (https://www.3dbrew.org/wiki/CTCert)