Hacking Official [Source Release] ReiNand CFW

[chocoboss]

There's really no reason to keep using MenuHAX with how easy and safe it is to install A9LH

Maybe some ppl don't want to risk brick ? ( this can happened even if you follow the guide corrupted nand, SD problem ... )
Why should I change something that work ?

"If ain't broken don't fix it !"

 

[Xiphiidae]

Maybe some ppl don't want to risk brick ? ( this can happened even if you follow the guide corrupted nand, SD problem ... )
Why should I change something that work ?

If you check your SD card before starting (which the guide tells you to do), the odds of bricking are akin to winning the lottery. Not to mention that using Menuhax has a far greater risk of you losing your ability to get into CFW.

"If ain't broken don't fix it !"

What a strange way of saying "don't ever improve on what you have".

 

[The Catboy]

Maybe some ppl don't want to risk brick ? ( this can happened even if you follow the guide corrupted nand, SD problem ... )
Why should I change something that work ?

"If ain't broken don't fix it !"

The Guide more than covers the proper steps to avoid that. The risk is extremely low and even lower if you take the extra time for preparation.
Because Menuhax still has a greater risk of being patched out or accidentally updating your sysNAND. With A9LH, there's little to no risk of losing your CFW, because Nintendo can't make a targeted update to remove it.
Be honest with me, why are you trying so hard to defend out of date stuff? You defend RXTools tooth and nail (even through I am making suggestions to improve it,) and now you defending Menuhax. Why are you so adamant to hold on these things? I really suggest in the form of a PM because this is about to go seriously off topic.

 

[nechigawara]

I still stand on my opinion
1. Menuhax is not outdated. But it's not as good as A9LH. People who are willing to take a risk should install A9LH for it benefit.
I will consider it outdated when: A. There is no update and not working with latest FW. B. No CFW supports it anymore.
2. It's their console, if they're not willing to install A9LH and keep using menuhax, taking a risk of being patched, it's their decision. I once said that "it will be a bother to them". Just leave them be.
3. If the developer decides to remove the support, it's the developer's choice.
4. You said you're open for a choice for CFW, more choice is better, why not an exploit too?

 

[Hayleia]

For someone on 9.0-9.2 (includes those who already have menuhax or those who bought a new 3DS and got that firmware), I can understand menuhax. I mean, it's shit, but it's true that it really has a probability of bricking of 0 compared to 0.00000000000000000001 for a9lh (or a probability of 75 for people who can't read).
For everyone else, as long as they have to do at least one CTR Transfer to get to 9.0-9.2, well they could do it to 2.1 and install a9lh, there is really no reason not to.

 

[nechigawara]

For someone on 9.0-9.2 (includes those who already have menuhax or those who bought a new 3DS and got that firmware), I can understand menuhax. I mean, it's shit, but it's true that it really has a probability of bricking of 0 compared to 0.00000000000000000001 for a9lh (or a probability of 75 for people who can't read).
For everyone else, as long as they have to do at least one CTR Transfer to get to 9.0-9.2, well they could do it to 2.1 and install a9lh, there is really no reason not to.

Menuhax work on 11.2: How to Autoboot EmuNAND on FW 9.0.0-11.2.0 (without A9LH).

 

[Wolfvak]

For someone on 9.0-9.2 (includes those who already have menuhax or those who bought a new 3DS and got that firmware), [...]

I'm not sure why people still have 9.0-9.2 in mind. With safefirmlaunchax you get full ARM9 on ALL firmwares up to 11.2 (dunno if they'll fix it in the next one lol) and considering menuhax/soundhax is available on all firmwares...
So yeah, if you're in something like 9.3-11.2 you can launch CFW straight from the HBL lol

 

[MsMidnight]

I still stand on my opinion
1. Menuhax is not outdated. But it's not as good as A9LH. People who are willing to take a risk should install A9LH for its benefit.
I will consider it outdated when: A. There is no update and not working with latest FW. B. No CFW supports it anymore.
2. It's their console, if they're not willing to install A9LH and keep using menuhax, taking a risk of being patched, it's their decision. I once said that "it will be a bother to them". Just leave them be.
3. If the developer decides to remove the support, it's the developer's choice.
4. You said you're open for a choice for CFW, more choice is better, why not an exploit too?

fixed some errors

 

[nechigawara]

fixed some errors

Thanks!! Edited.

 

[Deleted User]

Maybe some ppl don't want to risk brick ? ( this can happened even if you follow the guide corrupted nand, SD problem ... )
Why should I change something that work ?

"If ain't broken don't fix it !"

You can't really brick with a a9lh installation if you know how to read basic instructions.

 

[Hayleia]

Menuhax work on 11.2: How to Autoboot EmuNAND on FW 9.0.0-11.2.0 (without A9LH).

Oh, I never knew menuhax was back on 11.2. Well forget my above post. If people like 32 seconds of boot time, go ahead, use that.

I'm not sure why people still have 9.0-9.2 in mind. With safefirmlaunchax you get full ARM9 on ALL firmwares up to 11.2 (dunno if they'll fix it in the next one lol) and considering menuhax/soundhax is available on all firmwares...
So yeah, if you're in something like 9.3-11.2 you can launch CFW straight from the HBL lol

No, I knew about that but not about the availability of menuhax on 11.2. And yeah, soundhax remains a valid entrypoint for that but it's even worse than menuhax as an entrypoint for a CFW (though it's an awesome entrypoint for unhacked 3DSes).

 

[The Catboy]

I still stand on my opinion
1. Menuhax is not outdated. But it's not as good as A9LH. People who are willing to take a risk should install A9LH for it benefit.
I will consider it outdated when: A. There is no update and not working with latest FW. B. No CFW supports it anymore.
2. It's their console, if they're not willing to install A9LH and keep using menuhax, taking a risk of being patched, it's their decision. I once said that "it will be a bother to them". Just leave them be.
3. If the developer decides to remove the support, it's the developer's choice.
4. You said you're open for a choice for CFW, more choice is better, why not an exploit too?

The issue with these old entrypoints is that they are vulnerable. In entrypoints like Ninjahax and MSET, you need to boot into an unprotected sysNAND to get to your CFW. That leaves your sysNAND completely vulnerable. With Menuhax, it can be removed through a targeted update and again launches through an unprotected sysNAND.
Yes, it's their choice to continue using this software and honestly I am not completely against them doing so. But devs shouldn't have to be held behind. It's a lot like devs dropping hardware support. Sooner or later, the user needs to upgrade.

 

[nechigawara]

The issue with these old entrypoints is that they are vulnerable. In entrypoints like Ninjahax and MSET, you need to boot into an unprotected sysNAND to get to your CFW. That leaves your sysNAND completely vulnerable. With Menuhax, it can be removed through a targeted update and again launches through an unprotected sysNAND.
Yes, it's their choice to continue using this software and honestly I am not completely against them doing so. But devs shouldn't have to be held behind. It's a lot like devs dropping hardware support. Sooner or later, the user needs to upgrade.

I'm not talking about dev, that's why I said it's up to developer to keep or remove menuhax support.
I also know the downside of menuhax, the point is, it still work if you're not boot to sysNAND and updateing.
And with the last update, it even work on the lastest FW. menuhax will totally become useless when Nintendo force an update before it can run.
Right now, this exploit is not broken, that downside is something it can't fix because of how it was design.
Unlike rxtools, broken, no update, no fixed.

 

[The Catboy]

I'm not talking about dev, that's why I said it's up to developer to keep or remove menuhax support.
I also know the downside of menuhax, the point is, it still work if you're not boot to sysNAND and updateing.
And with the last update, it even work on the lastest FW. menuhax will totally become useless when Nintendo force an update before it can run.
Right now, this exploit is not broken, that downside is something it can't fix because of how it was design.
Unless rxtools, broken, no update, no fixed.

I am not disagreeing with you, just pointing out reason why users should consider switching and or reasons why devs should encourage switching. Right now a lot of people are using them because devs really aren't encouraging them to change.

 

[nechigawara]

You can't really brick with a a9lh installation if you know how to read basic instructions.

There are people who got black screen even though they followed the guide correctly (That's what they claim)
Such as @Lilligant case that nobody can find it cause since it fixed already. Also @amximo case that we not sure what the cause of his problem.
So, I would say there always a risk but very very very low.

Atleast, if users were following the guide correctly and created a Nand Back Up, the brick can still be fixed by hardmod except some user error brick.

 

[Reisyukaku]

If anything, I'll probably just push a good few updates first then just push to a legacy branch and the main branch will be a9lh only or something.. someone can make a universal a9lh loader for ninjhax if they want

 

[Wolfvak]

I am not disagreeing with you, just pointing out reason why users should consider switching and or reasons why devs should encourage switching. Right now a lot of people are using them because devs really aren't encouraging them to change.

Sorry if I sound like a dick, but who're you/the devs to tell other people what they should use? It's not like you can force other people to think the same way you do. You just gotta present the pros and cons and let them make a decision.

This is one of the things I really dislike about this "scene", and ironically it bashes against your stance (on this thread). Whenever a newbie comes up all they're told is "get a9lh and luma" instead of properly explained what they are. It's borderline ridiculous how many messages I read saying "lol idk anything about this but I did it anyways". Most people consider it a good thing because they didn't brick and such. I share this sentiment, but on the other hand I consider it a negative part because then you get a flood of people that know absolutely nothing about the topic.

If anything, I'll probably just push a good few updates first then just push to a legacy branch and the main branch will be a9lh only or something.. someone can make a universal a9lh loader for ninjhax if they want

*hax? got you covered fam
mset is a completely different beast, but if you can get mset chances are high that you have access to hax, so...

 

[nechigawara]

It's not like you can force other people to think the same way you do. You just gotta present the pros and cons and let them make a decision.

Not many person who think like me. Lately, I always use this paragraph or similar one when do the suggesting.
(Since the lastest one is for ReiNAND user, so the CFW in this paragraph is ReiNAND instead of Luma3DS)

There is 4 things you need to know right now, of course, about 3DS hacking.

1. 3DS exploit: This is a way allow to run somethings that normally can't run such as homebrew, etc. Example of 3DS exploit are menuhax, arm9loaderhax, fasthax, etc.
2. 3DS CFW: This is what you want to allow your 3DS to add more function to FW, such as out of region cart load, pirating, ETC. This one need 3DS exploit to be able to run. Example of CFW is Luma3DS. ReiNAND, Corbenik.
3. SysNAND: This is your System OS that run on the 3DS.
4. EmuNAND: The clone of your SysNAND that store on SD card. This one is need to allow CFW to run without some exploit such as menuhax getting remove by Nintendo update

Your current setting is menuhax (an Exploit) + ReiNAND (CFW) + EmuNAND
The choices you have here are:

1. Installing Arm9loaderhax (A9LH) Exploit with ReiNAND CFW. Can be done by following this guide: http://3ds.guide/ by replacing Luma3DS file with ReiNAND instead. This setting is mostly safe from removed by Nintendo.The problem is, this setting require user to hack into 3DS System files. So it has a small risk of brick. But, if you're understand and following every step of the guide I gave you correctly. Even though you bricked, it can still be fix by hardmod. This setting won't need EmuNAND anymore, but you can still keep using it.
   
2. Keep menuhax Exploit and Updating ReiNAND CFW to the lastest version. Just replace old ReiNAND file with a new one and you're done. This one is more safer in installing state. But, drain SD card space for cloning SysNAND into EmuNAND, and has a chance getting remove if you update to next firmware when you accindently boot to SysNAND.

And let them pick their choice. Strangly, most people after reading the paragrash pick A9LH, although I already explain the risk.

 

[Deleted User]

There are people who got black screen even though they followed the guide correctly (That's what they claim)
Such as @Lilligant case that nobody can find it cause since it fixed already. Also @amximo case that we not sure what the cause of his problem.
So, I would say there always a risk but very very very low.

Atleast, if users were following the guide correctly and created a Nand Back Up, the brick can still be fixed by hardmod except some user error brick.

Yeah but still,the odds are very rare if we compare it to the percentage of people who don't brick and follow the guide perfectly.

 

[gnmmarechal]

Menuhax work on 11.2: How to Autoboot EmuNAND on FW 9.0.0-11.2.0 (without A9LH).

AFAIK, 11.2's MenuHax aka BannerHax doesn't autoboot.