Audioboxer if you update through system settings it can lead to a brick, Shadow updated using Sysupdater with the Native_firm.cia removed, later he installed the native_firm but I would advise against it at the moment.

I have no bloody idea why it worked that way. Native Firm IS installed as a TITLE too so maybe that's why it works when installed via cia rather than system settings, i dunno.That's fair, but how come installing the update package and NATIVE_FIRM seperately works for avoiding an update brick?
That sounds really weird.
You can use reinands arm9loaderhax.bin it boots very fast and you dont have to remove arm9loaderhax from sysnandYeah don't worry I'm not going to. Just wondered how Shadow got to 10.5. I'm currently setting up an emunand again, and restoring my 9.2 sysnand backup to remove arm9loader from sysnand (for now). I survived a brick scare earlier, best to get my noob ass back to the land of emunand where idiots can survive.

I just like pushing the boundaries.Audioboxer if you update through system settings it can lead to a brick, Shadow updated using Sysupdater with the Native_firm.cia removed, later he installed the native_firm but I would advise against it at the moment.
You can use reinands arm9loaderhax.bin it boots very fast and you dont have to remove arm9loaderhax from sysnand
I just like pushing the boundaries.(plus i can recover easily haha)
Yeah I will. No reason to leave arm9loaderhax in sysnand though, would rather it's clean. So if I bugger up emunand I can just pull the sdcard and load into sysnand.
Or it may well be arm9loader has to be in sysnand to even boot Rei emunand in the first place. I assume it may well have to be considering I don't know how you'd get emunand to boot without it. Now that I think of it.
Pushing the limits/boundaries, huh..
Back on topic though:
You have to leave it in sysnand, or you won't have access to the hack. Or am I misunderstanding you?
I assume it doesn't need to be installed in emunand then? Rei's loader.bin just points Rei to emunand.Yeah I just thought along those lines. This is why noobs like me should either have a hard mod or GTFOI assume it doesn't need to be installed in emunand then? Rei's loader.bin just points Rei to emunand.

No, it doesn't.Yeah I just thought along those lines. This is why noobs like me should either have a hard mod or GTFOI assume it doesn't need to be installed in emunand then? Rei's loader.bin just points Rei to emunand.
I have setup reinand 3.2 as usuaslly and than copied the bin from Rei and on a other sdcard i have the sysnand payload(just in case i need to boot sysnand).Yeah I will. No reason to leave arm9loaderhax in sysnand though, would rather it's clean. So if I bugger up emunand I can just pull the sdcard and load into sysnand.
Or it may well be arm9loader has to be in sysnand to even boot Rei emunand in the first place. I assume it may well have to be considering I don't know how you'd get emunand to boot without it. Now that I think of it. We aren't using menuhax or a boot manager anymore.
No installation into emunand required, no (it'd be pointless).
No, it doesn't.![]()

The filename shouldn't be a problem as i did it myself with the same filenames.in the comand at a "." before the xorpad "nand.fat16_0x5_.xorpad"

Because ReiNAND is doing a firmlaunch to a newer FIRMWould there be something stopping decrypt9/emunand9 loading via HBL on my amr9 rei 9.2 sysnand setup?
They both just kick me back to the HBL.