Hacking Official [Source Release] ReiNand CFW

  • Thread starter Thread starter Reisyukaku
  • Start date Start date
  • Views Views 988,221
  • Replies Replies 6,480
  • Likes Likes 115
Because it uses crappy arm9 patching...

Fun fact, I've seen RxTools randomly throw RX-E into applications like DevMenu
Yea, i've wanted to move that shit to an arm11 thread, but havent found the motivation to look into k11, or pickup some reading material on coprocessor stuff so i can allocate a new area for the arm11 payload.
 
I got pasted armips problem. Now I am stuck at
Code:
make[1]: Leaving directory '/home/wire/ReiNand/ninjhax'
cp: cannot stat 'ninjhax/ReiNand.3dsx': No such file or directory
Edit: FIXED. I finally got it to build!
 
Last edited by Wire,
Just ran a "hit counter" for every time the version patcher code caught a "Ver." match and patched it with Rei.

After just 5 minutes of play, the patching code hit 0x34 times. Let me repeat that, 52 times it patched Ver. with Rei. And get this, I didn't even run mset.
Mind doing this for RX-Tools and see where it happens?

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

Because it uses crappy arm9 patching...

Fun fact, I've seen RxTools randomly throw RX-E into applications like DevMenu
Honestly? Until the issue came up this morning with Reinand patching region names and game titles, I had only seen it replace instances where a version number was being called. Like where it references the system firmware version in devmenu.

edit:

Actually I'm not seeing reinand edit that string in DevMenu.
 
Last edited by Aroth,
Any major chances to the source since yesterday? I am looking through it now. Seeing if I should recompile now or wait till it releases...
 
Any major chances to the source since yesterday? I am looking through it now. Seeing if I should recompile now or wait till it releases...

No changes have been made by Rei since yesterday evening. There is a small code change that fixes how the Ver. string is patched to " Rei", that seems to fix some crashes in a few games as well. If you want a copy with that fix, look for the post I made a few pages back with two uploads. The "autoboot" file will not display the splash or prompt you to press Start, it will just load the cfw. The other file functions as normal with the splashs creen and the prompt to press Start.
 
  • Like
Reactions: mungry
Thanks. Is the change in Git or was it by users here?
Discussed here, made by me. I submitted a pull request but it has not been merged yet. I think Rei is waiting until the other changes he is working on are done.

edit:

If you have a build already compiled in the last 24 hours, all you need is the updated arm9.bin file, which I can PM you
 
Last edited by Aroth,
Found it and copied it. Works perfectly.
Saved me the trouble of breaking out the laptop to compile too :)
Ty sir.
 
Alright... stupid questions by the guy that came too late to the party :) (part1)...
  • Can we still use the same firmware.bin as in earlier versions with that?
  • I'm scared of updating (yup, that's my first time)... I just go into settings, check if the 'Rei' string is there, then bottom left button -> page 5 -> system update. If Nintendo has decided to give us the gift of even more stability in the meantime with v10.4, I will see that and I can still stop.
Is this correct? Sorry, but I can't be bothered to hunt for the correct bit of information through the last 20 pages. If @Reisyukaku still reads along here, at least the answer to the first question or a hint on how to get the correct one somewhat belongs in the readme.md.
 
  • Like
Reactions: peteruk
Alright... stupid questions by the guy that came too late to the party :) (part1)...
  • Can we still use the same firmware.bin as in earlier versions with that?
  • I'm scared of updating (yup, that's my first time)... I just go into settings, check if the 'Rei' string is there, then bottom left button -> page 5 -> system update. If Nintendo has decided to give us the gift of even more stability in the meantime with v10.4, I will see that and I can still stop.
Is this correct? Sorry, but I can't be bothered to hunt for the correct bit of information through the last 20 pages. If @Reisyukaku still reads along here, at least the answer to the first question or a hint on how to get the correct one somewhat belongs in the readme.md.
New firmware.bin is required for 10.3.. Update like normal via system settings... Make sure you're in emunand

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

Discussed here, made by me. I submitted a pull request but it has not been merged yet. I think Rei is waiting until the other changes he is working on are done.

edit:

If you have a build already compiled in the last 24 hours, all you need is the updated arm9.bin file, which I can PM you
Can I have that file, please? I haven't experienced any issues.. But I haven't exactly tested.. Been busy setting up another system.
 
Have people been able to boot eshop titles with the 9.6 encryption from other regions on their 10.3 emunands (I realize you need to run the region free program first)?
 
Worked perfectly. Thanks.

Question - the arm9 bin is only needed for GBA VC games run from CIA, correct? I don't have any of these, but I've not encountered any issues.

The arm9.bin is required to run the firmware.

What you are thinking of is the patched agb_firm, which is only required if you plan to run custom made gba VC injections

edit:

if you downloaded the file pack that was attached to the post you quoted, then you already have the updated arm9.bin with my strcomp() fix.
 
Last edited by Aroth,
Yes, thanks. That's exactly it.

Btw, your ambassador GBA games will run just fine without the patched agb_firm, you just need to install the game to both emunand and sysnand. You can use funkycia2 to generate cias of those games to install to the sysnand.
 
if you downloaded the file pack that was attached to the post you quoted, then you already have the updated arm9.bin with my strcomp() fix.

This is the fix I was looking for. Read about it while at work and figured this could be a nasty bug. Thanks again for the recompile.
 
If you're interested, I made a small mod: I removed the arm9 thread entirely (no version patching, or screenshots/RAM dumps - HANS does screenshots better, anyway), and made it autoboot (it boots to sysNAND if L is kept pressed). So just emuNAND and signature patches. No splash screen is displayed either, it boots as fast as it can :D
http://www73.zippyshare.com/v/pCv459vf/file.html
(On my n3DS, I found that the "autobootfix" value in CTR Boot Manager's conf.cfg must be set to 120 for a perfect boot rate).
 
Last edited by Aurora Wright,
If you're interested, I made a small mod: I removed the arm9 thread entirely (no version patching, or screenshots/RAM dumps - HANS does screenshots better, anyway), and made it autoboot (it boots to sysNAND if L is kept pressed). So just emuNAND and signature patches. No splash screen is displayed either, it boots as fast as it can :D
http://www73.zippyshare.com/v/pCv459vf/file.html
(On my n3DS, I found that the "autobootfix" value in CTR Boot Manager's conf.cfg must be set to 120 for a perfect boot rate).
can you please post the source somewhere? I'd like to see it :)

particularly because of how you got it to boot to sysnand if you're holding L
 
can you please post the source somewhere? I'd like to see it :)

particularly because of how you got it to boot to sysnand if you're holding L
Sure, this is the main source folder:
http://www59.zippyshare.com/v/lYYY2z5k/file.html
Nothing special, I just edited the main.c to make it autoboot and boot sysnand with L, and removed the files and functions to load the thread and draw the splash screen.
 

Site & Scene News

Popular threads in this forum