i downloaded the sdk and i downloaded a samsung galaxy driver and when i look for my phone in the command line it just doesnt show up. theunlockt just isnt helping. anybody got a good link for dummies?
antonio91282 said:
i downloaded the sdk and i downloaded a samsung galaxy driver and when i look for my phone in the command line it just doesnt show up. theunlockt just isnt helping. anybody got a good link for dummies?
Click to expand...
Click to collapse
Did you put your phone in debug? Settings>Applications>Development
yes. and i been going over the directions repeatedly on theunlockr. im running xp 32 i believe
ADB for Dummies: Download http://de.codeplex.com/
- Once installed... open command prompt:
cd C:\Program Files\Droid Explorer\SDK\tools
Click to expand...
Click to collapse
- <type your ADB command here> e.g.
adb shell
Click to expand...
Click to collapse
^ yeah...
adb devices
Click to expand...
Click to collapse
should show your device...
To the OP, I don't know if this is the case for you but I changed my path on my Windows PC like the guides said to and that didnt completely work. (Maybe neede a restart). But in any case if you go to the command prompt, change directories to were you have adb and run your commands from there, it works like a charm.
For example if you unzip the the SDK in your download directory, open up the command line and type:
cd C:\Documents and Settings\<your user name>\Downloads\<whatever-you-named-the-unzipped-folder>\tools
ADB is in the tools directory you just went to. From here you can run the adb command without having to set up the system paths. This is a quick and dirty explanantion and might not even work for you. I was running this on Windows XP when I had this problem. Same thing had to be done on my Ubuntu Linux box b/c I'm to lazy to set up paths on that one, lol.
zephiK said:
ADB for Dummies: Download http://de.codeplex.com/
- Once installed... open command prompt:
- <type your ADB command here> e.g.
Click to expand...
Click to collapse
Oops, didnt see that you allready posted this. Yea do what zephiK says and it should work.
i have not been able to get adb to work no matter what i did (i am using xp) and i have been trying since i had the htc magic last year. here is how i recently got it working.
i downloaded the one-click root zip file and unzipped it. inside there is a adb.exe file. i clicked it and then then made sure my phone was in debugging mode and connected to my pc and used the command prompt to point to where adb is in my android sdk which for me is cd\androidsdk\tools
adb devices
i hit enter after tools and enter after devices and now it works. not sure why but it does. i couldnt get my magic, my nexus one or even the galaxy to work until i did this.
i got everything done. i think? only problem is im getting $ sign instead of # sign. any ideas?
i got adb working. thanks everyone.
A thread success story without any casualties. Almost makes me weep.
Hello,
My vibrant got recently run over by a car and the screen doesn't work anymore However, I know that it still can function because I can see the 4 capacitive keys on the bottom light up when I touch them. Is there anyway for me to be able to view the Vibrant's harddrive on my computer without having to switch to USB mode (since my screen doesn't work)?
if you have adb installed and know some basic linux commands you can use ADB to view the contents of your vibrants storage via command prompt and should be able to copy most of your data over. As far as a graphical solution i think there was something being developed called screen cast at some point but i dont think that will be much use to you as i believe it has been abandoned
I am familiar with adb but I can't see my device for some reason when I connect my phone to my computer and run 'adb devices'. I've used adb in the past to push / pull files but I remember having to mount the device from the dropdown menu before it would be recognized. Is there any way to force the phone to be connected? Thank you for your help!
isyiwang said:
I am familiar with adb but I can't see my device for some reason when I connect my phone to my computer and run 'adb devices'. I've used adb in the past to push / pull files but I remember having to mount the device from the dropdown menu before it would be recognized. Is there any way to force the phone to be connected? Thank you for your help!
Click to expand...
Click to collapse
are you on a stock rom? ever since i started using custom roms ive always had ADB debugging enabled, unfortunately you may be SOL if you need to enable ADB debugging as both the adb method and screen cast require ADB to work,the other option is to take apart your vibrant and have the internal memory chip read that way tho your stand a good risk of damaging the internal memory chip
when I type adb devices cmd in the terminal it does not list my device and its plugged in....
when I try to type adb usb it says no devices found...
for the record nothing is wrong with my USB connection cable because, I'm able to connect my HTC ReZound via USB cable to my macbook, the CDROM and STORAGE auto mounts to my desktop so i know the connection is working, because I'm able to copy files, update music via winamp sync playlists, also my paid EasyTeather copy works, etc.
I updated & installed most recent Android SDK adt-bundle-mac-x86_64-20130917 and updated the device manager for my ver 4.0.3 and all tools, even tryed using a stand alone platform-osx-tools.zip that contains a adb and fastboot...\
I read up on this and found nothing tryed everything....
adb kill-server > adb start-server - does nothing
adding device in the adb_usb.ini didn't help either.
chmod a+r /etc/udev/rules.d/51-android.rules after creating file didn't help.
rebooted many times .
i've attached a terminal cmd window below to show.
USB debugging is enabled on the device, yes? Does the "USB debugging enabled" notification show up when you plug it into the computer?
MaxxPayne said:
when I type adb devices cmd in the terminal it does not list my device and its plugged in....
when I try to type adb usb it says no devices found...
Click to expand...
Click to collapse
are you doing proper methods in command prompt for sdk's adb such as directing it to the folder its in...example did you type cd c:/androidsdk/platform_tools/ in command prompt for example
I used to have a mac ....but here
Download htc sync for mac
http://www.iskysoft.com/convert-mobile/sync-htc-to-mac.html
Download the sdk and all you need is a folder called platform tools
http://developer.android.com/sdk/index.html
Extract the platform tools folder Put it on your desktop
Open terminal type "cd" then hit space then drag and drop the platform tools folder into the terminal after that hit enter
Then you can run any command just make sure to put "./ " before the command without quotations so if you wanna flash a boot you would put
./fastboot flash boot boot.img and hit enter
Note that adb works perfectly well on my Mac without the HTC Sync drivers.
Hi guys,
EDIT: See the last posts - I have figured this out, and tried to include helpful information, if you are having this problem too.
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
urbainmenace said:
Hi guys,
Firstly please accept my apologies if this has been answered already. I have searched the forum, and the Internet, and cant find specific instructions, or a guide that I can follow with any success.
I stupidly deleted system files from my Kindle, but now I have purchased a fastboot cable, and I'am able to get it into fastboot mode.
I have correctly installed the ADB Drivers, and the device is now recognized by my Windows 7 Device Manager. It shows 'Android ADB Interface'.
I would guess that I need to flash the entire Kindle, but I'm unsure of how to do this, as I cannot seem to access the device at all. It currently loops when booting, giving me no time to see it as external storage via My Computer.
Please would someone more versed in this, guide me specifically through how to get myself back up and running again? I would be forever greatful.
I have SDK and JDK installed, but do not have the knowledge I need to learn how to use them properly.
Thanks so much in advance.
Click to expand...
Click to collapse
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
goodayoo said:
what is the fastboot cable? where can I get it? can a normal usb cable do the job?
Click to expand...
Click to collapse
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
urbainmenace said:
You definitely need the fastboot cable to push files through the ADB Interface dude. You can buy one for dirt cheap on EBay. Then all you do is simply plug it into your PC and Kindle, and it should put the Kindle straight into Fastboot mode.
Then you need to install the ADB Drivers for the Kindle.
From there, I'm stuck I'm afraid.
Click to expand...
Click to collapse
OK，I think I'm gonna get one and give it a try. the only way to fix this brick is in the ADB Interface I'm sure. though I also don't know How to do.
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
urbainmenace said:
I've finally figured out how to get ADB up and running, and how to start command prompt. I found this link helpful:
developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing
If anyone needs help pushing files through ADB, I recommend that link!
Do the following to detect your Kindle Fire tablet through ADB:
Open a command prompt window.
Change directory to your Android SDK platform-tools directory. - To do this, find out where SDK is installed on your PC. Copy the path.
Type cd in command prompt, then space, then paste the directory path. EG, C:\Users\Administrator\sdk\platform-tools
Hit enter, and the command line will change to read C:\Users\Administrator\sdk\platform-tools.
Run the following commands and confirm that the serial number for your Kindle Fire tablet appears in the list of devices.
adb kill-server
adb start-server
adb devices
Then follow the rest of the guide. I think all you need to to do, is push a system update through, by putting the file in the tools folder of SDK. This should make the device update, and put back any critical system files that you had previously deleted.
Now I'm just having issues with it finding the device, so I'm going to charge the Kindle for a few hours, and then try it again.
:good:
Click to expand...
Click to collapse
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
goodayoo said:
good to hear that! I hope you can tell me how to push the system folder into the fire hdx via ADB ,I got a thor-amazon-os-13.3.1.0.zip file.
Click to expand...
Click to collapse
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
bootlooped, adb runs some commands
urbainmenace said:
In command prompt, there is an ADB push command, so I think all you do is type that, then the path of the file.
To list all the commands you can use, change command prompt to your platform-tools folder within SDK, type ADB in command prompt, and it will give you all the options.
You'll need to unzip the update file first I think.
:good:
Click to expand...
Click to collapse
Working with the HDX 8.9.
I think I have deleted some of the system files also. I was reloading a safestrap backup and rebooted but the backup had failed to complete. I don't know what may be missing from the system files and would like to push the system files onto the device.
Right now I get a gray kindlefire screen for about 90 seconds, during which I have adb access, then it goes to the color kindlefire screen and asks if I want to Restore to Factory Defaults or reboot. I finally subjected it to the Restore to Factory Defaults, but that just wiped the cache and data partitions, I don't see where it did anything to the system files. It did not change my adb access.
In adb I can push files to some locations but others say: failed to copy ....: Read-only file system.
I cannot run shell commands
# adb shell
soinfo_link_image(linker.cpp:1617): could not load library "/vendor/lib/libNimsWrap.so" needed by "/system/bin/sh"; caused by load_library(linker.cpp:745): library "/vendor/lib/libNimsWrap.so" not foundCANNOT LINK EXECUTABLE
I was working in Windows 8.1 but have switched to Suse Linux but the results are the same so far.
I have the stock system files but I am not sure how to push them to the device, if it can be done, while the device is trying to reboot.
fastboot
I can put the HDX in Fastboot mode with the adb command. But when I try to pass commands to the HDX I get:
< waiting for device >
and I have to Ctrl-c to stop the process.
Do the fastboot commands only work if you have a fastboot cable???
Since you guys are using adb checkout these threads:
http://forum.xda-developers.com/showthread.php?t=2530623 Factory Reset
http://forum.xda-developers.com/showthread.php?t=2636817 [Video Tutorial] GAPPS + Amazon from Cpasjuste
http://forum.xda-developers.com/showthread.php?t=2638241 How to un-boot-loop (another way)
http://forum.xda-developers.com/showthread.php?t=2598577 [TUT/FIX] Fix the Boot Loop on Kindle Fire HDX 7"
This guy may also be able to help, forum member: GSLEON3 Post #16
http://forum.xda-developers.com/showthread.php?t=2580989&page=2
I'm sorry if this has been answered already. But I'm having a hell of a time getting ADB to work. I have the latest drivers installed as well as Android dev tools. I connect my G3 to my laptop and put it in "Ethernet" mode with USB Debugging checked off. I open up a command prompt and cd to my platform-tools folder. I then type adb devices. No matter what, it won't recognize it. I've rebooted phone, laptop and even deleted the "adbkey" file to see if that would fix it. Any ideas guys? I'm on Windows 8.1. It's not a huge deal because I can just use Terminal Emulator to execute most of the commands. But it would be nice to have ADB working. Never had a problem with it on my G2.
Fuse8499 said:
I'm sorry if this has been answered already. But I'm having a hell of a time getting ADB to work. I have the latest drivers installed as well as Android dev tools. I connect my G3 to my laptop and put it in "Ethernet" mode with USB Debugging checked off. I open up a command prompt and cd to my platform-tools folder. I then type adb devices. No matter what, it won't recognize it. I've rebooted phone, laptop and even deleted the "adbkey" file to see if that would fix it. Any ideas guys? I'm on Windows 8.1. It's not a huge deal because I can just use Terminal Emulator to execute most of the commands. But it would be nice to have ADB working. Never had a problem with it on my G2.
Click to expand...
Click to collapse
I sometimes have to reinstall the drivers while the phone is connected.
Thanks. I'll give that a shot
Wow, it worked! Thanks so much. I spent hours trying to figure this out :x