Then you're doing something wrong, Wolfvak has confirmed it to be working.that's what I used
ok, I see my filesThen you're doing something wrong, Wolfvak has confirmed it to be working.
Oups, I made a wrong analysis is CtrBootManager doesn't work
I use the last version...CtrBootManager does work for me, maybe you are using an outdated version.
I use the last version...
Thanks, it workThis is the one i'm using and it works well for me.
Remove .txt
Did you try the file just two posts above yours?Can help me figure out what's going on when I use a boot manager payload like CtrBootManager or BootCTR9 and then try to boot luma3ds payload from it it seems to break ds mode GBA VCs causing them to black screen they work fine if I load directly the luma3ds payload. Dose anyone know a fix or workaround?
I did and it didn't fix anything but CtrBootManager was already successfully loading the issues is that loading luma through it breaks DS mode GBA VCs functionality.Did you try the file just two posts above yours?
I did and it didn't fix anything but CtrBootManager was already successfully loading the issues is that loading luma through it breaks DS mode GBA VCs functionality.
I did and it didn't fix anything but CtrBootManager was already successfully loading the issues is that loading luma through it breaks DS mode GBA VCs functionality.
It's a known limitation of luma. No fix, but there's a workaround. You have to use the pathchanger tool -> look at the wiki : https://github.com/AuroraWright/Luma3DS/wiki/Installation-and-Upgrade
yes; it also doesn't work if it detects FIRM 11.0 or higher.The uninstall option have accident insurance? Something like Decrypt9, bottom combination, there are all kinds of people in the world.
I had the same issue earlier. You're most likely using an old firm0.bin file.I keep getting told firm0.bin dosn't exist or has a wrong size. I'm trying to update a9lh on my n3ds, with the screeninit payload for A9LH. Currently my a9lh folder looks like this
/a9lh/firm0.bin
/a9lh/firm1.bin
/a9lh/otp.bin
/a9lh/payload_stage1.bin
/a9lh/payload_stage2.bin
/a9lh/secret_sector.bin
I had the same issue earlier. You're most likely using an old firm0.bin file.
Go to Plailect's guide and download the newest firm0 and firm1 files, use those instead
Merged screeninit and noscreeninit stage2s into one: arm9loaderhax.bin does not init the screen, while arm9loaderhax_si.bin does; added a built-in mini CFW in case no payload is found which loads FIRM from CTRNAND and patches signature checks and FIRM partition writes