New(er) Release needed about fastboot3ds HOT 6 CLOSED

The private key won't be made public as that would defeat its point. We sign the releases, because we want to stop people installing potentially malicious builds through fb3DS itself. Of course we can't stop you overwriting it using GodMode9 for example.

A release is still planned. People have a real life and maybe other interests as well and so we kept pushing this back. Hopefully we will get the release out soon.

from fastboot3ds.

Thank you!
I'm on a deployment and haven't been home since May. The way this is written, I can't even compile it myself, because I can't clone it with git (no internet access on my personal laptop). Seems some variables require info that's tucked away in the .git folder that you simply don't get by downloading a zip of the source. Lots of "fatal not a git repo" kind of errors...

from fastboot3ds.

It's getting the version number from git, yes. For some odd reason Github never includes the git history in the zip files.

from fastboot3ds.

So, I just reminded myself of why I never tried installing a build. I got around the errors by doing:

make NO_DEBUG=1 VERS_MAJOR=1 VERS_MINOR=2

but the result is a 138.8kb .firm file! Isn't this too big to install in firm0? b9s is 30.7kb

from fastboot3ds.

I guess it's not too big. I'm also hard-modded AND have an ntr flash card, so I installed it (and noticed that the firm0/1 backups are 4MB). Didn't seem to cause a brick. Using boot_Ctr9 to chainload my GW emunand seemed broken with it, either with a direct chainload or with Luma3ds chainloading it.

Godmode9 seems to recommend this, but I'm unsure of the advantages.

EDIT: Correction. boot_CTR9 (or the version of it that I'm using) has a problem with fastboot3ds in quiet mode. From "quick boot", it works and so does the loading of my GW emunand... as long as I'm QUICK to let go of the "down" button (but the bootCTR9 splash screen is scrambled). Normal boot and choosing boot_CTR9 from the menu, it works 100%. Perhaps boot_CTR9 (or my version) has an old screen init bug in it, that isn't accounted for in fastboot3ds when using quiet mode.

from fastboot3ds.

I don't know what these old bootloaders rely on. Possibly they require screens being inited (they must indicate so with a flag in the FIRM file).

from fastboot3ds.