I am trying to use the ADBD Insecure app to enable adb root access by default. I have already flashed my Nexus to BETA-SuperSU 2.67, and that has worked and allowed me to use su in adb. However, I need to have adb root functionality by default, which is where your ADBD Insecure app has saved me many times.
For my Nexus 6P though, which is running Android M (6.0.1), I'm unable to use the app. Every time I enable insecure adbd, my computer no longer recognizes that there is a device plugged in (it disappears from the Devices and Printers window). Also, although Android OS is still showing that USB debugging is enabled, the app shows that it is disabled.
I've seen this issue a few places on the internet, but have come across no solutions. Does ADBD Insecure not work on Android M, or is there something I am missing?
As a side note, I have a Nexus 5, which was rooted with the same BETE-SuperSU, and the app works fine on there.
Thanks for the help.
Here's a screenshot showing the inconsistency between the app and Android.
i.imgur.com/6p2ZRxa.png
meesa said:
I am trying to use the ADBD Insecure app to enable adb root access by default. I have already flashed my Nexus to BETA-SuperSU 2.67, and that has worked and allowed me to use su in adb. However, I need to have adb root functionality by default, which is where your ADBD Insecure app has saved me many times.
For my Nexus 6P though, which is running Android M (6.0.1), I'm unable to use the app. Every time I enable insecure adbd, my computer no longer recognizes that there is a device plugged in (it disappears from the Devices and Printers window). Also, although Android OS is still showing that USB debugging is enabled, the app shows that it is disabled.
I've seen this issue a few places on the internet, but have come across no solutions. Does ADBD Insecure not work on Android M, or is there something I am missing?
As a side note, I have a Nexus 5, which was rooted with the same BETE-SuperSU, and the app works fine on there.
Thanks for the help.
Click to expand...
Click to collapse
I'm having the same issue on a HTC One M9 stock Marshmallow rooted with beta SuperSU 2.65. As soon as I enable ADB Insecure it reports USB Debugging not active and my computer no longer sees my phone. When I go to developer options USB Debugging is still checked @Chainfire any ideas?
Edit: After settling SELinux to permissive the computer now sees the phone. Going to ADB Insecure it still reports USB debugging not enabled, but after un-checking enable ADB insecure going to developer options and uncheck then RE-check USB debugging I can go back to ADB insecure it shows debugging enabled. I can then enable ADB insecure and all is good.
Using XDA to unleash the power of Android on my HTC One M9 and S6 Edge Plus
but after un-checking enable ADB insecure
Click to expand...
Click to collapse
Yes, ADB still works if ADB Insecure is not in use, but I need adb root functionality.
meesa said:
Yes, ADB still works if ADB Insecure is not in use, but I need adb root functionality.
Click to expand...
Click to collapse
I have root function after going back to ADB Insecure and re-enabling it.
Using XDA to unleash the power of Android
If anyone's post or work has helped you please, use the thanks button
Unfortunately that has not been what has happened for me. Re-enabling it just breaks it again.
Same issue using a Nexus 9 LTE, running Android 6.0.1.
@Chainfire , any idea what's going on with this? Did Android break your app?
Figured out the issue! I was using ElementX 4.06, which is the latest version. I noticed that one of my other devices had version 3.0 on it, so I downgraded and now ADBD Insecure is working as expected.
im also having this issue and i am not using element. my phone is complete stock except im using TWRP. any idea's as to why its not working?
---------- Post added at 11:00 AM ---------- Previous post was at 10:56 AM ----------
after looking i see this app hasn't been updated for two years. im gussing theres some system in place on android 6 thats blocking this.
Related
I'm following instructions given by karnovaran "How to root the Droid 2"
I have a Droid 2 running 2.2 OS, latest SDK, latest Moto drivers. I'm new to Droid 2 but not to windows or linux. After running the instructions rageagainstthecage, waiting to be kicked out, and then issuing "adb kill-server". The following command "adb devices" lists my device as "offline" and not surprising "adb shell" give me the "error: device offline".
The similar threads didn't seem to help. Does anyone have an idea?
Just use z4root. It's no longer on the market but you can download it from its official thread. The Droid 2 works beautifully with it.
Thank You for the quick reply. I will take a look and see if a z4root is a better route to take. I will also watch for other replies. I am as curious as to way rageagainstthecage is not working as I am to complete the rooting process. Has Verison block this application? I'm even more curoius to know why providing something as simple as superuser to a linux OS is so shrouded in voodoo. It may just be something simple I missed but the device goes offline on the phone side and I can not reconnect until it is rebooted.
Well, rageagainstthecage is an exploit that tricks the adb daemon on the phone into running as root instead of setuid'ing to a non-root user. Once that's accomplished you can do pretty much anything through adb such as installing system level packages and changing some system configuration files. Basically all the existing root methods for the Droid 2 use rageagainstthecage to obtain root and then fix the system to allow any user to su to root.
Verizon can't block the exploit because the bug is in the adb daemon which a vendor really shouldn't touch. As for why it might not be working on your phone, rageagainstthecage really relies on what is called a race condition. The exploit has to kill the adb daemon and fork off another process before the adb daemon is restarted. Sometimes it fails to do so.
Really z4root has made most previous methods obsolete. It does the hard work for you.
Thank you for that very fine explaination. I guess I will proceed to z4root now.
Just a last followup.
Z4root worked prefect! I'm rooted, got the SDK connected to Netbeans and the latest moto drivers. Let the games begin.
Thank you again Spitemare
Hi there, I got a similar problem. I downloaded z4root as well but the thing simply quits halfway. No error message appears and the device remains unrooted. What else can I do?
elsenoire said:
Hi there, I got a similar problem. I downloaded z4root as well but the thing simply quits halfway. No error message appears and the device remains unrooted. What else can I do?
Click to expand...
Click to collapse
Try this
Reboot your device then try running the app again ....
It would quit half way on me too but a fresh reboot did the trick
Sent from my DROID2 using XDA Premium App
I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.
Dynesh said:
I rooted using Mskip's rootkit. I updated with the OTA update thinking I could use the kit to root again. I'm on the latest version of the toolkit after donating and updating it. I go to option 4(root options) then I choose option 1(root). I do this while in fastboot mode. The Nexus 10 reboots, goes to the home screen, and the toolkit says it is "Waiting for Device" Nothing happens. I tried rebooting into fastboot mode again, but nothing. I ran root checker, and it says I do not have root.
Any ideas on what I'm doing wrong.
Click to expand...
Click to collapse
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.
xIC-MACIx said:
First off, do you have "USB Debugging" checked in settings? Sounds like ADB isn't working. (Especially since you were already in fastboot mode, which doesn't require debugging.
See THIS thread.
If you have a custom recovery installed, download the superSU app and Su binaries from Chainfire's thread I just linked and flash them in recovery.
If you don't have a custom recovery, use the toolkit to either temp flash or fully flash the right recovery onto your tablet.
Also, if I remember correctly, options 3 & 4 in the toolkit's root menu will essentially do this for you.
NOTE: For future OTA updates, download "OTA Rootkeeper" or "SuperSU Pro" from the market. They both have options to protect root during an OTA update. (SuperSU Pro has never failed me when I used it to protect root when I had my Asus TF700.
Click to expand...
Click to collapse
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!
Well, I tried to run that program from the link, and it said some files were missing, so I stopped it. I tried to flash clockwork mod recovery and when it booted back into Android to rename the files, it got stuck on waiting on ADB. Frustrating.
Dynesh said:
Thanks for the answer. I'm not a total newb to rooting things, but defintely not a pro, so some of this goes beyond what I've done before. I'll have to approach slowly. I don't really need root for anything right now, I only rooted to connect BT controllers to the Nexus, and those apps are broken right now anyway.
I do have usb debugging checked. I'm not sure about the other things you asked. I've never flashed anything to my droid devices, so I'll try and go through that thread and see what makes sense.
Thanks!
Click to expand...
Click to collapse
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)
xIC-MACIx said:
Yeah, it seems more intimidating than it really is. Luckily, all of the things I listed in my above post are all achievable through the Nexus 10 Toolkit that you have downloaded.
I agree though, take it slow and read through the instructions, that is the best way to avoid breaking something. Rooting is a pretty safe procedure these days, my first Android phone was quite the headache.
When you do decide to root again, you can use the toolkit to either:
-- Install root through ADB (no recovery needed) like you already tried. Beforehand, you should check to make sure you correctly installed the correct drivers.You also need to check the toolkit's "List of attached devices" section to see if you see your device (represented by a string of letters & numbers) whenever your device boots back to the homescreen.
--Or temporarily install the necessary recovery to flash a root package, once it is flashed the device will revert to the stock recovery. (When you see "CWM" the toolkit is referring to a custom recovery BTW.)
Click to expand...
Click to collapse
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Glad it's working, Android can be temperamental at times & the issue is typically caused by the small things!
Dynesh said:
Success!
I think the problem coming in for me was not understanding ADB and fastboot. I have the drivers installed, but it wasn't seeing it. I switched to PTP mode and instantly it was being seen in ADB mode by the toolkit. I then ran option 4-->Option 1(Root Device) from fastboot mode. This time when it booted back to the homescreen the toolkit was able to continue with the root and I am now rooted again.
Thanks for taking the time to respond to this and help me out. You mention of the drives is what kind of kicked me in the right direction.
Click to expand...
Click to collapse
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.
kane1513 said:
Which root method did you use? The only one I've looked at requires unlock to root. Ive rooted every phone ive owned and they are super easy, they never do a factory reset/unlock to root. BTW I'm on 4.2.1 and i gave up when the toolkit i used wouldnt connect to fastboot.
Click to expand...
Click to collapse
I rooted using this method.
http://forum.xda-developers.com/showthread.php?t=2001868
I did have to unlock the bootloader so I did lose everything, but it wasn't that hard and I did it early enough that I didn't lose too much of what I had on there.
I've searched and searched but can't find anything that seems to work for my Nexus 7...
I need to just run this one command "fastboot oem off-mode-charge 0" on the 7 that's built into my truck's dashboard. I didn't root it beforehand because I didn't think I would need to. I COULD take it out of the dash to use USB ADB but that would be a huge PITA.
I'm on stock unrooted 4.2.1
-So... Is there an app for temp root so I can use wireless ADB in a terminal/ wifi ADB app?
-Is there an app for built in option (some say there is...?) to do wireless ADB without root?
-Is there an easy way to just root the 7 without USB?
-Can I change off-mode-charge 0 in any other way using just the tablet without root?
-Am I screwed without taking the truck apart and connecting the tablet via USB?
Thanks for any help!
AW: Wireless ADB without root?
You can't root without usb, because you need to unlock your bootloader to root. I guess you have to get it out there to unlock the bootloader and root
Sent from my SK17i running Android 4.1.2
mihahn said:
You can't root without usb, because you need to unlock your bootloader to root. I guess you have to get it out there to unlock the bootloader and root
Sent from my SK17i running Android 4.1.2
Click to expand...
Click to collapse
Dang, lol.
Do they not even make those "temp root" apps I've seen in the market anymore? I should have rooted it earlier... I've rooted every other phone I've had. I just didn't think I'd ever need it. :silly:
Come to think of it... how did those "temp root" apps even work if you need to unlock first?
It is possible to use adb over wifi without root, google play store: adb wireless (no root)
m.dlc said:
It is possible to use adb over wifi without root, google play store: adb wireless (no root)
Click to expand...
Click to collapse
I have tried that and it didn't work.
Hello,
I'm just starting with rooting and installing custom roms.
So I don't have any experience with that.
Today I unlocked my bootloader with the WugFresh Toolkit.
But when I want to root my device I get this message: ''ADB Device not found''
I already tried it with my Galaxy Nexus but I get the same message.
How can I fix this?
TheRicolaa10 said:
Hello,
I'm just starting with rooting and installing custom roms.
So I don't have any experience with that.
Today I unlocked my bootloader with the WugFresh Toolkit.
But when I want to root my device I get this message: ''ADB Device not found''
I already tried it with my Galaxy Nexus but I get the same message.
How can I fix this?
Click to expand...
Click to collapse
Did you go through all the driver steps? Even after the correct drivers were installed, I had to put mine into bootloader mode manually, then root.
I already tried that, with no succes.
I also had to uncheck MTP and install the drivers while in the webcam mode. Then my device would show up in the toolkit as ADB connected but status would be red. At that point is when I put it into bootloader manually. Running Windows XP, btw.
Krulm said:
and install the drivers while in the webcam mode. .
Click to expand...
Click to collapse
I will try to uncheck MTP. But what do you mean by ''In webcam mode''?
Mine gives two options (4.2.1). Media Device(MTP) or Camera(PTP), whereas I am forced to select one or the other. In PTP mode it shows up as a Webcam when connected to Win XP.
I did the rooting process. Bit it looks like it's failed. When I start up SuperSU it said: "No SU binary found".
Can I do this rooting process again?
It should have loaded the su binary. Are you ruining each section of the tool and following the instructions exactly? It's pretty fool proof.
Sent from my DROID RAZR using Tapatalk 4
iresq said:
It should have loaded the su binary. Are you ruining each section of the tool and following the instructions exactly? It's pretty fool proof.
Sent from my DROID RAZR using Tapatalk 4
Click to expand...
Click to collapse
I did it 2 times, I had no errors when I did the rooting process. I don't know where it goes wrong actually.
Is it possible to delete SuperSU?
iresq said:
It should have loaded the su binary. Are you ruining each section of the tool and following the instructions exactly? It's pretty fool proof.
Sent from my DROID RAZR using Tapatalk 4
Click to expand...
Click to collapse
Download http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Use Wugs toolkit to flash to device. Worked for me.
TheRicolaa10 said:
Hello,
I'm just starting with rooting and installing custom roms.
So I don't have any experience with that.
Today I unlocked my bootloader with the WugFresh Toolkit.
But when I want to root my device I get this message: ''ADB Device not found''
I already tried it with my Galaxy Nexus but I get the same message.
How can I fix this?
Click to expand...
Click to collapse
Hey, just turn off mpt connection, turn on USB debugging and ptp connection and viola. Might have to delete any former files from nexus 7 on computer first though. Then just use cmd or command line to confirm adb, type adb devices on the command line and hopefully it should identify your device (it doesn't have to be your actual device name, it can be with random numbers.) Those steps worked for me so it should work for you to, rooting it then takes 10 minutes if I can remember.
Sent from my Nexus 7 using XDA Premium HD app
I did this last night and I had to put mine into ptp. Then adb would recognize it. After I got unlocked before I could root I had to re delete everything and then it recognized it.
Hope that helps.
Sent from my Nexus 7 using xda app-developers app
I found a very small number of posts about how to get ADB to recognize the V20, but no success. I did just install the latest platform tools.
Any suggestions?
Did you activate developer settings with USB debugging
ewingr said:
I found a very small number of posts about how to get ADB to recognize the V20, but no success. I did just install the latest platform tools.
Any suggestions?
Click to expand...
Click to collapse
i see you have decided to root it now LOL! well. first things first. go into developers options and activate debugging. mode. If there is OEM unlock option, also activate that (after all you are going to root, but be aware because it will erase all your data) Also install the proper drivers for your phone on the computer. All these are critical. after that you should be able to detect your device. But just in case, what update of ADB have you downloaded? I used one from the pixel's section on XDA which allowed me to see the prompt box and give permission to my computer to access and make changes to my device.
FijNNY said:
Did you activate developer settings with USB debugging
Click to expand...
Click to collapse
I thought sure I had turned that on, but it was off. But that was before I had done a software update to 10f. Maybe it changed back. Thanks.
jinkerz9430 said:
i see you have decided to root it now LOL! well. first things first. go into developers options and activate debugging. mode. If there is OEM unlock option, also activate that (after all you are going to root, but be aware because it will erase all your data) Also install the proper drivers for your phone on the computer. All these are critical. after that you should be able to detect your device. But just in case, what update of ADB have you downloaded? I used one from the pixel's section on XDA which allowed me to see the prompt box and give permission to my computer to access and make changes to my device.
Click to expand...
Click to collapse
Well, actually, I'm not quite ready to root. But I'll be appreciating your input when it comes time. (I forget...are you on a US996?).
Here's what I am trying to do: I am messing with apps to try to improve battery life while still not rooted. I installed Greenify again, hoping I don't have the same problem you and I discussed over in my Journey thread.
So, I just also installed Forcedoze, which typically 'requires' root. But on first run, it says that if not rooted you can give it the rights to do what it needs to do with the following command:
adb -d shell pm grant com.suyashsrijan.forcedoze android.permission.dump
Click to expand...
Click to collapse
All being on the same line.
Any idea if that's a bad idea?
[edit]
I just found that I can do a similar command for Greenify and have it do an aggressive doze. I think I'll try that. I may pop back into my Journey thread to update what's going on.
ewingr said:
I thought sure I had turned that on, but it was off. But that was before I had done a software update to 10f. Maybe it changed back. Thanks.
Well, actually, I'm not quite ready to root. But I'll be appreciating your input when it comes time. (I forget...are you on a US996?).
Here's what I am trying to do: I am messing with apps to try to improve battery life while still not rooted. I installed Greenify again, hoping I don't have the same problem you and I discussed over in my Journey thread.
So, I just also installed Forcedoze, which typically 'requires' root. But on first run, it says that if not rooted you can give it the rights to do what it needs to do with the following command:
All being on the same line.
Any idea if that's a bad idea?
Click to expand...
Click to collapse
Hmm it wouldnt hurt to try. I mean, without root priviliges there are not changes that can affect the system of the phone internally speaking. So... What adb did you download? I used the one from the pixel because my system wouldnt show me the prompt box asking me whether i want to allow my laptop to make changes to my phone.
I'm getting device unauthorized from ADB. I'm Googling now to find the problem. I am NOT getting stack overflow with it.
[fixed]
Rebooted PC and PHone. When I plugged in a pop-up came up on the phone to authorize debugging mode. That had not happened before. That got it to working.
ewingr said:
I'm getting device unauthorized from ADB. I'm Googling now to find the problem. I am NOT getting stack overflow with it.
[fixed]
Rebooted PC and PHone. When I plugged in a pop-up came up on the phone to authorize debugging mode. That had not happened before. That got it to working.
Click to expand...
Click to collapse
see? hahaha that's what you needed to find. the prompt asking you to authorize. in my case it didnt show it until i used the adb from pixel's forum since it appear that the adb shown on the rooting method's thread is missing a file which wouldnt allow to work properly so, then after i opened the adb , it did ask me for the authorization box