I installed everything perfectly, boot into TWRP but I was never given a prompt to install supersu. So my phone isn't rooted. I'm running Android 4.1.2 and TWRP V.2.5.0.0.
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 2.00 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: lrwxrwxrwx root root 2014-06-29 14:30 su -> /system/xbin/su
Analysis: File: su is a symbolic link pointing to another file: /system/xbin/su
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 348160 2014-06-29 14:30 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SGH-T989 device by Root Checker Pro version 1.3.6 from joeykrim in the Android Market - http://goo.gl/NcnHn
Wrong forum, US variants have their own fora. Your thread belongs here, I've asked mods to move it. Sit tight until they do.
Karetus said:
I installed everything perfectly, boot into TWRP but I was never given a prompt to install supersu. So my phone isn't rooted. I'm running Android 4.1.2 and TWRP V.2.5.0.0.
Click to expand...
Click to collapse
You need to download the su zip and flash it in recovery.
Lokke9191 said:
You need to download the su zip and flash it in recovery.
Click to expand...
Click to collapse
This ^^^^^
Twrp never installed SU for me....always had to flash the zip.
KJ said:
This ^^^^^
Twrp never installed SU for me....always had to flash the zip.
Click to expand...
Click to collapse
Would you happen to have a link available? Or will any version do the trick?
Karetus said:
Would you happen to have a link available? Or will any version do the trick?
Click to expand...
Click to collapse
You should not use any version. Use the one I attached.
Related
Anyone knows how to install busybox?
I've tried to follow some guides but ends up with:
Code:
215:Desktop ricardo$ adb push busybox /data/local
580 KB/s (1083568 bytes in 1.823s)
215:Desktop ricardo$ adb shell
$ su
# cd /system/xbin
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cat /data/local/busybox > busybox
cannot create busybox: not enough memory
or
$ su
# cd /data/local
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# dd if=/data/local/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Out of memory
or
$ su
# cd /data/local
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# ./busybox cp /data/local/busybox /system/xbin
cp: can't create '/system/xbin/busybox': Cannot allocate memory
same here. cannot write to rw-mounted /system.
sucks
Try my zip file. Woked for me
The only thing that I want to change and I can't is the init.rc file. I tried to mount the / (rootfs) with rw, but every time I restart my device the file is copied, again, from the ramdisk image.
I have the same problem
ricardoft said:
Try my zip file. Woked for me
The only thing that I want to change and I can't is the init.rc file. I tried to mount the / (rootfs) with rw, but every time I restart my device the file is copied, again, from the ramdisk image.
Click to expand...
Click to collapse
What should I do with your files?
Nobody has a solution to this?
I don't think this is a memory issue though, .. added 512mb swap and still it claimed to be out of memory, ..
also I figured maybe hd space .. however when i ln /data/local/tmp/busybox to /system/xbin it had the same error.
I both tried ln from the system and ln from busybox both had same result.
It's not a memory problem! In order to install it you have to be in recovery mode.
Try:
While in recovery mode use adb to connect to our phone. Now transfer the zip file (busybox.zip) to your phone and install it via clockwork recovery -> install zip file -> select my zip file.
can anyone post the proper busybox file cause for some reason the file signature verification failed.
adb push busybox-signed.zip /sdcard/busybox-signed.zip
rebooted phone held down volume button while booting ..
choose recovery, ..
choose install zip from sdcard..
then i see a lot of no and one yes .. so i choose yes but the installation is aborted.
Just install titanium backup and click on 'problems?' at the bottom. It will install BusyBox for you.
it has error during installation at line 4 with your busybox.zip
somethinf like can not chmod
(rooted buzz with stock rom)
Elibongo said:
Just install titanium backup and click on 'problems?' at the bottom. It will install BusyBox for you.
Click to expand...
Click to collapse
Do what this guy said.
titanium install in /sdcard busybox, not in /system/bin (xbin) , so it is not usuable by other apps
i have installed it in during recovery mode in /system/xbin
how now to specify PATH for using commands from it?
kevin2516 said:
Do what this guy said.
Click to expand...
Click to collapse
you have read my mind especially since that isn't free software.
hellysmile said:
i have installed it in during recovery mode in /system/xbin
how now to specify PATH for using commands from it?
Click to expand...
Click to collapse
i think you need to create aliases however why install it in xbin anyways then, .. if you need to create aliases or links in bin.. ?
example
$ ln -s /data/local/tmp/busybox ls
$ ./ls
if it is in a path that is included in PATH executing a command will auto look for it in all directories defined in PATH env so basicly you could just create all the directories under /data/local/tmp/bin
and just then append that to PATH env echo $PATH then append :/data/local/tmp/bin to it and busybox should work as well.
Ofloo said:
you have read my mind especially since that isn't free software.
Click to expand...
Click to collapse
titanium backup is free software... look on the market, there's a free version and a donate version.
i have aliases in /system/xbin
they was created after busybox --instal -s
but in system allready exists some commands like ls => i want to use ls from busbox, not from system
and terminal emulator dont anderstand ^[ likes bindings
is there a definitive way to do this. There seems to be no clear way of doing it.
matpol said:
is there a definitive way to do this. There seems to be no clear way of doing it.
Click to expand...
Click to collapse
Maybe this helps:
fang0654 said:
To install:
1) extract and push busybox to your sdcard, reboot into recovery
2) mount /system
3) if you don't have /system/xbin (you should), create it
adb shell:
# mkdir /system/xbin (if necessary)
dd if=/sdcard/busybox of=/system/xbin/busybox
cd /system/xbin
chmod 755 busybox
./busybox --install .
4) reboot and done
OPTIONAL - before rebooting replace the busybox installed by the root process in /system/bin
1) mv /system/bin/busybox /system/bin/busybox.bak
2) cp /system/xbin/busybox /system/bin/busybox
Click to expand...
Click to collapse
from this site: http://forum.xda-developers.com/showthread.php?t=702634
The above is pretty straightforward. The only thing is you need to download the zip in the other thread and 'busybox' refers to the binary in the zip rather than the whole directory - as I understand it. Correct me if I am wrong but trying the dd command on the dir will not work.
matpol said:
The above is pretty straightforward. The only thing is you need to download the zip in the other thread and 'busybox' refers to the binary in the zip rather than the whole directory - as I understand it. Correct me if I am wrong but trying the dd command on the dir will not work.
Click to expand...
Click to collapse
You dont have to extract the binary into a folder, just extract the busybox file direct on your sdcard. Than the dd command should work, on my phone it works fine.
But if not, does the command cat in the adb shell work?
If so, try istead of the dd comand:
Code:
mount /sdcard
cat /sdcard/busybox > /system/xbin/busybox
And remember to start your wildfire in the recovery mode, that was the mistake I had done...
I thought I'd let folks know what I did in order to root on 8.5.1 and not have slowness. This isn't a complete walkthrough and assumes you have ADB drivers installed and working and access to ADB.
First I used the exploit found in this thread.
http://forum.xda-developers.com/showthread.php?t=2544736
I downloaded kindlehd2013_root.zip and also got the zip copy of superuser from
http://download.clockworkmod.com/superuser/superuser.zip
I extracted all to a folder. I then replaced the su from the kindlehd2013_root.zip with the superuser.zip armeabi folder version. Then you run the commands it has in the post.
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
Before I ran this last line I made sure su had the correct permissions:
type adb shell:
then ran the command
chmod 6755 /data/local/tmp/su
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
now you can get root via ADB by going into
adb shell
then run the command su
from there I made sure the su had the correct permissions again in the new location:
mount -o remount,rw /system
I had a complaint about space so I just removed the officesuite.apk in /system/apps to the sdcard
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
Then using the superuser.apk from the zip installed it.
adb install superuser.apk
Hope this helps others have success. From here you can follow the tutorials to get Google apps and such. I'd love to run an alternative ROM but have the LTE version and haven't been able to find one that has working LTE.
Hi Macman005!!
I want to use your method to root my Hd 8.9, I dont want too install a room, only install google services to use my chromecast. But before I want to Know:
How I move the officesuite.apk in /system/apps to the sdcard, if I have the space complaint you had?
I really appreciate any help you can provide
jaramosparra said:
Hi Macman005!!
I want to use your method to root my Hd 8.9, I dont want too install a room, only install google services to use my chromecast. But before I want to Know:
How I move the officesuite.apk in /system/apps to the sdcard, if I have the space complaint you had?
I really appreciate any help you can provide
Click to expand...
Click to collapse
On device you can use es file explorer -> enable root explorer from the left side the click on root explorer -> mount r/w -> then make sure /system is rw
Via ADB
adb pull /system/app/OfficeSuite.apk
adb shell
su for root
mount -o remount,rw /system
rm /system/app/OfficeSuite.apk
Hi Macman005
I had follow your instructions and I had manage to root my hd 8.9, total success!!!
Thanks!!
hi there folks,
so i've read through a bunch of guides and steps to accompish getting root on a kindle fire hd 8.9 running 8.5.1
i followed your above steps to the T but everytime i try and execute the exploit i get a error like this
***********
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
write: No space left on device
************
i read further into this post and in others that moving files around was the answer but i'm unable to move the files using
Code:
./adb shell
mv /system/OfficeSuite.apk /sdcard
i get a error like "failed cross device link"
so i'm guessing i'll only have access after rooting to move or delete files in /system
************
Code:
$ df
Filesystem Size Used Free Blksize
/dev 383M 32K 383M 4096
/mnt/asec 383M 0K 383M 4096
/mnt/obb 383M 0K 383M 4096
/system 872M 872M 0K 4096
/data 13G 372M 12G 4096
/cache 639M 10M 628M 4096
/efs 15M 4M 11M 4096
/mnt/sdcard 13G 372M 12G 4096
[email protected]:/system/app $
*********
any suggestions tips or links would be appreciated
Use adb pull to get the file out of /system/app then just try to delete it. I'm guessing it won't work though without root.
Did you check to see if su was in the /system/xbin/su dir?
macman005 said:
Use adb pull to get the file out of /system/app then just try to delete it. I'm guessing it won't work though without root.
Did you check to see if su was in the /system/xbin/su dir?
Click to expand...
Click to collapse
already tried rm -rf OfficeSuit.apk
pulling it leaves the file inplace
su is in place in xbin
Code:
[email protected]:/ $ cd /system/xbin/
[email protected]:/system/xbin $ ll
-rwxr-xr-x root shell 59392 2008-08-01 12:00 dexdump
-rwxr-xr-x root shell 63448 2008-08-01 12:00 hciconfig
-rwxr-xr-x root shell 36776 2008-08-01 12:00 hcitool
-rwxr-xr-x root shell 5608 2008-08-01 12:00 hdcp-test
-rwsr-sr-x root root 94208 2014-11-19 22:25 su
127|[email protected]:/sdcard $ su --help
Segmentation fault
139|[email protected]:/sdcard $ su touch test
Segmentation fault
139|[email protected]:/sdcard $ su
Segmentation fault
139|[email protected]:/sdcard $
i've tried tinkering with permissions with no luck
i'm not worried about root on the kindle os, i mostly want to stick CM11 on it - i recall reading a article on cyanogenmod's page about flashing the CM11 rom on the kindle it didn't mention that root was required i just kind of assumed it was to be able to install a second bootloader etc
If you don't need to follow my root you just use this tutorial. The root being slow isn't a big deal since you'll replace it with cm11
http://forum.xda-developers.com/showthread.php?t=2789289
macman005 said:
If you don't need to follow my root you just use this tutorial. The root being slow isn't a big deal since you'll replace it with cm11
http://forum.xda-developers.com/showthread.php?t=2789289
Click to expand...
Click to collapse
sweet thanks for the tip - i'll give this one a try (i'd tried a couple other methods with no success)
Everything good for me until:
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
Then I get:
Code:
Device detected: KFJWI (IMM76D)
Attempt acdb exploit...
KFJWI (IMM76D) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
After that nothing works. Any ideas where i might have taken the wrong turn?
Do you have su in the /system/xbin folder?
macman005 said:
Do you have su in the /system/xbin folder?
Click to expand...
Click to collapse
Thanks for reply macman.
I gave up... Followed the instructions you gave and all seemed well until step: adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
So not sure but will check when I can try again. Would love to totally clean out amazon junk and turn into android pad.
Im having the same problem as Justanumber, and I'm not sure if I have the su in the /system/xbin folder
I was able to root 8.5.1. What I did was try the Bin4ry method, first option 1, when that didn't work option 2. It made my kindle run slow and was almost unusable. Being very patient due to the slowness, I tried the QEMU method. It seems like some things transferred to the kindle and others didn't and I got an error. I then went back to Bin4ry and ran unroot and got an error. The last thing I tried was to run root option 2 once more and success. I then went right to Hashcodes post and installed a second bootloader and cm11. I'm not a developer so I put everything I did. Maybe someone who knows what they are doing can figure out what is needed from all that. Whatever I did though, I got for on 8.5.1 without any issues once it went through
Sent from my HTC6525LVW using XDA Premium 4 mobile app
worked perfectly for me on 8.5.1, always a bit nervous messing with the kindle but no problems . Big thanks to the op. I didn't have any complaints about space, and there was none of the slowdown problems so many people complain about after rooting the new firmware. Now i have installed hashcode's cm12 port and its like a brand new gadget...
I got as far as "adb shell", but the su command returns "permission denied"
What exactly do you mean when you say "check su permissions." First time using ADB.
please help me
macman005 said:
I thought I'd let folks know what I did in order to root on 8.5.1 and not have slowness. This isn't a complete walkthrough and assumes you have ADB drivers installed and working and access to ADB.
First I used the exploit found in this thread.
http://forum.xda-developers.com/showthread.php?t=2544736
I downloaded kindlehd2013_root.zip and also got the zip copy of superuser from
http://download.clockworkmod.com/superuser/superuser.zip
I extracted all to a folder. I then replaced the su from the kindlehd2013_root.zip with the superuser.zip armeabi folder version. Then you run the commands it has in the post.
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
Before I ran this last line I made sure su had the correct permissions:
type adb shell:
then ran the command
chmod 6755 /data/local/tmp/su
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
now you can get root via ADB by going into
adb shell
then run the command su
from there I made sure the su had the correct permissions again in the new location:
mount -o remount,rw /system
I had a complaint about space so I just removed the officesuite.apk in /system/apps to the sdcard
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
Then using the superuser.apk from the zip installed it.
adb install superuser.apk
Hope this helps others have success. From here you can follow the tutorials to get Google apps and such. I'd love to run an alternative ROM but have the LTE version and haven't been able to find one that has working LTE.
Click to expand...
Click to collapse
Please help sir can you do a video of it on how to root the version 8.5.1 cause I cnt follow hard instruction pls lemme see
macman005 said:
Do you have su in the /system/xbin folder?
Click to expand...
Click to collapse
Could you specify a little on how to find this out?
I'm also getting stuck after:
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
"Attempt acdb explot...
KFJWI <IMM76D> is not supported.
Attempt fj_hdcp exploit...
Attempt msm-cameraconfic exploit...
Detected kernel physical address at 0x80008000 from iomem
Attempt put_user exploit...
Thanks
macman005 said:
I thought I'd let folks know what I did in order to root on 8.5.1 and not have slowness. This isn't a complete walkthrough and assumes you have ADB drivers installed and working and access to ADB.
First I used the exploit found in this thread.
http://forum.xda-developers.com/showthread.php?t=2544736
I downloaded kindlehd2013_root.zip and also got the zip copy of superuser from
http://download.clockworkmod.com/superuser/superuser.zip
I extracted all to a folder. I then replaced the su from the kindlehd2013_root.zip with the superuser.zip armeabi folder version. Then you run the commands it has in the post.
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
Before I ran this last line I made sure su had the correct permissions:
type adb shell:
then ran the command
chmod 6755 /data/local/tmp/su
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
now you can get root via ADB by going into
adb shell
then run the command su
from there I made sure the su had the correct permissions again in the new location:
mount -o remount,rw /system
I had a complaint about space so I just removed the officesuite.apk in /system/apps to the sdcard
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
Then using the superuser.apk from the zip installed it.
adb install superuser.apk
Hope this helps others have success. From here you can follow the tutorials to get Google apps and such. I'd love to run an alternative ROM but have the LTE version and haven't been able to find one that has working LTE.
Click to expand...
Click to collapse
I'm pretty proficient with ADB, so your steps were easy to follow. Now I have a rooted Kindle Fire HD 8.9 on 8.5.1.
Thank you
Hello,
I'm following these instructions. When I run su, i get "Permission Denied."
Any ideas? The steps before seem to run fine.
When i run the exploit, i see the follwing:
Device detected: KFJWI (IMM76D)
Attempt acdb exploit...
KFJWI (IMM76D) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt put_user exploit...
---------- Post added at 04:27 PM ---------- Previous post was at 03:48 PM ----------
I got it to work.
I enterd adb shell, then exploit again, without the rootme.sh argument.
Then su worked and I was able to get everything to run
Thanks for the instructions!
At first I thought it was maybe because I didnt'nt have enough free space on my sd card so I made sure I had 3GB's free but I still got this when I clicked install:
[13:04:26] Updating configuration file ... done
[13:04:27] >>> begin: install
[13:04:27] Checking mount points ... done
[13:04:27] Checking installation path ... done
[13:04:27] Making new disk image (512 MB) ... fail
[13:04:27] <<< end: install
And this when I try to reconfigure:
[13:02:49] Updating configuration file ... done
[13:02:50] >>> begin: configure
[13:02:50] Mounting partitions:
[13:02:50] / ... fail
[13:02:50] <<< end: configure
When I check my root stutus I get this message:
Congratulations! You have root access!
Super User Application Status:
SuperSU application by Chainfire - version 2.36 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 71264 2014-11-30 16:22 su
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SM-T800 - Android 4.4.2 device by Root Checker Pro version 1.3.9 from joeykrim in the Android Market
Can anybody tell me why I get this fail message after clicking install?i
Please help
Thank You
AO!
Same issue
Im currently having the same issue with trying to install kali on my tab s. Have root and even sd formated to ext4 but still issues .
Check your SE(Linux) status on Settings / About Device. If it says Enforcing then this is the cause of the problem.
You need to change it to permissive, but you can't do it on a stock rom. You need a kernel with permissive mode
enable or a custom rom with a permissive kernel.
Good Luck
eupeso4 is wrong. You don't need a different kernel. There is an app called SELinuxModeChanger... It works charms
I've attached the app below.
soulcrusher101 said:
eupeso4 is wrong. You don't need a different kernel. There is an app called SELinuxModeChanger... It works charms
I've attached the app below.
Click to expand...
Click to collapse
Also, go to terminal emulator after this.
Code:
su
getenforce
If you get "Enforcing" as a response, it's FUBAR. you can try to run the command "setenforce 0" as su as a workaround but if the app didn't work, it won't likely work either.
Molikai1988 said:
Also, go to terminal emulator after this.
Code:
su
getenforce
If you get "Enforcing" as a response, it's FUBAR. you can try to run the command "setenforce 0" as su as a workaround but if the app didn't work, it won't likely work either.
Click to expand...
Click to collapse
Okay i got enforcing. my deviceis SC-04E thats is S4 (docomo). i want to set SE Linux to premissive tell me the solution
soulcrusher101 said:
eupeso4 is wrong. You don't need a different kernel. There is an app called SELinuxModeChanger... It works charms
I've attached the app below.
Click to expand...
Click to collapse
Doesn't work on stock kernels.
I tried everything. But it doesn't work even after changing the SELinux to permissive., But after searching a lot, I found a thread which said me to change the partition to ext2. I changed the partition and then it all worked like charm.., If you still have issues, follow the guide in this link from start to end-https://github.com/meefik/linuxdeploy/issues/183, This solved most of the issues I had..
Linux Deploy Mounting Partitions Fail
Bro problem solved by me..
Check out this video
https://youtu.be/n5opus76c3k
So I rooted my phone used it for a bit then for some reason it messed up so I bought root checker pro and it said Root access not properly configured or granted.
Superuser Application Status
NOT installed: Superuser by ChainsDD, SuperSU by Chainfire, or Superuser by Koush
System Files Status
Standard Location
Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 66916 2015-01-23 18:48 su
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Alternative Location
Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
User and Group ID Status
Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1
ADB Shell User Status
ADB setting for shell access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
System Environment PATH Status
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
Results provided for your SGH-I747M - Android 4.3 device by Root Checker Pro version 1.4.2 from joeykrim in the Android Market - my device is an android Galaxy s3 version is 4.3 and I'm not running a Rom and I used towel root please help I can't find the solution anywhere
Hi there,
Please wait until mods will move this thread to the device specific forum.
Stand by
The simplest way to get root in my opinion is to flash Philz Touch recovery for the d2lte using Odin. Then flash super su from recovery, boot phone, let supersu and disble knox, reboot phone, done.
I have an Alcatel ideal 4060a and it's does the exact same thing an says the same when I do my root checker. What do I do to get my root back?
If you have an older kernel, made on or before May 2014, then you can use towel root to gain root.
Hello been awhile, I have a Aspen a785. Rooted. Used China site few years back. Installed kingroot. Tab was new then. Only place to unlock it at the time.
I run Linux machines. No windows at all available. . I've tried to get su working have pro key. Problem is kingroot has controls of root. Disabled I can't get su working properly, fx has no root access. Super won't install. King active , su installs but doesn't control root, it Thinks it does, it can blok access but only if king is active . king is in #/system/app
Is there a source file I can manually install or modify to change permissions?
I did find a file permissions.text or something that showed eu.chainfire??? As none
And com.kingroot.??? As ,3003,1028,####,####,###.
Is there a web source for info on these files?
Is there a Linux method software available for su install and rooting?
update! need help
Iv dug a bit more
No file install-recovery-2.sh
File install-recovery.sh shows
#!/system/xbin/sh
/system/xbin/Ku.sud -d &
/system/etc/install-recovery-2.sh
Mount -0 remount -rw /system
/system/bin/toolbox chcon ubject_r:system_file:s0 /system/app/kinguser.apk
chcon ubject_r:system_file:s0 /system/app/kinguser.apk
/system/bin/toolbox chcon ubject_r:system_file:s0 /system/xbin/su
chcon ubject_r:system_file:s0 /system/xbin/su
/system/etc/kds --global-daemon 1
#end
Would changing /kinguser.apk too ( EU.chain fire.supersu-2.apk) solve issue with root control at boot up? Then delete all references to king?
Unable to edit install-recovery.sh seams r protected