Hacking [Release] rxTools - Roxas75 3DS Toolkit [fw 2.0 - 9.2]

  • Thread starter Thread starter Roxas75
  • Start date Start date
  • Views Views 3,301,860
  • Replies Replies 19,240
  • Likes Likes 151
Status
Not open for further replies.
Messages like this just annoy developers.. I would like to advise you to search this thread and keep calm
I was asking a simple question. This thread is too long to read and I'm not good at searching. Now if I put the question in all caps, I could understand someone getting annoyed.
 
I'm not an expert with Makefiles...
Is there a way to run all the commands (make, make release, make theme, make doc, etc...) at once?

@nastys I could add you to the pasta cfw theme thread so you can updated with rx tools themes. Or would it be better to have a new one?
Since themes are not cross-compatible, I think a new one would be better :)
 
  • Like
Reactions: Syphurith
So, what's the deal with the bios? Like, where to place the gba bios?
And latest github compiled has the agb bios option in settings (just compiled it myself), therefor i ask, as it seems you already messed with it ;)
Thx

You don't. The option patches the decrypted AGB_FIRM copy stored in rxTools/data at 0xD7A12 to use the SVC 0x26 call instead of SVC 0x01. Basically what the "Nostalgia" version of the patched AGB_FIRM CIA does. Just launch a GBA VC and you'll notice.
 
  • Like
Reactions: DjoeN
I know, but a Makefile itself is a script, so it doesn't make sense to write another script.
It does if your more familiar with one type of script than another. I'm more familiar with a batch script than a Makefile script.
 
I'm not an expert with Makefiles...
Is there a way to run all the commands (make, make release, make theme, make doc, etc...) at once?
Since themes are not cross-compatible, I think a new one would be better :)
all-content: doc theme release
Cause it would take 'all' as the default target, so if you need to do so, you could either overwrite all to let it do more, or just add a new target.
>>Hope this solves your issue.
 
  • Like
Reactions: DarkMatterCore
I think the nand dumped won't work with hardmod, am I right?
That is why I still use the gateway launcher
 
I think the nand dumped won't work with hardmod, am I right?
That is why I still use the gateway launcher
Well, it should, because the only difference is the trash beyound the actual data. In the worst case you jus tneed to pad it with any data. If you have a hardmod you can easily try it both with GW restore nand and hardmod itself.
 
  • Like
Reactions: Syphurith
Well, it should, because the only difference is the trash beyound the actual data. In the worst case you jus tneed to pad it with any data. If you have a hardmod you can easily try it both with GW restore nand and hardmod itself.
I believe it was @VerseHell who said he tried restoring a NAND created by rxTools using GW launcher. It gave an error. I wouldn't know what hardmod would do.

Assuming NAND created by rxTools also fails with hardmod, then what else could it be good for?
 
I believe it was @VerseHell who said he tried restoring a NAND created by rxTools using GW launcher. It gave an error. I wouldn't know what hardmod would do.
Assuming NAND created by rxTools also fails with hardmod, then what else could it be good for?
There is difference between GW and normal hardmod nand dumps. Futhurmore rxTool dump differs from them too.
To figure out what is the difference is not too difficult, if you've already successfully dumped your NAND via hardmod.
You could compare those. To my speculation there should be junk-bytes and paddings difference.
Get yourself a Hex Compare Tool that would make it easier. Also, there is FAT16 xorpad generation, get yourself one if you'd like.
BTW if you've find out how to make RxTools NAND Dump to be able to flash back, you could even write a tool for re-make the dump.

I teamed up with CakeCFW team and we got N3DS arm9bin decrypted. So I'm one step closer to N3DS support!
@DarkMatterCore @AlbertoSONIC @duke_srg @mid-kid I heard that CakesFW and Rei have decrypted N3DS FIRM, is that true? (Or my mistake)
Note: saw that in ReiNAND post near its newest response, by rei. Quote added. Hope the progress is smoothly..
 
There is difference between GW and normal hardmod nand dumps. Futhurmore rxTool dump differs from them too.
To figure out what is the difference is not too difficult, if you've already successfully dumped your NAND via hardmod.
You could compare those. To my speculation there should be junk-bytes and paddings difference.
Get yourself a Hex Compare Tool that would make it easier. Also, there is FAT16 xorpad generation, get yourself one if you'd like.
BTW if you've find out how to make RxTools NAND Dump to be able to flash back, you could even write a tool for re-make the dump.
I get that. As some already said the difference is only some junk files. My question is related to be actually able to use it to restore your NAND. Rxtools dumps can't be used to restore your NAND with GW launcher, and maybe a hardmod.
 
I’m sure GW dumps can be used directly to restore the NAND with hardmod,I have done it many times.
But for rxtools, I don't know how to combine the firm0,firm1,ctrnand into one nand file
 
I’m sure GW dumps can be used directly to restore the NAND with hardmod,I have done it many times.
But for rxtools, I don't know how to combine the firm0,firm1,ctrnand into one nand file
I don't know about firm0 and firm1 but ctrnand is not encrypted and will need to be in order to restore it.

Almost forgot that firm0 and firm1 should be identical as firm1 is a backup of firm0
 
I don't know about firm0 and firm1 but ctrnand is not encrypted and will need to be in order to restore it.
Almost forgot that firm0 and firm1 should be identical as firm1 is a backup of firm0
If what you need is only the encryption - just get yourself the FAT16 xorpad to do so.
However since there should be padding and junk difference, you would have to decrypt the GW NAND dump and compare it to.
Once the padding or junk is solved, you could use rxtool dump with xorpad to encrypt it and flash it back.

I've an easier idea, no need for actual hardmod if anyone would like to have a try.
GW Dump (SysNAND), RxTool Dump (SysNAND), EmuNAND Dump (Emunand tool), FAT16 Xorpad (RxTools).
Once you have all those above.
1. Decrypt the GW one and EmuNAND one with Xorpad.
2. Compare decrypted GW one with RxTools one.
3. Once you have offset and solved the padding, get RxTools one encrypted.
4. Backup all files within your SD.
5. Use Emunand Tool to restore the Encrypted RxTools dump to Emunand.
6. See if it works. If yes, the emunand would be same one as your SysNAND.
7. If it works, you could flash the EmuNAND dump back.
To me, the Xorpad has smaller size than GW one. Don't know if it meets the length of RxTools one, yup.

If such a method work, you could tell devs and you may even have a Format EmuNAND option in RxTools.
 
I’m sure GW dumps can be used directly to restore the NAND with hardmod,I have done it many times.
But for rxtools, I don't know how to combine the firm0,firm1,ctrnand into one nand file
rxTools creates a full nand dump. If you dumped partitions, use emunand tools to combine a nand dump.
BTW I transferred ticked.db from emunand to sysnand when rxTools have a bugs in thatoperation using rxTools emunand dump and emunand tools. Can't say for sure now which sysnand dump was used as a source.

--------------------- MERGED ---------------------------

To me, the Xorpad has smaller size than GW one. Don't know if it meets the length of RxTools one, yup.
xorpad may be of any size, the truth is that the junk tail of GW emunand dump processed with xorpad is still junk :)
 
  • Like
Reactions: Syphurith
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum