Hacking Official SaltFW - "Slim Alternative Firmware"

  • Thread starter Thread starter Shadowhand
  • Start date Start date
  • Views Views 87,491
  • Replies Replies 456
  • Likes Likes 7
Lol, you're funny. You don't see people forking Ubuntu, stripping out a FS driver, and making a "release" of it, do you? Same concept here.
You again?
tumblr_nrvao1pgQP1qf7yhjo1_500.png
 
Oh, so you've run out of arguements to try and prove me wrong? :P
I am not going to bother to argue with you because it's very apparent that you are just here to be salt. At some point it's just stopped being about the actual CFW and just about you wanting people to agree with you that we don't need another CFW.
Also I can name countless Distros that don't do shit, but are still considered "distros," "spins," and even "forks."Why? Because the Linux community understands that not one distro fits all, so they embrace when someone wants to make their own project. That's the point of the GNU/GPL, to allow anyone to make any fork of another project, no matter how major/minimal those changes can be.
 
I am not going to bother to argue with you because it's very apparent that you are just here to be salt. At some point it's just stopped being about the actual CFW and just about you wanting people to agree with you that we don't need another CFW.
Also I can name countless Distros that don't do shit, but are still considered "distros," "spins," and even "forks."Why? Because the Linux community understands that not one distro fits all, so they embrace when someone wants to make their own project. That's the point of the GNU/GPL, to allow anyone to make any fork of another project, no matter how major/minimal those changes can be.
Look, the CFW is ok at this point. He fixed the issues I had with it. It's your logic I have a problem with.
 
Look, the CFW is ok at this point. He fixed the issues I had with it. It's your logic I have a problem with.
My logic is that I embrace forks and more CFW's. If I see something open-source than I am ok with someone forking it. As long as they are still crediting their sources, then I see no reason to discourage anyone from making their own projects out another project.
 
My logic is that I embrace forks and more CFW's. If I see something open-source than I am ok with someone forking it. As long as they are still crediting their sources, then I see no reason to discourage anyone from making their own projects out another project.
My point is that too many forks not a good thing, as it fragments the code base a lot. Think about linux. What questions do you have to ask to troubleshoot something? What distro? If you don't know their particular obscure distro, off for research. When did you last update? When was the last code update? When did your repositories update the software? What custom versions are you using? Is your distro no longer maintained? Is it a bug that was fixed upstream that your distro didn't fix? See? Fragmentation becomes a god awful thing to deal with. Same is bound to happen with 3DS.
 
My point is that too many forks not a good thing, as it fragments the code base a lot. Think about linux. What questions do you have to ask to troubleshoot something? What distro? If you don't know their particular obscure distro, off for research. When did you last update? When was the last code update? When did your repositories update the software? What custom versions are you using? Is your distro no longer maintained? Is it a bug that was fixed upstream that your distro didn't fix? See? Fragmentation becomes a god awful thing to deal with. Same is bound to happen with 3DS.
It's actually not that hard to deal with. You act like this is the old days of the internet when research requires actual time to research.
Not to mention it's really not going to be that hard to figure out of your CFW is supported or not. If you are using it and know what the name, it's not hard to find the information. If I am using this CFW (which I am,) then I just simply follow this thread. It's not hard to bookmark a thread. If I don't see any updates from it and it's gone dead, I simply stop using it. This isn't really communicated stuff.

The Linux community hasn't fallen to shit from forks and nor did the DS community. Back in the old DS days, we used to love seeing more kernels being made.
 
Last edited by The Catboy,
If you are getting that error and say ur not using arn's built in loader I'm going to assume ur using a stand alone bootmanager. You need to use the patcher that comes with aureinand to patch the arm9loaderhax.bin from arn. It tells you all this on the wiki. This cfw would make you use sysnand mode so why not just switch arn to sysnand mode?

I have AuReiNand latest working with GBA. I am one of those OCD people who like minimal simple (basic AGB/TWL patching) CFW. AuReiNand is awesome but it is more for people (power users who use NTR, CPU clock, region free, built in loader). I use arm9select to load payloads (one button loading of payload and I can use all buttons on my N3DS except ZL and ZR), I would like to use either Mizuki or ShadowFW for GBA loading from sysNAND, and I use ReiNand 4.0 for emuNAND cias. No extra settings, button combos or distractions from just start and play. I literally have not used anything in AuReiNand except AGB/TWL patching, so once that makes its way into a minimal sysNAND only CFW I will use that for GBA loading. I will AuReiNand in the meantime.
 
It's actually not that hard to deal with. You act like this is the old days of the internet when research requires actual time to research.
Not to mention it's really not going to be that hard to figure out of your CFW is supported or not. If you are using it and know what the name, it's not hard to find the information. If I am using this CFW (which I am,) then I just simply follow this thread. It's not hard to bookmark a thread. If I don't see any updates from it and it's gone dead, I simply stop using it. This isn't really communicated stuff.
But but changing cfw is so hard. Swapping files is so much work.
 
But but changing cfw is so hard. Swapping files is so much work.
It's like a whole 2 seconds and I am very busy girl! I can't both be a slut and change my CFW at the same time!
 
It's actually not that hard to deal with. You act like this is the old days of the internet when research requires actual time to research.
Not to mention it's really not going to be that hard to figure out of your CFW is supported or not. If you are using it and know what the name, it's not hard to find the information. If I am using this CFW (which I am,) then I just simply follow this thread. It's not hard to bookmark a thread. If I don't see any updates from it and it's gone dead, I simply stop using it. This isn't really communicated stuff.

The Linux community hasn't fallen to shit from forks and nor did the DS community. Back in the old DS days, we used to love seeing more kernels being made.
Whatever. This CFW is pretty good at least. But @shinyquagsire23 has a point. Doing it via Makefile is better.
 
Since everyone is arguing, I'd add my humble opinion. First of all I have nothing against Shadowhand, however I wouldn't have done the same myself. When I started messing with ReiNand's source (I only re-added sysNAND, and then also added O3DS support + reboot patch from cakes) I asked if people were interested in the RN thread and, since they said they were, I posted the builds without even making a separate one (since the changes were so minor). At that point, if Rei wanted he could have merged my changes. Then, I was asked to start my own thread/project, so I did. Originally I only called it "Reinand mod" because I didn't think it deserved a new name, then when the projects really diverged I added a prefix but kept the original name out of respect for the original author.
So, tl_dr: while it's great to tinker with stuff and understand how everything works, remove stuff etc., I wouldn't make a thread out of it and add my name after removing a few things from a different project, especially if those things are completely optional (as it is, ARN becomes "sysnand only" if there's no emunand, and the chainloader is fully disabled if there's no default payload).
But that's just me, I suppose others can see things differently.
 
Last edited by Aurora Wright,
I like the idea of this and I don't want to sound rude by posting this in this thread, but it would be better if this project was a branch of AuReiNand that served this purpose or If Aurora created a branch that served this purpose.

The idea appeals to me because it comes across as being very stealthy cfw!! But, for this cfw to be ultimately stealthy, we would need arm9load from within nand and not the sd :) I think it would be pretty neat!

But I would always want to be able to defer back to AuReiNand full feature set at any time.

I find it hard to believe that those of you with hardmod haven't tried loading arm9 from nand yet! I just want to know, what is it like?:rofl2:
 
Last edited by democracy,
I like this idea of this and I don't want to sound rude by posting this in this thread, but it would be great if this project was a branch of AuReiNand that served this purpose. I don't know, this appeals to me because I like the idea that it cfw comes across as very stealthy!! But, for this cfw to be ultimately stealthy, we would need arm9load from within nand and not the sd :) I think it would be pretty neat! But I would always want to be able to defer back to AuReiNands full feature set at any time.

I find it hard to believe that those of you with hardmod havn't tried this yet! I just want to know, what is it like?:rofl2:
I've tried NAND payload before. It works, but is NOT fun.

Edit: Besides, that's beyond the scope of this project. That can only be done with A9LH itself, not the payload.
 
Last edited by MassExplosion213,
  • Like
Reactions: democracy

Site & Scene News

Popular threads in this forum