Database Users

adb "error: device not found" with Haykuro builds

I tried installing the latest builds of Haykuro into my G1, they install fine however I lose adb I keep getting "error: device not found" when I revert to the latest JesusFreak build it starts working again just fine, any ideas why? Thank you in advance.

Sometimes adb.exe stay open in windows process close it reboot your phone and plug it again all is good.

did this fix it?
If not i updated to the new spl and got the new drivers and now adb works fine.

I am using Windows 7 64bit... I could get ADB working one time, and two mins later not at all.
I found this "tip" in a prior thread and I cannot remember who to credit (sorry).... but this worked for me last night without a problem....
When you reboot... hit F8, and scroll all the way down and disable Digital Driver Signing.
After I booted ADB was working great.

Thank you all
Thank you for all your responses I will try them tonight =]

Do0zman said:
did this fix it?
If not i updated to the new spl and got the new drivers and now adb works fine.
Click to expand...
Click to collapse
quick question can u point me in da right direction for the new adb driver....ive searched cant find it

im still getting the problem ive tryed disable driver signing uninstalling reinstall drivers reboot after reboot process kills. And stil cant mount adb. Vista Ultamite 32 bit with update drivers from haykuro

jmotyka said:
im still getting the problem ive tryed disable driver signing uninstalling reinstall drivers reboot after reboot process kills. And stil cant mount adb. Vista Ultamite 32 bit with update drivers from haykuro
Click to expand...
Click to collapse
I'm trying to get this to work also. I have Vista Ultimate 32 bit, where is this new driver that i've read about?

I7oobie said:
I'm trying to get this to work also. I have Vista Ultimate 32 bit, where is this new driver that i've read about?
Click to expand...
Click to collapse
Its in the driver package, just unzip it to C:\ then plug in your phone, go to device manager and look for Android Device, then install the driver from that folder on C:\
works for me and im on XP Laptop and an Vista Ultimate X64 Machine

Dantehman said:
Its in the driver package, just unzip it to C:\ then plug in your phone, go to device manager and look for Android Device, then install the driver from that folder on C:\
works for me and im on XP Laptop and an Vista Ultimate X64 Machine
Click to expand...
Click to collapse
Thanks for the response. I could've swore I've done that, but maybe I'll try it again.

[Q] Developing Processing on Oppo Find 5 on Windows 8

Hey everybody,
I got my Oppo since 3 days now and I am very satified with it. But this morning I was trying to connect the device via USB to continue developing an app in Processing and the IDE didn't find my device. The IDE is waiting for the device to become available and that's it.
After this, I tried the universal adb drivers, the usb drivers of the SDK and the usb drivers of the pdanet app. Nothing worked for me so far. In the device manager the device is listed as "Android ADB Device", so it should be working, right? I am working on Windows 8 on my laptop right now and I think this is where the evil comes from
Any Processing developers here, which got Processing working with their Oppo??
Greetings
digga_mies

I use windows 8 on my PC, but OPPO is recognized when plugged in. I'm pretty sure my correct drivers were installed when I connected the phone.
sent from my Find 5 using Tapatalk 4 Beta

Coreym said:
I use windows 8 on my PC, but OPPO is recognized when plugged in. I'm pretty sure my correct drivers were installed when I connected the phone.
sent from my Find 5 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Okay, and what drivers did you use? The stock drivers of Win 8? Or do you have downloaded others?
I don't know if it helps, but I have installed the stock firmware X909EN_12.A.09_GLO_009_130514

digga_mies said:
Okay, and what drivers did you use? The stock drivers of Win 8? Or do you have downloaded others?
I don't know if it helps, but I have installed the stock firmware X909EN_12.A.09_GLO_009_130514
Click to expand...
Click to collapse
I remember having some issues trying to get Casual to work as it wasn't seeing my phone. I'm pretty sure I used this reference to get everything working correctly.. Install Drivers for any Android

Okay, tried it again with pdanet and got no success again. Even the platform tools adb.exe doesn't recognize my phone as an adb device. I'm getting a little bit frustrated right now.
By the way, I tested it on Windows 7 and it doesn't work either.
Anyone got another idea?

digga_mies said:
Okay, tried it again with pdanet and got no success again. Even the platform tools adb.exe doesn't recognize my phone as an adb device. I'm getting a little bit frustrated right now.
By the way, I tested it on Windows 7 and it doesn't work either.
Anyone got another idea?
Click to expand...
Click to collapse
Try wireless adb, and connect manually to your phone via command line (something like: adb connect YOURIP). I pretty much use only wireless adb (as I do tend to develop stuff that relies a lot on the 9 DOF sensors...) Cheers.

I got it. My device was shown in the device manager all the time as adb device, but the Processing IDE didn't found it. In the Oppo forums is the same error described with eclipse.
The solution was, to change the adb_usb.ini in "C:\Users\YOURUSER\.android". In my file wasn't any entry and I simply added "0x22D9". That's it! Worked for Windows 7 and 8.
:victory::victory:

digga_mies said:
I got it. My device was shown in the device manager all the time as adb device, but the Processing IDE didn't found it. In the Oppo forums is the same error described with eclipse.
The solution was, to change the adb_usb.ini in "C:\Users\YOURUSER\.android". In my file wasn't any entry and I simply added "0x22D9". That's it! Worked for Windows 7 and 8.
:victory::victory:
Click to expand...
Click to collapse
I dont understand what you mean adb_usb.ini
can you make a guide?

digga_mies said:
I got it. My device was shown in the device manager all the time as adb device, but the Processing IDE didn't found it. In the Oppo forums is the same error described with eclipse.
The solution was, to change the adb_usb.ini in "C:\Users\YOURUSER\.android". In my file wasn't any entry and I simply added "0x22D9". That's it! Worked for Windows 7 and 8.
:victory::victory:
Click to expand...
Click to collapse
Thanks for the device code!

[Q] Can't use ADB After 4.3 Update

Here's a funky issue. I've been using ADB without any problems on 4.2.1 and 4.2.2 on this device (Stock Android and some CM10-based ROMs). When I flashed a CM10.2-based rom (JellyBro, I believe?) a few months ago, I was never able to get ADB to work, so I restored a nandroid of my previous setup. After a while, I decided to flash the stock 4.3 image (today) and see if I still have the problem. I do.
Here are the details in a format that I hope is both entertaining and helpful for troubleshooting
Okay fine, what's the problem now?
- I cannot use ADB with my N4 on 4.3.
- I cannot authorize my device.
Seriously? Simple ADB problems? Shut up and search the forums.
- I did. I tried many things.
Well what did you try, then?
I just tried to use the default feature. The phone should prompt to authorize my computer, but I never get a prompt.
I checked /data/misc/adb/ and the directory was empty.
Even so, I decided to click the "Revoke USB debugging authorizations" option in Developer options.
I copied ~/.android/adbkey.pub from my Linux box and put its contents in a new file named /data/misc/adb/adb_key on my device.
When that didn't work, I rebooted the device.
When that didn't work, I disabled/enabled ADB on the device.
When that didn't work, I killed adb on my computer, then restarted it.
When 3a-3c didn't work, I did them all sequentially before trying again, which also didn't work.
Exactly the same as above, but put it in /data/misc/adb/adb_keys intead of adb_key (because XDA and other sites cite both filenames).
Clicked the "Revoke USB debugging authorizations" button again. Rebooted the phone, killed ADB on my computer. Still no prompts to authorize.
It only removed /data/misc/adb/adb_keys, not adb_key. So I'm pretty sure adb_key is the wrong filename (despite being cited at a frequency on par with the correct name).
Update my platform-tools package. No dice.
Can't actually update; I have the most recent version (18.0.1)
Remove and reinstall platform-tools. No dice.
By the way, my permissions for the adb_keys file are 300. Owner is root. Group is root. Or in other terms:
Code:
#: ls -l adb_keys
-rw------- root root
Are you sure this is only happening to you on 4.3?
Yes. I have no problems after installing any 4.2 rom with recovery, or the 4.2.2 factory image with fastboot.
And it's exactly the same issue with factory 4.3 or a 4.3-based ROM?
Yes. Although I've only tried two or three roms, plus the factory image. There may be a magical rom out there somewhere that does work though.
Any other devices?
I tested adb with my girlfriend's 2012 Nexus 7 running 4.3. It had no issues at all.
Any other computers?
Unfortunately no. I only have my Linux Mint 15 box.
-------
Okay, so that's basically the gist of it. Does anyone else have any clever ideas? (Or does anyone see where I was an idiot and made a mistake?)

Check adb version. You need 1.0.31.

vkn said:
Check adb version. You need 1.0.31.
Click to expand...
Click to collapse
I had the same issue several weeks ago and the update to 1.0.31 fixed it here as well.

pjc123 said:
I had the same issue several weeks ago and the update to 1.0.31 fixed it here as well.
Click to expand...
Click to collapse
I did mention in the post that I already tried that. (EDIT: Well, I mentioned platform-tools, not adb specifically. Points to you.)
Code:
$ adb version
Android Debug Bridge version 1.0.31
Any other suggestions? =(

dotvezz said:
I did mention in the post that I already tried that. (EDIT: Well, I mentioned platform-tools, not adb specifically. Points to you.)
Code:
$ adb version
Android Debug Bridge version 1.0.31
Any other suggestions? =(
Click to expand...
Click to collapse
Oops, I didn't notice that. As I am using Windows when I communicate with the Nexus 4 on 4.3, I can't speak for anything related to Linux, although I do have several Linux computers.

pjc123 said:
Oops, I didn't notice that. As I am using Windows when I communicate with the Nexus 4 on 4.3, I can't speak for anything related to Linux, although I do have several Linux computers.
Click to expand...
Click to collapse
Ah, I gotcha. Thanks for trying though! =). Until I get an working solution, I'm just running 4.2 (Because really, 4.3 isn't THAT big of a deal for me).

i have the exact same problem!
i realy realy need ur help, my phone is dead without it.. i need that adb to work so i can fix this,
please help me im desprete

I had similar issues before w/ my N4 and basically did a full re-install of SDK. Have you tried that yet, might work.

[Q] LG-D802 Driver not found!

I installed TWRP on my LG G2 D802 to install a custom rom, but i format my internall sd card by accident (which had contained the custom rom Zip file) and now i need adb to copy the zip file into my phone (which is not turning on because of sd card format).
but when i try to connect to my phone with adb in order to use adb push or adb sideload, adb is not finding my phone and i figured that it is because of driver problems. I have already installed LG G2 drivers (file name is: LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1.exe) and u can see that in attachment 1.jpg, but in the device manager i get warning icon for LG-D802 and windows tells me that no driver is found for LG-D802 as you can see in the attachment 2.jpg.
Does anyone know why this is happening and how can i fix it?
I really need this guys, Any help is appreciated.

Try installing the adb driver itself.
Also, questions do go in general. There's a Q&A board.

Classic windows bull****
Sent from my LG-D802 using Tapatalk

Hid3rs said:
Try installing the adb driver itself.
Also, questions do go in general. There's a Q&A board.
Click to expand...
Click to collapse
thank u very much, it worked.After installing adb drivers I can see my device in adb devices command. I'm going to check if i can use sideload of adb push or not. Again thank u, it was a great help.

Hid3rs said:
Try installing the adb driver itself.
Also, questions do go in general. There's a Q&A board.
Click to expand...
Click to collapse
It worked exactly as i wanted, i used sideload and now i have a kitkat custom rom on my device. thanks for your help. You saved me lots of time and nerve!

Same problem, troubleshooting didn't work
kamran00f said:
It worked exactly as i wanted, i used sideload and now i have a kitkat custom rom on my device. thanks for your help. You saved me lots of time and nerve!
Click to expand...
Click to collapse
I have the same problem but when I run the adb driver installer it gives me the error "Incompatible with Win 8 x64"
Looking for the solution in other forums, they send me to the same adbdriver installer

@fbinimelis 8
I think you probably tryed to install the 32 bit adb driver.
I am not a big fan of automatic installers/tools if its not neccesary but this is an good tool since it also automatically detect which kind of windows u are using (x86 or x64) and then it will automatically install the right adb drivers for your os version.
http://forum.xda-developers.com/showthread.php?t=2588979
This might help you since it also works fine for me windows 8.1 x64

Samsung T-357T Stuck in boot loop device not found.

im trying to load into adb but it won't find the device, usb not reading. can anyone help?

the_rorshach said:
im trying to load into adb but it won't find the device, usb not reading. can anyone help?
Click to expand...
Click to collapse
You need the Samsung USB drivers installed first and the adb binaries on your PC.

Can you link me somehow to enable ADB? I keep having issues with that even though i have android studio and the SDK installed.

the_rorshach said:
Can you link me somehow to enable ADB? I keep having issues with that even though i have android studio and the SDK installed.
Click to expand...
Click to collapse
You can download the adb binaries as part of the Google platform tools package.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Open a command prompt from within the folder where the adb binaries are.

Gotcha, just got issues on win 7