Database Users

[Q] Error: adb is not recogzined as an internal or external command

Error: adb is not recogzined as an internal or external command, operable program or batch file???
i successfully installed the android sdk 08 and still got this message.
Has winxp, tmobile GT

I had this same exact problem, but I was just able to get it working. First, this website is helped a lot:
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
Also, make sure you download the Java SDK package from the link given on that website.
Second, when the website says to "Run Windows command line tool (cmd) and go to D:\android-sdk-windows\tool" open command prompt and enter this code:
cd (enter the path to where the android SDK was installed), for example:
cd C:\android\android-sdk-windows\platform-tools
Notice how I entered "platform-tools" instead of just "tools" because this is the folder where the adb file is download with the android SDK. After you do this, you should then be able to apply adb codes (make sure the screen on your tab is on because you will have to accept superuser prompts, therefore your tab needs to be rooted).
Every time you open command prompt, you will have to enter:
cd thentheplacewheretheandroidSDKisinstalled
as stated above before you are able to enter adb commands.
Hope this helps!

@caveman999 is giving good advice. Working in the command window is weird to those who did not use old pc-dos environment.
You have to be in the tools directory or you have to edit your PATH in windows so you can use adb from any prompt.

thnaks for both of you guys i installed the java jdk and also specified the path in environment variables but still error message!

I could only get adb to work error-free when I was in the same directory as adb.exe program. Just change directories cd..(enter) etc until you are in that directory.

tabing said:
Error: adb is not recogzined as an internal or external command, operable program or batch file???
i successfully installed the android sdk 08 and still got this message.
Click to expand...
Click to collapse
I had the same error, until I downloaded and placed the .adb files accordingly.
Source: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
"UPDATE: If it says adb not found or something similar, download the ADB files and extract them into the Tools folder of the SDK (they were taken out by Google in the R08 version for some reason and need to be put back)."
download adb files from here: http://www.megaupload.com/?d=RTEY0Q97
The important thing is to put the files really under the "tools" folder.
When you check out above Source I am sure your problem will be solved

Thank you all problem solved

tabing said:
Thank you all problem solved
Click to expand...
Click to collapse
Glad to here it. Why not hit a few thanks buttons?!

[Q]Need help with ADB shell/push/etc

So im trying to mod my launcher of my stock desire build in my HD2 with 'rosie remap' found here ----> http://forum.xda-developers.com/showthread.php?t=876464
i downloaded all the neccesary sdk/adb/java requirements. the command part is where i get confused. here are some questions:
1. before i start the commands, do i restart into clockworkmod recovery? or is this another type of recovery?
2. i tried using the commands in 'cmd' while in android debugging mode but it seems like the commands required in that thread isnt working for me.
what am i doing wrong?

mini_robot said:
So im trying to mod my launcher of my stock desire build in my HD2 with 'rosie remap' found here ----> http://forum.xda-developers.com/showthread.php?t=876464
i downloaded all the neccesary sdk/adb/java requirements. the command part is where i get confused. here are some questions:
1. before i start the commands, do i restart into clockworkmod recovery? or is this another type of recovery?
2. i tried using the commands in 'cmd' while in android debugging mode but it seems like the commands required in that thread isnt working for me.
what am i doing wrong?
Click to expand...
Click to collapse
You can actually run ADB commands with the phone in Android or in CWM. I would recommend doing it in CWM though as you would typically have to reboot after pushing anything into the system folder... Just make sure that if you boot into CWM that you mount the /system partition/folder first before pushing anything to it!
As far as running the commands, out of the box the Android SDK doesn't add the tools to the Windows environment path. You either need to CD (in the command window) to the location where the SDK tools are located or add the tools to your environment path.

Digital Outcast said:
You can actually run ADB commands with the phone in Android or in CWM. I would recommend doing it in CWM though as you would typically have to reboot after pushing anything into the system folder... Just make sure that if you boot into CWM that you mount the /system partition/folder first before pushing anything to it!
As far as running the commands, out of the box the Android SDK doesn't add the tools to the Windows environment path. You either need to CD (in the command window) to the location where the SDK tools are located or add the tools to your environment path.
Click to expand...
Click to collapse
I did exactly that. I added the sdk tools to my path. Im just unsure of the commands

mini_robot said:
I did exactly that. I added the sdk tools to my path. Im just unsure of the commands
Click to expand...
Click to collapse
Oh, ok. In that case here is an example to push files to a device:
Code:
adb push tun.ko /system/lib/modules/tun.ko
This will push tun.ko from your present directory in a command window to /system/lib/modules/tun.ko. You always have to specify the full path and filename as the destination. The source can be a relative path.
Pulling files from a device works exactly the same way, just in reverse:
Code:
adb pull /system/lib/modules/tun.ko tun.ko
If you have more questions try checking out the ADB reference here: http://developer.android.com/guide/developing/tools/adb.html.

[How To] Installing Custom Kernels

Okay, this guide is for users with less experience and want to overclock their Kindle Fire. This is for Windows.
This section is if you haven't installed ADB yet
1) You need to download the Android SDK
Android SDK: http://developer.android.com/sdk/index.html
2) Open the SDK Manager and install the SDK Tools and SDK Platform Tools
3) You need to add the ADB path. First find where you installed the Android SDK.The default is in C:\Program Files\Android\Android-sdk or C:\Program Files (x86)\Android\Android-sdk, you can check in the SDK Manager at the top, it will tell you your path. Then click on the start button, and right click on my computer and hit properties. Then on the left click Advanced System Settings In the next box at the bottom is Environment Variables click on this. Under System Variables find the variable that says Path DO NOT DELETE THIS VARIABLE! Hit Edit and at the the end put:
;YOUR ANDROID SDK PATH\tools;YOUR ANDROID SDK PATH\platform-tools
Then hit OK.
ADB install tutorial is now finished
4)Now we want to add the correct drivers. There are a couple of ways to do this, this is the way I do it. Again right click on My Computer, and click properties. Now in the top left corner is Device Manager click on this. Now find where it says Kindle and right click it. Click the drivers tab and then Update Drivers and then browse my computer for driver software. Then click, let me choose from a list on my computer and click adb interface, and then either a ADB Testing Interface, or fastboot Interface, both work for what we are doing.
5) The next thing you want is a kernel so download and put in the \platform-tools folder.
IntersectRaven's: http://forum.xda-developers.com/showthread.php?t=1382999
DoomLord's: http://forum.xda-developers.com/showthread.php?t=1372625
6) Plug your Kindle Fire into your computer
7) Open a CMD window. Hit start and run CMD.exe or search for CMD. Then type into cmd:
adb shell
idme bootmode 4002
reboot
8) Open another CMD and type cd YOUR ANDROID SDK PATH \platform-tools. Then type:
fastboot boot NAME OF KERNEL.img
9) Now your Kindle will reboot, make sure it boots! Now that you have verified that it works we are ready to flash it.
10) Shutdown your Kindle Fire.
11) Use your old CMD with fastboot, and type:
fastboot flash boot NAME OF KERNEL.img
12) It will probably get stuck in booting at this point. With the fastboot CMD type:
fastboot oem idme bootmode 4000
it will say waiting for device, do not close this CMD!
13) Now hold down the power button until your device turns off. Then turn it on again, and the command will register.
14) Let your Kindle Fire boot and enjoy your new kernel!
If this doesn't work please leave a comment, or if I forgot anything, I am kind of tired while writing this. I may add pictures later. Thanks!

All this does is boots the custom kernel a single time (which you MUST do to test it). You still need to flash it.
Sent from my Gingervolt-ed VS910 4G using xda premium

Sorry, I will add the rest soon, slipped my tired mind.

do we really need the whole android and java sdk ?
the only commands used is adb and fastboot.
woud'nt the tools directory of KFU be enough since it contains the necessary commands ?
furthermore the driver installation is a essential part for correct operation of adb and fastboot
and don't forget so say your how-to is for windows

I haven't looked at the KFU much yet, so I don't know. I added that it is for windows and removed the java sdk. And added how to flash the kernel.

Accessory mode suppot
Are any Fire kernels available that support Accessory Mode aka ADK.
The changes that need to be made to the kernel are available from Google. They are in the main 3.x kernel source tree and in the samsung source tree of the 2.6.35 kernel.

[Q] ADB Can't Read Sideload

So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?

UpsideDownAce said:
So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?
Click to expand...
Click to collapse
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...

uncleswoop said:
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...
Click to expand...
Click to collapse
Just to be sure, you've apply sideload from adb in the recovery, correct?

ducatic said:
Just to be sure, you've apply sideload from adb in the recovery, correct?
Click to expand...
Click to collapse
I'm in the same boat! I tried, today, several times to sideload the update but I'm constantly getting the cannot read sideload error message. I guess I'm off to other sites to see what the fix is.

I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]

YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
adb sideload 094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
Click to expand...
Click to collapse
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:

I might be just an idiot but why are you guys trying to SideLoad a system update?
AFAIK... sideload is merely to install apps into your rom that Jellybean or the Playstore doesn't like.
I think you guys want to use "ADB Fastboot" commands instead. Get a guide before you attempt to do this though. I used Wugs Toolkit to install the bootloader from 4.2.2 update.

fede01_8 said:
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
Click to expand...
Click to collapse
:laugh: true
For clarity:
- adb sideload can used for installing zip updates from PC, as an alternative for using the ROM/recovery manager on your tablet/phone.
Code:
adb sideload update.zip
- fastboot flash is used for installing img files to a specific partition (boot, recovery, system)
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img

fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
Thank you!!! Spending hours trying to figure it out, so simple. Although not sure why the toolkit didn't work, but using CMD did work.

fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
fede01_8 said:
YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:
Click to expand...
Click to collapse
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:

teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.

brandnewyc said:
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.
Click to expand...
Click to collapse
This is what got me on the right trail. I opened the command prompt, navigated to the correct folder, used the sideload command and copied the name of the update file into the command prompt window, but it wasn't until I appended it with the .zip extension that it finally worked.:victory:

Hey guys! I don't have the sideload problem anymore, but, I get this error. cannot read '(name of file).zip'

I am either really dumb or this isn't working! I have it connected to adb device number and all working fine. I have the zip in platforms-tools cmd window opened etc. when i go to adb sideload and then top of cmd window edit paste the name of the file add .zip and it says can not read file!
Please help!!

Same problem...fixed
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~

jihoon526 said:
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~
Click to expand...
Click to collapse
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!

Fix
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.

hkleiner said:
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.
Click to expand...
Click to collapse
are you on the same directory as your file?

teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
Try addind ".zip" at the end of the file name in CMD. So if the name in the directory is ROM, type into cmd "adb sideload ROM.zip"

DigitalOSH said:
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!
Click to expand...
Click to collapse
oddly this helped me a lot with another device. i was having the exact same problem and found this topic in searching for a solution. but after removing the extension, renaming, then renaming and re-adding the extension it worked. i also had to type adb sideload fielanme.zip.zip to get it working.

[Win, Mac, Linx] Simple-ADB

This is simply ADB/Fastboot, with a Graphical User Interface.
Click to expand...
Click to collapse
HOW-TO
• Installation
make sure you have java installed on your PC
• first you have to install adb system-wide:
[windows] : try ADB Installer tool.
[Linux] : adb support comes with most Linux distributions.
• then run Simple-ADB.jar and that's it!
[Windows shortcut]
[Linux shortcut]
Click to expand...
Click to collapse
• Usage
• select from "ADB", "Fastboot" or "Your command" modes:
- if "ADB" is selected the dropdown will contain lots of adb commands :
adb devices -l
adb connect <host>
adb disconnect
adb usb
adb logcat
adb install
adb uninstall
adb push
adb pull
adb kill-all
adb shell top
adb shell free
adb shell ps,
adb shell netstat,
adb shell pm list packages,
busybox df -h
rm /data/system/gesture.key
adb reboot
adb reboot recovery
adb reboot download
adb reboot bootloader
adb reboot fastboot
adb reboot sideload
adb help
adb kill-server
- if "Fastboot" is selected the dropdown will contain lots of Fastboot commands :
fastboot devices -l
fastboot reboot-bootloader
fastboot erase system
fastboot erase data
fastboot erase cache
fastboot flash
fastboot flash recovery
fastboot flash boot
fastboot flash system
fastboot flash data
fastboot flash cache
fastboot flash userdata
fastboot flash bootloader
fastboot flash radio
fastboot help
- if "Your command" is selected the dropdown will be disabled , and you can write your own command.
• You can Save output from the Options menu or simply press Ctrl+S.
Click to expand...
Click to collapse
COMPATIBILITY
• Windows
• Linux (Thanks a lot for @topnomi for testing and confirming Linux support, follow his Instructions for linux).
• Mac OS (read this post for details)
TO-DO/FIX
• fix memory leak because of large output to the JTextArea [(e.g during adb logcat).
• support for Mac (I really don't know why it's not working there, contributions are always welcome!)
Code:
*** Disclaimer
there are some commands I've never tested (like password command),
please use the tool at your own risk.
If you want to support the development of this program, feel free to donate.
Click to expand...
Click to collapse
XDA:DevDB Information
S-ADB, Tool/Utility for all devices (see above for details)
Contributors
mhashim6
Source Code:
GitHub
Source-Forge
This tool is based on System Command Executor Library
Version Information
Status: Stable
Current Stable Version: update6
Stable Release Date: 2018-02-03
Created 2016-07-12
Last Updated 2020-06-15
XDA:DevDB Information
S-ADB, Tool/Utility for all devices (see above for details)
Contributors
Mohamed Hashem
Source Code: https://github.com/mhashim6/Simple-ADB
Version Information
Status: Stable
Current Stable Version: update6
Stable Release Date: 2018-02-03
Created 2016-07-12
Last Updated 2020-06-14

CHANGELOG
update6 [stable] [16/09/2017]
Code:
• fixed the memory leak that occurred when a command with a large output is being executed, finally!
• support for using quotes in commands.
• fixed a bug in adb push command.
• updated with latest version of System Command Executor library.
.
update5 [stable] [16/09/2017]
Code:
• fixed the memory leak that occurred when a command with a large output is being executed, finally!
• fixed a freeze in some special cases.
• fixed the weird layout issue on linux.
• replaced the "output contains errors" prompt with a more informative text, including the exit code.
• update to the last version of System-Command-Executer library.
• updated donate url.
• overall performance improvements
• reduced jar size to 44 kbs
.
update4 [stable] [07/05/2017]
Code:
•I quote google: "several bug fixes, and speedy improvements".
•fixed a bug in adb pull command.
•errors are highlighted in red.
•added:
adb shell ip,
adb shell ps,
adb shell netstat,
adb shell pm list packages,
adb usb
version 5.6 [stable] [31/07/2016]
Code:
•Stability, stability, stability, all possible weak spots are fixed, with lots of enhancements , this program is now stable (Hopefully)
•Saving output now is through File dialog
•Shortcuts added for options menu items
•lots of fixes to "your own command" mode + (you can execute by hitting enter)
Version 5.5 [27/07/2016]
Code:
now it's open-source; check the op.
in supported commands:
•added:
adb connect [to connect the phone wirelessly]
adb disconnect
adb root
adb unroot
adb reboot sideload
fastboot reboot-bootloader
•renamed:
adb > adb help
fastboot > fastboot help
in UI :
•enhanced all UI colors.
Version 5.2 [21/07/2106] :
Code:
in compatiblity with Linux and Mac :
•Confirmed for Linux
need a confirmation from you for OsX.
in UI :
•new icon
•the whole UI (including file explorer and information panels) now is totally revamped to Windows Look and feel, now You can say it's beautiful.
•now every mode (adb, fastboot, your own command) has it's output color.
in Errors and Exception:
•now all exceptions are more detailed, to guide you and me to the problem.
in supported commands
•renamed all commands in the list to what they really are to avoid confusion and complexity.
•added :
adb
adb kill-server
fastboot
•changed :
adb devices to adb devices -l
fastboot devices to fastboot devices -l
•removed :
unlock password 2nd method to avoid confusion and complexity.
in output :
•you can save the output using "save output" in "options" menu.
•fixed some output issues.
in code :
•I've changed some algorithms > hmmm, the app size now is 30 kbs lol.
900 downloads
Version 5.0 [initial release] [12/07/2016] :
Code:
the tool now is much more stable and smart, renamed to SADB [Simple ADB]
in how the tool is working:
as I said I've rewrittten the whole code:
•now we have an output area, no files or any leftover data files at all, it's just the tool
•now the tool is executing the commands in really different and cleaner/faster way
•added the Abort button, to abort currently running operations
•added "Your own command" mode [experimental]
•the tool size is 27 kbs
in Errors and Exception:
•all exceptions and errors are caught and handled i believe
•the tool now can determine whatever the output is an error or not
in UI :
•now you can choose from adb, fastboot by radio buttons, instead of this large comboBox
•removed most of the annoying dialog panes
•the overall UI is certainly better and smoother
2800 downloads
Code:
In the future, I might make other changes and fixes,
but they may not be that big to include in separate updates,
so, if you're interested in the latest releases,
feel free to compile the code yourself.

In Debian, there are "android tools" packages and adb and fastboot are simply there. Otherwise, the executable may come with any of Android API packages.
So this runs on Linux. Install adb does nothing. Own command has no command input to use. Need a on-phone file-browser for file to pull. Need option to save logcat to a file. Small things.
I run adb CLI without much ado.

Dovidhalevi said:
In Debian, there are "android tools" packages and adb is simply there. Otherwise, the executable may come with any of Android API packages.
Click to expand...
Click to collapse
Thanks for the help, I'll check.
Edit: own command, intended to allow users to write their command in the same red area, But I'll check, and yes save logcat into file is coming.

Mohamed Hashem said:
ANNOUNCEMENT:
one year & half ago I've created this tool, the main idea was not new, it has been implemented so many times, but I believe that majority of implementations has just covered the most basic and direct commands of ADB/Fastboot,
So, this revive shall FIX WHATEVER PROBLEM YOU FACED WITH THE OLD TOOL. make sure to check the changelog [2nd post].
INSTALLATION :
(make sure you have java installed on your PC)
• first you have to install ADB Installer tool, it will install ADB to your System directly, so no need for any additional files (make sure to give @Snoop05 a Thanks :good .
• then run Simple ADB.jar and that's it!
GUIDE :
• select from "ADB", "Fastboot" or "Your own command" buttons :
- if "ADB" is selected the combobox will contain lots of adb commands :
Check if Device connected properly (adb devices).
Android Logcat.
Install a specific APK file(Android Application).
Uninstall apk <package> .
pull a file from your Android Device to your PC.
push a file from your PC to your Android Device.
View tasks running in your Android device.
Check your Android Device Memory usage.
Check your Android Device storage usage.
Kill all background processes.
Normal Reboot.
Reboot to recovery mode
Reboot to download mode (for Samsung Devices).
Reboot to bootloader mode.
Unlock Patterns/passwords [first method]
Unlock Patterns/passwords [formatting phone method]
- if "Fastboot" is selected the combobox will contain lots of Fastboot commands :
Reboot to Fastboot mode.
Flash Update.zip.
Flash recovery.img.
Flash boot.img.
Wipe (System,data & cache) before restoring nandroid backup.
Flash system.img.
Flash data.img.
Flash cache.img.
- if "Your own command" is selected the combobox will be disabled , and you can write your (still one line) command in the red area.
• Hit Activate to (well, activate the command :cyclops: ).
• Hit Abort to stop the currently running operation ( please think twice before aborting a command).
• You have the Options menu that contains :
-Donate : to support my development and studying (first year college :cyclops: )
- Main thread : to visit this thread.
- ADB Installer : to visit ADB Installer thread.
- Reset : to set the frame as you first opened it.
COMPATIBILITY:
windows (till now)
•the first issue preventing it from being compatible with other OS's is that the way java is executing commands, it's tricky to keep the same simple functionality with the mass compatibility, so i'm still working on that.
•also in other OS's you need to install adb system-wide, and i didn't find any adb-installer-like tool for Linux or Mac os.
I hope i'll get help from the community
Code:
*** Disclaimer
there are some commands I've never tested (like password commands),
because I don't have a spare phone to test on, please use the tool at your own risk.
! note: if you want to support the development of this program, it would be appreciated to click
under my avatar, and Click
:good:
XDA:DevDB Information
SADB, Tool/Utility for all devices (see above for details)
Contributors
Mohamed Hashem
Version Information
Status: Beta
Current Beta Version: 5.0
Beta Release Date: 2016-07-13
Created 2016-07-12
Last Updated 2016-07-12
Click to expand...
Click to collapse
This seems like a really nice tool to users new to ADB, nice work man!

FYI, there is an Ubuntu package called android-tools-adb that includes ADB & Fastboot.
It also appears to be in Debian repositories, so it likely works with all Debian derivatives.
I'd be happy to help test your linux based tool if/when you get to that point.
I'm no programmer, but i've been running all linux at home for a couple years, so I might have some good ideas :highfive:

topnomi said:
FYI, there is an Ubuntu package called android-tools-adb that includes ADB & Fastboot.
It also appears to be in Debian repositories, so it likely works with all Debian derivatives.
I'd be happy to help test your linux based tool if/when you get to that point.
I'm no programmer, but i've been running all linux at home for a couple years, so I might have some good ideas :highfive:
Click to expand...
Click to collapse
thanks, that would be great help for sure.

Just ran it in Ubuntu 14.04 with:
Code:
java -jar Simple_ADB.jar
Please change "adb devices" to "adb devices -l" (lowercase L). Longer output with board name.

ranf said:
Just ran it in Ubuntu 14.04 with:
Code:
java -jar Simple_ADB.jar
Please change "adb devices" to "adb devices -l" (lowercase L).
Click to expand...
Click to collapse
Does everything work fine? Thanks for testing!

I only tried adb devices and logcat so far. -l is just a feature request.
More features I miss
Code:
fastboot devices -l
fastboot reboot

ranf said:
Just ran it in Ubuntu 14.04 with:
Code:
java -jar Simple_ADB.jar
ranf said:
I only tried ad devices and logcat so far. -l is just a feature request.
Click to expand...
Click to collapse
@ranf fastboot reboot does exists: reboot to fastboot mode
Thanks, I'll change it, and thanks for testing, feel free to test other commands
topnomi said:
FYI, there is an Ubuntu package called android-tools-adb that includes ADB & Fastboot.
It also appears to be in Debian repositories, so it likely works with all Debian derivatives.
I'd be happy to help test your linux based tool if/when you get to that point.
I'm no programmer, but i've been running all linux at home for a couple years, so I might have some good ideas :highfive:
Click to expand...
Click to collapse
What about starting now, it would be helpful if you tested it now, it seems working, although I don't really know (why) lol
Click to expand...
Click to collapse

Mohamed Hashem said:
@ranf fastboot reboot does exists: reboot to fastboot mode
Click to expand...
Click to collapse
fastboot knows 2 reboots:
- reboot reboot device normally
- reboot-bootloader reboot device into bootloader

ranf said:
fastboot knows 2 reboots:
- reboot reboot device normally
- reboot-bootloader reboot device into bootloader
Click to expand...
Click to collapse
Oh I see, it's found under adb commands as reboot to bootloader, maybe I'll move it to fastboot to avoid confusion.

Great! I love it.
Will you add more commands?

Newyork! said:
Great! I love it.
Will you add more commands?
Click to expand...
Click to collapse
I'm open for suggestions
Also, that's why I've implemented "Your own command" option.

@Mohamed Hashem i belive i can tweak the UI to get close to the window's metro ui which is attractive, stunning and simple if you make it's source open. It's already a good program. And with some furnishings on the UI, it can be the de facto adb for a few years. What say?

iamsubhranil said:
@Mohamed Hashem i belive i can tweak the UI to get close to the window's metro ui which is attractive, stunning and simple if you make it's source open. It's already a good program. And with some furnishings on the UI, it can be the de facto adb for a few years. What say?
Click to expand...
Click to collapse
well, after seeing the initial poll answers, I think I'm taking the Open-source option seriously so whenever I publish it, You're free to do so
Also, I'm about to take a look at JavaFx to polish the ui, thus, We will have multiple good user interfaces, and this is definitely always better

Mohamed Hashem said:
well, after seeing the initial poll answers, I think I'm taking the Open-source option seriously so whenever I publish it, You're free to do so
Also, I'm about to learn javaFx to polish the ui, thus, We will have multiple good user interfaces, and this is definitely always better
Click to expand...
Click to collapse
I know about JavaFX and CSS stuff quite well from my self learning of 1 and a half years. I have some good metro like stylesheets ready to go with built in accent and base theme changing support. I look forward to the aforementioned happening.

Dovidhalevi said:
...
So this runs on Linux. Install adb does nothing. Own command has no command input to use. Need a on-phone file-browser for file to pull. Need option to save logcat to a file. Small things..
Click to expand...
Click to collapse
I indeed ran it under linux, usual java -jar ....was able to exercise adb commands as I describe.
Will always get io-exceptions when hitting abort.
Other exceptions may be due to the Process.start()
Mohamed Hashem said:
Till now I've been using java's regular Process.start() method, It's for Windows only,
Thanks for the help, I'll check.
Edit: own command, intended to allow users to write their command in the same red area, But I'll check, and yes save logcat into file is coming.
Click to expand...
Click to collapse
Great!
topnomi said:
FYI, there is an Ubuntu package called android-tools-adb that includes ADB & Fastboot.
It also appears to be in Debian repositories, so it likely works with all Debian derivatives.
I'd be happy to help test your linux based tool if/when you get to that point.
I'm no programmer, but i've been running all linux at home for a couple years, so I might have some good ideas :highfive:
Click to expand...
Click to collapse
You can run it right now as described!

Dovidhalevi said:
I indeed ran it under linux, usual java -jar ....was able to exercise adb commands as I describe.
Will always get io-exceptions when hitting abort.
Other exceptions may be due to the Process.start()
Actually I think that IOExeption comes from start()
did you face other exceptions?
Besides Abort, does executing commands actually work?
You can run it right now as described!
Click to expand...
Click to collapse
The described solves the second problem (adb installation) but the second problem still needs testing\investigation
Thanks for testing and information