System Transfer From Non-Hacked -> Hacked Wii U

Discussion in 'Wii U - Hacking & Backup Loaders' started by Belickade, Mar 1, 2017.

  1. Belickade
    OP

    Belickade Member

    Newcomer
    13
    0
    Apr 20, 2015
    Canada
    I have 2 Wii U consoles. The 32GB Deluxe (Black) and the 8GB Basic (White). The 8GB is my Hacked console, while the Deluxe 32GB model is my non-hacked system.

    I've decided to sell off the 32GB system, while keeping the 8GB Basic. The 32GB has been my main system. It has all my saves, purchased content etc. I've hacked the 8GB system's vWii and installed Haxchi via a DS game (non-coldboot) and set up RedNand on it.

    I'd like to System Transfer from the 32GB (non-hacked) to my 8GB (hacked) Wii U. Is this safe to do? Are there any precautions/issues I need to be aware of?
     
  2. Kafluke

    Kafluke GBAtemp Psycho!

    Member
    3,569
    1,763
    May 6, 2006
    United States
    You should be just fine to go ahead with the transfer. All the transfer really does is "marry" your Wii U to the NNID of the other one. You might have to just re-download all your purchased content. No big deal.

    No update to worry about at the time of this posting and I don't really think they'll be a new one on Friday since Zelda runs on 5.5 1 right now just fine. So just re-download everything from eshop before you enable update blocking.
     
    Last edited by Kafluke, Mar 1, 2017
  3. Belickade
    OP

    Belickade Member

    Newcomer
    13
    0
    Apr 20, 2015
    Canada
    Well, it seems I was correct in assuming it wouldn't just transfer over without error.

    When selecting my Hacked system (the 8GB Basic) as the Source system from the transfer menu, error code 162-3006 pops up. I've searched through Google and it seems others have encountered this error when attempting to update their systems. My system works fine and is updated to the current firmware.

    From what I've read, this error was caused by an incorrect IOS installed on the vwii side. I ran syscheck but I can't seem to pinpoint if I have the same problem.

    Here is my syscheck:

    Warning: Spoilers inside!

    Does anyone have any information on this? Any ideas what I could try to resolve this? Googling Wii U system transfer provides almost no information, even less so for a hacked system.
     
  4. cjizzle

    cjizzle Member

    Newcomer
    46
    41
    Dec 10, 2011
    United States
    Are both of your consoles on the same SM version?

    I can't speak for the error code, but if you believe some incorrect IOS on the vWii side is causing issue you could run a syscheck on both and compare them. If something is wrong, dump the correct IOS and install it to the other. If both are the same keep searching lol
     
  5. Belickade
    OP

    Belickade Member

    Newcomer
    13
    0
    Apr 20, 2015
    Canada
    SM version? Do you mean the same system version? Both are running the latest 5.5.1.

    I'm only guessing that the error may be related to the vwii side of things since the only mention of it that I can find on the net has a topic here mentioning people being unable to update their Wii U system because of an incorrectly installed IOS.

    If I select my Hacked Wii U as the Source console, the error doesn't pop up. If I select it as the target console, the error immediately pops up. It pops up so fast it almost doesn't seem as though it is even checking anything, just errors out immediately. There has got to be a reason for this. I think it's pretty obvious something on the system is preventing the transfer.
     
  6. CreeperMario

    CreeperMario GBAtemp Advanced Fan

    Member
    616
    364
    Jun 18, 2016
    Australia
    OSv10 v15702
    Your syscheck looks fine to me. IOSes after slot 200 (236, 249, 250, 251) should work without any issues.
     
  7. Belickade
    OP

    Belickade Member

    Newcomer
    13
    0
    Apr 20, 2015
    Canada
    Decided to format the system to see if that solved the problem. Surprisingly, it seemed to have done the trick. Was able to initiate and complete the system transfer afterwards. It's a shame as I would have preferred to figure out what was causing it so I could learn something and possibly prevent it from happening in the future if the need arises for another system transfer. Oh well.