Database Info

[Q] Waiting for device..

I've been trying to s-off my phone but its giving me the waiting for device status, after hours of googling i am stumped. I installed the latest SDk/drivers etc. adb devices detects my phone, i've even gone and installed pdanet just to see if it will connect and yes it does. HTC sync detects my phone, but revolutionary doesn't which i find very very odd and stressful. I am running windows 7 64 bit and yes i ran the program as admin. If there is anyone with any insight I will gladly appreciate it.
T.I.A!
MODS PLEASE LOCK THIS THREAD UP SOLUTION FOUND!!

I managed to figure it out by replacing AdbWinApi.dll with the newest one from the sdk. Now I am stuck on fastboot as adb doesn't detect it out now. reinstalled fastboot drivers, but nothing happens.

[SOLVED] USB still not recognized (ICS Leak)

Edit:
This problem has been solved. For any of you that are having issues with ADB recognizing your phone, even after you have uninstalled and reinstalled the correct drivers (As I had done several times on 2 computers), a factory reset might be your answer. So, if you are on ICS leak, and the last thing you want to do is try to FXZ back to 2.3.6...Try wiping data/factory reset first. It solved my problem once and for all.
------------------------------------------------------------------------------------------------
First, I must say that I have already found similar threads of this type, and some even with solutions, but I still cannot fix this problem.
I am on ICS Leak on my AT&T Atrix 2 and everything is running great, aside from one thing. I cannot get my computer to recognize my device. When I plug it in, it will charge, but I get no USB options in my notification bar on my phone. I have tried other solutions, and I have installed the necessary drivers, (Windows 7), I have uninstalled and reinstalled, and rebooted with no luck. If anyone could help me, that would be great! Let me know if any more details are needed...

Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?

I had to uninstall drivers and all moto services. Then plug in phone let it look for install drivers. It failed on one of them. I then installed the moto portal disconnected my phone, rebooted computer and phone, plugged it back in and it worked. Good luck.
Sent from my MB865 using Tapatalk 2

Garnerj013 said:
Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?
Click to expand...
Click to collapse
First off if you found similar threads post in them, no need to start a new thread
I'm guessing you are trying to root?
if you are, the script takes a while to run your phone will reboot several times it will tell you when it is done

Garnerj013 said:
Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?
Click to expand...
Click to collapse
adb devices command showing your device? If so, try again.. and wait, like drgravy said.
Or do what leif said and switch between the 3 different usb connection types and wait for the drivers to install.. and try putting it in mtp or ptp mode to run the root batch file..
Sent from my phone's mind

Drgravy said:
First off if you found similar threads post in them, no need to start a new thread
I'm guessing you are trying to root?
if you are, the script takes a while to run your phone will reboot several times it will tell you when it is done
Click to expand...
Click to collapse
Sorry about the new thread. Blame it on the n00b status. I have rooted with this method before on the same model phone with ICS leak and it worked after a few unsuccessful tries. It usually shows some activity in the command prompt, but this time it is hanging at *daemon started successfully*
alteredlikeness said:
adb devices command showing your device? If so, try again.. and wait, like drgravy said.
Or do what leif said and switch between the 3 different usb connection types and wait for the drivers to install.. and try putting it in mtp or ptp mode to run the root batch file..
Click to expand...
Click to collapse
I've tried in every connection mode, and I have the drivers installed. I've been trying every way possible. Also, for simplicity sake, could you tell me how to use the adb devices command? I'm tech savvy but pretty green to the development/programming side of things.

leifemagnuson said:
I had to uninstall drivers and all moto services. Then plug in phone let it look for install drivers. It failed on one of them. I then installed the moto portal disconnected my phone, rebooted computer and phone, plugged it back in and it worked. Good luck.
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Also, once i uninstall Motorola Device Manager, do I have to manually uninstall more drivers, or does that get them all? If not, how do I manually uninstall the drivers?

http://forum.xda-developers.com/showthread.php?p=29609879
I was having the exact same issue where it was hanging at daemon started successfully. Was totally a driver issue. Follow the link in my link...
I would suggest completely uninstalling everything Moto from your PC, rebooting and then follow the steps again, being sure to install those new drivers that are linked in that post.
Edit: I'm trying to remember when I did it....but I seem to recall having a bit of weirdness when I installed the new drivers. I had the install driver wizard pop up while I was installing the drivers from the moto driver executable. I just let the wizard sit there and wait while the moto driver installer did its thing.

So, instead of uninstalling all that is Moto on my laptop, I moved the Moto Device Driver executable and the batch files (with Su and Superuser.apk and all the extras to my desktop. Ran the moto executable and plugged my phone in to install the drivers and rebooted the computer. Still nothing. Do i need adb on my desktop to root my phone? I'm getting flustered with this. It really should be working one way or the other....

Same issue for me..i reinstalled drivers and connected the phone in media transfer mode..rest of procedure same..am successfuly rooted now
Sent from my MB865 using xda app-developers app

devilhunter47 said:
Same issue for me..i reinstalled drivers and connected the phone in media transfer mode..rest of procedure same..am successfuly rooted now
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
I tried and tried to reinstall the drivers, and even installing them on a different PC didn't work. Finally, I did a factory reset, and the phone was recognized by ADB. Thankfully, I am now rooted and on SCv7!! (Thanks to Jimbridgman, Ikrasner, and a couple other devs.) Thank you all.

[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.

Stuck on HTC Screen

Guys, i need some help.
I was able to install the Viper ROM without any problems. But when i did a factory reset, i'm now stuck on the HTC ONE screen. I can still get to the recovery without issue. But i can't reflash it because i don't have anything in my sdcard to flash.
I found somebody had this issue too:
http://forum.xda-developers.com/show...2518736&page=3
I'm trying to push the rom into my sd card but i can't get my computer to recognize my phone! It's having the HTC MCP device driver issue (code 10). Tried installing HTC sync and that didn't help. Tried uninstalling the driver, but it won't allow me to install driver after i uninstall. Tried to update the driver but Windows is saying driver is up to date and won't let me update. Without getting my phone to be recognized by my computer, i can't push anything into my phone.
I posted in the Viper forum and i was told that maybe i need to reflash the boot.img since I'm on S-On. Which i think is the case.
The thing is i can't flash boot.img because of this MTP issue. I tried different cables with different USB ports. Nothing's working. When i plug in with HTC One, it recognizes fine. But when i plug in with One S, it's back to that MTP issue.
Anybody has any suggestions?
Thanks!

kc73837 said:
Guys, i need some help.
I was able to install the Viper ROM without any problems. But when i did a factory reset, i'm now stuck on the HTC ONE screen. I can still get to the recovery without issue. But i can't reflash it because i don't have anything in my sdcard to flash.
I found somebody had this issue too:
http://forum.xda-developers.com/show...2518736&page=3
I'm trying to push the rom into my sd card but i can't get my computer to recognize my phone! It's having the HTC MCP device driver issue (code 10). Tried installing HTC sync and that didn't help. Tried uninstalling the driver, but it won't allow me to install driver after i uninstall. Tried to update the driver but Windows is saying driver is up to date and won't let me update. Without getting my phone to be recognized by my computer, i can't push anything into my phone.
I posted in the Viper forum and i was told that maybe i need to reflash the boot.img since I'm on S-On. Which i think is the case.
The thing is i can't flash boot.img because of this MTP issue. I tried different cables with different USB ports. Nothing's working. When i plug in with HTC One, it recognizes fine. But when i plug in with One S, it's back to that MTP issue.
Anybody has any suggestions?
Thanks!
Click to expand...
Click to collapse
same problem ....sm1 please help

hassam_2010 said:
same problem ....sm1 please help
Click to expand...
Click to collapse
Fixed it!! i used CWM sideload. Go into recovery, then go into sideload. Connect your usb, then open adb. type "adb devices" just to make sure you're connected.
Now, you want to flash the ROM again. Download the zip file and put it into the same folder as adb. then type this command: adb sideload <filename of update.zip> and you're good to go!
Let me know if you have any questions!!

Adb tools keeps showing error device not found ?

I keep getting error device not found with adb tools on two different verizon m8's ?
I was using adb tools 1.0.31 and never had any problem until tonight and my one m8 I had obtained s-off on it a bit over a week ago with no problem at all. I tried to firewater s-off another m8 that belongs to a friend and his keeps getting error device not found and mine does the same thing. My computer has froze up 2 times in the last 2 days I"am on windows 7 I used system restore and went back 5 days no difference.
I even tried another version of adb tools, then I tried my other computer which it never freezes up and same deal on it with multiple versions of adb tools. I have updated all drivers and done all that rebooted over and over I have even removed java on both computers and installed new versions. Really pulling my hair out on this. Even tried multiple usb ports on both computers.
I have also constantly been checking device manager and there are no conflicts on anything and all drivers keep showing that they are the newest driver.
I could see if it was doing it on just the one m8, but on mine also which it was working fine on it just days ago.
Anyone have any ideas ?

You did remember to enable USB debugging, did you? [emoji6]
Sent from my HTC6525LVW using Tapatalk

berndblb said:
You did remember to enable USB debugging, did you? [emoji6]
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Yes I even tried unchecking it then powering off restarting and rechecking it, actually did that all a couple times to rule it out.

Do you see the Android ADB interface in device manager, or are there any yellow exclamation marks there?
For ADB to work you need:
- ADB access on in Developer Settings (USB Debugging)
- The ADB application
- Drivers for your Windows PC for the ADB device to be recognized
You've stated you've done point 1, I don't doubt you have point 2, you need to work on point 3.
Note: The last possibility is you have some external program blocking your access. I've seen some draconian firewalls block USB.

jskup said:
Do you see the Android ADB interface in device manager, or are there any yellow exclamation marks there?
For ADB to work you need:
- ADB access on in Developer Settings (USB Debugging)
- The ADB application
- Drivers for your Windows PC for the ADB device to be recognized
You've stated you've done point 1, I don't doubt you have point 2, you need to work on point 3.
Note: The last possibility is you have some external program blocking your access. I've seen some draconian firewalls block USB.
Click to expand...
Click to collapse
If your talking about my htc it showed working fine and I tried to update the driver and it showed I have the newest driver available. I went through everything on device manager and everything was working fine, and no exclamation marks. Like I said it was working fine as I used it to firewater s-off an at&t m8 2 weeks ago and it worked fine for it. And I did the firewater on 2 other htc phones in the last 2 months. Also I have used the same adb tools for like the last year with no problems. Also I have not changed any programs, and I have used the same antivirus and firewall for the last 2 years so it should not be blocking it.
This is all why it has me stumped ?

It's not as bad as all that.
The next thing I'd do would be to uninstall and reinstall whatever method gave you the drivers. If you installed the HTC Sync software, uninstall and reinstall. If you used some other method, such as the Minimal ADB and Fastboot package, I'd uninstall and reinstall it.
I have to deal with drivers all the time at work. This sort of thing can happen. Windows makes this process more complicated than it is in Linux.

Roefastford said:
I keep getting error device not found with adb tools on two different verizon m8's ?
Click to expand...
Click to collapse
Have you tried a different USB cable?

Doc Ames said:
Have you tried a different USB cable?
Click to expand...
Click to collapse
Yes tried multiple cables and multiple usb ports. With android system running they pick up the phone as a storage device also. It makes no sense. Going to try unistalling drivers and reinstalling as the other guy suggested.

jskup said:
It's not as bad as all that.
The next thing I'd do would be to uninstall and reinstall whatever method gave you the drivers. If you installed the HTC Sync software, uninstall and reinstall. If you used some other method, such as the Minimal ADB and Fastboot package, I'd uninstall and reinstall it.
I have to deal with drivers all the time at work. This sort of thing can happen. Windows makes this process more complicated than it is in Linux.
Click to expand...
Click to collapse
I will try uninstalling and reinstalling the drivers and see if that fixes the problem, thanks.

Figured it out. I was trying to run firewater from bootloader lol, and not with android running. Ok I guess I really messed that up lol.