[HOW-TO] Set up SDK/ADB on Ubuntu 11.10 | 32 & 64 bits - Barnes & Noble Nook Tablet

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

Related

X10 Custom ROM AOSP 2.2.1 : How to for dummies

SINCE FREE X10 IS NOW BETA, THIS HOW TO IS NO LONGER VALID
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
** No responsability for anything, you are all responsible of what you're doing !! **
** Please follow ALL these steps. Don't try to be Indiana Jones by flashing your device without all the tools needed !!! **
INSTALL
(for 1st install)
Before attempting anything, make sure you have AT LEAST 50% of battery charge. Don't try anything with low battery, you can abort the flashing and brick your device !!!
Please make sure you're also running a 2.1 rom (Generic, nordic, official, custom...)​
- Download FreeX10 v0.0.1 file (NOT 002 yet !!!)
- Download Android SDK
You don't need to save the entire archive (but you can), you just need the Tools folder (because it contains ADB, the Android Debug Bridge we need to install files).
- On x10 :
Download and install Busybox (from Market), make sure it says "Done!".
Connect your x10 in USB, mount SD card, and copy files FreeX10.zip and install on the root of your SD Card.
Enable USB debugging (Parameters > Applications > Development).
- On your computer, go in the Tools folder, open a DOS prompt (for Windows 7 : hold CAPS + right click, you'll see Open a DOS prompt) and
type :
Code:
adb shell
(this will run ADB shell... You will get a "$")
- Type :
Code:
su
(this will make you super-user, you will get a "#")
- Type :
Code:
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
(It will display "11", "1+1", or "inflating:..." ...)
- Wait, have a beer, pray for your sins for your phone not to turn into a $600 brick
- One minute after, when it shows
Code:
All done, please reboot!
, reboot ! (But you can gently quit ADB by typing
Code:
exit
twice
)
Note : regarding me, I typed "exit" to quit ADB, I turned off ADB on phone and disconnected USB. You can do, it's even safer
- Wait up to 5 minutes for the phone to boot, it is NORMAL !!!! It looks stuck on Sony Ericsson logo and/or on Free X10 logo, it's NOT stuck !!! You MUST wait !!!!
- It will finally run normal, your phone is alive and 2.2-hearted !!
You are now eligible to install v0.0.2 (as it comes as an update).
Dual Boot usage
This rom comes with a great Dual Boot, which means the 2.2.1 is installed safely apart from your original 2.1 rom. This means you can switch back anytime to stock rom. To say it simply :
- Your Android 2.1 is here, and no changes are made to it (apps, version, etc etc). It is stored as it has to be, in the internal 1Gb phone memory storage (called the "NAND").
- FreeX10 (2.2.1) is running from image files (like .ISO files) stored in your SD Card. This means the two Android are living together peacefully, without affecting (theorically) each other.
FreeX10 mainly creates a bootloader, for you to choose whether to test 2.2.1, or go back to 2.1 for your daily use.
- To run 2.2.1 : do nothing (default boot)
- To run 2.1 : press any key at boot, when it shows "Sony Ericsson".
Notes when upgrading to v0.0.2 :
- As Android is stored into image files (.IMG), upgrading will wipe out all your content (it does a fresh "install"), make backup of what you need !
- to avoid future bugs, altough you're not forced to do, do the routines to make sure Wifi, root, packages install, ... work. This is because USB debug can break, so you won't be able to use ADB to fix these bugs
- Root is strongly recommended to work, because it's cool and because the CPU performance is set to highest : stuck at 998MHz all the time, it will drain your battery like hell ! You can switch it back to original power saving plan (ondemand plan) by using (ie) SetCPU. Root required !
If your Android goes instable, does not work anymore, or you want a fresh install after lots of tests, simply drag and drop the original v0.0.2 .img files on your SD card. This will make you boot into a fully fresh install.
For all bugs, commands, etc.. Please go first to this excellent (and very easy) thread !!
Nice..
How about one on AOSP 2.1
Perceval from Hyrule said:
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
Click to expand...
Click to collapse
nice dummies HOW TO
and ohhh my god there is dummies
all comands needed
INSTALLATION
1. Download the rom package (FreeX10_alpha-release_0.0.1.tar.bz2)
2. Unpack it to the root (main folder) of your SD Card
3. Connect your phone in USB Debugging mode
4. Open ADB shell, switch to root user (SU)
5. Issue the command
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && ./data/install
6. Reboot when installation is finished
7. Enjoy
---------------------------------------------------------------------------------------------
CHANGE BOOT PRIORITY
Copy chargemon.txt file to
/system/bin
folder ON YOUR ORIGINAL 2.1 ROM, NOT FROYO!!!
---------------------------------------------------------------------------------------------
UPGRADE TO 0.0.2 VERSION
Boot into 2.1, unpack the content of FreeX10_alpha-release_0.0.2-UPDATE.tar.bz2 into
/sdcard/FreeX10
folder and reboot into updated 2.2!
NOTES:
1. SMS vibrate is disabled by default; open Messaging, press MENU button -> settings -> vibrate -> always
2. If you don't have radio (network) after 1st boot, please open ADB shell and issue this command:
killall servicemanager
3. If you don't have root access, please open ADB shell and issue this command:
chmod 4755 /system/bin/su
---------------------------------------------------------------------------------------------
hope it helps too
UPDATE TO v.0.0.2
Note : you can only update from 0.0.1 to 0.0.2. I mean you can't do a fresh install of 0.0.2, you MUST have 0.0.1 installed !
- Download v0.0.2 from main thread.
- Run your device on your regular 2.1 rom (while off, power on, and press any button when it displays Sony Ericsson logo)
- Mount the SD Card, then copy data.img and system.img from the archive into the folder /FreeX10. Replace the two .img files.
- Reboot into 2.2, have fun ^^
OmegaRED^ said:
Nice..
How about one on AOSP 2.1
Click to expand...
Click to collapse
I'll try to do one if I get time, but I need a fully working ROM as my phone is useful for my life (still waiting for 2.1 stable )
Thanks for your posts all, it will help everybody who want to try the 2.2
(as it is safe and running from SD card, very very very cool idea !)
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
root privileges do you have it?
unmount sdcard
OmegaRED^ said:
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
Click to expand...
Click to collapse
sarcasm...love it
rendeiro2005 said:
root privileges do you have it?
unmount sdcard
Click to expand...
Click to collapse
yes mate i do have root access titanium etc works fine just cant get adb shell to run
When i installed 2.2, it rebooted and when to the sony ericsson logo for almost an hour, does this mean i have to reinstall 2.1, and if so, i would i accomplish this
fastphil said:
yes mate i do have root access titanium etc works fine just cant get adb shell to run
Click to expand...
Click to collapse
and what about sdcard?
uncheck nount/unmount
rendeiro2005 said:
and what about sdcard?
uncheck nount/unmount
Click to expand...
Click to collapse
done that too
fastphil said:
done that too
Click to expand...
Click to collapse
can you post a screenshot of cmd?
ok will do
I am still having problems also...
after I type the cmd...
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
it just says:
1+1 records in
1+1 records out
520 bytes transferred in 0.003 secs...
#
so, where am I going wrong?
fyi, I am trying to install v001, not the update, and the phone is rooted, busybox is installed. Sorry, but I have tried for a while now and I finally have to just ask for help. Thanks guys.
here pic off cmd
{
"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"
}
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
Does it work when your run "adb" command only ?
It looks to me your error is because you're not in the folder where adb.exe is
It is in folder tools, if you try to run it from root directory (where is the android app with nice icon) it won't work for sure
Edit: didn't see your screenshot >> you are NOT in the correct folder !! (so Windows is searching for a registered command which does not exist, I think there's a thread somewhere on how to add it as a registered (I mean global) command)
You must download Android SDK (22mb... Lmao regarding 4gb for iOS ), extract the archive and go in the tools folder. Here is adb.exe.
when i try & run adb exe it does not open it just closes right away

<[TOOL 7/13]> Jeremy's Fre3vo Sticky-Root Windows/Linux/Mac v2.5

This script will run on Windows, Linux and Mac. No longer do you have to worry about having adb in your path, as i have included the binaries for all the operating systems.
The Linux and Mac script will automatically detect what O/S your using and use the correct binary.
You should be all set right out of the box, as long as you have the adb drivers installed for your device if you are in Windows. Linux/Mac users need not worry about the drivers.
COMING SOON.
overclocking capability and more
For Windows Users:
1. REBOOT YOUR PHONE BEFORE RUNNING
2. Extract the zip.
3. Make sure your drivers are installed.
Youtube Video from a user
http://www.youtube.com/watch?v=ZcWqeYQjjk0
older version of the script but same principal
4. Run Root.bat
5. Select your device
6. Hit #1
7. Profit!!!
Drivers For Windows:
Evo3D 32-bit Windows drivers:
Download HERE
Evo3D 64-bit Windows drivers:
Download HERE X64
For Linux/Mac Users:
1. REBOOT YOUR PHONE BEFORE RUNNING
2. Extract the zip.
3. Enter the directory.
4. Set the script permissions to allow it to execute.
Code:
chmod +x root
5. Plug in your device.
6. Run the script.
Code:
./root
7. Select your device.
8. Select #1
9. Profit!
Notes:
After the script starts all you have to do is choose option #1
The script remounts the file system R/W by itself. The other options are just there for convenience if you were to need to remount for hackery. sorry for the confusion.
All files are included including Fre3vo, su, busybox and superuser.apk
I get absolutely no superuser force closes with this. Titanium backup works perfectly. This is also the newest version of the superuser beta.
I have tested these scripts on my phone 10x each, 20 reboots if your counting If you are having problems REBOOT the phone to wipe all the changes you may have made with other scripts/errors.
Also if you install the Terminal Emulator from the market and type "su" you will get a superuser pop up to allow permissions and you will get a root prompt in the Terminal.
Let me know how it works for you.
Changelog:
v2.5
[Linux/Mac] Auto-detect Os
[Linux/Mac] Linux and Mac binaries now included so no more adb having to be in your PATH
v2.4
[Linux/Mac] Fix stupid error on my part in linux script
v2.3
[Linux/Mac]
[Windows]
Script Tweaks
New sticky temp root method (Installs to /vendor/bin/)
v2.2
[Linux/Mac]
[Windows]
HTC Sensation Support!
v2.1
[Linux/Mac] script tweaks
[Windows] rewrote script & added tools
v2.0
[Linux/Mac] rewrote script & added tools
[Windows] SORRY WINDOWS USERS NEW SCRIPT ISNT DONE FOR WINDOWS YET
v1.1
[Windows] Added Windows .bat
v1.0
[Linux/Mac] Initial Release
[Windows] Release SOON!
Download it here
http://dl.dropbox.com/u/11406774/Jeremy_Fre3vo2.5.zip
------Linux
{
"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"
}
------Windows
Dam sweeeet
Can someone make one for a win XP setup
I plan on making a .bat soon but if someone that knows what they are doing wants to try to convert it over for me ill update the op. I use my only windows computer to watch netflix on my tv. LOL
Pew Pew
I got Linux but how do I run this one tho?
Sent From My "Desperate For Root" 3VO...
You Sir are Amazing. Thank You. (Moves my own script into trash =) )
Eagerly awaiting a .bat file for this.
I *THINK* this should work for Window users... I made it really quick like and haven't even tested it myself..
Put this in the SDK folder "platform-tools" and run it as Admin. Make sure you extract all of the files to the root directory of the platform-tools folder and it should work.
platform-tools > root.bat
platform-tools > bin
platform-tools > apk
That should be your folder structure.
Let me know if it works
I got a mac, but from reading the OP it says I need ADB in my path? Not sure exactly what that means...
Stericson said:
I *THINK* this should work for Window users... I made it really quick like and haven't even tested it myself..
Put this in the SDK folder "platform-tools" and run it as Admin. Make sure you extract all of the files to the root directory of the platform-tools folder and it should work.
platform-tools > root.bat
platform-tools > bin
platform-tools > apk
That should be your folder structure.
Let me know if it works
Click to expand...
Click to collapse
Testing now.. ill edit once it (hopefully) completes
EDIT:
steps one thru 3 work great...
cant seem to 4 to work... any ideas?
**************
Your choices:
**************
(1) Set PATH variable for SDK platform-tools directory
(2) List devices found by adb
(3) Temp Root your Evo3d or Sensation with Fre3vo
(4) Install su, Superuser.apk and busybox
(5) Mount /system as R/W
(6) Mount /system as R/O
(7) Check mount points
(8) ADB Shell
(9) Exit
Type choice number: 4
********** su, Superuser.apk and busybox ***********
---------------------------------------------------------
Mounting /system as R/W
mount: Read-only file system
Done!!
---------------------------------------------------------
Installing su and busybox
failed to copy 'bin/su' to '/system/bin//su': Read-only file system
Unable to chmod /system/bin/su: Read-only file system
link failed File exists
failed to copy 'bin/busybox' to '/system/bin//busybox': Read-only file system
Unable to chmod /system/bin/busybox: Read-only file system
[1] Segmentation fault busybox --instal...
Done!!
---------------------------------------------------------
Installing Superuser
failed to copy 'apk/Superuser.apk' to '/system/app//Superuser.apk': Read-only fi
le system
Done!!
---------------------------------------------------------
Installing user and group
cannot create /system/etc/passwd: read-only file system
cannot create /system/etc/group: read-only file system
Unable to chmod /system/etc/passwd: No such file or directory
Unable to chmod /system/etc/group: No such file or directory
Done!!
---------------------------------------------------------
Complete, Press ENTER to return back to the main menu
Click to expand...
Click to collapse
Not sure what I'm doing wrong, copied all the folder elements into c:/android-sdk-windows/platform-tools, ran root.bat, pressed 3, waited until process finished, then pressed 4, installation says Okay. I see SU.apk installed on my phone but whenver I open up any rooted apps, it says cannot find root.
EDIT: this is through the windows version of the script.
Hmmm... I just tried it and it worked for me first go....using adb shell, do you have root?
Stericson said:
Hmmm... I just tried it and it worked for me first go....using adb shell, do you have root?
Click to expand...
Click to collapse
I'm retrying, let me test again after reboot.
fowenati said:
I got a mac, but from reading the OP it says I need ADB in my path? Not sure exactly what that means...
Click to expand...
Click to collapse
here is the mac binary for adb.
what you have to do is copy it into the /usr/bin/ folder.
Code:
sudo cp adb /usr/bin/
you need to make sure you are in the directory that adb is in when you execute that.
spunks3 said:
Testing now.. ill edit once it (hopefully) completes
EDIT:
steps one thru 3 work great...
cant seem to 4 to work... any ideas?
Click to expand...
Click to collapse
try using step 5 first then step 4?
EDIT: Well you shouldn't have to do that...try running step 3 again and show us the output?
Stericson said:
try using step 5 first then step 4?
EDIT: Well you shouldn't have to do that...try running step 3 again and show us the output?
Click to expand...
Click to collapse
my first time 3 worked okay i believe.
when i adb shell i get #
rebooting and trying again
This is my setup. Fresh reboot, fresh file extraction (directly from your .zip into platform-tools). Failed.
http://i642.photobucket.com/albums/uu150/Deflectant/Cropped.png
This picture is cropped, much easier to read.
EDIT: root.bat is in c:/android-sdk-windows/, I cropped it out of the picture though.
SuperUser keeps crashing for me....that might be the problem...
Thanks J.eremy. You asked to let you know how it went in your OP, so I'm reporting back. It worked excellent and quick, as advertised. Couldn't have been simpler, thanks. I've had it running for about an hour now, and have had no super user FC. How long have you had this lasting so far? Prior to this, I would only be able to go about a half hour or so before i got FC on super user, and would have to start over again. Is something different here? It seems to be sticking far longer...at least so far.
k2buckley said:
Thanks J.eremy. You asked to let you know how it went in your OP, so I'm reporting back. It worked excellent and quick, as advertised. Couldn't have been simpler, thanks. I've had it running for about an hour now, and have had no super user FC. How long have you had this lasting so far? Prior to this, I would only be able to go about a half hour or so before i got FC on SU, and would have to start over again. Is something different here? It seems to be sticking far longer...at least so far.
Click to expand...
Click to collapse
Your welcome
it lasts me until reboot every time normally, im pretty sure the main problem with some other scripts are they are not setting the permissions right and not modifying the passwd and group files correctly.
no f/c on my end either
spunks3 said:
my first time 3 worked okay i believe.
when i adb shell i get #
rebooting and trying again
Click to expand...
Click to collapse
yea Stericson is right, looks like the batch file isn't auto mounting the /system as R/W.
gonna go take a look at it now
Overstew said:
This is my setup. Fresh reboot, fresh file extraction (directly from your .zip into platform-tools). Failed.
http://i642.photobucket.com/albums/uu150/Deflectant/Cropped.png
This picture is cropped, much easier to read.
Click to expand...
Click to collapse
interesting...your picture shows it cannot find /bin/fre3vo
either it cant find the folder, or it cant find the file....

[ Tutotrial ] Install either Ubuntu or Debian in any Android Phone without any app

This is a Tutorial to install either Ubuntu or Debian in any Android mobile without using any app ​
* Installing Ubuntu or Debian Linux does not format your Android OS or change anything to your phone.
The Operating Systems run over the underlying Android OS which continues to function as normal
Choosing your Linux OS:
There are few things you must be aware of before installing Ubuntu/Debian on youe Android Phone
Ubuntu does not support earlier ARM CPUs like the ones used in the Motorola Cliq. Samsung Galaxy Fit (ARMv6), Samsung Galaxy Y, etc.
( Reason behind this is , Your Android OS Kernel must support loop devices. Most newer Android smartphones/tablets come with this support so we can mount our Ubuntu image as a loop device. If not, you will either have to build your own kernel with support for loop devices or you can try an aftermarket ROM for your phone as most aftermarket ROMs come with support for it. )
You need at least an ARMv7 CPU like the kind found in the Motorola Droid, Samsung Galaxy S,HTC EVO 3D, Sony Experia Play, etc. most newer phones (Hummingbird, Snapdragon, Tegra2, etc.).So you can Install Ubuntu if you have ARMv7 or newer Processor.
If you have ARMV6 or any other moderate Processor don't be sad, because Debian supports the CPU on practically all Android devices, so if you prefer Debian, or you can't run Ubuntu, choose the Debian download link.
* If you're not sure what CPU your device has, look up your device on http://pdadb.net/, click the link under CPU, and read the line for "Supported Instruction Set(s)".
e.g. : My Phone which is a " Samsung Galaxy Fit" uses ARMV6 Instruction Sets.
{
"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"
}
Click to expand...
Click to collapse
Pre-Requirements:
Hardware Required:
an Android Phone
SD Card with more than 2GB of free Space
Android root environment:
Most important! Your Android device should be “rooted” because you need root access to run Ubuntu/Debian off your Android. If your device is not rooted you have to root your device.
Linux Operating System:
Download suitable OS from the following Link:
Ubuntu 11.04 (Natty Narwhal)
linux.ubuntu-natty.tar.bz2 Ubuntu 11.04 (Natty)
Ubuntu 11.10 Oneiric Ocelot
linux.ubuntu-oneiric.tar.bz2 Ubuntu 11.10 (Oneiric)
Debian 6.0 Squeeze
linux.debian-squeeze.tar.bz2 Debian 6.0 (Squeeze)
Click to expand...
Click to collapse
Applications Required:
BusyBox Installer
A terminal emulator like Better Terminal Emulator ( Recommended ) or Terminal Emulator.
Optional Apllications:
androidVNC
Or
ConnectBot
Click to expand...
Click to collapse
Procedure ----------------------------------------------->
Step 1:
(Mount the SD card on your computer.)
Extract the .tar.bz2 file you downloaded to your SD card. You should now have a folder named "linux" on the root of your card.
(Unmount the SD card.)
Open Busybox Installer, and install Busybox.
Open Better Terminal Emulator, and install Better Terminal Emulator.
Click to expand...
Click to collapse
Step 2:
Open your terminal emulator. (If using ConnectBot, connect to 'local', not 'ssh'.)
Run the following commands:
Code:
[B]su[/B]
( If Prompt for Superuser Request then allow )
Code:
cd /sdcard/linux
sh install.sh
If you don't see any errors, Linux is now installed.
Click to expand...
Click to collapse
Step 3:
Open your terminal emulator.
To start a chroot session
Code:
su
linux
To start the SSH server
Code:
su
linux ssh
You can then use ConnectBot (SSH: [email protected]) on your device, or any SSH client to connect to your device. See Login Information, below.
Click to expand...
Click to collapse
To start a VNC session
( Firest you need androidVNC to be installed , then type the following in terminal )
Click to expand...
Click to collapse
Code:
su
linux vnc
The first time you run VNC, it will prompt you to create a VNC password.
You can then use androidVNC (host: localhost port: 5901), or any VNC client to connect to your device.
Configure The VNC App as follows:
Note: The default desktop environment is icewm. If you wish to replace it, for example, with LXDE:
Run the following as root in Linux:
Code:
apt-get autoremove icewm- lxde+
Secure your Log in Password:
Please remember to change these passwords if you are planning on using the SSH server. Malicious people can do Very Bad things to your device if you don't.
There are two accounts included in the images:
root
Password:cheesecake
user
Password:dessert
Click to expand...
Click to collapse
After a successful connection to host you will be able to use Ubuntu / Debian in graphical interface just like in your PC ! It will keep your Android OS as it is and just run in the upper layer over it
These are some of the screen shots taken from my Samsung Galaxy Fit!
Click to expand...
Click to collapse
Linux vs Linux Terminal Emulator :
Terminal Emulator only Emulates Linux terminal, but after Linux Installation you can get full features; more than just the limited commands which runs on Android shell rather than Linux Shell.
Please Leave your Feedback and Queries below. Thank You
​
Click to expand...
Click to collapse
riddz17 said:
This is a Tutorial to install either Ubuntu or Debian in any Android mobile without using any app ​
Click to expand...
Click to collapse
Nice, i have tried for my Galaxy Ace so with ARM V6 too, but the terminal emulator gave me error in the step 3 and 4
error not working
I'm getting about a dozen errors in the install process, all of which seem to relate to file permissions.
G.Galante said:
Nice, i have tried for my Galaxy Ace so with ARM V6 too, but the terminal emulator gave me error in the step 3 and 4
Click to expand...
Click to collapse
what kind of error could you please specify??
First of all check is your phone rooted?
when I type su
sh install.sh
there are many error like dir.. not found help me...
Sent from my HTC Explorer A310e using xda app-developers app
sateesh907 said:
when I type su
sh install.sh
there are many error like dir.. not found help me...
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
worked for me. I tried to install from the microsd card (sdcard-ext) but i got errors. Once i moved the files to the phones memory (sdcard) it worked like a charm.
note: I am using Debian 6.0 Squeeze
Sent from my GT-I9000 using Tapatalk 2
ivke101 said:
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I get the same error. Anyone know how to fix it?
hey guys
Thanx to the author of this forum on debian on android. I had the same problem you see in the error logs above. the problem is between regular "mount" command and busybox "mount". you need to use the busybox mount. so I added the word busybox infront of every mount word in the script. eg. busybox mount -o , rw /system remount. the alternative is to delete the mount found on /system/bin so that the terminal will use the busybox one automatically on /system/xbin.
Thanks, I found that the version of busybox I had didn't install the mount comand. I had to use the smart installer and manually check the box to overwrite the mount command then it worked.
Sent from my SPH-L710 using xda app-developers app
Nice work. I've been experimenting with Ubuntu some so I can run side by side w/windows.
Does anyone know if You can connect to the the ubuntu instance on your phone from a computer through vnc? I would like to be able to use a bigger keyboard and mouse to control it.
Edit: If I make changes to the Linux.img on my phone and just copy the whole folder to my tablet will it still keep all of the changes? (I will try it tonight if know one knows).
---------- Post added at 10:52 AM ---------- Previous post was at 10:36 AM ----------
Ok you can connect to the phone from a computer. I used wifi tether and then just put the phones ip and the port into tightvnc and it connected. It took a minute to recognized the phone the first time though.
Sent from my SPH-L710 using xda app-developers app
riddz17 said:
This is a Tutorial to install either Ubuntu or Debian in any Android mobile without using any app ​
Click to expand...
Click to collapse
HI , THANKS
for your work..i have galaxy ace plus [armv7] ,i tired installing linux on my phone, when i type "sh install.sh "then ,,,such dir not found like error
appears, i am new for linux command [ my dir . /sdcard/external_sd/linux ].what can i do for this? plz help me .
patilsb said:
HI , THANKS
for your work..i have galaxy ace plus [armv7] ,i tired installing linux on my phone, when i type "sh install.sh "then ,,,such dir not found like error
appears, i am new for linux command [ my dir . /sdcard/external_sd/linux ].what can i do for this? plz help me .
Click to expand...
Click to collapse
- try to install "busybox installer" first..
- when you open the app, it will ask to install busybox..
pay attention to "Advanced install" checkbox.. be sure to have it checked..
- you will found so many applets.. try to find named "MOUNT"..
- when you found them, see the triangle sign on the right-side.. click it..
- there are 3 options: symlink applet / remove symlink / skip symlink
pick symlink applet..
- press install
- after it's done, get ou of busy box
- back to terminal, repeat the step "sh install.sh"
i got stuck @ step 2 " please wait while booting ubuntu.img.. this may take some time ,,. "
i installed busy box , i got my device root
sent from my Arc S
itzwood said:
i got stuck @ step 2 " please wait while booting ubuntu.img.. this may take some time ,,. "
i installed busy box , i got my device root
sent from my Arc S
Click to expand...
Click to collapse
How long did you wait? Mine took about 15 minutes the first time after the first its just is there.
i left it before i go to sleep .. waked up nothing "ABOUT 8hours "
scientist343 said:
How long did you wait? Mine took about 15 minutes the first time after the first its just is there.
Click to expand...
Click to collapse
itzwood said:
i left it before i go to sleep .. waked up nothing "ABOUT 8hours "
Click to expand...
Click to collapse
Try redownloading it to make sure it isn't corrupt.
You can also try a reboot, then try starting at the top again. I had it do that on my old phone and after a reboot it worked.
Also which version of ubuntu did you download 11.04 or 11.10?
no such file or directory errors
Hi I'm getting "no such file or directory" errors when I try the step "sh install.sh"
can't post pictures yet so I'll type up the short version
# sh install.sh
remounting /system rw ...
mount: no such file or directory
installing scripts in /system/bin ...
mounting the linux image ...
mounting prepwork...
mounting: loopback mount ...
mknod /dev/block/loop254: file exists
mount: invalid argument
mounting: setting up chroot environment ...
mount: no such file or directory
mkdir failed for /data/local/mnt/media/sdcard, no such file....
[done]
then the rest is no such file or directory
I'm on an Epic 4g touch rooted obviously
I tried putting busybox in front of mount in the script as suggested before
I moved all the files from /mnt/sdcard/external_sd to /sdcard
made sure mount is installed in busybox
Not sure what to try next. Guess I could make the folders manually and see what happens.

[GUIDE][Noobz][Tweaked-Linux]How to install KDE Kubuntu Active

{
"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

[GUIDE][UBUNTU/DEBIAN] Unlock Your Nexus 6P Without Resorting to Windows

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.

Categories

Resources