yashsingh1/xdaforums huggingface dataset:
[Android Software Development] fastguy:
I guess we will all need selinux permissive kernels. Samsung Stock kernels don't let selinux to be set permissive.
[Android Software Development] kmdangi:
============

After trying all possible solutions, I could finally get ADB is working !!!

I replaced the ADB in my laptop after reading the following (down loaded the ADB from this post) :

http://xdaforums.com/galaxy-nexus/help/resolved-adb-longer-android-4-2-2-t2144709
[Android Software Development] Tungstwenty:
Just FYI ...

I'm running the Stock 4.4.2 ROM on a Locked Bootloader Xperia Z.

I started getting these errors on the logcat every second, after moving from 4.3 to 4.4:

E/UsbDebuggingManager( 1307): Communication error:
E/UsbDebuggingManager( 1307): java.io.IOException: Connection refused
E/UsbDebuggingManager( 1307): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/UsbDebuggingManager( 1307): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:287)
E/UsbDebuggingManager( 1307): at android.net.LocalSocket.connect(LocalSocket.java:130)
E/UsbDebuggingManager( 1307): at com.android.server.usb.UsbDebuggingManager.listenToSocket(UsbDebuggingManager.java:75)
E/UsbDebuggingManager( 1307): at com.android.server.usb.UsbDebuggingManager.run(UsbDebuggingManager.java:111)
E/UsbDebuggingManager( 1307): at java.lang.Thread.run(Thread.java:841)

adb shell was still working, including root, but I'm not sure what this error might be affecting.

Looking into adbd-insecure, I noticed it includes binaries for sdk 17 only, so I went ahead and compiled my own adbd from the 4.4.3 sources and applied what I believe might have been the changes from Chainfire (should_drop_privileges).

All is running fine with my binary, so the solution might be a mere compilation of the newest sources for sdk 19 ...
[Android Software Development] Phatboyj420:
adb shell
su
-c "cp -f /sdcard/parted /system/xbin/"

I get

tmp-mksh: -c: not found
[Android Software Development] :
"adb-insecure.apk" Does not work with AT&T Galaxy Note 3 SM-N900A is there any alternatives for adb push, cp. mv, ETC. to system while booted

I've tried everything mentioned can not write to /system

adb shell
su
mount -o remount,rw /system
adb push /sdcard/parted /system/xbin/

I get

error: device not found
[Android Software Development] zeppelinrox:
After doing "adb shell" you are executing commands from within Android.

adb commands won't work when you're in Android.

adb commands are for use on a computer.

adb shell
su
mount -o remount,rw /system
cp /sdcard/parted /system/xbin/

Then set permissions for /system/xbin/parted

And you better know what you're doing with parted because judging from your previous post, with the "tmp-mksh: -c: not found" error, you know nothing about important commands and are headed for a disaster.
[Android Software Development] Phatboyj420:
Thanks, But I figured this out on my own

as far as the your response to the "tmp-mksh: -c: not found" error Thats what I got after your claim that running su -c would work, as a work around for pushing to system

I'm not ignorant

and no I don't know

enough

about important commands, as to why I'm here seeking guidance

All that i'm doing with parted, "now that I finally got it to push" is using it's print command via

" parted /dev/block/mmcblk0 print > /storage/extSdCard/GN-3_parted.txt "

" exit "

" exit "

" cd C:\Users\PB-2\Desktop\GN-3_Tmp\Working GN-3_Tmp\ "

" adb pull /storage/extSdCard/GN-3_parted.txt "

" adb shell "

" su "

" rm /storage/extSdCard/GN-3_parted.txt "

" exit "

Thus there is nothing dangerous being done with parted, But I will say thank you for your concern

Have Your supercharger scripts been updated to work with Kit-Kat
[Android Software Development] zeppelinrox:
1. Well you had adb push while you were still within adb shell ie. executing adb push from within the phone.

2. Its 1 line, not 3 lines.

adb shell su -c "cp -f /sdcard/parted /system/xbin/"

3. SuperCharger runs fine but the patch hasnt been updated as of yet. Too busy lately to dive into it 100%
[Android Software Development] eortizr:
anybody having this working on the Galaxy S5? after installing and enabling adbd.apk I lose adb connection even after killing adb and rebooting the phone. Once I remove adbd and reboot the phone ADB starts working again.

Any suggestions?

Thanks
[Android Software Development] :
It's not up to par with the latest API. Your best bet is to take the source, modify it as needed, then build. If this isn't in your range of experiences then you may need to reach out to someone who would be willing to assist. I'm currently on 4.2.2 (API 17) so I am not affected.
[Android Software Development] E:V:A:
Is that SELinux Enforced? If you got those errors also check the AVC error log.

Perhaps you could post your diff changes and binary somewhere? (GitHub?)

That might also help Chainfire updating this, and/or letting someone else may take over maintaining this.
[Android Software Development] Tungstwenty:
Yes, it's enforced. The avc messages I have are these ones:

<5>[142082.164729] type=1400 audit(1403706568.189:1090): avc: denied { getattr } for pid=7216 comm="zygote" path="socket:[7854]" dev="sockfs" ino=7854 scontext=u:r:untrusted_app:s0 tcontext=u:r:init:s0 tclass=unix_stream_socket op_res=0 ppid=553 pcomm="zygote" tgid=553 tgcomm="zygote"
<5>[142082.165064] type=1400 audit(1403706568.189:1091): avc: denied { getopt } for pid=7216 comm="zygote" path="/dev/socket/zygote" scontext=u:r:untrusted_app:s0 tcontext=u:r:init:s0 tclass=unix_stream_socket op_res=0 ppid=553 pcomm="zygote" tgid=553 tgcomm="zygote"
...
<5>[142083.519862] type=1400 audit(1403706569.550:1092): avc: denied { read } for pid=7237 comm="su" name="/" dev="selinuxfs" ino=1 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=dir op_res=0 ppid=20782 pcomm=4173796E635461736B202332 tgid=20346 tgcomm=".chainfire.adbd"
<5>[142083.520136] type=1400 audit(1403706569.550:1093): avc: denied { search } for pid=7237 comm="su" name="/" dev="selinuxfs" ino=1 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=dir op_res=0 ppid=20782 pcomm=4173796E635461736B202332 tgid=20346 tgcomm=".chainfire.adbd"
<5>[142083.520350] type=1400 audit(1403706569.550:1094): avc: denied { read } for pid=7237 comm="su" name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file op_res=0 ppid=20782 pcomm=4173796E635461736B202332 tgid=20346 tgcomm=".chainfire.adbd"
<5>[142083.520625] type=1400 audit(1403706569.550:1095): avc: denied { open } for pid=7237 comm="su" name="enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file op_res=0 ppid=20782 pcomm=4173796E635461736B202332 tgid=20346 tgcomm=".chainfire.adbd"
<5>[142083.520838] type=1400 audit(1403706569.550:1096): avc: denied { getattr } for pid=7237 comm="su" path="/sys/fs/selinux/enforce" dev="selinuxfs" ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file op_res=0 ppid=20782 pcomm=4173796E635461736B202332 tgid=20346 tgcomm=".chainfire.adbd"
...
<5>[142091.615199] type=1400 audit(1403706577.638:1097): avc: denied { read write } for pid=7466 comm="MtpMsgHandlerTh" name="mtp_usb" dev="tmpfs" ino=8342 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:mtp_device:s0 tclass=chr_file op_res=0 ppid=553 pcomm="zygote" tgid=30527 tgcomm="d.process.media"
<5>[142091.615443] type=1400 audit(1403706577.638:1098): avc: denied { open } for pid=7466 comm="MtpMsgHandlerTh" name="mtp_usb" dev="tmpfs" ino=8342 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:mtp_device:s0 tclass=chr_file op_res=0 ppid=553 pcomm="zygote" tgid=30527 tgcomm="d.process.media"

The 2nd block is related with adbd-insecure (the app), but it's not stopping it from replacing the /sbin/adbd binary.

The 3rd block (MtpMsg...) might be relevant, perhaps?

Anyway, the change I applied before compiling is fairly simple. Just patch this function to return 0.
[Android Software Development] E:V:A:
Yes, that does look like the problem. However, make sure you run the latest SuperSU. Because I have some SELinux trouble with SSHelper (or any other SSH app for that matter) to access /dev/pts|/ptmx for job control. Then I noticed to my great surprise, that after updating SuperSU from 1.94 to 2.00, the AVC errors from SSHelper changed, bt probalem still not resolved. And we're all screwed by Google who doesn't give us the proper tools to handle, edit or check our SELinux policies, before stating to Enforce all over the place, by default.
[Android Software Development] Tungstwenty:
I'm running SuperSU 2.00 so that's not the reason, at least not in my case.
[Android Software Development] Saeviomage:
Just a note

on my galaxy 3 running 4.3, I was getting the problem where enabling adbinsecure was disabling usb debugging, regardless of the settings menu. I solved it by opening a su command line and typing setenforce permissive. After that adbinsecure worked fine.

I understand that on some galaxy devices you may need to use setenforce 0, and on some devices it won't work at all. Use getenforce to see if selinux is set to enforcing or permissive, and remember to set it back when you are done.
[Android Software Development] zentaury:
Doesn't work on rooted N7100 (Galaxy Note II). Getting USB Debugging disabled right after ADBD is enabled :(. What could I do to remount root anyways?
[Android Software Development] Belamigo:
Turns off the USB connection, stays off until phone reboots

Some users of this app are reporting success with old versions -- especially v1.20. By success, I mean it's not turning off Android Device in the MS Windows' Device Manager. .

I've been searching with Google for these older apk's, and went through all 14 pages of this thread looking for a link.

Where can someone tell me where the other users are finding these old versions? Don't see it on Play ...

Incidentally, the phone I'm trying to get this running on is a Huawei U8510-1, with Gingerbread, in case someone else knows why the most recent version isn't working. Or, if there's another way on to do this on an older phone?
[Android Software Development] Belamigo:
No joy.

:( Sorry, v1.30 didn't work on the Huawei, and now, still not working on the M-Horse mini .. .

With the current version (v1.30), Android Device again disappears from Device Manager immediately after the Enable Insecure box is checked. And then, it won't come back until the phone is rebooted.

But, I finally found a copy of v1.20 by searching, and more searching, on the 'net. Without any other links in this thread, I had to get if from one of those sites where you have to give away your firstborn son, before it lets you access the file:eek: -- is this the only way to get previous versions of this app??

I would much rather that we could have a link to a more trustworthy source!

I'm going to put the Huawei aside, and work on the M-Horse phone, and hope for better luck.
[Android Software Development] Belamigo:
Success with v1.20 and M-Horse phone

On an M-Horse9500mini, running Mocordroid, the most recent version, v1.30, failed to create insecure root.

When the app's check-box was 'ticked', the line in Device Manager, Android Device - Android Composite ADB Interface, disappeared. Mocordroid seems to repair the problem more readily than 'regular' Android, as 'unticking' the check box brought back the 'Android Device' -- without rebooting the phone.

:good: On the other hand, according to info in this linked page, on how to test for insecure root, v1.20 is working correctly.

Once Android Device had cycled back-and-forth a bit, it then stabilized, and remained in place. This wasn't possible with v1.30.

To verify the result, I used a test for insecure root, given in the linked article. Querying shell id gives the following result:

C:\Users\Belo>adb shell id
[B]uid=0(root) gid=0(root)[/B]

An uid value of '1' would have meant secure root was still in effect, and so the app had failed.

On this M-Horse phone running Mocordroid, the command prompt works differently after you have insecure root access. Normally, adb shell brings up the '$' prompt. After this app runs and the check-box has been 'ticked', the command adb shell displays the '#' prompt right away, without having to first enter su.
[Android Software Development] Belamigo:
About the older version working where the current version failed, I have read the entire thread to this point and know this isn't supposed to happen. But I did come across one or two posts where someone had success. Maybe there's enough detail here to figure out why?
[Android Software Development] jazzruby:
This is exactly the purpose of adbd Insecure; so a remote ADB shell has root (su) access.

As you already know, with adbd Secure your adb shell does not have root (su) access so running a remote command like:

adb push MyFile /data/media/0

will fail.

HTH,

-JR-
[Android Software Development] phaedrus43:
Thank you [MENTION=631273]Chainfire[/MENTION] your contributions to the android community are awesome!
[Android Software Development] tobbbie:
I had experienced the same with my S4 mini on 4.4.2. To solve it finally I use the Wanam Xposed module where in the Security Tab you can set the SELinux to Permissive. Now all things with ADB and TotalCommander ADB plugin now finally work as they did with my older devices on ICS and JB.
[Android Software Development] Chainfire:
v2.00 released with 5.0 lollipop support
[Android Software Development] starbase64:
[MENTION=631273]Chainfire[/MENTION]

the app is same as "ro.adb.secure=0" from ramdisk?
[Android Software Development] Chainfire:
Similar!
[Android Software Development] Megaflop666:
Thanks for everything you do [MENTION=631273]Chainfire[/MENTION]
[Android Software Development] bombadier:
Is the adbd thats packed in the new version working with ADB wireless? I used to make an insecure kernel by making the changes to default.prop but to get it working I needed the adbd version packed into this app,only problem was that this adbd breaks adb wireless
[Android Software Development] Fuzzy13:
For someone that still uses Android Commander, this app has served me very well for the past couple years. Thanks again for this great app.
[Android Software Development] jimi27:
hi all

i am on a n9005 in kitkat 4.4.2

i confirm that this app kill adb wireless

that worked fine on all my precedent phones and tablets.

i search from one month why adb wireless not work and i just found the culprit !

i can reproduce the problem in real time

when i click the case the shell is closed immediatly
[Android Software Development] vampirefo:
doesn't work on intel devices, do you have a intel version?
[Android Software Development] dront78:
pls make adb wireless work
[Android Software Development] burakgon:
Damaged my adb on Mediatek 6589 4.4.2 kitkat device.
[Android Software Development] vampirefo:
Unistall app reboot a few times.
[Android Software Development] dtolos:
Hello with season Greetings!

I am a new owner of Huawei Ascend P7. I have a stock rom 4.4.2 and I have a serious problem with set_immutable.list (the app that blocks every change in /system). It was already rooted with SuperSu 1.2 (I think) installed and I re-installed through recovery the latest version of SuperSu v2.40. I was trying to install Busybox with no luck, even in a different directory or different versions.The SuperSu couldn't "overwrite" the set_immutable.list at /system, the folder that Busybox would going to be installed. I had a long discuss about it in this thread but with no result. After a long research I found your app and I installed it (sorry for non-pay version but I need to test it :) ) from here. Everything seems to be fine but it is not true. The /system is still not accessible (modify/delete/edit) and I test it with a simple way, to try to create an empty folder at /system. In the same time I create it in the same time is not exist. Is still unable to install Busybox! Any idea what I have to do or what it happens pls? Do you want from me to do a kind of a test to see what is happening?

Thank you in advance!
[Android Software Development] Chainfire:
(1) You quoted the entire first post without any reason whatsoever. It's not relevant to your post, so it shouldn't be quoted

(2) None of this has anything to do with adbd Insecure, but with your phone's protections. This is not the right place to post.

(3) Unburdened by any experience or knowledge about Huawei devices, I found the answer to your problem within 2 minutes of Google'ing. I suggest you try the same.
[Android Software Development] dtolos:
Thanks for your reply!

First of all I want to apologize about my post. I am feeling that your answer sounds angry but never mind I apologize again. I want to be clear that my post it has nothing to do with your app if it is working or not. I am sure that is perfect.

1),2) The reason that I quoted the entire post probably it's my fault but it became from this sentence "

[...]If you are running a stock (made by the phone manufacturer) kernel on your device, chances are adbd is running in "secure" mode, even if you are rooted. This app lets you run adbd in "insecure" mode, which gives you root access in "adb shell", allows access to system files and directories through "adb push/pull", and lets you run the "adb remount" command to make your /system partition writable".

. I thought that was described my situation.

I thought that it will solve my problem with inaccessible /system in my device and that's why I post it.

3) It is my 5th day to try find a solution. Maybe I don't google it as it should! But I don't know how can I describe it (search it). See, I don't know the exactly problem.

Sorry for any inconvenience!

Best Regards.
[Android Software Development] meiser:
Hi Chainfire,

thanks for this app. It works on my Samsung Galaxy S5 (with Android 4.4.2), but only in USB mode. The wireless adb app doesn't work anymore.

I'd be very grateful if you made wireless adb work. Thanks a lot in advance!

Best regards,

meiser
[Android Software Development] blackdir:
adb insecure v2 for intel devices?

[MENTION=631273]Chainfire[/MENTION]

thanks for this great app!

It is always working very well on rooted devices! :D

Untill now: I installed it on a Lenovo Yoga 2 10 tablet (intel powered) rooted but I believe adb-insecure is not able to patch kernel and the device is not seen by adb when adbinsecure is enabled :confused:

Is it due to the fact that it is a non ARM device?

Any chance to have adb insecure working also on these devices?

thanks

Dario
[Android Software Development] dhawansagar:
replacing adbd in boot.img

So I tried replacing the adbd binary in the stock boot.img for a nexus 5 running 5.0.1

For some reason, when I boot the device, adbd isn't running correctly and adb can't find any device.

I've tried this with the adbd.21.png (obviously) and have also confirmed that it works with the older binaries (17) when using the 4.4.4 boot.img.

What changed? For now, I ran CF-Autoroot to patch the device, and then re-flashed the kernel (stock adbd binary). Root was retained (even with superSU disabled) and

the behaviour is identical to copying your adbd binary into the ramdisk.

The kernel just has some flags changed in the default.prop. If I run CF-autoroot after flashing the kernel, it overwrites my changes.

So why does replacing the adbd in the stock boot.img not work anymore?
[Android Software Development] ertioct:
For Huawei users: it worked like a charm in Honor 6 H6-02. I have rooted and busyboxed my dev before using adb insecure. Then, I had to wait a bit and finally it worked. Now I can use Android Commander as root. Thank you very much.
[Android Software Development] brandonabandon:
samsung galaxy s captivate/cm11=adb remount

remount failed: Permission denied

selecting option enable at boot+reboot

current status=binary:insecure

usb debugging:enabled

default.prop=ro.adb.secure=1

ro.secure=1

help no ramdisk
[Android Software Development] soumyaxoloq900:
It seems that this doesnt work in my device.

Mine is Xolo Q900 and installed MIUI from here.

Although the Titanium Backup showing root access available I am too getting the "No Root access" error in Android Commander. Tried to install this but it showed "could not patch"

Peculiar things : My USB Debugging mode is turned on but still this showing that my USB Debugging insnt active.
[Android Software Development] soumyaxoloq900:
Update

Yes, I have able to successfully instal this software and now I can see root access status OK in Android Commander and able to edit root folder/files.
[Android Software Development] artur0588:
On HTC One android 5.0.2 after write command adb remount i received device offline.

I try put directly in boot.img and run with app, both way got device offline.
[Android Software Development] Hybris95:
Thanks for letting my scripts stay human-readable :D
[Android Software Development] conorconor:
same as here

I do the same as urs. It works on kitkat. But do now work on my Nexus 7 2013 5.1.0. The new adb do not work on 5.0 by replacing the adbd binary in the stock boot.img/ramdisk/sbin directory。 There must be something need to change (init.rc.etc) IT works perfect by installing it and run it. I could get root access by adb shell easilly!
[Android Software Development] conorconor:
Sorry Chainfire. Could u give us a tip that inject compiled adbd into 5.0 boot.img.? so that we could run adb shell as root whithout typing su.
[Android Software Development] zFr3eak:
Having troubles with devices is offline on android 5.0.2 ! Anyone can help ?
[Android Software Development] conorconor:
Yeah, I have the same issue
[Android Software Development] jbfountain:
Hello I have an HTC One M9 running stock Android 5.0.2 on stock T-Mobile firmware. It is rooted with S-OFF. I never had this problem with my M8, but when I enable adbd Insecure I lose connection with my computer running Windows 8.1. Even Though I have usb debugging enabled adbd Insecure reports that it is disabled. When I turn off adbd Insecure I regain connection through adb, and adbd Insecure reports usb debugging enabled. Any thoughts?
[Android Software Development] channeledbymodem:
LG G2 D801 (TMO), rooted, modified stock: "Even Though I have usb debugging enabled adbd Insecure reports that it is disabled. When I turn off adbd Insecure I regain connection through adb, and adbd Insecure reports usb debugging enabled."

I need ADB Insecure to work in order to run Android Commander on my pc. Thanks.

Never mind: working now for some reason.
[Android Software Development] WarlockW:
adbd Insecure - Not working with T-Mobile S6 ?

I have a S6 Now .. Stock Kernel - Rooted with pingpongroot_beta5.1

I never had this problem with my S4 Worked Great !

I could use Android Commander no problems.

But when I enable adbd Insecure I lose connection with my computer!

Even Though I have usb debugging enabled ..

The computer does not install the ADB Driver.

When I turn off adbd Insecure I regain connection through adb!

However : Android Commander Does not work !

Shows this with ADB Insecure Enabled ..

persist.security.ams.enforcing=1

ro.secure=1

ro.allow.mock.location=0

ro.debuggable=0

ro.adb.secure=1

persist.sys.usb.config=mtp

ro.zygote=zygote64_32

dalvik.vm.dex2oat-Xms=64m

dalvik.vm.dex2oat-Xmx=512m

dalvik.vm.image-dex2oat-Xms=64m

dalvik.vm.image-dex2oat-Xmx=64m

ro.dalvik.vm.native.bridge=0

Suggestions ?????
[Android Software Development] xda23:
What does this mod do exactly?
[Android Software Development] hometech99:
An way to insecure from recovery or download mode?

My system is wiped and twrp backup is gone.

I DO have EPS Pro backup of everything but userdata.

Every way I try to flash the system image from my backup in download mode (odin, etc) , i get a message on the phone about failure and something about security.

I found this in an adb tutorial:

"- Also to be able to do adb push to /system partition for parted binary, you will need insecure boot.img used in your ROM or adbd insecure installed in your device (Check this thread for that app).."

SInce I cant boot into OS and run this app, is there a way to insecure the boot image outside of running an app in the OS?

(I CAN get into TWRP and I CAN get into download mode.)

Thanks