Database Develop

[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...

Nougat Plugins for Tasker

I've recently upgraded to Nougat on my rooted phone and wondered how best to replicate my old Tasker profiles that were reliant on Secure Settings which appears to no longer work on Nougat (it says it cannot find root)/
The main functionality i want is the ability to turn on/off:
Airplane mode
Location Completely (when screen off)
GPS when opening apps that use maps
Mobile data
Can anyone suggest the best way to get this functionality back if its possible?

farquea said:
I've recently upgraded to Nougat on my rooted phone and wondered how best to replicate my old Tasker profiles that were reliant on Secure Settings which appears to no longer work on Nougat (it says it cannot find root)/
The main functionality i want is the ability to turn on/off:
Airplane mode
Location Completely (when screen off)
GPS when opening apps that use maps
Mobile data
Can anyone suggest the best way to get this functionality back if its possible?
Click to expand...
Click to collapse
You could try some of the run shell commands from this thread https://forum.xda-developers.com/u/tasker-tips-tricks/best-run-shell-commands-tasker-t3419204 or use the AutoTools plugin https://play.google.com/store/apps/details?id=com.joaomgcd.autotools

Majority (if not all) of Secure settings stuff is now easily available on AutoTools.

Thanks, just installed it and playing around with it and when i try to run a task it tells me 'No pemission to change settings' i see the adb command being talked about. Do i have to run that even though i'm rooted or do i just have something configured wrong?

farquea said:
Thanks, just installed it and playing around with it and when i try to run a task it tells me 'No pemission to change settings' i see the adb command being talked about. Do i have to run that even though i'm rooted or do i just have something configured wrong?
Click to expand...
Click to collapse
You're gonna have to run that command. It should work fine then.

farquea said:
Thanks, just installed it and playing around with it and when i try to run a task it tells me 'No pemission to change settings' i see the adb command being talked about. Do i have to run that even though i'm rooted or do i just have something configured wrong?
Click to expand...
Click to collapse
What ADB command are you talking about?
farquea said:
I've recently upgraded to Nougat on my rooted phone and wondered how best to replicate my old Tasker profiles that were reliant on Secure Settings which appears to no longer work on Nougat (it says it cannot find root)
Click to expand...
Click to collapse
I'm on Nougat as well and I'm using Secure Settings every day, it works fine for me...

The adb command worked but my bigger problem was that my phone had lost root. All fixed now tho

You can replace Secure Settings with SecureTask plugin. Free and it works great.

kitkat85 said:
You can replace Secure Settings with SecureTask plugin. Free and it works great.
Click to expand...
Click to collapse
Sounds great. Can you please provide a link? Thanks!

AJH101 said:
Sounds great. Can you please provide a link? Thanks!
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.balda.securetask

kitkat85 said:
https://play.google.com/store/apps/details?id=com.balda.securetask
Click to expand...
Click to collapse
Fantastic, thank you.
---------- Post added at 08:07 AM ---------- Previous post was at 07:25 AM ----------
kitkat85 said:
https://play.google.com/store/apps/details?id=com.balda.securetask
Click to expand...
Click to collapse
Forgive me, is this not very similar to the Auto Tools plug in? [emoji4]

AJH101 said:
Fantastic, thank you.
---------- Post added at 08:07 AM ---------- Previous post was at 07:25 AM ----------
Forgive me, is this not very similar to the Auto Tools plug in? [emoji4]
Click to expand...
Click to collapse
Simply better. First of all it's free. In addition it has a lot of features like sync settings, failed login monitoring, settings monitoring, change pin/password, log information, data usage and much more, nothing comparing to automess.

kitkat85 said:
Simply better. First of all it's free. In addition it has a lot of features like sync settings, failed login monitoring, settings monitoring, change pin/password, log information, data usage and much more, nothing comparing to automess.
Click to expand...
Click to collapse
Thanks. I will start digging!

kitkat85 said:
Simply better. First of all it's free. In addition it has a lot of features like sync settings, failed login monitoring, settings monitoring, change pin/password, log information, data usage and much more, nothing comparing to automess.
Click to expand...
Click to collapse
@automess... I have used both and though autotools is 2.99 I find it more user friendly. But both are equally up to task.

digitalpig82 said:
What ADB command are you talking about?
I'm on Nougat as well and I'm using Secure Settings every day, it works fine for me...
Click to expand...
Click to collapse
Hi, I'm in nougat with a ROM but I can't open tasker. I hope anyone can help

@farquea,::if you want to stick with securesettings in noughat,here is the work around i am using, found the fixfrom superSu forum..
Obviously i am using superSu to give root access for secure settings..
First flash superSu in systemless mode in twrp.
After reboot, using terminal emulataor type the following command
su
echo "BINDSYSTEMXBIN=true" >> /data/.supersu
and reflash superSU from twrp..securesettings will be enabled...
Reference :
1) https://plus.google.com/+Chainfire/posts/N6EARb8LF3d
2) https://forum.xda-developers.com/showpost.php?p=66140836&postcount=5493
This may help you if u want to stick with securesettings

vedhavyga said:
@farquea,::if you want to stick with securesettings in noughat,here is the work around i am using, found the fixfrom superSu forum..
Obviously i am using superSu to give root access for secure settings..
First flash superSu in systemless mode in twrp.
After reboot, using terminal emulataor type the following command
su
echo "BINDSYSTEMXBIN=true" >> /data/.supersu
and reflash superSU from twrp..securesettings will be enabled...
Reference :
1) https://plus.google.com/+Chainfire/posts/N6EARb8LF3d
2) https://forum.xda-developers.com/showpost.php?p=66140836&postcount=5493
This may help you if u want to stick with securesettings
Click to expand...
Click to collapse
You can actually enter that command in TWRP's terminal as well before you flash SuperSU. Saves that one extra reboot.

JRJ442 said:
You can actually enter that command in TWRP's terminal as well before you flash SuperSU. Saves that one extra reboot.
Click to expand...
Click to collapse
i think dat also..but not sure if enter both the values, will supersu install in systemless mode?

JRJ442 said:
You can actually enter that command in TWRP's terminal as well before you flash SuperSU. Saves that one extra reboot.
Click to expand...
Click to collapse
I'm using the Magisk interface and Secure Settings just works with the root method that is built into Magisk,
Also thinks like AndroidPay work with Magisk

Data dis/enable

Ok. I am running magisk....made shell cmd task of data on and off...they work....but why when I click "use root", it says device doesn't appear rooted. Could magisk be the culprit? Thanks.

Tmobilefan906 said:
Ok. I am running magisk....made shell cmd task of data on and off...they work....but why when I click "use root", it says device doesn't appear rooted. Could magisk be the culprit? Thanks.
Click to expand...
Click to collapse
Tasker cannot detect root with MagiskSU. If you attempt to select the Use Root option, you get a toast: "Error, you device doesn't appear to be rooted." However, as mentioned here, if you preface a Run Shell command with /sbin/su -c, Magisk Manager will prompt to allow Tasker root access and your command will work.
Code:
/sbin/su -c "svc data enable"

axxbat said:
Tasker cannot detect root with MagiskSU. If you attempt to select the Use Root option, you get a toast: "Error, you device doesn't appear to be rooted." However, as mentioned here, if you preface a Run Shell command with /sbin/su -c, Magisk Manager will prompt to allow Tasker root access and your command will work.
Click to expand...
Click to collapse
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.

Tmobilefan906 said:
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.
Click to expand...
Click to collapse
Didn't mean to offend will give a try a Magisk-enabled ROM today and hope will be back with ideas

Tmobilefan906 said:
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.
Click to expand...
Click to collapse
Well. Original position:
- Used RR April 16, 2017 nightly build as fresh install
- recovered Tasker from TiB backup
- created new task
- to avoid cheating assumptions created Tasker's task shortcut to run the task.
Video link is below. Pay attention to LTE symbol in the beginning of the vid. Task's goal was to disable it. The task was run via desktop shortcut
https://drive.google.com/file/d/0B8jDZdXO_06aMW5GYVJIRjBfemM/view?usp=drivesdk
Arrgh.just saw - LTE link run down before the task run - Tasker spotted my homecells and tried to setup WiFi connection (but no WLAN settings were restored). Nevertheless, it changes nothing - Task call via shortcut didn't call any root complaints, did it?
P.S. no offences again. In the cast i've intentionally shown Magisk's superuser tab to demonstrate nothing but two apps had root access. But after restore Tasker asked for 'su' perms (baloon), and was granted. Maybe, skipped 'su' perms for Tasker is Your headache?

axxbat said:
Didn't mean to offend will give a try a Magisk-enabled ROM today and hope will be back with ideas
Click to expand...
Click to collapse
u didn't offend me at all

axxbat said:
Well. Original position:
- Used RR April 16, 2017 nightly build as fresh install
- recovered Tasker from TiB backup
- created new task
- to avoid cheating assumptions created Tasker's task shortcut to run the task.
Video link is below. Pay attention to LTE symbol in the beginning of the vid. Task's goal was to disable it. The task was run via desktop shortcut
https://drive.google.com/file/d/0B8jDZdXO_06aMW5GYVJIRjBfemM/view?usp=drivesdk
Arrgh.just saw - LTE link run down before the task run - Tasker spotted my homecells and tried to setup WiFi connection (but no WLAN settings were restored). Nevertheless, it changes nothing - Task call via shortcut didn't call any root complaints, did it?
P.S. no offences again. In the cast i've intentionally shown Magisk's superuser tab to demonstrate nothing but two apps had root access. But after restore Tasker asked for 'su' perms (baloon), and was granted. Maybe, skipped 'su' perms for Tasker is Your headache?
Click to expand...
Click to collapse
What u mean skipped su perms?

Tmobilefan906 said:
What u mean skipped su perms?
Click to expand...
Click to collapse
1:48 request dialog
Sorry for late reply. Could it be so that Tasker was asking for root permission, but was not granted? Also, guess, You've checked that Tasker is in Device Administrators?
Upd. Stupid assumption. You've said , the task works when running on its own, from Tasker, but pops up the warning, when 'Use root' is checked... Not a big specialist in Magisk, but, haven't You use something like 'Hide root from apps' or alike in Magisk?

axxbat said:
1:48 request dialog
Sorry for late reply. Could it be so that Tasker was asking for root permission, but was not granted? Also, guess, You've checked that Tasker is in Device Administrators?
Upd. Stupid assumption. You've said , the task works when running on its own, from Tasker, but pops up the warning, when 'Use root' is checked... Not a big specialist in Magisk, but, haven't You use something like 'Hide root from apps' or alike in Magisk?
Click to expand...
Click to collapse
I guess I'm not too worried about it. As long as the task works, I'm fine with it. Haha

Oneplus 3T oreo and amazon appstore

Hello,
There's a little problem to use amazon appstore because you must allow it to install unknow source app.
But himself was download out of the official google store (there's not choice) then you can't allow an unknow source to install unknow source app.
Before android 8, it was possible and now how do it ?

I don't have any such problem
Unleashed by my rooted OP3T on 8.0

since root ?

rifmouk said:
since root ?
Click to expand...
Click to collapse
Since ever.
I had root since the beginning.
Unleashed by my rooted OP3T on 8.0

Since Android Oreo, "unknown sources" have been separated so now you have to allow it for each app separately. You can find it in Settings > Apps > Special access > Install unknown apps.

exactly, przemcio510,
But because "amazon appstore" was download outside from the "google play store", it doesn't appear in this list. ( but maybe there's something , i don't understand)
With Oreo, it seems the system changed , now you can allow an app to install an unknow source and NOT allow YOU to install unknow source.

rifmouk said:
exactly, przemcio510,
But because "amazon appstore" was download outside from the "google play store", it doesn't appear in this list. ( but maybe there's something , i don't understand)
With Oreo, it seems the system changed , now you can allow an app to install an unknow source and NOT allow YOU to install unknow source.
Click to expand...
Click to collapse
As I wrote earlier, there is no problem with Amazon.
It doesn't matter in which setting you are finding the unknown sources. It works just fine.
Unleashed by my rooted OP3T on 8.0

Same problem here!
RASTAVIPER said:
As I wrote earlier, there is no problem with Amazon.
It doesn't matter in which setting you are finding the unknown sources. It works just fine.
Click to expand...
Click to collapse
Well, that might be true, however for us it does NOT work, because in our case the setting can NOT be found at all
Same as rifmouk, i found the list where I should be able to enable apk installations through the Amazon App Store. However, there is no 'Amazon App Store' in that list, only a few other apps like my browsers.
I already had a lengthy discussion with the Amazon support about this. After letting me wait for a few minutes, the lady came back and asked me "Do you already have Marshmallow?"
In the end she suggested contacting One Plus, they should be able to unlock the 'install from unknown sources' setting (she didn't want to hear about that setting not being there anymore) on my phone from remote :laugh:
Anyways, I contacted them again via twitter. They told me the devs would take a look, and to have just a bit of patience. That was roughly three months ago.

or1on06 said:
Same problem here!
Well, that might be true, however for us it does NOT work, because in our case the setting can NOT be found at all
Same as rifmouk, i found the list where I should be able to enable apk installations through the Amazon App Store. However, there is no 'Amazon App Store' in that list, only a few other apps like my browsers.
I already had a lengthy discussion with the Amazon support about this. After letting me wait for a few minutes, the lady came back and asked me "Do you already have Marshmallow?"
In the end she suggested contacting One Plus, they should be able to unlock the 'install from unknown sources' setting (she didn't want to hear about that setting not being there anymore) on my phone from remote [emoji23]
Anyways, I contacted them again via twitter. They told me the devs would take a look, and to have just a bit of patience. That was roughly three months ago.
Click to expand...
Click to collapse
Can u post some screenshots?
And from a personal experience: the customer support of the Appstore is ****. I had also some long discussion about a problem with another device and they didn't have a clue, although they had people searching over the matter for weeks.
Unleashed by my rooted OP3T on 8.0

I just now installed the Amazon app store APK. Then I opened the application, logged in, and downloaded an app.
I was then prompted to change my settings to allow the downloaded app to be installed.
At this point I checked in Settings>Apps>Special access>Install unknown apps and the Amazon app is listed.
I'm in OOS 5.0.1.
So everything behaves as it should. Nothing wrong with the Amazon app or Oreo.
I suggest you wipe the data for the Amazon app and go through the process again.
Sent from my OnePlus3T using XDA Labs

I tried reinstalling it, still the same issue. Here is the list I have (can't post correct links yet).
http s://pasteboard.co/HeMKbPp.jpg

I have the same issu like u!

I have installed amazon appstore. I have given permission to allow amazon appstore to install from unknown source. But still when I try to install app from amazon appstore it shows that allow to install from unknown source in security settings and open security settings menu. I have allowed all permissions to amazon appstore but still not able to download or install single app.
Any solution please.!!

BillGoss said:
I just now installed the Amazon app store APK. Then I opened the application, logged in, and downloaded an app.
I was then prompted to change my settings to allow the downloaded app to be installed.
At this point I checked in Settings>Apps>Special access>Install unknown apps and the Amazon app is listed.
I'm in OOS 5.0.1.
So everything behaves as it should. Nothing wrong with the Amazon app or Oreo.
I suggest you wipe the data for the Amazon app and go through the process again.
Click to expand...
Click to collapse
I have Oxygen os 5.0.2 and i have even allowed unknown source installation to amazon appstore but still not able to download.

Sam_38 said:
I have Oxygen os 5.0.2 and i have even allowed unknown source installation to amazon appstore but still not able to download.
Click to expand...
Click to collapse
same thing for me since Oxygen Os 5.0.3

I'm running into the same thing rifmouk, running Oxygen OS 5.1.3 with redownloaded and installed Amazon Appstore as of today.

App update
Update: scratch everything below. Even when you enable the Appstore to install outside apps, it still prompts you to enable outside apps with a message inside the Appstore. Looks like Amazon still has work to do.
I was having issues with this too and wanted to give an update. It seems that Amazon has released an updated version of their app. You have to uninstall the Amazon Appstore app and then download the new version from the internet. If you don't uninstall first, it will just open the old store to try to download the new one.
Ironically, you'll have to enable chrome to install non-play store apps. This is done (as suggested earlier) by going to settings>apps>special access>install unknown apps. Once you've installed and signed into the new app, you will need to attempt to install a new app. It will again prompt you to go to the wrong (old) security section in the Android settings. Just navigate to the "special access" section from earlier and the new Amazon Appstore should be listed at the top.

I finally found the cause and also the solution of this issue.
In android Oreo, because of the new security management of "unknown apps", the value of the legacy setting INSTALL_NON_MARKET_APPS is now always 1.
See this page for more details: https://developer.android.com/about/versions/oreo/android-8.0-changes
This means that in Oreo there is an "old" string, only for legacy reasons (and bypassed by new security settings), that ALLOW unknown sources by default.
I found that some "security" apps (like avast, in my case), NOT well optimized for Oreo, detect this legacy string in Oreo as main setting for unknown sources: the result is an automatic procedure inside that "security" app, that disables unknown sources permission in that legacy string (wrong place, avast!).
The result is that, for some "strange" (bad) code inside Amazon Appstore, this app see only that legacy string and blocks any installation (even if you enable installations from this app in Oreo special permissions). Moreover, Appstore - as a result of this bad edited legacy string - point you to a wrong settings window (the "old" window, for nougat android and earlier).
The worst thing is that there is no window, no gui (graphical interface) to edit the above legacy string inside android Oreo settings, so you have to do it yourself using terminal (ADB).
SAID SHORTLY:
connect you device through ADB terminal.
write the following command
adb shell settings put global install_non_market_apps 1
(command to enable "old way" Unknown Sources).
Oreo needs to allow every single app as usual, you restored only one "invisible" (but necessary) Oreo legacy string as it is intended to be.
And don't use messy security apps anymore!
As an alternative of the above string, use:
adb shell settings put secure install_non_market_apps 1
THIS METHOD DOES NOT NEED ROOT, ONLY ADB DEBUG ENABLED!
Please, give thanks if this was useful, and share always with credits.
Thank you.

alessia3 said:
I finally found the cause and also the solution of this issue.
In android Oreo, because of the new security management of "unknown apps", the value of the legacy setting INSTALL_NON_MARKET_APPS is now always 1.
See this page for more details: https://developer.android.com/about/versions/oreo/android-8.0-changes
This means that in Oreo there is an "old" string, only for legacy reasons (and bypassed by new security settings), that ALLOW unknown sources by default.
I found that some "security" apps (like avast, in my case), NOT well optimized for Oreo, detect this legacy string in Oreo as main setting for unknown sources: the result is an automatic procedure inside that "security" app, that disables unknown sources permission in that legacy string (wrong place, avast!).
The result is that, for some "strange" (bad) code inside Amazon Appstore, this app see only that legacy string and blocks any installation (even if you enable installations from this app in Oreo special permissions). Moreover, Appstore - as a result of this bad edited legacy string - point you to a wrong settings window (the "old" window, for nougat android and earlier).
The worst thing is that there is no window, no gui (graphical interface) to edit the above legacy string inside android Oreo settings, so you have to do it yourself using terminal (ADB).
SAID SHORTLY:
connect you device through ADB terminal.
write the following command
adb shell settings put global install_non_market_apps 1
(command to enable "old way" Unknown Sources).
Oreo needs to allow every single app as usual, you restored only one "invisible" (but necessary) Oreo legacy string as it is intended to be.
And don't use messy security apps anymore!
As an alternative of the above string, use:
adb shell settings put secure install_non_market_apps 1
THIS METHOD DOES NOT NEED ROOT, ONLY ADB DEBUG ENABLED!
Please, give thanks if this was useful, and share always with credits.
Thank you.
Click to expand...
Click to collapse
Thank you, @alessia3. I've been trying to find a fix for this issue on my OnePlus 5T for six months. Once again able to download some apps I got on Amazon's app store before my Nexus 6p died.
I'll note that install_non_market_apps is under secure, not global, in my phone.

Question Okay, I'm stupid...

So, I was going through and removing bloat from my phone and was trying to remove the Samsung Contacts app through `adb`, but apparently I removed the wrong thing and now the Phone, Messages, and Contacts app are crashing every time I try to open them. I removed "package:/system/priv-app/SamsungContactsProvider/SamsungContactsProvider.apk=com.samsung.android.providers.contacts" which is apparently a core service. I'm wondering if anyone might know how I could reinstall that APK?

install this apk should solve the problem

If worse comes to worse a factory reset will.
A lot of the bloatware is useful. I prefer to use a package disabler as I can easily toggle them on or off as needed real time.

rtd4 said:
install this apk should solve the problem
Click to expand...
Click to collapse
It sat for a minute trying to install and then came up with, "App not installed" and says that every time I retry.

Trying install via adb I get: "
Performing Streamed Install
adb: failed to install /home/mhicks/Downloads/SamsungContactsProvider.apk: Failure [INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.samsung.android.providers.contacts attempting to redeclare permission android.permission.SEND_CALL_LOG_CHANGE already owned by com.android.providers.contacts]"
Hmmm, perhaps I should remove Google Contacts first...

Okay, that helped, but now I'm getting: "
Performing Streamed Install
adb: failed to install /home/mhicks/Downloads/SamsungContactsProvider.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE]"

I thought deleting the "com.samsung.android.providers.contacts" might solve the problem, but trying gave me: "
./adb -d uninstall com.samsung.android.providers.contacts
Failure [DELETE_FAILED_INTERNAL_ERROR]"

darkfrog26 said:
It sat for a minute trying to install and then came up with, "App not installed" and says that every time I retry.
Click to expand...
Click to collapse
try these commands on pc
adb shell cmd package install-existing com.samsung.android.providers.contacts
adb shell pm install -r --user 0 /system/priv-app/SamsungContactsProvider/SamsungContactsProvider.apk

The first command returns: "Package com.samsung.android.providers.contacts installed for user: 0", but the second command returns: "Failure [-3001: INSTALL_FAILED_REJECTED_BY_BUILDTYPE]"

If you have deleted the apk with root you just have to paste it again in the folder /system/priv-app/SamsungContactsProvider

@rtd4, unfortunately, this device isn't rooted.

darkfrog26 said:
@rtd4, unfortunately, this device isn't rooted.
Click to expand...
Click to collapse
It is somewhat complicated to recover the device without wipe in the past I had these problems, it was solved with a higher version of the application

@rtd4, I suppose it's time for a wipe... Thanks for trying to help me.

If you had made a copy of all your apps including system apks with ApkExport you could now use that copy to restore it.
Now before you factory reset make a copy of your installed apps and any system updates then save it on the PC or SD card. After the reload you won't need Playstore. It speeds things up a lot...
APK Export (Backup & Share) - Apps on Google Play
Manage and extract your apps.
play.google.com

@blackhawk, thanks for the tip. Right now, I'm trying to set up a Telegram account so I can root my phone (US version) if I'm going to go through the trouble of wiping. Unfortunately, Telegram's SMS verification appears to be broken or at least doesn't like Mint Mobile... Fun day.

darkfrog26 said:
@blackhawk, thanks for the tip. Right now, I'm trying to set up a Telegram account so I can root my phone (US version) if I'm going to go through the trouble of wiping. Unfortunately, Telegram's SMS verification appears to be broken or at least doesn't like Mint Mobile... Fun day.
Click to expand...
Click to collapse
You're welcome.
You really don't need to root.
Consider the possible consequences carefully.
Package Disabler will easily block apks you don't want running.

Well, it would appear it's moot anyway since I'm at Baseband v4 and only v1 can be rooted apparently...

darkfrog26 said:
Well, it would appear it's moot anyway since I'm at Baseband v4 and only v1 can be rooted apparently...
Click to expand...
Click to collapse
This is the one I use:
Home - Package Disabler
The only NON-root solution that let’s you disable any unwanted packages that come pre-installed / installed with your phone / tablet.
www.packagedisabler.com
It has an interactive widget that allows you to toggle selected entries on/off. It runs even in Safe mode so be careful what you disable. I've never had to do a factory reset because of it but the potential is there.
Unfortunately it no longer disables Google play Services but will disable all carrier bloatware including OTA updates.

darkfrog26 said:
@rtd4, unfortunately, this device isn't rooted.
Click to expand...
Click to collapse
Then how come you have removed apk from system?
In case you have used command like
pm disable packageName . Then try pm enable packageName
Or
If you have used
pm hide packageName then try
pm unhide packageName

darkfrog26 said:
So, I was going through and removing bloat from my phone and was trying to remove the Samsung Contacts app through `adb`, but apparently I removed the wrong thing and now the Phone, Messages, and Contacts app are crashing every time I try to open them. I removed "package:/system/priv-app/SamsungContactsProvider/SamsungContactsProvider.apk=com.samsung.android.providers.contacts" which is apparently a core service. I'm wondering if anyone might know how I could reinstall that APK?
Click to expand...
Click to collapse
Next time use this, so you don't make mistakes:
[TOOL] ADB AppControl 1.8.0 🚀 Ultimate App Manager & Debloat Tool + Tweaks
ADB AppControl 🚀 Root is not required. Works with any Android device. Can do almost everything you dreamed about with applications. ADB AppControl - the desktop program, that will allow you to easily manage applications on your android device...
forum.xda-developers.com