I just got a new laptop with Windows 8.1 64 bit. When I plug in my Evo LTE, nothing happens. It does not show up as new hardware and there is no trace of it in the device manager. The charge light is on, but that's it.
I've tried installing HTC sync & drivers only but I get the same results. I've dug around on this site and on the web for a couple of days before starting this thread just in case I could find something. No luck.
My phone:
Evo LTE S-Off
CM 10.2
My laptop:
Acer V5 122P
1 USB 3.0, 1 USB 2.0
I've tried plugging it into both ports with the same above results. I'm stuck.
Seems to be a common issue with 8.1. The consensus seems to be either downgrade to 8 or find a Windows 7 machine to use.
Nice avatar
Sent from my HTC EVO 4G LTE
oops. Double post.
Thanks. She's my baby.
I was afraid of that.. My Windows 7 machine has been retired. I've been reading about downgrading to 8.0 and it looks like it's a PITA as far as having to completely reset the machine.
So far everything but my phone works through the USB ports. I guess I'll just have to wait for a fix.
I spent countless hours trying to get ADB/Fastboot drivers to work on 8.1 and there was no fix.
I was able to find a fix for it!
Using a Live CD of Ubuntu and boot that. ADB/Fastboot work from there.
If you need help with that, I can guide you
Try a different USB cable - some will do charge only, others will give full access to communicate with phone.
If using an Intel chipset, go to Intel's webpage and download their USB 3.0 drivers and use those instead of Microsoft's - these are a must if trying to flash/root phone when using windows 8/USB3 drivers.
CapedCrusader said:
I spent countless hours trying to get ADB/Fastboot drivers to work on 8.1 and there was no fix.
I was able to find a fix for it!
Using a Live CD of Ubuntu and boot that. ADB/Fastboot work from there.
If you need help with that, I can guide you
Click to expand...
Click to collapse
This is my favorite solution. Ubuntu (Linux) is the bets when handling Android. Sometimes, ADB on Windows tends not to recognize devices that are booted into recovery, for example. Never a problem with Ubuntu.
I have a 32gb flash drive which I installed the complete Ubuntu package onto. So I simply boot from my USB whenever I want to use it. And this method is better than a Live CD because all of my files/settings are saved. Live CDs require setting up ADB and fastboot each time, to my knowledge. If I'm wrong, please inform me.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
aarsyl said:
This is my favorite solution. Ubuntu (Linux) is the bets when handling Android. Sometimes, ADB on Windows tends not to recognize devices that are booted into recovery, for example. Never a problem with Ubuntu.
I have a 32gb flash drive which I installed the complete Ubuntu package onto. So I simply boot from my USB whenever I want to use it. And this method is better than a Live CD because all of my files/settings are saved. Live CDs require setting up ADB and fastboot each time, to my knowledge. If I'm wrong, please inform me.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
Click to expand...
Click to collapse
How did you do this? I can't use 8.1 with fastboot. Would love to use one of my old thumb drives and try.
Download Ubuntu here:
http://www.ubuntu.com/download/desktop
Download the Live USB creator here (instructions included):
http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
Some might find my method to be a bit cumbersome, but it got the job done. I experienced a lot of problems trying to dual-boot Windows 7 & Ubuntu, so I used 2 flash drives. I used the 2gb drive as the Live USB install, rebooted using my new Ubuntu Live USB, then I installed Ubuntu onto my 32gb drive. In Windows, you might be able to run the installer, and install Ubuntu to the flash drive that way, but for some reason that I don't know, it would force me to try or install Ubuntu as my only option.
I will continue to edit this post as I find more tips, and clearer instructions.
If your win8 system only has USB 3.0 ports, try installing the intel usb3.0 drivers instead of the Microsoft ones. This is what I did to get around adb and htc sync connection issues - I have no problem connecting my win8.1 system w/intel usb3.0 drivers to communicate and flash rom's to my evo since I made the switch over. do a search and you will find all the information about intel vs. Microsoft usb drivers on this and other sites.
Related
I'm trying to use my 64-bit windows laptop to install the recently leaked ICS update on my SGH i717. Which as of now is only available as a .exe file. The problem is (confirmed by samsung tech support) that the i717 is incompatible with 64-bit windows, and isn't even recognized by my computer. Is there any way to remedy this? I do not have access to any 32-bit machines, and I really want this update!! Thankyou.
I installed the leak via the Odin exe. on my 64 bit machine with no problems.
Really? I can't even get my computer to recognize my phone, not even as usb storage. I've installed and reinstalled every driver I could find. I've even plugged it into a couple different computers. The best answer I could get was that it was because of the my windows version from the samsumg tech support woman. Is there a special driver out there or am I missing something?
mikesaull said:
I'm trying to use my 64-bit windows laptop to install the recently leaked ICS update on my SGH i717. Which as of now is only available as a .exe file. The problem is (confirmed by samsung tech support) that the i717 is incompatible with 64-bit windows, and isn't even recognized by my computer. Is there any way to remedy this? I do not have access to any 32-bit machines, and I really want this update!! Thankyou.
Click to expand...
Click to collapse
Just install dagr8's saurom ICS. It's flashable via CWM and located in dev section.
Sent from my SAMSUNG-SGH-I717 using xda premium
I don't have a problem with my 64 bit system recognizing and mounting my i717. It didn't work at first, but it turned out that my stock samsung data cable was faulty. Used a different cable and haven't had an issue since.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Well I tried a few chords. Is there any root methods that I can do from the device without a computer?
Download the latest Kies.
Let it install and make sure you select the USB drivers.
Uninstall Kies because it's ****.
Leave drivers.
Replug handset (make sure debugging is on)
This should put you in the clear mate. If it doesn't, get the Android Development Kit for the proper ADB drivers
Go to shop development, look for the pre root kernel, download USB drivers. It works, but your computer doesn't have the drivers for the phone
Sent from my SAMSUNG-SGH-I717 using XDA
Works for me on w7 64-bit as well... Don't remember doing anything special...
Sent from my SAMSUNG-SGH-I717 using XDA
Drivers
I am running Windows 7 Pro x64. No problems here.
You don't need to download kies. Just install these drivers;
http://download.cnet.com/20070905101545468-Samsung-Mobile-USB-Driver-exe/3000-18493_4-206977.html
I also installed it using 64 bit windows 7
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks everyone for your replies. I'll keep trying
That's a damn lie. I have a new 27" iMac with Windows 7 Ultimate 64-bit installed on it. I have successfully connected my Galaxy Note to the computer, every time.
There is a problem with how to get the computer to recognize your phone, that I never had with any of my HTC phones... With my HTC EVO's, all I had to do was connect my phone to a USB, and a bunch of options would automatically pop-up, asking me how I wanted to use my phone. I'd select the option to use my phone as a 'USB Storage Device,' and a few seconds later, my computer would automatically recognize my phone.
You can't seem to do it this way with Samsung phones. What you have to do, is:
MAKE SURE YOUR PHONE IS NOT ALREADY CONNECTED TO THE COMPUTER VIA USB!!! This is a must! Your computer will not recognize your phone if it's already connected BEFORE following the other steps.
Go to SETTINGS.
Select the first option (WIRELESS AND NETWORK).
Then you must select USB UTILITIES.
A screen saying "USB Mass Storage" will pop-up, and there will be a button you have to press stating, "CONNECT STORAGE TO PC."
Upon selecting "Connect Storage to PC," then and ONLY THEN, you will finally connect your phone to the USB.
If you follow these steps, after a few seconds, your computer will download any necessary drivers, and eventually it will recognize your phone. I am not sure why it's this difficult to do this on Samsung phones. Like I said, HTC phones are really simple. It doesn't matter when you connect the USB on HTC phones. Samsung, you can only connect it at a certain time. I hope this works for you.
I also run Windows 7 64 on my laptop, and have no problem with my Note. Odin, files transfers, Kies, everything works.
Steve
I used to use my old pen 4 desktop(one im typing from now) to do all my phone modding... When I bought my galaxy I thought that this machine was too sketchy and decided to use my win7 64bit xps laptop... Flawless.
Okay, so the samsung woman gave me the wrong information. Thanks Dr. Evo. I tryed your technique with no success. I haven't had any luck with anything. Could this possibly be a problem with my device? I'm considering a trip to the at&t store.
same here....
Funny... I'm now having the same issue on my laptop.... It connects fine to my 2k8 R2 x64 Server just fine. That one is an old and heavily upgraded Dell D9100 tower. I'm pretty sure I got it recognized on my ASUS U43J Bamboo laptop with Win7 Pro x64 when first got the phone. I've since reimaged and did a fresh install of the OS and drivers, and I'm certain that I reinstalled all the drivers and updates.
Tired the drivers built into KIES 2.0 - fail
Tried the USB_Driver_for_ATT_I717_Galaxy_Note_v1_3_2200_0 driver I used on my 2k8 server - fail
About to try some other drivers I found here. If something works, I'll report it...
***UPDATE***
Before trying any other drivers I decided to try one more thing...
With the phone connected via USB, shut the phone down, wait a few seconds, and turn it back on. On my laptop, PnP found three devices and installed the drivers when the phone powered on:
SAMSUNG Mobile USB Composite Device
SGH-I717
SAMSUGN Mobile USB Modem
Kies 2.0 then saw the device... still sitting there saying "Connecting..." but at least I'm one step further...
mikesaull said:
Okay, so the samsung woman gave me the wrong information. Thanks Dr. Evo. I tryed your technique with no success. I haven't had any luck with anything. Could this possibly be a problem with my device? I'm considering a trip to the at&t store.
Click to expand...
Click to collapse
I'm sorry my advice didn't help. I honestly have no idea what your issue could be. Are you still within your 30-day return window? If you were, I'd ask for a replacement phone, or if you bought your phone at an AT&T Store or BB, ask if anyone in the store has the ability to connect your phone to a laptop or computer in the store to see if they can get it to work.
For me it worked on 2 different Win 64 installs.
Here is what I did:
Install Kies. On the phone go to settings>apps>development and then check on USB debugging.
Phone connects perfectly. You can see the phone listed as a device in my computer. Clicking on it allows you to access both the USB storage and SD card.
To other poster saying you NEED to enable USB storage. You don't. It works in MTP mode.
Unplug all other usb hardware. Try another jack and cable. Don't use a hub. All virus and firewall software should be off. Log on to windows update with the phone plugged in and turned on. You might have to reboot and check again.
I have followed about every damn fastboot on Windows 8 post I can find on XDA and none of them seems to be working with this phone. adb drivers work just fine but no go on fastboot. Anyone out there have any luck getting fastboot working on Windows 8 with the DNA?
I successfully used fastboot and adb on Windows 8(64 bit). When i first plugged in the phone, and it wanted to install htc sync, i allowed it to. Then i uninstalled htc sync, but i believe it left the drivers. Adb and fastboot worked fine.
You might also check that you are using a usb2 port (not usb3) and not using a usb hub. Both have been known to cause problems with fast boot/adb
Sent from my Nexus 7 using Tapatalk 2
jasoraso said:
I successfully used fastboot and adb on Windows 8(64 bit). When i first plugged in the phone, and it wanted to install htc sync, i allowed it to. Then i uninstalled htc sync, but i believe it left the drivers. Adb and fastboot worked fine.
You might also check that you are using a usb2 port (not usb3) and not using a usb hub. Both have been known to cause problems with fast boot/adb
Click to expand...
Click to collapse
Reinstalled latest HTC Sync from their support site and switched to USB 2.0 port. Seems to be working ok now. Thanks! Can stop using the backup machine with this phone now :highfive:
mikeschuld said:
I have followed about every damn fastboot on Windows 8 post I can find on XDA and none of them seems to be working with this phone. adb drivers work just fine but no go on fastboot. Anyone out there have any luck getting fastboot working on Windows 8 with the DNA?
Click to expand...
Click to collapse
i was in the exact same position. My system runs Win8 x64 and I had my phone plugged into a USB3 port, but even when I plugged it into the only USB2 Port, it still had issues so I used my Win7 x64 Rig and it worked flawlessly.
Also make sure you don't have an app like easytether installed on the computer this if very often overlooked just disable it for the system tray in windows
Sent from my HTC6435LVW using XDA Premium App
I was able to select and install the driver directly using device manager in Windows 8. The driver file can be obtained from the drive that the DNA mounts when you plug it in USB. I used the windows 7 driver:
i.e. <MountedDrive> HTC Sync Manager:\Win7_64\androidusb.INF​
Hate to revive a old dead thread, but I guess it is better than posting a new one, so anyways on to my question, my only computer is a Microsoft Surface Pro, and it only had one USB port which is USB 3.0. In the last few months since this thread has been dead has there been any progress on a USB 3.0 driver from HTC, or here on XDA. ADB works perfectly but I can't get fastboot to install. I have the SDK installed correctly but I just can't seem to get the drivers for for fastboot to install.
androidoholic said:
Hate to revive a old dead thread, but I guess it is better than posting a new one, so anyways on to my question, my only computer is a Microsoft Surface Pro, and it only had one USB port which is USB 3.0. In the last few months since this thread has been dead has there been any progress on a USB 3.0 driver from HTC, or here on XDA. ADB works perfectly but I can't get fastboot to install. I have the SDK installed correctly but I just can't seem to get the drivers for for fastboot to install.
Click to expand...
Click to collapse
I don't have surface so i'm speculating but, just like everything else. Install htc sync to make sure that all the drivers take cleanly. Plug in your USB and
adb reboot bootloader
when your phone reboots it should say
fastboot usb.
If it does then you are good to go, just run the fastboot commands from the same folder that your platform-tools are in. fastboot flash boot boot.img
it will say sending, then working. and you should be good.
If it does not say fastboot usb, then please post back and we will do more research to figure this out.
dragonstalker said:
I don't have surface so i'm speculating but, just like everything else. Install htc sync to make sure that all the drivers take cleanly. Plug in your USB and
adb reboot bootloader
when your phone reboots it should say
fastboot usb.
If it does then you are good to go, just run the fastboot commands from the same folder that your platform-tools are in. fastboot flash boot boot.img
it will say sending, then working. and you should be good.
If it does not say fastboot usb, then please post back and we will do more research to figure this out.
Click to expand...
Click to collapse
It does say fastboot usb but none of the commands will work, no matter what I try it will always say <Waiting for device>
And I have tried it with HTC Sync installed and after uninstalling it. I seem to remember it did not play nice with some older phones but when you uninstalled it they drivers stay there, not sure if that is still the case but thought that I would try just to see.
androidoholic said:
It does say fastboot usb but none of the commands will work, no matter what I try it will always say <Waiting for device>
And I have tried it with HTC Sync installed and after uninstalling it. I seem to remember it did not play nice with some older phones but when you uninstalled it they drivers stay there, not sure if that is still the case but thought that I would try just to see.
Click to expand...
Click to collapse
I've never heard of anyone with a usb 3 succesfully doing it and i've searched the forums like crazy. The only way i was able to get it to work is cuz i have two ports and the other was a 2.0.
I mean maybe im crazy but is there some sort of an adapter than could change 3.0 to output 2.0? idk....
On a side note I loved Windows 8 for about 10 minutes then dumped it and went back to Windows 7. Just saying.. I know that's not always an option.
zone23 said:
On a side note I loved Windows 8 for about 10 minutes then dumped it and went back to Windows 7. Just saying.. I know that's not always an option.
Click to expand...
Click to collapse
Lol , I'm with you on that one. I had dual boot and windows 8 took over my whole computer and locked me out of my Ubuntu partition. Plus hate the fact that windows 8 integration is dependent on having a windows account for EVERYTHING.
dragonstalker said:
Lol , I'm with you on that one. I had dual boot and windows 8 took over my whole computer and locked me out of my Ubuntu partition. Plus hate the fact that windows 8 integration is dependent on having a windows account for EVERYTHING.
Click to expand...
Click to collapse
Well aside we are off topic anyways Windows 8 on a desktop or laptop is a piece of sh#t, but on the surface this is amazing I could not imagine anything better on a tablet. The only problems are the price and only one usb, other than that this thing is the best computer by far that I have ever owned. And I would venture to say that it's the best tablet EVER! The only thing that would make it better is if the DNA would play nice with it.
Sent from my HTC6435LVW using Tapatalk 2
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
Hey all,
I've got a One Max T6VZW running the latest NuSenseSIX and Flykernel 2.3.2, TWRP 2.8.1.
I am unlocked, S-off, but have my bootloader displaying locked (for the fingerprint scanner).
I can't recall at what point this began, probably after achieving unlocked status (I vaguely remember using ADB at the time).
I've tried to connect to Windows 7, 8.1, Ubuntu 13.13, Linux Mint, and probably openSUSE, but nothing can see my phone.
Only in fastboot is it ever even noted by Windows 7 (USB device not recognized; briefly).
I've tried HTC drivers from HTC Sync (sync uninstalled), HTC drivers standalone, and Android drivers from Squabbi's HTC One Max toolkit.
Can't be seen in Android, fastboot, bootloader, recovery, or recovery USB mass storage.
The One Max recognizes USB has been plugged in, begins charging, and allows me USB networking options, but no other options.
I've used multiple USB cables, and multiple ports (USB 3 and 2).
I think I may have put a stock (although leaked) RUU on my external SD card and installed that via the bootloader, and even that was unable to resolve the problem.
Has anyone experience this? Any solutions or ideas?
Attached is software information.
Thanks to all in advance.
griffinhaskins17 said:
Hey all,
I've got a One Max T6VZW running the latest NuSenseSIX and Flykernel 2.3.2, TWRP 2.8.1.
I am unlocked, S-off, but have my bootloader displaying locked (for the fingerprint scanner).
I can't recall at what point this began, probably after achieving unlocked status (I vaguely remember using ADB at the time).
I've tried to connect to Windows 7, 8.1, Ubuntu 13.13, Linux Mint, and probably openSUSE, but nothing can see my phone.
Only in fastboot is it ever even noted by Windows 7 (USB device not recognized; briefly).
I've tried HTC drivers from HTC Sync (sync uninstalled), HTC drivers standalone, and Android drivers from Squabbi's HTC One Max toolkit.
Can't be seen in Android, fastboot, bootloader, recovery, or recovery USB mass storage.
The One Max recognizes USB has been plugged in, begins charging, and allows me USB networking options, but no other options.
I've used multiple USB cables, and multiple ports (USB 3 and 2).
I think I may have put a stock (although leaked) RUU on my external SD card and installed that via the bootloader, and even that was unable to resolve the problem.
Has anyone experience this? Any solutions or ideas?
Attached is software information.
Thanks to all in advance.
Click to expand...
Click to collapse
This may sound stupid but is your firewall by chance blocking from drivers being installed from windows update,
I don't believe so, as I've had this issue on multiple operating systems.
I haven't had luck with Microsoft's drivers as well, and Windows Update installs them without problem.
Hope this helps !
griffinhaskins17 said:
Hey all,
I've got a One Max T6VZW running the latest NuSenseSIX and Flykernel 2.3.2, TWRP 2.8.1.
I am unlocked, S-off, but have my bootloader displaying locked (for the fingerprint scanner).
I can't recall at what point this began, probably after achieving unlocked status (I vaguely remember using ADB at the time).
I've tried to connect to Windows 7, 8.1, Ubuntu 13.13, Linux Mint, and probably openSUSE, but nothing can see my phone.
Only in fastboot is it ever even noted by Windows 7 (USB device not recognized; briefly).
I've tried HTC drivers from HTC Sync (sync uninstalled), HTC drivers standalone, and Android drivers from Squabbi's HTC One Max toolkit.
Can't be seen in Android, fastboot, bootloader, recovery, or recovery USB mass storage.
The One Max recognizes USB has been plugged in, begins charging, and allows me USB networking options, but no other options.
I've used multiple USB cables, and multiple ports (USB 3 and 2).
I think I may have put a stock (although leaked) RUU on my external SD card and installed that via the bootloader, and even that was unable to resolve the problem.
Has anyone experience this? Any solutions or ideas?
Attached is software information.
Thanks to all in advance.
Click to expand...
Click to collapse
Olrite so i guess you are dealing with the same i dealt with a while ago when i was on cayanogen mod 11 on my HTC one M7 International ... there are many alternatives to transfer stuff from phone to Laptop but first lets talk about the normal one
Method 1 which you should try is ....
* Download the HTC sync manager .. its ok if you dont wanna use it to transfer data .. just install it ...
* ok so now the important one .. make sure you have window media player installed on your computer ....
okay so why windows media player ??
Well it contains all the MTP drivers you need to connect your phone to your pc ...
* you can restart your system now .. (Optional)
* now connect your device with debugging on ... grab the notification bar click on USB related notification .. and choose MTP or something like that ...i mean don't choose HTC sync manger .. choose the other one
* Now if everything went well you will se your storage in My computer ... and in Windows media player too...
Method 2....
Well if nothing works then download an app called Air Droid ...
it have some nice functionality ...
you will get to know how to use it after installing it ...
by chance if the local link given in the app does not works make a hotspot .. connect your computer to it and open a browser like chrome .. and go to 192.168.1.1:8888
Note : port 8888 is pre configured in the app so if you changed it .. use the dirrent port you used ..
If you are not laptop is not connected with your phone's hotspot then your phone and computer should be on the same network ..
Good luck ... hit thanks if it works just to let me know
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
cq_ said:
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
Click to expand...
Click to collapse
First verify drivers are working. For whatever reason legacy composite drivers from Motorola seem to work best with this device regardless of platform or host OS. Install the Motorola Device Manager from this page and then switch drivers. No need to launch the utility.
TWRP must be at v2.7 or above for ADB support. If below 2.8.6.0 you should consider updating via fastboot assuming bootloader has been unlocked. See: https://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-3-0-0-0-t3322547
If still no joy you will have to erase/replace aboot and rebuild the device from scratch. Data loss is likely.
hmm yeah, the main problem seems to be the tablet never shows up in device manager as any device... thanks for the hints though, will try the motorola device manager drivers...
cq_ said:
Ok, I need to load an OS back to the device ( wiped data/system because girlfriend enabled encryption.....) anyway I've tried the same computer I rooted the thing 2 years ago, installed new drivers and also am in test mode, however
the hdx (when booted into TWRP) never shows up in device manager, and "adb devices" is always empty. I've tried several USB cables, and even a mac computer, anyone lose access to their device and got it back? Any hints?
Click to expand...
Click to collapse
Where'd you get the drivers from? Can you share a link to the ones you installed on your PC? In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled? What version of Windows?
I haven't tried this yet personally yet but I'm wondering if a live Linux (e.g. Mint) booted on USB thumb drive might be an option. I don't know enough about using a Mac to access the Kindle to offer much in detail there. Have you tried different USB ports on each of these computers? Do other USB devices show up okay?
fufu508 said:
Where'd you get the drivers from? Can you share a link to the ones you installed on your PC? In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled? What version of Windows?
I haven't tried this yet personally yet but I'm wondering if a live Linux (e.g. Mint) booted on USB thumb drive might be an option. I don't know enough about using a Mac to access the Kindle to offer much in detail there. Have you tried different USB ports on each of these computers? Do other USB devices show up okay?
Click to expand...
Click to collapse
Read here literally two posts above yours. Where was Linux/Mac ever mentioned? Connectivity on Windows almost always boils down to procedures, drivers and/or USB cable integrity. Assuming the device itself is not toast.
fufu508 said:
In control panel devices have you tried enabling show hidden devices to see if the tablet is detected but not enabled?
Click to expand...
Click to collapse
Oh snap, this is a good idea - will try when I get home.
TWRP 3.1.1-1, Win 10 64bit - yeah tested several usb ports on my computer - I originally rooted the HDX with this computer and windows 10 install about 2 years ago [side note do you guys remember reformatting every 6 months because windows was such a pos, I'm really glad those days are long gone!]
LOL yep Windows 10 nowadays does seem a lot more stable than the earlier stuff.
---------- Post added at 06:14 PM ---------- Previous post was at 05:50 PM ----------
Davey126 said:
Read here literally two posts above yours. Where was Linux/Mac ever mentioned? Connectivity on Windows almost always boils down to procedures, drivers and/or USB cable integrity. Assuming the device itself is not toast.
Click to expand...
Click to collapse
Hi Davey oops somehow I missed that you had already replied a few days ago . cq_ did mention a Mac computer. I suggested testing with a live Linux thumb drive boot in case they have an extra thumb drive kicking around to find out what that OS sees as compared to the Windows and Mac already tried. When reviving my Thor, part of the process I tried was draxie's 1-click, which required Linux and access to the device to do its work, so it seemed like a good to me to try to boot the PC that cq_ is using into Linux. In my case I have Linux Mint installed on a separate SATA hard drive but not everybody has that type of rig, hence the live Linux USB thumb drive boot suggestion.
fufu508 said:
Hi Davey oops somehow I missed that you had already replied a few days ago . cq_ did mention a Mac computer. I suggested testing with a live Linux thumb drive boot in case they have an extra thumb drive kicking around to find out what that OS sees as compared to the Windows and Mac already tried. When reviving my Thor, part of the process I tried was draxie's 1-click, which required Linux and access to the device to do its work, so it seemed like a good to me to try to boot the PC that cq_ is using into Linux. In my case I have Linux Mint installed on a separate SATA hard drive but not everybody has that type of rig, hence the live Linux USB thumb drive boot suggestion.
Click to expand...
Click to collapse
Fair enough; I may have been a bit harsh in my response. I now see the passing reference to an Apple rig and appreciate the unfiltered perspective often obtained via Linux. That said, there is new info on the table that suggests the OP has access to a Win10x64 box which should connect effortlessly/reliably with Moto drivers and a quality USB cable. Mucking with drivers can be a PiTA on Windows; the Moto variants remove much of the pain - although you still have to select the proper driver after tethering in the target mode (adb or fastboot) as Windows will typically default to Microsoft/stock variants which rarely work with HDX devices.