Lucky Patcher

For Example, You have an app which requires license
Verification and it denies you access if you did not actually
purchase it and that you just downloaded it off the web.
Then, Lucky Patcher might be the solution for you.
( Credits to Chelpus for creating this wonderful app )
Download Lucky Patcher here ( The App Needs ROOT
access to work )
Guidelines and legends ( If you don’t understand the
colours )
Green – This program has a great chance to become
registered;
Yellow – custom patch in folder /sdcard/LuckyPatcher/ Present
Cyan – Google Ads Present
Magenta – This program is in BootList;
Impossible – This program has no chance of becoming a
registered. The exception is the application of two parts
(Application and APK-Pro-Key). In such cases, patch both sides
or either one of them.;
Orange – System Application. Be very careful when performing
any operations with them, it could end very badly for
Application or Operating System.;
BootList – a list of programs that will patch the boot device. At
this point, it is used only for Applications that require the
correction of libraries “.so” But custom patches do not exist,
except for the old Titanium backup, which is no longer in use.;
Star – means that dalvik-cache applications have been fixed
(ODEX with Changes created), and this in turn means that the
application will remain in its current state until the first update,
or deletion of the application. If such ODEX removed with
“Remove ODEX with Changes”, then the application will be
fully restored to the state before the patch. When you update
an application, problems can arise: the market will swear that
it had not enough space, run Lucky Patcher and close and try
to install the application again, if such an error is written to the
uninstalled application,select the settings Luckypatcher
“Troubleshooting->Remove fixes and backups (to update app)
” – all fixes dalvik-cache for all programs will be removed;
Rewritten Chelpus’s original explaination. Some sentences in
original did not make sense, Corrections done. 🙂
Instructions For use
Remove License Verification:
– ONLY Use target’s original apk files signed by the developer;
– Tap the Software and select “Remove License Verification!”;
– Select “Auto mode” and test Application with Internet;
– If the result is negative, Select “Extreme Auto mode”;
– If you’re lucky, your program will be registered;
– To return Application to its original state, you need to tap
“Remove ODEX with Changes”.
Remove Google Ads:
– Tap the Software and select “Remove Google Ads!”;
– Run and test Application with Internet;
– If you’re lucky, Google Ads will disappear;
– To return Application to its original state, you need to tap
“Remove ODEX with Changes”.
Custom Patch:
– Tap the Software and select “Custom Patch!”;
– Run and test Application with Internet;
– If you’re lucky, patch works;
– To return Application to its original state, you need to tap
“Remove ODEX with Changes”.
Change Permissions:
– Be very careful doing this. Since on some devices, this
method can lead to a circular reboot or other undesirable
consequences. Make a backup system before you try to disable
permission. – Tap the Software and select “Change
Permissions”;
– Tap to Permission for disable (red);
– Tap to Permission for enable (green);
– You must tap Apply (Reboot).
Creating Modified APK:
– Tap the Software and select “Create Modified APK”;
– Select Patch for Modification of APK;
– Modified installation file will be in folder /sdcard/LuckPatcher/
Modified/ ;
– You should know that a rebuilt apk-file is not the same as
installing custom patches to the application. As opposed to
simply patching the application, it is very easy to test the
changes yourself, and thus work correctly so hopefully, the
install will not..
PS: Patcher closes the application, when making
patches. This is necessary so that the new changes are
implemented. But sometimes you may need to restart
the device itself or use third-party tools to kill the
process of Applications.
This part was rewritten as there were mistakes in grammar
and meaning.
Information was taken from Chelpus’s website and improved
the explanation. Credits belong solely to him.