guorui21036
Platinian
Nice
Tutorial How to install unsigned APK on NON-rooted devices
- Thread starter AndnixSH
- Start date
qwqer12388
Rookie
升you
Muhammad Adnan
Platinian
Do you have to keep installing LuckyPatcher even though you have installed VMOS?
What do you mean?
You have to install Lucky Patcher IN Vmos to be able to patch the Android in VMOS to use unsigned Versions.
When you patched your android in vmos you can delete lucky patcher when you want, the patches will still be applied.
VMOS root works on my Vivo V9 Pro OS 8.1. Thanks for your tutorial. But there is a problem with the unsigned mod apk after overwritten the original one, I can’t still log in into Google Play Games. The mod apk just started from zero.
Note: All necessary patches were applied.
Thank you.
Note: All necessary patches were applied.
Thank you.
The modder may have signed it by accident. Ask the modder to check the apk file
I did try the unsigning trick also by opening the apk file, move lib folder, delete original lib, and move it back to the apk folder but still no avail. Thanks @AndnixSH
SaeedRaouf
Solid & Active Platinian
Where is Vmos file location at internal storage i need file location
For what do you need a File Location?
To import or export data you use the file explorer inside vmos and nothing else
If you can't install unsigned APK, Install signed APK on top of original version without having to uninstall it
Your save data will be intact and Google login will still work until you reboot your device. Some games still logged in as Google even after it doesn't work, but don't log out because you can't login again until you install original APK
It does not work that way on me. After installing either unsigned or signed mod APK over original, the game starts from zero. All game data in OBB file (Original) was replaced by the new OBB (Mod). Between both OBB files are not replaceable because they have different built numbers like 200xxx for original and 100xxx for mod version. This problem only occurs for games with OBB.
Your save data will be intact and Google login will still work until you reboot your device. Some games still logged in as Google even after it doesn't work, but don't log out because you can't login again until you install original APK
It does not work that way on me. After installing either unsigned or signed mod APK over original, the game starts from zero. All game data in OBB file (Original) was replaced by the new OBB (Mod). Between both OBB files are not replaceable because they have different built numbers like 200xxx for original and 100xxx for mod version. This problem only occurs for games with OBB.
Sadly some games like to release multiple builds separetely.
In this case the modder downloaded 100xxx version to be compatible with his device while you downloaded 200xxx to be compatible with your device
You can ask the modder to mod the other build version or try to find build version that match with modded apk
I did some experiment though by matching build numbers of the game, this one from Game Developer Ltd. like Modern Strike. I downloaded from Apkpure with build numbers 100xxx to match the one from mod apk so both have 100xxx. After installing it, I login to Google Play. Close the game and install the mod version that had unsigning processes. Yes, I tried two different way. First, by moving lib folder and second, by replacing metadata. Again, after overwriting the original apk, the mod version still can not login to Google Play. It looks like only happened to certain games, tried other game from different developer; It works ?. Thanks.
- Tags
- google play games google play services implementation microg unsigned apk virtual machine virtualxposed vmos