[Android Software/Hacking General [Developers Only]] PANCHOMATASANO:
1-Preparing the environment.

sudo add-apt-repository ppa: nilarimogard/webupd8

sudo apt-get update

sudo apt-get install-android-tools-tools adb-fastboot android

Those three commands install ADB TOOLS, for Ubuntu 12.04 and earlier versions.

2-Each manufacturer has its ID development.

This, in principle, we can solve in a simple way Ubuntu. We need to add a line in the file / etc / udev / rules.d.

The line to add to the file depends on the manufacturer and model of the device. We can find the Vendor ID and Product ID of the device running (after having connected to USB, of course):

$ lsusb

This will be returned

*

Bus 002 Device 021: ID 2207:0000

(This is an example of what we can give back, by brand and manufacturer)

This indicates that the Vendor ID is "2207" and the Product ID is "0000".

3-Let's do it step by step:

Enable USB debugging and unknown sources on the Android.

Go to Settings -> Security and check the Unknown sources checkbox, then go to Options and development USB debugging enabled.

Connects via USB to Ubuntu Android.

Create / edit a file in / etc / udev / rules.d called 51-android.rules:

$ sudo gedit / etc/udev/rules.d/51-android.rules

Add the following line and save it

SUBSYSTEMS == "usb", ATTRS {idVendor} == "....", MODE = "0666", GROUP = "plugdev"

***IMPORTANT: Place the idVendor ATTRS {idVendor} == "HERE"***

4-Restart udev

$ sudo restart udev

At this point adb and should recognize our device, but it is not. This is because the version of adb included in the Android SDK does not "understand" our Vendor ID (not a salesman "officially recognized").

To fix this do the following:

Create / edit a file in $ HOME / .android called adb_usb.ini:

$ gedit $ HOME / .android / adb_usb.ini

Add the following content and save it

# ANDROID 3RD PARTY USB VENDOR ID LIST - DO NOT EDIT.

# USE 'android update adb' TO GENERATE.

# 1 USB VENDOR ID PER LINE.

0 × 2207

************************************************** *****************************

At this point gave me a problem, which was solved in a way a little strange. The following file $ gedit $ HOME / .android / adb_usb.ini

has to look like:

# ANDROID 3RD PARTY USB VENDOR ID LIST - DO NOT EDIT.

# USE 'android update adb' TO GENERATE.

# 1 USB VENDOR ID PER LINE.

0 × 2207

# ANDROID 3RD PARTY USB VENDOR ID LIST - DO NOT EDIT.

# USE 'android update adb' TO GENERATE.

# 1 USB VENDOR ID PER LINE.

0 × 2207

It was the way it worked for me and found the tablet.

************************************************** *******************************

5-At this point adb and should recognize our device:

$ adb devices

List of devices attached

0123456789ABCDEF device

Although sometimes you need to stop and start the adb server:

$ adb kill-server

$ adb start-server

************************************************** *********************************

Or maybe we should use this other method to stop the deamon

************************************************** *********************************

Reinitiate the 'deamon', as follows:

$ sudo stop udevd

It is likely that in the process of detention remains in standby, so the terminal will show nothing after entering the command.

Do not panic, simply: Restart our machine.

After restarting our team, we will ensure that our tablet has enabled debug mode, for that we can address

Settings >> Applications >> Development

And check the option 'USB debugging'

Once marked, we connect our tablet via cable / USB, open a terminal command:

$ adb devices

Automatically our deamon 'udevd' ripped, since previously we had stopped. And if all goes well, it should show you a list of connected devices, with their ID's.

6-Now that our team recognizes our device we root him:

Superuser unloaded tool (ICS compatible version and with our platform ARM, MIPS, ROKCHIP, ALLWINNER, etc.) and extract the application "Superuser.apk" and binary "your" in, for example, / tmp.

Su and Superuser installed:

$. / adb remount

$. / adb push / tmp / su / system / bin / su

2568 KB / s (22364 bytes in 0.008s)

$. / adb push / tmp / su / system / xbin / su

2843 KB / s (22364 bytes in 0.007s)

$. / Adb push / tmp / Superuser.apk / system / app / Superuser.apk

4593 KB / s (843503 bytes in 0.179s)

$. / adb shell chown 0.0 / system / xbin / su

$. / adb shell chmod 6775 / system / xbin / su

$. / adb shell chown 0.0 / system / bin / su

$. / adb shell chmod 6775 / system / bin / su

$. / adb remount

remount succeeded

$. / adb reboot

We hope to restart the tablet and go!

Sources:

http://rubensa.wordpress.com/2012/05/21/energy-sistem-i828-hd-ics-4-0-3-rooting/

http://www.htcmania.com/showthread.php?t=469742