I know.

 

I mean Lima3ds has a better UI and is more stable.

 

Just gonna bump it! Have o3ds with rxtools on emunand 11.2, sys on 9.2.
Safe to try this? Or should I have some patience for a change?
Thanks @duke_srg for dusting the good ol' RXTools. I still don't know what happend to Roxas

 

The CFW part is the same as in the last RXTools 2.x official build. So it will work wirh sys9.2/emu11.2 (I have exactly the same setup)
As for the tools part, refer to the compatibility chart at github. Generally NAND partitions/files dump/restore completely refactored and working, bit injections is not.

 

You must be very unlucky to brick with that version - NAND write protection is enabled by default in settings
The less people uses this version - the less probability I'll continue with my work. The current feature in development is double speed NAND/SD transfers is actually stuck because of the lack of the testers.

 

If you need emunand on the second card you must format it with emunand before using. For testing you must be able to build it from sources

 

Build requirements and instructions are also on GitHub. Additional SD card only required for destructive test, like restore emu/nand partitions or files while the test currently needed to perform on a number of SD cards is emunand dump.
With the current prebuild beta version available at GitHub you could easily dump emunand from one SD card and then restore it to the second one.

 

You'll need to build dev-cardboost branch form of my fork and test sysnand and emunand dump on as much SD cards as you can. This branch utilizes maximum possible speed of 3DS SD controller, but Mardiri have issues with one of his card which we can't resolve. So having only abouy 4 cards tested one of which failed is not a good statistics, so we need to make sure is it is an exact card issue or more common problem.

 

Any updates? Would be nice to have some test results

 

granted i advocated the right for using a bootmanger even that it just updated for Sighax support but... rxtools is Dead, Let it Rest stop trying to revive it there are better CFWs even if you want one that just "works" theres Luma, Corbnik, Cakes etc. the only place rxtools has left remotely in this day and age is for those Stupid high paranoid users, that see the migration to A9LH (now outdated)/ or to Sighax(Boot9strap Installer > Sighax installer atm) will brick em and these are the people who look at the 3DS Guide as "too risky" and w/ 11.3 (and it not changing in 11.4) now introducing its methods to stop External NATIVE_FIRM loading. RXTools is in its coffin w/ teh final nail in.

Sure people could fork rxtools or even this and try to bring it to standards but i thought the point of it all you all so helplessly clung to was "its not broken, no nee dto fix it, it just works!" (well sorry it is Broken [by 11.3+]. it needs to be fixed [again 11.3+ Support and now needing sighax/boot9strap support] and it only "Just Works" with Firmwares 11.2 and older, (and even then you cant go online (w/o CTRHTTP Pwn even then that wont work forever) no patches to protect your Sysnand FIRM1/FIRM0 so any attempt to update would and will update yer precious 9.2 Sysnand!

again people who want something under the name rxTools its your choice to develop a CFW that can work w/ todays Firmwares, offer the same protections or as little as you see fit. but the orginal that carried everyone to where things led to , today? the orginal rxTools is just Dead, deceased, 6feet under in teh digital ground. and in its place we say Decrypt9 take its "Tools" place (rxMode was the "CFW" not what everyone else was concerned about the "Tools") and evcen then, GodMode9 is quiockly becomming what Decrypt9 is and more (there will always be someone that wants an all in one solution, but if its waht you want then by all means study study study learn experiment and code your own "rxtools Reborn or wtf you want to call it. just leave its ancestor where it belongs.