Hello,
First of all, the problem started when Android Kitkat update ota came to my device. After downloading it, my device was not able to verify it, as a result of which, it started downloading the update all over again. It downloaded the update more than 10 times without any success.
So finally I decided to sideload it. I set up everything properly, double checked everything. As I was going to send the update.zip to my tablet through command, the cmd prompt showed me "error: device not found".
I restarted the device, checked the drivers in my computer, even checked whether adb recognized it by commanding "adb devices". It did.
So again I turned it off, entered fastboot mode, But this time before entering recovery, I connected the device (it gave the connecting sound as on Win7). I ran the command "adb devices" and it showed no device at all!
My device is complete stock, unrooted. Usb debugging is turned on and MTP is selected.
Use a toolkit to install\test adb drivers then slide load using it. Some times windows install some crap adb drivers u have to remove them and install the naked drivers.
Toolkit is in development section.
I tested with wugfresh toolkit.
Please ignore my spelling mistakes. English is not my native language.
Related
First let me get the stats out of the way in case it's a compatibility issue (doubtful):
Mytouch 3g 32b
Hboot 1.33.2005
Radio 2.22.23.02
Running on the last cm6 nightly (307, i believe)
Using this kernel: http://droidbasement.com/db-blog/?p=1531
All flashed through recovery.
Ok, so the problem..
Following this guide, http://forum.xda-developers.com/showthread.php?t=532719, I successfully got the ADB to work properly (calling "adb devices" on a terminal returns my device). However when I boot the phone into fastboot, connect it to the PC via USB and call "fastboot devices" through the terminal (yes, I first cd to the android-sdk/tools folder), it returns nothing. Calling something like "fastboot reboot" simply returns "<waiting on device>" indefinitely.
I googled for HOURS last night searching for a solution but to no avail. I uninstalled the drivers via the Device Manager and tried the PDANet method, but nope. Uninstalled drivers again, rebooted everything, and reinstalled using the method posted in the above guide again, pointing it to the google/usb_drivers folder, just in case I had f*'d up somewhere along the way. I just ended up with the same problem. ADB works. Fastboot doesn't. What am I doing wrong? :/
Basically, I'm stumped. While it's not completely necessary to get this working, I'd like to free up some ram on my phone (http://forum.xda-developers.com/showthread.php?t=831139) and for this I need fastboot. I'm not that noobish so I'm willing to experiment. Any help is appreciated.
Nobody? :/
Thanks to my persistence I finally got it working. I'll share in case anyone else has the same problem.
Apparently there were still old HTC related devices under the Device Manager that would not show even when I clicked on "Show hidden devices." I fixed this by adding a new system variable.
Variable name: devmgr_show_nonpresent_devices
Variable value: 1
This allowed me to see a bunch of HTC labeled grayed out devices under 'Disk drives' and under 'Universal Serial Bus controllers,' some grayed out USB Mass Storage Devices and one USB Composite device which I believe was also a culprit. Uninstalled all of them.
I then restarted the process of setting up ADB using these drivers, mediafire.com/?wzdjcmowziw, which I got from the guide I link to in the first post. Then when I hooked up the phone to the PC under fastboot mode, I used the drivers supplied by PDANet. Worked immediately.
Thanks for all the help. (sarcasm)
Since I can't post on the actual threads yet, due to being a new account, I will be posting here in hopes that someone comes across this and can help me out.
I have done a pretty hefty amount of reading trying to get my Nexus 7 rooted and for some reason I just can't get past the part of installing the necessary drivers for my computer.
Specs:
- Windows 7 32 bit. (Administrator account)
- Nexus 7 32GB (Wifi) running 4.2.1 w/ OEM cable (Also tried a non-OEM cable)
What I have done so far with Wug's Toolkit:
- Step 1
1. Plugged in my device and made sure USB Debugging was enabled. (At this point, the Device Manager recognized a device and tried installing drivers, but failed.) So the first thumbnail is what I have in my device manager from the start. Nexus 7 under "Portable Devices" and "Other Devices."
2. I uninstalled both of the devices.
3. Unplugged my device and used USBDeview to uninstall anything that resembled "Google" or "ADB", etc. like it states.
4. Rebooted my computer.
- Step 2
1. It says that the recommended solution is #3, so naturally, I tried that one first. I followed the steps and installed the Android Composite ADB Interface drivers successfully and it even shows it under "Android Phone" in my device manager, second thumbnail, when my device is plugged in. (USB Debugging enabled)
2. Now, when I click on the "Reboot Bootloader" button on step 6 is where it just hangs with the dialog box "Rebooting your device into bootloader mode..." but my Nexus never reboots or anything. My Task Manager show two "adb.exe" processes and none ever end. I read the thread and some users were having the same problem and they got it to work by ending one of the adb.exe processes. So I have to end one of them and after a while I get a "Checking Fastboot status" then a few seconds later this message box pops up, third thumbnail. It says that Debugging is not necessary for bootloader mode, so I turn off USB Debugging and my computer recognizes a new device. So it successfully installs Android ADB Interface and I try the Reboot Bootloader button again, and it still hangs. Only this time, there is one adb.exe. So I kill it, and after a while I get the same error dialog box as the third thumbnail. Like it states, I am using driver configuration #3, so I will go ahead and close the dialog box and go to step 7.
3. Since my device is already configured, I go to Step 12.
4. I hit the "Reboot Device" button, but nothing happens to my device.
At this point, I decide to try a different driver solution. So I go through the whole process all over again, with Solution 1. Go through and install the drivers, everything goes according to the tutorial. I get to Step 3, and hit "Full Driver Test" and it hangs on "Checking ADB Status". There are two
adb.exe's so I end one of them. I get a dialog box that says ADB device not found.
Finally, I decide to try Solution 2. So I go through the whole process. Yet I still get the same hanging with adb.exe. I even tried different USB ports, but nothing.
Now, with mskip's Toolkit I never get past the "Starting ADB..." message. It just hangs there.
So the problem lies with ADB.exe I'm guessing. I'm tired and I've spent hours just trying to root this thing. Am I SOL? Anyone have anything that I can try out or the same problems?
Have you tried rebooting your PC after installing the drivers? It took me ages to get mine installed and I think a reboot allowed the device to show up and work properly. I thought it would be easy being a nexus device. Turned out to be a right pain in the ass.
Yep.
davidoff59 said:
Have you tried rebooting your PC after installing the drivers? It took me ages to get mine installed and I think a reboot allowed the device to show up and work properly. I thought it would be easy being a nexus device. Turned out to be a right pain in the ass.
Click to expand...
Click to collapse
Hey thanks for the response. Yes I have. I tried rebooting after every driver change. (Uninstalling, re-installing, etc.) My device does show up, almost as if the drivers are working correctly. Though I'm not sure why adb.exe is giving me troubles.
Have you tried 'adb devices' via cmd prompt? I take it your all stock then?
davidoff59 said:
Have you tried 'adb devices' via cmd prompt? I take it your all stock then?
Click to expand...
Click to collapse
No I haven't. Is this what you are talking about? http://forum.xda-developers.com/showthread.php?t=1741395
EDIT: I just tried "adb devices" via command prompt in the Advanced Settings, "Daemon not running, running it now, daemon started successfully." Now it'st just hanging. Two adb.exe processes.
What I was hoping to do was to create a backup of all my apps and data before I mess around with it. Yes, I'm all stock.
Add me on gchat and hit me up. Not sure what you are having problems but I could help you trouble shoot.
{{ WugFresh }}
WugFresh said:
Add me on gchat and hit me up. Not sure what you are having problems but I could help you trouble shoot.
{{ WugFresh }}
Click to expand...
Click to collapse
Thanks for the response, I have e-mailed you.
I updated to 4.3, which nuked my TWRP recovery. I have been trying to get TWRP back on my Nexus 10 so I can reroot. The problem is, my computer refuses to see it in Fastboot mode no matter what I do. The drivers are the main issue. I can't get ADB to detect my device in Fastboot.
I have followed all of the instructions on the Wugfresh tool exactly and I still have the same issue. By default, my Nexus shows up as a "Samsung Mobile USB CDC Composite Device" in Fastboot mode. It shows up as an ADB device in normal boot. USB debugging is enabled.
I have tried all of the drivers: Raw, PDAnet, universal, and Samsung. All are giving me the same result. I even plugged my Nexus 10 into another computer and tried the process from scratch and that computer also sees it as a "Samsung Mobile USB Composite Device". Changing the device manually to something like an Android ADB device will still not allow Fastboot to see it.
I'm all out of ideas here. I have uninstalled everything, removed all USB devices, rebooted, tried different computers, etc. Nothing is working. What am I missing?
Update: After several hours, I managed to get my computer to recognize it in fastboot long enough to flash the new TWRP manually and then got rooted from there. What a nightmare!
I am still having this problem. I tried all your steps and I am still having the problem.
Sent from my SGH-M919 using xda premium
It's weird.
I had my HD8-6G on v5.3.1.0 (now, v5.3.1.1).
I installed the Amazon Fire Drivers that were on the Amazon developer website. But, my Win7x64 PC complained that it still didn't recognize the HD8 device while it was in ADB mode. So, I manually selected the Amazon.com ADB Composite Device for my updated driver. This works ... partially
If I booted the HD8 into "adb sideload" mode, the HD8 was properly recognized, and I was able to install the v5.3.1.1 update. However, the tablet is still not visible when I did an adb devices command. in my ADB / Fastboot shell. I tried running KingoRoot, and the tablet wasn't discovered.
How can I get ADB working properly on Win7x64?
¿GotJazz? said:
It's weird.
I had my HD8-6G on v5.3.1.0 (now, v5.3.1.1).
I installed the Amazon Fire Drivers that were on the Amazon developer website. But, my Win7x64 PC complained that it still didn't recognize the HD8 device while it was in ADB mode. So, I manually selected the Amazon.com ADB Composite Device for my updated driver. This works ... partially
If I booted the HD8 into "adb sideload" mode, the HD8 was properly recognized, and I was able to install the v5.3.1.1 update. However, the tablet is still not visible when I did an adb devices command. in my ADB / Fastboot shell. I tried running KingoRoot, and the tablet wasn't discovered.
How can I get ADB working properly on Win7x64?
Click to expand...
Click to collapse
this might be silly, but make sure you have developer mode enabled/adb enabled. also enable unknown sources in security. I would think it should show up when you issue adb devices..how strange.
* also I like to check stay awake.
Those are the very same drivers (fire usb for everything except recovery, and the android ones for the adb composite for recovery) I used and I'm on Windows 7 64 Bit.
* I just put my device in recovery mode and yeah it says android composite adb interface 10/27/2014 1.4.0.0 Amazon Services
hmm..actually it says the same when i reboot
smokejumper76 said:
this might be silly, but make sure you have developer mode enabled/adb enabled. also enable unknown sources in security. I would think it should show up when you issue adb devices..how strange.
* also I like to check stay awake.
Those are the very same drivers (fire usb for everything except recovery, and the android ones for the adb composite for recovery) I used and I'm on Windows 7 64 Bit.
* I just put my device in recovery mode and yeah it says android composite adb interface 10/27/2014 1.4.0.0 Amazon Services
hmm..actually it says the same when i reboot
Click to expand...
Click to collapse
I have all the same settings you list above, but the ADB device isn't being found.
I also don't get prompted for an RSA key. Could that be related? I may have been prompted previously, but I don't think so. This is the first time I think I did any ADB stuff on this tablet.
¿GotJazz? said:
I have all the same settings you list above, but the ADB device isn't being found.
I also don't get prompted for an RSA key. Could that be related? I may have been prompted previously, but I don't think so. This is the first time I think I did any ADB stuff on this tablet.
Click to expand...
Click to collapse
yes, you must get prompted for RSA key. If you disable usb debugging, then reenable it (with tablet still connected) you should get a prompt and check remember. That definitely is an issue if that never was applied.
* also I like to make sure stay awake is on. In addition, whenever you reboot the tablet, upon rebooting, I like to make sure the screen is unlocked and sometimes you need to quickly unplug it, then replug it back it once it's rebooted for the device to show up in my computer.
I know I am probably the millionth person to say this, but I can't for the life of me get my device recognized in ADB when it's in Bootloader.
What I have tried so far:
- Activated OEM Unlock, USB debugging and set my computer to always be allowed for usb debugging
- Manually installed latest google usb drivers through device manager
- started up adb in cmd, made sure the device was recognized, rebooted in bootloader to check device list again
- Same thing, but with the drivers from the Mi A1 Tool)
The results:
- in Bootloader: Not recognized in ADB, but windows device manager shows "Android Bootloader Interface" as properly installed with google's driver 11.0.0.0.
- booted up: Recognized in ADB as " d59.... device" and in device manager as "ADB Interface"
This is not my first android rooting experience, but I have never had such problems installing drivers before. Is there anything special about the MI A1 I don't know? Anything I am forgetting maybe? All other Threads I found weren't helpful.
Thank you in advance for just taking the time to read until this point Any pointers even just links will be much appreciated!
Did you type 'su' after opening ADB/command prompt?
No I did not. Will try it out at home, but isn't that just for superuser meaning root access? The command to list devices should be "adb devices" not matter what mode the device is in, no?
Thank you for the tip!
Use "fastboot devices" "fastboot oem unlock".