Related
I just got my Droid 4 off of Ebay, and I'm going back to Android after 5 long years of Windows Phone. Rooted and installed the latest version of Safestrap that lets us used the (now)unused partitions. Seeing the lack of ROM diversities, My question is: Which ROM should I install? xD
All the Marshmallow ones and the Lollipop one I tried where really slow after installing just a few apps. So I went back to 4.1.2. There is a KitKat one that I'd like to try but the links are dead. I also found a thread suggesting to modify the booting of Cyanogen 12 with apparently good results, but I didn't look too much into how to do that.
Tbh I'd love something like SFOS but it looks like it's being worked on right now. So it might be a while till it's ready for daily usage, if it's ever brought to that point. :/
peter768 said:
I just got my Droid 4 off of Ebay, and I'm going back to Android after 5 long years of Windows Phone. Rooted and installed the latest version of Safestrap that lets us used the (now)unused partitions. Seeing the lack of ROM diversities, My question is: Which ROM should I install? xD
All the Marshmallow ones and the Lollipop one I tried where really slow after installing just a few apps. So I went back to 4.1.2. There is a KitKat one that I'd like to try but the links are dead. I also found a thread suggesting to modify the booting of Cyanogen 12 with apparently good results, but I didn't look too much into how to do that.
Tbh I'd love something like SFOS but it looks like it's being worked on right now. So it might be a while till it's ready for daily usage, if it's ever brought to that point. :/
Click to expand...
Click to collapse
Hello,
I'm using stock one JB 4.1.2, heavy debloated and overclocked. You can add some functionality from other roms by instaling xposed.
I recommend the latest Lineage 13.0 ROM. This is my daily driver and it's amazing.
I also have Mentors' debloated Stock ROM for dualboot, in case I ever need it. The biggest contra of the Stock ROM is the extremely bad GPU performance. It can't even display Snapchat because there are graphical errors everywhere. It also stutters while scrolling in a lot of apps.
These problems are all gone with CM13. I played through Red Dwarf on it and the game worked smooth as butter, with some nice, detailed graphics. Get an overclocked kernel from the forums here, while you're at it.
You should also never use the Stock ROM as the main system, because it lacks years of updates and has severe security holes in it.
schmatzler said:
I recommend the latest Lineage 13.0 ROM. This is my daily driver and it's amazing.
I also have Mentors' debloated Stock ROM for dualboot, in case I ever need it. The biggest contra of the Stock ROM is the extremely bad GPU performance. It can't even display Snapchat because there are graphical errors everywhere. It also stutters while scrolling in a lot of apps.
These problems are all gone with CM13. I played through Red Dwarf on it and the game worked smooth as butter, with some nice, detailed graphics. Get an overclocked kernel from the forums here, while you're at it.
You should also never use the Stock ROM as the main system, because it lacks years of updates and has severe security holes in it.
Click to expand...
Click to collapse
I tried Lineage with an overclocked kernel yesterdat but it was still quite laggy. I also couldn't install the google apps due to insufficient space. Did you do anything else? Also I'm on cdma so I stayed away from Mentor's ROMs.
Instead of the original GAPPS, I'm using:
- XPosed
- the FakeGapps module for XPosed
- the MicroG Play Services from here
- and the Google Play Store. Got the APK from apkmirror, installed it, copied the files from /data/app/com.android.vending to /system/priv-app/com.android.vending and chmodded the files to 644 and directories to 755 (this has to be done, otherwise the Play Store cannot login).
This is a bit of work, but it runs much faster and doesn't drain my battery as fast as the original GAPPS do. The last step isn't even required, you can use FakeStore or BlankStore instead and just get all your applications from apkmirror if you want it.
Bonus feature: You can now use Google Maps with the Apple NLP backend.
schmatzler said:
Instead of the original GAPPS, I'm using:
- XPosed
- the FakeGapps module for XPosed
- the MicroG Play Services from here
- and the Google Play Store. Got the APK from apkmirror, installed it, copied the files from /data/app/com.android.vending to /system/priv-app/com.android.vending and chmodded the files to 644 and directories to 755 (this has to be done, otherwise the Play Store cannot login).
This is a bit of work, but it runs much faster and doesn't drain my battery as fast as the original GAPPS do. The last step isn't even required, you can use FakeStore or BlankStore instead and just get all your applications from apkmirror if you want it.
Bonus feature: You can now use Google Maps with the Apple NLP backend.
Click to expand...
Click to collapse
I tried to follow this, but Google Play Store crashes. When I run the app, the Google Account is created, but thats it, I cannot run Play Store. Do you have any advice?
It still works fine for me with the same instructions posted above.
Maybe you have a different version of the PlayStore? Mine is from here and doesn't crash:
http://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-7-8-32-release/
You may have to kill the app after the first login and open it again so you can accept the EULA, though. Otherwise you'll get a connection error.
(Useful: 5 second back button killing in the developer options.)
If it still doesn't work:
- Open up the microG Settings and check if signature spoofing is indeed enabled
- Open up Xposed and check if the FakeGapps module is activated. If it isn't, activate it and reboot.
---
A completely different, even more lightweight method to get PlayStore and microG working:
1. Flash the latest LOS13 ROM.
2. Enable ADB debugging on the device and connect it via USB to your PC.
3. Install adb and python on your PC and run the Tingle application (cmd.exe: "python main.py")
This will patch the installed ROM on the fly and replace a system file. It enables signature spoofing, which means fake Google Play Services will run WITHOUT XPosed. No XPosed means even more free resources on the device.
The rest of the instructions is unchanged:
4. Get the MicroG Play Services from here
5. Get the Google Play Store from apkmirror, install it, copy the files from /data/app/com.android.vending to /system/priv-app/com.android.vending and chmod the files to 644 and directories to 755 (this has to be done, otherwise the Play Store cannot login).
This method is a lot more extensive, especially on Windows systems where you'll have to install ADB and make it visible in the system path. You'll also have to install python manually. A pain. Much easier on a Linux system.
But it's the only method to make it work on LOS14 at the moment, because there is no XPosed for Android 7 out yet AND the only method for people who don't want to use XPosed.
Just FYI, maybe this helps someone.
peter768 said:
There is a KitKat one that I'd like to try but the links are dead.
Click to expand...
Click to collapse
You can get CM11 and other CyanogenMods for Droid 4 here - http://web.archive.org/web/20161226224516/http://download.cyanogenmod.org/?device=maserati.
peter768 said:
Tbh I'd love something like SFOS but it looks like it's being worked on right now. So it might be a while till it's ready for daily usage, if it's ever brought to that point. :/
Click to expand...
Click to collapse
You can get Sailfish OS for Motorola Droid 4 here - https://talk.maemo.org/showthread.php?t=99031.
It's not 100% stable but worth trying out (though not as daily driver for me).
Of course using Safestrap you can have more than one ROM installed on the device so you can follow the development of each ROM/OS you are interested in.
For example I have CM11 as my daily driver, stock ROM in case of problems (didn't have to start it until now) and Sailfish OS to look on its development.
schmatzler said:
You may have to kill the app after the first login and open it again so you can accept the EULA, though. Otherwise you'll get a connection error.
(Useful: 5 second back button killing in the developer options.)
.
Click to expand...
Click to collapse
Many thanks, this was the issue. Works perfectly also with newer play store version.
After some frustration with LOS13 (Bluetooth not working, laggy performance) I'm using now Mokee ROM (with FakeGapps for Xposed). Workes nicely, especially I appreciate the Aegis app for controlling app behaviour (autorun, wakelocks, background services, hibernate, broadcasts). Restarting the phone every 2nd day prevents performance lags which build up slowly.
a module ?
Xposed rootless for example, at each Snapchat logon i have to deactivate/activate it, and each deactivation it's a full dalvik remake (1h).
And the switch toggle of Xposed doesn't work for SafetyNET or SnapChat, so the module have to be deactivated
It's impossible and too long !
So i don't use XPosed and don't make Update of module !
pingopower said:
a module ?
Xposed rootless for example, at each Snapchat logon i have to deactivate/activate it, and each deactivation it's a full dalvik remake (1h).
And the switch toggle of Xposed doesn't work for SafetyNET or SnapChat, so the module have to be deactivated
It's impossible and too long !
So i don't use XPosed and don't make Update of module !
Click to expand...
Click to collapse
Easy, everything has to be optimized for Xposed. But... I don't have long boot time on my device. Activate and deactivate Xposed in magisk is very quick for me. Normal boot time for both. Moto e4 on nougat 7.1.1. so it may be something specific to your device or Android version. Your device may just be very slow optimizing. Do you have a ton of apps installed? Because that makes optimization even longer. It is a very resource intensive operation.
No other modules should have that besides Xposed. Like I said, Xposed MUST optimize EVERYTHING.
pingopower said:
a module ?
Xposed rootless for example, at each Snapchat logon i have to deactivate/activate it, and each deactivation it's a full dalvik remake (1h).
And the switch toggle of Xposed doesn't work for SafetyNET or SnapChat, so the module have to be deactivated
It's impossible and too long !
So i don't use XPosed and don't make Update of module !
Click to expand...
Click to collapse
I don't know why the switch inside Xposed dont work for you. It worked for me when I used Marshmallow.
But what happens about the dalvik is that Xposed is a very complex and extended modification that can hook (and therefore alter) pretty much every app on your device. So when you "remove" or "install" it by enabling or disabling the module on magisk a dalvik wipe is triggered by the system the next time you boot.
The process is similar to when you systemize an app or updates your device, but instead of one or few apps to recompile, the system has to recompile (aka "optimize") most, if not all the apps on your system.
On Marshmallow specially, the Android uses an Ahead Of Time (AOT) compiler, meaning that all this compilation will occur on next boot, before the rest of the system can be used. To fix this problem, Google started using Just In Time (JIT) compiler from Nougat on, meaning that the optimization will occur when and if necessary, and if possible when the device is idle or not being intensely used. That's why in Nougat or Oreo this problem does not happen.
First I made a full backup because I didn't think it would work. You should too if you're going to attempt it.
- I patched my rom's services.jar using the Smali Patcher found HERE, enabling the option for signature spoofing in the app
- I pushed the resulting magisk module to my sdcard
- I flashed the module in magisk (using magisk 19.4-736729f5), rebooted, and confirmed that signature spoofing was working using Signature Spoofing Checker
- I downloaded the microg unofficial installer found HERE, making sure it was available on my sdcard for flashing
- I booted into TWRP recovery, mounted the System partition, and using the file manager found under "Advanced", I deleted Google Play Services, Google Services Framework, and Google Play Store from my /system/priv-app directory (I had already deleted Chrome, Play Movies/Music, Duo, etc. a long time ago, so I'm not sure if that's necessary for this to work)
- I went back to the main menu and installed the microg unofficial installer and rebooted the phone
- microg settings was now visible in my launcher, so i opened it and enabled device registration.
- I opened the the patched Play Store app provided by the microg unofficial installer and added my account when prompted
- I downloaded a previously purchased app to test if the app purchases could be validated. It was successful.
That's it. I read a lot of posts claiming that microg wouldn't work on OxygenOS, but I've been using it for 2 1/2 days now with no issues. UnifiedNLP still doesn't work unless you use the xposed module, but this seems to be an issue on every android pie rom that i've tried so far.
UPDATE:
Due to request, I uploaded my generated Magisk module which replaces services.jar with a patched version as requested. It was generated from OOS 9.5.11.
Please be aware that I cannot guarantee it will be compatible with your particular setup
Thanks for this, will give this a try , cheers.
Just a warning, I noticed I'm not passing safetynet after doing this. I've personally never encountered a situation where safetynet is relevant, but I know it'a a concern for a lot of you. I'll let you know if I figure out what's triggering it.
Hi,,may u share your service jar or signature spoofing magisk module here?
I managed to get UnifiedNlp working on custom ROMs. The culprit is the 'NLP Combo feature' commit present in all major OnePlus 7 Pro ROMs' frameworks/base. I made a custom build with this patch and backported Q animations in LineageOS if anyone is interested.
https://forum.xda-developers.com/oneplus-7-pro/development/rom-lineageos-16-microg-support-t3960116
muphetz said:
Hi,,may u share your service jar or signature spoofing magisk module here?
Click to expand...
Click to collapse
Done. Check original post for attachment.
bsimpson1 said:
Done. Check original post for attachment.
Click to expand...
Click to collapse
Tks,,its work with stock oss 9.5.11,,signature checking was enabled,,
Anyone know how to get UnfiedLP working on 10.0.3 without edexposed?
One word ahead: I am a huge fan of Custom Rom (LOS). Nevertheless some feature will be missed (volte) and performance might be not perfect (camera, dolby) due to proprietary firmware.
On the other hand I like to keep away from data collecting companies as google.
Isn't than a rooted and debloated stock image with microG instead of Gapps the best possible option? I did this once for an older Samsung and results was fine. But there is one thing I don't know: How it will act on updates. I don't want to miss security updates.
Any ideas? Or is it a bad idea at all? Curious to your feedback
I will extend this posts. Not only writing a step by step howto, but also explain the ideas behind. Maybe also some steps aside, mistakes I did.
So for the first steps look https://forum.xda-developers.com/t/...est-performance-privacy.4240057/post-84573619
EDIT Mai 1st 2021:
I get for some time a second phone and did some experiments. From what I see new - there is no real need to go the long, long way to root it. Even on a stock RAM you get get back control over your data!
The gapps are less important than I ever thought. If you get curious, just switch over here to get more information:
https://forum.xda-developers.com/t/...est-performance-privacy.4240057/post-84909643
(To avoid misunderstandings: I will not provide a ROM. There are some steps to go with existing stock ROM - as only this gives you full features.)
Isn't than a rooted and debloated stock image with microG instead of Gapps the best possible option?
Click to expand...
Click to collapse
I will assume you are comparing it with the latest LOS available.
Privacy-wise? Not really. Even if you remove GApps from the stock rom, Samsung will still collect data. You can limit that by:
1. Not using Samsung Account/Pay/Pass (as on why, read privacy policy)
2. Removing "com.hiya.star", which collects your location, tho it will break the "Places" feature in the Phone app.
3. Replacing Samsung Keyboard with an open-source alternative or disabling the autocorrect feature as it sends corrected texts to Samsung.
4. Not using Samsung Weather app/widget (as on why, read privacy policy)
After that and using some F-Droid apps I would say you have a pretty decent privacy.
Performace-wise? Absolutely. The battery life is a lot better compared to AOSP ROMs and thats not even taking into account that OneUI has the Ultra Power Saving Mode. The camera is miles ahead too and of course, VoLTE actually works.
How it will act on updates. I don't want to miss security updates.
Click to expand...
Click to collapse
I have tested that. If its just a security update, then it will install flawlessly. If its a feature update, some bloatware and Gapps may reinstall. I haven't experienced any update failing, but that may change in the future.
Any ideas? Or is it a bad idea at all? Curious to your feedback
Click to expand...
Click to collapse
If you really care about privacy, but dont want to miss out on features, then go ahead with debloating and degoogling the stock rom. Just note that some problems with compatibility and some rare random crashes may occur.
Retrecd said:
...
1. Not using Samsung Account/Pay/Pass (as on why, read privacy policy)
2. Removing "com.hiya.star", which collects your location, tho it will break the "Places" feature in the Phone app.
3. Replacing Samsung Keyboard with an open-source alternative or disabling the autocorrect feature as it sends corrected texts to Samsung.
4. Not using Samsung Weather app/widget (as on why, read privacy policy)
After that and using some F-Droid apps I would say you have a pretty decent privacy.
Click to expand...
Click to collapse
Sure, that was the ideas to remove as much of Google/Samsung stuff as possible and also use AFWall to limit data transfer. I am using FDroid already, there are good tools, respecting privacy.
So you went already same approach? There is already a thread about debloating, but I think what I want to do is even behind that. If you like, you can share more details. I would like create some kind of a howto ...
starbright_ said:
Sure, that was the ideas to remove as much of Google/Samsung stuff as possible and also use AFWall to limit data transfer. I am using FDroid already, there are good tools, respecting privacy.
So you went already same approach? There is already a thread about debloating, but I think what I want to do is even behind that. If you like, you can share more details. I would like create some kind of a howto ...
Click to expand...
Click to collapse
Here is an article on using ADB to remove bloatware: https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Now here is a list of bloatware on the S10, remove it the way showcased in the article: https://forum.xda-developers.com/t/galaxy-s10-s10-debloat-bloatware-removal-list.3912073/
The list is a bit older, but most of the bloatware is still present in the latest version.
The same way you removed the bloatware, you remove the Gapps. Remove the following core Google packages:
Code:
com.google.android.gsf
com.android.vending
com.google.android.gms
If you want to remove more packages that aren't listen in the article install the "App Inspector" from Google Play or any APK site and find out the names of the packages.
Please read and share your ideas. I am sure that we only together can create the best possible solution. Maybe you know othere ways/apps to solve a problem. As of now I share my point of view.
My hope is, that at the end of this to have an "howto" covering as many aspects as required for this.
First thing nevertheless is install TWRP/Magisk, which seems to be more tricky than usual.
While you can debloat your ROM without root, there are imho 3 reasons for doing that:
microG needs be installed as a system-app to have working location service (get your location by GPS or by offline database)
you will have problems to install a firewall and adblocker. There are solution with don't need root (Netguard and Blockada), but both base on a "virtual" VPN connection and you can have only one at a time. So you do have either a Firewall or an AdBlocker, but not both.
The way of create and restore backups are much better with root. I can recommend TWRP itself for a general backup and migrate for apps/settings.
For those like me, coming from unrooted stock fw the recommendation is to
root with Magisk - details here
flash the TWRP - details here
spoofing the signature for usage of microG instead of playservices
install microG and "friends"
debloat stock ROM
migrate data from old to new device
starbright_ said:
First thing nevertheless is install TWRP/Magisk, which seems to be more tricky than usual.
Click to expand...
Click to collapse
Tricky indeed and even more tricky is installing updates. Once you know the procedure it's ok, but it is still a major hassle compared to a stock OTA update.
here
jelbo said:
Tricky indeed and even more tricky is installing updates. Once you know the procedure it's ok, but it is still a major hassle compared to a stock OTA update.
Click to expand...
Click to collapse
Sure, I am aware of that. I just read about it. But there is no other way except you are happy with stock. First time is always a nightmare, but I hope once get used to it.
Retrecd said:
Here is an article on using ADB to remove bloatware: https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Now here is a list of bloatware on the S10, remove it the way showcased in the article: https://forum.xda-developers.com/t/galaxy-s10-s10-debloat-bloatware-removal-list.3912073/
The list is a bit older, but most of the bloatware is still present in the latest version.
The same way you removed the bloatware, you remove the Gapps. Remove the following core Google packages:
Code:
com.google.android.gsf
com.android.vending
com.google.android.gms
If you want to remove more packages that aren't listen in the article install the "App Inspector" from Google Play or any APK site and find out the names of the packages.
Click to expand...
Click to collapse
How did you managed that switch from Gapps to microG? I assume if you delete Gapps without MicroG installed you will get lot of problems.
How did you manage to spoof Stock Rom? Are you on 11?
Hi all. Very interesting conversation. Has someone successfully used microG on stock rom on a daily usage? In my past experience, using microG without signature spoofing is making a lot of apps not working properly...
lp35 said:
Hi all. Very interesting conversation. Has someone successfully used microG on stock rom on a daily usage? In my past experience, using microG without signature spoofing is making a lot of apps not working properly...
Click to expand...
Click to collapse
I think spoofing is a must have. I just evaluate how this can be done.
With Android 11 it is more difficult. I found that one (but not sure whether signature spoofing works):
https://forum.xda-developers.com/t/module-smali-patcher-7-3.3680053
this one:
https://forum.xda-developers.com/t/signature-spoofing-on-unsuported-android-11-r-roms.4214143/
or via NanoDroidPatcher
https://forum.xda-developers.com/t/...7-microg-pseudo-debloat-f-droid-apps.3584928/
It says:
11.0 / SDK 30 (R)
Patcher does not work from TWRP
Patcher works from Magisk if your ROM's services.jar already contains classes.dex
I checked that and /service/framework/service.jar contains that classes.dex
So I give this a try, downloaded the patcher and started it out of Magisk. Log looks ok so far. It requires reboot.
The problem with enabling Magisk is - you have to boot with "recovery" mode - and not sure, it fails several time (although USB is plugged) or phone reboots again and than Magisk is disabled - while booting into TWRP still works.
So my guess is: This causes some problem.
Step 3) - Spoofing
Have been successful:
I followed that thread:
Signature Spoofing on unsuported Android 11 (R) Roms
How to get Signature Spoofing working on Android 11 (R) Roms that have no support for Signature Spoofing? In my Case here I use a Samsung Galaxy S8 with an unofficial LineageOS 18.1 (Android 11) by stricted I use TWRP recovery but this should...
forum.xda-developers.com
But I just created a spoof_AVDapi30.zip. My thinking just flashing that one for spoofing seems to be wrong. Also flashing both: spoof and microG_AVD....
So what I did was flashing out of Magsik (Module install out of memory) NanoDroid-microG-23.1.2.20210117.zip and followed by spoof_AVDapi30.zip.
Power off. And take care you boot with Power + Vol+ + Bixby + USB Cable pressed until you see the splash-screen.
I really hope stock + MicroG takes off!
It is already. I started debloating - that is another step. See this thread:
Debloating S10e
I am still in testing phase and I would like to see once an FW-update via OTA will happen. Curious what will happen with my system.
starbright_ said:
It is already. I started debloating - that is another step. See this thread:
Debloating S10e
I am still in testing phase and I would like to see once an FW-update via OTA will happen. Curious what will happen with my system.
Click to expand...
Click to collapse
Amazing! Keep us posted!
Debloating is done.
Final step is takeover of my previous installation. I do that with the tool/app migrate. That works rather fine.
I am not using the special sections to export contacts, SMS ...
Contacts will be exported from the app itself and than imported in new device.
Is this dead? Hehe
No it is working. Have you tried that?
I couldn't deinstall com.samsung.android.kgclient and blocking its UID (with awfall) causes some battery drain. Maybe I have to live with not blocking this.
Anyhow, I am wondering whether debloating is required at all. Cutting the connection to Ethernet (to not talk "home") might be enough.
I don't not have enough understanding of what will be better: remove or just block.
A removed app might not spend time on connecting servers again and again, while a missed service can cause trouble if you don't expect that.
Probably it is best to uninstall apps you are really sure there are no dependencies to others and block the others-
starbright_ said:
Step 3) - Spoofing
Have been successful:
I followed that thread:
Signature Spoofing on unsuported Android 11 (R) Roms
How to get Signature Spoofing working on Android 11 (R) Roms that have no support for Signature Spoofing? In my Case here I use a Samsung Galaxy S8 with an unofficial LineageOS 18.1 (Android 11) by stricted I use TWRP recovery but this should...
forum.xda-developers.com
But I just created a spoof_AVDapi30.zip. My thinking just flashing that one for spoofing seems to be wrong. Also flashing both: spoof and microG_AVD....
So what I did was flashing out of Magsik (Module install out of memory) NanoDroid-microG-23.1.2.20210117.zip and followed by spoof_AVDapi30.zip.
Power off. And take care you boot with Power + Vol+ + Bixby + USB Cable pressed until you see the splash-screen.
Click to expand...
Click to collapse
So just install those inside of magisk and reboot? I'll give it a shot.
Dead thread, I see.
steventorres said:
Dead thread, I see.
Click to expand...
Click to collapse
What are you continuously posting about dead thread? Any question or any feedback? Strange. It is is all set and done. What do you expect?
@VenfefulRat:
This wasn't a real question, right. It was stated to do it out of magsik. It would be great to have some feedback.
@All: A forum lives from reading (to gain knowlegde ) and posting (sharing experience, ask questions, give feedback). If someone ask and he gets answer I would expect a feedback or at least a like (as a sign it has been read). Otherwise people stop posting and the only left here are those who ask or feed the troll.
microG works great until a paid app tries to verify the license or when it comes to in app purchases. Using existing tools like NanoDroid and microG Installer Revived has disadvantages (see Readme below). That's why I created a Magisk module that replaces FakeStore with a patched version of the PlayStore. After installing the module, licenses can be verified and even in-app-purchases are possible with microG.
Visit on Github or download v0.1 directly.
Readme:
FakeStore 2 PlayStoreThis is a Magisk module that replaces FakeStore with the patched Play Store by Nanolx and is mainly intended to be used with LineageOS for microG, which already ships with microG and FakeStore. I only tested it on LineageOS 18.1 for microG. Use at your own risk, if you are on a different ROM.
The module uses fixed permissions settings from nift4's microG Installer Revived. Additionally it adds the Nanolx's NanoDroid companion F-Droid repository to F-Droid for automatic updates of the patched Play Store.
Why you want to use itYou want to have License Verification and In-App-Purchases with microG and already have a system with microG + FakeStore (like LineageOS for microG)
Installation
Install LineageOS for microG
Install Magisk
Install the module through the Magisk Manager App
Important: Do NOT flash in TWRP, you need to use the Magisk app and have an active internet connection for downloading the patched PlayStore.
NanoDroid or microG Installer Revived already do the job, don't they?Yes and no. After several tries with combinations of LineageOS 18.1, Lineage OS 18.1 for microG, NanoDroid and microG Installer Revived, I always ended up with either an unbootable system or with configurations that don't survive OTA upates or that would render microG upgrades useless or install too much.
NanoDroid's patcher (currently?) isn't able to successfully patch signature spoofing into LOS 18.1 and I didn't want to fiddle around with deodexing. My intention was to have a ready-to-use solution for LineageOS that survives OTAs. So I had to use LOS for microG, which already has the signature spoofing patch. However installing the patched PlayStore in LOS 18.1 for microG using NanoDroid always resulted in an unbootable system - even when disabling every other feature in .nanodroid-setup and hiding FakeStore with .nanodroid-overlay.
Though microG Installer Revived does a better job (the system was bootable after installing the patched PlayStore , it isn't able to hide FakeStore on it's own. So I had to still hide FakeStore somehow. Additionally microG Installer Revived installs DroidGuard as a system app, which is not what I wanted. Furthermore, it overwrites GmsCore with it's own version and therefor any OTA updates by LineageOS for microG would've been overwritten by the Installer's version.
That said, it's possible to use NanoDroid's .nanodroid-overlay feature to hide FakeStore in combination with microG Installer Revived to install the patched PlayStore and live with the DroidGuard and OTA issues. But I decided to make a Magisk module that does no more than replacing FakeStore with a patched version of PlayStore. Here it is.
BuildLinux, BSD, macOS, AndroidRequires wget.
wget -O META-INF/com/google/android/update-binary https://raw.githubusercontent.com/topjohnwu/Magisk/master/scripts/module_installer.sh && zip fakestore2playstore.zip -9r *
OtherDownload this and put it into META-INF/com/google/android/update-binary. And ZIP it.
Credits
Nanolx for the PlayStore patch.
nift4 for microG Installer Revived
wait does this still use the google play in-app purchase dialogue or are in-app purchases just free now?
MirageSteezyBoi said:
wait does this still use the google play in-app purchase dialogue or are in-app purchases just free now?
Click to expand...
Click to collapse
Negative, nothing is for free! Otherwise it'd be considered warez! This means, this modificated Google Play Store allows you to make the same purchases like the "normal" play store despite the lack of Google Play Services and the use of µG.
Oswald Boelcke said:
Negative, nothing is for free! Otherwise it'd be considered warez! This means, this modificated Google Play Store allows you to make the same purchases like the "normal" play store despite the lack of Google Play Services and the use of µG.
Click to expand...
Click to collapse
cool. works great. vouch
now this is helpful - thank you for releasing this!
for me only worked the one to download directly (1.0). generating or updating the zip like described led to "unzipping failed" message in magisk. i don't know, where the pitfall could be, just mentioning this here.
klaasklever said:
now this is helpful - thank you for releasing this!
for me only worked the one to download directly (1.0). generating or updating the zip like described led to "unzipping failed" message in magisk. i don't know, where the pitfall could be, just mentioning this here.
Click to expand...
Click to collapse
Thanks for reporting. However, I double checked the build steps and ended up with the same file as the released one. I guess it doesn't have to do anything with fakestore2playstore, but may be due to your "zip" executable. In fact, Magisk also complains about the unzipping progress itself. Anyway, I'm happy you find this module helpful!
You should check out https://github.com/FriendlyNeighborhoodShane/MinMicroG_releases they already include the same PatchedPhonesky along with a minimal microG setup similar to the revived version from the Magisk repo, all in one package.
As for signature spoofing and all that if your ROM doesn't support it the easiest way is to use f0mey's Smali Patcher:
[MODULE] Smali Patcher 7.4
Smali Patcher WHAT THE HELL IS THIS THING? :: To sum things up this is an application I developed that pulls the android framework from your device, applies what I (or other users) consider useful patches to the sourced files and then...
forum.xda-developers.com
Thank you a big bunch. Very easy to install, and works pretty good. Some paid apps can't be installed for some reaaon, but you can install them with means, and the licence verification later works! Which is the main point.
I've been using this on 3 phones running gappless + microG. All with different custom ROMs and it appears to work wonderfully for license verification on the few apps I have paid for - except one (titanium backup). FWIW 2 are running A10 and one A11.
Thank's to the developer for this useful app!
It used to work for me, but after I reset my phone a few days ago and tried to install the module again I get error message "download failed and installation failed". I use /e/os (a fork of Lineage OS 18.1) on a Galaxy S10+ and Magisk 24.3. Any ideas?
thegreekfreak said:
It used to work for me, but after I reset my phone a few days ago and tried to install the module again I get error message "download failed and installation failed". I use /e/os (a fork of Lineage OS 18.1) on a Galaxy S10+ and Magisk 24.3. Any ideas?
Click to expand...
Click to collapse
Fixed in fakestore2playstore-0.2.zip
The wget version that ships with the busybox provided by Magisk 24 somehow can't download the patched playstore from Nanolx's repository. The server closes the connection because of a tls error. Now the patched playstore is included in this module and a download isn't required any more.
By the way: I'm on Android 12 now, but the Playstore doesn't work properly. Seems like some permissions/settings are missing. Unfortunately I'm quite busy currently and can't look into this deeper right now. Hope to find some sparetime soon.
sn00x said:
Fixed in fakestore2playstore-0.2.zip
The wget version that ships with the busybox provided by Magisk 24 somehow can't download the patched playstore from Nanolx's repository. The server closes the connection because of a tls error. Now the patched playstore is included in this module and a download isn't required any more.
By the way: I'm on Android 12 now, but the Playstore doesn't work properly. Seems like some permissions/settings are missing. Unfortunately I'm quite busy currently and can't look into this deeper right now. Hope to find some sparetime soon.
Click to expand...
Click to collapse
Please fix Android 12 issue! Please!
Hello, your module is running perfetcly on my device. Thanks!
But I'm still have some questions. Is it possible to install the Original PlayStore with microG installed?
I might have the exact case described here (LOS 18.1 for MicroG), but this does work perfectly. Thanks a lot
Well, doesn't work on Android 12+... Any chance for an update ? This was really a neat module :/
lPolarisl said:
Well, doesn't work on Android 12+... Any chance for an update ? This was really a neat module :/
Click to expand...
Click to collapse
I made it work again, but can't really remember how... first thing is enable network access for playstore in app-setting, it was disabled by default. also, try microG_Installer_Revived-Revived_3.0.0. and mess around with it, somehow it turns out ok ...
Jackson Karloff said:
I made it work again, but can't really remember how... first thing is enable network access for playstore in app-setting, it was disabled by default. also, try microG_Installer_Revived-Revived_3.0.0. and mess around with it, somehow it turns out ok ...
Click to expand...
Click to collapse
It works... Can't believe I missed that, that was all, network access was disabled x(
Thanks a lot, I had completely given up on this !
@sn00x In case you're still around... I now have trouble with your module, for some reason, it installs fine and the Play Store's there on the first reboot, but after the second reboot, it still shows up as active in the Magisk module list, but no Play Store app to be found, only FakeStore...
IodéOS, Android 12