-
Notifications
You must be signed in to change notification settings - Fork 124
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
GUI #12
Comments
Can Project Sandcastle's framebuffer driver being used to get graphics working? |
Don't think so, their driver is for connecting linux to the iPhone's screen. What we need to do is to connect iOS to QEMU's "screen". |
|
can the framebuffer in https://github.com/checkra1n/pongoOS be used? (i think they have darwin ABI) |
Unfortunately I don't think it is helpful. The first challenges are on the iOS side. We need to force the iOS kernel to enable the graphic interface and starting using the framebuffer with software rendering. Since PongoOS runs before iOS I think both challenges are unrelated to this code you are referencing. |
So, run SpringBoard and debug from it. |
I'm interested in doing this, how do I run SpringBoard? I've done the steps in the wiki and have a XNU QEMU running iOS 12 |
It seems SpringBoard is running, but not displaying
IOMobileFramebuffer seems to be attaching. I'm looking at the decompilation of kernelcache.release.n66.out using Ghidra and so far I'm not understanding how iOS is blocking software rendering |
Apologizes for the bump, but is the GUI portion still being worked on?? :) |
nop |
What repo are they doing it in then? :) |
Well I mean there's no activity on this repository for a long time so... There is a fork (not related) of iOS QEMU at https://github.com/TrungNguyen1909/qemu-t8030 it still does not have GUI yet, and it uses QEMU 7.0.0. SpringBoard requires Metal besides a basic graphical framebuffer, so it will be difficult to do. |
Metal support is partially implemented here https://github.com/iqemu64/iqemu64 |
Bullshit |
Is that thing really work? |
Literally just QEMU with the history removed. If mouths could shit this guy would have two butts |
:v |
Seems like I was partially wrong, there are changes but from what I can tell it just knows how to run iOS binaries (in bsd-user directory) but it doesn't emulate any hardware, it is just binary emulation |
So that means it require a MacOS or *BSD host to run? If *BSD is OK then that's really easy, go and get FreeBSD, OpenBSD or NetBSD |
No, it doesn't have Metal emulation. It just knows how to parse and run iOS binaries, so it would only work in macOS itself |
Well there is actually MacOS (both x86_64 and ARM64 emulation, but ARM64 doesn't have display), so I think it will work in a Mac VM, but slowwwwwwwwwwwwww |
Virtualised macOS without GPU passthrough (via KVM or similar) wouldn't have acceleration anyway |
Corellium reveals an interesting but also undocumented boot argument:
|
Make the Graphic Frame Buffer work and displayed in a QEMU window.
The text was updated successfully, but these errors were encountered: