Homebrew SafeA9LHInstaller

[chronoss]

Use screeninit version.

that's what I used

 

[astronautlevel]

that's what I used

Then you're doing something wrong, Wolfvak has confirmed it to be working.

 

[chronoss]

Then you're doing something wrong, Wolfvak has confirmed it to be working.

ok, I see my files

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

Oups, I made a wrong analysis is CtrBootManager doesn't work

 

[liomajor]

Oups, I made a wrong analysis is CtrBootManager doesn't work

CtrBootManager does work for me, maybe you are using an outdated version.

 

[chronoss]

CtrBootManager does work for me, maybe you are using an outdated version.

I use the last version...

 

[liomajor]

I use the last version...

This is the one i'm using and it works well for me.

Remove .txt

 

[chronoss]

This is the one i'm using and it works well for me.

Remove .txt

Thanks, it work

 

[tvo770]

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?

 

[Redferne]

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?

Did you try the file just two posts above yours?

 

[tvo770]

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.

 

[AkGBA]

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

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

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

Or better : http://luma3ds.ericchu.net/

 

[kedest]

So this new v2 is needed for 'future compatibility' people are saying.
What does that mean exactly? Will there be .bin payloads in the future that will only run on v2?

 

[RacsoSakuraba]

The uninstall option have accident insurance? Something like Decrypt9, bottom combination, there are all kinds of people in the world.

 

[ihaveahax]

The uninstall option have accident insurance? Something like Decrypt9, bottom combination, there are all kinds of people in the world.

yes; it also doesn't work if it detects FIRM 11.0 or higher.

 

[AkGBA]

derp

 

[Mewz]

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

 

[Supster131]

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

 

[Mewz]

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

Yep, that was my issue. Now I feel silly for not checking that - thanks!

 

[Raylight]

I'm following Plailect guide on how to update a9lh and i used Fix94 arm9select so how do i go about updating

 

[DjoeN]

@Aurora Wright
So what's the thing with arm9loaderhax.bin and arm9loaderhax_si.bin? (i know it's no screen init and screen init)

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

I used latest github versions and don't have an arm9loaderhax_si.bin how do i switch? i only have arm9loaderhax.bin (compiled from safea9lhinstaller) and payload_stage1.bin and payload_stage2.bin (compiled from your armloaderhax fork) (and yes i know i need firm0 etc... but those i have)
Do i need a switch to compile the the _si.bin version?