microG
I am no longer working on this, or updating any information here! This was created back in the day of Oreo.
I've personally moved on and I'm presently using /e/ which you can see the info here and get the ROM for OP5T.
/e/OS documentation - OnePlus 5T
Info about OnePlus 5T - dumpling
As of this post edit on 10/20/22 I'm using 'e-1.4-r-20220922220394-dev-dumpling' and /e/ uses microg. It runs quite nice, so check it out!
microG is Freedom, Security & Privacy from Google, by replacing the Google Services & Framwork, also improving phone and battery performance!
This guide shows you the steps needed to Deodex, Signature Spoofing, Debloat Gapps and install microG.
This is not just a OxygenOS guide, this works on any ROM with Gapps baked in, lack signature spoofing, or doesn't come with microG installed! The only areas specific to OxygenOS is using Xposed and the microG permissions, both which might not be needed on other ROMs, everything else you follow in this guide for any ROM.
The information is here to give you a complete understanding of the process, it's just the Android way is all! Without the information and only steps to follow, there are a lot of areas you could experience problems, and not know how to deal with them.
There is no shorter, or easier way to accomplish this, if there was I would of made a smaller quickie guide, this is the way it works in Android! If you want to do microG you're going to have to read, it looks like a lot but it's not, once you've done it a few times!
Remember, the information is here to help you!
Pie is not supported in Xposed, and at the present moment OxygenOS requires Xposed.
You need to WIPE and install the ROM and start fresh, otherwise it can get complicated, you've been warned! You also need to follow the steps exactly, do not deviate, the process is picky, that is why the steps are to be done this way!
When you go online for the first time do not allow any Google updates! Do not install any Gapps, or anything, other than what is mentioned in this guide!
Keep online time limited to the steps needed in this guide. Connect only to accomplish what is needed and keep an eye out for Google updates and cancel them!
I highly recommend making TWRP backups every step of the way, in case of a mistake, then you don't have to start all over!
Once you get the steps down, the entire process takes around 30-60 minutes to complete!
Each of the RED sections are the STEPS, just read and follow them one by one!
DEODEX OR FAKEGAPPS
For stock or custom roms that don't support signature spoofing, you can either deodex the rom with the VDEXEXTRACTOR steps and use the Nanodroid-patcher to apply signature spoofing, or use the Xposed FakeGapps module which enables signature spoofing support.
If you use an application called "Signature Spoofing Checker" with the Xposed FakeGapps module installed and it shows the support disabled, ignore it. FakeGapps is working, it's a bug in the "Signature Spoofing Checker". 5.1.5 shows Green/Enabled and 5.1.6 shows Red/Disabled.
If you use the Xposed FakeGapps module skip to the [MAGISK] SYSTEMLESS XPOSED section! If you know how to compile for vdexExtractor, there is no reason to use FakeGapps!
VDEXEXTRACTOR
This method shown below is a simple Deodex that NanoDroid uses. SuperR's Kitchen also uses vdexExtractor, but instead does a Full Deodex. The NanoDroid method is simpler, without the need for SuperR's Kitchen. I plan on eventually adding a method of using SuperR's Kitchen to the guide at some point in time.
This NanoDroid Deodex method shown here is good, it's just not a Full Deodex, it hurts nothing, it's not better or worse, just different! So, if you aren't concerned with needing/wanting the full customization capability that a Full Deodex offers, or you have no idea of what is being said here, then don't worry!
ROMs that are either in a state of VDEX or ODEX need to be DEODEX in order to apply Signature Spoofing! So depending on the ROM, check to find out which state it is in, and then you will apply either the VDEX or ODEX methods outlined in this guide; https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md
In this guide for OxygenOS you will be following the VDEX method. OxygenOS follows the VDEX method because it has both .odex and .vdex files in the system.
You will have to compile the vdexExtractor source on either Windows, MacOS, or Linux, this guide doesn't cover compiling.
At the end of this section where you download vdexExtractor on GitHub, under the Dependencies section being mentioned there, this is a brief explanation of that information to help get you started.
This is only the basics explained to help get you now moving in the right direction for compiling. If you have any other concerns or questions please search on Google, there is a wealth of information online to help you.
1. macOS users will need to compile by installing Homebrew https://brew.sh/ and adding the dependency zlib-devel as brew install zlib-devel. Then you should be able to use the terminal in macOS to run the command, ./make.sh gcc or sh make.sh gcc to now compile.
2. For Linux users you need to make sure you have libz-dev installed and then at a terminal run either, ./make.sh gcc or sh make.sh gcc to compile.
3. For Windows users you'll need to install cygwin, https://www.cygwin.com/ cygwin helps to give you a Unix/Linux like build environment. Make sure to install zlib-devel from the cygwin installer, it should be listed under the Devel section which you click it so it changes from the word Default to Install, if you don't see zlib-devel listed there, then search for it. There is a lot of information online about installing and using cygwin, hopefully this link below is still working fine for Windows 10 to help you setup the Cygwin Path to the Windows Environment Variable, to make it easier to use the command prompt to compile from. In Windows you'll also run the commands, either ./make.sh gcc or sh make.sh gcc to compile.
Install Cygwin and How to Use Linux Commands in Windows with Cygwin
https://www.howtogeek.com/howto/41382/how-to-use-linux-commands-in-windows-with-cygwin/
If compiling is a problem you can always use the Xposed FakeGapps module, but it's best to DEODEX/PATCH the ROM!
Learn to compile, you'll be better off for it in the long run, switch to Linux it makes the process of compiling a lot easier than any other OS.
Be sure to look at the vdexExtractor Github for basic compile information, where you'll download the source; https://github.com/anestisb/vdexExtractor
NANODROID PATCHER
Download the NanoDroid-patcher; https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Download from Stable Download (Nanolx) - As of to date it's version NanoDroid-patcher-20.2.20181122.zip
DEODEX SETUP
Boot to TWRP and mount the /system read-write.
Once you have mounted the /system in TWRP run these commands on your computer to deodex!
DEODEX COMMANDS
Code:
adb pull /system/framework framework
cp framework/services.jar services.jar-backup
vdexExtractor -i framework/oat/arm64/services.vdex --ignore-crc-error
mv framework/oat/arm64/services_classes.dex classes.dex
zip framework/services.jar classes.dex
zip -j framework/services.jar classes.dex
adb push framework/services.jar /system/framework
adb shell
chmod 644 /system/framework/services.jar
chown root:root /system/framework/services.jar
SIGNATURE SPOOFING
Unmount the /system read-write - TWRP > Mount > uncheck System
Install the NanoDroid-patcher in TWRP. (This takes around 10 minutes!)
If you did the deodex correctly, when flashing NanoDroid-patcher it will say Deodex.
When the patch has completed reboot the phone.
[MAGISK] SYSTEMLESS XPOSED
Xposed does not pass SafetyNet!
Download [Magisk] Systemless Xposed - XposedInstaller_3.1.5-Magisk.apk; https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
MAGISK ROOT
Boot to TWRP and install Magisk to root your phone.
Reboot the phone and update Magisk.
MAGISK MODULES
Do not reboot until you have installed all three modules!
Install the Xposed Framework (SDK 27) - For Xposed to install, Systemless Xposed and Magisk need to be the only two things first installed in the rom!
Install the Debloater (Terminal Emulator) - Debloats the phone Systemlessly!
Install the F-Droid Privileged Extension - Read about it here; https://f-droid.org/en/packages/org.fdroid.fdroid.privileged/
After installing these three modules reboot your phone!
XPOSED MODULES
Open Xposed while connected online, it should be displaying in Green! If it is Red you might not of followed the steps correctly, especially the part about doing this on a "Fresh Clean ROM", and following the guide step by step.
Install FakeGapps if you did not deodex the rom, and then apply the signature spoofing NanoDroid-patch!
The XposedGmsCoreUnifiedNlP module will be installed later with microG, mentioned in the MICROG section!
If you installed FakeGapps, go to the Modules section and check the module to enable it, then reboot the phone.
F-DROID
You have basically 3 choices for applications; Aurora Store, F-Droid, Yalp Store.
For now I recommend you install F-Droid, download from https://f-droid.org/en/
After installing F-Droid go to Settings, toggle on Expert mode, make sure Privileged Extension is checked, close and reopen F-Droid and then update F-Droid if a new version is available!
You'll need a terminal emulator in Android because Debloater (Terminal Emulator) runs from the command line, it doesn't have a GUI. I recommend using Termux, it's a very powerful terminal emulator with many features.
Search for an install Termux!
DEBLOATING APPS SYSTEMLESSLY
Do not debloat the Google Play Store if you plan on using it!
Do not create/add a Google Account, it will only get removed when you debloat out Google, instead wait to the last section I WANT MY GOOGLE & STAY PRIVATE TOO, and add it after you have installed and setup microG!
If you want to keep some Gapps that's your choice! Be sure to run any Gapps that you want to keep before debloating. This is not always the common situation where you need to run Gapps before debloating, it's typically rare, but some odd applications will have a hard time working with microG if this isn't done. For applications you are not sure of, be sure to run them, especially applications that use Location, such as OnePlus Weather and the Camera, etc., before debloating!
Make sure you are connected online when you run Termux for the first time.
With Termux running, at the command prompt type su for superuser access and grant root access.
Type debloat and you'll remove from 1 - System Apps & 2 - System Priv-Apps.
Type the numbers with spaces in between for the applications you are debloating, as an example; 15 16 17.
When you have the applications typed in and you are ready to debloat, tap enter.
For the best Gapps Free experience debloat all of these;
Android Setup
Calendar
Chrome
Drive
Duo
Gboard
Gmail
Google
Google Backup Transport
Google One Time Init
Google Partner Setup
Google Pay
Google Play Movies
Google Play Music
Google Play Services
Google Play Store - (Do not debloat if you're going to use!)
Google Services Framework
Market Feedback Agent
Maps
Photos
On a note of Privacy, there's information online in regards to OnePlus and Analytics/Data Mining as it relates to the below applications.
I highly recommend that if you're serious about privacy to do your own research and judge for yourself, but if you're asking me I debloated all of them!
BugReportLite
EngSpecialTest
FactoryMode
Insight Provider
LogKitSdService
OnePlusLogKit
Oneplus System Service
RfToolkit
After debloating you are suppose to reboot your phone for the changes to take effect!
If you debloated Chrome, make sure you update the Android System WebView in either the Aurora Store or Yalp Store, after you've completed the installation of microG!
Make sure you debloated Gboard, be sure to install another keyboard before rebooting! I recommend installing AnySoftKeyboard from F-Droid!
If you make any mistakes, you have the option to reinstall applications!
Reboot the phone...
If any updates occurred, after debloating some Gapps might still appear in the system. These now turn into User-Installed applications, so either in the Settings > Apps > Application List, you'll have the option to uninstall, or if the application is in the App Drawer, you can now uninstall it from there!
If the Google Play Services is listed in the phone but no option shown to uninstall, follow the GMS PROBLEMS section! Regardless of what you see or don't see in the Application List be sure to still follow the GMS PROBLEMS section!
GMS PROBLEMS
Before installing microG you need to make sure this GMS directory com.google.android.gms is out of the system!
Run this command;
Code:
adb uninstall com.google.android.gms
If com.google.android.gms exists and you were able to remove it, you'll see this reply; Success
If you see a lot of output with this line, then you have no changes or updates installed, there's nothing to remove;
java.lang.IllegalArgumentException: Unknown package: com.google.android.gms
If com.google.android.gms exists and the Google Play Services is still active, you'll see this reply; Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
If the Google Play Services is still active you will have to manually remove com.google.android.gms.
Run these commands;
Code:
adb shell
su
cd /data/data
rm -rf com.google.android.gms
If you run rm -rf com.google.android.gms and get this reply back; rm: databases: Directory not empty, just run the command over!
Even if the command gave you a success response, or unknown package, be sure to visually check for the presence of com.google.android.gms in /data/data!
Exit and reboot your phone!
If you had to manually remove com.google.android.gms, go to the Settings > Apps > Application List > Three Dots (Upper Right) > Show system apps. If you see the Google Play Services uninstall it, the option to uninstall should now be available. Click uninstall and wait a few seconds for a popup to appear and click ok to remove.
microG creates com.google.android.gms, do not remove it after you have microG installed!
DALVIK CACHE & CACHE
Before installing microG, boot into TWRP and Wipe the Dalvik Cache and Cache!
When done wiping reboot the phone back into the system.
NANODROID-MICROG
At the present moment it is better to use the NanoDroid-microG version! Official microG is not getting as much development!
Visit the NanoDroid post on XDA;
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Down from the Stable Download (Nanolx) link!
If you use the NanoDroid-microG version, take the "FakeStore" "GmsCore" "GsfProxy" from the zip, look for them in the folders under /system/priv-app/ use the "GmsCore_NanoDroid" and "GsfProxy_NanoDroid" and be sure to rename them, and follow the MICROG steps below using these versions instead of the Offical microG!
MICROG
microG on stock Android sometimes take a little more effort with Gapps installed compared to custom roms without Gapps, but the process typically only involves dealing with the preinstalled Gapps and Google updates. Most of the time you only need to follow the GMS PROBLEMS steps outlined in the guide when running into problems.
If you debloat the Play Store and then later reinstall it, make sure you do not have FakeStore installed, Play Store will not go back in with FakeStore installed!
microG DroidGuard Helper is only required if you want to use applications that require SafetyNet or to test DroidGuard!
The microG UnifiedNlP package at this point in time is not supported in OxygenOS, for this reason the XposedGmsCoreUnifiedNlP Xposed module needs to be installed!
Open Xposed and install XposedGmsCoreUnifiedNlP, go to the Modules section, check the module to enable it!
Android 7 (or later) needs to have microG installed to the /system.
If you use the Official microG download FakeStore GmsCore GsfProxy! (It's higly recommened to use the Nanodroid-microG version!)
FakeStore - (Only needed if you're not using the Play Store)
https://github.com/microg/android_packages_apps_FakeStore/releases
GmsCore
https://github.com/microg/android_packages_apps_GmsCore/releases
GsfProxy
https://github.com/microg/android_packages_apps_GsfProxy/releases
Rename all the APK!
FakeStore.apk
GmsCore.apk
GsfProxy.apk
Create theses directory names and place the APK in them!
FakeStore
GsfProxy
GmsCore already has a directory in /system/priv-app!
Debloater (Terminal Emulator) places a file .replace in all the /system/priv-app directories that you debloated.
In GmsCore the contents of ".replace" is "Google%Play%Services", so that the Google Play Services apk doesn't populate the directory. If you were to remove or rename ".replace" and rebooted, you would see the actual Google Play Services GmsCore.apk in the directory!
Do not touch these hidden ".replace" files!
Because GmsCore already has a directory in /priv-app, copy the microG GmsCore.apk to your phone with a File Manager that gives you root access to /system/priv-app/GmsCore.
Do not adb push GmsCore.apk in TWRP, it will only get removed when you reboot!
Boot to TWRP and mount the /system read-write.
Use this command to push the directories for FakeStore and GsfProxy. - (FakeStore is only needed if you're not using the Play Store)
Code:
adb push FakeStore /system/priv-app
adb push GsfProxy /system/app
Make sure /system is still mounted in TWRP, then > Advanced > Terminal.
Run these commands to make sure you have the correct permissions! - (FakeStore is only needed if you're not using the Play Store)
Code:
chmod 755 /system/priv-app/FakeStore
chmod 644 /system/priv-app/FakeStore/FakeStore.apk
chown -R root:root /system/priv-app/FakeStore/FakeStore.apk
chmod 755 /system/priv-app/GmsCore
chmod 644 /system/priv-app/GmsCore/GmsCore.apk
chown -R root:root /system/priv-app/GmsCore/GmsCore.apk
chmod 755 /system/app/GsfProxy
chmod 644 /system/app/GsfProxy/GsfProxy.apk
chown -R root:root /system/app/GsfProxy/GsfProxy.apk
Do not update microG through Aurora Store or Yalp Store, only update through F-Droid!
If at any time there are any new updates, you'll need to follow the steps over for adb push, copying GmsCore, and the permissions for FakeStore - GmsCore - GsfProxy! Delete all the old APK first before copying and doing adb push!
If you use the Official microG Open F-Droid, Settings, tap on Repositories and add in the microG repo; https://microg.org/fdroid/repo so you can keep microG updated!
If you use NanoDroid-microG, in F-Droid, Settings, tap on Repositories and add in the NanoDroid-microG repo; https://nanolx.org/fdroid/repo/ so you can keep microG updated!
Unmount the /system read-write and reboot the phone.
MICROG SETUP
Open F-Droid and search for microg. The Network-based Geolocation choices are, Deja VU - MozillaNlPBackend - Local GSM Location. It's good to just install all three, or experiment to see which works best for you, either alone or in combination. For address lookup and to also test Geocoder, install NominatimNlPBackend.
Make sure WiFi, Mobile data, "Location ( Mode - High Accuracy)" are all turned on in the phone before opening microG!
Open microG, you'll notice at the top it says Permission missing, tap on this, tap on the words REQUEST MISSING PERMISSIONS and ALLOW all of them!
If your deodex went successful, or you went with FakeGapps, you should notice at the top System spoofs signature checked.
You should now only see two check marks missing at the bottom for Location backend(s) setup and UnifiedNlP do not have Location to test Geocoder.
Network-based location enabled should be checked if you didn't turn off Location in the Phone Settings.
Make sure Battery optimizations ignored is also checked!
To get Location working properly in microG, under Self-Check tap on Google device registration and toggle it ON.
Google device registration needs to be ON, when signing up or logging into your Account, or the Play Store for the first time, afterwards it can be turned OFF if you don't need Location support! If at any time an application doesn't run, trying turning Google device registration back ON to see if it helps.
Go to the phone Settings > Location and put the Mode on "High Accuracy".
In the "UnifiedNlP Settings" configure the "Network-based Geolocation" backends you just installed!
Under "Address lookup" for the NominatimNlPBackend, tap Choose Nominatim API Server and pick MapQuest! I recommend using MapQuest, you'll need to sign up for a free account at MapQuest to get an API key.
https://developer.mapquest.com/
When you get your key, tap on MapQuest Developer API Key and add it in.
The MapQuest API key only allows 15,000 transactions a month!
MICROG PERMISSIONS
To get UnifiedNlP do not have Location to test Geocoder checked in microG, you need to add these two permissions.
Code:
adb shell
su
pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
After adding the permissions reboot your phone.
If you go into the microG settings before it's updated the Location, you will still see UnifiedNlP do not have Location to test Geocoder unchecked. Go back out of Self-Check and wait a few seconds then check it again, sometimes you need to scroll up and down a few times too. After a few seconds your Location should be updated and everything should be checked.
This time you'll see it says Geocoder provides address resolution from location checked. Also scroll up and down for a few seconds, and this time under UnifiedNlP status you should have 6 sections now checked.
Over a period of time, depending on what you do, you might see UnifiedNlP do not have Location to test Geocoder become unchecked, if this happens just run the permissions over!
I WANT MY GOOGLE & STAY PRIVATE TOO
All of this just depends on your level of privacy and concerns in regards to Google!
If you debloated Chrome, before you can add a Google Account in the phone settings through microG, you need to update Android System WebView!
These steps below are only if you need paid applications through the Play Store! Free and paid applications can also be downloaded through Aurora Store and Yalp Store, F-Droid can only download free applications.
If you want to stay away from Google, you can use your Google Account on either Aurora Store or Yalp Store. Some paid applications with their License Checks might not work without being downloaded through the Play Store, or if the Play Store isn't installed, you'll have to test this out with various applications to see how they work.
Besides paid applications, system applications will also appear through Aurora Store and Yalp Store, so you can limit the time using the Play Store for privacy, and update everything through either Aurora Store or Yalp Store, possibly even paid applications too.
Aurora Store and Yalp Store violates ยง3.3 of Google Play Terms of Service, so your account could be disabled, but as it's mentioned on the Yalp Store site, they've never heard of any real cases of accounts being disabled.
https://github.com/yeriomin/YalpStore
https://gitlab.com/AuroraOSS/AuroraStore
To make this step of privacy work, you will need to create a Google account for the first time, because if you did it the normal way on your phone, then you have exposed your device, given up your carrier name, mobile or wifi ip address, geo location etc... If you signed up on a computer, depending on what you did, you might of also exposed yourself!
If you want to create your Google account on a computer, be sure to cover your tracks, like using a VPN!
If you need paid applications from the Play Store, create your Google account after you've done all the steps outlined in this guide for privacy!
Before you follow the steps, make sure Location is off, WiFi is off, Mobile Data is off, and switch the sim card! You do not need an active sim card to use the Play Store! With dual sims, deactivate the good one, and activate the dead/spoofed one! Make sure the spoofed sim card is also the sim card set as the default for the Phone, text, mobile data!
Follow these steps even if you are signing up through a computer, to make sure you are ready to sign into the Play Store on your phone you've prepared!
Every time you sign into the Play Store on your device, if you want privacy with as little attention drawn to the account, then you need to always connect to the Play Store with all of the same phone settings, sim card, etc., otherwise you will get a new device added to the account.
Make sure you never sign into a Google account using your real sim, wifi/mobile network IP, or Location on! Anything that can track you, make sure it's spoofed or off!
For the best Privacy use a VPN that does not log, then sign into the Play Store over wifi using this VPN! As an example you can also use some throw away sim card that you paid for by cash that has no trail to you, but remember the Carrier Network does place you locally! If Geo Locality is a concern, use a VPN!
It's also recommended to maintain the same network(s) and GEO location when signing into the Play Store!
If at anytime you want to update, or get more applications, follow the steps over repeating the process!
Here's a break down in the steps! - (1 - 4)
1. You can sign up for the Google account on your computer, then add it into your phone, but don't forget to follow step #2 when you add the account in the device.
2. When signing up or adding your Gmail/Google account on your device, use another sim card in your phone so the mobile network goes through a different carrier, or a spoofed sim card that doesn't work, or wifi over a VPN, Phone, text, mobile data all set on the spoofed sim card, Location is off! Make sure anything that can track you is off or spoofed!
3. If you are either signing up, or logging into your Account on your device, make sure Google device registration is ON in microG! This also needs to be ON the first time you log into the Play Store!
4. When you are done using the Play Store for the first time you can turn Google device registration OFF in microG, if you don't need phone Location! If at any time applications aren't working properly try turning Google device registration ON!
Be careful with the Account and Play Store on the phone, that you don't access either of them with anything that gives up your identity, as you can see there are a few things you could forget!
NANODROID PHONESKY
If at anytime you have problems with the original Play Store, you can get Phonesky.apk from NanoDroid-microG, it's a patched version to work with microG. Download it from Stable Download (Nanolx), it's located in the /system/priv-app/Phonesky directory.
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Copy Phonesky.apk with a File Manager to the Download directory.
Boot to TWRP and mount the /system read-write.
Rename the original Phonesky.apk in /priv-app to keep a backup, also so it won't run. Rename it like; Phonesky.bak - Phonesky.orig
In TWRP copy the Nanodroid version to /priv-app/Phonesky.
In TWRP > Advanced > Terminal, run this command to make sure you have the correct permissions on the Nanodroid version of Phonesky!
Code:
chmod 644 /system/priv-app/Phonesky/Phonesky.apk
Unmount the /system read-write and reboot the phone.
The Nanodroid version of the Play Store is now located in the App Drawer.
If Privacy is a concern, when you are done using the Play Store you can go to Settings > Apps > Application List > Google Play Store - Tap Disable to stop the Play Store from running, then you can Enable it later when you want to run it again! You do not need to debloat the Play Store! You can also tap Permissions and disable all of them!
Settings > Security & lock screen > Apps with usage access > Google Play Store > Permit usage access - Disable this for better privacy!
That's all there is to accomplishing microG on OxygenOS, Stock Android ROMs, and Custom ROMs!
>
>
>
If this post helped you in any way, please press the THANKS button!
Thank you for your time and effort with this detailed tutorial.
I understand every step except for the VDEX bit. Can I bypass this part? I don't use Playstore but one app (BT sport) after some updates refuses to work without it. Even on Lineage microG.
bluegrass55 said:
Thank you for your time and effort with this detailed tutorial.
I understand every step except for the VDEX bit. Can I bypass this part? I don't use Playstore but one app (BT sport) after some updates refuses to work without it. Even on Lineage microG.
Click to expand...
Click to collapse
BT Sport wants the Play Store in order to work?
For VDEX I mentioned it before, but this time I changed it to make it more noticeable.
Look back up at ---> DEODEX OR FAKEGAPPS
What computer OS you running?
DoR3M3 said:
BT Sport wants the Play Store in order to work?
For VDEX I mentioned it before, but this time I changed it to make it more noticeable.
Look back up at ---> DEODEX OR FAKEGAPPS
What computer OS you running?
Click to expand...
Click to collapse
Windows 8.1 Pro.
Yes BT sport needs to feel the presence of Playstore to work. Even though I'm not logged into Playstore, full restriction using XprivacyLua and blocked internet access via AFWall+. When on dedicated Lineage 15.1 microG it used to work. But not anymore.
Excelent guide, I run microg about 3,5 years, now with oxygen the only thing i miss is signature spoofing but I didn't have any problem except of some messages eg when opening tapatalk. Is there any way to deodex on macos?
Sent from my ONEPLUS 5T
vagkoun83 said:
Excelent guide, I run microg about 3,5 years, now with oxygen the only thing i miss is signature spoofing but I didn't have any problem except of some messages eg when opening tapatalk. Is there any way to deodex on macos?
Sent from my ONEPLUS 5T
Click to expand...
Click to collapse
Everything is mentioned in these steps, please look them over again, you can always use FakeGapps...
DEODEX OR FAKEGAPPS
VDEXEXTRACTOR
I made some changes to make it clearer. But if you went to the vdexExtractor Github, you would of seen mention of MacOS if you want to compile and DEODEX instead of FakeGapps.
bluegrass55 said:
Windows 8.1 Pro.
Yes BT sport needs to feel the presence of Playstore to work. Even though I'm not logged into Playstore, full restriction using XprivacyLua and blocked internet access via AFWall+. When on dedicated Lineage 15.1 microG it used to work. But not anymore.
Click to expand...
Click to collapse
Play Store is mentioned in the Guide, so if you need it, just follow these steps;
I WANT MY GOOGLE & STAY PRIVATE TOO
I would also suggest filing an Issue on the microG Github, maybe the microG DEVs will have some suggestions/ideas on how to do this without the Play Store;
https://github.com/microg/android_packages_apps_GmsCore
bluegrass55 said:
Windows 8.1 Pro.
Yes BT sport needs to feel the presence of Playstore to work. Even though I'm not logged into Playstore, full restriction using XprivacyLua and blocked internet access via AFWall+. When on dedicated Lineage 15.1 microG it used to work. But not anymore.
Click to expand...
Click to collapse
Managed to install this via the Fake Gapps route but it failed the Signature Spoofing check via the app from Fdroid. Flashed the NanoDroid Patcher which fixed it.
https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-19.1.1.20181103.zip
For some strange reason I still have Faceunlock function even with all Google stuff uninstalled.MicroG self test has everything ticked and Fdroid is working.
This was a test run on an already debloated stock 5.1.6 ROM. Will try again on a later date with clean fresh ROM as recommended. Looked into the Deodex thing again but still non the wiser on how to achieve it.
bluegrass55 said:
Managed to install this via the Fake Gapps route but it failed the Signature Spoofing check via the app from Fdroid. Flashed the NanoDroid Patcher which fixed it.
https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-19.1.1.20181103.zip
For some strange reason I still have Faceunlock function even with all Google stuff uninstalled.MicroG self test has everything ticked and Fdroid is working.
This was a test run on an already debloated stock 5.1.6 ROM. Will try again on a later date with clean fresh ROM as recommended. Looked into the Deodex thing again but still non the wiser on how to achieve it.
Click to expand...
Click to collapse
The 5.1.6 OTA is available for me to download, and I checked it, and it's VDEX!
Do you remember when you were installing the NanoDroid-patcher, at the beginning it said "Deodex"?
See the attached image where it says; services.jar status: VDEX this is on 5.1.5 & 5.1.6 showing that the ROMs have not be DEODEX yet. It needs to say; services.jar status: DEODEX in order for the Nanodroid-patcher to work...
I noticed too that the Signature Spoofing Checker shows "Disabled" in 5.1.6. microG shows the support, so it appears that the "Signature Spoofing Checker" has a bug and I'll remove it from the post until it can be fixed.
BT Sports is complaining about the Google Play Services, which is not the Play Store. So as I mentioned, just follow the last step of the Guide for the Play Store and see if BT Store works, and if not, make the Issue at the microG GitHub for help.
OB19 deodex possible?
deszczuXS said:
OB19 deodex possible?
Click to expand...
Click to collapse
Did you read the guide?
This is a microG guide for Android not just Oxygen...
But there are slight differences between ROMs, all you have to do is avoid all the OxygenOS parts for Android.
FakeGapps isn't supported in PIE, so if you use PIE then you have to DEODEX, otherwise you can use FakeGapps.
DoR3M3 said:
The 5.1.6 OTA is available for me to download, and I checked it, and it's VDEX!
Do you remember when you were installing the NanoDroid-patcher, at the beginning it said "Deodex"?
See the attached image where it says; services.jar status: VDEX this is on 5.1.5 & 5.1.6 showing that the ROMs have not be DEODEX yet. It needs to say; services.jar status: DEODEX in order for the Nanodroid-patcher to work...
I noticed too that the Signature Spoofing Checker shows "Disabled" in 5.1.6. microG shows the support, so it appears that the "Signature Spoofing Checker" has a bug and I'll remove it from the post until it can be fixed.
BT Sports is complaining about the Google Play Services, which is not the Play Store. So as I mentioned, just follow the last step of the Guide for the Play Store and see if BT Store works, and if not, make the Issue at the microG GitHub for help.
Click to expand...
Click to collapse
Thanks for the detailed reply.
Don't remember if it said "Deodex" at the beginning but about to have another ago as the phone is bootlooping. Using the Terminal Debloat I removed all the Google stuff but for some reason Google Services Framework and Google One Time Init were still was showing up in the system. Used Titanium, System Uninstall app and Root Browser to remove but without luck. Changed their permissions but ended up in bootloop.
bluegrass55 said:
Thanks for the detailed reply.
Don't remember if it said "Deodex" at the beginning but about to have another ago as the phone is bootlooping. Using the Terminal Debloat I removed all the Google stuff but for some reason Google Services Framework and Google One Time Init were still was showing up in the system. Used Titanium, System Uninstall app and Root Browser to remove but without luck. Changed their permissions but ended up in bootloop.
Click to expand...
Click to collapse
After a second attempt and reading the guide more carefully with fresh clean stock ROM have managed to do this. The only issue is these remaining Google things which were also present on my previous attempt even though I got rid of them with Terminal Debloat.
Regarding the BT sports app if I want to use it then microG isn't the way to go. It was a free offer but don't use it that much.
bluegrass55 said:
After a second attempt and reading the guide more carefully with fresh clean stock ROM have managed to do this. The only issue is these remaining Google things which were also present on my previous attempt even though I got rid of them with Terminal Debloat.
Regarding the BT sports app if I want to use it then microG isn't the way to go. It was a free offer but don't use it that much.
Click to expand...
Click to collapse
Try not to double post to keep things together...
I went back and edited the post over, with greater details, explaining, that if you Debloat and still see stuff in the system or app drawer, that is because of updates, but now all of these apps can be uninstalled, and that is what you do, manually uninstall them all from the Settings or App Drawer, it's also a reason for trying to do all this on a Clean ROM with no updates, otherwise you deal with this next.
Also for BT Sport, run it and set it all up on Clean Stock Oxygen first, then debloat next. I did mention that if someone wants to keep any Gapps, to run them first before debloating. Hopefullly doing this, it will then run with microG, but if not, I highly recommend making a bug report at the microG Github;
https://github.com/microg/android_packages_apps_GmsCore
As far as the Nanodroid-Patcher, if you did not DEODEX the rom, I have no idea how that managed to work, but I'm assuming it just did a little bandaid on the system is all, which helped a little, but wasn't a real complete patch. So for any concerns questions, problems or help with that, please post and ask Setialpha;
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
P.S. As far as the DEODEX goes it's very simple, it only take a few minutes, the biggest issue would be for people who have never compiled before, understanding and getting that setup on their box/computer, but in Linux compiling is really easy. Once vdexExtractor is built, all you have to do is run a few DEODEX commands and install the Nanodroid-patcher...
DoR3M3 said:
Try not to double post to keep things together...
I went back and edited the post over, with greater details, explaining, that if you Debloat and still see stuff in the system or app drawer, that is because of updates, but now all of these apps can be uninstalled, and that is what you do, manually uninstall them all from the Settings or App Drawer, it's also a reason for trying to do all this on a Clean ROM with no updates, otherwise you deal with this next.
Also for BT Sport, run it and set it all up on Clean Stock Oxygen first, then debloat next. I did mention that if someone wants to keep any Gapps, to run them first before debloating. Hopefullly doing this, it will then run with microG, but if not, I highly recommend making a bug report at the microG Github;
https://github.com/microg/android_packages_apps_GmsCore
As far as the Nanodroid-Patcher, if you did not DEODEX the rom, I have no idea how that managed to work, but I'm assuming it just did a little bandaid on the system is all, which helped a little, but wasn't a real complete patch. So for any concerns questions, problems or help with that, please post and ask Setialpha;
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
P.S. As far as the DEODEX goes it's very simple, it only take a few minutes, the biggest issue would be for people who have never compiled before, understanding and getting that setup on their box/computer, but in Linux compiling is really easy. Once vdexExtractor is built, all you have to do is run a few DEODEX commands and install the Nanodroid-patcher...
Click to expand...
Click to collapse
I removed the remaining Google stuff using Root Browser but after reboot it resulted in Bootloop.
After any ROM install I never used to allow data access till Xprivacy Lua & AFWall+ were up and running. But for some reason this phone (unlike my Nexus 5) doesn't like Xposed installed directly from TWRP. So I have to allow data and install directly via Xposed Installer. I think the best route is the Deodex way but I have tried looking for guide without success. It's really annoying.
bluegrass55 said:
I removed the remaining Google stuff using Root Browser but after reboot it resulted in Bootloop.
After any ROM install I never used to allow data access till Xprivacy Lua & AFWall+ were up and running. But for some reason this phone (unlike my Nexus 5) doesn't like Xposed installed directly from TWRP. So I have to allow data and install directly via Xposed Installer. I think the best route is the Deodex way but I have tried looking for guide without success. It's really annoying.
Click to expand...
Click to collapse
To begin with, I edited over the "DEODEX OR FAKEGAPPS" section, "Signature Spoofing Checker" is a BUG, so forget it saying disabled, FakeGapps is working, so use FakeGapps and you are good to go!
As far as everything else, if you follow the GUIDE 100% EXACTLY IT WORKS! I've done this for almost a year on 3 devices so far, and I just did it on 5.1.5 and 5.1.6 without any problems!
You must follow the guide, do not divert from it, like how you used Root Browser as example, you don't need to do this, and that means after the OTA with 5.1.6, the OTA update for 5.1.6 should of wiped your phone clean, then you start from there.
Personally, after the 5.1.6 OTA update, I booted into TWRP and made a BACKUP, then if you mess up, you wipe everything, Dalvik, cache, system, vendor, data and then RESTORE the backup...
P.S. I am now going to start out on 5.1.6 and do the entire Guide, then I'll come back and post the images of 5.1.6 so you'll see it was done with success...
DoR3M3 said:
To begin with, I edited over the "DEODEX OR FAKEGAPPS" section, "Signature Spoofing Checker" is a BUG, so forget it saying disabled, FakeGapps is working, so use FakeGapps and you are good to go!
As far as everything else, if you follow the GUIDE 100% EXACTLY IT WORKS! I've done this for almost a year on 3 devices so far, and I just did it on 5.1.5 and 5.1.6 without any problems!
You must follow the guide, do not divert from it, like how you used Root Browser as example, you don't need to do this, and that means after the OTA with 5.1.6, the OTA update for 5.1.6 should of wiped your phone clean, then you start from there.
Personally, after the 5.1.6 OTA update, I booted into TWRP and made a BACKUP, then if you mess up, you wipe everything, Dalvik, cache, system, vendor, data and then RESTORE the backup...
P.S. Look at the time of this post, I am now going to start out on 5.1.6 and do the entire Guide, then I'll come back and post the images of 5.1.6 so you'll see it was done with success... BRB
Click to expand...
Click to collapse
Thank you. Looking forward to it. Will attempt again during weekend. I formatted device and installed stock 5.1.6 so no OTA.Don't want to give up especially as you've gone to some effort.
bluegrass55 said:
Thank you. Looking forward to it. Will attempt again during weekend. I formatted device and installed stock 5.1.6 so no OTA.Don't want to give up especially as you've gone to some effort.
Click to expand...
Click to collapse
By the way, the apps you debloat, that ended up getting updates, now appear to you as user installed apps with the ability to uninstall them in the Settings or the App Drawer is what I meant to say, which I'll add that in. So since they turn into user installed apps, that's why you don't need anything to uninstall them...
P.S. @bluegrass55 Sorry it took longer then expected, got tied up a bit with some things, anyhow it's all done and as I mentioned before FakeGapps works fine in 5.1.6, it's just a bug with the Signature Spoofing Checker, so ignore it. I did a DEODEX on my phone for 5.1.6 and here's the screen shots!
I made some changes to the post, so be sure to read it all over, and follow it step by step exactly! If you deviate just a little, it's enough to screw up the entire process and you'll have to start over, it's that picky!
P.S. I went back looking over your replies and you mentioned Xposed through TWRP, and I never mentioned installing Xposed this way. Please be sure to follow the guide and use the Magisk Module for Xposed. I'd also stick to 5.1.5, 5.1.6 hasn't been Officially released yet, just a partial rollout.
Please ignore my last message. Couldn't resist doing it again ( don't want to be defeated). Have Decrypted phone to see if it makes any difference.
bluegrass55 said:
Please ignore my last message. Couldn't resist doing it again ( don't want to be defeated). Have Decrypted phone to see if it makes any difference.
Click to expand...
Click to collapse
Re did the install for the 4th time and wow. Phone runs so much better.
Just two questions.
1- Using Root Browser I notice that GooglePackageInstaller.apk is still present is system-priv. Since it's not included in the Debloat list am I right to assume it should be in the system?
2- Face Unlock function is still present and works. Since it needs Gapps to work does it mean I've missed something?I have checked several times and all the items in the Debloat list have been removed.
FLOSSbOxIN - Since 2016, I am a non-foogle person, nor do I have shucksfook, or anything of those stuffs. I was on Telegram and used to run the flossboxin channel, but left the application due to too much of spam and useless stuffs, and moreover, privacy issues tbvh. Now my XMPP channel is named FLOSSbOxIN too. I recently lost my M30, however, I have been for quiet sometime trying to get this M30 debloated to a level where knox also does not trip, nor where one will have to face the unnecessary Samsung bloatware and annoying analytics. Finally, I have made it to that level, after several permutation combinations.
Code:
[B]FLOSSbOxIN M305F Debloated FOSS/FLOSS Stock ROM[/B]
Released: [B]20200925[/B]
Patch Level: September 01, 2020
Build Date: [B]20200926[/B]
Base Version: Android 10
Build #: QP1A.190711.020.M305FDDS6CTI1
Kernel: [I]4.4.177-19407255[/I]
UI Core: [U]One UI 2.0[/U]
Links:
M30 Database -- AFH
DM-Verity -- AFH
FLOSSbOxIN - ROM -- Cloud - Direct Link
Odin V3.14.4 -- AFH
TWRP 3.4.0-0 -- AFH
Magisk Canary -- AFH
Installation Guide (Only For Bootloader UL On Q/10)
Download ROM from the links given.
Boot to recovery (stock/TWRP) (Guide Link)
Code:
adb reboot download
You will have to format data, as the ROM is decrypted, and coming from an encrypted ROM will give issues. For decrypting, do a "format data" in TWRP Recovery and then reboot to recovery and Wipe Dalvik/ART, Cache, System, Data, Hidden, Internal
Copy over ROM OS & DM-Verity file (do not rename DM-Verity file, keep as is)
Flash ROM - Would take around 10 minutes time for it to flash
Go to wipe, and wipe /hidden
Flash DM-Verity file
Reboot - should take around 5-6 minutes
Notes:
I have removed the setup wizard altogether
Post system starts, wait 5-10 minutes, as system tries to integrate system apps, which are newly introduced
Only necessary foogle stuff is kept, including Maps+Location, GSF & Play Services and all other foogle stuffs is removed
Somehow, even after removing the notorious HIYA (so called caller id and spam protection service), it somehow comes back with a valid internet/mobile data connection. If you wish to remove it again, boot to TWRP, mount /system and then delete the hiya service folder and clear dalvik/cache, and reboot
If any app has permission issue, then reinstall as "user" app (install again manually), and reboot sysui. Should work post that, as sometime, few apps are by default not allowed system changes by Samsung framework, and to add each app to framework is a bigggg task, and very irritating too
Still if any app (e.g., AnysoftKeyboard (see git issue), then uninstall as system, and reinstall as user
Ensure minimal apps are made /system, as they can be harmful
Features:
Fully debloated
Fully stock
Smoother, faster and has long battery run
Foogle & Samsung stupidity free
FLOSS apps included:
Aurora Droid, Aurora Store
F-Droid Classic - Classic variant by bubu
F-Droid Privilege (if you ever install F-Droid main app)
Bromite Webview is default
UngoogledChromium is the default browser
FreeOTP+ is your FLOSS 2FA companion
K9 Mail is the default FOSS email
KeePassDX for auto-login and enhanced privacy
Notification Log allows you to view several logs, once usage access is granted, and is fully FLOSS
QKSMS replaces Samsung Messaging app
Power App allows you to reboot to various modes - sysui, recovery, bootloader....
Vinyl is your music buddy
Dual-Mod for audio included
Screen capture (image & video) feature added
Data transmit (Up/Down) in status bar added (thanks Akhil)
Various camera tweaks (FOSS - OpenCamera is not included)
My hosts file is included, which enhances privacy by blocking various trackers and ads - URL
Hosts editor also included
GPS fast locking in closed areas - debug included for it
USB debug revoke option added to Dev mode
initd support added
Shutdown thread log enabled
BUGS
FLOSSbOxIN - You tell me..
Contributors/Credits:
Samsung for the superb bloat filled operating system, which is like a bliss in the irritation module
topjohnwu for Magisk
Akhil99 for TWRP
vdbhb59 for actually spending hours on getting this sorted, and when I do not even have the phone anymore (lol)...
XDA:DevDB Information
FLOSSbOxIN, ROM for the Samsung Galaxy M30
Contributors
vdbhb59, vdbhb59
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: M305FDDS6CTI1, M305FDDUS6CT13
Based On: Stock
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2020-09-25
Created 2020-09-25
Last Updated 2020-10-17
Snapshots
Snapshots
Reserved 2
Cool FLOSS Rom sar!
Thank you sir. Working on getting a Foogle Based FOSS ROM, so that few stupid apps which are GSF dependent can work out of box.
Google version added, and OFFICIAL tag added..
vdbhb59 said:
DM-Verity -- https://www.androidfilehost.com/?fid=8889791610682882483
Click to expand...
Click to collapse
@faiz5200 here is the link..
Ajayagrawal said:
Hello
Click to expand...
Click to collapse
Okay mate.
Few ways to do it.
1. By installing rooted AP with TWRP already included:->
Install September stock Firmware from my post here: https://forum.xda-developers.com/galaxy-m30/development/rom-t4167497
Use that to flash the September FW. Use ODIN via windows, and use the file: AP ROOTED WITH TWRP RECOVERY. Flash only AP. CP is optional. Follow the steps there. Ensure to flash DMVERITY.
This is one way...
Another way:
2. Flash stock ROM. Connect to wifi/mobile data and setup. Change the time to say 7 days prior to today. Wait 30 minutes and boot to download mode via the following method:: switch off. Press Vol+/- together and connect to laptop/pc via usb. Ensure usb debugging is ON and then perform. Now you are in download mode. Flash TWRP.tar file from AP. All checkboxes should be unticked. Once flashed successfully, press vol- and power button for 7-8 seconds and let go off vol- upon haptic feedback and press vol+ to enter to twrp recovery. You can let go of the buttons once twrp shows up.
Now format data and reboot to twrp again. Mount data and /system and if OS is installed boot to system, else flash a ROM of your choice.
3rd way:
3. Download FLOSSbOxIN (FLOSS/Google variant available). Extract to any desktop folder. Now open 7Zip and make a zip file with all the .img files. Choose .tar (available from 7Zip dropdown as well) and rename the tar file to say rom.tar.
Once done flash this one via AP. Ensure all checkboxes are unchecked. Reboot to TWRP following the steps in method 2 above. Format data, boot to twrp, flash dm-verity and boot to system. You can wipe cache/dalvik and /hidden if you want. Will take around 10 minutes to boot. Dont forget to boot to twrp first and flash dmverity, else you will end in bootloop.
Note: With Samsung, in case you forget to flash DMVerity, and by mistake clicked boot to system, do not worry. Switch off, or reboot to twrp and mount /system and flash. Wipe dalvik and cache, reboot. Done.
vdbhb59 said:
Okay mate.
Few ways to do it.
1. By installing rooted AP with TWRP already included:->
Install September stock Firmware from my post here: https://forum.xda-developers.com/galaxy-m30/development/rom-t4167497
Use that to flash the September FW. Use ODIN via windows, and use the file: AP ROOTED WITH TWRP RECOVERY. Flash only AP. CP is optional. Follow the steps there. Ensure to flash DMVERITY.
This is one way...
Another way:
2. Flash stock ROM. Connect to wifi/mobile data and setup. Change the time to say 7 days prior to today. Wait 30 minutes and boot to download mode via the following method:: switch off. Press Vol+/- together and connect to laptop/pc via usb. Ensure usb debugging is ON and then perform. Now you are in download mode. Flash TWRP.tar file from AP. All checkboxes should be unticked. Once flashed successfully, press vol- and power button for 7-8 seconds and let go off vol- upon haptic feedback and press vol+ to enter to twrp recovery. You can let go of the buttons once twrp shows up.
Now format data and reboot to twrp again. Mount data and /system and if OS is installed boot to system, else flash a ROM of your choice.
3rd way:
3. Download FLOSSbOxIN (FLOSS/Google variant available). Extract to any desktop folder. Now open 7Zip and make a zip file with all the .img files. Choose .tar (available from 7Zip dropdown as well) and rename the tar file to say rom.tar.
Once done flash this one via AP. Ensure all checkboxes are unchecked. Reboot to TWRP following the steps in method 2 above. Format data, boot to twrp, flash dm-verity and boot to system. You can wipe cache/dalvik and /hidden if you want. Will take around 10 minutes to boot. Dont forget to boot to twrp first and flash dmverity, else you will end in bootloop.
Note: With Samsung, in case you forget to flash DMVerity, and by mistake clicked boot to system, do not worry. Switch off, or reboot to twrp and mount /system and flash. Wipe dalvik and cache, reboot. Done.
Click to expand...
Click to collapse
@vdbhb59 THANK YOU SO MUCH ,SIR.I was about to sell the phone coz TWRP could not be booted.
Finally,TWRP is booted huge thanks to you.Procedure 2 did not work(bootloop) and Procedure 3 gave me .binary error in odin(maybe i messed up in some steps).But Procedure 1 was easiest and foolproof & it booted TWRP in first try without any bootloops.
Now coming to Floss ROM(Vanilla).It was simple,clean and elegant and performance is good as well.I have not checked the battery life with this ROM but i hope it gives me more than standard battery life.Will be checking other ROMS as well-Lineage,Bliss,Turbo etc. and will be settling once i find ROM suitable for me.
Again thank you DEV for guiding me,giving me your time and most importantly contributing to this community !!
Ajayagrawal said:
@vdbhb59THANK YOU SO MUCH ,SIR.I was about to sell the phone coz TWRP could not be booted.
Finally,TWRP is booted huge thanks to you.Procedure 2 did not work(bootloop) and Procedure 3 gave me .binary error in odin(maybe i messed up in some steps).But Procedure 1 was easiest and foolproof & it booted TWRP in first try without any bootloops.
Now coming to Floss ROM(Vanilla).It was simple,clean and elegant and performance is good as well.I have not checked the battery life with this ROM but i hope it gives me more than standard battery life.Will be checking other ROMS as well-Lineage,Bliss,Turbo etc. and will be settling once i find ROM suitable for me.
Again thank you DEV for guiding me,giving me your time and most importantly contributing to this community !!
Click to expand...
Click to collapse
Anytime mate. Actually all the 3 ways I mentioned, do work. Probably, some trouble while flashing. However, no worries, I am glad you were able to boot to TWRP and flash a bloat free OS. Enjoy mate, and happy riding.
Battery life is around 1.5-2 days basis your usage. At times more, touching 3.5 days too. Again, the logic basis is always usage and background stuff.
Bliss does not boot for all, LOS does though.
BTW, which FLOSSbOxIN variant did you try? Google one will eat more battery obviously, against FLOSS one.
FLOSS(Vanilla)-[without google] review
Everything is good with the ROM but some problems i faced could be solved by following procedures:
1.If some apps does not work/launch as expected then "UNINSTALL AS SYSTEM" then REINSTALL it or INSTALL APP OF YOUR CHOICE.For eg:Vinyl player.
2.If AURORA STORE does not download apps then first give permission to Aurora Services and then rerun Store.Otherwise install GooglePlayStore manually once, update GMS and it will work.PS:You can delete PlayStore or disable if you want to.
Other than these everything is FINE.Would certainly recommend to try this ROM ?
Ajayagrawal said:
Everything is good with the ROM but some problems i faced could be solved by following procedures:
1.If some apps does not work/launch as expected then "UNINSTALL AS SYSTEM" then REINSTALL it or INSTALL APP OF YOUR CHOICE.For eg:Vinyl player.
2.If AURORA STORE does not download apps then first give permission to Aurora Services and then rerun Store.Otherwise install GooglePlayStore manually once, update GMS and it will work.PS:You one delete PlayStore or disable if wants to.
Other than these everything is FINE.Would certainly recommend to try this ROM ?
Click to expand...
Click to collapse
Thanks for this mate. Though not bugs, but the app behaviour itself. The ROM itself does not have any bugs.
October release coming soon.
Dear Dev,
Thanks for the rom.
My 3 queries
1. Getting access denied on some files like magisk, odin, and m30 database.
2. Is there any aggresive battery saver or something alike in rom which switches off all functions except calling?
3. The download link to download google version is very slow and is showing close to 17 hours to download on 150 MBps connection.
Thanks and Regards
Ashish
ashish128 said:
Dear Dev,
Thanks for the rom.
My 3 queries
1. Getting access denied on some files like magisk, odin, and m30 database. Also, you will only need the ROM, DMV erity & Magisk files anyways.
2. Is there any aggresive battery saver or something alike in rom which switches off all functions except calling?
3. The download link to download google version is very slow and is showing close to 17 hours to download on 150 MBps connection.
Thanks and Regards
Ashish
Click to expand...
Click to collapse
Hi Ashish,
Actually, AFH is having some issues. I too am unable to view files at times. Magisk and ODIN are Public files anyways. You can navigate with androidfilehost then my user, which is vdbhb59.
Battery saver is there, Ultradata by Samsung itself. You can use any 3rd party app too.
Google version link is quick here. Showing 25 minutes at 80Mbps.
Update - 20201017
Hi All,
Update released for the new version.
N.B., the update by Samsung never was for October 2020 patches, and was only a con, as they moved the apps & priv-app between the 2 folders, and added a very big BUG along with several privacy issues.
When I reached out to them with the details, I was blocked, and my account was suspended.
I have stripped away every bit and piece of bloat and BUGS (afaic). Security patch is still September.
Also, the stock camera is now replaced with 2 open variants, and much better ones. With the latest update, while trying to remove Knox, and some resources, the stock Camera breaks up fully, and the hidl does not link, rendering the app useless.
Magisk Canary 20201017
20201017 - FLOSSbOxIN_Foogle_V2_20201017
20201017 - FLOSSbOxIN_V2.2_20201017
Difference between the 2 versions
Difference between the 2 versions -->
FLOSSbOxIN_Foogle_V2_20201017 - this version is a bit smaller compared to the version 2.2 below. Version 2.2 contains a few more privacy oriented apps, and XDA app as well inbuilt, along with OSMAnd+ and UNLP. I have retained GMS Core and Maps as OSMAnd does not cover many parts of Asia and Russia.
FLOSSbOxIN_V2.2_20201017 - this version contains the following:
SMS - QKSMS
Mail - K9 & pEp - both open source. Both more reliable then stock.
Clipboard - Added function for clipboard. Probably, some apps may not work with it. Ideally, it will come as an option with pop-ups.
Maps - GMaps, OSMAnd+, UNLP
Music - Odyssey & Vinyl
Video - MPV is a great tool. VLC somehow does not integrate with Samsung while building, so have not added it yet.
SimpleTools - Gallery & Calendar alongside stock ones. Do use the open source ones, as they are fully privacy oriented. Some folks like Samsung one, but it is filth filled, and I have taken huge time out to prepare these stuffs, so do try.
Camera - OpenCamera & FreeDCam have been added. I have been using these 2 since a long time, so, do use them too.
Browser - 2 variants of Ungoogled Chromium, Bromite Webview alongside Android Webview.
Terminal - Termus. Do install the relevant addons from F-Droid/AuroraDroid and enjoy.
Downloader - Download Navi is prebuilt.
Launcher - OpenLauncher is added too, which is a better option compared to Samsung one. Use the one you prefer.
Stores - As usual F-Droid (2 variants), Aurora Store and Aurora Droid.
The ROM has been tested completely, in terms of retaining of Samsung features, and additional stuffs that I could integrate. I hope on getting Stock custom ROM soon, if the framework parts pans out, and may have inbuilt power menu options, more QS stuffs and theming, all again depending on time I can spare and framework nuisance.
It would be great if Theme option is added
vdbhb59 said:
Hi All,
Update released for the new version.
N.B., the update by Samsung never was for October 2020 patches, and was only a con, as they moved the apps & priv-app between the 2 folders, and added a very big BUG along with several privacy issues.
When I reached out to them with the details, I was blocked, and my account was suspended.
I have stripped away every bit and piece of bloat and BUGS (afaic). Security patch is still September.
Also, the stock camera is now replaced with 2 open variants, and much better ones. With the latest update, while trying to remove Knox, and some resources, the stock Camera breaks up fully, and the hidl does not link, rendering the app useless.
Magisk Canary 20201017
20201017 - FLOSSbOxIN_Foogle_V2_20201017
20201017 - FLOSSbOxIN_V2.2_20201017
Click to expand...
Click to collapse
Did they replaced system.img with super.img ? Samsumg keeps adding their security related sh**t in the name of security patches making difficult for devs to mod their Roms.
akhil093 said:
Did they replaced system.img with super.img ? Samsumg keeps adding their security related sh**t in the name of security patches making difficult for devs to mod their Roms.
Click to expand...
Click to collapse
Nope. They moved few /system/apps to /priv-app and to /vendor and made a lot of framework changes to ensure boot goes for a toss. One of the worst was how system auto cleans at a schedule. Also busybox installation fails due to /system free space being minimal.
Few more things, which I think cannot explain here.
So I just wanted to share my journey with trying to get MicroG on OxygenOS 13 for my OnePlus 8T!
I wouldn't say I have successfully done but it is working as MicroG is doing what it is intended to do but with definite issues.
The first obvious issue is after flashing MicroG revived module via Magisk, I notice a black spot near the camera. I'm assuming that the module made the UI misalign with the actual camera. Please check screenshots!
Second issue is there is no AOD, it is completely gone. I tried downloading the latest AOD for Oneplus via the web browser and it installed and also showed up in settings as it didn't after flashing MIicroG.
On the plus side I don't believe Google to be harvesting my data as much as stock OxygenOS would allow, and the running services has increased ram availibility from 6.4 gigs of ram usage to 7.1 and I haven't started debloating yet!
The steps I produced to get MicroG to work:
1. After having magisk installed flash Lsposed.
2. In Lsposed flash the modules FakeGapps, Corepatch, and Xdowngrader.
3. Flash MicroG Revived via magisk.
FakeGapps allows for the signature spoofing of microG.
CorePatch allows for no signature checking as that is an issue when flashing microg, so corepatch is a workaround.
Xdowngrader allows for downgrading the gsm to microG version from the current one with OxygenOS 13.
Perhaps if we work together we can get everything working accordingly and have a Degoogled OxygenOS rom.
I know why not just use Lineage 20? Lineage is great but I just perfer the UI of OxygenOS but if the issues I presented to you are not resolved eventually I shall return to Lineage. I just figure "Hey this is what we do, we experiment with roms, right?"
This is an update to having microg on OxygenOS 13.
I have good news as it seems all the above issues with microg on OxygenOS 13 have been resolved!
So for those interested I will list my steps in order to achieve a successful microg install. Of course magisk and unlocked bootloader is needed.
Flash Lsposed and the same modules listed in my above post!
Download fdroid and then App management via fdoid repo.
Use app management app to disable and uninstall GmsCore using mixplorer (flash magisk module mixplorer)
GmsCore directory location: ROOT/PRODUCT/PRIV-APP. Use mixplorer to locate and than click on the GmsCore.apk and select App Info, this will open Google Play Services using App management app. Disable and try to uninstall, you may get a failed to uninstall notification at first.
Download this microg package as it differs from microg revived which was the microg installer that created an overlay issue: minmicrog-standard flash via magisk and reboot.
On first boot you may not see microg in your app drawer but if you search for it through setting apps and enable view system apps you should see it but it maybe still useless. Use mixplorer and try to uninstall GmsCore.apk again. It should uninstall and than flash the microg module again via magisk.
Reboot and now you should see microg in your app drawer---enable its permission and location modules---go to each location module and make sure to always allow location.
Use fdroid or microg website to download and update to the latest microg!!!
Those are the steps I took and wrote this post immediately after doing so while the process was fresh in my mind!
Just ONE issue, microg in app drawer doesn't survive reboot- just install the microg.apk again!
UPDATE: It turns out after 2 days of this current microg setup that Google's GmsCore can not be uninstalled but can be disabled due to the fact that the system partition in Android 13 is read-only. Until there is a script to flash in custom recovery or perhaps any other means of obtaining write access to system there will not be a truly google-less Oxygen OS 13. Just a matter of time before or workaround is released I'm sure.
My final thoughts for now: Microg is functioning as intended and I will continue to use this setup as my daily driver. I have not encountered a google services dependable app that's having issues working with MicroG except Meet or formerly Duo. No severe bugs what so ever---phone functions as intended with everything intact including AOD, fingerprint, ram expansion and app cloning. However still issues with MicroG surviving reboot, I guess until we can obtain system write access. I hope someone finds my post helpful!
Thats so great. Please keep updating further about the rest issues. I will be trying the same myself soon.
alp47470 said:
Thats so great. Please keep updating further about the rest issues. I will be trying the same myself soon.
Click to expand...
Click to collapse
How is your microg setup going? The only issue is MicroG not surviving reboot but all yo have to do is remove the microg module from magisk then reboot and flash the module again and reboot then you'll have to setup microg google account and the location modules within microg.
I think the reason is because google GmsCore lives in the system partition and on reboot the GmsCore reclaims permission which prevents MicroG to function correctly. When someone makes a module for magisk or perhaps to flash with a custom recovery that debloats google or at least gives use write access the reboot issue should be resolved.
JedidroidX said:
UPDATE: It turns out after 2 days of this current microg setup that Google's GmsCore can not be uninstalled but can be disabled due to the fact that the system partition in Android 13 is read-only. Until there is a script to flash in custom recovery or perhaps any other means of obtaining write access to system there will not be a truly google-less Oxygen OS 13. Just a matter of time before or workaround is released I'm sure.
Click to expand...
Click to collapse
There is such script. Recently updated.
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Rootk1t said:
There is such script. Recently updated.
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Click to expand...
Click to collapse
I believe that script in not available for Android 13 and continued development has been suspended as the thread is closed.
JedidroidX said:
I believe that script in not available for Android 13 and continued development has been suspended as the thread is closed.
Click to expand...
Click to collapse
[MAGISK][TWRP][ARM32/64][A8+]Universal Read Only to Read Write for android (RO2RW) | Auto converting SUPER "system partitions" to read/write mode
Read Only to Read Write for android (RO2RW) Update 03.01.2023 : Stable Beta v 3.7.2.1 The first truly working script, original and unique in its logic for all devices with a SUPER partition Universal auto RO2RW | EROFS-2-RW | F2FS-2-RW by...
forum.xda-developers.com
Rootk1t said:
[MAGISK][TWRP][ARM32/64][A8+]Universal Read Only to Read Write for android (RO2RW) | Auto converting SUPER "system partitions" to read/write mode
Read Only to Read Write for android (RO2RW) Update 03.01.2023 : Stable Beta v 3.7.2.1 The first truly working script, original and unique in its logic for all devices with a SUPER partition Universal auto RO2RW | EROFS-2-RW | F2FS-2-RW by...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, so the script was very helpful, took me a few hours to understand how it works but I got it although with some limitations. It seems the script did not grant me write access to the system partition but I was able to eliminate the GmsCore.apk from the system so MicroG can assume all permissions and now working flawlessly on OxygenOS 13.
The script is very helpful in doing so by allowing me to delete certain apk's from the super image and than from my understanding the script would mount that super image without the apk's that I selected which of course GmsCore was one of them. Google's GmsCore is officially eliminated from my current setup with all of Oneplus's benefits intact and no bugs or any issues have been experienced for now.
I will report an update in a couple of days to post the steps I took and any other relevant user experience with the current setup.
Thanks for posting the script @Rootk1t
How to install microg on stock oos13:
1. Debloat google play services apk using
https://github.com/sunilpaulmathew/De-bloater (it's magisk debloater)
2. Flash lsposed and enable fakegapps module.
3. Flash microg installer revived (minmicrog ci or release not working this time)
4. Done. 10 reboots, 0 issues.
My setup:
Magisk delta with new zygisk loader option enabled and lsposed_mod