Either. They do the same thing.by injecting 9.2 sysnand backup to emunand , right ? or just go to emunand restore and chose sysnand 9.2?
Either. They do the same thing.by injecting 9.2 sysnand backup to emunand , right ? or just go to emunand restore and chose sysnand 9.2?
I prefer a silent boot without the splash image and only having screen init when the payloads need it, but it's up to personal choice. You can use both kinds of A9LH just fine@Aurora Wright, would it be better to re-run the @dark_samus3 updater with my original stage0x5C000.bin that DOESNT have screen_init if I want to fully take advantage of your new update? Are there any real benfits to having screen_init now that AuReiNAND can load the payloads and how them without it?

Share your build of A9LH pls.I prefer a silent boot without the splash image and only having screen init when the payloads need it, but it's up to personal choice. You can use both kinds of A9LH just fine![]()
Share your build of A9LH pls.![]()
Flash it to emuNAND then. NAND backups are interchangeable (unless you use Gateway for emuNAND, in which case the FIRM partitions are no good for sysNAND, but this doesn't have to do with your situation).
I believe that is the case, but I don't have a gateway so I'm not quite sure.So if I used a gateway card to make the emunand, I cannot swap sysnand and emunand?

You should be able to.So if I used a gateway card to make the emunand, I cannot swap sysnand and emunand?
Use Decrypt9 (or maybe EmuNAND9, I can't recall which) to extract all of the partitions out of your emuNAND backup, except for the FIRM0 and FIRM1 partitions, then inject them all to sysNAND. As long as you leave FIRM0 and FIRM1 alone (thus keeping ARM9LoaderHax intact for if anything goes wrong), it should be fine.So if I used a gateway card to make the emunand, I cannot swap sysnand and emunand?
Use Decrypt9 (or maybe EmuNAND9, I can't recall which) to extract all of the partitions out of your emuNAND backup, except for the FIRM0 and FIRM1 partitions, then inject them all to sysNAND. As long as you leave FIRM0 and FIRM1 alone (thus keeping ARM9LoaderHax intact for if anything goes wrong), it should be fine.

You should be able to still swap. While Gateway will likely still have created a 2GB partition all the current *9 tools are smart enough to create a 1240MB version which can then be injected into sysnand.
partial update-> NOSo if I used a gateway card to make the emunand, I cannot swap sysnand and emunand?
ok, finished thatEither. They do the same thing.
Its possible in theory to do this from arm9, for example, because you can svcBackdoor on arm9, but the available memory for the arm9 thread is not very much, so its hard to fit all the code to it.ARM9 is a very dirty way. Like for the Ver string, it doesn't know *where* to patch, and so it will patch ALL the instances of that pattern in the 3DS FCRAM.
I don't want bad things to happen, and that's why I removed the Ver. patch in the first place. Both are suitable to do from ARM11.
If you look at the FMP source (I read through it today), if first locates the beginning of the memory info structs for the ARM11 processes, then it finds the Home Menu one, and then it finds the exact range to patch (which is hardcoded). You can't do it from ARM9.
Its simplier, and maybe a bit faster, but not as configurable as bootctr9. For example you can't set an offset to use multi entrypoint payloads, like the reinand.dat or cakes.dat, and you cant configure delays,for example to press a key, or before you jump to the payload, which is usefull to boot payloads like reinand or cakes with a key combination on boot.The boot multi .bin of aurora its better then ctrboot9?
As far as I know there's no need for delays on A9LH, those were only needed to make kernel exploits more reliable.Its possible in theory to do this from arm9, for example, because you can svcBackdoor on arm9, but the available memory for the arm9 thread is not very much, so its hard to fit all the code to it.
Its simplier, and maybe a bit faster, but not as configurable as bootctr9. For example you can't set an offset to use multi entrypoint payloads, like the reinand.dat or cakes.dat, and you cant configure delays,for example to press a key, or before you jump to the payload, which is usefull to boot payloads like reinand or cakes with a key combination on boot.
This only happens if rei/loader.bin or rei/payloads/default.bin don't existI don't know what i'm doing wrong, i use the new aureinand and i rename my payload to default.bin now i can't launch decrypt9 it now just send me to emunand....




