Hacking Official SaltFW - "Slim Alternative Firmware"

[rasputin]

Black screen no boot up here? Any ideas, i just put the a9lh bin file on root, and nothing.

Edit, eur 2ds 11.2 a9lh, and luma 6.6 works ok

 

[Shadowhand]

Black screen no boot up here? Any ideas, i just put the a9lh bin file on root, and nothing.

Edit, eur 2ds 11.2 a9lh, and luma 6.6 works ok

I've been busy irl so I haven't had time to check if it works on latest implementations of A9LH.

 

[The Catboy]

I really wish more updates would come of this. This the perfect CFW for the CTRNAND. The LTS design makes it perfect for anyone who just wants to install a CFW to their CTRNAND and never touch it again

 

[Shadowhand]

I really wish more updates would come of this. This the perfect CFW for the CTRNAND. The LTS design makes it perfect for anyone who just wants to install a CFW to their CTRNAND and never touch it again

Coming soon.

 

[The Catboy]

Coming soon.

If you need a tester, you know you who to PM. I have both an old3DS and new3DS ready to test on.

 

[The Catboy]

SaltFW does not work on 11.3

 

[Shadowhand]

SaltFW does not work on 11.3

Investigating

EDIT: try these builds: https://up1.secretalgorithm.com/#9nWto0_NMY-nziPd5cWaaw
Pick the one for your a9lh fork, or the reboot patches won't work.
There are no splashes yet. It also works from CTRNAND.

 

[The Catboy]

Investigating

EDIT: try these builds: https://up1.secretalgorithm.com/#9nWto0_NMY-nziPd5cWaaw
Pick the one for your a9lh fork, or the reboot patches won't work.
There are no splashes yet. It also works from CTRNAND.

Tested on both old3DS and new3DS, working just fine. And if you are using the current A9LH (the one that allows CFWs to be booted from CTRNAND,) then you should just be able to get bootsplashes working through arm9loaderhax_si.bin

 

[Shadowhand]

Tested on both old3DS and new3DS, working just fine. And if you are using the current A9LH (the one that allows CFWs to be booted from CTRNAND,) then you should just be able to get bootsplashes working through arm9loaderhax_si.bin

I disabled splashes altogether because the new version is in heavy development.

 

[The Catboy]

I disabled splashes altogether because the new version is in heavy development.

Ah, alright I haven't tested copying to the CTRNAND yet.

 

[MelonGx]

@Aurora Wright @Shadowhand
An old era ShadowNAND+SaltFW (which boots chain-payloads on /homebrew/boot.bin) causes 11.3.0-36J Luma broken on this GSP process, while AR's A9LH fork + 11.3.0-36J Luma doesn't.

This type of old-era-ShadowNAND is pre-installed by TGBUS and sold over 1,000 pcs so it may be popular. But unfortunately I don't own such a 3DS that I can't give out any solution myself.

 

[Shadowhand]

@Aurora Wright @Shadowhand
An old era ShadowNAND+SaltFW (which boots chain-payloads on /homebrew/boot.bin) causes 11.3.0-36J Luma broken on this GSP process, while AR's A9LH fork + 11.3.0-36J Luma doesn't.
View attachment 77515
This type of old-era-ShadowNAND is pre-installed by TGBUS and sold over 1,000 pcs so it may be popular. But unfortunately I don't own such a 3DS that I can't give out any solution myself.

I haven't had time to actually investigate what changes 11.3 brought that'd break things. However, both ShadowNAND and SaltFW are going to be updated soon, and I can confirm there are working (private) builds for both that work on 11.3.

 

[The Catboy]

@Aurora Wright @Shadowhand
An old era ShadowNAND+SaltFW (which boots chain-payloads on /homebrew/boot.bin) causes 11.3.0-36J Luma broken on this GSP process, while AR's A9LH fork + 11.3.0-36J Luma doesn't.
View attachment 77515
This type of old-era-ShadowNAND is pre-installed by TGBUS and sold over 1,000 pcs so it may be popular. But unfortunately I don't own such a 3DS that I can't give out any solution myself.

I suggest suggest until ShadowNAND updates to use the Guide to update your A9LH and copy Luma3DS onto it.
https://3ds.guide/updating-a9lh
You can safely update from ShadowNAND using the guide, I know because I've done it on several 3DS's

 

[MelonGx]

I suggest suggest until ShadowNAND updates to use the Guide to update your A9LH and copy Luma3DS onto it.
https://3ds.guide/updating-a9lh
You can safely update from ShadowNAND using the guide, I know because I've done it on several 3DS's

I don't know if it works on Old Era ShadowNAND (which boots chain-payload on /homebrew/boot.bin) because all the reported upgrade (included yours) are based on New Era ShadowNAND (which boots chain-payload on /homebrew/3ds/boot.bin).

 

[The Catboy]

I don't know if it works on /homebrew/boot.bin Old Era ShadowNAND because all of the reported upgrade (included yours) are based on /homebrew/3ds/boot.bin New Era ShadowNAND.

It won't, you will have to use the "arm9loaderhax.bin" provided in the latest nightly. That one can be copied to your CTRNAND and basically works the same as ShadowNAND.

 

[MelonGx]

It won't, you will have to use the "arm9loaderhax.bin" provided in the latest nightly. That one can be copied to your CTRNAND and basically works the same as ShadowNAND.

You haven't answer my question.
I'm asking whether old era ShadowNAND is different from new era ShadowNAND or not.
Since directly upgrading A9LH on some incompatible A9LH fork with SafeA9LHInstaller may cause a brick, New Era ShadowNAND is safe to upgrade != Old Era ShadowNAND is safe to upgrade.

 

[The Catboy]

You haven't answer my question.
I'm asking whether old era ShadowNAND is different from new era ShadowNAND or not.
Since directly upgrading A9LH on some incompatible A9LH fork with SafeA9LHInstaller may cause a brick, New Era ShadowNAND is safe to upgrade != Old Era ShadowNAND is safe to upgrade.

Bricks like that have long been fixed. You won't updating to ShadowNAND, you will be updating your ShadowNAND build to the latest A9LH. Which then allows you to copy/launch your CFW from your CTRNAND. It also allows all features of the CFW such as reboot patches, ect. to work, something ShadowNAND does not have.
Most likely the next update to ShadowNAND will add these. But for now, this is a working fix.

 

[Shadowhand]

Bricks like that have long been fixed. You won't updating to ShadowNAND, you will be updating your ShadowNAND build to the latest A9LH. Which then allows you to copy/launch your CFW from your CTRNAND. It also allows all features of the CFW such as reboot patches, ect. to work, something ShadowNAND does not have.
Most likely the next update to ShadowNAND will add these. But for now, this is a working fix.

There are no public builds/code of a CTRNAND-capable ShadowNAND out there yet.

 

[The Catboy]

There are no public builds/code of a CTRNAND-capable ShadowNAND out there yet.

I know, I said that <_<

 

[MiePx3]

Quick question, hope you guys dont mind.
The last time I did anything on my 3DS was when "V2" A9LH came out, and you had to be careful using the right files with the right installer, otherwise you would risk a brick. I never used SafeA9LHInstaller, only the ShadowNAND variant.
Has anything like this happend again? Is there a "V3" A9LH?

https://3ds.guide/updating-a9lh
You can safely update from ShadowNAND using the guide, I know because I've done it on several 3DS's

So this still holds true for me, beeing on said V2 A9LH and ShadowNAND?

After re-reading the posts above:

Since directly upgrading A9LH on some incompatible A9LH fork with SafeA9LHInstaller may cause a brick, New Era ShadowNAND is safe to upgrade != Old Era ShadowNAND is safe to upgrade.

^
This is, what I was talking about. I just want to make sure, that I am in the same boat.