I have had a very eventful few hours and I'll do my best to explain. Earlier this morning I was rooted, twrp installed and running FreedomOS. I had this bright idea of flashing a file I had downloaded from the OP3T website. It was a firmware file (either the first option, the option before OB5). Everything was running smoothly until I got home and tried using fastboot at which point it just sticks on waiting for device. All normal options are checked (adb files installed, debugging selected, the works), but now I can not use fastboot what so ever. I did at one point sideload an OTA using adb sideload (filename.zip). I have tried just about every adb option I can think of to include: 15 second ADB and minimal adb and fastboot. I even deleted the OP3T drivers from my computer, reinstalled those drivers. I followed an article through technobuzz: http://www.technobuzz.net/download-oneplus-3-usb-drivers/
http://www.technobuzz.net/setup-adb-fastboot-drivers-for-nexus-oneplus-samsung-or-any-android/
I have been using adb and fastboot with no issues up til Open Beta 5 and now my PC and another PC is giving me crap and it's iritating the %%%k out of me.
adb reboot recovery works, adb devices work - showing that the device is connected. I checked the device manager and only found the portable devices. It's like my computer somehow magically deleted the adb driver and will not allow me to install an adb driver. I have no logs to check out....15 second adb was suppose to place a log file on the desktop, but it doesnt....it wont install
Here's what Im on:
OB5 (7.1.1) with stock recovery. I can not use fastboot commands. Here are some pics
http://imgur.com/a/y7iFE
http://imgur.com/a/SVVMg You should see something that says, "Android Device or ADB", but nothing - just MTP
http://imgur.com/a/62msw
I'm using windows 10, device signature is off
Essentially I just want to be able to fastboot flash TWRP and gain root.
Has anyone else experienced any kind of issues with OB5 and adb/fastboot
Btw I had the entire Android SDK installed on another computer and that did not work either....Any assistance would be greatly appreciated. I'm talking about you @redpoint73, lol
Oh boy, I've been summoned! I have to say, I'm not anywhere near knowledgeable yet with the 3T as I was with my past devices. But I'll try.
I assume you are properly trying fastboot commands while in fastboot mode (not in OS or recovery)? I assume so, since you already said it worked fine before the update. But it never hurts to ask the obvious, as a lot of folks forget that adb and fastboot work a bit differently (fastboot only in fastboot mode, adb only in OS or recovery - debugging only needed for adb, not fastboot).
Do you have the OP3T drivers installed? These are the files that Windows always opens whenever I connect the phone (while booted into phone OS), select File Transfer, and it gives the option to open the folder. Although I don't think you even need the drivers for fastboot to work. I unlocked the bootloader and flashed TWRP before I ever installed the OnePlus drivers. The generic fastboot drivers worked fine. But it's worth a try, to install the OP drivers.
I don't even know where to begin or how to reply to what you just said @redpoint73. I haven't attempted to use adb/fastboot commands since yesterday, so i have no idea as to rather it will work or not. If you have teamviewer, I can give your access to a backdoor to show you as it's easier to show then explain. Have you ever noticed when you download a zip from here: http://downloads.oneplus.net/devices/oneplus-3t/#title-section
it never saves the file as Open Beta 3, 4, or etc. It saves the file as this long-named file.zip rather than being something easy to understand. Im able to understand it now, but a few moments ago I wasnt. I "have" downloaded the OP3T drivers on multiple occasions with no success to to fastboot only adb. My computer recognizes the device though. When I go into device manager checking things out. I will have an option that says, "portable devices". when you select that option you'll go across through some contextual menus where you wind up seeing MTP. You should see MTP if you successfully installed the OP3T devices, but at the same time you should be able to see an option that says something along the lines of ADB or Android Debug Bridge, vice versa. My computer does not say that and I have no idea where to go from here. I have no logs or anything helping me out, so it's like finding a needle in the haystack. I do know that I have all of the prereq's such as debugging selected from developers options within the phone, device signature turned off through Windows, adb/fastboot installed, OP3T drivers installed - you know the works you usually need in order to get everything working right. What I might end up doing is just reformatting my entire laptop, installing a fresh copy of windows, fresh copy of adb/fastboot and going from there. My bootloader is unlocked and has been since I've owned the device. As of right now I'm on OB5 with stock recovery. Yesterday I tried three times to sideload one of the downloads from this site: http://downloads.oneplus.net/devices/oneplus-3t/#title-section
. However, my phone would end up saying, "installation failed" when Im in sideload mode. I'm thinking that might have something to do with a botched download from the OP3T server.
Looks like you found your solution here: https://forum.xda-developers.com/showpost.php?p=72046709&postcount=20
Fastboot/adb is usually as simple as reinstalling drivers, etc. as opposed to reformat the PC as you were considering. Reinstalling adb/fastboot was a good idea also, as I don't think I would have thought of that (although it makes perfect sense). So good job working it out!
Related
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.
mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".
nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything
Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.
alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?
http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery
when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right
have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone
tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"
I believe you can also try "./fastboot-mac flash recovery ./recovery.img"
Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!
you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829
fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder
I've searched and searched for a solution to this, nothing is working. Really need help guys.
Phone is on stock ICS rom, PC is Win8 Pro x64. All three files are in the folder, SDK is installed (x64 version), Google USB driver installed, Java for windows installed, and HTC Sync installed but not running.
When in FASTBOOT and USB connected it shows FASTBOOT USB. Device manager shows Android Phone - Android ADB Interface. Is this correct or should it show something else in device manager?
No matter what I've tried when running fastboot oem get_identifier_token in command prompt I get waiting for device. Also running fastboot devices returns nothing.
Don't know what else to try... Seems it doesn't recognize the device but it's in device manager.
Edit: have also tried different usb ports and I know the cable works.
Edite 2: I fixed it. Took me hours to get this working but for any one struggling like I was here is what I did.
Got rid of all the drivers and started back at Android 1.0 in device manager. Manually installed the official SDK google usb driver and selected Android Bootloader Interface for Android 1.0. Also boot the phone and manually install again and select Android ADB Interface.
Here is what really caused me problems. The HTC tutorial I looked at said to take adb.exe, fastboot.exe, and adbWinApi.dll and put them in their own folder. This absolutely does not work for me even now. I used the directory straight from the SDK (sdk\platform-tools) and added fastboot.exe from a previous sdk revision into that folder. Now everything works!!! Finally!
Hi everyone!! I have the same issue as brother bassvoykevlar but the solution here expresed is not all clear to me. Can anyone please give me a hand on this, i am really mad with it . Thanks in advance.
The Best Solution
this problem has also happened with me and i found a solution to this,
this usually happens if your system lacks fastboot drivers.
ADB drivers can only Run ADB shell so that is why you need to have fastboot drivers as well to use fastboot commands.
i think you must have tried this code:
"fastboot oem unlock"
then cmd may have got stuck on "waiting for device"
don't worry install drivers for fastboot then it should work.
google it then get it.
there is 15seconds ADB,fasdtboot installer available try that.
then give it another try.
Ok I've been at this for hours trying to get adb to recognize the tablet in recovery mode and to no avail. I've tried every trick and random driver i can find on here and still am unable to get adb to recognize the tablet while waiting for a sideload .bin file. While in normal mode while up and running adb devices command find sit np but once it goes into recovery it's gone.
I type adb devices and it comes back null. I've tried killing and restarting the daemon server and that isn't it. I've tried uninstalling and reinstalling the drivers. There is even an ADB composite driver listed in the device manager and yet once the tablet is in recovery mode it seems to disappear.
I tried doing a factory reset and wiping the cache. i'm drawing a blank on this. I've also tried changing usb ports and cables on the computer. It's just not working.
Any ideas?
You may need to disable driver signature enforcement
then install drivers.
After that you may still need to follow this guide
http://forum.xda-developers.com/showpost.php?p=62561874&postcount=2
This was written for a different FIRE so yours will be KFFOWI instead of KFARWI in the guide.
I did this and in worked for me..
There are two options to restore stock at the bottom of this link, it all depends what version you have. See if it helps...
http://forum.xda-developers.com/showpost.php?p=62986666&postcount=4
or you could also try this to get into Amazon Custom recovery:
adb reboot recovery
Yeah, most likely a driver issue. Try different drivers until you find one that actually works!
Well I just thought of this when I woke up, could it be that I'm using minimal ADB and fastboot or should that not make a difference?
As long as your device is listed when doing a "adb devices" or "fastboot devices" should make no difference. But yes, minimal should be fine.
But it is usually a good idea to have the latest version.
I think your issue is with getting to Amazon recovery. If in recovery, there should be a menu. See that menu here in post #3:
http://forum.xda-developers.com/amazon-fire/general/amazon-fire-2015-tips-tricks-t3214544
Tuvan03 said:
Ok I've been at this for hours trying to get adb to recognize the tablet in recovery mode and to no avail. I've tried every trick and random driver i can find on here and still am unable to get adb to recognize the tablet while waiting for a sideload .bin file. While in normal mode while up and running adb devices command find sit np but once it goes into recovery it's gone.
Click to expand...
Click to collapse
You're talking 2 different modes here: (1) Recovery mode: You see menu options on tablet. Windows can't ever recognize device while in recovery mode; no driver appears in Win Device Manager. (2) Sideload mode: After you select "apply update from ADB" and press power button and you see yellow text on tablet saying to sideload the file. Fire appears in Device Manager. If no driver installed (or messed up), it's under "Other" with the name KFFOWI as @gray-beard said. That's what you need to install drivers for in order for sideload to work. I doubt Minimal adb is the problem. You're probably just not all the way into sideload mode. If problems persist, open the console window from the folder containing adb.exe.
gray-beard said:
You may need to disable driver signature enforcement
then install drivers.
After that you may still need to follow this guide
http://forum.xda-developers.com/showpost.php?p=62561874&postcount=2
This was written for a different FIRE so yours will be KFFOWI instead of KFARWI in the guide.
I did this and in worked for me..
Click to expand...
Click to collapse
Many Thanks Gray Beard, it's reloading the stock firmware now. I was just trying to go through the pick your device drivers thing too quickly and needed to do the see all devices to be able to see the adb drivers to get them loaded.
A pint of the finest dwarven ale to you (with a name like gray beard i couldn't resist)
EDIT: I did all this just to try to restore OTA updates, yet i hit the update button now that it's restored with the factory firmware and it's saying no updates found. hmm
I just purchased by OnePlus 3T and in the process of trying to unlock the bootloader. I have ADB while in stock oxygen os 4.0.2 but when entering fastboot to unlock the bootloader I no longer have access to the device. As per some searching I switched to a USB 2.0 port and still no luck. In device manager it shows my phone under "Other devices -> Android." I'm pretty sure i'm missing a driver for ADB, but can't figure out what is missing. Any help would be greatly appreciated!
http://www.androidusbdrivers.com/oneplus-3t-usb-drivers
Install, restart.
Specifically in folder you have adb files, hold Shift+Right Click, open command prompt.
fastboot devices to confirm connection
fastboot oem unlock to get started.
Search for the one plus 3t toolkit. It has the original one plus drivers.
Then install minimal adb and fastboot.
And it should work. If it doesn't, try on another pc.
Well it's been a while since my last new phone totally forgot to install USB drivers all good to go, newb mistake thank you!
or plug your phone into the pc and use the emulated cd drive that appears to get the drivers
Jo_Jo_2000 said:
or plug your phone into the pc and use the emulated cd drive that appears to get the drivers
Click to expand...
Click to collapse
After having my phone since Monday, I just now noticed that emulated drive when I had to nuke it earlier today, lol.
Longtime reader, firsttime caller. I've read as much as I can and searched for a solution, but haven't found one yet.
I have a new Pixel 7 and am trying to install LineageOS following the official instructions. I've successfully worked through the initial steps through flashing custom recovery. However, when I start on installing LineageOS from recovery, I run into a problem that after the factory reset I'm unable to sideload LineageOS because adb doesn't recognize the phone. (I can still see it in fastboot, but not with adb.)
I believe that this is a driver problem, because the phone shows up in Device Manager with a triangle.
I initially installed the drivers from here. After I discovered the problem, I also tried the universal drivers from here. Neither of these has seemed to work.
What would you suggest for what I should try next?
laticola said:
Longtime reader, firsttime caller. I've read as much as I can and searched for a solution, but haven't found one yet.
I have a new Pixel 7 and am trying to install LineageOS following the official instructions. I've successfully worked through the initial steps through flashing custom recovery. However, when I start on installing LineageOS from recovery, I run into a problem that after the factory reset I'm unable to sideload LineageOS because adb doesn't recognize the phone. (I can still see it in fastboot, but not with adb.)
I believe that this is a driver problem, because the phone shows up in Device Manager with a triangle.
I initially installed the drivers from here. After I discovered the problem, I also tried the universal drivers from here. Neither of these has seemed to work.
What would you suggest for what I should try next?
Click to expand...
Click to collapse
You should download the official Google drivers.
elong7681 said:
You should download the official Google drivers.
Click to expand...
Click to collapse
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
Which version of platform-tools do you have? You should only be using v33.03. I would also encourage you to use the Pixel Flasher Thread 'PixelFlasher for Google Pixel 7 Support Thread.' https://forum.xda-developers.com/t/pixelflasher-for-google-pixel-7-support-thread.4505289/
laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
I suggest you follow the advice I gave and the other member ended up doing quoted below from another thread (his experience is fairly similar to yours and/or achieving the same things would get to the same end result -- might be worth reading through the whole thing) -- it seemed to work out for him...
simplepinoi177 said:
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Click to expand...
Click to collapse
GodieDan said:
SOLVED! thanks especially to @simplepinoi177 for cracking the case!
In case someone has this same problem in the future, here's the solution:
1. Open device manager and locate the misbehaving driver. If it's not obvious, plug and unplug the USB cable and watch for the appearing and disappearing entry.
2. Right-click the driver > click properties from the drop-down menu > select the driver tab > driver details
3. To be safe, use the snipping tool or something to take a picture of the file directories. Before you change anything in a system file it's always good to keep a record of how things were, but also you'll need to know the directories for the next step.
4. Unplug the device from the computer. As the directory list vanishes, use the screenshot to locate the .dll files.
5. Again to be safe, don't just delete the .dll files; instead just cut and paste into a backup folder somewhere. Also save the screenshot of the directories in the same folder, so you will know where to put them back if you need to. I didn't, and who knows, maybe I could be overcautious, but best practices and whatnot
6. Open device manager and again plug your android in. This time the driver will probably have a different name. Locate it as you did in step 1.
7. Right-click and select "uninstall device." Tick the box and say OK
8. Unplug the phone and reboot the phone and the computer both
9. Plug it back in
I have also determined the cause of my problem: Drive Booster, a program designed to automatically update drivers. It's not an unsafe program, but it is bad at installing the correct driver. I uninstalled it.
Thanks again!
Click to expand...
Click to collapse
laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
Why do you think fastboot and recovery are the same? I haven't been in recovery for a bit but fastboot is available once connected to the computer but is recovery mode supposed to as well? Don't make me go into recovery mode please. But I thought recovery mode was device only.
I'm using platform tools v34.0.1, and I worked through the steps simplepinoi177 suggested for the drivers. I then discovered that my problem was something very basic: I was mistakenly using files for a Pixel 7 Pro instead of a Pixel 7 (my actual device). Once I flashed the correct boot, dbto, and recovery for my device, I was fine.
Apologies for the error, and thanks so much for the help. You all rock! And I will read up on Pixel Flasher.