[Guide] Kafluke's HardMod CBHC Unbrick guide

Discussion in 'Wii U - Hacking & Backup Loaders' started by Kafluke, Jul 7, 2017.

  1. sarkwalvein

    sarkwalvein There's hope for a Xenosaga port.

    Member
    18
    GBAtemp Patron
    sarkwalvein is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    Jun 29, 2007
    Germany
    Niedersachsen
    I think I fixed that now on the OP.
     
  2. n00b2015

    n00b2015 GBAtemp Fan

    Member
    2
    Oct 19, 2015
    Slovenia
    I did everything by your tutorial.
     
    Last edited by n00b2015, Mar 21, 2018
  3. sarkwalvein

    sarkwalvein There's hope for a Xenosaga port.

    Member
    18
    GBAtemp Patron
    sarkwalvein is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    Jun 29, 2007
    Germany
    Niedersachsen
    As I said before, I don't have experience with this, so I feel I am doing just administrative work here, anyway perhaps it helps.

    First, @n00b2015 I would like if you could read, verify, and answer each of these questions based on the OP: (almost a checklist)

    1. Is your Teensy++ a Teensy++ 2.0?

    2. Did you cut the track between the 3.3V and 5V pads?

    3. Did you check there is no continuity between those pads?

    4. Did you solder the 3.3V voltage regulator?

    5. Did you check you get 3.3V between the regulator output and GND while it is powered?

    6. Did you flash the appropriate HEX file to the Teensy? (NANDway_SignalBoosterEdition.hex)

    7. Did you check all the "solder together" points in the Teensy have continuity, checking from the board side, pin to pin?

    8. Did you connect *RB and *CE points to the appropriate solder point in the Wii U board, according to the NAND you want to dump? (see pictures in section 2. SOLDER THE TEENSY TO THE WII U BOARD)
    => I guess it is RB2 and CE2 if you are trying to dump the WiiU NAND.

    9. Did you check continuity between each solder point on the Teensy PCB, and the corresponding pin of the NAND chip directly? (that is, check between the Teensy board and the pins from PINOUT picture in section 2. SOLDER...)

    10. Did you solder the ground cable to the same point as the it is in the corresponding picture in Section 2? (marked as GND with a red circle in that picture)

    11. In a previous post you said:
    "When i connect Teensy to PC and reassemble Wii U and press power button on, the light blinks blue and fan doesn't start."

    But according to the guide on the OP, you must:
    Did you check actually following this sequence? That is, first with the Teensy disconnected from the PC (and the Wii U disconnected from power), plug your Wii U to power and turn it on, only then plug the Teensy to the PC via USB cable.




    @Kafluke or anybody else with experience on this:

    1. Point 4 in section 3 of the OP states:
    "Turn on your Wii U. The power LED should turn blue and your fan should spin."

    But as @n00b2015 states, for him:
    "When i connect Teensy to PC and reassemble Wii U and press power button on, the light blinks blue and fan doesn't start."

    I suppose this is not the expected behavior, is there some reason this could happen, and a suggested way to fix this?

    2. When @n00b2015 runs NANDway.py, he gets a weird "0xff 0xff 0xff 0xff 0xff" reading from the NAND, and subsequently an error message. This reading suggests to me either bad power voltage on the Teensy, bad initialization of the NAND chip (due perhaps to point 11 in the checklist above), bad cabling, or (less probable) a very damaged NAND chip.
    Do you know what could actually be a common cause for this, and a suitable solution?

    @n00b2015's NANDway.py output below:

    NANDway.py COM3 0 dump slc.bin

    Pinging Teensy...
    Available memory: 3776 bytes
    NAND0 information:
    Raw ID data: 0xff 0xff 0xff 0xff 0xff
    Error reading size of NAND! Exiting...
     
    Last edited by sarkwalvein, Mar 21, 2018
  4. Kafluke
    OP

    Kafluke GBAtemp Guru

    Member
    14
    May 6, 2006
    United States
    I don't think I could do any better than that^

    I asked the user to read through the OP because I don't know he/she did any of those steps but no response back.
     
  5. n00b2015

    n00b2015 GBAtemp Fan

    Member
    2
    Oct 19, 2015
    Slovenia
    1. yes
    2. yes
    3. yes
    4. yes
    5. yes
    6. yes
    7. yes
    8. yes
    9. not but i checked connections several times
    10. yes
    11. yes blue light blinking and fan wont start
     
  6. sarkwalvein

    sarkwalvein There's hope for a Xenosaga port.

    Member
    18
    GBAtemp Patron
    sarkwalvein is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    Jun 29, 2007
    Germany
    Niedersachsen
    Are the optical drive and fan connected to the Wii U board?

    There are a couple of clues that make me see you have the correct HEX file flashed, the correct COM port selected, and that the communication between PC and Teensy is correct (i.e. you get 3776 bytes RAM free as the result from the ping).
    So, the problem is not on the PC->Teensy side, but on the Teensy->Wii U side, or on the Wii U itself.

    The websites I've read report similar problems (0xff 0xff 0xff 0xff 0xff readings) when there are power problems in the NAND chip, so I would suggest you to 10x check all connections from the Teensy to the pins from the NAND chip directly, and specially check if there are no shorts in the Wii U board, around the points you have soldered.

    I can't think of anything else.

    PS: Another possibility would be some of the Teensy pins used for serial communication shorted.
     
    Last edited by sarkwalvein, Mar 21, 2018
  7. n00b2015

    n00b2015 GBAtemp Fan

    Member
    2
    Oct 19, 2015
    Slovenia
    i resoldered and gonna start from scratch tomorrow.
     
  8. n00b2015

    n00b2015 GBAtemp Fan

    Member
    2
    Oct 19, 2015
    Slovenia
    RIP Wii U
    I overheated connectors on board. I’m done.
     
  9. Kafluke
    OP

    Kafluke GBAtemp Guru

    Member
    14
    May 6, 2006
    United States
    Yeah. I did the same to the first one I tried. That's some delicate soldering there. I used the alternate solder points on the nand itself and it worked after destroying the main solder points. Had to buy a really fine tip for my iron though
     
  10. n00b2015

    n00b2015 GBAtemp Fan

    Member
    2
    Oct 19, 2015
    Slovenia
    At least I tried. Can you solder directly on chip? I tried, but even 40 AWG Kynar wire si too thick.

    And yes, I had connected optical drive and fan to the WII U board.
    I’m not great at soldering, but I have managed to solder QSB to ps3 super slim, Modbo to Ps2 slim, and other like ONEchip to PSone, but this is on the other level.
     
    Last edited by n00b2015, Mar 22, 2018
  11. Kafluke
    OP

    Kafluke GBAtemp Guru

    Member
    14
    May 6, 2006
    United States
    Yes you can. Instructions are in the OP. You need very very tiny wire
     
  12. d41u5

    d41u5 Newbie

    Newcomer
    1
    May 20, 2017
    France
    Hi Dudes,
    Any idea for a result like that for the vwrite phase:

    I:\WIIUIMG\NORway-master>NANDway.py COM3 0 vwrite fix2.slc.ORI.full.img
    NANDway v0.65 - Teensy++ 2.0 NAND Flasher for PS3/Xbox/Wii
    Pinging Teensy...
    Available memory: 3776 bytes
    NAND0 information:
    Raw ID data: 0xad 0xdc 0x90 0x95 0x54
    NAND chip manufacturer: Hynix (0xad)
    NAND chip type: H27U4G8F2D (0xdc)
    NAND size: 512 MB
    NAND plus RAS size: 528 MB
    Page size: 2048 bytes
    Page plus RAS size: 2112 bytes
    Block size: 131072 bytes
    Block plus RAS size: 135168 bytes
    RAS size: 64 bytes
    Plane size: 268435456 bytes
    Pages per block: 64
    Number of blocks: 4096
    Number of pages: 262144
    Number of planes: 2
    Bus width: 8-bit
    Writing...
    Writing 1000 blocks to device (starting at offset 0)...
    Device is write-protected!
    Block 0 - error erasing block
    132 KB / 540672 KB Device is write-protected!
    Block 1 - error erasing block
    264 KB / 540672 KB Device is write-protected!
    Block 2 - error erasing block
    396 KB / 540672 KB Device is write-protected!
    Block 3 - error erasing block
    528 KB / 540672 KB Device is write-protected!
    Block 4 - error erasing block

    I've just put in place my 3.3v regulator, i ve check the output, dump & info command is ok.
    Before sold the regulator I was able to vwrite without and error. But when I redump to check it nothing was write really.
    It why I add the 3.3v regulator, but now I get this error of write-protected device :(

    (ps I use Signal Booster Edition)

    br,

    BsP
     
    Last edited by d41u5, May 24, 2018
  13. KingBlank

    KingBlank King of Nothing

    Member
    6
    Sep 17, 2008
    New Zealand
    New Zealand
    Hi, I ended up with one of the Wii U units that bricked around the time the Wii U launched, do you know if it is possible for me to revive this using someone elses backup?
     
  14. godreborn

    godreborn GBAtemp Guru

    Member
    12
    Oct 10, 2009
    United States
    unfortunately, you can't.
     
    KingBlank likes this.
  15. edizius2

    edizius2 Member

    Newcomer
    1
    Nov 10, 2018
    Germany
    Hi all,

    in this tutorial: after soldering everithing, and connecting optical drive, fan and front cover, and plug to AC the red LED goes on. But pressing the ON/OFF button has no effect (keeps red). Has anyone expirienced this problem ass well resp. knows what might be the problem?

    cheers,
    Edizius

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

    HDMI output stays black as well. Would a overheated NAND show such a behaviour? Because I have seen that the text from the NAND has partially dissapeared. Maybe I destroyed it by overheating it by soldering the 2nd row (closer one to the chip)?
     
  16. Litle_Bird

    Litle_Bird GBAtemp Regular

    Member
    5
    Jan 1, 2017
    Sweden
    If I recall that exact behaviour occured when I accidentially removed some solderpads where you attatch the wires.
     
  17. edizius2

    edizius2 Member

    Newcomer
    1
    Nov 10, 2018
    Germany
    OK, thank you. I'll have a check If they are all still connected.
    Have you had the problem although the teensy was not yet connected to the PC? Or has the compleate pad been removed from the PCB in your case?
    Anyhow, thanks, first hint what i can check.

    P.S. attached the picture of my nand. But I remember that i have had some flux on the chip. Maybe by removing the paste the text has been removed?
     

    Attached Files:

    Last edited by edizius2, Dec 11, 2018
  18. Litle_Bird

    Litle_Bird GBAtemp Regular

    Member
    5
    Jan 1, 2017
    Sweden
    Well, it was a harder project than I could handle, and in so I messed up. So the entire pad got desoldered, and that was before finishing up the solderjob and connecting the teensy

    Regarding the text on the chip, I would say it is possible it was removed by flux/cleaning, but someone might correct me.
     
  19. edizius2

    edizius2 Member

    Newcomer
    1
    Nov 10, 2018
    Germany
    Yes, I am also strugeling more than expected. I thought the soldering to the board is the hardest part, but the whole project consists of critical parts. So I am not wondering if it is compleately dead now. I have bought already a new one, but using all my games installed to the external HDD and the game saves would be really appriciated. So I hope I can revive it.
     
  20. edizius2

    edizius2 Member

    Newcomer
    1
    Nov 10, 2018
    Germany
    Can I get game saves via eMMC with a SD card reader? Or is it saved in the HDD?
     
Quick Reply
Draft saved Draft deleted
Loading...