Hacking Nand Dump Help Needed

[FordSVT53]

Hey Guys,

I am new to the Wii U Hacking, but have managed to follow wiiu.guide and successfully mod the console. The only issue I am now having is when I go to dump the files from the consold to SD, I receive "first partition not FAT32". I used guiformat and the card itself is MBR. It is a brand new Sandisk 64GB Ultra Plus SDXC UHS-1.

Any suggestions on how to get the SD card working properly? I did a clean format of the SD after the error, but still receive the same error code.

Any advice would be great!

Cheers,

Luke

 

[Kafluke]

First advise, don't follow wiiu.guide.

 

[Xyphoseos]

First advise, don't follow wiiu.guide.

Why this guide is so bad ?

 

[THEELEMENTKH]

Why this guide is so bad ?

That guide basically tells you "Do this, do that and hope it works properly"

 

[Kafluke]

Why this guide is so bad ?

I really need to write it all down so I can just copy and paste.

We have a community noob guide here. It's a guide that several contributors edit constantly. We strive to keep it current and updated. You can imagine how frustrating it must be to see new threads daily from users of other guides asking for our help to fix their issue. We didn't write those guides. We aren't responsible to keep them updated, valid, and consistent with current hacking methods. Yet we see them all the time and were left to clean up the mess.

As far as wiiu.guide goes. I get it. I used 3ds.guide as well. The major problem we see here is that it took a long time to get updated correctly. This is the reason I keep a "last checked for updates" time stamp at the top of the guide. Things change fast around here. In the beginning wii.guide was directing users to incorrectly install rednand. This took a while for the guide maker to update. Again we had user after user asking us for help with a emulated nand that was never intended for basic users. After that was fixed the wii.guide was telling users to Install CBHC but had no nand backup step. I could go on and on.

The major point is that there is no "one hack fits all". That's why our guide explains all the steps and encourages you to make your own decision.

It's important to understand what type of hack you're using when you try to troubleshoot issues.

 

[FordSVT53]

I really need to write it all down so I can just copy and paste.

We have a community noob guide here. It's a guide that several contributors edit constantly. We strive to keep it current and updated. You can imagine how frustrating it must be to see new threads daily from users of other guides asking for our help to fix their issue. We didn't write those guides. We aren't responsible to keep them updated, valid, and consistent with current hacking methods. Yet we see them all the time and were left to clean up the mess.

As far as wiiu.guide goes. I get it. I used 3ds.guide as well. The major problem we see here is that it took a long time to get updated correctly. This is the reason I keep a "last checked for updates" time stamp at the top of the guide. Things change fast around here. In the beginning wii.guide was directing users to incorrectly install rednand. This took a while for the guide maker to update. Again we had user after user asking us for help with a emulated nand that was never intended for basic users. After that was fixed the wii.guide was telling users to Install CBHC but had no nand backup step. I could go on and on.

The major point is that there is no "one hack fits all". That's why our guide explains all the steps and encourages you to make your own decision.

It's important to understand what type of hack you're using when you try to troubleshoot issues.

Hey Kafluke,

I completely understand and sorry for not even stepping back to realize that.

What would be your suggestion for either removing the steps I have taken through that guide in order to follow the steps posted on the noob guide that you mentioned?

Thanks!