I was installing a9lh on a friends o3ds and found a series of problem throughout the process: First the emunand didn't want to boot up, I ended up changing the sd card and the CFW I was using and eventually it started to boot up. But the CFW would stop working after each entry into emunand (regardless of if I used rxtools or reinand, luma wasn't working for me) and would start working again randomly after a number of tries (entering sysnand once seemed to fix it, but correlation doesn't equal causation). After that I managed to downgrade the emunand, but I needed to defrag the ctr partition because a previous gateway downgrade had left the system in a fragmented state. I also needed to stop using reinand because it was preventing native firm from being downgraded. This should be included in the guide instead of that "use whatever CFW you want" crap. Specially the part about the gateway downgraded fucking up the system like that. After all that trouble I managed to flash my downgraded nand to the sysnand, got the otp, re-flashed the original nand and was back safe and sound on the menuhax booted homebrew launcher. Everything was awesome! I finished setting a9lh and luma to auto boot emunand and everything was working fine!...... Except the sysnand, it refuses to boot no matter how many time I re-flash it. I even tried flashing my emunand into it, but nothing seems to work. Right now I am suspecting that it has something to do with a9lh, but I have no way of confirming that. I don't want to give the system to my friend in that state, any ideas what could have gone wrong? If it is important, I have been re-flashing it using decrypt9 loaded through the luma payloads and with the keep a9lh option.