Looks like 8.0 and 8.1 "stable" are a whole mess and the developers are unable to fix it. https://github.com/AuroraWright/Luma3DS/issues/682
I'm in the process of making a NAND backup so I can try formatting the 3DS. Should that fail, I don't know what to do. I'm unsure whether or not I can restore a B9Sv1.1 backup safely.Legacy is essentially the same as 7.1 updated to run on b9s 1.2.
--------------------- MERGED ---------------------------
Alright, I'll take a look at the dump once I get back. In the meantime, try out the other debugging options I mentioned.
While I dislike the "works on my machine(TM)" response to the issue, as an issue isn't invalid just because it can't be reproduced by one person - especially when it affects multiple users - I wouldn't say they're unable to fix it, we just need to narrow down what exactly causes it. It's not Rosalina, as it still affects legacy build users.Looks like 8.0 and 8.1 "stable" are a whole mess and the developers are unable to fix it. https://github.com/AuroraWright/Luma3DS/issues/682
Alright, let me know how it goesI'm in the process of making a NAND backup so I can try formatting the 3DS. Should that fail, I don't know what to do. I'm unsure whether or not I can restore a B9Sv1.1 backup safely.
I agree that it isn't Rosalina. In fact, Rosalina seems to be operating perfectly and is the only way I can open the Homebrew Launcher. I don't know what is causing so many issues for us, but Rosalina isn't it.While I dislike the "works on my machine(TM)" response to the issue, as an issue isn't invalid just because it can't be reproduced by one person - especially when it affects multiple users - I wouldn't say they're unable to fix it, we just need to narrow down what exactly causes it. It's not Rosalina, as it still affects legacy build users.
Alright, let me know how it goes
An a9lh backup should be able to be restored without any issue, but I'm not positive. It just needs to be a complete restore (including FIRM0/1) in order to work. I'd like to test it on a console with a hardmod first, though.I don't know what to do any longer. I am unsure whether or not a B9S 1.1 backup can be restored and I know an A9LH backup cannot be without a hardmod. I do not have a hardmod, nor would I like one. I plan on restoring my previously made NAND backup because at least most of my games worked even if none of the homebrew did. And then it will probably sit on my end table for a few weeks while I'm disgusted with it and play Rocket League instead and eventually I'll look back into it.
Any way is convenient. I'll bookmark this thread and check back periodically. A DM is perfectly acceptable also, however. I appreciate it astronautlevel. And I hope that something comes from this and can be passed along to Aurora for everyone else with similar issues.An a9lh backup should be able to be restored without any issue, but I'm not positive. It just needs to be a complete restore (including FIRM0/1) in order to work. I'd like to test it on a console with a hardmod first, though.
For now, I'd wait until I'm able to look into the dumps and test out restoring a9lh. I'll respond to this thread with any new information (or any other way that you find convenient).
So is there nothing we can do? Essentially, we have to wait for a new Luma update from devs?
http://astronautlevel2.github.io/Luma3DS ("Legacy" tag)where r those builds?
Yes. I am using exactly that version. I can also get you versions of other homebrew CIA's immediately crashing and randomly crashing.@bobdamnit, just to confirm; you are using TWLoader v5.4.2, correct? I just need to know for debugging purposes
Anyway, Luma "stable" branch definitly have serious issues due to untested/pushed too quickly changes (like Rosalia), Astronautlevel already aggreed with me on another thread about it (Rosalia) that's why I stick to Legacy branch and recommand it to all Luma users I know.
Like I already suggested, "Legacy" should be renamed as "Stable" and current "stable" as "Testing" until serious 8.x debugging/bugfixing since it's clearly the case actually.