- Thread starter Shadowhand
- Start date
- Views 76,655
- Replies 456
- Likes 7
I've been busy irl so I haven't had time to check if it works on latest implementations of A9LH.
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
If you need a tester, you know you who to PM. I have both an old3DS and new3DS ready to test on.
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.
Last edited by 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.
@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.
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.
Last edited by MelonGx,
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.
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).
Last edited by 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.
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.
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?
After re-reading the posts above:
This is, what I was talking about. I just want to make sure, that I am in the same boat.
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?
So this still holds true for me, beeing on said V2 A9LH and ShadowNAND?
After re-reading the posts above:
^
This is, what I was talking about. I just want to make sure, that I am in the same boat.
Last edited by MiePx3,
Similar threads
-
-
@
Psionic Roshambo:
One thing that just occurred to me.... The sound on the 2600 sucked less back then the harsh sound we hear now is from infinitely better speakers we have now, back when the 2600 was new speakers produced a almost muffled sound, like CRTs made old graphics look slightly better. -
@
Psionic Roshambo:
I wonder if I could recommend that to some emulation devs that perhaps the sound could use some smoothing out to simulate those old TVs
-
@
Psionic Roshambo:
I think a few of the early systems could benefit from that, at least up to the 8 bit generation, by the 16 bit generation I think TVs had gotten a lot better in almost every way
-
-
-
-
-
-
-
-
-
-
@
Xdqwerty:
it says it only works for the original R4, R4i Gold (r4ids.cn), R4iDSN (r4idsn.com) and Acekard R.P.G. -
-
-
-
-
-
@
Psionic Roshambo:
Just give it a try, but honestly if you have a 3DS you can play DS games without a card just off the internal SD card
-
-
-
-
-
