Hacking Improving boot rate on CFW Emunand without A9LH?

  • Thread starter Thread starter gaboumafou
  • Start date Start date
  • Views Views 1,492
  • Replies Replies 10

gaboumafou

Well-Known Member
Member
Joined
Dec 23, 2006
Messages
489
Reaction score
2
Trophies
1
Website
Visit site
XP
614
Country
Canada
Hi!

I recently downgraded and installed an emunand on my n3DS and I love it! There's only one annoyance: my CFW sometimes crash to a black screen on launch (I'd say about 5-10% of the times).

I use lesshax to replace the normal menuhax, so this part boots flawlessly; the problematic part is the CFW boot part. I tried the following: CTR Boot Manager booting Reinand (this had the worst boot rate), BootCTR with Reinand, Reinand alone and AuReinand alone. The last three boot most of the times, but there's still a 5-10% chance it'll crash and that can be annoying.

I'd like to avoing A9LH, at least for the time being. Downgrading and setting up Emunand was already a challenge for me, so A9LH in its current state is pretty intimidating and I don't really have the time to get it. On top of that, I like the way the Emunand setup works, so I'm in no hurry to change it.

So do the experts here have some tips to ensure a boot rate as reliable as possible with my setup? A particular combination of boot manager and CFW that works best? A setting to change somewhere?

By the way, I'm on n3DS XL, 9.2 sysnand and 10.7 emunand, and use a 32gb microSD if that changes anything.
 
Doing the otp guide is not that hard, it it will swap your sysnand with emunand

and that's why i returned using menuhax.
 
Doing the otp guide is not that hard, it it will swap your sysnand with emunand

and that's why i returned using menuhax.

Nobody said you had to give up emuNAND at all. Just because the guide might suggest it doesn't mean you have to do it. Once you have A9LH installed, you can do whatever you want.
 
Doing the otp guide is not that hard, it it will swap your sysnand with emunand

and that's why i returned using menuhax.
you don't have to switch your NANDs when you start using arm9loaderhax, just don't put "NAND.bin" at the root when you use the installer 3dsx and they won't be switched unless you choose to
 
  • Like
Reactions: aos10 and daxtsu
By the way, I might ask here, is there a better choice between Reinand VS Aureinand with my current setup? I upgraded yesterday from Reinand to the latest version of Aureinand and I THINK boot rate got slightly worse, but it's hard to tell without extensive testing...
 
By the way, I might ask here, is there a better choice between Reinand VS Aureinand with my current setup? I upgraded yesterday from Reinand to the latest version of Aureinand and I THINK boot rate got slightly worse, but it's hard to tell without extensive testing...

On MenuHax, there's little difference between vanilla Rei and AuRei, aside from the fact that AuRei doesn't have the version string, works on O3DS, and now supports an optional bottom splash screen too. Switching between one or the other shouldn't change your boot rates much.

Regarding the OP, all you can really do is try different boot managers with different boot delays. CFW booting via MenuHax can fail in 3 main places:

  1. On a white screen when MenuHax first starts
  2. On a yellow screen just before it boots the payload
  3. When your CFW boots, typically resulting in a black screen if Brahma failed
There really isn't a way to improve it aside from boot managers and delay values, like I said. MenuHax and Brahma rely on "race attacks", which basically means that the homebrew code has to beat the regular Home Menu, or else it'll crash, and thus they won't always succeed.
 
you don't have to switch your NANDs when you start using arm9loaderhax, just don't put "NAND.bin" at the root when you use the installer 3dsx and they won't be switched unless you choose to
Finally some help here
No body told me not to put the NAND.bin on the root of SD card.
 
Finally some help here
No body told me not to put the NAND.bin on the root of SD card.
the guide was changed to support sysnand cfw because apparently it's "no less safe than using emunand". I don't really support this decision though, so there you go.
 
On MenuHax, there's little difference between vanilla Rei and AuRei, aside from the fact that AuRei doesn't have the version string, works on O3DS, and now supports an optional bottom splash screen too. Switching between one or the other shouldn't change your boot rates much.

Regarding the OP, all you can really do is try different boot managers with different boot delays. CFW booting via MenuHax can fail in 3 main places:

  1. On a white screen when MenuHax first starts
  2. On a yellow screen just before it boots the payload
  3. When your CFW boots, typically resulting in a black screen if Brahma failed
There really isn't a way to improve it aside from boot managers and delay values, like I said. MenuHax and Brahma rely on "race attacks", which basically means that the homebrew code has to beat the regular Home Menu, or else it'll crash, and thus they won't always succeed.
Thanks a lot. Steps 1 and 2 are fixed on my side with lesshax: it's really efficient and never crashed on me so far. It's step 3 that's sometimes causing problem. Do you have a link with more detailed explanation on how to implement delay for maximum boot rate? I feel this might be loooooooong to tweak and test without any point of reference.
 
the guide was changed to support sysnand cfw because apparently it's "no less safe than using emunand". I don't really support this decision though, so there you go.
Thank you again

So now when i reach to that point, i don't put the nand.bin (it was renamed from original_emunand.bin)
What should i put instead?
 

Site & Scene News

Popular threads in this forum