Related
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
I just rooted my A510 and ever since my laptop won't recognize my tablet. What can I do? I've tried factory reset, as well as flashing cm10/other roms. I downloaded the os from the acer website but don't know how to flash. Can anyone help me out?
Recovery= cwm
rom = cm10 unofficial
Update I was able to flash back to stock with unlocked bootloader and recovery from the acer website. But still I cannot get any computer to recognize my tablet. I have also lost root. What can I do now? Charging works perfectly so micro usb slot is not messed up.
Did you try another USB Cable ? another PC ?
What's no working ? MTP ? USB Mass Storage ? ADB ? Fastboot ?
Yes I've tried different USB and computers. The problem is that the computer won't recognize tablet in any mode. I'm currently on stock recovery with stock ww jb. I have us version of the tablet. Also update. zip not working in stock recovery. Idk if this is related but this problem occurred after unlocking boot loader also cwm would not mount ext SD. Boot loader is still unlocked. Maybe locking again will fix?
Edit: When in fastboot mode I am able to get usb device not recognized error in windows but have not been able to get it to recognize the device. I have tried pointing driver to acer official drivers but windows rejects these drivers. Device shows up as unrecognized device under device manager in windows and tablet fastboot mode.
Edit2: Windows gives same usb device not recognized error as in fastboot when plugging in using debug mode. Still no solution to this problem.
anybody know how I can fix this? Maybe flashing bootloader again can fix problem? Someone please help!
aamir123 said:
anybody know how I can fix this? Maybe flashing bootloader again can fix problem? Someone please help!
Click to expand...
Click to collapse
yes, you might try to flash all the Firmware using Acer ADT and a full Firmware file (BIN)
aamir123 said:
anybody know how I can fix this? Maybe flashing bootloader again can fix problem? Someone please help!
Click to expand...
Click to collapse
This sounds more like a Windows issue. What version of Windows? The Acer drivers only support Win XP or 7. If you load the Android SDK, those drivers can be made to work. If the USB on the tab recognizes a flash drive, I say look at Windows to resolve.
Also, I believe that once the bootloader is unlocked, it cannot be locked. It maybe can be replaced with a locked one using the fastboot flash command.
Acer Drivers are compatible with Windows 8 x64 (I'm using it)
Shreps said:
yes, you might try to flash all the Firmware using Acer ADT and a full Firmware file (BIN)
Click to expand...
Click to collapse
How would I do that? ADB doesn't recognize the device neither does fastboot. Idk if it is a windows problem since I have tried updating drivers over and over again. I get an error returned saying usb device not recognized. Also I'm having trouble flashing in stock recovery. I put update.zip on root of sd card and external sd but nothing works. External sd doesn't show in recovery.
I'm now having trouble getting the pc to recognize the tablet at all.
Someone Please help.
aamir123 said:
How would I do that? ADB doesn't recognize the device neither does fastboot. Idk if it is a windows problem since I have tried updating drivers over and over again. I get an error returned saying usb device not recognized. Also I'm having trouble flashing in stock recovery. I put update.zip on root of sd card and external sd but nothing works. External sd doesn't show in recovery.
I'm now having trouble getting the pc to recognize the tablet at all.
Someone Please help.
Click to expand...
Click to collapse
I would suggest making a Linux thumb drive (http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows). You don't have to futz with drivers as much in Linux. All ADB and Fastboot commands are available. I used it for my phone and my TF101. An old 2GB USB will suffice.
Any utilities, files, etc. can be placed on the stick for use, as well.
so basically I should boot my computer using a usb drive then connect my tablet to another usb port correct? Also I'm starting to think my usb drivers in the tablet itself are messed up from trying to root. How would I fix that? But I will try what you said first. Thanks
Btw I am unrooted now cuz I flashed Acers stock firmware but it didn't lock bootloader which is weird.
I have tried using the usb stick to boot into linux but that would not recognize my tablet as well. My phone was recognized immediately but my tablet was not. The tablet won't even recognize that a usb is connected when it is connected to the computer, but shows charging when connected to charger. Again I think the usb drivers in the tablet itself are messed up. What can I do?
Do you guys think I could possibly do something in APX mode? Seems like it may be my only hope
anybody?
aamir123 said:
Do you guys think I could possibly do something in APX mode? Seems like it may be my only hope
Click to expand...
Click to collapse
If you still have the USB adapter, try connecting a USB stick to the tablet. If the tablet mounts the stick and you can view files, then there is most likely nothing wrong with the tablet USB. If not, then Acer may still be able to help with a warranty claim. I bought the extended warranty w/ mine.
As I stated earlier, once the bootloader is unlocked, it can't be locked... perhaps replaced, but not locked.
If the USB functions, boot to the Linux stick and run ADB usb.
then plug in the device to see what happens...
Pretty much all you can do in APX is flash the factory image. that's the most primitive state for android devices...
http://forum.xda-developers.com/wiki/APX_mode
You would still need a functioning USB port.
Hope this helps.
pmrmx774 said:
If you still have the USB adapter, try connecting a USB stick to the tablet. If the tablet mounts the stick and you can view files, then there is most likely nothing wrong with the tablet USB. If not, then Acer may still be able to help with a warranty claim. I bought the extended warranty w/ mine.
As I stated earlier, once the bootloader is unlocked, it can't be locked... perhaps replaced, but not locked.
If the USB functions, boot to the Linux stick and run ADB usb.
then plug in the device to see what happens...
Pretty much all you can do in APX is flash the factory image. that's the most primitive state for android devices...
http://forum.xda-developers.com/wiki/APX_mode
You would still need a functioning USB port.
Hope this helps.
Click to expand...
Click to collapse
I tried plugging in the usb drive with the adapter and the tablet was unable to recognize the usb. does this mean that the usb drivers are bad? What are my options? What happens if Acer denies me support due to being out of warranty?
aamir123 said:
I tried plugging in the usb drive with the adapter and the tablet was unable to recognize the usb. does this mean that the usb drivers are bad? What are my options? What happens if Acer denies me support due to being out of warranty?
Click to expand...
Click to collapse
Sounds like a hardware or physical problem. Inspect the contacts on the USB for an obstruction or a misaligned contact. There are 5 contacts on my A700. I would power down before messing with it. Also, check for a loose socket... you did say that the charger works, though.
pmrmx774 said:
Sounds like a hardware or physical problem. Inspect the contacts on the USB for an obstruction or a misaligned contact. There are 5 contacts on my A700. I would power down before messing with it. Also, check for a loose socket... you did say that the charger works, though.
Click to expand...
Click to collapse
Yea the charger works perfectly fine so I don't think that is the problem. It may be usb drivers in the bootloader or something cuz this problem started right after I unlocked the bootloader.
I contacted Acer and they said my tablet is out of warranty and to fix it it'll cause $250. Is there anything else I could try?
Sent from my SGH-T999 using xda app-developers app
aamir123 said:
I contacted Acer and they said my tablet is out of warranty and to fix it it'll cause $250. Is there anything else I could try?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I really don't believe the USB driver was changed when you unlocked the boot-loader. If you replaced the Kernel, that would more likely. This is resolvable by replacing the kernel with stock...doable if you can flash from recovery.
Again, I say inspect the USB contacts. they are really tiny and delicate. If one is crossing another, this can cause your issues. They can be straightened with a lot of patience.
It would be very hard to find the USB port for sale as it is unique to Acer... with the 12VDC capability.
Thanks I will carefully look at the pretty itself. I did not change the kernel before the problem started occurring but did flash cm10'1 to see if that would fix problem amd it didn't. Thank you very much for all of your help!
Sent from my SGH-T999 using xda app-developers app
the micro usb ports pins seem straight to me, they are perfectly aligned. I'm seriously at a loss as to why it still won't work.
Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following Buster's guide I was able to successfully reflash stock firmware and the device runs fine when booted up now.
However, now ADB is not detecting my device. At all. I have tried running the kill-server and start-server commands to see if that would do the trick to no avail. I'm not even receiving an error saying "device not found." Rather, the device listing is left blank whenever I enter the devices command into the command prompt. I can still send commands via fastboot, but I'm concerned that there's something here that I'm missing, or that I have somehow managed to completely bork the motherboard. I have already tried uninstalling and reinstalling the Asus usb drivers, in addition to the ADB drivers/software to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.
Does usb debugging is on?
Graiden05 said:
Does usb debugging is on?
Click to expand...
Click to collapse
Yes, USB debugging is enabled; yes that was the first thing I checked.
Any other ideas?
If You use asus drivers it worth to try universal naked driver.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I'll give that a shot this evening.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I just installed the naked drivers and tried again, but that didn't work either. Fastboot still works just fine, but I'm still at a complete loss as to how to get adb working again.
Thanks for your help thus far.
Hmm... How windows show tablet when You connect it to PC?
Graiden05 said:
Hmm... How windows show tablet when You connect it to PC?
Click to expand...
Click to collapse
Yeah everything *looks* normal, and appears to be acting normally whenever I have the tablet plugged in. When my tablet is booted up and connected to my pc, I can transfer files to and from with no issue. Also when it's plugged in, there are two different entries under the device manager (one for adb and the other for the tablet itself). It's only when I have my tablet running in bootloader mode that things don't seem to want to work correctly.
I even ran netstat last night to see if there were any programs/services using the same port as adb, and even that turned up nothing. Is it possible that I somehow inadvertently altered the settings on my tablet's motherboard when I installed a bad version of CWM, per my original post?
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Graiden05 said:
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Click to expand...
Click to collapse
It wasn't a problem until I flashed the wrong version of CWM, got stuck in a boot-loop and fixed the problem using fastboot to completely wipe my tablet and start over from scratch.
Edit: I suppose I could try a fresh install of Windows.
Try first remove all drivers and software for tablet. Then install universal naked driver.
Graiden05 said:
Try first remove all drivers and software for tablet. Then install universal naked driver.
Click to expand...
Click to collapse
Update: finally got adb to detect my device. Ended up removing everything Android-related from my desktop and re-downloaded/installed everything, including usb drivers. That did the trick.
Thanks again for the help.
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.
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