Skip to content

Fix autorun race condition on Samsung One UI (ignore LOCKED_BOOT_COMPLETED) - #190

Open
be3uchii wants to merge 1 commit into
mitschud:masterfrom
be3uchii:fix-samsung-boot-race
Open

be3uchii wants to merge 1 commit into
mitschud:masterfrom
be3uchii:fix-samsung-boot-race

Conversation

@be3uchii

Copy link
Copy Markdown

On Samsung devices (tested on Galaxy S22 Ultra SM-S908U1, Android 16 / One UI), LOCKED_BOOT_COMPLETED and BOOT_COMPLETED fire within ~30ms of each other.

Because the first thread has not created /dev/df yet when the second broadcast arrives, two ExploitRunner threads race to patch crash_dump64 and vendor libraries simultaneously, causing the run to fail and triggering the autorun interlock.

Ignoring non-BOOT_COMPLETED intents in BootReceiver.onReceive() ensures a single clean execution after unlock without false interlock triggers.

@mitschud mitschud self-assigned this Nov 19, 2026
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

Successfully merging this pull request may close these issues.

2 participants