Here are two objectively useful things that are for end users that have come out in the last week, as a result of the public work:
- vWii Hacking without a game
- creating a NAND backup
[...]
And no, none of this is to speak ill-will of any Salt team developers. But it's silly to pretend like the public work is somehow hurting the scene or creating some big mess. If anything, Salt now has more information to work with due to the public info that's out there now. And when their miracle system comes along, it can come along. [...]
I never stated this release hurts the scene. In fact I think it's good for the scene.
While I do agree the features, like you said, benefit what I would call the "end user", you have to realize people mupping about with this release do have a chance to brick their systems, especially those who don't really know what they are doing.
It's definitely good enough for those who know their way around electronics (if you can compile this fw.img you probably do) but you have to consider that lower-tier users who will find a way to get their hands on this (probably doesn't help with people like me uploading precompiled... but I mostly did that for windows users like me which is obnoxious to get to compile)
The WiiUBru release is great, especially for those who know how to properly make use of it. But until we get better tools the only real advantage with the current redNAND over sysNAND with the USB method is installing pirated DLC and eShop titles. At this point it is pure piracy for both the USB method and redNAND. And I'm not saying that's bad as it opens the door to more in the future.
What WiiUBru could do to really impress me is making HBL as an installable title for redNAND.
I'm not even really against normal users using this, but I just hope they know what they are doing when going in.
Also does anyone know if updating firmware from redNAND still bricks the system? I'm wondering if that is something that WiiUBru fixed yet or plans on fixing. Last I heard updating the firmware from redNAND has the potential to brick because it still writes to system EEPROM and some other things. And if so I would like that and a list of other things that could potentially brick the system (not just brick redNAND) in a stickied thread to at least help prevent anything like that from happening.
Thank you WiiUBru for providing a list of user-reported bricks:
http://pastebin.com/wMSNfZTV
With this list we can find out what has caused previous bricks and hopefully help prevent future bricks.
Also to note, a good way to make sure you are on redNAND is to create a folder in the same spot on both sysNAND and redNAND, naming them appropriately (and I recolored the redNAND one red so it is easy to see the difference)