droid explorer

Rastaman-FB · December 5th, 2009, 01:35 PM

You lot seen this
not only does it seem to contain the drivers for galaxy for most os's
it also gives alot of nice functionality
Droid Explorer

i just installed it, flash recovery seems to be greyed out and i personally wouldnt try "apply rom update" lol
it allows access to some nice stuff though and will make things easier.

Gizmo306 · December 5th, 2009, 02:27 PM

useful tool, will keep in my PC.

Bomberman · December 5th, 2009, 02:35 PM

Got it, cheers mate

kofuukali · December 6th, 2009, 04:56 AM

You mention that it has drivers for practically all OSs, but I can't seem to find a linux version... or am I not looking right?

Rastaman-FB · December 6th, 2009, 07:25 AM

Quote:

Originally Posted by kofuukali

You mention that it has drivers for practically all OSs, but I can't seem to find a linux version... or am I not looking right?

when i say "most" i refer to the many versions of windows that the galaxy does and doesnt have issues with.

ironic that linux has an issue with android in general

kofuukali · December 6th, 2009, 07:27 AM

Ouch... that's what I feared I was to understand, but I refused to do it

.
Ironic it is indeed...

Andronix · December 6th, 2009, 10:51 AM

Linux issues are solved with right udev rules and patched adb.

pasxal · December 6th, 2009, 11:51 AM

We can start a project here to make sth like this for linux.

ryko · December 6th, 2009, 02:43 PM

Hi ,
Could anyone tell me if this program might help me to get by my problem with installing Gapps on the galaxo rom ? thanks

Rastaman-FB · December 6th, 2009, 03:28 PM

Quote:

Originally Posted by ryko

Hi ,
Could anyone tell me if this program might help me to get by my problem with installing Gapps on the galaxo rom ? thanks

it does say this
Backup the "Google Experience" applications and creates an update.zip containing the applications

however i think you should makesure you have 4.3 downloaded
download a fresh copy of the ii5 firmware saving to a location that is not compressed or encrypted (not desktop, "c:\Android files" would probably be best)
rename it to II5.tar then move it to the storage of the galaxy
boot into recovery and restore gapps

i have a feeling people are seeing issues cos the file has been through windows encryption or compression (going through my documents via protected account with protected areas)

ryko · December 6th, 2009, 03:56 PM

Ok Thanks Rastaman

camalot · December 11th, 2009, 11:36 AM

So am i reading this post correctly, Droid Explorer is working for the i7500?

Bomberman · December 11th, 2009, 11:42 AM

Rooted ones yes it would seem.

camalot · December 11th, 2009, 11:46 AM

Quote:

Originally Posted by Bomberman

Rooted ones yes it would seem.

Wonderful, this is another device I can add to the list of confirmed working.

Would someone be kind enough to run getprop on the following and post the values they return for this device, so I can confirm that I am detecting this device correctly:

Code:

# getprop ro.product.device
# getprop ro.product.model
# getprop ro.product.name

Thank you.

apcs · December 11th, 2009, 12:20 PM

Quote:

Originally Posted by camalot

Wonderful, this is another device I can add to the list of confirmed working.

Would someone be kind enough to run getprop on the following and post the values they return for this device, so I can confirm that I am detecting this device correctly:

Code:

# getprop ro.product.device
# getprop ro.product.model
# getprop ro.product.name

Thank you.

getprop ro.product.device
[root@galaxy:/][00mgetprop ro.product.device
GT-I7500
[root@galaxy:/][00m
getprop ro.product.model
[root@galaxy:/][00mgetprop ro.product.model
Samsung Galaxy running GalaxHero
[root@galaxy:/][00m
getprop ro.product.name
[root@galaxy:/][00mgetprop ro.product.name
GT-I7500
[root@galaxy:/][00m

Thanks for a great app - VERY USEFULL

Matenrou · December 11th, 2009, 02:09 PM

looks great, wish I could root my damn phone. Having problems with fastbooter.

Rastaman-FB · December 11th, 2009, 02:25 PM

Quote:

Originally Posted by Matenrou

looks great, wish I could root my damn phone. Having problems with fastbooter.

try the steps on this guide
http://androidforums.com/samsung-i7500/24540-simple-rooting-guide-without-galax0-galaxher0-roms.html#post163257

there is a driver pack i included that should help you
keep device manager open on windows then boot into fastboot
if you see android1.0 then immediately click update driver, choose from a list, have disk and point it to the driver you downloaded, select samsung galaxy composite.

you have 15 seconds to do it.
reboot into fastboot and you should be able to flash the recovery.img

Matenrou · December 11th, 2009, 03:16 PM

Quote:

Originally Posted by Rastaman-FB

try the steps on this guide
http://androidforums.com/samsung-i7500/24540-simple-rooting-guide-without-galax0-galaxher0-roms.html#post163257

there is a driver pack i included that should help you
keep device manager open on windows then boot into fastboot
if you see android1.0 then immediately click update driver, choose from a list, have disk and point it to the driver you downloaded, select samsung galaxy composite.

you have 15 seconds to do it.
reboot into fastboot and you should be able to flash the recovery.img

Had some problem with waiting for device. I then did the upgrade driver thing again, but I rebooted the phone into fastboot again before clicking confirm. Everything went smooth from there.

Rastaman-FB · December 11th, 2009, 03:50 PM

Quote:

Originally Posted by Matenrou

Had some problem with waiting for device. I then did the upgrade driver thing again, but I rebooted the phone into fastboot again before clicking confirm. Everything went smooth from there.

so you are now rooted?

Matenrou · December 11th, 2009, 03:56 PM

Quote:

Originally Posted by Rastaman-FB

so you are now rooted?

Hmm, I managed to get market enabler going and bought an app.

But now when I try to fix busybox so I can run your program I get permission denied etc while trying to set readwrite

It says operation not permitted.

Rastaman-FB · December 11th, 2009, 04:01 PM

Quote:

Originally Posted by Matenrou

Hmm, I managed to get market enabler going and bought an app.

But now when I try to fix busybox so I can run your program I get permission denied etc while trying to set readwrite

It says operation not permitted.

ahh you are trying this when fully booted into the phone?
the kernal is not rooted so it wont let you do it
theres a difference between a rooted kernal and su root
all you have to do is boot into recovery then attach the device via usb and run the commands needed to apply busybox

Matenrou · December 11th, 2009, 04:09 PM

Quote:

Originally Posted by Rastaman-FB

ahh you are trying this when fully booted into the phone?
the kernal is not rooted so it wont let you do it
theres a difference between a rooted kernal and su root
all you have to do is boot into recovery then attach the device via usb and run the commands needed to apply busybox

Ahh, ok I did that now and managed to push it there. But ofc I continue to have problems :P

Now when I try to install it and when I do cd /system/sbin it says /sbin/sh: cd: can't cd to /system/sbin

-.-

Rastaman-FB · December 11th, 2009, 04:28 PM

Quote:

Originally Posted by Matenrou

Ahh, ok I did that now and managed to push it there. But ofc I continue to have problems :P

Now when I try to install it and when I do cd /system/sbin it says /sbin/sh: cd: can't cd to /system/sbin

-.-

what guide are you using?
on galaxy system/sbin does not exist

taken from a post from Pegasus some time ago when i was rooting

Quote:

To install busybox on a firmware on the phone, there are a few ways. Easiest is to either use the rooted recovery v3 image or a rooted kernel.

If using the recovery, you'll need to boot up in recovery mode and connect your phone to your computer. For rooted kernel, just connect the phone when it's running normally and make sure adb is enabled in settings.

1. Run "adb remount"
2. Next push busybox with "adb push busybox /system/bin/busybox"
3. Create the symlinks with "adb shell /system/bin/busybox --install -s /system/bin" (you can skip this part if you do not foresee using the rest of the commands that busybox provides)
4. Modify cp's symlink to allow file managers to copy files "adb shell rm /system/bin/cp"
"adb shell ln -s /system/bin/busybox /system/bin/cp"

Matenrou · December 11th, 2009, 05:26 PM

Quote:

Originally Posted by Rastaman-FB

what guide are you using?
on galaxy system/sbin does not exist

taken from a post from Pegasus some time ago when i was rooting

I used the guide on the website, well I copied it to system/bin instead and when I tried to install it, it just spammed the window with loads of errors from missing files etc. But when I typed "busybox" the info came up. Plus it works now so I guess everything is ok :P

EDIT: ok everything isnt working -.-

briany · December 11th, 2009, 07:39 PM

I tried installing it, but at the end of the installation it said the setup has ended "permanently" due to an "error," and hence wasn't installed. I have Windows Vista (x64), and I tried both the x64 setup and standalone, but neither worked. Is anyone else having this problem?

Rastaman-FB · December 11th, 2009, 09:24 PM

Quote:

Originally Posted by briany

I tried installing it, but at the end of the installation it said the setup has ended "permanently" due to an "error," and hence wasn't installed. I have Windows Vista (x64), and I tried both the x64 setup and standalone, but neither worked. Is anyone else having this problem?

i managed to install it on windows7 x64 professional just fine

Rastaman-FB · December 11th, 2009, 09:25 PM

Quote:

Originally Posted by Matenrou

I used the guide on the website, well I copied it to system/bin instead and when I tried to install it, it just spammed the window with loads of errors from missing files etc. But when I typed "busybox" the info came up. Plus it works now so I guess everything is ok :P

EDIT: ok everything isnt working -.-

did you follow the steps i posted that pegasus gave me?

camalot · December 11th, 2009, 09:26 PM

Quote:

Originally Posted by briany

I tried installing it, but at the end of the installation it said the setup has ended "permanently" due to an "error," and hence wasn't installed. I have Windows Vista (x64), and I tried both the x64 setup and standalone, but neither worked. Is anyone else having this problem?

A few people are reporting this, it seems to be an issue with vista x64. I am trying to track down the issue.

briany · December 11th, 2009, 11:44 PM

Quote:

Originally Posted by camalot

A few people are reporting this, it seems to be an issue with vista x64. I am trying to track down the issue.

okay. fortunately i've got another computer with XP on it, so I'll just install it on that one--problem solved.

scollie · December 12th, 2009, 12:36 PM

I've managed to successfully install Droid Explorer on my Win 7 x64 PC but when I launch it, it shows '0 Devices Found'.

I've been having an issue with trying to get adb to see my phone for weeks and have trawled all the forums trying various 'solutions' but no luck.

I believe my problem is with the drivers from NPS which are required by adb but I'm not sure.

One solution was to not install NPS but instead just find the device in Device Manager (DM) which had a yellow flag next to it and point it to a set of drivers that were provided in the solution; however I don't have a yellow flagged device relating to the phone in DM!

Can someone (Rastaman-FB?) who has successfully got adb working on a Win 7 x64 system tell me what appears in DM in relation to the Galaxy?

All I see in DM is
ADB Interface
Samsung Galaxy Composite ADB Interface

There are no entries for the Galaxy under Modems or USB controllers. Should there be?

I'm starting to doubt whether I'll ever resolve this issue!!

Rastaman-FB · December 12th, 2009, 01:38 PM

Quote:

Originally Posted by scollie

I've managed to successfully install Droid Explorer on my Win 7 x64 PC but when I launch it, it shows '0 Devices Found'.

I've been having an issue with trying to get adb to see my phone for weeks and have trawled all the forums trying various 'solutions' but no luck.

I believe my problem is with the drivers from NPS which are required by adb but I'm not sure.

One solution was to not install NPS but instead just find the device in Device Manager (DM) which had a yellow flag next to it and point it to a set of drivers that were provided in the solution; however I don't have a yellow flagged device relating to the phone in DM!

Can someone (Rastaman-FB?) who has successfully got adb working on a Win 7 x64 system tell me what appears in DM in relation to the Galaxy?

All I see in DM is
ADB Interface
Samsung Galaxy Composite ADB Interface

There are no entries for the Galaxy under Modems or USB controllers. Should there be?

I'm starting to doubt whether I'll ever resolve this issue!!

thats all i see under ADB Interface is Samsung Galaxy Composite ADB Interface
that would suggest your device is connected as an adb device correctly
the modem stuff is only available when you install NPS

when you connect the device and use ADB and type ADB Devices what happens? seems odd that it displays but you cannot use ADB

try updating the driver and repointing it to my custom driver set here http://yardimage.co.uk/files/i7500/samsungADB.zip
this should deffo work as they are the ones im using since android sdk does not include the correct drivers anymore

camalot · December 12th, 2009, 03:32 PM

Quote:

Originally Posted by scollie

I've managed to successfully install Droid Explorer on my Win 7 x64 PC but when I launch it, it shows '0 Devices Found'.

I've been having an issue with trying to get adb to see my phone for weeks and have trawled all the forums trying various 'solutions' but no luck.

I believe my problem is with the drivers from NPS which are required by adb but I'm not sure.

One solution was to not install NPS but instead just find the device in Device Manager (DM) which had a yellow flag next to it and point it to a set of drivers that were provided in the solution; however I don't have a yellow flagged device relating to the phone in DM!

Can someone (Rastaman-FB?) who has successfully got adb working on a Win 7 x64 system tell me what appears in DM in relation to the Galaxy?

All I see in DM is
ADB Interface
Samsung Galaxy Composite ADB Interface

There are no entries for the Galaxy under Modems or USB controllers. Should there be?

I'm starting to doubt whether I'll ever resolve this issue!!

Make sure you have USB Debugging enabled on the device under Settings -> Applications -> Development

scollie · December 13th, 2009, 11:52 AM

Quote:

Originally Posted by Rastaman-FB

thats all i see under ADB Interface is Samsung Galaxy Composite ADB Interface
that would suggest your device is connected as an adb device correctly
the modem stuff is only available when you install NPS

when you connect the device and use ADB and type ADB Devices what happens? seems odd that it displays but you cannot use ADB

try updating the driver and repointing it to my custom driver set here http://yardimage.co.uk/files/i7500/samsungADB.zip
this should deffo work as they are the ones im using since android sdk does not include the correct drivers anymore

I updated the driver to the samsungADB as you suggested but same result.
I have always had USB Debugging enabled and have tried with the SD card Mounted/Unmounted but no difference.

ADB devices shows
List of devices attached

and a blank line after it!

ADB version shows 1.0.22

ADB remount shows
error: device not found

You mention that the modem stuff is only available when you install NPS.
I currently don't have it installed but when I have installed it in the past no Galaxy information has ever shown up under Modems.

That is why I was asking what shows up in your PC. I thought for adb to work it also needed some libraries from NPS, is this correct?

Rastaman-FB · December 13th, 2009, 01:59 PM

not that im aware of no
odin needs some of the libraries but not adb
my adb version shows 1.0.25
im using a redownloaded version of googles modular sdk rather than the old one as its been completely decommissioned now but it was working on 1.0.20
i find it odd that it lists the device there (in device manager) but cannot connect to it.
is the device rooted? do you get the same if you boot into recovery without connecting the device, run ADB usb (so it starts the daemon) then connect the device and do adb devices?

is it a RC version of windows7 or retail/RTM?
you got full admin rights with UAC settings quite low?

scollie · December 14th, 2009, 08:34 AM

Quote:

Originally Posted by Rastaman-FB

not that im aware of no
odin needs some of the libraries but not adb
my adb version shows 1.0.25
im using a redownloaded version of googles modular sdk rather than the old one as its been completely decommissioned now but it was working on 1.0.20
i find it odd that it lists the device there (in device manager) but cannot connect to it.
is the device rooted? do you get the same if you boot into recovery without connecting the device, run ADB usb (so it starts the daemon) then connect the device and do adb devices?

is it a RC version of windows7 or retail/RTM?
you got full admin rights with UAC settings quite low?

My phone is rooted and running GalaxoHero rom and the driver I am trying to install is from http://yardimage.co.uk/files/i7500/samsungADB.zip which you mentioned in a previous post.

I tried booting into recovery without connecting the device, ran "adb devices" ( not sure what you mean by "adb usb"?) to start the daemon, connected the device and ran "adb devices" again but no device shown.

I am running a retail upgrade version of win7 x64, upgraded from XP (where I had adb working successfully!).
I have full admin rights and I had previously also created an admin user to try getting adb working but no luck.

My UAC settings were on "Default - Notify me only when programs try to make changes to my computer" - the second highest but I thought this only changed the notification level. I reset them to the lowest level "Never notify me", rebooted and tried again - same result.

Apart from notification levels, are there other UAC settings I could try?

Rastaman-FB · December 14th, 2009, 08:49 AM

very odd
those drivers are the same im using cos i created them and hosted them.
its wierd that it sees the samsung galaxy composite interface but you cannot do anything with it.

try reinstalling NPS clicking ok to all the prompts and errors then turning off usb debugging then turn it back on again and connect device and see if it picks it up again

im at a loss completely as apart from you upgrading from xp we are identical
i did a fresh install of win7 pro 64 Retail

Rastaman-FB · December 14th, 2009, 11:36 AM

ok found a fix for you and im sure its the same issue so ill write it up when i get home and add it to the FAQ as this deffo works

go into device manager and uninstall absultely every samsung usb related driver including the ADB
if it gives you an option to delete it click yes
after all of the drivers are deleted, DO NOT connect the device and make sure you reboot your machine

once you boot back in connect the device, windows 7 will try and auto find the drivers so click skip and it should fail.
click here and download the samsung usb drivers
extract them to a folder (default file name is good so you know which drivers they are)
go into device management and right click samsung usb device. click update driver, click browse computer for driver software, click browse and point it to the driver folder of the file you just extracted.
windows7 should install samsung galaxy usb composite device and then it should start auto installing the rest of the drivers

It will now fail on one driver and should show in device manager as unknown device
now this is the ADB driver.
go to device manager click update driver, click browse computer for driver software, click let me pick, click all devices, click have disk, point that one to the usb_driver/amd64 folder you downloaded from yardimage and select samsung composite adb interface.

jobs done

scollie · December 14th, 2009, 11:52 AM

Quote:

Originally Posted by Rastaman-FB

ok found a fix for you and im sure its the same issue so ill write it up when i get home and add it to the FAQ as this deffo works

go into device manager and uninstall absultely every samsung usb related driver including the ADB
if it gives you an option to delete it click yes
after all of the drivers are deleted, DO NOT connect the device and make sure you reboot your machine

once you boot back in connect the device, windows 7 will try and auto find the drivers so click skip and it should fail.
click here and download the samsung usb drivers
extract them to a folder (default file name is good so you know which drivers they are)
go into device management and right click samsung usb device. click update driver, click browse computer for driver software, click browse and point it to the driver folder of the file you just extracted.
windows7 should install samsung galaxy usb composite device and then it should start auto installing the rest of the drivers

It will now fail on one driver and should show in device manager as unknown device
now this is the ADB driver.
go to device manager click update driver, click browse computer for driver software, click let me pick, click all devices, click have disk, point that one to the usb_driver/amd64 folder you downloaded from yardimage and select samsung composite adb interface.

jobs done

I'll give this a try shortly but before I do I'll just mention that this is similar to previous advice given by either yourself or Kam or maybe someone else and my problem as I have been mentioning all along is that apart form ADB Interface I have nothing else related to the Galaxy showing up in Device Manager(DM).

When I connect the device win7 doesn't try and install the drivers and I have never had a samsung usb device show up!!

This is why I was constantly asking what others had in DM in relation to Samsung.

In XP I believe I had entries under USB controllers and Modems for the Galaxy, but nothing in win 7 and I think this is a major part of my problem.

Anyway I'll give your suggestion a try and report back.

Thanks for taking the time to help!

Rastaman-FB · December 14th, 2009, 12:23 PM

Yes its because the samsung usb device driver has been pointex to the adb driver rather than the samsung usb composite driver so it can't fint the rest. I tested and reproduced your fault at work on your same setup and its easy to mess up if you don't do it in the order I specified.
Good luck mate

scollie · December 14th, 2009, 01:46 PM

Right we're getting closer but not quite there yet!

I deleted the adb device and uninstalled all Samsung USB related drivers, rebooted my machine and connected my device.

I could now see devices with missing drivers which I updated with the drivers you linked to in your post.

Now in DM I can see
Ports(COM & LPT)
Samsung Mobile Modem Diagnostic Serial Port (WDM) (COM4)

and under USB controllers
Samsung USB Composite Device
USB Mass Storage Device

There was already a USB Mass Storage Device but there is now a second which is not marked as Samsung but the hardware Ids show it as
USB\Vid_04e8&Pid_6601&Rev_0100&Mi_03&Os_NT
USB\Vid_04e8&Pid_6601&Rev_0100&Mi_03
USB\Vid_04e8&Pid_6601&Mi_03&Os_NT
USB\Vid_04e8&Pid_6601&Mi_03
USB\Vid_04e8&Pid_6601&Class_08&SubClass_06&Prot_50 &Os_NT
USB\Vid_04e8&Pid_6601&Class_08&SubClass_06&Prot_50
USB\Vid_04e8&Pid_6601&Class_08&SubClass_06&Os_NT
USB\Vid_04e8&Pid_6601&Class_08&SubClass_06
USB\Vid_04e8&Pid_6601&Class_08&Os_NT
USB\Vid_04e8&Pid_6601&Class_08

It is not flagged with a yellow marker but I've tried pointing this at the driver folder and it tells me that the best driver is already installed.

When I untick the "Show compatible hardware" box and scroll down I see Manufacturer Samsung which shows 3 models "Digimax 220", "E.M. USB Hub" and "USB Hub" and also Manufacturer
Samsung Electronics Co Ltd and model "USB Composite Device".

When I select the Electronics one and point it to the same driver folder as above it looks for an .inf file and says the .inf files don't contain the relevant driver.
When I point it at samsungADB I get the same message.

At this point I had debugging turned off so there is no "ADB Interface" in DM.
When I turn on USB Debugging ADB Interface appears as a default ADB Device and I pointed this at the samsungADB drivers and it updated to
"Samsung GALAXY Composite ADB Interface", however the other entries mentioned above under Ports and USB Controllers disappeared.
They reappear when I turn off USB debugging but ADB Interface disappears

I then tried running adb devices with debugging both on and then off but no luck.

I'm just wondering whether I should have had USB Debugging on when I connected my device after rebooting?

Unfortunately I don't have any more time this evening to try it again.
Unless I hear to the contrary I will repeat the process tomorrow with USB debugging already on and see what happens then.

I must admit when I saw the new Samsung entries appear in DM I thought we were there as I hadn't managed that before.

Rastaman-FB · December 14th, 2009, 02:30 PM

try it again with debugging on
the mass storage should just be default windows7, there is nothing special there and doesnt need specific samsung ones
have debugging on when you delete the ADB driver please

there will only be one driver left with an X in windows 7 hardware automation and in device manager it will just show a yellow exclamation with "unknown device" that is the last driver and is the samsung composite ADB interface

Quote:

It is not flagged with a yellow marker but I've tried pointing this at the driver folder and it tells me that the best driver is already installed.

When I untick the "Show compatible hardware" box and scroll down I see Manufacturer Samsung which shows 3 models "Digimax 220", "E.M. USB Hub" and "USB Hub" and also Manufacturer
Samsung Electronics Co Ltd and model "USB Composite Device".

is a red herring and not much to do with it, its mass storage and you shouldnt be messing about with that.

ryko · December 14th, 2009, 02:40 PM

Hi started following this thread having had similar problem. I seem to remember that there is also a Nokia driver with the same date as the Samsung drivers that you have to unistall at the same time for this fix to work .(do'nt ask me why just hope it helps

)

scollie · December 15th, 2009, 01:59 PM

Quote:

Originally Posted by Rastaman-FB

try it again with debugging on
the mass storage should just be default windows7, there is nothing special there and doesnt need specific samsung ones
have debugging on when you delete the ADB driver please

there will only be one driver left with an X in windows 7 hardware automation and in device manager it will just show a yellow exclamation with "unknown device" that is the last driver and is the samsung composite ADB interface

is a red herring and not much to do with it, its mass storage and you shouldnt be messing about with that.

Just read your reply but I don't have time to do this tonight. Hopefully I will get time tomorrow - so this is just a note to let you know that I'm still here looking for a solution and appreciating your help.

scollie · December 16th, 2009, 12:31 PM

Thanks a million Rastaman-FB!!!!!!!!!

I had another go with USB debugging enabled and after a little bit of messing around, adb works as does DroidExplorer.

I think I'm fairly competent on a technical level (Oracle developer; Unix/Linux) but don't know much about windows - esp Win7. I think I would still be messing around trying to get this working at Xmas next year if it hadn't been for your help.

So once again - THANKS!!

Rastaman-FB · December 16th, 2009, 01:35 PM

no worries, glad we got there in the end :P

Rastaman-FB · December 22nd, 2009, 08:34 AM

hmm i cannot create new folders or files within droid explorer
running windows7 professional x64

camalot · December 22nd, 2009, 11:22 AM

Quote:

Originally Posted by Rastaman-FB

hmm i cannot create new folders or files within droid explorer
running windows7 professional x64

That functionality is coming, i've had to put it on the back burner for the last couple releases because of some install issues, but I am working on it. Once I wrap up the couple issues I have, it's on the top of my list.

Rastaman-FB · December 22nd, 2009, 01:23 PM

Quote:

Originally Posted by camalot

That functionality is coming, i've had to put it on the back burner for the last couple releases because of some install issues, but I am working on it. Once I wrap up the couple issues I have, it's on the top of my list.

ahh ok so this is work in progress then?
that would explain it. i wasnt sure if it was something broken or not

thanks for the clarification

cbuy · March 19th, 2010, 08:46 AM

Hi ! I'm new to Android (tech profile though), and was searching for a solution to my "pains" when I found this forum, which I find great. So, signed in... and here I am ! For now, I just have questions... hope to have answers in the future ! The thing is this:

I bought a Motorola Milestone (the best cell phone I've ever seen). I learned all the necessary liturgia, and started messing with it: rooted it, then installed SDK, etc. I then began using ADB, which worked great. I could manage to install busybox without a flaw. Later, I installed de 2.0.1 SBF from Brazil, which is very nice. So far, so good.

Buuuuut, then I installed Droid Explorer !!! In short, since then, ADB won't work any longer. I get the message "error: device not found". That's it ! It's a strange matter, because when I plug the device my computer "sees" it without a problem. I turn USB debugging on. I've tried even to run RSD Lite, which also can see the device.

What's up ? Hope you can help me ! (And hope I can help anyone in the near future !)

ryko · March 19th, 2010, 09:21 AM

Hi cbuy, you could try asking Android Forums - View Profile: camalot he is the developer of droid explorer, I think