[Q] Custom kernal/ROM - root "disappeared" after some time - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting
Hello all,
Bit of background, I've been rooting phones since my old HTC Hero so I'm not a complete newb... but your help on this would be appreciated.
Got a Samsung Galaxy Note GT-N7000 some years ago, of course immediately rooted it and put on a ROM (non-stock, not CM). Anyhoo all things go well for several years. Late last year I put a new kernel and Asylum 4.4 ROM on it. Again all is pretty well, works as intended.
BUT
I tried to do something which required root the other day and things were not successful. Tried a few bits and pieces, fired up SuperSU app, informed me that root was out of date, flash a new one... tried that, but it failed.
Long story short, I've flashed new kernel/recovery (raw_kernel_r4_j43) and new ROM (4.4.2 SlimSaber), tried flashing SuperSU from recovery, tried FramaRoot... Flashing in recovery indicates success, but RootChecker still indicates that there is no root access. FramaRoot comes up with an error advising me to use the "build.prop" (maybe "local.prop"?) trick. Whatever I've tried is all to no avail. To be clear, the device works perfectly otherwise - boots up normally, runs apps without problem, etc. Developer menus and so on all available. Root access just doesn't stick, and whenever I try to do something that requires root access - change DPI for instance - the app just hangs.
Here's the log from RootChecker Pro:
Super User Application Status:
SuperSU application - version 1.93 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: lrwxrwxrwx root root 2014-03-12 13:18 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 91980 2008-08-01 13:00 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 GT-N7000 device by Root Checker Pro version 1.3.6 from joeykrim in the Android Market
Click to expand...
Click to collapse
And regarding Busybox:
BusyBox has been installed correctly!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
BusyBox binary location:
/system/xbin/busybox
BusyBox binary file information:
-rwsr-xr-x root root 1165484 2008-08-01 13:00 busybox
Installed BusyBox Version:
1.20.2-linusyang
BusyBox supports the following applets:
[, [[, acpid, adjtimex, ar, arp, arping, ash, awk, base64, basename, bbconfig, beep, blkid, blockdev, bootchartd, brctl, bunzip2, bzcat, bzip2, cal, cat, catv, chat, chattr, chgrp, chmod, chown, chpst, chroot, chrt, chvt, cksum, clear, cmp, comm, cp, cpio, crond, crontab, cttyhack, cut, date, dc, dd, deallocvt, depmod, devmem, df, dhcprelay, diff, dirname, dmesg, dnsd, dnsdomainname, dos2unix, dpkg, dpkg-deb, du, dumpkmap, dumpleases, echo, ed, egrep, env, envdir, envuidgid, ether-wake, expand, expr, fakeidentd, false, fbset, fbsplash, fdflush, fdformat, fdisk, fgconsole, fgrep, find, findfs, flash_lock, flash_unlock, flashcp, flock, fold, free, freeramdisk, fsck, fsck.minix, fsync, ftpd, ftpget, ftpput, fuser, getopt, grep, groups, gunzip, gzip, halt, hd, hdparm, head, hexdump, hostname, httpd, hush, hwclock, id, ifconfig, ifdown, ifup, inetd, init, inotifyd, insmod, install, ionice, iostat, ip, ipaddr, ipcalc, ipcrm, ipcs, iplink, iproute, iprule, iptunnel, kbd_mode, kill, killall, killall5, klogd, less, linuxrc, ln, loadkmap, logread, losetup, lpd, lpq, lpr, ls, lsattr, lsmod, lsof, lspci, lsusb, lzcat, lzma, lzop, lzopcat, makedevs, makemime, man, md5sum, mdev, mesg, microcom, mkdir, mkdosfs, mke2fs, mkfifo, mkfs.ext2, mkfs.minix, mkfs.reiser, mkfs.vfat, mknod, mkswap, mktemp, modinfo, modprobe, more, mount, mountpoint, mpstat, mv, nameif, nanddump, nandwrite, nbd-client, nc, netstat, nice, nmeter, nohup, nslookup, od, openvt, patch, pgrep, pidof, ping, ping6, pipe_progress, pivot_root, pkill, pmap, popmaildir, poweroff, powertop, printenv, printf, ps, pscan, pstree, pwd, pwdx, raidautorun, rdate, rdev, readlink, readprofile, realpath, reboot, reformime, renice, reset, resize, rev, rm, rmdir, rmmod, route, rpm, rpm2cpio, rtcwake, run-parts, runsv, runsvdir, rx, script, scriptreplay, sed, sendmail, seq, setconsole, setkeycodes, setlogcons, setserial, setsid, setuidgid, sh, sha1sum, sha256sum, sha512sum, showkey, slattach, sleep, smemcap, softlimit, sort, split, start-stop-daemon, stat, strings, stty, sum, sv, svlogd, swapoff, swapon, switch_root, sync, sysctl, syslogd, tac, tail, tar, tcpsvd, tee, telnet, telnetd, test, tftp, tftpd, time, timeout, top, touch, tr, traceroute, traceroute6, true, tty, ttysize, tunctl, tune2fs, ubiattach, ubidetach, ubimkvol, ubirmvol, ubirsvol, ubiupdatevol, udhcpc, udhcpd, udpsvd, umount, uname, uncompress, unexpand, uniq, unix2dos, unlzma, unlzop, unxz, unzip, uptime, usleep, uudecode, uuencode, vconfig, vi, volname, watch, watchdog, wc, wget, which, whoami, whois, xargs, xz, xzcat, yes, zcat, zcip
Results provided on your GT-N7000 device by Root Checker Pro version 1.3.6 from joeykrim in the Android Market -
Click to expand...
Click to collapse
Any help or ideas would be much appreciated, and thanks in advance!
Related
[Q] Galaxy Tab rooting problem
Hi, I tried to root a 7" Galaxy Tab (device MID7 with Marvell CPU) runing Android 2.3.5 by using z4root ver.1.3.0 but I haven't managed. I got the following response from Root Check Pro V1.2.7 (I have Superuser 3.0.7 installed). Verifying BusyBox: BysyBox has been installed correctly! Verifying Root: Root Access is not properly configured or was not granted. Detailed results: Superuser application - version 3.0.7 - is installed System file properties for root access: Standard location Check command: ls -l /system/xbin/su: Result: -rwsr-sr-x root root 64196 2008-08-01 20:00 su Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access! Question: which file and how do I execute it?? 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 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: Nosuch file or directory. Analysis: File /ststem/xbin/sudo does not exist. Root user ID and group ID status: SU binary not found or not operating properly System environement path: /sbin/vendor/bin /system/sbin/system/bin /system/xbin data/bin/ marvell/tel/busybox/bin ADB shell default user: ADB shell setting for standard access, stored in default.prop is configured as rootuser -ro.secure=0 Using the Root Browser I noticed that: - there is no /system/bin/su file (as correctly indicated by Root Checker) - folder /sbin is empty, although the Checker says there is a su flile there, but permission is denied. It the file hidden? - there is a /system/xbin/su file, - there is no /system/xbin/sudo file (as correctly indicated by Root Checker) - there is a /marvell/tel/busybox file, but not a folder I also have Terminal Emulator 1.0.41 installed, however it seems I cannot do anything with it now. I would appreciate explanations and suggestions about how to gain root, taking into considerations all of the above. Thank you.
Try using SuperOneClick. It worked for me: http://forum.xda-developers.com/showthread.php?t=803682
[Q] Rooted but no root access?
First, here is what root checker pro says about my root Super User Applications Status: Superuser application - version 3.1.3 - is installed! SuperSU application - is NOT installed. The SuperSU application is an alternative application for managing root access. System File Properties for Root Access: Standard Location Check Command: ls -l /system/bin/su: Result: -rwsr-sr-x root root 22364 2013-07-02 09:52 su Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access! Standard Location Check Command: ls -l /system/xbin/su: Result: /system/xbin/su: No such file or directory Analysis: File /system/xbin/su does not exist. 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 DROID BIONI I've had my verizon droid bionic rooted for a few months now on ICS using razors edge. Then I used Voodoo OTA root to temp unroot and updated to Jellybean. I restored root and everything was fine. So then I tried to install busy box after, but superuser wouldn't come up. So I deleted superuser and reinstalled it. Now Root checker says I don't have proper root access. (Also root browser still works fine) All other apps instead of having a su prompt they say I'm not rooted. Whats happening to my phone?
clyde1914 said: First, here is what root checker pro says about my root Super User Applications Status: Superuser application - version 3.1.3 - is installed! SuperSU application - is NOT installed. The SuperSU application is an alternative application for managing root access. System File Properties for Root Access: Standard Location Check Command: ls -l /system/bin/su: Result: -rwsr-sr-x root root 22364 2013-07-02 09:52 su Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access! Standard Location Check Command: ls -l /system/xbin/su: Result: /system/xbin/su: No such file or directory Analysis: File /system/xbin/su does not exist. 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 DROID BIONI I've had my verizon droid bionic rooted for a few months now on ICS using razors edge. Then I used Voodoo OTA root to temp unroot and updated to Jellybean. I restored root and everything was fine. So then I tried to install busy box after, but superuser wouldn't come up. So I deleted superuser and reinstalled it. Now Root checker says I don't have proper root access. (Also root browser still works fine) All other apps instead of having a su prompt they say I'm not rooted. Whats happening to my phone? Click to expand... Click to collapse Try rebooting.
If rebooting it doesn't work, it might be because when installing the busybox something on the System side messed up. The only way to fix this would be to HOB with Data and the re-rooting the device. Everything which can be found through this link Here. If you don't run a Linux distro this can be ran off of a Live USB setup. You can make a simple one using a 4 or 8 gig USB thumb drive and make sure that you let it make some space for updates and adding files. I would keep this around just for the fact that you don't need any specific drivers to run on Linux like you need on Windows. There are treads that have instructions on using Windows to get this done, but I would say that Ubuntu would be the best way to accomplish anything. Best of Luck.
nobe1976 said: If rebooting it doesn't work, it might be because when installing the busybox something on the System side messed up. The only way to fix this would be to HOB with Data and the re-rooting the device. Everything which can be found through this link If you don't run a Linux distro this can be ran off of a Live USB setup. You can make a simple one using a 4 or 8 gig USB thumb drive and make sure that you let it make some space for updates and adding files. I would keep this around just for the fact that you don't need any specific drivers to run on Linux like you need on Windows. There are treads that have instructions on using Windows to get this done, but I would say that Ubuntu would be the best way to accomplish anything. Best of Luck. Click to expand... Click to collapse Would it brick if I flashed it using RSD Lite? Just wondering because I've done that before and am familiar with it. If not, yes I do have Windows, not Linux, so I can try the HOB.
clyde1914 said: Would it brick if I flashed it using RSD Lite? Just wondering because I've done that before and am familiar with it. If not, yes I do have Windows, not Linux, so I can try the HOB. Click to expand... Click to collapse I would stick with the HOB just to keep the data. The only route I have found that will successfully re root it is done with Linux. It can be done running Linux on a thumb drive as long as there was space created for updates. Sent from my XT875 using Xparent Red Tapatalk 2
If that doesn't work and you need restore it to JB, here are the relevant links: FXZ files for Bionic: http://forum.xda-developers.com/showthread.php?t=2240725 RSD Lite Example (not for bionic, but gets you some of the links you'll need): http://forum.xda-developers.com/showthread.php?t=2231249 If you want to try it from linux, fastboot from linux: http://forum.xda-developers.com/showthread.php?t=1263009&highlight=fxz And if you need to root once you flash your JB stock image, you'll need something like this: Easy root: http://forum.xda-developers.com/showthread.php?t=2256439
Unable to Root
I have an HTC One Dev Edition (M7) and since day 1 I have had issues with getting root access. I have had it now for a few months and it seemed like I could only have root access for a few minutes after a reboot and then root access would be denied. I finally decided to dump the stock ROM and installed Android Revolution 3.0 GE and since installing it I am unable to even obtain root at all. I have tried several different methods, nothing seems to work. I have never had an issue with prior phones, which I buy 2-4 phones a year and always unlock and root it as soon as I power it on. I have even tried using Hasoon2000's Toolkit and the root process, flashes fine but when I reboot, no root. Here is the link from Root Checker. Root Access is not properly configured or was not granted. Super User Applications Status: Superuser application - version 3.1.3 - is installed! SuperSU application - is NOT 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: -rwsr-sr-x root root 366952 2008-08-01 05:00 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: root user - ro.secure=0 Results provided on your HTC One device by Root Checker Pro version 1.3.3 from joeykrim in the Android Market - http://goo.gl/NcnHn Anything thoughts?
phenixdragon said: I have an HTC One Dev Edition (M7) and since day 1 I have had issues with getting root access. I have had it now for a few months and it seemed like I could only have root access for a few minutes after a reboot and then root access would be denied. I finally decided to dump the stock ROM and installed Android Revolution 3.0 GE and since installing it I am unable to even obtain root at all. I have tried several different methods, nothing seems to work. I have never had an issue with prior phones, which I buy 2-4 phones a year and always unlock and root it as soon as I power it on. I have even tried using Hasoon2000's Toolkit and the root process, flashes fine but when I reboot, no root. Here is the link from Root Checker. Root Access is not properly configured or was not granted. Super User Applications Status: Superuser application - version 3.1.3 - is installed! SuperSU application - is NOT 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: -rwsr-sr-x root root 366952 2008-08-01 05:00 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: root user - ro.secure=0 Results provided on your HTC One device by Root Checker Pro version 1.3.3 from joeykrim in the Android Market - http://goo.gl/NcnHn Anything thoughts? Click to expand... Click to collapse go to recovery.....flash ARHD 3.0 GE...after install dont reboot....go to instal and point to the file you downloaded from: http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip then reboot...you should have your root back:good:
Cool, that worked for me. Any to thoughts on why with the stock ROM I would lose root after a few minutes? Doesn't really matter now but I am curious to why this was happening.
Probably you did not hit thanks button after somebody helped You... LOL
Never noticed it before.
S3 i9305 supersu binary problem
Samsung S3 i9305 supersu binary problem Quote: Originally Posted by cbmk I had similar problem. Here is what I did - 1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu. 2. Unzip 3. Use ODIN in the package to root. 4. Install ROM Manager. 5. Install SuperSU(Chainfire) from Play Store. 6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it 7. Install CWM Touch. Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware. ** Credit goes to all those hardworking folks who stay ahead in the game ** —------------------------------------------------------ I know this is an old problem and has been answered many times, i have read all thepossible ways to fix it and i have tried, over and over but I'm missing something. Please help. I rooted with Supersu, it worked for 2days then stopped. Now all the root apps can't work and i have tried everything to make it work, to no avail. Here is a copy of my Root hecker: Root access not properly configured or granted. Superuser Application Status Installed: SuperSU by Chainfire - version 2.46 System Files Status Standard Location Command: ls -l /system/xbin/su: Result: -rwxr-xr-x root root 66916 2015-04-17 00:03 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. 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. 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 Account Status Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1 Optional: ADB Shell User Status Non-Root Shell User Setting stored in /default.prop and configured as: ro.secure=1 Additional: System Environment PATH Status System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin _---------------------- So my device is rooted, but i don't have permission. Tried to copy .su file from xbin to bin, not possible. Uninstalled reinstalled, unrooted rerooted, reinstalled SuperSu from playstore. Made sure no double superuser programs running. Got rid of Knox. Tried to custom install Supersu update, says invalid certificate. I extracted SuperSU.zip and tried to copy the .su file to \bin but also didn't work. I believe if i can copy the .su file in \xbin to \bin the permissions wil be there. Bought Rootbrowser but error when copying. Or give permission on file SetUID. Can't run Bootbox cause didn't install before root stopped working. Also Titanium backup stopped working now. Any ideas how to fix? Don't want to factory reset. Can't be to difficult to fix. Any help will be appreciated this is the first time I have rooted. PS. If this post is in the wrong place please advise where itshould be. Thanks S
[Q] Samsung S3 i9305 rooted but not anymore with SuperSU
—------------------------------------------------------ I know this is an old problem and has been answered many times, i have read all thepossible ways to fix it and i have tried, over and over but I'm missing something. Please help. I rooted with Supersu, it worked for 2days then stopped. Now all the root apps can't work and i have tried everything to make it work, to no avail. Here is a copy of my Root hecker: Root access not properly configured or granted. Superuser Application Status Installed: SuperSU by Chainfire - version 2.46 System Files Status Standard Location Command: ls -l /system/xbin/su: Result: -rwxr-xr-x root root 66916 2015-04-17 00:03 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. 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. 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 Account Status Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1 Optional: ADB Shell User Status Non-Root Shell User Setting stored in /default.prop and configured as: ro.secure=1 Additional: System Environment PATH Status System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin _---------------------- So my device is rooted, but i don't have permission. Tried to copy .su file from xbin to bin, not possible. Uninstalled reinstalled, unrooted rerooted, reinstalled SuperSu from playstore. Made sure no double superuser programs running. Got rid of Knox. Tried to custom install Supersu update, says invalid certificate. I extracted SuperSU.zip and tried to copy the .su file to \bin but also didn't work. I believe if i can copy the .su file in \xbin to \bin the permissions wil be there. Bought Rootbrowser but error when copying. Or give permission on file SetUID. Can't run Bootbox cause didn't install before root stopped working. Also Titanium backup stopped working now. Any ideas how to fix? Don't want to factory reset. Can't be to difficult to fix. Any help will be appreciated this is the first time I have rooted. PS. If this post is in the wrong place please advise where itshould be. Thanks