Yes.
This should help you. Put godmode9.firm to the root of your sd card and rename it to "boot.firm". And follow the guide then.
Unfortunately, bootrom error 8046 (aka, "Blue Screens of Death") is not fixable with CTRTransfer. Whoever last had that o2DS must have failed at their attempt at hacking it using hardmod or A9LH 2.1.0 firmware downgrade approach.
If the BSoD is due to hardmod, that means physical damage to the motherboard. If that o2DS ever had its SysNAND *.bin image backed up,
@Denisu12 might have gotten away with using EmuNAND.
A software based 8046 BSoD is recoverable if its SysNAND *.bin image was previously backed up before the brick. If the BSoD is due to bad firmware reflashing but that *.bin image was not made beforehand, one would have to resort to
Lazarus3DS using a donor o2DS/o3DS nand files dumped from the
[S:] SYSNAND VIRTUAL.
Short of having that o2DS original SysNAND *bin image, this category of bricks is considered terminal if its hardware and not for the faint of heart fixing/debugging if its software. Unless you're a masochism,
@Denisu12, you're better off buying a replacement o2DS motherboard from eBay or aliexpress. You want one that has its NAND (both the physical chip and flashrom within it) in working condition for a mobo swap job.
Or, you should cannibalize the o2DS for parts or get a different system.
