I messed up two things but it was nothing that compromised the consoleI just went almost blind but followed the guide to the letter,Only problem i had was i named a file the wrong name LOL.
I messed up two things but it was nothing that compromised the consoleI just went almost blind but followed the guide to the letter,Only problem i had was i named a file the wrong name LOL.
The problem is OP doesn't have a Nand backup created by Decrypt9 since he use safehax to boot SafeA9LHinstaller, skip to A9LH installing state with his O3DS OTP.I have unbricked systems using the plaintext method,, and I have always tried to discourage end users from trying to hardmodding themselves (too many complete screw up for my liking), it would be better for him to send it off to someone else and maybe they would be able to unbrick for him, but yeah your right someone who can't follow simple instructions would probably screw up even worse than they already have
With the known plaintext attack, he doesn't need a NAND backup. Maybe one of the hardmodders can do it for him. @vb_encryption_vb ?The problem is OP doesn't have a Nand backup created by Decrypt9 since he use safehax to boot SafeA9LHinstaller, skip to A9LH installing state with his O3DS OTP.
With the known plaintext attack, he doesn't need a NAND backup. Maybe one of the hardmodders can do it for him. @vb_encryption_vb ?
So the way to fix this by plaintext attack or somthing only avaliable by him then?Other than the hardmod, I don't even know where to begin with this. I'm not sure how @gamesquest1 managed to unbrick. I assume dumped and patched NAND manually with hex?
The problem is OP doesn't have a Nand backup created by Decrypt9 since he use safehax to boot SafeA9LHinstaller, skip to A9LH installing state with his O3DS OTP.
yeah I kow this, all he would need to revert back to stock would be the plaintext of one of the firm partitions, AFAIK this should be the firm0.bin in the a9lh folderOther than the hardmod, I don't even know where to begin with this. I'm not sure how @gamesquest1 managed to unbrick. I assume dumped and patched NAND manually with hex?
well it's less known/used because if it weren't for people being stupid it wouldn't be neededSo the way to fix this by plaintext attack or somthing only avaliable by him then?
I think this plaintext method won't be famous since less people know it.