-
Notifications
You must be signed in to change notification settings - Fork 1
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
SE + iOS 11.4.1 failed #1
Comments
|
@platinumstufff Do you know which commit did I introduce the write error? It has to be recent but I would like to narrow it down so I can get rid of that issue |
This should not happen. The fdscream control should be in effect here. Are you saying adding an fd3 folder caused the write error to go away? |
Yes, but another error in this commit. It happens then i try to build with FD=3. |
Log:
|
@platinumstufff I see, you shouldn't be building with FD=3 unless you empirically verified using the scream test build that the descriptor actually is 3 |
If you are building the scream test, do not include a FD variable at all |
Probably the last one. I checked and the last to be built is Add trailing newlines. |
I know but:
|
Also the main issue now is
|
@platinumstufff That's fine, it's just a warning so you don't build the scream test by accident |
What's happening in the attempts? Is it just taking forever in stage 5 and then panic? I'm actually trying to switch it over to the sock_port exploit for better reliability but I haven't figured out how to make that not be a guaranteed panic in postexploitation |
Yes, but sometimes it show error
|
Yep, this has been addressed in future commits. I'll keep this issue open until error 85 is fixed on the main branch. |
Thank you for the answers. |
@platinumstufff No problem. It might even work now if you use the 32bit branch but change the assignment in line 69 of src/app/MainVC.m to |
I wiil try it thank you |
Build failed, |
Command-F to search "error", the message you gave just means there is an error above |
Error is |
That's weird because the Linux man page for sched_yield shows That said, the v0rtex exploit is not actually used in Spice, so you could technically patch out the entire file by replacing the
This has been fixed, but as a side effect, the warnings have been reduced back to |
I will try it, thank you |
Sorry for the delay. I believe I have rewritten these issues out of the commit history. You should be able to use Spice 1.0.171 or later. |
How can i add offsets for iPad Air 11.0.1? |
I have some questions about Spice. So there is no issues in that repo, and i cant found any contacts.
The text was updated successfully, but these errors were encountered: