Database Info

Need help

I relocked my bootloader and tried running a RUU but it keeps telling me that my phone is not connected. I'm using parallels for mac, I installed the drivers and I notice that when i connect the phone it doesn't say "fastboot usb" but when i push volume down is changes yet it still is unable to detect the phone. I installed the htc drivers but when I connect the phone is shows i dont have the drivers for " HTC Remote NDIS based device"
Could this be because im using parallels instead of a full windows pc?
please help, this is my very first android device and im scared I already ruined it

Yeah parallels is touchy. It works in VMware. Make sure in vm settings the usb device for the phone is set to always available to windows. If it is set to ask then it can lose connection.

Ok, Ill give a try.

I still have another problem. When I try to install the htc drivers, I get an error saying device not found. How am I able to install the drivers now?

I found the best way to get the driver installed is to install HTC sync

Thanks for the replies gunnyman, I have one last problem and hopefully theres a fix. I have a low battery and unable to flash the RUU. Is there a fix?

Is there battery actually low? Just shut down the phone and charge it up.

When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?

Jaykelso said:
When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?
Click to expand...
Click to collapse
Sorry. No idea. Sounds like it.

Fastboot doesn't work on Windows 8.1

So before installing Windows 8.1, adb and fastboot worked beautifully, however after grabbing the update from the Metro store, fastboot doesn't work, my phone isn't recognized. It says something about "failed enumeration" in the device manager. I've tried reinstalling HTC Sync and redownloading it from HTC's site ti get the latest drivers (after which I uninstall HTC Sync of course)
I've also tried Koush's drivers but neither installs the fastboot driver.

Theshawty said:
So before installing Windows 8.1, adb and fastboot worked beautifully, however after grabbing the update from the Metro store, fastboot doesn't work, my phone isn't recognized. It says something about "failed enumeration" in the device manager. I've tried reinstalling HTC Sync and redownloading it from HTC's site ti get the latest drivers (after which I uninstall HTC Sync of course)
I've also tried Koush's drivers but neither installs the fastboot driver.
Click to expand...
Click to collapse
I have been trying to get it recognized in fastboot for pas four hours without any luck.. Prior to this, I also had W8 with working fastboot and now I get the same error as well. I tried numerous times, even uninstalled all my drivers (except for display and mouse) to do a clean driver reinstall, but without luck :/

Theshawty said:
So before installing Windows 8.1, adb and fastboot worked beautifully, however after grabbing the update from the Metro store, fastboot doesn't work, my phone isn't recognized. It says something about "failed enumeration" in the device manager. I've tried reinstalling HTC Sync and redownloading it from HTC's site ti get the latest drivers (after which I uninstall HTC Sync of course)
I've also tried Koush's drivers but neither installs the fastboot driver.
Click to expand...
Click to collapse
rs70 said:
I have been trying to get it recognized in fastboot for pas four hours without any luck.. Prior to this, I also had W8 with working fastboot and now I get the same error as well. I tried numerous times, even uninstalled all my drivers (except for display and mouse) to do a clean driver reinstall, but without luck :/
Click to expand...
Click to collapse
Hi, can you guys try this method if you still in windows 8.1???
I personally having a samsung phone and I also having this problem after upgraded to windows 8.1 but now I'm back to windows 8 so I just cannot test it. After test please report back the results to me and I really hope it works. Thanks~
By the way, can you guys tell me your phone model???

DreamerTKM said:
Hi, can you guys try this method if you still in windows 8.1???
I personally having a samsung phone and I also having this problem after upgraded to windows 8.1 but now I'm back to windows 8 so I just cannot test it. After test please report back the results to me and I really hope it works. Thanks~
By the way, can you guys tell me your phone model???
Click to expand...
Click to collapse
Well, I tried something similar, but whenever I uninstalled the usb port from device manager, it reinstalled back and reported that the device is not recognized..
I've got HTC One and its drivers don't work on 8.1. However, I installed HTC drivers (by installing and uninstalling HTC Sync Manager - possibly the lamest method that exists) on Vista and it instantly recognized the phone. So the five hours on 8.1 could have been saved by spending circa 3 minutes on Vista.
But on some forum somebody mentioned that you can use live CD of linux and it will get recognized easily

rs70 said:
Well, I tried something similar, but whenever I uninstalled the usb port from device manager, it reinstalled back and reported that the device is not recognized..
I've got HTC One and its drivers don't work on 8.1. However, I installed HTC drivers (by installing and uninstalling HTC Sync Manager - possibly the lamest method that exists) on Vista and it instantly recognized the phone. So the five hours on 8.1 could have been saved by spending circa 3 minutes on Vista.
But on some forum somebody mentioned that you can use live CD of linux and it will get recognized easily
Click to expand...
Click to collapse
Thanks for your fast reply. Seems that even Microsoft is providing free update for windows 8 but a phone that unable to flash by using bootloader is kinda useless for unofficial ROM users like us.
I have something don't understand from your post. You mentioned that install and uninstall the sync manager on Vista but why not back to 8? The drivers will work on 8 right? I formatted my computer back to 8 and now finally the windows recognize back my phone.
Other than that, do you still have the link to the live CD forum??

DreamerTKM said:
Thanks for your fast reply. Seems that even Microsoft is providing free update for windows 8 but a phone that unable to flash by using bootloader is kinda useless for unofficial ROM users like us.
I have something don't understand from your post. You mentioned that install and uninstall the sync manager on Vista but why not back to 8? The drivers will work on 8 right? I formatted my computer back to 8 and now finally the windows recognize back my phone.
Other than that, do you still have the link to the live CD forum??
Click to expand...
Click to collapse
Well, my primary PC is my laptop with 8.1, but I've got desktop as well with dual-booting Vista and 8.1 and it is way faster to do it on vista, than to partition HDD and install Windows 8. Also I'm not dev or some tinkerer, so I don't need to use fastboot that often.
To answer the second question, I closed all tabs regarding the drivers on 8.1 as soon as I did what I needed on Vista, so I'm afraid I don't have the link. I could probably find it somehow using my internet history, but I spent several hours browsing various forums, so it would take me an eternity...

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

op7 pro recognized in adb but not in fastboot

I feel like I have tried absolutely everything but my computer will not recognize my phone when I type fastboot devices, while in fastboot. When the phone is on though, adb devices shows the device.
I'm curious if anyone else has run into this issue and if so, how did you fix it?

triteshy said:
I feel like I have tried absolutely everything but my computer will not recognize my phone when I type fastboot devices, while in fastboot. When the phone is on though, adb devices shows the device.
I'm curious if anyone else has run into this issue and if so, how did you fix it?
Click to expand...
Click to collapse
Hey pal, I'm no expert but I'd say try download adb driver for your OS version whether it's Windows or Linux. and maybe phone driver as well. Worked for me

niteStalker09 said:
Hey pal, I'm no expert but I'd say try download adb driver for your OS version whether it's Windows or Linux. and maybe phone driver as well. Worked for me
Click to expand...
Click to collapse
Thank you for the response. Did both of those things already.

triteshy said:
Thank you for the response. Did both of those things already.
Click to expand...
Click to collapse
Just making sure but you do have the latest platform-tools?
I've never actually experienced it not being detected in fastboot before so that's really the only solution I can think of.

So just for some one in the future trying to figure out what happened. I managed to get it fixed.
The problem I was running into was that my computer recognized the driver (the regular oneplus driver that you can install when you plug in your phone) only when my phone was using adb (or in other words, my phone was on, in a usable state, in the regular OS, not fastboot or anything).
However when I launched into fastboot, my computer would no longer recognize my phone as the same device.
To fix:
I had to open file explorer on my pc (running windows), then right click "my pc", then manage devices.
There was my phone, right there, but under "unknown device". I right clicked it, and installed a driver for it, however I didn't use the oneplus driver, I used the Samsung phone drivers. It then worked perfectly.
I know that's not good directions but it still may help someone in the future and save them from a horrible headache that I experienced, at least pointing them in the right direction.
GLHF.

I had this happen to me as well. Was driving me nuts. I had to use a different cable. The wrong cable solution usually never works, but for some reason, my older USB-C anker cable would work in ADB but not fastboot. Newer Anker cable worked. I'm sure the OEM cable would work too.

help with fastboot.

I previously unlocked my bootloader, installed oxygen 11 (am on beta 4) . I want to install PA but I can't get fastboot on my machine. Shouldnt it be as simple as instilling adb and fastboot as well as the oneplus drivers? I've done everything I can think of and the majority of times ,I ended with an exclamation point in device manager and couldn't get the correct driver installed. I tried SDK etc.. more so... Android composite adb isn't showing in device manager. I might just use my laptop.
Any quick ideas on how to fix though? Thanks

There are lots of guides and links to the minimal adb/fastboot packages here on XDA. I will say it's a heck of a lot easier on Linux or even Mac, but typically the issue is that you want to have your device drivers installed first, then connect your phone (switch it between charging, file transfer, and MTP modes and let it install each of them fully to the device manager while it's plugged in), then install adb, enable debugging, plug in, run "adb devices" and trust the RSA fingerprint, and let it install that side of things to device manager as well.
I'd start by uninstalling all of the instances of the device in your system first to start over. You might even try plugging it in with no drivers installed first to see if it loads working generic drivers.
Man, I do not miss Windows.

I've done all that, and now I tried my laptop and it's the same issue. Adb works fine, mtp works, just fastboot says "waiting for device" so frustrated.
I'd switch to linux if gaming was better... You think most games can run in linux? I am used to use it in the last before I started pc gaming and I really liked how capable it was. Creating bash scripts for simple tasks was great.. Windows really does suck. Getting fastboot working shouldn't be this much of a hassle and it never has been so I don't know what's wrong. I've uninstalled drivers multiple times now and still can't get anything. I'm Wondering if it's this latest release of Windows...

Make sure you have the latest Android Platform Tools installed...
https://developer.android.com/studio/releases/platform-tools

satva49721 said:
I've done all that, and now I tried my laptop and it's the same issue. Adb works fine, mtp works, just fastboot says "waiting for device" so frustrated.
I'd switch to linux if gaming was better... You think most games can run in linux? I am used to use it in the last before I started pc gaming and I really liked how capable it was. Creating bash scripts for simple tasks was great.. Windows really does suck. Getting fastboot working shouldn't be this much of a hassle and it never has been so I don't know what's wrong. I've uninstalled drivers multiple times now and still can't get anything. I'm Wondering if it's this latest release of Windows...
Click to expand...
Click to collapse
Try revoking all adb authorizations and then try to plug it in and run "adb devices" to regenerate an authorization maybe? Is the problem only with fastboot or is adb also broken? You are running fastboot commands in the bootloader instead of adb commands, right?

satva49721 said:
I've done all that, and now I tried my laptop and it's the same issue. Adb works fine, mtp works, just fastboot says "waiting for device" so frustrated.
I'd switch to linux if gaming was better... You think most games can run in linux? I am used to use it in the last before I started pc gaming and I really liked how capable it was. Creating bash scripts for simple tasks was great.. Windows really does suck. Getting fastboot working shouldn't be this much of a hassle and it never has been so I don't know what's wrong. I've uninstalled drivers multiple times now and still can't get anything. I'm Wondering if it's this latest release of Windows...
Click to expand...
Click to collapse
Any luck? I'm having the same issue. Just managed to get my phone unlocked from tmo, and for the life of me can't get windows to recognize my device in fastboot. After an uninstall of the device in device manager, and plugging it back in fastboot. It appears under other devices as simply android with a question mark icon top left, and a yellow triangle bottom right. Manually pointing to either the drivers from 15 sec minimal adb & fastboot google drivers, or selecting all devices>have disk>and pointing too the inf of the driver downloaded straight from google results in the yellow triangle going away, but the question mark still remains, and it's still listed under other>Android. So I suspect for some reason or another the drivers aren't installing properly. Usually (having to have to do this with other devices) has worked in the past. I've had win 10 mess up loads of things most notably my dl speed once. Some bug had it capped at like 24 kb/sec (shudders). Just for comparison what Windows version are you on?
Tried dl ubuntu to boot from usb and try that. Then I ran into issues dl the iso. Couldn't catch a break yesterday I guess. I'll try again after work today, and report back. Don't like the idea of having to boot linux just for fastboot. Might a vm, but I'm not sure that would work considering windows doesn't recognize the device to pass it through, but we shall see. I will say this just about over win10.
Also Idk if it matters, but I had Android studio installed before this as well. Might be time for a fresh install it's been a while.
Sent from my OnePlus8TMO using XDA Labs