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.
Related
I'm trying to flash hardSLP, I get to the tricolored bootloader screen with USB at the bottom but when I unplug the USB and plug it back I can not get active sync to connect. Is their something I missing?
Thanks,
Matt
your system is probably installing the wrong USB driver for the new updated mode - you may need to force an install of the proper driver. in my case, running vista ultimate, the system will default to HTC USB driver instead of the microsoft USB interface driver.
Try to continue anyway with the flashing. I'm running XP and got the same thing as you, I rebooted my phone and did the procedure again, even tough I had no "green light", and it worked fine.
Not sure when USB stopped working but nothing I've done let's my HTC One X (AT&T) connect via usb. I'm running CM10.1 and have tried both MTP and USB Storage and none of my PC's will see my phone.
I'm running TWRP 2.5, which I just updated today. When I boot into recovery and mount USB, my PC shows nothing. I boot the phone into recovery and the fastboot line says fastboot AC instead of fastboot USB. I've tried 3 different cables, an older cable that came with a MyTouch 4G, the HOX cable, and a generic USB cable. All three cables work with my wife's HOX, though hers is stock.
I've also tried on two different laptops (one vista, one win7), my PC (win7), even ran an Ubuntu VM on my PC and nothing.
HTC Sync Manager has been installed and is currently uninstalled though I do see the HTC Driver in Programs so it is there. Some times when I plug the phone in I get an error from Windows about the USB device not installing right. One odd thing is I don't see the device anywhere in device manager, nothing other Other, Android Devices or anything like that.
Developer options are turned on, with Android debugging, USB debugging notify turned on. Root access is set to Apps and ADB.
I've tried other things I've found such as turning the phone off and plugging it into the USB and letting windows detect that way. Pretty much at a loss at this point.
al_g said:
Not sure when USB stopped working but nothing I've done let's my HTC One X (AT&T) connect via usb. I'm running CM10.1 and have tried both MTP and USB Storage and none of my PC's will see my phone.
I'm running TWRP 2.5, which I just updated today. When I boot into recovery and mount USB, my PC shows nothing. I boot the phone into recovery and the fastboot line says fastboot AC instead of fastboot USB. I've tried 3 different cables, an older cable that came with a MyTouch 4G, the HOX cable, and a generic USB cable. All three cables work with my wife's HOX, though hers is stock.
I've also tried on two different laptops (one vista, one win7), my PC (win7), even ran an Ubuntu VM on my PC and nothing.
HTC Sync Manager has been installed and is currently uninstalled though I do see the HTC Driver in Programs so it is there. Some times when I plug the phone in I get an error from Windows about the USB device not installing right. One odd thing is I don't see the device anywhere in device manager, nothing other Other, Android Devices or anything like that.
Developer options are turned on, with Android debugging, USB debugging notify turned on. Root access is set to Apps and ADB.
I've tried other things I've found such as turning the phone off and plugging it into the USB and letting windows detect that way. Pretty much at a loss at this point.
Click to expand...
Click to collapse
Helping a gentleman with the same issue in another thread, it sounds to me like a hardware issue.
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
Need help. I was using Miracle Box to flash stock ROM, I don't know how but the phone (Micromax E453) is bricked now. I tried to start phone in Meta Mode (swiched off phone connected to PC by holding volume up button), it worked once, then following some tutorials I uninstalled (and checked, Delete the driver software for this device) MTK USB COM driver under port. Since then phone is not turning on and PC is not recognizing the device. Tired changing the USB cable and even tried it on another laptop, but no go. Kindly share what else I can try. PC has Windows 10 64 bit and MTK preloader vcom driver always has yellow exclamation mark (always installs with error code 10). I have disabled driver signature verificiation.
vnandwana said:
Need help. I was using Miracle Box to flash stock ROM, I don't know how but the phone (Micromax E453) is bricked now. I tried to start phone in Meta Mode (swiched off phone connected to PC by holding volume up button), it worked once, then following some tutorials I uninstalled (and checked, Delete the driver software for this device) MTK USB COM driver under port. Since then phone is not turning on and PC is not recognizing the device. Tired changing the USB cable and even tried it on another laptop, but no go. Kindly share what else I can try. PC has Windows 10 64 bit and MTK preloader vcom driver always has yellow exclamation mark (always installs with error code 10). I have disabled driver signature verificiation.
Click to expand...
Click to collapse
Did you have USB debugging enabled in the device's system settings before it got bricked? If not, you might not get it to connect via USB and be recognized.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Did you have USB debugging enabled in the device's system settings before it got bricked? If not, you might not get it to connect via USB and be recognized.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thank you for your response. Yes, USB debugging was enabled before it got bricked. I was able to successfully see my device when I ran adb -devices command. I was also able to run fastboot commands. Now its completely dead.