castix

We are not Apple Support. They have an extra section just for Purchase issues

iAPFree has that but idk what the dev did to prevent that >.<

This is one of the easiest games to hack i suggest you hack it yourself

Yay, I just wanted to tell you how to fix the crash but you figured it out

It's always All Versions if not specified

Requirements Cydia Substrate PreferenceLoader Features Unlimited Gems (Complete a challenge) Unlimited Coins (Complete a race) Free Challenge Skips Free Ability Charge Jenga Unlocked High Score Unlimited Powerups (Requires some gems first) Unlimited Ability Time Instructions Download my hack, open it with iFile and press 'installer'. Enable the cheats from preferences. Download [Hidden Content] Credits castix

Have you thought about buying it .. It seems the tweak is smarter than you

There are some tweaks to fast forward in apps but other way is impossible

Why should I

Requirements Cydia Substrate PreferenceLoader Features Unlimited Ammo Unlimited Grenades No Flinch God Mode (only campaign and local) Unlimited Accuracy No Recoil Show FPS More EXP (100 EXP) One Hit Kill No Spread Speedhack Instructions Download my hack, open it with iFile and press 'installer'. Enable the cheats from preferences. Download [Hidden Content] Credits castix

Yep what @DiDA said

- (void)example:(BOOL)fp8 { return %orig(true); } - (void)example:(id)fp8 { NSLog(@"Test !"); %orig; }

http://AutoTouch.me/repo

You can get sudo from Cydia

What is a Debian control file Specifics regarding the contents of a Debian control file are provided in the Debian Policy Manual Briefly, a sample control file is shown below for the Debian package Test: Package: Test Priority: optional Section: devel Installed-Size: 45 Maintainer: castix <[email protected]> Architecture: iphoneos Version: 1.3-16 Depends: libc6 (>= 2.1) Description: The classic greeting, and a good example The GNU hello program produces a familiar, friendly greeting. It allows nonprogrammers to use a classic computer science tool which would otherwise be unavailable to them. Seriously, though: this is an example of how to do a Debian package. It is the Debian version of the GNU Project's `hello world' program (which is itself an example for the GNU Project). The Package field gives the package name. This is the name by which the package can be manipulated by the package tools, and usually similar to but not necessarily the same as the first component string in the Debian archive file name. The Version field gives both the upstream developer's version number and (in the last component) the revision level of the Debian package of this program. The Architecture field specifies the chip for which this particular binary was compiled. The Depends field gives a list of packages that have to be installed in order to install this package successfully. The Installed-Size indicates how much disk space the installed package will consume. This is intended to be used by installation front-ends in order to show whether there is enough disk space available to install the program. The Section line gives the "section" where this Debian package is stored at the Debian FTP sites. The Priority indicates how important is this package for installation, so that semi-intelligent software like dselect or aptitude can sort the package into a category of e.g. packages optionally installed. The Maintainer field gives the e-mail address of the person who is currently responsible for maintaining this package. The Description field gives a brief summary of the package's features. What is a Debian conffile Conffiles is a list of configuration files (usually placed in `/etc') that the package management system will not overwrite when the package is upgraded. This ensures that local values for the contents of these files will be preserved, and is a critical feature enabling the in-place upgrade of packages on a running system. To determine exactly which files are preserved during an upgrade, run: dpkg --status package And look under "Conffiles:". What is a Debian preinst, postinst, prerm, and postrm script These files are executable scripts which are automatically run before or after a package is installed. Along with a file named `control', all of these files are part of the "control" section of a Debian archive file. The individual files are: preinst This script executes before that package will be unpacked from its Debian archive (".deb") file. Many 'preinst' scripts stop services for packages which are being upgraded until their installation or upgrade is completed (following the successful execution of the 'postinst' script). postinst This script typically completes any required configuration of the package `foo' once `foo' has been unpacked from its Debian archive (".deb") file. Often, 'postinst' scripts ask the user for input, and/or warn the user that if he accepts default values, he should remember to go back and re-configure that package as the situation warrants. Many 'postinst' scripts then execute any commands necessary to start or restart a service once a new package has been installed or upgraded. prerm This script typically stops any daemons which are associated with a package. It is executed before the removal of files associated with the package. postrm This script typically modifies links or other files associated with `foo', and/or removes files created by the package. Currently all of the control files can be found in directory `/var/lib/dpkg/info'. The files relevant to package `foo' begin with the name "foo" and have file extensions of "preinst", "postinst", etc., as appropriate. The file `foo.list' in that directory lists all of the files that were installed with the package `foo'. (Note that the location of these files is a dpkg internal; you should not rely on it.) What is an Essential, Required, Important, Standard, Optional, or Extra package Each Debian package is assigned a priority by the distribution maintainers, as an aid to the package management system. The priorities are: ▪ Required: packages that are necessary for the proper functioning of the system. This includes all tools that are necessary to repair system defects. You must not remove these packages or your system may become totally broken and you may probably not even be able to use dpkg to put things back. Systems with only the Required packages are probably unusable, but they do have enough functionality to allow the sysadmin to boot and install more software. ▪ Important packages should be found on any Unix-like system. Other packages which the system will not run well or be usable without will be here. This does NOT include Emacs or X or TeX or any other large applications. These packages only constitute the bare infrastructure. ▪ Standard packages are standard on any Linux system, including a reasonably small but not too limited character-mode system. Tools are included to be able to browse the web (using w3m), send e-mail (with mutt) and download files from FTP servers. This is what will install by default if users do not select anything else. It does not include many large applications, but it does include the Python interpreter and some server software like OpenSSH (for remote administration), Exim (for mail delivery, although it can be configured for local delivery only), an identd server (pidentd) and the RPC portmapper (`portmap'). It also includes some common generic documentation that most users will find helpful. ▪ Optional packages include all those that you might reasonably want to install if you did not know what it was, or do not have specialized requirements. This includes X, a full TeX distribution, and lots of applications. ▪ Extra: packages that either conflict with others with higher priorities, are only likely to be useful if you already know what they are, or have specialized requirements that make them unsuitable for "Optional". If you do a default Debian installation all the packages of priority Standard or higher will be installed in your system. If you select pre-defined tasks you will get lower priority packages too. Additionally, some packages are marked as Essential since they are absolutely necessary for the proper functioning of the system. The package management tools will refuse to remove these. What is meant by saying that a package Depends, Recommends,Suggests, Conflicts, Replaces, Breaks or Provides another package The Debian package system has a range of package "dependencies" which are designed to indicate (in a single flag) the level at which Program A can operate independently of the existence of Program B on a given system: ▪ Package A depends on Package B if B absolutely must be installed in order to run A. In some cases, A depends not only on B, but on a version of B. In this case, the version dependency is usually a lower limit, in the sense that A depends on any version of B more recent than some specified version. ▪ Package A recommends Package B, if the package maintainer judges that most users would not want A without also having the functionality provided by B. ▪ Package A suggests Package B if B contains files that are related to (and usually enhance) the functionality of A. ▪ Package A conflicts with Package B when A will not operate if B is installed on the system. Most often, conflicts are cases where A contains files which are an improvement over those in B. "Conflicts" are often combined with "replaces". ▪ Package A replaces Package B when files installed by B are removed and (in some cases) over-written by files in A. ▪ Package A breaks Package B when both cannot packages cannot be simultaneously configured in a system. The package management system will refuse to install one if the other one is already installed and configured in the system. ▪ Package A provides Package B when all of the files and functionality of B are incorporated into A. This mechanism provides a way for users with constrained disk space to get only that part of package A which they really need. What is meant by Pre-Depends "Pre-Depends" is a special dependency. In the case of most packages, `dpkg' will unpack its archive file (i.e., its `.deb' file) independently of whether or not the files on which it depends exist on the system. Simplistically, unpacking means that `dpkg' will extract the files from the archive file that were meant to be installed on your file system, and put them in place. If those packages depend on the existence of some other packages on your system, `dpkg' will refuse to complete the installation (by executing its "configure" action) until the other packages are installed. However, for some packages, `dpkg' will refuse even to unpack them until certain dependencies are resolved. Such packages are said to "Pre-depend" on the presence of some other packages. The Debian project provided this mechanism to support the safe upgrading of systems from `a.out' format to `ELF' format, where the order in which packages were unpacked was critical. There are other large upgrade situations where this method is useful, e.g. the packages with the required priority and their LibC dependency. As before, more detailed information about this can be found in the Policy manual. What is meant by unknown, install, remove, purge and hold in the package status These "want" flags tell what the user wanted to do with a package (as indicated either by the user's actions in the "Select" section of `dselect', or by the user's direct invocations of `dpkg'). Their meanings are: ▪ unknown - the user has never indicated whether he wants the package ▪ install - the user wants the package installed or upgraded ▪ remove - the user wants the package removed, but does not want to remove any existing configuration files. ▪ purge - the user wants the package to be removed completely, including its configuration files. ▪ hold - the user wants this package not to be processed, i.e., he wants to keep the current version with the current status whatever that is. How do I install a source package Debian source packages can't actually be "installed", they are just unpacked in whatever directory you want to build the binary packages they produce. Source packages are distributed on most of the same mirrors where you can obtain the binary packages. If you set up your APT's sources.list(5) to include the appropriate "deb-src" lines, you'll be able to easily download any source packages by running apt-get source foo To help you in actually building the source package, Debian source package provide the so-called build-dependencies mechanism. This means that the source package maintainer keeps a list of other packages that are required to build their package. To see how this is useful, run apt-get build-dep foo before building the source. How do I build binary packages from a source package The preferred way to do this is by using various wrapper tools. I'll show how it's done using the `devscripts' tools. Install this package if you haven't done so already. Now, first get the source package: apt-get source foo and change to the source tree: cd foo-* Then install needed build-dependencies (if any): sudo apt-get build-dep foo Then create a dedicated version of your own build (so that you won't get confused later when Debian itself releases a new version) dch -l local 'Blah blah blah' And finally build your package debuild -us -uc If everything worked out fine, you should now be able to install your package by running sudo dpkg -i ../*.deb If you prefer to do things manually, and don't want to use `devscripts', follow this procedure: You will need all of foo*.dsc, foo*.tar.gz and foo*.diff.gz to compile the source (note: there is no .diff.gz for some packages that are native to Debian). Once you have them, if you have the `dpkg-dev' package installed, the following command: dpkg-source -x foo_version-revision.dsc will extract the package into a directory called `foo-version'. If you want just to compile the package, you may cd into `foo-version' directory and issue the command dpkg-buildpackage -rfakeroot -b to build the package (note that this also requires the `fakeroot' package), and then dpkg -i ../foo_version-revision_arch.deb to install the newly-built package(s). As always thanks for reading, castix

Hello everyone, I'm castix but this thread is not about introducing myself. Instead, I am going to show you debian packages, their appearance in Linux and Unix systems and how they are related to the deb packages you already know from your iDevice. What is Debian GNU Debian GNU/Linux is a particular distribution of the Linux operating system, and numerous packages that run on it. Debian GNU/Linux is: Full featured Debian includes more than 37400 software packages at present. Users can select which packages to install; Debian provides a tool for this purpose. You can find a list and descriptions of the packages currently available in Debian at any of the Debian mirror sites Free to use and redistribute There is no consortium membership or payment required to participate in its distribution and development. All packages that are formally part of Debian GNU/Linux are free to redistribute, usually under terms specified by the GNU General Public License. The Debian FTP archives also carry approximately 187 software packages (in the `non-free' and `contrib' sections), which are distributable under specific terms included with each package. Dynamic With about 990 volunteers constantly contributing new and improved code, Debian is evolving rapidly. The FTP archives are updated twice every day. Most Linux users run a specific distribution of Linux, like Debian GNU/Linux. However, in principle, users could obtain the Linux kernel via the Internet or from elsewhere, and compile it themselves. They could then obtain source code for many applications in the same way, compile the programs, then install them into their systems. For complicated programs, this process can be not only time-consuming but error-prone. To avoid it, users often choose to obtain the operating system and the application packages from one of the Linux distributors. What distinguishes the various Linux distributors are the software, protocols, and practices they use for packaging, installing, and tracking applications packages on users' systems, combined with installation and maintenance tools, documentation, and other services. Debian GNU/Linux is the result of a volunteer effort to create a free, high-quality Unix-compatible operating system, complete with a suite of applications. The idea of a free Unix-like system originates from the GNU project, and many of the applications that make Debian GNU/Linux so useful were developed by the GNU project. For Debian, free has the GNUish meaning (see the Debian Free Software Guidelines). When we speak of free software, we are referring to freedom, not price. Free software means that you have the freedom to distribute copies of free software, that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. The Debian Project was created by Ian Murdock in 1993, initially under the sponsorship of the Free Software Foundation's GNU project. Today, Debian's developers think of it as a direct descendent of the GNU project. Although Debian GNU/Linux itself is free software, it is a base upon which value-added Linux distributions can be built. By providing a reliable, full-featured base system, Debian provides Linux users with increased compatibility, and allows Linux distribution creators to eliminate duplication of effort and focus on the things that make their distribution special. How does the Debian project fit in or compare with the Free Softwaren Foundation's GNU project The Debian system builds on the ideals of free software first championed by the Free Software Foundation (http://www.gnu.org/) and in particular by Richard Stallman (http://www.stallman.org/). FSF's powerful system development tools, utilities, and applications are also a key part of the Debian system. The Debian Project is a separate entity from the FSF, however we communicate regularly and cooperate on various projects. The FSF explicitly requested that we call our system "Debian GNU/Linux", and we are happy to comply with that request. The FSF's long-standing objective is to develop a new operating system called GNU, based on Hurd (http://www.gnu.org/software/hurd/). Debian is working with FSF on this system, called Debian GNU/Hurd (http://www.debian.org/ports/hurd/). How does one pronounce Debian and what does this word mean The project name is pronounced Deb'-ee-en, with a short e in Deb, and emphasis on the first syllable. This word is a contraction of the names of Debra and Ian Murdock, who founded the project. (Dictionaries seem to offer some ambiguity in the pronunciation of Ian (!), but Ian prefers ee'-en.) How source code compatible is Debian with other Unix systems For most applications Linux source code is compatible with other Unix systems. It supports almost everything that is available in System V Unix systems and the free and commercial BSD-derived systems. However in the Unix business such claim has nearly no value because there is no way to prove it. In the software development area complete compatibility is required instead of compatibility in "about most" cases. So years ago the need for standards arose, and nowadays POSIX.1 (IEEE Standard 1003.1-1990) is one of the major standards for source code compatibility in Unix-like operating systems. Linux is intended to adhere to POSIX.1, but the POSIX standards cost real money and the POSIX.1 (and FIPS 151-2) certification is quite expensive; this made it more difficult for the Linux developers to work on complete POSIX conformance. The certification costs make it unlikely that Debian will get an official conformance certification even if it completely passed the validation suite. (The validation suite is now freely available, so it is expected that more people will work on POSIX.1 issues.) Unifix GmbH (Braunschweig, Germany) developed a Linux system that has been certified to conform to FIPS 151-2 (a superset of POSIX.1). This technology was available in Unifix' own distribution called Unifix Linux 2.0 and in Lasermoon's Linux-FT. How can I check that I am using a Debian system, and what version is it? In order to make sure that your system has been installed from the real Debian base disks, use the lsb_release -a command. It will display the name of the distribution (in Distributor ID field) and the version of the system (in Release and Codename fields). The following is an example run in a Debian system: $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 7.4 (wheezy) Release: 7.4 Codename: wheezy You can also check for the existence of `/etc/debian_version' file, which contains a single one-line entry giving the version number of the release, as defined by the package `base-files'. Users should be aware, however, that the Debian system consists of many parts, each of which can be updated (almost) independently. Each Debian "release" contains well defined and unchanging contents. Updates are separately available. For a one-line description of the installation status of package `foo', use the command `dpkg --list foo'. To view versions of all installed packages, run: dpkg -l For a more verbose description, use: dpkg --status foo Note that the existence of the program `dpkg' shows that you should be able to install Debian packages on your system. However, since the program has been ported to many other operating systems and architectures, this is no longer a reliable method of determining is a system Debian GNU/Linux. How does Debian support non-English languages Debian GNU/Linux is distributed with keymaps for nearly two dozen keyboards, and with utilities (in the `kbd' package) to install, view, and modify the tables. The installation prompts the user to specify the keyboard he will use. ▪ Vast majority of the software we packaged supports entering non-US-ASCII characters used in other Latin languages (e.g. ISO-8859-1 or ISO-8859-2), and a number of programs support multi-byte languages such as Japanese or Chinese. ▪ Currently, support for German-, Spanish-, Finnish-, French-, Hungarian-, Italian-, Japanese-, Korean-, Dutch-, Polish-, Portuguese-, Russian-, Turkish-, and Chinese-language manual pages is provided through the `manpages-LANG' packages (where LANG is the two-letter ISO country code). To access an NLS manual page, the user must set the shell LC_MESSAGES variable to the appropriate string. For example, in the case of the Italian-language manual pages, LC_MESSAGES needs to be set to 'italian'. The `man' program will then search for Italian manual pages under `/usr/share/man/it/'. What is a Debian package Packages generally contain all of the files necessary to implement a set of related commands or features. There are two types of Debian packages: Binary packages, which contain executables, configuration files, man/info pages, copyright information, and other documentation. These packages are distributed in a Debian-specific archive format; they are usually distinguished by having a '.deb' file extension. Binary packages can be unpacked using the Debian utility `dpkg' (possibly via a frontend like `aptitude'); details are given in its manual page). Source packages, which consist of a `.dsc' file describing the source package (including the names of the following files), a `.orig.tar.gz' file that contains the original unmodified source in gzip-compressed tar format and usually a `.diff.gz' file that contains the Debian-specific changes to the original source. The utility `dpkg-source' packs and unpacks Debian source archives; details are provided in its manual page. (The program `apt-get' can get used a frontend for `dpkg-source'.) Installation of software by the package system uses "dependencies" which are carefully designed by the package maintainers. These dependencies are documented in the `control' file associated with each package. For example, the package containing the GNU C compiler (`gcc') "depends" on the package `binutils' which includes the linker and assembler. If a user attempts to install `gcc' without having first installed `binutils', the package management system (dpkg) will send an error message that it also needs `binutils', and stop installing `gcc'. (However, this facility can be overridden by the insistent user.) Debian's packaging tools can be used to: ▪ manipulate and manage packages or parts of packages, ▪ administer local overrides of files in a package, ▪ aid developers in the construction of package archives, and ▪ aid users in the installation of packages which reside on a remote FTP site. What is the format of a Debian binary package A Debian "package", or a Debian archive file, contains the executable files, libraries, and documentation associated with a particular suite of program or set of related programs. Normally, a Debian archive file has a filename that ends in `.deb'. The internals of this Debian binary packages format are described in the deb manual page. This internal format is subject to change (between major releases of Debian GNU/Linux), therefore please always use dpkg-deb if you need to do lowlevel manipulations on `.deb' files. As always thanks for reading, castix

Because it works you abused it

They work, I tested them .. you must have done something wrong

Open source is not free to take. It's just for people to see what code was used in a program and how to apply some code. You can view it if you need help or don't understand something but it's not allowed to copy code without permissions. All Github repositories are copyrighted if not licensed

"from some code I found on Github that bypasses ptrace and I can PM it to you" I doubt you're allowed to

Yay the servers will eat shit and go hell down because of all the traffic from kids who can now get the game.

That's kinda pointless because Kleptocracy is right. That would be a custom request because the base is unique.

Clutch detects all your apps. The display names are the binary names and not of the app itself

What o_0

Watch the video again and install everything which is shown