Database Develop

[Q] [HELP]cannot connect to pc with adb or fastboot or in pc devices

cannot connect to pc i have unlocked bootloader with htcdev and installed cwm touch v 6.0.4.4 one Flyhalf205's thread. that all worked fine.
but after doing a nandroid backup for my uk EE htc one cid htc_001. i then rebooted phone from recovery but now when i connect phone to laptop it does not recognize it through windows. nothing happens when i fastboot devices either please help thanks.

nathlynn22 said:
cannot connect to pc i have unlocked bootloader with htcdev and installed cwm touch v 6.0.4.4 one Flyhalf205's thread. that all worked fine.
but after doing a nandroid backup for my uk EE htc one cid htc_001. i then rebooted phone from recovery but now when i connect phone to laptop it does not recognize it through windows. nothing happens when i fastboot devices either please help thanks.
Click to expand...
Click to collapse
You cannot do fastboot devices in recovery mode.
in recovery mode you can do adb devices to check if your phone is recognized by your laptop
in fastboot usb mode, you can do fastboot devices to check if your phone is recognized by your laptop

I have the same. Was working fine beforehand now nothing. When I connect to the PC with the phone booted it connects then a second or two later disconnects, like it "doesn't like" the connection. It tried to install HTC MTP driver but fails as it says the "device is disconnected." Fastboot USB works fine though and I can carry out fastboot commands from bootloader, but no ADB

[email protected] said:
You cannot do fastboot devices in recovery mode.
in recovery mode you can do adb devices to check if your phone is recognized by your laptop
in fastboot usb mode, you can do fastboot devices to check if your phone is recognized by your laptop
Click to expand...
Click to collapse
I tried fast boot devices in fast boot USB by going into minisdk. Didn't try in recovery would have been good to try adb devices in recovery because I was stuck in that when first tried the custom recovery but a hard reset kicked it back out. Got recovery sorted just wanted to take nandroid backup off phone to PC and put root files which I'm still trying to get best 1's any idea where to get them where URL link is working? I've tried fastboot so doesn't work and basic trying to connect phone to PC for file transfer doesn't work either

stovie_steve said:
I have the same. Was working fine beforehand now nothing. When I connect to the PC with the phone booted it connects then a second or two later disconnects, like it "doesn't like" the connection. It tried to install HTC MTP driver but fails as it says the "device is disconnected." Fastboot USB works fine though and I can carry out fastboot commands from bootloader, but no ADB
Click to expand...
Click to collapse
Ok so not only person. When I try connect mine doesn't even flag up I've connected a device USB debugging starts up on phone but have just noticed USB connection doesn't show. Plus I connect to PC and doesn't make the sound as I've it recognized my connecting anything. Fastboot USB comes up empty. I've been spending a couple hours here and there for past 2 nights trying to set phone up ready for rum runner. But my other question is if I'm already on htc_001 there's no need for me to change CID num anyways? Thanks

Try going to command prompt and typing in set devmgr_show_nonpresent_devices=1 followed by start devmgmt.msc
Click on view and show hidden devices. This will show devices which are not connected but have been installed. Look for something like android phone or android device and update the drivers by selecting update driver > let me select > have disk and then select the driver from here:
http://forum.xda-developers.com/showthread.php?t=2386956
Try that and see if it works

I'm all sorted now thanks just kept at it.
Sent from my HTC One using XDA Premium 4 mobile app

Phone bricked, need help :c

Hey, Ive tried to install xiaomi.eu rom but didnt realize that i needed the chinese rom and that the global didnt work for this, after ive installed using TWRP the rom, ive rebooted and it just went black, not recovery, not fastboot.
BT was unlocked.
I also see my phone as qualcomm...qloader 9008 when connecting to my pc
Any help?

after having a few heartattacks, ive installed a good Miflsah and a good fastboot rom, and managed to restore my phone to its former glory
no need for further help, but i have a few advices
dont be stupid like me, and listen to directions like theyre the word of god, when they say change from chinese rom to a non official rom, YOU NEED CHINESE, global wont work
and if you're having problems with miflash giving errors, try a bunch of downloads, old, new, everything.

Hi, yet another brick here!
I had an AOSP ROM but I had problems with it. I entered TWRP, downloaded a MIUI official ROM for recovery, wiped the phone from TWRP and decrypting it (there was an option for that). Then I did try to flash the ROM and... black screen. No signs of life.
However, when I connect it to the computer it detects it as the famous Qualcom xxx 9008 (COM10) device. But fastboot is not working, when I type "fastboot devices" it doesn't return anything. ADB doesn't recognize the phone either. Everywhere I saw that I should use MiFlash to recover it, but I took a look at the scripts and are using fastboot to perform the process. But since fastboot doesn't recognize the device, it won't work. I get stuck all the time at "Failed to receive the hello packet".
Fastboot doesn't detect my phone either on Linux or Windows. I tried Linux, virtual Windows 10 (x64) and at last I'm trying on a Windows 10 (x64) computer (no virtualization). No matter what I do, it always stays at the same point. I also used several MiFlash versions (from old builds from last year to the most up-to-date version of XiaomiMiFlash). But since fastboot is not detecting the phone I think there's no point in switching MiFlash versions.
So... what can I do? Should I use the pin short-circuit /deepflash cable method? As of I understand, that is what you use to get into EDL, but if my device is showing 9008 in device manager doesn't it mean that I'm already in EDL? I'm not really sure because all the threads I saw in several forums are a bit messy.
I'll appreciate any help. I don't have phone since 3 days ago and I can survive without it but I need it for my work.
Thank you in advance!
EDIT:
Forgot to say, if I try to power off and power on it doesn't do anything BUT when I plug and unplug from the charger it does show a battery icon with the charged percentage. That's the only sign of life from the phone, aside from being recognized as a 9008 device, but that actually happens when I try to (blindly) get in fastboot mode.

FIXED!!! After four hours testing out several options I found the solution: Open up the phone, unplug the battery cable, plug it again, and voilà. The phone automatically got recognized (again) as Qualcomm 9008 device but this time the flash went on flawlessly. It took less than 5 minutes, once succeeded I powered on the device and it ran into MIUI 8 in less than 5 minutes.
So, if you find issues with the command "fastboot devices", unplug the battery and try it again before troubling yourself with deepcables or shortcircuits ;-D
NOTE: Taking out the back cover is very easy, search on youtube, I bought the thing you need for 1$ at the store next to my home (sorry I don't know what it's called).

Question Phone in fastboot mode not recognised

Since I flashed my Mi 11 ultra from CN to EEA version Rom, it is not recognised by Windows 10 laptop when in fastboot mode.
Its the same Win 10 laptop which I used to flash the phone, so all the drivers are still installed.

You have to turn USB Debugging on again in developer settings

Done that. I've done everything. It just doesn't get recognised. No little chime when I plug it in, nothing. It works in normal mode, but not fastboot.

message me privately and i can help you through zoom/teamviewer

saisannihith said:
message me privately and i can help you through zoom/teamviewer
Click to expand...
Click to collapse
there is a hardware fault on my phone. usb debugging is enabled. when in plug in phone in fastboot mode, it doesn't even show in device manager. nothing. this screenshot is taken with the phone plugged in in fastboot mode. As you can see, it doesn't show at all.

spikemann007 said:
there is a hardware fault on my phone. usb debugging is enabled. when in plug in phone in fastboot mode, it doesn't even show in device manager. nothing. this screenshot is taken with the phone plugged in in fastboot mode. As you can see, it doesn't show at all.
Click to expand...
Click to collapse
I cant tell you anything until i see it.

Weird, I attached a screenshot before. Here I try again.

put cellphone in fastboot download and install file here's download link https://ufile.io/1xc7dudc

thephonetechdoc said:
put cellphone in fastboot download and install file here's download link https://ufile.io/1xc7dudc
Click to expand...
Click to collapse
I already installed that same file before. No difference. doesn't even show in devive manager. I give up.

Bro not like this. Iam asking if i can connect remotely to your PC to diagnose the drivers.

Unusual xiaomi drivers and adb devices and reinstall

Have a look and try out the method mentioned in the video. Did the trick for me

I did all of it. I don't even get that little chime that lets you know when you plug the phone in. Silence.
It works fine in normal mode.

Hi @spikemann007 !
I had the same issue.
Root cause was (for me) the USB cable. Have you already tried a alternative?
best regards!

Question Fastboot driver only displays on first use

I have a very odd issue with fastboot. The computer (windows 10) detects the device the first time I use fastboot and then will not show up in device manager on other attempts.
I have the EU variant running Oxygen OS 11.0.11.11.EB12BA with Magisk installed.
I have installed the Oneplus ADB drivers and this works flawlessly. Booting the first time into fastboot mode the device showed in the device manager, I was able to install the fastboot driver and fastboot devices showed my phone.
Trying a second or third time nothing shows in the device manager. The device is completely absent from USBDeview.exe. It behaves as if it's not even plugged in.
I was able to reproduce this on another computer I have.
Is anyone else facing this issue and/or knows what might be going wrong?
EDIT: If it helps anyone else having this issue I'm able to get the "OnePlus Android Bootloader Interface" to show up if I plug the phone into a USB HUB, then plug the HUB into the computer. Rebooting the phone again into fastboot will not show up but if I unplug and replug the hub in the driver will activate again.

VoltaGe86 said:
I have a very odd issue with fastboot. The computer (windows 10) detects the device the first time I use fastboot and then will not show up in device manager on other attempts.
I have the EU variant running Oxygen OS 11.0.11.11.EB12BA with Magisk installed.
I have installed the Oneplus ADB drivers and this works flawlessly. Booting the first time into fastboot mode the device showed in the device manager, I was able to install the fastboot driver and fastboot devices showed my phone.
Trying a second or third time nothing shows in the device manager. The device is completely absent from USBDeview.exe. It behaves as if it's not even plugged in.
I was able to reproduce this on another computer I have.
Is anyone else facing this issue and/or knows what might be going wrong?
EDIT: If it helps anyone else having this issue I'm able to get the "OnePlus Android Bootloader Interface" to show up if I plug the phone into a USB HUB, then plug the HUB into the computer. Rebooting the phone again into fastboot will not show up but if I unplug and replug the hub in the driver will activate again.
Click to expand...
Click to collapse
You don't need to install any fastboot drivers, if you're on windows; just install one plus driver (without driver signature/in test mode) and stay on them.

Sony make.belive said:
You don't need to install any fastboot drivers, if you're on windows; just install one plus driver (without driver signature/in test mode) and stay on them.
Click to expand...
Click to collapse
Sorry I think I've explained incorrectly. Those are the drivers I've installed, the problem is it only works once.
The second time I reboot the phone into Fastboot mode it doesn't display in device manager. Looking at USBDeview absolutely nothing shows up. Changing USB ports and the cable have no effect, however if I plug the phone into an old USB 2 hub I have then plug that into the computer it will display again in the device manager.

device not getting detected in both adb and fastboot.

I am stuck in a very weird situation, my device is not getting detected in both adb in recovery mode and fastboot. I have no ROM (No OS) installed at the moment.
I am booting to recovery and fastboot through hardware keys.
I have tried installing drivers from mi unlock tool and any other USB drivers I could find in top searches of "USB drivers".
I am sure the USB cable is not the issue as other xiaomi device (Redmi note 4) is getting detected.
The port also looks fine as I can see 'charging' in recovery mode.
What are my options here? is my device 'gone'? I have orange fox recovery so I have access to `shell` if that helps.

Sparkenstein said:
I am stuck in a very weird situation, my device is not getting detected in both adb in recovery mode and fastboot. I have no ROM (No OS) installed at the moment.
I am booting to recovery and fastboot through hardware keys.
I have tried installing drivers from mi unlock tool and any other USB drivers I could find in top searches of "USB drivers".
I am sure the USB cable is not the issue as other xiaomi device (Redmi note 4) is getting detected.
The port also looks fine as I can see 'charging' in recovery mode.
What are my options here? is my device 'gone'? I have orange fox recovery so I have access to `shell` if that helps.
Click to expand...
Click to collapse
Hey man, I know this might sound dumb, but have tried using a different PC ??, I have been in a situation like this and trying using a different pc actually was successful

> Have you tried different PC
Yes. My first suspicion was USB3.0 Ports. So I tried a different PC as well. Unfortunately couldn't find a PC with USB 2.0 ports but yeah another PC didn't work as well (Note mine worked for past 4 years just fine)