iOS 14.2 JIT support not working on A11 devices or older #516
Comments
|
You said “ from previous UTM builds” but didn’t mention trying VMs created with the current build. Have you tried creating a new empty x86 VM and seeing if you can get to a bootloader prompt? |
I get the same behavior from new VMs. |
|
Please post a crash log.
Does this happen always? Including with brand newly created VM? |
That error only happens when I chose to use custom QEMU arguments. When I chose not to, UTM simply crashes to desktop. |
|
Okay please post a crash log of when you try to open a newly created VM |
|
Here's the crash log. I am downloading Xcode 12.2 Release Candidate to try again, it was probably a codesigning error? I never had such issues with previous builds. I've renamed the file from .ips to .txt because GitHub wouldnt let me upload it. Edit: I'll also try out one of the pre-made linux VMs from the vm-downloads repo to test again. |
Not sure if that may have caused any issues. Any reason why you changed the bundle Identifier? Also can you confirm that you’re signing with a development certificate and not an enterprise or distribution certificate? |
|
A test with the Debian ARM VM from the vm-downloads repo showed the same behavior, except that with custom QEMU arguments, I'd be stopped at a black screen with a spinning wheel.
No, but I have used it in the past before with no issues. I have two provisioning files, I can try again to re-sign on iOS App Signer. One provisioning file has a custom bundle identifier, the other doesn't. I'll try re-signing again with the other one, but I've tried both today too. Two days ago I just used them to re-sign some apps with no issues.
It's a development certificate, yes. I do not have an enterprise or distribution certificate. I'll try again re-signing, if it fails, soon Xcode 12.2 RC download will finish so I can try again. |
|
I mentioned a possible codesigning problem before, because there there was an warning on xcode about iOS 14.2 and Xcode 12.1, saying that I'd have to update Xcode. The warning did not stop me from sideloading the app, though. In 10 or 20 minutes after the download completes, we'll find out. |
|
I’ve noticed that you’re running 18B92 I hope nothing changed from 18B91 that was the RC... |
Yes, it's the public version. I've just tried again with my normally used provisioning file (the other you mentioned was from my dad, I've used that before though without issues too), the identifier says com.utmapp.UTM, yet same issues. Xcode 12.2 RC download finished, I'll install this new Xcode version and try again. It's probably just an issue with older Xcode version not being able to recognize a new iOS version. |
|
Uh oh let’s hope Apple didn’t fix this |
OK, while Xcode 12.2 RC is still being extracted and installed (it's damn slow) I am thinking... Is 18B91 still being signed? If yes, I can still downgrade, I'd just need to find the IPSW file and downgrade it, maybe? |
|
Maybe... but I would be very surprised if in the few days between the two builds that they fixed this. |
|
Question: why is UTM crashing with a codesigning violation while pc is in libsystem_platform? |
|
@saagarjha it’s crashing in the icache flush |
|
No luck with Xcode 12.2 RC. Same issues. They (Apple) probably fixed it? |
|
Can reproduce this as well, I guess they did :/ |
|
I'm downloading the iPadOS 14.2 RC (18B91) and praying it to be still being signed. EDIT: It will take hours to download the ipsw, it's very slow. Dammit. I better go to sleep and cry in a corner while it attempts to download. |
|
Attention- These appear to be the only signed versions as of 11/5/20 8:07 PM GMT-7. |
|
First and second betas only? Jesus. I'll try downgrading to 14.1 and use the beta profile to see if I can get the last beta, although I think it will not work too. EDIT: I give up. Downgrading requires a big backup effort I am not willing to do, there's too much data on this iPad to back up and restore manually, it'd require hours. I'm sad now. I guess that I'll have to go back to using QEMU on my macOS Catalina before Big Sur update, where UTM will have a macOS version to try out. Apparently we can still use the 14.1 tethering method with 14.2, but I haven't tried it. |
|
Can anyone else confirm this? We’ve checked the cs flags and can’t find any difference. Maybe a newer device acts differently? |
|
Hi, |
|
iPad Pro 2017 (10.5” and 12.9”) has A10X, not A11 |
|
I can personally confirm 18B92 works on my iPhone 12 Pro. |
How did you install UTM ? Got a free Apple account, AltStore beta, and added UTM repo to AltStore. Trying to open your custom Debian image instantly gets me back to homescreen. Trying to use the exact same procedure than people who succeeded. |
|
I am doing a manual backup of my iPad Pro data to try a downgrade to iPadOS 14.2 (18B91) Release Candidate build. I'll keep people posted if I manage or fail to downgrade and run UTM under a such scenario. This afternoon I was able to quickly download the IPSW. I think Apple needs to reconsider their stance - because even on macOS it is possible to run things with JIT and without any major issue. EDIT: Successfully downgraded to 18B91. Right I have to resign UTM and reinstall to try again. Fingers crossed. |
|
Hello, I'm new using UTM. I installed the 2.0.8 version signed through my BuildStore account but when I launch it says "Your version of iOS does not support running VMs while unmodified. You must either run UTM while jailbroken or with a remote debugger attached". I'm trying it on my iPad Pro 2020 running iOS 14.2 |
|
@brunocastello don’t think it’ll work because I got it working on both builds. It’s probably related to the device model. @josemsanchezb does it crash when trying to start a VM? Anyways the instructions says to use AltStore (latest beta) or iOS app signer. |
|
Downgrading to 18B91 RC build did not solve the problem on iPad Pro 2017 2nd gen 12.9". Same issues as reported yesterday on UTM build 2.0.8. It's 100% a device model issue. I'll just upgrade back to the final build and call it a day. My best hope is the checkra1n jailbreak, they were expecting to be able to run on A10X devices in a future update but it has been months since they said that. |
Thanks @osy86 , the tool I used is like the iOS App Signer, using a premium plan and my device UDID. It doesn't allow me to launch any VM, nor I can't attach any .iso file, it doesn't respond. |
|
There’s a reason I specified iOS App Signer and AltStore. Those are the only options that work. Most of these “premium signers” don’t work because they don’t use the right type of certificate. See the readme for more details. |
|
iPhone X (A11), 14.2 (18B92), paid dev account, iOS App Signer -> crash. |
|
It’s beginning to seem that way. I too would love to see a confirmation of any < A12 device. |
Someone on twitter in your feed mentioned iPhone X not working as well |
|
checked with ipad pro11 2018 version, (A12/x device) UTM started normally, crashed after start of VM (timeout). debug log here: |
|
A crash log would likely be more useful here, if you have it. |
|
UTM-2020-11-07-195051.log |
|
Looks like a UTM bug there. Can you open a new ticket and possibly provide the .utm that caused the crash? |
|
@osy86 A update to the Checkra1n jailbreak is out! 14.2 and A10X support, I will have to try again later tonight! Fingers crossed |
|
It’s now working again! I just jailbroke the iPad Pro 2017 running iOS 14.2 (18B92) and ran one of the pre-made VMs (Debian ARM no GUI) and it booted flawlessly. Good news, thanks to Checkra1n! |
|
Can replicate issue on iOS 14.2, iPad Air 2, with AltStore. VM crashes instantly. However, I’ll try the new checkra1n, see if it works. |
|
Now my machines are working again, but I have only one issue: I am now unable to drag the windows on desktop, for example macOS 9.2 finder windows are not draggable anymore. The touch input needs some kind of tweak, it seems. EDIT: I retreat it. The drag still works. For some reason it is more sensible now. Hard to get it right sometimes now. |
|
I think this is the cursor issue mentioned previously. For the future file a new bug when you find issues. |
osy
changed the title
|
Has the issue with alt-store been fixed? My iPhone 7+ is having this problem. |
|
AFAIK only a12 and newer can do jit on 14.2. |
|
I have an iPad Pro 2020 with latest iOS but when I start utm it shows the message about jailbreak and remote debugger. I compiled using the modified iOS app signer and my own certificate. I don’t know how to make it work. When I start a vm the screen is black and it doesn’t start. |
Just updated my iPad Pro 2nd gen 12.9" to iOS 14.2. Then I proceeded to re-sign the UTM.ipa with iOS App Signer, to be able to install using my own paid developer certificate. All clear, then installed the UTM.ipa through Xcode 12.1 on iPad Pro.
App was installed perfectly so I moved my old VMs inside to run. But none of my machines are loading up (MSDOS 6.22/Windows 3.1, Windows 95, macOS 9.2 and OS X 10.5 Leopard) because when I hit run, UTM crashes back to iPadOS home screen. I was able to go a bit further when I chose to bypass configuration and manually specify arguments, but then UTM would crash again complaining about error: "Could not allocate dynamic translator buffer". I hit OK, then UTM crashes again back to iPadOS home screen. Nightmare. I am unable to run any VM.
The text was updated successfully, but these errors were encountered: