The first, I'm beginner coding android for android studio or eclipse but my device has not adb (or eclipse and android studio didn't see) although I install driver from pc companion, use cmd [adb devices] is show unauthorized including i try install adb.bat that show killing-server, daemon successfull and gone
Help me pleashttp://dl.xda-developers.com/attachdl/cb9471a26af0816560a1f998f0fffeb1/53345aac/2/6/5/3/6/7/6/device_manager.png
http://dl.xda-developers.com/attachdl/292092d7ea82c6eef2cac9b35d14e4fd/53345ac1/2/6/5/3/6/7/7/10151209_10201661776966300_1517802886_n.jpg
Monkun said:
The first, I'm beginner coding android for android studio or eclipse but my device has not adb (or eclipse and android studio didn't see) although I install driver from pc companion, use cmd [adb devices] is show unauthorized including i try install adb.bat that show killing-server, daemon successfull and gone
Help me pleashttp://dl.xda-developers.com/attachdl/cb9471a26af0816560a1f998f0fffeb1/53345aac/2/6/5/3/6/7/6/device_manager.png
http://dl.xda-developers.com/attachdl/292092d7ea82c6eef2cac9b35d14e4fd/53345ac1/2/6/5/3/6/7/7/10151209_10201661776966300_1517802886_n.jpg
Click to expand...
Click to collapse
Is USB debugging turned on in developer options?
I assume you have the Android SDK installed, along with ADB and the path has been set for ADB?
Edit - I see you have from your screenshots. Ignore this. Sorry.
Sent from my C6603 using Tapatalk
I found a problem that a happen the rom on eXistenZ and now I re-install this rom(fresh install)
Related
Totally new to android, anyone mind explaining?
the command is "adb install <path/name of apk>".
do it from your computer in a shell/terminal.
Do I have to mess with the NDK at al? I thought I saw something on that...
Bump, more info please?
NDK? Did you mean SDK (android for windows developer kit), If so yes. Download and install. Follow the link below for drivers.
http://forum.xda-developers.com/showthread.php?t=882751
Once SDK and drivers are installed, connect the NC. open command prompt (start menu, run, CMD), type adb devices
You should get a return back of some numbers and DEVICE. This means SDK and drivers were installed correctly. Once ADB (SDK) is installed correctly follow this thread.
http://forum.xda-developers.com/showthread.php?t=857732
Post up if you need some more specifics.
fprice02 said:
NDK? Did you mean SDK (android for windows developer kit), If so yes. Download and install. Follow the link below for drivers.
http://forum.xda-developers.com/showthread.php?t=882751
Once SDK and drivers are installed, connect the NC. open command prompt (start menu, run, CMD), type adb devices
You should get a return back of some numbers and DEVICE. This means SDK and drivers were installed correctly. Once ADB (SDK) is installed correctly follow this thread.
http://forum.xda-developers.com/showthread.php?t=857732
Post up if you need some more specifics.
Click to expand...
Click to collapse
Thanks!
Even though I installed the JDK 6u23, the Android SDK installer won't let me install because it doesn't see the JDK installed...
I used the same 623 package, installed that, then reboot, then install the SDK. BTW what OS are you using?
fprice02 said:
I used the same 623 package, installed that, then reboot, then install the SDK. BTW what OS are you using?
Click to expand...
Click to collapse
Win x64... I installed the 32-bit version of the JDK and got it..
If you're totally new, I'd suggest heading over to http://nookdevs.com/NookColor and reading up there.
fprice02 said:
Once SDK and drivers are installed, connect the NC. open command prompt (start menu, run, CMD), type adb devices
You should get a return back of some numbers and DEVICE.
Click to expand...
Click to collapse
CMD is giving me 'adb is not recognized as a command'
The nook drivers are installed, along with the SDK
ironcrotch said:
If you're totally new, I'd suggest heading over to http://nookdevs.com/NookColor and reading up there.
Click to expand...
Click to collapse
This helped, thanks
fprice02 said:
Once ADB (SDK) is installed correctly follow this thread.
http://forum.xda-developers.com/showthread.php?t=857732
Post up if you need some more specifics.
Click to expand...
Click to collapse
My SDK install is in C:\Program Files (x86)\Android\android-sdk-windows
When I run in cmd:
cd\
cd Program Files (x86)\Android\android-sdk-windows\platform-tools
I can run adb commands. The thread wants me to run sqlite3 commands too, but they are in a different directory:
C:\Program Files (x86)\Android\android-sdk-windows\tools
I am pretty confused on what to do
Do you guys use search at all or check the development forum for this device i mean come on its all in black and white.
I don't know what I did exactly, but I managed to install apk's from the root of my SD card
sweet
Please someone help!
After following instructions of Easy USB ADB Installer for Windows, and running adb devices, my nook didn't show up as a device.
Also I tried installing a software and it said application not install.
Thanks in advance
Easier thing to do is go into Settings --> Application --> Unknown Sources then download an APK with your Browser and install it from the Downloads window. I suggest finding an APK for Astro File Manager and get Dropbox, that way you can install Apps straight from Cloud storage.
____________________________________________________
Sent from Nookie Froyo using Tapatalk
Try this Bro, it's the easiest way to get the USB Drivers onto your PC and then your NC recognized.
http://forum.xda-developers.com/showthread.php?t=910008
thereddog said:
Thanks!
Even though I installed the JDK 6u23, the Android SDK installer won't let me install because it doesn't see the JDK installed...
Click to expand...
Click to collapse
I have that same problem, have you found a fix for it yet?
I'm running Windows 7 x64
with an I-7 Processor
I've install [ROM][2.3.5][10/14/11] MIUI Development 1.10.14 http://forum.xda-developers.com/showthread.php?t=1066885.
But when my captivate not connect to laptop by USB.
I try hidden code: *#7284# but it not work in my phone.
Help me
Reinstall drivers
Install Android sdk because your computer probably sees it as a nexus s
Sent from my SAMSUNG-SGH-I777
To install sdk, you need to install (or already have) Java JDK installed.
mrhaley30705 said:
To install sdk, you need to install (or already have) Java JDK installed.
Click to expand...
Click to collapse
from the Android SDK page:
If you downloaded the Windows installer (.exe file), run it now and it will check whether the proper Java SE Development Kit (JDK) is installed (installing it, if necessary), then install the SDK Tools into a default location (which you can modify).
its not a requirement to install it on your own any more, apparently
Yep, that's new to me.
mrhaley30705 said:
Yep, that's new to me.
Click to expand...
Click to collapse
it would appear that with each new release of sdk, that they make it more and more noob friendly. thank god for that
now all they need to do is make the installer include adb in the environment path automatically (or by choice, via installation selection)
explaining to a noob to:
install java jdk
download android sdk > unzip it in a location you can find easily
add adb to environment path OR cd c:\path\to\sdk\folder
hell, with most of the noobs you lose them at install java jdk....
Im learning android dev n java. When i had official v20a, it was shown in eclipse online when i ran my apps for testing.
But since i installed cm 10.1 (april 29 updated), it shows my phone but offline n i cant test my apps
Sometimes it show up as online but most of the times it show my phone offline. When it is offline i tried following things but it does not show online even after them...
Tried unplug n plug my phone again
Tried restarting my phone
Tried restarting eclipse
But no hope. :banghead:
Can anyone solve this prob? I need it very much to test my apps.
Thanks in advance...
Sent from my LG-P880 using xda premium
Hi , try this:
1)Run eclipse : windows -> sdk manager . Close eclipse (not the sdk manager) and upgrade your sdk to 4.2.2 and perform all the updates that the sdk manager find.
2)Run eclipse : it will report some problem and advice you to check for updates : do it and upgrade. If eclipse doesn't report any error you can perform the check via help->check for updates.
3)Restart eclipse and you are ok
Zeph90 said:
Hi , try this:
1)Run eclipse : windows -> sdk manager . Close eclipse (not the sdk manager) and upgrade your sdk to 4.2.2 and perform all the updates that the sdk manager find.
2)Run eclipse : it will report some problem and advice you to check for updates : do it and upgrade. If eclipse doesn't report any error you can perform the check via help->check for updates.
3)Restart eclipse and you are ok
Click to expand...
Click to collapse
i already have 4.2.2 installed fully. and i said my phone sometimes is detected as online, but most of times it is offline
one more thing to mention.
my phone is also shown offline in adb, when i put this command in adb
adb devices [ENTER]
********** offline
it shows my phone's serial and then says it's offline, wtf?
the problem is in adb. In android 4.2.2 there is a debug usb protection .If you use the sdk 4.2.2 when you connect for the first time your device in usb debug, a popup on your screen device will ask you if that computer is trusted.
A lot of people have reported issues with this.. i've resolved easily with the upgrade of the sdk.
However there is a topic somewhere in xda with adb and fastboot drivers that work properly with 4.2.2 devices
this solved my problem.
i was studying this issue on many forums and blogs, and came to stack overflow. and found this answer.
go to your adb command prompt on pc and enter these commands one by one.
adb kill-server
set ADB_TRACE=all
adb nodaemon server
after that restart your pc,
Done!
now everytime i connect my phone with adb, it is online
Note: i don't know what these commands are doing, but it just solved my problem. the problem came out because of wrong path to sdk or something. and these commands do it magically lol, thats what i know.
Sooooooooooo,
I have a Z1 [C6903] that I picked up yesterday. It came with 14.2.A.1.136 Jellybean 4.3.
I wanted to
Unlock bootloader
Install custom recovery
Root
Install any nice AOSP ROM [preferably LP-based]
I installed the Minimal ADB-Fastboot 1.4.
I also installed the Flashtool 0.9.18.2.
I also installed the Z1 device, Fastboot, and Flashmode drivers [version 1.6.2] from the driver folder. It first failed, and then I disabled driver verification then everything went smooth!
Device manager recognized the phone in MTP and Fastboot, and Flashmode modes. Drivers installed correctly I presume.
Then the challenges arrive:
adb devices returned it as "offline"
Android studio couldn't push a project to it because it was offline
fastboot devices identified it, but fastboot -i 0x0fce getvar version returned an error [getvar:version FAILED (command write failed (Unknown error))]
Things I've tried to do to rectify the connectivity issue:
I'm using a SurfacePro 4 so I can't switch USB ports [only have one].
I've tried different cables - they yield the same result.
I've enabled and disabled USB debugging, revoked access, unplugged and replugged, rebooted, etc. Still no change in result.
Since the device had some OTA updates pending, I ran those and now i'm on 4.4.4 with 14.4.A.0.157, with some other updates currently waiting for me to accept so they can download. I've decided to post here for help and won't run those updates unless it increases my profit
PS: Even after the updates, adb and fastboot still are unchanged in their results.
Help please
Update:
It was a freaking USB cable. I had tried two of them. None had worked.
I finally unleashed my Anker USB cable and Boom! We good to go!!!
Thanks all!:highfive::highfive::highfive::highfive:
Make sure to enable USB debugging in Developer Options at the bottom of the Settings app
tomascus said:
Make sure to enable USB debugging in Developer Options at the bottom of the Settings app
Click to expand...
Click to collapse
Did this and more. Still to no avail.
The phone shows up in the computer, it just doesn't show as online when I run the adb devices command.
That's what I need help with.
Thanks
ahh have you tried using
Code:
adb kill-server
adb start-server
and trying again?
What should happen is the authorisation window pops up on your phone
tomascus said:
ahh have you tried using
Code:
adb kill-server
adb start-server
and trying again?
What should happen is the authorisation window pops up on your phone
Click to expand...
Click to collapse
Excellent! I did that, too. even manually closed and restarted adb.exe to no avail.
The thing is, my Z1 DOES NOT show me the authorization pop-up! Ever!
I've done this a million times on other phones, and I know the procedure. It's just that this Z1 is not showing the authorization popup
Thoughts?
boydee said:
Excellent! I did that, too. even manually closed and restarted adb.exe to no avail.
The thing is, my Z1 DOES NOT show me the authorization pop-up! Ever!
I've done this a million times on other phones, and I know the procedure. It's just that this Z1 is not showing the authorization popup
Thoughts?
Click to expand...
Click to collapse
Find a quiet corner and cry
Tried running adb as admin?
tomascus said:
Find a quiet corner and cry
Tried running adb as admin?
Click to expand...
Click to collapse
Tried this, too!
No change, anywhere.
I actually went ahead and tried adb on another PC with minimal adb-fastboot and adb drivers installed, and it returned the same "offline" response
Whoa!:angel:
@boydee
this could work with you
i assume that you rooted your phone you will do that:
1. open your favorite file explorer(suggest: ES File Manger)
2.go to /data/misc/adb/
3.delete "adb_keys" file
4.enable usb debugging
5.reinstall your drivers
6.open command and kill adb server(adb kill-server)
7.connect your device and run command (adb devices)
8.look at your device you will find text box telling you a new pc check always trust bla bla and click trust or something like that
9.you will see something like that
http://imgur.com/ReQtofb
How to upgrade to kitkat 4.4.4 India version of c6903 Sony Xperia Z1 pls help
DectonX said:
@boydee
this could work with you
i assume that you rooted your phone you will do that:
1. open your favorite file explorer(suggest: ES File Manger)
2.go to /data/misc/adb/
3.delete "adb_keys" file
4.enable usb debugging
5.reinstall your drivers
6.open command and kill adb server(adb kill-server)
7.connect your device and run command (adb devices)
8.look at your device you will find text box telling you a new pc check always trust bla bla and click trust or something like that
9.you will see something like that
http://imgur.com/ReQtofb
Click to expand...
Click to collapse
Hey, thanks for the advice!!
Finally got root [without use of PC] and when I open the /data/misc/adb/, the folder is EMPTY
A little confused there.
I did the same procedure for the PC [deleting from C:/Users/boydee/.android/] but it also was to no avail.
k9rockstar said:
How to upgrade to kitkat 4.4.4 India version of c6903 Sony Xperia Z1 pls help
Click to expand...
Click to collapse
Hey there! Please check here for a firmware file that works for you.
When you've downloaded, use the Flashtool to flash it to your phone.
If you want help flashing it to your phone, check this thread out.
Hope that helps
boydee said:
Hey, thanks for the advice!!
Finally got root [without use of PC] and when I open the /data/misc/adb/, the folder is EMPTY
A little confused there.
I did the same procedure for the PC [deleting from C:/Users/boydee/.android/] but it also was to no avail.
Click to expand...
Click to collapse
This could problem with installing drivers as PC don't detect adb in debugging mode
So disable driver verification again and install drivers from flashtool remember to check
1. Fastboot drivers
2. Flashmode drivers
3. Xperia Z1 drivers
And restart
If the problem not fixed try adb universal drivers just Google it
I was have same problem with win 8.1 but I didn't all that I just installed win 7 and do it
Remember to backup ta before unlock to backup your DRM keys
Former-Prime R1 HD 16GB
Windows v8.1
TL;DR:
I am unable to get my phone to be recognized in fastboot by the fastboot utility, yet it is recognized by adb. I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). Besides the fact that adb sees the phone fine with the cable I'm using, it's the same cable I have successfully used with my Samsung and Nexus devices. I'm at my wit's end. :crying: I could really use some help.
Full version:
I've followed the instructions from this thread to flash my phone into an OEM non-Prime device:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
It's now running V12. I want to verify the state of the bootloader and jump through the hoops to safely put V17 on it (without whacking the preloader, etc.). My problem is that when I try fastboot devices no devices are listed. However, adb devices shows the phone.
I installed ADB and fastboot v1.4.3 using the package from this thread:
https://forum.xda-developers.com/showthread.php?t=2588979
I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). I've got tzul's signed drivers installed which were obtained from this post using the enclosed instructions (both those in the "Android" and "CDC" folders):
https://forum.xda-developers.com/showpost.php?p=67927242&postcount=23
I also have the Android SDK's Platform Tools and Google USB driver installed and tried the adb and fastboot from there with the same results.
When booted to the Android OS, the phone shows up as Android Composite ADB Interface in Device Manager. When I use adb to try and reboot the phone into fastboot via adb reboot fastboot it merely reboots into the OS. To get into fastboot mode I have to do it via the bootloader (power+vol. up). When attatched in fastboot mode the phone shows up in device manager under "Other devices" as "Android" with The Yellow Triangle of Doom, and says drivers for the device aren't installed (Code 28). From what I've read, the drivers it's looking for are the in the "Android" folder of the drivers .zip I downloaded, which I have installed per the instructions.
Can someone please help me figure out what I've done incorrectly?
Fixed
As I had surmised, it was a driver issue. One of the driver bundles I had downloaded from androidmtk.com or another site foobar'd me. But before I had this straightened out, I gave up and used a Linux Mint virtual machine to verify my bootloader status, etc.
The way my drivers got straightened out was that I coincidentally ran Windows Update as I had updates available for which enough time had passed without reports of problems. Update offered me the following updates:
Important
Windows 8.1 Drivers
Microsoft - Other hardware - MTP Device
TP-LINK - Other hardware - Android Bootloader Interface
Windows 8.1 and later drivers
Samsung - Other hardware - Samsung Mobile MTP Device
Optional
Windows 8.1 Drivers
MediaTek - Other hardware - Android Composite ADB Interface
After installing these I again tried to use fastboot from my Windows box and it worked fine. So, one of the driver packs I installed screwed up my MTP drivers evidently (both the updates offered were from early last year). The TP-LINK driver was the VCOM I needed for fastboot to work.
So, all's well that ends swell.
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
OldSkewler said:
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
Click to expand...
Click to collapse
This shows adb is on , on your phone but you did not allow the connection. =. When you first connect pc to phone with usb cable and adb enabled , you should get a pop up window on the phone. You may need to wake the screen and unlock to see it. The window asks you to authorize the connection
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
Click to expand...
Click to collapse
You also missed a step here. You needed to reboot phone to bootloader /fastboot mode before asking to list fastboot devices.
So before that line you should have done "adb reboot bootloader"
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
Click to expand...
Click to collapse
mrmazak, you are absolutely right on both items. I wish I had come across something explaining this earlier... spent a lot of time sorting this out!
Hopefully this will help someone in the future!