Ok, thanksThis version of Luma3DS 7.1 allegedly works with B9S 1.2.
If it doesn't work, you can just replace the boot.firm with a conventional one (e.g. 8.1).Ok, thanks
Should I try it? Would it mess up my system or anything?
Sure, but I wouldn't do it without a hardmodWant me to try it then get back to you?
Well, I attempted it but it didn't register that I was using the b9s 1.1 files. I was probably doing something wrong and I don't want to risk trying again.Sure, but I wouldn't do it without a hardmod
I wouldn't downgrade to B9S 1.0/1.1. If you don't know what you're doing, you're asking for a brick. Try the above 7.1 version of Luma3DS that's supposed to work with B9S 1.2.Well, I attempted it but it didn't register that I was using the b9s 1.1 files. I was probably doing something wrong and I don't want to risk trying again.
Thanks, but I'm not the one having issues with Luma. I was seeing if it was possible and I was trying it on a spare system.I wouldn't downgrade to B9S 1.0/1.1. If you don't know what you're doing, you're asking for a brick. Try the above 7.1 version of Luma3DS that's supposed to work with B9S 1.2.
That would work.Could he use SafeB9SInstaller to downgrade b9s to v1.1/v1.0?
Try the legacy build like I said. It should be just as stable as 7.1.I think I am on B9 1.2. What Luma's can be used with 1.2? It seems like Luma 7's have best stability and was hoping I can go with one of those...
--------------------- MERGED ---------------------------
Should I downgrade B9? Also, how would I do that?
I don't think I can downgrade B9 as I dont have a backup of B9 1.0. I followed the A9LH to B9 guide on 3DS guide site. Think I went directly to B9 1.2...
Was I doing something wrong then? Like I said, I tried using the files for boot9strap v1.1 and it still booted to Luma 8.0, when Luma 8.0 requires b9s v1.2. I was using the most recent SafeB9SInstaller, if that made a difference.That would work.
Try the legacy build like I said. It should be just as stable as 7.1.
new version?
is this true?
This is happening then. At least I will be able to confirm B9S/Luma3DS 8+ as the culprit. If this stops the issue, I will restore my B9S backup and continue debugging with you.Also, it's safe to restore an a9lh backup onto a b9s console.
Nah, go for it. Let me know the outcomeThis is happening then. At least I will be able to confirm B9S/Luma3DS 8+ as the culprit. If this stops the issue, I will restore my B9S backup and continue debugging with you.
Unless you feel it is not necessary.
This is very interesting, thank you. I can't analyze the dumps right now because my development laptop is out of power and I forgot the charger but I should be able to within a few days once I get my windows laptop setup for 3ds development.Dumps are attached.
1-4 are TWLoader.cia. Immediate crashes.
5/6 are CSPSP.cia (Counter Strike PSP 3DS port). Immediate crashes.
7 should be TWLoader attempting to load a ROM from my flashcart. (AceKard 2i)
8 is TWLoader trying to view settings.
All cia's are the latest versions. Luma3DS is 8.1. Exception handlers are not disabled. Clock+L2 is stock, always has been. TWLoader 3dsx works perfectly. I forgot a 3dsx dump because 12 hour shift.
A9LH 11.4 backup restored perfectly. Luckily, before B9S I had backed up the SD card so I had an exact copy of my system before B9S. Everything works flawlessly. Mario Sports Superstars works again, TWLoader is working fine again, HBL.cia is launching again, etc... For information, the console is now A9LH, 11.4, Luma3DS 7.0.5. All cia's are the latest. I even updated TWLoader manually to the latest version. (It was about 3 behind.) I am calling it confirmed: something happened from Luma3DS 7.0.5 to Luma3DS 7.1/8+.
Which only begs the question to you developers: What on earth can we do to help you help us? If it is simply providing dumps, I'll load everything I can think of after restoring my B9S Luma3DS 8.1 NAND and provide them until you hate me for giving you 300+ at a time. If there's anything else, please don't hesitate to request it.
Community: Listen to the devs that actually know what they're doing. If they request dumps, give them up! If they want other info, give it to them. They can't fix it if we don't help them. Luma3DS saves your dump files in a folder on your SD card. The location is /luma/dumps/arm11/. Compress them (zip them) and upload them here. Try and be descriptive about what is happening during the crash and what is running when it crashes. If enough of us are having the same error it should help make the problem clearer. Likewise, you might show a unique crash that is unknown. Thanks!
I don't have a 1.0 backup. I do have a 1.1 backup. Somehow I missed the initial release. I will try a 1.1 restore later tonight, then restore back to A9LH, then upgrade to B9S 1.2 manually again. Maybe it has something to do with the way I performed it and it will work this time. (Not too hopeful, but you just never know.)This is very interesting, thank you. I can't analyze the dumps right now because my development laptop is out of power and I forgot the charger but I should be able to within a few days once I get my windows laptop setup for 3ds development.
In the meantime, I'd be interested to know what happens if you :
Also, your point about being compliant with devs is hugely important. It's not like Aurora or Tux are laughing in some hidden channel "lol look at all these noobs who bricked," they genuinely want to help the community get the best experience possible, and being hostile won't help them.
- restore a b9s 1.0 with luma3ds v7.1 backup (if you have one, if not nbd)
- manually reinstall b9s 1.2 and luma3ds v8.1, instead of restoring a backup
There shouldn't be any crashes in 3DS games assuming that it doesn't crash immediately on starting.
With all due respect, you're fucking with us right?Yes, it would be helpful if you listed the games you're experiencing issues with - I haven't heard of anything like this yet, and your case seems to be a unique one.