Any games with 5.5.3/5.5.4 firmware?

[Toscanelli]

Hi,

after years I digged out my 5.5.2 Wii U and when I launch the web browser the error "160-1710" occurs. After some research I'd like to try updating the firmware, but not to the latest version 5.5.5 to have some headroom. Are there games that contain firmware 5.5.3 or 5.5.4 for an offline update?

 

[godreborn]

not that I know of. there's no reason not to update. I tested everything, and everything works.

 

[godreborn]

btw, updates for games come in the sys folder iirc, beside the code, content, and meta folders. you'd only have that issue with disc games. online games don't contain the folder, since it's assumed you're on the latest.

 

[Toscanelli]

Unfortunately the update process fails with error 160-0103

 

[godreborn]

says that means the system memory is corrupt. not sure how to fix that. is the update folder deleted?

 

[Toscanelli]

I don't know. It's been too long. I now tried "Delete All Content and Settings" but the browser or system update still doesn't work after Wii U setup. From my nand backup I could only find otp.bin and seeprom.bin.

mlc.full.img, slc.full.img and slccmpt.full.img are missing.

I think it's gone :/

 

[godreborn]

you only need the otp.bin to fix the mlc, but you'll need whatever files are corrupted, which could be anything.

 

[Toscanelli]

I guess the fixing process would somehow look like this?

1. hardmod MLC dump
2. decrypt with OTP.bin
3. ???
4. encrypt with OPT.bin
5. flash modified MLC

 

[godreborn]

yes

 

[flowlapache]

before you can check with ftpiiu if the folder "update" has been deleted. it was a tips to avoid system update

 

[Toscanelli]

Thanks for the suggestion. I used Mocha which requires a working web browser. Since the browser refuses to start I can't access Homebrew Launcher to run FTPiiU.

 

[godreborn]

I've got an idea. try using bluUbomb. I've never used it, but I don't think you need to use the browser to get into the homebrew launcher.

edit: yep, don't need a working browser: https://gbatemp.net/threads/bluubomb-a-primary-wii-u-entrypoint-via-bluetooth.588522/

 

[Toscanelli]

I didn't know there was a new exploit method. BluuBomb looks very promising for my case. Glad you came up with this

 

[godreborn]

it's not my exploit, @GaryOderNichts created it, just thought of the only way I know of to get into the homebrew launcher, hopefully, without needing the browser or some form of haxchi.

 

[godreborn]

btw, if this works, you may be able to fix your browser if you have a backup of the mlc and use wfs-extract on it. I think there might also be a nus thing of some sort for the wii u to download system title updates to decrypt, then replace files.

 

[CMDreamer]

Sorry to get into this thread out of nowhere. The mention of the 160-0103 error turned on my brain.

I've got a Wii U (second hand) that goes through the first setup process up to the point of language selection but then comes to that same error message, and I can't do anything afterwards but restart the console up to the same error message in an endless loop.

Does someone know how can I go into fixing this? I don't have a NAND backup, because I've got the Wii U as it is right now.

Thanks in advance.

 

[godreborn]

afaik, bluUbomb only works if you can connect the gamepad (not sure about wiimote), but if you can't connect anything yet, then I don't think it's going to work. no idea how to fix this problem.

 

[Toscanelli]

Does someone know how can I go into fixing this?

I finally found time to further investigate the issue. According to the crash log files in "storage_slc/logs" it's most likely the MLC that has gone bad. The Wii U tries to read a Internet Browser related file but fails and gives a fatal error. Replacing or deleting this file does not work. This indicates a bad memory block. Unfortunately I don't think there is way to tell the system "don't use that block". I likely have to replace the NAND chip.

 

[CMDreamer]

I finally found time to further investigate the issue. According to the crash log files in "storage_slc/logs" it's most likely the MLC that has gone bad. The Wii U tries to read a Internet Browser related file but fails and gives a fatal error. Replacing or deleting this file does not work. This indicates a bad memory block. Unfortunately I don't think there is way to tell the system "don't use that block". I likely have to replace the NAND chip.

But replacing the NAND chip would be only usefull, if and only if, you've had a NAND backup, right?

Sadly in my case, I've got no NAND backup, so I'll have to wait that some solution comes to light.

 

[KleinesSinchen]

But replacing the NAND chip would be only usefull, if and only if, you've had a NAND backup, right?

Sadly in my case, I've got no NAND backup, so I'll have to wait that some solution comes to light.

NAND image should be possible for OP; minus the bad block(s). It is worth a try. Of course it won't work when the OS doesn't fully start like in your case. I see no real solution unless somebody finds a usable exploit at boot time or a signed SD boot image appears.
=====

The OTP is theoretically enough. If one has the possibility the replace the NAND, it should be done because:

a) It is cool to do something like that.​

b) "Just replace the console! It is cheaper and easier." is not a solution in the long run with the limited number of Wii U.​

​

Partially off-topic: Has anybody tried to replace the NAND with a larger version? Would it be possible to have a 256GB NAND and install games internally? I mean there are the 8GB and the 32GB version… so the OS is kind of flexible in this regard.

I finally found time to further investigate the issue. According to the crash log files in "storage_slc/logs" it's most likely the MLC that has gone bad. The Wii U tries to read a Internet Browser related file but fails and gives a fatal error. Replacing or deleting this file does not work. This indicates a bad memory block. Unfortunately I don't think there is way to tell the system "don't use that block". I likely have to replace the NAND chip.

Try to backup now (if no backup exists). Maybe the NAND goes all bad.