Hacking Wii-U Error 160-0101 No Backup

matt382

Well-Known Member
OP
Member
Joined
Jan 30, 2008
Messages
134
Trophies
0
Age
30
Location
United Kingdom
XP
344
Country
Hi,

I've been given a faulty Wii U with error code 160-0101 which after reading up on it means it's bricked.

I don't have a NAND backup as the previous owner hadn't passed one over. Reading guides on unbricking all mention needing the NAND backup, but does anyone know if there's an updated method at all to fix the error without a backup.

If not I'll just keep it aside for parts
 
D

Deleted User

Guest
Hi,

I've been given a faulty Wii U with error code 160-0101 which after reading up on it means it's bricked.

I don't have a NAND backup as the previous owner hadn't passed one over. Reading guides on unbricking all mention needing the NAND backup, but does anyone know if there's an updated method at all to fix the error without a backup.

If not I'll just keep it aside for parts


Currently there is no "updated method" since WiiU is a complex machine. If you brick it, the processor will refuse to go on booting. No matter how much you change the parts.

Only one day when (maybe) all security can be circumvented or custom OS can be put on it without the machine noticing it, it will be possible to revert these non-booting-issues and get the machine booting up again.

But for now? Bad luck.

For now the only working method is that you need a backup of your nand.

This is because you cannot circumvent the security-system. So this is pretty much just a workaround.

And by using a backup, the security simply doesn´t know what´s going on. it simply thinks it´s OK. Since the backup is exactly the same data 1:1. So the security won´t see any differences between the old (damaged) data and the new data.

See? Once the security detects you use a non-compatible backup (just 1 bit is wrong!) your WiiU will refuse to boot.

So for now, you can only use it for spare parts...
 
  • Like
Reactions: matt382

matt382

Well-Known Member
OP
Member
Joined
Jan 30, 2008
Messages
134
Trophies
0
Age
30
Location
United Kingdom
XP
344
Country
Ah okay that's what I'd thought would be the case, but wanted to double check before I sent this console to the brick grave. Guessing the previous owner must of tried to hack it without ready the instructions first
 
  • Like
Reactions: godreborn

GerbilSoft

Well-Known Member
Member
Joined
Mar 8, 2012
Messages
2,395
Trophies
2
Age
34
XP
4,250
Country
United States
Currently there is no "updated method" since WiiU is a complex machine. If you brick it, the processor will refuse to go on booting. No matter how much you change the parts.

Only one day when (maybe) all security can be circumvented or custom OS can be put on it without the machine noticing it, it will be possible to revert these non-booting-issues and get the machine booting up again.

But for now? Bad luck.

For now the only working method is that you need a backup of your nand.

This is because you cannot circumvent the security-system. So this is pretty much just a workaround.

And by using a backup, the security simply doesn´t know what´s going on. it simply thinks it´s OK. Since the backup is exactly the same data 1:1. So the security won´t see any differences between the old (damaged) data and the new data.

See? Once the security detects you use a non-compatible backup (just 1 bit is wrong!) your WiiU will refuse to boot.

So for now, you can only use it for spare parts...
Or, instead of this word salad of nonsense, you could simply say that each console has unique NAND encryption keys, and without an OTP dump, you can't get the encryption keys. But then you couldn't pretend that you're a Super Genius® by pretending to be an expert, could you?
 
D

Deleted User

Guest
If you don't have an opt.bin or a full slc.bin backup that is associated with the unit then you got a paperweight.


Exactly!

First rule when using WiiU´s dangerous homebrew (especially when you do vWii-stuff):

Backup, Backup, Backup!

I even backuped my full mlc-content. Just for safety...

The problem is: Most people think the WiiU is just like a Wii (in terms of safety and protections against foreign code) and thus they think a backup isn´t required...until their system fails or the nand gets damaged or they simply brick it by doing unauthorized changes to the OS.

It´s funny since in our county most people also still think and handle like "a backup isn´t required". It´s cheaper!

it´s sad. But this is how modern world still works here. No backups created...saves money.
 
  • Like
Reactions: JAB03

godreborn

Welcome to the Machine
Member
Joined
Oct 10, 2009
Messages
38,471
Trophies
3
XP
29,138
Country
United States
the good news is that the gamepad is like two-thirds the cost of a full wii u, and the gamepad should be fine if you bricked the console itself (or at least the previous owner in your case). you can probably find consoles by themselves on ebay. I found one a long time ago that was on 5.3.2, when that was the highest hackable, by itself with no gamepad. I updated the system after 5.5.1 was hackable. I bought the system, when it was rare, for $150 many years ago. now that any system is hackable pretty much you can buy one for maybe $60 (without looking at ebay). I still have that second system, in case I ever need it. I once bought a box for it, a wii u box, and it came crushed, because the person put it in a skin-tight packaging material. that really pissed me off, because paypal sided with the seller for some reason. I haven't bought a box for it since. I need a box for my superslim ps3 as well, but those cost like $50 (major ripoff!).
 

tarekhaig

New Member
Newbie
Joined
Dec 16, 2021
Messages
4
Trophies
0
Age
34
XP
23
Country
Lebanon
Currently there is no "updated method" since WiiU is a complex machine. If you brick it, the processor will refuse to go on booting. No matter how much you change the parts.

Only one day when (maybe) all security can be circumvented or custom OS can be put on it without the machine noticing it, it will be possible to revert these non-booting-issues and get the machine booting up again.

But for now? Bad luck.

For now the only working method is that you need a backup of your nand.

This is because you cannot circumvent the security-system. So this is pretty much just a workaround.

And by using a backup, the security simply doesn´t know what´s going on. it simply thinks it´s OK. Since the backup is exactly the same data 1:1. So the security won´t see any differences between the old (damaged) data and the new data.

See? Once the security detects you use a non-compatible backup (just 1 bit is wrong!) your WiiU will refuse to boot.

So for now, you can only use it for spare parts...
i have the same error and my wii u is bricked but i have a copy of my nand back up how any idea how to fix it ?
 

tarekhaig

New Member
Newbie
Joined
Dec 16, 2021
Messages
4
Trophies
0
Age
34
XP
23
Country
Lebanon
Guys sorry to bother will any version of teensy work i just found many versions on ebay the latest one is 4.1 i think or do i need a specific version for wiiu ?
 

godreborn

Welcome to the Machine
Member
Joined
Oct 10, 2009
Messages
38,471
Trophies
3
XP
29,138
Country
United States
they recommend the teensy++ 2, but from what I've heard, it's not longer made. what is your issue? wii u doesn't boot?
 

AQS

Well-Known Member
Newcomer
Joined
Oct 15, 2021
Messages
69
Trophies
0
Age
41
XP
1,001
Country
Canada
Guys sorry to bother will any version of teensy work i just found many versions on ebay the latest one is 4.1 i think or do i need a specific version for wiiu ?

It needs to be Teensy++ 2.0 . The specific "NANDway_SignalBoosterEdition.hex" required to flash the device is only meant for this version of Teensy. To my knowledge there is no other hex file that is available for the newer versions of Teensy that are compatible with the WiiU SLC Nand.

While the original board is really hard to find for purchase, there are clones ( on Ebay or Aliexpress ) that should work. The clones require an extra circuit board cut (picture). (more info about the clone can be found here => link )

However you will require the opt.bin file for any sort of work. Make sure you have this before you go down the Teensy route.

The full guide to follow is here => link
 
Last edited by AQS,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    OctoAori20 @ OctoAori20: Nice nice-