• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ADB Shell issue

DemizE

DemizE

Well-Known Member
So I am trying to throw the command: adb shell. following error I recieve:

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed

I have all drivers installed properly. Never had this issue up until today. All my ports are wide open and all that good stuff. Messed up part is when I throw "adb devices" my device shows up. Anyone know what's up?

Also I do not have my antivirus running at the time of throwing the commands.
 
DemizE said:
So I am trying to throw the command: adb shell. following error I recieve:

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed

I have all drivers installed properly. Never had this issue up until today. All my ports are wide open and all that good stuff. Messed up part is when I throw "adb devices" my device shows up. Anyone know what's up?
Click to expand...


Restart the phone maybe....also u never sent me those links....
 
t3084 said:
...lol..

so yea, try restarting your computer and phone and try it again. if that doesn't work try deleting your adb files and install them again.
Click to expand...

Done all that good stuff. Even deleted all my stuff and tried again and it wouldnt work. It sees the device and all that. Just get a error everytime I run adb shell. Im starting to thin its something on the phone.
 
sammyz said:
The ones to your rom that you never released..... I can't test anything or help you without it..
Click to expand...

Once I get this ADB working I will send them too you. Primed helped me with the kernel embedding so thats all well. Now to put them together.
 
Yup. Rebooted plenty of times. Even rebooted into safe mode although when I did it didnt pick up the phone at all (because it was loading minimal services). Very annoying. I have even completely removed the antivirus I had to see and that wasnt it. I also had cut alot of services starting that I thought could cause confusion. Just weird it happened all of the sudden. I am using Windows 7 64-bit.
 
DemizE said:
Yup. Rebooted plenty of times. Even rebooted into safe mode although when I did it didnt pick up the phone at all (because it was loading minimal services). Very annoying. I have even completely removed the antivirus I had to see and that wasnt it. I also had cut alot of services starting that I thought could cause confusion. Just weird it happened all of the sudden. I am using Windows 7 64-bit.
Click to expand...

close command prompt
cd back to where adb is located
type adb devices and tell me what happens
 
sammyz said:
close command prompt
cd back to where adb is located
type adb devices and tell me what happens
Click to expand...


It shows the device. Thats why I am stumped. Everytime I try to do anything with the shell it just says "error:close:".
 
DemizE said:
I know all about this lol.
Click to expand...

I wasn't insulting your ability to make sure things were set up. If you want to lul at help, considering YOU have the problem, you didn't need to comment back with it.

You say you've done all this stuff... please tell us in detail, unless you do not want us to continue to use Google for you?

But I can already tell you the problem is in your PC OS. I could tell you how to identify it for sure... but you know all this :)
 
DemizE said:
It shows the device. Thats why I am stumped. Everytime I try to do anything with the shell it just says "error:close:".
Click to expand...
try another ROM, maybe it's your custom rom's fault that you made....if it is, then you have a big issue to fix :p
 
sammyz said:
...it's your custom rom's fault that you made...
Click to expand...

If not your OS then this is the problem for sure.

load up a ubuntu live cd, download adb for linux, the copy i have posted in my adb thread has it already, unless you have a linux version ready to go.

plug in your device, no drivers needed, and try running adb. if this works then your OS is the problem, else if it doesn't, then your ROM is the problem, in which case happy hunting! :p
 
You need me to send me that ROM, bro. I'd really like to help you fix out the bugs. And as far as adb goes, check if your java is the latest version, because I think java is required to use it..
 
Flashed to stock and back to normal. I have pieced the ROM back together and its better than the last time :) Catch me on gmail chat or Skype.
 
You must log in or register to reply here.
Back
Top Bottom