I restored my sysnand in order to have it clean so i can use emunand. I downgraded to 9.2.0 in order to do so since that's the OFW my sysnand backup was on and i had to dump boot0/1 on it since i didnt do that before. Now when I boot without RCM, it'll give me the BSoD. Using RCM and CFW will work just fine, but i cant use stock sysnand from hekate because it'll say "wrong ini cfg or missing files! failed to launch HOS!" and has said that before i restored the sysnand. I even tried updating...
Switch Blue Screening After SYSNAND Restore
Continue reading...
Switch Blue Screening After SYSNAND Restore
Continue reading...