Samsung Galaxy S7 on latest April Patch. Giving access to Greenify through this "https://greenify.uservoice.com/knowledgebase/articles/749142-how-to-grant-permissions-required-by-some-features" method is not working. I tried using different version of it starting from v2.9 to 3.3. The older ones give me a notification that I do not have root privileges, but the latest version don't.
Is this method still viable or just not working for me?
Also if this method is something that is endorsed by the developer shouldn't it be good to put a force check on it?
PS: Was working before updating to 3.2.2, by which I mean it didn't use to give me the "No root" notification.
PPS: Used to different machines with both CMD PowerShell to grant the adb access.
Related
I've searched, but not found, anyone else doing this yet, so I thought I'd post in case it helps. Hopefully this isn't old or well known news tho
I am successfully side-loading on my NT with the 1.4.1 update, using 'adb install ...' - without rooting.
First a little background:
I did have my NT 1.4.0 previously rooted, and Market installed.
I didn't block Over-The-Air updates but didn't get any until just yesterday.
I also had SwipePad installed BEFORE the update and a SwipePad add-on called AppLauncher (all I needed for launching/task switching)
It appears that B&N uninstalled ADW and Go Launchers off my device?!
Wow, that's privacy infringement, I would think!
I'm quite sure they were on my device before the update and aren't to be found now?! Other things in /system/bin went missing also - su, BusyBox, custom scripts etc.
Here's How I managed to side-load:
With SwipePad and AppLauncher add-on (it shows all apps like an app drawer), using AppLaunchers menu for "App Settings" allowed me to go to dev and set USB debug mode and uncheck Auto Mount.
Then simply using "adb install <name here>.apk" with the apk file on my computer, I can install and run apps (including Go Launcher ).
SwipePad + AppLaucher give me all my previously and newly loaded apps.
What's Not Working:
Just gotta figure out how to get su to work again. I've loaded Superuser and gone into terminal but I have no su command anywhere I can find (did B&N remove it too?!).
Epilog:
So I can side-load and run apps, but no super-user (root) access.
Running the Nook&Zergy exploit doesn't work, as it fails on a remounting.
Here's what I'm getting when I try to root...
Code:
NookZergy$ adb push zergrush /data/local/zergy
1557 KB/s (23056 bytes in 0.014s)
NookZergy$ adb shell "chmod 755 /data/local/zergy;cd /data/local/;./zergy"
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
NookZergy$ adb remount
remount failed: Operation not permitted
I did side-load busybox, with a "success" status from adb - but I can't find it on the device after the install - weird?!
DeanGibson actually figured out a way to root 1.4.1 and install Android Market, but you must downgrade to 1.4.0 first.
Also, like you mentioned, adb install works just fine as long as you have an app installed that allows you to access the USB Debugging settings. Indirect actually released a script for sideloading via this way a while back. The Android Central Sideloading Wonder Machine works great as well.
Another thing, brianf21 figured out a way to allow sideloading via browser/email downloads and built the functionality into his Nook Tablet Hidden Settings App. Your 1.4.1 device must be rooted in order for the functionality to work.
darkquota said:
DeanGibson actually figured out a way to root 1.4.1 and install Android Market, but you must downgrade to 1.4.0 first.
Also, like you mentioned, adb install works just fine as long as you have an app installed that allows you to access the USB Debugging settings. Indirect actually released a script for sideloading via this way a while back. The Android Central Sideloading Wonder Machine works great as well.
Another thing, brianf21 figured out a way to allow sideloading via browser/email downloads and built the functionality into his Nook Tablet Hidden Settings App. Your 1.4.1 device must be rooted in order for the functionality to work.
Click to expand...
Click to collapse
Yeah, I did find and read all the posts you referenced. I don't really understand why Dean's method worked any different then what I already had tho, yet my tablet did not stay rooted after the upgrade - is that what he was suggesting happened? We still don't have a rooted 1.4.1, right?
kgingeri said:
Yeah, I did find and read all the posts you referenced. I don't really understand why Dean's method worked any different then what I already had tho, yet my tablet did not stay rooted after the upgrade - is that what he was suggesting happened? We still don't have a rooted 1.4.1, right?
Click to expand...
Click to collapse
Following his method, I ended with 1.4.1 being rooted. He somehow prepares the device to be able to be rooted on 1.4.1 before the 1.4.1 update is applied. I don't know the details, but he'd probably be willing to explain it to you.
back to 1.4.0
@darkquota - used the thanks button on ya
Well, did a funny thing using the hidden settings app... I went into accounts and deleted the "user" account - turns out this re-inits the entire /system folder as I lost everything - custom keyboard the works... Needless to say I'm reverting to 1.4.0.
BTW if anyone stumbles on this thread, there are better resources elsewhere AND it looks like things are getting very close to 'ROM build time' as there are reports of by-passed boot-loader!
...so many Thank-you's to click...
kgingeri said:
Here's How I managed to side-load:
With SwipePad and AppLauncher add-on (it shows all apps like an app drawer), using AppLaunchers menu for "App Settings" allowed me to go to dev and set USB debug mode and uncheck Auto Mount.
Then simply using "adb install <name here>.apk" with the apk file on my computer, I can install and run apps (including Go Launcher ).
Click to expand...
Click to collapse
Just to make sure I'm understanding correctly (I'm a bit technologically challenged), in order to install whatever app you're wanting to install .... Once you've checked and unchecked the boxes, do you have to have your Tablet connected to the PC in order to make the file transfer and install the app or can you send the apk file to yourself via web email account and download/install it from there?
TnTexasNT said:
Just to make sure I'm understanding correctly (I'm a bit technologically challenged), in order to install whatever app you're wanting to install .... Once you've checked and unchecked the boxes, do you have to have your Tablet connected to the PC in order to make the file transfer and install the app or can you send the apk file to yourself via web email account and download/install it from there?
Click to expand...
Click to collapse
Hi Tn, yes you have to load via the 'adb install ....' and the apk file FROM YOUR COMPUTER (tablet connected via USB of course). Email won't work as you get blocked by the security msg
FYI... I've since reverted my NT to 1.4.0 as I messed it up removing the main user account.
Still having debugging issues ...
Hello ...
I do not want to root my NT (1.4.1), I just want sideloading. Running Windows 7 on my laptop. Only USB 2.0 ports.
Yes, I have access to the settings menu, I installed AppMenu (TGPS) before 1.4.1.
I have been able to get USB Debugging ON and AutoMount OFF ... I know debugging is active because I am getting the little Android "bug" in the lower left corner ... and I still have control of the NT screen.
I have checked my installed USB menu with deview, and I do not see any other ADB devices present.
But no matter what I do, I cannot get SWM or the command prompt script to "see" my NT ... all I get is "Device Not Found".
What am I missing? The advice regarding drivers seems confusing if you are not trying to root the NT.
Thanks ...
np
notpaul said:
Hello ...
I do not want to root my NT (1.4.1), I just want sideloading. Running Windows 7 on my laptop. Only USB 2.0 ports.
...snip...
What am I missing? The advice regarding drivers seems confusing if you are not trying to root the NT.
Thanks ...
np
Click to expand...
Click to collapse
Not real sure Np - I am on a Mac, but it does sound like you have driver issues. I've read a lot of posts with Windows users complaining of such.
This from Indirect:
NOTE: Anyone who is having problems with drivers, http://forum.xda-developers.com/show....php?t=1363652 <-- That explains the two most common problems.
Click to expand...
Click to collapse
I'm sure the answer to this question is somewhere there, but I cannot find it. There is plenty of information on how to root your phone or tablet, but not on how the root works on Android.
When I work on my Linux box I usually use a "normal", limited user. Only when I need to install something, I switch to superuser, or root, using "su" or "sudo".What happens on a rooted Android? Do all apps run with root privileges all the time? Or rather some sort of "su" command is unlocked, and an app can access it when required. Can I give and revoke superuser powers to an app?
It is always safer to run all programs or apps with limited privileges, so when they misbehave, the risk to system integrity is minimal. If everything runs in root mode, it might just spectacularly crash one day.
In this context, how does adaway work? Does it start with the system, sitting in the background and using its root privileges to intercept and filter incoming HTTP packages? If I understand this correctly, it should then work with any browser?
Sorry for asking several questions in one topic, but I'd appreciate if someone could briefly explain the whole thing.
There is a superuser app, which seems to be doing the same job as gksu does on a linux desktop. Apps can request root, you can allow/deny. If you use the shell, su works as normal (just no password) - but connectbot needs to be given root privileges in order for this to succeed.
Have a strange one I don't know how to fix. Purchased a Pyle PTBL102BCD tablet for the Mrs. to use basically as an ebook reader (according to About, running 4.2.2). When it came in I started sideloading apps to prepare it for her (I do not have a Google account), and searched on the Net about rooting the device. Found a one-click that worked with a different Pyle tablet, so I gave it a shot.
Now I have root access _only_ through the adb shell. None of the apps (including Superuser.apk itself as tested by updating /system/bin/su) can get root access, yet I have no problem running root through an adb shell - remounted file systems, even performed an su which is the only instance Superuser.apk's log shows. Root access in the shell remains between reboots, so it's not a temporary root.
If the adb shell has root, I _should_ be able to use it to grant access to everything else, and I've followed a few different "manual" root instructions (having different permission settings for su and busybox), with no joy. So long as I connect with a USB cable and type on the Windows machine, I'm god. On the tablet itself...not so much.
I hope that someone with a more intimate knowledge of Android internals can point me in the right direction for achieving root completely. Currently have Titanium Backup and ConnectBot (long java errors when I attempt to su there) installed to test root, Superuser v3.1.3 and su v3.1.1. Permissions on su are -rwsr-sr-x. And the human is confused.
Did you get anywhere with this? I have the same problem. What one-click did you use?
mfurlend said:
Did you get anywhere with this? I have the same problem. What one-click did you use?
Click to expand...
Click to collapse
Side note; REALLY hate the new forum software. With all the untrusted Google and Amazon javascript (which my company firewalls), it's a pain for me to even log in let alone post replies. (And I wonder if I'm the only person in the world sick to death of all the unnecessary ajax garbage...)
Anywho, used Kingo, rooted and unrooted a few times, until I finally acquired complete root on the thing. Once I did, I could run Samba, and once that worked, I could more easily transfer files and apks to the tablet.
Still don't understand why it was left in such a...weird...state - having root by default in adb is just a scary thing!
thanks for the information. I tried doing that but I encountered various problems. Eventually, after trying to do it manually, I totally screwed up the device. Now it won't boot.. I still have access to adb. I need to flash this thing. Do you know what the stock ROM is?
mfurlend said:
Do you know what the stock ROM is?
Click to expand...
Click to collapse
No...I can give you the Kernel version info (3.0.36+ [email protected] #48) and build number (rk3168_k11_4.2.2_v20131230), but other than that no clue.
I used the towelroot method and it seems to have gotten my phone rooted. A basic root checker confirms it. I installed SuperSU and when I open it, the app says the binaries need to be updated, however it fails to do that when I click "normal". I also installed the Wireless Tether for Root Users app (play version and the v3.2 beta when that wasnt' working). I've tried various configurations to no avail. It pops up asking for root access from SuperSU which I grant. When I start the tethering it says there are errors and to check the log file, however when I click on "show log" it says "unable to find log-file. File does not exist". I've also tried Barnacle WiFi tethering and it doesn't work either.
Any advice is appreciated.
Algo2 said:
I used the towelroot method and it seems to have gotten my phone rooted. A basic root checker confirms it. I installed SuperSU and when I open it, the app says the binaries need to be updated, however it fails to do that when I click "normal". I also installed the Wireless Tether for Root Users app (play version and the v3.2 beta when that wasnt' working). I've tried various configurations to no avail. It pops up asking for root access from SuperSU which I grant. When I start the tethering it says there are errors and to check the log file, however when I click on "show log" it says "unable to find log-file. File does not exist". I've also tried Barnacle WiFi tethering and it doesn't work either.
Any advice is appreciated.
Click to expand...
Click to collapse
until you have updated your binaries, rooted apps will do this....
if you have safe strap installed and working, you can download the updated SU 1.99 zip and flash it thru safestrap....other methods are talked about I believe in the towel root threads but I haven't done that myself
Algo2 said:
I used the towelroot method and it seems to have gotten my phone rooted. A basic root checker confirms it. I installed SuperSU and when I open it, the app says the binaries need to be updated, however it fails to do that when I click "normal". I also installed the Wireless Tether for Root Users app (play version and the v3.2 beta when that wasnt' working). I've tried various configurations to no avail. It pops up asking for root access from SuperSU which I grant. When I start the tethering it says there are errors and to check the log file, however when I click on "show log" it says "unable to find log-file. File does not exist". I've also tried Barnacle WiFi tethering and it doesn't work either.
Any advice is appreciated.
Click to expand...
Click to collapse
The version of SuperSU on the playstore is outdated, you have to do the folowing:
5. Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip
6. Use ES File Explorer https://play.google.com/store/apps/details?id=com.estrongs.android.pop or other unzipers and unzip the file
7. Open the /common folder in the unzipped file, and copy the SuperUser.apk to the /system/app/ folder in the root of the phone, confirm any SuperUser Access requests at this point.
You can also use the safestrap method:
Note: SafeStrap doesn't work with encryption turned on (disabled by default). If you don't know if you don't have encryption on/your phone isn't a business phone (in which case you shouldn't be doing this!!!) then you most likely don't have encryption on!!
5. Use this app to change your SELinux mode to "Permissive" https://play.google.com/store/apps/details?id=com.mrbimc.selinux, this is required to use SafeStrap
6. Install SafeStrap 3.72 APK from this thread http://forum.xda-developers.com/showthread.php?t=2448925, NOT 3.71 FROM THE VERIZON THREAD!!! Then click install in the SafeStrap App
7. Flash http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip, this step is NOT OPTIONAL, without this file, your SU Binaries will not update!!! (This is important!)
Credits to @npjohnson
SuperSU in the Playstore has been updated top 2.0 and is the latest, greatest version now.
I don't know whereto put this thread although ths seems like a right forum,anyway, I have a problem with this persistent king root, and I want to remove it but these chinese 'communist' devs won't let me. I tried the following things:
1 Manually delete kinguser app from /system/app part, and then install supersu from play store. The result it just says what su binary is occupied.
2. Install BusyBox. Download this popular replace_kinguser_with_supersu_2.4.zip and 2.0 files (this ones with mrw folder) and run it. Supersu installs, asks for update and su binary update. Yes, yes, looks great, but doesn't work. When running any root app, like terminal emulator, nothing happens, no auth prompt pops up.
3. Reroot with older kingroot version (4.5), do the same as 2. Same result
4. Set auth mode in Supersu settings to allow/deny, when oddly it works. Allows or denies immediately, and I can find this in Supersu's log.
So, everything seems working fine except what Supersu doesn't want to show me my root promts when I need them.
If any information about my device needed, I will be happy to provide it. For starters, my device is ITELL K3300, I am not sure what else coud be needed if you want to help?