Database Develop

ADB Driver installation issues Windows 7

Hello,
I wanted to root my new Sony Xperia T and I found this http://forum.xda-developers.com/showthread.php?t=1886460.
However I needed to install the ADB drivers and I am having extreme difficulties in doing so. From my limited knowledge on the subject I guessed that the ADB drivers are installed when I plug my phone into my computer. When I plugged my phone in windows installed two drivers. When I then went into device manager to see if my phone was registered as an android device but it wasn't. It was instead listed as a portable device. I also tried running
Code:
adb devices
but this ended up with an empty list. Despite this my phone appears in My Computer and I can transfer files to and from it easily.
After looking on the internet for a while I found I needed a few things installed. So I removed the drivers, installed the Android SDK with SDK-tools and the Sony PC companion as well as turn my phone to USB debugging. I then retried windows installed the same two drivers and it again was listed as a portable device.
I looked up this issue and found suggestions to restart the SDK-tools ADB server, restart my phone, update drivers, unlock my phone and install PDaNet. These all ended with the same result. I also found a suggestion to update the drivers by going into the Android SDK and using the driver in there. This didn't work though as Windows said the current version of the driver is the most up to date. I tried various techniques suggested to get around this but I was unable to.
Any help on how to install these drivers is greatly appreciated. My phone is about a month old, unrooted, Sony Xperia T (LT30p). My computer runs Windows 7 Professional 64bit.
Thanks,
JamesStewy
(I may have forgotten some of the things I tried to get it to work yesterday so please suggest anything )

Download flashtool and install the drivers from the driver folder in there. They are the only drivers I ever install.
Use the Tx, flashmode and fastboot drivers
Sent from my star trek communicator
Sony Flagship device circa 2145

It was kind of nightmarish to get the phone recognized for me as well. I managed to solve it (after may trials and errors) by manually "updating" the phone drivers once it was connected with the ones in the pccompanion folder; specifically the ones called sa0105...

Hello gregbradley and Arcano. Thanks a lot for your replies.
manually "updating" the phone drivers once it was connected with the ones in the pccompanion folder; specifically the ones called sa0105
Click to expand...
Click to collapse
I found the drivers in the PC Companion folder except I was unable to install them either by right clicking on the inf and clicking install or by going into device manager right clicking on my phone -> Update Driver Software... -> Browse my computer for driver software -> Enter in PC Companion drivers folder -> Next -> Windows Message (attached file). Is there another way of installing the driver? I also previously tried getting windows to not install the drivers when I plugged my phone in but nothing I could find on the internet worked.
Download flashtool and install the drivers from the driver folder in there.
Click to expand...
Click to collapse
Sorry for being a bit of a n00b but what is a flashtool and where do I get it? Also, same as previous, I can't find anyway of overriding drivers (I have gone through about three pages of google but can't find a solution that works for me).
Thanks again for your replies,
JamesStewy

JamesStewy said:
Sorry for being a bit of a n00b but what is a flashtool and where do I get it?
Thanks again for your replies,
JamesStewy
Click to expand...
Click to collapse
Flashtool is THE tool for use with xperia devices. Look in the first thread of the development section.
It should be the first thing you download when you get an xperia device.
EDIT
No need to post your thanks. If you feel the need to express gratitude to anyone on xda just their thanks button

JamesStewy said:
I found the drivers in the PC Companion folder except I was unable to install them either by right clicking on the inf and clicking install or by going into device manager right clicking on my phone -> Update Driver Software... -> Browse my computer for driver software -> Enter in PC Companion drivers folder -> Next -> Windows Message (attached file). Is there another way of installing the driver? I also previously tried getting windows to not install the drivers when I plugged my phone in but nothing I could find on the internet worked.
Click to expand...
Click to collapse
The way I did it was to plug the phone in, wait till the automatic driver installation failed, and then in the device manager I selected the phone and went thru the "update drivers" procedure. You must select the specific folder where that driver is, not the parent, or windows won't detect it. In my case that folder is named
C:\Program Files (x86)\Sony\Sony PC Companion\Drivers\{2CD1390C-A74E-434A-B652-73D3683B3BEF}
which is quite a weird name; just look for the folder with sa0105* drivers inside, and that's the one.
By the way, I never had a "WPD composite device". This is how it is shown now in device manager:

The way I did it was to plug the phone in, wait till the automatic driver installation failed
Click to expand...
Click to collapse
I saw this method on the internet but the weird thing is is that the drivers install correctly, first time, every time. See attached pictures.
Flashtool is THE tool for use with xperia devices. Look in the first thread of the development section. It should be the first thing you download when you get an xperia device.
Click to expand...
Click to collapse
I got the tool, found the drivers folder but was unable to install the drivers.
JamesStewy

JamesStewy said:
I saw this method on the internet but the weird thing is is that the drivers install correctly, first time, every time. See attached pictures.
I got the tool, found the drivers folder but was unable to install the drivers.
JamesStewy
Click to expand...
Click to collapse
¿Could it be that you have two phones detected?, as my pc only shows "Xperia T", no trace of "LT30p"; and the adb driver is in a category of its own.

I have no idea. I only have one thing connected to my computer which is my phone. I don't have an adb, Sony or android node in device manager at all.
JamesStewy

I don't know what else to tell you then. You might try uninstalling the LT30p, and forcing the upgrade to the pccompanion drivers I talked about before. But this is a wild guess, I can't really help you any further.

It's your adb installation correct. Have your added it to the path in environment.
Do you have usb debugging on in settings on your phone.
What was the error when you installed the flash tool drivers
What dies flash tool say when you attach the phone whilst it is open.
As the post above says, you could uninstall all phone/Sony/adb software and drivers and re install them.
I have never heard of this issue and just installing flash tool and/or pccompanion is enough to install all the drivers
Sent from my star trek communicator
Sony Flagship device circa 2145

It's your adb installation correct. Have your added it to the path in environment.
Click to expand...
Click to collapse
I am not sure. Is the adb installation part of the Android SDK platform-tools? If so I think it is. I can use all the commands such as adb devices but this returns and empty list. And yes it is in my PATH environment variable.
Do you have usb debugging on in settings on your phone.
Click to expand...
Click to collapse
Yes.
What was the error when you installed the flash tool drivers
Click to expand...
Click to collapse
When you say install, what do you mean? If you mean the process I described in a previous post then I get the message attached (untitled2.png).
going into device manager right clicking on my phone -> Update Driver Software... -> Browse my computer for driver software -> Enter in PC Companion drivers folder (or any other folder with appropriate drivers) -> Next -> Windows Message (attached file).
Click to expand...
Click to collapse
What dies flash tool say when you attach the phone whilst it is open.
Click to expand...
Click to collapse
Is the flash tool called EMMA or something? I downloaded it of Sony's site here: developer.sonymobile.com/services/flash-tool/. If so I can't get in because I am still waiting for a confirmation email.
As the post above says, you could uninstall all phone/Sony/adb software and drivers and re install them.
Click to expand...
Click to collapse
When I uninstall them and plug my phone back in the drivers on the phone install to my computer. Pictures attached. These drivers have nothing to do with ADB and only allow Windows to transfer files to my phone.
JamesStewy

No, flashtool I'd found in the first post in the development section.
Please download it, install it, and ruin the driver.exe found in the driver folder of flashtool in the installation path.
Install the Tx, flash mode and fast boot drivers
Sent from my star trek communicator
Sony Flagship device circa 2145

That's where I looked. Can you post a link.
JamesStewy

you sure you looked properly
http://forum.xda-developers.com/forumdisplay.php?f=1801
the very first thread. The link is in the very first post
EDIT
If you google "flashtool" and click I feel lucky it takes you straight to the flashtool homepage...

Xperia T - adb problems
I also tried all sort of things until this:
- you must put your phone in Mass Storage mode, as default is MTP mode.
As simple as that.
On your phone (unpluged) - Settings / Xperia / USB Connectivity / USB Connection Mode - and select MASS Storage, not MTP. I did uncheck Install PC Companion. Plug USB back, put your phone in debugging mode - It work right away. No need to Update drivers, no need to change the android_winusb.inf. You may need to kill adb.exe before trying again adb devices.
That was it for me

Hi laplada27,
Thanks for your reply. When I get home today I will give that a go.
Thanks,
James

Solution
laplada27 said:
I also tried all sort of things until this:
- you must put your phone in Mass Storage mode, as default is MTP mode.
As simple as that.
On your phone (unpluged) - Settings / Xperia / USB Connectivity / USB Connection Mode - and select MASS Storage, not MTP. I did uncheck Install PC Companion. Plug USB back, put your phone in debugging mode - It work right away. No need to Update drivers, no need to change the android_winusb.inf. You may need to kill adb.exe before trying again adb devices.
That was it for me
Click to expand...
Click to collapse
YES! It worked
Thank you so much.
James

Installing drivers 8.1
I am trying currently to update my T, it has an unlocked bl that I did when I first got it in Dec 12.
I am running w8.1 64 bit.
Tried both mass storage mode & mtp mode.
I have the latest 64 bit version of flashtool installed.
I am trying to flash the 295 generic ce ftf android 4.3 update, no problems with the ftf itself.
The error flashtool spits out is that the drivers are not installed, either the adb or flashmode drivers.
I have repeatedly tried to install the drivers that come with flashtool, and it appears that they install, but
there are a few that won't, I think namely the above.
I note that when I have device manager open, it detects the T, when plugged in in flashmode (i.e. turned off, with volume down)
as an s1boot device. I have intercepted device manager several times when it does this, in order to try and update the drivers
by hand, but no luck.
When I first plugged the T in in flashmode mode, it installed some drivers automatically, however, not ones that will allow flashtool
to work.
In truth I am now scratching my head as to what to do next.
I never had any problems with w7 64 ultimate flashing the T, solid as a rock, all the drivers would install as required, and I am
thinking the easiest way to update my T would be to use a w7 based machine, however, if anyone has any more ideas as to
what might help me flash it using 8.1 then I would be very grateful to hear them.
TheGSL

I think there is a patch for Windows 8.1... Search the forum and you will find it.
Good luck!

ADB problem and no OS on device

Last night, on TWRP I formated data on the SD card, which is why I have no OS. Now looking for how to fix this on xda/google, I get into the bootloader, have fastboot usb and try to adb shell but I keep getting the "error no device found". I already installed latest drivers from HTC on to my laptop and still nothing. Any other idea?

windows 8?

First off, make sure you have HTC Sync Manager installed because that will give you the proper drivers in order to be able to use ADB commands.
Afterwards, make sure you install Java JDK and Android SDK.
Just follow this tutorial here: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Follow it word for word and make sure you install JDK X86 even if you have a X64 computer. And then download SDK Manager, put it in C:/ drive, open SDK Manager, and download the necessary tools (also all in the tutorial).
I was in the same position as you just before yesterday and I followed this tutorial with success.

skinsfanbdh said:
windows 8?
Click to expand...
Click to collapse
Windows 7, and mac.

Evolancer13 said:
Windows 7, and mac.
Click to expand...
Click to collapse
try downloading all in one toolkit and try that. just make sure to read the onscreen instructions as you go through the process

TarekElsakka said:
First off, make sure you have HTC Sync Manager installed because that will give you the proper drivers in order to be able to use ADB commands.
Afterwards, make sure you install Java JDK and Android SDK.
Just follow this tutorial here: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Follow it word for word and make sure you install JDK X86 even if you have a X64 computer. And then download SDK Manager, put it in C:/ drive, open SDK Manager, and download the necessary tools (also all in the tutorial).
I was in the same position as you just before yesterday and I followed this tutorial with success.
Click to expand...
Click to collapse
skinsfanbdh said:
try downloading all in one toolkit and try that. just make sure to read the onscreen instructions as you go through the process
Click to expand...
Click to collapse
I'll look into both things, thanks.
EDIT: even on my mac adb does not see any devices, before when I entered ./adb devices it would show "list of devices:" and it would be blank.

Good luck, man. It's fairly easy once you read the tutorial carefully and follow all the steps to the word. After it's all done and the command prompt says Sideload 100%, boot into TWRP, tap INSTALL and then scroll down to sideload.zip and that's your ROM. Also after copying the desired ROM to platform-tools in the SDK folder, rename it to rom.zip, it seems to work 100% that way while it struggles a bit with long names.

TarekElsakka said:
Good luck, man. It's fairly easy once you read the tutorial carefully and follow all the steps to the word. After it's all done and the command prompt says Sideload 100%, boot into TWRP, tap INSTALL and then scroll down to sideload.zip and that's your ROM. Also after copying the desired ROM to platform-tools in the SDK folder, rename it to rom.zip, it seems to work 100% that way while it struggles a bit with long names.
Click to expand...
Click to collapse
Still getting the error: device not found.
I even ran the all in one tool kit and attempted the "ADB sideload a ROM" follow the steps but get an error on CMD "C:\users\(username) is not recognized as an internal or external command, operable program or batch file"
I really do not understand why adb is not working, I did s-off and supercid myself maybe less than a week ago.

Are you sure you followed all the steps in the tutorial including installing JDK, using SDK Manager to download some tools and such? And are you sure you have the proper drivers installed (e.g HTC Sync Manager)? I used to get that error before I installed it. Go to Device Manager while in ADB mode in TWRP and see if the device is recognized or if there's a yellow sign beside it indicating that there are no drivers for it.

TarekElsakka said:
Are you sure you followed all the steps in the tutorial including installing JDK, using SDK Manager to download some tools and such? And are you sure you have the proper drivers installed (e.g HTC Sync Manager)? I used to get that error before I installed it. Go to Device Manager while in ADB mode in TWRP and see if the device is recognized or if there's a yellow sign beside it indicating that there are no drivers for it.
Click to expand...
Click to collapse
It came up under Android USB Devices as My HTC. When I was following the steps on the link you provided, when I tried to update the drivers with the google usb driver wouldnt work, it would say "windows had determined the driver software for your device is up to date". When I go into My HTC properties says the driver version is 2.0.7.18.

The Google USB drivers did not work for me either, only the ones provided by HTC Sync Manager did. I have not experienced that problem, mate, so I do not know what to do at this point, I am very sorry. If you are not able to fix this, I suggest getting an OTG cable and directly loading the ROM from the PC to your SD card. I ordered one a couple of days ago and it is coming tomorrow, it's very helpful

TarekElsakka said:
The Google USB drivers did not work for me either, only the ones provided by HTC Sync Manager did. I have not experienced that problem, mate, so I do not know what to do at this point, I am very sorry. If you are not able to fix this, I suggest getting an OTG cable and directly loading the ROM from the PC to your SD card. I ordered one a couple of days ago and it is coming tomorrow, it's very helpful
Click to expand...
Click to collapse
Crap, I appreciate your help though.
EDIT: nevermind googled it, gonna pick one up. Phoneless till wednesday

I am sorry to hear that, but I suppose that's the only thing you can do at the moment. Even if somehow get ADB working, do not cancel your order because OTG cables aren't only used for mounting the device, but also for things like connecting gamepads and controllers to play games on your device.

USB 3
If you have USB3 port adb.exe wan't recognize your device.
I triend first on USB3 and after on other older computer on USB2 all was fine

Evolancer13 said:
Last night, on TWRP I formated data on the SD card, which is why I have no OS. Now looking for how to fix this on xda/google, I get into the bootloader, have fastboot usb and try to adb shell but I keep getting the "error no device found". I already installed latest drivers from HTC on to my laptop and still nothing. Any other idea?
Click to expand...
Click to collapse
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip

tash2013 said:
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip
Click to expand...
Click to collapse
check first with "adb devices" to see does your PC recognize your HTC

tash2013 said:
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip
Click to expand...
Click to collapse
Tash2013 YOU ARE AMAZING! Got my One back up running!

Oh man I'm so glad it's working. I thought you already knew that it is sideload not shell lol.
Sent from my HTC One using Tapatalk 4 Beta

TarekElsakka said:
Oh man I'm so glad it's working. I thought you already knew that it is sideload not shell lol.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
If I knew I would have tried lol, and it no one said anything about sideload but oh well.

Haha! Damn. I am glad it worked out, though.

Getting "device offline" with adb after 4.4 OTA

This is just weird. I went back to stock to get the 4.4 OTA. Done, now I want to reinstall TWRP and I'm getting the device offline error. Debugging is on, drivers are installed . . . what stupid mistake have I made?
OK - oddly, I reinstalled the sdk and it works. Who knows?

robsw said:
This is just weird. I went back to stock to get the 4.4 OTA. Done, now I want to reinstall TWRP and I'm getting the device offline error. Debugging is on, drivers are installed . . . what stupid mistake have I made?
OK - oddly, I reinstalled the sdk and it works. Who knows?
Click to expand...
Click to collapse
I'm having the same issue, but reinstalling the sdk didnt help.... im lost, i really want this root

robsw said:
This is just weird. I went back to stock to get the 4.4 OTA. Done, now I want to reinstall TWRP and I'm getting the device offline error. Debugging is on, drivers are installed . . . what stupid mistake have I made?
OK - oddly, I reinstalled the sdk and it works. Who knows?
Click to expand...
Click to collapse
nickfromfresno said:
I'm having the same issue, but reinstalling the sdk didnt help.... im lost, i really want this root
Click to expand...
Click to collapse
try turning off/on usb debuggin.. also try revoking the usb debug auths.. check your adb version to be 1.3x..those should fix it

kreegaa said:
try turning off/on usb debuggin.. also try revoking the usb debug auths.. check your adb version to be 1.3x..those should fix it
Click to expand...
Click to collapse
I have this same issue. Device shows up in "adb devices" but, shows to be "offline."
I'm running Windows8, adb version 1.0.29, with an MotoX (ATT). I cd to "platform-tools" to run adb.
---------------------------
Ok, I solved it by locating the 1.0.31 adb files here: http://forum.xda-developers.com/attachment.php?attachmentid=1724500&d=1360704125
I unzipped and replaced the adb files in the "platform-tools" folder with the ones from the above link. My issue was that the older adb files weren't causing the MotoX to prompt me to verify access from my computer. Updated adb files caused the prompt. Once, I verified my computer access - all is good!

shaneaus said:
I have this same issue. Device shows up in "adb devices" but, shows to be "offline."
I'm running Windows8, adb version 1.0.29, with an MotoX (ATT). I cd to "platform-tools" to run adb.
Any suggestions?
Click to expand...
Click to collapse
You need adb version 1.0.32 or above. I had the same problem.

m0biusace said:
You need adb version 1.0.32 or above. I had the same problem.
Click to expand...
Click to collapse
in linux this can be a sign that you need to run ADB as SUDO.

nickfromfresno said:
I'm having the same issue, but reinstalling the sdk didnt help.... im lost, i really want this root
Click to expand...
Click to collapse
There are a couple other things to try.
One, just get the latest ADB platform tools and see if your device shows up online using that adb.
The other thing would be to delete the adb keys on your phone. Remove /data/misc/adb/adb_keys.

How to Solve 'Unauthorize Device' in ADB

Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot

Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app

speedyjay said:
Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
What does the Android SDK do mate?
I never used it before, so would be great if u can give me some hints
Thanks

toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.

android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).

I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

tdamocles said:
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.
Click to expand...
Click to collapse
Le_Zouave said:
android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).
Click to expand...
Click to collapse
Hello sir, i've been trying all of this method, include the wipe the phone (except using another computer) but still no prompt re-appear. Another advice would be greatly appreciated.
Thanks

joho5 said:
I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho

toughkid said:
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho
Click to expand...
Click to collapse
Have you checked all of your USB ports? I know in the past (with other phones), problems arise if you're not using a direct USB port (one soldered into your MoBo).

toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Go to Control Panel > Hardware and Sound > Device Manager > expand Universal Serial Bus controllers. Now connect your phone. You'll now see USB Mass Storage Device. Right click on it. Select Properties, then go to Details. In the Details section, under Property, select Hardware ids. You'll then see the device id. It will be shown something like this: USB\VID_2A70&PID_9011&MI_01. From this you have to take the 2A70 code ~ the code between the first _ and &. Now go to desktop and create a new text document and copy paste this using your device id as shown:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2A70
Now open the Save As menu. In Save As type select All Files. Save the file as adb_usb.ini
Copy this .ini file from desktop and paste it in C:\Users\YourPCName\.android
Disconnect your phone, reboot your pc. Now with USB Debugging turned on, connect your phone to your pc, you'll surely get the permission thingy popup in your phone.

For completion:
If you DO NOT have access to your phone for any reason but still want to use ADB you can simply boot your phone into TWRP and follow these steps.
Windows:
1. Open %userprofile%\.android
2. Copy "adbkey.pub" to your phone (adb push %userprofile%\.android\adbkey.pub /sdcard/adb_keys)
3. Switch to your phone.
4. Go to Advanced > Open Terminal
5. Type in "stop adbd"
6. Move "adb_keys" from /sdcard to /data/misc/adb (mv /sdcard/adb_keys /data/misc/adb/adb_keys)
7. Type in "start adbd"
8. Switch to computer
9. Type "adb shell setprop persist.service.adb.enable 1"
10. Type "adb shell setprop persist.sys.usb.config mtp,adb"
11. Reboot your phone - DONE
Linux / Maybe Mac:
Same steps, but use "~/" instead of "%userprofile%"
Please note:
You may have to repeat the steps 1-7 after boot when still not having permissions so it makes sense to use cp (copy) instead of mv (move) and only repeat steps 5-7.
Edit: Please also check if your drivers are all installed and enabled.
Sent from my OnePlus 2 using XDA Labs

?k

Unable to get OP3T recognized in ADB/FASTBOOT( tried everything )..help!!

Hey guys, a fellow flasher here. I've tried everything ( really everyhting i know ) but still i cant get my op3t to get recognized in adb or in fastboot.
It's just shows nothing under the list of adb device. Also in drivers section i cant make that exclamation go which means that drivers arent installed properly, but i've tried every driver and toolkit but none of them are of any help as when i go to update driver and select the option to browse to update the driver i cant find the google one. And when i connect my phone with debugging on it shows( in the right bottom corner ) drivers for adb installing but after about 5 seconds it shows failed-no driver found.
P.S-windows 7 is being used and driver enforcing is off also ive used the same pc to flash and unlock my oneplus one many times.
Help!!!

Try another USB port, another driver source, open console as admin, restart your PC after installing driver etc... there are many options... Did you try the command "fastboot devices"?

redukt said:
Try another USB port, another driver source, open console as admin, restart your PC after installing driver etc... there are many options... Did you try the command "fastboot devices"?
Click to expand...
Click to collapse
Thank you but I've tried all this but no luck.
But I've got it working now.
Things I did-
Download android SDK manager, run it as admin, while connected to internet download the Google drivers under extras section, connected op3t with debugging on, go to drivers section, update that driver manually by selecting the google folder in the android SDK folder under extras and now it's good to go!..
BTW do you suggest that should I unlock bootloader and flash twrp the traditional way or use that unified toolkit?