I wanted to use nvflash to bring back to clean slate. Could not get the USB driver issue resolved in Windos 7 or XP, Read the threads, just did not work. Also noticed that the USB connect to the GTablet stopped working, it woriked fine for before trying adp. Tried Linux and the device is not seen using LSUSB did see the device is I tried via USB debugging mode. I power on and hold the vol- button see boot screen then unit goes black. No usb connect to PC either after trying.
Reset the device to stock with CWM and PC USB comes back. Is there a utility or something to check the ADP functionality at boot level, has anyone had USB issues that can help? Is it a possible hardware issue?
mrmpo said:
I wanted to use nvflash to bring back to clean slate. Could not get the USB driver issue resolved in Windos 7 or XP, Read the threads, just did not work. Also noticed that the USB connect to the GTablet stopped working, it woriked fine for before trying adp. Tried Linux and the device is not seen using LSUSB did see the device is I tried via USB debugging mode. I power on and hold the vol- button see boot screen then unit goes black. No usb connect to PC either after trying.
Reset the device to stock with CWM and PC USB comes back. Is there a utility or something to check the ADP functionality at boot level, has anyone had USB issues that can help? Is it a possible hardware issue?
Click to expand...
Click to collapse
Try USBDeview: http://www.nirsoft.net/utils/usb_devices_view.html
Disconnect the G Tablet from your PC. Then run USBDeview as administrator (i.e. right click and Run as Administrator in Windows 7). Then uninstall any drivers related to the G Tablet.
Now plug in G Tablet and it should be detected again and you can point it at a properly working ADB driver on your PC.
Have done that, but it seems that it is something on the GTablet that is causing the error. When is is malfunctioning no USB connections work and driver issues pop up, after set to factory the USB works and driver issue for storage go away.
So far I can tell that adp mode from power and vol - unroots my tab and I can not connect to pc. After re-rooting I can connect. Linux can not see device in adp mode.
Update. Returned the unit to sears for a new one and problem solved. I must of had a clinker.
I'm loading a ROM on this Nexus S i9020A. I have unlocked the bootloader and flashed CM 5.0.2.0.
When I boot into recovery, the Windows 7 host reports "This Device Can Perform Faster" and recommends moving the phone to a different port. However all ports on the computer are USB 2 or USB 3. I have tried other ports just in case and I get the same warning.
When I try to download files with ADB PUSH, it takes forever (5-10 minutes), indicating that it is probably running at USB 1 speeds.
Windows Device Manager reports that it is using the "Android Composite ADB Interface" as the USB driver for the phone.
I have performed a ROM update using the same procedure on another Nexus S on the same computer with the same drivers, and I did not have this issue.
Why does this happen, and how can I solve it? Is there something wrong with the phone or its USB port?
As a workaround, it seems to be possible to unplug the USB cable and plug it back into the same port. In the few times I tried it, it would correctly connect at full speed. There must be some timing issue when the USB port is initialized in CM Recovery that causes the problem with Windows.
Hi,
Have a TF101 tablet here stock rom, stock recovery...
However it seems the USB will not detect on a windows PC tried multiple cables multiple PC's tried from recovery nothing is detected in device manager at all. Tablet doesn't even detect that its connected to PC either.
Is there anyway to root this thing without USB??? I need to root it so I can install recovery and flash another rom.
Thanks,
Which Windows version are you running?
If you use Win 7 and prior you should be able to connect with the universal naked drivers manually installed from device manager
Win 8 and above need driver signing disabled or they wont install the driver and the PC wont see the TF
If you have already tried the above, you might need a new cable
http://forum.xda-developers.com/showthread.php?t=1688012
*Detection* said:
Which Windows version are you running?
If you use Win 7 and prior you should be able to connect with the universal naked drivers manually installed from device manager
Win 8 and above need driver signing disabled or they wont install the driver and the PC wont see the TF
If you have already tried the above, you might need a new cable
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
Thanks. Well i tried windows 7 x64 and windows 8 x64, neither showed any device or unknown device in device manager... Tried multiple cables as wel, no dice...
Shouldn't MTP work regardless of drivers installed in windows 7/8 ?
Are you putting the TF into APX mode?
Connect TF to PC USB > Power Off TF > Hold Power & Volume Up until the PC recognises it (Only takes a couple seconds, nothing appears on the TF screen) then install drivers
You need APX mode for Easyflasher
For normal media transfer, it will still need to install at least some USB type driver, as do all USB devices to function, possibly not the APX drivers
Check in Developer Options > USB Debugging mode
Try it enabled and disabled with the TF plugged in
But really the MTP drivers are not what you need if you want to root. you need APX mode to work (As above)
*Detection* said:
Are you putting the TF into APX mode?
Connect TF to PC USB > Power Off TF > Hold Power & Volume Up until the PC recognises it (Only takes a couple seconds, nothing appears on the TF screen) then install drivers
You need APX mode for Easyflasher
For normal media transfer, it will still need to install at least some USB type driver, as do all USB devices to function, possibly not the APX drivers
Check in Developer Options > USB Debugging mode
Try it enabled and disabled with the TF plugged in
But really the MTP drivers are not what you need if you want to root. you need APX mode to work (As above)
Click to expand...
Click to collapse
Doesn't seem to do anything when I hold power vol+, the screen of the tablet (blank/off) and on the pc nothing is being detected.
I can get to the bootloader/recovery via holding power vol- though. Also tried USB debugging mode... nothing is detected whatsoever... ordering another cable on ebay will see if that works but I doubt it since it seems to be a common issue with this tablet (port not working with pc)
I edited my post
Nothing will appear on the TF screen in APX mode until data transfer begins
The cheap non genuine cables are renowned for data connection failing, genuine cables are recommended
I still have my original cable and it still works 100%
*Detection* said:
I edited my post
Nothing will appear on the TF screen in APX mode until data transfer begins
The cheap non genuine cables are renowned for data connection failing, genuine cables are recommended
I still have my original cable and it still works 100%
Click to expand...
Click to collapse
Using the original cable, I still can't tell if its in APX mode, installed all the drivers provided by asus, nothing is detected in windows device manager. I'm 100% its not being detected ie. no connection. I ran easyflasher anyway both sbk1 and sbk2 says it flashed recovery but it never did still the stock recovery is on the tablet.
Will try again once the new cable comes in, thanks.
Forget the ASUS drivers, use the Universal ones from the Easyflasher thread
Here's what will happen when its working as intended
When you plug the TF into the PC, no matter what mode it is in, the PC should sound the USB connect sound
When you power off the TF, then put it in APX mode, the PC will again sound the USB connect noise, then it will fail to install the correct drivers
That's when you open Device Manager, find the ! missing driver ! exclamation mark, and update drivers manually pointing it to the extracted Universal drivers
Once you have installed them, then Easyflasher should work as normal
So unless you actually have a hardware fault on the TF, or the USB ports of the PC, Id hedge my bets on the cable
Have you tried a different PC?
*Detection* said:
Forget the ASUS drivers, use the Universal ones from the Easyflasher thread
Here's what will happen when its working as intended
When you plug the TF into the PC, no matter what mode it is in, the PC should sound the USB connect sound
When you power off the TF, then put it in APX mode, the PC will again sound the USB connect noise, then it will fail to install the correct drivers
That's when you open Device Manager, find the ! missing driver ! exclamation mark, and update drivers manually pointing it to the extracted Universal drivers
Once you have installed them, then Easyflasher should work as normal
So unless you actually have a hardware fault on the TF, or the USB ports of the PC, Id hedge my bets on the cable
Have you tried a different PC?
Click to expand...
Click to collapse
Ok, well ya thats the thing no sound or detection of anything when plugging it in, or going into apx mode, rebooting etc...
I tried 2 cables and 2 different PCs. Will try a new cable but I betting that is won't work either... we'll see.
Thanks again
No need to bother with cables and drivers, just download Baidu Root: https://app.box.com/s/pyehf9fh4xem3hy50dot
EDIT: The app has built-in su access management, but I'd recommend installing SuperSU from the Play Store.
Duchman said:
No need to bother with cables and drivers, just download Baidu Root: https://app.box.com/s/pyehf9fh4xem3hy50dot
EDIT: The app has built-in su access management, but I'd recommend installing SuperSU from the Play Store.
Click to expand...
Click to collapse
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!! Worked to let me get TWRP installed and flashed a new rom with SU etc...
Thanks again!!!!!!!!!
Hi Guys,
I've had a few problems with my N5 recently...
If I plug my N5 into my PC via the stock USB cable and boot into the Bootloader (PWR+VOLDN) then it will allow me to flash the original N5 firmware, located here: https://developers.google.com/android/nexus/images, this would indicate to me that there is no issue with the actual devices ability to transfer files via USB connection... Right?
No!
For some strange reason my phone will allow me to push a full factory image to it and will also process any Fastboot commands that are sent to it but as soon as you boot into something like TWRP and try to control the phone's ADB functionality it will not find the device at all! The new MTP option in TWRP 2.8 will allow my computer to see my phone's MTP connection for about 1 second and then will immediately disconnect, the same happens when trying to connect to MTP from within Android too.
USB debugging doesn't show that it is connected when my phone is plugged into my PC and Windows makes the 'device connected' sound and then straight after makes the 'device disconnected' sound...
Any ideas? I am certain that this is an issue with my handset's hardware or software rather than any of the computers or cables... I have tried 3 different cables (including the stock cable) and also three different computers (Windows 8.1 @ Work, Mac OS X @ Work and my own personal PC running Windows 8.1 & Ubuntu @ Home)... All OSs and all computers run into exactly the same issue, device connects briefly and then disconnects.
I have troubleshooted issues relating to the driver. This is not the issue... Device Manager cannot even see the hardware after the disconnect.
Thanks for any help in advance,
Lewis
Also:
-Android does not detect that the USB is charging the device unless the device is booted with the cable attached (if it's not attached before the 'Google' screen then it can't see the USB input at all, within android or TWRP, of course...).
Having the exact same problem. Did you find a solution?
EvilBetty said:
Having the exact same problem. Did you find a solution?
Click to expand...
Click to collapse
It's most likely a driver issue.
Elluel said:
It's most likely a driver issue.
Click to expand...
Click to collapse
Not a driver issue.
3 different Nexus 5s, 5 different workstations. Other two Nexi are fine on all 5 PC's.
1 PC used for ADB forensics, 2 used for ADB development work, one known working for ROM'ing / rooting.
Phone has been factory reset, factory ROM'd from Fastboot. Connects fine on Fastboot. Will not connect on ADB / MTP.
On a fresh PC / phone reboot, the PC will detect the phone for just a second and then it will not reconnect until process is completed.
-EB
What's your adb version?
Went on for about 2 weeks, then suddenly went away on its own. I have no idea what the problem was or the solution. Sorry.
i have a nexus 5 which has stock ROM and blu spark kernel . i locked the bootloader while on the same kernel and again unlocked it . . the phone is bootlooping into twrp and the google logo . in twrp it says unable to mount data . i can access twrp . . i am unable to flash anything . it says unable to mount data/ . please the attachment
Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
wwwiesel said:
Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
Click to expand...
Click to collapse
Hmmm, intermittent ADB occured before attempted sideload falure.
Boot to bootloader and see if you can
fastboot devices
If you can detect the device in fastboot, but still cant ABD, then maybe take a look here http://forum.xda-developers.com/showpost.php?p=59420668&postcount=322
After looking there, if you are absolutely certain that it is not a driver issue, you might be 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 sideload.