Zum Hauptinhalt wechseln
Gemeinsam reparieren - Jetzt registrieren

Informationen zur Reparatur, Demontage und Fehlerbehebung für das iPhone 16 Pro, das am 20. September 2024 als Nachfolger des iPhone 15 Pro veröffentlicht wurde. Dieses Smartphone verfügt über ein 6,3 Zoll ProMotion OLED-Display, Apples A18 Pro SoC, eine Rückkamera mit drei Objektiven und die neue Camera Control Taste.

I'm stuck on a boot loop and have no idea what the analytics tells me

"build" : "iPhone OS 18.7.7 (22H340)",

"product" : "iPhone17,1",

"socId" : "8140",

"socRevision" : "11",

"incident" : "583B00EF-44FD-48D2-8F86-8A2638DF95C4",

"crashReporterKey" : "a351540b553d38e81439d2522d52b901f31dc74a",

"kernel" : "Darwin Kernel Version 24.6.0: Wed Mar 4 22:15:54 PST 2026; root:xnu-11417.140.69.706.9~1\/RELEASE_ARM64_T8140",

"date" : "2026-04-25 13:11:09.65 +1000",

"panicString" : "panic(cpu 0 caller 0xfffffff0384bd7dc): SMC PANIC - ASSERT: target\/d93\/target.cpp:195: 0, SMC BSC failure, spreadsheet ver(*10) 60\nS.sensor array 0 - 7 is 0, 3145728, 0, 0, 0, 0, 0\nF.sensor array 0 - 1 is 0\n\n - Misc(2) OUTBOX1 not ready\nASSERT: target\/d93\/target.cpp:195: 0, SMC BSC failure, spreadsheet ver(*10) 60\nS.sensor array 0 - 7 is 0, 3145728, 0, 0, 0, 0, 0\nF.sensor array 0 - 1 is 0\n\n\nRTKit: RTKit-2784.140.9.release - Client: AppleSMCFirmware_H17-5204.140.29.d93.REL\n!UUID: 0cd7a03d-b1fe-3ddf-aee8-dab8cc3af42b\nASLR slide: 0x0000000000000000\nTime: 0x00000001304b4fbc\n\nFaulting task 2 Call Stack: 0x0000000000054e58 0x0000000000054818 0x0000000000054634 0x0000000000053010 0x000000000003f6e8 0x0000000000067d30 0x0000000000048578 0x00000000000509ac 000000000000000000\n\nChinook ASC Async error info: \nl2c_err_sts 000000000000000000, l2c_err_adr 000000000000000000, l2c_err_inf 000000000000000000\nlsu_err_sts 000000000000000000, fed_err_sts 000000000000000000, mmu_err_sts 000000000000000000\ndpc_err_sts 000000000000000000\n\nMailbox (0): (0)\n Inbox AKF_KIC_INBOX_CTRL = 0x00020001, AKF_KIC_MAILBOX_SET = 0x11111101\n Outbox AKF_AP_OUTBOX_CTRL = 0x00020001, AKF_AP_MAILBOX_SET = 0x00000000\n\n dir endpoint

Diese Frage beantworten Ich habe das gleiche Problem

Ist dies eine gute Frage?

Bewertung 0
Einen Kommentar hinzufügen

2 Antworten

Hilfreichste Antwort

Don't feel bad about not understanding the analytics files; heck, I was a software engineer for 45 years and I have trouble making out what it says. However, there are a lot of very smart people who are good at figuring out stuff that Apple won't tell us about, and we have a pretty good idea what your panic log is saying. Here's the smoking gun:

S.sensor array 0 - 7 is 0, 3145728, 0, 0, 0, 0, 0

Us programmers have been used to dealing with this code in hexadecimal (base 16) rather than the regular decimal (base 10) format your panic log is reporting. Anyway, the number 3145728 that we're interested in translates to 0x300000 in hex, and that lets us look up what people have found out about it.

There's a wiki article here on iFixit that we've been trying to keep up to date with these codes, as Apple keeps changing them with each new model.

iPhone SMC Panic Assertion Failed

As you can see, we don't have any information on the iPhone 16 models yet, but I did find another authority that does have updated information for us.

Troubleshooting iPhone Reboot Problems

According to that information, code 3145728 indicates an issue with the charging port flex cable assembly. As I mentioned, our iFixit wiki doesn't have 16 information, but if we look back at the 15 Pro and Pro Max column, we see that it does show a 0x300000 code, and reconfirms that the likely cause is the charging port assembly. This guide shows how to replace that part on your phone.

iPhone 16 Pro Ladebuchse tauschen

Good luck, and be sure to come back and let us know how it all turns out; what you learn will help the next person who comes along with the same problem.

War diese Antwort hilfreich?

Bewertung 1
Einen Kommentar hinzufügen

Reboot by yourself

War diese Antwort hilfreich?

Bewertung 0

1 Kommentar:

In the interest of education, manually rebooting the phone isn't going to help in a situation like this. What's happening is every three minutes, the phone scans its sensors. If it runs into an issue where for some reason it can't read one of those sensors, it starts a process called a kernel panic. That entails logging the error and rebooting the phone in an attempt to recover from the error. Unfortunately, being a hardware error, the problem is still going to be there the next time the sensors are scanned, so the phone does the only thing it knows how to do, initiate another kernel panic.

Sorry to say, computers are actually pretty stupid, as it will never figure out that no matter how many times it reboots, the error is still going to be there, so you get stuck in this boot loop cycle forever, until the problem is fixed.

So nothing is going to help until, at least in this case, the charging port assembly is replaced.

von

Einen Kommentar hinzufügen

Antwort hinzufügen

Andres Forrisi wird auf ewig dankbar sein.
Seitenaufrufe:

Letzte 24 Stunden: 2

Letzte 7 Tage: 20

Letzte 30 Tage: 47

Insgesamt: 118