[HTC Pico (Explorer)] Red Devil:
Hello everyone at xda !

As a newcomer I was searching for a bit of help getting started with android tools and its development.

So I decided to help out the newcomers a bit more by creating this thread..

I found this to be essential for our

HTC Explorer Development Forum

This guide contains :

Post 1:

Info about SDK / ADB and how to install them on linux and windows.

Logcat- How to logcat , types of logcats , meaning

Adb wireless

Post 2:

Clean install

Paritioning sd

Flashing kernel , recovery

Permissions

What is overclocking ?

Recover from OC

md5 checksum

Post 3:

Video tuts and credits.

Info about ADB/SDK :

ADB

What is adb ?

Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:

A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.

A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.

A daemon, which runs as a background process on each emulator or device instance.

SDK

What is android SDK ?

Android software development is the process by which new applications are created for the Android operating system. Applications are usually developed in the Java programming language using the Android Software Development Kit, but other development tools are available. As of October 2012, more than 700,000 applications have been developed for Android, with over 25 billion downloads.The Android platform has also grown to become a favorite among mobile developers.

Want to download and use adb and SDK ( its in one package )?

Visit http://developer.android.com/sdk/index.html

Extract the files of the package you downloaded from the site as whatever you want to but remember it ?

Windows Specific

(VISTA)

Keep your path name to which is extracted to

Eg : C:\(*package-name*) [ eg of package name : adt-bundle-windows-x86 ]

Rename the Folder to C:\(*Whatever you want to name it*) [ eg change "adt-bundle-windows-x86" to "android" ]

In order to run adb do the following steps :

Click start

Search for cmd

Right click and * RUN AS ADMINISTRATOR *

type the following commands

C:\Windows\system32\>cd C:\android*\sdk\platform-tools\ [*click enter*]
C:\android*\sdk\platform-tools>adb
C:\android*\sdk\platform-tools>adb devices

Now you should get a huge code block with all the adb commands

That means adb has been installed correctly.

adb devices gives you the list of attached adb devices and if their permissions are right.. :)

Setting up ADB as a command on Windows 7/ Vista

Assuming you have done the above steps correctly you should have no problem going ahead

Right click on Computer

Click on properties

Go the advanced system settings

Click on the advanced tab

Go to Enviornmental variables in the dialog box

In system variables find the variable " Path ".

Double click on it and in variable value add the following line

at the end of it

:

;C:\android\sdk\platform-tools\;

Click on OK etc and save the settings

now Run command prompt

Type adb and your adb commands will be in function..

You can now run adb as a command and dont need to go to the directory every time. :cool:

Linux Specific

( Ubuntu )

PS (important) if someone has a 64bit linux then they need to download 32bit libs

for this, before all these steps run this

sudo apt-get install ia32-libs

You should have an updated JDK for this.. Just in case..

$ sudo add-apt-repository ppa:sun-java-community-team/sun-java6

$ sudo apt-get update

$ sudo apt-get install sun-java6-jre sun-java6-bin sun-java6-jdk

we need to make a new directory by this command

mkdir android

then extract by

tar -zxvf ~/Downloads/android-sdk_r21.0.1-linux.tgz

then move it to the directory we just made

mv android-sdk-linux ~/android/sdk

the open android sdk manager by

android/sdk/tools/android

this will open android sdk manager

we need to select just android sdk tools and android sdk platform tools for adb and then select install packages

^^this will download everything required

then we need to set a path to include adb

gedit .bashrc

and then a file opens and paste this text in that file

export PATH=${PATH}:~/android/sdk/platform-tools

then we make the above bashrc file executable by this

chmod a+x .bashrc

then we need to setup device rules and make that file executable

ps sample is the username

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

and copy and paste this

SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"

and then make rules executable by:

sudo chmod a+x /etc/udev/rules.d/*

we need to add full path to adb start server

Type :

sudo gedit /etc/rc.local

this will open a file

now add this line just above where it is written exit 0

/home/sample/android/sdk/platform-tools/adb start-server

"sample is username"

after this we dont need to cd to adb directory..we can just type adb devices and the phone will surely show up

Guide for Linux by Gnexus. Thank him Here!

Now we have a blooming xda forum at HTC Pico aka Explorer with :

Cyanogen mod 7

Cyanogenmod 9

Cyanogenmod 10

Cyanogenmod 10.1

Sense 3.5(stock)

Sense 4.0

Which is quite a lot considering our device is considered as

Now with all those ROMs come their respective bugs..

Just saying

Gives just another burdening job for a ROM dev of trying to find that same mistake and trying to take a log of it..

At times they are on a different ROM and it becomes difficult for them to flash their old ROMs again..

Sometimes they dont even have the same device !!

So.. Try to ease the job of the dev by bringing whats called a logcat so you can do the following to help them out :

You should have installed adb and fastboot by now

For getting a logcat you should do the following easy steps

Connect phone to pc / laptop ( quite obviously )

Assuming you have rooted your phone you should have required drivers installed ?

To enable ADB mode on your phone go to settings > developer options > Debugging > USB Debugging > ON

1st go to cmd and run as administrator and go to the root of adb

simply type

C:\android*\sdk\platform-tools>adb logcat

and you get a logcat running on your screen :cool:

Want to post a logcat somewhere ?

1] A logcat that can be easily copy pasted and given to someone else :

to do that type :

adb logcat > cat.txt

*cat is just an example .. it can be Anything logcat.txt, catlog.txt, etc ( let your imagination go wild ;) )

This gives you a logcat at the platform-tools folder .

Now if you get your logcat you can post the logcat somewhere in the dev threads as a whole logcat or you can put specific lines where you want the dev to look at or you know the error is present. There is a character number limitation on a single post on xda for which you can simply upload the .txt file or you can also post it on Pastebin and share the link/url on the thread. This helps a lot .

Alternatively there are apps such as aLogcat or Catlog but installing adb and fastboot is essential as it will not only help you with this but other functions also look further down..

Meanings of symbols in a logcat !

You usually see this at the start of a sentence in logcat .

I/> ===> Information

S/> ===> Silent

D/> ===> Debug

W/> ===> Warning

E/> ===> Error

F/> ===> Fatal

For more information about logcats

Help with solving a logcat from fellow members only for pico !
​

DMESG

(*Useful for devs / beta testers alike*)

Go to your adb directory via terminal / cmd on admin privileges

Type

adb shell dmesg > dmesgLOG.txt

Terminal emulator :

dmesg > /sdcard/dmesglog.txt

DMESG is useful for finding out errors / bugs in the hardware aspects caused due to software issues and kernel issues (* eg : deepsleep , bluetooth not working , wifi not working etc . *) which cannot sometimes be easily solved through a simple logcat.

Lastly

K-MESG

To help solving with respect to

kernels

(* Yes it is a kernel not kernal... *)

Kernel issues like a kernel panic and similar. Similar steps to dmesg but the code is

adb shell cat /proc/last_kmsg > kmsg.txt (*via adb*)
cat /proc/last_kmsg > /sdcard/last_kmsg.txt (*via terminal emulator*)

ADB wirelessly

To use adb via Wi-Fi

Download this wonderful app from the playstore adbWireless

Click on the green button and an IP will come on the app screen. (* eg: 123.456.7.890 *)

On your computer go to your adb directory via terminal / cmd prompt

type

adb connect 123.456.7.890

Voila! You are using adb wirelessly :cool:

Some useful extra stuff !

Adb guide

Note : Please do not quote the entire first post in the replies ! :)