A lot of people seem scared to use "adb" (Android Debug Bridge), or try it out and hit problems, then immediately give up.
I personally think that the method of rooting using adb (rage) is "better" than Visionary, because you have more control over the process and can see what it's doing. e.g. if there's an error message then you can see that, and ask for help.
But even if you don't use adb in rooting, it's still a very useful tool to have available. You can use it to run commands on your phone, copy files between your PC and phone, and to debug various issues that may occur at some point (plus lots more).
The guide in this first posting is for Windows, since I think this is what the majority of what people are using, and also it's what I use myself. Though you can use adb on Linux or Mac too. There's a Mac guide in the second posting, with a Linux guide "coming soon".
There are different ways to install adb. Below I list two methods, the first method I call "Complete", which involves installing the Android SDK (Software Development Kit), and the second "Quick" way. Either should be fine for rooting etc.
There's also a guide by gtrab in his useful FAQ posting (thanks !) HERE , which involves a very quick way to get it up and running (scroll down to the "Adb Mini Package" section).
INSTALLING ADB ON WINDOWS - METHOD A, THE "COMPLETE" WAY, USING THE SDK
Step 1
If you haven't done so already, then download and install HTC Sync from HTC's website.
You'll find it in the Support section for the Desire Z (works on the G2 too), e.g. at http://www.htc.com/www/help/htc-desire-z/#download.
This is HTC's software to sync various stuff from your phone to your PC, such as email, bookmarks etc. However, even if you don't need that stuff, HTC Sync has a bunch of USB drivers for your phone, and that's what we *do* need.
Step 2
Download and install the Android SDK (Software Development Kit) Starter package from http://developer.android.com/sdk/index.html
There are two choices for Windows there, a simple zip file which you can unzip somewhere appropriate on your PC (e.g. put it on C:\ if you like). Or there's an installer (which is the recommended option according to the Android website), though that forces you to download some Java stuff which we don't really need for adb and takes a lot longer to install (but there won't be any harm in getting). It doesn't really matter which one you pick though.
You can read all about how to install the SDK at http://developer.android.com/sdk/installing.html . Ignore all the stuff about Eclipse though, you don't need that unless you're going to start writing Android apps.
Step 3
Now we need to add the Platform Tools component to the SDK, because that contains adb.
Run "SDK Manager" on your PC. You will find that in the root directory of the SDK, so you can open up a file explorer window to find that, then double-click on "SDK Manager" to run it.
Wait for a few seconds while it checks on the Android website for updates etc, let it then pop up with a window showing you what is on offer.
Add the "Android SDK Platform Tools", you can "reject" (i.e. don't install) all the other things it offers you if you like, though there's no harm in installing them (just takes up disk space on your PC).
Step 4
Now we need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)
Step 5
On your phone, go into Menu->Settings->Applications->Development and make sure you have the entry "USB Debugging" ticked. adb will not work without this.
Step 6
Plug your phone into your PC using the original HTC cable. This is important, do not use a third-party cable since it might not work with adb (even though it might seem fine with other communication with your phone). If this is the first time you've done it since installing HTC Sync, you might have to wait while it installs additional drivers.
Step 7
Fire up a command prompt on your computer, e.g. "Run" then "cmd", or pick the "Command prompt" option from the menus, and type in the following (obviously the C:\> bit is your actual PC's prompt, not what you type). To emphasise, you are running this on your PC, not directly from your phone (e.g. terminal emulator) :
Code:
C:\> adb devices
This should display something like the following :
Code:
List of devices attached
XXX12345 device
... where the "XXX12345" bit is actually your phone's serial number. If the list is blank and the phone is plugged in ok, go back to Step 5 and make sure USB Debugging is enabled. If you can see your phone, then you're in business, adb can see your phone and communicate with it, and you're ready to start using adb !
By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output.
INSTALLING ADB ON WINDOWS - METHOD B, THE "QUICK" WAY, NO SDK
Thanks to amroush_1800 for the input on this.
Step 1
If you haven't done so already, then download and install HTC Sync from HTC's website.
You'll find it in the Support section, e.g. at http://www.htc.com/uk/supportdownloadlist.aspx?p_id=325&act=sd&cat=all.
This is HTC's software to sync various stuff from your phone to your PC, such as email, bookmarks etc. However, even if you don't need that stuff, HTC Sync has a bunch of USB drivers for your phone, and that's what we *do* need.
Step 2
Download this zip archive and unzip it somewhere memorable on your PC (e.g. into a folder on your desktop) - http://dl-ssl.google.com/android/repository/platform-tools_r04-windows.zip
Step 3
On your phone, go into Menu->Settings->Applications->Development and make sure you have the entry "USB Debugging" ticked. adb will not work without this.
Step 4
Plug your phone into your PC using the original HTC cable. This is important, do not use a third-party cable since it might not work with adb (even though it might seem fine with other communication with your phone). If this is the first time you've done it since installing HTC Sync, you might have to wait while it installs additional drivers.
Step 5
Fire up a command prompt on your computer, e.g. "Run" then "cmd", or pick the "Command prompt" option from the menus.
Use the "cd" command to change to the folder that contains the adb.exe and other files that you unzipped in Step 2.
Then type in the following (obviously the C:\> bit is your actual PC's prompt, not what you type). To emphasise, you are running this on your PC, not directly from your phone (e.g. terminal emulator) :
Code:
C:\> adb devices
This should display something like the following :
Code:
List of devices attached
XXX12345 device
... where the "XXX12345" bit is actually your phone's serial number. If the list is blank and the phone is plugged in ok, go back to Step 3 and make sure USB Debugging is enabled. If you can see your phone, then you're in business, adb can see your phone and communicate with it, and you're ready to start using adb !
By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output.
INSTALLING ADB ON MAC
The following excellent guide kindly provided by siedkins, please thank him and not me !
What you will need:
A Mac
USB cable
Android SDK for OSX- http://developer.android.com/sdk/index.html
At the time of writing this the version was "android-sdk_r08-mac_86" so please have a look at the above link and let me know if you can't find that same version.
So download the zip file and I would extract it to a folder where you are happy to keep it such as within your user home folder i.e. Macintosh HD/Users/{Your User Name} and for my mac it is Users/siedkins which is how I have my OSX set up.
Then open then still in Finder, open "android-sdk-mac_86" then "tools".
Now launch Terminal - ⌘ + space then type Terminal or Applications>Utilities>Terminal
Now drag and drop the file called "android" in the "tools" folder into your terminal window and you should see something like:
/Users/siedkins/android-sdk-mac_86/tools/android
Then hit enter - this should load Android SDK
Next go to Available Packages on the left and Android Repository > Android SDK Platform-tools, revision 1 -tick the box and hit "Install Selected"
It should download and install the Platform Tools which includes ADB !!!!
Now quit Android SDK after it has downloaded and go back into Finder. Now you should see a new folder "platform-tools" in the "android-sdk-mac_86" folder. Open that and you can now see a file called adb.
Now .... I am going to show you how to make your life a lot easier in Terminal to run ADB without having to navigate to the folder every time you want to launch it.
Go back to your Terminal window and type (or copy & paste):
Code:
cd ~
The screen should then look like
NAME_OF_YOUR_MACHINE:~ USERNAME$
For me I have:
Mac-Pro:~ siedkins$
Next, type
Code:
touch .bash_profile
to create your new bash / path file
Next, type
Code:
open -e .bash_profile
to open it in TextEdit.
Now into Text Edit please copy:
Code:
export PATH=${PATH}:
Then go into Finder and navigate your your "android-sdk-mac_86" folder. Then click on the "platform-tools" folder and drag and drop this into TextEdit at the end of the code above that you copied. Mine looks like:
export PATH=${PATH}:/Users/siedkins/android-sdk-mac_86/platform-tools/
Yours should look like:
export PATH=${PATH}:insert your path to the "platform-tools" folder in your Android SDK here
All you need is that one line. Then Save and exit TextEdit and then very importantly QUIT TERMINAL.
Now ........ to turn on USB Debugging in your handset Settings > Applications > Development > USB Debugging - ticked and also go to Settings > Connect to PC > Default connection type > Charge Only and also UNTICK "Ask me ..." there also. You can always go back here and change these settings back.
Now plug in your phone to a USB port. I noticed that if I plugged my phone into one of the standard USB ports on the front of my machine I couldn't see the phone further down the line and if I plugged it into a powered USB port on the front (I have an "akasa AK-ICR-08" which has a powered connector behind the 5 USB ports. But you guys will probably be using a MacBook or MacPro and there shouldn't be any issues with the power to your USB ports.
Now to launch ADB - re-open terminal (remember that you had quit it - very important!) then type in:
Code:
adb devices
And you should see:
List of devices attached
HXXXXXXXXXX device
where XXXXXXXX is your unique phone ID.
Now you can run all of your favourite ADB commands straight by typing:
adb shell
etc straight into Terminal. I won't go into that here as there are plenty of guides about what to do with ADB once it's installed!
Now you have ADB setup on your Mac and can run it without the need for installing HTC Sync - un-installing it - loading some modified drivers over the top !!!!
It all just works !!!!!!
INSTALLING ADB ON LINUX
Coming soon ...
USING ADB
There's a comprehensive guide to using adb, including all its commands, at http://developer.android.com/guide/developing/tools/adb.html
Here are a few example commands :
Code:
C:> adb push hello.txt /data/local/tmp
The above copies the file hello.text from the current directory of your PC (i.e. the directory shown in the command prompt) into the /data/local/tmp directory on your phone.
Code:
C:\> adb pull /sdcard/error.log error.log
The above copies the file /sdcard/error.log onto your PC.
Code:
C:\> adb install Superuser.apk
The above installs the app in the Superuser.apk file in the current directory of your PC, onto your phone.
Code:
C:\> adb shell
The above starts a command prompt session on your phone. So when you see the $ prompt, that's your phone and commands you type there will be executed on your phone.
Code:
C:\> adb shell ls
The above runs the command "ls" on your phone and displays the results. So it's a way of issuing one command at a time, without starting your own shell session. You can subsitute other shell commands for the "ls".
Code:
C:\> adb reboot
The above reboots the phone.
Code:
C:\> adb reboot bootloader
The above reboots the phone into the bootloader (hboot).
Code:
C:\> adb reboot recovery
The above reboots the phone into recovery.
USING ADB FOR DIAGNOSTICS (logcat)
Coming soon ...
Thank god! Lol thanks for all your hard work.
Sent from my HTC Vision using XDA App
Get a "how to logcat" section added.
Nice work. Can we elect you to be a mod?
Sent from my HTC Vision using XDA App
ddotpatel said:
Get a "how to logcat" section added.
Click to expand...
Click to collapse
Thanks for the suggestion, will do
Nice dude. Just what I needed
Sent from my HTC Desire using XDA App
+1 mod vote!
Sent from my HTC Vision using XDA App
Nice guide mate. Let me know if you need any more posts or help in any way
steviewevie said:
Using adb
Using adb for logcat
adb logcat
Or
adb lolcat
Click to expand...
Click to collapse
Also update it for Mac / Linux users.
Mainly different adb files (I had adb and fastboot for Win/Mac/Lin uploaded somewhere, if you want?) and they go in /system/bin instead of PATH.
Otherwise, good idea + well done.
DanWilson said:
Also update it for Mac / Linux users.
Mainly different adb files (I had adb and fastboot for Win/Mac/Lin uploaded somewhere, if you want?) and they go in /system/bin instead of PATH.
Otherwise, good idea + well done.
Click to expand...
Click to collapse
Thanks. I need someone to help me come up with the different steps for Mac/Linux users please ? Then I can add those in.
steviewevie said:
Thanks. I need someone to help me come up with the different steps for Mac/Linux users please ? Then I can add those in.
Click to expand...
Click to collapse
I'll do that.
I'll also hunt down my Mediafire adb and fastboot files, because not everyone wants the whole SDK
I don't know if you need any drivers for the phone (like HTC Sync for Windows). Someone else will need to tell you, or you can wait till Christmas.
INSTALLING ADB
Step 0
Drivers perhaps? XD
Step 1
Download these files;
Mac - http://www.mediafire.com/?z8myxs9941kz3gg
Linux - http://www.mediafire.com/?m62rt943mroxm4s
Or you can download and install the Android SDK (Software Development Kit) Starter package from http://developer.android.com/sdk/index.html
You can read all about how to install the SDK at http://developer.android.com/sdk/installing.html . Ignore all the stuff about Eclipse though, you don't need that unless you're going to start writing Android apps.
Now, from version 8 (Android 2.3) of the SDK onwards, adb has been taken out of this starter package. If you downloaded version 7 (Android 2.2), then you've already got adb and you can skip Step 3 and go straight to Step 4 below. Otherwise you need to proceed to Step 3 to add adb to the SDK.
Step 2
Extract the files and rename "adb-linux" ("adb-mac") to "adb" and "fastboot-linux" ("fastboot-mac") to "fastboot"
You could call it anything you like, like "cheese" and "bread", but that makes things difficult.
Step 3
Mac - Copy the files to the folder /bin
You will need to unhide the folder. Google it.
Linux - Copy the files to /system/bin *OR* /bin
I have not used Linux for ages so my folders are rotting away. I believe you will need root access to do this, I used Kongregate (I think) as an app to control my root copying needs.
Step 4
On your phone, go into Menu->Settings->Applications->Development and make sure you have the entry "USB Debugging" ticked. adb will not work without this.
Step 5
Plug your phone into your PC using the original HTC cable. This is important, do not use a third-party cable since it might not work with adb (even though it might seem fine with other communication with your phone). Or whatever.
Step 6
Open a Terminal window. On your PC/Mac. To emphasise, you are running this on your PC, not directly from your phone (e.g. terminal emulator) :
The part were it says "Dan-Wilsons-MacBook:~ danwilson$" will probably not be on your PC/Mac, unless you are called Dan Wilson, and have a MacBook.
Code:
Dan-Wilsons-MacBook:~ danwilson$ adb devices
This should display something like the following :
Code:
List of devices attached
XXX12345 device
... where the "XXX12345" bit is actually your phone's serial number. If the list is blank and the phone is plugged in ok, go back to Step 6 and make sure USB Debugging is enabled. If you can see your phone, YOU WIN A CHEESECAKE!
If you decided to be awkward and call "adb-linux" ("adb-mac") "cheese", replace the word "adb" in command lists (like the above) to "cheese". It looks cool but complicates things.
Example;
Code:
Dan-Wilsons-MacBook:~ danwilson$ cheese devices
-------------
I think this looks OK. Some bits are weird and I don't know about drivers, but still, better than nothing. It is rough, but I've not done it in ages. Sorry bout that.
Here is the adb and fastboot files for Windows. Check they work with the Z before throwing them in the first post. If you do.
http://www.mediafire.com/?zlbyfbaaf5lrj8i
I've updated this guide to flesh it out a bit more (still more to be done though).
Significantly, please note that in the latest version of the SDK (i.e the one for Android 2.3), they have taken adb *out* of the Starter version of the SDK. So now there's an additional step, which is downloading the "Platform Tools" component of the SDK. It's all in the guide though.
nice, this needs to be "stickied"..
steviewevie...
whatever you are on.. can i haz some?
you are poster of the year! wow, such effort.
this beeyotch must be stickied all over the world.
EDIT -- i dont see "adb pull /" so as to dump all your files from system data etc into your sdk folder. if i missed that nevermind!
@steviewevie:
My 2 cents for your great work:
I have tested and uploaded a Mini ADB package and the ADB USB drivers for Windows Vista / Windows 7, to the Resources Centre, easy tutorial + FAQs thread here:
http://forum.xda-developers.com/showthread.php?t=835777
I thought this would make things easier for newbies or people who don't want to download the whole SDK / Sync software
Also, setting the path is not required, since the "Runme" file is located inside the same folder within the ADB files
This could save some steps for newbies
If you find it helpful, feel free to link from your guide
Thanks for the input guys, I have some updating to do !
steviewevie said:
INSTALLING ADB - METHOD B, THE "QUICK" WAY, NO SDK
Step 2
Download the adb binary from ? * to be completed *
Click to expand...
Click to collapse
Direct Download Links for Android SDK Platform-tools, revision 1
ht*p://dl-ssl.google.com/android/repository/platform-tools_r01-windows.zip
ht*p://dl.google.com/android/repository/platform-tools_r01-windows.zip
It contains ADB.exe and needed dlls
size 3.06 MB
Also i recommend ADBMagic from Chainfire if you got tired of using ADB commands by hand for a lot of operations
ht*p://forum.xda-developers.com/showthread.php?t=746313
Have fun
if you add adb.exe to system32 folder is windows u can adb from anywhere in command prompt.. just in case adding the variables dont work
Hey so if anyone knows how to test roms on android sdk emulator with your pc please help me!
I found a really old guide from modaco and the problem I first enountered was that it wouldn't give me some ID number or something on cmd.
So a step-by-step guide would be great!
I have the same problem too...
what can we do?
Old topic but my answer would help for people using search button or google
1. Download the Android SDK (which includes the emulator) from here.
2. Extract the downloaded zip.
3. Run a command prompt, and change to the 'tools' directory of the SDK (or add the tools directory to your path).
4. Type 'android list target'
5. Note the 'id' number of the '1.5' target (in my case it's '2')
6. Type 'android create avd -n enhanced -t 2' (substitute 2 with the target number determined above if required)
7. You will be prompted to create a hardware profile. This is optional, but I selected 'yes' and accepted the defaults for everything except RAM, where I gave it 256MB. wink.gif
8. Download and unzip THIS image file.(in this step you can just use your own rom)
9. Copy the above file to the location of the enhanced.avd directory ('C:\Documents and Settings\<user>\.android\enhanced.avd' on Windows XP, and 'C:\Users\<user>\.android\enhanced.avd' on Windows Vista).
10. You're ready! Type 'emulator -avd enhanced' to run! Note: inital boot may take a few minutes!
If you get Java errors, you need to download the JDK for your system from here!
Mac OSX
1. Download the Android SDK (which includes the emulator) from here.
2. Extract the downloaded zip.
3. Run Terminal, and change to the 'tools' directory of the SDK (or add the tools directory to the path settings in ~/.profile).
4. Type './android list target'
5. Note the 'id' number of the '1.5' target (in my case it's '2')
6. Type './android create avd -n enhanced -t 2' (substitute 2 with the target number determined above if required)
7. You will be prompted to create a hardware profile. This is optional, but I selected 'yes' and accepted the defaults for everything except RAM, where I gave it 256MB. wink.gif
8. Download and unzip this image file.(again, here is where you can use your custom rom)
9. Copy the above file to ~/.android/avd/enhanced.avd/system.img (e.g. if you saved it to and unzipped it to downloads enter 'cp ~/Downloads/system.img ~/.android/avd/enhanced.avd/system.img')
10. You're ready! Type './emulator -avd enhanced' to run! Note: inital boot may take a few minutes!
If you get Java errors, you need to download the JDK for your system from here!
Help me please........
I've downloaded the android studio & sdk tool separately (both from official website)
Now my question is : can I use them together??......if yes.....then tell me the process
Why do u people just copy and paste the stuff from other websites?
Pls. Do specify in ur own way or pls make a video on this!!
Hi,
I want to start creating a custom rom, but i did not want to test it each time on my desire.
So i would like to know, if there is a possiblity to run desire custom roms on android emulator?
That would make it much more easier for me.
Metin
Sent from my HTC Desire using Tapatalk
Edit: its a Sense Rom
Tip
Maybe you've found it already but here are the steps that work with CM:
1. Download the Android SDK (which includes the emulator) from here.
2. Extract the downloaded zip.
3. Run a command prompt, and change to the 'tools' directory of the SDK (or add the tools directory to your path).
4. Type 'android list target'
5. Note the 'id' number of the '1.5' target (in my case it's '2')
6. Type 'android create avd -n enhanced -t 2' (substitute 2 with the target number determined above if required)
7. You will be prompted to create a hardware profile. This is optional, but I selected 'yes' and accepted the defaults for everything except RAM, where I gave it 256MB.
8. Download and unzip CM7 image file.
9. Copy the above file to the location of the enhanced.avd directory ('C:\Documents and Settings\<user>\.android\enhanced.avd' on Windows XP, and 'C:\Users\<user>\.android\enhanced.avd' on Windows Vista).
10. You're ready! Type 'emulator -avd enhanced' to run! Note: inital boot may take a few minutes!
If you get Java errors, you need to download the JDK for your system.
It does not seem to work ! can anyone help please!
Hello guys and girls. I'm gonna describe a little tool called Knives & forks and why it's so awesome. It's made by a user called DieHappy, so all credit to him! Source post: http://forums.acsyndicate.net/showthread.php?5008
Need I say once more that this isn't my work?
Before we start, I'd like to say I take no responsibility if something bad happens!
What is this, you say?
It is a set of tools for everyone, all operating systems and devices. It is a toolkit written in Python to work for Linux, Mac OS X and Windows.
Well, what does it actually do?!
Easy there. DieHappy started working on this not so long ago, so the features are limited. Right now, he focuses on making sure this program offers a stable base for all known android devices. It sets up correct ADB and Fastboot drivers and also makes the need of an android sdk useless if you only use the drivers. No need to set up an environmental path to the sdk or to navigate to a folder to use ADB, you can use ADB from ANYWHERE! Just open up cmd/a terminal and type adb and bam, it works.
How to support this project?
I don't really offer assistance to this as my knowledge is limited, but I can probably give you answers to most questions. Check out the original thread here for more help.
How to reply to this thread?
Ask anything, or write anything about this program here. Do not clutter the original thread over at ascyndicate forums.
Ok, how do I go about installing this?
First off, make sure you know how to decompress archives (namely zip or rar archives). Try 7-zip. Also, make sure you know the process of creating and renaming folders.
Download current version: 12.02.04
Mac OS X
This was tested on Mac OS X 10.7.2. Please report your success or any errors you have running this on other versions, but report them on the source thread, no use in reporting this here.
Unzip to "/Users/INSERT-YOUR-USERNAME-HERE/knives-and-forks/"
NOTE: REPLACE "INSERT-YOUR-USERNAME-HERE" WITH YOUR COMPUTER USERNAME.
FOR EXAMPLE, I WOULD UNZIP THE FILE TO: "/Users/DieHappy/knives-and-forks/"
NOTE: MAKE SURE THE DIRECTORY NAME IS SIMPLY "knives-and-forks".
DO NOT INCLUDE THE VERSION NUMBER IN THE FILE NAME FOR THE .ZIP FILE YOU DOWNLOADED.
Open Finder to "/Users/INSERT-YOUR-USERNAME-HERE/knives-and-forks/"
Double-Click "/Users/INSERT-YOUR-USERNAME-HERE/knives-and-forks/Knives-and-Forks-Mac.app"
You should see the Knives and Forks Main Menu in the Terminal window.
Linux
This was tested on Ubuntu 11.10 and Xubuntu 11.10. Please report your success or any errors you have running this on other versions or Linux distros.
Unzip to "/home/INSERT-YOUR-USERNAME-HERE/knives-and-forks/"
NOTE: REPLACE "INSERT-YOUR-USERNAME-HERE" WITH YOUR COMPUTER USERNAME.
FOR EXAMPLE, I WOULD UNZIP THE FILE TO: "/home/DieHappy/knives-and-forks/"
NOTE: MAKE SURE THE DIRECTORY NAME IS SIMPLY "knives-and-forks".
DO NOT INCLUDE THE VERSION NUMBER IN THE FILE NAME FOR THE .ZIP FILE YOU DOWNLOADED.
Open Terminal
Change the permissions to executable for "Knives-and-Forks-Linux.sh" by typing this into the Terminal window, then pressing [ENTER]:
Code:
chmod +x ~/knives-and-forks/Knives-and-Forks-Linux.sh
NOTE: "~" is a shortcut so you don't have to type "/home/INSERT-YOUR-USERNAME-HERE/"
Change to the "knives-and-forks" dir by typing the following in the Terminal window, then pressing [ENTER]:
Code:
cd ~/knives-and-forks
Run "Knives-and-Forks.sh" by typing the following in the Terminal window, then pressing [ENTER]:
Code:
[B]./[/B]Knives-and-Forks-Linux.sh
NOTE: DON'T FORGET TO TYPE "./" BEFORE THE FILE NAME.
THIS TELLS LINUX TO RUN THE SCRIPT IN THE CURRENT DIRECTORY.
TYPING JUST THE FOLLOWING WOULD RESULT IN AN ERROR:
Code:
Knives-and-Forks-Linux.sh
You should see the Knives and Forks Main Menu in a new Terminal window.
Windows
This was tested on Winows 7 Pro x64. Please report your success or any errors you have running this on other versions.
Unzip to your user profile directory
-- Vista, 7, Server 2008, Server 2008 R2: "c:\Users\INSERT-YOUR-USERNAME-HERE\knives-and-forks\"
-- 2000, XP, Server 2003: "c:\Documents & Settings\INSERT-YOUR-USERNAME-HERE\knives-and-forks\"
NOTE: REPLACE "INSERT-YOUR-USERNAME-HERE" WITH YOUR COMPUTER USERNAME.
FOR EXAMPLE, IN WINDOWS 7 I WOULD UNZIP THE FILE TO: "c:\Users\DieHappy\knives-and-forks\"
NOTE: MAKE SURE THE DIRECTORY NAME IS SIMPLY "knives-and-forks".
DO NOT INCLUDE THE VERSION NUMBER IN THE FILE NAME FOR THE .ZIP FILE YOU DOWNLOADED.
Run "c:\Users\INSERT-YOUR-USERNAME-HERE\knives-and-forks\Knives-and-Forks-Windows.cmd"
Python will automatically be downloaded and installed for you.
Once python is installed, you should see the Knives and Forks Main Menu in the command prompt window.
Ok, installed it, now what?
You should be able to open up your terminal application (or command prompt) and run some adb commands. In the future we will be automating adb commands for you, but for now you can try rebooting your device via adb by opening up a terminal (or command prompt) window, then typing the following, then pressing [ENTER]:
Code:
adb reboot
NOTE: AT THIS STAGE, YOU SHOULD ONLY NEED TO RUN THE KNIVES & FORKS SCRIPT ONCE TO INSTALL DRIVERS AND GET ADB WORKING. ONCE SETUP IS COMPLETE, YOU CAN RUN ADB COMMANDS AS SOON AS YOU OPEN UP YOUR TERMINAL/COMMAND PROMPT WINDOW.
If everything worked, your Android device should reboot. For further reading on what you can do with adb you can read THIS PAGE.
Code:
[B]**** 12.02.04 ****[/B]
- LINUX CHANGES:
-- "python2" is now called by "Knives-and-Forks-Linux.sh" instead of "python" on Arch.
- This prevents starting the script with Python 3, which results in errors.
-- Changes to "scripts/linux/install-adb-linux.sh":
- "su" will be used if "sudo" is not installed, or user doesn't have permissions to use it.
- Added 32-bit libs for more 64-bit distros:
- Arch (new in this release)
- CentOS (new in this release)
- Debian
- Fedora (new in this release)
- Ubuntu, Kubuntu, Xubuntu
- Added Debian version of '/etc/udev/rules.d/99-android.rules'
- Added '/lib/udev/rules.d/92-permissions.rules' for Debian.
This should fix permissions, allowing adb to run without sudo or su.
- WINDOWS CHANGES:
-- Fixed a couple of missing quotes which were breaking things under Windows XP
- "%userprofile%" was coming back as "c:\documents" instead of
"c:\documents and settings\username" in a couple of places
-- "c:\python27" is now the only directory where we look for python.exe
- It is faster to download and install Python to "c:\Python27" than it is to search for it
elsewhere.
- This will also prevent issues where Python 3 was installed instead of Python 2, since the
script currently gives errors under Python 3.
-- Updated amd64 and x86 versions of setx.exe for updating system PATH on XP/VISTA/7
-- PATH is updated with adb.exe location after Python is installed.
-- The computer will now reboot after updating the PATH, to make sure it will be updated before
running the main program.
[B]
**** 12.01.27 ****[/B]
- GENERAL CHANGES:
-- After adb is installed, adb will reset the android device by running "adb reboot" instead of
displaying a list of attached devices with "adb devices".
adb was occasionally reporting no devices were attached, when they infact were. When this happened
"adb reboot" still worked, so it is a better test to see if adb is setup properly.
-- Friendlier messages during adb install and testing
-- Added a startup check to make sure the script is running from the correct directory
-- Removed empty Project directory, as it is not being used yet.
- LINUX CHANGES:
-- Added support for "lxterminal" and "urxvt" in "Knifes-and-Forks-Linux.sh"
-- Changed idVendors for Linux udev rules to lowercase instead of uppercase.
- WINDOWS CHANGES:
-- Startup script searches for python in "C:\Program Files (x86)" then "C:\Program Files" and
"c:\" last.
-- Drivers should now install even if the language is not English
-- Added drivers for Casio C771 G'zOne Commando
-- Added LG drivers
-- Replaced setx.exe
[B]**** 12.01.25 ****[/B]
- Replaced "Knives-and-Forks-Mac.sh" with "Knives-and-Forks-Mac.app".
Starting the script on a Mac should now be as simple as double-clicking the new .app file.
[B]**** 12.01.24 ****[/B]
- Fixed a typo which caused the script to crash when viewing the credits screen.
- Smarter python fix for Windows users.
-- "C:\" and all sub-directories are searched for python.exe.
-- If python is not not found, it will be downloaded from python.org and installed to c:\python27.
-- If python is found (in "C:\python27", "c:\python", "c:\xyz123", "c:\program files\python27" or
in any directory with any name anywhere on drive c:) the main menu script will launch.
- Added changelog.txt to the release .zip file.
[B]
**** 12.01.23 ****[/B]
- Minor update to fix Python installation for Windows users, which was causing the script not to launch.
[B]
**** 12.01.22 ****[/B]
(FIRST PUBLIC RELEASE)
- Added option to install adb & fastboot for Linux, Windows, Mac
- Added Linux drivers for:
-- ACER
-- ASUS
-- DELL
-- FOXCONN
-- GARMIN-ASUS
-- Google
-- Hisense
-- HTC
-- HUAWEI
-- K-TOUCH
-- KT Tech
-- KYOCERA
-- LENEVO
-- LG
-- MOTOROLA
-- NEC
-- NOOK
-- NVIDIA
-- OTGV
-- PANTECH
-- PEGATRON
-- PHILIPS
-- PMC-SIERRA
-- QUALCOMM
-- SK TELESYS
-- SAMSUNG
-- SHARP
-- SONY ERICSSON
-- TOSHIBA
-- ZTE
- Added Mac drivers for:
-- Nothing. According to Google, "It just works." Let me know if they are right.
- Added a custom Windows installer with drivers for:
-- GOOGLE
-- HTC
-- HUAWEI
-- SAMSUNG
is it useful to you guys? I mean, you don't ever have to hassle with having bad drivers as these always work. And you never need to hassle with ADB and/or fastboot commands as this sets up environmental values and other stuff so you can access the adb and fastboot commands from wherever you are, i.e. no need to navigate to a certain folder.
*bump*
Thanks man. Did some googling just now and found tools for my linux mint debian edition. Any new on this tools mate?Perhaps new features for next release.
Mac OSX 10.6.8, nothing happens on double click on .app file
Can You Mirror?
Theshawty said:
*bump*
Click to expand...
Click to collapse
I have tried 4 a wk. It seems the site is down. Could you please attach the latest version here or mirror it mega? I would greatly appreciate it. I just wanted to try this out and "round out" my toolkits. Thank you for your time and help.
May you install Magisk Manager and export the "patched" kernel, and flash the patched kernel through fastboot?
Hi mingkee.
This works whit G3311 confirmed. Build: 43.0.A.6.49 Android 7.0 Baseband MOLY.LR9.W1444.MD.LWTG.MP.V166..5, Kernel 3.18.35+
Kernel is for G3313 magisk patch.
Everything works with this for G3311 as I've tested. Try it at you're own risk.
In linux in (debain, Ubuntu, Linux Mint and all) you need tools
Terminal "sudo apt-get install android-tools-adb android-tools-fastboot"
1. Unlock bootloader https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code. Get the code
2. Go to settings/ about phone/ build number/ click 7 times. Go back to settings. Developer options/ USB debuggning ON. OEM unlock ON. And try "adb devices" in terminal GNU/Linux. Should popup a allow PC on the phone" tranfer files is necessary "MTP", on the phone.
3. In terminal "adb reboot bootloader" this is where "allow access to computer" if it's haven't appeared allow on the phone.
4. In terminal "fastboot oem unlock x0(the code). no space. Don't know why x0 doesn't exist in the code. Don't know why. It's my first Sony with the openness they got now (thank god for Lund, sweden and Jolla, Finland). But it seems pretty easy to unlock. Honor 8 have closed bootloader unlock since 8 Month. So be at ease. And maybe save you're unlock code. But it doesn't seems like you need it.
5. I did it this way.
5/1 Download https://serv8.asuscomm.com/owncloud/index.php/s/t3N4iYNUoAMnwqI "latest I think" otherwise you can look at this link https://forum.xda-developers.com/apps/magisk. A bit messy I think.
6. Terminal command "adb install (this apk) drag it from dir. Of course ADB-debugger ON. I don't know instructions for Windownsyndrom. If you need it, I can guide you or somebody else that need it. Just ask.
7. Download https://serv8.asuscomm.com/owncloud/index.php/s/QXkxRkBezJXLlQE. And the easiest way are with ADB "adb reboot bootloader". Or use buttons and cable. Blue LED should be on and black screen.
8. Teminal "fastboot devices" Permission denied. Then you need sudo. Try "sudo fastboot devices"
8/1 If you need ROOT remember
------------------------------------------------------------------------------------------------------------------------------------------------------------
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
----------------------------------------------------------------------------------------------------------------------------------------------------------
Terminal
[email protected] ~ $ sudo fastboot devices
[sudo] password for johan:
WUJ01R6*** fastboot
----------------------------------------------------------------------------------------------------------------------------------------------------------
When you see a number then you know the GNU/Linux recognize the phone and back.
So after that "fastboot flash boot "this boot patched_boot_G3313.img" or if you need root "sudo fastboot flash boot "this boot patched_boot_G3313.img" drag is the lazymans work from dir. Or cd to the dir and find the file. Works whit both ROOT and user.
Terminal
"fastboot restart"
Then you should see in the magisk app that you are rooted systemless. And can use modules.
Haven't tried any modules yet.
Just try too break it down to simple language.
This is the origin of https://forum.xda-developers.com/xperia-l1/how-to/root-l1-g3313-magisk-t3693350.
Need help at 5.
purjolini said:
Hi mingkee.
This works whit G3311 confirmed. Build: 43.0.A.6.49 Android 7.0 Baseband MOLY.LR9.W1444.MD.LWTG.MP.V166..5, Kernel 3.18.35+
Kernel is for G3313 magisk patch.
Everything works with this for G3311 as I've tested. Try it at you're own risk.
In linux in (debain, Ubuntu, Linux Mint and all) you need tools
Terminal "sudo apt-get install android-tools-adb android-tools-fastboot"
1. Unlock bootloader https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code. Get the code
2. Go to settings/ about phone/ build number/ click 7 times. Go back to settings. Developer options/ USB debuggning ON. OEM unlock ON. And try "adb devices" in terminal GNU/Linux. Should popup a allow PC on the phone" tranfer files is necessary "MTP", on the phone.
3. In terminal "adb reboot bootloader" this is where "allow access to computer" if it's haven't appeared allow on the phone.
4. In terminal "fastboot oem unlock x0(the code). no space. Don't know why x0 doesn't exist in the code. Don't know why. It's my first Sony with the openness they got now (thank god for Lund, sweden and Jolla, Finland). But it seems pretty easy to unlock. Honor 8 have closed bootloader unlock since 8 Month. So be at ease. And maybe save you're unlock code. But it doesn't seems like you need it.
5. I did it this way.
5/1 Download https://serv8.asuscomm.com/owncloud/index.php/s/t3N4iYNUoAMnwqI "latest I think" otherwise you can look at this link https://forum.xda-developers.com/apps/magisk. A bit messy I think.
6. Terminal command "adb install (this apk) drag it from dir. Of course ADB-debugger ON. I don't know instructions for Windownsyndrom. If you need it, I can guide you or somebody else that need it. Just ask.
7. Download https://serv8.asuscomm.com/owncloud/index.php/s/QXkxRkBezJXLlQE. And the easiest way are with ADB "adb reboot bootloader". Or use buttons and cable. Blue LED should be on and black screen.
8. Teminal "fastboot devices" Permission denied. Then you need sudo. Try "sudo fastboot devices"
8/1 If you need ROOT remember
------------------------------------------------------------------------------------------------------------------------------------------------------------
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
----------------------------------------------------------------------------------------------------------------------------------------------------------
Terminal
[email protected] ~ $ sudo fastboot devices
[sudo] password for johan:
WUJ01R6*** fastboot
----------------------------------------------------------------------------------------------------------------------------------------------------------
When you see a number then you know the GNU/Linux recognize the phone and back.
So after that "fastboot flash boot "this boot patched_boot_G3313.img" or if you need root "sudo fastboot flash boot "this boot patched_boot_G3313.img" drag is the lazymans work from dir. Or cd to the dir and find the file. Works whit both ROOT and user.
Terminal
"fastboot restart"
Then you should see in the magisk app that you are rooted systemless. And can use modules.
Haven't tried any modules yet.
Just try too break it down to simple language.
This is the origin of https://forum.xda-developers.com/xperia-l1/how-to/root-l1-g3313-magisk-t3693350.
Click to expand...
Click to collapse
Hi, I've unlocked my phone but I don't uderstand at the 5 can you explain please ? Because I'm on Windows.
Cordially,
Atomiikz.
AtomiiKz said:
Hi, I've unlocked my phone but I don't uderstand at the 5 can you explain please ? Because I'm on Windows.
Cordially,
Atomiikz.
Click to expand...
Click to collapse
Ok Atomiikz. So download and install adb and fastboot tools. From here https://forum.xda-developers.com/showthread.php?t=2588979 install system wide. Otherwise you need to open CMD in the folder whith adb and fastboot.
The open CMD and write "adb devices" and allow on the phone. This should come upp in the command promt "CMD"
--------------------------------------
C:\Users\Mr.J>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
WUJ01R**** device
--------------------------------------
Then " adb install (drag the apk here)" and ENTER. That installs magisk app on you're phone.
Or download the apk. Transfer to the phone. Then use some file explorer like https://play.google.com/store/apps/details?id=com.mi.android.globalFileexplorer https://play.google.com/store/apps/details?id=nextapp.fx https://play.google.com/store/apps/details?id=com.estrongs.android.pop and find the apk. Then install it.
And a heads up if you never used fastboot in windows 10, in my case. I used this application http://zadig.akeo.ie/ to install fastboot drivers for (s1boot fastboot)
Good luck. Write if you have more questions.
I have a question Does the camera or screen or performance get damaged with this proccess ?