Lockdown e mux error как исправить

Modded/Hacked App: ドラゴンボール レジェンズ By BANDAI NAMCO Entertainment Inc.
Bundle ID: jp.co.bandainamcoent.BNEI0333
iTunes Store Link: https://itunes.apple.com/jp/app/ドラゴンボール-レジェンズ/id1358232022?mt=8

Mod Requirements:
— Jailbroken or Non-Jailbroken iPhone/iPad/iPod Touch.
— Cydia Impactor.
— A Computer Running Windows/Mac/Linux.

Hack Features:
— Enemies Don’t Attack
— No Ki Cost
— Unlimited Ki
— No Character Swap CoolDown
— No Vanish CoolDown
— Auto Complete All Challenges — Currency/Chrono Crystals Hack! 
— Always Critical
— All Cards Give DragonBall 

 This hack only works on x64 or ARM64 iDevices: iPhone 5s, 6, 6 Plus, 6s, 6s Plus, 7, 7 Plus, 8, 8 Plus, X, SE, iPod Touch 6G, iPad Air, Air 2, Pro & iPad Mini 2, 3, 4 and later.

Go to jailbreak

Again I see device id 0 here…. Let’s try to figure this out.
It starts in device.c in device_version_input():
Connected to v2.0 device 1 ...
https://github.com/libimobiledevice/usbmuxd/blob/master/src/device.c#L580-L589

usbmuxd_log(LL_NOTICE, "Connected to v%d.%d device %d on location 0x%x with serial number %s", dev->version, vh->minor, dev->id, usb_get_location(dev->usbdev), usb_get_serial(dev->usbdev));
dev->state = MUXDEV_ACTIVE;
collection_init(&dev->connections);
struct device_info info;
info.id = dev->id;
info.location = usb_get_location(dev->usbdev);
info.serial = usb_get_serial(dev->usbdev);
info.pid = usb_get_pid(dev->usbdev);
info.speed = usb_get_speed(dev->usbdev);
preflight_worker_device_add(&info);

here we have the correct id. This function calls preflight_worker_device_add() with a struct that also has the device id in it.
In preflight_worker_device_add(), a copy of the structure is made:
https://github.com/libimobiledevice/usbmuxd/blob/master/src/preflight.c#L347-L349

struct device_info *infocopy = (struct device_info*)malloc(sizeof(struct device_info));

memcpy(infocopy, info, sizeof(struct device_info));

Then, a thread is created that will call the thread handler preflight_worker_handle_device_add() with that copy.
Now in preflight_worker_handle_device_add() a idevice_private struct is created and filled with the device info, among that is the device id:
https://github.com/libimobiledevice/usbmuxd/blob/master/src/preflight.c#L125-L131

struct device_info *info = (struct device_info*)userdata;
struct idevice_private *_dev = (struct idevice_private*)malloc(sizeof(struct idevice_private));
_dev->udid = strdup(info->serial);
_dev->mux_id = info->id;
_dev->conn_type = CONNECTION_USBMUXD;
_dev->conn_data = NULL;
_dev->version = 0;

This is then used to create a lockdown connection. It has a log message there:
https://github.com/libimobiledevice/usbmuxd/blob/master/src/preflight.c#L141

usbmuxd_log(LL_INFO, "%s: Starting preflight on device %s...", __func__, _dev->udid);

Maybe you can add the dev->id there, like this:

usbmuxd_log(LL_INFO, "%s: Starting preflight on device %d %s...", __func__, _dev->mux_id, _dev->udid);

This would allow us to see if, at this point, it still has the right device id. To look a bit further, the device id (mux_id) is passed to usbmuxd_connect() in libimobildevice’s idevice_connect():
https://github.com/libimobiledevice/libimobiledevice/blob/master/src/idevice.c#L293

int sfd = usbmuxd_connect(device->mux_id, port);

and it libusbmuxd.c it is finally sent to usbmuxd here:
https://github.com/libimobiledevice/libusbmuxd/blob/master/src/libusbmuxd.c#L731

plist_t plist = create_plist_message("Connect");
plist_dict_set_item(plist, "DeviceID", plist_new_uint(device_id));
plist_dict_set_item(plist, "PortNumber", plist_new_uint(htons(port)));

res = send_plist_packet(sfd, tag, plist);

In usbmuxd, it will land in client.c and this is where the id will end up being 0:
https://github.com/libimobiledevice/usbmuxd/blob/master/src/client.c#L677-L687

node = plist_dict_get_item(dict, "DeviceID");
if (!node) {
	usbmuxd_log(LL_ERROR, "Received connect request without device_id!");
	plist_free(dict);
	if (send_result(client, hdr->tag, RESULT_BADDEV) < 0)
		return -1;
	return 0;
}
val = 0;
plist_get_uint_val(node, &val);
device_id = (uint32_t)val;

Somewhere in between the id gets lost. Maybe you can also add a printf to libusbmuxd’s send_plist_packet() here:
https://github.com/libimobiledevice/libusbmuxd/blob/master/src/libusbmuxd.c#L541
Just add a line after this:

plist_to_xml(message, &payload, &payload_size);
printf("%sn", payload);

Then report back

No technology is complete without giving its users some error message or codes along the way.

In this case, I’m talking about Cydia Impactor.

While it’s no technology device, this utility is critical to a lot of iOS users, especially the ones that do not have a jailbroken iPhone or iPad.

In fact:

Even if you have a jailbroken iOS device, the Cydia Impactor tool can really be helpful as we all know AppSync Unified still hasn’t been updated for iOS 10.

Good News! Version 6.0~b1 now works on iOS 10!

Plus, many of our tutorials here have Cydia Impactor as a prerequisite before proceeding further into the instructions.

That being said, if you ever run into any issues with this tool, the list below will get you out of it.

SSL ERROR 133

A user recently reported this error message to me as he tried to use Cydia Impactor on his Mac and it shows:

http-sox.cpp:133 An SSL error has occurred, and a secure connection to the server cannot be made

…after he entered his Apple ID credentials.

I didn’t personally experience this trouble, so the following fix was contributed by a user from Reddit.

1. Force close Cydia Impactor
2. Launch iTunes and sync your device
3. Quit iTunes and re-open Cydia Impactor
4. Try to sideload your iOS app again

HTTP-WIN.CPP:158

We just talked about an SSL error in Cydia Impactor, so mind as well mentions another one.

Peer certificate cannot be authenticated with given CA certificates. SSL certificate problem: self-signed certificate in the certificate chain

Lucky for you, this problem can be solved without having to do much. Saurik just updated his tool to address to issue. All you have to do is uninstall your current version and click here to download the latest update of Cydia Impactor.

ERROR 68

If you see a popup that says,

ios/addAppId

An invalid value ‘CY- mach_portal’ was provided for the parameter ‘appIdName

Then you might want to also upgrade your Cydia Impactor to the newest version.

INSTALLATION ERROR 42

Unlike other errors, this one actually gives you an explanation that’s easy to understand. If you didn’t catch it, I would repeat it again.

The system version is lower than the minimum OS version specified for bundle…

In other words, your iPhone or iPad isn’t running on one of the iOS version that’s compatible with the iOS app. The best thing to do is upgrade your firmware.

Alternative fix if extra_recipe is refusing to install.

1. Unzip the IPA
2. Navigate to Payload > extra_recipe > Select show package contents > Payload > Info.plist
3. Change MinimumOSVersion to 10.0.0
4. Compress the Payload file
5. Change its extension from .ZIP to .IPA
6. Now try again using Cydia Impactor. Thanks /u/System0verlord

ERROR 179

Here’s the full log:

ipa.cpp 179 application already installed as incompatible team

If you encountered this problem while re-jailbreaking your home depot jailbreak or yalu, then the best thing to do is remove either app from your iOS device and then try again.

LOCKDOWN ERROR

Sounds a bit extreme, isn’t it?

lockdown.cpp:57

LOCKDOWN_E_SSL_ERROR

Don’t worry; I had this issue before in Cydia Impactor. The way I troubleshoot this problem was super easy.

Disconnect your device from the computer. On your iPhone, go to Settings > General > Reset > Reset Location and Privacy. Plug your device back to the computer and open iTunes. On your iPhone screen, it should have a popup with the “Trust” button on it, tap on that and you can use Cydia Impactor again.

The lockdown:57 error will eventually go away.

Note: If you received this error while running iOS 11, it means that Cydia Impactor is not compatible with your firmware yet. To learn more about that, read this article.

ERROR 62

provision.cpp:62 _assert(response.head[“content-type”] == “text/x-xml-plist”)

The fix for this error is quite weird if you ask me. Just keep entering your Apple Id and password until the error no longer appears.

But many times? Several users reported that it took them about 5 – 10 tries until Impactor would start working again.

ERROR 71

Someone on Twitter recently reached out to me and asked about an error in Cydia Impactor called provision.cpp:71. Although upgrading to the latest version will not help you resolve this issue, we have found a way to fix it.

ios/SubmitDevelopmentCSR=7460

You already have a current iOS Development certificate or pending certificate request.

This Cydia Impactor Error is one that has been popping up a lot lately.

Here’s a quick excerpt from the detailed guide on how to fix it this Cydia error:

1. Launch Cydia Impactor on your Mac or Windows computer
2. Click Revoke Certificates under the Xcode menu
3. Enter your Apple ID

PLIST.HPP:92

./plist.hpp:92 _assert(plist_get_node_type(plist) == PLIST_STRING)

Technically this is an error, but it won’t prevent Impactor from installing the app on your device. In fact, once you see the hpp:92 warning, it means the app has been successfully installed.

Just open your iPhone and check if the application is there. In most cases, it should.

STUCK ON PREFLIGHTINGAPPLICATION

When you install an IPA through Cydia Impactor, it will show a progress bar to let you know the current installation status. At some point in time, you might be stuck at “PreflightingApplication.” This means your iOS device and the sideload apps you’re trying to use are incompatible with each other.

For example, you can’t install a Pangu jailbreak on a 32-bit device. To solve this issue, you will have to download the right IPA file.

STUCK ON VERIFYINGAPPLICATION

Unlike other errors, when Cydia Impactor is stuck at the VerifyingApplication screen, it means there’s a loss in connections between the utility, the IPA file, and your iOS device.

To fix this problem, use one of the following tips:

• Turn on Airplane Mode and turn it off (after a minute or so)
• Hard resetting your iPhone or iPad
• Delete the existing profile from the Settings app (if this happen during a re-sign process)
• Check for two-factor authentication

I was able to get past the VerifyingApplication log after deleting Yalu and rebooted my device.

PROVISION.CPP:138 MAXQUANTITY

Users have seen this new Cydia Impactor error called provision.cpp:138 which we were unable to find the cause behind it. As of now, we’ve tried the revoke certificate method, making a new Apple ID account, and using a different IPA source. Nothing has helped so far.

The best way to bypass this error at the moment is to install your IPA from a third-party app installer. You can check out a full list of them from here.

Update #1: Saurik just updated Cydia Impactor to version 0.9.44. According to the changelog, this update should fix the “maxQuantity error due to Apple change.”

INSTALLATION.CPP:42 ERROR

When you see this Cydia Impactor error, it means that the system version is lower than the minimum operating system version specified. The IPA zip file may be dragging and causing this error to appear. If this is the case, extract the zip file at the desktop and drag it to the software.

You can also try using a VPN from another region to try again or use a different tool to sign in to the IPA file. Some have tried to use iOS App Signer to resign yalu.ipa and then installed the latest Impactor, and this solution worked for them.

CYDIA IMPACTOR RUNTIME ERROR

If you run into a message that says runtime error or this application has requested the Runtime to terminate unusually, then you should try installing the latest and newest version of Visual C++ Redistribution.

WHY IS CYDIA IMPACTOR NOT WORKING?

If you signed in to your device with a Microsoft account, then the Cydia Impactor software might not work. When signing in with a Microsoft account, some activities are considered a security breach and are prohibited, and the Cydia Impactor may be one of those things that are prohibited.

DOES CYDIA IMPACTOR VOID MY WARRANTY?

No. Jailbreaking is what voids the warranty. If you need to use the warranty, then you can use Cydia Impactor to unjailbreak the iOS device before you send it in for service. You can also choose to restore the system via iTunes. Apple can’t distinguish a previously jailbroken iPhone if a proper restore on the device has been completed.

DO YOU NEED X CODE FOR CYDIA IMPACTOR?

No. You don’t need X Code for Cydia Impactor, even if you are using the feature to sign into IPA files. When you want to download new versions, check for updates under the Impactor menu. You will also find that the Impactor will occasionally prompt you when there are new versions available.

WHAT HAPPENS NEXT?

It’s important to me that those will be the only Cydia Impactor errors that you encountered because the fix for them is included above.

However, if you ever experienced another issue that wasn’t mentioned here, be sure to comment down below so we can all help each other out.

Cydia Impactor Unable to Recognize iPhone

Check out this tutorial if Cydia Impactor fails to recognize your iPhone.