Database Develop

[Q] Superuser/SuperSU issues

Here is a problem I have and I am wondering if anyone else has experienced it and/or solved it:
Phone: Bell SGS i9000
FW: CM9 Nightly (currently May 30) all "stock" (no custom kernels etc)
I installed SuperSU some time ago as it seemed to have more utility than Superuser. I noticed after a flash that Superuser would take back "control" of the su binary and I'd have to manually re-assign it to SuperSU. I decided, after doing some research to see if it was OK, to freeze Superuser in Ti Backup. So far so good.
I noticed today though, that none of my scheduled backups in Ti Backup have taken place for a while, so I launched the app to see what gives. It was at that point I discovered that TB couldn't get su privileges from the system. I launched SuperSU and it attempted to update the su binary - and failed.
Since TB froze the Superuser apk, I can't uninstall it. I also cannot unfreeze it in TB because it cannot get su!
I'm a bit stuck.
I have ROM Toolbox, which appears to work OK, as well as ROM Manager, and both seem to be able to use su commands without issue (I told SuperSU to remember the granting of su permission when I first started using it) I don't have any other apps that regularly use su permissions (not that I know of) so everything else seems fine.
I'd like to fix the updating binary issue with SuperSU though, so I can once again grant TB su and then fix everything.
Anyone have any ideas? I've already tried re-flashing Superuser from recovery, still shows as frozen. I tried unfreezing from ROM Toolbox, but it fails.
I'm stuck and I'm at the limit of my understanding and experience with this. Anyone who can help will receive my eternal gratitude - and a pint if you're ever in my town!

Try to delete tb then reflash the rom without any wipe
Sent from my GT-I9100 using Tapatalk 2

Can't edit or write data on my phone after rooting.

I f'ed up guys, it seems that after rooting I dont have access to edit data on my phone, it can boot and all, but I cant for example take pictures(says it doesn have space wich is not true), intall apps, etc. I dont know in what extents it affected because I can uninstall apps for example.
When I try to delete a file with a file explorer it says the access was denied. Nor I can copy files from my pc to the phone.
I have a XT1063 with lollipop 5.0.2 that I installed manually before and worked great.
I installed Super SU through TWRP 2.8.5.0 (maybe wasnt compatible with lollipop?) that have Super SU 2.4 built in (according to what i’ve read, maybe this version of Super SU isnt compatible?).
Anyway, after that I proceeded to install busybox with default configuration and later smscript, dont know if all this is relevant. I only was aware of the problem when I tried to download a script for smcript but couldnt save it to my phone.
So next I tried to unroot from super su configuration with no luck, only got to unroot after uninstalling busybox. (also uninstalled smscript if that matters).
I hope I gave enough data if you need more just ask, thanks!

fede011 said:
I f'ed up guys, it seems that after rooting I dont have access to edit data on my phone, it can boot and all, but I cant for example take pictures(says it doesn have space wich is not true), intall apps, etc. I dont know in what extents it affected because I can uninstall apps for example.
When I try to delete a file with a file explorer it says the access was denied. Nor I can copy files from my pc to the phone.
I have a XT1063 with lollipop 5.0.2 that I installed manually before and worked great.
I installed Super SU through TWRP 2.8.5.0 (maybe wasnt compatible with lollipop?) that have Super SU 2.4 built in (according to what i’ve read, maybe this version of Super SU isnt compatible?).
Anyway, after that I proceeded to install busybox with default configuration and later smscript, dont know if all this is relevant. I only was aware of the problem when I tried to download a script for smcript but couldnt save it to my phone.
So next I tried to unroot from super su configuration with no luck, only got to unroot after uninstalling busybox. (also uninstalled smscript if that matters).
I hope I gave enough data if you need more just ask, thanks!
Click to expand...
Click to collapse
I got the same problem here! pls HELP!

I also had the same problem on my XT1068
Just reboot the device and format the internal storage using TWRP 2.8.6.0 (Latest). Problem will be solved

sharkymyn said:
I also had the same problem on my XT1068
Just reboot the device and format the internal storage using TWRP 2.8.6.0 (Latest). Problem will be solved
Click to expand...
Click to collapse
It means that I have to clean install everything again? I dindt want to go to this point, but thanks!

Uninstall system app

Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc. At first I thought it was Floating Fake Location issue but soon I realize I can't even uninstall other Sony bloatware such as Socialife, Xperia Lounge etc.
Please enlighten me why I can't uninstall system app even tho I am rooted.
P/S: it may have something to do with my root (partial? as I didn't unlock my bootloader), as I can't even mount r/w using root explorer or any other app that can mount r/w on /system.

Steven90 said:
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc. At first I thought it was Floating Fake Location issue but soon I realize I can't even uninstall other Sony bloatware such as Socialife, Xperia Lounge etc.
Please enlighten me why I can't uninstall system app even tho I am rooted.
P/S: it may have something to do with my root (partial? as I didn't unlock my bootloader), as I can't even mount r/w using root explorer or any other app that can mount r/w on /system.
Click to expand...
Click to collapse
You also need to instal Supersu, which is an interface for granting root. Then you will be able to delete system apps.

optimumpro said:
You also need to instal Supersu, which is an interface for granting root. Then you will be able to delete system apps.
Click to expand...
Click to collapse
I am using Kingo SuperUser to grant the apps root permission. Had some trouble replacing Kingo SuperUser with Chainfire SuperUser but I figured Kingo should've done the trick as well. When I mount Kingo did prompt me for permission and I allowed it, somehow I think the root is incomplete ?

Steven90 said:
Hi I just rooted my Z1 using KingoRoot APK app and I installed Lucky Patcher to install Floating Fake Location as "system app". The thing is, I cannot uninstall Floating Fake Location afterwards using tools like Root Uninstaller Pro,KingoSuperUser etc.
...
...
somehow I think the root is incomplete ?
Click to expand...
Click to collapse
Does your device have recovery installed? You can delete system apps through it: mount /system through XZ Dual Recovery's TWRP and delete the folder with the app's apk inside. You could also try flashing a SuperSU zip this way to fix root, but make sure you don't use the systemless version.
I suggest you next time don't use kingroot or any one-click root: though uncomplicated, they're notorious for being untrustful, leaking private IMEI information to unknown servers, and unreliable. Read THIS thread thoroughly, re-root using the method in the 2nd post, and upgrade to 5.1.1, or get a pre-rooted FTF through XperiFirm.

kentexcitebot said:
Does your device have recovery installed? You can delete system apps through it: mount /system through XZ Dual Recovery's TWRP and delete the folder with the app's apk inside. You could also try flashing a SuperSU zip this way to fix root, but make sure you don't use the systemless version.
I suggest you next time don't use kingroot or any one-click root: though uncomplicated, they're notorious for being untrustful, leaking private IMEI information to unknown servers, and unreliable. Read THIS thread thoroughly, re-root using the method in the 2nd post, and upgrade to 5.1.1, or get a pre-rooted FTF through XperiFirm.
Click to expand...
Click to collapse
No I haven't installed any custom recovery.
Cause I am already using 5.1.1 so I figured Kingo Root is the easiest way to go, didn't know it will cause so much trouble. So basically I need to unroot then root again using the "proper" method? I am already on 5.1.1 btw.

Steven90 said:
No I haven't installed any custom recovery.
Cause I am already using 5.1.1 so I figured Kingo Root is the easiest way to go, didn't know it will cause so much trouble. So basically I need to unroot then root again using the "proper" method? I am already on 5.1.1 btw.
Click to expand...
Click to collapse
The fact that you can't install Supersu and get root indicates that your phone is not fully rooted. I bet you wouldn't be able to install recovery either for the same reason...
Do the classic rooting, install TWRP and then flash any pre-rooted stock rom you want...

optimumpro said:
The fact that you can't install Supersu and get root indicates that your phone is not fully rooted. I bet you wouldn't be able to install recovery either for the same reason...
Do the classic rooting, install TWRP and then flash any pre-rooted stock rom you want...
Click to expand...
Click to collapse
I suspect I am not fully rooted as well. Can you point me a direction towards "classic" rooting my my Z1 5.1.1 ? Almost every post I went points me back to one-click-root solution.

I have the same problem, it's because we can't remount /system to rw ("operation not permitted"), so the update to SU isn't working as well, tried several different methods with terminal emulator but without any luck. Neither will total commander help in this situation. I'm begining to lose hope

Steven90 said:
I suspect I am not fully rooted as well. Can you point me a direction towards "classic" rooting my my Z1 5.1.1 ? Almost every post I went points me back to one-click-root solution.
Click to expand...
Click to collapse
Ulvgrim said:
I have the same problem, it's because we can't remount /system to rw ("operation not permitted"), so the update to SU isn't working as well, tried several different methods with terminal emulator but without any luck. Neither will total commander help in this situation. I'm begining to lose hope
Click to expand...
Click to collapse
Try this, it's almost a one-click tool
http://forum.xda-developers.com/showthread.php?t=2784900
Exploit maybe works with 5.1.1, but if not, downgrade your firmware to 5.0.2, use Easyroot to exploit, then upgrade back.
The "classic" root I was referring to requires downgrading from Sony's Lollipop/Kitkat FW to Jellybean due to Sony patching the exploits in the newer FW used for rooting. The steps are outdated now and is replaced by Easyroot. http://forum.xda-developers.com/showthread.php?t=2688933

The second Wind (Parallel SU)

Hello, new user here.
Since I stuggled with root on my Phone and somehow managed to maintain it, I thought, I 'd share you the stuff I did with you.
I put the TL;DR between hide, if you want to read the story behind my struggle anyway, you are welcome.
I am better with explaining stories then explaining things.
Spoiler
I am using a Samsung S4 mini, Stock ROM and just don't want to flash a cROM.
But I wanted more functions to do - a swiss knife like my old GT-S3650, which was able to boot a PC from.
Most of the things I want to use need root, so why not rooting this sleep S4 mini baby?
And I managed to root it using Kingroot. And all of the things I want to use worked.
After a few days, I noticed network traffic, even with the most network apps and Sync disabled.
Weird? Yes. So I installed "Shark" on my Phone and "Wireshark" on my PC, and started logging.
I noticed an increase of Jabber (the protocol) and a lot of request on domains from China.
Some requests even included my IMEI, how I am connected to the Internet, etc... pretty private Stuff.
I found most of the sources, the IMEI sending App was Shark itself.
Used Lucky Patcher to get rid of it and /etc/hosts blocked the DNS with Hosts Editor.
Did the same with some Kingroot DNS.
But then I asked myself: "Can Kingroot still root my phone, even when cut of the web?".
So I UNROOTED my Phone from Kingroot. Bad idea. Really bad one.
After I ran Kingroot again, it told me, it didn't have a network connection.
I have no idea how I was able to edit the hosts file without SU.
Rerooted the Phone, even if it left a bitter taste of having unwanted network traffic.
This is which made me want to switch to SuperSU.
I tried to mount system as RW prior and installing SuperSU over Kingroot SU. And it failed.
I even tried to make my own uninstall script to uninstall KR by unpacking the Kingroot APK and look what it does.
Not working, the script failed (I am not used to Linux), so I stayed at Kingroot.
While I was working on Kingroot, I was thinking about the idea of having 2 SU Apps, which everyone said it won't work.
But I wanted it to make work - and this is actually the focus on this topic.
During tests, it didn't work as intended, so I stopped working on it and forgot it overtime, resting within my /system.
Days passed, Weeks and Months and I lived with Kingroot, forgot all the trouble and access to/from China.
Recently, I started SuperSU - it was still on my phone. This "cannot install su binary" nagged me and thought:
Oh, why not use this instead.
And then there was SuperSuME... which I didn't want to use, since I was able to brick BlueStacks with it.
But I really wanted to get rid of Kingroot and use SuperSU. This was yesterday.
My phone still has warranty and I think I have Odin here (just in case), but not the 100% exact ROM file.
So I did SuperSuME anyway -I always could return the phone and claim it "broken after OTA update", lol.
Well, SuperSuME did it's Job better then expected and no bricks. Nice Job.
While playing around with SuperSU, I did another mistake.
And here we are... at the main topic.
TD;TR for those who didn't want to read the story:
I rooted my phone 2 times with Kingroot and finally wanted to switch to SuperSU.
After I accidentally broke Kingroot the first time, blocked it's Internet access and unrooted afterwards, I got stuck with a unrooted phone and Kingroot failed to root it.
I was lucky to fix that problem and rooted again with Kingroot.
After months, I used SuperSUME to change that. After SuperSU was installed, i made the mistake of unticking "Enable Superuser". Bad idea.
Tapping "Enable" again, it failed to update the su-binary. oh god. I unrooted again.
While traversing through my directories to start Kingroot again to root, I found my "shadow copy" of SU.
Wut? Shadow copy? Let me explain:
After my first unroot, I wanted to have a SU backup anyway at all costs, just in case I accidentally messup root again.
Now after hours I think I know why it doesn't work.. the normal way, of course.
I installed SuperSU, went into /data/data (or where ever SuperSU has its files) and took a look at them.
Unpacked the SuperSU APK on the PC and gathered all "needed" (I think were needed) files.
I hexedited the most SU binaries from SU to ZU and changed all other referenced binaries as well.
I am sorry about that, Chainfire. I was just testing things.
SU => ZU
SUpolicy => ZUpolicy
setup_su => setup_zu
99SuperSUDaemon => 99SuperZUDaemon
daemonsu => daemonzu
zygote => zugote
I had no idea what sukernel was for, so I left that out.
Why call it ZU? "Sun Tzu" thats why. Known as "Sunzi", he wrote Book about "the Art of War".
After I made sure everything is properly renamed and edited, I moved them onto my phone in the right directories required and chmod them.
I don't know much about that, I just copied the chmod numbers from Kingroot SU and some weird script I found on the web.
Tried to run it using JuiceSSH local terminal, and BAM!! the SuperSU box popped up.
But pressing "Allow" accepted it and nothing else happened.
It became stuck after ZU... it did nothing, but the daemon was running as daemonzu and daemonsu at the same time..
JuiceSSH popped up in SuperSU (while it told me the SU bin was outdated), though.
So I was on the right track, but a piece of the puzzle was missing, so I stopped delving deeper into it.
And forgot about it until about yesterday - where I disabled "Superuser" in SuperSU.
Midwhile the su binary changed from Kingroot SU to SuperSU SU.
Note: It should really ask "Do you want to disable Superuser? SuperSU will delete su binary" Yes/NO.
As I found those files, I started JuiceSSH and typed "zu".
This time, ZU somehow worked like it should.
It spawned a root shell. OMG...
I guess it somehow requires something else needed, which wasn't working while Kingroot was active.
I tried "Root Checker" and it failed. I had no "official" root. But still root available in JuiceSSH.
Somehow I managed to restore SuperSU to normal status. Guess this thing can latch onto an active root user or so.. no idea.
I even screenshotted this, cause I couldn't believe it. If you want, I can post those.
I have now a working second su on my phone, which is hidden from most apps.
But I think it is not perfect, it relies on something SuperSU does or installs during installation.
I apologize again to Chainfire for editing his stuff.
So, now my questions:
1. How can I make it perfect to run standalone, only using SuperSU as a GUI for (Allow/Deny)?
1b. Can we make it part of SuperSU? As a special function: "Install Stealth SU"?
2. Can we use that for something else? -> Probably for this? http://forum.xda-developers.com/apps/supersu/suhide-t3450396
3. Why must the binary be called SU? I know it's for the most apps to do their job and somehow Linux standard.

Rooting LN14????

Could someone please point me at instructions on how to root LN14.
I've searched the HD/HD+ forums for 'root LN14' and 'rooting LN14' and got no results (which by itself is suspicious).

have you enabled Developer Options?

I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!

harryzee said:
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
Click to expand...
Click to collapse
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.

digixmax said:
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
Click to expand...
Click to collapse
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.

harryzee said:
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
Click to expand...
Click to collapse
I meant "enable, disable,, then re-enable" the root access option in "Developer Options".

Aha! Will give it a go. Thanks.
5/2/2018:
Okay: I d/l three android root checkers and titanium backup. The first root checker (Clivin Inc. with small green android robot graphic) told me I was not rooted both before following your above instructions and after. The other two (d/l after following the above) both say I am rooted. However, I was not and am still not able to get "TB" to run. It says "failed" and that I am not rooted.
Since the HD+ is running really well now in its stripped down mode, I can "leave well enough alone" or try to get "TB" working so I can remove anything not needed for my chosen minimal functionality (ereader, viewing videos, photo review/minor editing) that would further reduce unnecessary battery drain.
Thanks again for the above clarification and any additional thoughts.

I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

You got it. Use Magisk. Works wonders and way better than SuperSU or any other root permission tool I've came across. It's even akin to, and even has within it, xposed and other magical rooted modules for you to try out for a day or two and then decide you don't need it.
pchc_lx said:
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse