[2014.11.10][ROOT] adbd Insecure v2.00
- Thread starter Chainfire
- Start date
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"
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.
[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.
edit it in default.prop not build.prop after unpack stock boot.img, then reflash boot.img
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.
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
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
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
438adbd Insecure lets you run adbd in root mode if your device is rooted.
(Note that if you are running a custom kernel, it is likely that it already implements this functionality)
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.
Of course, your device must already be rooted for this to work. It may not work with "S-ON" devices and locked bootloaders.
This app does not make any permanent changes to your device - a reboot will undo any modification. That's why there is also the option to enable this feature at boot.
Note that if you have USB connected when the app activates or deactivates adbd root mode, you may need to unplug/replug the cable or run "adb kill-server" on your computer before adb will work again.
Download
Download from Google Play
The Google Play download is not free - it costs about a beer (thanks!). The download listed below is 100% the exact same program, but free. Please consider supporting my work
REDISTRIBUTION IS NOT ALLOWED
(no posting on other sites, no cooking into your ROMs, etc)
(The download is free for now, but I reserve the right to pull it at any time)
( 1.0: 3616; 1.1: 3527; 1.2: 8582; 1.30: 35699 )10No, 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 you7
No, it *allows* you to run 'adb remount' on rooted devices that do not allow it (which is quite a few).
New posts
-
Features disabled on fastboot and bootloader. How do I enable them?- Latest: mayberandomparable
-
-
