Related
I've been struggling with this for about six hours. Now, I have finally worked out a solution.
Hopefully it works for you. I will do my best to tell you exactly what I did so that if you don't entirely understand how to do stuff (for lack of a better phrase) in Linux, you can get this working.
Step 1: Go download the android SDK
http://developer.android.com/sdk/index.html
When it is done downloading, unzip the file into your home directory. Make sure to rename the folder androidsdk
Open up the newly unzipped folder and go into the tools directory. run the android shell script.
NOTE: WHEREVER IT SAYS "androidsdk" AS A DIRECTORY IN THIS GUIDE, YOU WILL HAVE TO REPLACE THAT WITH WHATEVER YOU NAME THE FOLDER. (I would suggest just naming it androidsdk)
Go to "available packages" and select all of the boxes. Once they are all selected, click on "Install" in the bottom right corner.
Go grab a cup of hot chocolate. That is an order.
Go into the platform-tools directory in the sdk directory (androidsdk) and right click on adb. Go to "properties" then the "permissions" tab and make sure the box that reads "allow executing file as program" is checked.
Go to the "open with" tab and add "autorun prompt."
Step 2: Get your paths in order
Go to your home folder and hit ctrl H to show all of the hidden folders and files.
Find bashrc and open it with the text editor. Copy and paste the following text at the very top.
#AndroidDev PATH
export PATH=${PATH}:/androidsdk/tools
Open up your terminal and type:
export PATH=$PATH:/androidsdk/tools
gksudo gedit /etc/udev/rules.d/51-android.rules
#When it opens up the file 51-android.rules, copy and paste this into it, then save the file:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="0e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
Plug in your Archos Gen8 Tablet via USB.
https://dl-web.dropbox.com/get/AndroidFiles/LINUX_SDK_ADB_INSTALLER.zip?w=b4bd354e&dl=1
(The credit is in the code)
Download that and extract the zip to your home directory.
Go to the home directory and run the LINUX_SDK_ADB_INSTALLER shell script
It will download and install the drivers for ADB.
Step 3: Nautilus-ize it
Open up another terminal and type in:
sudo nautilus
(If you don't have nautilus like i didn't, just type in: sudo apt-get install nautilus)
once a window pops open that says "root", go ahead and navigate back to the filesystem (one folder up)
navigate to /usr/local/androidsdk/tools and make sure that adb is still an executable and is set to open with the "autorun prompt" (like in step 2)
close the window that nautilus opened up and shut down the terminal to end the root session.
Step 4: Finishing touches.
Go to the .Android directory in Home (it is hidden, you will have to put ctrl H to make it show) and find a file called adb_usb.ini ( if there isn't one, then you just have to create a text file and save it as adb_usb.ini )
Copy and paste
"0x0e79" >> ~/.android/adb_usb.ini
Into the adb_usb.ini file
Step 5: Run ADB.
Open up a terminal and type:
cd /usr/local/androidsdk/tools/
Type:
echo "0x0e79" >~/.android/adb_usb.ini
./adb kill-server
./adb start-server
type in ./adb devices
your Gen8 Tab should show up now as A70-3FAXXXXX-XXXXX-XXXXX device (the X's are your serial number. Don't freak out if you don't get a bunch of X's)
you can now run all of the adb commands by typing:
./adb kill-server
./adb reboot
./adb etc... etc...
(Those are examples. you dont have to actually type them in)
Voila. You are now all connected via ADB.
If you have any questions or something isn't working, we can troubleshoot in the comments.
I hope i was able to help those using Ubuntu 10.10 that need ADB.
(Hopefully if we get this working, it will be easier for developers to pull/ push files and get things working better.)
~ClothoBuer6293
~PokeJake2002
I get error 403 when i try to download the file.
http://forum.xda-developers.com/attachment.php?attachmentid=448536&d=1290585848
There. That is the link to the original location of the file.
I guess i need to work on making dropbox links.
There's a couple of things wrong, since it's mixing terminal commands with doing things entirely via the GUI (Step 4 more precisely). It also seems it's mixing guides from different sources, there's a couple of redundant steps. I don't think you've done these steps as they stand, they wouldn't have worked
This is my suggestion:
Step 1. Download SDK and extract it
Step 2. Run android shell script in extracted_folder/tools (just double click and choose run in Ubuntu). If you just want adb then it's sufficient to mark only "Android SDK Platform-tools revision 1" for installation. The adb executable ends up in extracted_folder/platform-tools, and already has the exacutable bit set.
Step 3. For the device to show up with adb you need to do the udev step above, that is:
gksudo gedit /etc/udev/rules.d/51-android.rules (in a terminal) and paste this in the file
Code:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="0e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
In the same terminal, enter
gedit ~/.android/adb_usb.ini
and paste this in the file (or add at the bottom, if you already have it)
Code:
0x0e79
Step 4. Enable USB Debugging on the Archos (Settings -> Applications -> Development) and connect it to the computer
Step 5. Navigate to extracted_folder/platform_tools and run
./adb devices
(if nothing shows up, run ./adb kill-server followed by ./adb start-server and then ./adb devices again)
So what needs to be fixed in the guide is:
* the redundant step of downloading adb separately
* step 4 is really messed up, it's pasting terminal commands in the adb_usb.ini file and if it worked for you, it's because after pasting the terminal command you actually in Step 5 also echo the vendor ID to the end of file. Also, step 4 uses relative paths (./) to the adb executable, which indicates that the path step hasn't been done. Actually, come to think of it you get "no such file or directory" error if you enter ./adb if you don't happen to be in the right directory, so adding the adb folder to PATH isn't going to help.
Personally, I think the path step can be skipped altogether, but if people really want to be able to enter the adb command when they open a terminal window they should make sure the put the folder somewhere they plan to keep it. The best thing is for people to know how the basic terminal command works, as that is what they are using for adb anyway.
Thanks. This is pretty much my first walkthrough so i appreciate your assistance.
Sent from my A70S using Tapatalk
It's a good first attempt, you're detailed in your steps which is good. One thing which is nice though, is describing why something is done too, for example the case with adding the udev rule etc. Speaking of that, thanks a bunch for the info on that, wouldn't have gotten my Archos to show up without it
Thanks. Haha.
I was really confused and I think most of what I did to get it to work was on accident.
I just didnt see any particular howtos on getting ADB for Archos Gen8 working in Ubuntu so I thought I would type one up based on how I got it to work and hope that smarter developers would correct me and help me to polish it.
The only way I have been able to connect to the Archos is to run as "root". Is this the purpose of the "nautilus" instruction? I thought the MODE="0666" would make the device accessible to all users. If I try this as a normal user, the device appears with "no permissions".
How do you fix this?
pokejake2002 said:
I've been struggling with this for about six hours. Now, I have finally worked out a solution.
Hopefully it works for you. I will do my best to tell you exactly what I did so that if you don't entirely understand how to do stuff (for lack of a better phrase) in Linux, you can get this working.
Step 1: Go download the android SDK
http://developer.android.com/sdk/index.html
When it is done downloading, unzip the file into your home directory. Make sure to rename the folder androidsdk
Open up the newly unzipped folder and go into the tools directory. run the android shell script.
NOTE: WHEREVER IT SAYS "androidsdk" AS A DIRECTORY IN THIS GUIDE, YOU WILL HAVE TO REPLACE THAT WITH WHATEVER YOU NAME THE FOLDER. (I would suggest just naming it androidsdk)
Go to "available packages" and select all of the boxes. Once they are all selected, click on "Install" in the bottom right corner.
Go grab a cup of hot chocolate. That is an order.
Go into the platform-tools directory in the sdk directory (androidsdk) and right click on adb. Go to "properties" then the "permissions" tab and make sure the box that reads "allow executing file as program" is checked.
Go to the "open with" tab and add "autorun prompt."
Step 2: Get your paths in order
Go to your home folder and hit ctrl H to show all of the hidden folders and files.
Find bashrc and open it with the text editor. Copy and paste the following text at the very top.
#AndroidDev PATH
export PATH=${PATH}:/androidsdk/tools
Open up your terminal and type:
export PATH=$PATH:/androidsdk/tools
gksudo gedit /etc/udev/rules.d/51-android.rules
#When it opens up the file 51-android.rules, copy and paste this into it, then save the file:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="0e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
Plug in your Archos Gen8 Tablet via USB.
https://dl-web.dropbox.com/get/AndroidFiles/LINUX_SDK_ADB_INSTALLER.zip?w=b4bd354e&dl=1
(The credit is in the code)
Download that and extract the zip to your home directory.
Go to the home directory and run the LINUX_SDK_ADB_INSTALLER shell script
It will download and install the drivers for ADB.
Step 3: Nautilus-ize it
Open up another terminal and type in:
sudo nautilus
(If you don't have nautilus like i didn't, just type in: sudo apt-get install nautilus)
once a window pops open that says "root", go ahead and navigate back to the filesystem (one folder up)
navigate to /usr/local/androidsdk/tools and make sure that adb is still an executable and is set to open with the "autorun prompt" (like in step 2)
close the window that nautilus opened up and shut down the terminal to end the root session.
Step 4: Finishing touches.
Go to the .Android directory in Home (it is hidden, you will have to put ctrl H to make it show) and find a file called adb_usb.ini ( if there isn't one, then you just have to create a text file and save it as adb_usb.ini )
Copy and paste
"0x0e79" >> ~/.android/adb_usb.ini
Into the adb_usb.ini file
Step 5: Run ADB.
Open up a terminal and type:
cd /usr/local/androidsdk/tools/
Type:
echo "0x0e79" >~/.android/adb_usb.ini
./adb kill-server
./adb start-server
type in ./adb devices
your Gen8 Tab should show up now as A70-3FAXXXXX-XXXXX-XXXXX device (the X's are your serial number. Don't freak out if you don't get a bunch of X's)
you can now run all of the adb commands by typing:
./adb kill-server
./adb reboot
./adb etc... etc...
(Those are examples. you dont have to actually type them in)
Voila. You are now all connected via ADB.
If you have any questions or something isn't working, we can troubleshoot in the comments.
I hope i was able to help those using Ubuntu 10.10 that need ADB.
(Hopefully if we get this working, it will be easier for developers to pull/ push files and get things working better.)
~ClothoBuer6293
~PokeJake2002
Click to expand...
Click to collapse
I thought the instructions from Archos were pretty clear. I've never had an issue with ADB in Linux.
Code:
Add Archos vendor ID (0x0e79) to adb_usb.ini in .android folder in your home directory:
Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
For Linux users only: You need to add a udev rule if ADB only works as root:
Create a file /etc/udev/rules.d/51-android.rules that contains the following lines:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="e79", MODE="0666"
Make the rule known to udev with the following command:
udevadm control --reload-rules (or udevcontrol reload_rules on older systems)
foh1981 said:
There's a couple of things wrong, since it's mixing terminal commands with doing things entirely via the GUI (Step 4 more precisely). It also seems it's mixing guides from different sources, there's a couple of redundant steps. I don't think you've done these steps as they stand, they wouldn't have worked
This is my suggestion:
Step 1. Download SDK and extract it
Step 2. Run android shell script in extracted_folder/tools (just double click and choose run in Ubuntu). If you just want adb then it's sufficient to mark only "Android SDK Platform-tools revision 1" for installation. The adb executable ends up in extracted_folder/platform-tools, and already has the exacutable bit set.
Step 3. For the device to show up with adb you need to do the udev step above, that is:
gksudo gedit /etc/udev/rules.d/51-android.rules (in a terminal) and paste this in the file
Code:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="0e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
In the same terminal, enter
gedit ~/.android/adb_usb.ini
and paste this in the file (or add at the bottom, if you already have it)
Code:
0x0e79
Step 4. Enable USB Debugging on the Archos (Settings -> Applications -> Development) and connect it to the computer
Step 5. Navigate to extracted_folder/platform_tools and run
./adb devices
(if nothing shows up, run ./adb kill-server followed by ./adb start-server and then ./adb devices again)
So what needs to be fixed in the guide is:
* the redundant step of downloading adb separately
* step 4 is really messed up, it's pasting terminal commands in the adb_usb.ini file and if it worked for you, it's because after pasting the terminal command you actually in Step 5 also echo the vendor ID to the end of file. Also, step 4 uses relative paths (./) to the adb executable, which indicates that the path step hasn't been done. Actually, come to think of it you get "no such file or directory" error if you enter ./adb if you don't happen to be in the right directory, so adding the adb folder to PATH isn't going to help.
Personally, I think the path step can be skipped altogether, but if people really want to be able to enter the adb command when they open a terminal window they should make sure the put the folder somewhere they plan to keep it. The best thing is for people to know how the basic terminal command works, as that is what they are using for adb anyway.
Click to expand...
Click to collapse
It's important to ad ADB to your PATH. Many aapt tools and the like use it. And you can't just put ADB in every directory you want to work in. I do framework stuff in a framework folder, os stuff in others, etc. I'm not going to use the full path every time I type.
pokejake2002:
All that is really needed in this tutorial is "Download the SDK, extract, run ./tools/android and download the ADB driver. Add vendor id to .android/adb_usb.ini, then create udev rule /etc/udev/rules.d/51-android.rules. Add export PATH=$PATHdownloaded directory)/android-sdk/platform-tools to bash.rc"
That's it. I'm not sure what all that extra stuff is. You've done almost every step twice, and some are incorrect, such as the export path, you did it twice, and the actual path should be platform-tools, not just tools, and you echoed the vendor ID twice as well.
Also, nautilus is included by default in ubuntu > 7.0, so i'm not sure how it wasn't installed on 10.10.
Also, all the "./adb" lines should just be "adb" if you exported the path correctly, which like i said, is supposed to be platform-tools, not just tools.
Just FYI, not trying to flame, I can tell you don't have much experience, it's not a bad thing. But also, "(Hopefully if we get this working, it will be easier for developers to pull/ push files and get things working better.)" I don't know any developers who haven't had adb working from day one.
1. Linux(easy)
2. Mac(easy)
3. Windows(medium)
________________________________________________________
1. Linux
You don't need any special drivers for SDK on linux(adb shell), but you don't get fastboot binary in SDK package. To set fastboot for linux follow instructions:
1. Download SDK(this isn't need if you want just fastboot)
http://developer.android.com/sdk/index.html
2. Download fastboot linux binary
http://www.mediafire.com/?ldlovlzi9mx3pbh
3. Copy it to your SDK directory
/path_to_your_SDK_directory/platform-tools
or
if you use fastboot often and you don't want to type cd /path_to_your_SDK_directory/platform-tools, ./fastboot <action> every time, you can do this:
1. Open Terminal and type:
sudo nautilus
to get file browser with root privileges.
2. Copy fastboot binary to /bin directory
Now, just open terminal and type fastboot <action> and that's it?
Copy this file to /etc/udev/rules.d
EDIT:
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
Easy?
______________________________________________________________
2. Mac
I don't have Mac, but it should be like for linux:
1. Download SDK(this isn't need if you want just fastboot)
http://developer.android.com/sdk/index.html
2. Download fastboot Mac binary:
http://www.mediafire.com/?kjozh1q5dyyqhn3
3. Copy it to your SDK directory
/path_to_your_SDK_directory/platform-tools
or
(I don't know that this is possible on Mac, try to change nautilus with Mac's default file browser?)If you use fastboot often and you don't want to type cd /path_to_your_SDK_directory/platform-tools, ./fastboot <action> every time, you can do this:
1. Open Terminal and type:
sudo nautilus
to get file browser with root privileges.
2. Copy fastboot binary to /bin directory
Now, just open terminal and type fastboot <action> and that's it? Easy?
______________________________________________________________
3. Windows
1. Download SDK
http://developer.android.com/sdk/index.html
2. Download Google USB Drivers from SDK Manager
3. After download, there're located in /path_to_your_SDK_directory/extras/google/usb_driver
4. Open android_winusb.inf and add this after [Google.NTx86] or [Google.NTamd64](32 bit or 64bit)
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
(Here is my modificated android_winusb.inf file here, but it's old and an updated version arrived from Google and it's compatible with 32bit and 64bit)
5. Open CMD from Start>Run and type:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
6. Reboot
==========================================================
7. On tablet go to Settings > Applications > Development and enable USB Debugging if it wasn't enabled and connect tablet with computer via USB.
8. Right-click on Computer and click Manage. Identify your device from the list(I think it's Tegra with board icon), right-click it and click Update Driver Software
9. Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer
10. Choose to view all devices and click Have Disk
11. Browse to the google-usb_driver folder inside your Android SDK folder(/path_to_your_SDK_directory/extras/google/usb_driver) and select the android_winusb.inf file
12. If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing
13. Once the drivers have been installed, you should be able to use ADB with your device
14. To confirm that your device is recognized, launch a Command Prompt window and enter these commands:
adb kill-server
adb start-server
adb devices
If you see your device name or a few numbers as the output under the list of devices, your device is now recognized by ADB
For fastboot you need to go to /path_to_your_SDK_directory/platform-tools in terminal(cd /path_to_your_SDK_directory/platform-tools) and type fastboot(.exe) <action> and before it to change ADB Interface to ADB
That's it, if you have some complaints, post them.
Bye!!!
EDIT: Changed android_winusb.inf file due error in it.
EDIT2:Changed android_winusb.inf file due error in it again.
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
shut the cmd say something ? because when i write the command and push enter its just jump to another line and says nothing ???
No. You can go to that file("%USERPROFILE%\.android\adb_usb.ini") and manualy add 0x955 to it.
Sorry!
I cannot connect to this link:http://www.mediafire.com/?kjozh1q5dyyqhn3
Please do me a favor, send fastboot as an attachment to this mail address:
[email protected]
I'll try because I'm not at home, I went to my grand parents and I have really slow internet.
Hello guys I have a problem, the step 5. Open CMD from Start> Run and type:
echo 0x955>> "% USERPROFILE% \. Android \ adb_usb.ini"
I run this step but I open a txt file that says this:
Android # USB Vendor ID 3RD PARTY LIST - DO NOT EDIT.
# USE 'adb Android update' TO GENERATE.
USB Vendor ID # 1 FOR LINE.
0x955
I now do not understand where I write echo 0x955?
/documents_and_settings/[your user name]/.Android(hidden file)/adb_usb.ini
Sent from my Xoom using Tapatalk
Nice guide. Think you forgot the udev rule for Linux:
Create a file called /etc/udev/rules.d/51-android.rules containing:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", MODE="0666"
Without that Linux won't give you write permission to the device.
Ok, I'll add.
Sent from my IDEOS S7 Slim using XDA App
So when I want to use fastboot, I install the Android Bootloader Interface driver? Not the ADB interface driver?
Needless to say I haven't got fastboot working yet but ADB works. One other thing: If I manage to install a firmware and do a wipe and everything works; can it be that I would experiance better performance if I as well managed to to a full wipe with fastboot? I mean, can it flush things that CWM can't? I'm using the latest cyanogenmod (test version) from DerArtem, but I am a bit interested in trying the latest progress of honeycomb...
I have problems with interfaces. On one computer is ADB interface and on other is something else but I prefer linux for doing any job that's connected with android. In theory wiping should be same with fastboot and recovery but, again, I prefer fastboot because it's JUST erase all on data/cache/system partition and recovery might don't have support for other partition types as well as other problems, but I don't say that it can be different.
Thanks. I hope I continue to have a functioning cwm. If it breaks I will have to install Linux
ı do everything but when ı wrote adb devices nothing
Linux or Windows?
Jon2555 said:
Linux or Windows?
Click to expand...
Click to collapse
windows 7 x64
When the tablet is open in USB Debugging mode I can see my device adb devices list but when ı restart my tablet fastboot mode ı can't find
The best slow to install Linux via VM. It complicated on windows, it's different from computer to computer.
Sent from my IDEOS S7 Slim using XDA App
do i type this exactly with all the " ???
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
????????????????/
HELP PLEASE
No
Sent from my IDEOS S7 Slim using XDA App
When i tipe the echo 0x955 line
It keeps on saying that system cannot find the path specified
can someone please help?
even when i open comand prompt and type adb it says adb is not recognised as an internal or external.........
[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]
ADB & FASTBOOT FOR OS X
There has been some confusion since I discuss using Fastboot in this post, but the zip only contained ADB. This is completely my fault and I apologize. Either way I've updated the .zip to include ADB & Fastboot.UPDATED: 08/17/2013 - Added Fastboot to adb-1.0.31-mac.zip
I've seen several people having issues on OS X trying to use ADB since the release of Android 4.3. In my case ADB recognized my device, but each time I ran adb devices my device would be reported as offline. I downloaded the SDK from Google several times and always ended up with ADB v1.0.29 (4.2.2).
This will should solve your OS X & ADB issues if you're running Android 4.3. This ONLY includes the ADB & Fastboot executable files and is for Mac OS X ONLY. I, like many others, do not need the full SDK. If you're not an app developer, like myself, this is all you need to have ADB working on your machine.
For any new OS X users I'll add a how to just so you don't have to go search for it else where:
How to setup ADB + Fastboot on OS X
Note: This is for not for developers. This only includes ADB & Fastboot and is not the full Android SDK
Step 1: Download the ZIP containing ADB & Fastboot
Step 2: Extract the ZIP to the directory of your choice
Step 3: Optional Create an environment variable
1. Open Terminal
2. Type cd to take you to your home directory.
Code:
cd
3. Type touch .profile to create a hidden file in your home directory named .profile
Code:
touch .profile
4. Type open -e .profile to open the file you just created in TextEdit
Code:
open -e .profile
5. In the file, add the following:
Code:
export PATH=${PATH}:/PathToDirectoryWhereYouExtractedTheZIP
6. Save the file and close TextEdit, quit Terminal, and relaunch the Terminal
Step 4: In Terminal type adb devices, you should see your phone's corresponding serial number Ex: HXM1005HNF012345 device
Code:
adb devices
Note: If you choose not to create an environment variable from Step 3 it effects two things:
1. You will need to cd to the directory containing ADB each time you want to run ADB.
2. When executing ADB commands you will need to add ./ in front of ADB. Ex: ./adb devices
Dropbox Download
Alternate Download
wad3g, thanks for helping out.. but for some reason adb version is still showing 1.0.29 for me. I extracted the zip, removed the old adb and fasboot, restarted my machine.. ran kill-server, start-server but no luck.. any ideas? not sure what to do at this point.
mamba_nz said:
wad3g, thanks for helping out.. but for some reason adb version is still showing 1.0.29 for me. I extracted the zip, removed the old adb and fasboot, restarted my machine.. ran kill-server, start-server but no luck.. any ideas? not sure what to do at this point.
Click to expand...
Click to collapse
Hey, I was having the same issue so I took the adb and fastboot files from the SDK. You can copy them to usr/bin/ and run normally (as if the third step in the op's post had been completed), or by following the op's procedure if you're not an admin user.
kunjunk said:
Hey, I was having the same issue so I took the adb and fastboot files from the SDK. You can copy them to usr/bin/ and run normally (as if the third step in the op's post had been completed), or by following the op's procedure if you're not an admin user.
Click to expand...
Click to collapse
Thank you so much!
For some reason, that zip still reports ADB version 1.0.29.
I found the latest version (1.0.31) from https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/. It has zips for linux, mac and windows adb.
kunjunk said:
Hey, I was having the same issue so I took the adb and fastboot files from the SDK. You can copy them to usr/bin/ and run normally (as if the third step in the op's post had been completed), or by following the op's procedure if you're not an admin user.
Click to expand...
Click to collapse
thanks that works fine 4 me
Hi this is the guide to install Linux Ubuntu on your Chromebook either arm or Intel ones.
1. First you need to turn off the OS verification.
(Note:- On older devices there is a hardware button to switch between developer and normal mode. You can use that button to turn off OS Verification. The following steps are for newer versions of Chromebooks.)
2. Hold esc and refresh key and press the power button.
3. Then a screen appears with a scary notification about the chrome OS being damaged. Just ignore it and press ctrl+d.
4. Now another screen appears which tells us to press enter if we wish to turn off OS Verification, so we do it.
(Note:- By doing this all the local data will be cleared. Make sure you have backed up all your accounts and local data.)
5. Now wait for the chromebook to beep twice and reboot. It will take upto 15 minutes to boot into developer mode.
6. It will greet you with the first time boot screen. Take some time to fill up your details and create an account.
7. Now comes the installing part. Download this file named crouton from here http://goo.gl/fd3zc
8. Make sure it is present in your downloads folder.
9.Now press ctrl+alt+t to open a terminal (crosh).
10. Type shell and press enter
11. Now type in this command and press enter.
sudo sh -e ~/Downloads/crouton -r list
12. This will give you the list of recognized Debian, Kali and Ubuntu releases.
13. Now as we are aimed at installing Ubuntu we don't give our concern to Debian and Kali releases. Select a release which is not marked with * symbol as they are not supported. I prefer trusty because it is supported by a majority of devices.
14. Now type in this command and press enter.
sudo sh -e ~/Downloads/crouton -t help
15. This will give you the list of different desktop environments such as unity, kde, lxde, xfce etc.
16. I prefer xfce as it is a light desktop environment.
17. Now type in this command and press enter.
sudo sh -e ~/Downloads/crouton -r "your preferred Ubuntu release" -t "your preferred desktop environment"
18. If you want to follow my preferences type in this command and press enter.
sudo sh -e ~/Downloads/crouton -r trusty -t xfce
19. Wait until it completes and asks you for a username. Type in a username. Then it will ask you to type and re-type a password
(Note:- Don't worry if nothing appears on the screen while you type in the password because it is not any problem . It happens the same way on all Chromebooks)
20. Now type in the following command to boot into Ubuntu.
sudo startxfce4
21. If you log out or shut down your Chromebook. You need to first enter shell and then enter the command above to boot into Ubuntu.
( Note:- Each time you turn on your computer the OS Verification Screen appears for 30sec before booting Chrome OS. You can skip this by pressing ctrl+d.)
Was the experience nice. Finished playing with Ubuntu. Want to remove it and have only Chrome OS. Simply turn the OS Verification back on. This will overwrite any change that you have made including Ubuntu.
Great, but now explain how to change the primary boot from Chrome OS to Ubuntu
I have OP6 Pie, rooted using Magisk
I installed Termux,
when i open termux, I get $ prompt to type commands, I am able to use all normal commands of Linux like CD, ls, rm, python, apt update......, there is no issues at all
when I use type SU and granted root access
the command line changed to
:/data/data/com.termux/files/home/storage/shared
now if I type command apt-update, python, python2..., I get error that its not installed.
I mean to say why is it not allowing me to use python in root
One more thing, if I am in root mode and I type exit
I get $ prompt as usual and all commands including python works here
Have no idea about that