Hacking Official SaltFW - "Slim Alternative Firmware"

[regnad]

Maybe it should have been named ShadAuReiNand.

 

[Aurora Wright]

Besides, it isn't even "minimalist". If it were it'd either force the user to load their firmware from either NAND or from file. Giving the user more options at the cost of LOC doesn't count towards "minimalism"

Minimalism is entirely subjective. And this shows from the features of this, Mizuki and RN (all three define themselves as minimalists), which are all different. I might want the splash screen but not external payloads, or maybe I might not want firmware.bin loading, so for me a CFW with firmware.bin loading isn't minimalist. Someone else might want firmware.bin but not the splash screen, and so on. Making a program which fits a lot of different use cases isn't easy.

 

[a9lh-1user]

Forgett "Mizuki" as it looks like this is now CLOSED source!
Thanks to many discussions that are not even discussions but personal meanings to subjects most of the people who mean have something to say didn't know about what they are talking about!
I'am very confused and a little bit angry because "Mizuki" was one of those CFW i liked very much.......Now i could't use it at version 1.2 and NO UPDATES will be coming

 

[Aurora Wright]

Forgett "Mizuki" as it looks like this is now CLOSED source!
Thanks to many discussions that are not even discussions but personal meanings to subjects most of the people who mean have something to say didn't know about what they are talking about!
I'am very confused and a little bit angry because "Mizuki" was one of those CFW i liked very much.......Now i could't use it at version 1.2 and NO UPDATES will be coming

Could you please rewrite that? I'm having an hard time reading it. What's "closed source" now? None of these projects can be closed source without breaking the (GPL) license.

 

[Docmudkipz]

Could you please rewrite that? I'm having an hard time reading it. What's "closed source" now? None of these projects can be closed source without breaking the (GPL) license.

Dax requested the Mizuki thread to be locked

 

[MassExplosion213]

Could you please rewrite that? I'm having an hard time reading it. What's "closed source" now? None of these projects can be closed source without breaking the (GPL) license.

Mizuki has gone under. The OP is now gone, as is the source.

 

[Shadowhand]

What, why?!

 

[Docmudkipz]

Forgett "Mizuki" as it looks like this is now CLOSED source!
Thanks to many discussions that are not even discussions but personal meanings to subjects most of the people who mean have something to say didn't know about what they are talking about!
I'am very confused and a little bit angry because "Mizuki" was one of those CFW i liked very much.......Now i could't use it at version 1.2 and NO UPDATES will be coming

@daxtsu is trying to make a point by doing that. Mizuki was the initial spark that brought the discussion and this lit the flame. If you can't see that then I can't help you. Though I still use Mizuki

 

[a9lh-1user]

Sorry for the misunderstanding (wrong writting from me!)
English isn't my native language!
What im meant is it is closed (not anymore here or at github for download)
I asked daxtsu on his profile page why ...... take a look at the answer

 

[Shadowhand]

@daxtsu is trying to make a point by doing that. Mizuki was the initial spark that brought the discussion and this lit the flame. If you can't see that then I can't help you. Though I still use Mizuki

Mizuki was just released before I released ShadowNAND (a private project based on ARN 3.14, that was working, but wasn't publicly talked about), I had been telling everyone that I wanted to make such a thing, and then, two-three days later, Mizuki was released. With exact set of features I said I'd do, so I canned ShadowNAND and started over on ShadowFW based on ARN 5.1.x.

 

[a9lh-1user]

As i wrote befeore i'am a USER.
I like to try things and play around with them (CFW also as tools).
But sorry if i misunderstand that again (dont think i do!) but normaly if there is a thread with a RELEASE there are questions for things that could be implemented, or things that dosn't work......and so on.
But here in MANY RELEASE threads are more spam and flaming messages and it is VERY hard to read from the first to the last page to get the information USERS need.
If someone want a discussion about what is "stolen" "not correct" or on a higher level (programming skills, code basis....and so on) IMHO there has to be another thread for that or PM's or a IRC conversation with the person i have a problem with!

Take a look at those RELEASE threads for CFW and tell me i'am wrong!
I'am the first person who say "SORRY I MAD A MISTAKE"

 

[Wolfvak]

@daxtsu is trying to make a point by doing that. Mizuki was the initial spark that brought the discussion and this lit the flame. If you can't see that then I can't help you. Though I still use Mizuki

Well, he got the point accross. Unfortunately Mizuki was the only cfw (that I know of) that had an external injector.cxi, making it quite easy to prototype this stuff. Other cfw s have this built-in which is nicer for noobs but not better for regular users.
And I want to bring up a point here, which is quite off-topic: the noobs are part of the issue, they were so confused by simple instructions that they had to be spoonfed. Not giving any elitism/SALTiness here, but it should be a little harder (not un-safer) to do all this stuff

BTW @Shadowhand did you want to release this before adding your unique features?

 

[Docmudkipz]

Mizuki was just released before I released ShadowNAND (a private project based on ARN 3.14, that was working, but wasn't publicly talked about), I had been telling everyone that I wanted to make such a thing, and then, two-three days later, Mizuki was released. With exact set of features I said I'd do, so I canned ShadowNAND and started over on ShadowFW based on ARN 5.1.x.

The entire forking discussion started when Mizuki was released and Yifan was expressing concerns about it but most people ended up blowing it off or giving it a pass for whatever reason. The problem lies in the fact that with each release of a cfw that really hasn't changed we're indirectly telling newer devs that its okay to do that sort of thing and that's when it becomes a moral issue, legality was never a problem.

As i wrote befeore i'am a USER.
I like to try things and play around with them (CFW also as tools).
But sorry if i misunderstand that again (dont think i do!) but normaly if there is a thread with a RELEASE there are questions for things that could be implemented, or things that dosn't work......and so on.
But here in MANY RELEASE threads are more spam and flaming messages and it is VERY hard to read from the first to the last page to get the information USERS need.
If someone want a discussion about what is "stolen" "not correct" or on a higher level (programming skills, code basis....and so on) IMHO there has to be another thread for that or PM's or a IRC conversation with the person i have a problem with!

Take a look at those RELEASE threads for CFW and tell me i'am wrong!
I'am the first person who say "SORRY I MAD A MISTAKE"

This was an extremely important discussion imo, but if Shadow wants to continue it then by all means go for it, I'd just like to see some unique features soon to set it apart from ARN.

Well, he got the point accross. Unfortunately Mizuki was the only cfw (that I know of) that had an external injector.cxi, making it quite easy to prototype this stuff. Other cfw s have this built-in which is nicer for noobs but not better for regular users.
And I want to bring up a point here, which is quite off-topic: the noobs are part of the issue, they were so confused by simple instructions that they had to be spoonfed. Not giving any elitism/SALTiness here, but it should be a little harder (not un-safer) to do all this stuff

BTW @Shadowhand did you want to release this before adding your unique features?

The best way to do this is tell them to compile it themselves. And make something go wrong if they mess up.

 

[peteruk]

Dax asked me not to post anything defending Mizuki etc... and I will respect his wishes

All I have to say is I am very disappointed this has happened and it will no longer be shared publicly

 

[Shadowhand]

BTW @Shadowhand did you want to release this before adding your unique features?

That's a hard question to answer: It's not completely ready for public consumption. As I told you privately as well, I wanted it to be a base for my upcoming work. But it was also a bug-free product that didn't need alpha/beta testing. So as far as the working base I had in mind goes, v1.0 is a feature-complete release. Did I want it publicly? Yes, but if I had known that the scene was full of bitter, unwelcoming people, I wouldn't have given the greenlight to @icecream.

I will continue developing SFW further, but I'm extremely disappointed in the scene.

 

[peteruk]

That's a hard question to answer: It's not completely ready for public consumption. As I told you privately as well, I wanted it to be a base for my upcoming work. But it was also a bug-free product that didn't need alpha/beta testing. So as far as the working base I had in mind goes, v1.0 is a feature-complete release. Did I want it publicly? Yes, but if I had known that the scene was full of bitter, unwelcoming people, I wouldn't have given the greenlight to @icecream.

I will continue developing SFW further, but I'm extremely disappointed in the scene.

Carry on regardless, pay no attention the the negativity, do your own thing, if people use it then great, if they don't like it then it doesn't matter

 

[Wolfvak]

Dax asked me not to post anything defending Mizuki etc... and I will respect his wishes

All I have to say is I am very disappointed this has happened and it will no longer be shared publicly

Don't worry, Mizuki was pretty much replacing memcpy() with a fileRead(). Although I have to admit that it was a welcome change on my part, not so sure about other people tho.

That's a hard question to answer: It's not completely ready for public consumption. As I told you privately as well, I wanted it to be a base for my upcoming work. But it was also a bug-free product that didn't need alpha/beta testing. So as far as the working base I had in mind goes, v1.0 is a feature-complete release. Did I want it publicly? Yes, but if I had known that the scene was full of bitter, unwelcoming people, I wouldn't have given the greenlight to @icecream.

I will continue developing SFW further, but I'm extremely disappointed in the scene.

Go ahead, I expect great things. Sorry if I sounded ass-holeish but really, right now it's just a rebranded ARN for the most part.

 

[Shadowhand]

Go ahead, I expect great things. Sorry if I sounded ass-holeish but really, right now it's just a rebranded ARN for the most part.

Again, I never claimed it to be more. I said it time and time again that it's ARN-Lite as it stands right now.

 

[Aurora Wright]

To address the external 3ds_injector thing: I'm sure if a dev is able to make patches to ASM code they're also able to compile ARN. I like the bundled approach because it seamlessly allows userland patching without the user needing to know (I can even configure patches, such as CPU mode, Ver. and stuff). My focus is on user-friendliness, so that's that

 

[MassExplosion213]

To address the external 3ds_injector thing: I'm sure if a dev is able to make patches to ASM code they're also able to compile ARN. I like the bundled approach because it seamlessly allows userland patching without the user needing to know (I can even configure patches, such as CPU mode, Ver. and stuff). My focus is on user-friendliness, so that's that

This makes sense, but the OPTION to is always better. It avoids having to recompile the entirety of ARN to fix a single missed semicolon.