Join the discord, send me the files and i shall.

(you can find the discord link on the 3ds guide page.)

 

Join the Discord, someone will most likely help you there.

Otherwise, this is what I've got written up, kudos to RandalHoffman:

Guide

## 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)

 

how long would the movable.sed process take on a amd acelerated parralel proccesing gpu

 

uuh so how long is long i already started it plus its not my pc so i cant swap parts and how many msed3 offsets are there?

 

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.

Just contact me on Discord and I'll do it for you real quick.

 

there's a Link to the homebrew discord on the 3ds.guide page. You can't miss it - just ask in the appropriate channel and we'll find each other.

 

Discord has text chat, which is the usual way to communicate in these types of dicord servers

 

One more (Bumblescumps)

 

So, after doing a bit of reading about this, I'm probably going to try this when I get my new 2DS XL. Ordered it at a very bad time as all the flash cart sellers are having a holiday (chinese new year lol ).
Just to get confirmation, OP said that this could get patched, does that mean that this exploit could get patched? Was wondering 'cause later he says that ntrboot is better for the long term. But if I install b9s using this method, will my cfw be safe from Nintendo?

 

once you have hacked your 3ds it's hacked, no different from ntrboot,
but in the future people may not be able to hack with this if they patch it