i've tried windows xp, windows 7, ubuntu, and debian. i've tried samsung new pc studio drivers, and any other set of drivers i could find. i've factory reset the phone but still cannot seem to connect. any help would be appreciated. can't find any instructions that work online anywhere.
I am desperate for help with this. I have tried USBDeview to delete drivers. I can see it in Modem Mode and in Mass Storage Mode (with de-bug off) but as soon as I put it in DeBug mode my computer won't see it.
I get the following errors:
Can not install this device "Samsung Android USB Device"
Can not start this device the driver may be missing or corrupted.
I have the Android SDK
I have the Samsug PC Studio
I have the Samsung USB drivers
The computer keeps saying the driver I have selected is no better a match than the ones already installed.
It connects in download mode. Odin 3.98 works. I have flashed the phone to CL14 and Zefie's 10.3 kernel.
I have transfered files back and forth, but I can get ADB to see it, in DeBug mode or otherwise.
As soon as I put it in debug mode I get the Yellow Exclamation point in system > device manager.
I am trying to get rid of the mute and speaker buttons on the dialer and I think ADB is the only way to do it.
a couple of possible workarounds...
1) i'm assuming it's a driver issue; but boot into recovery and connect and see what happens (vol down, call, end) --> i doubt it'll see your phone for you to adb to it, but who knows...
2) take one of the themes out there (not sure if you've put one on), and open it up with 7zip - replace the Phone.apk with the one without the mute & speaker button (or it's actually minimized to 0x0, hehe) and apply the zip in recovery...
drivers are a pain to work through and talk people through, so that may be easier and faster...
3) i'm not sure if terminal will mess anything up if you push it that way (it's always a little scary when your phone is on and you're pushing things to the system folder)
The Following User Says Thank You to chibucks For This Useful Post:
1) boot into recovery and connect and see what happens (vol down, call, end) --> Tried - failed
2) take one of the themes out there (not sure if you've put one on), and open it up with 7zip - replace the Phone.apk with the one without the mute & speaker button (or it's actually minimized to 0x0, hehe) and apply the zip in recovery...
drivers are a pain to work through and talk people through, so that may be easier and faster...
3) i'm not sure if terminal will mess anything up if you push it that way (it's always a little scary when your phone is on and you're pushing things to the system folder)
1. Tried, but did not work
2. Attempting, but I want to do it right. Do I need to rename PhonEClair.apk to Phone.apk prior to doing this?
3. I'll need to figure out how to do this first. I'll try it if #2 doesn't work.
Take a screenshot of your device manager while your phone is connected. Specifically the usb section and any spot that shows your phone. Lemme see that picture.
You may have to add a path variable if your running a windows 64bit Operating System:
* * On Windows, right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the tools/ directory to the path.
2. Attempting, but I want to do it right. Do I need to rename PhonEClair.apk to Phone.apk prior to doing this?
Thank you, so much for helping.
Yes, you'll need to rename it to Phone.apk (in essence you're replacing the Phone.apk in the theme.zip)
One note: if you haven't applied themes, you MAY have to apply to the cl14 template zip first before applying the theme.zip; but that's a whole other subject. also, you'll need to make sure you have the right, deodex'd one.
there are 3 sets of different drivers used (copied from someone else's post)
On Vista x64
1 - (Standard USB connection.)
-"Android UMS Composite USB Device" - Listed under Disk Drives
- Drive letter, for me its "J:\" - Listed under Portable Devices
2 - (Connected in Recovery Mode)
-"Android UMS Composite USB Device" - Listed under Disk Drives
- "Samsung Android USB Modem" - Listed Under Modems
- "Samsung Android USB Composite Device" - Listed Under Universal Serial Bus controllers
3 - (Connect in Download Mode)
- "Samsung Mobile Modem" - Listed Under Modems
- "Samsung USB Composite Device" - Listed Under Universal Serial Bus controllers
Last edited by chibucks; March 12th, 2010 at 10:55 AM.
One note: if you haven't applied themes, you MAY have to apply to the cl14 template zip first before applying the theme.zip; but that's a whole other subject. also, you'll need to make sure you have the right, deodex'd one.
Did this, but it bricked my phone. Couldn't get past Glowing Samsung image.
Will reflash to CL14 with Zefie's 10.3 Kernel and try the drivers you linked to.
Did this, but it bricked my phone. Couldn't get past Glowing Samsung image.
Will reflash to CL14 with Zefie's 10.3 Kernel and try the drivers you linked to.
btw... I am not Vista, I am on Windows XP.
have you applied a theme before? i got stuck at the glowing samsung image when i first applied a theme...
so i had to first apply maxdamage's cl14_theme_template.zip (found at sdx-developers), which is the deodex'd default template... after it deodex'd the system, then i flashed the theme i wanted...
not sure if you tried that or not. just a thought.
The new drivers did not help. Windows still says it could not find a better match. I wonder if there is a way to force it to use those drivers.
Can not adb into the phone. I will try the path changes, but ADB launches just fine, it just doesn't see my device. And the driver is definitely yellow exclamation while in de-bug mode, but fine when it is not in de-bug mode.
Sorry the path changes were for the OP. For you Im not sure whats going on. On the device manager Im sure youve uninstalled the device and "searched for new hardware" right?
Sorry the path changes were for the OP. For you Im not sure whats going on. On the device manager Im sure youve uninstalled the device and "searched for new hardware" right?
I have uninstalled it over and over and searched for new hardware over an over.
As soon as I plug in the phone, it recognizes it as Samsung Android USB Composite Device. It's almost like it has a memory of the wrong driver, but it won't accept any other driver as a better match.
Actually it worked out. I was trying to get the phone connected back to Re-Flash and it was fine. Not sure exactly how, but it worked.
So, I think I have the cl14_theme_template.zip loaded correctly.
Now I need to find a theme to replace the phone.apk - Any recommendations. I am using Panda Home right now, but would be fine with the stock Home.
Would APK Intaller work for this or not, since it is a system file?
i'm using the black_aero theme... i think there may be conflicts with panda or you have to put panda back on after you install the theme or something, but i thought i read that somewhere.
an apk installer probably would not work for /system files - you'll have to push it... but you could try. i'm pretty sure you can't though.
actually, another thing you COULD do is apply a theme with ONLY the Phone.apk changed (you could even use max's cl14 template, remove all the other apps, and just change the Phone.apk)... that way it won't overwrite what you have already. you do need to leave the meta folder alone, and the deodex.sh
Last edited by chibucks; March 12th, 2010 at 02:25 PM.
So just in case you didn't know, you don't need ADB to remove apps. Pull down connectbot from the apps store, run it and connect to "local"...su...cd system/app...etc...
OK, so I used a different computer with the NEW Samsung PC Studio drivers, and I can connect via ADB to the phone, but only when it is on.
I can not connect while it is in Recovery Mode. Any thoughts?
Also CHIBUCKS - I once saw a step by step ADB instructions for pushing the Phone.apk but I can't find them now. Not sure why it's not coming up in search.
OK, so I used a different computer with the NEW Samsung PC Studio drivers, and I can connect via ADB to the phone, but only when it is on.
I can not connect while it is in Recovery Mode. Any thoughts?
Also CHIBUCKS - I once saw a step by step ADB instructions for pushing the Phone.apk but I can't find them now. Not sure why it's not coming up in search.
the recovery drivers probably aren't correct...
but if you can access it when you're in debug mode, if you're just pushing an apk, you can do that... for the phone.apk push... here you go:
Sprint has just added its first full QWERTY Keyboard Android Phone to their lineup with the Samsung Moment. Initially rumored as the "InstinctQ", the Moment rocks an 800 MHz processor - what was the fastest processor in an Android phone a... Read More
can't connect to phone via adb
