Skip to content
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

Tweak causing "respring loop" or "boot loop" in checkra1n #1

Open
yur1xpp opened this issue Feb 22, 2020 · 2 comments
Open

Tweak causing "respring loop" or "boot loop" in checkra1n #1

yur1xpp opened this issue Feb 22, 2020 · 2 comments

Comments

@yur1xpp
Copy link

yur1xpp commented Feb 22, 2020

First of all, thank you! This is a really amazing tweak that helped me find methods that I was looking for. However, installing this tweak on checkra1n iPhone X 13.3.1 device caused it to enter "respring loop" or "boot loop" after successfully jailbroke with checkra1n and booting up, it stuck at the Apple logo. Only if you jailbreak with Safe Mode on and remove this tweak, the device will boot up normally. If you're already in jailbroken mode with this tweak installed, the device will not loop as how I described previously, but the respring took very long time to complete.

Thank you! :)

@EthanArbuckle
Copy link
Owner

Sorry, just saw this issue. I reproduced this. The problem is that on iOS13, a lot of system daemons link UIKit. The cymbal tweak injects into every UIKit process, so when you reboot Cymbal is doing a ton of work across most system processes. This pushes the daemon watchdogs over their limit and they fail to spawn.

When you install cymbal and then respring, its only being injected into the handful of daemons that are killing during a respring. It slows the respring down noticeably but not enough to kill processes.

The solution is to reduce the number of processes cymbal is injected into by tweaking the filter plist. I'd like to make a preferenceloader bundle that lets you select which processes Cymbal is injected into

@yur1xpp
Copy link
Author

yur1xpp commented Aug 9, 2020

Thank you for the reply and info! Haven't using Cymbal for quite some time now due to this issue, looking forward to the update :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants