Hacking Luma3D weird... stuff

[Tattorack]

..... Did you somehow remove b9s? You weren't using menuhax or anything right?

Way back I used Soundhax to install Luma3D when my 3DS was at version 11.4. It boots up automatically into EmuNAND (without crazy screen spazzing that RXTools used to do).
I edited my previous post: (I know this because in the settings app it will say "Sys 11.6 E" and in the EmuNAND it wont have "Sys" infron of it).

 

[Giodude]

Way back I used Soundhax to install Luma3D when my 3DS was at version 11.4. It boots up automatically into EmuNAND (without crazy screen spazzing that RXTools used to do).
I edited my previous post: (I know this because in the settings app it will say "Sys 11.6 E" and in the EmuNAND it wont have "Sys" infron of it).

Did you ever copy boot.firm to your ctrnand? That might be why it's still booting up. Either way, try downloading the latest version of godmode9. Rename godmode9.firm to boot.firm and out it on the sd card. If b9s is installed, it will prioritize boot.firm over the boot.firm on the ctrnand.

 

[Tattorack]

Did you ever copy boot.firm to your ctrnand? That might be why it's still booting up. Either way, try downloading the latest version of godmode9. Rename godmode9.firm to boot.firm and out it on the sd card. If b9s is installed, it will prioritize boot.firm over the boot.firm on the ctrnand.

I don't think I've ever done that. The only time I ever did anything with my EmuNAND was when I installed Luma3D using the instructions on 3DS.guide (I don't think it ever tells me to do anything like copying boot.firm to ctrnand).
I updated Luma3D using the Luma3D updater and let it run its course till it said the update was successful.
This situation only occurred when I intended to update my EmuNAND to 11.6, but somehow updated my SysNAND instead. I did this through the Nintendo eshop.

 

[Deleted User]

A quick question since there seems to be a loop hole within this thread.Are you using b9s+emunand or a9lh+emunand

 

[Tattorack]

A quick question since there seems to be a loop hole within this thread.Are you using b9s+emunand or a9lh+emunand

Since I followed these instructions: https://3ds.guide/homebrew-launcher-(soundhax) I believe it's B9S.

 

[Deleted User]

Since I followed these instructions: https://3ds.guide/homebrew-launcher-(soundhax) I believe it's B9S.

I see,so before you updated you should of had autoboot emunand checked in the luma settings correct?

 

[Tattorack]

I see,so before you updated you should of had autoboot emunand checked in the luma settings correct?

Yes, the "autoboot emunand" option was active. My 3DS still automatically boots into EmuNAND when the SD card is inserted. The EmuNAND still functions perfectly, with the exception of there not seeming to be any trace of Luma3D.

 

[Deleted User]

Yes, the "autoboot emunand" option was active. My 3DS still automatically boots into EmuNAND when the SD card is inserted. The EmuNAND still functions perfectly, with the exception of there not seeming to be any trace of Luma3D.

Now what do you mean by not any trace? When you have show nand or userstring checked in luma settings,it should say either sys or emu which tells you luma is functioning properly.You should of also been able to tell the difference on what nand you where trying to update.

 

[Tattorack]

Now what do you mean by not any trace? When you have show nand or userstring checked in luma settings,it should say either sys or emu which tells you luma is functioning properly.You should of also been able to tell the difference on what nand you where trying to update.

Holding down select and powering up does not start up into Luma3D configuration. It just boots up like normal.
Telling the difference between the NAND I was updating was easy because I have a custom theme applied to my EmuNAND and no theme at all on my SysNAND. Yet, when I accessed the eshop through my EmuNAND to install the update it was my SysNAND that got updated and not my EmuNAND. The EmuNAND was still at 11.4, only without any of my installed apps and no more theme. It was also at this point that holding select and powering up no longer opened up the Luma3D configuration menu.

 

[Giodude]

The part that in sure is bugging both of us is that b9s has firm0 and firm1 write protection, meaning that without manually running the uninstaller, b9s cannot be removed. Do me a favor. Rename "boot.zip" to "boot.firm" and put it on your sd card. Tell me what happens. Also if you have arm9loaderhax.bin anywhere delete that too.

 

[Quantumcat]

Maybe OP was only running menuhax?

 

[Giodude]

Maybe OP was only running menuhax?

They said that they used to with rxtools since they bring up the weird screen colors thing, but the op then switched what is most likely b9s. Also, i dont believe luma ever had menuhax support.

 

[Quantumcat]

They said that they used to with rxtools since they bring up the weird screen colors thing, but the op then switched what is most likely b9s. Also, i dont believe luma ever had menuhax support.

Yes it did, up to 7.0.5

 

[The Real Jdbye]

Holding down select and powering up does not start up into Luma3D configuration. It just boots up like normal.
Telling the difference between the NAND I was updating was easy because I have a custom theme applied to my EmuNAND and no theme at all on my SysNAND. Yet, when I accessed the eshop through my EmuNAND to install the update it was my SysNAND that got updated and not my EmuNAND. The EmuNAND was still at 11.4, only without any of my installed apps and no more theme. It was also at this point that holding select and powering up no longer opened up the Luma3D configuration menu.

You should only ever update from System Settings. Updating from anywhere else is largely untested and could be unpredictable. Also, that way you can check that you are actually in emuNAND right before performing the update.

Holding down select and powering up does not start up into Luma3D configuration. It just boots up like normal.
Telling the difference between the NAND I was updating was easy because I have a custom theme applied to my EmuNAND and no theme at all on my SysNAND. Yet, when I accessed the eshop through my EmuNAND to install the update it was my SysNAND that got updated and not my EmuNAND. The EmuNAND was still at 11.4, only without any of my installed apps and no more theme. It was also at this point that holding select and powering up no longer opened up the Luma3D configuration menu.

What happens if you hold Start while powering on?

I don't think I've ever done that. The only time I ever did anything with my EmuNAND was when I installed Luma3D using the instructions on 3DS.guide (I don't think it ever tells me to do anything like copying boot.firm to ctrnand).
I updated Luma3D using the Luma3D updater and let it run its course till it said the update was successful.
This situation only occurred when I intended to update my EmuNAND to 11.6, but somehow updated my SysNAND instead. I did this through the Nintendo eshop.

If you used Luma Updater, it will ask you to install to ctrnand every time. Also, I'm pretty sure 3ds.guide uses a script that automates the ctrnand copy these days, that's why you didn't see any instructions for it.