I have an issue where I can't read the logcat: neither via 'adb logcat', 'adb shell logcat' or any logcat app. I always get the following error: 'logcat read failure'.
On a fresh install, logcat works fine, but after I root the OnePlus 3, it stops working.
I tried rooting with 'BETA-SuperSU-v2.74-2-20160519174328-forced-systemless.zip' and with 'SuperSU-v2.78-201609011115.zip', root works, but the problem occurs with both.
I'm using the latest version of ADB, supplied with Android Studio.
Does anyone have an idea what's going on?
Can you open up a terminal emulator on the device and run logcat directly? I have no idea, but if I had to guess, it sounds like it could be a SELinux issue. Maybe set it to permissive temporarily and try? Have you installed any other zips apart from SuperSU-v2.78-201609011115.zip? Perhaps an audio mod like Viper4Android? Were any init scripts installed? Check if there's anything in /su/su.d...
Related
I am new to this forum so please forgive me if I have re-posted. My device was rooted using a windows system, and i have su. But, when I plug my device into my Linux machine it gives me - "insufficient permissions for device" error in adb shell, and I don't want to put eclipse on my laptop for development. I am hoping an engineering bootloader will fix my problem. If anyone can help me out I would appreciate it greatly.I am trying to test an app, and my device shows up as ?????????? in the ADB.(The emulator sucks too) Another reason I miss my G1
CyanogenMod CM6 (Nightly 7/11/10)
Koush's Recovery
HTC Incredible
setup the udev permissions for the phone??
http://developer.android.com/guide/developing/device.html
step#3
Without the udev rules, when you run the first adb command for any given session, it will start *without* the permissions it needs, and subsequent adb commands will fail. Setting up the udev permissions as doug suggests is the ideal way, but there is also a temporary workaround you can do in any given session without adding a rules file: just make sure to start the adb server with root permissions.
If adb is already started, you can 'adb kill-server' and then (ubuntu example) 'sudo adb start-server' or similarly run any adb command as root to also load the daemon with the permissions it needs.
askwhy said:
Without the udev rules, when you run the first adb command for any given session, it will start *without* the permissions it needs, and subsequent adb commands will fail. Setting up the udev permissions as doug suggests is the ideal way, but there is also a temporary workaround you can do in any given session without adding a rules file: just make sure to start the adb server with root permissions.
If adb is already started, you can 'adb kill-server' and then (ubuntu example) 'sudo adb start-server' or similarly run any adb command as root to also load the daemon with the permissions it needs.
Click to expand...
Click to collapse
Thanks. I was unaware of this.
Awesome! It worked like a charm. Thank you very much.
This has nothing to do with an Engineering Bootloader
So I'm trying to get into su to run gfree_verify to make sure my permaroot S-off/SIM card unlock/SuperCID was successful, but I'm getting a permission denied error.
What happens is, I type adb shell, then I type su, there's a really long delay, then it tells me Permission Denied. However, when I run the Terminal Emulator from my phone and type in the su command, I get root access just fine.
I used the "official" method that is on the HTC Vision Wiki that is located here. The only thing, however, is that my Android SDK install wasn't installed using any type of installer. I just extracted a zip file and shoved it in a random folder. I did make sure to run the Command Prompt as Administrator before issuing the adb shell command, but I'm still unable to get superuser access through the PC. Trying to use the adb root command gives me an "adbd cannot run as root in production builds" error.
Did I do something incorrectly?
adb kill-server
adb start-server
See if that works. If not, try rebooting your computer.
Sent from a Western Union telegram.
Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?
steviewevie said:
Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?
Click to expand...
Click to collapse
I rebooted the daemeon, computer, and also the phone. No dice.
The Superuser app is correctly installed. When I ran Adfree and attempted to go into SU in Terminal, I got the usual Allow Superuser access dialog. Both worked without any problems; like I said, I can get root access from the on-the-phone terminal, it's when I attempted to get root access from the adb shell command on my computer where I have problems.
No special ROMs, completely stock post-November OTA update. The only thing I flashed after permarooting was the Clockwork Recovery mod, but adb shell SU wasn't working before this. I initially used some outdated instructions (involving the use of the dd command, and the wpathis.ko or something). I read some more and learned these were out of dated, so I unrooted. I then used the instructions that are on the wiki using gfree to permroot.
gfree_verify works without any problems if I run it from the Terminal Emulator on my phone. Returns the proper values to indicate I'm SIM Unlocked, SuperCID, and S-off. I'm glad it works, but I still don't like the fact I can't use the adb shell. Typing characters on the G2 is a pain in the ass.
I still want to know why I can't enter superuser from the PC adb shell. Am I doing something incorrectly?
Thanks a lot for your help!
Try clearing data for the SuperUser app?
go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.
dietotherhythm said:
go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.
Click to expand...
Click to collapse
This worked perfectly! When I entered su from the command prompt, the SuperUser app popped up on the phone's side and I hit allow. It then let me through.
What exactly was broken though? Why did mounting everything from the Clockwork Recovery menu fix this?
Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...
I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
skyraven83 said:
Hi all,
I come with what is probably a silly question after I did not manage to stumble upon someone with the exact same situation while doing some googling around.
I have a Nexus 4, running the older Android 4.2.2 (did not update as I have some custom patches in there).
My phone has also been rooted for quite a while and working perfectly until recently something broke it (did not manage to find out when I broke it).
I have CWM installed and that is working fine.
I have SuperSu installed, now the latest version.
If I boot my phone into Recovery Mode and then I access it with the shell commands:
a) I mount the sdcard partition
b) I run
$ ./adb shell
~ # /system/xbin/su -
[email protected]:/ #
All works fine.
If I boot my phone normally and I run SuperSU, then I get: "no su binary installed" and the app kicks me out.
If I connect with ADB to it .. then I see that the binary is indeed in /system/xbin/su but trying to run it just doesn't do anything.
The process "freezes" and I don't get a command prompt anymore.
I can cancel it with CTRL+C and try to run it again but still ...nothing happens
This is one point where I am missing the Linux strace which I did not think of having here but would have enabled me to at least see what the SU binary is doing when it is not returning control to the command prompt or at least giving an error
Any idea what might be happening ?
Also..why is "su" working fine when called from the bootloader/CWM and why freezing when calling from the normal running system (aside from that funky error that no su binary is installed).
I tried so far flashing also an older version of SuperSU...same result, then went back to v1.94
Sorry if my problem is stupid but I don't seem to get my way around it...
Click to expand...
Click to collapse
it seems in the end that it was all in xprivacy problem....
solved and now it is functional
skyraven83 said:
I solved the first part by myself
Seems Xprivacy suddenly lost my preferences and was not allowing the running of su...
Now from the Terminal App on my Android, I can do: /system/xbin/su - and I get root.
But both SuperSU and SuperUser report that there's no SU binary....
Are they searching for it in some other path ?
I don't get it...
How can the binary not exist but if I run it by hand from the terminal app, everything works perfectly and I get to be root.
Click to expand...
Click to collapse
Just so you know
The reason you probably did not get responses to this is because you posted it in Galaxy Nexus section and not Nexus 4 forums
Hey there,
hopefully somebody can help me out here.
I tried to execute an .sh script which executes some adb commands. (kill-server / start-server). I sadly only get an "adb: not found" response.
Yes, ADP WIFI is enabled in Developer Settings. I also disabled and enabled and tried again. i also tried to execute adb command from "Android Terminal Emulator" App. That didnt work eighter. i am running 5.2.1.0 build. What am i doing wrong here?
You most likely need to put adb back onto the device. see here
So I updated a magisk module, and it's now causing a bootloop. After 2-3 times it boots to stock recovery and sits there. If I power off the phone and connect a cable, I can see the device in adb devices, but I'm unable to shell into it to attempt to fix this:
PS C:\platform-tools> .\adb.exe devices
List of devices attached
c966941e unauthorized
PS C:\platform-tools> .\adb.exe shell
adb.exe: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
PS C:\platform-tools>
I've tried killing the adb server like it suggested but that doesn't fix it.
Any ideas how I can get in this thing without having to factory reset?
Flash the original boot.img
I was able to fix it by booting the TWRP recovery image and using the File Manager to delete the module. Oddly enough, after I rebooted, my homescreen pages/shortcuts were all hosed up but I'll gladly take that over a reimage.
In case anyone is wondering, the module that did this was updating the "Busybox for Android NDK" module. Upon installing after fixing it above, it's working fine.
jbradshw said:
I was able to fix it by booting the TWRP recovery image and using the File Manager to delete the module. Oddly enough, after I rebooted, my homescreen pages/shortcuts were all hosed up but I'll gladly take that over a reimage.
In case anyone is wondering, the module that did this was updating the "Busybox for Android NDK" module. Upon installing after fixing it above, it's working fine.
Click to expand...
Click to collapse
I had no issues with that module using Fox's magisk manager
NameIsOptional said:
I had no issues with that module using Fox's magisk manager
Click to expand...
Click to collapse
Yeah I don't know what happened.