I already use adb and fastboot (Xperia and OnePlus) but with the ZUK it will not connect. Can't find device and I have no idea whats the problem :/
I hope someone can help me (Ubuntu 15.10), because I will flash CM on my Z1.
I had to use windows - could not get my linux laptop to see the Z1 at all. Had more luck using my wife's windows 8.1 laptop. I think (in my simple view) is there's some extra drivers needed which isn't present in linux as my nexus 7 and moto G worked exactly as expected in linux adb command line. This is how far I got and will continue with the replies tonight http://forum.xda-developers.com/zuk-z1/help/z1-adb-devices-t3249461
I want to put cyanogen mod on the Z1 too
Also Nexus 6 no problems, just the ZUK will not work :/
Did you guys try "adb kill-server", " adb start-server" on Linux terminal?
Yes - pretty sure its a driver thing as I can get better results in windows after installing AdbDriverInstaller.exe
Sent from my Z1 using Tapatalk
Related
I dont want to install linux for this one purpose of fixing my lcd density so i downloaded a live cd of ubuntu. Is there a way to use adb on here i tried one way and i had to extract files to the usr/bin which it wouldnt do ( i think because that exists on the disc so its not able to write) any help? maybe another way for adb on linux so i can fix that build.prop?!
you could run it in terminal:
in the adb's folder, run:
Code:
./adb [your command]
hey
i got the adb running the way u said to with adb in the folder. it still dose not show my device and my phone is in debug mode also. on linux it doesn't even show my sd card.
i put in abd devices and no device is shown. any help did i miss a step here.
I kinda have the same problem, I'm new to linux, and just finished installing Ubuntu on my laptop. The first thing I was thinking whether i needed a driver to install the phone like in Windows, or is there some "device manager" like plugin to find out more details on what devices need drivers or whats installed.
on my kaiser, adb doesn't work always. reboot your android if not.
You could see it with command:
Code:
lsusb
and/or
Code:
adb devices
hey thanks dark side just got a hero and couldn't be happier except for battery life my old vogue lasted longer lol (probably all the hero HTC stuff). But thanks for actually giving advice about the adb! no one else seemed to it drove me to get a hero! The sense ui is really great i didn't think i would like it because of how it felt on vogue. but actually its a really good thing. That sense ui from jamezelle is insane. its almost like it but after u leave an app it dose not loads again. if he some how gets that fixed it will be close to the hero. anyway everyone thanks for letting me experience android (dzo plemen, jamezelle and zen i tired your builds so this is to you). You helped with my decision to get a hero. Best phone i have ever owned! also to help anyone i think that if u plug your phone into windows 7 and then windows xp it can mess up your adb with the vogue that what happened to me... it let me see the files in windows 7 but after i hooked up to xp both became unable to use!
Ok,
So Ive been scouring the net to find out if there is anyway I can get my device to be recognized. So far I've tried:
Windows 7 Ultimate 64bit, phone goes into storage mode and loads the drivers. although the drivers are not signed so windows refuses to load them, nice microsoft.
Ubuntu 10.04 64bit, ok i've installed usb_modeswitch and setup a bunch of udev rules (attached) and I can get the device to be detected but not recognized ie if I execute
Code:
adb devices
I get
Code:
List of devices attached
???????????? device
if I try
Code:
adb shell
I get dropped right into the user shell on the device. *Nice* score one for linux, but this doesn't do me much good because if I try to bring up the dalvik monitor it refuses to recognize the device grrr bad linux
I've attached my udev rules and a listing from when I tried to start the dalvik monitor, if anybody has some idea how I can get either windows to load the provided drivers or ubuntu to recognize the device I would be eternally greatfull
Thanks
Tired and wear from trudging around the net all day
Ben
Hello,
i wanted to flash the slimbean rom on my nexus 7 3g but was stupid enough to format the whole storage, so that nothing is left on it.
i tried to connect the device to my pc by mounting it, but it seems not to work, because nothing happens.
well, i found out that i can install the rom from sideload. and after googling it, i managed to find out that i have to install the nexus 7 adb drivers through android sdk, which i did.
to test it, i opened the cmd and typed in "dir", but there was no android-sdk listed. what did i do wrong?
my cmd does not understand the command "adb sideload", although the adb drivers are listed in the device manager...
please help me, i need my nexus 7 tomorrow...
thanks in advance!!
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!
I happen to update platform-tools in the Android SDK from version 23.1 to version 24 on an older PC.
The newest adb.exe included with v24 no longer works on WinXP.
You will get the following error upon startup:
adb.exe - Entry Point Not Found
The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll.
Click to expand...
Click to collapse
In case anyone is curious, I tracked the change down to this one:
https://android-review.googlesource.com/#/c/203387/
ADB
I've attached the v23.1 adb and fastboot to this post in case someone needs the previous version (which works fine with 5x up to at least MTC20F)
Just unzip and you can use adb/fastboot from the resulting platform-tools-v23.1 directory or copy them over to where your normal platform-tools directory is.
USB drivers for 5x
I also included USB drivers that work with 5x. These should work for 32/64-bit for winxp and vista. Win7 is maybe, haven't tested.
They WILL NOT work with win8 and above due to changes in driver enforcement. I am not sure about win8.x but on win10, there is a built-in driver that works with adb. To get bootloader/fastboot driver, just allow win10 to search for drivers. It will load Marshall London Bootloader Interface. This is for a different phone from music company Marshall, but it works fine since it is an Android-based device.
I could never find one official driver from google or lg that would work with adb inside android, adb inside twrp, adb sideload inside stock recovery, and fastboot.
I stopped worrying about why it works for other people and just fixed the problem myself.
Not sure if it matters to that many people these days, but it was confirmed the change in adb is not a bug and will persist going forward, so if you ever need to run adb on a WinXP box or emulator, you'll need to retrieve platform-tools-23.1 or earlier.
WinXP compatible platform-tools also could be downloaded from official repository:
http://dl-ssl.google.com/android/repository/platform-tools_r23.1.0-windows.zip
Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.
Greefus said:
Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.
Click to expand...
Click to collapse
Actually Windows 7 is still installed on nearly half of all desktop and laptop computers: https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0. Did the most recent SDK drop support for it?
For anyone who wants to use adb on the latest version of Android Studio running on Windows XP use the adb .exe from version 23 and paste it into the platform tool folder. Keep a copy of the new adb.exe just in case you need it. No need to use the entire v23 platform tool folder.
The references in this thread have so far appear to refer to latest adb compatibility, particularly for Windows XP.
Does the latest fastboot still work fine with Windows XP? If not, what was the last known-good or thought to be last known-good version for Windows XP?
Hi
The adb from the v2.3.1 works fine with my win xp, thank you for the file.
Hello,
I am another WinXP user facing the error
"adb.exe - Entry Point Not Found. The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll."
@sfhub & @Sintetix
Thanks for the info and provide the latest version supported by XP ...
Are you aware of any important changes / additions in the future versions to be concerned of?
Regards
---------- Post added at 11:16 ---------- Previous post was at 10:47 ----------
Just to let you know,
C:\v23.1>adb devices
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037:
I am trying to connect an Asus Transformer tablet with "MTP file transfer" mode on WinXP Service Pack 3 laptop... cable is fine and the plan is to move from custom ROM (Android 6.0) to Stock (JellyBean) ... Something I already did few years ago having Win10 (I have the receipe used then)
I think I better get a fresh Win7 on my primary Win10 PC and start from there... I never liked W10 anyway ... and since I did mods to [finally &effectively] stop the [annoying, unwanted & plenty of bugs] Win10 updates ... I got funny errors when using dev stuff ... even DotNet ...
And I need to think a better O.S for the XP PC ...
Time to change. Regards
Before jumping to my major O.S actions,
I gave a chance to my Asus Transformer tablet with another cable under the W10 PC and the latest adb (r29.0.2-win) and this second time it worked fine ...
The first time and first cable did not work (reason that drove me to the WinXP PC thinking the cause was Win10)
fastboot devices
was literally returning
???????????? fastboot
But this second time with another cable
fastboot devices
returned
BLAxxIDxxSTRING fastboot
And I was finally able to perform the format and flash series of commands to return my tablet to the stock ROM ...
As I understand this thread is about WinXP, for testing purposes, I hooked my fresh flashed tablet to the WinXP PC with the successful spare cable, and
adb devices
got again
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037
Certainly I don't have the explanation of this, but I can tell you is not because a faulty cable or something related to the tablet.
And something scary to add: the first cable looks in good shape and is the one used every day to charge the tablet without any delays or issues ...
Hope someone find this useful and provide more insight. Regards