Database Users

Recovery mode, device not detected by Windows

ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,

brandonyoung said:
ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,
Click to expand...
Click to collapse
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.

sparkplugDev said:
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.
Click to expand...
Click to collapse
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,

brandonyoung said:
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,
Click to expand...
Click to collapse
I've heard that unplugging the device from the PC until you're in recovery mode might help. I would also suggest, if that doesn't work, to install the ADB drivers again once you're in recovery mode.

Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.

garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
When it is running, and usb debugging is enabled, it shows up under Android Phone as Android Composite ADB Interface.
I turn USB debugging off, and it shows up under Portable Devices as Nexus 10
I boot into the bootloader and it shows under Android Phone as Android Bootloader Interface.
but It doesn't show at all when I am in recovery

How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?

mevensen said:
How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?
Click to expand...
Click to collapse
I am connecting with a USB cable. I don't know if it is "good' or not, but it works with the tablet in all other modes. I was able to use adb to transfer files, reboot, etc. I was able to use fastboot to flash Chainfire's autoroot, and to flash the factory images.
I was using a USB2 port directly on my laptop, but I just tried the USB3 port and it didn't change anything.
Plugging it into my USB hub, and my hub did not detect that it was plugged in either while it was in recovery mode. It was detected when I rebooted back into the system.
USB debugging is on when I enter recovery. I used "adb reboot recovery" to reboot my tablet into the recovery mode

garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
Thank you !!!!!!!!!

my lenovo a6000 shot no display but detecting n device manager.
it occured due to flash flash.rec.
please help me.

[Q]PC doesn't recognize my nexus 4.

Hi all,
i have a problem with my Nexus 4 , my PC doesn't recognize my phone not in mass storage not in the device manger, but it will charge the phone also i cant get in my recovery it says NO COMMAND , i got Un rooted phone with unlocked bootloader and i have stock rom 4.4.0 krt16s.
any ides?
tnx for the help...

and i try to change cable, pc, other os, nothing helped.

Does your phone boot normally? Can you turn on USB debugging?

audit13 said:
Does your phone boot normally? Can you turn on USB debugging?
Click to expand...
Click to collapse
yes it boot normally and i can turn USB Debugging and it still doesn't recognize with and without USB debugging mode.

When you select recovery from fastboot, that's when you get the "no command" error?

audit13 said:
When you select recovery from fastboot, that's when you get the "no command" error?
Click to expand...
Click to collapse
yes

delete

Its drivers problem.
Delete all driver you have then install again

Oz4225 said:
Its drivers problem.
Delete all driver you have then install again
Click to expand...
Click to collapse
i got fresh windows without any drivers.

Install this driver:
https://www.copy.com/s/C9uWyr4n4WEE/UniversalAdbDriver.msi

Oz4225 said:
Install this driver:
https://www.copy.com/s/C9uWyr4n4WEE/UniversalAdbDriver.msi
Click to expand...
Click to collapse
no help

rep
theshield88 said:
Hi all,
i have a problem with my Nexus 4 , my PC doesn't recognize my phone not in mass storage not in the device manger, but it will charge the phone also i cant get in my recovery it says NO COMMAND , i got Un rooted phone with unlocked bootloader and i have stock rom 4.4.0 krt16s.
any ides?
tnx for the help...
Click to expand...
Click to collapse
I do same kind of prob with my PC. The root of problem is mostly the USB cable itself. I've got the stock nXs⁴ cable yet after a year its out I think. When that happens try some many cable.
The prob might even occur due to MTP. If debugging is enable then ADB would recognize nXs⁴ as offline and no Portable media device would be visible in My PC. In that case try restarting PC!
nXs⁴ aRvInD G R

Bricked Oneplus 2 (SOLVED)

**UPDATE I have unbricked my phone and the whole time I thought it was a software issue on my phone but it was a cable, I guess my cable got broken when I bricked my phone and I thought it was a software issue but it was not the whole time**
I have a bricked device and I would appreciate your help and I have tried EVERYTHING!!
here is how my oneplus 2 got bricked, I was on stock oxygen os 3.0 and rooted and I had twrp recovery 3.0.
So I did a full wipe on my device and when I was flashing the resurrection remix rom in twrp it said "Error 7" so then I reboot my phone and I was in a bootloop with no os.
I went back to twrp and flash the rom again and it not work. So then I tryed to transfer a file through my computer to my device and twrp was not recognizing it and tryed adb sideload and same thing and even in cmd I
typed "adb devices" and it not recognize it and I have the drivers installed, the 15 second 1click adb and fastboot.
And then I went to fastboot mode and then I tried first aid kit and the qualcomm mega unbrick guide and all the methods and still my oneplus 2 is not being recognized by PC and I am using the official oneplus 2 usb type c cable.
I have tried 2 windows 10 PC and I turned driver signniture enforcement off for the qualcomm drivers and nothing in device manager
I tried 1 Windows 7 PC and same thing and nothing in device manager
And I tried a Linux Mint virtual machine and I typed adb devices and fastboot device in the terminal and it was not recognizing it even though I installed the packages
So do you think the problem might be the cable? because it is the official one. But my device charges through the cable to and the cable was working before my phone got bricked. Or is it a driver problem? What do you guys think and please help and I will really appreciate it and thank you.

fahad999 said:
I have a bricked device and I would appreciate your help
here is how my oneplus 2 got bricked, I was on stock oxygen os 3.0 and rooted and I had twrp recovery 3.0.
So I did a full wipe on my device and when I was flashing the resurrection remix rom in twrp it said "Error 7" so then I reboot my phone and I was in a bootloop with no os.
I went back to twrp and flash the rom again and it not work. So then I tryed to transfer a file through my computer to my device and twrp was not recognizing it and tryed adb sideload and same thing and even in cmd I
typed "adb devices" and it not recognize it and I have the drivers installed, the 15 second 1click adb and fastboot.
And then I went to fastboot mode and then I tried first aid kit and the qualcomm mega unbrick guide and all the methods and still my oneplus 2 is not being recognized by PC and I am using the official oneplus 2 usb type c cable.
I have tried 2 windows 10 PC and I turned driver signniture enforcement off for the qualcomm drivers and nothing in device manager
I tried 1 Windows 7 PC and same thing and nothing in device manager
And I tried a Linux Mint virtual machine and I typed adb devices and fastboot device in the terminal and it was not recognizing it even though I installed the packages
So do you think the problem might be the cable? because it is the official one. But my device charges through the cable to and the cable was working before my phone got bricked. Or is it a driver problem? What do you guys think and please help and I will really appreciate it and thank you.
Click to expand...
Click to collapse
If your recovery mode is TWRP.. Then goto Mount -> Data
Then your computer will show your oneplus 2.
If still its not showing then update Driver Software of phone in device manager.

eldos777 said:
If your recovery mode is TWRP.. Then goto Mount -> Data
Then your computer will show your oneplus 2.
If still its not showing then update Driver Software of phone in device manager.
Click to expand...
Click to collapse
I tried both mount data on and off and still no luck, I have mtp enabled in twrp. I also checked device manager and there is nothing showing up. But twrp says that my phone is charging when my phone is connected to pc. I think the problem is probably the cable because the usb end of the cable looks sort of damaged, And I tried a Type-C OTG and put a usb on that and TWRP was not recognizing it

eldos777 said:
If your recovery mode is TWRP.. Then goto Mount -> Data
Then your computer will show your oneplus 2.
If still its not showing then update Driver Software of phone in device manager.
Click to expand...
Click to collapse
Holy crap the cable was the problem the whole time!!! I just went to the store and bought A new 3rd party USB-C cable and I plug it in to my pc and phone and immediately the pc installed drivers and now I could transfer files to TWRP from my PC!! It was a really hot sunny day today and I walked to the store which took 30 minutes and both ways 1 hour. I am so tired right now from the walk but it was worth it since my phone will be brought to life!! I am so happy right now!!!

fahad999 said:
Holy crap the cable was the problem the whole time!!! I just went to the store and bought A new 3rd party USB-C cable and I plug it in to my pc and phone and immediately the pc installed drivers and now I could transfer files to TWRP from my PC!! It was a really hot sunny day today and I walked to the store which took 30 minutes and both ways 1 hour. I am so tired right now from the walk but it was worth it since my phone will be brought to life!! I am so happy right now!!!
Click to expand...
Click to collapse
:good:

eldos777 said:
:good:
Click to expand...
Click to collapse
Thanks for your advice to for fixing the phone! I appreciate it!!

USB not recognized by PC or OTG

Has anyone faced this problem where the LePro is does not connect to the PC anymore? Charging works but otg and PC connection don't work anymore.

My brand new had this bug, first wipe resolved it.

marik1 said:
My brand new had this bug, first wipe resolved it.
Click to expand...
Click to collapse
Was it the exact same problem? It would charge but no connection with the PC and no USB otg?

I dont have any OTG devices, so I dont know. It was on stock ofc.

rmarcus said:
Was it the exact same problem? It would charge but no connection with the PC and no USB otg?
Click to expand...
Click to collapse
Had it, wouldnt even charge. A combo of plugging/unplugging multiple times, w/rebooting enabled me to charge it, then i flashed the official 21s or 19s, dont remember now, and it started working. Also, sometimes just reversing the cable (phone side) did the trick.
Try rebooting w/ different cable and see if that helps the pc connectivity issue.

trizex said:
Had it, wouldnt even charge. A combo of plugging/unplugging multiple times, w/rebooting enabled me to charge it, then i flashed the official 21s or 19s, dont remember now, and it started working. Also, sometimes just reversing the cable (phone side) did the trick.
Try rebooting w/ different cable and see if that helps the pc connectivity issue.
Click to expand...
Click to collapse
I'll try that, but it seems that there was glitch in the current some sort of fluctuations and it maybe fried post of the USB connector. The thing is I simply can't root and install any custom ROM other than that it is perfect. Thanks for sharing!

rmarcus said:
I'll try that, but it seems that there was glitch in the current some sort of fluctuations and it maybe fried post of the USB connector. The thing is I simply can't root and install any custom ROM other than that it is perfect. Thanks for sharing!
Click to expand...
Click to collapse
Did you get it to work?

ftardism said:
Did you get it to work?
Click to expand...
Click to collapse
Nope... Sold it to someone who claimed to be able to fix it. It's a shame, I loved that phone.

I've just received a "new" Pro3 from Aliexpress which has this exact problem. Although it looks new, the dust and fluff in the USB connector gave away that it's been reconditioned.
I have another 2 of these phones which connect to my PC fine.
The PC doesn't even detect a connection with this one though.
Now I can't unlock and replace EUI with LineageOS. I'm not going to use EUI.

I have the same problem. It is charging but cannot connect to pc. It must be a windows 10 problem, because with windows 7 it connects ok.

arist1976 said:
I have the same problem. It is charging but cannot connect to pc. It must be a windows 10 problem, because with windows 7 it connects ok.
Click to expand...
Click to collapse
Your issue is just the driver, update the drivers on the PC and you will be fine. Also make sure in developer options that usb debugging is turned on and default usb settings are on file transfer mtp.

tsongming said:
Your issue is just the driver, update the drivers on the PC and you will be fine. Also make sure in developer options that usb debugging is turned on and default usb settings are on file transfer mtp.
Click to expand...
Click to collapse
Thank you but I've tried all these and many more. But the problem is still here. I almost quit, there is nothing more to do. I tried ALL, literally.

arist1976 said:
Thank you but I've tried all these and many more. But the problem is still here. I almost quit, there is nothing more to do. I tried ALL, literally.
Click to expand...
Click to collapse
I have written these instruction many, many times. the answers are here if you search.
Remove all external hard drives from PC
Update PC
Install All in One Tool, use AIT to update android/leeco drivers/adb fastboot/enable system wide privileges.
Enable developer options> oem unlock, adb debugging and file transfer (MTP)
If in TWRP Recovery, the system must be mounted to be seen by the PC
If the drive is encrypted > it has to be formatted ( Not wiped) Reboot to Recovery > Issue resolved
Read the signature, its highly applicable

tsongming said:
I have written these instruction many, many times. the answers are here if you search.
Remove all external hard drives from PC
Update PC
Install All in One Tool, use AIT to update android/leeco drivers/adb fastboot/enable system wide privileges.
Enable developer options> oem unlock, adb debugging and file transfer (MTP)
If in TWRP Recovery, the system must be mounted to be seen by the PC
If the drive is encrypted > it has to be formatted ( Not wiped) Reboot to Recovery > Issue resolved
Read the signature, its highly applicable
Click to expand...
Click to collapse
I have problem with the twrp. It is not compatible with 8.1 and it cannot see internal storage or anything

tsongming said:
I have written these instruction many, many times. the answers are here if you search.
Remove all external hard drives from PC
Update PC
Install All in One Tool, use AIT to update android/leeco drivers/adb fastboot/enable system wide privileges.
Enable developer options> oem unlock, adb debugging and file transfer (MTP)
If in TWRP Recovery, the system must be mounted to be seen by the PC
If the drive is encrypted > it has to be formatted ( Not wiped) Reboot to Recovery > Issue resolved
Read the signature, its highly applicable
Click to expand...
Click to collapse
Thank you again. I tried all these before. I try again now but nothing happens. There is nothing else I can do.

arist1976 said:
I have problem with the twrp. It is not compatible with 8.1 and it cannot see internal storage or anything
Click to expand...
Click to collapse
Okay, try using an older version of Twrp Recovery. ( A Non Treble Version)
Use OTG if you have it. Otherwise place te TWRP image on the SD storage > When installing your will need to select install IMG ( instead of zip) Install to Recovery, Reboot to Recovery. Click Mount, select data, and erase all of the encrypted data on your phone by choosing Wipe, Format > type yes, Reboot to Recovery. ( check boxes) you want the the phone to be read/writable.
At this point go to File manager > SD Card> You should only see a TWRP folder > Fo to Wipe Advanced wipe, select everything except your OTG drive > Wipe > Reinstall your Rom, Gapps, and Magisk. Did this work?
If no,
Reboot to TWRP recovery
* Select Advanced Wipe
* Select "Repair or Change File System".
* Select Change File System > Even if its already ext 4 select it again
* Format Data> Yes. Reboot to recovery > Full Wipe > Finished
* Now /data is mounted back. > You should be able to install whatever you want. > hopefully > if not you may have a hardware issue, such as the usb card, flex cables or worse.

@tsongming Good morning friends I have my Leeco Le Pro 3 with no system installed, just twrp working. When plugging the otg or the PC he does not recognize anything, I already bought 3 otg and tested with 4 cables and more than 5 flash drive, all this and without success. I installed all the necessary drivers from which, downloaded the tool all in one, tried the qfil mode, but the phone is not recognized on the PC. Has anyone managed to solve this problem?

I have 3 X720 and one of this has got the same problem.
TWRP 3.2.1.0 could not recognize OTG USB and Internal storage. Now Lineageos doesn' start . The start is in loop.
PC doesn't see X720 also in fastboot when the other two in fastboot works.
I think it's a hardware problem!
I have also chankged Micro USB Charging Dock Port Charger Connector, but nothing is changed.
How could I make?
Thanks

CapVi said:
I have 3 X720 and one of this has got the same problem.
TWRP 3.2.1.0 could not recognize OTG USB and Internal storage. Now Lineageos doesn' start . The start is in loop.
PC doesn't see X720 also in fastboot when the other two in fastboot works.
I think it's a hardware problem!
I have also chankged Micro USB Charging Dock Port Charger Connector, but nothing is changed.
How could I make?
Thanks
Click to expand...
Click to collapse
Is your charging problem resolved ?
In my case the phone won't charge anymore.
Do You think that changing the dock port will be the solution ?
Is the change difficult ?

dkoek said:
Is your charging problem resolved ?
In my case the phone won't charge anymore.
Do You think that changing the dock port will be the solution ?
Is the change difficult ?
Click to expand...
Click to collapse
I must change Usb dock port.

Pc cant detect fastboot device

Tried miui 12 and after flashing rom the twrp is gone I tried to reflash it the same way I did first but sadly when I'm on fastboot PC can't detect it. also tried it with other softwares but same result. Device is fine and responds when open but not in fastboot mode. Currently running miui 11 .0.6 China stable. Stucked. Also all drivers are updated

Same here.
I accidentally flashed china stable 11.0.4 zip rom on my global device through twrp and upon booting up twrp was gone and when i plug in usb the pc doesn't detect anything. In order to make pc detect the phone via usb cable i have to reboot phone while plugging usb to laptop that way file transfer option shows up in laptop and adb works but fastboot doesn't work i can force boot to fastboot through adb but upon booting to fastboot the pc stucks at waiting for device. All the drivers are installed
Currently on china stable 11.0.6

Same issue indeed
That's exactly what's happening right now. I hope someone can help us

Quote me if u find any luck.

Same issues

That happens me sometimes. I only reboot the device into fastboot again, reboot the computer, and that it. This may change depending on your computer CPU, mine is AMD. And ussually I have to use a 2.0 USB or if it still does not work a USB 2.0 hub. I know the hub thing is strange but it worked for me when my pc does not detect the phone in fastboot. Hope it helps .

With my PC I have to open device manager, look for the device, usually has a yellow sign next to it. Right click on the device name, click update driver, click browse my computer for driver software, click let me pick from a list of available drivers on my computer and pick mtp USB device. Then I read it. I hope this helps.

daniml3 said:
That happens me sometimes. I only reboot the device into fastboot again, reboot the computer, and that it. This may change depending on your computer CPU, mine is AMD. And ussually I have to use a 2.0 USB or if it still does not work a USB 2.0 hub. I know the hub thing is strange but it worked for me when my pc does not detect the phone in fastboot. Hope it helps .
Click to expand...
Click to collapse
What hub?
Tried with multiple pcs with no success

epicblue8 said:
What hub?
Tried with multiple pcs with no success
Click to expand...
Click to collapse
I use a usb hub that is very old i guess, as it uses MiniUSB. By the way with multiple computer it should work, your error is very strange, I never saw it. A thing that may work is trying to use fastboot on a Linux system (no, with VMs no). So if you can flash a pen drive with a Ubuntu ISO or any linux distro, boot linux,install fastboot and check if it detects your phone.

daniml3 said:
I use a usb hub that is very old i guess, as it uses MiniUSB. By the way with multiple computer it should work, your error is very strange, I never saw it. A thing that may work is trying to use fastboot on a Linux system (no, with VMs no). So if you can flash a pen drive with a Ubuntu ISO or any linux distro, boot linux,install fastboot and check if it detects your phone.
Click to expand...
Click to collapse
Read my 1st reply to this op
Even file transfer option doesn't show up if i connect my phone via usb to laptop.
In order to make pc show file transfer option i have to reboot phone while connecting the phone to pc so.
That way i can use adb but as soon as i boot to fastboot via cmd pc doesn't detect the fastboot mode.
Tried with 3 laptops

Issue Fixed
epicblue8 said:
Same here.
I accidentally flashed china stable 11.0.4 zip rom on my global device through twrp and upon booting up twrp was gone and when i plug in usb the pc doesn't detect anything. In order to make pc detect the phone via usb cable i have to reboot phone while plugging usb to laptop that way file transfer option shows up in laptop and adb works but fastboot doesn't work i can force boot to fastboot through adb but upon booting to fastboot the pc stucks at waiting for device. All the drivers are installed
Currently on china stable 11.0.6
Click to expand...
Click to collapse
Dude I fixed it and I managed to flash global and maybe reflash EU when miui 12 stable arrive
Try another type c cord preferable the original one. I just change the cord and everything went fine fastboot can now be detected via "fastboot devices".

Chipotle crackers said:
Dude I fixed it and I managed to flash global and maybe reflash EU when miui 12 stable arrive
Try another type c cord preferable the original one. I just change the cord and everything went fine fastboot can now be detected via "fastboot devices".
Click to expand...
Click to collapse
Not with original but tried 3 type c cables and 3 pcs

epicblue8 said:
Quote me if u find any luck.
Click to expand...
Click to collapse
hey have find any solutions? we have the same problem