Related
I'm seeing more and more people use Android phones Google-free by not installing gapps and getting all their applications through alternative sources like F-Droid. When I look at the custom ROMs for the Essential Phone, I see most have gapps baked in.
Just curious if anyone has experience on the PH-1 without gapps or Google service. What ROM are you using? Any issues?
Sent from my [device_name] using XDA-Developers Legacy app
Yes I'd love to know if anyone has gone microG, Xposed FakeGapps on Oreo with a custom rom?
Also if anyone has used Terminal Debloater on Stock Oreo and doing ok?
Thanks
Does Generic System Image come with Gapps? if not then you can use that.
TheIronLefty said:
Does Generic System Image come with Gapps? if not then you can use that.
Click to expand...
Click to collapse
I was thinking that as well. In fact, perhaps the deodex ROM is without gapps. I'll have to ask in that thread.
Sent from my [device_name] using XDA-Developers Legacy app
TheIronLefty said:
Does Generic System Image come with Gapps? if not then you can use that.
Click to expand...
Click to collapse
If that reply was for me, I'm asking more about Custom Roms.
ooklathemok said:
I'm seeing more and more people use Android phones Google-free by not installing gapps and getting all their applications through alternative sources like F-Droid. When I look at the custom ROMs for the Essential Phone, I see most have gapps baked in.
Just curious if anyone has experience on the PH-1 without gapps or Google service. What ROM are you using? Any issues?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
It has been a long process, but I am most of the way there. Used deodexed Oreo Stock. Had to use Tingle manually to patch the framework.jar to get microg running. Haven't debloated yet, but most of the stock apps are disabled at this point. Most apps I use are from F-Droid. Using it as DD now.
Took several days to discover the NFC point is very narrow at the bottom center of the back. I had thought I had broken something. :silly:
I think I'm 99.9% there with CarbonROM LOL...
UnifiedNip is registerd in system, but this section I can't checkmark, even after rebooting. I was using the latest Preview GMSCore, I'll flash the rom over and try with the Stable GMSCore and see if it makes any difference and report back.
I have Xposed, FakeGapps, Magisk 16.7, Magisk Module for F-Droid Privilege, and Debloater (Terminal), and F-Droid. Everything working pretty good, Debloater systemlessly removed some Gapps I didn't want, Browser, Calendar, Gallery...
DoR3M3 said:
I think I'm 99.9% there with CarbonROM LOL...
UnifiedNip is registerd in system, but this section I can't checkmark, even after rebooting. I was using the latest Preview GMSCore, I'll flash the rom over and try with the Stable GMSCore and see if it makes any difference and report back.
I have Xposed, FakeGapps, Magisk 16.7, Magisk Module for F-Droid Privilege, and Debloater (Terminal), and F-Droid. Everything working pretty good, Debloater systemlessly removed some Gapps I didn't want, Browser, Calendar, Gallery...
Click to expand...
Click to collapse
I don't have "UnifiedNlp has known location" checked even though Satstat and OSM clearly show the location.
I am using Core -127 from NanoDroid 17.7.
Debloater is up next.
Well I just wiped/formatted, flashed back the Oreo fastboot image, now ready to flash in carbonrom and try this as I said with the stable versions of microg...
BRB...
DoR3M3 said:
I think I'm 99.9% there with CarbonROM LOL...
I have Xposed, FakeGapps, Magisk 16.7, Magisk Module for F-Droid Privilege, and Debloater (Terminal), and F-Droid. Everything working pretty good, Debloater systemlessly removed some Gapps I didn't want, Browser, Calendar, Gallery...
Click to expand...
Click to collapse
How was your experience with FakeGapps? I kept getting Null pointer exceptions. Tried v1.1 and 2.0.
gadgetguy08 said:
How was your experience with FakeGapps? I kept getting Null pointer exceptions. Tried v1.1 and 2.0.
Click to expand...
Click to collapse
Where did you see, get this at?
Ok UnifiedNIp is registered in system - [Checked]
To make everything work correctly, you'll want to push the GmsCore.apk to /system/priv-app/GmsCore/GmsCore.apk and then extract the lib/ folder from the GmsCore.apk to /system/priv-app/GmsCore/lib - otherwise the bundled libraries will not be found by the app and the maps library will crash apps.
If you don't know how to extract from an .apk, just rename to .zip, then copy out the lib directory.
I did have Xposed modules installed for this, so I will go back one more time, wipe it all again, and this time, see if I get it again.
DoR3M3 said:
Where did you see, get this at?
Ok UnifiedNIp is registered in system - [Checked]
To make everything work correctly, you'll want to push the GmsCore.apk to /system/priv-app/GmsCore/GmsCore.apk and then extract the lib/ folder from the GmsCore.apk to /system/priv-app/GmsCore/lib - otherwise the bundled libraries will not be found by the app and the maps library will crash apps.
If you don't know how to extract from an .apk, just rename to .zip, then copy out the lib directory.
I was always able to get
I did have Xposed modules installed for this, so I will go back one more time, wipe it all again, and this time, see if I get it again.
Click to expand...
Click to collapse
I had the FakeGapps errors in the Xposed Log [systemless version 90.2-beta3]. Tried several things. Interesting you didn't experience them.
I was always able to get UnifiedNLP to registered. It just doesn't show that it has a known location in the microg self check, but SatStat, OSM and others show it.
gadgetguy08 said:
I had the FakeGapps errors in the Xposed Log [systemless version 90.2-beta3]. Tried several things. Interesting you didn't experience them.
I was always able to get UnifiedNLP to registered. It just doesn't show that it has a known location in the microg self check, but SatStat, OSM and others show it.
Click to expand...
Click to collapse
Xposed showed a notification, I mean, you just looked in the logs, or how did you first know?
What is SatStat, OSM and others?
How are you installing microg? I just installed the apk is all, these versions and in this order;
Services Core - com.google.android.gms-12221403.apk
Services Framework Proxy - com.google.android.gsf-8.apk
Store (FakeStore release) - com.android.vending-16.apk
DroidGuard Helper - org.microg.gms.droidguard-14.apk
This is how I intalled microg on another phone and rom and it always worked.
So you have UnifiedNIp is registered in system - checked? For some reason I had to do the steps I mentioned to get it registered... hmm
DoR3M3 said:
Xposed showed a notification, I mean, you just looked in the logs, or how did you first know?
What is SatStat, OSM and others?
How are you installing microg? I just installed the apk is all, these versions and in this order;
Services Core - com.google.android.gms-12221403.apk
Services Framework Proxy - com.google.android.gsf-8.apk
Store (FakeStore release) - com.android.vending-16.apk
DroidGuard Helper - org.microg.gms.droidguard-14.apk
This is how I intalled microg on another phone and rom and it always worked.
So you have UnifiedNIp is registered in system - checked? For some reason I had to do the steps I mentioned to get it registered... hmm
Click to expand...
Click to collapse
I noticed I had an issue with FakeGapps because the MicroG self check showed that sig spoofing failed. At some point after that, I found the Xposed logs showing many errors for Null Pointer exception. I searched around but could not find anyone else with the issue. I submitted an issue on github.
SatStat, OSM are open source apps that will show location on a map. They are able to locate me so I know it is working using UnifiedNlp Settings (shows in the Setting > Location settings).
I installed microG using NanoDroid 17.7 using the full package.
How did you install Xposed?
Ok on NanoDroid 17.7...
DoR3M3 said:
How did you install Xposed?
Ok on NanoDroid 17.7...
Click to expand...
Click to collapse
I installed Xposed Framework 90.2-beta3 systemless through Magisk.
I'd use the Xposed Installer - XposedInstaller_3.1.5.apk;
https://forum.xda-developers.com/showthread.php?t=3034811
But I've learned a trick with it, flash rom and magisk, then install Xposed as the first app, and install the framework from within Xposed 'Install/Update' click cloud on right...
P.S. I'm not using Xposed any longer since it will break SafetyNet check....
Welcome to the XDA home of Webview Manager by Androidacy
Read about it on our blog:https://www.androidacy.com/tag/webview-manager/What is this?This magisk module allows to install several webviews and browsers, replacing the stock one with more privacy friendly/better performing browser and/or webview. By default this module will install Bromite.
Can I use older versions?No.
Why use different webview or default browser?These webviews are de-googled or more privacy friendly, or just more updated, or better optimized. Because it's better than Google or AOSP webview.
Why not other methods?These usually involve directly modifying system and are less versatile and more incompatible. In addition, thanks to auto updates and dynamic system detection, you know you get the right files without extra bloat.
Systemful installSystemful install is not supported and we currenly have no plans to change that.
ConfigurationConfiguration is done during install, thanks to @Zackptg5 magnificent Volume-Keys selector with a touch of our own spice.
Getting supportZip /sdcard/WebviewManager/logs, and send along with detailed description of the issue including device name, ROM, and Android version.
LinksWebsite and blog is at https://www.androidacy.com
Donations are here
Beta/alphas: no longer available, due to an improved QA process.
ZIPs: click me
Telegram: Androidacy Discussions
Discord: Available to Patrons. See our donation link above.
reserved
reserved
Not sure, if this is relates to your module. I installed the module, but in developer settings, where I can choose the webview engine, bromite is greyed and it is written, it is not active for the user "me"... What should I do? I am on Linage for MicroG 15.1
doesnt seem to work on pixels. i think it is because the package name for webview is different on them.
what this module do?
gorillus said:
Not sure, if this is relates to your module. I installed the module, but in developer settings, where I can choose the webview engine, bromite is greyed and it is written, it is not active for the user "me"... What should I do? I am on Linage for MicroG 15.1
Click to expand...
Click to collapse
disable chrome
It's a preferred webview package and will be used no matter what if installed
pbanj said:
doesnt seem to work on pixels. i think it is because the package name for webview is different on them.
Click to expand...
Click to collapse
Package name being different
I wouldn't be surprised if Google blocks it though; the stock ROM probably only will allow Google packages
kos25k said:
what this module do?
Click to expand...
Click to collapse
Exactly what it says
anyway to exclude the actual bromite webview from the zip and script it detect architecture and download correct version and install as system since the filesize is awfully large 150mb+!? i guess that'd make it only work in magisk manager and not twrp flash.
clcombs262 said:
disable chrome
It's a preferred webview package and will be used no matter what if installed
Click to expand...
Click to collapse
Well it was kind of the opposite. I disabled the default webview (Lineage OS) and installed the Bromite Module afterwards. Now I re-enabled webview, which was no longer the default, but Bromite. So it works, if you don't disable default webview, because Bromite is a replacement. Never had chrome installed btw.
Problem is the version is kept anonymous.
So there is no easier way to find what version of Bromite u r flashing.
No details in Magisk module, nothing.
I mean, I know u can't keep the browser up-to-date, but that doesn't mean, u need to hide it too. It dumb thing to do.
JohnWrick said:
Problem is the version is kept anonymous.
So there is no easier way to find what version of Bromite u r flashing.
No details in Magisk module, nothing.
I mean, I know u can't keep the browser up-to-date, but that doesn't mean, u need to hide it too. It dumb thing to do.
Click to expand...
Click to collapse
We don't hide anything; the app version is easily found under app info
Sent from my Moto Z3 Play using XDA Labs
DvineLord said:
anyway to exclude the actual bromite webview from the zip and script it detect architecture and download correct version and install as system since the filesize is awfully large 150mb+!? i guess that'd make it only work in magisk manager and not twrp flash.
Click to expand...
Click to collapse
It was chosen to do it this way because the last attempted way broke versions 1.4-2.0, we just aimed for a stable version
Thanks for the feedback though, we'll definitely consider it in v3.0
Sent from my Moto Z3 Play using XDA Labs
clcombs262 said:
Exactly what it says
Click to expand...
Click to collapse
but it doesn't say.it converts chrome to work with other view?
kos25k said:
but it doesn't say.it converts chrome to work with other view?
Click to expand...
Click to collapse
Because it doesn't
It de-systemized chrome so it won't act as a preferred webview
Sent from my Moto Z3 Play using XDA Labs
Weird, I installed this module on Xz premium (stock pie) but it's not showing in selection of webviews, in developer settings ,not there at all.
I use Google-free Chinese version with NanoDroid installed.
I don't think it's module problem, it appears in list of system apps,but system doesn't recognise it as Webview.
Edit: just tried to push apk into system, results are the same.
Theoretically if I repack apk with the same name as android Webview maybe system will recognise it.
Good evening, first friend, excuse my English, I use Google translator! I installed on my Xiaomi S2 Android 9 Miui10 and everything OK. Only application that gave bad was OLX. Reminding friends that I installed Magisk and used the Titanium backup to freeze the Google View.
Not working on the few AOSP / LOS ROMs for the OnePlus 3 I've tried.
Module installs but there's no Bromite webview under developer options
Anyway I have to uinstall it because I couldn't open Gmail and other apps behaved bad, i.e exit itself.
Waited few days, rebooted but nothing worked.
Device: 1+5, Magisk, Twrp, Oxygen Os Latest
1. Install the latest weekly or global firmware in twrp. (without magisk)
2. reboot.
3. complete the first setup.
4. reboot to recovery.
5. install latest magisk canary (now the latest stable version is v20.4, but need higher)
6. reboot.
7. enable magiskhide and hide magisk manager.
8. install magiskhide props config.
9. reboot.
10. run in termux or any terminal and type:
su
props
choose 1 Edit device fingerprint (Redmi k30 pro)
reboot
choose 2 enable force BASIC key attestation
reboot..
Hide magisk manager keeps failing
Can't find the K30 Pro in the devices fingerprints. Should I use the Mi 10 instead?
It works. Thanks ?
@tze_vitamin
Works flawless!
A bit tricky to find (You mist choose "Redmi" as vendor), but this took just a few seconds to execute :good:
---------- Post added at 11:26 PM ---------- Previous post was at 11:26 PM ----------
NielsvdS said:
Can't find the K30 Pro in the devices fingerprints. Should I use the Mi 10 instead?
Click to expand...
Click to collapse
Choose as vendor "Redmi"
IronSingh said:
Hide magisk manager keeps failing
Click to expand...
Click to collapse
you must in developers options enable install via usb and verify apps over usb..
I choses POCO F2 Pro ( global ) instead Redmi K30 pro for fingerprint and force basic key.
It's also works well !!
sampei said:
I choses POCO F2 Pro ( global ) instead Redmi K30 pro for fingerprint and force basic key.
It's also works well !!
Click to expand...
Click to collapse
Same here :fingers-crossed:
Now use magisk beta 21.0 also good result.
And also much stable than canary. When I was used canary I've had apps keep crashing issue. But with 21.0 it solved that issue for me.
How can I get android 11? I have global miui version...
Google Pay doesn't work for me even though I'm passing SafetyNet. It let me set up my cards but then on the main screen below the contactless symbol it says "Not set up" and when I go to "Contactless setup" it says "Your phone doesn't meet security requirements."
It is exactly the same for me. Safetynet is ok but gpay doesn't work
Safety net is pass but device name changed to Lmi
cherryduck said:
Google Pay doesn't work for me even though I'm passing SafetyNet. It let me set up my cards but then on the main screen below the contactless symbol it says "Not set up" and when I go to "Contactless setup" it says "Your phone doesn't meet security requirements."
Click to expand...
Click to collapse
Have you select HCE Wallet under NFC setting?
I chose HCE for Google play to use contact less and it is works well.
PS : I applied the Theme that made by russian guy that's y my phone having some russian words are appear issue in the setting...:silly:
sampei said:
Now use magisk beta 21.0 also good result.
And also much stable than canary. When I was used canary I've had apps keep crashing issue. But with 21.0 it solved that issue for me.
Click to expand...
Click to collapse
Can you give me a link for Magisk beta 21.0?
seitentaisei said:
Can you give me a link for Magisk beta 21.0?
Click to expand...
Click to collapse
You just set to bate under the setting of the magisk manager.
Then tap install , choose download zip only then install use twrp.
Anyway, attached beta zip but actually you can find very easily at the magisk github......
pennywise1985 said:
Safety net is pass but device name changed to Lmi
Click to expand...
Click to collapse
Choose POCO F2 Pro Global fingerprint in option 1. and POCO F2 Pro Global device model in option 2.
Also, in option 5., manually set ro.product.brand, ro.product.odm.brand and ro.product.vendor.brand to POCO for everything to be perfect.
Restart and you are good to go.
Thanks! Working on 21.0+ (stable)
Just wanted to confirm for all that 21.0+ stable from Magisk works!
(perhaps you can update post @tze_vitamin)
Before any stupid questions, I mean this version (flashed via TWRP) : https://github.com/topjohnwu/Magisk/releases/tag/v21.0
To spell out the steps I took (as XDA users love to re-ask the same questions):
Flash above linked stable Magisk via TWRP
enable MagiskHide (under Magisk manager settings)
install & enable `MagiskHide Props Config` from plugins menu in MagiskManager & reboot
termux su; props; 1-edit fingerprint; f- certified fingerprint; 22-POCO; 2- POCO F2 Pro Global(10); reboot
termux su; props; 2-enable force BASIC key attestation; reboot
... enjoy your safetynet passing PocoF2
Click to expand...
Click to collapse
alloysious said:
Just wanted to confirm for all that 21.0+ stable from Magisk works!
(perhaps you can update post @tze_vitamin)
Before any stupid questions, I mean this version (flashed via TWRP) : https://github.com/topjohnwu/Magisk/releases/tag/v21.0
To spell out the steps I took (as XDA users love to re-ask the same questions):
Click to expand...
Click to collapse
It works on Xiaomi.eu rom too?
tze_vitamin said:
It works on Xiaomi.eu rom too?
Click to expand...
Click to collapse
hy i chanched from last global to xiaomi.eu_multi_HMK30Pro_20.10.16_v12-11
and yes it works.
greats
Hi, magisk was passing saftey net. I installed magisk 21.2 with twrp and it says its installed. Installed Magisk hide and hid all Google apps and I think it changed the devices fingerprint in the install log. But no luck. Any ideas?
Miui 12.0.5 global
Vanmanman said:
Hi, magisk was passing saftey net. I installed magisk 21.2 with twrp and it says its installed. Installed Magisk hide and hid all Google apps and I think it changed the devices fingerprint in the install log. But no luck. Any ideas?
Miui 12.0.5 global
Click to expand...
Click to collapse
You just need to enable Magisk hide option in Magisk Manager (nothing specially to install for), and the required activity for GooglebPlay Services to hide will be already checked-in. You don't need to check in manually the other Google apps (and better you don't)
All that does not change device fingerprint or any prop.
If you really want to change props (incl. device fingerprint), use Magisk Hide Props Config (MHPC), find its XDA thread with the Guide in OP post (and more detailed guide on its Github)
And I don't see any problem ("no luck"?!) on your screenshot.
If SafetyNet is passing, better don't change any props/fingerprints - specially, before playing with, carefully study Magisk Wiki and MHPC Guide from Github
zgfg said:
You just need to enable Magisk hide option in Magisk Manager (nothing specially to install for), and the required activity for GooglebPlay Services to hide will be already checked-in. You don't need to check in manually the other Google apps (and better you don't)
All that does not change device fingerprint or any prop.
If you really want to change props (incl. device fingerprint), use Magisk Hide Props Config (MHPC), find its XDA thread with the Guide in OP post (and more detailed guide on its Github)
And I don't see any problem ("no luck"?!) on your screenshot.
If SafetyNet is passing, better don't change any props/fingerprints - specially, before playing with, carefully study Magisk Wiki and MHPC Guide from Github
Click to expand...
Click to collapse
Hi, Thanks for the reply.
I reinstalled to go back to default magisk settings. I have Magiskhide enabled. But for instance. The macdonalds app when redeeming an offer will say "security check failed". Also playstore cant see netflix and some other apps anymore with new version of magisk. I used magisk to pass safteynet to do that before, or it was doing that before but its not passing safteynet with 21.2 magisk now
I tried using MagiskHide Props Config to change the devices finger print but attestation keeps failing
Vanmanman said:
Hi, Thanks for the reply.
I reinstalled to go back to default magisk settings. I have Magiskhide enabled. But for instance. The macdonalds app when redeeming an offer will say "security check failed". Also playstore cant see netflix and some other apps anymore with new version of magisk. I used magisk to pass safteynet to do that before, or it was doing that before but its not passing safteynet with 21.2 magisk now
Click to expand...
Click to collapse
On Magisk Github find Wiki, there is the whole chapter devoted to the problems how certain apps detect root and tips how you can try to prevent
But it's a constant game of mice and cat - you may fix it for now (for some of those apps), but a newer version of that app may explore a new methods to again detect the root
As the minimum, enlist the given apps to the Magisk hide list.
Also, take Hide Magisk Manager and rename it - it may help (some apps look if Magisk Manager is installed).
Remove TWRP folder (some look for that) - read the Wiki, try all the tips suggested there
Btw, are you passing SafetyNet or no. First you must make sure to pass (my comments above are about that even if you pass SsfetyNet, that there are still apps that declare that phone is rooted, by taking other checks and methodes).
So, Msgisk Hide must be enabled.
If its still not passing SafetyNet, take a screenshot - does it pass Basic Integrity or not, does it show taking Basic or Hardware eval type for CTS
Some Magisk modules may also cause SafetyNet to fail. Disable all modules, reboot and try again
These are all important details, not just SN is failing or some app detects root...
thanks will do. Gave them a go and now trying changing my devices finger print. Just cant get attestation/basicintegrity or cts profile to pass. Only have magisk hide propconfig module @zgfg
See again my previous post - I've edited/added some details
I enabled magisk hide. Changed magisk name. Changed every fingerprint and simulation of device I could but still get this
I checked magisk hide with a root checker and its working with that. So somethings working. Cant find the magisk github wiki but finding lots of other stuff to try to get saftey net passing. Just no luck yet
trying to install HiddenCore Module from Xposed but the manager is saying xposed framework is not installed even though I've have Riru core and tried both frameworks. All this stuff worked before on my phone before the new magisk update or googles updated something maybe
had to install framework via TWRP. Got HiddenCore Module going and safety net check pass!!! However still cant redeem offers with macas because of security check fail. Wonder what there looking for now. Removed everything before and just hid with magisk but they must have updated. Also cant see my netflix in google play like i used to
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