yashsingh1/xdaforums huggingface dataset:
[Android Software Development] partcyborg:
It's unfortunately not working for me :(

I installed (bought and paid for! :) ) The app and installed it.

First, when I enable it it does some work for a while and ends up with "Failed to patch adbd!" Each time. I did some digging by enabling full logging with SuperSU and found that problem: my device (s8 G950U snapdragon system root from sampwnd) does not have a fstab so the remount rootfs rw command you use does not work. It also may be the fact that I see two backslashes in the command, I don't trust SuperSU logging enough to be sure :)

Anyway, I REALLY want this to work so I recreated what the series of commands that fail due to not making rootfs rw by hand, which according to my reading of the logs entail:

- stop adbd

- remount rootfs rw

- cat /sbin/adbd to /sbin/adbd.original

- cat /data/data/<app name>/files/adbd.21.png to /sbin/adbd

- chmod a-x /sbin/adbd.original

- chown root:root /sbin/adbd

- chmod a+x /sbin/adbd

- start adbd

So I ran all of these successfully, except I use cp instead of cat, why did you use cat with output redir? :) And when I restart adb a few things happen (or don't happen):

- adbd starts and stays up

- after several unplugs/replugs, "adb kill-server"s, and even a reboot of my computer my device no longer shows up

- the new patched adbd spams immense log messages to my system log (what you see in logcat) that look very similar to what the stock one writes but looks like it's getting stuck in a loop? I will upload the logs somewhere because even one line is way too big to paste here.

Sampwnd root leaves selinux off and confirmed getenforce returns 0.

My only suspicion about what's up is that my system is arm64 and the binary is arm32. This is supposed to work fine but who knows? It does run so that shouldn't be an issue (iirc wrong atch binaries usually fail with "no such file or directory" or something equally vague) and that does not happen in this case.

Is there any way I can help? I have a 100% working cross compile environment working right now (I've built things like kexec there statically trying to work on installing a new kernel with locked bootloader :) ) so if you are building this from source and would be willing to share the patch I would happily do so (and not share your trick because I don't want it patched!) Or if you have some other method I will happily test however and whenever you want.

My other thought is 7.0 Android or the latest version I am running on my laptop is not compatible with the version being installed by the tool? I see that your latest update msg on play store says Android 5.0 support and was in 2014) so maybe? But others running nougat have gotten it working so who knows?

Please let me know how I can help :)

Attached is now a screenshot of what the app runs as root

PS: flashfire and SuperSU changed my mobile life I love your work!!
[Android Software Development] partcyborg:
Edit: it's not the console spam adbd isn't doing that, red herring. It is running and not working though.

Does it matter if adbd runs with a sec_label flag?

What about on a socket as defined in init?
[Android Software Development] vega509:
not working here either, nougat 7.1.1, I tried kernel auditor mod, still a no go.

anyone have another working solution?

moto z play stock nougat 7.1.1, rooted

thanks
[Android Software Development] leroy1:
I rebuilt apk using apktool

changed one line from "mount -o rw,remount / /" to "mount -o rw,remount /" in a.smali

and it works on android 7.1

uploadfiles.io/7l42p
[Android Software Development] devastatorx:
This worked for me on 7.1.2. Thanks!
[Android Software Development] partcyborg:
Thank you for figuring out this part and sharing!

Unfortunately for me while I can now enable insecure adb successfully, nothing shows up in my adb devices list.

S8 with stock deodexed 7.0

Can you tell me what adb version on your computer you are using and what os?
[Android Software Development] mr_unpredictable:
WTF FTW!

This worked! :D

Thanks a lot btw for ur workaround on this one. :)

But there is a problem, i can't backup my droid based on 7.1.2 via MtkDroidTools.

It does show that it has root shell, but still backup option won't backup system and userdata [absolutely pointless of backup without system partition, never mind of the userdata]

And last but obviously the least, :p the NVRAM/IMEI backup option is also blocked.

Have a look at the SS below.

Throw some light, torch, candle, headlight, lantern on this. :D

Thanks in regards. ;)

[IMG="SS"]https://scontent.fmaa1-2.fna.fbcdn.net/v/t1.0-9/fr/cp0/e15/q65/24129732_214897689051632_3455425436176289139_n.jpg?efg=eyJpIjoiYiJ9&oh=b7924c6913bfb9013a29831c31166df1&oe=5A991ACC[/IMG]
[Android Software Development] partcyborg:
Don't use whatever this is if it needs adb.... Use online nandroid or flashfire
[Android Software Development] mr_unpredictable:
Neither of them which you have mentioned are better than the Legendary MtkDroidTools. :p
[Android Software Development] partcyborg:
They actually work on your device lol
[Android Software Development] mr_unpredictable:
Did I ever mention about their compatibility on my device or even say a thing about it!?

Read and make out by the reply fully, before you LoL! :p

ROFL!
[Android Software Development] partcyborg:
No, you used the word "better" which is about as vague and open to interpretation as words get.

ROFLMAO!
[Android Software Development] mr_unpredictable:
Better = Comparison

Do you even know what's the difference between Comparison and Compatibility!

AH

Came to teach me!

Lol!

Just justify your sentence perfectly, rather than being a PH!

BIATCH! XD
[Android Software Development] partcyborg:
Apparently someone needs to teach you English lol
[Android Software Development] mr_unpredictable:
FYM

LOLz!

Why, got pissed off?? XD

Turning the tables! :v

Make a correction, you r the one who's in need of it!
[Android Software Development] Raymond Ebertt:
Doesn't seem to be working for me with HTC 10. I moment I attempt to patch, I loose USB debugging enabled. I need the debugging enabled to do anything. This is a frustrating moment. I had it working only a few months ago but now, nothing.
[Android Software Development] ermakovermakov7878:
Thank you! It works I have an Android 7.0 Samsung Galaxy A7 (2017):D
[Android Software Development] toscanelli:
Can you reupload it please?
[Android Software Development] leroy1:
Sure

https://nofile.io/f/86605d8qsJs/adbd-Insecure-v2.00.apk
[Android Software Development] KumoKairo:
Thanks for the updated APK. However, I dub the "no USB Debugging" question. There is a lot of questions like this everywhere (here in this thread, on stackoverflow etc.) but no answers. Does someone know how to enable both things (both adbd insecure and USB debugging)? I need adbd insecure just for that.

Thanks

--- UPDATE

Okay I have fiddled with it for a bit and it's kinda "merged" approach to solve this using different advises from everywhere. The key is to take @ Bigbossnake89's way of "setenforce 0", but it's not that simple.

So first we go and do that -

Then go to insecure adbd and enable it. It will disable USB Debugging. Go to Settings->Developer and untick-tick the "USB Debugging" option - it will say that it's enabled even when it's clearly not. It won't work yet. Go to insecure adbd again and disable it. Go to settings and disable-enable USB Debugging again. This time it will work as insecure adbd is disabled. Then go to insecure adbd again and enable it. This time it will be enabled and USB Debugging will remain active too.
[Android Software Development] shellshocker:
Well it's pretty easy to get USB Debugging and adbd (root mode) working.

1. Install Magisk

2. Install Module Magisk SELinux Manager

2.1 During Installation set SELinux mode to »Permissive«

3. Install adbd Insecure

3.1 Check "Enable insecure adbd"

3.2 Check Enable at boot

4. Enable USB Debbuging under Developer options

5. Reboot

6. Enjoy!
[Android Software Development] rootlessabroad:
I tried what was mentioned above. I updated to Magisk 16 to be able to load the SELinux mode manager. Set it to permissive. Uninstalled and re-installed adbd insecure. Checked the boxes enable and enable at boot. Rebooted. Verified that the USB debugging was enabled. (tried disabling and re-enabling USB debugging.) It still isn't working for me.

I tried the Chainfire apk and the re-compiled apk. Same result with both of them.

This is all on a OnePlus 5T stock, rooted, 8.0, build 43_180223.
[Android Software Development] donnyhie:
Verizon Pixel - not working

Also, wanted to add that it's not fully working on Pixel (Verizon) - Andoid 8.0.0. It's unlocked and rooted.

It would show in current status:

Binary: Original

USB debugging: Enabled.

Once I've enabled insecure adbd, the status would show:

Binary: Insecure

USB debugging: Disabled

I've gone into Developer options > USB Debugging - enabled.

Is there a step I'm missing?

Thank you for your time.
[Android Software Development] DE SEXIEST:
Does it work on rooted Nougat mtk based device?
[Android Software Development] harischeong:
working on my android 7.1 device.

steps to get it working:

1. download the version by leroy at https://nofile.io/f/86605d8qsJs/adbd-Insecure-v2.00.apk

2. install in your phone.

3. run adb shell in your adb directory

4. type "su" so u can get the "#"

5. type "setenforce 0"

6. enable insecure adbd. usb debugging turns off

7. turn usb debugging on and off from developer options

8. turn insecure adbd off and on again.

Hope this helps

Haris
[Android Software Development] DE SEXIEST:
Thanks

Will provide you with feedback after trying
[Android Software Development] xdayman:
Extract google authenticator credentials

I have a rooted Moto x4 with lineageOS 15.1 on it and I'm trying to manually extract my google authenticator keys but I'm getting a permission denied error. The binary is in the Insecure state and USB debugging is on and the error is returned when I run the pull command.

adb pull /data/data/com.google.android.apps.authenticator2/databases/databases
[Android Software Development] MaikolReyes:
Tengo Sony Xperia z1 compact D5503 tengo Kingroot pero al poner este comando. Su

Mount -o rw,remount /system

Me sale; operación no permitida

Como debo hacer?
[Android Software Development] bacon612:
Anyone having luck with this anymore? I'm trying to get access to be able to push files to my rooted LGV35 running Android 8.0
[Android Software Development] yelayye44:
root
[Android Software Development] surya2495:
adbd Insecure - error | Could not patch adbd!

Hi Chainfire,,

I Have installed "adbd insecure.apk" on my device. then i opened the application and checklist the "Enable insecure adbd" then the app show notification like that "adbd insecure - error | Could not patch adbd" . could you please show me the way to fix this problem for me?
[Android Software Development] RootedLee:
link to adbd Insecure re-compiled apk, please?

here's the link to the re-compiled apk (thanks, leroy1) -> https://xdaforums.com/showpost.php?p=75587044&postcount=250
[Android Software Development] RootedLee:
Two questions:

1) How do I make adbd insecure stick even after reboot? Even with Magisk SELinux Manager latest v1.0.5 installed and activated via Magisk (latest), it does not stay persistent during reboot here even with the ckeckmark "Enable at boot" checked. I tried both apks, orignal Chainfire and re-compiled by leroy1.

I have also added ro.debuggable=1 and ro.secure=0 to /system/build.prop, too, as per suggestions here.

2) Inside 'adbd-Insecure-v2.00/assets' I only see adbd up to API/SDK 21 (oddly with file extension .png, but this must mean something different here, not a image format), but I am running Nougat 7.1.1 = API/ SDK 25. Maybe that's why the setting does not stick?

Is there a pre-compiled insecure adbd for API/ SDK 25?

My system specs see in my signature below.
[Android Software Development] RootedLee:
[MENTION=8755711]leroy1[/MENTION] or anybody else have *any* idea how to mod the adbd Insecure app to include a newer version of a root-enabled adbd? The most recent in the app (sdk/ api 21) is from Android 5.0/ 2014..

I overwrote the sdk 21 adbd inside adb Insecure.app with the one from TWRP 3.2.1 (v.10.0.39) which DOES give me adb root when booted into TWRP, but even though adb insecure *applies* the updated adb (which I see when I run a version check via adb because it *does* change from my ROM's native adbd v.10.0.36 to v.10.0.39 = the one from my mod), but NO adb root ..

This applies to both apks I modified, original Chainfire and leroy1's mod.

As soon as I revert back to either the original app or leroy1's mod, adb insecure *does* give me adb root again, but it is so old that adb can't even retrieve the version number, and some functions are - well, funky.

Any ideas etc. are *highly* appreciated (bummer that Chainfire did not pass his knowledge along).
[Android Software Development] apapedulimu:
Hello, I after download adbd Insecure from google apps. and when I try to enabled the adbd Insecure, the usb debugging is set to disabled, and after I go to Developer to toggle of and turn back on, the status of usb debugging is still disabled. Any idea?. Thanks
[Android Software Development] martyfender:
I had the same issue and installing Selinux Switch and setting it to permissive solved it for me.

https://xdaforums.com/android/apps-games/app-selinux-switch-t3656502

See my post near the end of that thread, on how I prevented Google Play Protect from disabling it on boot.
[Android Software Development] Rannek222:
Thanks

Worked perfectly thank you! Is the app still paying for you? Because then i will buy it. :D
[Android Software Development] hashstudioz:
Nicely explained and query sorted

It helps to sort out the query with the Selinux Switch installation. Thanks for the heads up.
[Android Software Development] wqhjstudios:
thank you

your contribution is very much appreciated. i can't wait to try it out. i hope these crazy times are treating you well, Dr. Chainfire. good day.
[Android Software Development] jwilcox25:
Unfortunately the link is dead. Is it possible to re-upload this? Would be greatly appreciated!
[Android Software Development] RootedLee:
@jwilcox25 sure, here you go - attached :)
[Android Software Development] chunkitlau:
Unfortunately I can't open th link too. Could you please give me a copy of the re-compiled apk. Thanks a lot.
[Android Software Development] RootedLee:
@chunkitlau

https://xdaforums.com/attachments/a...lt-apk-for-android-7-1-by-leroy1-zip.5225627/
[Android Software Development] chunkitlau:
Thanks a lot
[Android Software Development] mpgioia:
Does this work in Android 8.0 ?

I can't get it to patch.. It reports back "Could not patch adbd !" Definitely have root...
[Android Software Development] B4rabbas:
still get "adbd cannot run as root in production builds" :/
[Android Software Development] RootedLee:
Is there a adb insecure for Android 11 (LineageOS 18.1)?
[Android Software Development] wenyendev:
Try, first, enabling “adbd insecure” in “Superuser” in Magisk, provided that your device is rooted.

Then go back to abdb insecure.apk to check the box "Enable insecure adbd".
[Android Software Development] wenyendev:
Hi, after checking two following boxes in abdb insecure,

- Enabling insecure abdb;

- Enable as boot,

in abd, after

adb shell.

it returns

adb: no devices/emulators found.

Any one knows how to solve it?

Thanks.
[Android Software Development] lolvatveo:
install driver
[Android Software Development] Marzycielx:
unfortunately it doesn't work on Doogee S88 Plus, i run the application i check both option but when i try to run "adb root" i get response "adbd cannot run as root in production builds"
[Android Software Development] 007.4:
Does not work for me in Android 12 on rooted Ulefone Note 14.

"Could not patch adbd" even with superuser rights granted.

Is there another way to get around the "adbd cannot run as root in production builds" issue (rooted stock rom)
[Android Software Development] Lubo99:
guys as chainfire and magisk modules dont work anymore on android version 12+ what if i change this prop setting

[ro.adb.secure]: [1] to 0 . I dont think this can cause bootloop since it does not mean boot image is unprotected but rather ADB setting is "unprotected" I will welcome any ideas but mostly someone who can confirm this.
[Android Software Development] lolvatveo:
edit it in default.prop not build.prop after unpack stock boot.img, then reflash boot.img
[Android Software Development] Lubo99:
so unpack boot.img and there is default.prop ? and then pack back and flash?

thing is that boot.img i have is patched with magisk and I have system32 tool(to be able to set all partition to RWmode) I dont know if this affects boot.img and I dont want to lose this.
[Android Software Development] lolvatveo:
it just packages and unpacks your boot.img
[Android Software Development] 57ar7up:
Shame it doesn't work in TCP/IP mode.

Eh.....
[Android Software Development] theteeth07:
hi

i'm trying to use a modified adbd like adbd_21.png from eu.chainfire. Just wondering if there is a later version that's better to try Android 10, wireless adb, temporary su so can edit default.prop but my adbd daemon seems protected. I heard there is an adbd_25.png for adb insecure but can't seem to find it.

thanks in advance

steve
[Android Software Development] essence25:
Here is what I have discovered:

Any manipulation of the ro.debuggable= set to "1" on A14 will allow adb as root but will crash the Developer Console menu in settings. To avoid that set SELinux to permissive. The developer menu will show but while it is open the CPU usage will increase dramatically. Maybe someone can figure why this occurs.

I use a "ADB Root Enabler" magisk module in KernelSU in conjunction with SelinuxModeChange toggle app to do what I need in ADB as root, then I disable both when I'm done.

Lastly will there be support for A14 in adbd insecure?
[Android Software Development] Chainfire:
adbd starts running as root ... but then it drops to lower level privileges. This app contains a patched adbd that stays at root level instead (ignoring ro.secure). The app stops adbd, replaces the kernel's adbd copy with the patched copy, then restarts adbd ...
[Android Software Development] xd.bx:
Great program! I'm having a very small issue though, adbd-insecure fails to properly restart adbd (however it is indeed patched, because if I restart manually in settings -> enable usb development then the new adbd drops a root shell). Possible the vendor, in this case ZTE, did something that interferes with adbd-insecure restarting adbd.
[Android Software Development] qkster:
Thank you.

Will have to try this at some point.

I'm using the SGH-i997 Samsung Infuse.

We have an official kernel source for GB. There is some battery drain associated with wifi from older kernels 2.3.3 - our hope is the new kernel fixes this.

The official source is supposedly 2.3.6.

The official firmware 2.3.6 UCLB3 can be rooted using an older insecure kernel and loading in busybox, su and superuser.apk.

Then a re-flash with the official kernel and retaining root.

However, when the firmware is run with the compiled kernel, an occasional touch screen of death happens. When this happens, the screen is off and touch and buttons do not work. Connect to adb works but root access and command results in a "root access denied".

Will see if this will solve it. The problem is, the sod in currently unpredictable and hard to replicate.
[Android Software Development] rishabh22:
I have the same problem in my lg optimus one with cm10 (4.1.2)

Anyway to fix it?
[Android Software Development] mikevillarroel:
This app just fixed my issue with Android Commander. Thanks!

I just saw your post on G+ about the Superuser update but I didn't got it even though I'm on the elite(bought it to support your development) do i need to do anything? Superuser v3.1.4 (47)

Did I pay for a wrong one? lol
[Android Software Development] Chainfire:
I make SuperSU (Pro), not Superuser (Elite) :)
[Android Software Development] mikevillarroel:
ok, my bad will buy it anyways to support developers like you, thanks!

---------- Post added at 08:25 AM ---------- Previous post was at 08:23 AM ----------

I got confused between ChainsDD and Chainfire,

sorry,

https://play.google.com/store/apps/developer?id=Chainfire
[Android Software Development] shoutokuyaki:
I can't use adbd after patch...

Even i reboot my device...i cant use adb root or remount :(:(
[Android Software Development] gunigugu:
Anyone know if this still works in 4.2?

When I enable it on my Nexus 10 it kills the ADB server it seems on the device...
[Android Software Development] Chainfire:
I will look at this.
[Android Software Development] Chainfire:
Updated to v1.20, fixes problems with Android 4.2 (like Nexus 10)
[Android Software Development] gunigugu:
Awesome work!! Now I can finally do backups / restores over ADB again :)
[Android Software Development] magikstar:
works great on my u-boot device Alcatel OT-986,thanks
[Android Software Development] Goatshocker:
Oh, nice app. Works well too. Is it ok if I add a link to this thread on my Quick ADP Pusher thread?

Its a nice way for people on rooted stock roms to get full access to the system :)

Edit: Actually Im just gonna go ahead and do that. Throw me a PM if you, for some reason, dont want it and I'll remove it.
[Android Software Development] dfkt_:
Tried this on a Cowon D3 (running on Android 2.3.3), and it messed up both Superuser and USB debugging, making them non-functional. Simply uninstalling ADBD Insecure luckily fixed that, no lasting damage done.
[Android Software Development] ikjadoon:
Someone want to educate a noob? :D

1) What sort of adbd runs in recovery (I use TWRP)? From there, I can always push into /system no issue. If my phone is on, though, I can never push files into /system. It spats "permission denied," (

even after

adb shell -> su -> mount -o remount,rw /system!).

If I run adbd insecure, of course, I can push into /system when Android is running.

2) When Chainfire says "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."

I've read a dozen guides about adb, nobody moves things: everyone pulls straight from /system. And maybe that relates to question: because I don't do that, is that why I can't push into system while Android is running even after remounting through adb shell -> su? And what are locations accessible to adbd?
[Android Software Development] efrant:
When your phone is booted into Android, the system is mounted as read-only. So you should be able to do an "adb pull" of files in /system (I think CF made a mistake there), but not an "adb push". You will not be able to do an "adb push" even if you open a shell and type your mounting command -- in this case /system would be mounted r/w for the shell user only. You would need to push the file you want to your device in an accessible location (say, /sdcard), then open a shell, type your mounting command, then copy/move the file from /sdcard to /system.

When booted in Android, in order for you to be able to use "adb push" to write directly to /system is by having ro.secure set to 0 via booting an insecure boot image (and then using the "adb remount" to mount it as r/w), or by having this app running (and then using "adb remount"). CWM and TWRP both have this set by default, so that is why you can do it when those are booted.
[Android Software Development] ikjadoon:
Ohhh..thank you hugely! I'm out of thanks, but I'll get ya tomorrow, :D

/system, after adb shell mount, is

only

mounted for the shell user: that seems like a crucial bit of this whole story, haha. :D And CWM/TWRP set ro.secure to 0 = whew, all right, then! :D

Thank you kindly; this post is forever bookmarked.