So ive been trying to figure out how to push files onto my eris for like a week now and im not smart enough with computer to so it. Ive downloaded the mac ADB, and have a 2.2 emulator up and running. But when i plug my phone in i cant ever find it using terminal. Im pretty sure its just cause im using the wrong commands so if anyone knows them for a mac that would be awesome. Any info would help me, Thanks.
No emulator is involved. Find the adb executable, and cmd+c to copy it. Fire up terminal and cmd+v to paste it, then type a space, then "push" (without the quotes), then a space, then drag the file you want to copy onto the terminal window, then type the location on your phone you plan on pushing to (like /system/app/ for example). And that's it! But you should do an adb remount before pushing. Again, to do a remount, paste the adb file into terminal or drag it in, then type a space, then "remount" (without the quotes).
It's been a while since I did the initial install steps, but the main difference to the commands is having to use a dot and a slash before the command "./" to specify the command you want to run is in the directory you're working in. Other than that, the PC steps are the same.
For example, my files are in a sub-directory under my user profile: /Users/<user_name>/Phone/android-sdk-mac_86/tools/ which can also be typed as ~/<user_name>/Phone/android-sdk-mac_86/tools/
So, in Finder, I go to that directory and double click the android file. That starts terminal which also starts the Android app. I go back to Terminal, press Command+T to open a new tab in Terminal (just so I won't have a ton of windows open), change directory to ~/<user_name>/Phone/android-sdk-mac_86/tools/ then I run the adb command typed as ./adb
So, to re-cap step by step:
My adb files are located in ~/<user_name>/Phone/android-sdk-mac_86/tools/
Make sure your phone is connected in USB debugging mode
In Finder, go to the above directory and double click android
Switch back to Terminal, press Command+T to open a new tab and change directory to ~/<user_name>/Phone/android-sdk-mac_86/tools/
Type: ./adb remount
Type ./adb shell (or whatever adb commands you want to run)
So im trying to get HDMI mirroring on my atrix
I've successfully rooted the phone (and it shows up as rooted with root check app)
I've downloaded eclipse and gotten android SDK manager (and AVD) operating.
I changed the PATH on my cpu to include:
;c:\android-sdk-windows\tools;c:\android-sdk-windows\platform-tools
(which is the file location I saved SDK to)
When i have my phone plugged in and if i go under Control Panel>Hardware and Sound>Device Manager>
ADB Interface (and subgroup Mot Composite ADB Interface) show up
but when i open the command prompt and try to open the adb shell it says:
'adb' is not recognized as an internal or external command,
operable program or batch file
Any help please?
(operating on windows vista 64 bit)
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
Hi,
Hope this is the right forum.
I just upgraded from Windows 7 to 10. Now Helium for Windows can't activate the backup on my android phones any more (Moto X and Samsung Galaxy).
Any settings that I need to change?
Thanks
--- update
I installed the driver from https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and now it's working.
Use the chrome version
I have tested on windows 10 build 11082 and worked.
I had the same problem: my Helium Backup App could not be activated by my Windows 10 helium desktop program.
I dived into it and saw that Helium uses ADB under the hood. But I found out it is using an older version of ADB.
When I typed ADB I got:
Code:
adb server is out of date. killing...
ADB is part of the huge Android Development Environment, but there is a thread showing you to install a compact standalone version: see http://bit.ly/1UgK4Xy
After installing that one, you will notice an ADB dir in the root of your windows C: drive.
Open command prompt and test if ADB can connect with your phone: type in command prompt (make sure helium desktop is closed):
Code:
adb devices
you should get result like:
Code:
List of devices attached
0123456789ABCDEF device
If you get something else like "0123456789ABCDEF unauthorized", check you have installed the correct drivers for your phone.
If connection is ok, copy all the files from C:\ADB to C:\Program Files (x86)\ClockworkMod\Helium\win32 (best to backup originals first).
Now you should be able to open your desktop Helium program and activate your Android Helium App.
xplorr said:
ADB is part of the huge Android Development Environment, but there is a thread showing you to install a compact standalone version: see http://bit.ly/1UgK4Xy
After installing that one, you will notice an ADB dir in the root of your windows C: drive.
Open command prompt and test if ADB can connect with your phone: type in command prompt (make sure helium desktop is closed):
Code:
adb devices
you should get result like:
Code:
List of devices attached
0123456789ABCDEF device
If you get something else like "0123456789ABCDEF unauthorized", check you have installed the correct drivers for your phone.
If connection is ok, copy all the files from C:\ADB to C:\Program Files (x86)\ClockworkMod\Helium\win32 (best to backup originals first).
Now you should be able to open your desktop Helium program and activate your Android Helium App.
Click to expand...
Click to collapse
Easy enough fix. Wonder if the Helium creators will update.
This worked perfectly! Thanks so much!
this worked perfect for me!
The coder really should make his windows application just point to the default ADB installation folder. Or better yet, he should have a prompt/wizard which will lead the user to the default directory but also give them the opportunity to point to a non-default location. Since ADB is a pre-requisit for this program, users just need to be told "go to the android website and download platform-tools or the android studio." I prefer the studio because it comes with the GUI sdkmanager and that's nice because I dont have to go anywhere to find out if there has been an update to platform-tools, it tells me right away and will download/install it for me. And that's good for me cause I can be pretty lazy sometimes.
xplorr said:
I had the same problem: my Helium Backup App could not be activated by my Windows 10 helium desktop program.
I dived into it and saw that Helium uses ADB under the hood. But I found out it is using an older version of ADB.
When I typed ADB I got:
Code:
adb server is out of date. killing...
ADB is part of the huge Android Development Environment, but there is a thread showing you to install a compact standalone version: see http://bit.ly/1UgK4Xy
After installing that one, you will notice an ADB dir in the root of your windows C: drive.
Open command prompt and test if ADB can connect with your phone: type in command prompt (make sure helium desktop is closed):
Code:
adb devices
you should get result like:
Code:
List of devices attached
0123456789ABCDEF device
If you get something else like "0123456789ABCDEF unauthorized", check you have installed the correct drivers for your phone.
If connection is ok, copy all the files from C:\ADB to C:\Program Files (x86)\ClockworkMod\Helium\win32 (best to backup originals first).
Now you should be able to open your desktop Helium program and activate your Android Helium App.
Click to expand...
Click to collapse
xplorr said:
I had the same problem: my Helium Backup App could not be activated by my Windows 10 helium desktop program.
I dived into it and saw that Helium uses ADB under the hood. But I found out it is using an older version of ADB.
When I typed ADB I got:
Code:
adb server is out of date. killing...
ADB is part of the huge Android Development Environment, but there is a thread showing you to install a compact standalone version: see http://bit.ly/1UgK4Xy
After installing that one, you will notice an ADB dir in the root of your windows C: drive.
Open command prompt and test if ADB can connect with your phone: type in command prompt (make sure helium desktop is closed):
Code:
adb devices
you should get result like:
Code:
List of devices attached
0123456789ABCDEF device
If you get something else like "0123456789ABCDEF unauthorized", check you have installed the correct drivers for your phone.
If connection is ok, copy all the files from C:\ADB to C:\Program Files (x86)\ClockworkMod\Helium\win32 (best to backup originals first).
Now you should be able to open your desktop Helium program and activate your Android Helium App.
Click to expand...
Click to collapse
i Don't believe such a simple trick works ..... thank you very much ...