Hacking Luma3DS 9.0 ErrDisp

[Zappo23]

I am trying to figure out this issue. I have attempted to redownload the boot.firm, formatted the SD card (SDXC), and flashing back to a previous NAND to no avail. The only progress I've made is determining that when the SD card is in the system, the home menu will not even boot and it goes straight to the error you see below, but if I take the card out, it gets to the home menu before crashing. I am at a loss. Has anyone experienced this issue, and if so, did you solve it and how?

If you can't see the image, here is the text from it:

An error occurred (ErrDisp)

Error type: generic

Process ID: 21
Process type: qtm
Process title ID: 0x0004013000004202

Address: 0x00103f18
Error code: 0xf96183fe

Press any button to reboot.

Thanks.

 

[Ryccardo]

QTM is the driver for stabilized 3D, and I frankly don't know why it would crash depending on whether the SD is in (or at all). Camera troubles?

For the "time of other people is free" series: tried flashing a known good ctrtransfer image (in case of OS corruption)?
Fully restoring a nand backup, immediately recreating a backup, and comparing them (nand failure... you would probably be the first)?

 

[Zappo23]

QTM is the driver for stabilized 3D, and I frankly don't know why it would crash depending on whether the SD is in (or at all). Camera troubles?

For the "time of other people is free" series: tried flashing a known good ctrtransfer image (in case of OS corruption)?
Fully restoring a nand backup, immediately recreating a backup, and comparing them (nand failure... you would probably be the first)?

So what you are saying is that something with the 3D stabilizer driver is possibly corrupted? I haven't tried to use the camera or 3D on this console, nor do I have any software that isn't stock on it that actively utilizes the 3D or camera.

When I restored the NAND backup the same issue occurred, which tells me that it might be that backup has a corruption somewhere in the file. If I created a SYSNAND backup on my other N3DS and used it for this one, is it possible it will resolve the issue, or do I run the risk of bricking it?

EDIT: If it helps, I used my other N3DS XL to do a system transfer following the 3DS Guide website instructions. So maybe the backup NAND on my original WOULD work?

 

[Ryccardo]

So what you are saying is that something with the 3D stabilizer driver is possibly corrupted?

Possibly, yes

nor do I have any software that isn't stock on it that actively utilizes the 3D or camera.

You do, Home itself supports 3D (even if it didn't, I think the QTM driver is loaded by default in the first place)

If I created a SYSNAND backup on my other N3DS and used it for this one,

Nand backups are inherently console specific, you would want a ctrtransfer image!

 

[Zappo23]

Nand backups are inherently console specific, you would want a ctrtransfer image!

How would I create a CTRTransfer image to use?

EDIT: I found a guide to help install CTRTransfer Image, but it's for CTRTransfer 11.5 and since my FW is on 11.6 I want to make sure that using that guide and its linked assets will be fine for me. Here's the link for reference:

https://3ds.hacks.guide/ctrtransfer.html

 

[SCOTT0852]

It's fine, just update back to 11.6 afterwards.

 

[Zappo23]

It's fine, just update back to 11.6 afterwards.

Thanks for letting me know.

 

[Zappo23]

It's fine, just update back to 11.6 afterwards.

So I did that and I am still getting the same error as above. Not sure what to do from here.


EDIT: So I did some more digging and actually found someone deep in a Reddit thread that was having the exact same issue as I am now. There was a solution provided but the link to download the updated boot.firm is dead, so the only option is to compile and uncomment line 301 of this code and rename as boot.firm and replace the one on the SD card, but I don't know how to do that.

Can anyone compile that for me?

 

[Redferne]

You can also try to run the head tracking calibration setup again. With some luck it could fix the issue. But if it is indeed a hardware issue you could also try to do without the 3D.

 

[Zappo23]

You can also try to run the head tracking calibration setup again. With some luck it could fix the issue. But if it is indeed a hardware issue you could also try to do without the 3D.

Thanks, I'll try that once I solve the problem of BOOTING into an ErrDisp screen. Also, I already said waaaaay up top there that I don't use the 3D.

 

[Redferne]

Thanks, I'll try that once I solve the problem of BOOTING into an ErrDisp screen. Also, I already said waaaaay up top there that I don't use the 3D.

Arf my bad I miss read your post. I fail to see the crash occurs on boot...

 

[Zappo23]

Arf my bad I miss read your post. I fail to see the crash occurs on boot...

Lol all good

 

[Zappo23]

Still can't find the cause. Though, update: Now the screen stays black regardless of whether the SD card is in the slot. Don't know what changed between last night and now, only that I tried a different boot.firm


EDIT: Finally found someone who could do the build. Here is the link to the new boot.firm that fixes the above issue. I don't know how long it will remain an active link, but I have a copy. If anyone needs it and the link is dead, please let me know. This works for Luma3DS 9.0 and to fix the above error in the OP.

The only issue I had afterwards was that I needed to shut off Super-Stable 3D and restrict 3D in Parental Controls to make the images look normal again.

 

[The Real Jdbye]

Still can't find the cause. Though, update: Now the screen stays black regardless of whether the SD card is in the slot. Don't know what changed between last night and now, only that I tried a different boot.firm


EDIT: Finally found someone who could do the build. Here is the link to the new boot.firm that fixes the above issue. I don't know how long it will remain an active link, but I have a copy. If anyone needs it and the link is dead, please let me know. This works for Luma3DS 9.0 and to fix the above error in the OP.

The only issue I had afterwards was that I needed to shut off Super-Stable 3D and restrict 3D in Parental Controls to make the images look normal again.

I thought you said you didn't use the 3D.

 

[Zappo23]

I thought you said you didn't use the 3D.

I don't but when the new boot.firm was loaded, even with the slider down the image was doubled without the 3D effect so in order to adjust the image to make it look normal again those are the steps I took to fix it.

 

[The Real Jdbye]

I don't but when the new boot.firm was loaded, even with the slider down the image was doubled without the 3D effect so in order to adjust the image to make it look normal again those are the steps I took to fix it.

That's odd. Is the 3D slider all the way down (until it clicks)?

 

[ArviDroid]

I don't but when the new boot.firm was loaded, even with the slider down the image was doubled without the 3D effect so in order to adjust the image to make it look normal again those are the steps I took to fix it.

Thanks for providing a link! Hopefully this will solve my similar problem with ErrDisp! I might add that I´ve yet to encounter a ErrDisp with this boot.firm and that there´s no problem with the 3D after changing boot.firm.

EDIT: Ocarina of Time now lags badly with 3D turned on in a certain sequence.

 

[Zappo23]

Thanks for providing a link! Hopefully this will solve my similar problem with ErrDisp! I might add that I´ve yet to encounter a ErrDisp with this boot.firm and that there´s no problem with the 3D after changing boot.firm.

EDIT: Ocarina of Time now lags badly with 3D turned on in a certain sequence.

You gotta keep super stable 3D turned off in System Settings > Other Settings. The QTM issue has to do with the Super Stable 3D. Its main purpose is to act as a workaround to whatever error the 3D is experiencing. If you keep 3D on using that boot.firm, you're probably going to experience intermittent issues.

 

[ArviDroid]

You gotta keep super stable 3D turned off in System Settings > Other Settings. The QTM issue has to do with the Super Stable 3D. Its main purpose is to act as a workaround to whatever error the 3D is experiencing. If you keep 3D on using that boot.firm, you're probably going to experience intermittent issues.

It was lagging with the normal 3D too... No biggie for me to play without 3D, but I'll use it as much as possible anyway! Nice that I bought a new and at the same time broken 3DS!

EDIT: I believe you should either create a new thread adressing the solution directly or change the title to include [SOLVED] since the solution seems to be uncommon knowledge and is hard to come by!

 

[Era]

From someone who just had this happened today. I thank all of you for your knowledge and guidance. That file did solve my problem as well and now everything is back to normal. I also turned off the super stable 3d now since I don't really use 3d anyway. Thank you all again.