Related
Hey everyone , so I installed Android SDK on my Ubuntu 9.10 machine, the IDE works fine, my problem arises when I want to send commands to the phone using the fastboot command in the terminal. I get command not found error.
I followed both of these procedures:
http://forum.xda-developers.com/showthread.php?t=537508
http://wiki.cyanogenmod.com/index.php/Fastboot
any help would be greatly appreciated.
try this out......(link)
Follow this its better . Just got passed to me I think its cool. Try it out.
http://dennis.christilaw.com/?p=135
blackerwater said:
Follow this its better . Just got passed to me I think its cool. Try it out.
http://dennis.christilaw.com/?p=135
Click to expand...
Click to collapse
well i did try it , and still nothing it still says adb:command not found , fastboot: command not found
i don't know how good your linux skills are. but you might need to
Code:
chmod +x adp
, then you can run it from it's dir with
Code:
./adb
or you can ln or cp it to your bin dir. for fastboot the same applies (mutatis mutandis).
you might have to use sudo, too.
hope that helps
tried that too
Ubuntu still doesnt recognize it
i should tell you im trying to run it from the terminal window.
pk198105 said:
tried that too
Ubuntu still doesnt recognize it
i should tell you im trying to run it from the terminal window.
Click to expand...
Click to collapse
do this:for jaunty/karmic..
step 1
sudo touch /etc/udev/rules.d/51-android.rules
step 2
sudo gedit /etc/udev/rules.d/51-android.rules
#and add this line and save/close:
SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
step 3 (modified permission)
sudo chmod a+rx /etc/udev/rules.d/51-android.rules
step 4( testing device)
./adb devices
step 5 (if works say thanks!))
note: some linux terminal accept ./adb devices or adb devices
Also before that you might want to check and see if the device ids show up when you plug the phone in. Might be something else with your device or rom your running......good luck.
pk198105 said:
Hey everyone , so I installed Android SDK on my Ubuntu 9.10 machine, the IDE works fine, my problem arises when I want to send commands to the phone using the fastboot command in the terminal. I get command not found error.
I followed both of these procedures:
http://forum.xda-developers.com/showthread.php?t=537508
http://wiki.cyanogenmod.com/index.php/Fastboot
any help would be greatly appreciated.
Click to expand...
Click to collapse
These are the best instructions I've found for setting up the Android SDK on Ubuntu:
http://www.futuredesktop.org/developing_android_apps_on_ubuntu.html
The bit you need to get right it setting up the "udev" policy file. The permissions you set here allow you to access the phone from Ubuntu's point of view.
Also....Do you know that to run a program FROM ITS FOLDER from the command prompt in Linux you need to put "./" in front of it? This is telling to look in the current folder for the program to execute it. But you have to be in that folder.
So you would go to [sdk-folder]\tools and type in (you may have to use 'sudo') "sudo ./fastboot devices" and it should list any attached phones that have USB debug turned on in the phone settings (you do have it turned on, right?)
You should see something like (from my phone):
[email protected]:~/android-sdk-linux/tools$ sudo ./fastboot devices
HT95SKF07937 fastboot
If you see this, then you can move to booting a recovery on your phone. If fastboot doesn't list any devices, then your udev probably isn't set up right.
Here is an extract. This works *every* time. The lines below mean you must use sudo to run fastboot or adb....and to start the adb server ("sudo ./adb start-server"). Butif you add GROUP="plugdev" to the end of each line and also add your username to the group "plugdev" (via SYSTEM -> Administration -> Users and Groups), then you don't need to use sudo.
*****
10d) In Ubuntu, create a new rules file for these vendor:device IDs.
Type this command to create the file.
$ sudo gedit /etc/udev/rules.d/51-android.rules
Add the following blue lines (rules) to it and save the file. If your lsusb command reports other, newer product IDs for vendor 0bb4, add them also to the file.
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c01", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c02", MODE="0666"
--
10e) Re-connect your phone.
Your phone should be detected if you unplug and reconnect it to the computer.
*****
List devices again and you should be fine.
If you're reading and understanding the instructions, it should work. If you're skipping the bits you don't understand.....then go back and understand them. No other way. I'm assuming here that your phone is able to handle fastboot. If you see the three dancing androids, it most likely can.
Try this write up by Google. Hope this one helps. If not then ill do an easy step by step. ....good luck. You know now that I think about it its easy doing it on windows witch doesn't make since it should be easier on a unix box for crap sakes!
http://www.google.com/gwt/n?u=http://developer.android.com/sdk/eclipse-adt.html
finally got it to work. It seems I was missing a file from the Android SDK. Everything is running smoothly, thank you all for your help.
Unfortunately it didnt say which file was missing..
pk198105 said:
finally got it to work. It seems I was missing a file from the Android SDK. Everything is running smoothly, thank you all for your help.
Unfortunately it didnt say which file was missing..
Click to expand...
Click to collapse
try using the sdk manager to update your sdk...see if that gets you the missing file...
-BMFC
i can't get fastboot to work. i placed it in the tools folder. if i enter "fastboot" in a terminal, i get the command line options. "fastboot devices" does not work, though adb and the android sdk are running fine. i'm able to make screenshots, but i'm not able to explore the phone or use fastboot. ideas?
when it says "adb: command not found" it usually isn't in your .bashrc path, or if you did put it in possibly you didn't log out/log back in or restart your computer.
PATH=”$HOME/bin:$PATH:/home/{USERNAME}/android-sdk-linux_86:/home/{USERNAME}/android-sdk-linux_86/tools"
glad you got it working though
could you help me, too?
if i enter fastboot in my terminal i get all the options:
Code:
[email protected]:~$ fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
so the program is working, executable and in my path.
adb does work, as well as the sdk.
i can connect to my phone via ddms and adb, but not via fastboot. it does not find anything....
I have a tip for everyone who use adb and fastboot in linux.
In most of the tutorials i see that you have go to exac folder to use them, but there is quite simple think you can do to use them from anywhere in your consol. All you have to do is
1. go in consol to the folder where you have adb and fastboot
2. then give command
Code:
sudo nautilus
or
Code:
su
nautilus
This should open a window with root permissions
3. in this windows you need to create shourtcats for adb and fastboot by right click mouse menu.
4. Next you need to cut shourtcats you created and place in folder /bin (you need to do this in the same window beacose you need to have root permissions to paste anything there.
5. And last think you need to do when you paste them it`s change there name`s for adb and fastboot.
Now you can use this commands without "./" and firstly you do not need to go to the folder where they realy are.
Now let say you have an system.img in /home/user/data you can now flash your phone in this way
Code:
su
cd /home/user/data
fastboot flash system system.img
or
Code:
su
fastboot flash system /home/user/data/system.img
su gives root permitions
Now i want to apologize for my english
If any one want to add this to his tutorial please give link for this thread or just write it`s made by me
abrams89 said:
I have a tip for everyone who use adb and fastboot in linux.
In most of the tutorials i see that you have go to exac folder to use them, but there is quite simple think you can do to use them from anywhere in your consol. All you have to do is
1. go in consol to the folder where you have adb and fastboot
2. then give command
Code:
sudo nautilus
or
Code:
su
nautilus
This should open a window with root permissions
3. in this windows you need to create shourtcats for adb and fastboot by right click mouse menu.
4. Next you need to cut shourtcats you created and place in folder /bin (you need to do this in the same window beacose you need to have root permissions to paste anything there.
5. And last think you need to do when you paste them it`s change there name`s for adb and fastboot.
Now you can use this commands without "./" and firstly you do not need to go to the folder where they realy are.
Now let say you have an system.img in /home/user/data you can now flash your phone in this way
Code:
su
cd /home/user/data
fastboot flash system system.img
or
Code:
su
fastboot flash system /home/user/data/system.img
su gives root permitions
Now i want to apologize for my english
If any one want to add this to his tutorial please give link for this thread or just write it`s made by me
Click to expand...
Click to collapse
Sometimes SU alone wont switch to the root user in some distributions (eg. Ubuntu Variants) If you want to switch to root, type sudo su or type "sudo <name of program>" and it will run that program as root.
Jack
Hello all,
I haven't really seen any options for restoring our Nexus 7's using Linux and terminal commands....
SO I made one!
This guide is the simplest I could make it and it only uses a few commands to get your Nexus 7 back up and running in the event of a brick or loss of data.
AS long as you have access to the Bootloader option of the device, this tool should work.
INSTRUCTIONS
1.Make sure that you have ADB and Fastboot installed
Open Terminal (CTRL+ALT+T)
Just type what's in the quotation marks, do not include the marks
Type "sudo apt-get update"
Type "sudo apt-get install android-tools-adb android-tools-fastboot"
2. While in Terminal, browse to location of downloaded files (boot.img , system.img)
ex. Type something like "cd ~/Downloads/NexusRestore"
3. Connect your Nexus 7 to your computer with USB cable and make sure that the device is in bootloader mode
HINT: type "fastboot devices" and it should show a set of random characters and then the word "Fastboot" to the right
4. Type these commands to restore your device to a stock rooted Jellybean ROM
fastboot devices
fastboot flash system system.img
fastboot flash recovery recovery.img (ONLY use this if you DO NOT want to kep your original recovery or if you lost it due to your situation)
fastboot flash boot boot.img
fastboot -w
fastboot reboot
5. Profit
You may now go back to recovery and flash the ROM of your choice or do whatever your heart desires
DOWNLOADS
Dev-Host: http://d-h.st/KaZ
Extract the ZIP file and work from that directory.
Happy Restoring!! Let me know if you have any questions or need more Help :laugh:
Not to be nit picky but the instructions you gave are for Debian based distros (most likely Ubuntu/Mint- since android-tools are a backport in Debian Wheezy), IMHO it would be better to specify that this is a Ubuntu/Mint (Debian) Guide, since other distros use different package managers.
Once you have android tools installed there is an easier method.
Download factory image, extract the tar archive, run flash-all.sh
(optionally edit flash-all and remove the -w switch to preserve user data)
oldsoldier2003 said:
Not to be nit picky but the instructions you gave are for Debian based distros (most likely Ubuntu/Mint- since android-tools are a backport in Debian Wheezy), IMHO it would be better to specify that this is a Ubuntu/Mint (Debian) Guide, since other distros use different package managers.
Once you have android tools installed there is an easier method.
Download factory image, extract the tar archive, run flash-all.sh
(optionally edit flash-all and remove the -w switch to preserve user data)
Click to expand...
Click to collapse
I appreciate the info, I've only ever used Ubuntu Linux and every method that I had found so far was super in depth and not exactly simple. I've been doing this stuff for a while, so it's no big deal for me, but I wanted to provide something for people who don't do this kind of stuff every day. Just trying to contribute to the "cause" i guess. lol
Good tutorial
Help
Zesty01 said:
Hello all,
I haven't really seen any options for restoring our Nexus 7's using Linux and terminal commands....
SO I made one!
This guide is the simplest I could make it and it only uses a few commands to get your Nexus 7 back up and running in the event of a brick or loss of data.
AS long as you have access to the Bootloader option of the device, this tool should work.
INSTRUCTIONS
1.Make sure that you have ADB and Fastboot installed
Open Terminal (CTRL+ALT+T)
Just type what's in the quotation marks, do not include the marks
Type "sudo apt-get update"
Type "sudo apt-get install android-tools-adb android-tools-fastboot"
2. While in Terminal, browse to location of downloaded files (boot.img , system.img)
ex. Type something like "cd ~/Downloads/NexusRestore"
3. Connect your Nexus 7 to your computer with USB cable and make sure that the device is in bootloader mode
HINT: type "fastboot devices" and it should show a set of random characters and then the word "Fastboot" to the right
4. Type these commands to restore your device to a stock rooted Jellybean ROM
fastboot devices
fastboot flash system system.img
fastboot flash recovery recovery.img (ONLY use this if you DO NOT want to kep your original recovery or if you lost it due to your situation)
fastboot flash boot boot.img
fastboot -w
fastboot reboot
5. Profit
You may now go back to recovery and flash the ROM of your choice or do whatever your heart desires
DOWNLOADS
Dev-Host: http://d-h.st/KaZ
Extract the ZIP file and work from that directory.
Happy Restoring!! Let me know if you have any questions or need more Help :laugh:
Click to expand...
Click to collapse
First link in "Dowload" is dead !
Thanks for this simple tuto !
In introduction of your thread, you can put this link : http://developer.android.com/tools/device.html
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
I'm a daily Linux user and don't have installed Windows on my PC.
So I would like to ask first how to backup my X720 phone into my Linux PC? Then install root and new custom rom using the same OS?
Before I had Samsung phone and was using application called Heimdall in Linux, similar like Odin for Windows.
Is there any similar app for Le Eco or can I use commands in Terminal?
https://www.xda-developers.com/install-adb-windows-macos-linux/
https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Follow the links above, all you really need is adb. There are some Chinese Windows recovery programs and scripts for certain variants of the Pro3 (like the x722 and the x720) but you probably won't need to use them unless you catastrophically brick the phone somehow. As long as you're following instructions from ROM threads properly, all you'll ever need is adb and the rest you can do through your phone via TWRP or Magisk or whatever.
Well there is one additional hangup...the phone will not appear in "adb devices" at least on Linux Mint/ubuntu...the solution is as follows.
sudo apt-get install android-tools-adb android-tools-fastboot
tar -jxvf lepro3.tar.gz
cp abd_usb.ini /home/<your username>/.android
sudo cp 51-android.rules /etc/udev/rules.d
sudo killall adb
sudo adb devices
Basically you are manually adding the vendor id so adb can find it. Plan on having to use sudo in front of any adb or fastboot commands to avoid possible errors.
It should then find the device and you can follow a tutorial like the one here: https://docs.google.com/document/d/1qFJ7ULjU57XSkm-j8P9vDbnV1JU1YZYQS70StWRlrbo/edit?usp=sharing
I did not create this. It's a copy of the one created by Abel408 on slickdeals but I used it to take my factory phone and install omnirom about 5 days ago on linux.
famewolf said:
Well there is one additional hangup...the phone will not appear in "adb devices" at least on Linux Mint/ubuntu...the solution is as follows.
sudo apt-get install android-tools-adb android-tools-fastboot
tar -jxvf lepro3.tar.gz
cp abd_usb.ini /home/<your username>/.android
sudo cp 51-android.rules /etc/udev/rules.d
sudo killall adb
sudo adb devices
Basically you are manually adding the vendor id so adb can find it. Plan on having to use sudo in front of any adb or fastboot commands to avoid possible errors.
It should then find the device and you can follow a tutorial like the one here: https://docs.google.com/document/d/1qFJ7ULjU57XSkm-j8P9vDbnV1JU1YZYQS70StWRlrbo/edit?usp=sharing
I did not create this. It's a copy of the one created by Abel408 on slickdeals but I used it to take my factory phone and install omnirom about 5 days ago on linux.
Click to expand...
Click to collapse
Hello
I'm new in this community and me too, I have a LeEco Le Pro 3, never flashed, so it has the new updates of EUI 5.9s and all chinese apps.
I'd like to put this ROM
Me too, I'm a linux user, I've Ubuntu 16.04 LTS
Before I never flashed a phone, so I don't know how to do well even if I read a lot of procedures, but all for Win.
How do to the same with my OS?
I'd prefer to follow a complete list of instructions not to make errors and problems to my phone.
I've a LeEco Le Pro 3 (X720) original and never flashed, with 6GB of RAM, and 64GB of memory
Thanks to who wants to help me accurately
Hello,
no one could help me?
Is there no solution for Linux users? How is it possible?
spsturbo said:
Hello,
no one could help me?
Is there no solution for Linux users? How is it possible?
Click to expand...
Click to collapse
In short install ADB&fastboot tools, reboot to bootloader, unlock it via fastboot, flash TWRP, boot into TWRP, do a factory reset, flash your ROM, you're done
BlueFlame4 said:
In short install ADB&fastboot tools, reboot to bootloader, unlock it via fastboot, flash TWRP, boot into TWRP, do a factory reset, flash your ROM, you're done
Click to expand...
Click to collapse
And in more detailed manner?
Could you list the exact commands to type on the terminal?
spsturbo said:
And in more detailed manner?
Could you list the exact commands to type on the terminal?
Click to expand...
Click to collapse
Whoa, no offense but I don't have time for that. Just search for each of these things and you will find an answer. I will also answer specific questions but I don't like unspecific ones like "post the whole process please".
spsturbo said:
And in more detailed manner?
Could you list the exact commands to type on the terminal?
Click to expand...
Click to collapse
Just google it and you will find all that you need.
spsturbo said:
And in more detailed manner?
Could you list the exact commands to type on the terminal?
Click to expand...
Click to collapse
https://ubuntuforums.org/showthread.php?t=2326450
famewolf said:
Well there is one additional hangup...the phone will not appear in "adb devices" at least on Linux Mint/ubuntu...the solution is as follows.
sudo apt-get install android-tools-adb android-tools-fastboot
tar -jxvf lepro3.tar.gz
cp abd_usb.ini /home/<your username>/.android
sudo cp 51-android.rules /etc/udev/rules.d
sudo killall adb
sudo adb devices
Basically you are manually adding the vendor id so adb can find it. Plan on having to use sudo in front of any adb or fastboot commands to avoid possible errors.
It should then find the device and you can follow a tutorial like the one here: https://docs.google.com/document/d/1qFJ7ULjU57XSkm-j8P9vDbnV1JU1YZYQS70StWRlrbo/edit?usp=sharing
I did not create this. It's a copy of the one created by Abel408 on slickdeals but I used it to take my factory phone and install omnirom about 5 days ago on linux.
Click to expand...
Click to collapse
Thank you for your great help! I tried this but it still didn't recognized the device if you use the command "adb devices", instead you need to use "fastboot devices" and add to your file USB id for fastboot.
First you need to find your USB id number by running phone in fastboot mode and use command "lsusb" in terminal. Here are instructions: https://android.stackexchange.com/questions/144966/how-do-i-get-my-device-detected-by-adb-on-linux
Then put those number into your two files:
Put in "adb_usb.ini" your first ID number in my case
Code:
0x18d1
(Don't root directory /home/USERNAME/.android)
for opening file 51-android.rules in /etc/udev/rules.d you need to use root and put this inside:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d00d", MODE="0666", GROUP="plugdev", SYMLINK+="android"
In the end restart the udev service in terminal "service udev restart" and restart the ADB server: adb kill-server && adb start-server. Disconnect and reconnect the device again.
For recovery used this tutorial: https://forum.xda-developers.com/le-pro3/how-to/leeco-le-pro-3-root-t3476560
I was unable to get info from
Code:
fastboot oem device info
, but manage to unlock the bootloader:
Code:
fastboot oem unlock-go
and successfully installed Lineage 15.1 OS.