I have a Sony Xperia Z2 Tablet (SGP561; Build: 17.1.D.0.417) which appears to be rooted. (Settings > About Tablet > Status > Rooting Status: Rooted) however neither SuperSU or Super User appears to work. (and without Super User privileges the Root Checker apps always say I don't have root access even when I otherwise would) No matter what I try, it always says a variation of "There is no SU binary installed." (SuperSU) or "The Superuser binary (su) must be updated." (Superuser, and no logs created when it fails)
Is there any method of installing those binaries? Maybe through a USB cable and USB Debugging?
Elliander said:
I have a Sony Xperia Z2 Tablet (SGP561; Build: 17.1.D.0.417) which appears to be rooted. (Settings > About Tablet > Status > Rooting Status: Rooted) however neither SuperSU or Super User appears to work. (and without Super User privileges the Root Checker apps always say I don't have root access even when I otherwise would) No matter what I try, it always says a variation of "There is no SU binary installed." (SuperSU) or "The Superuser binary (su) must be updated." (Superuser, and no logs created when it fails)
Is there any method of installing those binaries? Maybe through a USB cable and USB Debugging?
Click to expand...
Click to collapse
You can try to download supersu from here http://www.appsapk.com/supersu/ and install if via adb.
Of you could also root it using easy root tool: http://forum.xda-developers.com/showthread.php?t=2784900
I rooted my device using the second method and everything went fine.
Let us know what happen
Syol said:
You can try to download supersu from here http://www.appsapk.com/supersu/ and install if via adb.
Of you could also root it using easy root tool: http://forum.xda-developers.com/showthread.php?t=2784900
I rooted my device using the second method and everything went fine.
Let us know what happen
Click to expand...
Click to collapse
As I mentioned in another thread, Easy Root ended up being the solution. It gave me errors like it failed, but after rebooting the device everything started to work fine and I was able to successfully install SuperSU without error.
Related
i'm quite confused. I believe my phone is partially rooted. I installed SuperSu but it says that i do not have the Su Binary installed. under root checker it says that supersu is not installed but busybox is. I successfully installed Root Explorer and am able to view system files but not edit them.
anyways, i got a verification error when trying to flash CWM-supersu in recovery. I followed al the steps and downloaded all the required recovery.img files etc. I am tempted to flash a custom rom. but afraid if it gets locked up during the process, as there is no back up option with the stock recovery.
Any suggestions?
swift2fly said:
i'm quite confused. I believe my phone is partially rooted. I installed SuperSu but it says that i do not have the Su Binary installed. under root checker it says that supersu is not installed but busybox is. I successfully installed Root Explorer and am able to view system files but not edit them.
anyways, i got a verification error when trying to flash CWM-supersu in recovery. I followed al the steps and downloaded all the required recovery.img files etc. I am tempted to flash a custom rom. but afraid if it gets locked up during the process, as there is no back up option with the stock recovery.
Any suggestions?
Click to expand...
Click to collapse
Update the binaries in superSU settings or reinstall root with CF-Root with Odin, see item 1 in my signature.
gee2012 said:
Update the binaries in superSU settings.
Click to expand...
Click to collapse
will not allow it. "It says that SuperSu can not install it. There is a problem"
I'm on Android version 4.0.4 firmware BULF1
swift2fly said:
will not allow it. "It says that SuperSu can not install it. There is a problem"
Click to expand...
Click to collapse
Yes, flash CF-Root with Odin.
Update your busybox to latest version.then update the su..it will work
Then cwm problem can be solved by using a manual cwm(new cwm from someone)...
gee2012 said:
Yes, flash CF-Root with Odin.
Click to expand...
Click to collapse
ok i will look into that. i gotta find a PC. I've successfully rooted 2 S3s with the method i use on mac but for some reason it's not working on this current phone i'm trying to root.
I have the LG Power (aka LG Leon) from Tracfone, which has a protected bootloader. KingRoot roots it, but its su binary is not fully compatible with all root apps. Fooling around with KingRoot, I found a way to ultimately root the phone with SuperSU, using KingRoot as a "mule" app to do it.
Warning: As always, you can make your device unusable by attempting to root it. You follow these instructions at your own risk.
Download KingRoot from kingroot.net, install it, and let it do its thing. You may have to try a couple or three times before it gains root.
Install SuperSU from Google Play. Open it and "Cancel" the prompt to update the su binary (it won't work, yet). Configure SuperSU to your preferences, and grant it root permission when KingUser asks.
Install a root browser such as ES File Explorer from Google Play, open it, and enable root access. KingUser should prompt to allow it root.
You will need a copy of the SuperSU su binary. It is not yet in the /system/xbin folder, as KingRoot has control over that. You can get it through ChainFire's site, or from the "root.zip" file attached to this thread: http://forum.xda-developers.com/fir...ne-supersu-t3105546/post60669196#post60669196
Load the mule with the payload. Browse to /data/data/com.kingroot.kinguser using the root browser and REPLACE all instances of "su" with the SuperSU version of the su binary. You will find at least two deeply embedded in the directory tree.
Now wait, possibly for several minutes. KingRoot will eventually check its integrity and find that the installed su binary is different than the one it its data directory. It will reinstall automatically and test its access. If successful, you will see a SuperSU prompt to grant KingRoot superuser access! :victory: Deny it.
Now open SuperSU again and allow it to upgrade the su binary through the "Normal" method. It should succeed.
Restart the device.
Open SuperSU again to test root access. Open a few root apps such as the root explorer. SuperSU should prompt to grant root access.
You can uninstall KingRoot (and Purify, if you want).
Some issues that I ran into that may or may not be of concern to you:
After rooting, my device became unstable and would freeze a few minutes after restarting. I had to take out the battery to restart it. I was messing around a lot with it, so most likely it's something else I did. However, if this happens to you, go into "Safe Mode" by powering it on, waiting for the LG Logo to appear, then holding the "volume down" button until you see the default launcher screen with "Safe Mode" in the lower left corner. Give it many minutes to settle in, then restart normally. This restores a few things to default (such as your widgets, which you will have to re-configure).
SuperSU asked me a second time to update the su binary. I allowed it, and it never asked me again.
If all else fails and you can't get a stable root, install KingRoot again and have it re-root the phone.
FlashFire works on this phone after rooting as above. I was able to successfully flash Xposed to the device.
Don't try to flash TWRP, however. The bootloader is locked and you will lose recovery if you do this. (Yes, I did it.)
this not work on H340n with android 6.0
gsearle5 said:
FlashFire works on this phone after rooting as above. I was able to successfully flash Xposed to the device.
Don't try to flash TWRP, however. The bootloader is locked and you will lose recovery if you do this. (Yes, I did it.)
Click to expand...
Click to collapse
Hey, quick question because I'm still not getting the framework to successfully flash. Which version of the framework did you use specifically?
Corbow6 said:
Hey, quick question because I'm still not getting the framework to successfully flash. Which version of the framework did you use specifically?
Click to expand...
Click to collapse
I flashed version 81. It's working great, so I haven't attempted to upgrade yet.
gsearle5 said:
FlashFire works on this phone after rooting as above. I was able to successfully flash Xposed to the device.
Don't try to flash TWRP, however. The bootloader is locked and you will lose recovery if you do this. (Yes, I did it.)
Click to expand...
Click to collapse
I had the same issue... So after lots of searching I found a stock 5.0.1 recovery for a LG G3 that works. The zip file is NOT flashable but just unzip the recovery.img and flash that with FlashFire. You can then turn off the phone, press & hold vol- & power till the phone vibrates the continue to hold vol- and release then press and hold power again to enter stock recovery.
voluptuary said:
I had the same issue... So after lots of searching I found a stock 5.0.1 recovery for a LG G3 that works. The zip file is NOT flashable but just unzip the recovery.img and flash that with FlashFire. You can then turn off the phone, press & hold vol- & power till the phone vibrates the continue to hold vol- and release then press and hold power again to enter stock recovery.
Click to expand...
Click to collapse
Thank you! I'll try it out. What do I have to lose, recovery?
gsearle5 said:
I flashed version 81. It's working great, so I haven't attempted to upgrade yet.
Click to expand...
Click to collapse
I just updated to version 86 without a hitch.
Looks like I celebrated too soon, while you can enter recovery with the IMG I posted above it won't actually do anything... except make you have to pull the battery out. Least you don't get an error in the top left corner anymore so there's that.
Just installed the new Xposed Framework self-installer for Lollipop on this device (LG Power). It worked flawlessly.
http://forum.xda-developers.com/showthread.php?t=3034811
I had recently upgrade my s3 using TWRP recovery from 4.4 to 7.1 lineage os
But I am facing problem with rooting.
I am not able to root my device from
1)TWRP recovery
2)Odin(CF Auto Root)
3)Kingroot(Android and PC )
I have installed TWRP properly
PLz give an idea to root my device
I have checked in developer option
That is ROOT ACCESS
Their is 2 Option only
1)Disable
2)Adb only
But I am not able to get root access any of this Or Adb only
Previously I tried with different ROM
Their is option of
1)disabled
2)Apps only
3)Adb only.
4)apps and Adb
But in this ROM I am not able to find suggest me any way to fix this
I installd 4 time s same ROM to get this root access but failed
Check below screenshot
In SuperSU application
No su binary installed
https://dropfile.to/bRO4jKc
https://dropfile.to/MMWxWrp
As far as I'm aware the rom should be pre rooted and all you'll need to do is install supersu from googleplay and then update the su binaries from within the supersu app.
Set it to option 4 (apps and abd) and go about installing supersu first as the app from googleplay and if no joy then as a flashable zip file.
Beamed in by telepathy.
amitrider04 said:
I had recently upgrade my s3 using TWRP recovery from 4.4 to 7.1 lineage os
But I am facing problem with rooting.
I am not able to root my device from
1)TWRP recovery
2)Odin(CF Auto Root)
3)Kingroot(Android and PC )
I have installed TWRP properly
PLz give an idea to root my device
I have checked in developer option
That is ROOT ACCESS
Their is 2 Option only
1)Disable
2)Adb only
But I am not able to get root access any of this Or Adb only
Previously I tried with different ROM
Their is option of
1)disabled
2)Apps only
3)Adb only.
4)apps and Adb
But in this ROM I am not able to find suggest me any way to fix this
I installd 4 time s same ROM to get this root access but failed
Check below screenshot
In SuperSU application
No su binary installed
https://dropfile.to/bRO4jKc
https://dropfile.to/MMWxWrp
Click to expand...
Click to collapse
Did you try to flash the addonsu.zip from LineageOS website?
You must flash it to get root access in LineageOS 14.1
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Flash a stock firmware and start over.
Beamed in by telepathy.
amitrider04 said:
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Click to expand...
Click to collapse
Are you sure you flashed the correct addonsu???
As far as i remember, the s3 doesn't have 64x, flash the normal arm version (arm32x).
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
amitrider04 said:
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
Click to expand...
Click to collapse
flash supersu.zip 2.79 with twrp it worked for me
Thanks it also worked for me:laugh:
Thank you!!!
That worked for me.
Now i would like to know why this works and not the file from Lineage itself....
Zwolly said:
Thank you!!!
That worked for me.
Now i would like to know why this works and not the file from Lineage itself....
Click to expand...
Click to collapse
It works, you will get an error in recovery, but when you boot, you will get root access normally, i don't why the error happens, but it's harmless anyway.
Root fix
I'm not sure if you have fixed it yet but just in case if this helps the way I got around this is by simply downloading the latest super su zip from the official site and manually flashing via twrp kinda sucks but it works the first boot took a little though so if you try this and it takes forever for your device to not just wait because it can take up to 15 min the first time. So basically as long as you have twrp you are rooted technically it's just based on the rom wether they chose to support it if not the zip always works but you need the app too.
amitrider04 said:
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Click to expand...
Click to collapse
amitrider04 said:
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
Click to expand...
Click to collapse
S3 has arm32. So neither x86 not x64 would work. You should've flashed addonsu.zip for 32.
Sent from my Pixel XL using Tapatalk
I never post for help, but I am at my wits end.
I have a Vodafone tablet that's running 6.0 marshmallow that refuses to root. I did find a TWRP recovery compiled for the device, which I installed using SP Flash Tool.
TWRP seems to work as expected. I can make and restore backups, format partitions, mount system, delete files with the file manager and so on.
TWRP is also kept on every reboot. It never replaced by the stock recovery.
However, when I try and install the SuperSU zip 2.82 to root the device, it seems to be successful. However, when I boot into Android and open the SuperSU app, it says,"SU binary occupied" and closes.
That error is displayed when installing 2.82. When installing versions like 2.79, it shows the option to install the SU binary, again like normal, but it always fails to install the binary.
Using a root checker app from FDroid tells me the same thing, that root isn't avaliable. TWRP flashing should be working though, since I can flash busybox and it is detected correctly by the same root checker app.
Other root apps refuse to work.
Whilst in TWRP, I am able to browse the file system and the su file is located in system/xbin, again like it should be. Numerous other files from busybox are also located there, further signalling a successful flash. I can chmod 755 the su file without issue, but it doesn't fix anything.
The bootloader of the tablet is unknown to me. I can't boot into fastboot or bootloader mode. Trying to do so just reboots the tablet. Nothing is shown on the screen either, and it boots to Android again. I did enable ,"OEM Unlocking" in developer options.
Any ideas what I can do? I really want to give this device a thorough chance, since it is a surprisingly enjoyable device to use, and for the price I paid it's almost a total no-brainer.
I just want root so it can become a total no-brainer to own.
Thank you for your time.
I figured it out.
I tried installing Magisk by patching the boot.img within the app and flashing it via SP Flash Tool, and it worked perfectly.
I never thought of using that, but I am glad that I did.
So, yeah. Use Magisk.
Ive veen trying to root my sm-t380 to the point of even creating my own modded boot.img with security set to 0. When i felt like everything had been done correctly, magisk flashed successfully, and there were no bootloops, I go to magisk manager and see that only the ramdisk was modified. Sar and a/b were both no and the root status showed up as na. No app could detect the root.
What went wrong?
P.S SuperSU systemless dident work either
P.P.S SuperSU system puts me in a bootloop that lasts for around 15 minutes per bootloop
Bump
/\
The most simple method to detect Android is rooted:
Code:
adb devices
adb shell
You should now see either a ‘$’ or a ‘#’. The # means Android is rooted.
jwoegerbauer said:
The most simple method to detect Android is rooted:
Code:
adb devices
adb shell
You should now see either a ‘$’ or a ‘#’. The # means Android is rooted.
Click to expand...
Click to collapse
i know how to check, my problem is my device is **** and cant be rooted. Ive heard multiple places that say the sm-t380 is a sort of "touchy" device. It dosent like rooting AT ALL
Any updates with this? I'm trying to root with the latest OS this tablet has but is not picking magisk like it patch the BOOT.img perfectly but when I flash it with odin is not detecting anything.
I went through many guides for T380 and I get to the same point as OP and Barto604. TWRP installed success, Magisk-patched boot.img flashed success, system launches successfully, Magisk app shows "Installed N/A, Ramdisk Yes, A/B No, SAR No"
I tried running adb devices; adb shell and it shows $ so not rooted
flya258 said:
I went through many guides for T380 and I get to the same point as OP and Barto604. TWRP installed success, Magisk-patched boot.img flashed success, system launches successfully, Magisk app shows "Installed N/A, Ramdisk Yes, A/B No, SAR No"
I tried running adb devices; adb shell and it shows $ so not rooted
Click to expand...
Click to collapse
Hi I am reading through the xda treads have the same thing after patching the boot except my device in root checker says successfully rooted. What I did was switch from supersu to magisk( switch superuser app). I noticed the superuser binaries have to be installed or it will not work.
In my situation I just went inside supersu app and selected switch superuser app, then supersu uninstalls itself then reboot phone and open magisk app. root checker says successfully rooted.
I don't know if I am doing it right but my phone still says successfully rooted??