Fixing error 160-0103

Serjio193 · Mar 23, 2023

Wii U 5.5.5 fix 106-0103 or how to reinstall a clean OS.

Highly recommend making a physical Nand backup.
Cheapest option using SD card reader

Also I would recommend using SD card instead of nand. This method did not work for me, because I had suspicions that the download was coming from the boot1 or boot2 area. But after reading the nand configuration, I realized that the download is coming from the user area.

Instruction:
1. Enter the recovery menu using your Nintendo Switch or Raspberry Pi Pico.
In the recovery menu, we need an item install WUP .
Through it we will restore the file system.
2.Download Title Update
Example "000500101000400A"
NUSgrabber version dos.
Download the update from the Nintendo server.
NUSGrabber OS 5.5.5-Download OS.bat
Download the update from the Nintendo server in your region.
NUSGrabber EUR 5.5.5E - Download EUR.bat
NUSGrabber EUR 5.5.5J - Download JAP.bat
NUSGrabber EUR 5.5.5U - Download USA.bat
3.Install header update
3.1 Setting the installation folder on the SD card
3.2 Copy the contents of the sample "000500101000400A" to an empty installation folder.

3.3 Insert our card into WII U and install WUP through the recovery.
3.4 After installation turn off WII U and repeat 3.2 turn on and install TitleUpdate one by one.
4. Turn on Wii u Mode and go to Home.

If the memory in the settings is not displayed correctly, you need to do a complete removal through the settings and reconfigure the console.

V10lator · Mar 23, 2023

Don't do this before inspecting logs (or at least taking a full NAND backup) as it might corrupt the filesystem even more until it reaches a point we can't fix it even with exchanging the eMMC.

Also note that with a hardware defective eMMC this will be just a temporary fix: Your Wii U will fail sooner or later and this "fix" won't work a second time.

Lastly without logs we can't be sure which titles are corrupted, so you might have to reinstall other ones.

//EDIT: We have a tutorial about how to fix error 160-0103 now: https://gbatemp.net/threads/using-nand-aid-to-replace-a-hardware-damaged-mlc-160-0103-error.636361/

Serjio193 · Mar 23, 2023

If Nand is out of order, then it will be blocked for writing. If this happens then the only method is to transfer data from nand to sd card mod (if it works) or to a new Nand.

I transferred my nand backup to a new nand from a Samsung sm-a520f phone.

Barracuda · Mar 23, 2023

Serjio193 said:
If Nand is out of order, then it will be blocked for writing. If this happens then the only method is to transfer data from nand to sd card mod (if it works) or to a new Nand.

I transferred my nand backup to a new nand from a Samsung sm-a520f phone.

how did you do it with switch?
In mine, all the partitions at the end of the line put me 0x4 and I don't get any error. I don't see the recovery menu either

Serjio193 · Mar 23, 2023

Barracuda said:
how did you do it with switch?
In mine, all the partitions at the end of the line put me 0x4 and I don't get any error. I don't see the recovery menu either

Memory card in fat32 copy the recovery file to the root and paste it into the wii u. Copy preloder on nintendo swich and launch it via hekato. There are many videos on the launch.

SDIO · Mar 23, 2023

Hi @Serjio193 thanks for sharing this with us, and I am glad you got your console working again.

But I see some potential problems and would prefer a more targeted approach.
Imagine what would happen if the emmc goes read only in the middle of the installation of a wup. If the title is necessary for udpih to work, you might have locked yourself out. And it would be a real shame if that title wasn't even broken in the first place. As we don't have the tools to have proper write access and the slc cache might come in the way this then wouldn't even be fixable with soldering, without a NAND Backup. At the moment we don't have a tool to dump the NAND in the recovery menu (but soon we have) so I can't complain about not doing a backup before.
Another way it could go wrong, would be that the file system metadata is corrupted and cause the install to fail.
And you are right that the expected failure mode of the eMMC is to become read only, but with the retention problem of the Hynix chips even the FTL could become corrupt and cause other failure modes of the chip. At the moment we are discussing a case in discord where it seems that the eMMC failed completely and is not even readable anymore.

So I would would rather first dump the logs, there we can see if there are MEDIA ERRORS, which would mean the eMMC is bad and should be swapped ASAP before the filesystem corrupts more. When I had this problem because of a bad Hynix it just got worse with everything I tried to reinstall and I was lucky to have a backup. If it says DATA CORRUPTION ERROR it could be a bad eMMC but also just a power outage in the wrong moment. In most cases the log would tell you which file is corrupted (yours didn't unfortunately https://gbatemp.net/threads/offline...access-recovery-menu-0-4.621991/post-10108569 so I also can't really blame you for going for the shotgun approch). If the log tells the corrupted file it would be much safer to use wup server to first upload the replacement file and then move it over the corrupted file. So the operation would be as atomic as possible and the window for a fatal error as small as possible.

And I am not saying you did anything wrong, you got your console working after all, and the logs weren't that helpful in your case, but other people might have another problem with the same symptom and a more targeted approach would be safer.

riders556 · Mar 25, 2023

bonjour nous devons tout installer les fichiers

Fixing error 160-0103

Member

Attachments

Well-Known Member

Member

Active Member

Member

Well-Known Member

Member

Similar threads

Popular threads in this forum