Chapter 1 android custom ROM Introduction

Introduction

Android is Linux based operating system which is Developed by Google for android devices with
java interface. Android developed for touchscreen Devices like mobile and tablet. Android is
also an open source Alliance. It means each user can customized android firmware according to
own requirement. Generally, we see each manufacture customized android operating system or
firmware according to his requirement and provide different UI to the user like Samsung and LG
device has the same operating system and same version but provide the different-different User
interface. This operating system takes input through touch from the user and provides solution
according to input provide by the user. Touch may be resistive or capacitive. Android is popular
in technology because it provides low-cost and customizable operating system for high-tech
devices.
It is the pure open source operating system, For example, an application can call any of the
phone's core functionality such as making calls, sending text messages, or using the camera.
Android is built on the open source Linux Kernel. It utilizes virtual machine (Dalvik virtual
machine) that was designed for optimizing memory and hardware resources in a mobile
environment.
Android does not differentiate between the phone's core applications or system applications and
third-party applications. They can have equal access to a phone's capabilities.
Android provides the wide range of useful libraries and tools that can be used to build
applications. For example, Android enables developers to Developed access the location of the
device and allows devices to communicate with one another social applications.

Mobile OS/Firmware In Market

There are a lot of operating systems available in the current market and around 70%
smartphone company uses the android operating system.

BADA- It is partially java based operating system and it was used in old Samsung non-
smartphone devices.

Simbian - It is partially java based operating system and it was used in old Nokia non-
smartphone devices.

J2ME- It is also java based pure operating system and it was used in old Nokia,samsung and
china non-smartphone Devices.

BLACKBERRY- It also java also based operating system but partially and it is used in
blackberry devices.

IOS- It is objective c based operating system and it is used in apple device like iPhone and
IPAD.

Windows- It is .net based operating system and is use in Nokia smartphone.

android- It is java based operating based operating system and it is used in around 70% device
like HTC, LG, Samsung, Micromax, Lemon, Carbon, Lava

Types of Android Devices

There are a lot of android devices available in the market like Smartphone, tablet, TV stick
(android TV), car(Android Auto), Digital Camera, glasses. These devices are very cheap and
easy to use and change the lifestyle of the human being.
Android Features
Messaging
Android provide two types of messaging SMS and MMS.SMS provide text messaging android
MMS provide image audio and Video Messaging. It also provides C2DM(cloud to device
messaging). It also provides push notification from server to registered device.

Web browser
Android web browser provides open source web kit.

Voice Features
Android provide the voice-based feature for text, voice, and calling.

Multi-touch
Android also provide the multi-touch feature.

Multitasking
We can do multiple tasks at a time in android, for example, we can listen to music and chat
together at same time.

Calling
Android include two types of calling features audio and video.

Multiple language support

Android support multiple languages by generalization.

Bluetooth and Wifi support

Android support Bluetooth and wifi which provide communication between different devices.
Bluetooth sends text, audio and video files between two devices and wifi provide internet data
connectivity.

Wifi Hotspot
Wi-Fi Hotspot connects internet data to another device.

Media
Android provide media support also like png, jpg, Gif, BMP (image) mp3, mp4, amr.wav (audio
and video) formats.
Screen Capture and Screen Recording
Android provide screen capture facility in all version and screen recording in kit-Kat and upper
version.

Data Storage
Android also provide data storage facility. There is three data storage facility in android device
first one os storage which contains app and system file the second one is internal data storage it
provides internal memory for data storage and the third one is external storage.

Sqlite
Sqlite use data storage in android application. It is a lightweight database.

Android versions
Name Version API level

Alfa 1.0 1

Beta 1.1 2

Cupcake 1.5 3

Donut 1.6 4

clair 2.0-2.1 5,6,7

Froyo 2.2-2.2.3 8

Gingerbread 2.3-2.3.7 9,10

Honeycomb 3.0-3.2.6 11,12,13

Ice Cream Sandwich 4.0-4.0.4 14,15

Jelly Bean 4.1-4.3.1 16,17,18

Kit Kat 4.4-4.4.4 19,20

Lollipop 5.0-5.1 21,22

Android version features

An droid 1.0 ( Alfa and API level 1 )

Android market
Web browser
Camera
Home screen
Gmail
Google contacts
Google map
Google search
Google talk
SMS and MMS
Media player
wifi
Bluetooth
YouTube
Alarm clock
Calculator
Dialer
 Gallery
Setting

Android 1.1 ( Beta and API 2 )

User business search on map
User can attach on messages

Android 1.5: ( cupcake and API 3 )

Support third party keyboard
Video recording
Pairing in Bluetooth
Copy and paste in web Browser
Use picture in contact
Attach date time in call log
Auto rotation
New stock boot animation
Ability to upload videos to YouTube

Android 1.6: ( Donut and API 4 )

Voice and text entry to search
Speech synthesis
Easier searching
Advance gallery and camera
Text to speech engine
Support for WVGA screen resolution
Expand gesture framework

Android 2.0-2.1: ( Eclair and API 5 , 6 , 7 )

Expand account sync
Bluetooth 2.1 support
Ability to tap a contact and select call SMS and email
Improve camera like flash support, digital zoom, scene mode
Improve typing speed of virtual keyboard
Browser UI with thumbnail
Optimize hardware speed
Support more screen size and resolution
Improve Google map
Live wallpaper
Android 2.2-2.2.3: ( Froyo and API 8 )
Enhance speed and memory
Add javascript to browser
Add c2dm
Improved launcher app
Add wifi tethering and wifi hotspot
User can disable data access
Add multiple keyboard facility
Improved Bluetooth
Add password facility
Enhance app memory
Adobe flash support
Add zoom gesture with gallery

Android 2.3-2.3.7: ( Gingerbread and API 9,10 )

Updated user interface
Add WXGA screen resolution
Faster and improve virtual keyboard
Add copy/paste function
Support NFC
New download manager
Add front and back end camera
Improved power management
Improve native development code
Improve audio graphics and input
Increase performance
Add more sensors
Add new API
Add Google talk
Add lib support for peripheral device
Improve network performance
Improve Gmail app
Improve camera
Improve battery efficiency
Add Google wallet

Android 3.0-3.2.6: ( Honeycomb and API 11,12,13 )

Add new holographic user interface
Add system bar
Add action bar
Add multitasking
 Redesign keyboard, fast typing
More function into copy/paste
Add multiple tabs in browser
New function in camera like focus flash zoom
Hardware acceleration
Support multiple core process
Add ability to encrypt data
Add secondary memory
Add recent app list
Resizable home screen
Support external keyboard
High-performance wifi lock
Improve hardware support
Ability to access app to sd card
Add new function to display
Improve android market
Improve Google ebook
Improve adobe flash

Android 4.0-4.0.4: ( Ice Cream Sandwich and API 14,15 )

Add holo interface
Separation of widget in a new tab
Improve visual voicemail
Pinch to zoom function in calendar
Add screenshot capture
Add lock screen
Improve copy paste
Improve voice integration
Add face lock feature
Enable and disable data
Ability to close recent app
Improve camera app
Built-in photo editor
New gallery layout
Add NFC
Hardware acceleration of the UI
Numerous bug fix and optimization
Improve to graphics, database,spell-checking
New API for developer
Improve calendar app
Improve camera app add QVGA
Better camera performance
Smooth screen rotation
 Improve phone no reorganization

Android 4.1-4.3.1: ( Jelly Bean 16,17,18 )

Bluetooth low energy support
Add ability to transfer audio/video to Bluetooth
OpenGL support
Dial paid autocomplete
Volume for incoming call
Rework camera UI
Smoother UI
Improve accessibility
Expandable notification
Ability to turn off notification
Shortcut and rearrange widget
Bluetooth data transfer for beam
Improve camera app
Multichannel audio
USB audio
Ability to add another launcher
Lock home screen rotation support
Lock screen improve
Notification power Control
Screensaver
Multiple user accounts
New clock app
Group messaging
Fixed Bluetooth audio streaming bug
Quick setting
New download notification
New alert for low battery
New gallery app animation
USB debug whitelist
Bugfix and improvement
Improve security
System-level support for geofencing and wifi scanning API
Add support more language
Change DRM API
Clock display in status bar

Android 4.4-4.4.4: ( Kit Kat and API 19,20 )

 Improve clock app
Ability to app to trigger translucency
Ability to use app in immersive mode
Menu button always visible
Improve performance
Wireless printing
Improve web view
Expand notification listener service
New framework UI
Audio tunneling and audio monitoring
Screen recording feature
Native infrared blaster API
Bluetooth message access profile support
Improve autofocus
Better app compatibility
Camera app can load google+ photo
Bugfix
Refreshed dialer app interface
Release smart watches
UI updates for Google map navigation and alarm
Offline playback
GPS support

Android 5.0-5.1.1: ( Lollipop and API 21,22 )

Support 64 bit CPU
OpenGL ES 3.1
Add material design
Refreshed lock screen
Refreshed notification
Quick search
Lock screen with shortcut
Audio and video input with USB
The third party can read and modify sd card data
Recent app remembered after reboot
Webview receiver update through Google play
Add 15 new languages
flashlight style app include
add the smart lock
few bug fix
quick control on wifi and Bluetooth from setting
support multiple sim cards
device protection
high definition voice call
 improve notification priority
fix memory leak issue

Android Architecture

The Android operating system architecture is a stack of software components of applications, an

operating system, run-time environment, middleware, services, and libraries. In this architecture,
each layer communicates with another layer for execution of any process.

This is the android architecture, it has five layer and it work from bottom to top.
Android ROM Architecture
Application Layer
This is the most upper layer in android architecture. This layer contains all Applications of
devices. There are two types of applications in android, first types are system applications like
phone contact, SMS, call and second types are third party applications which are installed
externally or from play store. System application cannot be Uninstall but Third party application
can uninstall by a user from the device.

Application framework
This is the second layer of the android structure. This layer contains set of services which is
required for android activity and reuses by other applications like that if we want to perform
calling so we will have to need telephony manager service to perform this task. So there are lot
of other services just like activity manager perform activity task and lifecycle task, window
manager perform system UI, content provider manage shared set of data of device like contact
and message, system view manage application widget, package manager manage all install
application packages, Resource manager manage another resource like String, color, and
layout, location manager manage map related functions, notification manager manage system
notification like battery, message, location.

Libraries
This layer divides into two parts one is android libraries and second is android runtime. Libraries
contain java based libraries and C/C++ libraries. Java libraries contain a lot of libraries.

Java libraries
android.app- this library has fully model of an android application.
Android.view-this library provide the user interface to the user.
android.widget-this library provide user interface component for an application like button, edit
text etc.
android.webkit-this library contains all classes regarding web server.
android.os-this library contains all classes for os just like message passing between activity
messaging.
android.media-this library contains media classes.
android.openGL- this library contains 3D graphic classes.
Android.provider- this library provides classes for the shared set of database or predefined
database.
android.content- this library contains all classes to use transfer data from one activity to other
activity.
android.database-this library contains all classes to use store data of any application.
android.graphics-this library contains all classes for graphic 2D and 3D.
android.hardware-this library contains all classes to interact with hardware like a sensor.
android.net-this library contains app classes for network programming.
android.util-this library contains all classes for string data conversion and collection framework.

C/C++ libraries
This library contains slandered libraries of C/C++. This libraries communicate between the
android driver and android libraries because all drivers developed with C/C++ libraries. This
library also used for NDK (native development kit).

Android Runtime
It is a type of JVM used in android devices to run apps and optimized for low processing power
and low memory environments. Android runtime contains core libraries which communicate with
the kernel. JVM provides the environment for multitasking execution. Each task executes
directly by the kernel in android.

Linux kernel
The fourth layer of android architecture is Linux kernel which provides communication between
hardware and software. The whole Android OS is built on top of the Linux Kernel. Kernel means
the core of Operating System. Linux kernel that interacts with the hardware and it contains all
the essential hardware drivers.
Drivers are programs that communicate with the hardware. For example, all devices have a
Bluetooth hardware in it. Therefore the kernel must include a Bluetooth driver to communicate
with the Bluetooth hardware.

Android drivers
This is the fifth layer of the android architecture. This layer provides all drivers which are
necessary for android device. Android drivers communicate between hardware and Linux
kernel. Drivers recognize the hardware and perform talk with software or we can say that it
perform exactly what we want with hardware, for example, suppose we want to extend out
device memory for this task we will need flash memory driver which recognize external memory
then process to software.

Android hardware
This is the last layer of android architecture which contains device hardware. We can easily
understand by this diagram
Flow of android execution
From above Diagram, we can easily understand that the execution of any task done from
bottom to top. For example, supposes we want to perform any action on our device then firstly
we will have to interact with device hardware by touchscreen or any other hardware. then
screen recognize what action you want to perform and hardware interact with the driver
according to your requirement for example if you want to play music then will go to the audio
driver or if want to use wifi it goes to wifi driver. The driver interacts with libraries by Linux kernel
then the process will be forward to Native libraries Because Native libraries used to develop
android operating system files, then it forwards to java and android libraries to execute the
process. java libraries contain core libraries android libraries predefined classes just like calling
messaging etc. then finally application perform the task.
Chapter 2 android ROM HAL Audio and Bluetooth Architecture

Hardware abstraction layer

It is the main layer of the android architecture. This layer provides Communication between
hardware and software, mean that it provide communication between android driver and android
services. Android open source provides the facility that you can download the android software
and customize this software according to your requirement. HAL contain audio, graphics, wifi,
Bluetooth, camera, media and storage drivers.

A hardware abstraction layer (HAL) is a logical division that provides communication between a
computer's physical hardware and its software. It provides a device driver interface allowing a
program to communicate with the hardware.

The HAL, or Hardware Abstraction Layer, provides the application developer with a set of
standard functions that can be used to access hardware functions without a detailed
understanding of how the hardware works.
Low-Level android architecture
Hardware Abstraction Layer
Application Layer
This Layer has all application including system and third party application. Application Layer
provides User interface to the user that interact directly to the user for example contact,
messaging, calling etc.

Application Framework
Android framework provides API to provide android libraries to user applications. The
application may be system applications or third party applications.

JNI (java native Interface)

JNI provide core code for android libraries or android API.

Native Libraries
Native libraries provide the interface to system API. These files are written in c/c++ code.

IPC (Inter Process Communication)

IPC provide Communication between different processes.

Services
Services are bang round process which provides the interface between API. There are two
types of services, system service and media service. System service includes Window and
notification services and media service includes Media player and Media Recording.

HAL (Hardware Abstraction Layer)

HAL provide communication between hardware with software. It provides Interface with your
hardware and drives.

Kernel
Linux processes any task with providing resources with adding hardware and software. It is the
link of hardware and software.

Drivers
This layer provides all drivers which are necessary for android device. Android drivers
communicate between hardware and Linux kernel. Drivers recognize the hardware and perform
talk with software or we can say that it perform exactly what we want with hardware, for
example, suppose we want to extend out device memory for this task we will need flash
memory driver which recognize external memory then process to software.

ROM Audio Architecture

Android is Linux at heart, it uses modified Linux Kernel optimized to battery and memory. It's not
just advanced in terms of features, but also the best sounding.

We had been running Linux PC as our Audiophile system for a year now, and it simply beats
every other OS ever built when it comes to bit-perfect audio.

It provides AudioFlinger interface to applications that interact with Libaudio (HAL), hiding the
unnecessary details.
Audio Architecture has mainly two process media player and media recording.
ROM Audio Architecture
Application Layer
The application layer of audio architecture includes media player application and media
recording application.

Application framework Layer

Android framework layer includes android.media library which accesses JNI.

JNI
JNI access by Application framework layer and it contain java core code. It is located in
framework/base/core/JNI and framework/base/media/JNI folder.

Native Libraries
Native libraries contain c/c++ core libraries which communicate with android.media API. It is
located in framework/av/media/libmedia.

IPC (Inter-process Communication)

IPC provides communication between different processes. It is also located in
framework/av/media/libmedia.

Media Service
Media service providers interface with HAL. It is located in framework/av/services/audio flinger.

HAL
HAL provide the interface with audio hardware component with audio HAL. It is located in
device/vendor/product/audio.

Kernal
The Main work of Kernel is that executes the process and provide the interface with the driver
with native code.

Driver
Driver layer contains audio drivers.
ROM Bluetooth Architecture

Android support Bluetooth and wifi which provide communication between deferent devices.
Bluetooth sends text, audio and video files between two devices and wifi provide internet data
connectivity.

The Android platform includes support for the Bluetooth network stack, which allows connecting
a device to wirelessly exchange data with other Bluetooth devices. The application framework
provides access to the Bluetooth functionality through the Android Bluetooth APIs. These APIs
wirelessly connect to other Bluetooth devices, capable point-to-point, and multipoint wireless
features.
Bluetooth architecture executes all Bluetooth related application and provides API to third party
applications.
ROM Bluetooth Architecture
Application Layer
The application layer of audio architecture includes Bluetooth applications.

Application framework Layer

Android framework layer includes android.Bluetooth Libraries which access JNI and interact
with Bluetooth hardware.

JNI
JNI access by Application framework layer and it contain java core code. It is located in
package/app/Bluetooth/JNI.

Native Libraries
Native libraries contain c/c++ core libraries which communicate with android.Bluetooth API.

IPC (Inter-process Communication)

IPC provides communication between different processes.

System Service
Media service providers interface with HAL. It is located in package/app/Bluetooth.

HAL
HAL provide the interface with audio hardware component with android.Bluetooth libraries. It is
located in hardware/libhardware/include/hardware.

Kernal
The Main work of Kernel is that executes the process and provide the interface with the driver
with native code.

Driver
Driver layer contains Bluetooth drivers.
Chapter 3 Android ROM Sensor & Graphics Architecture

ROM Media Architecture

The Android system provides APIs for recording and playing audio and video, and for using the
built-in camera as an input device.

Supported Media Formats

The media codec, container, and network protocols supported by the Android platform.

MediaPlayer
The MediaPlayer class provides basic audio and video playback capabilities.

MediaRecorder
The MediaRecorder class provides basic audio recording capabilities using the device's
microphone.

Media Routing
Apps use the Android routing APIs to play audio and video on remote devices.

Camera API
The Camera API is used to specify image capture settings, start/stop imaging preview, take
pictures, and retrieve the raw video.

The Android multimedia framework contains support for playing various of common media
types, so that you can easily integrate audio, video and images into your applications. You can
play audio or video from media files stored in your application's resources (raw resources,
assets) using MediaPlayer APIs.
In media, architecture executes all media application and provides API to third party
applications.
android ROM Media Architecture
Application Layer
The application layer of audio architecture includes media applications.

Application framework Layer

Android framework layer includes android.media Libraries which access JNI.

JNI (java native Interface)

JNI provide core code for android libraries or android API.

Native Libraries
Native libraries provide the interface to system API. These files are written in c/c++ code.

IPC (Inter Process Communication)

IPC provide Communication between different processes. It is also located in
framework/av/libmedia.

Media Service
It is the multimedia framework which provides the engine for audio and video Record. For this
process use mediaplayerservice.cpp and located into
framework/av/media/libmediaframewrokservice.

OMX Integration
OMX Integration provides interface with the hardware-based component.

ROM Sensors Architecture

Android has built-in sensors that measure motion, orientation, and various environmental
conditions. These sensors are providing raw data with accuracy and provide three-dimensional
device movement or positioning, or you want to monitor changes in the environment near a
device. For example, a game might track readings from a device's gravity sensor to infer
complex user gestures and motions, such as tilt, shake, rotation, or swing. Likewise, a weather
application might use a device's temperature sensor and humidity sensor to calculate or a travel
application might use the geomagnetic field sensor and accelerometer to report a compass
bearing.
Sensors Architecture executes all applications which are related Sensors.
android ROM Sensors Architecture
Application layer
The application layer of audio architecture includes Sensor applications.

Application framework Layer

Android framework layer includes android.hardware Libraries which access JNI and interact with
Bluetooth hardware.

JNI (java native Interface)

JNI provide core code for android libraries or android API. Its provide interface with
android.hardware API. This included in frameworks/base/core/JNI folder.

Native Libraries
Native libraries provide the interface to system API. These files are written in c/c++ code. This
included in frameworks/native folder.

IPC (Inter Process Communication)

IPC provide Communication between different processes.

Sensor Service
Sensor service provides interface with HAL.

Sensor HAL
Sensor HAL provides userspace. It provides Interface with your hardware and drives. Its contain
sensors.h and sensors.app files. Its located into hardware/libhardware/include/hardware.

Sensor Driver
Sensor driver contains input event and sensor hub driver which understand by the kernel.

Sensor Hub
Sensor hub use in low-level computation.

Batching
Batching process is used to store sensor event in hardware in FIFO to process to HAL.

Sensor Types
Base Sensor
This types sensor associated with hardware
ACCELEROMETER
GYROSCOPE
MAGNETOMETER

Composite Sensors
A sensor which not associated with the base sensor is called composite sensor.

ROM Graphics Architecture

android Provides low-level graphics features such as canvases, color, points, and rectangles to
drawing to the screen directly.

The Android framework provides a various of graphics APIs for 2D and 3D that interact with
manufacturer implementations of graphics drivers, so it is important to the understanding of how
those APIs work at a higher level. This page introduces the graphics hardware abstraction layer
(HAL) upon which those drivers are built.
Application developers draw images to the screen in two ways: with Canvas or OpenGL.
Graphics Architecture executes all applications which are related to 2D and 3D graphics.
android ROM Graphics Architecture
Application Layer
This layer contains media player app, camera applications, OpenGL app.

Application Framework
This Layer includes window Manager Lib and OpenGL lib.

JNI (java native Interface)

This layer contains core code like surface.cpp, GLConsumer.cpp files in
frameworks/native/lib/gui folder.

2D and 3D Engine
This layer contains java lib for 2d and 3d Graphics.

Composition with HwComposer

HwComposer used to combine specific surface layer supported by the specific vendor. And HW
composer Disable by removing /System/lib/hw/hwComposer.imx6.so. Its a hardware lib file.

HwComposer HAL
HwComposer HAL Layer provides interface HwComposer with CPU 2D core layer.

Display Frame Buffer

Frame buffer display takes input from hardware and provides output to display. For this used to
the high-speed semiconductor.

Modern Graphics System

ROM above figure we can easily understand Application access graphics and android graphics
lib contain OpenGL or Direct3D lib. Its provide communication between application part and
hardware part and hardware part provide input to the system.
Chapter 4 Android ROM DRM Storage and IO Architecture

ROM DRM Architecture

The Android platform provides an extensible DRM framework that lets applications manage
rights-protected content according to the license constraints associated with the content. The
DRM framework supports many DRM schemes; which DRM schemes a device supports is up to
the device manufacturer.

DRM is an acronym for Digital Rights Management. Android developers include DRM licenses
in applications that protect their best interests. The DRM framework on your Android device
makes the use of DRM licenses possible. Android DRM licensing is free service offered to
Android application developers who publish apps through the Android Market.
android ROM DRM Architecture
Application Layer
Application layer contains many android apps which provide interface with application
framework layer.

Application Framework
Application framework layer contains android.media.mediacrypto API which accesses by the
application layer.

JNI
This API contain core code of c/c++ code. It is located in frameworks/base/media/JNI folder.

Native API
Native API associated with JNI API and it located into frameworks/av/media folder.

IPC
IPC provide the direct link between different processes. Its contain Icrypto.cpp and Imedia*.cpp
and its located in to frameworks/av/include/media directory.

Media Service
Media service providers interface with HAL it contains in Crypto.cpp. It is located in
frameworks/av/media.

ROM Storage Architecture

Android supported external storage accessories (such as SD cards), but these accessories
have limited to simple file storage and minimal data protection Android 6.0 introduces the ability
to adopt external storage media to act like internal storage.
When external storage media is adopted, its store data in encrypted to only work with a single
Android device at a time. Because the media is strongly tied to the Android device that adopted
it, it can safely store both apps and private data for all users.

When users insert new storage media (such as an SD card) in an adaptable location, Android
asks them how they want to use the media. They can choose to adopt the media, which formats
and encrypts it.

Storage Architecture provides storage API to third party Applications.

android ROM Storage Architecture
Application Layer
This is the most upper layer which can contain many storage applications like file manager etc.

Application framework Layer

This is the second layer of storage Architecture which contains Android storage API like the
content provider. For this Layer used android.os.storage lib.

JNI (Java Native Interface)

This Are java lib which provides the interface between native lib android lib.

Native Libraries
Native Libraries is a most important layer in this architecture. Native Libraries provide the
interface between java lib android IPC because both IPC and java lib used this layer.

IPC
IPC provide communication between native lib and different Applications.

Service
This layer contains Mount Services which provide declare memory related all Information about
the device.

HAL
HAL layer is a most important layer in this architecture which provides communication between
android driver part and application part.

Driver
Driver layer contains many android drivers which provide the interface between hardware part
and low-Level application part.

android ROM I/O Architecture

Input/output Architecture provides all APIS for Input/output data to access by this party
application.

Device drivers are software modules which plugged with an OS to handle a particular device.
Operating System takes use device drivers to handle all I/O devices. Device drivers are low-
level programming t code and implement a standard interface in such a way that code contains
device-specific register reads/writes. The device driver is generally written by the device's
manufacturer.
android ROM I/O Architecture
Application Layer
Application Layer is a most upper layer in android I/O Architecture. This Layer Contain much
Application for input Declaration like that touch screen or game, Key layout mostly all
applications.

Application Framework Layer

Application framework layer Support application layer and provide android libraries to the
application layer.

JNI
Java native libraries are java libraries which support to android libraries like 2D and 3D
graphics, OpenGL.

Native Libraries
Next Level is native libraries which support to java or we can say that access by java native
library.

IPC (Inter Process Communication)

IPC provide Communication between different processes which provide the link between
applications.

Services
This layer contains all services to related devices it may be system services or server services
depend on the talk which does you want to be executed.

HAL
HAL layer performs linking between to layer or we can say that its associated hardware and
low-level software layer.

I/O Layer
This layer provides input to the device by software. We may provide input by touch screen or
key layout we will learn about key layout later.
Chapter 5 Android ADB Command

What is ADB Command

ADB (android debug bridge) are the command which provides communication with the android
device or emulator or we can control the whole device with commands. We can interact with
ROM through ADB commands. Like In PC we can interact with kernel level through cmd
commands as at same we can interact at kernel level by ADB commands. Some commands
may work or not because of all device control through by providing root and devices read-write
permission. We can provide root in our device by two types first by externally and second by
internally we will learn deep later about rooting. This command may work on some device and
may be not in some device the reason behind this because we can see there is lots of different-
different ROM available in currently in the market like stock ROM, Rockchip ROM, MTK ROM
etc. Each ROM directory structure is different.There are two types of commands we find in
android ADB command and shell command.

ADB file in the android device located in /system/bin directory.

In below picture, we can see ADB file in device
To run ADB command connect your device with the computer using USB and type ADB devices
here.
This command show all devices which are connected with PC at this time.

ADB Command

ADB (android debug bridge) are the command which provides communication with the android
device or emulator or we can control the whole device with commands. We can interact with
ROM through ADB commands.
ADB, Android Debug Bridge, is a command-line utility included with Google's Android SDK.
ADB can control your whole device using USB from a computer, copy files, install and uninstall
apps, run shell commands.

How to Run ADB Command in android

There are following the step to apply to execute ADB command.

1) For ADB commands firstly you will have to connect your device through USB debugging
mode or you will have to on USB debugging to going developer option in setting application in
the device.
2) Next, connect your device with the system by USB cable.

3) and check USB debugging check box.This Step provides authorization to the user for
debugging.

4) Go to the platform-tools folder in SDK and press ctrl+shift and right click there.

5) Press open command window here.

6) type ADB devices here.

Types of ADB Commands

Their lots of ADB commands available in android which shows information about the android
device and we can change android device internal file, data, and setting. It means we can break
manufacture device limitations.

1) Android ADB command Syntax

If a single device is connected to the system no need to specify it but if more than one device
are attached with the system you will have to specify target device by d, e, and s.

Ex: adb [-d|-e|-s <serial no> <command>

2) ADB device command

To check how many devices are connected to your PC so we run this command.

Ex: ADB devices

3) ADB push command

ADB, push command use to move a file from your system to android devices.
Ex: adb push <path of source file> <path of destination file>

4) ADB pull Commands

ADB, push command use to move a file from your device to system.

Ex: adb pull <path of destination file> <path of source file>

5) ADB Reboot command

ADB reboot command uses to restart your device or we can say boot again.

Ex: adb reboot

6) ADB reboot recovery command

If you want to go in device recovery mode you will have to use ADB recovery command. With
help of this command, you can change your device setting like reboot or if you want to install
any shell script or flashing Rom.

Ex: adb reboot recovery

7) adb reboot-bootloader command

This command use to reboot your device into bootloader mode (white screen with android
wheels).Once you are in bootloader, ADB Wont work anymore.

Ex: adb reboot-bootloader

8) Fastboot command
Fastboot command uses to unlock your device and modify your it.

Ex: fastboot devices

9) fastboot oem unlock command

fastboot oem unlock command to use to unlock your bootloader and make possible to root
access. In some device like nexus, your device needs to root access or super user permission
you will have to need this command to do it.

Ex: fastboot oem unlock

10) fastboot flash recovery command

fastboot flash recovery command to use flash custom recovery image to your device.

Ex: fastboot flash recovery

11) adb restore command

adb restore command use to restore and back your device all data in form of zipping file.
Ex: adb restore C:\[restorefile].zip

12) adb sideload command

ADB sideload command to use to push and flash the android custom ROM and zip file in your
device. With help of this command, we can put your ROM zip file into your device and starts to
flash it.

Ex: adb sideload <path of zip file>

13) Install an apk file

If you want to push an apk on your device and install it so we use install apk command.

Ex: adb install <apk path>

14) Uninstall an apk file

We can unstill also an apk file using unstill apk adb commands.

Ex: adb unstill <package name>

15) adb remount command

Sometimes you may need to read write permission so ADB remount command uses to remount
the system partition in your drive and provide the device to read and write permission.

Ex: adb remount

16) adb logcat command
This command mostly uses in android debugging your android device. When you start your
device various process running on your device or in another word various log run in your device
so this command use to view various log.

Ex: adb logcat

17) adb Kill server and start server command

Sometimes your adb may be stuck so this is the common problem so you kill your adb with this
command. And again you can start your adb with start server command.

Ex: adb kill-server Ex: adb start-server

19) Adb backup

This command use to take all data backup in database file .db

Ex: adb backup all f /temp/backup.db

From above picture, this command unlocks your device and takes backup in form of database.

20) adb restore command

adb restore command use to restore all backup data reverse in your device.

Ex: adb restore /tem/backup.db

Chapter 6 ABD Shell Command In android

ADB Shell Commands

In this Chapter, we will discuss android shell commands like root status, ls command, cp
command etc. which are necessary for any developer or any android user.

in below picture, you can see shell command structure.

What is shell command?
Shell is programs that listen to keyboard input from the user and display output to the user. We
run the shell command like cmd command in the system. If our device is rooted we can read,
write and edit system file with the shell command. This contains in system/bin/ directory. This
command may work on some device and may be not in some device the reason behind this
because we can see there is lots of different-different ROM available in currently in the market
like stock ROM, Rockchip ROM, MTK ROM etc. Each ROM directory structure is different.

1) Check root status

This command checks this device is root status. Rooting is broken manufacture limitation of the
device. We will learn about rooting in next chapter. From above figure, we can see that
shell@android:/$ in output this sign indicate that device is non-rooted device if it will be
shell@android:/# than it will be the rooted device.

2) Su Command
Ex: adb shell su

Su command indicates that this device provides super user permission to the user. If the device
uses a super user we can do anything with device or we can modify device according to our
requirement.

From above picture, we can see clearly that su file not found in /system/bin directory this
indicate that device has no power permission to the super user.

3) ls shell Command
ls command uses to find all folder and files in the directory.
Ex: adb shell ls

From this picture, we can see that these are all directories and files in root directory.

4) cd shell command

cd command uses to switch from one directory to another directory or from current directory to
another directory.

Ex: cd <current directory> <other directory>

5) cp shell command

cp command uses to copy data from one directory to other or we can say that its copy data from
system to device or device to system.

Ex: mv /system/app/example.apk > /sdcard/example.apk

in above picture, we copy data from system app to sd card.

6) cat shell command

cat command also uses to copy data from one directory to other or we can say that its copy data
from system to device or device to system.

Ex: cat <source path> <destination path>

7) Move Command
It is also the format of copy command .it move the file from source to destination.

Ex: mv /system/app/SystemUI.apk /sdcard/ SystemUI.apk

8) rm Command

rm command uses to remove any directory or ant file from the device.

Ex: rm <path of the file>

9) Mount Files system command

Mount file system command use to mount the partition to read/write to the file in the device we
can say that it provides read/write permission to the device.

Ex: mount o rw, remount -t ysffs2 /dev/block/mtdblock3 <path of directory>

10) exit command

exit command use for exit from the shell command.

Ex: exit
Chapter 7 Activity Manager Commands in android

In this Chapter, we will learn about different activity manager command. For this commands, we
can know all information about any device application activities.

What is Activity manager commands

Activity manager commands are ADB shell commands which are use for any application Activity
and these commands perform many actions with activity. This command is used to start an
activity, stop any activity, broadcast any intent modify ant device screen properties and much
more.
And syntax is.
am <command>

Activity manager commands start with am the syntax. The may include intent specification.

<intent> Specification includes these Flags:

-a: <ACTION>
-d :< DATA_URI>
-c :< CATEGORY>
-t :< MIME_TYPE>
-e :< EXTRA_KEY>
--es:<EXTRA_STRING_VALUE>
--esn: <EXTRA_KEY>
--ez: <EXTRA_KEY> <EXTRA_BOOLEAN_VALUE>
-n :< COMPONENT>
-f: <FLAGS>

Start Activity command

If we want to start any activity from ADB commands so use start activity
command for it.

ex: am start <package name>/.<activity name>

or

am start<intent>

1) open menu
1) open menu
This is command will open complete action menu of your device. For this, we pass access intent
and start will initiate intent. We just need to know what kind of intent we need.

Ex: am start <Intent>

And the output of this command is below.
2) open web page
2) open web page
We can also open a web page directly using am start command.

Ex: am start http://www.google.com

And the output of this command is in below picture.
3) Current location
3) Current location
We can open the map and find out the current location of our device using this command.

Ex: am start geo: 0,0q=Delhi, India

And the output of this command is.
4) add delete or modify device contacts
You can also add, edit or view your device contacts.

Ex: am start content: //contacts/people

And the output of this command is below.
And we can add or create a contact using start command.

Ex: am start -a android.intent.action.INSERT -t vnd.android.cursor.dir/contact -e name

'Android Auto' -e phone 1234567890
And the output of the command is.
5) calling
We can also make a call using start command.

Ex: am start -a android.intent.action.CALL -d tel:777

And out of this command is.
6) Start Service
From this command, we can start ant device service.
Ex: am startservice n <package name>/.<service name>
Or

am startservice <Intent>
7) Kill package
Kill package command use to kill the whole package including all activity and service. This
command kills all process in a package in safe mode and does not affect other processes.

Ex: am kill <package name>

8) Kill all services

This command kills all background services and taped up your device and efficiency.

Ex: am kill-all
9) Broadcast
This command use to access our device any broadcast receiver class.

Ex: am broadcast <package name>/.<name of broadcast>

Or

am broadcast <Intent>

10) Force Stop package

Force stop command uses to force stop any package.

Ex: am force-stop <package name>

11) Instrument
Instrument commands use to start monitoring with an instrument instance. These commands use to testing
purpose of the device.
Ex: am instrument -w <test_package_name>/<runner_class>

Instrument commands use to start monitoring with an instrument instance.

These commands use to testing purpose of the device.

Ex: am instrument -w <test_package_name>/<runner_class>

And component of package in form <test_package>/<runner class>. am instrument -w

<test_package_nwhere <test_package_name> is the Android package name of your test
application, and <runner_class> is the name of the Android test runner class you are using
-w flag use to Forces an instrument to wait until the instrumentation terminates
before terminating itself.
-r flag use to view result in raw format.
-e<TEST_OPTIONS> flags use Provides testing options as key-value pairs.

We can test a class in three types

unitTests
functionTests
IntegrationTests
12) Debug app
We can debug the android application using the command.

Ex: as set-debug-app <package name>

13) Clear debug app

Clear debug app command use to clear debug data in a package.

Ex: am clear-debug-app

14) Monitor
Sometimes we may be got error in our programs like unfortunately crash or ANR (application
not responding )
To check this command we use monitor command to resolve it.

Ex: am monitor [option]

15) Screen compact

In some time we may need to adjust package screen compatibility to adjust screen resolution
compatibility so we use this command for this purpose or we need to control screen resolution.

Ex: am screen-compat [on|off] <package name>

16) change screen size

This command use to adjust device screen size according to user requirement.

Ex: am display-size<screen size in pixel>

17) Change screen density
This command change device screen display density.

Ex: am display-density<dpi>
Chapter 8 Package Manager Commands in android

What is Package Manager Commands

Package manager (pm) command apply to all android package it may be system application or
third-party application packages. We can perform actions and queries on application packages
installed on the device.

1) List package
This command use to view all android application packages on your device.

Ex: pm list package

We can also filter the list of packages.

Ex: as list packages [options] <FILTER>

And types of filter
-f: view associated file.
-d: view disabled packages.
-e: view enabled packages.
-s: contain system packages.
-3: view third party packages.
-i: contain installer for the packages.

-u: include uninstalled packages.

2) List group permission

List permission group command use to show all group Permission which used for android
application package in the device just like the camera, battery, network etc.

Ex: pm list permission-groups

We can filter groups.
-g: Organize by the group.
-f: Print all information.
-s: Short summary.
-d: Only list dangerous permissions.
-u: List only the permissions users will see.

Ex: pm list permissions [options] <GROUP>

3) list instrumentation
This command shows the list of all test packages.
Ex: pm list instrumentation f

-f : Use for the list of apk files.

4) System features
It shows all features of the device just like the camera, Bluetooth, network, and map etc.

Ex: pm list features

5) list of libraries
This command use to show all android libraries in which are use in device currently.

Ex: pm list libraries

6) List users
This command show list of all users currently uses in the device.

Ex: pm list users

7) apk Path
Through this command, we can find apk full path in the device.

Ex: pm path <package name>

8) Install application

From this command, we can install any apk in any specific location in our device.

Ex: pm install [option] <path>

There are many types of option for installation.

-r: Reinstall an existing app, keeping its data.

-t: Allow test APKs to be installed.
-i: Specify the installer package name.
-s: Install the package on the shared mass storage (sd card).
-f: Install the package on the internal system memory.

-d: Allow version code downgrade.

9) Uninstall Application
This command use to uninstall any application from the device.

Ex: pm uninstall <package>

We can keep the data and cache directories using option

Ex: pm uninstall [option] <package>

10) Clear package

This pm command uses to clear all data associated with the package.

Ex: pm clear <package name>

11) Enable package component
This pm command uses to enable any package or component like the class in your device.

Ex: pm enable <package or class name>

13) Disable package or component

This pm command uses to disable any package or component like the class in your device.

Ex: pm disable <package or class name>

14) Granted permission

This command use to provide user permission to package.

Ex: pm grant <package permission>

15) Set install location
This command use to install any application on particular location
Ex: pm set-install-location <LOCATION>
We can install in three locations
0 [auto]-represented to system location
1[internal]- represented to internal location

2[external]- represented to system location

Chapter 9 Screenshot and Screen Recording in android

In the early days of Android taking a screenshot on a phone or tablet was a painful activity, but
now the ability to take a screenshot is built into the OS. In this Blog, we show you how to take a
screenshot on an Android smartphone or tablet, including the Samsung Galaxy S7, HTC 10,
Sony Xperia XZ, LG G5, Google Pixel and other Android phones and tablets.

There are lots of new features in android. The main important features Screenshot, in android
kit-kat. Screenshot available in all versions of android but screen recording feature is available
on kit-kat or higher level versions.

To make the Android phone screen video capture easy. There are lots of android application
have been build for android Screen capture and-and screen Recording or we can capture and
recording using and command too.

Screenshot
We can take the screenshot of many types in android like using the hard button or using android
ADB command android programming and it is saved in screenshot directory in sd card. To take
the screenshot using the hard button we will have to press and hold home power and volume
button at same time.
Screenshot file in the android device located in /system/bin directory.
In below picture, we can see screencap and screenshot files in the device.

Screenshot using ADB command

Note: Here, we'll complete the task with the Windows version. As a Mac user, you can take the
similar steps as well.

We can take the screenshot with ADB command.

Ex: adb shell screencap p <path to storage>

We can pull this screenshot image

Ex: adb pull/sdcard/screen.png

We can also delete this screen shot using this command

Ex: adb shell rm /sdcard/screen.png

Screen Recording
There are lots of improvements done in KitKat and one of the features is screen recording.
Screen recording is the shell command use to record device screen in video presentation form.
We get screen record achieved in form of MPEG. Screen recording feature available in KitKat
(API level 19) or higher version.

Screen Recording using command

Ex: adb shell screenrecord <path of file>

We can stop screen recording by press ctrl+c otherwise recording will be stopped in 3 minutes
automatically.
There are some limitations of screen recording.
1) in some screen recording may be not work in the high-resolution device so always use the
low-resolution device for screen recording.
2) screen rotations do not support by screen recording.

3) audio does not support.

Set size of screen recording

We can set the size of the screen but default screen size is 1280*780.

Ex: screenrecord size<width*height> /sdcard/screen.mp4

Set bit rate of screen recording
As well as we can set bit rate of screen recording. The bit rate of screen record is set in form of
megabit per second and the default value is 4Mbps.
Bit rate=1/video quality
It means if we increase bit rate then video quality will be decreased.

Ex: screenrecord --bit-rate<rate> /sdcard/screen.mp4

Set time limit of screen recording

As well we can also set the time limit of screen recording. The recording time is set in form of
second and the default time is 180(3 seconds).

Ex: screen record --time-limit<time> /sdcard/screen.mp4

Set rotation of screen recording

We can also set screen rotation of recording

Ex: screenrecord --rotation <degree> /sdcard/record.mp4

Verbose
Verbose display log information on display .if you does not set any option in command utility it
does not display any information

Ex: screen record verbose /sdcard/screen.mp4

Other android commands

There are lots of other commands in android like monkey testing, SQL database commands, log
cat commands and server commands.
UI/Application Exerciser Monkey command

This is also shell command use to testing purpose of any device and application or in another
word we can say that use to debug app or device. This application test system event like click,
volume, touch, gestures.
Ex: adb shell monkey v -p <app package name> 500

Where v is verbosity and p represent package name.

Sqlite database command
With SQLite database command we can manage a database which creates by an application.
There are lots of ADB commands like .dump which show the output of the table and .schema
create a table.

Ex: adb shell squlite3 data/data/<package name>/database/<database name>

Other ADB Commands

Restart USB:
ADB USB restarts USB mode.
Ex: adb usb
List of device
We can show all device which attached with USB.
Ex: adb devices
Restart host
We can start host with ADB commands.

Ex: adb tcpip 5555

Other shell Commands

All shell programs are located in the bin directory in the system directory and the help of this
program we can run all commands.

Ex: adb shell ls /system/bin

You can see in the picture there are lots of programs.

1) dumpsys
2) dump state
3) dmesg
4) Start
5) 5) stop
Chapter 10 dumpsys Commands in android

dumpsys Commands

Dumpsys is the tool to get various information from the android device and show to the user,
this means we can find device information by dumpsys program and these commands also use
for testing of the android device.

1) EMEI No/phone Information

We can find device EMEI number and device id of any device.

Ex: adb shell dumpsys iphonesubinfo

2) Device battery
We can find information about device battery from this program like battery manufacturer name
and status and the other information.

Ex: adb shell dumpsys battery

3) WIFI
From this command, we can view all information about device wifi like wifi name, wifi address
and other information.

Ex: adb shell dumpsys wifi

4) CPU
From this command, we can also show all information about device CPU.

Ex: adb shell dumpsys cpuinfo

5) Location
This dumpsys program show about your device current location.

Ex: adb shell dumpsys location

6) Disk Memory
This command provides information about disk space like total disk space, cache space,
available space.
Ex: adb shell dumpsys diskstats

7) Network
This command provides full information about your device network.

Ex: adb shell dumpsys netstat

8) Provider
This command provides information about our device content providers full information like
phone contact information or message or WhatsApp contact information.

Ex: adb shell dumpsys telephony.registry

9) User Permission

This command provides information about all permission which uses by in all applications in the
device.
10) Process and PID
This command provides all information about all processes and all process id's about of device.

Ex: adb shell dumpsys meminfo

11) Account
This command provides all information about all account of the device like Google account or
another application account like WhatsApp account link dean account and yahoo account.

Ex: adb shell dumpsys account

12) Activities
This command provides all information about all activities use the device like that app name,
app package name, activates and provider as well as service.

Ex: adb dumpsys activity

13) Window
This dumpsys command use to show window display information like keyboard and z-order.

Ex: adb shell dumpsys window

14) Alarm
This command use to show all information about alarm and alarm intents.

Ex: adb shell dumpsys alarm

15) GFX

This command shows all information about gfx use in the device just like OpenGL lib and
classes.
16) Surface Flinger

This command shows all information about Graphics of your device.

17) Storage Manger

Ex: adb shell dumpsys devicestoragemonitor

This command also shows storage manager like internal, external and cache memory.
18) Network Management
This command shows all information about device network management.

Ex: adb shell dumpsys network_management

19) Notification
This command shows all information about all notification received to the device.

Ex: adb shell dumpsys notification

20) Application Widget
This command provides full information about all application widget.

Ex: adb shell dumpsys appwidget

21) Audio
This command provides information about audio like audio recorder, audio player, audio types,
and audio volume.

Ex: adb shell dumpsys audio

22) Backup
This command provides information about system backup like last back information, backup
size, which applications use for backup.

Ex: adb shell dumpsys backup

23) Clipboard
This command provides information about clipboard like clipboard manager.

Ex: adb shell dumpsys clipboard

24) Content
Content class shows the data so this command display full description about content manager
classes use in the android device.

Ex: adb shell dumpsys content

25) Input Method

This command provides information about input methods like keyboard and other input in
android device.

Ex: adb shell dumpsys input_mehtod

26) Camera
This command explains about device camera and camera application which use to the camera
and other information just like camera quality.

Ex: adb shell dumpsys media.camera

27) Storage
This command explains about storage method of the device just like that storage type, storage
path, storage partition and other information.

Ex: adb shell dumpsys mount

28) Player
This command provides information about media player just like audio recording and other
media player classes.

Ex: adb shell dumpsys media.player

29) Power Management

This command provides information about power management just like power conception,
power management classes.

Ex: adb shell dumpsys power

30) Search
This command provides information about search application and search classes.

Ex: adb shell dumpsys search

31) Sensor
This command full explains about sensors just like accelerometer and sensor services.

Ex: adb shell dumpsys sensorservice

32) Status Bar
This command provides describe status bar like icon list, status bar notification.

Ex: adb shell dumpsys starusbar

33) Gesture
This command provides information about gesture application and gesture classes.

Ex: adb shell dumpsys gesture

34) Wallpaper
This command provides information about wallpaper just like wallpaper classes and wallpaper
services.

Ex: adb shell dumpsys wallpaper

Chapter 11 Key Layout in android

In this Chapter, we will learn about key layout, key layout structure, storage location, types of
key layout and description about keys.

Key layout

Key layouts are files in the format of .kl which use to run key event by Linux device. There are
no of the specific predefined key used in the android device like home, back, menu and other
keys. There are two types of keys in android one is hard to button keys and other is soft button
keys.

Key Layout file storage Location

Around all key layout files are located in key layout folder which path is
/system/user/keylayout/ and some files are may be located in
/data/system/device/keylayout/ folder in android device.
You can understand better with the picture.

The main file of the key layout is genric.kl which content all key of keyboard and joystick.

Key Declaration
There is an each key has the specific role and performs the specific action when press it in
android device and each key assign a specific role just like that key 102 will be referred to home
button so each key has some specific reason to use.
Some files are using some specific sentence. There is some sentences use with some key.

WAKE: wake mean that this key use when the device will be wake or screen will be in on
mode.
WAKE_DROPED: wake mean that this key use when the device will be wake or screen will be
in off mode.
SHIF: use for the shift.
CAPS_LOCK: use for Capital Letter.
ALT: use for alt key press.
ALT_GR: use for right alt key press.
FUNCTION: use for function key press.
VIRTUAL: use for the softkey press.

MENU: use for menu key.

Keyboard Key
There are lots of keyboard key. It may be hard code key or soft key just like that home Manu
back because some kind of device may contain hard code button or not.
key 1 ESCAPE
key 2 1
key 3 2
key 4 3
key 5 4
key 6 5
key 7 6
key 8 7
key 9 8
key 10 9
key 11 0
key 12 MINUS
key 13 EQUALS
key 14 DEL
key 15 TAB
key 16 Q
key 17 W
key 18 E
key 19 R
key 20 T
key 21 Y
key 22 U
key 23 I
key 24 O
key 25 P
key 26 LEFT_BRACKET
key 27 RIGHT_BRACKET
key 28 ENTER
key 29 CTRL_LEFT
key 30 A
key 31 S
key 32 D
key 33 F
key 34 G
key 35 H
key 36 J
key 37 K
key 38 L
key 39 SEMICOLON
key 40 APOSTROPHE
key 41 GRAVE
key 42 SHIFT_LEFT
key 43 BACKSLASH
key 44 Z
key 45 X
key 46 C
key 47 V
key 48 B
key 49 N
key 50 M
key 51 COMMA
key 52 PERIOD
key 53 SLASH
key 54 SHIFT_RIGHT
key 55 NUMPAD_MULTIPLY
key 56 ALT_LEFT
key 57 SPACE
key 58 CAPS_LOCK
key 59 F1
key 60 F2
key 61 F3
key 62 F4
key 63 F5
key 64 F6
key 65 F7
key 66 F8
key 67 F9
key 68 F10
key 69 NUM_LOCK
key 70 SCROLL_LOCK
key 71 NUMPAD_7
key 72 NUMPAD_8
key 73 NUMPAD_9
key 74 NUMPAD_SUBTRACT
key 75 NUMPAD_4
key 76 NUMPAD_5
key 77 NUMPAD_6
key 78 NUMPAD_ADD
key 79 NUMPAD_1
key 80 NUMPAD_2
key 81 NUMPAD_3
key 82 NUMPAD_0
key 83 NUMPAD_DOT
# key 84 (undefined)
key 85 ZENKAKU_HANKAKU
key 86 BACKSLASH
key 87 F11
key 88 F12
key 89 RO
# key 90 "KEY_KATAKANA"
# key 91 "KEY_HIRAGANA"
key 92 HENKAN
key 93 KATAKANA_HIRAGANA
key 94 MUHENKAN
key 95 NUMPAD_COMMA
key 96 NUMPAD_ENTER
key 97 CTRL_RIGHT
key 98 NUMPAD_DIVIDE
key 99 SYSRQ
key 100 ALT_RIGHT
# key 101 "KEY_LINEFEED"
key 102 MOVE_HOME
key 103 DPAD_UP
key 104 PAGE_UP
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 107 MOVE_END
key 108 DPAD_DOWN
key 109 PAGE_DOWN
key 110 INSERT
key 111 FORWARD_DEL
# key 112 "KEY_MACRO"
key 113 VOLUME_MUTE
key 114 VOLUME_DOWN
key 115 VOLUME_UP
key 116 POWER WAKE
key 117 NUMPAD_EQUALS
# key 118 "KEY_KPPLUSMINUS"
key 119 BREAK
# key 120 (undefined)
key 121 NUMPAD_COMMA
key 122 KANA
key 123 EISU
key 124 YEN
key 125 META_LEFT
key 126 META_RIGHT
key 127 MENU WAKE_DROPPED
key 128 MEDIA_STOP
# key 129 "KEY_AGAIN"
# key 130 "KEY_PROPS"
# key 131 "KEY_UNDO"
# key 132 "KEY_FRONT"
# key 133 "KEY_COPY"
# key 134 "KEY_OPEN"
# key 135 "KEY_PASTE"
# key 136 "KEY_FIND"
# key 137 "KEY_CUT"
# key 138 "KEY_HELP"
key 139 MENU WAKE_DROPPED
key 140 CALCULATOR
# key 141 "KEY_SETUP"
key 142 POWER WAKE
key 143 POWER WAKE
# key 144 "KEY_FILE"
# key 145 "KEY_SENDFILE"
# key 146 "KEY_DELETEFILE"
# key 147 "KEY_XFER"
# key 148 "KEY_PROG1"
# key 149 "KEY_PROG2"
key 150 EXPLORER
# key 151 "KEY_MSDOS"
key 152 POWER WAKE
# key 153 "KEY_DIRECTION"
# key 154 "KEY_CYCLEWINDOWS"
key 155 ENVELOPE
key 156 BOOKMARK
# key 157 "KEY_COMPUTER"
key 158 BACK WAKE_DROPPED
key 159 FORWARD
key 160 MEDIA_CLOSE
key 161 MEDIA_EJECT
key 162 MEDIA_EJECT
key 163 MEDIA_NEXT
key 164 MEDIA_PLAY_PAUSE
key 165 MEDIA_PREVIOUS
key 166 MEDIA_STOP
key 167 MEDIA_RECORD
key 168 MEDIA_REWIND
key 169 CALL
# key 170 "KEY_ISO"
key 171 MUSIC
key 172 HOME
# key 173 "KEY_REFRESH"
# key 174 "KEY_EXIT"
# key 175 "KEY_MOVE"
# key 176 "KEY_EDIT"
key 177 PAGE_UP
key 178 PAGE_DOWN
key 179 NUMPAD_LEFT_PAREN
key 180 NUMPAD_RIGHT_PAREN
# key 181 "KEY_NEW"
# key 182 "KEY_REDO"
# key 183 F13
# key 184 F14
# key 185 F15
# key 186 F16
# key 187 F17
# key 188 F18
# key 189 F19
# key 190 F20
# key 191 F21
# key 192 F22
# key 193 F23
# key 194 F24
# key 195 (undefined)
# key 196 (undefined)
# key 197 (undefined)
# key 198 (undefined)
# key 199 (undefined)
key 200 MEDIA_PLAY
key 201 MEDIA_PAUSE
# key 202 "KEY_PROG3"
# key 203 "KEY_PROG4"
# key 204 (undefined)
# key 205 "KEY_SUSPEND"
# key 206 "KEY_CLOSE"
key 207 MEDIA_PLAY
key 208 MEDIA_FAST_FORWARD
# key 209 "KEY_BASSBOOST"
# key 210 "KEY_PRINT"
# key 211 "KEY_HP"
key 212 CAMERA
key 213 MUSIC
# key 214 "KEY_QUESTION"
key 215 ENVELOPE
# key 216 "KEY_CHAT"
key 217 SEARCH
# key 218 "KEY_CONNECT"
# key 219 "KEY_FINANCE"
# key 220 "KEY_SPORT"
# key 221 "KEY_SHOP"
# key 222 "KEY_ALTERASE"
# key 223 "KEY_CANCEL"
# key 224 "KEY_BRIGHTNESSDOWN"
# key 225 "KEY_BRIGHTNESSUP"
key 226 HEADSETHOOK

key 256 BUTTON_1

key 257 BUTTON_2
key 258 BUTTON_3
key 259 BUTTON_4
key 260 BUTTON_5
key 261 BUTTON_6
key 262 BUTTON_7
key 263 BUTTON_8
key 264 BUTTON_9
key 265 BUTTON_10
key 266 BUTTON_11
key 267 BUTTON_12
key 268 BUTTON_13
key 269 BUTTON_14
key 270 BUTTON_15
key 271 BUTTON_16

key 288 BUTTON_1

key 289 BUTTON_2
key 290 BUTTON_3
key 291 BUTTON_4
key 292 BUTTON_5
key 293 BUTTON_6
key 294 BUTTON_7
key 295 BUTTON_8
key 296 BUTTON_9
key 297 BUTTON_10
key 298 BUTTON_11
key 299 BUTTON_12
key 300 BUTTON_13
key 301 BUTTON_14
key 302 BUTTON_15
key 303 BUTTON_16
key 304 BUTTON_A
key 305 BUTTON_B
key 306 BUTTON_C
key 307 BUTTON_X
key 308 BUTTON_Y
key 309 BUTTON_Z
key 310 BUTTON_L1
key 311 BUTTON_R1
key 312 BUTTON_L2
key 313 BUTTON_R2
key 314 BUTTON_SELECT
key 315 BUTTON_START
key 316 BUTTON_MODE
key 317 BUTTON_THUMBL
key 318 BUTTON_THUMBR

# key 352 "KEY_OK"

key 353 DPAD_CENTER
# key 354 "KEY_GOTO"
# key 355 "KEY_CLEAR"
# key 356 "KEY_POWER2"
# key 357 "KEY_OPTION"
# key 358 "KEY_INFO"
# key 359 "KEY_TIME"
# key 360 "KEY_VENDOR"
# key 361 "KEY_ARCHIVE"
key 362 GUIDE
# key 363 "KEY_CHANNEL"
# key 364 "KEY_FAVORITES"
# key 365 "KEY_EPG"
key 366 DVR
# key 367 "KEY_MHP"
# key 368 "KEY_LANGUAGE"
# key 369 "KEY_TITLE"
# key 370 "KEY_SUBTITLE"
# key 371 "KEY_ANGLE"
# key 372 "KEY_ZOOM"
# key 373 "KEY_MODE"
# key 374 "KEY_KEYBOARD"
# key 375 "KEY_SCREEN"
# key 376 "KEY_PC"
key 377 TV
# key 378 "KEY_TV2"
# key 379 "KEY_VCR"
# key 380 "KEY_VCR2"
# key 381 "KEY_SAT"
# key 382 "KEY_SAT2"
# key 383 "KEY_CD"
# key 384 "KEY_TAPE"
# key 385 "KEY_RADIO"
# key 386 "KEY_TUNER"
# key 387 "KEY_PLAYER"
# key 388 "KEY_TEXT"
# key 389 "KEY_DVD"
# key 390 "KEY_AUX"
# key 391 "KEY_MP3"
# key 392 "KEY_AUDIO"
# key 393 "KEY_VIDEO"
# key 394 "KEY_DIRECTORY"
# key 395 "KEY_LIST"
# key 396 "KEY_MEMO"
key 397 CALENDAR
# key 398 "KEY_RED"
# key 399 "KEY_GREEN"
# key 400 "KEY_YELLOW"
# key 401 "KEY_BLUE"
key 402 CHANNEL_UP
key 403 CHANNEL_DOWN
# key 404 "KEY_FIRST"
# key 405 "KEY_LAST"
# key 406 "KEY_AB"
# key 407 "KEY_NEXT"
# key 408 "KEY_RESTART"
# key 409 "KEY_SLOW"
# key 410 "KEY_SHUFFLE"
# key 411 "KEY_BREAK"
# key 412 "KEY_PREVIOUS"
# key 413 "KEY_DIGITS"
# key 414 "KEY_TEEN"
# key 415 "KEY_TWEN"

key 429 CONTACTS

# key 448 "KEY_DEL_EOL"

# key 449 "KEY_DEL_EOS"
# key 450 "KEY_INS_LINE"
# key 451 "KEY_DEL_LINE"

key 464 FUNCTION

key 465 ESCAPE FUNCTION
key 466 F1 FUNCTION
key 467 F2 FUNCTION
key 468 F3 FUNCTION
key 469 F4 FUNCTION
key 470 F5 FUNCTION
key 471 F6 FUNCTION
key 472 F7 FUNCTION
key 473 F8 FUNCTION
key 474 F9 FUNCTION
key 475 F10 FUNCTION
key 476 F11 FUNCTION
key 477 F12 FUNCTION
key 478 1 FUNCTION
key 479 2 FUNCTION
key 480 D FUNCTION
key 481 E FUNCTION
key 482 F FUNCTION
key 483 S FUNCTION
key 484 B FUNCTION

# key 497 KEY_BRL_DOT1

# key 498 KEY_BRL_DOT2
# key 499 KEY_BRL_DOT3
# key 500 KEY_BRL_DOT4
# key 501 KEY_BRL_DOT5
# key 502 KEY_BRL_DOT6
# key 503 KEY_BRL_DOT7

# key 504 KEY_BRL_DOT8

Joystick Keys
Joy stick key use for play games just like that screen axis.
axis 0x00 X
axis 0x01 Y
axis 0x02 Z
axis 0x03 RX
axis 0x04 RY
axis 0x05 RZ
axis 0x06 THROTTLE
axis 0x07 RUDDER
axis 0x08 WHEEL
axis 0x09 GAS
axis 0x0a BRAKE
axis 0x10 HAT_X

axis 0x11 HAT_Y

Input key Event using command

We have already discussed in the previous blog that in android each key has a specific role and
each key assign number and with help of this number we can activate this button or press
button but the main question is that how we can use this number to activate button so we have
one option to use this number that we can use with help of ADB command.
Ex: adb shell input keyevent <event code>

Here we are activating home button with help of ADB shell command.

There some other key which you can see in below picture.
from above picture you can do run all key event means you can perform any key event in your
device using the command in android device.
Chapter 12 android Testing and Monkey Testing

In this Chapter, we will learn about testing, testing modules, android testing, types of testing and
Monkey testing.

Android testing

From above picture, we can easily understand that testing contains with part one is JVM from
java and other is the android library.

Unit Testing
In unit testing, test runs on a local JVM on the development machine rather than android
runtime.
Unit testing is done by the android.jar library, all exception methods include in android.jar and
execute by default.

JUnit Testing
You can use the JUnit TestCase class to do unit testing on a class that doesn't call Android
APIs.

Testcase class is the super class for androidTestCase. You can easily understand with given
code.
Public class Testapp extends TestCase
{
Int a;
Int b;
}
Protectd void testMethod()
{
a=10;
b=10;
}

public void testMethod () {

int c = a + b;
assertTrue(c == 5.0);

Monkey testing
MonkeyTalk is tools which use to test any android or I-Phone application or test and device. In
android SDK include these testing tools. We can test any device or any application with two
types first Junit testing and second is monkey testing. Junit test any application by test classes
and the monkey is a command line tool which tests with device action like touch screen, gesture
and other.

Device Testing structure

Monkey Testing Feature
There is four main feature of monkey testing.

Basic configuration option

Debugging option
Event types
Operational constraints

Monkey Testing using Shell Command for device

There are a lot of a command to execute monkey testing.

Ex: adb shell monkey -v 500

Where v represent verbose method and 500 represents no. of the event to be sent for testing.
Monkey testing
MonkeyTalk is tools which use to test any android or I-Phone application or test and device. In
android SDK include these testing tools. We can test any device or any application with two
types first Junit testing and second is monkey testing. Junit test any application by test classes
and the monkey is a command line tool which tests with device action like touch screen, gesture
and other.

Monkey Device Testing structure

Monkey Testing Feature

There is four main feature of monkey testing.
 Basic configuration option
Debugging option
Event types
Operational constraints

1) Monkey Testing using Shell Command for android device

There are a lot of a command to execute monkey testing.
Ex: adb shell monkey -v 500

Where v represent verbose method and 500 represents no. of event to be sent for testing

2) Monkey Testing with Shell Command for android application

There are lots of commands to execute monkey testing.

Ex: adb shell monkey p <package name> -v 500

Where -p represent package and v represent verbose method and 500 represents no. of the
event to be sent for testing.
3) Run the same event sequence again in monkey testing
Sometimes you want to check an application on the same sequence or randomly again so you
will have to test exact same sequence with monkey tool.

Ex: adb shell monkey p <package name> -s 999 v 500

Here s refer to seed and 999 is seed value

4) Monkey testing to get Event time

If want to set fix time between events so we can do it by the throttle.
Ex: adb shell monkey p <package name> -- throttle 1000 v 500

5) Monkey testing to get Touch Event percentage

We can also test an application touch event percentage.

Ex: adb shell monkey p <package name> --pct-touch 25 v 500

6) Monkey testing to get Motion Event percentage
We can also test an application motion event percentage.

Ex: adb shell monkey p <package name> --pct-motion 25 v 500

7) Monkey testing to get Any Event percentage

We can also test an application any event percentage.

Ex: adb shell monkey p <package name> --pct-anyevent 25 v 500

8) Monkey testing to get Number of Events
We can also find no events use on any android device.

Ex: adb shell monkey --dbg-no-event v 500

9) Monkey testing to Ignore Crashes

If we want to fill full test an application without crashes we use this command or we want the full
test by avoiding crashes. This Command avoids any types exception.

Ex: adb shell monkey p <package name> ignore-crashes v 500

10) Monkey testing to Ignore Timeouts
If we want to fill full test an application without the timeout exception we use this command or
we want the full test by avoiding timeout crashes.

Ex: adb shell monkey p <package name> -ignore-timeouts v 500

11) Monkey testing to Ignore Security Exceptions

If we want to fill full test an application without security exception we use this command or we
want the full test by avoiding security exception crashes.
Ex: adb shell monkey p <package name> -ignore-security-excetions v 500
Chapter 13 android Rom and Its Structure

android ROM

Rom is an operating system run on your device. It is stored in read only memory in hardware
segment where your firmware and all application store and all device come with a ROM which
installs by the manufacturer. Android ROM contains all flash files like system, boot, and
recovery. It is stored in read only memory part on hardware.

Custom ROM

Android is open source which allows the developer to customize it and we can edit or update
some new feature in it and build the own new ROM image for android phone or tablet or another
word we can say that it is the standard version of the android operating system.

Advantage of custom ROM

These are some advantage of android custom ROM.
1) Provide update version
2) Improve performance
3) Improve battery performance
4) Customize theme

5) Add some new feature

the disadvantage of custom ROM

These are some disadvantage of android custom ROM.

1) Break manufacturers warranty.

2) It may have defected ROM

Android ROM Structure

There are mainly six partitions in android phone, tablet and another android device. In below are
the list of file systems. It may be exciting other file systems it depends on the android model but
logically 6 partitions in android devices.

Boot
Boot file contains ramdisk and kernel.This is the boot partition of your Android device. It includes
the android kernel and the ramdisk. The device will not boot without this partition. Wiping this
partition from recovery should only be done if absolutely required and once done, the device
must NOT be rebooted before installing a new one, which can be done by installing a ROM that
includes a /boot partition.

Recovery
It provides advanced recovery, installation, restoration, and maintenance operation for the
device.

This is specially designed for backup. The recovery partition can be considered as an
alternative boot partition.

System
This partition contains the entire Android OS, other than the kernel and the ramdisk. This
includes the Android GUI and all the system applications that come pre-installed on the device.

System partition contains the entire Android OS, other than the kernel and the ramdisk. This
includes the Android GUI and all the system applications that come pre-installed on the device.
you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
Data
This partition contains the users data like your contacts, SMS, settings and all android
applications that you have installed.
It is called user data partition. This partition contains the users data like your contacts, SMS,
settings and all android applications that you have installed. when you used for the first time or
the way it was the last official or custom ROM installation.

Cache
This is the partition where Android stores accessed data and app components.

This is the partition where Android stores frequently accessed data and app components.
Wiping the cache doesnt affect your personal data but simply gets rid of the existing data there,
which gets automatically rebuilt as you continue using the device.

Misc

This partition contains USB configuration and hardware setting etc.

This partition contains miscellaneous system settings in form of on/off switches. These settings
may include CID (Carrier or Region ID), USB configuration and certain hardware settings etc.

sd card

This is not a partition on the internal memory of the device but rather the SD card. In terms of
usage, this is your storage space to use as you see fit, to store your media, documents, ROMs
etc. on it. Wiping it is perfectly safe as long as you backup all the data you require from it to your
computer first. Though several user-installed apps save their data and settings on the SD card
and wiping this partition will make you lose all that data.
And we can check system partition by df command
Chapter 14 Types of android Rom and Their Structure

android ROM
Rom is an operating system run on your device. It is stored in read-only
memory in hardware segment where your firmware and all application store
and all device come with a ROM which installs by the manufacturer. Android
ROM contains all flash files like system, boot, and recovery. It is stored in
read-only memory part on hardware.

Types of ROM

There are many android ROM available in currently in the market and mostly ROM internal
structure is same. We will discuss only a few android ROM but from the help of this book, you
can customize around all ROM. There are follow.
1) Stock ROM
2) Rockchip ROM
3) MT ROM
4) Cyanogenmod ROM
This Rom is mostly currently used by most of the manufacture.

Stock Rom
It is a cd Image file which builds in Linux operating system. This ROM generally uses in Chinese
device like all winner devices.
Supported firmware images:
1) Sochip SC8600/SC9800
2) Boxchip F10/F15/F16/F20
3)Teclast T7200/T8100
4) Allwinner F10/F13/F18
5) Allwinner F1C100/F1E200
6) Allwinner A10/A13/A10s
7) Allwinner A20/A31/A31s
8) Allwinner A80 (Phoenix Suit)

You can see stock ROM in below picture

Structure Stock Rom

Here there four are four main files
1) Boot.fex- boot file contain all files which are necessary for the boot like all boot script, boot
logo, boot animation.
Boot file contains ramdisk and kernel.This is the boot partition of your Android device. It includes
the android kernel and the ramdisk. The device will not boot without this partition. Wiping this
partition from recovery should only be done if absolutely required and once done, the device
must NOT be rebooted before installing a new one, which can be done by installing a ROM that
includes a /boot partition.

2) Recovery.fex- recovery file contains all back and restores files.

It provides advanced recovery, installation, restoration, and maintenance operation for the
device.
This is specially designed for backup. The recovery partition can be considered as an
alternative boot partition.

3) System.fex- folder all system files contain in the system.

This partition contains the entire Android OS, other than the kernel and the ramdisk. This
includes the Android GUI and all the system applications that come pre-installed on the device.

4) Bootloader.fex- this file contains the script for boot, battery images, and first boot logo file.

MTK ROM
This ROM is called media tech ROM and its get in many versions like MT6577, MT6572,
MT6575 and this is called MT65XX series.

This ROM is used currently in most of the android devices.

Structure of MTK ROM

Here this is the structure of MT6582 version.
There are lots of files in MTK ROM
1) Boot.img- boot file contain all files which are necessary for the boot like all boot script, boot
logo, boot animation.

2) Recovery.img- recovery file contains all back and restores files.

3) System.img- folder all system files contain in the system.

4) Logo.bin- this file contains first boot logo.

5) userdata.img-The userdata.img file is a blank partition. It is used to reset the user data
partition to its factory state. ramdisk.img is a small partition image that is mounted read-only by
the kernel at boot time. It only contains /init and a few config files.

Rockchip ROM

Rockchip ROM also look like stock ROM but structure is different and there are lots of versions
of rock chip ROM are available in market
Structure and Extract Rockchip ROM

We can see it file structure in below figure. It contains four main files like system, boot, recovery
and kernel images.

1) Boot.img- boot file contain all files which are necessary for the boot like all boot script, boot
logo, boot animation.

2) Recovery.img- recovery file contains all back and restores files.

3) System.img- folder all system files contain in the system.

4) Kernal.img- this file contains all files related to android kernel.

Chapter 15 android Stock Rom

android ROM
Rom is an operating system run on your device. It is stored in read-only memory in hardware
segment where your firmware and all application store and all device come with a ROM which
installs by the manufacturer. Android ROM contains all flash files like system, boot, and
recovery. It is stored in read-only memory part on hardware.

Stock Rom
It is a cd Image file which builds in Linux operating system. This ROM generally uses in Chinese
device like all winner devices.
Supported firmware images:
1) Sochip SC8600/SC9800
2) Boxchip F10/F15/F16/F20
3)Teclast T7200/T8100
4) Allwinner F10/F13/F18
5) Allwinner F1C100/F1E200
6) Allwinner A10/A13/A10s
7) Allwinner A20/A31/A31s
8) Allwinner A80 (Phoenix Suit)

You can see stock ROM in below picture.

Structure Stock Rom

Here there four are four main files

1) Boot.fex- boot file contain all files which are necessary for the boot like all boot script, boot
logo, boot animation.
Boot file contains ramdisk and kernel.This is the boot partition of your Android device. It includes
the android kernel and the ramdisk. The device will not boot without this partition. Wiping this
partition from recovery should only be done if absolutely required and once done, the device
must NOT be rebooted before installing a new one, which can be done by installing a ROM that
includes a /boot partition.

2) Recovery.fex- recovery file contains all back and restores files.

It provides advanced recovery, installation, restoration, and maintenance operation for the
device.
This is specially designed for backup. The recovery partition can be considered as an
alternative boot partition.

3) System.fex- folder all system files contain in the system.

This partition contains the entire Android OS, other than the kernel and the ramdisk. This
includes the Android GUI and all the system applications that come pre-installed on the device.

4) Bootloader.fex- this file contains the script for boot, battery images, and first boot logo file.

Extract Stock Rom

There lot of tools available in the market to extract stock ROM like imagerepacker tools. When
we extract this image file with imagerepacker we will get many .fex files.

In above picture, it is the structure of imagerepacker tools.

There are following steps to extract the stock image.

1) change name of stock ROM as original and run runner.bat

2) provide the path of stock ROM.

3) press enter

You can see it extracting all files in .fex format.

4) This all .fex files are store in stockrom.img.dump folder

You can see in below picture.

MTK ROM
This ROM is called media tech ROM and its get in many versions like MT6577, MT6572,
MT6575 and this is called MT65XX series.

This ROM is used currently in most of the android devices.

Structure of MTK ROM

Here this is the structure of MT6582 version.

There are lots of files in MTK ROM

1) Boot.img- boot file contain all files which are necessary for the boot like all boot script, boot
logo, boot animation.
Boot file contains ramdisk and kernel.This is the boot partition of your Android device. It includes
the android kernel and the ramdisk. The device will not boot without this partition. Wiping this
partition from recovery should only be done if absolutely required and once done, the device
must NOT be rebooted before installing a new one, which can be done by installing a ROM that
includes a /boot partition.

It provides advanced
2) Recovery.img- recovery file contains all back and restores files.
recovery, installation, restoration, and maintenance operation for the device.
This is specially designed for backup. The recovery partition can be considered as an
alternative boot partition.

3) System.img- folder all system files contain in the system.

This partition contains the entire Android OS, other than the kernel and the ramdisk. This
includes the Android GUI and all the system applications that come pre-installed on the device.
System partition contains the entire Android OS, other than the kernel and the ramdisk. This
includes the Android GUI and all the system applications that come pre-installed on the device.
you will still be able to put the phone into recovery or bootloader mode to install a new ROM.

4) Logo.bin- this file contains first boot logo.

5) userdata.img-The userdata.img file is a blank partition. It is used to reset the user data
partition to its factory state. ramdisk.img is a small partition image that is mounted read-only by
the kernel at boot time. It only contains /init and a few config files.
Chapter 16 Rock Chip and Cyanogen ROM

Rockchip ROM

Rockchip ROM also looks like stock ROM but the structure is different and there are lots of
versions of rock chip ROM are available in the market.

Structure and Extract Rockchip ROM

We can see it file structure in below figure. It contains four main files like system, boot, recovery
and kernel images.

1) Boot.img- boot file contain all files which are necessary for the boot like all boot script, boot
logo, boot animation.
Boot file contains ramdisk and kernel.This is the boot partition of your Android device. It includes
the android kernel and the ramdisk. The device will not boot without this partition. Wiping this
partition from recovery should only be done if absolutely required and once done, the device
must NOT be rebooted before installing a new one, which can be done by installing a ROM that
includes a /boot partition.

2) Recovery.img- recovery file contains all back and restores files.

It provides advanced recovery, installation, restoration, and maintenance operation for the
device.
This is specially designed for backup. The recovery partition can be considered as an
alternative boot partition.

3) System.img- folder all system files contain in the system.

This partition contains the entire Android OS, other than the kernel and the ramdisk. This
includes the Android GUI and all the system applications that come pre-installed on the device.
System partition contains the entire Android OS, other than the kernel and the ramdisk. This
includes the Android GUI and all the system applications that come pre-installed on the device.
you will still be able to put the phone into recovery or bootloader mode to install a new ROM.

4) Kernal.img- this file contains all files related to android kernel.

There are following steps to extract rock chip ROM.

1) extract factory tool and copy rock chip ROM here.

2) run FWFactoryTool .

3) Provide path of rock chip ROM image file.

4) Here you get or extracted the file in under the tool.

What is Cyanogen ROM

Cyanogen OS is not only an operating system. In actuality, Cyanogen OS is a version of

Android thats been modified to include additional functionality.Android, itself, is an open-source
software that anyone can build and change upon.

The customization of Cyanogen ROM

Android offers only limited customization: You can throw a wallpaper onto the home screen,
download and create ringtones, and change the size of the font used throughout the operating
system. In android Without rooting your device or installing a third-party launcher, any additional
personalization options i.e., custom icon packs, system fonts, etc.

Many of the specific customization settings available with Cyanogen OS come from the Theme
Engine, which is exactly as it sounds. Its a powerful app built into Cyanogen OS that lets you
download free and premium themes that can be applied to change the look of your phones
operating system. Currently, there are more than 100 themes available on the Theme Engine
with more added regularly.

How to Install CyanogenMod

CyanogenMod is a custom ROM for Android devices. Its free, and it extends the capabilities of
your device with themes, dramatically improved privacy functionality. If you have a rooted
device, installing CyanogenMod is incredibly easy. The CM team created an app called
CyanogenMod Installer that lets you download and flash the ROM with minimal technical
knowledge. Be sure to backup your data before you proceed.
Step 1: Download CyanogenMod Installer
Visit get.cm by your Android device and download the .apk file.

Step 2: Enable Unknown Sources

Go to Settings > Security > Check Unknown Sources

Step 3: Install the App

Open the .apk file that you downloaded earlier, and install it.

Step 4: Follow the instructions

The CyanogenMod Install app will provide simple instructions. It will guide you to downloading
the appropriate ROM for your device and flashing it through your recovery.
Chapter 17 Structure Extract and Repack boot and recovery
file in android

Boot file
Boot file contains ramdisk and kernel. This file is necessary to boot from any android device.
The boot.img is part of the Android ROM you flash onto your device.

This is the boot partition of your Android device. It includes the android kernel and the ramdisk.
The device will not boot without this partition. Wiping this partition from recovery should only be
done if absolutely required and once done, the device must NOT be rebooted before installing a
new one, which can be done by installing a ROM that includes a /boot partition.

Structure of boot file

It is a like a disk image. This is the part to enable boot to phone. Its include kernel and ramdisk
without this part phone it not able to boot.
We can see boot structure
There are 6 layers of Linux boot
and execution of boot file is followed as in below diagram.

BIOS
-BIOS include basic input-out system.
-It executes the bootloader program.
-Its look bootloader in floppy, cd-ROM, and hard drive.
-Once boot loader program loaded in memory BIOS given full control to it.

MBR
-MBR stands for master boot Record.
-It is store in the bootable disk.
-It's size less than 512.

GRUB
-GRUB stand for the grand Unified Bootloader.
-If you install more than one kernel you can choose one of them.
-GRUB display splash screen.
-GRUB Configuration file located in /boot/grub/grub.conf.

Kernel
-Mounts the root file system.
-Kernel executes the /sbin/init program.

Init
-Its decide kernel run level.
-Run level
0-halt.
1-single user mode.
2-multiuser.
3-full multiuser mode.
4-unused.
5-X11
6-reboot
-Identified the default init level and load all associate programs.

Runlevel Program
-it contains all runlevel programs.
-Runlevel depend on default init level setting
Run level 0-/ete/rc.d/rc0.d/
Run level 1-/ete/rc.d/rc1.d/
Run level 2-/ete/rc.d/rc2.d/
Run level 3-/ete/rc.d/rc3.d/
Run level 4-/ete/rc.d/rc4.d/
Run level 5-/ete/rc.d/rc5.d/

Run level 6-/ete/rc.d/rc6.d/

Extract and repack boot file

We can extract boot file by two types first one by window command tools and
other is by Linux command tools. There are lots of tools available to extract
boot.img. For extract boot file firstly rename boot.fex to boot.img.
Extract and repack boot file by window command tools
We can extract boot.img using the bootimg tool.
Here there following steps to extract it.

1) extract bootimg.zip put bootimg.exe and boot.img file in test folder.

2) now go in the test folder and click Ctrl+Shift and right click and choose Open command
window here.
3) And write command bootimg.exe unpack-bootimg boot.img and press enter.

4) After edit file and folder in boot file, we can Repack boot.img.

For repack boot file run this command boot.img --repack-booting And press enter.
Recovery File

Recovery file is an android flash memory partition that use to perform the factory reset or
restore the original os and it provides clockwork mode to custom recovery for android
Smartphone and tablet or we can say that it provide advanced recovery, installation, restoration,
and maintenance operation for the device.

This is specially designed for backup. The recovery partition can be considered as an
alternative boot partition.
Recovery File Structure

Recovery.img file contains many parts like install, Wipe, backup, restore and setting. Each part
has an own different role in android device. We will discuss later in on each part.
We can run recovery mode by ADB command (ADB recovery reboot) or with hard code button
(by volume+ and power).

There are the main functions of recovery file to manage the android device.

Install- Install function contains to install any android device script to install any library or
application.

Wipe- This function contain wide android data to the device.

Backup- This function use to backup of the android device.
Restore- This function use for restore any android device.
Mount- This function uses to mount os files like sd card files.
Setting- This function uses to communicate device application.
Advanced- This function use for the advance setting.

Reboot- This function uses to reboot the device.

Extract and repack Recovery File
Here we will extract and repack recovery file using Rk Firmware
tools here there is some step to extract it.

1) extract RK firmware tool and copy recovery file here.

2) run start file and press single tool.

3) Select recovery file and press Extract then it will start automatically extract recovery file.
4) Here we can see extracted recovery file in the temp folder.
5) After the edit, we can also repack recovery file using press build button. we can see it in the
root directory.
Extract and repack System files in ubuntu
Required tools
Stock firmware - as a starting base.
Linux image tools - for extracting and building the partitions of the image.
A text editor that supports Unix line endings, do not use Notepad.

Here there is some step to extract boot file in ubuntu system.

1) Copy boot, recovery and system file in folder custom ROM.

2) Copy tools in this folder here.

3) Extract tools.zip file here.

4) Open terminal application.
5) For extract, boot file go to custom folder using command
$ cd custom ROM
And extract boot file using command
$ tools/split_bootimg.pl boot.img
And type command ls to check files in directory
$ ls

Here you can see the ramdisk.zip file here.

6) Now we will extract ramdisk file using these command
Firstly we will create a directory using command

$ mkdir ramdisk
Go to ramdisk folder using command
$ cd ramdisk
Now we will extract ramdisk.zip file using command
$ gunzip c ../boot.img-ramdisk.gz | cpio i
And check ramdisk files using ls command

$ ls

7) Now are able to edit as need

Now we can rebuild boot file using the following command

$ cd ..

$ tools/mkbootfs ramdisk | gzip > ramdisk-new.gz

$ tools/mkbootimg --base 0x40000000 --kernel boot.img-kernel --ramdisk ramdisk-new.gz --

cmdline 'console=ttyS0,115200 tw init=/init loglevel=8' -o new-boot.img

$ ls
Chapter 18 Structure Extract and Repack System and Bootloader
file in android

System File
many of the Android users are using their Android phone for calls, SMS, browsing and basic
apps, But from the development perspective, we should know first about Android internal
structure.
Android has several partitions (like boot, system, recovery, data etc) to organize files and
folders on the device just like Windows OS. Each of these partitions has its own working
functionality, But most of the user dont know the significance of each partition and its contents.
In this article, we will take you on a tour of Android partitions. So let's start the android file
system tutorial.

The system file is the main file in android os system and most of the work of any Rom depend
on it. Rooted android phones provide many additional benefits when compared to a non-rooted
phone and thats because we can read and modify system files.

This file contains the entire Android OS, other than the kernel and the ramdisk. This includes
the Android

GUI and all the system applications that come pre-installed on the device.

This partition includes all Android OS, other than the kernel and the ramdisk. This includes the
Android GUI and all the system applications that come pre-installed on the device. you will be
able to put the phone into recovery or bootloader mode to install a new ROM.

This partition contains the entire Android OS, other than the kernel and the ramdisk. This
includes the Android GUI and all the system applications that come pre-installed on the device.
System partition contains the entire Android OS, other than the kernel and the ramdisk. This
includes the Android GUI and all the system applications that come pre-installed on the device.
you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
Extract and repack system File
Here we will extract and repack system file using Rk Firmware
tools here there is some step to extract it.

1) extract rk firmware tool and copy system file here.

2) run start file and press single tool.

3) Select system file and press Extract then it will start automatically extract system file.
4) Here we can see extracted system file in the temp folder.

when we open this folder.

5) After the edit, we can also repack system file using press build button. we can see it in the
root directory.

Bootloader file

A bootloader is a computer program that loads an operating

system (OS) or runtime environment for the android device.

the bootloader is code that is executed before any Operating System starts to run. Bootloaders
basically package the instructions to boot operating system kernel and most of them also have
their own debugging and modification environment.
Structure of Bootloader file
Extract and repack bootloader file
Here there is some step to extract and repack bootloader file.

1) Firstly install PowerISO software and copy bootloader.img file in the separate folder.

2) Right click and select PowerIso and then select extract here.

3) Here you can see expected bootloader file.

Here you can save extracted file and also we can directly bootloader file.

Extract and repack System files in ubuntu

Required tools
Stock firmware - as a starting base.
Linux image tools - for extracting and building the partitions of the image.
A text editor that supports Unix line endings, do not use Notepad.

Here there is some step to extract boot file in ubuntu system.

1) Copy boot, recovery and system file in folder custom ROM.

2) Copy tools in this folder here.

3) Extract tools.zip file here.

4) Open terminal application.
5) For extract, boot file go to custom folder using command
$ cd custom ROM
And extract boot file using command
$ tools/split_bootimg.pl boot.img
And type command ls to check files in directory
$ ls

Here you can see the ramdisk.zip file here.

6) Now we will extract ramdisk file using these command
Firstly we will create a directory using command

$ mkdir ramdisk
Go to ramdisk folder using command
$ cd ramdisk
Now we will extract ramdisk.zip file using command
$ gunzip c ../boot.img-ramdisk.gz | cpio i
And check ramdisk files using ls command

$ ls

7) Now are able to edit as need

Now we can rebuild boot file using the following command

$ cd ..

$ tools/mkbootfs ramdisk | gzip > ramdisk-new.gz

$ tools/mkbootimg --base 0x40000000 --kernel boot.img-kernel --ramdisk ramdisk-new.gz --

cmdline 'console=ttyS0,115200 tw init=/init loglevel=8' -o new-boot.img

$ ls
Chapter 19 android Rooting

What is android rooting

Android rooting is a process which breaks manufacture device limitation or in other work, it is
like a jell break. After rooting process user can edit, delete or update system files or directory.
This process provides super user permission to the user. It is same like Sudo command in Linux
and root word come from Unix/Linux.

Root Advantages
There are following advantage of android rooting.

1)custom ROM/Firmware
ROM is a software which runs on your device so after root we can do anything in ROM just like
we can edit, delete or update ROM files and we can also flash ROM. we can also change
device boot processes like boot logo and boot animation.

2)Custom Theme
We can also change android launcher or we can change Device theme.

3)Kernel, Speed, and Battery

After root, we can flash device kernel and we also improve the speed of device or battery
performance.

4)Backup/Restore
We can also back device data and applications of our device.

5)Unlocked other Feature

We can unlock other feature like we can add or delete system application or some application
which require root permission may be perfectly run in rooted device.

Root Disadvantages
There are following Disadvantages of rooting
1) Break Device Warranty
After root, you may be lost your device warranty because many manufacturer or developer does
not allow device rooting.

2) Security
After rooting process, you lost your security because it may be the unwanted person can
change your device files any one can modify your ROM.

How to Check Either Device root or not

The main question is that how we can check a device root or not. We can check it by types first
one is that there are lot of application available in android market for check root and other by
android command

Ex: adb shell

For the above picture, we can see that when we run ADB shell command we find here two
symbols first one is # and second one is $. # indicate that device is already rooted and $
indicate device in unrooted.

How To Root
From the above picture it clear that We can root a device in types by internally or Externally.

Internally Means if we have device original firmware we can root or Device ROM we can root
whole Operating system by changing some files and in externally root we can root device by
applying some command or by some tools. In externally root It may be root or no because you
already know that in currently market there are lot of android ROM available in market like stock
ROM, rock chip ROM, MTK ROM, and each ROM has different structure or file format or it may
be it require some additional user permission so that why It may be root or not by commands or
tools.

ROM root Internally

If have already discussed that if have original device ROM so can root it. For root externally we
have to extract ROM and we will need the default.prop file. generally, we can find it in the boot.
img or recovery.in.

You can better understand with below pictures.

when we open this file we get as

In the last picture, you can see that there is line ro.secure=1. If this is 1 means that it's secure
or unroot but if its value is 0 it means is unsecured or root. So we will have to change this value
for root.
We can change this value by ADB command

From this pull command, we copy the default.prop file into the desktop.

Now we can edit this value using not paid and again insert into the device by push command.

Rom Root Externally

We can also externally root a device by two types by tools or ADB command. There are a lot of
rooting tools available in market at this time like kingo root, one click super user tools but we are
sure about rooting tools because we already know that each ROM has the different directory
structure.

Other for root by ADB command we will have need three files.

1)su
2)busybox
3)superuser.apk
Now copy busybox, su and superuser.apk to /data/local/tmp/ using adb command

You can see it in below picture.

Now run ADB shell command it still shows $ sign means it is unrooted still.
Now run other command like
Chmod 6755 /data/local/tmp/su
Chmod 755 /data/local/tmp/bustbox

Chmod 644 /data/local/tmp/superuser.apk

For further you will have to need Linux distro with nautilus(Linux ubuntu 11.04)
Now turn reboot your device.
Now connect your device with ubuntu.
Run command
Sudo nautilus on obuntu terminal.
Now put your device into recovery mode by press power and volume + button simultaneously.
Run both commands on ubuntu terminal.
Move/cut-paste su and busybox to /system/bin/ using Nautilus.
Move/cut-paste Superuser.apk to /system/app/ using Nautilus.

Turn off your device and again connect with window device and run adb shell su command
now your device must be rooted.

You can see it in below picture.

Chapter 20 Create and change Boot animation and its
structure in android

Boot animation

The boot animation is the first screen that you see when power on your Android phone or tablet.
It may be a zip file or video file. It shows manufacturer logo on boot screen and its run after the
boot logo.The boot animation is the first screen that you see when power on your Android
phone or tablet. It may be a zip file or video file. It shows manufacturer logo on boot screen and
its run after the boot logo.

The Android boot animation is contained an uncompressed zip file as bootanimation.zip that
can be found in the media folder of the system /system/media on the device.

This single file contains all the information about to run the boot animation and is loaded
automatically when the device boots.
.

you can see boot animation directory in below picture.

when we open this media folder we get

Structure of Boot animation

If you extract the contents of the bootanimation.zip file to your computer, you will see
Desc.txt file
Part 0 folder(contain png or jpeg images in order form)

More part 1, part 2 folder(it may be present or not).

The animation is played simply by displaying the images in a sequence, and the text file defines
how they are to show images in device screen.

Folder
These contain PNG or Jpeg images in order, starting from like 0000.jpg or 00001.jpg and
proceeding with increments one by one. There should minimum at least one folder in
bootanimation.zip

you can see all contain in the folder in below picture

Desc.txt file
This file defines how the images in the folder are displayed in during the boot time.

You can see the format of desc.txt file format in below picture.
As you can see, in the first line, 600 and 1024 define the width and height of the boot animation
in pixels and
It depends on device screen resolution 6 is the frame rate in fps (frames per second)
number of images to display per second.
The second and line p represent part of animation and end with part0 or part1 and 0
represent how many times this part
will loop before switching to the next part (if exist) and here 0 number represent it will run
infinite till boot complete and
1 represents it will run the single time and hang in the last image till boot. Send number 0
is for pause and it represent in frame
A pause of 5 for example, would mean pausing for the time it takes 5 frames to play and
since the frame rate is 6
frames per second.

We can better understand with below picture.

Create boot animation
 We can easily create device boot animation in zipping file format.

Here there are some steps to create boot animation.zip file

1) For creating boot animation for device firstly we will have to install WinZip software in PC.

2) Copy all image in a folder as name part 0 in order format then create desc.txt and write
according to device configuration and user requirement as the previous topic structure of boot
animation.
when we open this desc.txt file we get.

3) Then select part0 folder and desc.txt file and right click here according to below picture.

4) Then choose to add to archive and check zip & select store in compression method then ok
5) Here we will get a uncompressed zip file.

Change boot animation

If you have original ROM of your device then we can easily replace custom boot animation with
original boot animation of your device. For this process Extract system.img file of android ROM
and open system folder and then select media folder you put this zip file in this directory then
again compress system.img file.
Change boot animation using ADB command
We can also replace your custom boot animation with ADB command if your device is rooted.

Open command promote of pc and adb push <path of bootanimation.zip>

system/media/bootanimation.zip
Chapter 21 Create and change boot logo in android

Boot logo

The boot animation is the first screen that you see when power on your Android phone or tablet.
It may be a .bmp file or .rle file. It shows manufacturer logo on boot screen and its run after the
boot logo.

It may be the different structure in different ROM and it may one or two boot logo exist in ROM.
In each ROM boot logo location and existing form are different and it depends on types of ROM.

boot logo in stock ROM

There may exist two boot logo in android stock ROM.

First boot logo in stock ROM

First boot log in stock ROM exists in bootloader file in form .bmp format.

Second boot logo in stock ROM

second boot logo in stock ROM exist in boot file in form of .rle format.
boot logo in MTK ROM

There may exist two boot logo in android stock ROM.

First boot logo in MTK ROM

First boot log in MTK ROM exists in root inform logo.bin format.
second boot logo in MTK ROM

second boot log in MTK rom exist in isboot.img and path is /system/media/images in form
boot_logo format.

Boot logo in Rockchip Rom

We have already seen ROM structure of rock chip ROM. In rock chip ROM, It may be exit one
or two boot logo.
In rock chip, ROM boot logo exists in form of .ppm with name logo. Here we can see it in below
picture.

Create and change First Boot logo

Create and change First Boot logo in Stock ROM

Here there are following steps to create and change boot log in android.

1) Extract stock ROM according to the previous chapter and change its name from
bootloader.fex to bootloader.img.
2) Create a folder bootloader and copy bootloader.img file here

3) Install PowerISO software and right on bootloader.img file and select PowerISO then Extract
To.
4) Here you can see file structure of the bootloader.img file.

Create a .bmp file for boot logo and Click the add button to replace new boot logo then save.

Create and change second Boot logo in Stock ROM

Create boot logo
As we know that second boot logo in stock ROM exists in form of .rle file form.
Here there are following steps to create .rle boot logo file.
1) First of all download logogen tools and extract it.

2) Copy BMP file of boot logo here.

3) BmpConvert.exe file and select BMP file.

4) Press convert button it will create a .rle file for boot logo with name initlogo.rle.
Change second boot logo in stock ROM

Here there are following steps to create .rle boot logo file.

1) Extract stock ROM according to the previous chapter and change its name from boot.fex to
boot.img.

2) extract bootimg.zip put bootimg.exe and boot.img file in test folder.

3) now go in the test folder and click Ctrl+Shift and right click and choose Open command
window here.

4) And write command bootimg.exe unpack-bootimg boot.img and press enter.

5) Open initrd folder and replace initlogo.rle file.
6) After edit rle file write command bootimg.exe unpack-bootimg boot.img and press enter
to again repack boot.img.
7) After edit file and folder in boot file, we can Repack boot.img.

For repack boot file run this command boot.img --repack-bootimg And press enter.

Here we get two files boot-new.img as edited boot file and boot-old.img old file.
Create and change First Boot logo in MTK ROM

We already know that First boot logo in MTK ROM exists in root inform logo.bin format.
So there are some steps to create and change first boot logo in android MTK ROM

1) extract Logo Builder tools and copy the original logo.bin file here.

2) run logobuilder.exe.
3) press create new project button and provide the path of the original logo.bin file and extract it
into a new folder as name logo here.
4) so create an edited logo image and replace with the original image. here we replacing img1
and img39 images with the new logo image.
5) After replacing now we can again create the logo.bin file using press make the button. And
you can see it in logo folder.

6) Replace this new logo.bin file with the original logo.bin file.

Create and change second Boot logo in MTK ROM

We already know that second boot log in MTK ROM exists in is boot.img and path are
/system/media/images in form boot_logo format.
So there are some steps to create and change second boot logo in android MTK ROM
1) Extract Image_Search_Editor.zip to a folder.

2) Now open Image Search Editor.exe.

3) Select the file, boot_logo.bin to open.

4) Now select 16 colors from the left side panel.

5) Now press BMP button on the toolbar on the top.

6) Now resize the image according to your device size by the press : Size --> 'Set image Size'.
7) Press ok Now you should see the full default boot logo image.

8) Now, select Edit-->Replace by new boot logo BMP image. Select the BMP image that you
saved then press apply.

9) Then, go to File-->Save as BIN. Save it and rename this file as boot_logo.

10) Now replace this new boot_logo with the original boot_logo file.

Create and change boot logo in rock chip ROM

Now there are a lot of tools which can convert a .jpg or .png image to .ppm image or we can
also convert online it.
Here we will see how we can change boot logo in rock chip ROM.
There are following steps to extract rock chip ROM and change boot logo.

1) extract factory tool and copy rock chip ROM here.

2) run FWFactoryTool

3) Provide path of rock chip ROM image file.

4) In tempFolder, we can see the logo.ppm file exists so now we can replace with our custom
logo.ppm file.

5) when we open this TempFolder we get.

Chapter 22 Install android ROM and android Diver

Install device driver

Now at this time lot of ROM available in the market and many time we will need those drivers to
connect with computer for installation ROM or may other reason.

Here the following the step to install the device driver on your computer.
1) Download and extract USB diver.zip

2) Firstly right click on my computer->manage->device manager

Here you can see that if your device does not install in the computer it show the unknown
device.
3) Right, click on the unknown device.

4) Click on Update Driver Software.

5) Click on browse my computer for driver software.
6) Click on Let me pick from the device.
7) Press next button.
8) Then press Have Disk button.
9) Provide android_winusb.inf file path by select browse button and press ok button.
10) Select android ADB interface and click next button.
11) Then press yes button and it will install ADB driver for the device.
12) You can see install driver for your device.
Install android ROM in android

We can install android stock ROM with mainly two tools like live suit and phoenix but both are
the platform or operating system dependent.now we will see how to install android ROM in any
device using different tools.

Install stock ROM by live suit

This tool may work on window 7 platform and here below there are following steps to install
stock ROM in android device.
1) Download and install android ADB drivers on your computer.
2) Download and extract the livesuite.zip file on your computer.
3) Run livesuit.exe

4) Select stock ROM path by press SelectImg.

5) Now we can connect android Smartphone or tablet to the computer using USB cable and it
should be power off.
Before connecting your device press volume down button and connect your device to the
computer with USB cable while holding volume down button press power button around 10
times.

6) After successfully reorganization to your device we get a window to format your device and
press yes.
7) Again we will get another window, press yes again it will automatically start to installation
ROM in your device.
8) After successfully installation software we will get upgrade window.

Install stock ROM by phoenix Card

Install with phoenix card dependent on os platform. it may install software on window 7 or may
be on window XP by phoenix card tools. It depends on the version of phoenix card version.
here below there are following the step to install stock ROM in android device.
1) Download and install android ADB drivers on your computer.
2) Download and extract the phoenixCard.zip file on your computer.
3) Insert TF Card /MicroSD Card in the Card reader and attach Card Reader with PC. Use
minimum 1GB memory card.
4) format MicroSD card to make sure it does not have any other file or it's not corrupted.

5) Open PhoenixCard.exe
6) click on Disk check.Disk Check will detect TF Card port Like J Drive, K drive.
7) Now click on Img File button and browse the stock ROM file from the above-extracted
directory.

8) Then click on Format to the Normal button to format the sd card using this application.
9) Finally, click Burn button to start burning an image to Micro-SD card.
10) Wait until the Burn End.. message appears on the screen.

11) Switch off your device and insert the memory card in it and switch on the device. ROM will
start installation automatically and after 100% complete remove your memory card in and start
your device.

Install MTK ROM by Sp Flash tool

here below there are following the step to install MTK ROM in android device.
1) Download and install android ADB drivers on your computer.

2) Download and extract Sp Flash tool.zip file on your computer.

3) Run the flashtool.exe file.

4) Provide ROM Android_scatter.txt file path by Press Scatter-loading File button.

5) Press F9 or download button.
6) Connect your device to computer using USB cable. It will start format first by the red line and
then it will start to install software by the yellow line.
7) After complete 100%, it will install successfully.

8) Then remove the USB cable and now it installs ROM.

Install Rockchip ROM by batch tool

here below there are following the step to install Rockchip ROM in android device.
1) Download and install android ADB drivers on your computer.

2) Download and extract the batch tool.zip file on your computer.

2) Run RKBatch Tool.exe.

3) Provide rock chip ROM path by browsing.

4) Connect your device to the computer by USB cable with press power and volume up key
simultaneously.
5) Then press upgrade button the start to install ROM in the device after 100% remove the
cable from drive and device ready to use with the new firmware.
Chapter 23 Build.prop and defualt.prop File in android

We already know that how we can extract any ROM and how we can customize it because
customize ROM improve android ROM performance. In this chapter, we will discuss ROM
performance improvement by editing some ROM files like build.prop file, default .prop file and
some other customization.

Build.prop file

Basically, build.prop is system or firmware properties file which is located in /system folder.
System Directory consists of all necessary information for your ROM specific build.

We are going to edit this file and many custom ROM developers edit these files to free up
existing RAM. Editing should be carefully done and once small changes can be harmful to your
mobile device. Backup all your data before you make any changes.

Fast Reboot
persist.sys.purgeable_assets=1
 Faster boot
ro.config.hw_quickpoweron=true
Increasing Video Recording Quality
ro.media.enc.hprof.vid.bps=8000000
Change Screen Rotate To 270 degree
windowsmgr.support_rotation_270=true;
change Heap Size
dalvik.vm.heapsize=64m
Render UI With GPU
debug.sf.hw=1
Make device much Smoother
windowsmgr.max_events_per_sec=150
Video Acceleration Enabled And HW debugging.
video.accelerate.hw=1
debug.sf.hw=1
debug.performance.tuning=1
debug.egl.profiler=1 ( Measure rendering time in adb shell dumpsys gfxinfo)
debug.egl.hw=1
debug.composition.type=gpu (Disable hardware overlays)
Increase Performance
debug.performance.tuning=1
Disable Sending Usage Data
ro.config.nocheckin=1
Deeper Sleep/Better battery life
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
Ringing Will Start Immediately
ro.telephony.call_ring.delay=0
ring.delay=0
Enable/Disable Error Checking
ro.kernel.android.checkjni=0
change Media Streaming Quality
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=true
media.stagefright.enable-record=false
15) Enable/Disable Boot Animation
debug.sf.nobootanimation=1
Force To Remain Launcher In Memory
ro.HOME_APP_ADJ=1
Enable/Disable Waking by Volume Buttons
ro.config.hwfeature_wakeupkey=0
Off The Proximity Quickly After Call
mot.proximity.delay=25
ro.lge.proximity.delay=25
Better Signal Tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
NetSpeed Tweaks
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
Google DNS Tweak
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
Photo And Video Quality
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.capture.maxres=8m
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true
ro.media.enc.hprof.vid.fps=65
change Touch Responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
Scrolling Responsiveness
windowsmgr.max_events_per_sec=500
Power Save Tweaks
pm.sleep_mode=1
ro.ril.power_collapse=1
 wifi.supplicant_scan_interval=180
ro.mot.eri.losalert.delay=1000 (could brake tethering)
Enable/Disables Debug Icon On Status Bar
persist.adb.notify=0
Faster Scrolling
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
windowsmgr.max_events_per_sec=150
ro.min_pointer_dur=8
wifi to scan less frequently
wifi.supplicant_scan_interval=180
improve battery under no signal
ro.mot.eri.losalert.delay=1000
makes apps load faster and frees ram
dalvik.vm.dexopt-flags=m=v,o=y
Off The Proximity Quickly After Call
ro.lge.proximity.delay=25
mot.proximity.delay=25
Enable/Disables built in error reporting
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
3G Network tweaks.
ro.ril.hep=0
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=8
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=6
Enable/Disables logcat
logcat.live=disable
Screen recognizes only two fingers.
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
Support for ipv4 and ipv6.
persist.telephony.support.ipv6=1
persist.telephony.support.ipv4=1
Enable/Disables blackscreen issue after a call.
ro.lge.proximity.delay=25
mot.proximity.delay=25
Better call voice quality.
 ro.ril.enable.amr.wideband=1

Dalvik Virtual Machine tweaks.

dalvik.vm.checkjni=false
dalvik.vm.dexopt-data-only=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=64m
dalvik.vm.verify-bytecode=false
dalvik.vm.execution-mode=int:jit
dalvik.vm.lockprof.threshold=250
dalvik.vm.dexopt-flags=m=v,o=y
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.jmiopts=forcecopy
Enable/Disable notification while adb is active
persist.adb.notify=0
Change LCD density
ro.sf.lcd.density=240
Key lights stay on while screen is on.
ro.mot.buttonlight.timeout=0
Enable/Disable notification sound for SD storage insert
persist.service.mount.playsnd=0
Enable display dithering
persist.sys.use_dithering=1
change volume steps in the call.
ro.config.vc_call_steps=20
Lock app in memory.
sys.keep_app_1=com.your.app.app
Enables MTP mode.
persist.sys.usb.config=mtp

Smooth UI
persist.service.lgospd.enable=0
persist.service.pcsync.enable=0
Wireless Tweaks
net.ipv4.ip_no_pmtu_disc=0
net.ipv4.route.flush=1
net.ipv4.tcp_ecn=0
net.ipv4.tcp_fack=1
net.ipv4.tcp_mem=187000 187000 187000
net.ipv4.tcp_moderate_rcvbuf=1
net.ipv4.tcp_no_metrics_save=1
 net.ipv4.tcp_rfc1337=1
net.ipv4.tcp_rmem=4096 39000 187000
net.ipv4.tcp_sack=1
net.ipv4.tcp_timestamps=1
net.ipv4.tcp_window_scaling=1
net.ipv4.tcp_wmem=4096 39000 18700
wifi.supplicant_scan_interval=180
Change android device name and version
ro.build.display.id=Your ROM name
ro.build.version.release=4.4.2 (Android version)

Defalt.prop

Default.prop file is also specified android ROM properties and it is located in init folder both
boot.img as well as recovery.img file. This also consists of all necessary information for your
ROM specific build.
ro.secure=0 it means adbd running as root by default. ro.debuggable=1 and service.adb.root=1
will allow you to run adbd as root via the ADB root command.

Once you are able to run ADB as root via ADB root, you will be able to remount the /system/
directory as writable and can install anything which you want.

when we open this default.prop file we get as

Root/Unroot ROM
This line show either a device is rooted or not 1 indicate the device is unrooted and 0 rooted.
ro.secure=1( 1 unroot,0 root)

USB Enable/Disable
This line indicated that device is USB enable by default or not. 0 indicate the device by default
USB debugging and 1 not.
ro.debuggable=0

Storage
persist.sys.usb.config=mass_storage

Adb enable/disable
persist.service.adb.enable=1( 1 enable, o desable ).
Chapter 24 android app libraries and system permissions

System apps
A System application is NOT an application which is signed by the OSs platform signatures.
/system is read-only without root so it prevents uninstalling applications from /system/app and
/system/priv-app. Applications that are critical are put there so that they can't be uninstalled.

/system/priv-app also allows apps installed there to use signatureOrSystem and other privileged
permissions.

As for why apps might be critical, that depends on the ROM. HTC's Sense is heavily dependent
on their built-in apps from what I hear, for example. They simply didn't design their UI such that
it would work natively with third party apps.Updates for some system apps can be downloaded
via the Play Store, such as Google Maps.
All System applications are stored in system/app directory. We from this folder we can add any
application as system application and also remove.
Some application may be in system/private app or system/vendor/app directory.
when we open this app folder we get as

System Libraries
Android.mk


This page describes the syntax of the Android.mk build file, which glues your C and C++ source
files to the Android NDK.
The Android.mk file resides in a subdirectory of your project's jni/ directory, and describes your
sources and shared libraries to the build system

The syntax of the Android.mk allows you to group your sources into modules. A module is either
a static library, a shared library, or a standalone executable.

All system libraries are stored in system/lib directory in form of. so files are.
System Permission
All system permission files are located in system/etc/permission directory. Here we can mention
all system permission like wifi, camera etc.
Break pattern and password lock

Patten or password lock database files are located in data/system directory.

Break pattern lock
Pattern lock database file is located with the gesture.key
Here we are removing gesture.key database file by ADB command but your device should be
rooted.
password lock
password lock database file is located with the password.key name.
Similarly, we can also remove the password.key database file by using ADB command.
Create an application as system application
All system application are located in /system/app/ directory in android rom so if want create our
application as system application we will have to insert this application into app directory.
try {
Runtime.getRuntime()
.exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] {"su","-c","cat "+ f + " > /system/app/"+name });
Toast.makeText(getApplicationContext(),"You Suceesfully set"+" "+name+" "+"system
app",Toast.LENGTH_LONG).show();
} catch (IOException e) {
Toast.makeText(getApplicationContext(),"You need to root access",
Toast.LENGTH_LONG).show();
}
Remove an application System application

Similarly we have to remove application form app directory.

try {
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] {"su","-c","rm"+" system/app/"+application name });
Toast.makeText(getApplicationContext(),"Successfully remove" +" "+name2+"
"+"app",Toast.LENGTH_LONG).show();
} catch (IOException e) {
Toast.makeText(getApplicationContext(),"You need to root access",
Toast.LENGTH_LONG).show();
}

Copy system application

Similarly we can keep backup of any system application.

try {
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c","cat"/system/app/applicationname" >
/sdcard/SystemApps/"+name2 });

Toast.makeText(getBaseContext(), "SuceesFully Copy"+name2,

Toast.LENGTH_LONG).show();
} catch (IOException e) {
Toast.makeText(getApplicationContext(),"You need to root access",
Toast.LENGTH_LONG).show();

}
Chapter 25 Create and change boot animation programmatically in
android

Create Boot animation

In given below example here will create bootanimation.zip file programmatically. In this example
are first will create many jpeg files from a video file then will create part0 folder and desc.txt file
again we will convert these part0 folders and desc.txt file in a bootanimation.zip file.

package com.create.bootaminmationcreater;

import java.io.BufferedInputStream;
import java.io.BufferedOutputStream;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.IOException;
import java.io.InputStream;
import java.io.OutputStream;
import java.util.ArrayList;
import java.util.List;
import java.util.zip.CRC32;
import java.util.zip.ZipEntry;
import java.util.zip.ZipOutputStream;

import org.jcodec.api.FrameGrab.MediaInfo;
import org.jcodec.api.JCodecException;
import org.jcodec.api.android.FrameGrab;
import org.jcodec.common.FileChannelWrapper;
import org.jcodec.common.NIOUtils;

import android.app.Activity;
import android.app.Dialog;
import android.graphics.Bitmap;
import android.graphics.Bitmap.CompressFormat;
import android.os.AsyncTask;
import android.os.Bundle;
import android.os.Environment;
import android.os.Handler;
import android.util.Log;
import android.view.View;
import android.widget.TextView;
import android.widget.Toast;

import com.create.bootaminmationcreater.FileChooserDialog.OnFileSelectedListener;

public class Create extends Activity {

private TextView progress;
List<String> filesListInDir;
private volatile boolean flag;
InputStream in = null;
OutputStream out = null;

protected void onCreate(Bundle savedInstanceState) {

super.onCreate(savedInstanceState);
setContentView(R.layout.create);
progress = (TextView) findViewById(R.id.progress);
}

public void startDecode(View view) {

try {

File fileOrDirectory=new File("/sdcard/BootAnimation Creater");

DeleteRecursive(fileOrDirectory);
FileChooserDialog dialog = new FileChooserDialog(view.getContext());
dialog.addListener(new OnFileSelectedListener() {
public void onFileSelected(Dialog source, File folder, String name) {
}

public void onFileSelected(Dialog source, File file) {

source.hide();
new Decoder().execute(file);
}
});
dialog.show();
} catch (Exception e) {
}
}

void DeleteRecursive(File fileOrDirectory) {

if (fileOrDirectory.isDirectory())
for (File child : fileOrDirectory.listFiles())
DeleteRecursive(child);
fileOrDirectory.delete();
}

public void stopProcess(View view) {

flag = true;
}

public void create(View view) {

try {
filesListInDir = new ArrayList<String>();

File dir = new File("/sdcard/BootAnimation Creater");

String zipDirName = "/sdcard/BootAnimation Creater/bootanimation.zip";

zipDirectory(dir, zipDirName);
} catch (Exception e1) {
}

Toast.makeText(getBaseContext(), "wait...........", Toast.LENGTH_LONG).show();

new Handler().postDelayed(new Runnable() {
public void run() {
try {
Toast.makeText(getBaseContext(), "Create Bootanimation",Toast.LENGTH_LONG).show();
} catch (Exception e) {
e.printStackTrace();
}, 10000);

private void zipDirectory(File dir, String zipDirName) {

try {

populateFilesList(dir);

FileOutputStream fos = new FileOutputStream(zipDirName);

ZipOutputStream zos = new ZipOutputStream(fos);

byte[] buffer = new byte[1024];

int bytesRead;

CRC32 crc = new CRC32();

for (String filePath : filesListInDir) {

File file = new File(filePath);

BufferedInputStream fis = new BufferedInputStream(new FileInputStream(file));
crc.reset();
while ((bytesRead = fis.read(buffer)) != -1) {
crc.update(buffer, 0, bytesRead)
}
fis.close();

fis = new BufferedInputStream(new FileInputStream(file));

ZipEntry entry = new ZipEntry(filePath.substring(dir.getAbsolutePath().length() + 1,
filePath.length()));
entry.setMethod(ZipEntry.STORED);
entry.setCompressedSize(file.length());
entry.setSize(file.length());
entry.setCrc(crc.getValue());
zos.putNextEntry(entry);
while ((bytesRead = fis.read(buffer)) > 0) {
zos.write(buffer, 0, bytesRead);
}
zos.closeEntry();
fis.close();
}
zos.close();
fos.close();
} catch (IOException e) {
}
}
private void populateFilesList(File dir) throws IOException {
File[] files = dir.listFiles();
for (File file : files) {
if (file.isFile())filesListInDir.add(file.getAbsolutePath());
else
populateFilesList(file);
}
}
private class Decoder extends AsyncTask<File, Integer, Integer> {
private static final String TAG = "DECODER";
protected Integer doInBackground(File... params) {
FileChannelWrapper ch = null;
try {
ch = NIOUtils.readableFileChannel(params[0]);
FrameGrab frameGrab = new FrameGrab(ch);
MediaInfo mi = frameGrab.getMediaInfo();
Bitmap frame = Bitmap.createBitmap(mi.getDim().getWidth(), mi.getDim().getHeight(),
Bitmap.Config.ARGB_8888);
for (int i = 0; !flag; i++) {
frameGrab.getFrame(frame);
if (frame == null)
break;
OutputStream os = null;
try {
File folder = new File(
Environment.getExternalStorageDirectory()+ "/BootAnimation Creater");
boolean success = true;
if (!folder.exists())
success = folder.mkdir();
if (success) {
copydesc();
File folder1 = new File(
Environment.getExternalStorageDirectory()"/BootAnimation Creater/part0");
boolean success1 = true;
if (!folder1.exists())
success1 = folder1.mkdir();
if (success1) {
os = new BufferedOutputStream(new FileOutputStream(new File("/sdcard/BootAnimation
Creater/part0",String.format("img%08d.jpg",i))));
frame.compress(CompressFormat.JPEG, 90, os);
}
}
} finally {
if (os != null)
os.close();
}
publishProgress(i);
if(i==50)
{
flag = true;
}
} catch (IOException e) {
} catch (JCodecException e) {
} finally {
NIOUtils.closeQuietly(ch);
}
return 0;
}
private void copydesc() {
in = getApplicationContext().getResources().getAssets().open("desc.txt");
out = new FileOutputStream("/sdcard/BootAnimation Creater/"+ "desc.txt");
copyFile(in, out);
}
private void copyFile(InputStream in, OutputStream out)
throws IOException {
byte[] buffer = new byte[1024];
int read;
while ((read = in.read(buffer)) != -1) {
out.write(buffer, 0, read);
}
}
protected void onProgressUpdate(Integer... values) {
progress.setText(String.valueOf(values[0]));
}

}
}

Change Boot animation programmatically

For change boot animation we will create ADB command programmatically. We can change
boot animation two types because the bootanimation.zip file may exist in two location first one in
/system/media/bootanimation.zip or in second /data/local/bootanimation.zip.
First method

for change in first location /system/we will have to needed rooted device.
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime()
.exec(new String[] {"su","-c","cat "+ f + " > /system/media/bootanimation.zip" });
Toast.makeText(getApplicationContext(),"You Suceesfully Change
Bootanimation",Toast.LENGTH_LONG).show();
Toast.makeText(getApplicationContext(), "Wait till boot.....",Toast.LENGTH_LONG).show();
new Handler().postDelayed(new Runnable() {
public void run() {
Runtime.getRuntime().exec(
new String[] { "su", "-c", "reboot" });
}
}, 20000);
}

second method

for change in second location /data/local/bootanimation.zip, it is not the necessarily rooted

device.
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] {"su","-c","cat "+ f + " > /data/local/bootanimation.zip"
});
Toast.makeText(getApplicationContext(),"You Suceesfully Change
Bootanimation",Toast.LENGTH_LONG).show();
Toast.makeText(getApplicationContext(), "Wait.....",Toast.LENGTH_LONG).show();
new Handler().postDelayed(new Runnable() {
public void run() {
Runtime.getRuntime().exec(
new String[] { "su", "-c", "reboot" });
}, 20000);

}
Chapter 26 android OS programmatically

Reboot Device programmatically

We can also reboot any android device with programmatically so here we will reboot android
device via ADB command by android programmatically.

try {
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "reboot" });
Toast.makeText(getBaseContext(), "Reguler Reboot", Toast.LENGTH_LONG) .show();
} catch (IOException e) {
e.printStackTrace();
}

Reboot to Recovery programmatically

We can also do the reboot to recovery any android device with programmatically so here we will
reboot to recovery android device via ADB command by android programmatically.

try {
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "reboot recovery" });
Toast.makeText(getBaseContext(), "Reboot to Recovery", Toast.LENGTH_LONG) .show();
} catch (IOException e) {
e.printStackTrace();
}

Reboot to bootloader programatically

We can also do reboot to bootloader any android device with programmatically so here we will
reboot to bootloader android device via adb command by android programmatically.
try {
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "reboot bootloader" });
Toast.makeText(getBaseContext(), "Reboot to bootloader ", Toast.LENGTH_LONG) .show();
} catch (IOException e) {
e.printStackTrace();
}

Power off Device programatically

Similarly we can switch off any device via programmatically.

try {
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "reboot -p" });
Toast.makeText(getBaseContext(), "Power off", Toast.LENGTH_LONG) .show();
} catch (IOException e) {
e.printStackTrace();
}

Factory Reset Device programatically

We can also reset any device with programming.

try {
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", " recovery --wipe_data" });
Toast.makeText(getBaseContext(), "Factory Reset", Toast.LENGTH_LONG) .show();
} catch (IOException e) {
}

Storage management Programmatically

We can store our android ROM data in three possible location first in system memory or we can
say that ROM memory, the second one is in internal storage or we can say that device internal
memory and third one is in external memory with providing by TF card or memory card by
default by ADB command but our device should be rooted.

Set as system memory by default

Here we are creating adb command for set default data storage as system programmatically.
try {
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "pm set-install-location 0" });
} catch (IOException e) {
}

Set as internal memory by default

Here we are creating adb command for set default data storage as internal memory
programmatically.
try {
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "pm set-install-location 1" });
} catch (IOException e) {
}

Set as internal memory by default

Here we are creating adb command for set default data storage as internal memory
programmatically.
try {
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "pm set-install-location 2" });
} catch (IOException e) {

check rooted device programmatically in android

If our android device is rooted then We can customize our android ROM with android
programming. In this chapter will study about rooting, boot animation maker, boot animation
checker and other some programming. Here we are implementing ADB commands in android
programming.

Root Checker

We already know that how we can check root status but ADB commands But here we will check
root status by android programming. Here we have two conditions that device is rooted
externally or internally.

Root Checker externally

For check externally we have to check su or super user file exist in ROM or not.

First method

For check externally we will have to check that su file executes or not.
private boolean canExecuteSuCommand()
{
try
{
Runtime.getRuntime().exec("su");
i = 1;
return i;
}
catch (IOException localIOException)
{
while (true)
int i = 0;
}
}
Or either su file exist or not in xbin folder.
private boolean hassufile()
{
return new File("/system/sbin/su").exists();
}

Second method

The second method we are checking for superuser.apk file exist in app folder or not.

private boolean hasSuperuserApkfile()

{
return new File("/system/app/Superuser.apk").exists();
}

Root Checker internally

For check root status we will have findtest_kesys string exist in buid.prop file which exist in
/system/ directory.
private boolean isTestKeyBuild()
{
 String str = Build.TAGS;
if ((str != null) && (str.contains("test-keys")));
for (int i = 1; ; i = 0)
return i;

Create an application as system application

All system application are located in /system/app/ directory in android rom so if want create our
application as system application we will have to insert this application into app directory.
try {
Runtime.getRuntime()
.exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] {"su","-c","cat "+ f + " > /system/app/"+name });
Toast.makeText(getApplicationContext(),"You Suceesfully set"+" "+name+" "+"system
app",Toast.LENGTH_LONG).show();
} catch (IOException e) {
Toast.makeText(getApplicationContext(),"You need to root access",
Toast.LENGTH_LONG).show();
}

Remove an application System application

Similarly we have to remove application form app directory.

try {
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] {"su","-c","rm"+" system/app/"+application name });
Toast.makeText(getApplicationContext(),"Successfully remove" +" "+name2+"
"+"app",Toast.LENGTH_LONG).show();
} catch (IOException e) {
Toast.makeText(getApplicationContext(),"You need to root access",
Toast.LENGTH_LONG).show();
}

Copy system application

Similarly we can keep backup of any system application.

try {
Runtime.getRuntime().exec(new String[] { "su", "-c","mount -o remount,rw -t yaffs2
/dev/block/mtdblock3 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c", "chmod 777 /system/" });
Runtime.getRuntime().exec(new String[] { "su", "-c","cat"/system/app/applicationname" >
/sdcard/SystemApps/"+name2 });

Toast.makeText(getBaseContext(), "SuceesFully Copy"+name2,

Toast.LENGTH_LONG).show();
} catch (IOException e) {
Toast.makeText(getApplicationContext(),"You need to root access",
Toast.LENGTH_LONG).show();