Hacking [SUPPORT] rxTools Official technical support thread

[Syphurith]

Installed Bigblue/red menu and devmenu x2 using Rxsysnand. Non of them appear as presents or whatever. I do see then under 'Nand' in FBI, but when i launch them, i get a black screen and it just stays that way (i had to reboot). Why is this?
Edit - I might reinstall my sysnand backup and try all this again. Might see how that goes. Thanks anyway.

Hey no please never install those into NAND, but into SD. I can't see those NAND user titles neither.
Pay attention to where you 're installing the CIA to!

 

[Shurikan117]

Hey no please never install those into NAND, but into SD. I can't see those NAND user titles neither.
Pay attention to where you 're installing the CIA to!

I actually wanted then on sysnand. But if it is impossible, then oh well. Thanks for the help bro.

 

[Gil_PL]

someone help me with a question. downgrade sysnand mset on 9.2 + format sysnand = brick?

 

[djalmafreestyler]

someone help me with a question. downgrade sysnand mset on 9.2 + format sysnand = brick?

I read this somewhere in GBATemp, looks like when you try to format, the system settings modified (MSET downgraded) it bricks your console...I'm not sure about that.

QUESTION:

Where do I install GBA CIAs to play on DevMode?
SysNAND
emuNAND
devMode

 

[will67]

I think this problem is only related to 2ds. 3ds and 3ds xl are not affected. Someone to confirm?

 

[Gil_PL]

I read this somewhere in GBATemp, looks like when you try to format, the system settings modified (MSET downgraded) it bricks your console...I'm not sure about that.

I did not try this yet, but as I changed the integrity of sysnand with mset downgrade and I was afraid to format with system format.

 

[samiam144]

I actually wanted then on sysnand. But if it is impossible, then oh well. Thanks for the help bro.

No he means, install to destination SD (in FBI) while you are in rxmode sysnand. That actually installs to sysnand, which is what you want lol

QUESTION:

Where do I install GBA CIAs to play on DevMode?
SysNAND
emuNAND
devMode

Sysnand, if playing from devmode

I did not try this yet, but as I changed the integrity of sysnand with mset downgrade and I was afraid to format with system format.

I'm sure it only affects 2DS, since the brick happens when it asks the system to configure the 3D slider.

 

[Shurikan117]

No he means, install to destination SD (in FBI) while you are in rxmode sysnand. That actually installs to sysnand, which is what you want lol

Faceplam. Thank you kind sir.

 

[Koryushin]

So actually i turn around without any solution.
I passed 2 days compiling rxtools myself and i always went to the same point.

When comiling all goes fine, i don't have any error just a warning when compiling Rxmode.

Spoiler: Rxmode compiling

$ make
make[1]: Entering directory `/E/Programmation/Projets/rxTools/rxmode/native_firm'
make[2]: Entering directory `/E/Programmation/Projets/rxTools/rxmode/native_firm/source/arm9'
arm-none-eabi-gcc -g -Wall source/myThread/myThread.c source/myThread/lib.c -c -mcpu=arm946e-s -march=armv5te -mlittle-endian -fshort-wchar -std=c99
arm-none-eabi-gcc -g source/EmuNAND.s source/CreateThread.s source/myThread/FS.S -I source/myThread -c -mcpu=arm946e-s -march=armv5te -mlittle-endian -fshort-wchar
arm-none-eabi-gcc -nostdlib -T 3ds.ld EmuNAND.o CreateThread.o myThread.o lib.o FS.o
e:/programmation/devkitpro/devkitarm/bin/../lib/gcc/arm-none-eabi/4.9.2/../../../../arm-none-eabi/bin/ld.exe: warning: cannot find entry symbol _start; defaulting to 0801a4c0
arm-none-eabi-objcopy -O binary a.out arm9.bin
rm -f *.o *.out
mv arm9.bin ../../build/0801a4c0.bin
make[2]: Leaving directory `/E/Programmation/Projets/rxTools/rxmode/native_firm/source/arm9'
arm-none-eabi-as source/k9_fix_flags.s -o build/0801b564.o
arm-none-eabi-ld -e 0 -Ttext 0x0801b564 build/0801b564.o -o build/0801b564.elf
arm-none-eabi-objcopy -O binary build/0801b564.elf build/0801b564.bin
arm-none-eabi-as source/p9_emunand_hook_1.s -o build/0807882c.o
arm-none-eabi-ld -e 0 -Ttext 0x0807882c build/0807882c.o -o build/0807882c.elf
arm-none-eabi-objcopy -O binary build/0807882c.elf build/0807882c.bin
arm-none-eabi-as source/p9_emunand_hook_2.s -o build/0807886c.o
arm-none-eabi-ld -e 0 -Ttext 0x0807886c build/0807886c.o -o build/0807886c.elf
arm-none-eabi-objcopy -O binary build/0807886c.elf build/0807886c.bin
arm-none-eabi-as source/p9_keyx_spoof.s -o build/080282f8.o
arm-none-eabi-ld -e 0 -Ttext 0x080282f8 build/080282f8.o -o build/080282f8.elf
arm-none-eabi-objcopy -O binary build/080282f8.elf build/080282f8.bin
arm-none-eabi-as source/p9_mythread_hook_1.s -o build/08086140.o
arm-none-eabi-ld -e 0 -Ttext 0x08086140 build/08086140.o -o build/08086140.elf
arm-none-eabi-objcopy -O binary build/08086140.elf build/08086140.bin
arm-none-eabi-as source/p9_mythread_hook_2.s -o build/08086174.o
arm-none-eabi-ld -e 0 -Ttext 0x08086174 build/08086174.o -o build/08086174.elf
arm-none-eabi-objcopy -O binary build/08086174.elf build/08086174.bin
arm-none-eabi-as source/p9_reboothax_1.s -o build/080859ec.o
arm-none-eabi-ld -e 0 -Ttext 0x080859ec build/080859ec.o -o build/080859ec.elf
arm-none-eabi-objcopy -O binary build/080859ec.elf build/080859ec.bin
arm-none-eabi-as source/p9_reboothax_2.s -o build/08094454.o
arm-none-eabi-ld -e 0 -Ttext 0x08094454 build/08094454.o -o build/08094454.elf
arm-none-eabi-objcopy -O binary build/08094454.elf build/08094454.bin
arm-none-eabi-as source/p9_signatures_spoof_1.s -o build/0805d63c.o
arm-none-eabi-ld -e 0 -Ttext 0x0805d63c build/0805d63c.o -o build/0805d63c.elf
arm-none-eabi-objcopy -O binary build/0805d63c.elf build/0805d63c.bin
arm-none-eabi-as source/p9_signatures_spoof_2.s -o build/080632b8.o
arm-none-eabi-ld -e 0 -Ttext 0x080632b8 build/080632b8.o -o build/080632b8.elf
arm-none-eabi-objcopy -O binary build/080632b8.elf build/080632b8.bin
Patches folder : build
Number of patches : 0
cfwtool - generating : NATIVE_FIRM
rm build/0801b564.elf build/0807882c.elf build/0805d63c.elf build/08086174.elf build/080859ec.elf build/08094454.elf build/080282f8.elf build/080632b8.elf build/0807886c.elf build/08086140.elf
make[1]: Leaving directory `/E/Programmation/Projets/rxTools/rxmode/native_firm'
make[1]: Entering directory `/E/Programmation/Projets/rxTools/rxmode/agb_firm'
arm-none-eabi-as source/p9_signatures_spoof.s -o build/080238a8.o
arm-none-eabi-ld -e 0 -Ttext 0x080238a8 build/080238a8.o -o build/080238a8.elf
arm-none-eabi-objcopy -O binary build/080238a8.elf build/080238a8.bin
Patches folder : build
Number of patches : 0
cfwtool - generating : AGB_FIRM
rm build/080238a8.elf
make[1]: Leaving directory `/E/Programmation/Projets/rxTools/rxmode/agb_firm'
make[1]: Entering directory `/E/Programmation/Projets/rxTools/rxmode/twl_firm'
arm-none-eabi-as source/p9_signatures_spoof.s -o build/080238c0.o
arm-none-eabi-ld -e 0 -Ttext 0x080238c0 build/080238c0.o -o build/080238c0.elf
arm-none-eabi-objcopy -O binary build/080238c0.elf build/080238c0.bin
Patches folder : build
Number of patches : 0
cfwtool - generating : TWL_FIRM
rm build/080238c0.elf
make[1]: Leaving directory `/E/Programmation/Projets/rxTools/rxmode/twl_firm'

But when i try to launch rxtools on my 3DS it is installing fine, i can use the menu but when i boot Sysnand or emunand with rxtools i have a black screen.
I can boot Devmode without issues.

I use an already configured Msys/mingw32 installation, with gcc/g++ 4.8.1
Python 2.7.10, The last devkitpro, and armips from this link http://www.romhacking.net/utilities/635/

Here it's a copy/paste from my Path on windows 7
C:\Python27\;E:\Programmation\MinGW\bin;E:\Programmation\MinGW\msys\1.0\bin;E:\Programmation\devkitPro\devkitARM\bin;E:\Programmation\devkitPro\devkitARM\arm-none-eabi\bin;E:\Programmation\ImageMagick-6.9.1-Q16\;E:\Programmation\Git\bin;

What did i do wrong ?

 

[djalmafreestyler]

No he means, install to destination SD (in FBI) while you are in rxmode sysnand. That actually installs to sysnand, which is what you want lol

Sysnand, if playing from devmode

I'm sure it only affects 2DS, since the brick happens when it asks the system to configure the 3D slider.

Thank you, but can you please answer this questions?

Which methods I can play GBA?

You said If playing form devmode, can I play GBA from emuNAND? or it's devmode only?

 

[samiam144]

Thank you, but can you please answer this questions?

Which methods I can play GBA?

You said If playing form devmode, can I play GBA from emuNAND? or it's devmode only?

You CAN play from emunand. If your nands are linked, just install the gba cia while in emunand. If your nands are unlinked, you will have to install the gba cia while in emunand AND sysnand.

Also to expand further on your previous question, you can also install gba cias while in devmode if you want to play from devmode.

 

[Syphurith]

Here it's a copy/paste from my Path on windows 7
C:\Python27\;E:\Programmation\MinGW\bin;E:\Programmation\MinGW\msys\1.0\bin;E:\Programmation\devkitPro\devkitARM\bin;E:\Programmation\devkitPro\devkitARM\arm-none-eabi\bin;E:\Programmation\ImageMagick-6.9.1-Q16\;E:\Programmation\Git\bin;
What did i do wrong ?

What?!

Patches folder : build
Number of patches : 0

I don't know what happened really. Are there files with extension ".o" and ".bin" in /E/Programmation/Projets/rxTools/rxmode/native_firm/build?
Really wonder how it could be patches 0... (So no clue for you sorry.)

 

[Chad Banks]

I can't get anything to happen when I go into System Settings -> Other Settings -> Profile -> Nintendo DS Profile. I have downgraded the system settings app and I have installed the mset exploit. sysnand is 7.2, emunand is 9.8.

 

[samiam144]

I can't get anything to happen when I go into System Settings -> Other Settings -> Profile -> Nintendo DS Profile. I have downgraded the system settings app and I have installed the mset exploit. sysnand is 7.2, emunand is 9.8.

sysnand needs to be 4.x or 9.x

 

[Chad Banks]

but sysnand has to be 9.2 or below, not 9.8, correct?

 

[samiam144]

but sysnand has to be 9.2 or below, not 9.8, correct?

emunand version doesn't matter. The coding only works on 9.x or 4.x sysnand version, any other version needs more coding to be supported

Edit: yes sorry, obviously 9.x refers to 9.0 - 9.2

 

[Chad Banks]

emunand version doesn't matter. The coding only works on 9.x or 4.x sysnand version, any other version needs more coding to be supported

so if I update sysnand to 9.8 (the most recent version) I'll be able to user rxtools, mset exploit, etc? I thought I read somewhere it can't be higher than 9.2?

 

[samiam144]

so if I update sysnand to 9.8 (the most recent version) I'll be able to user rxtools, mset exploit, etc? I thought I read somewhere it can't be higher than 9.2?

Nope, sorry I edited my post! It won't work on anything above 9.2. When we say 9.X it just refers to 9.0 - 9.2, the only exploitable firmware versions out of all 9.x versions.

 

[jernk]

Nevermind

 

[megazero1x1]

could someone please post the MD5 hash of the firmware.bin needed/created by the latest version of rxtools (2.6 or 3.0b3 or whatever is the newest one).