[WIP] update for isw11k #18
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I attach dmesg. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ISW11K temp root is done via breaksuiddiag.
However, it is known that breaksuiddiag (and break_setresuid) is quite unstable.
So, I tried to analyze the 145.0.0002 kernel.
However, the device reboots in attempting futex.
libdiagexploit is not working either (which is contrary to breaksuiddiag result!)
Very sorry for WIP pull request, but would you mind to take a look?
I upload the mmcblk0p8 to https://dl.dropboxusercontent.com/u/46196585/mmcblk0p8_145_0_0002 .