i recompiled using the latest commit and got 91aec1450002169e68c86ed1dc75cdbd. Thanks for clarifying! Also, I had a quick question. Dumping the NAND can't brick my Wii U, right? (I assume so because I don't think it writes anything to NAND.)Just to get this hash confusion out, if you compiled fw.img before this commit, your md5 will most likely be different to the current ones. If you compiled it after, then your md5 will be
91aec1450002169e68c86ed1dc75cdbd from my branch and 55ddc0d6f3df3e11b54fedee719f6cf7 from dimoks branch.
The dumping shouldn't as that only reads.i recompiled using the latest commit and got 91aec1450002169e68c86ed1dc75cdbd. Thanks for clarifying! Also, I had a quick question. Dumping the NAND can't brick my Wii U, right? (I assume so because I don't think it writes anything to NAND.)
Yes, redNAND lives on the SD card. Hence the name redNAND, which is short for "Redirect NAND". It redirects NAND read/writes to a special partition on the SD which acts as the system NAND instead. This gives us the ability to prevent bricking the system NAND (which could only be fixed by hardmod) by instead using the SD as NAND, which if bricked would only require redumping and recreating redNAND, leaving the sysNAND (aka system NAND) mostly untouched.After I dump my NAND, will I still need a 64GB SD card to run redNAND?
OK. Thanks! (I'm an idiot. I should have known this from the 3DS scene welp ) Also, what do you mean, "mostly untouched?" Just curious.Yes, redNAND lives on the SD card. Hence the name redNAND, which is short for "Redirect NAND". It redirects NAND read/writes to a special partition on the SD which acts as the system NAND instead. This gives us the ability to prevent bricking the system NAND (which could only be fixed by hardmod) by instead using the SD as NAND, which if bricked would only require redumping and recreating redNAND, leaving the sysNAND (aka system NAND) mostly untouched.
If you leave NANDs linked it seems some things tend to leak between the NANDs. That and you will still use sysNAND for some things, so it won't be entirely untouched until we get a coldboothax, at which point we will either be using redNAND at boot, or we will have something like A9LH for 3ds where we have software sysNAND brick protection (booting homebrew with NAND read/write access before loading firmware.OK. Thanks! (I'm an idiot. I should have known this from the 3DS scene welp ) Also, what do you mean, "mostly untouched?" Just curious.
--------------------- MERGED ---------------------------
Sorry for the pestering, but I have another question. I booted CFWBooter and it seemed to load redNAND (loaded the home menu but showed some stuff on the GamePad first). Does that mean the NAND dump was successful? Using dimok's sdio_nand_extractor throws this error: NAND dump signature is not matching
Stable or not RedNand is still dangerous. Even with unlinked Nands that sysconfig tool (or any other) could still change values in your SEEPROM and brick your console. Read a lot and avoid doing anything not in the guides.OK. Thanks! (I'm an idiot. I should have known this from the 3DS scene welp ) Also, what do you mean, "mostly untouched?" Just curious.
Try it. I doubt you'll brick if you are on RedNAND.It is possible to mount the content of Optical disk on WiiU and dump a game disc in encrypted form?
I see in wupclient.py that there is a function called mount_odd_content() other then def mount_odd_tickets() used to dump ticket from inserted disk.
Hey there, have you solved this?Have same Problem. stays a bit red and tells mount something and then goes whitescreen
Guru Meditation Error (prefetch abort)
00000000
r0= some hex numbers
r1=...
...
r15=...
Console Crashes
Well, that's obviously a bug in the Makefile that CMake created, unless you edited it afterwards. Not sure what that error means, but you shouldn't have to fix it yourself, because it shouldn't be there.Hello everyone, got a little problem trying to compiling armips to make my fw.img, saying "Makefile:37: *** missing separator. Stop." when i try to "make".
Not really familiar with all of that, managed to cmake, then trying to make it give me this, would like some little help
Searched a LOT to fix that, but was out of options, so i searched for a armips 0.8 alying around for reinand or Luma3DS sad ! I and still had a problem because my armips was a debug one and i needed a release one x), still got it afterward, fw.img operational and contenthax working perfectly .Well, that's obviously a bug in the Makefile that CMake created, unless you edited it afterwards. Not sure what that error means, but you shouldn't have to fix it yourself, because it shouldn't be there.
Check if you're using up-to-date versions of Make (Cygwin/MinGW, Xcode Command Line Tools or from your package manager, depending on your platform) and CMake.
Though if you can;t be screwed updating your stuff just now, then just look up "makefile missing separator" and you should be able to find an answer.
When we say that an SD card is 32 GBs we are rounding to get that number. There's imperfections and dead sectors. Salt members (I think I remember) were talking about "¿shrinking?" the MLC (not sure what terms that means tho).hey, I'm just curious, why isn't possible yet for lower sd cards , i got a wiiu with 32gb, and im just curious why it can't be equal or higher. is anyone going to enable for that to happen. I have 32 gb sd, and not a 64... but best of luck
It's possible to install the DS VC exploit (Brain Training) to have access to homebrew launcher offline with fw.img and cfw booter?