why do i NEED this adp program, all it does is push files to the sdcard right? Windows 7 (not sure about vista) has the android software drivers prebuilt into the 7000 beta. If the only reason i need adp is to copy files to the sdcard (which i do when i just mount the device and up pops the sdcard) than i shouldnt bother reading into this anymore.
adb is for much more than just pushing files. It is the debugger interface for android that allows a lot of things, including, installing/uninstalling apps. pushing/pulling apks, shelling into the phone, and so on.
The sdk works well in windows 7 too. That's what I've been using lately.
It's a developer tool. If you're not a developer you don't need it.
alright, install uninstall, which can be done with the app installer through the root of the sdcard. Same way i put the multitouch apps to play around with. Shelling into the phone is as easy now as opening the terminal on the phone and doing what i need through the file system.
The "linux guru" is asking why he needs adb?!?
ADB can be used to push things to places other than the sdcard.
I, for my part, prefer to shell with my full-size keyboard when I want to do anything long and involved.
you can't mount you sdcard if you phone doesnt boot up, but you can still push, also you can perform commands that are cant be done in terminal emmulator, you can run commands while phone is in recovery mode, you can use the debug monitor and so much more fun stuff
inpherno3 said:
If the only reason i need adp is to copy files to the sdcard
Click to expand...
Click to collapse
Hahahaha
Related
1. DOWNLOAD USB DRIVERS
Motorola ADB Driver 32bit
Motorola ADB Driver 64bit
2. INSTALL THE SDK
-Download latest SDK http://developer.android.com/sdk/index.html
-Extract Archive to C:\SDK\ (or C:\Android, or whatever you want)
3. Enable debugging on your phone (thanks naplesbill)
-Goto Settings > Applications > Development > and Check the USB debugging option
4. Optional, but recommended
-Setup Enviroment Variables:
On Windows, right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the tools/ directory to the path AFTER A SEMICOLON (;C:\SDK\tools\) .-Setup Droid Explorer:
Goto Droid Explorer Downloads and snatch the latest version, then install. (mine showed an error during install i believe due to the lack of HTC drivers. If you installed motorola's drivers it should still be in your start menu and work fine)
If for some reason you can't figure it out, install the drivers then try this installation guide: ADB For Dummies Guide
ADB APK Install instructions
j101399j said:
1. Create a folder called adb on your C drive
2. Extract all files to your adb folder
3. Copy the cmd.exe file (copy the file don't make a shortcut to it or move it) from your "C:\Windows\System32" folder to the adb folder
4. Install the downloaded USB driver
4. Once you have the driver installed, on your phone enable debugging mode (Menu --> Settings --> Applications --> Development --> Check USB Debugging)
5. Copy the apk files you want installed to your "C:\adb\tools" folder. The adb.exe and cmd.exe should be in that tools folder.
5. Open the cmd.exe file
6.Type the following command:
Code:
Code:
adb install [B]application.apk[/B]
Where application.apk is the name of the apk to install
Your app should now be installed
Please note that you cannot install apps used on 1.6, 2.x builds
Click to expand...
Click to collapse
BACKFLIP SYSTEM DUMP http://forum.xda-developers.com/showthread.php?t=642684
BACKFLIP SOURCE CODE http://forum.xda-developers.com/showthread.php?t=645369
Don't you still need root?
I fail to see how this can help without rooting the Backflop unless Droid Explorer has some way of overriding that setting.
Charrion said:
I fail to see how this can help without rooting the Backflop unless Droid Explorer has some way of overriding that setting.
Click to expand...
Click to collapse
It doesn't help deleting the protected apps, but it makes it easier to install apks. This is especially helpful since the backflip doesn't allow anything to be installed through phones interface except through the market.
Ok, it works, but only if you turn on the Applications, Development, USB Debugging in the settings menus.
Well, that's kind of a given as ADB won't work without USB Debugging on.
Charrion said:
I fail to see how this can help without rooting the Backflop unless Droid Explorer has some way of overriding that setting.
Click to expand...
Click to collapse
We meet again Charrion! This is like the third time today I've run into you.
Don't need to have root to install APKs via ADB. Even us poor Milestone owners can do it via 'ADB install <app.apk>.'
I am just pointing that out for those that aren't familiar with that. I imagine there will be users who wouldn't normally bother with this, doing it just to be able to install non-market apk files.
naplesbill said:
I am just pointing that out for those that aren't familiar with that. I imagine there will be users who wouldn't normally bother with this, doing it just to be able to install non-market apk files.
Click to expand...
Click to collapse
Ah, fair enough. Sorry about that.
Unimaginative said:
Well, that's kind of a given as ADB won't work without USB Debugging on.
We meet again Charrion! This is like the third time today I've run into you.
Don't need to have root to install APKs via ADB. Even us poor Milestone owners can do it via 'ADB install <app.apk>.'
Click to expand...
Click to collapse
I'm on a crusade
OK, so you can install apks through adb even without unknown sources being enabled.
Has anyone determined if the option to enter debug mode is still available on the backflop? I wouldn't be at all surprised if they disabled that option also.
I'm also curious whether the backflop has a signed mbm like the Milestone to prevent loading custom roms.
Charrion said:
I'm on a crusade
OK, so you can install apks through adb even without unknown sources being enabled.
Has anyone determined if the option to enter debug mode is still available on the backflop? I wouldn't be at all surprised if they disabled that option also.
I'm also curious whether the backflop has a signed mbm like the Milestone to prevent loading custom roms.
Click to expand...
Click to collapse
The use debug mode is indeed available, I just forgot to mention turning it on.
From what I understand, this phone will be rooted like the cliq.... unfortunately for that to happen certain key files need to be leaked.
@moosefist;
Thank you so much for posting this.
I am now able to install non-Market apps
moosefist said:
The use debug mode is indeed available, I just forgot to mention turning it on.
From what I understand, this phone will be rooted like the cliq.... unfortunately for that to happen certain key files need to be leaked.
Click to expand...
Click to collapse
So; I'm new to the whole Android stuff; but what files need to be "leaked" in order to do this?
Squeaky369 said:
So; I'm new to the whole Android stuff; but what files need to be "leaked" in order to do this?
Click to expand...
Click to collapse
According to Skrilax_CZ a modmymoto moderator:
If we are up to root it; we need the shx/sbf flashfile, which must be leaked. Then I can see if the CLIQ RAMDLD exploit is present in here or whether has it been fixed as on the new CLIQ firmwares.
Click to expand...
Click to collapse
It was those files being leaked that allowed the CLIQ to be rooted...
I will be watching this thread closely I'm tired of having edge on my android....I need 3g for once!
Has anyone given this a try under Linux? I read the ADB beginners guide, but it didn't mention anything about drivers or whatnot. I'd really like to get this phone, but if I can't develop for it on my platform of choice, I don't think I need it that badly.
JK_the_Slacker said:
Has anyone given this a try under Linux? I read the ADB beginners guide, but it didn't mention anything about drivers or whatnot. I'd really like to get this phone, but if I can't develop for it on my platform of choice, I don't think I need it that badly.
Click to expand...
Click to collapse
This is from androidforums.com about this spicifically
http://androidforums.com/motorola-b...on-market-apps-via-adb-solved.html#post419647
On MacOS, ADB doesn't need a USB driver for your phone. Just download the SDK, and you can execute ADB from a terminal.
On Linux, all you need to do are to follow the instructions here:
Developing on a Device | Android Developers
Specifically the bit about creating and chmod'ing an /etc/udev/rules.d/51-android.rules file.
Hope AT&T fixes this issue soon, it's ridiculously stupid to attempt to disallow non-market apps given that ADB works.
Click to expand...
Click to collapse
j101399j said:
This is from androidforums.com about this spicifically
(URL deleted for forum reasons)
Click to expand...
Click to collapse
Thanks much, I'm just getting started on navigating all these forums. =)
Would it be possible for someone to create a utility to turn this option on, then load it via ADB? Or would this require root access?
BetterCut or AnyCut?
Charrion said:
I'm on a crusade
OK, so you can install apks through adb even without unknown sources being enabled.
Has anyone determined if the option to enter debug mode is still available on the backflop? I wouldn't be at all surprised if they disabled that option also.
I'm also curious whether the backflop has a signed mbm like the Milestone to prevent loading custom roms.
Click to expand...
Click to collapse
I don't have a Backflip, but it may be possible to find hidden settings / controls by using BetterCut or AnyCut. Both are in the Market.
I'd be interested in knowing. A crippled phone is a tiny electronic soul yearning to breathe free and live free.
I have a backflip, and just installed anycut. Do you know what I would need to fill in as the new shortcut to get to that option? I'm at work now, but will be doing the development method to install apks later under linux (gowalla app, most likely)
This is my first android phone, so I'm pretty excited to get it broken open and crapware free.
I just ordered the Backflip. Yes, I'm a newb at all this andriod, and rooting stuff. But, I'm in the process of learning more. I think it will be easier when I have the phone in hand to play with.
But, do you guys really think that someone will take the time to root the backflip, considering, (what I have read) that it is alittle out dated?
I'm going to attempt the non-market app install, once I get the phone. This forum is great, from what I've seen so far. I'll definatly be staying tuned to this thread.
Thanks guys,
J
I currently have a mytouch 3g and am running a slide rom on it, problem is there is no keyboard, how do I manually install an apk file preferrably from the computers console such as swype or astro both of which apk files are currently on my sd card. Any help is much appreciated, I started using this forum in 2008 but have never once posted, sad really. ive been trying to install it via adb commands but I keep getting device not recognized errors, feel free to flame my noobishness
Once you have a file explorer you can just click on APKs to install them. If you don't have access to the market to get a file explorer you will have to install them using the ADB method. I found a forum post that gives some rough instructions, but it sounds like you don't have ADB set up correctly. Also I believe the path used with the adb install command is the location of the apk on the PC.
http://androidcommunity.com/forums/f4/how-to-install-apps-using-adb-4482/
The following is a response to someone having a similar problem on another site:
http://www.androidkit.com/steps-to-install-and-uninstall-apk-file-on-android-g1-device
The message is coming because the drivers for the G1 Android device are not properly installed.
If you are running windows, Check so:
Right click on My Computer, and click Manage, then go to the device manager
If you see an “ADB Interface” category at/near the top, with “HTC Dream” under it, then you’re good to go.
Else, you need to install the drivers by pointing to the driver location to the usb_driver folder under the android sdk folder installed by you, while the device is connected, and the system prompts for it.
Click to expand...
Click to collapse
Will we be able to put Side Loading Apps on the captivate without rooting?
Yes, you download and extract the android sdk, connect the phone to your computer and make sure you can detect it with command promt (or terminal in linux or equivalent in mac) by changing to the sdk directory then tools and type adb devices. If it comes up then type the command adb install name_of_the_file_your_trying_to_install.apk.
This worked for aria before root and has worked for the backflip community for some time, no reason to think it won't work for the Captivate. (Sorry for bad explanation, tired and might be a few mistakes in there but thats the quick version of it)
i thought rooting was required?
cropythy said:
Yes, you download and extract the android sdk, connect the phone to your computer and make sure you can detect it with command promt (or terminal in linux or equivalent in mac) by changing to the sdk directory then tools and type adb devices. If it comes up then type the command adb install name_of_the_file_your_trying_to_install.apk.
This worked for aria before root and has worked for the backflip community for some time, no reason to think it won't work for the Captivate. (Sorry for bad explanation, tired and might be a few mistakes in there but thats the quick version of it)
Click to expand...
Click to collapse
wouldn't necessarily call that "side-loading" you still wont be able to backup all your apks to the sd card and install them from the sd card if u need to wipe.
Is it not possible to pull the SD card, and copy apps to it from PC, and then put back in and install?
That would be the definition of side-loading ATT is refering to. Some people just need to be told a third, fourth, fifth time.
Thanks for the adb mention.
hello. ive been reading on different forums on the best way to sideload apps on captivate on mac. ive read about sideload wonder machine but seems ppl have problems... seems ppl r being more successful on pc.... if i were to run parallels then win 7 and try to use sideload wonder machine on pc will it work? im still reading on how to use commands, and terminals and cmd lines and all that . im new to android but familiar with winmo phones and jailbreaking iphones. so if anyone can help me or point me to the right direction, it is greatly appreciated! on a side note, i use parallel's and ran win 7 and dl droid explorer to try and delete some at&t bloatware but no go. when i try to delete it nothing happens... so i dont know what to do! lol. im rooted and all. i wanna have sideload next! thanks again guys!
1. Install Android SDK for Mac
2. Using Terminal CD to android-SDK/Tools directory
3. place your apk file in the tools directory
4. In terminal type: adb install file.apk <where file.apk is what you want to install>
This is the manual way on windows and this is what sideload wonder does for you. If you want to learn - this is the best way to start. ADB is easy, and it opens up the gateway for everything else.
YOu can probably find a more detailed tutorial on using ADB commands in Mac.
ADB is what lets you copy system files off the phone, change permissions, get access to the systems.db where you can allow sideload from phone, etc.
Portable ADB Prompt
If you're on the road and you need an ADB prompt to interact with your phone, many people will be lost as to what to do. It's kind of hard to carry the Android SDK on a flash drive, and if you're doing that solely for an ADB prompt, then it's kind of useless.
Basically, I've packaged an ADB prompt into a portable package for debuggers, hackers, and others to carry on the road. It fits on a small USB drive, and can even sit on your phone's SD card slot, ready to use.
You don't need a working copy of the Android SDK to use it. I've tested this on several computers, with and without the SDK on them.
So far a Windows-only copy is working fully. I haven't started on a Linux repackage, and perobably won't do a Mac port (unless a Mac owner/user is willing to).
All you need to do is extract the package, run adbprompt.bat, and you're good to go!
I'm sure this is stable enough for everyday use. Although seeing as I haven't explored every single facet of ADB on this portable package, I can't be too sure. It's labeled as a BETA until I've confirmed its stability.
Download link is below.
This is pretty handy to have. I'd be willing to look into this for a mac. If I'm not mistaken, it should just be one file. I've been playing around with a 1-click-root for mac and come to find that only the adb file from the sdk is needed for the command prompt to work.
Sweet, feel free! It's be pretty cool if you could put it up in this thread to - y'know, as a central hub for portable ADB prompts.
If you want, you could do a port/repackage. Basically it's just caling the ADB executable, executing adb command, and looping back to ask for more input. Simple, really. Easier than cding to the directory with the exe and all that wankery.
The best thing to do by means of disribution would be to package it in a .dmg and make it call a script to to the input-execute-loop thing (I don't know much about Mac file extensions). If you understand Windows batch code, you could try interpret adbprompt.bat to work with the Mac's native shell code - which I think is .sh, correct me if I'm wrong.
So yeah, port it if you want, send it my way through a PM (upload it to mediafire or something), and I'll put it up - with appropriate credit of course
Kickface said:
Portable ADB Prompt
If you're on the road and you need an ADB prompt to interact with your phone, many people will be lost as to what to do. It's kind of hard to carry the Android SDK on a flash drive, and if you're doing that solely for an ADB prompt, then it's kind of useless.
Basically, I've packaged an ADB prompt into a portable package for debuggers, hackers, and others to carry on the road. It fits on a small USB drive, and can even sit on your phone's SD card slot, ready to use.
You don't need a working copy of the Android SDK to use it. I've tested this on several computers, with and without the SDK on them.
So far a Windows-only copy is working fully. I haven't started on a Linux repackage, and perobably won't do a Mac port (unless a Mac owner/user is willing to).
All you need to do is extract the package, run adbprompt.bat, and you're good to go!
I'm sure this is stable enough for everyday use. Although seeing as I haven't explored every single facet of ADB on this portable package, I can't be too sure. It's labeled as a BETA until I've confirmed its stability.
Download link is below.
Click to expand...
Click to collapse
With Your permissions i would like to upload this file and any updates of it to my dropbox to share on OXygenRom Forum
Regards
Yeah, sure! Feel free! Just make sure you credit Kickface of xda-developers forums for the package.
And although I don't own a Desire, I've joined up at the forums.
Good luck with the ROM!
Cool think for my flash-drive, but this version doesn't support the 'connect' command or?
i wanted to use it with the App 'adbWireless'.
Great. Exactly what i was looking for. I will try this and report back.
Sadly, I get an error saying "the system cannot find the file specified" with every command I try to run
I think a "portable" ADB is already in the SuperOneClick root solution. It has a folder called adb with the executable and a couple of .dll. It worked great on first try, so to anybody who this might not work, you can download SOC and extract the folder from there.
Thanks for your work though
Sweet. This is pretty much an essential tool for me.
You should add an if/goto label command before the 'cd src' so it only tries to cd once. This would prevent the 'The system cannot find the path specified.' message after every command
:newline
if exist AdbWinApi.dll goto jump
cd src
:jump
Thank you so much for this.
I moved your batch file in the "src" directory and modified line 12 to make it more "portable":
Code:
cd %~dp0
nice software but seems it is a bit out of date, my Note 4 with 5.1.1 doesnt get recognized.