Database Info

[Q] Unbricked successfully, ADB broken?

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.

[Q] Do I need HTC drivers after a Cyanonegmod rom is installed?

Do I need HTC drivers after a Cyanonegmod rom is installed?
Acutally I can't connect my device to the PC (Win7 x64).
Thanks
Sent form HTC One S Ville C2

Andrewww65 said:
Do I need HTC drivers after a Cyanonegmod rom is installed?
Thanks
Sent frm HTC One S Ville C2
Click to expand...
Click to collapse
You need HTC drivers Doesn't matter which ROM you have installed.

LS.xD said:
You need HTC drivers Doesn't matter which ROM you have installed.
Click to expand...
Click to collapse
What do you think about this problem? Why my PC dosen't reognice my device?

Andrewww65 said:
What do you think about this problem? Why my PC dosen't reognice my device?
Click to expand...
Click to collapse
You want to connect your storage to copy files? Try uninstalling all drivers.

LS.xD said:
You want to connect your storage to copy files? Try uninstalling all drivers.
Click to expand...
Click to collapse
Since I installed Cyanogenmod 4.3 onto my device I can connect my storage but without enabling the storage my PC doesn't recognize the device properly.
The reason my asking is I'd like to update the recovery (as I heard TWRP 2.6.0.0. does't support KitKat and want to upgrade it to 2.6.3.0. or newer).
When I try to flash a newer recovery with fastboot I get an error message "device not found". Doesn't matter the storage connection is on or off. Unfortunately my ROM doesn't have setting for fast reboot or something but I assume it's off.
The latest official HTC driver's installed.

Andrewww65 said:
Since I installed Cyanogenmod 4.3 onto my device I can connect my storage but without enabling the storage my PC doesn't recognize the device properly.
The reason my asking is I'd like to update the recovery (as I heard TWRP 2.6.0.0. does't support KitKat and want to upgrade it to 2.6.3.0. or newer).
When I try to flash a newer recovery with fastboot I get an error message "device not found". Doesn't matter the storage connection is on or off. Unfortunately my ROM doesn't have setting for fast reboot or something but I assume it's off.
The latest official HTC driver's installed.
Click to expand...
Click to collapse
You need the drivers but not htc sync. That should be uninstalled. I've also had problems with adb but i've noticed that if connection to pc is set as MTP the pc recognize it and ADB works. You can try this as well
Sent from nowhere over the air...

I've read several threads here...
Rapier said:
You need the drivers but not htc sync. That should be uninstalled. I've also had problems with adb but i've noticed that if connection to pc is set as MTP the pc recognize it and ADB works. You can try this as well
Sent from nowhere over the air...
Click to expand...
Click to collapse
It could be a stupid question but how to connect the device and PC as MTP?
I've read several threads here and found MTP drivers in .cab files including .inf and .cat files. When I tried to update the portable devices drivers I get the message (My Windows7 x64 is Hungarian, maybe the translation isn't totally correct): "You already installed the up to date driver - WPD file system driver"
Just to summarize the situation:
- HTC One S Ville C2 - Unlocked but S-on !!!
- HTC sync and HTC sync manager are uninstalled.
- Unofficial Cyanogenmod 10.2 by bilal_liberty - I do not have an option to check whether the usb debugging is on or off.
- When I connect the device the windows can see it, gives it a driver letter but I can' use any fastboot/flash command.
- My phone recognize the connection and offers to turn on the usb storage and it works.
Thanks for your help.

Andrewww65 said:
It could be a stupid question but how to connect the device and PC as MTP?
I've read several threads here and found MTP drivers in .cab files including .inf and .cat files. When I tried to update the portable devices drivers I get the message (My Windows7 x64 is Hungarian, maybe the translation isn't totally correct): "You already installed the up to date driver - WPD file system driver"
Just to summarize the situation:
- HTC One S Ville C2 - Unlocked but S-on !!!
- HTC sync and HTC sync manager are uninstalled.
- Unofficial Cyanogenmod 10.2 by bilal_liberty - I do not have an option to check whether the usb debugging is on or off.
- When I connect the device the windows can see it, gives it a driver letter but I can' use any fastboot/flash command.
- My phone recognize the connection and offers to turn on the usb storage and it works.
Thanks for your help.
Click to expand...
Click to collapse
The debugging ON is done in the Dev Options. If you don't have Dev Options you should go to about phone an tap several times on the Build Version till you got the message "Now you're a developer"
I don't remember in CM1.2 but in CM11 there's a menu in Settings-Storage to change from UMS to MTP

Rapier said:
The debugging ON is done in the Dev Options. If you don't have Dev Options you should go to about phone an tap several times on the Build Version till you got the message "Now you're a developer"
I don't remember in CM1.2 but in CM11 there's a menu in Settings-Storage to change from UMS to MTP
Click to expand...
Click to collapse
Ok it's done. Thank you so much (button pushed:good.
I don't know why the dev option is hidden in CMs like this.
So Dev option/Debugging is on and MTP connection enabled. Now I get a new error message: "device offline". But it's on. Screen unlocked etc.:crying:

Andrewww65 said:
Ok it's done. Thank you so much (button pushed:good.
I don't know why the dev option is hidden in CMs like this.
So Dev option/Debugging is on and MTP connection enabled. Now I get a new error message: "device offline". But it's on. Screen unlocked etc.:crying:
Click to expand...
Click to collapse
This could be due to older or incorrect drivers. I had some issues several times due to improper drivers and I had to try several times till it worked. Starting with the HTC ones and up to the default Google drivers found in the Android SDK. Finally I make it work but believe me, I don't know how it worked I just tried until I got the proper drivers that worked

Rapier said:
This could be due to older or incorrect drivers. I had some issues several times due to improper drivers and I had to try several times till it worked. Starting with the HTC ones and up to the default Google drivers found in the Android SDK. Finally I make it work but believe me, I don't know how it worked I just tried until I got the proper drivers that worked
Click to expand...
Click to collapse
Thanks Rapier! I will do like that.

[Q] fastboot, win7/64 drivers?

Hey all,
I've got a new-to-me TF700. Got CROMBi-KK installed, which took some backflips as I could not get fastboot connectivity.
I'd like to be setup for NvFlash (but then never need it), so even though I don't need fastboot right now, I'm feeling the lack.
Data transfer works fine.
ADB (not fastboot) works fine (adb shell gets me a shell, etc, etc)
When I put the phone in fastboot/bootloader "fastboot devices" gets an empty response "fastboot reboot" gets no response.
In Win7 device manager, the TF700, which appears in the "portable devices" section normally when I plug it in, does not appear.
So... probably device drivers.
Have you had this problem on your w7/64 box? How did you fix it? Sorry, but "install linux" isn't all that helpful.
Thanks!

From a semi-related question I'd asked, berndblb mentioned
berndblb said:
Windows is infamous for driver problems.....
Connect the tab in fastboot and open device manager. Near the top you should have an entry for Android device, bootloader mode or something similar, and probably a yellow ! next to it.
Right click it and choose "update driver", let Windows search for it.
If you're lucky it'll install the driver by itself.
If not: What Windows version are you running?
Click to expand...
Click to collapse
Yep, I get an "unknown device" in the USB section when I connect a TF700 in fastboot. Win can't find an appropriate driver. I've tried (manually) ASUS_Android_USB_Drivers and Universal_Naked_Driver_0.72 (both, AFAIR, from the xda tf700 forums). Neither worked.
So... if you got this going, what driver did you use? Thx!

I have a Win7 32 bit laptop and this cool little tool installed the drivers for me:
http://forum.xda-developers.com/showthread.php?t=2588979

berndblb said:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
I'd installed that previously (easiest way to setup fastboot). Re-downloaded, re-installed. Went fine. Still no fastboot.
Unzipped the exe, looked at the drivers being installed - labeled "google". No google driver in the driver cache (so no device ever associated with it.)
Looked at the driver error again. Code 43. That means hardware or driver. I'd been taking it to mean driver, but... switched the USB cable to a port in the rear of the PC - and it worked.
Thanks!
So, for anybody with a similar issue, install the package above. If that doesn't work, maybe try a different USB port.

[Q] Soft brick but no adb/fastboot connection

Hey
A couple of days ago i tried to install the latest CM12 nightly. After updating it my phone crashed everytime it booted up. I did a factory reset and tried to flash older versions but nothing seemed to work so i went into CWM recovery 6.0.4.5 and pretty much formatted everything.
I still have access to the bootloader and recovery but my Windows 8.1 PC doesn't recognize my phone ("Unknown usb device" "Windows has stopped this device because it has reported problems. (Code 43)") I can't access my phone with adb or fastboot now. This looks like a driver problem but i tried a lot of different drivers on multiple PC's.
What can i do now?

Try this thread, could help...
http://forum.xda-developers.com/showthread.php?t=2588979

Darth said:
Try this thread, could help...
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
He said that he can't access his phone with adb or fastboot. Maybe he must try to resolve driver problems first?

zagorteney said:
He said that he can't access his phone with adb or fastboot. Maybe he must try to resolve driver problems first?
Click to expand...
Click to collapse
It's a driver issue likely. Starting from scratch in the thread I linked addresses drivers. Likely ones he hasn't tried.
Though, a few other ideas are trying another cable, another USB on the computer. And last... Try another computer. ?

Darth said:
It's a driver issue likely. Starting from scratch in the thread I linked addresses drivers. Likely ones he hasn't tried.
Though, a few other ideas are trying another cable, another USB on the computer. And last... Try another computer.
Click to expand...
Click to collapse
And in future: please, stay on stock.

No driver seems to work. Is it possible to install a zip from an usb flash drive with OTG?

dermaxe said:
No driver seems to work. Is it possible to install a zip from an usb flash drive with OTG?
Click to expand...
Click to collapse
Try this: http://nirsoft.net/utils/usb_devices_view.html
It helped me a few times.

I uninstalled everything from there that was android-related. After plugging in my phone (in bootloader mode) my PC detects it as " Google Nexus BootLoader Interface" but "this device cannot start. (code 10) an invalid parameter was passed to a service or function"

dermaxe said:
I uninstalled everything from there that was android-related. After plugging in my phone (in bootloader mode) my PC detects it as " Google Nexus BootLoader Interface" but "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
Click to expand...
Click to collapse
Did you use USBDeview or you just manually removed all drivers that you saw?

I went into USBDeview and uninstalled everything that was android related

ummm why hasnt everyone mentioned the very basics? USB Debbugin enabled?
you already flashed and reset phone...
because after any reset, that will default back to unchecked and u wont be able to adb or fastboot until that is checked

How do i enable usb debugging without any os?

dermaxe said:
How do i enable usb debugging without any os?
Click to expand...
Click to collapse
chaco81 said:
ummm why hasnt everyone mentioned the very basics? USB Debbugin enabled?
you already flashed and reset phone...
because after any reset, that will default back to unchecked and u wont be able to adb or fastboot until that is checked
Click to expand...
Click to collapse
USB debugging enabled is only needed when using Adb from within the Android OS. It's not needed for adb use in recovery mode, and never needed for fastboot.
??

good to know

Okay so i don't have to do this but i still have that driver problem. It is recognized as Android Bootloader Interface but i still get "this device cannot start. (code 10) an invalid parameter was passed to a service or function"

dermaxe said:
Okay so i don't have to do this but i still have that driver problem. It is recognized as Android Bootloader Interface but i still get "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
Click to expand...
Click to collapse
For me this sounds more like computer realted problem rather than device. If you can try all of those steps ( installign drivers, etc ) on another pc maybe this will solve your issue

Just tried it on a fresh installation of W7 but my device wasn't recognized and i couldn't install any drivers for it. How can it be a PC related problem if it doesn't work on so many different configurations?

If you run it on VirtualBox, see this answer (prepend http, I can't post links): superuser.com/a/887249/239087
To make it short, you need VirtualBox Extension Pack, and you need to configure the USB port to use USB 2.0 at least.

Moto G USB Problem

Greetings, everyone!
Okay so a few days ago I fell asleep while using my phone, a Moto G 2014 (XT1068). At one point I wake up to see a window saying something along the lines of 'Updating X of X Apps" on a black screen. I put my phone on my bedside table and fall asleep again. When I wake up, the phone's off so I assumed it was done doing whatever it was doing (which I now think it was some sort of system update), so I turn it on only to find out it gets stuck in the Motorola logo loading screen. I've left it like that for maybe an hour and it's just stuck there. I've accessed Fastboot to try the Recovery option but it just returns a 'Boot Up Failed' message and if I choose the 'Factory' option (which I assume is a factory reset), it also gets stuck in the Motorola logo loading screen. The other options are 'Normal PowerUp', 'Barcodes' & 'BP Tools', none of them doing anything either. Upon some research, I figured it was probably some sort of update that crashed down the whole thing and that apparently a way to solve this would be to flash the phone with the Stock ROM, which I've already acquired (and hopefully it's the right one). Now, thing is, I need to connect my phone to the computer, which is running Windows 10, while on the Fastboot menu. This is where the problem comes in. I never enabled USB Debugging in the settings. I've also installed the Motorola Device Manager from the Motorola website because apparently it installs the drivers for the phone, but after installing the MDM countless times, I just don't see drivers anywhere. I've checked the Device Manager on Windows and there's no track of my phone's drivers in there whatsoever. There's no 'Other Devices' tab anywhere and my PC doesn't do that "device was plugged in" sound effect when you connect something through USB. I've downloaded ADB Drivers and different versions of Motorola Drivers but nothing seems to work. I've tried 6 different cables in 10 different ports, still nothing. The phone charges but it's like the PC doesn't detect it. While on the Fastboot menu, according to a few videos I've watched, it is also supposed to say a USB Cable is connected when you connect the phone to the computer, but even though my phone is connected to my PC, that never shows up. I don't know if this is because the drivers might not be installing on my computer or if it's because I never enabled USB Debugging in the settings. I've seen some people say it doesn't need to be enabled while in Fastboot but I don't know if that's true or not. So I'm pretty much out of ideas at this point, do you think something might be done?
Thank you in advance,
- Nervly

Hello, did you try typing in `fastboot devices` while in fastboot ?

-Hope- said:
Hello, did you try typing in `fastboot devices` while in fastboot ?
Click to expand...
Click to collapse
Hey, thanks for replying!
I did, but it wasn't recognized. I also tried 'adb devices' but it just returned an empty list of devices attached. Any other commands just returns <waiting for device> and I'm guessing this is all happening because the drivers might not be actually getting installed (considering there's no track of them in device manager) and/or because my PC doesn't detect the phone as connected through USB (even though it is). The PC doesn't play the sound effect of when you connect something to it and the fastboot menu doesn't display the message "USB Cable Connected" (or something along those lines).

Nervly said:
Hey, thanks for replying!
I did, but it wasn't recognized. I also tried 'adb devices' but it just returned an empty list of devices attached. Any other commands just returns <waiting for device> and I'm guessing this is all happening because the drivers might not be actually getting installed (considering there's no track of them in device manager) and/or because my PC doesn't detect the phone as connected through USB (even though it is). The PC doesn't play the sound effect of when you connect something to it and the fastboot menu doesn't display the message "USB Cable Connected" (or something along those lines).
Click to expand...
Click to collapse
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
http://answers.microsoft.com/en-us/...ment-win/a53ec7ca-bdd3-4f39-a3af-3bd92336d248
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:

-Hope- said:
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
<link>
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
Click to expand...
Click to collapse
I'm off to a job interview right now but I will try the disabling drivers signature method you suggested once I get back.
As for the device manager, showing hidden drivers still doesn't list the phone's drivers or the 'Other Devices' tab, sadly. Perhaps after I disable the drivers signature enforcement and try to install the phone's drivers again it will work. I'll keep you updated!
Thank you for the help thus far!

-Hope- said:
Using a windows 10 and installing drivers may require you to disable drivers signature enforcements
Check here:
http://answers.microsoft.com/en-us/...ment-win/a53ec7ca-bdd3-4f39-a3af-3bd92336d248
Also go to device manager then press the view drop list > show hidden drivers
Check if the drivers are already there
If they are right click on them uninstall and reinstall drivers
Reply back :highfive:
Click to expand...
Click to collapse
Alright, I just got back and tried to disable the drivers signature enforcement thingy but it sadly still didn't work. The drivers still won't show up on the Device Manager and my phone still won't be detected by the computer. What's weird is that it seems like the drivers are being installed because there are some .sys files related to Motorola in my C:\Windows\System32\drivers folder but nothing will detect them.

Nervly said:
Alright, I just got back and tried to disable the drivers signature enforcement thingy but it sadly still didn't work. The drivers still won't show up on the Device Manager and my phone still won't be detected by the computer. What's weird is that it seems like the drivers are being installed because there are some .sys files related to Motorola in my C:\Windows\System32\drivers folder but nothing will detect them.
Click to expand...
Click to collapse
Fastboot drivers aren't same as USB drivers
They differ so if you want to work with fastboot you need fastboot drivers