Undecimus: Can't jailbreak iPhone XS Max Dual-SIM 12.4.1 with unc0ver 4.3.1

[raraavis1337]

Trying to jailbreak iPhone XS Max Dual-SIM (iPhone 11,6 model D331pAP) with the latest unc0ver.
According to the log (screenshots below):

1. It first gives KernelUtilities.c(1503): Assertion failure
2. Then looking for MIDI Device ID for about 5 minutes, after about 30 attempts finds one and says "good to break"
3. But then gets stuck on "Collecting Kernel attack surface:" message forever.

Tried several times, over restarts, relaunches, left the device for hours - always the same.

Very similar to issue 1640, which was closed 1.5 months ago. And maybe also to issue 1809

[raraavis1337]

Try using unc0ver 3.8.0 or 4.0.3. No promises, but I think it should work.

@Hamlock-Maneuver Thanks a lot, it works perfectly with 4.0.3!

Now the question is whether it's possible to upgrade to 4.3.1 somehow to get all the performance and stability fixes? I'm replacing 4.0.3 with 4.3.1, it launches fine but then crashes every time I'm trying to re-jailbreak :(

@pwn20wndstuff Seems that a lot of people are having problems with 12.4.1. Can we ask to merge a working implementation from 4.0.3 into 4.3.1 please?

[youngzzzzzzz]

same problem here. stuck while using v4.3.1

xs max 12.4.1

[raraavis1337]

The problem is most of the fixes are centered around IOS 13.

Does that include the performance and battery drain fixes since then, and especially in 4.3.1?
So far no concerns stability-wise, but respringing is quite slow, and haven't measured the battery yet.

You are on a weird one. (12.4.1)

Well, that was the last stable one in 12.x. AFAIR the early 13's were not very successful. So stayed there waiting for the JB to come :)

Did you ever get a chance to save your Blobs?

No, not this time unfortunately. Haven't got any of the 13.x version.
So the only hope that the team will find the time to fix the latest implementation, or even better - to JB 13.3.1 )

[youngzzzzzzz]

Try using unc0ver 3.8.0 or 4.0.3. No promises, but I think it should work.

4.0.3 works.

[jebediah2]

I am on XS 12.4.1 with the exact same issue on all unc0ver versions above 4.0.3
I had offered pwn20wnd to beta test but never had the pleasure to.

[eglacias]

As mentioned can we eventually merge a working implementation from 4.0.3 into 4.3.1?
Actually in iOS 12.4.1 iPhone 6S plus (a8) I get unsupported message with 4.0.3.

I’m definitely willing to beta-test any solution. I have a number of older tweaks that will not work on iOS 13

iOS 13 is significantly different and has dropped some features of iOS 12, I have no intention of upgrading these older devices anymore, but would sure like an on device jailbreak.

A lot of important stuff that has been added in this latest uncover version
I tried the two versions mentioned and only 4.0.3 runs, even though reprovision appears to crash while installing on-device but uncover says unsupported when run!

[jebediah2]

IOS 12 focus ended with version 4.0.3. 4.2.1 and 4.3.1 are focused on ios 13. This was stated before, but keeps being deleted for some stupid reason. It is highly doubtful that any more development on ios 12 will continue with pwn. Someone else might pick up where it was left off. But probably not.

That's not how things work. If a program isn't compatible with what it used to, it becomes a different program. If it's going from 4.x.x to 4.y.y, it is assumed it retains compatibility. "Focus" doesn't have a meaning with compatibility. This means that unc0ver should be made to still work with iOS 12, in otherwise case we have to tell the developer so they can fix it.

[eglacias]

There are a lot of devices on iOS 12.4 (12.4.1 in my case I found an eBay 6s plus on that version) since there was a specific window where we upgraded when they accidentally released an exploit in that version, and having an on device jailbreak is far more convenient than having to get out my laptop anytime I have to reboot

[jebediah2]

That's not how things work. If a program isn't compatible with what it used to, it becomes a different program. If it's going from 4.x.x to 4.y.y, it is assumed it retains compatibility. "Focus" doesn't have a meaning with compatibility. This means that unc0ver should be made to still work with iOS 12, in otherwise case we have to tell the developer so they can fix it.

That's informative and it would be nice if that were the way it really is. But no. The developer of this jailbreak himself said the very same thing I have already told you. I would suggest either using what is available. Or update and hope that someone will create a jailbreak that will work for you.

Good speech though.

Look at OP's screenshot, this section in particular:

unc0ver Jailbreak
for iOS 11.0 - 13.3

The way things work forms a basis from which the community provides feedback and appreciates the developer's ability to respond. If their response is to ignore it or to state 'sorry it's broken for your version I guess', we still did the right thing, and indeed the only thing we could do. If the reality is the developer is aware of the bug and won't fix it, it is their responsibility to acknowledge it publicly and to remove the relevant iOS version from unc0ver's compatibility, not pretend it's not happening and let idiots like me download the latest unc0ver and scratch their head.

It's not like unc0ver has been fail-proof from the beginning up to this day, so it isn't straightforward to figure whether the culprit is the number of times you try, your own configuration, or the program itself. Knowing that you should stay away for particular versions would save some people a lot of time. Fixing the program for it to work the right way on particular iOS versions would be better. We are trying to help the developer to make it better.

[jebediah2]

Look you are missing the point of what I said. I follow the creator of unc0ver on twitter regularly. He has stated that the last 2 builds 4.2.1. and 4.3.1 are mainly focused on ios 13 support. Some of which breaks some compatibility to ios 12 users. You need to stay on 4.0.3 until support is added. Like I said before. 4.4.0 should have this support. But no promises.

If that is true then just quote the man, we don't need your second hand information in disguise here.

[jebediah2]

Look bro. Continue your struggle. You have figured me out. I came here only to fuck up people trying to jailbreak. My mission is to stop everyone with false ( real information ) strait from pwn himself. This could be true I guess. Or maybe I know what I'm talking about, so I decided to come here and share my information with people who need help...

Suffer in your own ignorance my friend. Nobody can help you.
I'm done with this fuckin forum.

Where is the quote?

[raraavis1337]

@jebediah2 Look, as a person who started this discussion, I do believe that it makes sense to merge and support 12.4.x devices. However, 4.0.3 works, and works well.
As you can see above, it works for several people and hopefully also for you. Yes, the respring is at normal speed like any other JBs from the past, that super fast impl hasn't been merged (not sure it's compatible with 12.x at all btw).
The same way we are ready to stay on older iOS, we can start with the same JB can't we? And regardless be very grateful for the hard work!

[jebediah2]

You are simply not worth the effort anymore.

Fortunately this thread isn't about me. In fact it isn't about you either.

[jebediah2]

@jebediah2 Look, as a person who started this discussion, I do believe that it makes sense to merge and support 12.4.x devices. However, 4.0.3 works, and works well.
As you can see above, it works for several people and hopefully also for you. Yes, the respring is at normal speed like any other JBs from the past, that super fast impl hasn't been merged (not sure it's compatible with 12.x at all btw).
The same way we are ready to stay on older iOS, we can start with the same JB can't we? And regardless be very grateful for the hard work!

We can do all that AND report errors when they occur?

[raraavis1337]

We can do all that AND report errors when they occur?

Certainly. But to Hamlock's point, it developer's choice where to invest their time, and whether to support older versions of not. Unless you had a chance to deep dive into the source code and low-level differences between 12.x and 13.x, it is impossible to estimate the level of effort.
Quite sure if we were ready to collect several thousands to support their work, they could consider finding the time and prioritize...

[raraavis1337]

If he is to lazy to confirm this information himself. They he can wallow in his own ignorance for as long as he likes. This information on Pwn's twitter is free for anyone to view. He chooses to ignore it. Well that's his problem now. As far as I'm concerned this thread can be closed now.

@Hamlock-Maneuver Agree, I'll close it soon.

One last thought: after working for a week with 4.0,3 jailbreak, I just gave up, uninstalled and upgraded to 13.3.1. First time in the last 10 years, since 3gs. And that was not related to unc0ver, which was completely fine. It's due to so many essential apps which are now protected and refused working on a jailbroken phone, even tethered after clean restart. AirWatch, all banking apps, and now even Tesco couldn't be fooled with any of the publicly available hiding tweaks.

And imho that's were the problem lies and going forward imposes a real thread to the future of jailbreaking - if we can't really use it on our daily drivers, the only target audience will be pirates trying to save couple of bucks on their kids' ipad games.... :((

[eglacias]

Hey there, so original idea of merging whatever causes iOS 12.4.1 to work with uncover into future versions is the essence of this thread.
Ie My newer acquired 6s plus (a9) on 12.4.1 does not at all run uncover whatsoever. Interestingly, I have 2 of the exact same device, but the older one is on 12.4 working with all uncover versions flawlessly. The second with a restored copy from iTunes of the older one does not work.
Perhaps the two people having a private discussion could just delete the posts off topic and we could keep focus on this one idea? I came here because I had this problem and posted a duplicate of this idea, and would like to keep focus if possible.
In those arguments, there is a relevant point, and that is simply whether this request is not going to happen, which the developers could mark and post if that’s the case
-cheers!

[jebediah2]

I'm done with this fucking circus.

Haven't left yet? This thread is not meant for you to get over yourself.

[eglacias]

Here are the logs and screenshots of 4.0.3 successfully installed and signed not working on my iPhone 6s Plus on iOS 12.4.1

diagnostics (1).zip

[theLaxerz]

The iPhone 4 is exploitable using checkm8, 12.4.1 isn’t jailbreakable at the moment from any reverse engineering team or person I have seen.

Sincerely,
Aaron Lax

On Apr 4, 2020, at 5:03 PM, eglacias [e-mail] wrote:


Here are the logs and screenshots of 4.0.3 successfully installed and signed not working on my iPhone 6s Plus on iOS 12.4.1

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[eglacias]

Strange, later versions are jail breakable, you would think the same exploit would be there. Also it says for a12 and a13 devices it is jailbreaker

[theLaxerz]

Up to 13.3

Sincerely,
Aaron Lax

On Apr 4, 2020, at 5:11 PM, eglacias [e-mail] wrote:


Strange, later versions are jail breakable, you would think the same exploit would be there. Also it says for a12 and a13 devices it is jailbreaker

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

[eglacias]

Well, maybe not with uncover, but I am running checkrain on ios 12.4.1 now so it is indeed jailbreakable. I just really want an on device solution

[raraavis1337]

Well, maybe not with uncover, but I am running checkrain on ios 12.4.1 now so it is indeed jailbreakable. I just really want an on device solution

@eglacias Your iphone 6s plus on 12.4.1 is currently jailbreakable by chakra1n only. unc0ver does not support it. I recommend using the Reddit jailbreak matrix, it's always reliable and updated.

[eglacias]

All right, so uncover does support this operating system only on a12 devices. I still hope they get support for a9 one day as I originally said. We can only hope. If that had been made clear on the uncover download site, I would have saved a lot of time. It’s the only place I could trust that if they said it does not that I’m sure it does not. To avoid traffic about it Add a simple line at the top that says 12.4.1 is excluded!

[jebediah2]

And it only took 27 days for it to finally sink in. Imagine that...

This thread is done with you.

[raraavis1337]

@Hamlock-Maneuver Thanks a lot for your assistance, it was very helpful.
This thread is now closed.

[abdullahalhillaly]

Peace be upon you, good morning WhatsApp Aya sends pictures and video clips. If you would like, what is the reason? Thank you. If you delete the tool, it sends 🌹