Hacking rxTools with Signatures patched out!

  • Thread starter Thread starter AHP_person
  • Start date Start date
  • Views Views 339,015
  • Replies Replies 1,545
  • Likes Likes 44
Status
Not open for further replies.
Have you RE'ed rxtools or did you just inject code? If the first one than it would be nice if you released emuNAND sauce so pasta dev can make emuNAND.
 
  • Like
Reactions: Margen67
As long as you have a cia installer
Hmmm, FBI freezes on infinite 3DS logo loading in the patched rxTools emuNAND O_O
What to do?

Solved this issue. Software installed on sysNAND will not work on emuNAND. It needs to be installed on the SD before you inject NAND into emuNAND.
FBI and NES Remix works now :D
 
...So I was thinking of going back to using my original clean 9.2 NAND backup for emuNAND... Is it possible for me to install a CIA manager onto the emuNAND without having to muck around with downgrading and/or with sysNAND? Or should I just start again with 4.2?
 
...So I was thinking of going back to using my original clean 9.2 NAND backup for emuNAND... Is it possible for me to install a CIA manager onto the emuNAND without having to muck around with downgrading and/or with sysNAND? Or should I just start again with 4.2?

If you don't have a gateway or CN then no, you have to downgrade.
 
For the record: yes there is. Not sure about roxas' stance on this (it'd be extremely disrespectful if the author didn't so much as ask him permission to release), but every single rxtools.dat this person's posted has NATIVE_FIRM in it. rxTools usually has a mechanic to import an external file (and yes, it actually uses it) in order to avoid copyright issues. That is not used here.

If native_firm is inside rxTools on the original link, then it's an oversight and he can fix that by removing it. This version of rxTools will still use firmware.bin and decrypt and store in the launcher. It's possible he forgot to remove native_firm from the modified launcher while he was testing it. But I'm pretty sure he did remove native firm.
 
For the life of me can't get GBA in emunand to work.

Booted EmuNAND, launch FBI, switch to delete title NAND and delete the old AGBFIRM, install patched AGBfirm, reboot and boot emunand again but GBA games still give the poweroff error.
 
For the life of me can't get GBA in emunand to work.

Booted EmuNAND, launch FBI, switch to delete title NAND and delete the old AGBFIRM, install patched AGBfirm, reboot and boot emunand again but GBA games still give the poweroff error.

Your using the wrong version of rxTools then. There's a different one with out the patches needed to make Smash Bros work. That's the one that can boot TWL/GBA stuff.
 
  • Like
Reactions: Margen67
it works for me, but I used devmenu_2x because it automatically overwrite your current AGB_FIRM.
 
Your using the wrong version of rxTools then. There's a different one with out the patches needed to make Smash Bros work. That's the one that can boot TWL/GBA stuff.
No, you got that wrong. One has GBA and TWL support without Smash Bros support, while the other is the opposite. The second one can boot GBA. I've tried this.
 
Ok, well I'm stumped. This is weird. Trying to confirm I did this right.

I put the 2nd launcher on my SD - boot up to EMUNAND
MD5: B7C2D16214CC69F0B8B2D2130880E5D7

I noticed though when I removed my SD and went back the launcher now has a different MD5
MD5: 17D2655870F1C950FDEB17B6A19A4D63

What I did was boot emuNAND, launch FBI, switch DESTINATION: NAND, change to delete title option in FBI, found the AGBFIRM, deleted it, installed patched AGBFIRM, and then try to run a GBA, but keep getting "error occurred"
 
Last edited by ,
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum