[Solved] Unable to dump NAND

Discussion in 'Wii U - Hacking & Backup Loaders' started by SilenceBreaker, Nov 2, 2016.

  1. SilenceBreaker
    OP

    SilenceBreaker Member

    Newcomer
    13
    3
    Nov 2, 2016
    Swaziland
    This problem has been solved!

    Problem was the Transcend MicroSD, specifically the model TS64GUSDU1.
    While the WiiU was able to read and launch homebrew from that card, the dumper, or the console in general, was unable to write to it.

    So I've simply purchased a SanDisk 64GB MicroSD (SDSQUNC-064G-GN6MA) and formatted it as FAT32 with a cluster size of 64kb in order to make it work with the console.

    Ultimately, if you're seeing this and happen to have the same error as me ("Cannot write to the drive."), then it's most likely your SD card that doesn't play nice with the console.




    Hello guys!

    I'm basically experiencing the problem stated in the title.

    Now, to specify on what I mean exactly, I can't dump the NAND because CFWbooter is giving me an error.

    So after launching CFWbooter, I'm asked to simply hit the power button on the console to initiate the dump as you might already know.

    Thing is, after a few seconds, it aborts with the error "Cannot write to the drive." and simply reboots the console.

    I am using a Transcend 64GB microSD (TS64GUSDU1) with a generic, bland microSD to SD card adapter. The write-lock is not engaged of course.

    The SD is formatted in FAT32 (obviously) using a cluster/allocation size of 64kb.

    The fw.img file has been obtained from an external site whose name would probably violate the rules of this forum, basically meaning it was not compiled by me.

    If it helps, nothing else except for the SD card is inserted in the console.

    I've tried the following things already:
    - Reformatting the SD with a cluster size of 64kb instead of 32kb (primary partition)
    - Formatting the whole system
    - Use different microSD to SD card adapters (they are all the same function-wise anyway but one might could have had a bad pin or something, which is why I've tried doing that).

    Attached below is an image of the error.
    Do excuse the incredibly blurry and bad quality of the picture, but getting the camera to focus on only the text wasn't exactly easy. The white background didn't help with that either.
    Image

    Do any of you guys have an idea why this doesn't work?
    Is perhaps my SD card not supported?

    Any help would be greatly appreciated.

    Update:
    So I've noticed that while dimoks branch enables me to boot fw.img completely, I always get to face that "cannot write to the drive" error, which I'm currently blaming on my SD card.

    For some reason, FIX94s branch makes my fw.img cause a kernel panic, thus making the console crash to the home screen. I've attached a picture below documenting this phenomena. My wild guess is that the compiled fw.img of FIX94s branch contains a fatal bug. Maybe its fw.img somehow just compiled wrong for me though. Apparently this is completely normal and not in fact a kernel panic. This doesn't make things any different though because it still crashes to the home menu without any prompts to dump the NAND.

    I will now dig in said branch and see if I can get a revision of the project that could work for me. If I get no positive results, however, I'll just try a different SD card.

    "Error"
     
    Last edited by SilenceBreaker, Nov 3, 2016


  2. SomeGamer

    SomeGamer Within Hyrule Castle

    Member
    5,729
    2,676
    Dec 19, 2014
    Hungary
    Sorry for the obvious advice you may or may not have seen coming but please, for your own Wii U's safety, compile that fw.img yourself!
     
  3. x65943

    x65943 Resident Greekaboo, Amateur Dog Father

    Member
    2,452
    1,952
    Jun 23, 2014
    United States
    Indiana
  4. SomeGamer

    SomeGamer Within Hyrule Castle

    Member
    5,729
    2,676
    Dec 19, 2014
    Hungary
  5. SilenceBreaker
    OP

    SilenceBreaker Member

    Newcomer
    13
    3
    Nov 2, 2016
    Swaziland
    Alright, first of all thank you for providing such a swift answer.

    I guess I should have seen this coming.

    The reason why I haven't compiled it myself is because I figured a precompiled version would suffice, but that might be very well not be the case.

    I'll go ahead and perform the steps in the fw.img guide, linked by x65943. I'll also try to compare the MD5/SHA-256 hashes of my file vs the one I downloaded to see if this could change anything in the first place.
     
  6. x65943

    x65943 Resident Greekaboo, Amateur Dog Father

    Member
    2,452
    1,952
    Jun 23, 2014
    United States
    Indiana
    The MD5 is going to change unless you downloaded a fw.img compiled today - as Dimok has been updating things.
     
  7. SilenceBreaker
    OP

    SilenceBreaker Member

    Newcomer
    13
    3
    Nov 2, 2016
    Swaziland
    Ah, I see. Thanks for telling me that.
     
  8. aspire78

    aspire78 Advanced Member

    Newcomer
    82
    16
    Nov 29, 2015
    Swaziland
    Check if your SD is not write protected ..

    [​IMG]
     
  9. x65943

    x65943 Resident Greekaboo, Amateur Dog Father

    Member
    2,452
    1,952
    Jun 23, 2014
    United States
    Indiana
     
  10. SilenceBreaker
    OP

    SilenceBreaker Member

    Newcomer
    13
    3
    Nov 2, 2016
    Swaziland
    Alright, so I can finally report back with some news.

    I managed to compile the fw.img after fiddling around with some erros I've encountered during the installation.

    Unfortunately the system crashes back to the home screen after launching fw.img, only showing me the usual red screen and something along the lines of "initializing ..." in the top left corner for a few seconds.

    I've already verified the CRC-32 hash of both files (fw.img and fw.img.full.bin), and they seem to match with the ones provided in "getfwimg.py".

    I was using FIX94s branch but will now try the one of dimok. Let's see if this changes anything.

    — Posts automatically merged - Please don't double post! —

    It's me again.

    Dimoks branch enabled me to completely boot into fw.img this time, however I'm facing the same "Cannot write to the drive" error all over again...

    So basically this means I'm back at square one. I'll try and see if I can get FIX94s branch to boot in the meanwhile.

    If that fails I'll just try a different SD card tomorrow.
     
    x65943 likes this.
  11. opendata

    opendata Advanced Member

    Newcomer
    72
    56
    Oct 23, 2016
    Try formatting SC 64kb cluster size
     
  12. SilenceBreaker
    OP

    SilenceBreaker Member

    Newcomer
    13
    3
    Nov 2, 2016
    Swaziland
    As I've already stated above, it is formatted with your recommended cluster size.
     
  13. TheMagicMan

    TheMagicMan A Person

    Member
    310
    34
    Sep 21, 2016
    United States
    Im pretty sure the dev/net/ifmgr/ncl is suppose to happen. For me it shows that and then exits to the home menu.

    Also do you have enough space on your sd card(32gb)?
     
  14. x65943

    x65943 Resident Greekaboo, Amateur Dog Father

    Member
    2,452
    1,952
    Jun 23, 2014
    United States
    Indiana
    Dimok's dumper formats the card for you, so you don't have to worry about how much free space you have on it as long as it's a 64GB card.
     
  15. SilenceBreaker
    OP

    SilenceBreaker Member

    Newcomer
    13
    3
    Nov 2, 2016
    Swaziland
    I'm pretty sure that dev/... stuff is supposed to happen as well, but those numbers after the path indicating a kernel panic surely don't mean anything good.
    Especially if it doesn't even let me dump the NAND and instead just crashes.

    The SD has plenty of space available, so that is not a concern.

    upload_2016-11-2_22-54-35.png
     
  16. TheMagicMan

    TheMagicMan A Person

    Member
    310
    34
    Sep 21, 2016
    United States
    Oh yeah your dumping your nand. That just shows up for me when I run it nvm
     
  17. SilenceBreaker
    OP

    SilenceBreaker Member

    Newcomer
    13
    3
    Nov 2, 2016
    Swaziland
    Quick question:

    I've just noticed that my microSD is in the SDXC format.

    Could it be that the dumper is unable to access SDs in this format?
    I kind of doubt it to be honest but I'm not quite sure.
     
  18. TheMagicMan

    TheMagicMan A Person

    Member
    310
    34
    Sep 21, 2016
    United States
    So you didn't format it in Fat32 format? You need it to be Fat32 :wacko:
     
  19. ThatNintendoNerd

    ThatNintendoNerd GBAtemp Regular

    Member
    269
    41
    Feb 13, 2016
    United States
    A Cartridge
    Ah, I see what you did wrong. You need two partions, one unallocated that is about 32GB, and one that fills the rest at FAT32. Then try.

    EDIT: SDXC is fine too. I use that and works.
     
  20. x65943

    x65943 Resident Greekaboo, Amateur Dog Father

    Member
    2,452
    1,952
    Jun 23, 2014
    United States
    Indiana
    Guys the new nand dumper formats your card itself. You don't need to make any partitions.