Related
Video-Tutorial:
http://bit.ly/HzzmUn
Step 1. Install JDK
Open Terminal and enter the following command(s), then enter your ubuntu login password followed by ‘y’ when prompted for yes/no.
Code:
$ sudo apt-get update
$ sudo apt-get install openjdk-6-jdk
Step 2. Install 32 bit libraries - Only for 64 bit users
On x64 systems you are required to install some 32-bit libraries or the android toolkit will not work. In a terminal write:
Code:
$ sudo apt-get install ia32-libs
Step 3. Download and Install Android SDK
Download the Android SDK. Choose the one for linux: android-sdk_r16-linux.tgz
Extract android-sdk_r16-linux.tgz and put the folder in your desired location. I recommend to put it under home/username/ | When using the terminal the same path is described as ~/
Step 4. Choose packages to install
First of all go to ~/android-sdk-linux/tools/
Right clic to android >> Properties >> Permissions
Make sure "allow executing file as a program" it's checked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once done close that window and doble click on the Android file, select Run in Terminal.
Download the tools as shown in the following picture:
Step 5. Check your device's permission
Now head over to the platform-tools directory
Code:
$ cd ~/android-sdk-linux/platform-tools
Check if you have permission for your device
Code:
$ ./adb devices
If you're getting the following, go on to Step 6.
Code:
List of devices attached
OR
List of devices attached
???????????? no permissions
If you're getting something like shown below or other random numbers with the word device next to it, congrats! You can now use ADB. Now go on to Step 7.
Code:
List of devices attached
0123456789ABCDEF device
Step 6. Adding USB Vendor ID of your device
Open HOME folder and enable Show Hidden Files:
Open .android folder >> right click >> Create New Document >> Empty Document, name it adb_usb.ini and open it. Put the following on it:
Save & close the window
Then unplug your NT and plug it again (From the NT usb port, not PC). Now to check if it works...
Code:
$ ./adb devices
You should be getting something similar to the following line:
Code:
List of devices attached
0123456789ABCDEF device
Congrats! Now you can use ADB in Ubuntu! Now hop on to Step 7!
Step 7. Create path for ADB
NOTE: while using adb on Linux you'll need to type ./adb to execute adb commands unless you create a path in ~/.bashrc. In a terminal write:
Code:
$ sudo gedit ~/.bashrc
Add the following line at the very end of the file. Once you're done, save and exit.
Code:
# Android tools
export PATH=~/android-sdk-linux/platform-tools:~/android-sdk-linux/tools:$PATH
Then in a Terminal run this command to reload your .bashrc:
Code:
source ~/.bashrc
Now you can just run adb without put ./ before every command.
~ Veronica
great
thank you very much!!!
Can this help with porting and building from source
______________________________________________
Sent from my SPH-D710-EPIC-4G-TOUCH-using Tapatalk
Anon9mouz said:
Can this help with porting and building from source
______________________________________________
Sent from my SPH-D710-EPIC-4G-TOUCH-using Tapatalk
Click to expand...
Click to collapse
this helps partly it just gives you the basics to make adb work but if you want to develop then you will need other tools, to setup ubuntu for development/theming then use this script.
~ Veronica
lavero.burgos said:
this helps partly it just gives you the basics to make adb work but if you want to develop then you will need other tools, to setup ubuntu for development/theming then use this script.
~ Veronica
Click to expand...
Click to collapse
O ok thanks ill check it out
______________________________________________
Sent from my SPH-D710-EPIC-4G-TOUCH-using Tapatalk
Update april/10
Added Video-Tutorial
~ Veronica
Followed your video tutorial, but ubuntu adb still doesn`t see my device, while at the very same time it perfectly works under windows. The only step i missed is step 2, terminal is saying ia32-libs no candidate for installation(translating from russian, might be smth different)
PS: USB debugging is enabled in my nook settings dev
Devol said:
Followed your video tutorial, but ubuntu adb still doesn`t see my device, while at the very same time it perfectly works under windows. The only step i missed is step 2, terminal is saying ia32-libs no candidate for installation(translating from russian, might be smth different)
PS: USB debugging is enabled in my nook settings dev
Click to expand...
Click to collapse
cd to the folder where adb is located and type:
$ sudo ./adb devices
~ Veronica
I followed your video, so i`ve tried sudo aswell...may be i can just go on with windows adb?
Actually i`ve tried it already, there are only 7 files for 8gb partitions, i`ve copied one of them to my 4th big sdcard partition, and tried to dd if...bla bla bla... = writes error: no space left on device
Devol said:
I followed your video, so i`ve tried sudo aswell...may be i can just go on with windows adb?
Actually i`ve tried it already, there are only 7 files for 8gb partitions, i`ve copied one of them to my 4th big sdcard partition, and tried to dd if...bla bla bla... = writes error: no space left on device
Click to expand...
Click to collapse
hmm did you mount /sdcard in CWM? the cwm recovery by @meghd00t works now for 8GB NT... anyways that's ok you can copy it to /data instead of sdcard go one by one, i don't know what exactly you have done to your device but i recommend to just use the necessary partitions.
~ Veronica
No, i`m booting of cm7 sd card, used a file manager to go to internal emmc, looks like alot of files there...most 0kb, my mmc0p7 is in dev\block, but not copied fully, only around 208mb(full size is 300mb somthing)...file manager doesn`t allow to delete anything...
Devol said:
No, i`m booting of cm7 sd card, used a file manager to go to internal emmc, looks like alot of files there...most 0kb, my mmc0p7 is in dev\block, but not copied fully, only around 208mb(full size is 300mb somthing)...file manager doesn`t allow to delete anything...
Click to expand...
Click to collapse
no, you can't copy from a file manager the partition images neither remove them for security it is why you use dd from CWM to copy the partition images while non of them are IN USE!!!
advice don't be playing around with the partition table, please use @meghd00t recovery he has posted zip with all you need. Boot into CWM from sdcard run the commands.
PS: we're going offtopic in this thread
~ Veronica
Nope, it(meghd00t Repartition, Reformat, Restore and Rescue SDcard) also stops at 25% while restoring factory defaults at the last step...(
Ok, my actions that lead to this situation: rooted nook with sd card method for 8gb, installed recovery flasher apk, flashed cwm, followed steps(wiping data, daviks - here it hang up, then rebooted, after that tried flashing cm7 which was a big mistake, wish guys had a word in the topic that it`s not meant for 8gb...and the result is i cant boot from internal mem, only sd. btw, cwm acted strangly, it could hang on all of a sudden, or work for a while, cwm was internally installed, now i`ve removed it)
If we are offtoping, lets move to some other thread...
PS: for some reason nook doesn`t boot from cwm sd(cable plugged, part active fat32)...basicly it will boot only from cm7 rom and meghd00t recovery images.
@Devol i replied to you here
~ Veronica
Great Work!
Thanks a lots for such a detailed guide.
You can also drop the adb and fastboot binaries into /usr/bin and use both commands without needing to CD to the /tools folder in the SDK. Just don't forget to change the permissions.
cant get past the checking phone permission stage! keeps saying no permissions. if it helps any, im using ubuntu 12.04. im gonna reboot and try in windows. is there any benefit to using adb in linux over windows anyway?
ridleyj329 said:
cant get past the checking phone permission stage! keeps saying no permissions. if it helps any, im using ubuntu 12.04. im gonna reboot and try in windows. is there any benefit to using adb in linux over windows anyway?
Click to expand...
Click to collapse
For when you hard brick your device your device yes, you need linux and adb working or for those like me that prefer to use linux over windows daily.
~ Veronica
http://www.omgubuntu.co.uk/2012/05/...m=feed&utm_campaign=Feed:+d0od+(OMG!+Ubuntu!)
A little off topic but awesome. Any one know how to switch between java 6 and 7 on ubuntu? I need 7 for minecraft and 6 for android sdk. Im on 12.04.
Sent from my DROID RAZR using xda premium
Thanks alot just got this working on ubuntu 12.04 with no issues. Just make sure you complete a:
apt-get update && apt-get upgrade
apt-get dist upgrade prior to any of the steps
Android SDK - Powerful tool and easy to set up for use with your HTC One M8
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Reason that you would want to use Android SDK is because its very easy, it's well updated and it just WORKS! There is much more use with HTC devices with adb then with Samsung when it comes to the daily things like splash screens, radio updates, firmware. You will be dealing a lot with the bootloader and fastboot flashing. So to help out, I will post a helpful guide to help you get started for use with the HTC One M8.
Click to expand...
Click to collapse
USB 3.0 Information if Needed
USB 3.0 Windows 8 Solution Link 1
USB 3.0 Windows 8 Solution Lin 2 - Found in above thread
Part 1. Follow These Steps Below - (Preparation)
1. Download Android SDK For Windows
2. Click the
either the 32bit version or 64bit version
3. Create a folder in the C: and name it Android. See below
4. Place adt-bundle-windows in the Android Folder you just created. Use WinZip, WinRAR or 7-Zip to extract the contents inside the folder. See Below
5. Once extracted, Double click SDK Manager and instal all 4.4.2 and 4.3 items and under tools (SDK Tools and Platform Tools). See Picture Below
6. After all packages are installed and updated, download the latest HTC Sync Manager and install once download completes
7. Once Sync Manager completes installation process, go to control panel and uninstall HTC Sync Manager only, you will see HTC Driver in there as well (LEAVE IT THERE)
8. Important, make sure you enable developer options and turn on USB Debugging. Instructions Below if you are unsure how to do that
1. Go to Settings > About > Software information > More > Tap Build Number 5x
2. Once you get notification saying Developer options is unlocked go back to > settings
3. Click Developer options
4. Add check in the box USB Debugging
9. Plug phone into the computer and let it install all the drivers, you should see pop ups.
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\sdk\platform-tools
2. In Command prompt type
Code:
adb devices
3. If your output shows your device attached like below, then you are good to go!!!
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\sdk\platform-tools
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
reserved if needed
Or you can install just adb and fastboot from http://forum.xda-developers.com/showthread.php?p=48915118
Sent from my HTC One_M8 using Tapatalk
OP Updated
Updated OP
1. Added Environment Variables to no longer have to Change Directory
2. Cleaned up OP
3. Added Thanks
Rojax said:
Or you can install just adb and fastboot from http://forum.xda-developers.com/showthread.php?p=48915118
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thanks for pointing that out but it is kind of unnecessary to do after I put all this together, it took time.
This is easy as that period and it's constantly updated, all you have to do is run sdk manager and run updates, nothing else required once set up. This is streamlined for just our devices since it also has directions for drivers for our device. Otherwise I would have put it under Android and general...
The tool you suggest by the way is awesome. Appreciate you taking the time to share it, FYI it's updated via sdk, the op stated where he pulls the updates for adb from.
So tomatoe, tomato, please let the users decide which tool they would like to use.
Thanks
Sent from my HTC6525LVW using Tapatalk
The guide is great, I was just listing an alternative (much smaller) download. Thanks for sharing this to help our community grow
Sent from my HTC One_M8 using Tapatalk
Rojax said:
The guide is great, I was just listing an alternative (much smaller) download. Thanks for sharing this to help our community grow
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
No problem and thanks for sharing. Appreciate it
Sent from my HTC6525LVW using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Okay so after owning this tablet for a few days and running CM I wanted to install a Linux distribution on my Nexus 7 ( grouper) so I could use some Ubuntu image editing programs. So I installed Ubuntu and Ubuntu touch and found them extremely slow for a quad core tablet and the old always have to force reboot my device all the time. And so I decided to sit down today and work on Ubuntu 13.04 base and tweak it and make it run better on this amazing 2012 device.!!! And since I been a Ubuntu person since the 8.0.x days and having all the experience I have with Ubuntu I finally got it to a state were it runs beautifully on our nexus 7. And am going to share how to do so today.. Guide will be quite lengthy because I will describe step by step on how I got to the point with my Nexus 7.
Requirements :
- Nexus 7 (grouper)
- Fully charged device
- OTG cable
- Wired or Bluetooth mouse
Step 1 : Getting Multirom
First thing you want to do is install multirom, probably the most genius idea for this device yet.
1. Download MultiRom from Here.!!
2. Open the app and highlight these 3 options and install them and proceed to follow the apps directions. After that proceed to step 2.
Step 2 - Installing Ubuntu 13.04 via MultiRom
The reason I choose this method is so you can always return back to Android at the end of the day. And can easily remove Linux without the assistance of a computer.
1. Download Ubuntu 13.04 image for nexus 7 from Here.!!
2.*Place the image as it is in the internal memory of N7 or to USB flash drive
3. Reboot to recovery and choose Advance>Multirom>Add Rom*and choose Ubuntu*as ROM type.
4.*Then select the Ubuntu's image and confirm. Clean installation of Ubuntu is 1.5gb big, and takes a while (10 minutes?) to install.
5. Once complete boot Ubuntu by choosing it in MultiRom boot up manager and proceed to finish the installation.
Step 3 : Installing KDE Kubuntu Active Desktop
The reason we want to install KDE Kubuntu Active Desktop is because Unity in Ubuntu is definitely not ready for optimized use on a tablet. Where in my opinion KDE is optimized for tablets. Plus to me KDE is more easier for a new Linux user to understand than how unity is set up.
1. This command installs the basic minimal files to run the newer desktop. Download 200+mb
Code:
sudo apt-get install kde-plasma-desktop kubuntu-default-settings kde-config-gtk-style gtk3-engines-oxygen
2. Eventually, halfway through the installation, the program will ask you whether you want to change display managers. It is recommended that you stick with Lightdm, so that the onscreen keyboard remains the same.
Next, configure Lightdm to start KDE by default instead of Unity:
Code:
sudo /usr/lib/lightdm/lightdm-set-defaults -s kde-plasma
3. Finally, log out (rather than restarting or turning off), tap the Ubuntu icon next to the user name, and choose*KDE Plasma Workspaces. Then type in your password and log in. If you need an onscreen keyboard to type, tap the Accessibility Icon (a spread eagled man in a circle), and click*Show Onboard.
KDE will now be started. However, it probably needs to be configured for optimal performance.
Step 4 : Removing Ubuntu's Unity & Desktop
The reason why we would want to remove unity is because once your on KDE Kubuntu Active why would you still want Ubuntu's desktop that's slow as hell. so enter these commands 1 by 1 to free up disk space and remove un-needed files.
1.
Code:
sudo apt-get remove unity unity-2d unity-2d-panel unity-2d-spread unity-asset-pool unity-services unity-lens-files unity-lens-music unity-lens-applications gir1.2-unity-5.0 unity-common indicator-sound indicator-power indicator-appmenu libindicator7 indicator-application indicator-datetime indicator-messages libnux-2.0-0 nux-tools libunity-misc4 unity-2d-common
2.
Code:
sudo apt-get autoremove --purge unity unity-common unity-services unity-lens-\* unity-scope-\* unity-webapps-\* gnome-control-center-unity hud libunity-core-6\* libunity-misc4 libunity-webapps\* appmenu-gtk appmenu-gtk3 appmenu-qt\* overlay-scrollbar\* activity-log-manager-control-center firefox-globalmenu thunderbird-globalmenu libufe-xidgetter0 xul-ext-unity xul-ext-webaccounts webaccounts-extension-common xul-ext-websites-integration gnome-control-center gnome-session
3.
Code:
sudo rm /usr/lib/thunderbird-addons/extensions/[email protected]
Step 5 : Removing Un-Needed Apps [OPTIONAL]
Once done removing ubuntu unity and desktop you may want to remove some ubuntu apps like I did, helps remove some UN-needed apps that you should be using on a tablet PC.
1. Firefox Web Browser
Code:
sudo apt-get remove firefox
2. IM client - Empathy
Code:
sudo apt-get remove empathy
3. Disk Burner - Brasero
Code:
sudo apt-get remove brasero
4. Torrent Client - Transmissions
Code:
sudo apt-get remove transmissions-gtk
5. Scanner
Code:
sudo apt-get remove simple-scan
6. Mines - game
Code:
sudo apt-get remove gnomine
7. Sudoku - game
Code:
sudo apt-get remove gnome-sudoku
8. Text editor - gedit ( roaming cause we have kwrite )
Code:
sudo apt-get remove gedit
9. Document Viewer
Code:
sudo apt-get remove evince
Sent from my Nexus 7 using Tapatalk
References and Q&A :
Coming Soon
Credits :
Coming Soon
Nice, very useful.
Thanks! I will follow up when I get WiFi at my house and share stuff on tips keeping things running fast
Sent from my One X using XDA Free mobile app
Thanks for the tutorial.
Does this work on f2fs formatted storage ?
Because I get an error when booting ubuntu:
Code:
mounting dev/mmcblk0p9 on /root failed: no such device
darkchazz said:
Thanks for the tutorial.
Does this work on f2fs formatted storage ?
Because I get an error when booting ubuntu:
Code:
mounting dev/mmcblk0p9 on /root failed: no such device
Click to expand...
Click to collapse
Idk I run a ext4 file syste!
Sent from my Nexus 7 using Tapatalk
xXminiWHOOPERxX said:
Idk I run a ext4 file syste!
Click to expand...
Click to collapse
Never mind, I got it working.
It's not usable without a physical mouse though. Because there is a bug where the left mouse button gets permanently stuck pressed down until you restart.
darkchazz said:
Never mind, I got it working.
It's not usable without a physical mouse though. Because there is a bug where the left mouse button gets permanently stuck pressed down until you restart.
Click to expand...
Click to collapse
on f2fs partition... how?
wejgomi said:
on f2fs partition... how?
Click to expand...
Click to collapse
no. I reformatted to ext4
darkchazz said:
no. I reformatted to ext4
Click to expand...
Click to collapse
Plan to add more to the guide, just keep breaking the OS when I start removing some u core files, trying to slim core down so it's less on battery and a lot smoother... Have figure out how to Fox rotation but screen cordinates dont change so your forced to use a mouse
Sent from my HTC One mini using Tapatalk
not working i get only 404 not found.
Gothic4 said:
not working i get only 404 not found.
Click to expand...
Click to collapse
I believe Ubuntu 13.04 has been moved to the old-releases repo. Because of that you get 404 error
From terminal type
sudo gedit /etc/apt/sources.list
Tap Search, Replace
For "Search for" enter http://ports.ubuntu.com/ubuntu-ports/
For "Replace with" enter http://old-releases.ubuntu.com/ubuntu/
Tap Replace, tap Save.
From terminal refresh new repos
sudo apt-get update
I have another question. How to make Onscreen keyboard to run automatically in KDE? And how to rotate screen to landscape?
Thanks
So.. is no way to get it working on f2fs? is a pain to reformat the whole tablet again
i've installed Kubuntu as written but now i can't login to my account!!
only guests account can be accessed even tho the screem is only portrait
now i wonder if it's possible to delete ubuntu without tripping anything to start over
Please close.! As I no longer have my nexus 7.
xXminiWHOOPERxX said:
Please close.! As I no longer have my nexus 7.
Click to expand...
Click to collapse
I just saw this 3d and wanted to try...bad news
Hope someone will continue this 3d
alematt said:
I just saw this 3d and wanted to try...bad news
Hope someone will continue this 3d
Click to expand...
Click to collapse
https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_installation
That's the official guide
matyhew said:
https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_installation
That's the official guide
Click to expand...
Click to collapse
That's for plasma active. Isn't this thread for Ubuntu?
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 10:33 PM ---------- Previous post was at 10:31 PM ----------
I tried to do what's the op says. Updated repositories n ****. But I can see the console with the keyboard open. So I can't see what I'm typing to install the last few steps lol. I may not be clear in describing but I'm stuck and its frustrating to type.
Thanks for your time though op
Sent from my Nexus 7 using XDA Premium HD app
What the heck is all this about?
So, you all know that unlocking a Nexus device is usually pretty straight forward, especially if you're on Ubuntu; you're used to just install android-tools-fastboot and android-tools-adb from the default repos, using sudo fastboot oem unlock, and being on your merry way.
Unfortunately, that's been a bit of a pain with the new 6P for multiple reasons; the default Ubuntu 14.04+ repositories don't yet have the latest adb and fastboot binaries (which you need because the unlock command is now totally different), and the Android SDK Manager is kind of a piece of crap and needs to be beaten into submission before it works for you. I wrote this guide after figuring it out because I don't use Windows and don't ever use it unless there is simply no other way.
Yes, I could just post the adb and fastboot binaries, but this is Linux. We use it to better understand how computers work and ultimately learn.
This process will take you 5 minutes.
What I'm assuming about you
You know what a terminal is and how to use it
You are on Ubuntu 14.04+ 64bit
You have Java already installed
You have already booted your phone, gone into Developer Settings, and turned on "OEM Unlocking"
You're smart enough to not blame me for ruining your new phone (which won't happen) or your Ubuntu installation
Let's kick this off.
Install the Dependencies
The official Android SDK guidelines specify that you need several 32bit dependencies before proceeding. Let's get those set up.
Code:
[B]sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libncurses5:i386 libstdc++6:i386 zlib1g:i386 -y[/B]
That's it, dependencies are installed.
Grab the SDK
Pop open your terminal and grab the SDK:
Code:
wget http://dl.google.com/android/android-sdk_r24.4.1-linux.tgz
Extract it:
Code:
[B]tar -xzf android-sdk_r24.4.1-linux.tgz[/B]
The SDK is downloaded and extracted.
Open and Configure the SDK Manager
Change directory to the tools directory
Code:
[B]cd android-sdk-linux/tools/[/B]
Execute the "android" executable you see in there:
Code:
[B]./android[/B]
Oh no! We immediately run into an issue connecting to Google's server.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's okay, we can easily remedy that. Move your mouse up to your task bar to show your menu, and go to Options.
Uncheck "Use download cache", click on the "Clear cache" button, and then check the box for "Force https:// sources to be...".
Hit close, and reload. Voila! We now have ALL THE THINGS ready for us to grab.
Download the Platform Tools!
Go ahead and check the box for the latest Android platform tools (23.0.1) and hit "Install 1 Package".
When prompted, fill in the bubble to accept the license, and hit "Install".
You'll likely run into this error, which says it can't kill the adb server. This makes sense because there isn't yet an adb server running for it to kill. Ignore it.
Congrats! You've now installed the platform tools. Lets close the SDK.
Put those binaries where they belong!
From here on, you can just execute the adb and fastboot binaries using ./adb and ./fastboot, but come on now, let's make adb and fastboot globally accessible binaries to use so you don't have to cd into the Android tools directory each time you want to use it.
Go back to your terminal, and cd into the newly-created platform-tools folder. Assuming your terminal is where we left it when we launched the Android SDK, this is what you'll run:
Code:
[B]cd ../platform-tools/[/B]
Use "ls -l" to list the contents, you should see an adb and fastboot binary.
Code:
[B]total 3360
drwxrwxr-x 5 user user 4096 Nov 25 16:42 ./
drwxrwxr-x 7 user user 4096 Nov 25 16:42 ../
[COLOR="Magenta"]-rwxrwxr-x 1 user user 1221540 Nov 25 16:42 adb*[/COLOR]
drwxrwxr-x 2 user user 4096 Nov 25 16:42 api/
-rwxrwxr-x 1 user user 58920 Nov 25 16:42 dmtracedump*
-rwxrwxr-x 1 user user 211200 Nov 25 16:42 etc1tool*
[COLOR="magenta"]-rwxrwxr-x 1 user user 556700 Nov 25 16:42 fastboot*[/COLOR]
-rwxrwxr-x 1 user user 11427 Nov 25 16:42 hprof-conv*
drwxrwxr-x 2 user user 4096 Nov 25 16:42 lib/
-rw-rw-r-- 1 user user 220534 Nov 25 16:42 NOTICE.txt
-rw-rw-r-- 1 user user 16508 Nov 25 16:42 source.properties
-rwxrwxr-x 1 user user 1109318 Nov 25 16:42 sqlite3*
drwxrwxr-x 3 user user 4096 Nov 25 16:42 systrace/
[/B]
Copy these binaries to your /usr/bin/ folder.
Code:
[B]sudo rsync -ah adb /usr/bin/
sudo rsync -ah fastboot /usr/bin[/B]
Now they're in your bin folder, let's give them the proper permissions. Change directory to /usr/bin/.
Code:
[B]cd /usr/bin/[/B]
Let's give them the proper permissions.
Code:
[B]sudo chmod 755 adb fastboot[/B]
All done! Close your terminal window and open it again. Type sudo fastboot and sudo adb and you should see the help pages for both.
Go ahead and unlock your Nexus 6P now, using the command sudo fastboot flashing unlock. Done!
Word of advice, I assume you know how to flash TWRP, but make sure you do it in this order to prevent any bricking:
Let the device boot once after unlocking.
Turn off phone, manually enter bootloader.
Flash the TWRP image (sudo fastboot flash recovery twrp-image-name-goes-here.img)
From bootloader, boot into recovery. Allow TWRP to write to /system.
Reboot, and when rebooting DO NOT ALLOW TWRP TO INSTALL SUPERSU.
Now, reboot back into recovery and head off to the races.
Conclusion + FAQs
I hope this guide was useful to you. Here's some FAQs to help out.
"Sick guide bro, but what theme are you using??"
GTK: Arc Darker Theme
Icon Theme: Numix Circle
Font: Myriad Pro, Myriad Pro Semibold for WIndow Titles
Awesome work...a lot of work! This is the wave of the future on the go...
I had referenced this ground breaking thread by chamatht before Marshmallow.
galaxys said:
Awesome work...a lot of work! This is the wave of the future on the go...
I had referenced this ground breaking thread by chamatht before Marshmallow.
Click to expand...
Click to collapse
I did notice that, but I wanted people to be able to grab the binary themselves so they know exactly where it came from. :good:
Nice work, but manually copy binaries into /usr/bin is actually a very bad idea... Will conflict soon or later with your package manager.
Keep your binaries where ever you downloaded them, and learn how to tweak your $PATH variable instead (hint :it's easy)
@LiquidSolstice
very good guide. thanks a lot.
effraie said:
Nice work, but manually copy binaries into /usr/bin is actually a very bad idea... Will conflict soon or later with your package manager.
Keep your binaries where ever you downloaded them, and learn how to tweak your $PATH variable instead (hint :it's easy)
Click to expand...
Click to collapse
More than a hint, the solution to do it clean
instead copying binaries to /usr/bin (which is bad, dangerous and must be discouraged), keep your downloaded binaries where you want (people commonly use /opt or $HOME/bin ), and add that place to your $PATH, by adding a line such :
Code:
export PATH=$PATH:$HOME/bin/
or
Code:
export PATH=$HOME/bin/:$PATH
the position of $HOME/bin/, before or after $PATH, will determine the priority, if a binary with the same name is found in :$HOME/bin/ and your regular $PATH.
You can choose any place : $HOME/bin/ is usual, but :/home/my/fancy/name will work the same, as long you correctly adjust permissions
effraie said:
More than a hint, the solution to do it clean
instead copying binaries to /usr/bin (which is bad, dangerous and must be discouraged), keep your downloaded binaries where you want (people commonly use /opt or $HOME/bin ), and add that place to your $PATH, by adding a line such :
Code:
export PATH=$PATH:$HOME/bin/
or
Code:
export PATH=$HOME/bin/:$PATH
the position of $HOME/bin/, before or after $PATH, will determine the priority, if a binary with the same name is found in :$HOME/bin/ and your regular $PATH.
You can choose any place : $HOME/bin/ is usual, but :/home/my/fancy/name will work the same, as long you correctly adjust permissions
Click to expand...
Click to collapse
Eh, rather than dealing with exports, in this specific case, I would personally rather manually move the binary myself, and when the default repos actually finally update to the latest platform tools, I'll delete them before installing from the repo.
I appreciate the advice though!
Well, if you copy the binaries in the place package manager install regular software, you'll have to purge your distribution adb package, so you won't have any notification when it will be updated.
Export one variable is not so hard... Only one line to copy in your ~.bashrc, and then you can keep both, while keeping your system clean, not messing with your package manager, and being notified when the adb and fastboot packaged in your distribution is updated.
Obviously, you can do whatever you want, but i really can't see any advantage with your solution. (while I can see many possibilities of messing around and breaking your package manager or your system)
Quick question,my Ubuntu is 32bit will this still work? Honestly kinda confused when it comes to the 6p lol command changes and what not got me a little worried.
all good, for me simply downloading dependencies(after a gernal update) then the fastboot flashing unlock worked for me, Ubuntu 15.10 32bit.
Not sure if mentioned here but you can download adb tools and it gives you the adb tools through the terminal so you can do all the commands as you would on a windows machine. http://www.webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html this is an old guide but the ppa is up to date.
xSilas43 said:
Not sure if mentioned here but you can download adb tools and it gives you the adb tools through the terminal so you can do all the commands as you would on a windows machine. http://www.webupd8.org/2012/08/install-adb-and-fastboot-android-tools.html this is an old guide but the ppa is up to date.
Click to expand...
Click to collapse
No. That PPA does not have up to date android-tools. Check the versions here. It doesn't have the latest fastboot binary, which is required if you want to be able to unlock your 6P. The command is no longer "fastboot oem unlock".
LiquidSolstice said:
No. That PPA does not have up to date android-tools. Check the versions here. It doesn't have the latest fastboot binary, which is required if you want to be able to unlock your 6P. The command is no longer "fastboot oem unlock".
Click to expand...
Click to collapse
They worked fine for me but here is a more updated ppa I believe. http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
xSilas43 said:
They worked fine for me but here is a more updated ppa I believe. http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Click to expand...
Click to collapse
You were able to use "fastboot flashing unlock" with the Webupd8 PPA? I'm not so sure I believe that. The PPA you linked to in the Lifehacker article is using the same 2 year old tools package as well, man. https://launchpad.net/~phablet-team/+archive/ubuntu/tools
Not sure why you wouldn't just properly grab the latest tools.
LiquidSolstice said:
You were able to use "fastboot flashing unlock" with the Webupd8 PPA? I'm not so sure I believe that. The PPA you linked to in the Lifehacker article is using the same 2 year old tools package as well, man. https://launchpad.net/~phablet-team/+archive/ubuntu/tools
Not sure why you wouldn't just properly grab the latest tools.
Click to expand...
Click to collapse
To unlock I used a windows tool but have used the fastboot tools for various other things, I was unaware they were all so outdated thanks for the info!
great tutorial
working fine on 16.04
might need to install java to run sdk
Code:
sudo apt-get install default-jre
Hi everyone! I'm on cinnamon and I'm trying to unlock my 6p but when typing "fastboot flashing unlock" it gives me the list of fastboot commands. I downloaded the platform tools from the google site and installed adb and fastboot commands (or whatever they are ) with:
sudo apt-get install android-tools-fastboot
sudo apt-get install android-tools-adb
Adb devices and fastboot devices are working tho. I have even installed java with the command posted by dogmatism. Am I missing something? TIA
hughfollett said:
Am I missing something? TIA
Click to expand...
Click to collapse
Yes, reading the OP
What you downloaded is too old.
If you absolutely want packages, you need to follow testing or unstable --> https://tracker.debian.org/pkg/android-platform-system-core. I only know debian.
rchtk said:
Yes, reading the OP
What you downloaded is too old.
If you absolutely want packages, you need to follow testing or unstable --> https://tracker.debian.org/pkg/android-platform-system-core. I only know debian.
Click to expand...
Click to collapse
But why would google release some outdated files?
hughfollett said:
But why would google release some outdated files?
Click to expand...
Click to collapse
Google isn't doing the debian packaging. A maintainer is trying to, in his spare time.
Also debian distros follow stable or testing/unstable. Stable packages stay a long time unless they contain grave or security bugs. People following stable seek.. stable stuffs rather than newest packages. I run unstable to get rather recent packages.
And even this said, the fastboot and adb packages don't seem to get the attention they should deserve.
With the release of v3.2.1.0, there are many improvements to the Linux version of the kitchen compared to the native Windows version. WSL2 on Windows 10 is the perfect way to run the Linux kitchen on Windows. Installation takes a few more steps, but it will be worth it.
Below you will find a basic guide to get the kitchen running on WSL2. This guide will work with Ubuntu/Debian variants. Other variants will need to adjust the dependencies command for your chosen distro. I will update this post as needed.
Requirements: Donate kitchen, 64-bit Windows 10 (version 1903 or higher).
STEP 1:
Install WSL2 on Windows 10.
How to Install WSL 2 on Windows 10 (Updated) - OMG! Ubuntu
If you want to try out the improved Windows Subsystem for Linux 2 (aka WSL 2) in the latest Windows versions here's how — I cover everything you need to
www.omgubuntu.co.uk
or the official Microsoft documentation
Install WSL
Install Windows Subsystem for Linux with the command, wsl --install. Use a Bash terminal on your Windows machine run by your preferred Linux distribution - Ubuntu, Debian, SUSE, Kali, Fedora, Pengwin, Alpine, and more are available.
docs.microsoft.com
STEP 1 B (Optional):
Now that WSL is installed, you can move it to a different drive if you want. Some people might want WSL on the Windows D:\ drive for example. Here is how:
Close your WSL terminal.
Open cmd.exe, powershell, or Windows terminal
Code:
wsl.exe -l -v
NAME STATE VERSION
* Ubuntu Running 2
The first command will show you the distro name you need to use in the following commands. "Ubuntu" in this example, but yours may be named differently.
Code:
wsl.exe --export Ubuntu C:\WSL_backup.tar
wsl.exe --unregister Ubuntu
wsl.exe --import Ubuntu D:\wsl C:\WSL_backup.tar
STEP 2:
Open WSL2 terminal and install dependencies
Code:
sudo apt-get update
sudo apt-get install unzip default-jre
Do not close the WSL2 terminal. Leave it open until the end of the guide
STEP 3:
Download the kitchen into your WSL2 home directory.
First we need to create a "kitchen" directory and find the path to it from Windows so you know where to save the kitchen zip.
In the WSL2 terminal, do the following:
Code:
mkdir -p kitchen
cd kitchen
explorer.exe .
IMPORTANT! Do not forget the dot (.) at the end of the last command.
At this point, Windows explorer should have opened to the new "kitchen" directory you created in the terminal. Take note of this location. This is where we want to download and install the kitchen.
Time to head over to the kitchen downloads page and grab the latest Linux version zip. Save to the "kitchen" directory we found earlier.
STEP 4:
Extract the kitchen.
Back in WSL2 terminal, run the following (replace v3.2.1.0 with the version you are installing)
Code:
unzip SuperRs-Kitchen_Linux-64_v3.2.1.0.zip
IMPORTANT! Do not extract the kitchen using windows tools or you will have issues.
STEP 5:
Run the kitchen.
Code:
./superr
RUNNING THE KITCHEN LATER:
Run the kitchen after closing WSL2.
Open WSL2 terminal and run the following:
Code:
/path/to/kitchen/superr
reserved
Small tips to find Home directory for newbie
1.win 10 must be updated firt to Latest (at least 1903 or up) to install WSL2
2.Find home directory
Once Install ubuntu - Open it from start menu - and type and run
Code:
explorer.exe .
This will open home directory in windo explorer.
I install WSL2, but how I open the kitchen
ishay_shlomo said:
I install WSL2, but how I open the kitchen
Click to expand...
Click to collapse
Great, you finished STEP 1 in the guide. Now move on to STEP 2
Its showing "platform not supported" how do we fix that ?
mrsmileisgod said:
Its showing "platform not supported" how do we fix that ?
Click to expand...
Click to collapse
As mentioned in the thread title, this guide is for the donate kitchen. The free kitchen does not work in WSL.
edit: I added donate kitchen to the requirements in the OP to make this more clear.
edit2: I added text to free kitchen OP stating it will not work in WSL.
SuperR. said:
As mentioned in the thread title, this guide is for the donate kitchen. The free kitchen does not work in WSL.
edit: I added donate kitchen to the requirements in the OP to make this more clear.
edit2: I added text to free kitchen OP stating it will not work in WSL.
Click to expand...
Click to collapse
oh my bad...i didn't see that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
why？？？
This prompt appears after running and the previous steps have been completed
xingkong futur said:
View attachment 5171147why？？？
This prompt appears after running and the previous steps have been completed
Click to expand...
Click to collapse
As stated in the screenshot you sent, you are running the kitchen as root and you should not be. Your terminal is actually running as root so anything you do there is done as root. Run WSL2 terminal as a normal user and then run the kitchen.
I'm not knowlegable about this sort of thing but I can't get jre installed.
Tulsadiver said:
I'm not knowlegable about this sort of thing but I can't get jre installed.
View attachment 5178975
Click to expand...
Click to collapse
That is odd. Maybe try apt instead of apt-get:
Code:
sudo apt install default-jre
Otherwise, maybe try Ubuntu 18.04 instead. I have not tested 20.04.
SuperR. said:
That is odd. Maybe try apt instead of apt-get:
Code:
sudo apt install default-jre
Otherwise, maybe try Ubuntu 18.04 instead. I have not tested 20.04.
Click to expand...
Click to collapse
That didn't work either. I'll try 18.04
SuperR. said:
That is odd. Maybe try apt instead of apt-get:
Code:
sudo apt install default-jre
Otherwise, maybe try Ubuntu 18.04 instead. I have not tested 20.04.
Click to expand...
Click to collapse
sudo apt install default-jre didn't work. I installed 18.04 but got same error. apt-get update worked. Now I get a permission error when running the kitchen. I have v3.2.1.1 installed.
Edit: tried v3.2.1.0 also. Same result.
Tulsadiver said:
sudo apt install default-jre didn't work. I installed 18.04 but got same error. apt-get update worked. Now I get a permission error when running the kitchen. I have v3.2.1.1 installed.
Edit: tried v3.2.1.0 also. Same result.
View attachment 5179335
Click to expand...
Click to collapse
How did you unpack the kitchen zip? Did you follow the instruction in step 4 above? It sounds like you used a Windows tool to unpack the zip, and this will cause permission issues.
edit: According to my server log, it appears you are running WSL1, not WSL2.
edit2: you should remove the space from your project name. The kitchen does not allow this so you must have created the project directory manually. I am not sure if this will cause problems, but it certainly could.
SuperR. said:
How did you unpack the kitchen zip? Did you follow the instruction in step 4 above? It sounds like you used a Windows tool to unpack the zip, and this will cause permission issues.
edit: According to my server log, it appears you are running WSL1, not WSL2.
edit2: you should remove the space from your project name. The kitchen does not allow this so you must have created the project directory manually. I am not sure if this will cause problems, but it certainly could.
Click to expand...
Click to collapse
I used ubunto to unzip as per instructions, installed WSL2 and tried step 3 to set WSL2 as default. tried step 5 to change from WSL1 to WSL2 and it indicated "no such distribution". I also tried removing the space to no avail. I've probably hosed everything at this point...
According to Microsoft official WSL2 documentation, you need to meet these Windows requirements:
For x64 systems: Version 1903 or higher, with Build 18362 or higher.
For ARM64 systems: Version 2004 or higher, with Build 19041 or higher.
Builds lower than 18362 do not support WSL 2.
Does your system meet these requiements?
SuperR. said:
According to Microsoft official WSL2 documentation, you need to meet these Windows requirements:
For x64 systems: Version 1903 or higher, with Build 18362 or higher.
For ARM64 systems: Version 2004 or higher, with Build 19041 or higher.
Builds lower than 18362 do not support WSL 2.
Does your system meet these requiements?
Click to expand...
Click to collapse
Version 1909
build 18363-1198
Edit: If I have ubuntu 18.04 installed, what do I put here?
wsl.exe --set-version Ubuntu 2
Tulsadiver said:
Version 1909
build 18363-1198
Click to expand...
Click to collapse
In that case, it seems like a problem with Windows or WSL2. Surely there are other people in the world that are having trouble upgrading to WSL2. Maybe a google search on the topic would help.
Tulsadiver said:
Version 1909
build 18363-1198
Edit: If I have ubuntu 18.04 installed, what do I put here?
wsl.exe --set-version Ubuntu 2
Click to expand...
Click to collapse
Code:
wsl --set-version ubuntu-18.04 2