Related
These are the steps i used to set up my drive(may not work for everyone dont see why though)
I don't include a step for installing HTC Sync and its drivers as ADB only worked for me when the phone was on and in sync mode, also because the pdanet install wrote over them when i installed
1.Download pdanet for android Here(this will install the proper drivers)
2.Install Pdanet on comp no need for it on phone so if it fails dont worry. Have phone plugged in during install
3.Boot into hboot(vol dwn+power)
4.Boot into recovery(vol up+power to see menu)
5.Unplug phone then plug it back in
Make sure you have debugger on before going into recovery
Now you should see your device as Recovery when you adb devices in command.
If you see 2 devices try disabling(not unmounting) your usb mass storage and then upluggin and plugin the phone back in
I really appreciate it but...
Well i woke up this morning to this new thread, tried your EXACT 5 steps with deleting all traces of the old HTC SYNC drivers and software. Still a no go. The device STILL shows up twice and then disappears. Also disabled through DEVICE MANAGER the MY TOUCH SLIDE USB MOUNT. Unplugging and plugging back in does NOTHING. I am so sick of this it hurts. FOR THE LOVE OF ROOT PLEASE HELP ME TO FIND AN ACTUAL SOLUTION.
According to another person in the forum, another couple of steps need to be added here.
check the #3 post of the other adb thread for more details (I can't link yet :-( )
After installing the pdanet: install htc sync, download the sdk, then install latest drivers.
Then continue with the rest of the process
I haven't had a chance to try it, but thought I would share to see if it will help.
If it helps, we should prolly amend the first post here.
thecracker said:
According to another person in the forum, another couple of steps need to be added here.
check the #3 post of the other adb thread for more details (I can't link yet :-( )
After installing the pdanet: install htc sync, download the sdk, then install latest drivers.
Then continue with the rest of the process
I haven't had a chance to try it, but thought I would share to see if it will help.
If it helps, we should prolly amend the first post here.
Click to expand...
Click to collapse
I believe you're talking about me. I would just point out that I was listing what I did, not nec the steps needed to get the phone to show up in adb devices. Its not clear you need to install pdanet or htc sync.
Both of those drivers let me see the phone in adb devices when it was on, let me issue commands like adb reboot recovery. But neither of those drivers ever had the phone show up except for briefly after clicking recovery from hboot and going away once the recovery triangle showed up.
Finally when I removed all traces of the device driver and installed the (r3) driver from the sdk. The next time I tried it, it worked out for me.
I think a lot of people are misreading the steps or being ham-fisted in their approach. This method is as much an art as it is a science at this point.
seek and you shall achieve.
- faylix / local
Mytouch slide rooted Eugene's Update-1
I'm sry, i was just trying to make sure that any successful attempts were communicated.
I hope i didn't cause more harm then good
dsamuels39 said:
Well i woke up this morning to this new thread, tried your EXACT 5 steps with deleting all traces of the old HTC SYNC drivers and software. Still a no go. The device STILL shows up twice and then disappears. Also disabled through DEVICE MANAGER the MY TOUCH SLIDE USB MOUNT. Unplugging and plugging back in does NOTHING. I am so sick of this it hurts. FOR THE LOVE OF ROOT PLEASE HELP ME TO FIND AN ACTUAL SOLUTION.
Click to expand...
Click to collapse
I did the same thing you did and had the same problems you had. I went to try it on my laptop which is windows vista 64bit (pc is w7 64bit). I was still having the same problem, not detecting anything and it would show up twice or three times then disappear. I installed sync that comes stock with the SD card (I had sync from the HD2 installed). I already had PDANET installed on my laptop. Anyways having doing the same thing over and over which seemed to be half a million times it all the sudden worked. So it will "catch" sooner or later. Just keep doing it. As long as you have the proper sync installed and you dont have an error with you android 1 in the device manager then it will work sooner or later. I know its a MOFO, I've been doing it for 2 days stright now and just barly got it rooted.
Good Luck.
alas it was a no go for me
I havent changed anything with my ADB since it was setup for my G1 and I can still find the device and enter commands like "reboot". Does this mean that my ADB is setup correctly for my Slide?
I've attempted to install drivers, but it still isn't recognized by fastboot, kindle fire utility, and everything else. I reconnect it to my computer and it just comes up as "Unknown usb device"... It came to be this way because while I was installing TWRP with Kindle fire utility it froze and it's been like that for at least 30 minutes now. I've tried restarting it, resetting it, and nothing is working. Please help!
Look here http://forum.xda-developers.com/showthread.php?t=1417966
You maybe need to change boot mode to normal
Sent from my Kindle Fire using Tapatalk
But how do I manage to change the bootmode when my computer won't recognize that my kindle is connected?
Sent from my MB525 using XDA App
Follow the instructions posted by me, there and then your device should be recognized....
Sent from my Kindle Fire using Tapatalk
http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
Had the same issue. This solution worked for me
guillotinedream said:
http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
Had the same issue. This solution worked for me
Click to expand...
Click to collapse
I love you. No homo, of course. Thanks a ton! This worked great for me. I thought that my kindle was screwed Thanks so much for that!
lol You're welcome. Glad it worked for you
Computer doesn't even recognize that a device is connected...
Okay, I'm not having the same issue, but I'm pretty sure I've completely, irevicalbly, bricked my kindle.
I know that I'm not in Fastboot mode, I've experienced that issue and solved it with the KFU.
Here's what I did:
I used the KFU to root my kindle. That worked fine. I was able to load all the Google apps (which was my initial goal). Then, I got greedy and decided that ICS was my next step - oops.
I followed the instructions on the following site:
androidauthority.com/kindle-fire-miui-4-ics-55853/
Note: I know, I'm an idiot - I should have paid attention to comments! UGH!
After I did this, I now only get the firefirefire logo and that is it. I can't load/reload TWRP and I can't change my bootmode to normal or recovery. The thing is, no matter which computer I plug the device into, the computer won't recognize the device. I get a message saying something "malfunctioned" when I plug it in. I've tried 3 different Windows machines (I've installed/reinstalled drivers I don't know how many times!) and I even tried loading Linux on a spare laptop and that didn't work either.
So, I tried the next thing I could think of. I followed the instructions on the following site:
ramble.karrth.com - Section "Troubleshooting TWRP
which involved removing the back cover, shorting a circuit (to force usbboot) and plugging my Kindle in. This didn't work for me either.
At this point, I'm willing to try anything. I'm not quite sure how to fix this issue. I think my next step is to either order a factory cable or make my own and try that, but if my bootloader is broke (truely broke) will that even work?
Please, if I should post this in another forum/place, just let me know. Any help appreciated!
I should also not that nothing comes up in my device manager. It does come up as a unrecognized USB bit goes away after telling me there was a malfunction (it tries to recognize it twice).
Please don't post the same question in multiple threads... especially ones that have been dead for 4 months. I've replied to the same question as a followup to your other post.
I'm trying to root a Kindle Fire and I don't know why but I'm having alot of trouble getting ADB and drivers set up right on my laptop. I'm not sure which packages I need to install in SDK manager. When I try to use the adb command at a command prompt it says command not recognized and I'm thinking it's because I don't have the right packages installed or installed right.I didn't have to go through this when rooting a couple other phones I've done.
http://forum.xda-developers.com/showthread.php?t=1399889
Thanks so much for the link. I ran it and I'm having a hard time getting it to recognize the device. It said it installed the correct drivers but when I attempt the temp root it will not recognize the device, make sure device is plugged in and turned on.
With kindle unplugged Go into ur comps device manager and remove the kindle fire...then install drivers. Then plug it back in. I had same problem. Windows auto installed some generic driver when I first plugged it in before installing correct driver. If still not working try a diff usb port on computer. Hope that helps
I finally got it. Thanks very much. I finally had to switch computers for some reason to get it to work.
It seems like I go through this every damn time I get a new Android device, so you'd think I'd have figured it out by now, but I haven't.
How the heck to I get ADB working for this device? It's not being recognized by the "adb devices" command right now. As far as I know, I've got the drivers installed (at least, I could communicate via fastboot). I don't know what else I need to do, and would appreciate any help.
How did you get install the drivers? If you haven't done so, you can just grab the drivers from here: http://forum.xda-developers.com/showthread.php?t=1992345
Stryder5 said:
How did you get install the drivers? If you haven't done so, you can just grab the drivers from here: http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
Yes, that's where I got the drivers (and that's how I got fastboot working).
I've taken the drastic step now of uninstalling the entire SDK thing and am currently re-installing it. We'll see how that goes.
EDIT: yeah, "adb devices" still gives nothing at all.
You need to turn it on first but Developer Options are hidden in Settings. Go into About phone and tap the build version. After 7 times you will have access and you can turn on USB Debugging
chinly43 said:
It seems like I go through this every damn time I get a new Android device, so you'd think I'd have figured it out by now, but I haven't.
How the heck to I get ADB working for this device? It's not being recognized by the "adb devices" command right now. As far as I know, I've got the drivers installed (at least, I could communicate via fastboot). I don't know what else I need to do, and would appreciate any help.
Click to expand...
Click to collapse
do you have usb debugging on? its under development under settings. to make it appear, you need to press the about phone 7 times or so. http://www.androidcentral.com/how-enable-developer-settings-android-42
^^what the user said above. he beat me to it
0.0 said:
do you have usb debugging on? its under development under settings. to make it appear, you need to press the about phone 7 times or so. http://www.androidcentral.com/how-enable-developer-settings-android-42
^^what the user said above. he beat me to it
Click to expand...
Click to collapse
While this was, admittedly, once my problem back in the early days of android, it's not the problem this time. USB debugging is on.
EDIT: I've also reconfirmed that fastboot is still working after the whole re-installation thing.
Anyone have any other ideas? Is it correct that when I plug the phone in, it's detected add an MTP device?
chinly43 said:
Anyone have any other ideas? Is it correct that when I plug the phone in, it's detected add an MTP device?
Click to expand...
Click to collapse
thats very odd...perhaps run the android sdk and check for any updates for the drivers and whatever else is needed
0.0 said:
thats very odd...perhaps run the android sdk and check for any updates for the drivers and whatever else is needed
Click to expand...
Click to collapse
That's all I can suggest as well, although I can't see what the issue could be
Yer try installing the SDK and downloading the "Google USB Drivers" from there to see if it helps.
Sent from my Nexus 4 using Tapatalk 2
Here try this. It's from the sdk. I just zipped it. https://www.box.com/shared/7sutkummukh4pup0rwoi
Sent from my Nexus 7 using Tapatalk 2
You can just get the windows executable from Google, r21
http://dl.google.com/android/installer_r21-windows.exe
Thanks, everyone who's been reading/trying to help. Unfortunately, it's still not working.
People suggesting the .exe installer - that's how I've installed it each time. Twice now I've uninstalled/reinstalled the SDK. When installing, I choose the SDK tools, SDK platform tools, the 4.2 API (which is probably unnecessary, right?), and the Google USB driver. Each time, ADB has worked *in general*, but will not recognize this device (via the "adb devices" command).
Here's how things are going right now. When I first plug the phone in (with debugging on), if it's not currently installed as a device then it automatically self-installs and shows up as an "mtp" device. I try ADB, doesn't work. I then go in and manually install the drivers found in various places around this board. When I do this, it no longer appears as MTP. This is weird, though, and I didn't notice this last night - when I look at the list of devices in Device Manager in Windows, the category it falls into is "ASUS Android Devices", under which it's listed as "Android Composite ADB Interface", and it still doesn't work.
Something seems wrong about it being listed as ASUS, though. I wonder if all these current difficulties are a result of the problems I had getting my Transformer Prime to work with ADB? If anyone sees anything above that looks like I'm doing something wrong, let me know; I think the next thing I'm going to try is doing this whole process on a fresh computer here at work that's never been exposed to android at all, see how that goes. I'll check back in after I do that.
Have you tried these drivers?...
http://forum.xda-developers.com/showthread.php?t=1992345
EddyOS said:
Have you tried these drivers?...
http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
I have, and it still doesn't work on my laptop. However...
It's working! On a shared computed at work that had never had *anything* android-related installed before. Went through the same procedure I did on my own computer, so the problem is with my laptop, I guess. Which I'm more okay with than it being a problem with the phone. I guess I need to more thoroughly remove everything from the laptop, maybe?
An update:
I DO. NOT. UNDERSTAND. why this worked; I haven't changed the drivers or anything on the laptop itself. On a whim, I changed the device type on the N4 from "media device" to "PTP device" and suddenly ADB is recognizing it on the computer where it's never worked. Should I have expected that?
chinly43 said:
An update:
I DO. NOT. UNDERSTAND. why this worked; I haven't changed the drivers or anything on the laptop itself. On a whim, I changed the device type on the N4 from "media device" to "PTP device" and suddenly ADB is recognizing it on the computer where it's never worked. Should I have expected that?
Click to expand...
Click to collapse
I have to do that to my Nexus 7 before ADB will recognize it, so you're not alone there.
Just curious, what brand phone did you have before? If it was a samsung and you had all the samsung drivers and what not installed still, this could be causing the problem. My cousin couldn't get adb to recognize his device and we finally discovered the samsung software was conflicting in someway. He uninstalled it all and adb worked like a charm.
I had the same problem, here's what you need to do. When you plug it in, change the settings from MTP to Camera for USB settings. I don't know why, but you need to do it.
dcarpenter85 said:
Just curious, what brand phone did you have before? If it was a samsung and you had all the samsung drivers and what not installed still, this could be causing the problem. My cousin couldn't get adb to recognize his device and we finally discovered the samsung software was conflicting in someway. He uninstalled it all and adb worked like a charm.
Click to expand...
Click to collapse
I've got four other android devices that all worked (simultaneously, at that): T-Mobile/HTC G1, Nook Color, T-Mobile/HTC G2, and an Asus Transformer Prime.
Hi, been lurking around here for a good while now....fantastic website website and I've learned so much but now I have an issue.
For what ever reason my nexus 7 will not boot, I can get into fastboot and have been following the guides to do a full factory restore through fastboot. Everything goes fine until is comes to "Sending System" then just.....stops. I have used the nexus toolkit and also the official sdk drivers and fastboot contained there. I only have an old laptop as my main pc for some reason does not recognise the nexus.
I have tried alternative USB cable too.
Does anyone have any other advice.
Also the device is complete stock no custom rom has been installed so no custom recovery available.
I really appreciate any help.
Cheers!
Okay well ive managed to get it back alive!
used a new laptop and usb cable and it all seems to be fine now!
Now back to my original issue...windows 8 is pissing me around and wont recognise the bloody thing!
Any ideas?
Try a search, shouldn't be hard to find what others have done with Windows 8 difficulties...
singlemanriot said:
Okay well ive managed to get it back alive!
used a new laptop and usb cable and it all seems to be fine now!
Now back to my original issue...windows 8 is pissing me around and wont recognise the bloody thing!
Any ideas?
Click to expand...
Click to collapse
Go to Device Manager, show hidden devices and uninstall any Android or ADB related devices that you have. Disable USB debugging on your Nexus, then plug it into your PC and see if it's recognized. If it is, then re- enable USB debugging, then go to Device Manager and reinstall the Google USB drivers to get ADB support back.
Thanks for the advice, first thing I did was try searching....I have tried countless methods suggested but nothing works its like windows cant find the drivers. In the device manger its recognised but no diver installs no matter what I do. If I force the manual driver install it fails!? I have tried the Naked drivers, the SDK even making sure the media components of windows are installed properly