This method only works if you have done a system transfer before on the banned system.Can someone explain this betyer or preferibly make it into a video I am kinda lost but I do have a backup.
This method only works if you have done a system transfer before on the banned system.Can someone explain this betyer or preferibly make it into a video I am kinda lost but I do have a backup.
It doesn't even work anymore at all after 11.2, your moveable.sed will remain the same after a transfer. It wasn't really unbanning anyway, you're essentially using the certs from the other console just getting them differently. It used to just basically swap certs in a transfer, and why the target console would end up banned afterwards; or why you'd have a different moveable.sed if you'd done one previously.This method only works if you have done a system transfer before on the banned system.
My guide uses this method as method 2. Basically during a systransfer 2 systems swap a file called movable seed which stores info about the console. Some of this info is the local friend code seed b. So you can copy this info into local friend code seed b and inject it into a banned system to get unbanned.Can someone explain this betyer or preferibly make it into a video I am kinda lost but I do have a backup.
Dat Necro tho.Can someone explain this betyer or preferibly make it into a video I am kinda lost but I do have a backup.
I didnt know that method was patched. Good to know. I was aware it was using another systems certs, but saying the only way to unban is to get a new system / account isnt right, though. Account, yes. System, no. There are plenty of public LFCS_B's out there and they last a long time before getting banned. One I have from a place that shall remain un-named has lasted 6 months now, is used by easily 100 people, and is still unbanned to this day.It doesn't even work anymore at all after 11.2, your moveable.sed will remain the same after a transfer. It wasn't really unbanning anyway, you're essentially using the certs from the other console just getting them differently. It used to just basically swap certs in a transfer, and why the target console would end up banned afterwards; or why you'd have a different moveable.sed if you'd done one previously.
--------------------- MERGED ---------------------------
Either way anyone with a 022-2812 literally needs to accept that there is NO public way to get rid of this type of ban. Period. It's never going to happen. I'm not even going to mention the private method as it's entirely not feasible for public attempts; especially if you're not familiar with RAM processes and HeX editing. We all deserved that ban, some of us were lucky and able to reverse it before the method was patched, some of us weren't. Either way we all suffered and more than likely had to buy/use a second console to fix it anyway so it wasn't without detriment.
The only way you guys are going to get rid of it is to get a new console and make a new account. Yeah it sucks if you lose your NNID but in the words of Macbeth, "What's done is done."
Different kind of ban my friend...I didnt know that method was patched. Good to know. I was aware it was using another systems certs, but saying the only way to unban is to get a new system / account isnt right, though. Account, yes. System, no. There are plenty of public LFCS_B's out there and they last a long time before getting banned. One I have from a place that shall remain un-named has lasted 6 months now, is used by easily 100 people, and is still unbanned to this day.
thanks good to knowThis method only works if you have done a system transfer before on the banned system.
The method in question was never intended for the 022 error, it for the 002.... Not to mention a new LFCS_B will get you back online in games, even if you still have the 022 error. So its still wrong. You don't need to accept that you need a new system, you just need to accept that things like pokebank are off limits now.Different kind of ban my friend...
How do I inject LocalFriendCodeSeedB_B back into my sysnand? I was able to export it but there is no option to inject it back into my sysnandOh dear god it worked, it worked!
Acraeus, I could pay you a beer right now.
I just unbanned myself from 002 using nothing but my own 3DS! This is incredible. And I suck at writing tutorials of any kind, so please don't count on me when it comes to that!
But basically
1. Inject an old NAND backup from when you were still installing a9lh (I did one before)
2. Use Decrypt9 to extract movable.sed from it
3. Use Decrypt 9 to extract movable.sed and LocalFriendCodeSeed_B from your current NAND that is banned
4. Use HxD (hex editor) to compare your old movable.sed with your LocalFriendCodeSeed_B, see how offsets 00000000/08 through 00000110/07 is the SAME!
5. Open up your NEW movable.sed with HxD and copy offsets 00000000/08 through 00000110/07
6. Open up LocalFriendCodeSeed_B with HxD and CTRL+A and then paste what you just copied
7. Save, inject to sysnand
This is how I did it, don't blame me if something goes wrong because I'm even worse at giving instructions than following them.
EDIT: Ignore strikethrough text, that is no needed and was just a part of me finding out HOW to do it, you don't need to do that.