So, I'm pretty sure I bricked a New 3DS last night. Following Plailect's guide to the T, and double checking everything, I loaded up SafeA9LHInstaller and pressed select to install, a message flashed on the screen too fast for me to read and the screen turned off. I left it for several minutes, followed glitched screen instructions just in case, left it a bit more, then finally did a hard reboot. Now anytime it is powered on, the blue light comes on, but the screens stay dark. I followed the troubleshooting suggestions, took out SD card, took out cartridge, tried recovery mode. Nothing. I'll eventually hard mod it along with a Japanese New 3DS I have on FW 11.2. In the mean time, I have another New 3DS that I've followed all Plailect's guide on up to the point of last night's failure. I'm now on 220.127.116.11U, I just made a NANDmin.bin and backed it up onto my computer, and now I'm a little nervous to proceed. I've read posts about other people having the problem I had, but it seems pretty rare. Part of me feels like as long as I check and double check every step of the guide, it should be just fine. And another part of me feels like I am about to have yet another brick on my hands... Any advice? I'm using the stock 4gb memory card, reformatted with Panasonic SDFormatter on my MacBook, then did a system format on the N3DS before going step by step through Plailect's guide. Is there a safer way than the OTPless method? Should I try the SafeA9LHInstaller 2.6.2 that released a day ago and says, "Try to fix the rare OTPless bricks by using ITCM instead of ARM9 memory." in the release notes? Or should I stick to the guide and use 2.5.1... ? Reading through several threads, I'm a little confused why the guide uses 2.5.1 and not a more current version. Is this because this was the current version when the guide was last updated, or is this the version that should be used?