Related
Greenify doesnt working with xposed module....not all xperimental features....i mean boost mode...running lollipop5.0.2
Did it work before? Have you donated? You have root and the correct Xposed framework installed? Is Greenify enabled in Xposed and have you rebooted? etc etc etc
tnsmani said:
Did it work before? Have you donated? You have root and the correct Xposed framework installed? Is Greenify enabled in Xposed and have you rebooted? etc etc etc
Click to expand...
Click to collapse
I download cracked apk
reeeju said:
I download cracked apk
Click to expand...
Click to collapse
You have some nerve, reporting it here.
Ok...working now...latest stable apk2.6.2
reeeju said:
I download cracked apk
Click to expand...
Click to collapse
Proud of yourself? Don't expect any help here.
Oh come on people ... Haven't you ever used a crack??
Sent from my SM-G920F using XDA Free mobile app
Its working nicely with all experimental features through xposed.....nd all donation package features...����������������??
?
A Couple Issues
I will tag onto the need help thread here and hope someone is familiar with these issues. I have Greenify and the donation package installed. I have had it working well before. Now when I open Greenify I get only the screen that lets you select the mode and the experimental features.
I uninstalled it via TiBU and reinstalled the backup with the same result. I uninstalled via TiBU (could not uninstall via the Android App Mgr. It was grayed out. I reinstalled via the play store - had to do via PC because I can't install from the phone for some reason. I get the same result. Only can see the single screen. Also, Greenify is not asking for root and does not show as having root permission in SuperSU (2.49) . I have rebooted, wiped cache and dalvik, and still have the same issue.
Any help would be appreciated.
Thanks
Smithfolk4 said:
I will tag onto the need help thread here and hope someone is familiar with these issues. I have Greenify and the donation package installed. I have had it working well before. Now when I open Greenify I get only the screen that lets you select the mode and the experimental features.
I uninstalled it via TiBU and reinstalled the backup with the same result. I uninstalled via TiBU (could not uninstall via the Android App Mgr. It was grayed out. I reinstalled via the play store - had to do via PC because I can't install from the phone for some reason. I get the same result. Only can see the single screen. Also, Greenify is not asking for root and does not show as having root permission in SuperSU (2.49) . I have rebooted, wiped cache and dalvik, and still have the same issue.
Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Which version of greenify r u using now...cos here all working fine in my moto g2
reeeju said:
Which version of greenify r u using now...cos here all working fine in my moto g2
Click to expand...
Click to collapse
I have version 2.6.2. It had been working in the past. It would sometimes get stuck on the same screen, but I could always get it to go to the main screen for hibernating by reopening.
I installed 2.7 Beta 2 and got the hibernate screen. Then when I rebooted it went back to the same problem.
I figured out that I had to remove administrative rights to uninstall, so I did that, uninstalled, reinstalled 2.7 beta 2 and it asked for admin rights and has them, but still I cannot access the hibernate screen after rebooting. So it seems to work okay until I reboot. I am running the latest Xposed for LP 5.0. I also uninstalled and reinstalled from the play store 2.6.2 (via PC) and I could not access it either through exposed or through the app drawer. I then enabled Greenify in Xposed and rebooted and still it is the same. I may have to remove and reinstall Xposed.
Smithfolk4 said:
I have version 2.6.2. It had been working in the past. It would sometimes get stuck on the same screen, but I could always get it to go to the main screen for hibernating by reopening.
I installed 2.7 Beta 2 and got the hibernate screen. Then when I rebooted it went back to the same problem.
I figured out that I had to remove administrative rights to uninstall, so I did that, uninstalled, reinstalled 2.7 beta 2 and it asked for admin rights and has them, but still I cannot access the hibernate screen after rebooting. So it seems to work okay until I reboot. I am running the latest Xposed for LP 5.0. I also uninstalled and reinstalled from the play store 2.6.2 (via PC) and I could not access it either through exposed or through the app drawer. I then enabled Greenify in Xposed and rebooted and still it is the same. I may have to remove and reinstall Xposed.
Click to expand...
Click to collapse
Download and install 2.6.2....tick in module list....reboot.....open greenify..select boost mode...selinux status permissive...do a soft reboot.....
Smithfolk4 said:
I will tag onto the need help thread here and hope someone is familiar with these issues. I have Greenify and the donation package installed. I have had it working well before. Now when I open Greenify I get only the screen that lets you select the mode and the experimental features.
Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Go to SETTINGS>Device Administrators and uncheck Greenify. Then to SETTINGS>Accessibility and switch off Greenify. Then uninstall Greenify the usual way, not through TiBu. Reboot.
Then try to install Greenify from Play Store or download the apk and install. Enable Greenify in Xposed. Enable Greenify in Device Administrators and Accessibility. Reboot, not soft reboot.
Then open Greenify and see whether you are able to access all the features.
You have root and Xposed, I hope.
Thanks
reeeju said:
Download and install 2.6.2....tick in module list....reboot.....open greenify..select boost mode...selinux status permissive...do a soft reboot.....
Click to expand...
Click to collapse
I decided to reflash the ROM. Will see how it goes.
---------- Post added at 05:21 AM ---------- Previous post was at 05:18 AM ----------
tnsmani said:
Go to SETTINGS>Device Administrators and uncheck Greenify. Then to SETTINGS>Accessibility and switch off Greenify. Then uninstall Greenify the usual way, not through TiBu. Reboot.
Then try to install Greenify from Play Store or download the apk and install. Enable Greenify in Xposed. Enable Greenify in Device Administrators and Accessibility. Reboot, not soft reboot.
Then open Greenify and see whether you are able to access all the features.
You have root and Xposed, I hope.
Click to expand...
Click to collapse
Reflashed the ROM. Had other strange stuff going on.
Hi folks. Upon checking Root Checker Pro, the app says I have root, but it also says that the binary files are not installed. See photos attached. Is that possible? If so, can someone help me out to update the files?
See if theres an update for SuperSu on the Play Store. If there is then update it. It will then ask you to update the binary.
Double0EK said:
See if theres an update for SuperSu on the Play Store. If there is then update it. It will then ask you to update the binary.
Click to expand...
Click to collapse
Thanks - SuperSu was updated, but the issue still remains......
How could the binary files not update when busybox is installed and Root Checker is saying I'm rooted? Having issues writing to both internal storage as well as SD card.
Having the same issue on another phone model, if you got yours solved pls share how you fixed it.
No_Signal said:
Having the same issue on another phone model, if you got yours solved pls share how you fixed it.
Click to expand...
Click to collapse
Unfortunately, no - still haven't solved the problem yet.....
master1454 said:
Unfortunately, no - still haven't solved the problem yet.....
Click to expand...
Click to collapse
I got the problem solved by installing additionally phh's SuperUser.
All three stages cleared green
No_Signal said:
I got the problem solved by installing additionally phh's SuperUser.
All three stages cleared green
Click to expand...
Click to collapse
Question: Anything extra needed besides the flashing the zip & installing the apk?
master1454 said:
Question: Anything extra needed besides the flashing the zip & installing the apk?
Click to expand...
Click to collapse
Which is exact link I should click in phh's SuperUser?
Having the same issue - Total noob here!
I have Magisk but I have never had SuperSU. Does it matter that I don't have it and if so, how can I get around that without flashing/recovery etc and starting all over again?
I have the SuperSU app, fairly certain it's useless as I have Magisk. I have downloaded a patch for SuperSU in the lucky patcher to make SuperSU pro. Again, is this all pointless?
Any help greatly appreciated. I'm sure at the very least, someone can get a laugh at what, a complete noob I am
I will admit when I started this journey I had NO IDEA how out of my depth I would find myself :laugh:
Hi
I just flashed xiaomi.eu and magisk, I'm trying to install adaway but I'm getting an error that there is not enough space available on partition and adaway is suggesting me to change the host Target to /data/data/hosts which also fails when attempting the symbolic link.
Any idea on how to get this sorted?
digitalmahdi said:
Hi
I just flashed xiaomi.eu and magisk, I'm trying to install adaway but I'm getting an error that there is not enough space available on partition and adaway is suggesting me to change the host Target to /data/data/hosts which also fails when attempting the symbolic link.
Any idea on how to get this sorted?
Click to expand...
Click to collapse
Does Adaway have root access?
Also try checking systemless host settings in Magisk, and reboot...
suhridkhan said:
Does Adaway have root access?
Also try checking systemless host settings in Magisk, and reboot...
Click to expand...
Click to collapse
yup i resolved it with systemless host yeserday. the root access wasn't na issue. I think the partiiton is read-only or something.
suhridkhan said:
Does Adaway have root access?
Also try checking systemless host settings in Magisk, and reboot...
Click to expand...
Click to collapse
had to reboot for systemless to take affect, ty.
I am having the same issue. Any fix? Android 13 pixel 6 pro latest adaway version and magisk. (Also had same issue when checked moto g6 phone). It was working perfectly fine to previously. (did the systemless hosts to reverify to)
Dragon Kumera said:
I am having the same issue. Any fix? Android 13 pixel 6 pro latest adaway version and magisk. (Also had same issue when checked moto g6 phone). It was working perfectly fine to previously. (did the systemless hosts to reverify to)
Click to expand...
Click to collapse
I'm having the same issue on the same device... Found any fix?
fluxfield said:
I'm having the same issue on the same device... Found any fix?
Click to expand...
Click to collapse
Yes I managed to fix it. I updated the boot image (reflashing it with magisk). Somehow it started working again. I think one of the magisk versions had a bug.
Dragon Kumera said:
Yes I managed to fix it. I updated the boot image (reflashing it with magisk). Somehow it started working again. I think one of the magisk versions had a bug.
Click to expand...
Click to collapse
I also managed to fix it though in my case I didn't have systemsless hosts, seems to work after flashing it but the ad blocking isn't that good...
fluxfield said:
I also managed to fix it though in my case I didn't have systemsless hosts, seems to work after flashing it but the ad blocking isn't that good...
Click to expand...
Click to collapse
Seems to work really good on my end. I suggest check the hosts file and see what it adds for blocks.
Dragon Kumera said:
Seems to work really good on my end. I suggest check the hosts file and see what it adds for blocks.
Click to expand...
Click to collapse
Its got a lot of stuff there... I can add my own right? How would I do that?
fluxfield said:
Its got a lot of stuff there... I can add my own right? How would I do that?
Click to expand...
Click to collapse
I believe you find the host and add the website or domain to it. I am not sure.
Hi guys,
I'm using Miui Eu 11.0.6.0. I'm not sure what had gone wrong.Both ctsprofile and basicintegrity false. At first, I thought it was edxposed issue so I uninstall it, but it still the same issue after reboot.
Is there any way to resolve it? Appreciated.
These are my screenshots.
thomas140 said:
These are my screenshots.
Click to expand...
Click to collapse
Try disabling/ removing the magisk modules and if that doesn't work revert to stock kernel if you're using a custom kernel.
thomas140 said:
These are my screenshots.
Click to expand...
Click to collapse
Turn on magisk hide in settings and reboot.
MasterFURQAN said:
Try disabling/ removing the magisk modules and if that doesn't work revert to stock kernel if you're using a custom kernel.
Click to expand...
Click to collapse
Tried with stock miui Eu kernel but still the same. Disable all modules and still the same. Magisk hide is on. Hide magisk manager is on too. Weird.
callmebutcher101 said:
Turn on magisk hide in settings and reboot.
Click to expand...
Click to collapse
Both magisk hide and hide magisk manager is on but still both error. Funny.
thomas140 said:
Both magisk hide and hide magisk manager is on but still both error. Funny.
Click to expand...
Click to collapse
Did you hide all the google services from magisk ? Try clearing data of magisk and repeating the process. And btw MIUI EU can pass safetynet without magisk so if you really want safetyney pass you can sacrifice magisk.
callmebutcher101 said:
Did you hide all the google services from magisk ? Try clearing data of magisk and repeating the process. And btw MIUI EU can pass safetynet without magisk so if you really want safetyney pass you can sacrifice magisk.
Click to expand...
Click to collapse
Yup, I know miui Eu without magisk can definitely pass safetynet.
And ya, I have hide all related Google services and still same issue.
Just not sure what's triggering it.
But something's funny, when hide magisk manager, it still able to bypass those bank app root check although both still false status.lol
Try downgrading google play service. Run magisk from canary channel. Latest google play breaks cts
vjsanjay said:
Try downgrading google play service. Run magisk from canary channel. Latest google play breaks cts
Click to expand...
Click to collapse
Ok. That's surprising. For downgrading, I believe it is related to "uninstall updates", right?
Can disable the update once downgrade?
thomas140 said:
Ok. That's surprising. For downgrading, I believe it is related to "uninstall updates", right?
Can disable the update once downgrade?
Click to expand...
Click to collapse
Yes.. Till google makes mandatory.
vjsanjay said:
Yes.. Till google makes mandatory.
Click to expand...
Click to collapse
Update: you are correct. Once uninstalled update, status back to true.
I made few tests.
1. I tried install Edxposed, status became false.
2. In edxposed manager, blacklist Google play services and play store, still false.
3. Install hidden core module under exposed. Status became true but some government app became forced close.
4.I uninstaledl edxposed related stuff and reboot, status still false. I have to clear the data under Google play service to make status back to true.
So, it seems like edxposed is unable to hide properly like magisk does. No choice but have to abandon edxposed.
I have a rooted Samsung SG10Exynos/OS9 that bypasses SafetyNet with the help of Magisk 26.0 & safetynet-fix-v2.4.0-MOD_1.2 (meets BASIC INTERGITY) that I have been using the Starling Bank app 2.92.1.79025 without an issue. I stupidly upgraded to the latest version and got the attached screenshot saying that I had 14 days to restore the device to factory settings (I was still able to use the app after pressing ok). I even more stupidly thought that I could revert back to the previous version that I was using, using Titanium Backup which failed (the app would just flash continuous on launch) and then Swift backup (where it would just repeatedly crash even even before being launched requiring a force stop)
If I wipe data/uninstall/restart phone and install fresh from google play, I now get the attached screenshot saying again to restore to factory, but the button says close app. So being a digital bank, I'm now locked out of my account.
I've tried to install previous versions from APKMirror mirror after wiping data/uninstall/restarting phone, and then just restoring my data with my Titanium/Swift backups but still no joy.
Does anyone know how to downgrade/install not the latest version of Starling Bank, which doesn't have the increased STRONG INTERGITY check?
nukescript said:
I have a rooted Samsung SG10Exynos/OS9 that bypasses SafetyNet with the help of Magisk 26.0 & safetynet-fix-v2.4.0-MOD_1.2 (meets BASIC INTERGITY) that I have been using the Starling Bank app 2.92.1.79025 without an issue. I stupidly upgraded to the latest version and got the attached screenshot saying that I had 14 days to restore the device to factory settings (I was still able to use the app after pressing ok). I even more stupidly thought that I could revert back to the previous version that I was using, using Titanium Backup which failed (the app would just flash continuous on launch) and then Swift backup (where it would just repeatedly crash even even before being launched requiring a force stop)
If I wipe data/uninstall/restart phone and install fresh from google play, I now get the attached screenshot saying again to restore to factory, but the button says close app. So being a digital bank, I'm now locked out of my account.
I've tried to install previous versions from APKMirror mirror after wiping data/uninstall/restarting phone, and then just restoring my data with my Titanium/Swift backups but still no joy.
Does anyone know how to downgrade/install not the latest version of Starling Bank, which doesn't have the increased STRONG INTERGITY check?
Click to expand...
Click to collapse
It will force you to use the latest app.
Block firebaseremoteconfig.googleapis.com
theoneofgod said:
It will force you to use the latest app.
Block firebaseremoteconfig.googleapis.com
Click to expand...
Click to collapse
Also having the same issue. Is this something I should be blocking in Zygiskhide? I can't see it there. Googling the above isn't helping me.
Undeadwolfy said:
Also having the same issue. Is this something I should be blocking in Zygiskhide? I can't see it there. Googling the above isn't helping me.
Click to expand...
Click to collapse
You could try Magisk Delta as it now acts as whitelist so you add only what you want with root. This won't bypass Starling security though. You need to also block address above.
Undeadwolfy said:
Also having the same issue. Is this something I should be blocking in Zygiskhide? I can't see it there. Googling the above isn't helping me.
Click to expand...
Click to collapse
Blocking this address (firebaseremoteconfig.googleapis.com) through AdAway has fixed it for me! That is along with all the things that were needed to run it previously.
theoneofgod said:
You could try Magisk Delta as it now acts as whitelist so you add only what you want with root. This won't bypass Starling security though. You need to also block address above.
Click to expand...
Click to collapse
I think the part where I'm stuck is, what would you suggest to block that address? I can't do that in HMA or in Denylist because it doesn't exist.
I've tried blocking in AdAway and manually adding and still getting Starling recognising root.
I've blocked anything Google Play Services, Play Protect, Wallet too. Starling is my main bank. Has only been an issue in the last couple weeks.
A13 P6 Pro running the April security update 13 (TQ2A.230405.003.E1), Magisk 26101, USNF 2.4.0 Mod 1.2, passing Safetynet Basic+ CTS.
Will look at Magisk Delta next.
marian42 said:
Blocking this address (firebaseremoteconfig.googleapis.com) through AdAway has fixed it for me! That is along with all the things that were needed to run it previously.
Click to expand...
Click to collapse
This isn't working for me :/. Can you share what other modules you're running/how you've set up Magisk?
I followed the directions in this video.
I didn't do the final step where he renames the Magisk app, seems that it isn't necesary.
The YASNAC app shows that the device passes "Basic integrity" and "CTS profile match".
Also remember that blocking firebaseremoteconfig.googleapis.com might break other apps that use this domain (I've found one so far).
Undeadwolfy said:
I think the part where I'm stuck is, what would you suggest to block that address? I can't do that in HMA or in Denylist because it doesn't exist.
I've tried blocking in AdAway and manually adding and still getting Starling recognising root.
I've blocked anything Google Play Services, Play Protect, Wallet too. Starling is my main bank. Has only been an issue in the last couple weeks.
A13 P6 Pro running the April security update 13 (TQ2A.230405.003.E1), Magisk 26101, USNF 2.4.0 Mod 1.2, passing Safetynet Basic+ CTS.
Will look at Magisk Delta next.
Click to expand...
Click to collapse
It's a recent update that broke it.
Try Magisk 26.1, enable Zygisk and enforce deny list. Add systemless hosts. Add only Starling to the deny list.
Install safetynet fix 2.4.0 mod 1.2 by displax.
Add the domain I posted to adaway blocklist. Make sure its enabled and in root mode.
theoneofgod said:
It's a recent update that broke it.
Try Magisk 26.1, enable Zygisk and enforce deny list. Add systemless hosts. Add only Starling to the deny list.
Install safetynet fix 2.4.0 mod 1.2 by displax.
Add the domain I posted to adaway blocklist. Make sure its enabled and in root mode.
Click to expand...
Click to collapse
That's exactly how I have it running now. No change.
Undeadwolfy said:
That's exactly how I have it running now. No change.
Click to expand...
Click to collapse
It's the domain that did it for me. Working fine as of now.
theoneofgod said:
It's the domain that did it for me. Working fine as of now.
Click to expand...
Click to collapse
Thanks for updating. I have both of these in my AdAway too
Code:
firebaseinstallations.googleapis.com
firebaseremoteconfig.googleapis.com
Nothing doing
Undeadwolfy said:
Thanks for updating. I have both of these in my AdAway too
Code:
firebaseinstallations.googleapis.com
firebaseremoteconfig.googleapis.com
Nothing doing
Click to expand...
Click to collapse
Clean install for Starling? I'm trying to think if I did something else.
Oh. Have you "hidden" Magisk?
Just to weigh in here, I can confirm blocking:
firebaseremoteconfig.googleapis.com
Does indeed allow the Starling app to work. Yes blocking Firebase is going to stop some applications working, but you could always pause AdAway until you are done using the problematic app then resume AdAway when you want to use Starling.
Many thanks @theoneofgod
Not working
Reverting the Starling app back to version 2.95.1.79953 fixes things - just don't forget to re-add it to the Deny List.
I'll probably stay on this version until a new fix is found for the current version 2.96.0.80202.
darsh said:
Reverting the Starling app back to version 2.95.1.79953 fixes things - just don't forget to re-add it to the Deny List.
I'll probably stay on this version until a new fix is found for the current version 2.96.0.80202.
Click to expand...
Click to collapse
Wild, even this didn't work for me. No idea why I'm having issues.
Hi All
Quick update - Can confirm that rolling back to 2.95.1.79953 does fix things for now
This is using adaway to block the Firebase URLs in a custom host file and using enforce denylist. It doesnt work beyond that for now.
I swapped over to Magisk Alpha for now but i dont know what Starling are doing in the background to see that you have root at this point. Its very annoying
- Edit 2
They seem to be detecting the Enforce Denylist in Magisk (In any form)
Disabling it on version 2.95.1 shows the app can see root. Enabling it allows the app to proceed as if you are not rooted.
Give KernelSU a try if you can. No modules or any workarounds required.
theoneofgod said:
Give KernelSU a try if you can. No modules or any workarounds required.
Click to expand...
Click to collapse
Isnt that the same as the setting in magisk that hides root from everything not on the su list. Which also doesnt work.