I have looked at all the other problems that people have been having, but it appears that nobody else has had this, I feel like a special NooB..
Ok, coming from my Droid Eris, got the Razr last night and it has
6.11.744XT912... It is trying to update, but I havent installed it yet, most likely 748 or newer... However, I don't think this is a phone problem...
I have followed all the simple steps for Doomlord's, Zergrush... To the best of my knowledge. clicked on ADB application and it disappears so fast, I must assume it installed ADB drivers... I orginally was directed to Moto's site for their drivers and it installed 5.4 x64 drivers, have since uninstalled it and found a link with 5.2 drivers to see if that was causing it....
what happens is this... I press any key to continue and I get
--- STARTING ---
--- WAITING FOR DEVICE
The system cannot find the path specified.
And For EVERY line of code there after as well....
This is seriously getting to me now, I have the phone plugged in, in Charge Only Mode... proper debugging and unknown sources selected... but WTF?!?
Anyone have an idea? I know its gotta be something simple..
Brynn
not sure what kind of computer you have, but have you tried the 32 bit drivers?
I tried installing my Razr's 64 bit drivers the other day and couldn't get my computer to recognize it. I then remembered from modding my previous phone (Droid 1) that I needed the 32 bit drivers. Installed those and connected to my Razr no problem.
I am running Windows 7 x64, with an I7-2600k....
I can try the 32bit drivers and see if that makes a difference...
Ok, just tried it, uninstalled the 5.2 driver and took the link to Moto USB Drivers and downloaded the MotoHelper and Driver 5.4.0... It did not give me a choice of 32 or 64 bit.... I did see it install the ADB drivers too.... But atlast, still no change.....
This so makes me wish I had gotten the Nexus last night....CM9 ICS is calling me.... will feel so much better when I get something on this phone that I can use until the ICS update OS comes out.... (any ROMS available now for it? used to CM7 on my Eris..) Don't really want to start uploading apps and such until this is rooted and updated...
Possible solution
I had been having the same issue, then I found a post in a thread that stated to change the USB connection setting to Mass Storage by pulling down the notification tray after plugging the phone into your computer. Worked fine for me that way.
nope, no dice.... I have tried that in every setting within the past 16hrs... PC mode didnt help, and just tried USB Mass Storage again.... since I just reinstalled the drivers... it did install the drivers as I switched modes, but still no change....
Ok.. just so you all can hide the fact that you might just be as big a NOOB as I feel at the moment....
I have figured out why I am getting this error.... apparently my phone is already ROOTED!!!!.... I downloaded Root Explorer and Root Browser and it seems to work with no errors....
Nice Huh!
Related
I've just recently rooted my CDMA Hero using the unrevoked method and I had a lot of trouble figuring it out. I some how got the adb drivers to install on my phone (I was so annoyed by the time they installed I wasn't even paying attention when they did) but now they have disappeared (I think because I downgraded the phone to get it out of a booting screen loop) and I can't get them to re install no matter what I do. Im running on windows 7 64 bit and even when the bubble pops up and says that new drivers are installing when I go to type in
Code:
adb devices
it tells me that no internal or external paths can be found. Any tips for installing these would be greatful. I want to still use adb in the future.
Yeah nevermind. I was charging my phone via computer and an installing drivers bubble just so happened to pop up after I had been tinkering with loading themes. Figured I'd go ahead and give a shot to see if it was the drivers I needed turns out it was.
No idea what really went down but I'm glad i got adb working properly lets hope it's more permanent
basically I can't seem too root my gs2, coming from a nexus one i thought it'd be easy
Looks like a driver problem, kies is installed (and not running) but odin connects to a port and then when start is clicked it doesn't progress any further. I presume its a driver problem so was wondering if anyone could link me a set of drivers that are known to work.
might be worth a mention that kies doesn't connect to my phone either,
I found some, but they wouldn't install over what I had, and then when i uninstalled everything and started fresh, they installed and then windows updated over them.
Any help would be greatfull!
The driver install fails on the HTC MTP driver install...I cannot get by this. I am running Windows 7 64 bit...anyone else having this issue?
OMG I fought with that for HOURS. I never did get them to work. I installed htc sync, htc sync manager, and I installed the all in one kit drivers.. Nothing. Windows 7 64 bit too.
I assume you are trying to unlock the bootloader and root?
Do both things manually using fast boot commands and recovery.
Tl;dr you can root without MTP drivers
wdkingery said:
OMG I fought with that for HOURS. I never did get them to work. I installed htc sync, htc sync manager, and I installed the all in one kit drivers.. Nothing. Windows 7 64 bit too.
Click to expand...
Click to collapse
exactly like me, I have been fighting with this for two days now. Reinstalling htc sync, htc sync manager, cleaning out existing drivers reinstalling again. Removing everything that could be associated with htc at all, reinstalling android sdk etc etc.
Nothing makes my phone recogniced by ´adb devices´not even htc sync software recognice it.
Every time I plug it in, the device is recogniced and installed and it says under Portable Devices in the device manager ´HTC One X+´
Do you get the Choose type of connection screen on your phone when connecting it? Because I dont, is just says connected in debug mode, even if debug development tools is turned of and debug of. But it still doesnt show up in adb.
denne2 said:
Do you get the Choose type of connection screen on your phone when connecting it?
Click to expand...
Click to collapse
No, not on this phone.. I think it has to do with the MTP crap. You can read an informative post by Lloir in the dev section to find out more.
wdkingery said:
No, not on this phone.. I think it has to do with the MTP crap. You can read an informative post by Lloir in the dev section to find out more.
Click to expand...
Click to collapse
hmm.
went back to the store and made them try connecting the phone to one of their laptops, if course everything worked perfectly there
So now im back trying to figure out what to do. Going to find the post you mention and see if I get any hints there.
Did you notice my post above where you I claimed you can root and unlock without the drivers?
What do you need to do that you need them?
Hi,
I am reading this, it is exactly what I recognize with my new One X+ too.
BUT I am not wanting to root or something. I'd like the Navigon software to recognize my device and download the maps like it did on my Desire HD.
Any more hints to how I can get this running ?
regards,
Ruud
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
1stx2 said:
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
Click to expand...
Click to collapse
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
travisn000 said:
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
Click to expand...
Click to collapse
It's absolutely crazy isn't it? Please let me know if you figure out the problem. I don't consider myself a noob about rooting/romming/etc but this is making me feel like i just started today!
EDIT:::: I finnally got my phone to connect to my moms laptop but it still wont connect to mine. I got CASUAL to recognize the phone but I'm kind of scared to do it now since my first phone connected perfect the first time and when I started having other problems and needed to send it back and usb debugging WOULD NOT work. I don't want to leave it stock but I don't want to go through what I went through with the first phone again
Ok, I finally got my phone rooted, unlocked using casual. I had to use my moms laptop ( hp, windows 7, 32 bit ) to unlock it, our desktop ( windows xp 32 bit ) to use odin and my laptop to transfer music, vidoes, etc..... Now i absolutely hate installing drivers and windows in general. You would think being 1 of the top-of-line smartphones, **** like this wouldn't be so difficult.
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
travisn000 said:
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
Click to expand...
Click to collapse
Yep that's the same thing that happened on my windows xp based desktop, it would boot into download mode but it wouldn't recognize the phone. It's got to be a driver related issue though. I had similar issues with my gnex but that was nothing compared to this catastrophe.
Sent from my SCH-I605 using Tapatalk 2
I finally got mine done.. gave up on windows drivers and went back to linux.
I had to switch to a disto that used gksudo & dpkg in order for the CASUAL app to work properly (..my distro of choice is PCLinuxOS, but it doesn't use gksudo or dpkg).
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.