I'm still banned from eshop/NNID stuff.
022-2812 is still affecting me, that only clears 002-0102
the serial in SecureInfo_A should only be 8 digitsJust one question before I go.
I messed up with my secureinfoA waaaay too many times, now I have no idea how many serials have gone through my 3DS... but how many digits are in the serial string?
Is it QWxxxxxxxx or QWxxxxxxxxx? 8 or 9? The back of my 3DS has the ninth digit spaced out a bit, so I'm not sure.
the serial in SecureInfo_A should only be 8 digits
--------------------- MERGED ---------------------------
You ignore the spaced out digit
Decrypt9
Ok so I just replaced the contents of my LocalFriendCodeSeed_B with the bytes from offset 00000000/08 through 00000110/07 from my moveable.sed, injected it, and I can play online and use the friend list. No 002-0102. I didn't use any files from any backups. I made a nand backup first just in case, but everything seems to still be fine.
So I'm a little confused -- if this works, what are we still talking about?
(Of course I'm still banned from the eShop with error code 022-2812)
Hello everyone, I've been lurking here since page 1 when all this started. I have a few questions regarding the method Ultros just did and explained.
1- I'm really rusted on this whole 3ds hacking stuff. So much I still have RXTools so I don't know if this method works with my cfw.
2- Does this work on any kind of 3ds? And last
3- Will I lose my current Emunand or any data?
For further reference, that last digit is the 'check digit' that is derived from the other digits.Ohh, then it's already correct. Thanks!
This thread has paid off big time, in more ways than sharing the grief lol. Congrats everyone.
A way to generate a different movable.sed for people who have the same value in both files.Ok so I just replaced the contents of my LocalFriendCodeSeed_B with the bytes from offset 00000000/08 through 00000110/07 from my moveable.sed, injected it, and I can play online and use the friend list. No 002-0102. I didn't use any files from any backups. I made a nand backup first just in case, but everything seems to still be fine.
So I'm a little confused -- if this works, what are we still talking about?
(Of course I'm still banned from the eShop with error code 022-2812)
were they similar or different? the offsets
A way to generate a different movable.sed for people who have the same value in both files.
So the relevant portions of movable.sed and LocalFriendCodeSeed_B seem to be the same for me. Do I actually need an old NAND backup then?Oh 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.
Should be. Unless Nintendo finally decided to ban people using CIA.Is it safe to go online with a ver16 copy off freeshop/CIAngel now?
I mean:it *should* be safe, but I don't think anyone knows for certain yet. I think there's no problem though, as long as you're using a good CIA