[Q] Cannot detect Nexus 5 except fastboot - Nexus 5 Q&A, Help & Troubleshooting

So I've tried absolutely everything, new drivers, flash batch all newest firmware.. different computers, restarting computer..
whatever I do I cannot manage to get any computer to detect my Nexus 5 via adb or mounted storage.. the only thing that is detected is fastboot..?
any ideas??

Maybe it's a driver problem on your system. Did you try another computer?

What does device manager show? An unknown device connected? An acer device connected?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5

Ben36 said:
What does device manager show? An unknown device connected? An acer device connected?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
nothing, nothing detected at all. but the USB port on the phone works fine because fastboot is working fine..

any idea's anybody? I've tired several computer with different windows versions.
This phone is absolutely undetectable by USB/ADB. It charges perfectly fine and fastboot works flawlessly...

You have an issue with the Nexus 5's driver and your adb driver, but not your fastboot driver.
Try uninstalling/reinstalling the drivers and use the 15-second adb/driver installer, if that doesn't work then try the universal naked driver.

Elluel said:
You have an issue with the Nexus 5's driver and your adb driver, but not your fastboot driver.
Try uninstalling/reinstalling the drivers and use the 15-second adb/driver installer, if that doesn't work then try the universal naked driver.
Click to expand...
Click to collapse
tried both, this phone isn't detected by any computer at all when it's switched on, zero. It doesn't show up as android, or acer or anything, there is no driver able to be installed because the phone isn't even detected by the computer unless I put it in fastboot mode.

omg, first the first time it just got magically detected in TWRP as ADB composite device. This is completely un-explainable, it's been days this was achievable..
restarted phone, impossible to detect again....

THE_KINGDOM said:
tried both, this phone isn't detected by any computer at all when it's switched on, zero. It doesn't show up as android, or acer or anything, there is no driver able to be installed because the phone isn't even detected by the computer unless I put it in fastboot mode.
Click to expand...
Click to collapse
You can still install/uninstall a driver if the device is not plugged in/detected as unknown device.
Have you tried manually reinstalling the driver?

Elluel said:
You can still install/uninstall a driver if the device is not plugged in/detected as unknown device.
Have you tried manually reinstalling the driver?
Click to expand...
Click to collapse
it's not detected at all thats what I'm trying to explain, it's not an unknown device, it's never detected at all

THE_KINGDOM said:
it's not detected at all thats what I'm trying to explain, it's not an unknown device, it's never detected at all
Click to expand...
Click to collapse
If you are certain it is an issue with the device and not your drivers, try booting up a Linux distro (Ubuntu will do) in a VM or directly off a USB stick, as it requires no driver installation in Linux to access the internal storage via USB.

Elluel said:
If you are certain it is an issue with the device and not your drivers, try booting up a Linux distro (Ubuntu will do) in a VM or directly off a USB stick, as it requires no driver installation in Linux to access the internal storage via USB.
Click to expand...
Click to collapse
it's strange because for the first time a few moments ago i was able to see the device in adb mode via TWRP, as soon as I restarted the phone it's impossible again, I've tried 20+ times since then.
only thing i can get repeatedly with no issues at all is the bootloader interface/fastboot

tried with linux, ubuntu. no connection.. But I already knew it wasn't drivers.. device isn't detected at all.. it's not like it's allocating the wrong drivers.. it's not even registering a usb device was connected to the PC unless in bootloader/fastboot.

Sounds like an issue with your usb cable or the phone side adapter. Have you tried ADB through a wireless connection?

[RANT ON]
I have already addressed your issue in this thread http://forum.xda-developers.com/google-nexus-5/help/diagnosing-usb-driver-adb-issues-windows-t2514396/post59570828#post59570828 and yet without so much as even a single reply or simple thank you for taking my time and telling you in detail how it is, you found it necessary to create a new thread? Are you hoping for a magic bullet?
What's even worse in my world. You offered not a single thank you to anyone here in this tread that completely wasted their valuable time trying to help you after you already have your answers.
I realize I am relatively new member here at XDA. But I've been lurking here for over 5 years. Forgive me but this guy is why I have been reluctant to join and help until recently. He is the reason I will not waste much more of my time attempting to help others. [RANT OFF]
I will try to calm now.
Thanks for listening and I don't care if you are offended.
THE_KINGDOM said:
my situation is quite different from yours. There is no ability to "adb reboot" my device because the device is completely undetectable by USB.
I've now only managed to see the device twice in adb mode and that was completely random while in TWRP recovery, and I didn't need to turn on ADB sideload to make it visible either.. other than these two times I've tried well over 100-150 times, this phone is absolutely undetectable by USB/Computer unless in the bootloader.
Click to expand...
Click to collapse
joegestes said:
If you are able to detect the device in bootloader "fastboot devices" but still can't ABD devices in android with USB debug enabled or in recovery and/or you experience intermittent ABD detection. After looking through OP and post #322 you are absolutely certain that it is not a driver issue, you are likely looking at a hardware failure of the charging port.
https://www.youtube.com/watch?v=qqCEXEmcj4Y
If it were me, I'd replace the port and re-attempt ADB devices.
Click to expand...
Click to collapse
joegestes said:
Also be sure to try a new high quality USB data cable. (not a cheep charging cable)
Click to expand...
Click to collapse

joegestes said:
[RANT ON]
I have already addressed your issue in this thread http://forum.xda-developers.com/goo...es-windows-t2514396/post59570828#post59570828 and yet without so much as even a single reply or simple thank you for taking my time and telling you in detail how it is, you found it necessary to create a new thread? Are you hoping for a magic bullet?
What's even worse in my world. You offered not a single thank you to anyone here in this tread that completely wasted their valuable time trying to help you after you already have your answers.
I realize I am relatively new member here at XDA. But I've been lurking here for over 5 years. Forgive me but this guy is why I have been reluctant to join and help until recently. He is the reason I will not waste much more of my time attempting to help others. [RANT OFF]
I will try to calm now.
Thanks for listening and I don't care if you are offended.
Click to expand...
Click to collapse
Wow man you need to cut the estrogen pills out. This is borderline extremely weird...
You gave me one potential plausible scenario and this thread was created days before my activity on that other thread. And my first comment u quoted was a reply to somebody else lolol...
Also, I have no charging issues whatsoever with this phone... therefore charging port may not be an issue at all. But at this point I don't deny that chances are it's an extremely rare hardware issue, rare.. Hence why I'm trying to explore potential software issues/fixes before hand.
And actually I'm very generous with the "thank you" I dish out to users on XDA, unfortunately I most people seem to think its a driver issue because thats the common issue.. But im trying to relay to people that my phone is not detected at all, zero recognition of a USB attached device. EXCEPT when in fastboot.. Which makes no sense... If it was a broken port then why does fastboot work????

THE_KINGDOM said:
If it was a broken port then why does fastboot work????
Click to expand...
Click to collapse
Because it could be a single broken connector in the port, it could be a bad internal connector, it could be a motherboard issue, etc.

THE_KINGDOM said:
Wow man you need to cut the estrogen pills out. This is borderline extremely weird...
Click to expand...
Click to collapse
Resorting to childish insults when you are called out is weird for a Man and IMO cowardly.
It is also why you should consider taking you own sage advice.
THE_KINGDOM said:
You gave me one potential plausible scenario
Click to expand...
Click to collapse
Actually, I gave you virtually all plausible scenarios.
THE_KINGDOM said:
this thread was created days before my activity on that other thread.
Click to expand...
Click to collapse
Correct. You did not create a new thread afterwards. You first created a new thread and then posted the same issue in a separate thread.
My mistake.
But still you are here, after you already have your answers, never bothering to thank anyone.
THE_KINGDOM said:
I don't deny that chances are it's an extremely rare hardware issue
Click to expand...
Click to collapse
Good, but IMO, it's not that rare on N5.
THE_KINGDOM said:
And actually I'm very generous with the "thank you" I dish out.
Click to expand...
Click to collapse
I,ll give you the same answer I give most people I encounter who are likely in denial.
Your Right! :good:

I haven't seen this mentioned, just making sure you have turned on usb debugging in the developer options otherwise adb won't work.
Sent from my Nexus 5 using Tapatalk

Related

[Q] PC not recognizing Transformer after returning from ASUS service center[RESOLVED]

I have deleted and reloaded my drivers, though nothing has changed, tried on a 32 bit and a 64 bit pc, and still I cannot get adb to recognize a device plugged in. The device is showing when I plug it in (ASUS Android Composite ADB Interface), so I know it sees it. ADB recognizes my HTC EVO fine with the proper drivers installed.
Could my cord have gone bad all of a sudden not allowing adb to read it?
Did ASUS disable something when they worked on it? I had to send it in twice and the first time I got it back it did this, but I thought maybe it was something I didn't do right, as I didn't spend much time troubleshooting since I sent it back 3 days later.
I can still get into APX mode and flash via NVFlash, so I'm covered on root, rom, and kernel, but I really miss being able to just connect and open a command prompt to do stuff.
I've the same problem when I got back my pad from the service center. At least you use NVFlah and APX mode. For me, none of this work. Like you, I think probably the fault is in the cable.
try wireless adb
Sent from my Titan using Tapatalk.
did you re-enable usb debugging?
AustinMartin said:
did you re-enable usb debugging?
Click to expand...
Click to collapse
Yeah, remembered to do that, as I said it shows up in device manager.
greeny2010 said:
I've the same problem when I got back my pad from the service center. At least you use NVFlah and APX mode. For me, none of this work. Like you, I think probably the fault is in the cable.
Click to expand...
Click to collapse
Odd the cord goes bad after they looked at it, don' t you think? I mean, I ordered one so should have it next week, but I have my reservations that it will resolve the issue.
do you have te asus suite installed? That is required for adb to work.
AustinMartin said:
do you have te asus suite installed? That is required for adb to work.
Click to expand...
Click to collapse
Now that's something I haven't done yet! I'll try as soon as get home, thanks.
That worked!!! Thanks!!
I never installed that before and was using the adb interface all the time. Oh well, not going to lose sleep over it.
Thanks again, AustinMartin

no usb data. need to root -tf101

Long time listener. First time caller.
I have an issue. My tf101 lost the ability to transfer data about week ago. Meaning, its not detectable by computers or any usb device
The tablet was rooted but i returned to stock in an effort to fix the problem and lost root.
I have tried:
3 cables
4 PC's
1 linux box
The tablet charges fine and even trickle charges from usb ports
I narrowed down the problem to a partially corrupt bootloader. Or simply a bad flash(team rouges rec and revolution rom)
I think i may be able to fix the problem by flashing ClockWork recovery, but i need to get root access. Any ideas or am i just screwed?
So im screwed right?
Zone3 said:
Long time listener. First time caller.
I have an issue. My tf101 lost the ability to transfer data about week ago. Meaning, its not detectable by computers or any usb device
The tablet was rooted but i returned to stock in an effort to fix the problem and lost root.
I have tried:
3 cables
4 PC's
1 linux box
The tablet charges fine and even trickle charges from usb ports
I narrowed down the problem to a partially corrupt bootloader. Or simply a bad flash(team rouges rec and revolution rom)
I think i may be able to fix the problem by flashing ClockWork recovery, but i need to get root access. Any ideas or am i just screwed?
Click to expand...
Click to collapse
No, you're not "screwed" You could always just download an over-wifi file transfer app. I'm not sure what the best ones are on the Play Store, but I'd do you research if you're gonna drop a couple bucks on one. I haven't bothered since my Skyrocket is Samsung and I already get Kies Air.
I would suggest after flashing ClockWork recovery trying out some other ROMs and kernels and seeing if that fixes your problem. I would also highly suggest Team Win Recovery Project. It's been my favorite recovery so far, not to mention the touch screen interface is fantastic.
enterflux said:
No, you're not "screwed" You could always just download an over-wifi file transfer app. I'm not sure what the best ones are on the Play Store, but I'd do you research if you're gonna drop a couple bucks on one. I haven't bothered since my Skyrocket is Samsung and I already get Kies Air.
I would suggest after flashing ClockWork recovery trying out some other ROMs and kernels and seeing if that fixes your problem. I would also highly suggest Team Win Recovery Project. It's been my favorite recovery so far, not to mention the touch screen interface is fantastic.
Click to expand...
Click to collapse
Thanks for answering
Ive been using a combination of google drive and file expert for file transfer, but i cant flash any recovery or any rom or adbwireless because i dont have root anymore.
Did you try loading the official USB drivers?
Zone3 said:
Thanks for answering
Ive been using a combination of google drive and file expert for file transfer, but i cant flash any recovery or any rom or adbwireless because i dont have root anymore.
Click to expand...
Click to collapse
So you lost your recovery manager too?
enterflux said:
So you lost your recovery manager too?
Click to expand...
Click to collapse
Yep, and that appears to be my biggest hurdle in solving this issue.
Seems more than a few are having this issue as well
Zone3 said:
Yep, and that appears to be my biggest hurdle in solving this issue.
Seems more than a few are having this issue as well
Click to expand...
Click to collapse
I assume you can still get into APX mode? If so, I would try running this. It's what I initially used to root my TF101, and it doesn't require you to use your installed recovery. Basically it roots and installs CWM recovery from a script run from your computer. Let me know what happens.
enterflux said:
I assume you can still get into APX mode? If so, I would try running this. It's what I initially used to root my TF101, and it doesn't require you to use your installed recovery. Basically it roots and installs CWM recovery from a script run from your computer. Let me know what happens.
Click to expand...
Click to collapse
Yes, the tab can go into apx mode, but the computer wouldnt know if it was in apx. Pc doesn't know the tab exists when plugged in.
Zone3 said:
Yes, the tab can go into apx mode, but the computer wouldnt know if it was in apx. Pc doesn't know the tab exists when plugged in.
Click to expand...
Click to collapse
When plugged in to your computer and in APX mode, check Device Manager and see if there's any unrecognized devices.
enterflux said:
When plugged in to your computer and in APX mode, check Device Manager and see if there's any unrecognized devices.
Click to expand...
Click to collapse
Ive been through that. Its not a simple driver issue. Windows doesnt even acknowledge it as an "unrecognized usb device"
Linux does even list it with the lsusb command.
Same for mac.
There is no data being transfered. It doesnt even attempt usb handshaking...
Zone3 said:
Ive been through that. Its not a simple driver issue. Windows doesnt even acknowledge it as an "unrecognized usb device"
Linux does even list it with the lsusb command.
Same for mac.
There is no data being transfered. It doesnt even attempt usb handshaking...
Click to expand...
Click to collapse
Well, I'm assuming that this is no longer on stock firmware and/or too old to be still under warrantee. The only thing I can think of, unless someone else here can give you an answer, is that it may be a hardware problem and you'd have to send it in to ASUS to get it fixed.....
enterflux said:
Well, I'm assuming that this is no longer on stock firmware and/or too old to be still under warrantee. The only thing I can think of, unless someone else here can give you an answer, is that it may be a hardware problem and you'd have to send it in to ASUS to get it fixed.....
Click to expand...
Click to collapse
Did the OP found a solution to that? I have the exact same issue .
haha,, months after.....
But i am in the same situation...
a lost root and the USB dosnt work, exactly like the autor of this post...
any ideas?
sad_janus said:
haha,, months after.....
But i am in the same situation...
a lost root and the USB dosnt work, exactly like the autor of this post...
any ideas?
Click to expand...
Click to collapse
You need USB to root. I had the same issue and a new USB cable fixed it straight away.
frederuco said:
You need USB to root. I had the same issue and a new USB cable fixed it straight away.
Click to expand...
Click to collapse
hmmm, I'll try when I can get a new cable = (
but from what I've read some have tester with multiple cables and even so the USB dont work,,
sad_janus said:
hmmm, I'll try when I can get a new cable = (
but from what I've read some have tester with multiple cables and even so the USB dont work,,
Click to expand...
Click to collapse
If you have another PC you can try hat is the only other suggestion I have.
frederuco said:
If you have another PC you can try hat is the only other suggestion I have.
Click to expand...
Click to collapse
thanks
yeah, of curse i tried
but no luck. i try everything,
APX dosnt work, USB it is invisible for windows, in any way

A bit of an emergency...

Hey there, guys and gals,
I'm having a bit of an issue here, and it's somewhat serious.
The issue is as follows. I have Android 5.0.1 on my Nexus 5. When I connect my computer to my laptop... nothing.
Nothing at all. It doesn't show up in device manager, not even as unknown. Fastboot doesn't detect it, nor does ADB. I can't do anything, and it's scaring me. I don't know how I could have broken it, but I need to know how to fix it.
I'm happy to do whatever to get it working, so please help...
Update: Tried to factory reset, to see if it would fix the issue. It's stuck "Erasing...", and won't go further. I'm afraid my phone may be hard-bricked... Is it possible to reflash these using JTAG, and if so is there anyone that can assist with that process?
CypherX1389 said:
Hey there, guys and gals,
I'm having a bit of an issue here, and it's somewhat serious.
The issue is as follows. I have Android 5.0.1 on my Nexus 5. When I connect my computer to my laptop... nothing.
Nothing at all. It doesn't show up in device manager, not even as unknown. Fastboot doesn't detect it, nor does ADB. I can't do anything, and it's scaring me. I don't know how I could have broken it, but I need to know how to fix it.
I'm happy to do whatever to get it working, so please help...
Update: Tried to factory reset, to see if it would fix the issue. It's stuck "Erasing...", and won't go further. I'm afraid my phone may be hard-bricked... Is it possible to reflash these using JTAG, and if so is there anyone that can assist with that process?
Click to expand...
Click to collapse
Is it stock or what? are you rooted?
Also , keep in mind that the factory reset can take up to 30 minutes.
IMO it sounds like a busted cable/usb port on either side / incorrect drivers.
Edit : JTAG is not possible on our devices , access is locked from the chipset itself.
Are u on Windows 8.1 if so I had a problem with Windows thinking that my phone was a acer and I had to go the driver settings and manually tell it that it was a ADB USB connection then it would connect fine also could be USB cable I found the nexus 5 to be very picky about cables
Sometimes I get that but it solves by going into dev and checking and unchecking usb debugg, but sounds more like a busted usb plug
Have you considered that you may be using incorrect drivers on your PC? This issue can be caused by having improperly installed drivers.
dkconor said:
Have you considered that you may be using incorrect drivers on your PC? This issue can be caused by having improperly installed drivers.
Click to expand...
Click to collapse
Alxhn said:
Sometimes I get that but it solves by going into dev and checking and unchecking usb debugg, but sounds more like a busted usb plug
Click to expand...
Click to collapse
xstokerx said:
Are u on Windows 8.1 if so I had a problem with Windows thinking that my phone was a acer and I had to go the driver settings and manually tell it that it was a ADB USB connection then it would connect fine also could be USB cable I found the nexus 5 to be very picky about cables
Click to expand...
Click to collapse
Niflheimer said:
Also , keep in mind that the factory reset can take up to 30 minutes.
IMO it sounds like a busted cable/usb port on either side / incorrect drivers.
Edit : JTAG is not possible on our devices , access is locked from the chipset itself.
Click to expand...
Click to collapse
AndreIrawan97 said:
Is it stock or what? are you rooted?
Click to expand...
Click to collapse
Right. I'll address you all at once for ease.
Firstly, the USB connector functions fine. My USB-OTG cable still allows me to access files on a flash drive.
Secondly, drivers can't be an issue in this case. It won't even enumerate the device in device manager. As if the phone simply isn't plugged in.
Thirdly, Win8 isn't the issue, as I"ve had this phone connected to this computer many, /many/ times.
So it must be a problem within Android 5.0.1
But here's the problem. In order to install anything else, I'd have to install a recovery. In order to that, I need root. In order to root, I need USB. I'm lost, guys...
I just had an idea does towel root work on 5.0 if so u could try that?
xstokerx said:
I just had an idea does towel root work on 5.0 if so u could try that?
Click to expand...
Click to collapse
Hmm... That might work. I'll take a look. But if it succeeds, then something gets broken later in the process, this thing is a paperweight, right?
Edit: According to http://forums.androidcentral.com/an...29-rooting-nexus-5-towelroot.html#post4125236 Towelroot will never be possible on Lollipop. I didn't go much further than that though...
Ya I just read that to bummer
Edit: as of now there is no way to root without pc sounds like u may have some sort of hardware failure I'm guessing only way to fix is to send it in and that's 150 bucks min
xstokerx said:
Ya I just read that to bummer
Edit: as of now there is no way to root without pc sounds like u may have some sort of hardware failure I'm guessing only way to fix is to send it in and that's 150 bucks min
Click to expand...
Click to collapse
Well... This happened when I updated via OTA (after reinstalling the stock recovery) to 5.0.1 after 5.0. I did this all over USB. Immediately thereafter, it quit. I got it to boot, btw. The erasing problem fixed itself, and it's now running, but the USB is still stuffed. This is sounding more like software than hardware. Almost as if whatever chip talks via USB lost it's own firmware somehow.
Cable or driver 95% sure. Did you try connecting it to a windows 7 /linux pc ? And ... u can never be sure but try connecting to a usb2.0 port. I had those issues when I accidentally plugged my cable in my frontal panel ( usb3.0)
A few months ago I had the same problem, my phone got not recognized by adb or fastboot. I played around a whole day with drivers and stuff like that. At the end I found a post on the internet describing that not all USB cables are able to do adb connections and I should try the original USB cable that came with my Nexus 5. So I looked for that particular cable and hey presto it worked right away.
And 2$ usb cables do break over time. They might still charge , but one cold solder joint and no connection
CypherX1389 said:
Secondly, drivers can't be an issue in this case. It won't even enumerate the device in device manager. As if the phone simply isn't plugged in.
Click to expand...
Click to collapse
So you are correct. I didn't see that in your post, my bad.
Have you tried with another cable maybe?
Make sure you have either MTP or PTP checked in Settings/Storage/USB computer connection.
Niflheimer said:
Cable or driver 95% sure. Did you try connecting it to a windows 7 /linux pc ? And ... u can never be sure but try connecting to a usb2.0 port. I had those issues when I accidentally plugged my cable in my frontal panel ( usb3.0)
Click to expand...
Click to collapse
Georg2808 said:
A few months ago I had the same problem, my phone got not recognized by adb or fastboot. I played around a whole day with drivers and stuff like that. At the end I found a post on the internet describing that not all USB cables are able to do adb connections and I should try the original USB cable that came with my Nexus 5. So I looked for that particular cable and hey presto it worked right away.
Click to expand...
Click to collapse
Telyx said:
Make sure you have either MTP or PTP checked in Settings/Storage/USB computer connection.
Click to expand...
Click to collapse
Alxhn said:
Have you tried with another cable maybe?
Click to expand...
Click to collapse
Niflheimer said:
And 2$ usb cables do break over time. They might still charge , but one cold solder joint and no connection
Click to expand...
Click to collapse
I've tried multiple cables. I KNOW that this cable is fine for ADB, because it works fine for my other devices. All of them. I may be marked a newbie on the forums, but I'm really not one. When I first signed up for this account I was, but that was in what... '07?
I've tried:
Drivers (Obviously won't work.)
Cables
Rebooting
Factory Reset
Different Computers
Linux
Windows
Switching USB connection modes
Toggling Dev Mode/Debugging on/off
Nothing works. It HAS to be a software issue on the phone. I don't think anyone read it, but it's almost as if the IC that handles USB connections has lost it's firmware. I don't think that can happen, honestly, so it must be whatever's in the ROM that TALKS to that IC that's causing the issue. Problem is, I don't know how to fix the ROM without USB connection and Fastboot.
CypherX1389 said:
Nothing works. It HAS to be a software issue on the phone. I don't think anyone read it, but it's almost as if the IC that handles USB connections has lost it's firmware. I don't think that can happen, honestly, so it must be whatever's in the ROM that TALKS to that IC that's causing the issue. Problem is, I don't know how to fix the ROM without USB connection and Fastboot.
Click to expand...
Click to collapse
Its unlikely that the ROM will be the cause if the USB port suddenly stops working.
Do you have a custom recovery?
If not, then not much you can do except send it in for repair/replacement.

[Q]Nexus 5 doesn't connect to PC and can't download any files...

Hi, guys!
I have a problem..
My Nexus 5 doesn't connect to PC or Mac. Nor for MTP, nor for PTP. Device manager doesn't see phone. No beeps, dinglings etc. But phone is charging as normal.
And aaalso, i can't download files, can't make screenshots, Cabinet won't see anything in downloads, files etc. Tried recover from backup, tried reflash xtrasmooth from TWRP but didn't success. Same problem.. Tried different cables - no success. Tried moving cable - no luck.. Tried chmod from TWRP on /data/media/0 - didn't worked.. I've tried everything. ADB, fastboot not working..
Can someone help?
Thanks in advance. =)
If I remember correctly TWRP does provide an option to repair certain partitions. You could try that. I'm not sure if it will delete your personal data though :/
Flashing a factory image would be a second option. This will delete your files for sure though.
experience7 said:
If I remember correctly TWRP does provide an option to repair certain partitions. You could try that. I'm not sure if it will delete your personal data though :/
Flashing a factory image would be a second option. This will delete your files for sure though.
Click to expand...
Click to collapse
TWRP cannot repair internal storage partition.. At least for me. Other options was unsuccessful (tried repair, fix permissions etc. After permissions my phone even started bootloop).
Well.. did you use file encryption?
experience7 said:
Well.. did you use file encryption?
Click to expand...
Click to collapse
Nope..
Now, i cannot even make my nexus download files and take screenshots..
Do you have any important files on your internal storage? If not, a factory image might be the best try.
experience7 said:
Do you have any important files on your internal storage? If not, a factory image might be the best try.
Click to expand...
Click to collapse
Maybe you're right, but how can i put factory image on my phone without USB and option to download files?)
You don't need to copy it to your phone. It gets flashed via fastboot. Does your computer not even detect the phone in fastboot mode? Drivers installed? Do you use Windows 8?
experience7 said:
You don't need to copy it to your phone. It gets flashed via fastboot. Does your computer not even detect the phone in fastboot mode? Drivers installed? Do you use Windows 8?
Click to expand...
Click to collapse
I use WIn7 and Mac. Fastboot and ADB doesn't detect phone. Tried all 4 drivers from Nexus Tool Kit.
MelonJack said:
Hi, guys!
I have a problem..
My Nexus 5 doesn't connect to PC or Mac. Nor for MTP, nor for PTP. Device manager doesn't see phone. No beeps, dinglings etc. But phone is charging as normal.
And aaalso, i can't download files, can't make screenshots, Cabinet won't see anything in downloads, files etc. Tried recover from backup, tried reflash xtrasmooth from TWRP but didn't success. Same problem.. Tried different cables - no success. Tried moving cable - no luck.. Tried chmod from TWRP on /data/media/0 - didn't worked.. I've tried everything. ADB, fastboot not working..
Can someone help?
Thanks in advance. =)
Click to expand...
Click to collapse
Try this: http://www.nirsoft.net/utils/usb_devices_view.html
Remove all usb drivers and try again. Drivers for adb and fastboot are here: http://developer.android.com/sdk/win-usb.html
Usually it helps.
P.S. You don't need drivers from NRT.
P.S.2 I've noticed that @_MetalHead_ is around. Do not mention NRT or any other Toolkits anymore.
zagorteney said:
Try this: http://www.nirsoft.net/utils/usb_devices_view.html
Remove all usb drivers and try again. Drivers for adb and fastboot are here: http://developer.android.com/sdk/win-usb.html
Usually it helps.
P.S. You don't need drivers from NRT.
P.S.2 I've noticed that @_MetalHead_ is around. Do not mention NRT or any other Toolkits anymore.
Click to expand...
Click to collapse
Hahaha! Hey now, I have no problem with toolkits when used by people who actually know what they are doing, which OP seems to. They just encourage people to jump in the deep end before learning to swim, and that's what I have a problem with. But you know that
Anyways... I don't suspect OP has a driver issue, seeing as though it's also not working with his Mac. It almost seems like a permissions issue, but seeing as though OP tried chmod, then I really don't know what to say. Maybe ask @rootSU, if anybody knows how to fix it, it's him.
_MetalHead_ said:
Hahaha! Hey now, I have no problem with toolkits when used by people who actually know what they are doing, which OP seems to. They just encourage people to jump in the deep end before learning to swim, and that's what I have a problem with. But you know that
Anyways... I don't suspect OP has a driver issue, seeing as though it's also not working with his Mac. It almost seems like a permissions issue, but seeing as though OP tried chmod, then I really don't know what to say. Maybe ask @rootSU, if anybody knows how to fix it, it's him.
Click to expand...
Click to collapse
Yes, probably you are wright. This is just suggestion from my experience. I've had somethimes problems with drivers and allways fixed them with this little software.
But offcourse, we all hope that rootSU gave up from Nexus 6 and then get back here.
zagorteney said:
Yes, probably you are wright. This is just suggestion from my experience. I've had somethimes problems with drivers and allways fixed them with this little software.
But offcourse, we all hope that rootSU gave up from Nexus 6 and then get back here.
Click to expand...
Click to collapse
He went to the N6? No wonder I haven't seem him around in a while.
@Lethargy should know what to do as well.
zagorteney said:
Try this: http://www.nirsoft.net/utils/usb_devices_view.html
Remove all usb drivers and try again. Drivers for adb and fastboot are here: http://developer.android.com/sdk/win-usb.html
Usually it helps.
P.S. You don't need drivers from NRT.
P.S.2 I've noticed that @_MetalHead_ is around. Do not mention NRT or any other Toolkits anymore.
Click to expand...
Click to collapse
Tried already. Both. No luck..
Prostite for my english =)
MelonJack said:
Tried already. Both. No luck..
Prostite for my english =)
Click to expand...
Click to collapse
Try this, with your device connected to the pc go to device manager. Do you see a device with a yellow exclamation mark? If so right click and go to where it lets you choose a driver from your computer. Choose the android composite adb interface.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try this, with your device connected to the pc go to device manager. Do you see a device with a yellow exclamation mark? If so right click and go to where it lets you choose a driver from your computer. Choose the android composite adb interface.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Or in device manager look for something called an acer device (which you obviously don't have) uninstall it's driver if so
jd1639 said:
Try this, with your device connected to the pc go to device manager. Do you see a device with a yellow exclamation mark? If so right click and go to where it lets you choose a driver from your computer. Choose the android composite adb interface.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No yellow exclamation mark..
What if the problem is in permissions and maybe i'm doing something wrong? I have root. Tried to change them from Root Browser - no luck. Tried to make chmod from TWRP - no luck... At least, downloads and USB still not working. (BTW, music is OK and i can see photos, but can't write them)
_MetalHead_ said:
He went to the N6? No wonder I haven't seem him around in a while.
@Lethargy should know what to do as well.
Click to expand...
Click to collapse
He's had the Nexus 6 for over a month now.
MelonJack said:
No yellow exclamation mark..
What if the problem is in permissions and maybe i'm doing something wrong? I have root. Tried to change them from Root Browser - no luck. Tried to make chmod from TWRP - no luck... At least, downloads and USB still not working. (BTW, music is OK and i can see photos, but can't write them)
Click to expand...
Click to collapse
Doesn't show up at all?
What permissions are you changing on what files/folders?
Also, see the first link of my signature, try the 15-second adb/fastboot installer, and if that doesn't work then there is a thread for diagnosing driver issues.
Lethargy said:
Doesn't show up at all?
Click to expand...
Click to collapse
Nope..
What permissions are you changing on what files/folders?
Click to expand...
Click to collapse
Data/media/0/*
/sdcard etc.. I've tried almost on everything...
Also, see the first link of my signature, try the 15-second adb/fastboot installer, and if that doesn't work then there is a thread for diagnosing driver issues.
Click to expand...
Click to collapse
Already done. Not working..

op7 pro recognized in adb but not in fastboot

I feel like I have tried absolutely everything but my computer will not recognize my phone when I type fastboot devices, while in fastboot. When the phone is on though, adb devices shows the device.
I'm curious if anyone else has run into this issue and if so, how did you fix it?
triteshy said:
I feel like I have tried absolutely everything but my computer will not recognize my phone when I type fastboot devices, while in fastboot. When the phone is on though, adb devices shows the device.
I'm curious if anyone else has run into this issue and if so, how did you fix it?
Click to expand...
Click to collapse
Hey pal, I'm no expert but I'd say try download adb driver for your OS version whether it's Windows or Linux. and maybe phone driver as well. Worked for me
niteStalker09 said:
Hey pal, I'm no expert but I'd say try download adb driver for your OS version whether it's Windows or Linux. and maybe phone driver as well. Worked for me
Click to expand...
Click to collapse
Thank you for the response. Did both of those things already.
triteshy said:
Thank you for the response. Did both of those things already.
Click to expand...
Click to collapse
Just making sure but you do have the latest platform-tools?
I've never actually experienced it not being detected in fastboot before so that's really the only solution I can think of.
So just for some one in the future trying to figure out what happened. I managed to get it fixed.
The problem I was running into was that my computer recognized the driver (the regular oneplus driver that you can install when you plug in your phone) only when my phone was using adb (or in other words, my phone was on, in a usable state, in the regular OS, not fastboot or anything).
However when I launched into fastboot, my computer would no longer recognize my phone as the same device.
To fix:
I had to open file explorer on my pc (running windows), then right click "my pc", then manage devices.
There was my phone, right there, but under "unknown device". I right clicked it, and installed a driver for it, however I didn't use the oneplus driver, I used the Samsung phone drivers. It then worked perfectly.
I know that's not good directions but it still may help someone in the future and save them from a horrible headache that I experienced, at least pointing them in the right direction.
GLHF.
I had this happen to me as well. Was driving me nuts. I had to use a different cable. The wrong cable solution usually never works, but for some reason, my older USB-C anker cable would work in ADB but not fastboot. Newer Anker cable worked. I'm sure the OEM cable would work too.

Categories

Resources