Related
Hello I did not wanted to make a new thread for this question, but I can't figure it out.. I'm preparing my phone for jcase exploit to unlock my bootloader. I did just about everything to prepare the phone except for the drivers, and the drivers are usually the easiest thing to install.
1. I have sdk installed
2. Java is up to date
3. I have set up HTC sync several times.
- my phone is on debuggin
- I have followed the steps on HTC sync page including tunrning off my antivirus
The pic is what it says everytime I try to install drivers. There is also a pic of my platform-tools. When I try locate on adb the imei is not popping up it says waiting for device. What else can I do to install my drivers.. thx
sent from my DNA
to install the drivers, install htc sync. after that you should be all set.
you can probably open up a CMD and check adb devices
if it doesnt show up try running CMD with admin rights.
donjuan08 said:
Hello I did not wanted to make a new thread for this question, but I can't figure it out.. I'm preparing my phone for jcase exploit to unlock my bootloader. I did just about everything to prepare the phone except for the drivers, and the drivers are usually the easiest thing to install.
1. I have sdk installed
2. Java is up to date
3. I have set up HTC sync several times.
- my phone is on debuggin
- I have followed the steps on HTC sync page including tunrning off my antivirus
The pic is what it says everytime I try to install drivers. There is also a pic of my platform-tools. When I try locate on adb the imei is not popping up it says waiting for device. What else can I do to install my drivers.. thx
sent from my DNA
Click to expand...
Click to collapse
You can always search on Google HTC droid dna usb drivers, There might be some defected or missing files at yours. And if that doesn't work, try on a different computer.
OK, similar situation. I went through jcases exploit without a hitch. Adb works just fine, I can see my device with adb devices command. When I go to bootloader/fastboot-usb, and try to get my unlock token from htcdev, all I get is waiting for device. The fact that adb works tells me that the drivers are installed. What am I missing?
trickster2369 said:
OK, similar situation. I went through jcases exploit without a hitch. Adb works just fine, I can see my device with adb devices command. When I go to bootloader/fastboot-usb, and try to get my unlock token from htcdev, all I get is waiting for device. The fact that adb works tells me that the drivers are installed. What am I missing?
Click to expand...
Click to collapse
When in the bootloader have you selected the fastboot option?
Sent from my rooted and debloated HTC DNA
Mazer_R said:
When in the bootloader have you selected the fastboot option?
Sent from my rooted and debloated HTC DNA
Click to expand...
Click to collapse
Yes. I did this without issue on my Rezound, but this is really starting to piss me off.
trickster2369 said:
Yes. I did this without issue on my Rezound, but this is really starting to piss me off.
Click to expand...
Click to collapse
Ok, to further help you, I'm going to need you to thoroughly walk me through the steps you're taking -- all commands you're running, what you're plugging in, everything. I don't mean to insult you're intelligence or anything, but it's probably something simple.
Mazer_R said:
Ok, to further help you, I'm going to need you to thoroughly walk me through the steps you're taking -- all commands you're running, what you're plugging in, everything. I don't mean to insult you're intelligence or anything, but it's probably something simple.
Click to expand...
Click to collapse
No worries. As I stated earlier, I went through the unlock exploit from jcase without any problems. I went to htcdev, got to the spot to enter the command to get the unlock token(already in bootloader/fastboot usb), and I get "waiting for device".
trickster2369 said:
No worries. As I stated earlier, I went through the unlock exploit from jcase without any problems. I went to htcdev, got to the spot to enter the command to get the unlock token(already in bootloader/fastboot usb), and I get "waiting for device".
Click to expand...
Click to collapse
Some diagnostics:
1) Run fastboot devices
2) Move to a USB port of another USB bus (like on another side of the computer of the furthest port away physcially)
3) Reboot and do a 'adb devices'
4) Is HTC Sync installed? I've heard it can fudge some things up. Uninstall it if it is (the drivers will remain installed).
Reason for edit: making the diagnostics more clear for future users with this problem.
Mazer_R said:
Some diagnostics:
1) Run fastboot devices
2) Move to a USB port of another USB hub (like on another side of the computer of the furthest port away physcially)
3) Reboot and do a 'adb devices'
---------- Post added at 11:48 PM ---------- Previous post was at 11:46 PM ----------
Edit: Is HTC Sync installed?
Click to expand...
Click to collapse
Man, do I feel not so smart now. I moved to another usb port, plugged, and the drivers installed. Fastboot recognized and listed my device. I don't know how many times I've heard "try another port", and it never even crossed my mind.
Thanks, from a 44 year old geek
:laugh::laugh::laugh:
trickster2369 said:
Man, do I feel not so smart now. I moved to another usb port, plugged, and the drivers installed. Fastboot recognized and listed my device. I don't know how many times I've heard "try another port", and it never even crossed my mind.
Thanks, from a 44 year old geek
:laugh::laugh::laugh:
Click to expand...
Click to collapse
That's great to hear, man! Sometimes, when you're in a lower level hardware ROM, USB connections get finicky, and swapping around which USB bus handles the connection helps. Glad to hear you're unlocked -- let us know how the unlock finishes out.
Mazer_R said:
That's great to hear, man! Sometimes, when you're in a lower level hardware ROM, USB connections get finicky, and swapping around which USB bus handles the connection helps. Glad to hear you're unlocked -- let us know how the unlock finishes out.
Click to expand...
Click to collapse
Done deal. Unlocked, ready to get loaded.
trickster2369 said:
Done deal. Unlocked, ready to get loaded.
Click to expand...
Click to collapse
Good to hear! If you have any issues in the future feel free to PM me or ask on http://chat.andirc.net:8080/?channels=#droid-dna (the guys there are very friendly and helpful.) Or, post on the forums, but that one's obvious.
My Samsung Galaxy Note II (Verizon) won't show up in Odin. I've installed the samsung drivers but its doesn't recognize the phone. I can go into download mode on my phone, but I'm stuck in a boot loop. What can I do? Any help is much appriciated
I'm having the same issue on Windows 8 64 bit. I had all drivers in place and everything worked perfect. Usb MTP and PTP, in both regular and usb debugging modes. Adb worked and Odin worked. I unlocked a Note 2 for a buddy using the updated casual (as of 5/3) method. I had issues with Casual that I could only fix by uninstalling my drivers and allowing it to install it's own. Now when I connect my rooted Note or any Note, the computer can only see the phone in Camera (PTP) WITHOUT Usb debugging on. The computer can't see it in any other mode. No adb or odin.
I've uninistalled the drivers, reinstalled them, installed Kies, used another Note 2 tool and allowed it to install the drivers. Uninstalled them and let the computer decide which drivers. Every time I get the same result. I can only see the phone in Camera mode without debugging on.
Any help would be appreciated!
Sent from my SCH-I605 using Xparent Green Tapatalk 2
I had a similar problem with my Note 2, and eventually had to use a different computer.
Sent from my SCH-I605 using xda premium
USB Debgging Mode
Yeah, I am having the a same problem. Although I rooted my i605 and had the TWRP Recover, decided to go back to stock using http://forum.xda-developers.com/showthread.php?t=2040264 . Well Verizon sent an OTA last night and I clicked update on accident, and now it is in a boot loop. I can get into download mode but odin does not see the device, I am almost positive that this is because I cannot put the device into USB Debugging Mode.
More research is need for now, but your sounds like the same thing.
twistedxj said:
Yeah, I am having the a same problem. Although I rooted my i605 and had the TWRP Recover, decided to go back to stock using http://forum.xda-developers.com/showthread.php?t=2040264 . Well Verizon sent an OTA last night and I clicked update on accident, and now it is in a boot loop. I can get into download mode but odin does not see the device, I am almost positive that this is because I cannot put the device into USB Debugging Mode.
More research is need for now, but your sounds like the same thing.
Click to expand...
Click to collapse
That has got to be the problem. Is there any way to turn on debugging mode even with a looping boot? It was on before this problem occured, but it must have been switched at some point when I tried to root.
Usb debugging and download are different modes. I've odin'ed countless times. The problem is in the drivers. I'm still tinkering but cant get them to see the device.
Sent from my SCH-I605 using Xparent Green Tapatalk 2
bennybroseph said:
That has got to be the problem. Is there any way to turn on debugging mode even with a looping boot? It was on before this problem occured, but it must have been switched at some point when I tried to root.
Click to expand...
Click to collapse
Believe me I am very new to this but extremely tech savvy, I have spent almost all of my work day searching XDA and numerous other sites and I have not found a way.
Unfortunately this is on me i know after i rooted and loaded the Jedi ROM, that I had set the updates to stop, but I guess I forgot to when I "unrooted". Oh well you live you learn, that's how I started on computers back in the day, break it and fix it all day long, lol
I've exhausted everything I can think of. I'm about ready to try my old W7 computer and if that fails, I'll go back to XP.
Sent from my SCH-I605 using Xparent Green Tapatalk 2
---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------
OP, will you update the title with "Unable to use Odin (Driver Issue)" to hopefully draw attention of a developer or someone with more knowledge. As stated, it'll quickly be dismissed as a noob problem where it is very clearly not at this point.
Sent from my SCH-I605 using Xparent Green Tapatalk 2
joshw0000 said:
Usb debugging and download are different modes. I've odin'ed countless times. The problem is in the drivers. I'm still tinkering but cant get them to see the device.
Sent from my SCH-I605 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Josh I cannot help but think that if these two do not go hand in hand then why would every instructable on this advise to first set USB Debugging Mode to On, then reboot to download mode??
Like I said I am new to this and do my research before hacking anything up, so i may be incorrect.
twistedxj said:
Josh I cannot help but think that if these two do not go hand in hand then why would every instructable on this advise to first set USB Debugging Mode to On, then reboot to download mode??
Like I said I am new to this and do my research before hacking anything up, so i may be incorrect, but I do not think so.
Click to expand...
Click to collapse
If you're using an automated program to hack your phone then usb debugging is required so it can send adb commands to the phone telling it to reboot to download mode. However, without usb debugging enabled, you can power off and manually boot to download mode and Odin will work all the same.
Most tutorials and tools are noob friendly and it's easier for them to send the "adb reboot bootloader" command then to instruct the user to do it manually.
I've been rooting since the HTC Eris so I'm no noob. I'm not a developer either but I'm 99.9% sure the problem is driver related.
Sent from my SCH-I605 using Xparent Green Tapatalk 2
joshw0000 said:
If you're using an automated program to hack your phone then usb debugging is required so it can send adb commands to the phone telling it to reboot to download mode. However, without usb debugging enabled, you can power off and manually boot to download mode and Odin will work all the same.
Most tutorials and tools are noob friendly and it's easier for them to send the "adb reboot bootloader" command then to instruct the user to do it manually.
Sent from my SCH-I605 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Interesting, thanks for schooling me! Now I am completely lost!!!
I have 2 perfectly fine Note 2's in my hand (both rooted and rom'ed) and can't get my computer to recognize either accept for in a Camera mode without usb debugging enabled.
Let's try to get a common ground here. When did everyone unlock their bootloaders? More specifically, when did you use Adam Outler's (big props to that guy) tool on your computer?
I just plugged my Note 2 in my work computer with usb debugging enabled and it sees it perfectly. So something driver related is messed up on my computer.
Sent from my SCH-I605 using Xparent Green Tapatalk 2
joshw0000 said:
I have 2 perfectly fine Note 2's in my hand (both rooted and rom'ed) and can't get my computer to recognize either accept for in a Camera mode without usb debugging enabled.
Let's try to get a common ground here. When did everyone unlock their bootloaders? More specifically, when did you use Adam Outler's (big props to that guy) tool on your computer?
I just plugged my Note 2 in my work computer with usb debugging enabled and it sees it perfectly. So something driver related is messed up on my computer.
Sent from my SCH-I605 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Actually that's why I Un-Rooted mine, I used Adams Method and the loaded the Jedi ROM, when I connected it to the pc after after a couple days it would only recognize as PTP not MTP?!? This was only with USB Debugging Mode enabled, if I turned it off it did not recognize it at all. So I decided to Un-root the device, then a week later I get the OTA and selected update and now it is dead
April 28th Rooted & ROM'ed
May 3rd Back to Stock
May 9th BRICKED
twistedxj said:
Actually that's why I Un-Rooted mine, I used Adams Method and the loaded the Jedi ROM, when I connected it to the pc after after a couple days it would only recognize as PTP not MTP?!? this was onlky with USB Debugging Mode enabled, if I turned it off it did not recognize it at all. So I decided to Un-root the device, then a week later I get the OTA and selected update and now it is dead
April 28th Rooted & ROM'ed
May 3rd Back to Stock
May 9th BRICKED
Click to expand...
Click to collapse
Thanks for the info. You're only soft bricked. We'll get the drivers straightened out. Worst case, go to another computer and you'll be back in business in no time.
Sent from my SCH-I605 using Xparent Green Tapatalk 2
joshw0000 said:
Thanks for the info. You're only soft bricked. We'll get the drivers straightened out. Worst case, go to another computer and you'll be back in business in no time.
Sent from my SCH-I605 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Sweet...... I did try my XP machine but did not think about it being a VM. I tried another computer installed the drivers and opened odin, looks like I am getting blue again. Man I have a lot to learn!
twistedxj said:
Sweet...... I did try my XP machine but did not think about it being a VM. I tried another computer installed the drivers and opened odin, looks like I am getting blue again. Man I have a lot to learn!
Click to expand...
Click to collapse
I think I just fixed the drivers on my W8 machine. Looks like we're both good.
Sent from my SCH-I605 using Xparent Green Tapatalk 2
joshw0000 said:
I think I just fixed the drivers on my W8 machine. Looks like we're both good.
Sent from my SCH-I605 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
That's great, now what about the OP?
twistedxj said:
That's great, now what about the OP?
Click to expand...
Click to collapse
Where is he? The issue is probably with the driver. He can connect and go to device manager. He'll have to open up some of the universal serial bus and see what the computer recognizes the phone as. If you can't tell, unplug it and see which on the list goes away. Re-plug if it comes back, update drivers with the Samsung drivers. That should put him back in business (you too).
Sent from my SCH-I605 using Xparent Green Tapatalk 2
twistedxj said:
Yeah, I am having the a same problem. Although I rooted my i605 and had the TWRP Recover, decided to go back to stock using http://forum.xda-developers.com/showthread.php?t=2040264 . Well Verizon sent an OTA last night and I clicked update on accident, and now it is in a boot loop. I can get into download mode but odin does not see the device, I am almost positive that this is because I cannot put the device into USB Debugging Mode.
More research is need for now, but your sounds like the same thing.
Click to expand...
Click to collapse
joshw0000 said:
Where is he? The issue is probably with the driver. He can connect and go to device manager. He'll have to open up some of the universal serial bus and see what the computer recognizes the phone as. If you can't tell, unplug it and see which on the list goes away. Re-plug if it comes back, update drivers with the Samsung drivers. That should put him back in business (you too).
Sent from my SCH-I605 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
It recognizes it as Samsung Android Device. I've already re-installed the Samsung drivers several times.
bennybroseph said:
It recognizes it as Samsung Android Device. I've already re-installed the Samsung drivers several times.
Click to expand...
Click to collapse
And you're in Odin? It should be a Samsung Composite or Fastboot Device or something of that nature. I don't think it should see your phone as a phone in Odin. Have you tried changing the drivers or just uninstalling/reinstalling?
Sent from my SCH-I605 using Xparent Green Tapatalk 2
So im trying to root my new s4 and after installing the latest Samsung drivers adb will not find my s4 or s3, and odin same thing. Ive updated sdk and not sure where to go from this point... Any ideas?
Sent from my SCH-I545 using Tapatalk 2
abalsor said:
So im trying to root my new s4 and after installing the latest Samsung drivers adb will not find my s4 or s3, and odin same thing. Ive updated sdk and not sure where to go from this point... Any ideas?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I'll assume that you have also enabled USB debugging (just want to ensure )
try
Code:
adb kill-server
if that doesn't work if you hadn't already rebooted I would try that.
if that didn't work try another usb port/cable
[email protected] said:
I'll assume that you have also enabled USB debugging (just want to ensure )
try
Code:
adb kill-server
if that doesn't work if you hadn't already rebooted I would try that.
if that didn't work try another usb port/cable
Click to expand...
Click to collapse
Usb debugging is on, have tried reboots.. Found it curious that both the s3 and s4 would do the same thing...
Sent from my SCH-I545 using Tapatalk 2
abalsor said:
Usb debugging is on, have tried reboots.. Found it curious that both the s3 and s4 would do the same thing...
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
did you un-check "Verify Apps" under Security?
yyhd said:
did you un-check "Verify Apps" under Security?
Click to expand...
Click to collapse
All directions in the root thread followed perfectly... All settings are right...
Sent from my SCH-I545 using Tapatalk 2
abalsor said:
All directions in the root thread followed perfectly... All settings are right...
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
hmm...im not sure. i actually had a similar issue with an AT&T S4 last week, and i also couldnt figure it out. however, i returned the device for other reasons.
I would try another USB cable if possible. In the past I have had issues with Samsung phones regarding data connectivity either adb/odin.
[email protected] said:
I would try another USB cable if possible. In the past I have had issues with Samsung phones regarding data connectivity either adb/odin.
Click to expand...
Click to collapse
i have never had any problems with any USB cable i've used, but it doesnt hurt to give it a try. Maybe you'll find it is the cable's problem.
Are you using USB 3.0 ports? I tried on my new desktop and ODIN wouldn't find my phone, but I used it on my Windows 8 laptops with USB 2.0 and it worked fine.
I've tried multiple cords, and different ports.. Going to try a different computer tomorrow...
Sent from my SCH-I545 using Tapatalk 2
abalsor said:
I've tried multiple cords, and different ports.. Going to try a different computer tomorrow...
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Any luck with a different computer?
Sent from my Verizon S4 using Tapatalk 2
yyhd said:
Any luck with a different computer?
Sent from my Verizon S4 using Tapatalk 2
Click to expand...
Click to collapse
Did have success using another computer... Going to have to tear down the desktop and figure out what's going on
Sent from my SCH-I545 using Tapatalk 2
abalsor said:
Did have success using another computer... Going to have to tear down the desktop and figure out what's going on
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
i had a problem with a driver just going kapoot on my recently. i tried uninstalling and reinstalling, still no good. i removed all other drivers and software that i thought may be related to the problem, but the problem still persisted.
in the end, i just backed up all my important data to an external HDD and did a complete restore of Windows 7. All my problems were gone. I'm not saying this is what you should do or that this is your only options, but what I am saying is you could always restore to this.
yyhd said:
i had a problem with a driver just going kapoot on my recently. i tried uninstalling and reinstalling, still no good. i removed all other drivers and software that i thought may be related to the problem, but the problem still persisted.
in the end, i just backed up all my important data to an external HDD and did a complete restore of Windows 7. All my problems were gone. I'm not saying this is what you should do or that this is your only options, but what I am saying is you could always restore to this.
Click to expand...
Click to collapse
I've tried the same route with no success.. So i will be re-installing windows today. Wish they had a linux verison of the root, would make like life easier lol...
abalsor said:
I've tried the same route with no success.. So i will be re-installing windows today. Wish they had a linux verison of the root, would make like life easier lol...
Click to expand...
Click to collapse
I had the same issue and found that after plugging into my laptop where I initially rooted, the phone wanted me to allow USB debugging from my desktop; perhaps I had never done so in the first place...
Anyway, long press on home button and see if maybe you just need to find the notification, as I understand it can get buried under everything and not pop up...
Other than that, I'm not sure what to tell you. Maybe try the universal ADB driver from the folks at CWM?
OverkillSD said:
I had the same issue and found that after plugging into my laptop where I initially rooted, the phone wanted me to allow USB debugging from my desktop; perhaps I had never done so in the first place...
Anyway, long press on home button and see if maybe you just need to find the notification, as I understand it can get buried under everything and not pop up...
Other than that, I'm not sure what to tell you. Maybe try the universal ADB driver from the folks at CWM?
Click to expand...
Click to collapse
Yea , when I plugged into my lappy running Ubuntu 13.04 it popped up to allow for it access the computer. Not sure if my drivers are completely screwed up so doing a fresh install..
abalsor said:
Yea , when I plugged into my lappy running Ubuntu 13.04 it popped up to allow for it access the computer. Not sure if my drivers are completely screwed up so doing a fresh install..
Click to expand...
Click to collapse
When I went to my DT after lappy, the popup appeared and let me solve the whole not-being-seen problem. Have you tried it since you used lappy?
Also, remove all your samsung drivers and try the universal adb driver from CWM.
OverkillSD said:
When I went to my DT after lappy, the popup appeared and let me solve the whole not-being-seen problem. Have you tried it since you used lappy?
Also, remove all your samsung drivers and try the universal adb driver from CWM.
Click to expand...
Click to collapse
I had reinstalled all samsung drivers, trying the universal adb driver now.. I thought that was for windows 8 only but we shall see...
*edit- installed and reinstalled all drivers, with no luck...
abalsor said:
I had reinstalled all samsung drivers, trying the universal adb driver now.. I thought that was for windows 8 only but we shall see...
Click to expand...
Click to collapse
if that doesn't work, post a screenshot of your Windows Device Manager, and the Properties window of the Samsung device
OverkillSD said:
if that doesn't work, post a screenshot of your Windows Device Manager, and the Properties window of the Samsung device
Click to expand...
Click to collapse
https://docs.google.com/file/d/0ByJe0XtTYosZeXczb2tBOEVKdTA/edit?usp=sharing
edit- made public
hey there. So I have an AT&T X+ and I'm currently on Elegancia 5.2 I believe. I was wondering if I should just go back to stock and wait for the OTA 4.2.2 update, or flash the newest Elegancia ROM? But, I kinda have a handicap:
My phone doesn't connect to my PC or any PC at all. So if I'm going to flash a Rom I gotta put it on drop box and transfer it etc. I will NOT be able to flash a boot.img because of this either. I've tried the app Flashify, and it says it isn't compatible with my device. So if any of these roms have a custom boot.img I probably won't be able to use it.
Another thing. I feel like I know what the problem is with my device. It says that USB storage is unavailable at all times. Even when it is plugged in. If anyone knows a fix for this please don't be afraid to speak up.
Thanks guys!
Sent from my HTC One X+
Bump...Advice anyone?
Sent from my HTC One X+
poojiggles7 said:
Bump...Advice anyone?
Sent from my HTC One X+
Click to expand...
Click to collapse
What so u mean by the Phone wont connect.....
Its shows as USB device Unrecognized like this
or
The PC wont recognize ur Phone how is it...??????(like the ADB or fastboot wont show ur device)
[email protected] said:
What so u mean by the Phone wont connect.....
Its shows as USB device Unrecognized like this
or
The PC wont recognize ur Phone how is it...??????(like the ADB or fastboot wont show ur device)
Click to expand...
Click to collapse
the phone doesnt even appear as a USB device. nothing pops up, it makes no sound when it connects, nothing, just charges.
poojiggles7 said:
the phone doesnt even appear as a USB device. nothing pops up, it makes no sound when it connects, nothing, just charges.
Click to expand...
Click to collapse
Did u try Installing proper drivers and android-sdk-windows........????
To start with the Latest drivers and the ADB setup should be proper and even after that if that doesn't show then....
Open device Manager in Windows an see whether atleast it has been shown as Unknown device or something there.....
I tried all that and nothing. I've had this problem for the past month and every bit of troubleshooting I've done with ATT, HTC and xda hasn't worked. In the photo attached, my phone is plugged in to the PC and it still says usb storage unavailable.
Sent from my HTC One X+
poojiggles7 said:
I tried all that and nothing. I've had this problem for the past month and every bit of troubleshooting I've done with ATT, HTC and xda hasn't worked. In the photo attached, my phone is plugged in to the PC and it still says usb storage unavailable.
Sent from my HTC One X+
Click to expand...
Click to collapse
I dont think thats the issue at all...
If I am not wrong I remember its was the same with my phone also...(WITH all HOX+)
the Problem is AFAIK is the HTC drivers .....
Uninstall all the drivers u had installed and try this
and check whether the phone is recognized....
[email protected] said:
I dont think thats the issue at all...
If I am not wrong I remember its was the same with my phone also...(WITH all HOX+)
the Problem is AFAIK is the HTC drivers .....
Uninstall all the drivers u had installed and try this
and check whether the phone is recognized....
Click to expand...
Click to collapse
alright ill give that a shot...should i try the link you gave, or the link for the newer version?
poojiggles7 said:
alright ill give that a shot...should i try the link you gave, or the link for the newer version?
Click to expand...
Click to collapse
Try the Latest version I couldnt find the proper one for you sorry.....
[email protected] said:
Try the Latest version I couldnt find the proper one for you sorry.....
Click to expand...
Click to collapse
I tried it and nothing happened. I executed the driver .exes and downloaded the correct zip for my PC, and still no progress...
i had something like this on my hox, try to connect it in different modes (recovery, hboot, FASTBOOT) and type "adb devices" mby it will find it
Hmm.. I've had this problem too... Try using a different USB cable, (imo) samsung cables work perfectly
Sent from my GT-S5360 using xda app-developers app
a day after i rooted and flashed a rom on my l9, it just died, idk how. can't get into any kind of "mode". the strange thing is when i connect is via usb it tries to connect but a dialog box comes up in the bottom right saying "USB device not recognized" it makes the connect/disconnect sound over and over until i unplug it. Device manager doesn't show anything, it just keeps refreshing because the device is attempting to connect. I've tied different cables and different ports also, and no luck.
any help will be greatly appreciated, thanks
hachem28 said:
a day after i rooted and flashed a rom on my l9, it just died, idk how. can't get into any kind of "mode". the strange thing is when i connect is via usb it tries to connect but a dialog box comes up in the bottom right saying "USB device not recognized" it makes the connect/disconnect sound over and over until i unplug it. Device manager doesn't show anything, it just keeps refreshing because the device is attempting to connect. I've tied different cables and different ports also, and no luck.
any help will be greatly appreciated, thanks
Click to expand...
Click to collapse
Adb drivers? have you installed them?
kishandoshi said:
Adb drivers? have you installed them?
Click to expand...
Click to collapse
well i installed the original l9 drivers, is there specific adb drivers for it?
hachem28 said:
well i installed the original l9 drivers, is there specific adb drivers for it?
Click to expand...
Click to collapse
may b. well my story is. i had bricked my phone. installed the universal adb drivers as my phone doesnt have any driver released by company. and i did restored and flashed stock rom. hope it works for you.
kishandoshi said:
may b. well my story is. i had bricked my phone. installed the universal adb drivers as my phone doesnt have any driver released by company. and i did restored and flashed stock rom. hope it works for you.
Click to expand...
Click to collapse
Do you happen to have a link for the universal adb drivers?
hachem28 said:
Do you happen to have a link for the universal adb drivers?
Click to expand...
Click to collapse
adbdriver.com
hachem28 said:
Do you happen to have a link for the universal adb drivers?
Click to expand...
Click to collapse
More than likely your device is malfunctioned.
Sent from my LGMS769 using XDA Premium 4 mobile app