Can I just say that I'm astounded by everyone's ingenuity in creating this project

I am currently extracting the LFCS from a mii qr that I created on my console. I am only using an Intel integrated HD4600, so not sure how long it will take, but I'm not in a rush! I'll then extract the movable.sed using my i7. My issue is that I have a JPN 2DS LL, so unfortunately I'm not going to be able to use Blackfall's Dsihax injection service , but I see that some kind people with CFW already installed are offering to inject the hax manually, but I'm wondering if I'll need to find someone originally with a Japanese region console, or will it just work with any region?

Noticed that the No Homebrew and no friends with homebrew method was added to the readme:

[C - No homebrew and no friends with homebrew]

Currently for dedicated GPUs only. Needs Pycryptodomex installed. (pip install pycryptodomex)
1) Find a mii in mii maker that was created on YOUR system. That's very important. Make one from scratch if you're not sure where it came from.
2) Export the mii to a QR code. They're found in the "sdmc:/DCIM/100NIN03/" and named something like "HNI_1234.JPG".
3) Upload it to https://3ds.goombi.fr/editMii/ then "Import from -> QR code"
4) "Export to -> encrypted .bin"
5) Take resulting input.bin, place it in the seedminer/ directory, and run:
python seedminer_launcher.py mii new|old [year of 3ds manufacture]
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.

Click to expand...

How long does the bruteforcing here take? I've got an AMD 7950 pro at my disposal.

## stage 2 - DSIWARE exploit using TadPole:
1. put your movable.sed into the resources folder
2. put your ctcert.bin with the privkey into the resources folder (this file can only be generated by someone running cfw)
3. buy your dsiware game and install it
4. on the 3ds, go to settings->data management->dsiware->your dsiware game->copy
5. put the sd card into the comptuter and copy the dsiware bin from the following location to the tadpole folder: SD:/Nintendo 3ds/ID0/ID1/Nintendo DSIWare/####.bin where ### is the dsiware id
6. run the following command in the tadpole folder: .\tadpole.exe #####.bin d where #### is the game id

## OPT 1

7. download sudokuhax from the dsiware exploit guide
8. rename the sudoku_v0.app to srl.nds.inject
9. open the public.sav file using a FAT file mounter (OSFMount works well for this. google it)
10. delete all the files in the public.sav mount
11. move the savefile.bin from sudokuhax into the public.sav mount
12. unmount public.sav
13. move the srl.nds.inject file into the game folder (Tadpole/#####/)

## OPT 2

7. download and extract 3ds_dsiwarehax_installer
8. copy the public.sav from 3ds\3ds_dsiwarehax_installer\dsiware\<titleid>\public.sav to Tadpole\<titleid>\public.sav where <titleid> is the title id of the save injection title
9. when asked to overwrite, do.
10. to 13. Be Happy you others did some work for you

## Continue

14. run the following command: tadpole.exe ##### r
15. renamed the patched file by removing .patched from the filename.
16. copy the patched file to the dsiware folder on the SD overwriting the existing
17. put the SD back into the 3ds and go to settings->data management->dsiware->microsd (at the top)->game->copy
18. acknowledge the "this exists on system already" error
19. Move on with Section V of the guide (3ds.guide -> DSiWare entry point -> install b9s)

uuh so how long is long i already started it plus its not my pc so i cant swap parts

Click to expand...

It's basically random due to it being unknown where your seed is. But from my experience, what someone on a CPU took 5 days, it only took me 50 minutes. And the whole process finished after about 1 hour. Other finished in 5 and 10 minutes. Some take longer, but the first one of 1h was the slowest one for me, but that's with a decent GPU (RX480).

If you are unlucky and you have a very late seed, you may nee dto go to step, say, 2048 - which would take about a month on the first example - and only about 3-4 hours on my GPU.

As the OP mentions, Integrated Graphics may be _even worse_ - so you could be facing a non-stop, 40-day calculation going on.

It's basically random due to it being unknown where your seed is. But from my experience, what someone on a CPU took 5 days, it only took me 50 minutes. And the whole process finished after about 1 hour. Other finished in 5 and 10 minutes. Some take longer, but the first one of 1h was the slowest one for me, but that's with a decent GPU (RX480).

If you are unlucky and you have a very late seed, you may nee dto go to step, say, 2048 - which would take about a month on the first example - and only about 3-4 hours on my GPU.

As the OP mentions, Integrated Graphics may be _even worse_ - so you could be facing a non-stop, 40-day calculation going on.

It's basically random due to it being unknown where your seed is. But from my experience, what someone on a CPU took 5 days, it only took me 50 minutes. And the whole process finished after about 1 hour. Other finished in 5 and 10 minutes. Some take longer, but the first one of 1h was the slowest one for me, but that's with a decent GPU (RX480).

If you are unlucky and you have a very late seed, you may nee dto go to step, say, 2048 - which would take about a month on the first example - and only about 3-4 hours on my GPU.

As the OP mentions, Integrated Graphics may be _even worse_ - so you could be facing a non-stop, 40-day calculation going on.