Thank You,

Mike Niziolek

(203) 508-2919

I successfully replaced my iPhone 15 screen with the Hard OLED part form iFixit a few days ago. It’s been great, honestly, but I’ve noticed that the left side of the screen isn’t staying flush with the body of the phone. This is about 1.5mm above the edge of the phone body. The right side, top, and bottom are flush. I can push the left edge into the body very easily and there is no distortion on the screen when I do so. It stays for a while but so far eventually comes back up.

I’m posting here in case anyone has experience or thoughts before I go trying to open the phone again and dealing with the adhesive, clips, and risk of that, ha.

I have noticed that I don’t hear any click from the clip along the left edge when I push it back to flush. I’d expect that, but don’t know if that expectation is right. Would that clip hold the left edge flush if it were properly engaging? The left edge clip MAY have had a slight bend in it but it wasn’t enough to be obvious to my eye.

Some of the other clips were definitely bent when the part arrived: the top right corner clip was flat against the screen and the bottom screw loops were almost bent that far, as well. (the screen I replaced was freaking out with ghost touches, so I really couldn’t wait for another part and was able to bend those three into position).

Any thoughts will be much appreciated.

Thanks!

- Display (soft oled aftermarket)
- Battery (genuine Apple battery)
- Back glass (genuine Apple back glass)

Now, I understand that I cannot pair the display without transferring the touch IC and I'm okay with that. But I believe that this non-genuine display hinders the repair assistant to finish properly. It also shows up in the repair assistant in the "Finish repair" step next to the back glass and the battery.

However, the step fails within a few seconds with the message:

"Unable to Configure

Display
Back Glass
Battery

These parts could not be configured because they are not genuine Apple parts"

Is there a way to exclude the display from the repair assistant? I don't have an original Apple display laying around to hook that one up and then go through the assistant.

I have cleaned the base, replaced the new battery, screen and charging connector and started it up, but it is not responding and no electricity seems to be flowing.

Is there any way to repair these symptoms?

Can anyone tell me how to do this?

I'm hoping to get some assistance diagnosing and potentially repairing my iPhone 15. The phone will not charge at all when connected via a USB-C cable, but it charges perfectly fine using a MagSafe or other wireless charger.

Here are the details and troubleshooting steps I've already performed:

• Device: Iphone 15
• Problem: USB-C charging port appears to be non-functional: no charging indicator, no power delivery from multiple cables/adapters.
• Working Solution: Wireless charging (MagSafe and Qi) works flawlessly, indicating the battery and internal charging circuitry (aside from the wired port) are functional.

Troubleshooting steps I've already tried:

1. Multiple USB-C Cables: I've tested with several different, known-good USB-C cables and power adapters/wall bricks. None of them initiate wired charging.
2. Cleaned Charging Port: I have thoroughly inspected and carefully cleaned out the USB-C charging port on the iPhone 15. I used a non-metallic tool (e.g., a plastic toothpick, compressed air) to remove any potential lint, dust, or debris that might be obstructing the connection. The port appears clear.

My thoughts on the issue:

Based on my testing, and the fact that wireless charging is working, my strong suspicion is that the USB-C charging port assembly itself is faulty or physically damaged.

Found a Panic Log from last night, but I’m having trouble finding the actual cause of the crash.

{"bug_type":"210","timestamp":"2025-07-17 03:42:49.00 +0100","os_version":"iPhone OS 17.5.1 (21F90)","roots_installed":0,"incident_id":"FA248193-9DD3-4AEA-B451-BCC09AC6E9CE"}

{

"build" : "iPhone OS 17.5.1 (21F90)",

"product" : "iPhone15,4",

"socId" : "8120",

"socRevision" : "11",

"incident" : "FA248193-9DD3-4AEA-B451-BCC09AC6E9CE",

"crashReporterKey" : "6ed3b3eb6aa79fa1437db7b9775867f0e32c84c6",

"kernel" : "Darwin Kernel Version 23.5.0: Wed May 1 20:34:02 PDT 2024; root:xnu-10063.122.3~3\/RELEASE_ARM64_T8120",

"date" : "2025-07-17 03:42:49.87 +0100",

"panicString" : "panic(cpu 1 caller 0xfffffff04cbd3588): SMC SERROR Exception class=0x2f (SError interrupt), IL=1, iss=0 - power(1) OUTBOX1 not ready\nRTKit: RTKit-2419.120.45.release - Client: AppleSMCFirmware-4283.120.52.0.1.d37.REL\n!UUID: 528ac49b-01e1-370c-9d60-8a1ea5ada333\nTime: 0x0000025426c0c0e6\n\nFaulting task stack frame:\nWrong frame size for ARMv8. Got 840 bytes, expected 828\n Exception class=0x2f (SError interrupt), IL=1, iss=0\n r00=0x0000000080010001

However:

• Instagram works perfectly on other people’s iPhones (when they’re logged into their own accounts)
• My Instagram account works fine on Safari, PC, and Android
• I’ve tried logging into a different Apple ID, fully resetting my phone, and reinstalling Instagram multiple times
• I’ve also tried resetting network settings and factory resetting my iPhone
• The issue has followed me across more than one iPhone, so it’s not device-specific

Example errors pulled from Console logs:*** NSKeyedArchiver warning: replacing existing value for key 'iab_post_click_data';

nw_resolver_start_query_timer_block_invoke: did not receive all answers in time

System Policy: duetexpertd deny(1) file-read-metadata

SpringBoard: Acquiring focus timer elapsed, clearing acquiring focus state

broken or outdated UI variant or is flagged incorrectly on my account. It doesn’t seem like a hardware issue, but something server-side or deep in iOS.

I’ve contacted Meta support repeatedly with no fix. At this point I’m wondering if it’s a corrupted container, cached account flag, or some persistent data corruption linked to my user ID.

Question:

Has anyone ever dealt with something like this?

Could this be a hidden iOS-level cache or bad account flag stored somewhere locally or server-side?

Is there a repair step beyond full resets I’m missing?

Thanks in advance — I’ve been dealing with this for months.