thank youI can do it after i do the other one, it could take another hour for this one,
thank youI can do it after i do the other one, it could take another hour for this one,
thank you
movable.sed dumped to file!
msed_data will also be written to
msed_data_00005E72.bin
please share if you can!
done.
653.82 seconds, 604.73 M/s
Press any key to continue . . .
add 0319-2898-7891OK, I've been trying to bruteforce my movable_part1.sed from a mii image for the last 3 days using my integrated HD4600. I'm currently on an offset of 246, but I'm getting a little bored with it now. Is there anyone with CFW that could give me my LFCS, my friend code is 2552-6741-4832. Many thanks in advance
add 0319-2898-7891
I will also need the long 32 character folder from your "Nintendo 3DS" folder on your SD Card then I can bruteforce it
being a New3DS it should be done in 10-25minsAm adding you now, the code is
8715bb097d9e87532ed921162970646c
Thanks Hunter
Am adding you now, the code is
8715bb097d9e87532ed921162970646c
Thanks Hunter
movable.sed dumped to file!
msed_data will also be written to
msed_data_00005D68.bin
please share if you can!
done.
27.13 seconds, 607.64 M/s
Press any key to continue . . .
it's getting faster and faster, the more we hack, the more data we get, the more data we get, the faster it getswow, that was quick!
Yeah. Add 3540-4016-4154Could someone give me a hand getting the LFCS/ID0? Friend code is 0963-0294-9533
Could someone give me a hand getting the LFCS/ID0? Friend code is 0963-0294-9533
Starting it now. Here's a movable.sed @zoogieIs anyone able to bruteforce my "movable_part1" file for me. I am not able to get the program to do it running on my computer. I appriciate any help with this, thank you.
That was from a New 2DS XL or whatever that was bought a week ago. Took 2000 seconds to get on my 1080ti. I thought I did something wrong lolStarting it now. Here's a movable.sed @zoogie
Do you have the movable_part1.sed or are you still brute-forcing the mii qr itself?I've been bruteforcing this for like 7 hours on GPU and it's at offset 2726 and it's still going. What might have gone wrong? I did the Mii QR method.
readme said:NOTE: If you have a new3ds, you *might* have to choose "mii old". If you sys-transferred from an old3ds, and have ever system
formatted, you will need to select old. Although an incorrect guess will cause the brute force to fail, you can try the other
option next time.
NOTE2: You can optionally select the year you guess the 3ds was manufactured. This is done in hopes of reducing the brute-force time.
If you have no clue, just don't enter a year. The brute force will then start in the midpoint of the possible LFCS range.
A wrong year guess will not fail the brute force.
(old3ds 2011-2017, new3ds 2014-2017 inclusive are accepted year options)
7) Wait until movable_part1.sed dumps then move on to brute forcing movable.sed.
Yeah, I got the movable_part1.sed, I'm still bruteforcing the movable.sed.Do you have the movable_part1.sed or are you still brute-forcing the mii qr itself?
If you're having trouble, remember these parts of the readme:
so you have the correct ID0 ?Yeah, I got the movable_part1.sed, I'm still bruteforcing the movable.sed.