samsung I9506 not recognized

Jun 11 at 9:02 PM
Edited Jun 11 at 9:05 PM
I have a rooted device, with busybox, the last original drivers for samsung, and debugging active, but with crashed screen and lcd.

I have tried to connect with DE but it does nothing,

The pc recognize it, but DE not and need to access to "/".
The DE is not showing any error message

These are the last lines of the log:
2014-06-11 22:39:20,992   [1    ][ DEBUG] [DroidExplorer.Core.Logger] adb.exe start-server
2014-06-11 22:39:21,295   [1    ][ DEBUG] [DroidExplorer.Core.Logger] adb.exe root
2014-06-11 22:39:42,538   [1    ][ WARN ] [DroidExplorer.Core.Logger] * daemon not running. starting it now *
2014-06-11 22:39:42,539   [1    ][ WARN ] [DroidExplorer.Core.Logger] * failed to start daemon *
2014-06-11 22:39:42,555   [1    ][ DEBUG] [DroidExplorer.Core.Logger] adb.exe devices
2014-06-11 22:40:03,765   [1    ][ WARN ] [DroidExplorer.Core.Logger] * failed to start daemon *
2014-06-11 22:40:04,214   [1    ][ DEBUG] [DroidExplorer.Core.Logger] adb.exe devices
2014-06-11 22:40:25,515   [1    ][ WARN ] [DroidExplorer.Core.Logger] * daemon not running. starting it now *
2014-06-11 22:40:25,515   [1    ][ WARN ] [DroidExplorer.Core.Logger] * failed to start daemon *
2014-06-11 22:40:47,412   [1    ][ DEBUG] [DroidExplorer.Core.Logger] adb.exe devices
2014-06-11 22:41:08,591   [1    ][ WARN ] [DroidExplorer.Core.Logger] * daemon not running. starting it now *
2014-06-11 22:41:08,591   [1    ][ WARN ] [DroidExplorer.Core.Logger] * failed to start daemon *
Any idea?

Sorry for my bad english.

Edit: i tried too stop the avast firewall by the way but nothing
Coordinator
Jul 3 at 2:34 PM
Sorry for the delay in my response.

can you open a command line on your pc and navigate to the directory that you have the Android SDK installed. Specifically go to where adb.exe is located. Then in the command line type in : adb.exe devices

do you see your device listed there? Also, the logs you posted shows that the daemon was not started. Try rebooting your PC and see if you get the same type of error messages.