Related
Hey guys, thought id create a thread for people to discuss any issues of tips for android pay UK as it was released on 18/05/2016.
I've managed to get it working - Rooted with latest chroma & systemless root!
Tested in a shop - works perfectly!
Method if ROOTED
1. Make sure you are on latest systemless root beta.
2. Uninstall any ad blocking software (adaway edits system)
3. Enter the following permission changes in ADB or using a root explorer.
-Run "adb shell"
-From the shell run "su"
-On the # prompt run "chmod 751 /su/bin/"
4. Restart phone
5. You should now be able to add a card and then try it out in a shop. If not, try a clean install of your ROM and systemless root.
OPTIONAL - if you use adaway, there is a systemless version you can use so that it doesn't modify the system! Flash the "Systemless Hosts file" Zip in the link below PRIOR to adaway installation!
http://forum.xda-developers.com/showthread.php?t=2190753
Enjoy! =]
hltbest said:
Hey guys, thought id create a thread for people to discuss any issues of tips for android pay UK as it was released on 18/05/2016.
I've managed to get it working - Rooted with latest chroma & systemless root!
Tested in a shop - works perfectly!
Click to expand...
Click to collapse
May i Ask how?
I can second that - works like a charm!
I have Pure Nexus ROM installed.
Can download the app but get the message "Google is unable to verify that your device or the software running on it is Android compatible" when I try and add a card.
Android n v3 rooted and working good I think it's setup but not tested lol
Stretlow said:
May i Ask how?
Click to expand...
Click to collapse
Ive added the method to the 1st post so people can see how to do it!
Let me know if it works!
I flashed the latest N Dev preview then activated Pay but had a "can't verify your version of android" error message. Turns out I had changed the DPI on the last dev preview and after setting it to default Pay started working (at least I could now add a card). I'll test it actually works at a terminal today. Systemless root, adaway etc. As a matter of interest, I left a review on the Playstore (before changing the DPI) and Google answered within minutes asking me if I was rooted and/or on the preview. They also informed me they're actively working on allowing Pay to work on rooted devices.
*Edit* Yep, successful payment made today.
Nexus 6P
I'm on stock rooted systemless and latest AdAway installed no problem with Android pay.
Sent from my Nexus 6P using Tapatalk
AlmightyAl said:
I have Pure Nexus ROM installed.
Can download the app but get the message "Google is unable to verify that your device or the software running on it is Android compatible" when I try and add a card.
Click to expand...
Click to collapse
I suggest you wipe /system and install Pure Nexus again; this time don't use the newest provided GApps for that Rom, use the 2-3-16 GApps, or you can try Open GApps. Now flash the UnSu Update file, or whatever it's called to unroot Pure Nexus (Pure Nexus has /system root by default and will never work with Android Pay). After you've done that you can root with systemless root and AP should work. Check with the SafetyNet app from the Play Store to make sure it passes all the checks.
bouchigo said:
I suggest you wipe /system and install Pure Nexus again; this time don't use the newest provides GApps for that Rom, use the 2-3-16 GApps, or you can try Open GApps. Now flash the UnSu Update file, or whatever it's called to unroot Pure Nexus (Pure Nexus has /system root by default and will never work with Android Pay). After you've done that you can root with systemless root and AP should work. Check with the SafetyNet app from the Play Store to make sure it passes all the checks.
Click to expand...
Click to collapse
Yes. I did this and it works (not tried posting yet though!).
I wiped, reflashed, used April's gapps, followed all the other steps and hey presto! Thanks
Installed it the other day and used it for the first time today; feels pretty magical!
I'm not able to add any more cards at this point though even though my bank supports Android Pay. I keep getting a super vague and unhelpful "Request Failed" error message. My bank tells me it's Google's fault, and Google seems to be clueless about it. Anyone have any more information on this error?
AlmightyAl said:
Yes. I did this and it works (not tried posting yet though!).
I wiped, reflashed, used April's gapps, followed all the other steps and hey presto! Thanks
Click to expand...
Click to collapse
Works perfectly. Paid for my Friday night beers. Woohoo!
Where can I find systemless root for Preview 3 ?
Android Pay has been pretty ropey in my experience, been very slow to make payment, can take a good 4-5secs to get locked-on when it works, which it doesn't always. For the last couple of days I've only used it on the Underground when I know both entry and exit wouldn't be busy, basically not at rush hour.
I've tried all different approaches... top of phone, middle and bottom. Nothing seems to improve the speed of payment. Any tips on how I could improve performance?
Ta.
jodvova said:
Where can I find systemless root for Preview 3 ?
Click to expand...
Click to collapse
Your need modified boot then twrp and then flash SuperSU 2.72 or above
Just used android pay for the first time in Aldi. Worked very well, was really impressed!! Currently running the android N preview 3.
Sent from my Nexus 6P using XDA-Developers mobile app
highburybloke said:
Android Pay has been pretty ropey in my experience, been very slow to make payment, can take a good 4-5secs to get locked-on when it works, which it doesn't always. For the last couple of days I've only used it on the Underground when I know both entry and exit wouldn't be busy, basically not at rush hour.
I've tried all different approaches... top of phone, middle and bottom. Nothing seems to improve the speed of payment. Any tips on how I could improve performance?
Ta.
Click to expand...
Click to collapse
The NFC chip on the 6P is inside the glass visor. Make sure you touch any payment platform with that.
By the way, if the SafetyNet app says it passed the checks, can I use Android Pay without problem? I'm rooted with systemless root and have Adaway without any zips. However, in the Adaway settings I use the data/data/hosts target. Safety Net passes. I don't have a card that can be used with Android Pay right now, but it should be coming next week.
Sent from my Nexus 6P using Tapatalk
sherlock5545 said:
The NFC chip on the 6P is inside the glass visor. Make sure you touch any payment platform with that.
By the way, if the SafetyNet app says it passed the checks, can I use Android Pay without problem? I'm rooted with systemless root and have Adaway without any zips. However, in the Adaway settings I use the data/data/hosts target. Safety Net passes. I don't have a card that can be used with Android Pay right now, but it should be coming next week.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Just an FYI
There is a zip you can flash prior to installing Adaway that makes AP and Adaway play nice together
https://www.androidfilehost.com/?fid=24438995911977059
From the OP in the Adaway thread
Yesterday I tried n preview 3 for the first time and I must say that I'm impressed. Installed android pay with no problems at all. The only thing that seems a little annoying is that I was endeavouring to make twrp work, which I couldn't, and when it hung and I had to reinstall n3, I found I was required to phone the bank again to reactivate the card.
jodvova said:
Where can I find systemless root for Preview 3 ?
Click to expand...
Click to collapse
Just look for SuperSU 2.74 beta. That's working fine for me!
sherlock5545 said:
The NFC chip on the 6P is inside the glass visor. Make sure you touch any payment platform with that.
By the way, if the SafetyNet app says it passed the checks, can I use Android Pay without problem? I'm rooted with systemless root and have Adaway without any zips. However, in the Adaway settings I use the data/data/hosts target. Safety Net passes. I don't have a card that can be used with Android Pay right now, but it should be coming next week.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I used Android Pay yesterday, systemless rooted and Adaway installed v3.1.1(56)
A word ahead, I am far away from beeing an expert. I read and tested a lot, but can't answer all your question.
Instead this thread is intended to share experiences as I spend quit some days to become my phone as free from Google.
I did this on a Galaxy A3 (2017) with LOS.
First of course is not to install Gapps. We can replace many of its functionality. First of all we need a store to download apps. I highly recommend FDroid as a first choise. You can download the app at their website.
With this you get a variety of apps for almost all, but not all problems. Nevertheless I recommend to take your time and check what is offered there, even if you used other apps before.
If you don't find an equivalent, you might want access the google playstore. In FDroid there are two apps available for this purpose. With both you can anonymously access all (not payed) apps on Playstore. You can of course login with your google accound, but ... ok, that's not so anonymous anymore
What else do we miss without Gapps. There is a way of receiving push notifications, that is often handled via GCM (google cloud messanging).
First of all we need to enable spoofing. This was quite a challange, as usual tools (tingle, ...) work with non-odexed ROMS, while that for A3 is an odexed ROM.
Finally I found a zip here, that works for me:
https://forum.xda-developers.com/showpost.php?p=77456471&postcount=3775
Download that zip, goto TWRP.
Before installing it you have to do two steps.
Mount /system
Create a link (with advanced/terminal): ln -s /system/vendor /vendor
Otherwise install of this zip will fails. Be patient, it takes around 5..10min to pass.
Now we can work with microG, that will replace some google-APIs.
Add the repo "microg.org/fdroid/repo"
Then install micoG core, fakestore and proxy.
To get unifiedNLP running (this is for location services) the microG core must be a system app.
So do a reboot in the TWRP. Mount system first.
Than copy with integrated filemanager the folder com.google.android.gms-xxxx
from /data/app/
to
/system/priv-app
and reboot.
You will find in your app-overview the microG app - please open and let selftest run.
Enable permissions there and also disable battery optimisation
unifiedNlp should be registered. Next is to enable them.
Download from FDroid these two apps:
Local GSM Location (with this you can download a database of cell towers and their location, giving you a chance to get a rough estaimatin where you are, without waste of energy for GPS)
and
NominatimNlpBackend (to get your position as street/city/country instead of coordinates).
Very important:
Apps that require this gapps need to be installed after microG. Otherwise they will not work properly.
I guess that are usually apps that needs location.
Feedback for microG installation
I´ve tested your microG installation these days. Worked like a charm ! Thanks for your post.
The Nanodroid patcher referred in your link was gone, so i used http://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-18.1.20180909.zip.
I had the same problems with Yalp downloads you´ve described earlier, after reboot it worked.
GCM works, but just not with Threema ;-( But it´s a known problem.
Getting NLP to work was a little bit of hassle, but I found many articles about it. Was not sure which of the backends to use, there are many.
What is interesting - I didn´t use encryption and patched the ashyx_no_encryption patch right after flashing LOS and I didn´t use SU or Magisk right now. Result: absolutely no boot loops and no reboot after power off !
From which stock variant you came ?
@cyberbix:
The patcher for spoofing was quite beta at that time. Did you have to do any preparations to let it run? I remember in TWRP I had to mount /system and create that /vendor-link. Is it still required? I reported my issued there but I am not sure he cooked it with these patches finally.
The Yalp issue is completely independent on microG. It seems that there is a bug in the Downloader of LOS15.1. There are others suffered from this issue, not just the A320FL. The workaround to use internal download works.
Can you give more details about the NLP-hassle? That might help others to not go that painful way. Imho all is fine if you copy (or move) the folder I described above and reboot.
About the backends ... I think there is no alternative for Nominatim, which works only online. For the cell bases location I prefer a offline solution, I found that "Local GSM Location". The microG-Packages usually contain the mozilla-online backend.
BTW: Did you use one of the zip-packages to install microGSMcore, fakestore, GsfProxy ... or manually via FDroid as I did?
I had latest Oreo 8.0 installed before. But I am not sure whether or not I updated the bootloader too with Odin.
@starbright_
Did you have to do any preparations to let it run?
Yes. I did exactly the same as you did in TWRP.
Can you give more details about the NLP-hassle?
I wasn´t sure if its needed at all and even if microG went green, the backends seemed not wo work at all.
BTW: Did you use one of the zip-packages to install microGSMcore, fakestore, GsfProxy ... or manually via FDroid as I did?
I did it in the same way as you. Flashed the patcher, installed the rest from FDroid. That´s it.
Moreover: i didn´t install Magisk or any other root and I didn´t use Xposed. I used the push notification tester to test GCM. Everything was fine.
I can check if installing an su package or Magisk will lead into the same problems.
Installed Magisk on top of your microG setup. Everything works, see McFys thread. I guess you just didn´t read what TB tells about SU.
starbright_ said:
A word ahead, I am far away from beeing an expert. I read and tested a lot, but can't answer all your question..
Click to expand...
Click to collapse
My experience below:
-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green
-yalp works fine, i like it, but in the end i had to use my goggole account instread of the experimental 'internal account' and this because of gmaps
-gmaps works fine BUT it doesn't find the current gps position unless i restart it (long press on back arrow). This is odd because other map-apps (openstreet, tomtom..) work! Also, when i need to use the google account to save some locations or simply the offline maps, it does work only for the first time, later it doesn't recognize my (already set) googke account
-i don't know if it's related to microg but camera doesnt find the gps, while opencamera yes, fotej camera neither
-again, i don't know if it's related to microg but each time i add the google account i loose my contact list
-apps that need to talk with playstore doesn't work at all, I wanted to use Europe3D by geoflier and it didn't load properly until i installed also the playstore
- the same for those apps that need to purchase some addons
-BUT worst, above all (crying) is that the speechTotext is not wotking and it's a feature I really miss!
I don't know if a proper patched rom would work better, I always hope that mcFy finds some time to release the rom already patched.
Anyhow next days I will try to reinstall the stock rom to see if these behavioours happen also there.
I did another installation again. More details next.
But finally I gave up. I couldn't solve two issues
- neither telegram nor whatsapp works after a few minutes (doesn't wake up at incoming calls)
- heavy instabilities with LOS15.1/Magisk/Xposed/microG
I didn't find which component is responsible for that, but I remember that I didn't always get SU with Magisk. After a reboot it works again.
Even such components as DuckDuckbrowser crashed.
I couldn't recover my apps backup by TB from my previous S5mini on A3 with TB and Magisk (Parser error).
I need a rest from all this stuff.
starbright_ said:
I
I need a rest from all this stuff.
Click to expand...
Click to collapse
it took it some days and many reinstallations before i found out the right sequence!
i think everything related to microg is stable enough except what i wrote before
pink0 said:
it took it some days and many reinstallations before i found out the right sequence!
i think everything related to microg is stable enough except what i wrote before
Click to expand...
Click to collapse
So what is the sequence? This:
"-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green"
And it is stable for you? Never get problems with not granted root?
What is last box: cell based location? Same for me... But I am not sure what exactly means this.
I installed localGSMbackend which created an offline database with celltowers. This works fine in energy saving mode I get a rough position without any waste of energy or privacy (as offline).
Altogether I did at least 20 complete wipes and started from scratch.
At the first I started early with root (either Magisk or LOS-addsu).
Than there are two options to get a spoofed ROM.
Either via Xposed/Fakestore module or via nanodroid patcher.
Both works in general.
Than installed microG (different ways - manually, nanodroid, unofficial installer, that are the 3 options I know).
But it always become instable. Apps don't get root anymore or does FC ....
So I did it another way around.
I first installed all required via FDroid (without any root, Xposed ...). That seems to me rather stable. The good thing: this are around 80% or apps I need. Than I did a backup, so that I don't have to starts from scratch, which is painful as hell with around 40 .. 60 apps.
My last attempt was after that install Magisk, Xposed, Fakestore. Spoofingchecker was red, but a microG gets green.
I installed it with nanodroid (created first with setup wizard a file, so that only microG and mapsapiv1) gets installed.
This was first time my apps work fine with maps. Other attempts to manually install the maps framework/lib wasn't succesful (why ever).
Problems started when installing TB. First it doesn't get root permission. After a restart it works, but I get parsing errors. If I understand FAQ this is due to different busyboxes ?!? Ok, the backups I created at another device with LOS14.1 and addsu.
But this was not the only issue. Browser crashed and I never get neither Telegram nor Whatsapp to get wake up after a few minutes of deep sleep (they arn't get registered at microG too, so this might be another issue).
@pink0:
Did I understand it right, you use GMaps?
@cyberbix:
My problems with whatsapp and telegram (not registering in GCM) - did you found a way, maybe with an older version of whatsapp?
Does your system keeps stable after all?
To be honest, that Magisk and Xposed seems to add to much intrusive stuff that might fail altogether. But even with the manual way it wasn't perfect. Maybe after a rest and with the next version from McFy I try this again. Good luck I didn't sell my old S5min til now.
starbright_ said:
So what is the sequence? This:
"-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green"
And it is stable for you? Never get problems with not granted root?
What is last box: cell based location? Same for me... But I am not sure what exactly means
@pink0:
Did I understand it right, you use GMaps?.
Click to expand...
Click to collapse
it's here i writed down because my personal memory buffer, at my age, is really small
yes gmaps is working quite good except the behavour I wrote, but enabling developer options I can easily kill the program to get the new/current position (also I noriced tgat because of this gps problem ir cannot calculate any route while navigating)
I also dislike the idea of using xposed bexause I never needed it but now it's different
about telegram/whatsup i'm not using such softwae so I can't say what's wrong
starbright_ said:
...My problems with whatsapp and telegram (not registering in GCM) - did you found a way, maybe with an older version of whatsapp?
Click to expand...
Click to collapse
I do not use WhatsApp, I use Threema and Threema has known problems with microG GCM.
starbright_ said:
Does your system keeps stable after all?
Click to expand...
Click to collapse
Yes, but I didn´t flash Xposed, just Magisk.
Ok.That spoofing can happen via Xposed Module or nanodroid patcher. For non-odexed ROMs are more options (tingle,...) but not for ours.
So after all I am now happy with my current installation:
- install TWRP via ODIN
- Wipe in TWRP (system, data, cache, dalvik)
- install Lineage via TWRP
- boot into system
- install FDroid
install and setup most of needed apps - there is a good selection of apps in FDroid now
- Create Backup (via TWRP)
- Install Magisk (viaTWRP) and Magisk Manager in LOS
- Setup adaware and afwall (both from FDroid as they need root)
- Installing microG (via TWRP) with packets from here:
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
( use patcher for spoofing the ROM, setup to create a control file and than a minimal setup with microG, maps-api, FakeStore).
- install Yalp from FDroid and via Yalp the missing apps that are not available via FDroid.
I found that Telegram (and Whatsapp not 100% sure yet) push-notification work. I disabled battery optimization for both.
starbright_ said:
So after all I am now happy with my current installation:
[...snip..]
- Installing microG (via TWRP) with packets from here:
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
( use patcher for spoofing the ROM, setup to create a control file and than a minimal setup with microG, maps-api, FakeStore).
Click to expand...
Click to collapse
thanks for your post!
- did you run the nanodroid patcher itself or you deodexed tje rom by hand?
- do you notice any difference between a magisk-through instlation of nanodroid and a direct one?
- which build of LOS are you using?
pink0 said:
thanks for your post!
- did you run the nanodroid patcher itself or you deodexed tje rom by hand?
- do you notice any difference between a magisk-through instlation of nanodroid and a direct one?
- which build of LOS are you using?
Click to expand...
Click to collapse
I am not sure, but the LOS15.1 for A3 2017 (by @McFy from 08/21) ROM is in a state you need the patcher. Other methods (as tingle - what I used before with other mobiles) don't work.
Not sure what is odexed and deodexed. The only other method works for spoofing is Xposed framework. There is a module that fakes this. But until now I did't see a need for Xposed and I don't want to increase complexity. (From that point of view I rather should go for addsu instead of Magisk)
I did first a Magisk installation, as root is more important and you have later the chance to chose between microG and Gapps. (Did it step by step with backups not to start again from scratch).
But I didn't use Magisk for installation, but TWRP. How does it works? I am a Magisk newbee.
An update of LOS15 requires to redo it. I also updated microG in this sequence. Just as a short summery:
- boot into TWRP
- wipes system/cache/dalvik
- installed new LOS
- installed Magisk
- reboot into system (just for curiosity, probably not required) and back to TWRP
- let run uninstaller of microG (I used the zips from here: https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928)
- install (run) the patcher (be patients, that takes long time, maybe 15min)
- install (run) setup wizard (selected only few things, as maps-api, can remember exactly)
- install the real package (install what has been selected in setup).
check this out https://hackernoon.com/e-first-beta-soon-to-be-released-82d7ec950dd
basically, this is a LOS-based rom including microG, aiming at avoiding google applications/usage.
or https://download.lineage.microg.org/a5y17lte/
Nominatim backend
Has anyone using microG got the NominatimGeocoderBackend to work ? On the LOS15 or on LOS16 builds of McFy ? With Nanodroid or with microG core setup ?
The Self-Check in the microG Settings app on the LOS16-microG-build-20190412 with Nanodroid 20190310 from McFY fails the self-test "UnifiedNlp do not have Location to test Geocoder"
The NominatimGeocoderBackend is installed, activated and configured for OSM.
No big deal, everything else works fine.
cyberbix said:
Has anyone using microG got the NominatimGeocoderBackend to work ? On the LOS15 or on LOS16 builds of McFy ? With Nanodroid or with microG core setup ?
The Self-Check in the microG Settings app on the LOS16-microG-build-20190412 with Nanodroid 20190310 from McFY fails the self-test "UnifiedNlp do not have Location to test Geocoder"
The NominatimGeocoderBackend is installed, activated and configured for OSM.
No big deal, everything else works fine.
Click to expand...
Click to collapse
My selfcheck gives just 2 unchecked points:
Playstore signature (I installed Fakestore+Yalp and Fdroid)
Radiocell based location (altough Nominatem is setup).
"Playstore signature" I could manage after apply permission spoofing to Fake Store (system app).
But, I don't get any app registered, although I have enabled Google registration and GCM.
I even deinstalled ebay and installed it again - no effect. ?!? What can I do?
I remember @cyberbix mentioned the Push notification tester:
It fails for me with step1 - "No register" ?!? How can that be? What did I miss.
[/COLOR]
starbright_ said:
?!? How can that be? What did I miss.
Click to expand...
Click to collapse
Did you do the device check-in ?
See https://f-droid.org/en/packages/com.thermatk.android.xf.fakegapps/
What is push notifcation exactly claiming ? Unable to register or missing Play services ?
hello,
been having this weird bug/problem with com.miui.security center with every miui 9 release for poco(miui 10/pie security app runs fine but i didnt like miui10!)
the strange thing is that xiaomi is sending updates to all its apps on miui 9 exept security center!!(am talking about the app update not about the antivirus defs update etc).
the question is : can i remove the security app?and how?( am on miui 9.6.14 global stable ....rooted).
Install Titanuim Backup and uninstall from there.
P.S you can run into problems and force close issues along with other unbearable ****. so backup Security App on Titanium Backup and then uninstall it
Don't even think of uninstalling the Security app. I tried it twice and ended up in bootloop. I spoke to a miui dev and he said Security app is an essential part of miui rom and messing with it means messing with the ROM.
Right
Same here
com.miui.securitycenter
Need a mod for this can someone help.
How do i mod this so that all undesirable tracking & spyware components can be removed. It is obvious that this of a tracker agent making it unsafe for the user only makes it safer for XIamoi & its partners.
So I opened up the the app components-
Broadcast receivers activities services etc. And here is what I found .....
In something that supposedly claims to be a for security component for the phone
- Dunno if they will let me stick in a screenshot here . There are adware and spyware components down to the core.
Code:
AdsProcessPriorityService
com.facebook.ads.internal.ipc.AdsProcess
PriorityService
AdsMessengerService
com.facebook.ads.internal.ipc.AdsMessen
gerService
That is to name a few
- any attempt to disable this component is futile because even if you run pm disable the component is force enabled
- the other singers if I am rooted and I am ' magiskcally ' I hide magisk from all these redmi components. ..... even Here it forces need to unhide magisk could you see the extent of spyware organisation down to the core
I would like to continue this thread with an invitation to vah word wants to give me an approach and work with me so that a magisk module that will grab his component from the current phone and mod it -let the original spyware component load during boot time and post boot do a swap with the mod
Is it possible to do this kind of modification & unspy MIUI
Yes it can be. Use lucky patcher and "delete system app". It worked for me without bootloop. I think there wasn't many things changed after that except for no 10s warnings and no sidebar functions
Vipxpert said:
Yes it can be. Use lucky patcher and "delete system app". It worked for me without bootloop. I think there wasn't many things changed after that except for no 10s warnings and no sidebar functions
Click to expand...
Click to collapse
i can confirm this , i on miui 13.0.11 , redmi note 10(mojito) . uninstalled com.miui.securitycenter , rebooted . no bootloop. i will let other know if i encounter some bug later
Edit1: cant open battery setting, manage apps show nothing
Vipxpert said:
Yes it can be. Use lucky patcher and "delete system app". It worked for me without bootloop. I think there wasn't many things changed after that except for no 10s warnings and no sidebar functions
Click to expand...
Click to collapse
can i delete miui cleaner ?
Apih95 said:
can i delete miui cleaner ?
Click to expand...
Click to collapse
Well.... Isnt that intergrated into Security Center app as well lol
ron_hyatt said:
hello,
been having this weird bug/problem with com.miui.security center with every miui 9 release for poco(miui 10/pie security app runs fine but i didnt like miui10!)
the strange thing is that xiaomi is sending updates to all its apps on miui 9 exept security center!!(am talking about the app update not about the antivirus defs update etc).
the question is : can i remove the security app?and how?( am on miui 9.6.14 global stable ....rooted).
Click to expand...
Click to collapse
Lucky patcher (slightly sketchy) and De-Bloater appear to work to remove apps on rooted devices
Obviously
Code:
adb shell pm uninstall --user 0 com.miui.securitycenter
will not remove it but if all you need is it to be disabled you can try that
Hello, this probably won't be seen, but to the very few travelers who discover this message on google or something:
As of January 19th 2023, the "Security Center" application on MIUI 13 is extremely sketchy.
I'm planning on trying to decompile it if possible.
Currently (According to the AOSP part of the settings) The app has permissions that are very worrying. Downloading files without permission, proprietary MIUI perms, full network access, etc.
Not only that, the built-in package manager utility (PM), refuses to disable com.miui.securitycenter due to being unable to "disable core miui packages..." and spitting out an exception dump.
This is clearly a protected app, that has too many permissions, for no apparent reasson.
Setting SELinux to permissive dosen't help either.
There are 2 options that people have currently - Either leaving a piece of a PUP (Potentially unwanted program) on their phone, or risking bricking it by uninstalling it.
According to the posts on this thread some people have had success, some got a soft-brick.
Doing so shouldn't result in a hard brick, so if you have backups, a userdata format should solve the issue.
TheMagnificent_Y said:
Hello, this probably won't be seen, but to the very few travelers who discover this message on google or something:
As of January 19th 2023, the "Security Center" application on MIUI 13 is extremely sketchy.
I'm planning on trying to decompile it if possible.
Currently (According to the AOSP part of the settings) The app has permissions that are very worrying. Downloading files without permission, proprietary MIUI perms, full network access, etc.
Not only that, the built-in package manager utility (PM), refuses to disable com.miui.securitycenter due to being unable to "disable core miui packages..." and spitting out an exception dump.
This is clearly a protected app, that has too many permissions, for no apparent reasson.
Setting SELinux to permissive dosen't help either.
There are 2 options that people have currently - Either leaving a piece of a PUP (Potentially unwanted program) on their phone, or risking bricking it by uninstalling it.
According to the posts on this thread some people have had success, some got a soft-brick.
Doing so shouldn't result in a hard brick, so if you have backups, a userdata format should solve the issue.
Click to expand...
Click to collapse
i recommend lineageos rom instead of miui but make backups
Hi I'm struggling with the same problem trying to stop de SecCenter. Maybe there is a way to stop the app to run. I tried on my Note 10 Pro with MIUI12.0.6 Global (Android 11) and it works.
You need root on the phone. You should change the owner of the folder "/data/user/0/com.miui.securitycenter" to a user the is not System. In my case a run the command "chown -R root:root /data/user/0/com.miui.securitycenter". After that you need to kill the process of the "com.miui.securitycenter". So at the end the process doesn't start anymore. In the next boot you need do the process again because the boot change the permission of the folder to the system again.
I'm trying to create a Magisk Module to do that but i don't know how until now.
I decided that I needed a fresh start with my LG v30+ after over a year on Oreo, and figured I would go ahead and wipe everything and install rooted stock pie per this thread (using the TWRP flashable method).
From there, I went ahead and installed the Magisk Modules for Busybox, Riru - Core, and Riru -EdXposed, because I wanted to have a few Xposed modules. I started out with XPrivacyLUA, and GravityBox [P], making TWRP Backups and checking SafetyNet status after each install. Because it kept passing every time, I got complacent, and stopped checking. I installed Buttered Toast Revived, GM Dark Theme Enabler, and MinMInGuard in EdXposed, followed by several apps. I then installed the 4.4.153_haumea_I.base_1.9_3 kernel, and a bunch of more apps.
It was around this time I decided that I should try and set up Google Pay, only for it to complain about the device it was installed on. I went back to Magisk Manager and sure enough I was failing SafetyNet checks on both ctsProfile and basicIntegrity. And because I wasn't checking every step of the way, I don't know what caused it to break. I've tried unloading the various modules but none of them seem to be a smoking gun, as both check continue to fail even when some or all of them are turned off.. It's not the custom kernel is it? and if so, what do I do to to roll back to stock?
I also looked into the Magisk Module, MagiskHide Props Config but the developer of that says it doesn't have much chance of fixing basicIntegrity fails. Also, they don't have a device fingerprint in their database for v30+ Pie yet. So when I have some free time to dedicate to phone tinkering, I'm going to back up what I have now, revert to an earlier backup from before things broke, pull a getprop ro.build.fingerprint, and then restore my backup of the current broken state so I can give it a try anyway. Because I'm stubborn like that.
That is, unless I get easier suggestions to try first. Passing SafetyNet would be a nice to have thing, but I wasn't passing before I did my wipe, and so I won't really miss it if I'm not passing now either.
Try looking through here: https://github.com/ElderDrivers/EdXposed/issues/386
Seems a recent SafetyNet update is halfassedly checking for the edXposed Magisk module and workarounds are hit-and-miss, with no word from the dev(s) if they're working on it or intend to.
Septfox said:
Try looking through here: https://github.com/ElderDrivers/EdXposed/issues/386
Seems a recent SafetyNet update is halfassedly checking for the edXposed Magisk module and workarounds are hit-and-miss, with no word from the dev(s) if they're working on it or intend to.
Click to expand...
Click to collapse
This was it. Blacklisting Google Play, Google Play Services, and Google Services Framework in EdExposed (the suggested workaround) seems to be working for now.
And if anyone's curious, the device fingerprint on my US998 30b is
Code:
lge/joan_nao_us/joan:9/PKQ1.190414.001/192451445de41:user/release-keys
Not that that's changed at any point in my installation process, according to the backups that I've checked. So MagiskHide Props Config wouldn't have been any use, because that wasn't the problem in the first place.
radwolf76 said:
Code:
lge/joan_nao_us/joan:9/PKQ1.190414.001/192451445de41:user/release-keys
Not that that's changed at any point in my installation process, according to the backups that I've checked. So MagiskHide Props Config wouldn't have been any use, because that wasn't the problem in the first place.
Click to expand...
Click to collapse
Well I mean...the device fingerprint is only a contributer to the long list of crap that'll trip Safetynet; Google really, really doesn't want non-compliant devices to use Safetynet apps. The scans have become quite invasive.
All the official ROMs should have compliant fingerprints, anyway.
Thing is...I didn't mean "halfassedly" in a offhand or facetious way; they probably have implemented a check, in an experimental and thus inconsistent way, that only catches the module often enough to be annoying. Or the way they're checking might depend on other things in the environment (looking for signs of its presence rather than the module itself), which would explain why the workaround works on some phones and not others. Try to keep track of any root- or Magisk-requiring changes you make.
I couldn't get a pass when I tried a few days ago, and ultimately couldn't figure out why despite doing the usual stuff and the workaround above. Decided Ingress and PokeGO were more important than GravityBox, which I've done without for years anyway :v
Enjoy being able to pass the checks, but be prepared for it to break at any moment. Google has been annoyingly persistent about patching workarounds, and the workarounds for the patches to workarounds, and so on.
I've had the same problem, although blacklisting Google play, Google services framework, and Google play services didn't help.
Hello,
I recently installed GrapheneOS on my Pixel 6 and I want to use XPrivacyLua on it. But when I install and activate LSPosed (1.8.3) and reboot then it says there's no LSPosed installed. But in Magisk it is loaded together with Shamiko. Shamiko works fine, but I wasn't able to use LSPosed yet. Does anybody know how LSPosed can be used successfully on GrapheneOS?
Thank you,
Oebbler
Oebbler1 said:
Hello,
I recently installed GrapheneOS on my Pixel 6 and I want to use XPrivacyLua on it. But when I install and activate LSPosed (1.8.3) and reboot then it says there's no LSPosed installed. But in Magisk it is loaded together with Shamiko. Shamiko works fine, but I wasn't able to use LSPosed yet. Does anybody know how LSPosed can be used successfully on GrapheneOS?
Thank you,
Oebbler
Click to expand...
Click to collapse
you lose more for the little gain you get by using xprivacylua. also graphene os isn't meant to be used with root since you defeat the main goal of the os itself: security. it hardens several aspects of android to make it more secure, and that's why things like lsposed won't work.
hellcat50 said:
...graphene os isn't meant to be used with root since you defeat the main goal of the os itself: security.
Click to expand...
Click to collapse
That's a redundant and absurd thing to say. First of all, grapheneos objection to root is realistically tied to support burden and public impression rather than anything practical. Second, root doesn't threaten security if used responsibly. Third, root is HELPFUL for security when used competently.
Now for the other thing... lsposed... avoid like the plague.
Thank you for your answers!
The thing is that I cannot avoid LSPosed for XPrivacyLua on Android 12. I really want to use it in order to avoid tracking by getting IDs and other data from my device. So my question still remains on how to make LSPosed runnable.
I tried to install it with Riru. Riru was telling me that LSPosed is loaded, but the LSPosed app told me it cannot find LSPosed. It seems the same as with LSPosed on Zygisk. Is there any way to get LSPosed (or maybe EdXposed) working?
Oebbler1 said:
Thank you for your answers!
The thing is that I cannot avoid LSPosed for XPrivacyLua on Android 12. I really want to use it in order to avoid tracking by getting IDs and other data from my device. So my question still remains on how to make LSPosed runnable.
I tried to install it with Riru. Riru was telling me that LSPosed is loaded, but the LSPosed app told me it cannot find LSPosed. It seems the same as with LSPosed on Zygisk. Is there any way to get LSPosed (or maybe EdXposed) working?
Click to expand...
Click to collapse
Please read this about ID's: https://grapheneos.org/faq#hardware-identifiers
Thank you! This sounds good, but leaves something out which I also want to do:
I want to allow access to particular contacts for some apps only. And maybe in the future it should be possible to hook some other methods (with XPrivacyLua Pro) that apps use for things I don't want them to do. So I think I cannot avoid LSPosed, EdXposed or something like that. How can this be achieved?
Oebbler1 said:
Thank you! This sounds good, but leaves something out which I also want to do:
I want to allow access to particular contacts for some apps only. And maybe in the future it should be possible to hook some other methods (with XPrivacyLua Pro) that apps use for things I don't want them to do. So I think I cannot avoid LSPosed, EdXposed or something like that. How can this be achieved?
Click to expand...
Click to collapse
Contacts permission does not need any additional hacks to be denied.
hellcat50 said:
you lose more for the little gain you get by using xprivacylua. also graphene os isn't meant to be used with root since you defeat the main goal of the os itself: security. it hardens several aspects of android to make it more secure, and that's why things like lsposed won't work.
Click to expand...
Click to collapse
Unless you're running GrapheneOS via yellow state boot loader (and you checking the finger print each boot), I can't take claims of "root is insecure" quite seriously.
I don't want to deny contacts permission at all, but I want to allow only certain contacts to be seen by some apps. So I want e. g. Telegram or Signal to only see the contacts I am using in these apps. These aren't the same so Telegram's and Signal's access to the contacts list need to be hooked in order to provide individual faked/manipulated lists to these apps.
And maybe in the future some apps do a call to e. g. some app-internal ID which is used for tracking, so I want to hook that later on.
To me it doesn't matter if there are other hacks available to do these things. I'd just like to do that with XPrivacyLua Pro. So how can I get this working on GrapheneOS?
ezdiy said:
Unless you're running GrapheneOS via yellow state boot loader (and you checking the finger print each boot), I can't take claims of "root is insecure" quite seriously.
Click to expand...
Click to collapse
Yeah right rooting makes your device more secure haha. https://madaidans-insecurities.github.io/android.html#rooting
Oebbler1 said:
I don't want to deny contacts permission at all, but I want to allow only certain contacts to be seen by some apps. So I want e. g. Telegram or Signal to only see the contacts I am using in these apps. These aren't the same so Telegram's and Signal's access to the contacts list need to be hooked in order to provide individual faked/manipulated lists to these apps.
And maybe in the future some apps do a call to e. g. some app-internal ID which is used for tracking, so I want to hook that later on.
To me it doesn't matter if there are other hacks available to do these things. I'd just like to do that with XPrivacyLua Pro. So how can I get this working on GrapheneOS?
Click to expand...
Click to collapse
I don't think lsposed will ever work on graphene os. for that you will have to switch the os
hellcat50 said:
Yeah right rooting makes your device more secure haha. https://madaidans-insecurities.github.io/android.html#rooting
Click to expand...
Click to collapse
Applications don't just have access to root if you make it available to yourself. Again, its about the USER being competent and not just granting root permission willy nilly like a total retard. Nice try, but NOPE.
A project to keep an eye on...
GitHub - chriswoope/resign-android-image: Resign Android OS (esp. GrapheneOS) images with your signing keys and add ADB root and other modifications
Resign Android OS (esp. GrapheneOS) images with your signing keys and add ADB root and other modifications - GitHub - chriswoope/resign-android-image: Resign Android OS (esp. GrapheneOS) images wit...
github.com