Hacking 3DS SDK Compiler Tools

[SuperSDKDev]

FAKE

 

[Pong20302000]

nice set of tools

upload to filetrip much eayier to download them then

 

[Ericthegreat]

Really nice, but none of this is usable yet right?

 

[Pong20302000]

Really nice, but none of this is usable yet right?

you need a Dev unit

 

[Fudge]

I know you need to have a devkit, but will these files be useful in the hacking of the 3DS??

 

[Pong20302000]

the actual hack, no this does not help

once hacked it will let people make the apps

this is the same as having the Game Roms
no way to run them yet

 

[FireGrey]

can you use these on a dev unit right now?
I remember that someone from the 'temp has a dev unit...

 

[Cyan]

More than one user on the Temp have a dev unit.
And no, it's not useful either for these dev unit without the dev keys.

Users would need to use CiTRUS to merge all the above files into one (with the dev keys).

 

[CollosalPokemon]

Sorry, SuperSDKDev, "your" work is crap.

To name the most notable reasons...

1) Your RSF is completely in the wrong format. If you had the SDK, it wouldn't be a problem to know what the RSF format looks like.
2) Your BCWAV and CBMD are the _exact_ ones as Xcution provided. Make your own or GTFO.
3) Your ExeFS maker is worthless because the ARM11 Code binary is compiled from an AXF. An AXF is NOT the ARM11 Code binary in the ExeFS. You should know this if you did have a copy of the SDK.

My project at the moment is to reverse engineer the 3DS SDK tools and then rebuild them for you all to use.

I highly doubt you have a copy of the SDK based on the information I've seen in your post.
You're using Xcution's _EXACT_ CBMD and BCWAV, and also because your ExeFS maker is almost literally worthless with or without keys. In order to be able to make an ExeFS with your program you'd NEED to have already made an ARM11 Code binary from a program which can compile an AXF into the ARM11 Code binary, and doing that would defeat the purpose of your application because such a program would already be able to make an ExeFS, or even CXI / CCI, very easily at that point.

 

[SuperSDKDev]

Sorry, SuperSDKDev, "your" work is crap.

To name the most notable reasons...

1) Your RSF is completely in the wrong format. If you had the SDK, it wouldn't be a problem to know what the RSF format looks like.
2) Your BCWAV and CBMD are the _exact_ ones as Xcution provided. Make your own or GTFO.
3) Your ExeFS maker is worthless because the ARM11 Code binary is compiled from an AXF. An AXF is NOT the ARM11 Code binary in the ExeFS. You should know this if you did have a copy of the SDK.

My project at the moment is to reverse engineer the 3DS SDK tools and then rebuild them for you all to use.

I highly doubt you have a copy of the SDK based on the information I've seen in your post.
You're using Xcution's _EXACT_ CBMD and BCWAV, and also because your ExeFS maker is almost literally worthless with or without keys. In order to be able to make an ExeFS with your program you'd NEED to have already made an ARM11 Code binary from a program which can compile an AXF into the ARM11 Code binary, and doing that would defeat the purpose of your application because such a program would already be able to make an ExeFS, or even CXI / CCI, very easily at that point.

Really, I think _YOU_ are the one who does not have a 3DS SDK. I'd say, bring proof, but considering you don't have a 3DS SDK you would have nothing to show and probably upload a garbage file with .RSF attached at the end of the file name. BTW Xcution asked, me to make the .BCWAV and. CBMD for his CiTRus program, because unlike you he has a 3DS SDK. Though the person he purchased it from did not include the tools and documents to make the .BCWAV and. CBMD. Ever wondered why he gives no details on how to make the BCWAV and. CBMD for the .BNR made in CiTRus?

But if you really want to, upload your 'proof' and prove me 'wrong', I'd like to see what a real .RSF looks like

 

[SuperSDKDev]

Sorry, SuperSDKDev, "your" work is crap.

To name the most notable reasons...

1) Your RSF is completely in the wrong format. If you had the SDK, it wouldn't be a problem to know what the RSF format looks like.
2) Your BCWAV and CBMD are the _exact_ ones as Xcution provided. Make your own or GTFO.
3) Your ExeFS maker is worthless because the ARM11 Code binary is compiled from an AXF. An AXF is NOT the ARM11 Code binary in the ExeFS. You should know this if you did have a copy of the SDK.

My project at the moment is to reverse engineer the 3DS SDK tools and then rebuild them for you all to use.

I highly doubt you have a copy of the SDK based on the information I've seen in your post.
You're using Xcution's _EXACT_ CBMD and BCWAV, and also because your ExeFS maker is almost literally worthless with or without keys. In order to be able to make an ExeFS with your program you'd NEED to have already made an ARM11 Code binary from a program which can compile an AXF into the ARM11 Code binary, and doing that would defeat the purpose of your application because such a program would already be able to make an ExeFS, or even CXI / CCI, very easily at that point.

About point 3), anyone who has an SDK like Xcution and I would know what you've written in point 3) is complete crap, considering you don't have an SDK, you should probably read the articles 3DBrew.org. You never know, you might learn something.

 

[CollosalPokemon]

Sorry, SuperSDKDev, "your" work is crap.

To name the most notable reasons...

1) Your RSF is completely in the wrong format. If you had the SDK, it wouldn't be a problem to know what the RSF format looks like.
2) Your BCWAV and CBMD are the _exact_ ones as Xcution provided. Make your own or GTFO.
3) Your ExeFS maker is worthless because the ARM11 Code binary is compiled from an AXF. An AXF is NOT the ARM11 Code binary in the ExeFS. You should know this if you did have a copy of the SDK.

My project at the moment is to reverse engineer the 3DS SDK tools and then rebuild them for you all to use.

I highly doubt you have a copy of the SDK based on the information I've seen in your post.
You're using Xcution's _EXACT_ CBMD and BCWAV, and also because your ExeFS maker is almost literally worthless with or without keys. In order to be able to make an ExeFS with your program you'd NEED to have already made an ARM11 Code binary from a program which can compile an AXF into the ARM11 Code binary, and doing that would defeat the purpose of your application because such a program would already be able to make an ExeFS, or even CXI / CCI, very easily at that point.

About point 3), anyone who has an SDK like Xcution and I would know what you've written in point 3) is complete crap, considering you don't have an SDK, you should probably read the articles 3DBrew.org. You never know, you might learn something.

Dude, you need to look at 3DBrew articles. Not me.

http://3dbrew.org/wi...ry:File_formats

.AXF - Pre-assembled ARM code. before being linked into a CCI/CXI format. They're practically ARM specific ELF files.

They're assembled into the .code binary of the ExeFS which is inserted into a CXI (and then could either be inserted into a CCI or a CIA), but the .code binary isn't an AXF.

Check yourself before you wreck yourself next time

 

[JoostinOnline]

And we have yet another case of bitchy 'temp members.

 

[SuperSDKDev]

Sorry, SuperSDKDev, "your" work is crap.

To name the most notable reasons...

1) Your RSF is completely in the wrong format. If you had the SDK, it wouldn't be a problem to know what the RSF format looks like.
2) Your BCWAV and CBMD are the _exact_ ones as Xcution provided. Make your own or GTFO.
3) Your ExeFS maker is worthless because the ARM11 Code binary is compiled from an AXF. An AXF is NOT the ARM11 Code binary in the ExeFS. You should know this if you did have a copy of the SDK.

My project at the moment is to reverse engineer the 3DS SDK tools and then rebuild them for you all to use.

I highly doubt you have a copy of the SDK based on the information I've seen in your post.
You're using Xcution's _EXACT_ CBMD and BCWAV, and also because your ExeFS maker is almost literally worthless with or without keys. In order to be able to make an ExeFS with your program you'd NEED to have already made an ARM11 Code binary from a program which can compile an AXF into the ARM11 Code binary, and doing that would defeat the purpose of your application because such a program would already be able to make an ExeFS, or even CXI / CCI, very easily at that point.

About point 3), anyone who has an SDK like Xcution and I would know what you've written in point 3) is complete crap, considering you don't have an SDK, you should probably read the articles 3DBrew.org. You never know, you might learn something.

Dude, you need to look at 3DBrew articles. Not me.

http://3dbrew.org/wi...ry:File_formats

.AXF - Pre-assembled ARM code. before being linked into a CCI/CXI format. They're practically ARM specific ELF files.

They're assembled into the .code binary of the ExeFS which is inserted into a CXI (and then could either be inserted into a CCI or a CIA), but the .code binary isn't an AXF.

Check yourself before you wreck yourself next time

I should have explained on the release post, the exefs does more then the exefs maker from nintendo's SDK. it can handle .axf input. Perhaps you should check my make_exefs output with your copy of the... wait you can't... you don't have the SDK, my mistake I forgot for a moment you didn't have the sdk. Sorry for not explaining this in the release post, you wouldn't of had the opportunity to embarrass your self like you have above.

 

[Rydian]

Sorry, SuperSDKDev, "your" work is crap.

Who shit in your cornflakes this morning?

 

[JoostinOnline]

Sorry, SuperSDKDev, "your" work is crap.

Who shit in your cornflakes this morning?

I did. Do you think that's related to his bad mood?

 

[DiscostewSM]

I can't help but feel pity for anyone who takes the "I have such-and-such and you don't" approach to an argument, especially on the internet.

 

[elisherer]

@CollosalPokemon,
You have proven many times your work is genuine, carry on with your good work and ignore the ones that want to steal your thunder

 

[3DSGuy]

3DS SDK Compiler Tools!

Hello everyone, SuperSDKDev here. My project at the moment is to reverse engineer the 3DS SDK tools and then rebuild them for you all to use. Right now I have finished the the 3DS .BNR maker, .ICN maker, ExeFS Maker and RomFS Maker. It outputs' are 1:1 with Nintendo's tools.

.BNR Maker

You can download it here. It comes with example input files(.cbmd and .bcwav)

USAGE:

make_bnr -b filename.CBMD filename.BCWAV filename.BNR

.ICN MAKER

You can download it here. It comes with example input files.

USAGE:

make_icn -b filename.RXF

User input:
This requires more input than the .BNR Maker. For customisation you must first edit the ICN.RSF, ICN.RSF has an explaination for each of the entries. To edit the APP_FLAG.icnb, open it in a HEX editor and refer to 3DBrew.org for flag customisation.

ExeFS Maker

You can donwload it here. It comes with example dummy input files. You can build the BNR and ICN with the above tools, but I will not be giving an example of the ARM code or LOGO for potentially copyright reasons

USAGE:

make_exefs -b filename.RSF

For customisation you must first edit the EXEFS.RSF, it has an explaination for each of the entries.

RomFS Maker

You can download it here

USAGE:

make_romfs -b filename.ZIP output.BIN

RomFS stands for ROM File system, so resources used by the ARM code in the ExeFS goes in here. Package all of the resources into a .ZIP archive and then put package the archive into RomFS with the above usage.

Your programs output static hashes/signatures so stop speaking BS and leave CollosalPokemon alone, he has the SDK. But in case you can't read here's a picture to sumarise you argument:

 

[Cyan]

@CollosalPokemon,
You have proven many times your work is genuine, carry on with your good work and ignore the ones that want to steal your thunder

I couldn't have said it better

If he has to resort to this kind of arguments (saying that xCution requested the files from him), then who would know better than himself who is telling the truth?
He should read 3dbrew a little better to see who has a devkit and who doesn't.
I read it, and I know CollosalPokemon has one too.


@[member='SuperSDKDev']:
You stated that Xcution have the SDK but not the documentations, so HE can't make a new .BCWAV and .CBMD files.
But YOU, of course, have these documentations so it's really not difficult for you to create new one to discredit you, like you already did, right?.Don't provide the same than Xcution then.
And yes, it's up to you to provide another example, because CollosalPokemon clearly can't!

And once you did, all this drama/flaming war will be cleared.



What do you want to prove by providing fake informations?
It's not the best way to prove yourself knowledgeable.