How to create unsigned APK file for rooted devices + signature check disabled (fix Google & FB login)
Why unsigned APK, and why is it recommended for most games? With an
unsigned APK, you can install the APK over the original. You can login with
your Google+ account without signature error, and login with your Facebook
account without uninstalling Facebook app. No more login not working complains!





7. Enjoy
By using the method described, consider to NOT add new files or remove existing files on the APK, it will break compatibility with Lucky Patcher. For example, along with your mod you need to add a file into the APK, let say in "assets/myfile.dat". It won't work and lead to failure during APK installation. Another example, if you deleted "lib/arm64-v8a" out of the APK. Again, it causing installation failure.
This is because all file structures in the APK was mapped and their info
was stored in "META-INF/CERT. SF" file. The solution is you need to
put all your mods along with expected APK file structures in the compiled APK,
sign it (with any desired key), then pull the "META-INF/CERT.SF" from
this newly signed APK to be used as replacement for the old one at your working
APK. However, this trick will not work with new signature scheme for Lucky
Patcher anyway because the developer refused to improve it, you need to use
CorePatch, It is way better than Lucky Patcher and open source
Missing
.RSA, .SF, or .MF?
It is because
APK is using signature scheme v2 and above, don’t worry about it yet. For some
reason, .RSA, .SF, or .MF are available if you download split APK/XAPK from
Apkcombo or Apkpure. If Google login is not work, try copy entire contents from
signed APK to original APK except META-INF
I want
Lucky Patcher support!
Unfortunately,
he never reply to me no matter how many times I asked him for fix. If you want,
you can try ask him via mail [email protected]
or 4pda
Comments
Post a Comment