Hi guys, this is my first thread on xda btw
you see my j320az (cricket)
Baseband version: J320AZTUS3AQG1
Android version: 6.0.1
device status: custom
Security enhancements for android: permissive
I tired rooting my device using an img.tar file that set selinux to permissive and tried to root with no success but now when I try apps to root my deivce like kingoroot,
it says that I'm already rooted, but when I used multiple root checkers from the play store, most of them say I do not have root
But then when I used a Super SU app from the playstore (Just search up "SuperSU" without quotes and it should come up as the top one that has a green icon with the hashtag sign) says that my su binary is occupied, but when I try to fix , it says I have to use a custom recovery to flash the latest version of an su binary update .img.tar file and it gives a file for the j7elte
link to that: bit.ly/2qz6lqb
unfortunately I don't know of any custom recoveries for my device, can anyone help me out? I would really appreciate
I can try and give more info as needed, feel free to contact me, just tell me some ways you can communicate with me
Related
Android Version:-2.3.5
Kernel Ver:-2.6.35.7-I9100XWKJ1-CL647431 [email protected] #2
Doesnt have SU or recovery so i dont think it is but the ROOT portion of the Kernel version is throwing me here.
Does anyone know?
TheBlueRaja said:
Android Version:-2.3.5
Kernel Ver:-2.6.35.7-I9100XWKJ1-CL647431 [email protected] #2
Doesnt have SU or recovery so i dont think it is but the ROOT portion of the Kernel version is throwing me here.
Does anyone know?
Click to expand...
Click to collapse
Install the SuperSU app or the SUperUser app from the Android Play Store/ else, install any app that requires root.
once you run the app the app will request for root permissions, if it works, then you have root. if not, you will need to root the phone.
the ROOT portion in the kernel is almost usually there.. even if the kernel is not rooted.
Thanks for the quick reply, it doesnt look like it is, SU complains and adaway doesnt install.
Samsung actually compile their kernels as root (!). The root part of the kernel name is just the username it was compiled under.
Sent from my GT-I9100 using XDA
maybe install voltagecontrol via playstore and look if u can change ur voltages and if the programs ask u to grant root rights, if not then its unrooted!
Just read the FAQS and GUIDES
Install CWM and root kernel.
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
The Reverend is right on the money (Sorry Rev, out of thanks. Will hit you up tomorrow).
That '[email protected]' thing is in every kernel under settings/about phone, and as the Rev said is simply the name of the user account/machine that the kernel was compiled on.
It has nothing whatsoever to do with root.
i am trying to root some cheap tablet. its based on arm9 wm8800 dual core ,running android 4.4. in developers options there is option to set super user permission (always ask,etc) but it doesnt do anything,when i ran root checker it shows its not rooted,and when i installed superuser from play store it says something about SU binary also apps that require root wont work etc.. so i tried several other options.. after running z4root there's no more su binary problem. root checker shows its not properly rooted,it shows that su binary is there in system/xbin/su but there's red text with some permissions .like i need to fix them,but dont know what to do.. i have rooted many devices,but this is hard.. any help??
I had rooted Celkon Q 500 with some method, I do not remember exactly. May be Root Genius. For some reason I unrooted using SuperSu. I wanted to re-root. But I am finding it difficult. ( I have not got any OTA update after rooting)One root checker says it is rooted, another says it is not. I can explore files in root explorer of ROM Tool Box Pro I had installed earlier. But I can not reboot through ROM Tool Box Pro. One root checker provided me this information : subinary available via $PATH null null, then in the next line it says : -rwsr -sr -x root root, subinary location is system/bin/su. Second thing it says : I have installed two busybox one at (a) data/local/busybox and another at /system/xbin/busybox. I had tried to un-install and re-install SuperSu and Busybox 2/3 times. Then after opening Supersu I got an erratic message : su binary needs updating and when Itried to update it , it failed several times. One root checker app says ADB root is available, Root Genius says root available. So, I am quite confused. I do not know how to go about it. I will be thankful, if somebody guides me in right direction.:crying: (I also found a root checker app said SELinux enforcing.)
After rooting we instal busybox and SuperSU (or Superuser) and avail the benefits of rooting. When we unroot through SuperSU, is it possible that 'su' still remains inside '/system' folder? I came across a strange phenomenon : I rooted my Celkon Q 500 ( by Root Genius or One-click method or something else, I do not remember) and installed many root apps. After somedays, I decided to unroot, I uninstalled super su, busybox. Then, I tried to root it again. But, I noticed that one root checker says ur device is rooted(specifically through Root Genius PC software I got the message rooted and pressed the 'unroot' button, but it said failed), 2nd root checker says it is non-rooted, 3rd one says it has root access through ADB. I checked 'su' is present in some folder inside '/system', which could not be deleted , because I think, I do not have RW privilege. I had tried many method to root it again, but all failed. When I open Supersu, it throws an immediate message that 'su binary' needs to be updated and when I try it fails everytime. Can anyone meke me understand, what is the real proble.? Celkon Q 500 is Broadcom chip based, running android 4.4.2. Also I found One message in the root checker that "SELinux enforced".
Eversmile23 said:
After rooting we instal busybox and SuperSU (or Superuser) and avail the benefits of rooting. When we unroot through SuperSU, is it possible that 'su' still remains inside '/system' folder? I came across a strange phenomenon : I rooted my Celkon Q 500 ( by Root Genius or One-click method or something else, I do not remember) and installed many root apps. After somedays, I decided to unroot, I uninstalled super su, busybox. Then, I tried to root it again. But, I noticed that one root checker says ur device is rooted(specifically through Root Genius PC software I got the message rooted and pressed the 'unroot' button, but it said failed), 2nd root checker says it is non-rooted, 3rd one says it has root access through ADB. I checked 'su' is present in some folder inside '/system', which could not be deleted , because I think, I do not have RW privilege. I had tried many method to root it again, but all failed. When I open Supersu, it throws an immediate message that 'su binary' needs to be updated and when I try it fails everytime. Can anyone meke me understand, what is the real proble.? Celkon Q 500 is Broadcom chip based, running android 4.4.2. Also I found One message in the root checker that "SELinux enforced".
Click to expand...
Click to collapse
reinstall super su from play store go to settings in super su app and unroot there
selinux enforced means that your kernel is not permissive. has nothing to do with root
Hi,
I need to root a Zebra TC56 to install some other apps that require rooted Android. There is very little information in the way of rooting the Zebra TC56. I 'm pretty set on using Chainfire's superSU, but I cannot find any information on whether it will work on this hardware. Does anyone know if the superSU works on this device with Android 6? If not, is there another Root Tool that will work.
Any advice appreciated.
THANK YOU!
VK
1. Install BusyBox applet-suite what contains the SU-binary
2. Install latest SuperSU APK
jwoegerbauer said:
1. Install BusyBox applet-suite what contains the SU-binary
2. Install latest SuperSU APK
Click to expand...
Click to collapse
BusyBox installed fine.
SuperSU will not install all the way. When I select to root, it says root not detected and then, "How to Root", which launches my browser to a site that no longer exists.
Now what?
Thank You!
edit: Still stuck at this point. I read about TWRP, KingoRoot and some other random apps. I cannot brick this touch computer; it is $1600; that would be a very expensive brick. :crying:
So, I have no idea if I am right, but maybe I need to open the terminal emulator and "su" install the SuperSU apk. But I have no idea and I don't want to experiment. Hopefully, someone can help me.
@vidarr_kerr
Don't confuse things:
SU is the super user who unrestrictedly can perform any operation on Android OS. As soon as SU got installed Android is rooted! Again: BusyBox you successfully installed contains the su applet.
SuperSU is merely a root-manager app: it maintains a database where is stored what app can act as super user. SuperSU app doesn't grant super user rights.
BTW:
TWRP has nothing to do with rooting device's Android, as this is also true with Magisk.
The device is still not rooted after the "BusyBox Installer (No Root)", from your link, was installed.
I installed BusyBox, I followed the directions to then copy a command, then open a terminal, paste the command in and hit enter, then nothing happened. SuperSU was not installed with it.
So, as you told me, I then installed the latest SuperSU APK from your link. It says it installed, but when I run it, it says root not detected and then has a link named, "How to Root", which launches my browser to a site that no longer exists.
I followed what you said. Where did I go wrong?
Thank You!
You didn't get it. Sorry to say this.
jwoegerbauer said:
You didn't get it. Sorry to say this.
Click to expand...
Click to collapse
Didn't get what?
I installed the BusyBox you gave me the link to.
I semi-installed the SuperSU you gave me the link to.
SuperSU did not fully install, because the Android is NOT rooted..
BusyBox had no SuperSU as part of it --the file you said to use even says "BusyBox Installer (No Root)".
(That should have tipped me off right away you had no clue, but I thought maybe you knew something.
So, you gave me the links for both of those files and it doesn't work.
I don't think you have any idea what you are doing; and shouldn't be explaining things you do not understand.
The "no root" BusyBox, does not include SuperSU.
If it did, why did you give me the link for the separate SuperSU file?
All the "no root" BB did was install a terminal emulator (with no su abilities).
The SuperSU didn't install, because the Android is NOT rooted.
If the Android WAS rooted, SuperSU would run and allow me to grant su privilges to the apps that require it to work.
You basically just wasted my time.
I would have just said "thank you" and moved on, but you are rude.
You don't know what you are talking about either.
Hopefully, this will help others, to not do what you say to do.
vidarr_kerr said:
Didn't get what?
I installed the BusyBox you gave me the link to.
I semi-installed the SuperSU you gave me the link to.
SuperSU did not fully install, because the Android is NOT rooted..
BusyBox had no SuperSU as part of it --the file you said to use even says "BusyBox Installer (No Root)".
Click to expand...
Click to collapse
You're right: BusyBox (No Root) doesn't come with SU-binary. Wasn't aware of this. I misinterpreted APK's title. Pitty.
ERRARE HUMANUM EST ( To err is human ).
Installing BusyBox containing SU-binary requires your device's bootloader got unlocked before, because Android's /system partition gets modified. Hence manage to unlock device's bootloader as 1st thing of all things. Good luck.
DL BusyBox latest: https://github.com/meefik/busybox/releases/download/1.31.1/busybox-1.31.1-46.apk
My last 2 cents here: SuperSU and SU binary are totally different things.