Tool The New Auto Lipo/LipoARM64 with iOS 5, 6, 7, 8, 9, 10+ Support!

Rook · August 1, 2016

Since iOS 9 broke LipoARM64 with it's new "App Slicing" feature, we've made a simple postinst script to patch the user's binary automatically so people don't have to go through the process of thinning their binary and cheaters aren't forced to hack ARM64. For this to work, the thinned binary file must be integrated inside the deb file by the hacker.

This tutorial will guide you on how to add the new Auto Lipo in your project.

Tip: Click on the images to view them in their full resolution.

Instructions:
Go ahead and make your project using the "make package" command. You should have a folder named _ in your project folder.

Now go into the _ folder. There should be a folder called DEBIAN. Open it and go ahead and create a new file called postinst and add the code from here into it:
https://github.com/iOSGods/Auto-Lipo-for-iOS-5-to-iOS-9-/blob/master/postinst

Now we need to edit the postinst script for our project.

iosgods_binary="/var/mobile/Documents/Binary/BINARYNAME" <---- Replace the BINARYNAME with the binary name of the app.
iosgods_target_directory="/var/mobile/Containers/Bundle/Application/*/APPNAME.app/" <--- Replace the APPNAME with your app's name. In my case, it's blackops.app

iosgods_lipoarm64="/usr/bin/LipoARM64NAME" <--- We will be adding lipoarm64 to the project, and whatever you name the lipo file to, make sure you change it here to. I named my lipo file iOSGodsLipoARM64
lipoarm64_binarytarget="BINARYNAMETOPATCH" <--- This is the binary name lipo will be targeting. Change it to the name of your app's binary. In my case, blackops.
Now your postinst should be edited for the app you are making hack for.

Now inside the _ folder, we need to create folders /var/mobile/Documents/Binary
Once you have created those folders, go ahead and place the app's binary inside the Binary folder.

Now we need to add lipoarm64 to the project. Navigate to the beginning of the _ folder, and create folders /usr/bin/ and place the lipoarm64 file inside the bin folder. And remember, make sure lipoarm64 has the same name as in the postinst script (iOSGodsLipoARM64).

Now we are ready to build the .deb file. CD into your project file and build the deb using the dpkg command.

 dpkg-deb -Z lzma -b FOLDERNAME

Since the folder in my project is called _ , which contains the DEBIAN folder and other necessary files for our deb, i will write

 dpkg-deb -Z lzma -b _

LZMA is the highest level of compression so your .deb file won't be very big once it's compressed.

Now in your project folder, there should be a new folder called "_.deb" And that is it, you're done.

--------

You can also make your own custom templates to make everything said above automatic. This is an example NIC Template which has the New Auto Lipo integrated.

Updated with v3.0 of auto lipo with LipoARM64: http://iosddl.net/ec418d5f1df08afe/iOSGods_CSCI_Patcher_v3.0_NewAutoLipo.nic.tar

Auto Lipo binary only version 2.0 (installs faster than LipoARM64): http://iosddl.net/7675156e1f8b96e9/iOSGods_CSCI_Patcher_v2.0_NewAutoLipoBinary.nic.tar

When asked for Bundle ID in the template, enter in the binary name and add your binary inside the /ProjectName/autolipo/Binary folder and simply "make package" to generate and get everything ready. Also, the template does not include the latest version of the postinst so please update it manually.

Thanks to @ for writing the tutorial.

Note: There's also a simple edition version which you can try out.

--Techarmor-- · November 24, 2015

Thanks

And @DiDA how can you upload files on iosddl?

Rexsan · November 24, 2015

idk what this is for but ok...

Zahir · November 24, 2015

Awesome #prud+1

NitroxicDemon · November 24, 2015

awesome tut mate

Diversityy · November 24, 2015

/prune

Good job booss!

zzmorg82 · November 24, 2015

Kizzy · November 24, 2015

nice job

cu_rry · November 24, 2015

Awesome DiDA!

Gh0stByte · November 24, 2015

I guess posting binary hacks is a thing again, I wonder how the devs will react when they discover you are distributing their game's binary.. Not too happy i'd guess