Database Develop

[Q] Help with ADB uninstall

After returning 4 HDs that developed charging and other problems following the setting of the "allow unknown sources" flag, we decided not to tempt fate with the 5th Nook HD and then I discovered that apks can be installed via ADB, bypassing the Android setting. There is a drawback, of course--the apps cannot self-update.
I did this with a copy of an apk that's no longer available in the PlayStore and which I had already installed on my NT/CM10. What I forgot was that this package came with an Aptoide Store app attached. The desired app installed on the Nook HD and runs fine, but we now get periodic random messages like "this app cannot be installed" blah, blah, blah. I'm assuming this is because the Aptoide store is trying to install itself, but of course is blocked by the Android setting that won't allow unknown sources.
My question: where do you suppose this uninstalled package is hiding? If I try to use the ADB uninstall command as if it were already installed, will that expunge it?

Disabling Device Administrators triggers Apps getting activated again

Update (28. Sep. 2014):
Did some more research on that matter for I found this really annoying. Deactivated Apps shall remain deactivated, even more so for as long as we don't have root yet.
Figured finally out (reproducible) that it's Disabling Device Administrators to trigger (some) Apps to get activated again.
Steps to reproduce:
Goto Settings -> Apps -> All
Deactivate e.g. Chrome, Google+, Hangouts, File Commander, Gmail, Maps, Play Store, Sony Select or Video Unlimited (so it's not only the GAPPS coming back).
Check the App Drawer, all the above should no longer be visible.
Goto Settings -> Security -> Device Administrators: Disable a Device Admin (BTW: Enabling does not re-activate Apps, only deactivation!)
Check the App Drawer again and find all of the above deactivated Apps have re-appeared.
This works in 23.0.A.2.98 (customized DE) as well as 23.0.A.2.105 (customized UK).
Sony: please fix this asap.
Devs: please, please give us root. The phone is worth it
Original assumption (OUTDATED):
Noticed a strange behaviour in builds 23.0.A.2.98 (customized DE) and builds 23.0.A.2.105 (customized UK) w.r.t. deactivated Apps getting automatically re-activated after changing language settings.
Started off with 23.0.A.2.98 (customized DE) on my phone and deactivated e.g. Chrome, Google Play Store, Google Play Services and some other Apps. Now, as I wanted to make some screenshots in English, I changed language settings from German to English. That moment Chrome, Google Play Services and otheres (but not all of them) got automatically re-activated and also (re-)appeared in the App drawer. Changing the phone back to German did not help as still some Apps keep getting re-activated after say a re-start of the phone.
Then, installed 23.0.A.2.105 (customized UK), immediately set it to German during first boot, deactivated same apps as before and guess what... same here.
It looks as if whenever you set your phone to use a language different to the one for which the build was localized for this problems shows.
Can anyone please try and confirm?

This explains this reactivating of Apps. I was trying to deactivate Admin for the Sony Enterprise something. It re-activates automatically and reactivates some of the disabled apps. Not all though...
Very anoying. Especially that Sony gives themselves admin rights again after I deactivated it.... hmmm.

msm1111 said:
Very anoying. Especially that Sony gives themselves admin rights again after I deactivated it.... hmmm.
Click to expand...
Click to collapse
Happy to see (well, kind of, for it shouldn't be present in the first place) that finally someone has been able to reproduce the bug.
In order to get rid of admins "Sony Enterprise API" and "Sony My Xperia" do the following:
Download ADB and store it somewhere on you PC.
Enable USB debugging on the phone and connect it to your PC.
Open a command window and navigate to where you stored ADB.
Type "adb shell" at the prompt, hit ENTER and and the prompt changes to "[email protected]:/ $"
To block "Sony Enterprise API", issue command: "pm block com.sonymobile.enterprise.service"
To block "Sony My Xperia", issue command: "pm block com.sonymobile.mx.android"
While we are at that (though not an Admin, yet annoying), to block "What's New", issue command: "block com.sonymobile.advancedwidget.entrance".
The result of the block commands should look like "Package %PACKAGE_NAME% new blocked state: true. If still "false", you have to deactivate the corresponding admin in the settings first and re-issue the command again.
Only thing I have not been able to figure out yet is how to remove/block admin "Configuration Agent" but that one does not turn on itself (like the "Sony Enterprise API" does).

sxtester said:
Only thing I have not been able to figure out yet is how to remove/block admin "Configuration Agent" but that one does not turn on itself (like the "Sony Enterprise API" does).
Click to expand...
Click to collapse
Ah, thank you!
Configuration agent is: pm block com.sonymobile.deviceconfigtool

Wonderful, that removed my last (unwanted) one.

Thanks. I'll try it on Sunday! Is this enterprise stuff actually good for something? Or just tracking.

msm1111 said:
Thanks. I'll try it on Sunday! Is this enterprise stuff actually good for something? Or just tracking.
Click to expand...
Click to collapse
This is mainly for policy enforcement on mobiles given to employees by their company.
Check this for more info: http://developer.sonymobile.com/201...-work-with-our-sdk-and-become-a-sony-partner/

Just a quick note to say thanks to the guys who wrote this one up. I managed to follow the instructions and get rid of the whats new icon ive lost a bit of my touch though as this is not for those who don't know what sdk is.
pm block com.sonymobile.enterprise.service with this one I was getting: "False" without knowing how to change it to "true"

sxtester,
Thanks! It worked! I got rid of this stuff. I needed some attemps and reboots in between.
For "com.sonymobile.enterprise.service" you need to first disable admin and block "com.sonymobile.mx.android", reboot, then disable admin for the enterpriseAPI, block, reboot. Now its gone
I also successfully blocked "com.sonymobile.advancedwidget.entrance", "com.sony.smallapp.launcher" and "com.sony.smallapp.app.widget"
As I am not so familiar in adb, may I ask what is the difference between blocking and disabling (I guess its the same disable I can do in Settings/Apps)? I realized the blocked packages do not show up in the "pm list packages" anymore. Disabled ones do. Is there a list to see what was blocked? Thanks.

Btw I can also confirm that the OP is correct. When I first disabled Sony enterprise most or all of my disabled apps were re enabled.

Every thing worked great, thanks for help!

Thank you!!! Worked great Z3

PM BLOCK commands don't work...
I tried what was suggested above, but after I entered my ADB SHELL, the PM BLOCK command didn't work. I used the latest ADB that was installed on my system, but the only command that seems relevant to this was: PM DISABLE. I used that with the packages mentioned but they didn't get disabled. I had to disable them manually again after rebooting.

m0b1f0n3 said:
I tried what was suggested above, but after I entered my ADB SHELL, the PM BLOCK command didn't work. I used the latest ADB that was installed on my system, but the only command that seems relevant to this was: PM DISABLE. I used that with the packages mentioned but they didn't get disabled. I had to disable them manually again after rebooting.
Click to expand...
Click to collapse
As you didn't specify the version of ADB, try the following:
Download EasyRoot Tool from http://forum.xda-developers.com/showthread.php?t=2784900
Don't run the tool itself, it won't work on the Z3/Z3C! However, it contains a very slim ADB version 1.0.31 which worked for me.
Unpack the ZIP to a directory of your choice.
Open a CMD Window and navigate to %YOUR_FOLDER%\EasyRootTool v12.3\files
Connect you phone and issue the PM block commans as described above.

PM BLOCK commands still don't work...
sxtester,
Thanks for your response. I tried all sorts of ADB versions (1.0.25) including the one you suggested. I had no luck. Once I issued any of the commands above, I got the message: "Error: unknown command 'block'". I am not sure what more I can do at this point.
Any ideas?

m0b1f0n3 said:
sxtester,
Thanks for your response. I tried all sorts of ADB versions (1.0.25) including the one you suggested. I had no luck. Once I issued any of the commands above, I got the message: "Error: unknown command 'block'". I am not sure what more I can do at this point.
Any ideas?
Click to expand...
Click to collapse
I used "hide" command and it worked like a charm, i.e.: pm hide com.sony...
Hope it will help.

[ROOT] SM-T707A - Lollipop with SuperSu - Xposed & Debloated - Part II

Root SM-T707A on Lollipop with SuperSu - Xposed & Debloated - Part II
Where are we right now?
* Part I: Flash Stock Lollipop 5.0.2.
* Part II: Gain Root access for Lollipop with SuperSU. <---- YOU ARE HERE!
* Part III: Flash Xposed Framework thru Flashfire.
* Part IV: Debloat the tablet from both AT&T and most of Samsung stuff.
* Part V: Improve usability and aspect with Xposed Modules.
Once again, some words of our sponsors: NO, I'm NOT resposible for any consequence originated from the use of this guide, being that the death of your tablet, or your smart tv, the Panama Papers or Luis Suarez just playing rough with Filipe Luiz's foot. Whatever happens to your tablet, it's ON YOU.
Introduction (PLEASE READ!):
This guide works as a continuation of Part I, so we assume you flashed KitKat and applied Lollipop updates as described.
If you are already on Lollipop and have several weeks using it, of course you can try this guide, but I STRONGLY SUGGEST to start from zero, backup your files and use the guidelines on Part I of this guide.
Part II: Gain Root access for Lollipop with SuperSU
IMPORTANT - During the first boot on our brand new lollipop, don't try to connect to your WiFi and remove your SimCard if availble before even selecting any option. We don't want any internet at this time.
Our first move in Lollipop is to Reject all the AT&T offers..
Then accept terms of Samsung EULA (and hit No Thanks below)...unless you want to share information with Sammy.
Then you can put your name (I didn't), it' s up to you.
Disable the 3 checkboxes for location services (you can enable this later).
Then skip the Samsung Account creation and hit also Next on my "Find my mobile" screen without doing nothing.
Finally, you'll reach the Android Desktop.
Setting the stage for rooting with KingRoot
Still avoiding any conection to the internet, go to your apps and tap Settings.
Before doing nothin, I strongly suggest you change your language to english in case you use another.
If your first language is English, you're good.
If it's not, you can change it on General TAB, then "Language and Input".
After this, tap the Device tab, choosing then Display option on the left.
Choose Screen timeout and select 10 minutes.
Now select Lock screen on your left and Screen lock on your right. Tap "None".
Now go to "General" tab and tap "Security".
Enable the Unknown sources checkbox and press OK on the popup.
Press home button. Now you can connect to your Wifi.
The moment you got Internet, Samsung will start forcing some updates on your tablet.
At the same time, several Google popups will ask you to "regularly check device for security".
Decline them all the time!
There is a "Games" app that loves to open itself without asking
When that happens, it will introduce you to an agreement that you will REJECT.
If it doesn't show, better. But it will eventually.
Now enter the Play Store and Log in with your credentials.
Accept the playstore conditions when prompted. If you are kicked out of the app just enter again.
Still inside Playstore, now swipe from your left side border to gain access to the menu.
Tap "My Apps" and use the "Update All" button on the right.
Accept all APP Permisions (seven times in my case).
The update process will start. This will take some time so BE PATIENT and do nothing else.
When everything is updated, you'll notice some warning on your status bar.
Swipe down your status bar. It will ask several times to Update Google Play Services.
Tap any of update offers for Play Services. Playstore will open again offering the update.
Hit Update and Accept. When the update of Google Play Services is finished, hit the Open button.
You gain access to Google Settings. Tap Security.
Disable "Remote locate this device" - "Allow remote lock and erase".
Disable also "Scan device for security threats" and "Improve harmfull app detection" (unless is greyed out).
Hit the home button and go back to desktop.
Installing KingRoot
For the next step, you need to download these files on your PC:
* Kingroot V4.90
* RemoveKing
Copy them on your tablet's internal memory. Specifically on the root of your internal memory. If you copy them inside a folder, later commands will fail.
Back to your tablet's desktop, look for the folder icon on the bottom left corner. This will open the Samsung File Manager. Look for "Device Storage" on the left column. If you copied the files correctly, you'll find both on the right pane of the display. Extract the RemoveKing.zip file by tapping it and clicking "OK". A RemoveKing folder will appear on the root of your filesystem.
Now open the Kingroot V4.90 file. Hit Next and then Install.
If a google warning appears citing - "Installation blocked". Hit "Install anyway" (unsafe).
If it doesnt, just hit Open. A blue screen shows up with the legend "ROOT auth".
Swipe upwards twice (assuming you're holding your tablet in portrait).
Now hit the "Try it" button. The app will verify root status in a matter of seconds.
Now tap the "TRY THE ROOT" button at the bottom.
When the root is sucessful, you'll be asked to "Forbid Knox".
Tap Cancel and press the home button. Now you are rooted with Kingroot.
Installing and preparing Terminal Emulator
Now that we are rooted, enter the playstore and install the app "Terminal Emulator for Android". Open it. You'll notice some small font selected so, hit the 3 dots on the right upper corner and go to preferences. On Font Size choose 24 pt. Hit the back physical button of the tablet. Now the "white letters" become readable. And it shows something like:
Code:
klimtlteatt:/ $
Next type the following and hit enter:
Code:
su
A Kingroot popup will ask for root permission. Tap "Allow".
Now the $ symbol will change for #.
Next you hit the HOME button to exit the app briefly (don't close the app in any other way, just hit the HOME button).
Uninstalling KingRoot
After that, go to your apps and enter the KingRoot app.
Now tap the 3 dots on the upper right corner and select "General Setting". Disable "Smart Authorization", then disable "Enable Root Authorization". Finally choose below "Uninstall KingRoot". Hit Continue. Uncheck "Backup Root" when prompted and hit OK. When all is over, you're back to the desktop. Go back again to your apps and uninstall Purify.
Applying the Scripts
Open again Terminal Emulator app (thru the app Icon) . Now we need to hit a couple of scripts by moving first to our extracted folder by entering the following command on the terminal (plus enter):
Code:
cd /sdcard/RemoveKing/
To run the first script type (then press enter):
Code:
./step0.sh
It just takes 3 seconds, then type the following and press enter:
Code:
./step1.sh
This last script will ask for a confirmation during its process.
Type just an "y" and hit enter: (WARNING, the Y won't appear on your display after typing it)
Code:
y
You'll notice a bunch of errors, don't mind them.
Installing SuperSU
Now hit the home button and go to the play store.
Search and Install SuperSU (free version). Open it. Choose Expert.
The app will ask "The SU binary needs to be updated, continue?".
Hit Continue and then choose "Normal" when asked on the next popup.
You'll receive an "Installation Sucess!". Tap the Reboot option.
Congratulations! You are now rooted with SuperSU.
After rebooting, enter the Terminal app once more, and tap the X on the right upper corner and hit OK.
That will finish the current terminal session.
If you're interested in getting Xposed Framework, go to part 3 of this guide.
If you're just interested in debloating the SM-T707A and improve its performance, go to part 4 (Soon).
Part 5 is where I discuss the modules I'm using on Xposed and also some Playstore apps to improve functionality, and remove as much Touchwiz as possible, while also working on better battery life (Soon too).
Final Considerations (suggested reading - not mandatory)
While this guide may seem easy to carryout, it took me almost a month to get SuperSu to work on Lollipop.
I'm no coder (a soon to be Certified Public Accountant), and the real magic to pull this off was to try many combinations of different app versions, different situations with google services and several strategies with the script and superSU. In fact, most of KingRoot versions don't work on this tablet to get root, also tried SuperSume app from the playstore. The same could be said for KingoRoot (don't confuse it with KingRoot), it worked but I couldn't remove it without losing root.
Why I'm telling you this? Because using KingRoot and similar apps to root this tablet, your mileage may vary while doing it. In fact, even while applying my first two guides there's a respectable chance of KingRoot tool failing to root your tablet. If you followed this couple of guides to the last comma, your chances of success are very close to 100%. But I have noticed in similar Galaxy Tab S threads, that the use of KingRoot and KingoRoot to achieve root is just a matter of using the root tool many times until it works, and I wanted to avoid you guys going thru that. To take sucess rate as close as it gets to 100%, we took all of this steps. They were included to avoid many failures. I believe they're are 99% flawless to achieve root on Lollipop with SuperSU.
Also, the second script won't remove many KingRoot files, because it was thought for KingoRoot on KitKat.
I have to give myself more time to develop something that could really clean up the last traces of KingRoot.
Special Thanks
* @chixvicious - For showing how to achieve the same over KitKat and KingoRoot instead.
* @bakageta - For creating these scripts for the Alcatel smartphone over KingoRoot.
* @Kingxteam - For developing KingRoot to allow us to root our device.

Oh wow, I had forgotten all about those scripts. Glad to see someone getting some use out of them.

bakageta said:
Oh wow, I had forgotten all about those scripts. Glad to see someone getting some use out of them.
Click to expand...
Click to collapse
They were life-savers, thanks a lot for them!!

Broken links?
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.

zopert said:
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
Click to expand...
Click to collapse
Thanks for the heads up!!. I'll check them ASAP.
EDIT: All links are fixed!!

kainanmaki said:
Thanks for the heads up!!. I'll check them ASAP.
EDIT: All links are fixed!!
Click to expand...
Click to collapse
Man, can't thank you enough for this...So great for someone like me with little knowledge for all this magic. I am gonna do this when I get back from vacation. Can't wait for the rest of it!
Thanks again

ElCid43 said:
Man, can't thank you enough for this...So great for someone like me with little knowledge for all this magic. I am gonna do this when I get back from vacation. Can't wait for the rest of it!
Thanks again
Click to expand...
Click to collapse
I hope to get part IV and V in no more than 10 days...
I'm in the process of testing removing/freezing many services, just a sneak preview:
So far I was able to disable close to 180-190 apps/services from a total 250-260 (can't remember the exact number).
Of course there are some key services removed (for e.g multi windows, but that's just one service).
Still you can easily remove like 165 without losing any stock functionality. That's how much bloated the tablet is.
Removing useless stuff from samsung and 3rd party (eg. VPN, Policy Updates) or more evident like MultiWindow, the gallery app or even the file browser.
Or the weird ones like the phone app that is hidden and you can't use (you can disable it and still keep LTE Data).
More to come.

Need Help - Having Untimely Reboot Issues
Wow...Thanks SO MUCH for this guide! It gives me hope that I can actually enjoy using my T707A to the fullest!
Alas, I need some assistance PLEASE:crying:
I'm following your guide to the letter, and I've successfully achieved Part 1. Part 2, however, alludes me even after many, many tries. Here is what is going right and wrong:
a) Achieved root with KingRoot
b) installed and achieved SU with Terminal
c) ISSUE - KingRoot (or something) reboots the tablet during Uninstall, which kills SU access obtained with Terminal
d) ISSUE - after reboot, I no longer have permission to run the scripts to uninstall KingRoot
Is there another way for me to do this? As long as the tablet is rebooting during uninstall of KingRoot I have no SU access, so can't do anything but start over and experience the same thing time after time.
ANY assistance would be so very much appreciated...MOST humbly & sincerely...Tom

Where did you find the alternate method??
zopert said:
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
Click to expand...
Click to collapse
Hi...I am VERY interested in your "alternate" method for replacement of KingRoot with SuperSU that actually worked. Would you be so kind as to share that with me? I'm having huge troubles (see my post) replacing KingRoot as it reboots thus killing my SU access necessary to run the uninstall scripts provided in OP. Any help would be GREATLY appreciated. MOST humbly & sincerely...Tom

TomandJonna said:
Wow...Thanks SO MUCH for this guide! It gives me hope that I can actually enjoy using my T707A to the fullest!
Alas, I need some assistance PLEASE:crying:
I'm following your guide to the letter, and I've successfully achieved Part 1. Part 2, however, alludes me even after many, many tries. Here is what is going right and wrong:
a) Achieved root with KingRoot
b) installed and achieved SU with Terminal
c) ISSUE - KingRoot (or something) reboots the tablet during Uninstall, which kills SU access obtained with Terminal
d) ISSUE - after reboot, I no longer have permission to run the scripts to uninstall KingRoot
Is there another way for me to do this? As long as the tablet is rebooting during uninstall of KingRoot I have no SU access, so can't do anything but start over and experience the same thing time after time.
ANY assistance would be so very much appreciated...MOST humbly & sincerely...Tom
Click to expand...
Click to collapse
I had that problem many times, the uninstall reboots the tablet before you can establish SuperSu.
The most reliable way I found of overcoming this is to follow the exactly in this order and without stopping to much because google wants to run updates behind scenes that mess with our process (that's why sometimes it works and sometime it doesn't). My recommendation is to start over from scracth again (I know it's boring). I'll probably do it again on my tablet just to validate and to try some other things related to the original services).

TomandJonna said:
Hi...I am VERY interested in your "alternate" method for replacement of KingRoot with SuperSU that actually worked. Would you be so kind as to share that with me? I'm having huge troubles (see my post) replacing KingRoot as it reboots thus killing my SU access necessary to run the uninstall scripts provided in OP. Any help would be GREATLY appreciated. MOST humbly & sincerely...Tom
Click to expand...
Click to collapse
Other thing I forgot to ask, did you started clean from the first part or just started with part 2 of the guide?

Will this method trip Knox?

i need * RemoveKing file now...

[How To] Bypass Lloyds and Santander Root Detection

Hi All,
I've seen mention of Santander but not of Lloyds bypassing the root detection. After much trial and error it's quite simple and my method will bypass both Santander and Lloyds. If bypassing Santander just do the same for the Santander app as ive said to do with Lloyds.
<--Update 08/06/19-->
Having flashed a new rom and following my steps again I received the detection message again but was resolved by using the Canary build of Magisk Manager.
To get Magisk Manager Canary click the link below:
https://github.com/topjohnwu/magisk_...pp-release.apk
Once installed, open Magisk Manager and go to
settings > Update Channel > Canary
Go back to Magisk home screen and swipe down to check for updates, you'll receive an update for the canary build. Once you update follow the guides original steps below.
<--End of update-->
In Magisk Manager Settings:
Enable Magisk Hide
Enable Sytemless Host
And if the option is available select "Hide Magisk"
In Adaway:
Download my exported blacklist from:
https://drive.google.com/file/d/1xCBB4iVA65gJTTYqbhU1qTlghVYyAL1S/view?usp=drivesdk
Then in adaway click the 3 dots in the top right to open the menu, select "Your Lists" then press the menu button again in the top right and press "Import all lists" and select the file you downloaded.
With the urls added go back to the adaway main screen and press "Download Files and Apply ad blocking" and Reboot device. If "Download Files and Apply Ad Blocking" doesn't appear, click "check for updates" and then download them which will do the same thing.
Once your phone has restarted install the Lloyds Banking app but don't open it. Go into Magisk Manager and select Magisk Hide from the menu and tick the Lloyds Banking app. Reboot phone and Lloyds should work perfectly!
I managed to do this from researching other threads and adding my own bits in so credit due elsewhere as well, as usual you can follow this guide but do so at your own risk, i take no responsibility

This should also work for Halifax and TSB but with a different URL nice work but what happens if they fix this? No banking app again....
Also do you know how to get past Natwest?

Doesn't work for me.

Hi Steve,
This is the first time ive noticed an application that has gone to greater lengths and was relatively easy to bypass. Given how long it took to come up with this technique of connecting to a url to blacklist your device i cant see them coming up with something new anytime soon.
All that is required to bypass this new technique is to log dns requests in Adaway and with the listed urls the app connected to for the login you simply block the urls and leave 1 out. Take for example Lloyds used 3 urls, i blocked two leaving only one allowed but Lloyds couldnt connect so that url was genuinely used to login, i then knew to allow that url and focus on the other two finally figuring out it was that url i listed that was being used to connect and block my device. With the app unalee to connect to that url it cannot verify if my device is blacklisted. Its time consuming as you need to restart after each new url you blacklist but its simple to do.

Muresan01 said:
Doesn't work for me.
Click to expand...
Click to collapse
Are you on the new Magisk 17.1? And after inserting the url to adaway you rebooted the device then installed lloyds then hidden it in magisk and rebooted again?

Muresan01 said:
Doesn't work for me.
Click to expand...
Click to collapse
Thread will be updated in a minute with a link to an Adaway blacklist export i made, i tried on a rooted S7 after seeing your post and it didnt work but i did it after a few tries, it seems i missed out a few urls.

Muresan01 said:
Doesn't work for me.
Click to expand...
Click to collapse
Thread updated

thanks @steve51184. Lloyds bank app works for me. Wondering how to go about for the Halifax bank app.

Elvisnazareth said:
thanks @steve51184. Lloyds bank app works for me. Wondering how to go about for the Halifax bank app.
Click to expand...
Click to collapse
Ill have a look into Halifax later and see if i can update the adaway list to work with all 3. If i do ill let you know and update the link

mrsweet1991 said:
Hi All,
I've seen mention of Santander but not of Lloyds bypassing the root detection. After much trial and error it's quite simple and my method will bypass both Santander and Lloyds. If bypassing Santander just do the same for the Santander app as ive said to do with Lloyds.
First go into the Lloyds app info (hold on Lloyds App icon and select "App Info") or you can do the same by going to "Settings > Apps > Lloyds Bank" and then select "Storage" and press "Clear Data". With all the stored information removed uninstall the Lloyds Banking app completely and reboot your device.
In Magisk Manager Settings:
Enable Magisk Hide
Enable Sytemless Host
And if the option is available select "Hide Magisk"
In Adaway:
Download my exported blacklist from:
https://drive.google.com/file/d/1xCBB4iVA65gJTTYqbhU1qTlghVYyAL1S/view?usp=drivesdk
Then in adaway click the 3 dots in the top right to open the menu, select "Your Lists" then press the menu button again in the top right and press "Import all lists" and select the file you downloaded.
With the urls added go back to the adaway main screen and press "Download Files and Apply ad blocking" and Reboot device.
Once your phone has restarted install the Lloyds Banking app but don't open it. Go into Magisk Manager and select Magisk Hide from the menu and tick the Lloyds Banking app. Reboot phone and Lloyds should work perfectly!
I managed to do this from researching other threads and adding my own bits in so credit due elsewhere as well, as usual you can follow this guide but do so at your own risk, i take no responsibility
Click to expand...
Click to collapse
Works perfectly
Thank you !

Muresan01 said:
Works perfectly
Thank you !
Click to expand...
Click to collapse
Great to hear

Awesome, works for Halifax app as well!

This also allows the Metro Bank app to run. Thanks

Could you make this to work with Digibank DBS Indonesia? I'm stuck to stock rom because of this

steve51184 said:
This should also work for Halifax and TSB but with a different URL nice work but what happens if they fix this? No banking app again....
Also do you know how to get past Natwest?
Click to expand...
Click to collapse
Natwest in UK does not prohibit rooted phones.

Deleted

haybill said:
Sent from my SM-N910F using Tapatalk
Sorry, removed my post-- found both XDA source and FDroid source for Adaway, doh!!
Click to expand...
Click to collapse
Just want to say Thanks for putting this together, there are several Threads giving info but this one has got it all in an easy to use format.
Sent from my SM-N910F using Tapatalk
And, finally, after about a month of failing to access my Bank account--- success, after following all the necessary actions, I can now once again use Online Banking via the App.
Let's hope they don't make further changes that mean we can't, in the future.

Sadly it doesn't work for me.
Santander app on Oneplus 5T.
Get the solid red screen for a second or so then "Santander UK has stopped"
Is this what usually happens if the app detects root?
Cheers!

spwyatt said:
Sadly it doesn't work for me.
Santander app on Oneplus 5T.
Get the solid red screen for a second or so then "Santander UK has stopped"
Is this what usually happens if the app detects root?
Cheers!
Click to expand...
Click to collapse
I'd expect the app to tell you that you have a rooted phone instead of crashing. I'd try clearing data again, then removing the app completely and making your you followed the instructions fully.
If you haven't Magisk 17.1 then getting this together with the latest stable manager is also recommended. For a weird reason 16.4 has issues for me after some ROM update and wouldn't pass the Safetynet check any longer (even after complete removal and magisk reinstall). However, 17.1 somehow fixed it for me.
While I'm no fully sure about Santander, uninstalling and reinstalling the app also was essential for Lloyds on my phone (just clearing data and adding + applying the blacklist still showed the rooted message).
Good luck,

This thread is amazing, good work OP!
I am having an issue unfortunately when it comes to selecting the downloaded item. I'm unable to select the file from my Downloads, slight grey hue and long holding tap does nothing. (I'm trying to import)
I've checked and in the Downloads manager the file definitely exists, I just can't seem to apply it.
Any ideas?
EDIT: I solved the issue by granting Adaway storage permissions and importing the file from my Google Drive.

Fire 7" 9th gen, FireOS 6.3.1.2 , Google playstore chrashing, need advice

Hi there,
got an Fire 7" 9th gen, downgraded os to 6.3.1.2 build 000217050244 according to instructions here in the forum.
Also did this here successfully. https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
So far, the Amazon fire runs fine except when i try to run the google playstore.
Pushed the following files to the fire tablets "download" folder:
- com.google.android.gsf_5.1-1743759-22_minAPI22(nodpi)_apkmirror.com.apk
- com.google.android.gsf.login_5.1-1743759-22_minAPI21(nodpi)_apkmirror.com.apk
- com.android.vending_7.0.25.H-all_0_-80702500_minAPI14(nodpi)_apkmirror.com.apk
- com.google.android.gms_11.5.09_(230-164803921)-1109230_min_API21(armeabi-v7a)(nodpi)_aplmirror.com.apk
on the device, installed them using the filemanager that comes default. All good so far.
i am even able to start the playstore, i starts and i enter my payment credentials , after that i can browse the apps, but after selecting "install" on any app in the playstore, it just crashes. I am not able open playstore again, i opens and instantly closes.
Re-installing the apk files mentioned above helps to get tht playstore opened again but then same as before -> select "install" -> crash -> not able to open playstore again.
Since i am not aware of any system logs on the fire tabled, i have no clue whats going on.
Can anyone point me in some direction where to look for the cause of the issue?
Thanks and best
Phoken

phoken said:
Hi there,
got an Fire 7" 9th gen, downgraded os to 6.3.1.2 build 000217050244 according to instructions here in the forum.
Also did this here successfully. https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
So far, the Amazon fire runs fine except when i try to run the google playstore.
Pushed the following files to the fire tablets "download" folder:
- com.google.android.gsf_5.1-1743759-22_minAPI22(nodpi)_apkmirror.com.apk
- com.google.android.gsf.login_5.1-1743759-22_minAPI21(nodpi)_apkmirror.com.apk
- com.android.vending_7.0.25.H-all_0_-80702500_minAPI14(nodpi)_apkmirror.com.apk
- com.google.android.gms_11.5.09_(230-164803921)-1109230_min_API21(armeabi-v7a)(nodpi)_aplmirror.com.apk
on the device, installed them using the filemanager that comes default. All good so far.
i am even able to start the playstore, i starts and i enter my payment credentials , after that i can browse the apps, but after selecting "install" on any app in the playstore, it just crashes. I am not able open playstore again, i opens and instantly closes.
Re-installing the apk files mentioned above helps to get tht playstore opened again but then same as before -> select "install" -> crash -> not able to open playstore again.
Since i am not aware of any system logs on the fire tabled, i have no clue whats going on.
Can anyone point me in some direction where to look for the cause of the issue?
Thanks and best
Phoken
Click to expand...
Click to collapse
That's the problem, Google API services version is wrong. Make sure the Google API services version is corrected to Android version with 7.1.2 and API 25.
Try it to remove any Amazon apps folder like DeviceSoftwareOTA, DeviceSoftwareOTAContracts in /system/priv-app directory, install Google API services (Google Account Manager - v7.1.2, minimum API 25, Google Services Framework - v7.1.2, minimum API 25) as a system application or user application and reboot.

phoken said:
Hi there,
got an Fire 7" 9th gen, downgraded os to 6.3.1.2 build 000217050244 according to instructions here in the forum.
Also did this here successfully. https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
So far, the Amazon fire runs fine except when i try to run the google playstore.
Pushed the following files to the fire tablets "download" folder:
- com.google.android.gsf_5.1-1743759-22_minAPI22(nodpi)_apkmirror.com.apk
- com.google.android.gsf.login_5.1-1743759-22_minAPI21(nodpi)_apkmirror.com.apk
- com.android.vending_7.0.25.H-all_0_-80702500_minAPI14(nodpi)_apkmirror.com.apk
- com.google.android.gms_11.5.09_(230-164803921)-1109230_min_API21(armeabi-v7a)(nodpi)_aplmirror.com.apk
on the device, installed them using the filemanager that comes default. All good so far.
i am even able to start the playstore, i starts and i enter my payment credentials , after that i can browse the apps, but after selecting "install" on any app in the playstore, it just crashes. I am not able open playstore again, i opens and instantly closes.
Re-installing the apk files mentioned above helps to get tht playstore opened again but then same as before -> select "install" -> crash -> not able to open playstore again.
Since i am not aware of any system logs on the fire tabled, i have no clue whats going on.
Can anyone point me in some direction where to look for the cause of the issue?
Click to expand...
Click to collapse
- reset device
- install Google Play Store via Amazon Toolbox which will deliver the build most appropriate for your device
- resist temptation to 'fix' previous mistakes with further hacks (↑↑) that will likely yield a FrankenFire which will eventually have to be rest/rebuilt.
https://forum.xda-developers.com/hd8-hd10/development/official-amazon-fire-toolbox-v1-0-t3889604

DB126 said:
- reset device
- install Google Play Store via Amazon Toolbox which will deliver the build most appropriate for your device
- resist temptation to 'fix' previous mistakes with further hacks (↑↑) that will likely yield a FrankenFire which will eventually have to be rest/rebuilt.
https://forum.xda-developers.com/hd8-hd10/development/official-amazon-fire-toolbox-v1-0-t3889604
Click to expand...
Click to collapse
Wonderful, this did the trick. Playstore now runs and i am able to install and run apps from the playstore.
Thanks and best
Phoken