New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't install on High Sierra without a full system backup!! Hangs on login screen during restart #698

Open
essequattro opened this Issue Jun 10, 2018 · 10 comments

Comments

Projects
None yet
8 participants
@essequattro

essequattro commented Jun 10, 2018

Type of Controller

Xbox One

OS Version

macOS 10.13.4 High Sierra

Driver Version

0.16.8

Connection Method

Wireless

Device Name and Info

Device Name: MacBook Pro

Product ID: 0x0259

Vendor ID: 0x05ac (Apple Inc.)

Response of Controller

Untested

Response in Preference Pane

Untested

Detailed Explaination of Issue

I installed the drivers (I think the controller might have been already connected? Not sure) and allowed "Drew Mills" in System Preferences then rebooted as instructed. Tried to log in and the progress bar progressively slowed down after ~50% then eventually got all the way to 100% but just got stuck there and wouldn't log me in. Tried force rebooting into safe mode but it wouldn't work so I rebooted into recovery mode and did first aid on the drive (not sure if that did anything). Rebooted again holding shift to try to go into safe mode but it didn't appear to work (didn't say "safe boot" in top right corner, login screen functioned normally). Tried logging in anyways because I was out of ideas, left it alone on the loading screen for a while and when I came back it had magically kicked itself back to the login screen in safe mode. I was then mercifully able to log in and I immediately uninstalled the drivers and now it boots normally. I don't know how it ended up in safe mode but I guess I was lucky that it did because I didn't have enough space on my disk to reinstall macOS. This whole thing took about 2 hours and involved a lot of panic so I wouldn't recommend anyone else install it without a backup or a death wish.

@kittiban

This comment has been minimized.

Show comment
Hide comment
@kittiban

kittiban Jun 11, 2018

Hi, I had the same problem just now and got really scared. After the Safety Mode, resetting the SMC, and resetting the NVRAM didn't help, I managed to run First Aid via Disk Utilities. I managed to log in afterwards normally and deleted the driver. Hope this will help someone else and helps avoid some stress :)

kittiban commented Jun 11, 2018

Hi, I had the same problem just now and got really scared. After the Safety Mode, resetting the SMC, and resetting the NVRAM didn't help, I managed to run First Aid via Disk Utilities. I managed to log in afterwards normally and deleted the driver. Hope this will help someone else and helps avoid some stress :)

@doctorpangloss

This comment has been minimized.

Show comment
Hide comment
@doctorpangloss

doctorpangloss Jun 16, 2018

I don't think the Apple documentation is correct since 10.13.4 on how to install kext files.

doctorpangloss commented Jun 16, 2018

I don't think the Apple documentation is correct since 10.13.4 on how to install kext files.

@Reinkaos

This comment has been minimized.

Show comment
Hide comment
@Reinkaos

Reinkaos Aug 11, 2018

I had this issue as well!

Reinkaos commented Aug 11, 2018

I had this issue as well!

@FranticRain

This comment has been minimized.

Show comment
Hide comment
@FranticRain

FranticRain Aug 11, 2018

Collaborator

As I've said before many times, I'd love to fix this issue but I simply can't reproduce it to find the error and resolve the issue. Is there any other extension or program on your machine that would run as part of the boot process that may be causing some sort of incompatibility with the driver?

Collaborator

FranticRain commented Aug 11, 2018

As I've said before many times, I'd love to fix this issue but I simply can't reproduce it to find the error and resolve the issue. Is there any other extension or program on your machine that would run as part of the boot process that may be causing some sort of incompatibility with the driver?

@d235j

This comment has been minimized.

Show comment
Hide comment
@d235j

d235j Aug 11, 2018

Collaborator

Has anyone held down Command-V during boot to see where things get stuck?

Collaborator

d235j commented Aug 11, 2018

Has anyone held down Command-V during boot to see where things get stuck?

@jznadams

This comment has been minimized.

Show comment
Hide comment
@jznadams

jznadams Aug 31, 2018

I had the same problem although the only way I could solve it was restoring from backup. I did manage to get a capture of the Command-V output while it was stuck, hopefully that is helpful:

962a416d-16de-4e3e-90cc-6ced4b105305

jznadams commented Aug 31, 2018

I had the same problem although the only way I could solve it was restoring from backup. I did manage to get a capture of the Command-V output while it was stuck, hopefully that is helpful:

962a416d-16de-4e3e-90cc-6ced4b105305

@mistydemeo

This comment has been minimized.

Show comment
Hide comment
@mistydemeo

mistydemeo Sep 14, 2018

I encountered the same issue. Like @jznadams, it hung on an identical "Seting BTCoex Config" line. I had to remove 360Controller.kext in single user mode in order to boot my system again.

mistydemeo commented Sep 14, 2018

I encountered the same issue. Like @jznadams, it hung on an identical "Seting BTCoex Config" line. I had to remove 360Controller.kext in single user mode in order to boot my system again.

@FranticRain

This comment has been minimized.

Show comment
Hide comment
@FranticRain

FranticRain Sep 15, 2018

Collaborator

Since we seem to be failing on the Bluetooth coexistence part of boot, here's a version of the driver with none of the Bluetooth controller hooks in it, just for kicks and giggles. The timelines don't quite add up on this being the solution, but it's worth a shot. Let me know what your results are if you give it a shot.

Install360Controller.pkg.zip

Collaborator

FranticRain commented Sep 15, 2018

Since we seem to be failing on the Bluetooth coexistence part of boot, here's a version of the driver with none of the Bluetooth controller hooks in it, just for kicks and giggles. The timelines don't quite add up on this being the solution, but it's worth a shot. Let me know what your results are if you give it a shot.

Install360Controller.pkg.zip

@mistydemeo

This comment has been minimized.

Show comment
Hide comment
@mistydemeo

mistydemeo Sep 15, 2018

Can confirm that version of the package works for me; my system boots and I'm able to use wired controllers.

mistydemeo commented Sep 15, 2018

Can confirm that version of the package works for me; my system boots and I'm able to use wired controllers.

@FranticRain

This comment has been minimized.

Show comment
Hide comment
@FranticRain

FranticRain Sep 15, 2018

Collaborator

Well that's good enough for me. I've been looking for a legitimate reason to strip the Bluetooth code out of the driver for a while and you've given me a wonderful present.

I'm pushing this change and making a new release. I will leave this issue for a short period for feedback on this change.

Collaborator

FranticRain commented Sep 15, 2018

Well that's good enough for me. I've been looking for a legitimate reason to strip the Bluetooth code out of the driver for a while and you've given me a wonderful present.

I'm pushing this change and making a new release. I will leave this issue for a short period for feedback on this change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment