After racking my brain for a few days, a couple hours each day, I've fixed my issue with my device being unknown.
Let me start by saying I'm flash happy, and everyone that knows me personally, tells me to just quit jacking with my phone. NOT A CHANCE! I'm on my 3rd Cappy and shouldn't have ever exchange it again. I only had to in the beginning, because I was a newbie and had not know enough, but to get me in trouble.
I presume that this should work on all Windows OS's. I personally am running Vista Enterprise x86.
My symptoms:
Plug in phone to the usb and it there was about a 15% chance off being able to mount to usb, and Windows recognizing as a mass storage device. I tried un-installing drivers and re-installing and it would work some of the time, until the point came when parts of the driver install would fail. Then to the point when it was just completely unrecognizable. I thought I had it fixed because it seemed intermittent. In the middle of flashing to stock, something interrupted communication between the pc and my phone. Restarted the phone and attempted the flash again. Got a little farther and froze again. I had to use another pc that I had never connected my phone to before and I was able to use my jig to trigger download mode, because no buttons combinations would allow it into download mode.
This got me thinking that it was specific to my pc and not my cable or my phone.
My resolution:
I went straight to the registry and went to find. I deleted every entry that came up for "i897" and "i9000" excluding what was listed in the system volume information, as I didn't have permissions to remove any keys. I didn't keep count, but I probably deleted 300-400 registry keys that pointed to my phone. It seems as if with each developers rom that I had flashed, there was an entry for a different device. Don't quote me on that, because it is just my personal consensus. I also un-installed the samsung drivers, the unknown device driver, kies software, and anything associated with samsung. I noticed that next to all of the i9000 instances, the hex key for me started with 1000ee. So I also searched for the first part of that key trying to ensure that all instances of the device. Lastly, I deleted the samsung folder from program files.
I installed the samsung drivers package commonly listed in all of the other threads for x86 operating systems. I plugged in my phone and watched as each and every driver installed successfully. Keep in mind different drivers are installed depending on if you have usb debugging on/off, and the options for if the preferences on you phone are set to media, storage, or kies. I have multiple usb ports, however testing has shown me that, for me and my setup, I can plug into the port that I used when installing the drivers the final time, I am able to connect consistently. Earlier today, I tried to plug into a different usb port and it was an unknown device. I am led to believe, this is because I didn't un-install the unknown device on this particular port.
If you intend to work in the registry, please remember to always back it up first. You can always restore.
Hopefully my findings can help you as they did me. Happy flashing and I would like to thank the community for the dedication to assisting each other and the developers, for making flashing, better than crack cocaine. Flashing rom's doesn't make you twitch near as much as a crackhead.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Has anyone had any luck with this?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Related
Hi guys, I've had a look around the net and asked on other forums, but can't seem to find the answer to my problems, so someone recommended here.
Apologies, if this has already been covered, but I did have a search and couldn't find what I was looking for.
I think I have two problems, don't know if they are related, but don't think so.
Problem 1:
Got the Galaxy S for my daughter for Christmas. She has never been able to log in to the android marketplace. She was using the her google log in which wasn't a gmail account. Today I signed her up a gmail account, and tried again and got the following error message:
You don't have a network connection.
This could be a temporary problem or your phone may not be provisioned for data services. Please try again when connected to a mobile network, or connect to a wi-fi network. If the problem continues, call customer care.
Click to expand...
Click to collapse
The phone is definitely connected the net by wi-fi, which I have proved to be working correctly.
Problem 2:
To try and solve problem 1, I thought I would see if the firmware was up-to-date, however, I can't get the phone to connect to Kies. I have tried on two different laptops, one running Vista and one Windows 7. It seems to be saying it's some kind of driver problem. I have clicked on install drivers on Kies, but it makes no difference.
I have made sure the phone is selected Kies. I have also tried selecting mass storage and connecting through My Computer, but still it doesn't recognise the phone.
I believe the phone's firmware is out of date, as it is 2.1 update 1 and I believe 2.2 is available.
Apologies for the long post, can anybody help me to get Kies and marketplace working?
I am not interested in jailbreaking the phone, as it's for my daughter.
The phone is a contract phone, in the UK with orange. I have made sure orange safe guard is not active.
Thanks in advance, if you need anymore infor, i will try and supply it.
Any idea's?
Bump.
Can anybody help or is the best option to try a factory restore / take it back to the shop?
Well there is alot of tread that explain how you connect to kies.
If you can use internet then it should work.
Have you try to power of the phone and wait 5 minutes and then power it on?
**DamianGTO Steam kernel. 350MB Ram. 500HZ. ext2/jfs . js3 base**
I have got the market place working by doing a factory restore, but for the life of me, I can't get the phoned connected to Kies to do a firmware update.
I have tried on 4 different laptops.
1. Windows 7 Home Premium 64 bit.
2. Windows 7 Home Basic.
3. Windows Vista.
4. Windows XP.
and I can't get it to connect on any of them.
I have tried un-installing and re-installing Kies. I have tried using different usb wires and ports. Phone charges by usb when plugged in.
I have tried connecting the phone in both Kies mode and Mass Storage mode.
The error I keep getting seems to be a driver error:
Device Driver software was not successfully installed.
Please consult your device manufacturer for assistance in getting this device installed.
Bluetooth peripheral device - Driver not found
Click to expand...
Click to collapse
Looks like I'll need to take the phone back or ring Samsung.
just try to reconnect it
astralmaze05 said:
just try to reconnect it
Click to expand...
Click to collapse
Never thought of that.
p-2-b-a-a said:
Never thought of that.
Click to expand...
Click to collapse
tell me if that trick works
Are you using a USB hub? If so don't . Plug it straight into the rear USB of your computer.
Do you have Bluetooth active? Turn it off.
Are you using any other Home than the one it came with (the screen you see when you first turn it on)? Go back to the stock TW Launcher
In the Kies Tools menu click on Install Driver and then try again after it's finished.
Finally if it is still not connecting leave it plugged in and go into device manager. If the drivers show up there they should be listed as Samsung i9000 if I remember then right click and un-install drivers then unplug phone and plug it back in after a few moments.
Also use the cabel that did come with.the phone.
**DamianGTO Steam kernel. 350MB Ram. 500HZ. ext2/jfs . js3 base**
I've literally searched high and low for over 2 weeks trying to resolve this issue before bothering you with it.. I'm trying to flash this phone over to Cricket. Ive installed Android SDK and JDK, HW Virtual Serial,Debugging on. The problem I have is, when I just power on the phone it has no issues being recognized as a storage device. Its when I either press "T" and power it on the issues begin.. the Motorola composite device could not be installed. Or when I try to use HW serial it tells me Motorola USB networking device wasnt installed correctly. Ive downloaded two different drivers with no prevail. Im running XP 32bit. When I go to device manager I see the :ADB Composite device (Has no Drop down properties) with the sub folder Motorola A855 with an exclamation next to it.. I did a couple of manual updates(two official drivers from Motorola site) directing the update to the folder containing the driver. Even tried the edit .inf file I read about on another forum with no prevail. RSD Lite connects with no problem. Its the Networking driver and A855 driver that wont install in PC/Diag mode. My head is about to litterally explode dude.. Im irritated for spending $160 on it and stuck for 2 weeks now, my wife upset I wont give up and spending too much time trying.. PLEASE HELP! PLEASE! If not this phone is for sale! LOL! Mint condition.
What type of phone?
Also I've ran into driver issues, and its always been the computers fault every time. You may have conflicting drivers, or it may even be something as simple as a bad USB port.
When its problems like this, that just should normally work, its usually some stupid crap.
For instance, I was using a usb exension to connect my droid to the pc, and for somereason it was problematic, but when I connect directly it works.
I know these aren't the technical solutions u are loking for, but eliminate all the variables u can before moving on or giving up.
Check all cords, ports, etc; remove all drivers, uninstall all motorolla software. Uninstall anything phone related on your comp and try again.
Get ahold of me at (myscreenname).com [sn: aids] and ill try to help you more. I hate these large sies where people never help. You had 71 views and ZERO replies, to me that's unacceptable.
Good luck, and get ahold of me.
Sent from my Droid using Tapatalk
Got the same problem
hHey guys, I have the same trouble. I need an answer too. Help!
So I got my Samsung Galaxy Tab (sprint CDMA version) today and when I first plugged it into my computer the drivers installed fine. I was able to mount the sd card and transfer files with ease. I then proceeded to root the device hoping to put a new rom on it, I've got a captivate and am not a rookie at all when it comes to flashing roms via odin, cwm, etc...I first put the device into debugging mode which is where things got weird. As soon as I put the device into debugging mode and plugged it in via usb it immediately became "unrecognizable". I have the correct updated drivers for the device both from the Samsung website and via the Android SDK tools. There should be no reason why this happened. So I then took it out of usb debugging and plugged it back in and bam, again, "USB Device not recognized". I've been installing and uninstalling drivers, the device itself from the device manager, and have been trying other numerous ideas. I've been Googling and searching for hours upon hours at this point and don't know what to do next. Odin does NOT recognize the device when in download mode and the device does charge when connected to the computer. I have tried a different cord with the device and different computers and it's all the same story, works until debugging is enabled then it will no longer work no matter what. I am fairly sure at this point the device itself is malfunctioning or defected but I wanted the opinion of others before sending it back. I am pretty sure have tried everything and am doing everything right. Please help if you can, if not I still appreciate your time! Specs are listed below:
Hardware Version
P100.08
Model Number
SPH-P100
Firmware Version
2.2.1
Kernel Version
2.6.32.9
Ebicoustic said:
As soon as I put the device into debugging mode and plugged it in via usb it immediately became "unrecognizable".
....the device does charge when connected to the computer.
Click to expand...
Click to collapse
1. Just wondering, have you installed Kies before connecting the tab to your PC?
2. The SGT will not charge "normally" with a USB connection. It will trickle charge, which is very slow way of charging, and the device will not indicate that it is charging. Does your device indicate it's charging? (As stated above)
Hit thanks if I deserve it..
FWIW, My SPH-P100 Sprint Galaxy Tab has been an adventure as well. Enough so that I wish I'd known more and held out for a GSM model.
I am not even sure if Kies and/or Odin will in fact work with the Sprint GT. I've had almost no luck with a variety of attempts. Even the widely used ClockWorkMod Recovery does not include the Sprint GT among its list of supported devices. It does include the CDMA Verizon GT - and some folks have posted that they eventually got that to work.
I did get the SuperOneClick to work and setup root privileges on my tab. That part works fine. But so far I've been reluctant to experiment too much with the various tools that "almost appear that they should work" as I have too little experience with this Android tablet environment to feel comfortable that I can recover from the eventual disaster.
Am hopeful that Samsung will in fact follow through on their commitment to provide upgrade of all GTs to Gingerbread 2.3.3. If so that may be enough for my needs. I WOULD like to get the Netflix viewer app working. Is frustrating to already have a Netflix account and not be able to access it via my GT. A guy down the hall can get Netflix on his Droid X - which really bugs me! lol
IMHO, Google/Samsung/Motorola/HTC/etc. have done a horrible job rolling out Android - both on phones and tablets. Netflix really highlighted this when they decided to do device-by-device testing and certification before allowing Android devices access to their movies. Apparently the 'capabilities' inherent to various Android devices varies so much (and not just OS version) makes it difficult to roll out something as simple as Netflix access. It is frustrating. And the only "solution" so far is to wildly 'hack' your device in the hope that you'll shake something loose enough to make it work as you wished it had when you bought it.
Enough whining for now. But it has been a very frustrating and disappointing experience.
I installed Kies AFTER installing drivers and connecting the tablet and it has no effect. I also learned after googling that kies does not support the sprint cdma version though I could be wrong but many people have stated this. And the device does charge and does so very fast actually, 20% to 100% in 4 hours. I don't think it's trickling down as you say because it is very clearly charging at a fast pace. Thanks for the quick response though! And I have also tried superoneclick root and other methods i.e odin but neither can find the device. I know some people have had luck with this sort of thing after upgrading the rom and/or flashing firmware onto the device which I would love to try but unfortunately without windows being able to see the device, none of this is even remotely possible.
I think the reference to slow charging on USB is really refering to using a data USB port on a notebook or desktop computer. This is because the data USB ports are limited in how much current they will pass. My SPH-P100 will in fact charge on a data USB port - but very, very slowly. In fact if the device is ON it may just barely be breaking even.
The USB charger is certainly capable of charging at a very reasonable rate.
I'm still waiting on the 2.3.3 update that Samsung has promised. It only took them 5 months to get the 2.2.1 update out for my Fascinate! So maybe we'll see the 2.3.3 update by Thanksgiving...or Christmas...or...
Hi all,
I have problem with connecting my O2X to laptop.
When I connect phone to laptop phone start to charge, but USB connection is not recognized and no notification on phone (top left corner) is shown.
It was working once, but since then my phone was updated via OTA to V10e and then to V10f yesterday.
My phone is on stock.
I've seen on other forum that people had similar problem but I didn't found any solution.
I've tried different USB cables, different laptop (home and business - on both was working once before), unnistaling drivers and similar.
Please help!!!
Thank You.
I have the same problem and I still don't understand if it is hardware or software related.
In my case the usb sometimes stop working for a certain time, sometime a couple of hour, some time for a full day. After that magically start to work again.
I've tried every in my knowledge but without success.
You are not alone
Air_Mike said:
Hi all,
I have problem with connecting my O2X to laptop.
When I connect phone to laptop phone start to charge, but USB connection is not recognized and no notification on phone (top left corner) is shown.
It was working once, but since then my phone was updated via OTA to V10e and then to V10f yesterday.
My phone is on stock.
I've seen on other forum that people had similar problem but I didn't found any solution.
I've tried different USB cables, different laptop (home and business - on both was working once before), unnistaling drivers and similar.
Please help!!!
Thank You.
Click to expand...
Click to collapse
Using Topogigi 1.6 this exact thing hit me yesterday, I suddenly lost ADB-access (I was programming at the time, and suddenly couldn't upload the app to the phone anymore.) The "bug" top left had vanished, and no toggling of USB-debugging would turn it on again. I tried restoring froyo backups, tried wipe-install, didn't work. What finally solved it was to smartflash back to 10D. Very strange, I cannot find any logical reason for this behaviour, so it can only speculate it must be something illogical, like maybe overheating (wasn't overclocked.)
EDIT: Let me elaborate. When this happened I of course tried another cable, and what was extra weird was that it wouldn't even recognize a USB-connection, but it would charge. Plugging it back in the dock I normally use when programming would show a USB-connection, but no ADB. At first I was worried that perhaps the dock had pushed the pins in the socket too far in for the regular cable to get a connection. After smartflashing back to 10D though, both the dock and cable work as usual. So maybe, just maybe, a hot phone will expand certain areas around the usb-connection points either in the socket or on the motherboard. Again, just speculation. The usb-connection has worked fine since, using any cable.
Happened to me as well. In one day i can't connect my phone to the pc but after two weeks when i connected the o2x to a pc with vista the problem was vanished. I connected to my usual pc and the same it worked. let's hope that i will not have anymore this problem. It is possibility that your phone will revive i one day. good luck.
I think I may have solved this particular mystery, I'm now able to reproduce it at will, and get usb/adb functionality back.
It happens through a combination of ADB crashes/bugs on a computer and a usb-stack crash/error on the phone.
I can reproduce it by plugging in another phone/tablet on the computer (while still having the phone connected), installing/running something from eclipse on the other device, unplug and replug the o2x and then try to run/install something on it via ADB. This invariably leads to the ADB-icon (the status-bar bug-icon) disappearing, *and* it will lead to the phones USB not working on another computer, or even another port on the same computer.
Funny thing is, if I reboot the phone, and plug it back on the same computer, this instantly leads to the same behaviour. USB will only get recognized on the same port it was plugged in the last time, and ADB will still not get activated. Trying to connect to another computer *after* this will not work.
The solution is simply to reboot *both* the phone *and* the computer (or just kill adb I guess) before plugging in anything.
Plugging in the phone while *either* the PC *or* the phone is in this confused state will lead to both devices malfunctioning in the same way as before, which is why you cannot simply connect the phone to another PC. (Although unplugging the phone, rebooting it *before* plugging in to another computer should work.)
Thank You for info.
I just tried it but unfortunately it didn't work for me. I've tried restarting phone couple of times, plugin into different computers but phone still doesn't recognize usb connection (just charging).
I this the problem is in the phone and it maybe due to update to v10e and v10f.
Air_Mike said:
Thank You for info.
I just tried it but unfortunately it didn't work for me. I've tried restarting phone couple of times, plugin into different computers but phone still doesn't recognize usb connection (just charging).
I this the problem is in the phone and it maybe due to update to v10e and v10f.
Click to expand...
Click to collapse
Hm, okay, your problem may be of a different kind. I'm not entirely convinced yet, as you don't mention having rebooted any computer. So just to satisify my curiosity, do exactly these steps in the following order:
1) Unplug the phone from the computer.
2) Power down the computer
3) Power off the phone
4) Turn on your computer
5) Re-install the LG USB drivers
6) Turn on your phone
7) Connect the phone
If this doesn't work then you indeed have a completely different problem, and we're back to speculating.
TrymHansen said:
Using Topogigi 1.6 this exact thing hit me yesterday, I suddenly lost ADB-access (I was programming at the time, and suddenly couldn't upload the app to the phone anymore.) The "bug" top left had vanished, and no toggling of USB-debugging would turn it on again. I tried restoring froyo backups, tried wipe-install, didn't work. What finally solved it was to smartflash back to 10D. Very strange, I cannot find any logical reason for this behaviour, so it can only speculate it must be something illogical, like maybe overheating (wasn't overclocked.)
EDIT: Let me elaborate. When this happened I of course tried another cable, and what was extra weird was that it wouldn't even recognize a USB-connection, but it would charge. Plugging it back in the dock I normally use when programming would show a USB-connection, but no ADB. At first I was worried that perhaps the dock had pushed the pins in the socket too far in for the regular cable to get a connection. After smartflashing back to 10D though, both the dock and cable work as usual. So maybe, just maybe, a hot phone will expand certain areas around the usb-connection points either in the socket or on the motherboard. Again, just speculation. The usb-connection has worked fine since, using any cable.
Click to expand...
Click to collapse
Trym,
Does that mean you were able to smartflash despite having USB connectivity problems? I had these problems with my first O2X and after I flashed MCR I couldn't connect to USB at all. Luckily this was within the exchange period and I was given a replacement handset which hasn't had these issues but then I am still using stock 2.2
I did try all combinations of reboots on the phone and also driver installs etc on the problematic handset but nothing worked then.
mparack said:
Trym,
Does that mean you were able to smartflash despite having USB connectivity problems?
Click to expand...
Click to collapse
That's exactly what it means, yes. It's never been a hardware problem (luckily)
I had these problems with my first O2X and after I flashed MCR I couldn't connect to USB at all. Luckily this was within the exchange period and I was given a replacement handset which hasn't had these issues but then I am still using stock 2.2
I did try all combinations of reboots on the phone and also driver installs etc on the problematic handset but nothing worked then.
Click to expand...
Click to collapse
You may of course have had a genuine hardware fault, after all usb-sockets are among the first things to break on any phone. I thought my phone was a goner as well, until I discovered the things mentioned in my post. It's a really sneaky affair, it would be impossible not to assume the phone is broken the first time you experience it.
EDIT: Removed invalid assumption.
Just to report that I've tried everything, including connecting phone to computer on which my friend runs Nexus S with no problem and then connecting to computer on which my phone was never connected.
Is there easy way to revert to v10d (last version I know my usb connection worked)?
I don't want to experiment too much because this is my business phone.
Maybe I'll just wait for GB and V20e (I hope it will finally be released soon) and hope that this will resolve my problem, but until them I'm missing one of main functionality
What a waist, since I get the phone with all that fuzz about it, is nothing but problem after another: rebooting, battery drain, wifi problem, usb connection... whats next?
Air_Mike said:
Is there easy way to revert to v10d (last version I know my usb connection worked)?
Click to expand...
Click to collapse
Assuming your usb isn't actually broken, yes, it's pretty easy. Download 10D from here: http://forum.xda-developers.com/showthread.php?t=1035041
Instructions here: http://forum.xda-developers.com/showthread.php?t=1008070
NOTE: The instructions are for flashing baseband only. In addition to that, you also need to select the .bin file in "Ap bin"
Thanks, but links are broken.
Air_Mike said:
Thanks, but links are broken.
Click to expand...
Click to collapse
Indeed they are, were copied from another post I made, and XDA had truncated them.
1st one: http://forum.xda-developers.com/showthread.php?t=1035041
2nd one: http://forum.xda-developers.com/showthread.php?t=1008070 (this link is also at the bottom of the first post of the first link.)
Just to report that my USB connection suddenly stared to work again on both of my laptops (home and work).
I didn't do anything after I gave up weeks ago. Before that I've tried everything but with no success.
Air_Mike said:
Just to report that my USB connection suddenly stared to work again on both of my laptops (home and work).
I didn't do anything after I gave up weeks ago. Before that I've tried everything but with no success.
Click to expand...
Click to collapse
Weird. Glad you got it working.
Looking around on different LG Forums, as useless as they are, the support-people always gives the advice that you should take out the battery, and leave it out for five minues to "clear residual memory." (This, apparently, is the solution for any kind of problem with the phone ;-)) That's always sounded completely nuts to me, but that's the advice I'm going to give the next guy with usb problems ;-)
And another one bytes the dust.
That's ultra weird. one minute everything is just fine and on the other, USB is dead.
So, apart from the procedure TrymHansen gave us a few post back, there is no known solution/diagnose/whatever for this problem, right?
SmartFlash will not detect phone...
My post from other thread which was closed:
My optimus 2x is not detected when I plug it to my laptop via USB.
Turn on mass storage" in the phone does not appear, it's like I'm just plugging in into a wall charger.
It could connect just a few days before, same laptop, same drivers (LG mobile united drivers)
Have tried it with 3 different laptops, still can't connect (drivers are installed)
A google search reveals other people having the problem as well and unable to solve it.
Can't return it yet for warranty because superuser app is still there.
Originally, I rooted it using superoneclick. Can't unroot it in superoneclick since not detected in USB.
So i unrooted it using z4root (without a pc). It's now unrooted, however superuser app is still in the app drawer.
i believe mine can be detected from smartflash so maybe i can flash stock rom. will doing this remove superuser.apk?
fmartinezjr said:
i believe mine can be detected from smartflash so maybe i can flash stock rom. will doing this remove superuser.apk?
Click to expand...
Click to collapse
Yes it will.
So did you try to flash a stock rom and did solved your usb problem ?
I will try with a modaco rom next we.
lol, is this fixed or not?
ive had the same problem.. when my rom is totally chrashed, and usb is like stuck?
strange is, all the other usb devices (wifi dongle, not keybord mouse) stops working when i plug in my phone? also the phone does not see that there is an data cable in him so i cant mount my storage?
is this an warranty issue?
So I just updated my Bionic to ICS, YAY!
But, root isn't working, BOO! :crying:
I am relatively knowledgeable in this stuff; it is both my profession and my hobby. Investigating this issue has led me to believe that my problem is that the ADB interface does not show up in device manager (Mass Storage, MTP, and PTP mode have the same result) on Windows 7 Ultimate x64. When the device is connected in AP fastboot, however, the driver does show up and works fine. Additionally, when I try to manually add the driver, it fails to start (code 10).
What does show up, however, is the Motorola USB Networking Driver (MTP only), under network adapters.
The upgrade to ICS was performed with SamuriHL's HoB (ADB), and in an effort to resolve this issue, I did it again with HoB (Fastboot).
Can somebody please help?
Thanks,
Overkill
EDIT: I downloaded the SDK and ADB still doesn't list my device. I do know that the IP used by the Motorola driver is 192.168.137.2 for my device (.1 for my PC) and that "adb connect 192.168.137.2" fails to connect on the default port (maybe another port?)
Thanks again! I feel naked and powerless without my root =(
Do you have USB debugging enabled under Developer Options?
Yes, I do. I have tried disabling/re-enabling it as well to no avail.
I appreciate the KISS approach, but I've gone over the checklist on every how-to and I am confident that nothing is missing.
I tried the phone on another computer and with several different USB cables and no luck. I have all 64-bit machines, but I can also try my XP VM and maybe that'll behave properly ^_^ Or an actual XP machine at one of my jobsites that still won't pay to upgrade their equipment from 2002.
OverkillSD said:
Yes, I do. I have tried disabling/re-enabling it as well to no avail.
I appreciate the KISS approach, but I've gone over the checklist on every how-to and I am confident that nothing is missing.
I tried the phone on another computer and with several different USB cables and no luck. I have all 64-bit machines, but I can also try my XP VM and maybe that'll behave properly ^_^ Or an actual XP machine at one of my jobsites that still won't pay to upgrade their equipment from 2002.
Click to expand...
Click to collapse
I had this problem, reinstalling latest Motorola device manager fixed it for me.
No go on that either.
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
OverkillSD said:
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
Click to expand...
Click to collapse
You have to remember to reboot with the phone in all the different connection modes for multiple different drivers loaded.
OverkillSD said:
I gave up and did a factory restore, it's working fine now. Going to analyze the scripts used by House of Bionic and see if it's possible to work backwards and see if there was a way to do it without losing data, for posterity's sake.
Click to expand...
Click to collapse
Weird. FDR only kills user settigns and user apps - so, it seems like there was an app that was blocking ADB access. Which is extremely strange, b/c that should not happen, unless you have some sort of firewall on the BIONIC itself (or else something like DroidSheppGuard running).
beray5 said:
You have to remember to reboot with the phone in all the different connection modes for multiple different drivers loaded.
Click to expand...
Click to collapse
Not always true - you may need to reboot the phone. I can switch from any mode to any other mode and the connection pops up within 5 seconds every time. Of course, I'm running Win 7 Ult x64, and I only use the direct connect ports on my computer, no hubs, no USB 3 ports, and I never install the Motorola Device Manager software, only the direct USB drivers that I extract from the installer myself. Any one of those may be a factor in why it works for me, or some combination thereof.
However, I do know that I am not the only one for whom the switching works without rebooting either computer or phone....