Database Users

Fastboot not detecting device on Windows XP

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)

[Q] No Recovery, No Download Mode, Not Recognized in Fastboot mode by PC

Hello there!
So I accidentally bricked my phone a few days ago and now it is resting as a brick on my desk, but how did all of this happen, you may ask?
Well, the story is rather simple, I had the Simple ROM V. 1.4 installed on my G2 and decided to update it to version 2.0, which is posted here somewhere, but what I didn't notice was that the file I was downloading (even though it said it was compatible with all versions) was not for the D800 but for the LS980 and this bricked the phone.
First I was stuck on fastboot mode and was able to get my download mode back, but it kept saying that it couldn't flash the stock rom because it was the wrong model.
Looking online and through these forums, I found out that it was because the download mode that it had was not the right one to use, and that I needed to "destroy" download mode, enter once again in fastboot mode and flash the new download mode, this, however, turned out out to be impossible as the fastboot mode is no longer being detected by Windows nor Linux.
I installed back the USB drivers, installed Android ADB, changed the UDEV rules with mew vendors ID from the list provided by Google, updated the drivers on my PC and even tried to change the directory in which the phone would appear.
The problem resumes to this:
When in fastboot mode (connected to the PC) and type
Code:
fastboot devices
in both Windows and Linux, I get the response as
Code:
???????? devices
.
When I try with
Code:
adb devices
I get back nothing.
Curious thing is that the phone does appear on Device Manager as an Android ADB device and when on Linux I use the
Code:
lsusb
I get back that it is being recognized as
Code:
Google Inc. 18d1 d00d
, which I believe is the phone.
When trying to run any fastboot commands, the phone stays on "waiting for device" on Linux or "flashing" on Windows and later a messages pops back at me with
Code:
Error too many links
.
With all this in mind, I would like to ask you guys, is there something that I am missing?
Any help will be truly appreciated!
PS. Forgot to mention that I have tried with other computers and have the same result and the model of my phone is the D800.

Just to add a bit more into the case.
I had installed prior to all this mess, TWRP which had a Nandroid backup in the internal storage and file backup.
When using the LG Flash tool (KDZ one) I am able to see the available storage, which is about 2.5gb. This leads me to believe that both the Nandroid backup and Backup files are still in the internal storage.
Also, I did some more digging and got information that it might be the USB cable, however, this cable worked fine the first time and with other devices. and while connecting the phone with it to the PC it will still register the device as connected, but apparently no USB port is assigned or fastboot flash tool does not find the phone.

MSM8994DownloadTool.exe Won't Work For My OPT

MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).

I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.

Phil01234 said:
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
Click to expand...
Click to collapse
I've bricked my op2 a while ago. I'm a real noob so I don't know if it will work but have you installed the adb mac drivers or try "fastboot continue" while in fastboot. Just don't give up and keep try. You have absolutely nothing to lose.

chintu1234 said:
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Click to expand...
Click to collapse
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.

Phil01234 said:
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Click to expand...
Click to collapse
Try connecting your OPT to some other guys pc and see, it may be because of your pc's end that its not getting connected.
And if the same thing happens with a different pc then yeah your usb port or something is fried. Try going to service center if the same thing happens again.

If anybody still comes here, I need help flashing Remix 1.5 on my Ultratablet

I know there are instructions (which I am following) and a similar thread (which doesn't provide a solution). Anyway, I am following the instructions and I'm stuck at the command for detecting fastboot devices. The command window shows nothing, not my serial number or an error message. The Fastboot Protocol option on the tablet's menu just loops back to the same menu. I followed all the instructions (undetailed as they are) correctly, but on the fastboot device step I am stuck. I can't use the CyanogenMod links anymore because they're down. Other websites only give me steps I've already done or don't apply to this.
Basically, I just want to know how to make my PC detect my tablet so I can then wipe and flash the images. I want to downgrade because some apps just don't work correctly with 2.0 and I don't really want to wait for an eventual fix (which may or may not fix all the app issues).

I should mention that I can detect the adb device when it's on normally ( I type adb devices and it shows up). But when i reboot into bootloader and type adb or fastboot devices it isn't detected, and when I try to use fastboot protocol (either before or after connecting) it doesn't do anything.

Had the same issue with fastboot myself. If you are running Windows 10, that could be the problem. The ususal about checking different USB ports etc. also applies.
The drivers are most important. The naked usb drivers seemed to help me the most. Also, if you are going to change the usb drivers you have, reboot between changes. Fastboot can be challenging, but you are on the right tack.

ADB phone access via Windows 10 (broken screen)

Unfortunately I broke the screen of my beloved 6P today and have spent the last 8 hours trying to figure out how to recover everything from it. It's still working as I can hear notifications and phone calls but the screen is blank.
After searching everywhere (xda, stackoverflow etc.), I'm a bit stuck and was wondering if anyone can help. Here's my plan/what I know:
1) I want to emulate the phone screen on my PC via USB using Android Control
2) I need USB debugging mode to access the phone via ADB
3) I need the correct (Google) USB drivers installed on my PC to access ADB
I have downloaded several tools/drivers and this is how far I got:
1) Windows sees/recognizes the phone under Devices and in Device Manager (as It does normally) - I am unable to access the phone because it's not in file transfer mode
2) When I run adb devices, the list is empty
3) I tried to update the driver to the latest Google USB driver but Windows 10 won't let me (windows has determined the best drivers etc. etc.)
I can't be sure what is blocking access via ADB. I'm sure I enabled USB debugging when I first got the phone but it was a long time ago. I read that I might need to disable Windows Driver Signing to install the latest Google driver but I haven't tried it yet.
My question is, how can I tell if it's USB debugging or the Driver? Any help would be greatly appreciated!

If you have your bootloader open, then this should be easy. You can install (if not already installed) TWRP recovery with "fastboot flash recovery file.img". When you then boot blindly into the recovery (its always the same amount of button presses in bootloader) then you can access the storage of your phone.
Other cheap solution: Get a phone with bootloop issue and use that screen from it. Then you have again a fully working phone.