Fair point.No these are both banned systems. Far less likely to be useful.
Damn.
I opened the newly created payload on my SD card in a hex editor, searched for "boot.3dsx" in text, replaced it with "luma.3dsx" and save, moved the Luma3DS .3dsx to the root of my SD, and rename it to "luma.3dsx"What did you do with the previous boot.3dsx?
It's fine. Just need a way to clear the movables and LFC permanently to inject clean ones from my unbanned 3ds.Yeah sorry for getting your hopes up, i got all excited too when I had 2 different Movable, but when I checked the LFC, the values were the same. as the new movable.
So generally speaking, generating a new movable is a bust.
Likely this fix can only be done by
1. Injecting unbanned LFC
2. Unbanned Movable values to LFC.
3. System Transfer to generate new Movable as the values must have to come from Nintendo and signed
If luma boot , you don't have replace the boot.3dsxI opened the newly created payload on my SD card in a hex editor, searched for "boot.3dsx" in text, replaced it with "luma.3dsx" and save, moved the Luma3DS .3dsx to the root of my SD, and rename it to "luma.3dsx"
Yeah sorry for getting your hopes up, i got all excited too when I had 2 different Movable, but when I checked the LFC, the values were the same. as the new movable.
So generally speaking, generating a new movable is a bust.
Likely this fix can only be done by
1. Injecting unbanned LFC
2. Unbanned Movable values to LFC.
3. System Transfer to generate new Movable as the values must have to come from Nintendo and signed
Why system transfert to a banned is impossible ?Ok, so I assume you can't do a system transfer to a banned 3ds?
My son's got banned... it had no Nintendo Id linked... so no eshop ban... don't think that helps though.
I never installed or played sumo so my 3ds is in the clear and still has my NNID.
do i paste what i copied and replaOh 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.
when you copy it over do you replace it too?Basic jist of what to copy over is as follows (sorry for bad handwriting lolol, ignore first 8 bytes (SEED...) and last 40 bytes.
Last 3 bytes of the seed should be 00
View attachment 69297
uhhhh if you're willing to do a bit of guided science you can definitely unban your sons 3ds, back up the movable.sed and localfriendcodeseed on both consoles and attempt to transfer from your clean one to his banned one, if it goes will both of you should have unique seeds,if it doesn't you can still use your own seed to have both unbannedOk, so I assume you can't do a system transfer to a banned 3ds?
My son's got banned... it had no Nintendo Id linked... so no eshop ban... don't think that helps though.
I never installed or played sumo so my 3ds is in the clear and still has my NNID.
You probably just missed out on this https://twitter.com/MegaMew_/status/799640179107647488so i slept for the past 49 pages what did i miss if anything?
its the luma patch, I think is pretty buggy atm and probably wont be in final lumaYou probably just missed out on this https://twitter.com/MegaMew_/status/799640179107647488
But i think nothing major has happened that helps those not into hacking themselves (i.e. Just following instructions)
When i copy these values, going to replace my friendseedcode tells me in hxd that it will change the file size, i dont think its supposed to do that right?do i paste what i copied and repla
when you copy it over do you replace it too?
Especially since it doesn't have random number generation (RNG) built into it to change the device-id. If you use that your device-id will be the same as everyone else's who uses it.its the luma patch, I think is pretty buggy atm and probably wont be in final luma