Hacking Payloads Problems

[JCCG1989]

I've seen this theme around in many posts but I didn't find a solution yet.

I used to trigger my payloads menu with start+power button but since Luma update that method will only autoboot my SysNAND without the Nintendo 3DS banner. I checked my luma folder and (I don't know why) my "payload" folder is empty, however there is an "arm9lh-payloads" folder with all the payloads supposed to be on the "payloads" folder (Decrypt9, uncart, EmuNAND9, etc). I really need Decrypt9, can someone point at my any solution?

 

[chaser]

move or copy the payloads from the a9lh/payloads folder to the luma/payloads folder? make sure the filename for each payload is preceded with a ds button name (eg down_Decrypt9.bin or start_Hourglass9.bin).

 

[JCCG1989]

move or copy the payloads from the a9lh/payloads folder to the luma/payloads folder? make sure the filename for each payload is preceded with a ds button name (eg down_Decrypt9.bin or start_Hourglass9.bin).

Yeah, but, previously the start+power method prompted the selection menu of those payloads, what happened to that list?

 

[chaser]

Not sure what selection menu you're talking about. Sounds like you've lost a payload from the luma/payloads folder that would give you the selection menu. It's not something I've ever used. Hopefully some others will be able to help you out.

 

[JCCG1989]

Not sure what selection menu you're talking about. Sounds like you've lost a payload from the luma/payloads folder that would give you the selection menu. It's not something I've ever used. Hopefully some others will be able to help you out.

I've found my issue, for some reason the BootManager stopped to work and it was needed to add a key for each payload, no need to move them from folder... Any idea why the BootManager9 is not working anymore?

 

[nechigawara]

I've found my issue, for some reason the BootManager stopped to work and it was needed to add a key for each payload, no need to move them from folder... Any idea why the BootManager9 is not working anymore?

Did you update your console A9LH?

 

[JCCG1989]

Did you update your console A9LH?

I was thinking on that, how can I know if it is updated?

 

[nechigawara]

I was thinking on that, how can I know if it is updated?

I mean, BootManager9 need screenint to work. if you updated your A9LH files using safea9lhinstaller to non-screenint or SDless (which change how screenint work), that should be the cause.

 

[JCCG1989]

I mean, BootManager9 need screenint to work. if you updated your A9LH files using safea9lhinstaller to non-screenint or SDless (which change how screenint work), that should be the cause.

Yeah, I have the SD-less version... So, there is not a way my BootManager will work?

 

[nechigawara]

Yeah, I have the SD-less version... So, there is not a way my BootManager will work?

Renaming BootManager9's "arm9loaderhax.bin" into "arm9loaderhax_si.bin" should work.

 

[JCCG1989]

Renaming BootManager9's "arm9loaderhax.bin" into "arm9loaderhax_si.bin" should work.

Is that the file inside the "luma" folder, right?

 

[nechigawara]

Is that the file inside the "luma" folder, right?

No, the file on the root. Normally, @Aurora Wright 's folk A9LH should load the file arm9loaderhax.bin when boot.
But, SDless version will also looking for arm9loaderhax_si.bin to initialize screen function.

Sorry, forgot that you use Luma3DS as main A9LH and use Luma to call BootManager9.

 

[JCCG1989]

No, the file on the root. Normally, @Aurora Wright 's folk A9LH should load the file arm9loaderhax.bin when boot.
But, SDless version will also looking for arm9loaderhax_si.bin to initialize screen function.

Sorry, forgot that you use Luma3DS as main A9LH and use Luma to call BootManager9.

Ok, lets try.

--------------------- MERGED ---------------------------

No, the file on the root. Normally, @Aurora Wright 's folk A9LH should load the file arm9loaderhax.bin when boot.
But, SDless version will also looking for arm9loaderhax_si.bin to initialize screen function.

Sorry, forgot that you use Luma3DS as main A9LH and use Luma to call BootManager9.

The screen turns on differently but still it does not boot the manager, I renamed the file as you said, any other idea?

--------------------- MERGED ---------------------------

Ill try to give you some context:

Before updating arm9lh I could run Bootmanager9 without problems, now I realized it wasn't booting with my usual configuration (start+power), I went to the payloads folder and copied BootManager and the spash folder, it wasnt booting either, as suggested by another used i renamed the file with a "start_" to bind a key and it started normally, but using any option (Hourglass9, Decrypt9, Carter, etc) it says the file is invalid despite those files are adequatelly set in their rutes. If I ignore the BootManager and I rename Decrypt9 for example to boot with start key it boots sucessfully.

 

[nechigawara]

Ill try to give you some context:

Before updating arm9lh I could run Bootmanager9 without problems, now I realized it wasn't booting with my usual configuration (start+power), I went to the payloads folder and copied BootManager and the spash folder, it wasnt booting either, as suggested by another used i renamed the file with a "start_" to bind a key and it started normally, but using any option (Hourglass9, Decrypt9, Carter, etc) it says the file is invalid despite those files are adequatelly set in their rutes. If I ignore the BootManager and I rename Decrypt9 for example to boot with start key it boots sucessfully.

May be with the current setting , Bootmanager9 cannot load properly with lastet Luma & A9LH SDless.
If I remember correctly, Bootmanager9 need to be the main A9LH, and using Bootmanager9 Auto boot to call Luma3DS.

 

[JCCG1989]

May be with the current setting , Bootmanager9 cannot load properly with lastet Luma & A9LH SDless.
If I remember correctly, Bootmanager9 need to be the main A9LH, and using Bootmanager9 Auto boot to call Luma3DS.

Seems I'll be bound to rename my payloads to boot them with keybinding isnt it? Thank you so much for you time.

 

[JCCG1989]

May be with the current setting , Bootmanager9 cannot load properly with lastet Luma & A9LH SDless.
If I remember correctly, Bootmanager9 need to be the main A9LH, and using Bootmanager9 Auto boot to call Luma3DS.

Seems I'll be bound to rename my payloads to boot them with keybinding isnt it? Thank you so much for you time.