No, that command does actually work, prefixed with "su". In fact, all of the things mentioned are still possible with su, inside adb shell, even without adbd insecure, on one of the devices this program is made for.

The thing is, say you want to pull something from a location thats "protected", you'd first have to shell into the device, "su", move it to a location accessable to adbd, logout of the shell, then adb pull. Push ? Same thing, other way around.

Same thing goes for a large number of commands, you can skip the entire "su" part needed on some devices.

Everything this enables is still possible on every rooted device, it just saves you quite a bit of typing (and hairpulling) for those who do not have adb running as root. If you use adb as much as I do, this is absolutely something you want.

On the other hand, if you're the occasional adb user only, you may not know what to do with this - and then this is not for you

Originally Posted by Chainfire

Everything this enables is still possible on every rooted device, it just saves you quite a bit of typing (and hairpulling) for those who do not have adb running as root.

And saving all that typing is why many of us will be buying Chainfire a beer through the Play Store.

Sent from my Galaxy Nexus using Tapatalk 2

I used this app on my galaxy y gt S5360 running stock kernel with secure adb. But when i patch for insecure adb my computer doesn't recognize my device. I have already tried everything you mentioned. My computer recognises my device after unpatching. If you can plzz provide the solution for it.

Sent from my GT-S5360 using XDA

I just installed it on Galaxy SCH i509 which is already rooted but the boot.img is untouched (I'm using stock ROM).

When I clicked on Enable insecure adbd, the USB debugging status (on insecure adbd panel) was automatically disabled, but when I go to system's Setting>Application>Development>USB debugging remain checked. I toggled it off and back on with no effect.

How to correct this?

it make

---

some problem with some program

i notice it when i try to take screenshot by qtadb

if i enable it i can't take any screenshot by qtadb

also i can't use desktop notifier(usb) and qtadb at same time (when i try run qtadb desktop notifier is disconnected by it if this is enabled)

i use qtadb 0.8.1 on windows7 64bit ultimate (sony z138)

great app but i am just wondering how long it takes to finish the adbd patching? any idea anybody?

Is there a version of adbd Insecure that does not break adb install ?
On JB on SGS3 I have to unpatch adbd before I can use Eclipse to install and debug my apks.... else I get a permission denied when adb tries to install my package..

Here's how to get this working with Jelly Bean:

* Take the APK from the first post and open it in WinRar/7-Zip
* gunzip http://forum.xda-developers.com/show...&postcount=767 and replace assets/adbd.png with that binary
* Delete the META-INF folder
* testsign the new APK and install that

New version is out with Jelly Bean related fixes!

Nice app works well... I've been resetting the line in local.prop file then rebooting. Ever since I rooted, I have been looking for a way to just restart adbd into root mode without rebooting the phone. Could you explain to a noob what this app does to achieve this?