Database Users

Nexus 7 has root, but

When apps that ask for root permissions are launched, it doesnt work, example: TI backup says that the device isnt rooted and i might have to check the SU binaries. My N7 was rooted before a update for Superuser was available, now something happen after i updated it. But i dont know what...

That's weird. After you updated your SU, did you go to SU to update its binaries?

i did that twice, and it did say to update binaries...so...

you might need SuperSu instead
What Android version are you running?
Droid_Boi86 said:
i did that twice, and it did say to update binaries...so...
Click to expand...
Click to collapse

I had similar problems with "lightly rooted" stock (4.2.1/JOP40D) using a slightly older version of Superuser. Some apps could get root and others could not. But things have been in flux recently; read on...
I poked around a little bit and it appeared that the 4.2 multi-user stuff was interfering with the way that older versions of (ChainsDD's) Superuser worked, and at that time (only a couple weeks ago) ChainsDD had not released a newer update - things were still in flux.
I switched over to SuperSU, and no problems since... but....
...for me, installation of SuperSU didn't go swimmingly. As I recall the SuperSU install instructions say something like "you need to already have root to install the SuperSU `su' binary". Makes sense as it needs to write it's 'su' binary into /system, which in turn means it needs to get root privilege from a pre-existing su/Superuser installation.
So it poses a chicken-and-egg problem if you have lost root completely which I somehow managed to do... wait, I remember now! I had left the old 'su' binary in place, but had manually uninstalled "Superuser" from /system before I attempted the SuperSU install. Doh!
If you have lost root... you can manually install SuperSU offline inside the recovery via adb & the command line, which means getting both the SuperSU.apk and the 'su' binary ahead of time.
You can get the .apk from the market. You can attempt an install - it will download the 'su' binary and (no kidding) place a copy of it in /data/data/eu.chainfire.supersu/files/superuser.png
If you haven't lost root completely inside the booted OS, I suggest mounting /system in "rw" mode prior to running the SuperSU install and startup.
It looks like I am back a version or two - I have superSU v 0.99
4d7abc0eb5898cdb81bc233dcd16e052 /system/app/SuperSU.apk
0034ec008416b1c3fa7010deb8a3a758 /system/xbin/su
-rwsr-sr-x 1 root root 91992 Jan 10 16:40 /system/xbin/su
note the setuid,setgid bits on /system/xbin/su. Also - no symlink from /system/bin/su to xbin/su.
OK, sorry for the long post. There have been new releases from both chainfire (SuperSU) and chainsDD (Superuser) quite recently. Since I haven't had any troubles since 10 January, I haven't been following it closely - YMMV.
cheers

[Z3 All variant][Locked Bootloader][Noob Friendly] How to root

MOD EDIT @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
XPERIA ANDROID 5 LOLLIPOP EASY ROOT :​
ALL LOCKED&UNLOCKED BOOTLOADERS.
1-) Copy ALP folder in phone memory.
2-) Settings >Security > Unknown sources make it open. And Settings > Developer Options > USB debugging make it on. (If developer options exist go Settings > About phone and click Build number (7 times))
3-) Install Root.apk Allow all messages.
4-) Install Recovery.apk
5-) Install Busybox.apk
6-) Open KingRoot and click Root button.
MOD EDIT @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
6-) Wait to complete. İf you see a chinese blue button click it. All of messages you will allow.
7-) When you see blue tick symbol or %100 its ok.
Look to the menu KingUser its in here ok. No problem don't open it.
9-) Open busybox and install it. When you see It looks like busybox installed succesfully congratulations message its ok.
10-) Open XZRecovery and click Install Recovery .
11-) Phone will be reboot and recovery will open.
12-) Install > find ALP folder and select SuperSU.zip then swipe and install it.
13-) Complete the install Wipe Cache/Dalvik and reboot the phone.
14-) You can see SuperSU in menu and check with rootchecker your root access.
15-) Everything OK. You can enjoy with your rooted Android 5 lollipop device.
16-) You can uninstall KingRoot, busybox, Xzrecovery app. (won't delete supersu or ndrutils)
PREPARED BY ALPEREN ÇUBUK.
DOWNLOAD LİNK : https://yadi.sk/d/qMsejobDgedBw
MIRROR :
https://app.box.com/s/86e7vlwfmu5z62lo95vu2kfej38uj01q
NOTE: Extract downloaded zip and copy ALP folder your phone memory.

Thanks for the comprehensive guide. For some reason step 11) Getting my D6653 into recovery is not working (Also tried ADB reboot recovery)
Any ideas?
EDIT: After updating BusyBox, and then re-installing the Recovery, it re-started and is now stuck in a bootloop..
EDIT2: The bootloop is very likely related to this (from this post: http://forum.xda-developers.com/showthread.php?t=2261606):
"@vaisakh7 found a busybox updater which seems to be compatible with XZDualRecovery: Busybox On Rails, which installs a version of busybox created by stericson, which leads me to believe his Busybox installer should also install a version which works together with XZDualRecovery.
Either case, be careful with updating busybox as there still is a possibility it will break your ability to enter recovery or even break full root, which means you might not be able to recover from the broken situation. Your best bet is the installer version, using that to break the lock on the system partition and reinstall the correct busybox."
Recommended to NOT update BusyBox

Busybox can never be installed through this process always failed and there is no other option left once busybox installation failed except to reinstall the whole firmware please add the steps to guide for busybox installation too

Does this method null the waranty?
Sent from my Xperia Z3

Proper way to setup AdAway on stock rooted 6.0.1?

Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!

kwest12 said:
Hello, I'm on the latest 6.0.1 stock. I've used Nexus Root Toolkit to unlock my bootloader, root (SuperSU), and flash TWRP. I flashed Xposed using the Xposed installer. Now I'm looking to get AdAway up and running. I've done some searching and I see some conflicting reports about whether this needs to be done systemless, and how to get it working. Stuff I've heard is:
1. Just install the apk from XDA and install normally, update hosts, and you're good.
2. Install apk, use a program (like Titanium Backup) to make it a system app, update hosts, done.
3. Install apk, flash some sort of AdAway package in TWRP, update hosts, done.
4. Install apk, do some adb process to create a symlink of some sort, update hosts, done.
5. I haven't heard anyone really mention it, but in Preferences I see an option to "Enable systemless mode" which I haven't seen anyone really mention.
Can someone tell me which way I need to use, please?
>>> I also saw someone say that I need to use a file explorer after updating hosts to manually switch the permissions of the hosts file, in order to improve performance. Can anyone tell me if this is accurate, and if so how to do it?
Thanks!
Click to expand...
Click to collapse
Hello... Just allow SU permission, tic "enable systemless mode" in preferences if you use systemless Root. Tap on "disable" next to the red cross and let it download the new host. When prompted, reboot. Done...
Never seen anything about setting extra permissions... I don't read the XDA thread anyway and downloaded the app from here: https://f-droid.org/repository/browse/?fdid=org.adaway
Cheers...

Accidentally uninstalled SuperSU

Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu

Cacciu said:
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Click to expand...
Click to collapse
It's been awhile since I used SuperSU so I might be fuzzy: SuperSU has two components, 1) the .zip portion installed from TWRP and 2) the APK. The zip is like "the framework/service/su" part and the APK is the app that just tracks and loads the DB with which apps or services have been granted SU access.
My question is "Which of these did you uninstall?" : OR: Did you uninstall both? Maybe only uninstalling one or the other causes an 'out of sync' condition.
Anyway: This version of SuperSU https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 discussed in that thread has the APK in the .zip file. By definition all TWRP recoveries are rooted and can do what they want to like installing SuperSU.
What happens after you boot seems more likely to be about left-over crud from the APK / DB component, (and I'm guessing here), so if the SuperSU APK is still there, I'd clear it's data entirely, perhaps get rid of it entirely if you can and reinstall the .zip that contains all parts of SuperSU (maybe they all do now) from that link ^^. Make sure that link I gave is the one you want (systemless, etc).
TWRP should've done the heavy lifting during SuperSU install since it's already rooted. If it didn't, then keep the log from TWRP and look over it's install steps during the SuperSU install. Post it here maybe.

Thanks for the answer.
I uninstalled the apk.
I already tried to install the apk directly and also installing it from the zip, and there was either a message like "no root detected" or " root is corrupted".
I also deleted the su folder, uninstalled the apk and reinstalled the zip. But it was always the same: the apk did either say it's not rooted or did not install/show in the apps.
Probably i have to unroot and root it, or do you have any other idea?

TWRP Terminal
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal

Cacciu said:
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Click to expand...
Click to collapse
You might be out of luck if you deleted the su directory or any other related to binary su code. I'm not sure why you couldn't do a reinstall of the original SuperSU .zip file. You've got that whole 'catch-22' thing going right now.
The only thing I'm wondering about is whether a certain amount of cleanup has to take place before you can just roll SuperSU*.zip over an old mangled version and get it to work. Do you get errors in TWRP when trying to reinstall the entire package?
---------- Post added at 02:48 PM ---------- Previous post was at 02:05 PM ----------
I downloaded this version of SuperSU (which may or may not be what you used, but you of course want the one you used): http://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
Then I unzipped it and the installer script for not only the binary parts but the apk is here .\SR1-SuperSU-v2.82-SR1-20170608224931\META-INF\com\google\android\updater-binary. (updater-script is a dummy). It's kind of old school and is very easy to understand (the shell script that installs it).
All the files that it pushes onto the SD are easy to find and use, although you have to keep SELinux settings in mind.
It's worth taking a look at if you want to try to rebuild the wrecked version or if you want to just reapply the zip and have a better understanding of any errors it spits out.
Good luck.

Magisk 22101 (22.+) not detected by Manager, but SU still working on Android 6.0 Marshmallow with Samsung Note 4 SM-N910F TouchWiz,

- Target image: /dev/block/
- Device platform: armeabi-v7a
- Installing: 22.0 (22000)
! Unable to check signature
! Installation failed
this is the message inside of magisk manager when i try to install with recommended way. but i have root after flashing zip not showing anything else in the app not magisk hide not modules etc
ant solution?

I do not quite understand what you want, but I think I understand some of it. You want to install a new version of magic and can not do it from the magic app, it was properly understood. If it was I can help. Try using another file explorer if you need to patch for it, or download the zip file and install it from recovery.

i have tried all when flashing the latest magisk the manager doesnt recognize the version but i have root rights nor appears su hide modules etc in the manager

Im running a 6.0 Custom ROM and noticed Magisk isnt working well but does give me SU access. I you need to run an earler version of Magisk (16?) in order to run it smoothly.