Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[Kazuma77]

The only difference between master and legacy is the inclusion of Rosalina. There's absolutely no reason legacy should be able to launch and emunand and master cannot.


This seems even weirder - EmuNAND size has absolutely nothing to do with how it boots. A full-size EmuNAND is the exact same as a minimum size EmuNAND - the only difference is the minimum size one has a large amount of unused, unpartitioned space. There is absolutely no reason this should affect an EmuNAND boot.

That being said, I've brought your issue to AW and Tux. AW has a 9.2 EmuNAND we can test on so I'll let you know if your problem is user error or reproducible soon enough.

EDIT: What console model do you have?


This is known and we cannot do anything about it. Those games depend on oddities in how the *hax environment is set up, and replicating that environment without going through the same process (ROP, etc.) is extremely difficult. Those games will probably always require *hax, unfortunately.

It's definitely strange, but for whatever reason, it does crash. O3DS and N3DS. I'm not sure why. I usually do install Menuhax to mine for the convenience of going straight into the boot menu. But minimum sized EmuNANDs should break too if that was it. Adding to the strangeness, on the N3DS, Cakes cannot load a 9.2 either (for that matter, it can't decrypt TWL firmware, but I suppose that's a topic for mid-kid's thread), though Puma can, but even that requires a decrypted 9.0 firmware.bin for some reason.

I think most, if not all, of those issues are solvable by simply rebuilding those games with latest ctrulib.

Well, I'll try that since I recently updated my devkitpro then. Though I think some of these are not open source. I'll see what I can get working, and upload them for those who can't compile things. Thanks for the suggested fix. Though I'm even more curious to hear something back about the whole 9.2 thing. I suppose it's nothing to keep Legacy in development for, especially since I already have a workaround, but it's just baffling all the same.

 

[Quantumcat]

I don't know how to report issues on Github so...if I get a crash, I won't be able to report it unless someone explain me how to report stuff on Github...do I need to create an account there for example?

Make a github account, and go to https://github.com/AuroraWright/Luma3DS/issues and make a new issue (click plus button).

 

[RustInPeace]

But if Rosalina isn't the cause of any issues, why would people need to turn it off? You can just ignore it.

Selective reading by a certain person, jeez. I stated basically that Rosalina is a feature I almost completely forget, it has yet to add anything to my personal CFW usage, the key word is "yet." At the same time, it has not done anything to hinder said CFW usage.

This just reminds me of @Lilith Valentine arguing about this months ago, with almost the same explanations given when Aurora Wright was active here and hadn't left yet. It's just a facepalm to read now, especially with adequate and well spoken responses. Plus, pet peeve, "we," don't use that, you don't speak for me (and I never want you to). Choice? Rosalina is there, cool, it doesn't hurt me, so not having the choice to use it or not is kind of inconsequential, plus I know for sure I will use it at some point.

 

[Amapola62]

I have got two crash dumps created after exiting from the "edit activity log" option from Ctulhu...Do you want me to post them here?

Edit: Here there are

 

[astronautlevel]

I have got two crash dumps created after exiting from the "edit activity log" option from Ctulhu...Do you want me to post them here?

Sure.

Also, could you try with the legacy build attached? You won't get a crash screen, it'll just say "An error has occurred and your system needs to restart" or similar. Thanks.

 

[Amapola62]

Except that I access Cthulu from the Homebrew menu as a 3dsx...so how will I be able to test with a legacy build without Rosalina...unless I install the cia and try?

 

[astronautlevel]

Except that I access Cthulu from the Homebrew menu as a 3dsx...so how will I be able to test with a legacy build without Rosalina...unless I install the cia and try?

If you're on an n3ds you could use homebrewlauncher_loader, but on an o3ds there's not much you can do...

 

[Amapola62]

The good thing is that those dump come from my n3dsXL ^^

 

[astronautlevel]

It's definitely strange, but for whatever reason, it does crash. O3DS and N3DS. I'm not sure why. I usually do install Menuhax to mine for the convenience of going straight into the boot menu. But minimum sized EmuNANDs should break too if that was it. Adding to the strangeness, on the N3DS, Cakes cannot load a 9.2 either (for that matter, it can't decrypt TWL firmware, but I suppose that's a topic for mid-kid's thread), though Puma can, but even that requires a decrypted 9.0 firmware.bin for some reason.

Okay, I've got an answer for you.

When using multi-emunand setups, all emunands need to be the same format.

--------------------- MERGED ---------------------------

The good thing is that those dump come from my n3dsXL ^^

Those crash dumps, uh, break the exception parser

Spoiler

From what I did get though it seems to be an issue with the homebrew and not Luma itself.

 

[Amapola62]

I got an other arm11 exception that I'm going to send here...
So I retried opening Cthulu after switching off Game patching and exception handlers and now I can't even open the software library in Cthulu...

 

[Kazuma77]

Okay, I've got an answer for you.

When using multi-emunand setups, all emunands need to be the same format.

--------------------- MERGED ---------------------------


Those crash dumps, uh, break the exception parser

Spoiler

From what I did get though it seems to be an issue with the homebrew and not Luma itself.

That's not telling me something I don't already know. I found out the hard way while trying to help DarkMatterCore fix a bug in his software. And you're almost correct. However, the last EmuNAND CAN be minimum if formatted as a RedNAND, because that does not change the location of the NCSD header. Luma will load an 11.x minimum sized RedNAND created this way just fine even. But let's just take the whole multi-EmuNAND thing out of the picture if it's confusing the issue. Even with just one EmuNAND on the card, 9.2 still crashes if it's not minimum size.

 

[astronautlevel]

Might be worth it to zero the card out, seems like some really bizarre issue with the gw nscd still lingering. Is this an o3ds or n3ds?

Also testing seems to show that booting 9.2 full-sized EmuNAND on 8.1.1 works fine

 

[TheGuyMadeOfTofu]

Question. Is there a way to make Rosalina on a n3ds behave as if its running on a o3ds? By that i mean removing the n3ds option from it and me just have control of the clocking and L+2 on boot menu as per usual? Or is not doable? I have my reasons for asking. Because i still have to be tweaking its settings on Rosalina every time i start a game that i dont want to use L+2 and max clocking. Or make it disabled if your luma setting on it is off, which would make more sense.

 

[Kazuma77]

Might be worth it to zero the card out, seems like some really bizarre issue with the gw nscd still lingering. Is this an o3ds or n3ds?

Also testing seems to show that booting 9.2 full-sized EmuNAND on 8.1.1 works fine

The latest version of 3DS Multi EmuNAND Creator does that if you remove the first EmuNAND. So, done already.

I'd like to know how whoever pulled it off did it. Because I have tried it on one N3DS, and two O3DSes so far and they all crash. The N3DS only has one EmuNAND, also, so, you can't blame that one on my thoroughly researched and correctly performed multi-EmuNAND formatting methods. And it was put there by the same Decrypt9 that copied my EmuNAND to SysNAND. Though as I said, I can put an 11.x on the same slot and it will work just fine. Put 9.2 back using any method, and it crashes again. My experiments are repeatable and easily reproduced on as many systems as I try it on. It should be failing for anyone and everyone the same. That said, the two things I don't seem to have are an O3DS with a Toshiba NAND, and an N3DS with a Samsung NAND. So, I can't test with those. And why do you keep asking which system type? I've told you countless times I've got it failing in the same manner on both.

I'd suggest testing another system. Because someone with some abnormal configuration must have just got lucky or something. I assure you, there's nothing abnormal here. The abnormality is it working.

 

[ihaveahax]

Question. Is there a way to make Rosalina on a n3ds behave as if its running on a o3ds? By that i mean removing the n3ds option from it and me just have control of the clocking and L+2 on boot menu as per usual? Or is not doable? I have my reasons for asking. Because i still have to be tweaking its settings on Rosalina every time i start a game that i dont want to use L+2 and max clocking. Or make it disabled if your luma setting on it is off, which would make more sense.

the options aren't affecting anything if you do not use them. the system will always start in 804MHz mode because that is HOME Menu's doing. if you don't enable the option specifically, games will start in 268 unless they are specifically set by the dev to run using 804.

 

[TheGuyMadeOfTofu]

the options aren't affecting anything if you do not use them. the system will always start in 804MHz mode because that is HOME Menu's doing. if you don't enable the option specifically, games will start in 268 unless they are specifically set by the dev to run using 804.

That's the thing. When i start the system and check on the option it says is on 240 something and when i boot a game like DQ7 and check the options is on 804 without me doing anything. Sometimes L+2 enables itself too on the game. And i notice this even without checking because the menu (which lags horribly) goes smoothly. Which only happens when i use the 804 + L+2

 

[ihaveahax]

That's the thing. When i start the system and check on the option it says is on 240 something and when i boot a game like DQ7 and check the options is on 804 without me doing anything. Sometimes L+2 enables itself too on the game. And i notice this even without checking because the menu (which lags horribly) goes smoothly. Which only happens when i use the 804 + L+2

you're probably reading it wrong. if it enables itself, it's likely because the game was configured to do so. this is not the fault of luma/rosalina.

 

[astronautlevel]

That's the thing. When i start the system and check on the option it says is on 240 something and when i boot a game like DQ7 and check the options is on 804 without me doing anything. Sometimes L+2 enables itself too on the game. And i notice this even without checking because the menu (which lags horribly) goes smoothly. Which only happens when i use the 804 + L+2

Dragon Quest 7 is a n3ds enhanced game so it'll automatically use 804 MHz

 

[TheGuyMadeOfTofu]

Dragon Quest 7 is a n3ds enhanced game so it'll automatically use 804 MHz

That's not possible. Because before Rosalina the game would have a laggy menu even on those who arent using hacked system and only improves when i set my n3ds to use its full power on it. I did the personal testing for this even with the fps counter.

 

[astronautlevel]

That's not possible. Because before Rosalina the game would have a laggy menu even on those who arent using hacked system and only improves when i set my n3ds to use its full power on it. I did the personal testing for this even with the fps counter.

[9:28 AM] Aurora Wright: luma won't override games which use n3ds clock or l2
[9:28 AM] Aurora Wright: it didn't do so even on legacy
[9:28 AM] Aurora Wright: actually it used to a long time ago but I fixed it