Related
I'm on NC5 with MK2 bootloaders and my new company requires that I use Good For Enterprise as my email client. I've tried the Xposed module from this thread http://forum.xda-developers.com/showthread.php?t=2040163 along with an older version of Good as suggested, but I can't get it to work. I hate to give up root, but I have to be able to get work email on my phone so now I'm planning on removing Root. I really don't want to flash stock files if I don't have to because I at least have all the bloatware removed now and I know I can't do that if I flash stock without root.
So my question is what can i do to keep my current system as is, but remove ALL traces of Root? Is it as simple as going into SuperSU and doing a Full Unroot? I'm asking first rather than trying it because each time Good detects Root I have to request a new activation key and I've already done that once so I don't want to have to do it again if it's more complicated than that.
Also, will I have any issues with Knox after doing this?
Thanks
There is an Xposed module that will allow you to "trick" whatever app you want to think you're UNrooted but it's name escapes my memory at this moment...
Sent from my SCH-I545 using XDA Premium 4 mobile app
pamulli said:
I'm on NC5 with MK2 bootloaders and my new company requires that I use Good For Enterprise as my email client. I've tried the Xposed module from this thread http://forum.xda-developers.com/showthread.php?t=2040163 along with an older version of Good as suggested, but I can't get it to work. I hate to give up root, but I have to be able to get work email on my phone so now I'm planning on removing Root. I really don't want to flash stock files if I don't have to because I at least have all the bloatware removed now and I know I can't do that if I flash stock without root.
So my question is what can i do to keep my current system as is, but remove ALL traces of Root? Is it as simple as going into SuperSU and doing a Full Unroot? I'm asking first rather than trying it because each time Good detects Root I have to request a new activation key and I've already done that once so I don't want to have to do it again if it's more complicated than that.
Also, will I have any issues with Knox after doing this?
Thanks
Click to expand...
Click to collapse
You can do the Full Unroot, but first you must remove Busybox if it's installed.
THEN you can use SuperSU full unroot, then unistall SuperSU Pro (if you have it), then uninstall SuperSU.
The unroot.sh script that comes with Saferoot will get rid of busybox and leave you rooted so you can uninstall SuperSU.
Caution: if SuperSU is installed as a system app (/system/app/Superuser.apk) then you can't uninstall it using the application manager.
In that case, removing SuperSU by hand may be necessary.
dm1105 said:
There is an Xposed module that will allow you to "trick" whatever app you want to think you're UNrooted but it's name escapes my memory at this moment...
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried the Xposed module, which is posted here http://forum.xda-developers.com/showthread.php?t=2040163 and I can't get it to work. I also can't get a response on that thread to tell me if I did something wrong. I simply installed the Xposed module and then installed a previous version of Good that others reported as working with the module. Not sure if I'm supposed to do anything in Xposed other than just install the module?
Thanks
pamulli said:
I tried the Xposed module, which is posted here http://forum.xda-developers.com/showthread.php?t=2040163 and I can't get it to work. I also can't get a response on that thread to tell me if I did something wrong. I simply installed the Xposed module and then installed a previous version of Good that others reported as working with the module. Not sure if I'm supposed to do anything in Xposed other than just install the module?
Thanks
Click to expand...
Click to collapse
OK dumb user error. I'm guessing this works a lot better if the Xposed installer is actually installed. I had forgotten to reinstall it after I upgraded to 4.4.2 and only the Wanam module was installed. Hopefully that will solve my issue.
Thanks for the responses.
So on my kindle i had everything installed to have the play store working and i got the play store to work and i got the youtube app to work. And so what happened was i deleted the youtube app and installed the newest version and when i opened youtube it gave me the google play services error, but the play store itself still worked.
So what i did was i uninstalled all the google account manager, google services frame work, etc.
And tried to fix the youtube issue by reinstalling all of those things. I started by installing google account manager, and then i rebooted it to install the next thing. Only, when it started up i could unlock the device, but none of the apps would load. So i did a stupid thing and factory reset it, which i think got rid of the root.
I have no idea what to do. I couldn't find any thread about this.
The notificaton bar works and the navigaton buttons show up on the side. So i can get to settings, but the carousel and home screen won't load after i unlock it
here are some pics:
i can't post links because i'm a new member so type it in without spaces
http :// imgur . com / a/ uuB6f
What version of firmware do you use?
ONYXis said:
What version of firmware do you use?
Click to expand...
Click to collapse
13.3.2.6
Sorry, I missed that you did hard reset. without root I think i can do nothing.
Only way is update to 13.4.1..1 http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813 (if you can go to settings) and lose root. Of course if your devices HDX 7.
ONYXis said:
Easiest way , i think, is install safestrap and flash stock firmware by SafeStrap (without wiping anything!)
after that gapps need to install again.
Adb working?
Click to expand...
Click to collapse
How am i going to install safestrap when i can't open any apps?
android2204 said:
How am i going to install safestrap when i can't open any apps?
Click to expand...
Click to collapse
Sorry, I missed that you did hard reset. without root I think you can do nothing.
Only way is update to 13.4.1..1 http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813 (if you can go to settings) and lose root possibility.
What do you mean by loose root possibility?
android2204 said:
Do you mean by loose root possibility?
Click to expand...
Click to collapse
Sorry. English isn't my native language so I don't understand your question.
I wrote that if you upgrade to 13.4.1.1 you will not be able to obtain root.
How do i update?
http://www.amazon.com/gp/help/customer/display.html?nodeId=201390340
link to update file https://kindle-fire-updates.s3.amazonaws.com/update-kindle-13.4.1.1_user_411009920.bin
Yes. but how would i install it?
you wrote ""So i can get to settings, ", what difficulties after that?
Can you get into Settings - Device - System Updates?
nevermind. so i followed the instructions and put the update into the internal storage folder but when i went into system updates on my kindle the box said "check now" instead of "update" so when i tap check now it says "last update failed".
android2204 said:
kindle the box said "check now" instead of "update" so when i tap check now it says "last update failed".
Click to expand...
Click to collapse
Try to turn off wifi and reboot.
You should see that your device has found update, no more variants.
I'll try it again after school. What would I do next if I get the error again?
I have no idea. This is one variant. if tablet do not found update - this says about broken symlinks for example or something else that anyway do not fix without root.
btw check your root status:
adb shell
su
ONYXis said:
I have no idea. This is one variant. if tablet do not found update - this says about broken symlinks for example or something else that anyway do not fix without root.
btw check your root status:
adb shell
su
Click to expand...
Click to collapse
I didn't really understand any of that. What is a broken symlink? And I don't think I'm rooted because I factory reset it.
Also, how could I check root status and what would be the purpose?
Okey. You not rooted now, so do not pay attention.
Your one method to get working device is update firmware.
In way that I described.
If you do not see "update" button after pulling file - sorry. no other idea.
So basically, if this doesn't work I'm screwed?
Anyone else got any ideas?
This is a simple app to install GApps and disable items on your Kindle. This was tested on Fire HD 7 4th gen. I do not know the status on HD 6. but in theory it should work just fine. It doesn't make any MAJOR changes to where it would cause a non-booting system.
But with all things in the development world, you are taking a risk. I have tested this about 10 times on my own tablet.
Obviously, you need root for this. The only known way to root is via KingRoot.
The GApps install is a very minimal install to /system that fully works. It is no different than flashing a GApps package in recovery. I am also disabling updates for Play Store and Play Services. The method used is the ones referenced a few times in this forum. I am unable to find the original finder of this information so if you find the original source I will link that content appropriately.
Download Here
The safe way to disable ads on lockscreen and still use profiles or FreeTime is to run this command on every boot. "chmod 000 /data/securedStorageLocation/dtcp/adunits"
Changelog:
v4: Fixed backwards logic in BootReciever to block or unblock ads on boot. Thanks @DoLooper for pointing out the bug
v3: Updated Gapps with combination found by @AlbusAngelus and the casting libs needed he found. Changed the layout to more material design
v2: Found bug with button not showing enabled. Found MAJOR bug with the pm block method of disabling ads on lockscreen. Found workaround
v1: Original Release
jmz said:
This is a simple app to install GApps, busybox, and disable items on your Kindle. This was tested on Fire HD 7 4th gen. I do not know the status on HD 6. but in theory it should work just fine. It doesn't make any MAJOR changes to where it would cause a non-booting system.
But with all things in the development world, you are taking a risk. I have tested this about 10 times on my own tablet.
Obviously, you need root for this. The only known way to root is via KingRoot.
The GApps install is a very minimal install to /system that fully works. It is no different than flashing a GApps package in recovery.
Right this minute I would like a tester or two before releasing publicly. There may be some items left on my device that is causing it to seem to work. I just need someone that has done nothing but root.
Just post here and I will PM you details.
Click to expand...
Click to collapse
I have a fire HD7 just doing root right now
I'd be happy to give it a whirl. My Kindle is just sitting here on my desk right now, may as well do something with it.
jmz said:
This is a simple app to install GApps, busybox, and disable items on your Kindle. This was tested on Fire HD 7 4th gen. I do not know the status on HD 6. but in theory it should work just fine. It doesn't make any MAJOR changes to where it would cause a non-booting system.
...
Right this minute I would like a tester or two before releasing publicly. There may be some items left on my device that is causing it to seem to work. I just need someone that has done nothing but root.
Just post here and I will PM you details.
Click to expand...
Click to collapse
Nice tool! I would test it if I had not done everything manually. With GAPPS, do you block updates to Google Play Services by creating a directory in /data/app in order to keep version 6.0.99 which works?
Tester
Would gladly test this for you. I've rooted my HD 7 using KingRoot
Updated OP
jmz said:
This is a simple app to install GApps and disable items on your Kindle.
Click to expand...
Click to collapse
Thanks for this! Does it install google framework 4.4.4 and a gps that supports latest playstore? Also, can we use it to RE-enable OTA, launcher, ads ? thx
DoLooper said:
Thanks for this! Does it install google framework 4.4.4 and a gps that supports latest playstore? Also, can we use it to RE-enable OTA, launcher, ads ? thx
Click to expand...
Click to collapse
Yes it allows you to renable each of those.
As for the Play Store. The version being installed is 5.5.8. the Google Services Framework is 4.0.4. I am looking into ways to make updates work. There is no reason why updates shouldn't work.
Updated app. Please read the notes about upgrading.
jmz said:
As for the Play Store. The version being installed is 5.5.8. the Google Services Framework is 4.0.4. I am looking into ways to make updates work. There is no reason why updates shouldn't work.
Click to expand...
Click to collapse
Is there a reason you choose Framework 4.0.4 over 4.4.4? Just curious as to why you choose it over 4.4.4, maybe some undesired effect I'm unaware of yet?
AlbusAngelus said:
Is there a reason you choose Framework 4.0.4 over 4.4.4? Just curious as to why you choose it over 4.4.4, maybe some undesired effect I'm unaware of yet?
Click to expand...
Click to collapse
Its the one that I could get working. Using updated ones, I only got white play store with loading screen. Unless you have a combination that works with more updated ones.
jmz said:
Its the one that I could get working. Using updated ones, I only got white play store with loading screen. Unless you have a combination that works with more updated ones.
Click to expand...
Click to collapse
Are you saying with your combo you can let them update and they work?
Framework 4.4.4
Store 5.5.12
Play Services 7.0.99 - 034 --- Edit
Account Manager 4.4.4
This seems to work if you block updates for the store and services. The only issues I'm running into now is chromecast has stopped working correctly, and I had it working fine before root, and after initial root. Once I put playstore on it seemed to stop.
AlbusAngelus said:
Are you saying with your combo you can let them update and they work?
Framework 4.4.4
Store 5.5.12
Play Services 7.0.99 - 036
Account Manager 4.4.4
This seems to work if you block updates for the store and services. The only issues I'm running into now is chromecast has stopped working correctly, and I had it working fine before root, and after initial root. Once I put playstore on it seemed to stop.
Click to expand...
Click to collapse
No they won't update because I disable updating when installing them. I will check chromecast tomorrow and see if it works
jmz said:
No they won't update because I disable updating when installing them. I will check chromecast tomorrow and see if it works
Click to expand...
Click to collapse
Well the setup I listed works okay without the white loading screen. If chrome cast works on the older stuff though I'm going to go ahead and roll it all back and freeze it there. Chrome cast functionality is pretty vital, as my Kindle was basically being used as a movie streamer, before the root break through. Thanks for checking into chrome cast!
AlbusAngelus said:
Well the setup I listed works okay without the white loading screen. If chrome cast works on the older stuff though I'm going to go ahead and roll it all back and freeze it there. Chrome cast functionality is pretty vital, as my Kindle was basically being used as a movie streamer, before the root break through. Thanks for checking into chrome cast!
Click to expand...
Click to collapse
Don't get me wrong. I don't have that white loading issue with my tool. Only if I tried to update past what exists in my tool.
Just something I can think of is download the 4.4 gapps package like you would on AOSP and find the cast lib file and push it to /system/lib and see if that fixes it. I think it is libgcast.so. not 100% on that though. I know for a fact it has cast in the name
jmz said:
Don't get me wrong. I don't have that white loading issue with my tool. Only if I tried to update past what exists in my tool.
Just something I can think of is download the 4.4 gapps package like you would on AOSP and find the cast lib file and push it to /system/lib and see if that fixes it. I think it is libgcast.so. not 100% on that though. I know for a fact it has cast in the name
Click to expand...
Click to collapse
Oh I know , I'm just saying if you are already blocking updates with the tool as might as well go to 4.4.4 and newest playstore, because they are working with now without issue.
(Unless that's what's breaking chromecast) I'll check into the cast file when I get home, I'm at work for another 6 hours.
AlbusAngelus said:
Oh I know , I'm just saying if you are already blocking updates with the tool as might as well go to 4.4.4 and newest playstore, because they are working with now without issue.
(Unless that's what's breaking chromecast) I'll check into the cast file when I get home, I'm at work for another 6 hours.
Click to expand...
Click to collapse
Can you toss me the 4 apks you used?
jmz said:
Can you toss me the 4 apks you used?
Click to expand...
Click to collapse
Absolutely, here they are.
And btw, your chromecast idea worked brilliantly. You could implement the install of those too perhaps? I don't know if everyone is as huge on casting as I am, but that was a lifesaver.
AlbusAngelus said:
Absolutely, here they are.
And btw, your chromecast idea worked brilliantly. You could implement the install of those too perhaps? I don't know if everyone is as huge on casting as I am, but that was a lifesaver.
Click to expand...
Click to collapse
yeah i did. Updated OP
jmz said:
yeah i did. Updated OP
Click to expand...
Click to collapse
Just to confirm, tool now uses framework 4.4.4 and services 7.0.9.6 (or 9.9) and prevents them from updating? Thank you so much!
.
So I decided to manually upgrade my Google wallet app to the new Android pay which then requires a new Google play services which I installed but the problem is whenever I try to add a card it says it is unable to verify my android version. Has anyone else attempted this? I saw some people say to un-root and then try it but it didn't seem to work.
Chilidog said:
So I decided to manually upgrade my Google wallet app to the new Android pay which then requires a new Google play services which I installed but the problem is whenever I try to add a card it says it is unable to verify my android version. Has anyone else attempted this? I saw some people say to un-root and then try it but it didn't seem to work.
Click to expand...
Click to collapse
I've tried disabling root via SuperSU, clearing all data for Android Pay and Google Play Services, and resetting my DPI back to 640. None of those did the trick. I'm tempted to try flashing back to 12B and updating to 24B, installing Android Pay and adding my cards, then rooting and restoring a backup.
Chilidog said:
So I decided to manually upgrade my Google wallet app to the new Android pay which then requires a new Google play services which I installed but the problem is whenever I try to add a card it says it is unable to verify my android version. Has anyone else attempted this? I saw some people say to un-root and then try it but it didn't seem to work.
Click to expand...
Click to collapse
Where did you get the play services update?
Are you rooted? It will not run without an xposed module to hide root.
tech_head said:
Where did you get the play services update?
Are you rooted? It will not run without an xposed module to hide root.
Click to expand...
Click to collapse
It should be this one, http://www.apkmirror.com/apk/google...ices-8-1-14-2244331-230-android-apk-download/ and yes I am rooted and I already tried the root cloak exposed module but it didn't work.
Chilidog said:
So I decided to manually upgrade my Google wallet app to the new Android pay which then requires a new Google play services which I installed but the problem is whenever I try to add a card it says it is unable to verify my android version. Has anyone else attempted this? I saw some people say to un-root and then try it but it didn't seem to work.
Click to expand...
Click to collapse
Chilidog said:
It should be this one, http://www.apkmirror.com/apk/google...ices-8-1-14-2244331-230-android-apk-download/ and yes I am rooted and I already tried the root cloak exposed module but it didn't work.
Click to expand...
Click to collapse
Same issue.
Possibly of interest:
http://forum.xda-developers.com/showthread.php?p=62819708
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
roirraW "edor" ehT said:
Possibly of interest:
http://forum.xda-developers.com/showthread.php?p=62819708
Click to expand...
Click to collapse
I may have a build prop file. Somebody will figure it out.
joshua70448 said:
I've tried disabling root via SuperSU, clearing all data for Android Pay and Google Play Services, and resetting my DPI back to 640. None of those did the trick. I'm tempted to try flashing back to 12B and updating to 24B, installing Android Pay and adding my cards, then rooting and restoring a backup.
Click to expand...
Click to collapse
Android pay won't work if you're rooted or if you are using a third party lockscreen.
vv1914 said:
Android pay won't work if you're rooted or if you are using a third party lockscreen.
Click to expand...
Click to collapse
Actually it will work if rooted. There is a root cloak that works. There are people with root running Android Pay.
Something in the build.prop in non-factory ROMs is causing the failure.
I'm trying to get a copy of a factory build.prop for 24b so I can take a look at the differences between it and Jasmine 8.0.
A third party lockscreen is a no go.
tech_head said:
Actually it will work if rooted. There is a root cloak that works. There are people with root running Android Pay.
Something in the build.prop in non-factory ROMs is causing the failure.
I'm trying to get a copy of a factory build.prop for 24b so I can take a look at the differences between it and Jasmine 8.0.
A third party lockscreen is a no go.
Click to expand...
Click to collapse
Not a build.prop issue. Xposed being installed causes the issues. Must remove Xposed and hide root to add cards.
tech_head said:
Not a build.prop issue. Xposed being installed causes the issues. Must remove Xposed and hide root to add cards.
Click to expand...
Click to collapse
Well, I guess I've got something new to try.
I don't know why I'm so obsessed with trying to get Android Pay running. Perhaps because I used to use Wallet before they locked it down for root users, and I missed the memo when they opened it up for rooted phones. I've tried using rootcloak and nodevicecheck. I've tried turning off root with SuperSU. I've tried clearing Android Play Services data (which then forced me to factory reset my watch). I tried setting the DPI back to 640. Same evil message everytime. Cannot be verified.
If this doesn't work, I'll probably give up for a while and wait for a fix. Preferably with a Xposed mod that removes the lockscreen restrictions. Unless I get antsy enough to do a Nandroid backup, flash a 23c KDZ, add the cards, root and restore the backup.
Bramton1 said:
Well, I guess I've got something new to try.
I don't know why I'm so obsessed with trying to get Android Pay running. Perhaps because I used to use Wallet before they locked it down for root users, and I missed the memo when they opened it up for rooted phones. I've tried using rootcloak and nodevicecheck. I've tried turning off root with SuperSU. I've tried clearing Android Play Services data (which then forced me to factory reset my watch). I tried setting the DPI back to 640. Same evil message everytime. Cannot be verified.
If this doesn't work, I'll probably give up for a while and wait for a fix. Preferably with a Xposed mod that removes the lockscreen restrictions. Unless I get antsy enough to do a Nandroid backup, flash a 23c KDZ, add the cards, root and restore the backup.
Click to expand...
Click to collapse
Well, that didn't work. New approach, same message.
I wish there was a way we could consolidate our experiences across all devices. It would be helpful to know which devices and ROMs have more success than others. For example, my observation has been that stock ROMs are more successful than custom ROMS like CM 12.
tech_head said:
Not a build.prop issue. Xposed being installed causes the issues. Must remove Xposed and hide root to add cards.
Click to expand...
Click to collapse
I tried to add cards before I installed Xposed, even after disabling root via SuperSU it wouldn't work.
I managed to add cards by doing the following (on JasmineROM 8.0), all of which are REQUIRED:
1. Set DPI to stock 640
2. Disable SU
3. Reboot into recovery, flash the Xposed uninstaller.
NedDasty said:
I managed to add cards by doing the following (on JasmineROM 8.0), all of which are REQUIRED:
1. Set DPI to stock 640
2. Disable SU
3. Reboot into recovery, flash the Xposed uninstaller.
Click to expand...
Click to collapse
Tried those running RR. Failed again. Seeing that JasmineROM is a stock rom and RR is a CM-based rom, it supports my beliefe that Android Pay doesn't like CM.
I got it to work. Jasmine ROM 8.0.
1. Opened SuperSU app and unchecked "Enable Superuser" box on the Settings tab,
2. Rebooted,
3. Opened Android Pay app and went through the steps to add my Credit Card,
4. Opened SuperSU app and checked "Enable Superuser" box,
5. Rebooted,
6. PROFIT!!!
I do not have xposed installed, so my guess is that xposed may be the problem.
FWIW, I use Tasker and I have a Profile that when I open the Android Pay app, Tasker turns NFC on, and when I close Android Pay, NFC turns off. That works seemlessly. Only issue is that the delay in turning NFC on is a little longer than what Android Pay needs to see NFC, so I get a settings message from Pay. No biggie, I just dismiss it because by the time the message comes up, NFC has already been turned on.
I too can confirm Android Pay works on JasmineROM 8!
If I've helped, please don't forget to press the “Thanks” button!?
I read somewhere that it checks the bootloader. I have the "1003" secure boot error and I can't add cards no matter what I do regarding SU. Is this a common thread with everyone here that can't verify? Anyone know how to correct it while running CM12?
csyrell said:
I got it to work. Jasmine ROM 8.0.
1. Opened SuperSU app and unchecked "Enable Superuser" box on the Settings tab,
2. Rebooted,
3. Opened Android Pay app and went through the steps to add my Credit Card,
4. Opened SuperSU app and checked "Enable Superuser" box,
5. Rebooted,
6. PROFIT!!!
I do not have xposed installed, so my guess is that xposed may be the problem.
FWIW, I use Tasker and I have a Profile that when I open the Android Pay app, Tasker turns NFC on, and when I close Android Pay, NFC turns off. That works seemlessly. Only issue is that the delay in turning NFC on is a little longer than what Android Pay needs to see NFC, so I get a settings message from Pay. No biggie, I just dismiss it because by the time the message comes up, NFC has already been turned on.
Click to expand...
Click to collapse
I'm running Xposed and a new cloak module developed in the last few weeks for Pay.
I also have Tasker set up to enable NFC on Pay opening.
A modified framework (Xposed), root and a ROM not based on stock all cause issues.
BTW: I'm on Jasmine 8.0.
Considering backing up my current configuration, flashing JasmineROM, adding cards, and then restore the backup.
Sent from my LG-VS985 using XDA Premium App
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.