Video of the issue: Alright i'll go from start to finish, since i don't really know what is the issue here. what i had was this: a9lh sysnand 9.2 with aureinand emunand 10.6 obv with aureinand. Everything was working fine but then this update for a9lh came out, and my 3ds bricked, I hard modded my new 3ds xl and i always made Decrypt/emunand9 backups of every firmware i upgrade to. so i have .bin files of 2.1sys, 9.2sys a9lh and pre a9lh. emunand backups from 9.5 up to 10.7. so i restored my "non bricked" a9lh 9.2 sysnand backup by hard mod on to my nand, and boom my aureinand started working perfectly and booted my emunand on 10.6 i updated it to 10.7 no problems what so ever. but when i boot now with L or R trigger which should boot sysnand, i get a black screen and nothing but a black screen, and since i have a permanent hard mod, i could play around with my firmware's, here's what i've tried and found out: Restoring ANY firmware's a9lh or Non a9lh to my sysnand will result in black screen 3ds. if they are a9lh they will however boot emunand, if the backup only contains sysnand it will black screen from the boot on. if i put ANY firmware on sysnand and clone it by decrypt9 to emunand, the firmware will work perfectly, that means on my sysnand firmware's i always run a "sysnand warning theme" and cloning sysnand (not working) to emunand it will boot with those theme's and all my "usual sysnand" stuff fine in emunand, this mean's that my firmware's that i backup'd are fine. ofcourse i also tried to put my emunand (from 9.5/10.3-10.7) on sysnand with same results. black screens. Update: also Tried to restore 9.2 without a9lh and use the Recovery mode combination, no results too.. so conclusion: Everything works on emunand, everything that works on emunand does not work on sysnand, so what i can conclude is that it's not "firmware" related and my backups are all functional. but something blocks my stuff to boot in sysnand but they run perfect in emunand. if i validate my backup's with decrypt9 it shows me on 9.2 a9lh: FIRM0 section2 hash mismatch FIRM0 is corrupt (non critical) Validate NAND dump: secceeded! but even though it still boot's aureinand with that one. all other backup's show me just the Validate NAND dump: Succeeded! I have Samsung nand, all my backups show NCSD when opened with HxD, aureinand works on all the 9.2 sysnand backups that have a9lh,and can boot emunand, but holding trigger to boot sysnand results in black screen, i've also tried to transfer my 9.2 a9lh to emunand and wipe out all installed stuff + theme's to get a clean 9.2, restored that to sysnand and black screen. even restoring all of these with hard mod results in the same stuff. i Have latest EVERYTHING, i always update all tools and stuff, i have aureinand 4.2 decrypt and emunand latest, check them every day for update's. what i don't really get about nand stuff is the following: i have 1.21gb backup's but when i chose partition dump on decrypt it shows me twln twlp afbsave firm0 and firm1 and ctrnand. and some of those alone are 1.21gb so how do i restore a full sysnand with only 1.21gb, could it be that i restore not the full part of the NAND in my 3ds and something else is broken hence why i can't boot sysnand and. that would explain why all the stuff that doessen't run on sysnand works on emunand, but i could be totally wrong and hope that someone here can point me in the right direction. having no sysnand leaves me kinda forced to stay on a emulated software and blocks me from using gba.cia's and other stuff. i just rather have it working. even though emunand works fine.