Homebrew [Release] SRLSelector - A simple boot manager for the Nintendo DSi

[saphiren]

Hello @saphiren
Thanks for the changes you did, the code is pretty much more readable, I cannot test the changes right now, I didn't even touch my laptop since this release (too much busy on my job ). About the sources something went wrong when I uploaded the sources, I will fix the repo when I get some time and merge your PR too

Thanks for fixing the repo, and for merging my changes! I did a bit more cleanup (and was able to test it this time), when you get the chance to look. I noticed the error messages were getting cleared after a few frames, so I fixed that.

 

[Billy Acuña]

Thanks for fixing the repo, and for merging my changes! I did a bit more cleanup (and was able to test it this time), when you get the chance to look. I noticed the error messages were getting cleared after a few frames, so I fixed that.

Thanks to you for contribuding
Soon I will make a release giving all the credits to you, I was planning a release when I add splash screen and config support, but I think your changes deserves a release [emoji14]

 

[cualquiercosa327]

Thank you for this great tool.I am using it on my n3ds for testing and i can load SRLauncher ,fwtool (which doesnt work fine but i can dump the bios) with sudokuhax.

 

[saphiren]

I figure @Billy Acuña is kinda busy, so in the meantime anyone who wants the most recent build can grab it from my repo (or this post).
https://github.com/aj-m/SRLSelector/releases/tag/1.1

 

[Billy Acuña]

I figure @Billy Acuña is kinda busy, so in the meantime anyone who wants the most recent build can grab it from my repo (or this post).
https://github.com/aj-m/SRLSelector/releases/tag/1.1

Np here, yeah, I'm kinda busy at work [emoji28]

 

[Deleted member 424658]

So I've just noticed something strange, this doesn't seem to update homebrew properly (if that makes sense).
I have TWLNF in my srlselector folder as select.nds, and it reads "console_id.txt" from the folder it's in.
When I boot to it from SRLSelector, it errors out despite the console_id.txt being in the folder.
What actually happens is that SRLSelector is running the homebrew but the homebrew is thinking that it's in the root of the SD Card (probably because that's where SRLSelector is).
Running the same homebrew from HBMenu doesn't do this.

 

[realWinterMute]

So I've just noticed something strange, this doesn't seem to update homebrew properly (if that makes sense).
I have TWLNF in my srlselector folder as select.nds, and it reads "console_id.txt" from the folder it's in.

Please, please don't use this madness or spread it around. The *only* place the console id should be read from is the console itself.

Messing with NAND is dangerous enough without adding vulnerability to SD card corruption and/or momentary lapses of concentration to the mix.

 

[Deleted member 424658]

Please, please don't use this madness or spread it around. The *only* place the console id should be read from is the console itself.

Messing with NAND is dangerous enough without adding vulnerability to SD card corruption and/or momentary lapses of concentration to the mix.

The guy couldn't get the console id from the console for some reason, it only showed 0s. The problem still remains that SRLSelector causes slight functionality issues with homebrew though.

edit: I'm just booting it up to see if anything is immediately different anyway, then shutting down.
And I'm also not recommending to use it either since the guy says it's still pretty much in beta and needs hardmodded people to test.

 

[realWinterMute]

The guy couldn't get the console id from the console for some reason, it only showed 0s.

This isn't an excuse for endangering people's consoles. Messing with NAND is risky enough without adding more ways for it to potentially break.

The problem still remains that SRLSelector causes slight functionality issues with homebrew though.

I don't really understand why SRLSelector is a thing tbh, the functionality might be better as an hbmenu feature.

 

[JimmyZ]

The guy couldn't get the console id from the console for some reason, it only showed 0s.

FYI, original fwTool also can't get console id on site, actually, have you ever seen anything can do that?

It could work by letting the user export some dsiware to SD then extract from that, but that feels equally stupid.

Anyway I have an idea now, but requires some time.

--------------------- MERGED ---------------------------

Please, please don't use this madness or spread it around. The *only* place the console id should be read from is the console itself.

Before making accusations, I think you should know what you're talking about, yes I read the console ID from user provided file, but then I'll verify it against EMMC CID and MBR, if that doesn't match, the program will quit, I don't see how this could be more harmful than "read from the console itself".

 

[realWinterMute]

FYI, original fwTool also can't get console id on site, actually, have you ever seen anything can do that?

Yes I have. It's currently private precisely because of your dodgy forking though. I asked you to be patient and wait for the proper infrastructure support rather than charging ahead wasting your time & energy on things that are neither needed nor required on the console.

Sorry, I do generally prefer to keep things public so it's easier to contribute and I can collaborate with people willing to learn and avoid potentially bad mistakes. Unfortunately it appears I can't trust people to be responsible with the code I'm writing so it's private, for now.

Before making accusations, I think you should know what you're talking about, yes I read the console ID from user provided file, but then I'll verify it against EMMC CID and MBR, if that doesn't match, the program will quit, I don't see how this could be more harmful than "read from the console itself".

It's an extra unnecessary check which introduces another potential failure point to an already hazardous activity. Adding more things that need more checks increases complexity and the potential for error.

 

[JimmyZ]

Yes I have. It's currently private precisely because of your dodgy forking though. I asked you to be patient and wait for the proper infrastructure support rather than charging ahead wasting your time & energy on things that are neither needed nor required on the console.

What is dodgy?

It's an extra unnecessary check which introduces another potential failure point to an already hazardous activity. Adding more things that need more checks increases complexity and the potential for error.

Explain "potential failure point" or apologize.

 

[Billy Acuña]

I don't really understand why SRLSelector is a thing tbh, the functionality might be better as an hbmenu feature.

I was bored and wanted some kind of chainloader [emoji14] but yeah, I also think would be great if it gets build-in onto hbmenu itself

 

[Apache Thunder]

@Billy Acuña

There's a potential problem that may come up with using SRLSelector and HiyaCFW together with the new Unlaunch exploit. I've opened an issue for it on your github repo:

https://github.com/billy-acuna/SRLSelector/issues/4