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
I say they're for end users, cause if an end user wants to do them, now they can. That's caring about the needs of the end user. We keep throwing that term around like we're releasing the next iPhone.
Well we're not releasing the next iPhone. We're executing unauthorized code on a heavily locked-down Nintendo console.
no, the nand backups are fucking broken, they're not for the end user, haha. the way you pseudo-fixed them is wrong and gross. corrupted backups will still happen even if more rare.
and is that really what you call "heavily locked-down" ? lmao
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)
compiling things has nothing to do with electronics
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.
i'm sorry but that ""release"" is fucked up. i can't call that a release and even for developers it's gross. the ropchain is gross, the way the iosusb exploit is done is gross, etc. so no, you can't really get much out of it without having to fix up all their fucked mess.
plus, rewriting the rednand patches in C, what the fuck ???
You aren't going to break a console running this. If you "know enough to get by which could get me in trouble if I'm not careful" then you should know enough to not brick. You WILL not brick sysNAND without trying. If you try to brick sysNAND fuck yeah you can, if you aren't trying, it won't happen. Unlink your NANDs and don't be an idiot. This wasn't a release. Not at all. We did all of the work in a public IRC, releasing zips and other compiled things linking the source and other things. It was never "released" we just put it out there. It has a lot to offer. Y'know. That Brazilian method everyone is using right now, it more risky than installing games/shit with redNAND, by far. Install something corrupt and it bricks? You're fucked. If you have redNAND, guess what? You won't brick. Getting to redNAND has literally no risk of bricking. The only people I think can "brick" their sysNAND and/or redNAND are the devs, not the end-users, it'd take some titles that you made yourself, that are FUCKED to do it, or messing with wupclient enough.
TL;DR: You aren't gonna brick, quit bitching. There is a lot of shit you gain from using redNAND.
btw this isn't just for you, im just done with listening to people whine about the main idea of it being not worth it and risky
you
can brick with the current ""release"", haha. and even if you do know enough, you can still brick by touching something you could never have thought it would brick your console. you can brick even with fucking nand dumping. and to me, it's not work, it's duct-taped shit. you guys have no idea of what the fuck you are doing and that's truly impressive to still see you bitching around on forums, calling it a ""release""; which even devs that know what the fuck they are doing wouldn't use. and fyi, you can brick your console in redNAND, lmao.
You guys need to keep in mind that "the wiiubru team" started working on this (aka starting implementing the iosu userland exploit) exactly 1 month ago with 1 guy. So its quite impressive what we have so far, big props to everyone who worked on it and contributed. To be fair, there is/was iosuhax by smea so rednand, wupserver,nanddumper and much things were already done. This helped and speed up everything a lot.( I don't know when team SALT started, but they should've had this same "bonus".)
But! the whole dumper was ported and rewritten from arm assembler to actual readable, flexible (8GB + 32GB) and stable C code with more features (auto dumping, backup/injectinf tool) + the wupclient was fixed etc.
For the time this has been worked on + the progress has been made + the few people doing that in their freetime (probably in besides jobs and family) its really fucking impressive and not "rushed".
Maybe we could re-define "for endusers" as "you can't brick your fucking console, no matter what you're trying"
1 month is this a fucking joke... anyway, won't comment on that, haha.
i don't see how ARM isn't flexible lmao. in that case i don't see the point of rewriting a
broken dumper in C (+ rewriting the rednand patches). dumping the same block multiple times and checking it with the previous one isn't a solution to broken dumps haha.
for the time it has been being worked on, this is fucking disappointing. the progress is more than minor.
and you can brick your fucking console in redNAND.