After my last rebuild and root and flash to latest Beans build, I noticed when I tried to connect my phone to my laptop that it gave the dreaded "Does not recognize this device...." error on the phone and nothing came up on the laptop. Switched out a couple other cables, all good working. No luck.
I had recently rebuilt it as well with Win7Ultimate and thought I needed the drivers.
I went out and grabbed them from the root thread. No luck, even after a reboot.
Installed Samsung Kies. Went thru its troubleshooter, no luck still. Tried several other fixes as well, tethering check, usb debugging, etc. Nothing. Still reported the device having a problem installing properly, it would charge, but no access to the data.
I went to Devices and Printers and it was listed there as Samsung Android Device under Unrecognized Devices.
Right clicked on it, went to properties, went to the Driver properties and I saw it was listed as a driver by Jeremy Loper - that's the guy who made Casual if you didn't know. So its during the root and bootlocker unlocking process that his driver installs....so I clicked uninstall and checked the box to remove the driver software. When it was done, I unplugged the usb, plugged it right back in, Windows installed other drivers, boom, the storage comes up and I can get to my files.
I scoured around a bit and never saw anything for this fix for this problem - so figured I'd post here for everyone to have the fix avail as well.
*If this is the wrong area, no problem, sorry about that - I'd rather have this fix copied to the root/unlocker thread as a fix for this issue for others.*
Thanks for the heads up on this one. When I get back home I am going to test this out and report back.
aal1 said:
After my last rebuild and root and flash to latest Beans build, I noticed when I tried to connect my phone to my laptop that it gave the dreaded "Does not recognize this device...." error on the phone and nothing came up on the laptop. Switched out a couple other cables, all good working. No luck.
I had recently rebuilt it as well with Win7Ultimate and thought I needed the drivers.
I went out and grabbed them from the root thread. No luck, even after a reboot.
Installed Samsung Kies. Went thru its troubleshooter, no luck still. Tried several other fixes as well, tethering check, usb debugging, etc. Nothing. Still reported the device having a problem installing properly, it would charge, but no access to the data.
I went to Devices and Printers and it was listed there as Samsung Android Device under Unrecognized Devices.
Right clicked on it, went to properties, went to the Driver properties and I saw it was listed as a driver by Jeremy Loper - that's the guy who made Casual if you didn't know. So its during the root and bootlocker unlocking process that his driver installs....so I clicked uninstall and checked the box to remove the driver software. When it was done, I unplugged the usb, plugged it right back in, Windows installed other drivers, boom, the storage comes up and I can get to my files.
I scoured around a bit and never saw anything for this fix for this problem - so figured I'd post here for everyone to have the fix avail as well.
*If this is the wrong area, no problem, sorry about that - I'd rather have this fix copied to the root/unlocker thread as a fix for this issue for others.*
Click to expand...
Click to collapse
I have a link to a video tutorial in my guide that addresses this issue.
Related
Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
For quite some time now my fascinate will not connect to the computer other than for charging (no mass storage, not showing up in device manager). I can't say how many times i've installed drivers, changed cords and computers, etc. Today it finally showed up in device manager for the first time in a long time but 'Samsung Android Composide ADB interface" and 'Android composite ADB interface" show errors. It says drivers are up to date (also I just downloaded them) but there is a code 10 error saying drivers won't load. Sorry if this is too similar to other topics but any help is appreciated. I've been dying to get to CM9. Running CM7 Kang with Glitch v13.1
rjkxb2 said:
For quite some time now my fascinate will not connect to the computer other than for charging (no mass storage, not showing up in device manager). I can't say how many times i've installed drivers, changed cords and computers, etc. Today it finally showed up in device manager for the first time in a long time but 'Samsung Android Composide ADB interface" and 'Android composite ADB interface" show errors. It says drivers are up to date (also I just downloaded them) but there is a code 10 error saying drivers won't load. Sorry if this is too similar to other topics but any help is appreciated. I've been dying to get to CM9. Running CM7 Kang with Glitch v13.1
Click to expand...
Click to collapse
just wipe data and flash cm9...no need to odin. alot of folks seems to be having usb issues with thier devices lately....could possibly need cleaned? Thats a common place for pocket lint and other debris to build up.
have you tried to update the drivers manually ?
you can choose a driver to install. Sometimes when it gets to a list of drivers and the hardware compatibility is checked it may only list one driver. If you un-check that it will give you more drivers to choose from.
If you cant find anything that works check to see if your phone is recognized in download mode.
and your sure you tried decent new cable ???
Thanks for the help. I tried your driver suggestion and it still doesn't connect. This is the fourth cable I've been on and still nothing. I can get into download mode but odin never recognizes the device. I did successfully flash CM9 though. So I guess I'm okay until I need to odin for some reason.
I'm having the same issue as well. Until the connection issue, I was thoroughly enjoying ICS connecting.......10X quicker than GB. I have 3 different cables, updated drivers, no yellow exclamation in device manager......and all my phone will do is charge via USB. No PC or phone changes at all, just stopped working. I'm on ICS with AOPK. Still trying different methods...
I think Droidstyle might be right. My dad couldn't get his fascinate to connect, so he took it to a Verizon store and they cleaned the port and it connected.
MultipleMonomials said:
I think Droidstyle might be right. My dad couldn't get his fascinate to connect, so he took it to a Verizon store and they cleaned the port and it connected.
Click to expand...
Click to collapse
:good:
I tried giving it a little brush with a soft toothbrush and tried compressed air as well. No dice. Shouldn't I avoid taking it into verizon as they'll notice its clearly not stock (running aokp)? Or does that not really matter?
You should make a nandroid, then restore to stock. Make it look lived in, then take it to Verizon..
P.S. Sorry about taking a long time to respond, I am on vacation.
Without any computer connection at all how do I go about that?
And no worries. A late response is better than no response
Sent from my deviled aokp
Sorry. My brain must have still been on vacation... You might be able to disguise Superclean3 or TSM Resurrection as stock though, but make sure to use red CWM all and to flash the stock kernel immidiately after flashing.
I just tried the toothbrush method, dry at first. Then I attempted the toothbrush and isopropyl alcohol, no dice there either. Getting frustrated.....I need a beer!
---------- Post added at 10:40 PM ---------- Previous post was at 10:29 PM ----------
Ok, just figured out mine was the USB hub the entire time. I have one built into my desk. I plugged the USB into my printer, and it connects. Hmmm, my stuff in this room went crazy during a bad storm a few weeks ago......guess it may have messed some stuff up.
Hope the OP finds his problem. Maybe try running the USB right into the back of your computer, instead of a wherever you have it running to now?
Hi all. So I just picked up a Verizon Note 2 today and happily looked forward to rooting it. I'm on 4.1.2 Jellybean VRAMC3, model number SCH-I605. I'm afraid I may have messed something up.
I had downloaded Odin and installed the Samsung USB drivers and all that good stuff. Odin picked up the phone and all that, but a bit more looking around seemed to indicate that the usual Odin method of rooting wouldn't work on the latest version that I had.
So I downloaded the CASUAL installer and got that to run. It ran through the install, rebooted the phone, and then said it was waiting for Windows to recognize the device again so that it could continue with the install.
At that point, Windows informed me that a driver install had failed and the CASUAL install did not proceed any further, despite waiting a good 5-10 minutes.
Since doing this, the phone has had bizarre USB connection issues. Odin and Kies do not read the phone at all. Plugging the phone in brings up an additional drive for about two minutes with a Verizon Assistant Manager EXE, a USB Drivers EXE, and a couple other things, then it disappears.
The phone will often display a message informing me "Unable to find software on your PC that can recognize your device." This happens regardless of being in USB Debugging mode or not.
I've tried uninstalling and reinstalling several versions of Samsung's drivers as well as Kies. I also tried a factory reset on the phone itself, but these connectivity issues (and accompanying warning messages) persist.
Not sure how to proceed from here and would love a bit of help. Thanks!
Additional notes: All normal functions of the phone are working fine, and the computer DOES detect the phone as a "Samsung Android Device", but as stated Odin and Kies are not able to detect/connect with it.
Update: Messed with drivers a bit more and Odin will now pick up the phone again. When the phone disappears as a "drive" with install helper stuff, it reappears as a portable device, and I can browse the innards of the phone to put music and other stuff on it. CASUAL however still does not pick up the phone.
I'm Fairly New To The Android Concept, And I See Its A Little Bit More To Trying To Jailbreak It Vs. The iPhone, I'm Getting Stuck Using The Casual "NoYouVerizon" Concept Of The "One-Click" Method, But As Going On, I Don't Understand The Log's, I've Tried Searching For It Constantly, And I've Been At This For A Week Straight Now, I Need STEP by STEP Instructions On What To Do, Because I'm Reading Alot Of Different Things, And It's Not Really Helping Me At All, I Have A Verizon Samsung Galaxy Note 2, With Version 4.1.2 On It, and I Have *Correct Me If I'm Wrong* VRAMC3? If Thats The Right Thing. Please Somebody Help Me. Send Me A Message For My Contact Information. I Wanna Get This Done Pleasee!!!
theres the step by step guide
http://forum.xda-developers.com/showthread.php?t=2024207
One click root not working XDA. Someone needs to go back in and put the fix in for ERROR: No partition with identifier "60" exists in the specified PIT
Ive tried everything so far, even uninstalling the phone driver driver to allow samsung driver to reinstall, even manually installed the dev driver. I even tried to use odin3 to install via xda instructions. Odin can detect device if I just plug the phone in but if I put the phone in down load mode and connect, nothing. I checked device mgr and it shows the device in usb connections. WTF, XDA is verizon winning??????
Update:
Well I did discover after all this that I am rooted but I think that s all. When I plugged my phone into the computer Casuals usb showed in the Device Mgr screen instead of Samsung. To confirm I downloaded root checker from the play store and I am rooted via super user. Theres an issue though with putting the phone in download mode and odin detecting.
Update 2
Well it finally just worked and I was able to get odin to detect the phone while in download mode. I am now on root66 !! Help for others: Be persistent, I think it took time for my pc to accept and activate the changes IE: the casual driver replacing the samsung. It literally just happened after about 5 or 6 failed attempts of running the one click root. And it happened after a couple of samsung driver deletions. When the phone was plugged in, I went to device manager on the pc , usb devices and deleted the samsung drivers. I wound up doing this about 3 times. I restarted my computer after this to. Then I plugged the phone in again and there was casual usb controller appearing in device manager, replacing samsung. That was when I discovered I was rooted even though I had gotten the error message that started this post. Later, I went ahead and was able to install root66 by following the xda directions. wow......it was an all day affair but hopefully this will take some of the grey area out for others with this problem.
Thank you XDA for working to [email protected]^! this phone that verizon and google so graciously shoved up our #$% with a warm smile. The wi fi button for the notification bar is not available, I believe this is due to verizon when they put their stink on the phone. I would like to get that back if possible. Also the google search popping up when you plug the headset jack in is still there, but you can go into settings/task mgr/ all aps and scroll down to google search and disable it. The annoying pop up voice search hasnt showed up since I did this.
So after flashing 10/17/15 release of Tesla Arc_Flash I am unable to connect to the phone through adb without deleting the driver and adding it as an adb device. I have installed the LG G3 Verizon drivers but I am still not able to connect. In the device manager it shows that the drivers aren't there but also that they are there as a portable device. hxxp://tinypic.com/r/30ua82f/8
Also the command prompt is below. Brand new adb server started.
hxxp://tinypic.com/r/71myr4/8
Any help would be appreciated. If you need logs or anything else I am happy to provide it. Also since I feel this may get asked... Yes I have USB Debugging turned on. Have tried with Root for adb on and off and nothing seems to work. I can get it to connect through network but I don't want to constantly have to look for the IP address and port. This was also an issue in the previous release of Arc_Flash so please let me know.
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from http://www.lg.com/us/support-mobile/lg-LGVS985. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
roirraW "edor" ehT said:
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
Click to expand...
Click to collapse
I searched the ROM thread but found nothing matching what I am experiencing but I followed everything even close to it. I installed those drivers just now and restarted both computer and phone. Still comes up as an unknown driver. There is no modem section inside of the computer still. I can manually add the drivers but it still doesn't seem to help.
Also to add. I also have tried to add it as a modem and it gives Windows Error code (10) that it can not start the driver. I forgot to mention. Windows 10.
Well, I've connected to my phone via adb and used the LG flash tools on Windows 10 last week or the week before, although I have my insider updates set to Fast Ring and I kinda regret it because there was a recent huge push of a beta Windows, and they've broken how I had my video associations set up and I can't get my subtitles to work any more either. Sorry for off topic. My point is since Windows 10 is considered a constant "change in progress", and especially for people like me who joined to get "insider" builds, it's hard to tell what makes things not work. My main reason for even being on Windows 10 is to see what they come up with in their insider builds, but I guess when it mucks with my video enjoying ability, I start losing my patience.
I would seriously consider trying a different PC, or if you have the capability of performing a fresh Windows installation, even of Windows 10, that very possibly would fix it. Or if you just recently, within the last 30 days, upgraded from an earlier Windows to Windows 10, and didn't perform a clean installation, you can revert the upgrade through the the Windows settings. No idea if reverting would solve the problem, either, though.
As @bweN diorD pointed out in another similar thread just yesterday or the day before, when someone in your situation ends up trying a different PC, then everything goes smoothly. As far as the cause, there's too many variables.
If you can't use anyone else's PC, there's an outside chance that you could even do it at a library computer, as long as you don't reboot the PC (which I usually recommend after initially installing the driver, but sometimes things work fine without that). Rebooting a library PC usually undoes all changes, putting it back exactly the way it was.
Let us know how you make out.