GodMode9 v1.8.0 boot issues with Luma 3DS chainloader

[BaamAlex]

When i update to the latest version the 3ds shuts down instantly. This problem doesn't happen with version 1.7.1. What can cause this issue?

[dothackjhe]

I am also having this exact same issue. Reverting to 1.7.1 fixes it, though...

[urherenow]

A bit more explanation would help. What model/firmware are you? How are you launching it? Are you trying to boot with it installed to firm0?

[dothackjhe]

Seeing I am also experiencing the same issue as the thread starter, I am also answering the questions as follows:

New Nintendo 3DS XL running on latest firmware (11.8, I think) and latest Luma3DS version.
Trying to launch it at cold boot.
I do not know how to answer the last question, lolz.

[Nemris]

Cannot reproduce the bug on my end.

[Wolfvak]

@BaamAlex and @dothackjhe please post more information about your systems, such as:

• system model
• system firmware
• exploit used to run GM9
• boot storage
• and any other information that may seem pertinent

[BaamAlex]

New 3ds, Luma 9.1 with Firmware 11.9. And i haven't installed it to firm0

[BaamAlex]

Boot Storage? What do you mean with this?

[Wolfvak]

I mean where have you installed it. Whether it's on FIRM0/1, somewhere in the FAT NAND partitions or in the SD card.

Regarding your other message, you still don't say exactly how you try to boot it, or from where.

[BaamAlex]

From sd card.

[Nemris]

Tested on:
• New3DS with Luma 9.1, OS 11.9.0-42E, fastboot3ds on FIRM0;
• Old3DS with Luma 9.1, OS 11.9.0-42E, boot9strap on FIRM0

Boots fine.

[Wolfvak]

But how exactly are you booting it? Are you using b9s, fb3ds, etc? Do you boot anything in between the first stage loader and GM9?

[urherenow]

I'm using b9s, and loading Godmode9 via Luma3DS hotkey at coldboot (I named it x_GodMode9.firm in the payloads folder). It loads instantly. No issues at all. Just updated to 11.9 just in case. Still works.

[al3x10m]

tested latest release on firm0 with and without sd...no issues

[BaamAlex]

B9S

[Wolfvak]

@BaamAlex so you have the GM9 firm placed in the SD card root, called boot.firm and it shuts down as soon as you power on the console?

[dothackjhe]

I'm in the exact same disposition as @BaamAlex

[d0k3]

@BaamAlex - thanks for opening that issue. If you are running GM9.firm directly from B9S now, can you maybe try running it via the Luma chainloader? Or is this what you always did?

[BaamAlex]

I have only the godmode9.firm in the payloads folder.

[d0k3]

Can you try these two test builds?

https://f.secretalgorithm.com/15JCyI/godmode9-bkpt.firm
https://f.secretalgorithm.com/YPtgV/godmode9-nolto.firm

Maybe make a photo if something of note happens.

[PistolsAtDawn]

d0k3, as we briefly discussed on reddit, here is my initial report and the test results of the two builds you just posted:

This was tested on a New 3DS XL (11.9 / Luma 9.1 stable [chain loaded with payload in SD card path /luma/payloads] / b9s 1.3) -

From a powered off state, launching gm9 (release build 1.80) by pressing and holding start opens gm9 with the top screen being mostly black but with some vertical lines (about 25% of the time it opens completely fine though).

Using the test build you posted here in the comments [reddit], I get basically the same behavior.

It seems like perhaps keeping the start button pressed too long causes this. I can somewhat reliably get the splash screen logo and the top pane to show normally if I'm very careful with how long I keep the start button pressed once the 3DS has rebooted.

1.7.1 doesn't behave this way. I can be "careless" with the start button being pressed and gm9 starts reliably.

New test results -

As you said would happen, the bkpt build crashed immediately. I attached the dump.

The nolto build more reliably boots without the blank screen on top, especially when not started from a cold boot. Pressing and holding start within gm9 for instance will more likely cause everything to reboot normally as well as when I reboot from within the 3DS home screen using the Quick Reboot cia I have installed.

I hope this was helpful. Thank you and everyone else who has contributed to this fantastic utility.

crash_dump_00000000.dmp.zip

[dothackjhe]

How does one install B9S on Firm0, by the way?

[BaamAlex]

@dothackjhe boot9strap is installed to firm0 iirc

[dothackjhe]

I wonder what makes GodMode9 1.8.0 not boot on us if that's the case, then.

[d0k3]

Okay, here's another one for everyone to test, especially @BaamAlex, @dothackjhe and @PistolsAtDawn :
https://f.secretalgorithm.com/12rT10/godmode9-sifix.firm

Let me know if that changes anything!

[ghost]

@d0k3 what's causing the bug that makes gm9 not boot for some users?

[d0k3]

If we knew, we'd already have fixed it, @Ty-Dye. We're trying to find out.

[ghost]

@d0k3 a theory I have, could it be a n3ds (or o3ds) only thing

or could it depend on the bootloader?

[Nemris]

@Ty-Dye For me, GM9 works both on an Old3DS and on a New one.

@d0k3 I have a theory of mine, without proof to back it up. Could the bug depend on the date a 3DS was manufactured, and LTO triggers it?

[urherenow]

What is LTO? And do you want newer or older machines? I have a launch-day O3DS I can try it on. My N3DS doesn’t have an issue though. Edit: And... I need to hunt around for that O3DS... recently moved back to Japan and have no idea where it's at.

[dothackjhe]

@d0k3 Do we have to rename the provided file or we should use it as is?

Sorry, dumb question..

[legoj15]

I have noticed that if you enter the Luma3DS settings/config screen (by holding SELECT on boot), then tapping START (to save preferences), and then pressing and holding START (or whatever button you have assigned the GM9 firm), GodMode9 boots normally, with both screens working, every time

[TheStraubulous]

I also have this issue. When installing latest Luma today, first boot holding start worked and godmode9 loaded and I finished installing CFW. However every other time now unless I have more than 1 payload in the payload folder I just got the blue light on/off and nothing happens.
N3DS
Latest Luma

[GITitdoneboi]

I have noticed that if you enter the Luma3DS settings/config screen (by holding SELECT on boot), then tapping START (to save preferences), and then pressing and holding START (or whatever button you have assigned the GM9 firm), GodMode9 boots normally, with both screens working, every time

THANKS, That worked for me!

[aznnoodles420]

I seem to be having the same issue on my New Nintendo 3ds XL and I have discovered that it must be something nintendo changed in the new Models of the New Nintendo 3ds XL as my original one bought on release has no issues but my fire emblem model has this problem

[dothackjhe]

@aznnoodles420 Have you tried it on Luma3DS 10?

Luma3DS had just had its new updated version recently.

[aznnoodles420]

Ya I did. No change so I set up fastboot3ds and now it works but like I said this problem is only affecting one of my New Nintendo 3ds XL. The one I bought around launch works fine but my Fire Emblem New Nintendo 3ds XL has issues. This leads me to believe that they made some sort of change on the newer models

[TheGinGear]

If you would all read the previous messages, the cause of the issue has been discovered and solved. When directly chainloading gm9 1.8.0 from luma 9.1, IPS type screens initialize incorrectly. IPS screens are more common on New devices. You can get around this by booting gm9 by any different way than off> b9s > luma 9.1 > directly chainloading gm9 1.8. You can either update to luma 10, or place another .firm file in the /luma/payloads/ folder as to bring up the chainloader menu. And yes, another method is to first boot the luma configuration page first, as seen above.

[profi200]

I disagree with the "solved" part. The real problem still has not been identified and this issue keeps popping up. While it works fine with fb3DS there is no guarantee it may not also happen with it as bootloader.

While i was digging in boot11 i found how to actually reset the GPU but i don't know if this solves anything: https://github.com/derrekr/fastboot3DS/blob/master/source/arm11/hardware/gfx.c#L254-L255

[helltoast]

I came across this issue, is it still being worked on? non-XL n3DS here, NA Mario edition from November 2016, NT panels. using latest Luma. already tried resetting the rtc. putting multiple payload in the folder "fixes" it, I'm assuming fastboot would as well.

I also have an European launch n3DS (NT), Japanese 2016 one (NT) and a NA 2016 one (IPS) for testing if anyone is interested, all regular sized (don't ask)

EDIT: updated Luma and gm9 on the European one, it works. firmware 11.3.

[BaamAlex]

I tried the latest version from gm9 on another new 3ds non xl. Works fine with it

[helltoast]

alright, so I finished installing b9s on all of them, here are my results:

JP: 2014, 11.0, works [TN]
EU: 2014, 11.3, works [TN]
NA: 2016, 11.10, doesn't work (powers off instantly) [TN]
NA: 2016, 11.5, doesn't work (top screen shows gm9 logo, hangs) [IPS]

these are all non-XL n3DS'. tested with latest Luma (10.0.1 hotfix) and gm9 (1.8.0).

EDIT

updated the European one to 11.10, still works. also changed the region of the Japanese one to NA and updated it, also works.

[Insurr]

I'm having issues with this too. Now I first ran into it while setting up using the guide and installing Luma 10.0.1, the GodMode9 title would appear in the top screen but nothing would happen and I'd have to manually turn off the 3ds to get anywhere. The method for entering Luma first and then Godmode9 didn't help. This I DID fix by downloading the alternate boot.firm linked above, after which GodMode9 worked fine.

Unfortunately I ran into stability issues with that setup and decided I better update Luma just in case (seems to have worked so far). This time around Godmode does actually load entirely in the top screen unlike during my first attempt, but I have to do the trick with Luma menu->Godmode menu to actually get the bottom screen to load. Thankfully that does seem to work.

On an EU New 3D XL.

[trlkly]

I also have a Mario edition new 3DS (refurbished by GameStop), albeit the North American variety, and ran into the same problem, even using the latest Luma. All I did was simply follow the guide from https://3ds.hacks.guide. I have the lastest firmware (11.10.0-43). When I got to the point of booting GodMode9, it would just shut off.

I actually just went ahead and used the older version to complete the guide. However, I can confirm now that having two payloads (i.e. the old version and the new version) allows the new version to work properly.

[HedioOnlyTheName]

I have noticed that if you enter the Luma3DS settings/config screen (by holding SELECT on boot), then tapping START (to save preferences), and then pressing and holding START (or whatever button you have assigned the GM9 firm), GodMode9 boots normally, with both screens working, every time

omg it worked thank you 3000

[obsidianspider]

I have noticed that if you enter the Luma3DS settings/config screen (by holding SELECT on boot), then tapping START (to save preferences), and then pressing and holding START (or whatever button you have assigned the GM9 firm), GodMode9 boots normally, with both screens working, every time

Originally posted by @legoj15 in #466 (comment)

I can confirm this workaround is working for me on a n3DSXL running 11.10.0.-43U, Luma 10.0.1 and GodMode9 1.8.0. It's not as nice as just holding Start when I boot, but it works.

[Wolfvak]

Okay I think I got it fixed in the last commit - @BaamAlex and everyone else, can you test it out?

[TurdPooCharger]

I tried compiling the current master branch on my Manjaro Linux laptop. It gives these errors. :-(

[xxxxxxxxxxxxx@xxxx-pc GodMode9-master]$ git init
Initialized empty Git repository in /home/xxxxxxxxxxxxx/Desktop/GodMode9-master/.git/
[xxxxxxxxxxxxx@xxxx-pc GodMode9-master]$ make
fatal: No names found, cannot describe anything.
make: Warning: File 'Makefile.common' has modification time 10893 s in the future
Building arm9/arm9.elf
make[1]: Warning: File '../Makefile.build' has modification time 10893 s in the future
[ARM9] source/fatfs/ffsystem.c
[ARM9] source/fatfs/ff.c
[ARM9] source/fatfs/ffunicode.c
.
.
.
[ARM9] ../common/pxi.c
[ARM9] ../common/spi.c
make[1]: warning:  Clock skew detected.  Your build may be incomplete.
Building arm11/arm11.elf
make[1]: Warning: File '../Makefile.build' has modification time 10874 s in the future
[ARM11] source/hw/codec.c
[ARM11] source/hw/hid.c
.
.
.
[ARM11] ../common/pxi.c
[ARM11] ../common/spi.c
make[1]: warning:  Clock skew detected.  Your build may be incomplete.
Creating output/vram0.tar
add: easter.bin
add: font_default.pbm
add: GodMode9_splash.png
[FLAVOR] GodMode9
[VERSION] 
[BUILD] 2019-10-13 14:31:07
[FIRM] output/GodMode9.firm
[FIRM] output/GodMode9_dev.firm
make: warning:  Clock skew detected.  Your build may be incomplete.
[xxxxxxxxxxxxx@xxxx-pc GodMode9-master]$

[Wolfvak]

those aren't errors, they're just warnings about having the wrong clock for some reason.
why are you downloading the zip, then initializing a new git repo on the dir? just clone the repo and build that instead

[TurdPooCharger]

Sorry, still learning devkitarm. git clone https://github.com/d0k3/GodMode9/ works so much nicer. Thanks.

Alright, I compiled master again with no errors. What's weird is that the output GodMode9.firm has the size of 465 KiB. Previous builds were around 485 KiB.

On my n3DSXL, my compiled copy has the banner colors still washed out. Maybe it's my setup.

Can you provide your build here so I can double check?

[Wolfvak]

Anyone having problems, please use this https://cdn.discordapp.com/attachments/431968729488818186/633061313165393950/GodMode9-v1.8.0-144-g915cb2d1-20191013185856.zip

BTW, the size difference is because the README is only embedded on release builds, not personal builds

[KMulvena]

I was having some compatibility issues on my 3DS XL running Luma v10.2 and GodMode v1.9.1 where it would just keep saying "The payload is invalid or corrupted". Using GodMode v1.8 instead seems to work fine for me.