what's the latest version for o3ds that can boot from menuhax, and have gba/ds/dsi support in emunand?
thanks, much apreciatedO3DS XL - Sysnand 9.2 - Emunand 10.3
it doesnt work for me the browser crashes then it takes me to the home screen and nothing else im not getting into rxtools modeI think you can use this: http://dukesrg.no-ip.org/3ds/go.html
you need to go to your 3ds browser & url and type in https://dukesrg.github.io/?rxTools.dathaving the same issue... honestly I wish the project managers would make a new "main" topic so that they could keep the opening post properly updated... :/
If you are not sure, You should wait till ppl confirm it works!Was wondering does RxTools always support the latest system version on the O3DS? For example if Nintendo releases 10.4 tomorrow, will I be able to update my emunand no problem? Or would I have to update RxTools?
If you have a rxTools version with the rxTools.dat file you have to use your links. If you have a version without the .dat then you can use this https://dukesrg.github.io/?rxTools/sys/code.bin or the link I postedit doesnt work for me the browser crashes then it takes me to the home screen and nothing else im not getting into rxtools mode
We can't be certain about the future, but from what I remember, rxTools always worked with the latest fw in emunand without needing any updates, even way back when it was first released.Was wondering does RxTools always support the latest system version on the O3DS? For example if Nintendo releases 10.4 tomorrow, will I be able to update my emunand no problem? Or would I have to update RxTools?
1. Delete or move old "rxTools" folder, rxtools.dat, firmware.bin.okay, noob questions.
I have the old RxTools. I'm finally FINALLY ready to commit to using an updated version.
Other than code.bin and /rxtools/* is there anything else I need to remove before moving over the updated package? I've downloaded the Sep21 build posted a few pages back (unless there's a better choice).
Also, I remember rxTools having to "install" something once upon a time. Will I have to worry about any of that this time around?
Finally, assuming this doesn't go as planned, can I go back to my stable rxtools 2.6 relatively painlessly?
Is there any benefit to using a Oct 03 or newer version? Also, (I hate to ask), but if so, where can I find it already compiled?1. Delete or move old "rxTools" folder, rxtools.dat, firmware.bin.
Copy new "rxTools" folder.
According to your rxTools version, you should use BUNDLED /Tools/cdn_firm.py to generate a new firmware.bin and put it into /rxTools/sys. (This is completely different if you're using rxTools newer than Oct.03)
Then reinstall the BUNDLED rxinstaller.nds (if you're using DS profile exploit).
2. If you put correct firmware.bin on correct place, it will only happen once.
3. If you want to go back to 2.6, you should backup
- rxTools folder
- rxtools.dat
- firmware.bin
- rxinstaller.nds for 2.6
The recent versions still have some bugs to fix.Is there any benefit to using a Oct 03 or newer version? Also, (I hate to ask), but if so, where can I find it already compiled?
Secondly, I'm guessing the python script has something to do with copyrights?
romfs.bin xorpad is not required in some converters (simple cia converter)Can someone help me when trying to decrypt a 3ds game in rxtools im getting an eror sdinfo.bin not found? it only generates the exefs and exheader but not the romfs
Is there a method that doesn't require me downloading the huge python package?The recent versions still have some bugs to fix.
Since those versions mainly improve the CFW running on N3DS, your build is enough.
The python script drags files from Nintendo's server.
Both Python 2.X installer and Nintendo files aren't that huge if you're using broadband. Or are you using 56K modem?Is there a method that doesn't require me downloading the huge python package?