Godmode9: Certain info not shown on System Info

[Marenthyu]

On my system info prompt, the following information is :
Friendcode seed, SD keyY and System ID0.

Screenshot attached.

I do not know why it is happening, every other function of gm9 seems to be working just fine.
Current Firmware is newest, Luma is on 9.0.

The issue can be reproduced by @zetadesigns on an other European o3DS.

(censored other data for privacy, but i can provide them if they help with identifying the issue.)

[SirNapkin1334]

Do you have an aeskeydb.bin for support? This happened to me once, I can't remember how I fixed it.

[Marenthyu]

I suppose that's created by "create support files"?
Can provide that; but i'd prefer a personal channel - do DM me on discord or send an email.

[SirNapkin1334]

You can't get that from the Build Support Files. And what I'm asking is if you have one, as GodMode9 needs it for extra functionality, including accessing CTRNAND in entrypoints beside Boot9Strap. Is there an aeskeydb.bin in SD:/gm9/support?
DM me in discord. @SirNapkin1334#5144

[d0k3]

Okay, this is weird. The aeskeydb.bin is not required here. Can you check if you have the 1:/private/movable.sed file? Maybe something is special with it. I guess I may even have to have a look, but don't post it publicly.

[Marenthyu]

I do have it, it is 288 Byte and i have successfully extracted it previously using @zoogie 's seedstarter.cia for use with TADPole before.
My Discord is Marenthyu#4211 if you want to contact me.

[d0k3]

It's only 288 byte if the system has never been started. Is that the case? A standard, initializied movable.sed is 320 byte. An uninitialised system does not have a SD key Y or a system ID0. The LocalFriendCodeSeed is there, though.

[Marenthyu]

I have been using this 3DS for the past 7 years now, it certainly has been started - it has never been formatted or reset, however, if that changes things.
As far as i can tell, my movable.sed is fully stock, untampered with.
But comparing it to the other movable.seds i have mined as well as mining it again by dumping my movable_part1.sed and using seedminer, i do see that my exported/copied movable.sed has a lot more "stuff" in it.
All my mined movable.sed have a lot of 00 bytes before and 32 00 bytes after a part that's written to - this "written to" part is identical in my dumped/copied movable.sed.

Sorry if this is no news, i am not 100% educated.

But yes, if you want to examine my file, shoot me an email or discord message.

It may be of note that i did skip a couple firmware updates due to simply not using it for a long time.

[Marenthyu]

I updated https://www.3dbrew.org/wiki/Nand/private/movable.sed with the information of talking and testing with @d0k3 . Feel free to reword/rewrite it if i missed anything.

[Marenthyu]

Also to note from olliz0r on discord, the 0x120 data is written on system FORMAT, not system startup, so it may be just the fact that these early systems never got formatted before being shipped, yet newer systems were?
Idk. Just throwing the idea out there.

[d0k3]

As far as I know, your system is auto formatted when first booting up. Also, the CMAC inside the initialized part of the movable.sed is crucial. It's used for checking the validity of your own movable.sed, and it's also the reason why an initialised one from another console will not work.

[SirNapkin1334]

Formatted? I'm not sure. I believe there's a difference between format and initial setup.

[d0k3]

Okay, should be fixed in https://github.com/d0k3/GodMode9/commit/37cdb26f91c78857364e7e1dc8145499509b58e2

@Marenthyu - can you try this?

[Marenthyu]

Tomorrow afternoon, in 17ish hours. (Not home right now)
I dont have the homebrew devkit set up, so if you could make me a firm, I'd appreciate.

[SirNapkin1334]

I'll send you a compiled firm over Discord once I get home (about 50 minutes)

[mariohackandglitch]

I have a NAND backup from a 1.0.0 console that was updated to 4.5. I checked the movable.sed and indeed, it's 288 bytes. I don't remember if I formatted it before making the NAND backup, but in any case, the backup was made after updating to 4.5 (using the gateway ram dumper)

[Marenthyu]

was it also a european console?

[mariohackandglitch]

Yes, it is european.

[Marenthyu]

I can confirm that it is fixed with 1.6.0-6-g84bfac6a (.firm @SirNapkin1334 compiled for me.)

Issue may be closed at project's discretion, but it may be left open for documentation on the uninitialized movable.sed

[d0k3]

It will still be viewable after it's closed. Any further discussion / research regarding this should happen elsewhere (IRC or other platforms). I'm still interested in what causes this, ofc.