Tzirf

Console & Retro Gaming => Nintendo Consoles & Handhelds => Topic started by: nitgundo on Jul 06, 2025, 07:03 PM

Title: After Defuse I get a blinking orange light
Post by: nitgundo on Jul 06, 2025, 07:03 PM
I must have done something wrong, because, after defuse. I just get a blinking orange light. I desoldered the pico with defuse on it.
Title: Re: Defuse solder/wire question
Post by: tzirf on Jul 06, 2025, 08:34 PM
I would need more information. Are you saying after installing defuse you just got a blinking orange light or after using defuse to rebuild the MLC?
Title: Re: After Defuse I get a blinking orange light
Post by: nitgundo on Jul 06, 2025, 08:50 PM
I started defuse, and kept getting errors. When using putty. I thought it was a loose wire, and rechecked my connections. I used defuse again, and the errors persisted. I de soldered the pico and tried hax. I used a new pico, and now I can't get recover menu. I only get orange led blinking. I'm going to try defuse again, and see if I can get anything useful, from WiiU,
Title: Re: After Defuse I get a blinking orange light
Post by: tzirf on Jul 07, 2025, 10:01 AM
Quote from: nitgundo on Jul 06, 2025, 08:50 PMI started defuse, and kept getting errors. When using putty. I thought it was a loose wire, and rechecked my connections. I used defuse again, and the errors persisted. I de soldered the pico and tried hax. I used a new pico, and now I can't get recover menu. I only get orange led blinking. I'm going to try defuse again, and see if I can get anything useful, from WiiU,

Orange LED blinking usually means the SD Card that holds ISFShax is missing. Did you previously install ISFShax before installing defuse?

Also it doesn't sound like the Wii U ever defused properly. If it did you would see on screen or via putty the following and the minute menu would load...

Starting... 3224:0
Results:
Winner! 0xf368
01
02
03
04
05
08
09
0a
0b
0c
0d
0e
13
14
15
18
1b
1c
1d
1e
1f
25
88
89
8a
0f
8f
0f
00
80
01
81
00
80
01
81
00
80
01
81
00
80
01
81
0f
8f
0f
00
01
81
00
80
01
81
00
80
01
81
00
80
01
81
00
80
0f
8f
0f
00
80
01
81
00
80
01
81
00
80
01
81
00
80
01
81
0f
8f
0f
00
01
81
00
80
01
81
00
80
01
81
00
80
01
81
00
80
0f
8f
0f
00
80
01
81
00
80
01
81
00
80
01
81
00
80
01
81
0f
8f
0f
00
01
81
00
80
01
81
00
80
01
81
00
80
81
01
81
00
80
0f
8f
0f
00
80
01
81
00
80
01
81
00
80
01
81
00
80
01
81
0f
8f
0f
00
01
81
00
80
01
81
00
80
01
81
00
80
01
81
00
80
0f
8f
0f
00
80
01
81
00
80
01
81
00
80
01
81
00
80
01
81
0f
8f
0f
00
01
81
00
80
01
81
00
80
01
81
00
80
01
81
00
80
0f
8f
0f
00
80
01
81
00
80
01
81
00
80
01
81
00
80
01
81
0f
8f
0f
00
01
81
00
80
01
81
00
80
01
81
00
80
[pico] Changed state: WIIU_STATE_NEEDS_DEFUSE -> WIIU_STATE_DEFUSED
[pico] Changed state: WIIU_STATE_DEFUSED -> WIIU_STATE_MONITORING
Title: Re: After Defuse I get a blinking orange light
Post by: nitgundo on Jul 07, 2025, 05:32 PM
I don't know what I did. I was trying a NAND Aid setup. My eMMC has no media errors. Wii U was showing the Wii U logo, before I decided to run a NAND Aid. I wrote the sd card content directly to the Wii U Emmc. I now boot to minute without needing pico or sd card.
Title: Re: After Defuse I get a blinking orange light
Post by: nitgundo on Jul 07, 2025, 06:03 PM
Actually, I can boot minute from sd card. How do I resstore the Wii U eMMC? Thanx, for your time.
Title: Re: After Defuse I get a blinking orange light
Post by: tzirf on Jul 07, 2025, 07:49 PM
You installed a NAND-AID into a Wii U console even though the eMMC was working?

If the NAND-AID is correctly installed, you need to rebuild the MLC now. Follow this guide (https://gbatemp.net/threads/how-to-upgrading-rebuilding-wii-u-internal-memory-mlc.636309/) to do that.

You can also reference my video that shows how to rebuild the MLC. That starts at 25:09 in the video
Title: Re: After Defuse I get a blinking orange light
Post by: nitgundo on Jul 07, 2025, 08:26 PM
I didn't install a nand aid, but I guess I have to now. Thanx for your info.
Title: Re: After Defuse I get a blinking orange light
Post by: tzirf on Jul 07, 2025, 09:51 PM
No you don't have to install a NAND-AID. If the eMMC is working you can rebuild the MLC per the guide. Skip the section about installing the NAND-AID and just go to the rebuilding of the MLC.
Title: Re: After Defuse I get a blinking orange light
Post by: nitgundo on Jul 09, 2025, 07:23 PM
I did install ISFShax first. Then I tried defuse. I am not getting minute menu anymore with ISFShax. Do I need to get a NAND Aid? Is the Wii U recoverable?
Title: Re: After Defuse I get a blinking orange light
Post by: tzirf on Jul 09, 2025, 09:21 PM
Quote from: nitgundo on Jul 09, 2025, 07:23 PMI did install ISFShax first. Then I tried defuse. I am not getting minute menu anymore with ISFShax. Do I need to get a NAND Aid? Is the Wii U recoverable?

Dump the log files and upload them with your next post so they can be reviewed. The only reason to install a NAND-AID is if the eMMC is failing or has failed. 
Title: Re: After Defuse I get a blinking orange light
Post by: nitgundo on Jul 10, 2025, 06:37 PM
Sorry, to bother you again. The first time I did the restore, with hax. I never did get a blinking led. The led stayed purple the whole time.
Title: Re: After Defuse I get a blinking orange light
Post by: nitgundo on Jul 10, 2025, 07:57 PM
2012-01-03 22:24:54
Cafe OS SDK Version 2.13.01 Build 69088 Branch sdk_2_13
Espresso:       0x0000700100000201
Latte:          0x0000409f
System mode:    0x100000
Boot flags:     0x84210000
Security Level: 0x1e
Key Type:       0xfffffffc
Prod Version:   0x5
Serial:         710636308
Model:          WUP-101(02)
Prod Area:      0x2
Game Area:      0x2
5GHz Code:      0x7
BOOT1:          0x20b9
BT:             0x205
DRH:            0x190c
+0x000500301001110a:0x00000064





----------- Starting System Log -----------
00:00:00:244: USB Trace: Activating root hubs @ uptime 0.243 s with options 0x40000.
00:00:00:253: UHS0 Trace: DevFsm(EHCI-0/L0/P0): Creating device, speed=HIGH.
00:00:00:255: UHS0 Trace: DevFsm(OHCI-0:0/L0/P0): Creating device, speed=FULL.
00:00:00:255: USB Info: UhsServerAddHc 0 OK.
00:00:00:264: UHS0 Trace: DevFsm(EHCI-1/L0/P0): Creating device, speed=HIGH.
00:00:00:266: UHS0 Trace: DevFsm(OHCI-1:0/L0/P0): Creating device, speed=FULL.
00:00:00:266: USB Info: UhsServerAddHc 1 OK.
00:00:00:270: TEST Info: crossProcessHeap OK.
00:00:00:271: AUXIL Info: crossProcessHeap OK.
00:00:00:280: UHS0 Trace: Powering on root hub group 0.
00:00:00:294: UHS0 Trace: Powering on root hub group 1.
00:00:00:296: AHCI_MGR Trace: Turning on drive power.
00:00:00:300: AHCI_MGR Trace: Initializing phy.
00:00:00:300: AHCI_DRV Trace: Initiating cold open.
00:00:00:300: AHCI_DRV Trace: Resetting HBA.
00:00:00:305: AUXIL Info: Net OK.
00:00:00:351: AHCI_DRV Trace: HBA Reset OK.
00:00:00:351: AHCI_DRV Trace: link ready, speed is GEN 1.
00:00:00:412: ISFS: FAT INFO (ch WUP): slot 19 / seq 512149 (Each FAT slot has been updated 8002 times in avr)
00:00:00:412: FSA: [uptime 0.412 s]: Attached volume to slc01 (isfs): Capacity 511 MB, 262016 logical blocks of size 2048 B.
00:00:00:503: ISFS: FAT INFO (ch RVL Compat): slot 15 / seq 10945 (Each FAT slot has been updated 684 times in avr)
00:00:00:504: FSA: [uptime 0.503 s]: Attached volume to slccmpt01 (isfs): Capacity 511 MB, 261632 logical blocks of size 2048 B.
00:00:00:511: SCFM:Start init. BUILD_TIME:[16:02:03]
00:00:00:514: SCFM:FSAInit
00:00:00:514: SCFM:AddClient
00:00:00:515: SCFM:scfmMountSlc
00:00:00:515: SCFM:scfmLoad
00:00:00:515: SCFM:Done init.
00:00:00:516: PCFS: Disabled because we are in PROD mode.
00:00:00:517: MCP: booting from NAND
00:00:00:517: MCP: Boot PM flags - PON_COLDBOOT PON_POWER_BTN PON_SMC DDR_SREFRESH
00:00:00:535: MCP: Cafe OS SDK Version 2.13.01 Build 69088 Branch sdk_2_13
00:00:00:535: MCP: Booting on Espresso (0x0000700100000201), Latte (0x25100028), RTC (0x01)
00:00:00:535: MCP: Platform - boardType(CF), boardRevision(12), devicePresence(0x00000000), sataDevice(3), consoleType(1)
00:00:00:537: ISFS: FAT block entries check start
00:00:00:541: ISFS: FAT block entries check finished.
00:00:00:547: FSA: [uptime 0.547 s]: Attached volume to ramdisk01 (raw): Capacity 127 MB, 131070 logical blocks of size 1024 B.
00:00:00:552: MCP: Formatting Device ramdisk to wfs
00:00:00:695: FSA: [uptime 0.695 s]: Attached volume to ramdisk01 (wfs): Capacity 127 MB, 131070 logical blocks of size 1024 B.
00:00:00:696: MCP: Format Complete
00:00:00:724: FSA: [uptime 0.724 s]: Attached volume to mlc01 (wfs): Capacity 29760 MB, 60948480 logical blocks of size 512 B.
00:00:00:835: ISFS: FAT block entries check start
00:00:00:839: ISFS: FAT block entries check finished.
00:00:00:905: AHCI_DRV Trace: device ready.
00:00:00:905: AHCI_DRV Trace: port operational.
00:00:00:910: ODM: ODM: Successfully configured preload cache
00:00:00:962: MCP: File loading from ramdisk cache is enabled
00:00:00:970: MCP: life time number of fatal errors - 15
00:00:00:970: MCP: storing previous logs as '/vol/system/logs/16.log'
00:00:01:741: MCP: Finished storing previous logs as '/vol/system/logs/16.dsc'
00:00:01:742: MCP: Master title 0005001010040100 os 000500101000400a from mlc01 flags 0004
00:00:01:749: MCP: no valid title list found, rebuilding...
00:00:01:755: MCP: os version 10 NDEBUG (0x000500101000400a)
00:00:01:756: MCP: FSA volume on device /dev/mlc01 (wfs) attached @ uptime 1.756 s.
00:00:01:781: MCP: found master title 5001010040100 on mlc01 at 1.781 s
00:00:01:792: MCP: FSA volume on device /dev/ramdisk01 (wfs) attached @ uptime 1.792 s.
00:00:01:792: MCP: Titles scanned (dev_state 0006) on device /dev/ramdisk01 (wfs) @ uptime 1.792 s.
00:00:01:793: MCP: FSA volume on device /dev/slc01 (isfs) attached @ uptime 1.793 s.
00:00:01:794: MCP: FSA volume on device /dev/slccmpt01 (isfs) attached @ uptime 1.794 s.
00:00:01:794: MCP: Titles scanned (dev_state 0006) on device /dev/slccmpt01 (isfs) @ uptime 1.794 s.
00:00:01:967: MCP: ECO mode is disabled
00:00:01:967: [+-* DK is ready for console input *-+]
00:00:01:967: MCP: syslog mask is set to 0xffffffff
00:00:01:973: W2C: Does not need W2C-reflection
00:00:02:116: UHS1 Trace: DevFsm(EHCI-2/L0/P0): Creating device, speed=HIGH.
00:00:02:117: UHS1 Trace: DevFsm(OHCI-2:0/L0/P0): Creating device, speed=FULL.
00:00:02:118: CCR_MAIN: activating root hub.
00:00:02:173: MCP: Titles scanned (dev_state 000e) on device /dev/slc01 (isfs) @ uptime 2.173 s.
00:00:02:195: FS_MAIN: UMS Server Created.
00:00:02:198: AUXIL Info: resumed.
00:00:02:421: UHS1 Trace: DevFsm(EHCI-2/L1/P1): Creating device, speed=HIGH.
00:00:02:421: UHS1 Trace: DevFsm: There are now a total of 1 connected devices.
00:00:02:450: BT: BTA/BTE/STACK now operational
00:00:02:460: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.460 s.
00:00:02:461: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.461 s.
00:00:02:461: UHS1 Trace: CltIfFsm(V057e|P0341|IF2): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.461 s.
00:00:02:461: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.461 s.
00:00:02:462: UHS1 Trace: CltIfFsm(V057e|P0341|IF4): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.461 s.
00:00:02:462: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.462 s.
00:00:02:462: UHS1 Trace: CltIfFsm(V057e|P0341|IF6): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.462 s.
00:00:02:462: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.462 s.
00:00:02:462: UHS1 Trace: CltIfFsm(V057e|P0341|IF8): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.462 s.
00:00:02:463: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.462 s.
00:00:02:463: UHS1 Trace: CltIfFsm(V057e|P0341|IF10): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.463 s.
00:00:02:463: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 2.463 s.
00:00:02:463: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Acquired by client in pid 6.
00:00:02:464: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Enable endpoints 0x00080000.
00:00:02:504: __ccr_hid_attach_add_interface: idx 0 ep 3
00:00:02:504: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Acquired by client in pid 6.
00:00:02:504: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Enable endpoints 0x00100000.
00:00:02:544: __ccr_hid_attach_add_interface: idx 1 ep 4
00:00:02:545: UHS1 Trace: CltIfFsm(V057e|P0341|IF2): Acquired by client in pid 6.
00:00:02:545: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Acquired by client in pid 6.
00:00:02:545: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Activating bAlternateSetting 0.
00:00:02:548: UHS1 Trace: CltIfFsm(V057e|P0341|IF4): Acquired by client in pid 6.
00:00:02:548: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Acquired by client in pid 6.
00:00:02:548: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Activating bAlternateSetting 0.
00:00:02:551: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Acquired by client in pid 6.
00:00:02:551: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Enable endpoints 0x08001000.
00:00:02:552: UHS1 Trace: CltIfFsm(V057e|P0341|IF8): Acquired by client in pid 6.
00:00:02:552: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Acquired by client in pid 6.
00:00:02:552: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Activating bAlternateSetting 0.
00:00:02:555: UHS1 Trace: CltIfFsm(V057e|P0341|IF10): Acquired by client in pid 6.
00:00:02:555: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Acquired by client in pid 6.
00:00:02:556: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Activating bAlternateSetting 0.
00:00:02:558: DRH chip revision 00000040
00:00:02:558: DRH firmware version 190c0117
00:00:02:558: DRH cdc version 00080000
00:00:02:558: DRH wifi module id a8e502d0
00:00:02:558: DRH SPL id 00001cdc
00:00:02:726: NET: Applied interface MTU (wl0:1400 eth0:1400).
00:00:02:741: USBETH Trace: Created interface 100.
00:00:02:791: MCP: boot1 version 2.11.09
00;00;02;157: COSREPORT: Set level:1 from syslog level
00;00;02;157:
----------------------------------------------- BPERF: (0/2158338) PPC Init.
00;00;02;157: Cafe OS SDK Version 2.13.01 Build 69088 Branch sdk_2_13
00;00;02;157: PPC NDEBUG Kernel Build date - Feb  4 2021 16:37:45
00;00;02;157: BUILT AS OS_VERSION_MAJOR 000500101000800A MINOR 0x3DE8
00;00;02;157: core=1 COLD BOOT
00;00;02;157: SOFT INTERRUPT MODE
00;00;02;157: -----------------------------------------------

00;00;02;157: KiCblRegisterBlocks() completed with status 0:-4.
00;00;02;158: PROD Mode - don't even try to load kdebug.elf
00;00;02;158: title id: 5001010040100, app type 90000001
00;00;02;158:
00;00;02;158: ---------------------------------------
00;00;02;158: OS VERSION ID     0x000500101000400A
00;00;02;158: MASTER TITLE ON   FLASH
00;00;02;158: ---------------------------------------
00;00;02;158:
00:00:02:832: MCP: loaded and parsed 'preload.txt' at '/vol/system/title/00050010/1000400a/code'
00:00:02:849: MCP: Wake 0 signal
00:00:03:026: DRH using runtime generated WLAN data
00:00:03:026: Setting DRH to Normal mode
00:00:03:028: setting DRH system time to 22:24:56
00:00:03:029: sending DRC WOWL wake
00:00:03:045: WUD_BCMFWCheck ==> chipname 20702A1 build 517 from SERIAL FLASH
00:00:03:047: BT: BTRM now Active (WUD Operational)
00;00;02;932: DIAG:+KiRPLLoaderSetup
00;00;02;933: DIAG:-KiRPLLoaderSetup: before no-return call to KiLoadContext (0xEFE09400) (0x01003FFC)
00:00:03:071: ACT: Current account is #1.
00;00;04;007: DIAG:+KiProcess_FinishInitAndPreload
00;00;04;007: KiCblRegisterBlocks() completed with status 0:-4.
00;00;04;024: Kernel is loading shared data...
00:00:04:784: UHS0 Trace: HubPort(EHCI-1/L0/P0/A00)-P1: Device is not high speed, releasing port @ uptime 4.784 s.
00:00:04:941: ccr_admin_wowl_wake_drc() returned 0
00:00:05:036: UHS0 Trace: DevFsm(OHCI-1:0/L1/P1): Creating device, speed=FULL.
00:00:05:037: UHS0 Trace: DevFsm: There are now a total of 1 connected devices.
00:00:05:611: UHS0 Trace: DevFsm(OHCI-1:0/L1/P1/A01): Final teardown.
00:00:05:611: UHS0 Error: UhsFreeMem(pMem=0x102c0480) failed with error -4.
00:00:05:611: UHS0 Error: file uhs_device.c, function UhsDeviceHandleTeardown, line 432, status 0:-4, info 271320192(0x102c0480)
00:00:05:611: UHS0 Error: UhsFreeMem(pMem=0x102c0540) failed with error -4.
00:00:05:612: UHS0 Error: file uhs_device.c, function UhsDeviceHandleTeardown, line 432, status 0:-4, info 271320384(0x102c0540)
00:00:05:612: UHS0 Error: UhsFreeMem(pMem=0x102c0680) failed with error -4.
00:00:05:612: UHS0 Error: file uhs_device.c, function UhsDeviceHandleTeardown, line 432, status 0:-4, info 271320704(0x102c0680)
00:00:05:837: MCP: Heartbeat Enabled
00;00;05;717: DIAG:-KiProcess_FinishInitAndPreload: before no-return call to KiInitKernelFinish
00;00;05;717: DIAG:+KiInitKernelFinish
00;00;05;718: VVVVVVV----- PPC Kernel Waiting -----VVVVVVV
00;00;05;718: ^^^^^^^----- PPC Kernel Release -----^^^^^^^
00;00;05;718: DIAG:-KiInitKernelFinish: before no-return call to KiProcess_Launch
00;00;05;718:
--------------------
00;00;05;718: PROCESS  1 STARTING
00;00;05;718: SYSLOG_LEVEL 1: Warnings Enabled
00;00;05;718: UserMode Core & Thread Initialization (3 Cores)
00;00;05;718:   Core 1 Complete, Default Thread 0x100457E0
00;00;05;719:   Core 0 Complete, MSR 0x00005072, Default Thread 0x10045140
00;00;05;721:   Core 2 Complete, MSR 0x00005072, Default Thread 0x10045E80
00;00;05;721: Clearing Process MEM2 Arena...
00;00;05;734: MEM2 Arena clear complete, size 23 MB, 13ms
00;00;05;760: UserMode OS library build date: Feb  4 2021 16:38:58
00;00;05;760: __AppFlags: 0x00000200

00;00;05;761: OSBlockThreadsOnExit default for sdk version 21301
00;00;06;079: OSSetting_SynchronousPrinting DISABLED
00;00;06;084: OSSetting_CrashDumpType 0, MINI dump after crash
00;00;06;086: TCL(1): init DONE
00:00:06:283: UHS0 Trace: HubPort(EHCI-1/L0/P0/A00)-P1: Device is not high speed, releasing port @ uptime 6.283 s.
00;00;06;237: VPADInit() depricated, no need to call
00;00;06;238: VPAD Init end, BPERF: (0/6358491) Title PID=1
00:00:06:535: UHS0 Trace: DevFsm(OHCI-1:0/L1/P1): Creating device, speed=FULL.
00:00:06:536: UHS0 Trace: DevFsm: There are now a total of 1 connected devices.
00;00;06;617: ROOT: Read restart value 0
00;00;06;618: ROOT: Read audio relaunch value 0
00;00;06;618: ROOT: OSID 0x000500101000400A
00:00:06:860: MCP: Titles scanned (dev_state 0004) on device /dev/mlc01 (wfs) @ uptime 6.860 s.
00:00:06:894: UHS0 Trace: DevFsm(OHCI-1:0/L1/P1/A02): Final teardown.
00;00;06;796: Info: Calculating cold boot font CRCs on core:0
00;00;06;797: WPAD: Master Init
00;00;06;797: VPADInit() depricated, no need to call
COSREPORT: Using syslog level:1
COSREPORT: Set upid_mask:ffffffffffffffff module_mask:ffffffffffffffff level:1
00:00:06:964: MCP: Titles scanned (dev_state 000c) on device /dev/mlc01 (wfs) @ uptime 6.964 s.
00:00:06:966: MCP: Titles scanned (dev_state 0006) on device /dev/mlc01 (wfs) @ uptime 6.966 s.
00;00;06;889: TV mode before transition = 0
00;00;06;889: DRC mode before transition = 1
00;00;06;889: ROOT: Got audio buffer from foreground bucket @ e2c00000 len = 9437184
00;00;06;947:


Querying BSP for Hardware Information...
00;00;06;947: It is not Holly/Bolly-Wood
00;00;06;947: It is Latte A2x or later
00;00;06;947: using DSP memory parameters:
00;00;06;947:     DROM_BASE: 0x3000
00;00;06;947:     IRAM_SIZE: 0x2000
00;00;06;947:     DRAM_SIZE: 0x3000
00;00;06;947: Info: Cold boot processing font CRCs on core:1
00:00:07:085: MCP: PID 14 requested to disable power transitions
00;00;06;965: DIAG:Issued KiPrepareTitleAsync(0x000500301001110A)
00:00:07:254: MCP: loaded and parsed 'preload.txt' at '/vol/storage_mlc01/sys/title/00050030/1001110a/code'
00:00:07:254: MCP: Preparing error.rpx
00:00:07:261: MCP: Mapping /vol/content to /vol/storage_mlc01/sys/title/00050030/1001110a/content
00;00;07;141: DIAG:Result PrepareTitle(0x000500301001110A) came back with cosxml(0x000500301001110A)
00;00;07;143: TitleId 0x000500301001110A Version 0x00000064 Built On SDK 21204
00:00:07:566: UHS0 Trace: HubPort(EHCI-1/L0/P0/A00)-P1: Device is not high speed, releasing port @ uptime 7.565 s.
00:00:07:818: UHS0 Trace: DevFsm(OHCI-1:0/L1/P1): Creating device, speed=FULL.
00:00:07:818: UHS0 Trace: DevFsm: There are now a total of 1 connected devices.
Title: Re: After Defuse I get a blinking orange light
Post by: tzirf on Jul 11, 2025, 07:44 AM
That isn't the log files I am referring to. You can dump them using the minute menu in the backup and restore by selecting dump sys crash logs. You can also reference my video showing how to do this https://youtu.be/XgN_S1PgbGU?t=873