Well I have no idea then, it should work. Check the path and spelling again for Hourglass9.
Well I have no idea then, it should work. Check the path and spelling again for Hourglass9.
It is correctWell I have no idea then, it should work. Check the path and spelling again for Hourglass9.
Hasn't it been a part of Luma for quite a while? O.oI am glad to see Luma3DS is catching up to Corbenik by adding a chainloading menu. Not bashing, actually quite happy to see this feature being added to other CFWs.
I have no idea about the menu Chainloading has been, but I just heard about the menu this morningHasn't it been a part of Luma for quite a while? O.o
Really? O.o Unless I dreamt about it, I'm almost sure I've used it quite a while ago. Well, my memory is terrible.I have no idea about the menu Chainloading has been, but I just heard about the menu this morning
here's when it was implemented, the 13th of november : https://github.com/AuroraWright/Luma3DS/commit/2e1b9438059a2bc80a6b8e3df00f6e22b622b05dReally? O.o Unless I dreamt about it, I'm almost sure I've used it quite a while ago. Well, my memory is terrible.
Anyone able to help? I cant boot any payloads (hourglass9, decrypt9, godmod9) though luma config boots. If I let it boot normally I get this: An error has occurred Failed to mount CTRNAND. Im on a new 3ds and 2.1E idk what to do
Shows how long it's been since I've looked at the nightlies.here's when it was implemented, the 13th of november : https://github.com/AuroraWright/Luma3DS/commit/2e1b9438059a2bc80a6b8e3df00f6e22b622b05d
I tryed that tho I tested booting it with some other files on another SD and it workedRename the hourglass9.bin to start_hourglass9.bin
After you complete guide, get the latest version of Luma
If you use CTRNAND Luma, FIRM protection does exist, and updating won't remove A9LH or brick.A question: I updated the A9LH so that Luma works without SD, in case I upgrade my 3DS without SD will damage my 3DS ?
so i'm tired of having to boot to settings on luma, then change autoboot to sysnand on, then save then load sysnand, then go back to settings, turn off autoboot sysnand and go to emunand.
i read that holding L on boot will autoboot sysnand. mine shows garbage on the top screen, then an error has occurred screen.
using luma 6.6, a9lh version. not sure what is the problem. using the settings, autoboot sysnand works fine.
using errdisp -
FATAL ERROR
PID : 0x00040030_00008F02
REV : 59076
AID : 0xFFFFFFFF_FFFFFFFF
ADR: 0x001028E4
RSL: 0xC8804478
Level -7
summary 4
module 17
desc 120
any ideas?
Check your SD card?Sorry to bump but i think i got lost in the aurora haxxors...any thoughts on this?
not sure why a normal feature would error on my sysnand. it works fine when booting by changing the settings.
I can use the Gateway with Luma A9LH, if it is possible how can I create the emunand without losing the A9LH's working data, in the formatting process gives emunand9.
I still have that crap, Gateway's only good thing is Gateshark.You use Gateway? I'm not even gonna start lol...
Copy your SD Card contents over to a PC, create an emuNAND and then drag your SD Card contents back over.