Chosen Solution
Hello. My iPhone X keeps rebooting randomly, 3-4 times a day and it takes long time to work normally again. After investigating panic-full logs, I found this message: checkBusStatus SCL is stuck low; last write status 00000108 int shadow 00010100 xfer 40000000 fifo 00000022 for device display-pmu Looks like there’s a problem with the display PMU. Is it easy to replace only this part or will I need to obtain a whole new screen? Phone stores ask for $350++ to replace an iPhone X screen. Thank you. / Updated: The first section of panic-full log: “build”:“iPhone OS 12.4 (16G77)”, “product”:“iPhone10,6”, “kernel”:“Darwin Kernel Version 18.7.0: Fri Jun 21 22:24:16 PDT 2019; root:xnu-4903.270.47~7/RELEASE_ARM64_T8015”, “incident”:“4F9F6D52-6AD0-49AF-B230-C660F3A65753”, “crashReporterKey”:“64b11221d0a83ae164b70eb9f98dc321764fd0eb”, “date”:“2019-08-25 22:42:38.08 +0700”, “panicString”:“panic(cpu 2 caller 0xfffffff01008405c): “i2c3::_checkBusStatus SCL is stuck low; last write status 00000108 int shadow 00010100 xfer 40000000 fifo 00000022 for device display-pmu”@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleS5L8940X/AppleS5L8940X-166.200.1/AppleS5L8940XI2C.cpp:340 Debugger message: panic Memory ID: 0xff OS version: Not set yet Kernel version: Darwin Kernel Version 18.7.0: Fri Jun 21 22:24:16 PDT 2019; root:xnu-4903.270.47~7/RELEASE_ARM64_T8015 KernelCache UUID: 4E83915BBCAB6C91CDFCDADF90ACE495 Kernel UUID: B1307FDA-64B9-3CAA-893F-082821110C43 iBoot version: iBoot-4513.270.14 secure boot?: YES Paniclog version: 13 Kernel slide: 0x0000000009dc0000 Kernel text base: 0xfffffff010dc4000 mach_absolute_time: 0x1871a9df Epoch Time: sec usec Boot : 0x00000000 0x00000000 Sleep : 0x00000000 0x00000000 Wake : 0x00000000 0x00000000 Calendar: 0x00000000 0x00000000 Panicked task 0xffffffe00037e760: 1296 pages, 196 threads: pid 0: kernel_task Panicked thread: 0xffffffe0006bc000, backtrace: 0xffffffe04ed63260, tid: 200 lr: 0xfffffff010ed291c fp: 0xffffffe04ed632f0 lr: 0xfffffff010fc675c fp: 0xffffffe04ed63420 lr: 0xfffffff010e9d610 fp: 0xffffffe04ed63430 lr: 0xfffffff010ed1ed8 fp: 0xffffffe04ed637a0 lr: 0xfffffff010ed2250 fp: 0xffffffe04ed637e0 lr: 0xfffffff010ed20a4 fp: 0xffffffe04ed63800 lr: 0xfffffff01008405c fp: 0xffffffe04ed63890 lr: 0xfffffff010083c1c fp: 0xffffffe04ed638c0 lr: 0xfffffff010083920 fp: 0xffffffe04ed638f0 lr: 0xfffffff00fd3f778 fp: 0xffffffe04ed63910 lr: 0xfffffff00fd3f5e0 fp: 0xffffffe04ed63940 lr: 0xfffffff01137fc74 fp: 0xffffffe04ed639b0 lr: 0xfffffff00fd400e8 fp: 0xffffffe04ed63a10 lr: 0xfffffff01051a2d8 fp: 0xffffffe04ed63a60 lr: 0xfffffff01051a240 fp: 0xffffffe04ed63aa0 lr: 0xfffffff01051aa9c fp: 0xffffffe04ed63ad0 lr: 0xfffffff01135d138 fp: 0xffffffe04ed63b20 lr: 0xfffffff01135cf1c fp: 0xffffffe04ed63bb0 lr: 0xfffffff01135c44c fp: 0xffffffe04ed63c20 lr: 0xfffffff01135e134 fp: 0xffffffe04ed63c90 lr: 0xfffffff010ea86b4 fp: 0x0000000000000000 “, “panicFlags”:“0x2”,
Even if you would find a suitable IC for replacement, first you should tear down the display to separate the Oled screen to avoid damaging it with heat, replace the IC and then reassemble the screen. Chances you would get an acceptable and working result after all that, I would estimate being no more than 1 in 1,000,000. Do yourself a favor and forget about it :)
