Wii U bricked, UDPIH white screen

CeeDee · Feb 9, 2024

Hey all, I have a Wii U that's bricked/nonfunctional and alas, I'm nowhere near smart enough to figure out the why. I've tried UDPIH with the recovery_menu, but the regular one doesn't show anything and recovery_menu_dc_init shows a white screen with bluish stripes instead of a menu. I've blindly navigated to try and set the coldboot title to the US Wii U menu, which hasn't helped, but I was able to dump a log. Throwing it into a spoiler below:

2016-06-20 13:17:26
Cafe OS SDK Version 2.13.01 Build 68939 Branch sdk_2_13
Espresso: 0x0000700100000201
Latte: 0x0000409f
System mode: 0x80000
Boot flags: 0x4220000
Security Level: 0x1e
Key Type: 0xfffffffc
Prod Version: 0x5
Serial: 400923480
Model: WUP-101(02)
Prod Area: 0x2
Game Area: 0x2
5GHz Code: 0x7
BT: 0x205
BOOT1: 0x20b9
DRH: 0x190c
+0x0005001010066000:0x00000014

----------- Starting System Log -----------
00:00:00:592: AHCI_MGR Trace: This platform does not require SATA in ECO mode.
00:00:00:598: TEST Info: crossProcessHeap OK.
00:00:00:601: AUXIL Info: crossProcessHeap OK.
00:00:00:603: AUXIL Info: Net OK.
00:00:00:870: ISFS: FAT INFO (ch WUP): slot 36 / seq 756006 (Each FAT slot has been updated 11812 times in avr)
00:00:00:871: FSA: [uptime 0.871 s]: Attached volume to slc01 (isfs): Capacity 511 MB, 262016 logical blocks of size 2048 B.
00:00:01:060: ISFS: FAT INFO (ch RVL Compat): slot 12 / seq 176718 (Each FAT slot has been updated 11044 times in avr)
00:00:01:061: FSA: [uptime 1.061 s]: Attached volume to slccmpt01 (isfs): Capacity 511 MB, 261632 logical blocks of size 2048 B.
00:00:01:072: SCFM:Start init. BUILD_TIME:[19:23:46]
00:00:01:084: SCFM:FSAInit
00:00:01:084: SCFM:AddClient
00:00:01:086: SCFM:scfmMountSlc
00:00:01:087: SCFM:scfmLoad
00:00:01:087: SCFMone init.
00:00:01:089: PCFS: Disabled because we are in PROD mode.
00:00:01:090: MCP: booting from NAND
00:00:01:091: MCP: Boot PM flags - PON_SMC PON_SMC_TIMER DDR_SREFRESH
00:00:01:091: MCP: System is in ECO Mode
00:00:01:149: MCP: Cafe OS SDK Version 2.13.01 Build 68939 Branch sdk_2_13
00:00:01:149: MCP: Booting on Espresso (0x0000700100000201), Latte (0x25100028), RTC (0x01)
00:00:01:149: MCP: Platform - boardType(CF), boardRevision(11), devicePresence(0x00000000), sataDevice(3), consoleType(1)
00:00:01:156: ISFS: FAT block entries check start
00:00:01:170: ISFS: FAT block entries check finished.
00:00:01:196: FSA: [uptime 1.196 s]: Attached volume to ramdisk01 (wfs): Capacity 127 MB, 131070 logical blocks of size 1024 B.
00:00:01:231: FSA: [uptime 1.231 s]: Attached volume to mlc01 (wfs): Capacity 29760 MB, 60948480 logical blocks of size 512 B.
00:00:01:360: ISFS: FAT block entries check start
00:00:01:373: ISFS: FAT block entries check finished.
00:00:01:588: MCP: File loading from ramdisk cache is enabled
00:00:01:604: MCP: Master title 0005001010066000 os 000500101000400a from mlc01 flags 0004
00:00:01:663: MCP: os version 10 NDEBUG (0x000500101000400a)
00:00:01:666: MCP: FSA volume on device /dev/mlc01 (wfs) attached @ uptime 1.666 s.
00:00:01:702: MCP: found master title 5001010066000 on mlc01 at 1.702 s
00:00:01:709: MCP: FSA volume on device /dev/ramdisk01 (wfs) attached @ uptime 1.709 s.
00:00:01:710: MCP: Titles scanned (dev_state 0006) on device /dev/ramdisk01 (wfs) @ uptime 1.710 s.
00:00:01:711: MCP: FSA volume on device /dev/slc01 (isfs) attached @ uptime 1.711 s.
00:00:01:712: MCP: FSA volume on device /dev/slccmpt01 (isfs) attached @ uptime 1.712 s.
00:00:01:712: MCP: Titles scanned (dev_state 0006) on device /dev/slccmpt01 (isfs) @ uptime 1.712 s.
00:00:01:713: MCP: Titles scanned (dev_state 0004) on device /dev/mlc01 (wfs) @ uptime 1.713 s.
00:00:01:716: MCP: Titles scanned (dev_state 000e) on device /dev/slc01 (isfs) @ uptime 1.716 s.
00:00:02:114: ISFS: fs_ops.c(3733)Can not change the owner Id of a non-empty file
00:00:02:114: ISFS: fs_ops.c(6719)Could not set attribute, rc=-524312
00:00:02:195: MCP: Titles scanned (dev_state 000c) on device /dev/mlc01 (wfs) @ uptime 2.195 s.
00:00:02:197: MCP: Titles scanned (dev_state 0006) on device /dev/mlc01 (wfs) @ uptime 2.197 s.
00:00:02:770: MCP: ECO mode is enabled
00:00:02:770: [+-* DK is ready for console input *-+]
00:00:02:770: MCP: syslog mask is set to 0xffffffff
00:00:02:782: USB Trace: Device hierarchy retrieved from SLC (4).
00:00:02:784: USB Trace: Activating root hubs @ uptime 2.784 s with options 0xc0000.
00:00:02:815: UHS0 Trace: DevFsm(EHCI-0/L0/P0): Creating device, speed=HIGH.
00:00:02:821: UHS0 Trace: DevFsm(OHCI-0:0/L0/P0): Creating device, speed=FULL.
00:00:02:821: USB Info: UhsServerAddHc 0 OK.
00:00:02:850: UHS0 Trace: DevFsm(EHCI-1/L0/P0): Creating device, speed=HIGH.
00:00:02:855: UHS0 Trace: DevFsm(OHCI-1:0/L0/P0): Creating device, speed=FULL.
00:00:02:856: USB Info: UhsServerAddHc 1 OK.
00:00:02:874: W2C: Does not need W2C-reflection
00:00:03:464: UHS1 Trace: DevFsm(EHCI-2/L0/P0): Creating device, speed=HIGH.
00:00:03:469: UHS1 Trace: DevFsm(OHCI-2:0/L0/P0): Creating device, speed=FULL.
00:00:03:470: CCR_MAIN: activating root hub.
00:00:03:783: UHS1 Trace: DevFsm(EHCI-2/L1/P1): Creating device, speed=HIGH.
00:00:03:784: UHS1 Trace: DevFsm: There are now a total of 1 connected devices.
00:00:03:821: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 3.821 s.
00:00:03:822: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 3.822 s.
00:00:03:823: UHS1 Trace: CltIfFsm(V057e|P0341|IF2): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 3.822 s.
00:00:03:823: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 3.823 s.
00:00:03:824: UHS1 Trace: CltIfFsm(V057e|P0341|IF4): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 3.824 s.
00:00:03:825: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 3.825 s.
00:00:03:825: UHS1 Trace: CltIfFsm(V057e|P0341|IF6): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 3.825 s.
00:00:03:826: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 3.826 s.
00:00:03:826: UHS1 Trace: CltIfFsm(V057e|P0341|IF8): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 3.826 s.
00:00:03:827: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 3.827 s.
00:00:03:828: UHS1 Trace: CltIfFsm(V057e|P0341|IF10): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 3.827 s.
00:00:03:828: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 3.828 s.
00:00:03:829: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Acquired by client in pid 6.
00:00:03:829: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Enable endpoints 0x00080000.
00:00:03:915: __ccr_hid_attach_add_interface: idx 0 ep 3
00:00:03:916: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Acquired by client in pid 6.
00:00:03:916: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Enable endpoints 0x00100000.
00:00:04:002: __ccr_hid_attach_add_interface: idx 1 ep 4
00:00:04:004: UHS1 Trace: CltIfFsm(V057e|P0341|IF2): Acquired by client in pid 6.
00:00:04:004: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Acquired by client in pid 6.
00:00:04:005: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Activating bAlternateSetting 0.
00:00:04:009: UHS1 Trace: CltIfFsm(V057e|P0341|IF4): Acquired by client in pid 6.
00:00:04:010: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Acquired by client in pid 6.
00:00:04:011: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Activating bAlternateSetting 0.
00:00:04:014: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Acquired by client in pid 6.
00:00:04:014: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Enable endpoints 0x08001000.
00:00:04:016: UHS1 Trace: CltIfFsm(V057e|P0341|IF8): Acquired by client in pid 6.
00:00:04:017: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Acquired by client in pid 6.
00:00:04:018: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Activating bAlternateSetting 0.
00:00:04:022: UHS1 Trace: CltIfFsm(V057e|P0341|IF10): Acquired by client in pid 6.
00:00:04:023: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Acquired by client in pid 6.
00:00:04:024: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Activating bAlternateSetting 0.
00:00:04:027: DRH chip revision 00000040
00:00:04:027: DRH firmware version 190c0117
00:00:04:027: DRH cdc version 00080000
00:00:04:028: DRH wifi module id a8e502d0
00:00:04:028: DRH SPL id 00001c58
00:00:04:267: MCP: boot1 version 2.11.09
00:00:04:285: MCP: loaded and parsed 'preload.txt' at '/vol/system/title/00050010/1000400a/code'
00:00:04:302: MCP: Wake 0 signal
00:00:04:362: NET: Applied interface MTU (wl0:1400 eth0:1400).
00:00:04:393: USBETH Trace: Created interface 100.
00;00;04;225: COSREPORT: Set level:1 from syslog level
00;00;04;225:
----------------------------------------------- BPERF: (0/4226095) PPC Init.
00;00;04;225: Cafe OS SDK Version 2.13.01 Build 68939 Branch sdk_2_13
00;00;04;225: PPC NDEBUG Kernel Build date - Jul 28 2015 19:55:58
00;00;04;225: BUILT AS OS_VERSION_MAJOR 000500101000800A MINOR 0x3D56
00;00;04;225: core=1 WARM BOOT
00;00;04;225: SOFT INTERRUPT MODE
00;00;04;225: PPC KERNEL IN ECO MODE
00;00;04;225: -----------------------------------------------

00;00;04;256: KiCblRegisterBlocks() completed with status 0:-4.
00:00:04:552: DRH using runtime generated WLAN data
00:00:04:552: Setting DRH to ECO mode
00:00:04:557: setting DRH system time to 13:17:29
00:00:04:559: NOT sending WoWL wake for DRC for PM_ECO
00:00:05:069: ACT: Current account is #1.
00;00;04;305: PROD Mode - don't even try to load kdebug.elf
00;00;04;310: title id: 5001010066000, app type 9000002f
00;00;04;310:
00;00;04;310: ---------------------------------------
00;00;04;310: OS VERSION ID 0x000500101000400A
00;00;04;311: MASTER TITLE ON FLASH
00;00;04;311: ---------------------------------------
00;00;04;311:
00;00;04;764: DIAG:+KiRPLLoaderSetup
00;00;04;764: DIAG:-KiRPLLoaderSetup: before no-return call to KiLoadContext (0xEFE09400) (0x01003FFC)
00:00:05:689: MCP: Heartbeat Enabled
00;00;05;446: DIAG:+KiProcess_FinishInitAndPreload
00;00;05;446: KiCblRegisterBlocks() completed with status 0:-4.
00;00;05;446: DIAG:-KiProcess_FinishInitAndPreload: before no-return call to KiInitKernelFinish
00;00;05;446: DIAG:+KiInitKernelFinish
00;00;05;447: VVVVVVV----- PPC Kernel Waiting -----VVVVVVV
00;00;05;447: ^^^^^^^----- PPC Kernel Release -----^^^^^^^
00;00;05;447: DIAG:-KiInitKernelFinish: before no-return call to KiProcess_Launch
00;00;05;447:
--------------------
00:00:05:769: NET: Change admin state (2 -> 1)(iface:0 link:2)
00:00:05:769: [WD]>>>> Linkup msg from Net
00:00:05:809: wlc_mlme_join_cmd called with Command 0x3 Length 0x21
00:00:05:814: NET: Change admin state (0 -> 2)(iface:1 link:2)
00:00:05:814: IFNET_ETH: Configuring link adminState to DOWN.
00:00:05:816: NET: Change admin state (1 -> 1)(iface:0 link:3)
00;00;05;447: PROCESS 1 STARTING
00;00;05;448: SYSLOG_LEVEL 1: Warnings Enabled
00;00;05;448: UserMode Core & Thread Initialization (3 Cores)
00;00;05;448: Core 1 Complete, Default Thread 0x100457E0
00;00;05;450: Core 0 Complete, MSR 0x00005072, Default Thread 0x10045140
00;00;05;451: Core 2 Complete, MSR 0x00005072, Default Thread 0x10045E80
00;00;05;451: Clearing Process MEM2 Arena...
00;00;05;478: MEM2 Arena clear complete, size 23 MB, 26ms
00;00;05;523: UserMode OS library build date: Jul 28 2015 19:57:03
00;00;05;523: __AppFlags: 0x00000200

00;00;05;524: OSBlockThreadsOnExit default for sdk version 21301
00;00;05;653: OSSetting_SynchronousPrinting DISABLED
00:00:05:928: [WD]>>>> Linkup msg from Net
00:00:05:944: wlc_mlme_join_cmd called with Command 0x3 Length 0x21
00;00;05;680: OSSetting_CrashDumpType 0, MINI dump after crash
00;00;05;721: VPAD Init end, BPERF: (0/5964363) Title PID=1
00;00;05;736: ROOT: Read restart value 0
00;00;05;738: ROOT: Read audio relaunch value 0
00;00;05;739: ROOT: OSID 0x000500101000400A
00;00;05;739: DMARamClear_OnBoot RAMPID_HomeButtonMenu
00;00;05;874: DMARamClear_OnBoot RAMPID_Error
00;00;05;891: DMARamClear_OnBoot RAMPID_Overlay
00;00;06;363: DMARamClear_OnBoot RAMPID_Master
00;00;07;443: Info: Calculating warm boot font CRCs on core:0
COSREPORT: Using syslog level:1
COSREPORT: Set upid_mask:ffffffffffffffff module_mask:ffffffffffffffff level:1
00;00;07;741: Info: Warm boot processing font CRCs on core:1
00;00;07;932:

-----------------------------
ROOT IS STARTING MASTER TITLE
-----------------------------

00;00;07;933: TEST COOKIE: YOSHI-1992-11-21-00-00-00
00;00;07;935: DIAG:Issued KiPrepareTitleAsync(0x0005001010066000)
00:00:08:885: MCP: did not find 'preload.txt' at '/vol/storage_mlc01/sys/title/00050010/10066000/code', rval -196631
00:00:08:886: MCP: Preparing eco_process.rpx
00:00:08:895: MCP: Mapping /vol/content to /vol/storage_mlc01/sys/title/00050010/10066000/content
00:00:08:897: MCP: 0005001010066000 is not a demo title, skip increment demo launch count
00:00:08:897: MCP: Mapping /vol/content to /vol/storage_mlc01/sys/title/00050010/10066000/content
00;00;08;647: DIAG:Result PrepareTitle(0x0005001010066000) came back with cosxml(0x0005001010066000)
00;00;08;658: TitleId 0x0005001010066000 Version 0x00000014 Built On SDK 21204
00;00;08;745: ------------------PROCESS 1 LOST FOREGROUND--------------------
00;00;08;745: DIAG: PhysAlloc(15, 0x40000000, 0x00000000, 0x00000000, 0x0E000000, 0x00000001)
00;00;08;745: DIAG: InitAddrSpace
00;00;08;747: DIAG: Switch(New)
00;00;08;747: DIAG:+Loader(1, 7)
00;00;08;747: DIAG:+KiRPLLoaderSetup
00;00;08;747: DIAG:-KiRPLLoaderSetup: before no-return call to KiLoadContext (0xEFE09400) (0x01003FFC)
00;00;08;747: Title Loc is 0
00;00;08;803: DIAG:-Loader(1, 7)
00;00;08;804: DIAG: SetFG(7)
00;00;08;804: KiCblRegisterBlocks() completed with status 0:-4.
00;00;08;804: ------------------PROCESS 15 GAIN FOREGROUND--------------------
00;00;08;807: SYSLOG_LEVEL 1: Warnings Enabled
00;00;08;807: UserMode Core & Thread Initialization (3 Cores)
00;00;08;807: Core 1 Complete, Default Thread 0x100457E0
00;00;08;809: Core 0 Complete, MSR 0x00005072, Default Thread 0x10045140
00;00;08;811: Core 2 Complete, MSR 0x00005072, Default Thread 0x10045E80
00;00;08;856: UserMode OS library build date: Jul 28 2015 19:57:03
00;00;08;856: __AppFlags: 0x00000200

00;00;08;857: OSBlockThreadsOnExit default for sdk version 21204
00;00;09;870: SYSAPP: RPL Load
00;00;09;916: OSSetting_SynchronousPrinting DISABLED
SPM: SetManualMode
00:00:10:458: ACP: Mounting "/vol/save/" on "/vol/storage_mlc01/usr/save/00050010/10066000/user/"
00:00:10:459: ACP: Mount done (0)
00;00;09;928: OSSetting_CrashDumpType 0, MINI dump after crash
00;00;09;931: VPAD Init end, BPERF: (0/10174256) Title PID=15
00;00;09;931: ACP_AutoInit: start
00;00;10;182: ACP_AutoInit: ACPInitialize complete
00;00;10;182: ACP_AutoInit: ACPSaveDataInit complete
00;00;10;190: ACP_AutoInit: ACPNotifyPlayEvent complete
00;00;10;196: ACP_AutoInit: NDMInitialize complete
00;00;10;198: ACP: initialized
00:00:10:815: IFNET_ETH: Link DOWN.
00:00:12:804: Acquired IP address via DHCP client for interface: wl0
00:00:12:805: IP address : 10.0.0.8
00:00:12:805: Subnet Mask: 255.255.255.0
00:00:12:805: Gateway : 10.0.0.1
00:00:15:980: [BOSS] BG stress mode is disabled.
SPM: SetManualMode
00:00:18:382: ACP: USB storage is not found
00:00:18:882: ACP: Mounting "/vol/save/" on "/vol/storage_mlc01/usr/save/00050010/10066000/user/"
00:00:18:883: ACP: Mount done (0)
00:00:18:940: ACP: "find USB" flag is false.
00;00;18;926: ACP shim: USB storage is not found.
Result (a1883480)
Level: ( -3) LEVEL_STATUS
Module: ( 24) RESULT_MODULE_NN_SL
Description: (537728) CCRSYS_RESULT_UNKNOWN
Result (a1944d80)
Level: ( -3) LEVEL_STATUS
Module: ( 25) RESULT_MODULE_NN_ECO
Description: (281984) undefined
[ECO]: P: 48, R: a1883500
[ECO]: P: 58, R: a1883500
[ECOP]: Process, a1883500
00;01;40;043: CSC: Repaired: FALSE, Wagon: FALSE
00;01;40;054: CSC: InitialLaunch stage: 2
00;01;40;101: CSC: RCA Enabled: FALSE, KeepAlive Enabled: FALSE, ParentControl Enable: FALSE
00;01;40;102: CSC: Check : /vol/storage_mlc01/usr/boss/00000000/00000000/user/common/ (-196609)
00;01;40;102: CSC: Check : /vol/storage_mlc01/usr/boss/00000000/00000000/user/80000001/ (-196609)
00;01;40;102: CSC: Check : /vol/storage_usb01/usr/boss/00000000/00000000/user/common/ (-196609)
00;01;40;102: CSC: Check : /vol/storage_usb01/usr/boss/00000000/00000000/user/80000001/ (-196609)
00;01;40;102: CSC: Check : /vol/storage_usb02/usr/boss/00000000/00000000/user/common/ (-196609)
00;01;40;102: CSC: Check : /vol/storage_usb02/usr/boss/00000000/00000000/user/80000001/ (-196609)
00;01;40;104: CSC: Boss Storage Exist: FALSE, NetworkID Assigned: TRUE, System Network Connected: TRUE
00;01;40;179: CSC: NIC Type: WIFI, DNS obtained by DHCP: TRUE, IP obtained by DHCP: TRUE
00;01;40;192: CSC: TV Port: COMPOSITE, TV Aspect Ratio: 16:9
2016-06-20 13:19:05 - log collection event from pid 21
00;01;40;205: CSC: TV Resolution: TV_480I
00;01;40;205: CSC: CODE: [XXXX-02X0-3350]
00:01:40:457: MCP: life time number of fatal errors - 5298

If anyone has any insight as to what's causing the system to not boot or whether it's easily fixable, I'd appreciate it a ton. Thanks!

SDIO · Feb 9, 2024

please send the whole log folder as a zip.

V10lator · Feb 10, 2024

SDIO said:
please send the whole log folder as a zip.

^- This. The log file with the highest number isn't always the latest. We need the whole log folder to see which one is the last log. The log you (@CeeDee) showed is from 2016, the Wii U was connected to a CRT screen back then, outputting a 480i image... Not helping at all when we look for a issue which happened 8 years later.

CeeDee · Feb 10, 2024

SDIO said:
please send the whole log folder as a zip.

V10lator said:
^- This. The log file with the highest number isn't always the latest. We need the whole log folder to see which one is the last log. The log you (@CeeDee) showed is from 2016, the Wii U was connected to a CRT screen back then, outputting a 480i image... Not helping at all when we look for a issue which happened 8 years later.

My bad, as I said I am clueless and just assumed the 2016 date meant the system's internal clock might be off.

ZIP attached.

V10lator · Feb 10, 2024

Thanks @CeeDee

In case you're curious I'll outline the steps I'm doing now to get the latest log file: Open the meta.bin file with a hex editor. We see 0x000014CD as content. So let's go to https://www.rapidtables.com/convert/number/hex-to-decimal.html and enter that there: It shows 5325. So this Wii U produced 5325 log files in total. Whenever it reaches 99 it wraps back to 0 through so you have a max of 100 log files. To get the latest we need to take that number and do a modulo 100 calculation to it. To make this way more simple: Just use the last two numbers and ignore the rest. This gives us 25, so the latest log file should be 25.log. Let's look into that.

Inside of this log file we see a lot of DATA_CORRUPTION errors, which is exactly what we expect to see. No MEDIA_ERRORs through. Sp I search all logs for MEDIA_ERROR:

Code:

grep -r MEDIA_ERROR .

Doesn't find anything through.

So the final result of analysing is: There are corruptions on the MLC (eMMC) but we don't know why. It could have been caused by a brownout, for example, but seeing what files corrupted I think it's a dying Hynix eMMC.

Your best bet now would be to open the console and look what's written on the eMMC chip: Is it Hynix? If so you probably need to replace it (NAND-AID or redNAND via ISFSHax). If it's not Hynix we might be able to repair it in software through but yea, looking at the corrupted files I think it's unlikely that this is just a software issue.

//EDIT: The reason the recovery menu is blackscreening is btw that the fonts on your system corrupted. Corrupted fonts are a typical sign of a dying Hynix eMMC, like we see them in around 90% of cases...

//EDIT²: Also I see corrupted certificates on your system. It seems to be mostly read-only data which corrupted, so a brownout while writing beeing the cause is highly unlikely and again: Read-only data corrupting is a sign of a bad Hynix eMMC.

//EDIT³: @GaryOderNichts for cases like this it would be nice to have a way to dump the system information to SD. So people with corrupted fonts (recovery menu blackscreening) don't have to open the console to see what eMMC chip is inside.

SDIO · Feb 10, 2024

I would suggest you install ISFShax to have a backup plan.
Then would be the question: do you care for the data on the console?
After ISFShax is installed I could add an option to minute to show the eMMC CID.
With ISFShax installed we can also take the risk of reinstalling the fonts, so the recovery menu shows something

CeeDee · Feb 10, 2024

SDIO said:
I would suggest you install ISFShax to have a backup plan.
Then would be the question: do you care for the data on the console?
After ISFShax is installed I could add an option to minute to show the eMMC CID.
With ISFShax installed we can also take the risk of reinstalling the fonts, so the recovery menu shows something

Yup, I've got ISFShax installed now. Planning on going the rednand route if the eMMC is dying, just waiting for the high-endurance SD I ordered to get here.
I got the system in that state and it's been sitting around as a paperweight for about a year now, so I don't give a damn about whatever data's currently on it, anything to get it back to a working state would be a win for me.

SDIO · Feb 10, 2024

Do you have a 64gb sdcard? If so you could use my fork if the recovery to dump the mlc. The log from that would also give use an idea what state the mlc is in.

CeeDee · Feb 10, 2024

SDIO said:
Do you have a 64gb sdcard? If so you could use my fork if the recovery to dump the mlc. The log from that would also give use an idea what state the mlc is in.

I sure do, feel free to point me in the right direction for that and I'll dump the mlc

SDIO · Feb 10, 2024

If you use the recovery you used for installing ISFShax, it has the mlc dump as the first option. You just have to put it on the fat 32 formatted 64 GB card. Use UDPIH again to load it and then just press power once and then wait

CeeDee · Feb 13, 2024

SDIO said:
If you use the recovery you used for installing ISFShax, it has the mlc dump as the first option. You just have to put it on the fat 32 formatted 64 GB card. Use UDPIH again to load it and then just press power once and then wait

Trying to do this now, and I'm probably missing something obvious here, but I'm inserting the raspi USB at the same time I had before, and minute loads. Should I use minute to 'Patch (sd) and boot IOS (slc)' and then insert the USB?

SDIO · Feb 13, 2024

Yes you need to boot, because UDPIH is exploiting IOSU. So IOSU needs to be running. In minute USB isn't even powered on

CeeDee · Feb 13, 2024

SDIO said:
Yes you need to boot, because UDPIH is exploiting IOSU. So IOSU needs to be running. In minute USB isn't even powered on

Is there any visual indication (power LED) if the dump is finished? I'm booting IOS, inserting the USB, pressing power, and I haven't seen any new dumps show up on the SD.

SDIO · Feb 13, 2024

It should blink the led while it is dumping

CeeDee · Feb 14, 2024

SDIO said:
It should blink the led while it is dumping

Would it be easier to do if I set minute to autoboot? I've been trying to do it several times now and haven't been able to. Makes me feel like I'm probably missing something really obvious, thanks for your patience though!

Wii U bricked, UDPIH white screen

fuckin dork

Well-Known Member

Well-Known Member

fuckin dork

Attachments

Well-Known Member

Well-Known Member

fuckin dork

Well-Known Member

fuckin dork

Well-Known Member

fuckin dork

Well-Known Member

fuckin dork

Well-Known Member

fuckin dork

Similar threads

Popular threads in this forum