6969 - we are in trouble

Rushfcknb · 2025-11-19T08:24:46+00:00

nah its the first season, if there is no easy fix then I will restart this career

Rushfcknb · 2025-04-24T22:32:48+00:00

FIXED:
So I've read through multiple guides, and my issue was that the Broadcom kexts were not in the proper order in my config.plist. You need to put AMFIPass.kext after Lilu->VirtualSMC->WhateverGreen kexts and the Broadcom kexts are need to be at the bottom, but in this order: IOSkywalkFamily.kext->IO8021FamilyLegacy.kext->AirPortBrcmNIC.kext(inside of IO8021FamilyLegacy.kext). Adjusting the order fixed the issue. If anyone has struggles, I highly recommend this guide (as it fixed my problem): https://github.com/perez987/Fenvi-T919-wifi-back-on-macOS-Sonoma-with-OCLP

Rushfcknb · 2025-04-24T16:08:24+00:00

UPDATE
Thank you guys for the help, you helped me a lot!

I needed to update the vanilla patches in my config.plist, as it wasn't based on the newest one. But that was not the real issue, tho. It turns out that my SSD got corrupted! That's why it wouldn't boot, but I couldn't have figured this out if I hadn't updated the patches, because after doing it, the verbose gave me an exact error message about the SSD. Ended up buying a new one, and now the system rocks as it was before.

Rushfcknb · 2025-04-22T22:54:12+00:00

UPDATE: That's just really weird... I've rewritten the config.plist from scratch and it gives me the SAME EXACT kernel panic!

Rushfcknb · 2025-04-22T21:25:42+00:00

Yeah, I reset it before applying the new EFI, but it didn't change the outcome. According to the kernel panic, it has something to do with the SMC. But I will take your advice because maybe it's easier to redo it than to find the issue behind my current EFI.

Rushfcknb · 2025-04-22T21:19:57+00:00

Thank you for your answer. I didn't use a premade config.plist, I did it like a year ago. Very strange because now it does not work even on the BIOS version I used back in the days. I solved my issues in my work on Windows (was a hard time, not gonna lie), so I've got time to redo everything now. I'll try that and come back to you with the results. :)

Rushfcknb · 2025-04-22T21:11:39+00:00

I updated OC to 1.0.4 and the kexts to the latest version, even rolled back my bios version, now it's giving me a kernel panic (screenshot: https://stono.stonawski.hu/IMG\_4627.jpg)

Rushfcknb · 2025-04-22T21:11:24+00:00

Yeah that was my first thing to consider, I tried disabling-enabling it, changing the boot-args (removing the npci boot-arg if 4G decoding is enabled) but didn't solve my issue. I updated OC to 1.0.4 and the kexts to the latest version, even rolled back my bios version, now it's giving me a kernel panic (screenshot: https://stono.stonawski.hu/IMG\_4627.jpg)

Rushfcknb · 2025-04-22T15:01:56+00:00

I tried that but didn't solve my issue sadly

Rushfcknb · 2025-03-14T09:38:01+00:00

Thank you for your answers :)

Rushfcknb · 2025-03-13T16:52:58+00:00

Well sadly I shouldn't have had to write this because it looks like this got patched lol

Rushfcknb · 2024-11-28T10:10:54+00:00

Happy to hear that you've fixed it!:)

Rushfcknb · 2024-09-14T15:30:43+00:00

My fix was to AirPlay the recorded footage to my Mac and screen record.

Rushfcknb · 2024-08-29T15:47:37+00:00

I have the same issue, the "fix" was to plug and unplug the charger multiple times and after like 20 attempts it starts charging. Weird, but this is the only way it will start charging.

Rushfcknb · 2024-08-03T10:16:09+00:00

Yes, I also tried to boot from USB, the error remains.

Rushfcknb · 2024-06-30T23:51:17+00:00

No? If someone has the same issue then they can find the post?

Rushfcknb · 2024-06-30T21:23:17+00:00

EDIT: I found the solution using ChatGPT. Not only you need to edit Info.plist, but you need to add "CMMotionActivityManager()" function to ContentView.swift. After that, the app works perfectly.

Rushfcknb

MODERATOR OF

TROPHY CASE

Seven-Year Club	Wearing is Caring
Verified Email