I'm having some problems with adb recently and adb.exe keeps crashing. The strange thing is, something immediately restarts adb.exe. I looked through the services and couldn't find anything Android related.
Does anyone know how adb.exe keeps restarting after the process got killed?
This is on Windows 7.
Is logcat using it? Logcat will auto start adb if it's killed.
So the phone is able to start adb.exe on the PC? That would happen through the driver then?
edit: Nevermind, I forgot I had Eclipse running and the Android Plugin restarts adb whenever it's killed...
Can anyone confirm that it's actually the phone's driver that's retarting adb? I don't think I have logcat running on the phone though.
bur2000 said:
edit: Nevermind, I forgot I had Eclipse running and the Android Plugin restarts adb whenever it's killed...
Can anyone confirm that it's actually the phone's driver that's retarting adb? I don't think I have logcat running on the phone though.
Click to expand...
Click to collapse
The phone driver won't start ADB, it's only used for connecting to the phone in adb.
have you installed droidexplorer or myphonexplorer?
my problem was droidexplorer, after i uninstalled and delete it, adb.exe was killed and dont restart anymore
Droid Explorer kept adb.exe restarting
ignos said:
have you installed droidexplorer or myphonexplorer?
my problem was droidexplorer, after i uninstalled and delete it, adb.exe was killed and dont restart anymore
Click to expand...
Click to collapse
Thanks @bur2000 for posing the question, and thanks @ignos for posting my answer.
I got the same issue. Look if the process doesn't start at boot (with CCleaner for exemple) and loop kill it with a batch, it will finally stop I think.
Related
So I can't get adb to work and I'm about fed up. So here is what I've done. Could someone please tell me if I've gone wrong somewhere or what I'm missing because I'm sure it can't be that difficult.
I have an Atrix 4g that's rooted and running Adeo 0.1.7. Had zero issues doing either of those two things. Also I'm running Vista 64bit.
I've tried this in both normal and as administrator.
When I tried to push a file or list devices I get this. "daemon still not runningerror: Cannot connect to daemon"
When I tried adb shell su. I got permission denied.
I uninstalled sdk and reinstalled and now when I try to push I get "Not found." The other two are still the same problems.
I also added adb to the enviroment variables.
I used VanillaTbone's adb for dummies app. Which installs all the drivers for you automatically. So I don't believe there is an issue there. I've read all the threads I could find, but any issues I've seen have to do with rooting an HTC and the solutions I've seen are ones that I can't do on this phone. So I'm at a loss and my eyes are about to burst into flames from all this reading. Any help would be greatly appreciated!
I had a similar issue and it was fixed when I went into root explored and changed to r/w. Hope your fix is this easy...
Sent from my MB860 using XDA App
VicFerrari said:
So I can't get adb to work and I'm about fed up. So here is what I've done. Could someone please tell me if I've gone wrong somewhere or what I'm missing because I'm sure it can't be that difficult.
I have an Atrix 4g that's rooted and running Adeo 0.1.7. Had zero issues doing either of those two things. Also I'm running Vista 64bit.
I've tried this in both normal and as administrator.
When I tried to push a file or list devices I get this. "daemon still not runningerror: Cannot connect to daemon"
When I tried adb shell su. I got permission denied.
I uninstalled sdk and reinstalled and now when I try to push I get "Not found." The other two are still the same problems.
I also added adb to the enviroment variables.
I used VanillaTbone's adb for dummies app. Which installs all the drivers for you automatically. So I don't believe there is an issue there. I've read all the threads I could find, but any issues I've seen have to do with rooting an HTC and the solutions I've seen are ones that I can't do on this phone. So I'm at a loss and my eyes are about to burst into flames from all this reading. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Are you using Mac, Windows or Linux?
Sebring5 said:
Are you using Mac, Windows or Linux?
Click to expand...
Click to collapse
Windows vista 64
Hello,
Been trying to get droid explorer and adb to reconize my tilt2. Here is run down of what i have done.
on an up to date windows xp box
installed latest pdanet for android
installed latest droid explorer
connected my tilt2, it installed the adb driver but wont install the 2 cdc asm drivers
run droid explorer and it doesn't reconize the phone. i have the phone in debug mode and notification does come up.
on the android side i am running
frx 5
wistilt2 test kernel
highlandsun ril driver
btw, tried to run the busybox installer and it says it cant gain root access.. i thought all these builds have it by default or am i missing a step or two. I have superuser installed.
portreeve
All you need is the XDA device to install. The other two, CDC etc are not needed.
Is the adb service running? See if adb.exe is in task manager. You only need pda.net for the drivers, the software will mess with adb itself. So make sure their software is not running.
What do you mean busybox installer? For Titanium Backup or...?
You don't need SuperUser, that is an app that is more for security - if something asks for SU, it'll let you allow it thru the app. Yes, all our HaRET builds are rooted.
portreeve said:
Hello,
Been trying to get droid explorer and adb to reconize my tilt2. Here is run down of what i have done.
on an up to date windows xp box
installed latest pdanet for android
installed latest droid explorer
connected my tilt2, it installed the adb driver but wont install the 2 cdc asm drivers
run droid explorer and it doesn't reconize the phone. i have the phone in debug mode and notification does come up.
on the android side i am running
frx 5
wistilt2 test kernel
highlandsun ril driver
btw, tried to run the busybox installer and it says it cant gain root access.. i thought all these builds have it by default or am i missing a step or two. I have superuser installed.
portreeve
Click to expand...
Click to collapse
I didn't have a problem, My drivers installed automatically for me, but I'm using Win7.
You don't have to have pdanet or superuser for DroidExplorer to work.
Goto your device manager and see what device is listed under ADB interface. My Rhod300 shows up as a HTC DREAM.
arrrghhh said:
All you need is the XDA device to install. The other two, CDC etc are not needed.
Is the adb service running? See if adb.exe is in task manager. You only need pda.net for the drivers, the software will mess with adb itself. So make sure their software is not running.
What do you mean busybox installer? For Titanium Backup or...?
You don't need SuperUser, that is an app that is more for security - if something asks for SU, it'll let you allow it thru the app. Yes, all our HaRET builds are rooted.
Click to expand...
Click to collapse
Sorry arrrghhh, I had the window sitting open, and thought I had hit submit... lol
i was able to install on a windows 7 box and it picked up the drivers but when opening up droid explorer it still shows no devices found. any other advice?
portreeve said:
i was able to install on a windows 7 box and it picked up the drivers but when opening up droid explorer it still shows no devices found. any other advice?
Click to expand...
Click to collapse
Did you try mine? Remove pda.net, once you have the drivers no software is required from them.
Plus, you might also try the good ole reboot, and ensure that adb.exe is running in the task list.
All things I suggested previously...
yes, i've done the suggestion. It shows its connected. Under device manager there is an android phone, under that there is android adb interface but nothing under that. I don't know what else to do. Is there something i am missing on the android side?
and adb is running in taskmanager.
portreeve said:
and adb is running in taskmanager.
Click to expand...
Click to collapse
portreeve said:
yes, i've done the suggestion. It shows its connected. Under device manager there is an android phone, under that there is android adb interface but nothing under that. I don't know what else to do. Is there something i am missing on the android side?
Click to expand...
Click to collapse
and you've rebooted?
I'm out of ideas, I've installed adb on tons of computers, win7 xp etc and all work flawlessly. It is a pretty advanced debugging tool, it's not very easy to install or use...
yes and i have rebooted twice now. still the same thing.
Boot android on phone.
Plug phone in.
Run Windows update.
Check device manager to make sure everything has drivers installed.
Run DroidExplorer
phone will show up as 00000000 in DroidExplorer
Reinstall DroidExplorer if problem persists.
Oh and there should be a device or driver in device manager called XDA, if memory serves me correctly.
Had the same problem about a month ago... downloaded PdaNet from the Marketplace here and it established the connection so I could use the USB to my phone. I didn't have to run it or buy it though .. just install it.
downloaded all the stuff from the thread. everything went smoothly. i watched the video step by step. after uploading the usbdrivers to my NT it said
"Android ADB interface" instead of "android composite ADB interface"
it shows up in my device manager as a nook tablet still.
i derped. so i thought it would be ok anyways and then tried to zerg rush the baster-ahem NT only to see that the Zerg didn't even find my device.
i promptly decided to just wipe everything from my nook and start fresh but also every single thing i tried has failed to get rid of that blasted "android ADB device" from the one click unroot thing to doing a 8 step reset thingy and just plainly reset and wipe data from the stock settings, and now many hours later i have had enough and decided to swallow my pride and flaunt the noob card. i need help. i must find a way to wipe everything or maybe i can take a step from here. i dunno. derpy derp.
windows 7 ultimate 64bit
nook tablet 8 gb sd card.
(^^this is how people write these things right?)
wagon_burner said:
downloaded all the stuff from the thread. everything went smoothly. i watched the video step by step. after uploading the usbdrivers to my NT it said
"Android ADB interface" instead of "android composite ADB interface"
it shows up in my device manager as a nook tablet still.
i derped. so i thought it would be ok anyways and then tried to zerg rush the baster-ahem NT only to see that the Zerg didn't even find my device.
i promptly decided to just wipe everything from my nook and start fresh but also every single thing i tried has failed to get rid of that blasted "android ADB device" from the one click unroot thing to doing a 8 step reset thingy and just plainly reset and wipe data from the stock settings, and now many hours later i have had enough and decided to swallow my pride and flaunt the noob card. i need help. i must find a way to wipe everything or maybe i can take a step from here. i dunno. derpy derp
windows 7 ultimate 64bit
nook tablet 8 gb sd card.
(^^this is how people write these things right?)
Click to expand...
Click to collapse
hm... well not sure if this is hidden anywhere in your description but did you try reinstalling the nook tablet drivers? since you have android adb device right now, uninstall that and if windows prompts you to restart you should do that. When you uninstall the adb drivers if there is a checkbox saying delete driver software for this device make sure to check that as well. basically what i am trying to say is you want to start fresh as in there should not be any reference to android or nook on your windows pc
another program that may be helpful is using usbdreview which is a program that monitors all devices with usb drivers. this may help is attempting to delete any reference to android and nook on your windows pc. hope this helps!
EDIT: just to add this tidbit in, if your having troubles with ADB, chances are it has nothing to do with your NT but rather with the drivers that Windows has installed already. There's a guide to installing ADB correctly, here's a link:
http://forum.xda-developers.com/showthread.php?t=1424563
ShinnAsuka said:
hm... well not sure if this is hidden anywhere in your description but did you try reinstalling the nook tablet drivers? since you have android adb device right now, uninstall that and if windows prompts you to restart you should do that. When you uninstall the adb drivers if there is a checkbox saying delete driver software for this device make sure to check that as well. basically what i am trying to say is you want to start fresh as in there should not be any reference to android or nook on your windows pc
another program that may be helpful is using usbdreview which is a program that monitors all devices with usb drivers. this may help is attempting to delete any reference to android and nook on your windows pc. hope this helps!
EDIT: just to add this tidbit in, if your having troubles with ADB, chances are it has nothing to do with your NT but rather with the drivers that Windows has installed already. There's a guide to installing ADB correctly, here's a link:
http://forum.xda-developers.com/showthread.php?t=1424563
Click to expand...
Click to collapse
thanks for the reply, tried it. i tried the process and my computer said itfound drivers for my device but couldn't install new drivers on my android ADB interface.
same problem i had previously.
wagon_burner said:
thanks for the reply, tried it. i tried the process and my computer said itfound drivers for my device but couldn't install new drivers on my android ADB interface.
same problem i had previously.
Click to expand...
Click to collapse
hm.. well if it keeps on auto installing generic drivers you will need to disable auto installation of drivers by windows. try looking through each of these links and see if it solves your problem. fyi you should uninstall all drivers relating to android and nook before proceeding
http://www.addictivetips.com/window...tomatic-driver-installation-in-windows-vista/
http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/
hope this helps
ShinnAsuka said:
hm.. well if it keeps on auto installing generic drivers you will need to disable auto installation of drivers by windows. try looking through each of these links and see if it solves your problem. fyi you should uninstall all drivers relating to android and nook before proceeding
hope this helps
Click to expand...
Click to collapse
well this is weird one atleast for me. i had all those settings on at the very start of the rooting process. and in the end i need to enable in the system config the USER to override the automatic driver install policy. so my anti install was thwarting me this entire time!!! ugh!!! total noob but we all gotta start somewhere. thanks to everyone for helping me out!
Okay. I have been trying to do other things with rooting other phones. I've rewritten a exploit so it will work on Mac. But this is a general problem. I deleted the Emulator and every single thing but the platform-tools on the windows side of my computer. So the only thing I have on my computer is the platform-tools folder (aka fastboot and adb) So I have tried what almost every forum has said. The adb kill-server. I restart it. Still there. I've tried to individually kill it still there. I've unplugged my device and ran adb still there. This is one reason that stopped me from rooting on a windows because this stupid emulator won't go away and it never has. I've never ran eclipse on the windows side or to say that never anything but the adb and fastboot. Only the Mac side have I done other things. Please if anyone could help that would be nice. It'd save me time from having to take the .bat files and changing them to sh files and opening with text edit, editing the file to work with terminal, then sh install.sh run the file and it not work then back to the drawing board which after rewriting some stuff over and over is a miracle to see it finally execute the exploit. Thanks for any help. I would gratefully appreciate it. Thanks. Sorry this kind of a off topic thing. O yeah that is the other reason from keeping me going s-off to. It's annoying and I would really love to fix the issue. I will take any advice. Just saying though the adb kill-server and a lot of other commands are not working and not doing the process. Please anyone who would like to help. Just put anything :$ Please and Thank you.
Hi, I'm using a galaxy A03, very similar to A02s. In file managers, I can only move files and put them in data folder, but I cannot delete them nor move them away. After a quick google search I found out that the android 11 storage managerment is called SAF which stands for Storage Access Framework. It doesn't allow me to do the tasks above. So I tried to disable SAF using this command in ADB:
adb shell sm set-isolated-storage off
My phone automatically rebooted, after that the storage turn wierd
Check the picture in this post, you will get what I mean
I just wanna know if anyone know how to disable SAF but still keep access to everything in the home directory.
I have the same phone, but I haven't tried that ADB command. Have you tried restarting both your PC and the phone again, and/or updating the drivers? If it does not work try undoing your changes via adb shell sm set-isolated-storage on.
BTW I see you're still on Windows 7, you might want to upgrade to Windows 10 (and 11 if possible). It's still free but Microsoft doesn't advertise it, you can search around
Oh, I also found this comment on Reddit:
About disabling scoped storage entirely while there is a command for that last time I've tried it on 11 it resulted in both internal and external storages being unable to be mounted
Click to expand...
Click to collapse
Cyndaquissshhh said:
I have the same phone, but I haven't tried that ADB command. Have you tried restarting both your PC and the phone again, and/or updating the drivers? If it does not work try undoing your changes via adb shell sm set-isolated-storage on.
BTW I see you're still on Windows 7, you might want to upgrade to Windows 10 (and 11 if possible). It's still free but Microsoft doesn't advertise it, you can search around
Click to expand...
Click to collapse
Haha, my pc is slow af so I must use windows 7
I tried to set isolated storage off and nothing can be read when I boot up, and available storage shrinked to 128mb
Cyndaquissshhh said:
I have the same phone, but I haven't tried that ADB command. Have you tried restarting both your PC and the phone again, and/or updating the drivers? If it does not work try undoing your changes via adb shell sm set-isolated-storage on.
BTW I see you're still on Windows 7, you might want to upgrade to Windows 10 (and 11 if possible). It's still free but Microsoft doesn't advertise it, you can search around
Click to expand...
Click to collapse
And it's easy to revert the change, the point of the post is to find out the way to disable scoped storage but still keep access to storage
Huyqwerty said:
Hi, I'm using a galaxy A03, very similar to A02s. In file managers, I can only move files and put them in data folder, but I cannot delete them nor move them away. After a quick google search I found out that the android 11 storage managerment is called SAF which stands for Storage Access Framework. It doesn't allow me to do the tasks above. So I tried to disable SAF using this command in ADB:
adb shell sm set-isolated-storage off
My phone automatically rebooted, after that the storage turn wierd
Check the picture in this post, you will get what I mean
I just wanna know if anyone know how to disable SAF but still keep access to everything in the home directory.
Click to expand...
Click to collapse
Guys, can we really actually do this? Why don't you just use file manager and give all those permission? Or is it me that too noob to understand for what this is all about?
theteebox said:
Guys, can we really actually do this? Why don't you just use file manager and give all those permission? Or is it me that too noob to understand for what this is all about?
Click to expand...
Click to collapse
Well, I faced the problem and learned about it a lot, you just didn't understand