[X]Assistant

[A.S._id]

Toolkit developer mods based on Android.

Links to related topics:
Instructions for editing system resources | Editing framework-res.apk

When posting content, if possible, attach instructions

пїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅ: download

1. It is allowed to upload only verified software (it is also allowed to unsubscribe and give explanations on existing software - on which device and how it was tested).
2. Each tool should have a description (accessory, OS, manual).
3. It is forbidden to upload and give links to illegal (pirated) content.
4. It is forbidden to discuss software in the topic.

Catalog - Tools for modifying firmware and Android applications

Post has been editedFashionon - 18.02.16, 11:12

[Dimar]

Catalog - Tools for modifying firmware and Android applications

Auxiliary software

• Odmina's Tambourine - A tool for fine-tuning servers and not only.
  
• Java Development Kit - Java application development kit
  
• Android SDK - development tools
  
• Busybox - a set of command line utilities for UNIX (Linux) systems
  

Instruments

Decompiling / compiling / editing * .apk files

• UnicodeConverter.bat - Unicode conversion to human-readable language and back.
  
• ApkTools for Android 6.0.1
  
• Apktoolmod - based on apktool 2.0.2
  
• Tickle my android - Multi-purpose kitchen, for editing system resources
  
• FMD Apktool OS Linux - A utility for disassembling / assembling applications for Linux from the FMD team
  
• Apktool on Linux OS Installing and using apktool on OS Linux Ubuntu 14.04-64bit. Automatic installation
  
• APKTool - Ready kit, including everything you need to disassemble apk files
  
• Batch ApkTool - Allows batch deodexing, decompiling, modifying resources and smali-code ( transition to the topic )
  
• Apk manager - Ready kit, including everything you need to disassemble apk files
  
• Coloredit - The program allows you to conveniently edit the color.xml file
  
• Apk Manager, for disassembly, assembly, signature - For UBUNTU. In Russian.
  
• Easy debugging tool - Application to determine the running application activation
  
• Public ID Converter - Utility to find and replace id from public.xml in .smali
  
• Converter smiles - Recently, many instructions are not suitable for each other because of smali versions, the solution to this problem is not a big script
  
• The list of programs for working with applications (. Apk) on your android device.
  

Kernel, kernel, * .img

• Carliv Image Kitchen for Android - Utility for unpacking / packing boot.img or recovery.img under WINDOWS and Linux.
  
• The script for repacking boot.img / recovery.img - Repacking boot.img / recovery.img on device without PC
  
• Image Factory - work with the * .img image on android
  
• BOOT & RECOVERY REPACKER - tool for repacking boot.img and recovery.img in LINUX
  
• split_bootimg - Unpacking boot.img
  
• mkbootimg_tools-master - Linux utility with dtb support, correctly repacking msm boot.img recovery.img
  
• Android Image Kitchen - Unpack / Repack Kernel / Recovery + ramdisk - Utility for repacking kernels and recovery under Windows
  
• KERNEL Tools - a set of utilities for repacking kernels
  
• UBUNTU - Configuration and preparation for work with source codes, kernels, applications and firmware under ANDROID
  

Deodex applications

• JoelDroid Lollipop Batch Deodexer - Tool for batch deodexing apps in android Lollipop
  
• Deodexer for Android Runtime - Tool for deodexing Android 5.0 applications and above
  
• xUltimate - A package of utilities for deodexing system apk.
  
• AutoDEOTool - deodex firmware
  
• DeodexForART (Lollipop) _v2.2.2 - Full-automatic deodexed tool for lollipop
  

Firmware development tools

• FMD Tools - New utility for convenient processing of firmware files
  
• Utilities for RockChip - 100% working firmware for stock driver, OS Ubuntu
  
• Cygwin - UNIX-like environment and command line interface for Microsoft Windows
  
• Cygwin - detailed instructions for UNIX-like environment and command line interface for Microsoft Windows
  
• Android Kitchen - A tool for creating custom firmware based on Linux.
  
• INSTALL Android Kitchen - by dsixda (xda-developers.com) - FOR MAC OS X 10.8.x
  
• Odin3 ROM Editor - Only for Linux
  
• Build firmware on Samsung Galaxy S i9000 for Odin .[/ url]
  
• New TuxBox Flash Tools v.1.0 - utility for working with cramfs and yaffs2 images
  
• Compiling Android 4.1 Jelly Bean on Ubuntu Linux
  
• [DEV_TOOL] HTC ROM-EXTRACTOR - Tool for working with HTC firmware in LINUX
  
• [DEV_TOOL] TAR.MD5 PACKAGER - A tool for repacking firmware and their individual parts in .tar.md5 for subsequent firmware through Odin under Windows
  
• ROM Helper - integrated approach to working with firmware from under Windows
  
• jBART - Combine for working with firmware based on Android OS, a also with apk files
  
• Branded console tool RockChip - Allows you to do everything you need for the developer
  
• IEEE Calculator (IEEE Floating Point Calculator) - translation of values ​​from float to HEX and back IEEE Floating Point Calculator
  

Graphics, Color

• iCatalyst - application to reduce the weight of images while maintaining quality
  
• Draw9patch utility for working with * .9.png images.
  
• HTML Color Picker - With this application, you can quickly see the combination of text and background.
  
• PNG_convertor_v2.3 - A tool for batch conversion of indexed .png images to non-indexed
  
• 9 Patch Editor - This application helps to edit the graphic resources of Android applications and themes.
  
• 9Patch Resizer - group resizing of graphics
  
• Android Color Tool
  
• Color Conversion (Tool) - A tool to convert color codes between HEX, SMALI and XML.
  

Flashers

• HEIMDALL - OS: Linux, OS X, Windows Flash Driver
  
• HEIMDALL FLASHER SGSIII / SGNII SUPPORT - a tool based on the famous Heimdall flasher - a firmware version in LINUX
  
• COPERFIELD ROM MAKER v.0.0.5 - a tool for creating firmware for some Samsung devices
  
• Installing the "android-tools" package (adb and fastboot) on Ubuntu 12.04, 11.10 and 11.04
  
• Porting tool by fagci - a script for porting Android firmware. OS: Windows XP +
  
• Packing by tar-md5 - A small tool to automate tar.md5 packaging for UBUNTU
  
• ADB RUN - simplified use of ADB
  HUAWEI Multi-Tool -Allows you to perform the sequence of commands fastboot, adb and adb shell, helping you to produce many well-known operations without unnecessary gestures.
  

Post has been editedDimar - 05.12.17, 11:46

Reason for editing: HUAWEI Multi-Tool

[A.S._id]

Java Development Kit
The first thing you need to install before working with Java applications.

Description

Wikipedia, the free encyclopedia
Software development kit
Developer Oracle Corporation (formerly Sun Microsystems)http://www.oracle.com/technetwork/java/javase

Java Development Kit (abbreviated as JDK) is a freeware Oracle Corporation (formerly Sun Microsystems) Java application development kit that includes the Java compiler (javac), standard Java class libraries, examples, documentation, various utilities, and the Java runtime (JRE ). The JDK does not include an integrated development environment for Java, so a developer using only the JDK has to use an external text editor and compile his programs using command line utilities.

All modern integrated development environments in Java, such as NetBeans, Sun Java Studio Creator, IntelliJ IDEA, Borland JBuilder, Eclipse, rely on services provided by the JDK. Most of them use the JDK compiler to compile Java programs. Therefore, these development environments either include one of the JDK versions, or require JDK pre-installation on the developer’s machine for their work.

The full JDK source code is available, including the source code of the Java compiler itself.

References:
http://www.oracle.com/technetwork/java/jav...rceSiteId=otnru
http://www.oracle.com/technetwork/java/jav...oad-432154.html

[A.S._id]

Android SDK
The second thing you need to install before working with Android

Description

Wikipedia, the free encyclopedia
Android applications are programs in non-standard byte-code for the Dalvik virtual machine.

Google offers a free download development toolkit (Software Development Kit), which is designed for x86-machines running Linux, Mac OS X (10.4.8 or higher), Windows XP and Windows Vista. To develop JDK 5 or newer.

Development of applications for Android can be conducted in the Java language (not lower than Java 1.5). There is a plugin for Eclipse - “Android Development Tools” (ADT), designed for Eclipse versions 3.3-3.6. For IntelliJ IDEA, there is also a plugin that facilitates the development of Android applications. It is reported that an experimental plugin has been developed for the NetBeans IDE development environment. In addition, there is Motodev Studio for Android, which is a comprehensive development environment based on Eclipse and allows you to work directly with the Google SDK.

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

[A.S._id]

Cygwin
Cygwin is a UNIX-like environment and command line interface for Microsoft Windows. Cygwin provides tight integration of Windows applications, data, and resources with applications, data, and resources of a UNIX-like environment. You can run Windows applications from Cygwin, or you can use Cygwin tools from Windows.
OS: Windows x86, x64
A source
Manual
Download

Installation

1. Extract the cygwin archive and run the setup file.
2. Select Install from Local Directory:

3. Select the installation path cygwin, the default in the root of the disk C: /

4. Indicate the path toPackage directory, it is in the unzipped cygwin archive:

5. On the notification, click OK:


6. Click on the symbol shown in the figure to change the status toInstalland pressNext

7. Completing the installation so that Windows does not make any changes, select in the menuCancel:

Repacking firmware

1. Create a directory and extract the firmware files into it using 7zip or WinRAR and place them in the previously created directory on the C: / drive, as shown in the figure:

2. Extract the archive with an empty dbdata.rfsEmpty_dbdata.rfs_file.zip(2.09 KB)
and put in the same directory:

3. Launch cygwin from the desktop shortcut and do the following:
Specify the directory files -cd c: / your folder
Creating PDA.tar.md5:
Creating a PDA.tar file -tar -c param.lfs zImage factoryfs.rfs dbdata.rfs>>PDA_JS5.tar
Creating MD5 hash -md5sum -t PDA_JS5.tar>>PDA_JS5.tar
Adding MD5 hash information to the tar file -mv PDA_JS5.tar PDA_JS5.tar.md5

Creating Phone.tar.md5:

Creating Phone.tar -tar -c modem.bin>>PHONE_JPY.tar
Creating MD5 hash -md5sum -t PHONE_JPY.tar>>PHONE_JPY.tar
Adding MD5 hash information to the tar file -mv PHONE_JPY.tar PHONE_JPY.tar.md5

Creating CSC.tar.md5

Creating CSC.tar -tar -c cache.rfs>>CSC_XENJS3.tar
Creating MD5 hash -md5sum -t CSC_XENJS3.tar>>CSC_XENJS3.tar
Adding MD5 hash information to the tar file -mv CSC_XENJS3.tar CSC_XENJS3.tar.md5

All commands for packaging and creating a single tar.md5 file (3 commands) can be executed as a single command as shown in the example:

tar -c param.lfs zImage factoryfs.rfs dbdata.rfs>>PDA_JS5.tar; md5sum -t PDA_JS5.tar>>PDA_JS5.tar; mv PDA_JS5.tar PDA_JS5.tar.md5

Note*

(The first file in the command will be the first file to be added to the download file and the first firmware. I use this command in this particular order in accordance with the pit file and device sections, of which are:
] START
boot.bin
.pit
efs.rfs
sbl.bin
sbl.bin
param.lfs
zImage
zImage
factoryfs.rfs
dbdata.rfs
cache.rfs
modem.bin
END)

One of the reasons for the unsuccessful MD5 checksum is to rename it after packaging, so you cannot rename the packed files.
After repacking the archives, you can test them.
Run Odin and substitute the packed files and click start, it should turn out as in the picture.

if not, start over.

*

Post has been editedDimar - 25.01.16, 20:15

Reason for editing: In the topic header

[333vs333]

Hello! I decided to make my contribution to the assembly of the firmware onSamsung Galaxy S i9000for one:

Description

1. A root must be present on the phone, and a kernel supporting adb is installed (best speed / speedmod).
2. On the BB, the JDK, SDK must be installed.
3. In the on state, connect the phone to the BB, run the command line (type "cmd" in the search bar and press "enter"), switch to the folder with adb and type the following commands:

How easier it is to use adb via the command line for newbies:

The easiest way to launch the command line will be in the Total Commander / Total Commander, by clicking on the icon at the top of the "System Panel". A set of system plug-ins and utilities will appear, you need to click on the command line icon "Command line"

Screenshots to help you

adb shell
su

After entering "adb shell" the "$" icon should appear, it means everything is in order.

It looks like this:

After entering "su", your phone is ready to work with adb (if you connect the phone with adb for the first time, after entering "su" on the phone you need to confirm the request for root rights as for a regular program).
4. Enter the following commands and wait for the system copy creation to complete.(during the operation, do not touch the phone):

mkdir / sdcard / BackupRom - creates a folder / BackupRom in ext. memory card;
dd if = / dev / block / stl9 of = / sdcard / BackupRom / factoryfs.rfs - creates a copy of the system.

When the creation of a copy of the system is completed, a message will appear indicating the end of the operation:

Screen:

5. Enter the followingcommands for correct exit:

exit
exit

After that, you can close the command line and disconnect the phone from the BB.

The file you need - factoryfs.rfs can be found in the folder you created earlier on the sdcard / BackupRom path.
Next, copy the factoryfs.rfs file on the BB to a separate folder for further assembling the firmware. There also copy the remaining missing components of the firmware:

Components of the firmware:

Take the missing components from the stock firmware. Choose your kernel and modem at your discretion, as long as they are compatible with the firmware. In the total commander, select all components of the firmware, right-click and select "Pack files". In the window that appears, select "TAR" and click "OK."
Everything, your firmware is ready. Stitch as part of the "PDA" with a pit and a daw for repartition.
I'll tell you a secret, there is an adb emulator for working with adb commands right on your phone. So a copy of the system can be made without the help of BB.

jackpal.AndroidTerminalEmulator.1.0.21.apk(74.32 KB)


Post has been editedDimar - 25.01.16, 20:16

Reason for editing: Spoiler

[sk0t]

Addition

As i9000 @ 09/15/2011, 23:32

xUltimate Color Converter- convert hexadecimal color to binary code for editing in smali Use: xUltimate-CC {RRGGBB}

Here's more on this topic

acc.rar(1.8 KB)

* For Win,
Unix-like to change the extension to htm

FieldHEXSupports short color recording:09f =>FF0099FF
In fieldSMALIautomatically added0xif absent:3f3f40 =>0x3F3F40
█- is introduced
█- It turns out

Tip: If your smali color value is set asconst / high16(const / high16 v6, -0x1) to find out the color - add to the value 4 zero to the right (-0x1 =>-0x10000)

Updated: 11/09/2011 15:00
Reason: Invalid color calculation with valuesHEXless80000000

Post has been editedDimar - 25.01.16, 20:19

[A.S._id]

KERNEL Tools
OS: Linux

How to repack the kernel in order to make changes to it.
To begin with, the kernels are divided into two types:
1) The kernel consisting of the boot.img image consisting of zImage and RAM Disk (RAM disk for initial initialization).
2) A kernel consisting of a zImage image into which the initramfs image is integrated (a new boot disk concept - it is a gzip-compressed cpio archive).
So repack boot.img:
Instruction
Tool
zImage repacking:
Instruction
Tool
extracting initramfs from zImage
Instruction
Tool
Windows tool

Post has been editedAs i9000 - 29.11.11, 00:48

[vSowa]

New TuxBox Flash Tools v.1.0

Very handy Win utility for working with cramfs and yaffs2 images. Works with classic images (without perversions, signature type, etc.)
Allows you to delete / add files and links (understands the clipboard from the win-explorer), assign rights and owners.
Originally createdMcRipfor satellite receivers (therefore swears on the size of the firmware) in German.
I translated into Russian (omitting what concerns the firmware Rez)

NewTuxBox_ru.7z(1023.59 KB)


Post has been editedDimar - 25.01.16, 20:22

Reason for editing: Screenshot in spoiler

[Snegovik]

Coloredit

The program allows you to conveniently edit the file.color.xml.
Unpack the archive, run the program, select the file and modify it.

ColorEdit.zip(13.22 KB)


Post has been editedDimar - 25.01.16, 20:24

[A.S._id]

HEIMDALL - flasher

OS: Linux, OS X, Windows

Description

So let's start - let's look at the Samsung i9000 firmware using the Linux version as an example.
1. Downloading Heimdall (both packages of Release: Heimdall 1.3.1 - Command Line (Binary) and Release: Heimdall Frontend 1.3.1 (Binary)) and install.
2. Downloading firmware (I took the 3-file) and extract the contents + need a PIT file.

unpacking

I got eight parts, with the images of dbdata.rfs and cach.rfs both in CODE ... and CSC ..., but in CODE ... they were empty, but since I needed full firmware I took filling.
3. We start the terminal write
$ heimdall-frontend (press Enter)
and we get this shell:

launch

then we go on the device to the firmware mode, we hook the "hose" :), go to the Utilites tab, click on detect and see the inscription "device detected" in the window, i.e. the device is ready for firmware

connection

4. Go to the Flash tab. , we insert PIT into the window of the same name (if necessary, tick the Repartition and No reboot checkboxes), and in turn (observing the sequence), select all of our firmware components, as shown in the figure:

firmware

List of matches:
IBL + PBL = boot.bin (iROM bootloader + primitive bootloader)
SBL = Sbl.bin (secondary bootloader)
PARAM = param.lfs
FACTORYFS = factoryfs.rfs / img
DBDATAFS = dbdata.rfs / data.img
CACHE = cache.rfs / img
HIDDEN = hidden.rfs / img
KERNEL = zImage / boot.img
MODEM = modem.bin
5. Culminating moment - press Start and when the status reaches 100%, the device will reboot with a new firmware or become a brick, so that this does not happen:
Before sewing the bootloaders (if you need to sew them at all) - check yourself (for example, only modem)
List of supported devices:
Captivate, Vibrant, Fascinate, Mesmerize, Epic 4G, Galaxy S 4G, Infuse 4G, GT-I9000T, Galaxy Tab (7 and 10.1 inches), Galaxy S II
Successful firmware!

Post has been editedDimar - 25.01.16, 20:32

Reason for editing: Spoiler

[Hariec]

Android Kitchen - by dsixda (xda-developers.com)
A tool for creating custom firmware based on Linux.

Description

The script program is designed for use in the console.
The program requiresdev-java / sun-jdkor its open implementationdev-java / icedtea(for your distribution, look in the package manager)

The following devices are supported:

HTC Aria / Liberty
HTC Desire
HTC Desire HD / Inspire 4G
HTC Desire S
HTC Desire Z / Vision / T-Mobile G2
HTC Dream / G1
HTC Droid Eris
HTC Evo 3D
HTC Evo 4G
HTC Evo View 4G (untested)
HTC Evo Shift 4G
HTC Flyer (untested)
HTC HD2
- Use NAND ROM method (Please follow this thread for details)
HTC Hero / G2 Touch
HTC Incredible
HTC Incredible 2
HTC Incredible S
HTC Legend
HTC Magic / myTouch 3G
HTC myTouch 3G Slide
HTC myTouch 4G / Glacier
HTC Nexus One
HTC Rezound
HTC Sensation
HTC Tattoo / Click
HTC Thunderbolt
HTC Wildfire / Buzz
HTC Wildfire S (untested)

Acer liquid
Dell Streak 7
Huawei Ideos X6
- Please follow this thread for details
Huawei U8100 / U8110 / U8120 / U8150 / U8160 / U8180 / U8650
Huawei U8220 / T-Mobile Pulse
Lg ally
LG GT540 Optimus
LG Optimus 2X (P990)
LG Optimus Black (unconfirmed)
LG Optimus G2X (P999)
LG P500
- Please follow this thread for details
LG Shine Plus
LG Vortex
Micromax A60
Motorola Atrix (unconfirmed)
Motorola CLIQ / CLIQ XT
Motorola droid
Motorola droid bionic
- Please follow this thread for details
Motorola Milestone (unconfirmed)
- You may need to remove the boot.img before building
Samsung Galaxy Nexus (untested, 'maguro' and 'toro' versions only)
Samsung Galaxy S (GT-I9000 and most variants)
- Please follow this thread for details
Samsung Galaxy S Plus (GT-I9001)
- Please follow this thread for details
Samsung Galaxy S2 (GT-I9100 and Exynos)
- Please follow this thread for details
Samsung Galaxy S2 LTE (AT & T Skyrocket, T-Mobile SGH-T989 and equivalent)
- Please follow this thread for details
Samsung Galaxy W (GT-I8150, untested)
Samsung Nexus S / Nexus S 4G
Sony Xperia X10 / X10 Mini / X10 Mini Pro
- Build ROM without boot.img (please follow this thread for details)
ZTE Blade / Orange San Francisco

Downloading

git clone --depth https://github.com/dsixda/Android-Kitchen

Download archive

Go to the folder

cd android-kitchen

Run the command

./menu

We see the following menu (Russian designation absence in the program)

===================================================================
Android Kitchen - by dsixda (xda-developers.com)
===================================================================

Main Menu

1. Set up working folder from ROM -Unpacks firmware from original_update
2. Add root permissions -Add root rights
3. Add BusyBox -Add BusyBox
4. Disable boot screen sounds -Mute download sound
5. Add wireless tethering -Adds the function of WiFi tethering (distribution of access to the Internet via WiFi)
6. Zipalign all * .apk files to optimize RAM usage -Reduce apk size in memory
7. Change wipe ROM status -Automatic full wipe
8. Change name of ROM -Change the name of the firmware
9. Check update-script for errors -Check update-script for errors
10. Show working folder information -Show unpacked firmware info

Advanced options

11 - Deodex files in your ROM -Deodexing
12 - Add task killer tweak for speed (stock ROM only) -Tweak Task killer
13 - Add / data / app functionality -Add program to firmware
14 - Add Nano text editor + sysro / sysrw -Add Nano console text editor
15 - Add Bash (command shell) -Add bash shell to shell
16 - Add Apps2SD -Transfer programs to SD
17 - Add /etc/init.d scripts support (busybox run-parts) -Support start busybox
18 - Add custom boot animation functionality -Ability to add custom screensaver
19 - Porting tools (experimental)
20 - Tools for boot image (unpack / re-pack / etc.) -Work with the core
21 - Unpack data.img -Unpack data.img
22 - Sign APK or ZIP file (s)Digital signature apk
23 - Convert update-script or updater-scriptConvert update-script
24 - Miscellaneous optins / Plugin scripts

99. Build ROM from working folder -Build the firmware in the installation zip
00. About / Update kitchen -Refresh Kitchen
0. Exit -Output

In the process of work there is a detailed description of all actions, just translate and you will not have any difficulties.

Post has been editedDimar - 25.01.16, 20:51

Reason for editing: Spoiler

[alexseyuh]

Hariec,
Here is a more extended and updated version of the kitchen, as the theme is done onsavagemessiahzine.com !!!
There is an alt menu in Russian))
Creating custom firmware

Post has been editedalexyuh - 17.03.12, 12:11

[alexseyuh]

How to install Android utilities ADB and Fastboot in Ubuntu via PPA

The package called "android-tools", which includes the console utilities "adb" and "fastboot", was recently uploaded to the official repositories of Ubuntu 12.10 Quantal Quetzal. The WebUpd8 team received a request to download this package to the PPA repository for old Ubuntu releases, so the package was backported to Ubuntu 12.04, 11.10 and 11.04.
"adb" (Android Debug Bridge) is a console utility that you can use to access the file system on an Android device; It can be used to send commands, transfer or receive files, install and remove applications, and more.

"fastboot" is a console utility that you can use to open the file system on Android devices via USB.
These utilities can also be found in the Android SDK; using this package is just an alternative and easier way to install them in Ubuntu. Also, packages in PPA are available for both 32-bit and 64-bit, and Google's Android SDK is available only for 32bit.

Installing the "android-tools" package (adb and fastboot) on Ubuntu 12.04, 11.10 and 11.04

sudo add-apt-repository ppa: nilarimogard / webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot

After installation, run "adb" and "fastboot" in the terminal to view the available options, as well as learn how to use these Android utilities.

[alexseyuh]

Compiling Android 4.1 Jelly Bean on Ubuntu Linux

Attention! This instruction will not allow you to create a fully functional firmware right away, but will give you the opportunity to start working on it. The sources take approximately 6Gb. You need about 25Gb of free space to compile 1 build and up to 80Gb (or more) for a complete set of build. Before you start compiling Jelly Bean on Ubuntu, you need to go through several steps to set up a computer to get a ready-made tool.

Instruction

You need the following:

JDK 6 if you want to compile jelly bean. You can download it fromjava.sun.com
or:

sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
sudo apt-get update
sudo apt-get install sun-java6-jdk

Python 2.4 - 2.7, which can be downloaded frompython.orgor:

sudo apt-get install python

Git 1.7 or newer. You can find it ingit-scm.comor:

sudo apt-get install git-core

Install the necessary packages. 64-bit (recommended):

sudo apt-get install git-core gnupg flex bison gperf build-essential \ zip curl zlib1g-dev libc6-dev lib32ncurses5-dev iba32-libs \ x11proto-core-dev dev g ++ - multilib mingw32 tofrodos python-markdown \ libxml2-utils

Newer versions of Ubuntu, such as 11.10, may need to do the following:

sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so

In Ubuntu 12.04, there is currently only experimental support and work on other branches other than master is not guaranteed.

sudo apt-get install git-core gnupg flex bison gperf build-essential \ zip curl libc6-dev libncurses5-dev: i386 libgl1-mesa-dev g ++ - multilib mingw32 openjdk-6-jdk tofrodos \ python-markdown libxml2-utils xsltproc zlib1g-dev: i386
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so

Now let's set up USB:

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

Paste it inside an empty text file.

#Acer SUBSYSTEM == "usb", ATTR {idVendor} == "0502", MODE = "0666" #ASUS SUBSYSTEM == "usb", ATTR {idVendor} == "0b05", MODE = "0666" #Dell SUBSYSTEM == "usb", ATTR {idVendor} == "413c", MODE = "0666" #Foxconn SUBSYSTEM == "usb", ATTR {idVendor} == "0489", MODE = "0666" # Garmin-Asus SUBSYSTEM == "usb", ATTR {idVendor} == "091E", MODE = "0666" #Google SUBSYSTEM == "usb", ATTR {idVendor} == "18d1", MODE = "0666" #HTC SUBSYSTEM = = "usb", ATTR {idVendor} == "0bb4", MODE = "0666" #Huawei SUBSYSTEM == "usb", ATTR {idVendor} == "12d1", MODE = "0666" # K-Touch SUBSYSTEM = = "usb", ATTR {idVendor} == "24e3", MODE = "0666" #KT Tech SUBSYSTEM == "usb", ATTR {idVendor} == "2116", MODE = "0666" #Kyocera SUBSYSTEM == "usb", ATTR {idVendor} == "0482", MODE = "0666" #Lenevo SUBSYSTEM == "usb", ATTR {idVendor} == "17EF", MODE = "0666" #LG SUBSYSTEM == "usb ", ATTR {idVendor} ==" 1004 ", MODE =" 0666 "#Motorola SUBSYSTEM ==" usb ", ATTR {idVendor} ==" 22b8 ", MODE =" 0666 "#NEC SUBSYSTEM ==" usb ", ATTR {idVendor} == "0409", MODE = "0666" #Nook SUBSYSTEM == "usb", ATTR {idVendor} == "2080", MODE = "0666" #Nvidia SUBSYST EM == "usb", ATTR {idVendor} == "0955", MODE = "0666" #OTGV SUBSYSTEM == "usb", ATTR {idVendor} == "2257", MODE = "0666" #Pantech SUBSYSTEM = = "usb", ATTR {idVendor} == "10A9", MODE = "0666" #Philips SUBSYSTEM == "usb", ATTR {idVendor} == "0471", MODE = "0666" # PMC-Sierra SUBSYSTEM = = "usb", ATTR {idVendor} == "04da", MODE = "0666" #Qualcomm SUBSYSTEM == "usb", ATTR {idVendor} == "05c6", MODE = "0666" #SK Telesys SUBSYSTEM == "usb", ATTR {idVendor} == "1f53", MODE = "0666" #Samsung SUBSYSTEM == "usb", ATTR {idVendor} == "04e8", MODE = "0666" #Sharp SUBSYSTEM == "usb ", ATTR {idVendor} ==" 04dd ", MODE =" 0666 "#Sony Ericsson SUBSYSTEM ==" usb ", ATTR {idVendor} ==" 0fce ", MODE =" 0666 "#Toshiba SUBSYSTEM ==" usb " , ATTR {idVendor} == "0930", MODE = "0666" #ZTE SUBSYSTEM == "usb", ATTR {idVendor} == "19D2", MODE = "0666"

Save the file and close it, and then run the following command:

sudo chmod a + r /etc/udev/rules.d/51-android.rules

Install repo:

mkdir ~ / bin
PATH = ~ / bin: $ PATH
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo> ~ / bin / repo
chmod a + x ~ / bin / repo

Run repo:

mkdir WORKING_DIRECTORY
cd WORKING_DIRECTORY
repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.1_r1

For people who already have a ready repo:

cd WORKING_DIRECTORY
repo init -b android-4.1.1_r1
repo sync

If required, enter your name and email address.

Collect files:

repo sync

Compile:

source build / envsetup.sh

or

. build / envsetup.sh

Run:

lunch

Choose your device.

Now run the command:

make -j #

Where the pound (#) is the number of processor cores + 1, for example, I have a 2-core processor, then I write "make -j3".

How to add a device to the list

Find the devices you want to add on GitHub (for me, this is HTC Evo 3D-CDMA). Now go to the folder where you are going to clone the device tree:

cd WORKING_DIRECTORY / device
mkdir htc

Clone from the GitHub device tree from remote to local (make sure the folder will be named the same as the default name for your device, for example: Nexus One [passion], Nexus S [crespo] Motorola Droid [sholes], HTC Incredible [inc] etc.):

git clone git: //github.com/CyanogenMod/android_device_htc_shooter.git shooter

Now go to the folder:

cd shooter

Connect your phone to your computer and make sure that USB debugging is enabled and adb is working properly. Extract the device’s own files:

./extract-files.sh

Return to your home directory

cd ~ / WORKING_DIRECTORY

Prepare for compilation:

source build / envsetup.sh

or

. build / envsetup.sh

Get a list of your devices:

lunch

Select your device, then compile:

make -j #

Or to create a zip archive for the firmware:

make -j # otapackage

As a result, we get the compiled Jelly Bean for a specific device. Now you can try to run it on your device, see what works and what does not, then do the optimization of the new version of Android, make your AOSP firmware, etc.

Took it here !!

[nastor]

Tool forbatch conversion of indexed .png images to non-indexed.

The converter is designed for batch processing of files and allows you to:

1. Compress .png files, as well as convert other file formats to .png format; were checked .bmp, .jpg, .gif (for animated - only the first frame). .Png files that cannot be compressed are transferred to the output without changes. In this mode, all files from the input folder are processed.
   
2. To de-index indexed .png files - convert a color palette to 32bit while preserving the alpha channel:
   
   In this mode, only .png files are processed.
   

Version 2.3from 01/30/2013
PNG_convertor_v2.3.rar(35.72 KB)

Bugs, suggestions, suggestions and healthy criticism are accepted here:.

The basis was takenoptionproposedVSiemens, for which he is separatethank, and improved to allow batch processing, as well as file compression.

Previous versions:

Version 2.1

PNG_convertor_v2.1.rar(36.26 KB)

Version 1.0

Russian version:PNG_convert.rar(36.36 KB)
and with English (if problems with the encoding):PNG_convert_ENG.rar(36.14 KB)

Post has been editedDimar - 25.01.16, 21:04

Reason for editing: spoiler

[A.S._id]

HEIMDALL FLASHER SGSIII / SGNII SUPPORT !!!

I present the tool based on the famous Heimdall flasher - the version for the firmware in LINUX
Source code version HEIMDALL 1.4RC2 - developer siteBenjamin dobell

Fully supported devices

Samsung Galaxy SIII GT-I9300, I9305
Samsung Galaxy NoteII GT-N7100, N7105
Samsung Galaxy Note10.1-N8000

Instructions and menu items:

* Before use.

Make sure all tool files have executable permissions.
Place the firmware files in the "FLASH" folder or place the zip file with the firmware in the root of the tool

* Menu items.

0 - Configure tools - must be run once, it will compile and install components into the system

Flash menu

1 - Extract ROM - unpacks the firmware files in the "FLASH" folder and displays a report about the files (the zip file must be in the root of the tool)
2 - Download mod - reboots the device into firmware mode (USB debugging must be enabled)
3 - Heimdall detect device - show connection status
4 - STANDART - flash the standard firmware (the necessary files are shown in brackets)
5 - FULL - flash the full firmware with the bootloader (the necessary files are shown in brackets)
6 - MODEM - flash radio (required files are shown in brackets)
7 - KERNEL - flash the kernel (the necessary files are shown in brackets)
8 - RECOVERY - flash recovery (required files are shown in brackets)
9 - Download PIT file - extract PIT file from device

Root Menu (requires Root access)

10 - DOWNGRADE BOOTLOADER - downgrade the bootloader version (ROOT required and USB debugging must be enabled)
11 - EFS backup - save the image of the efs partition (the image will be saved in the tool root)
12 - EFS restore - restore the efs partition (the image must be in the root of the tool)
13 - Exit - exit

Description with pictures yethere- I will update later in Russian

heimdall_flasher_v.0.0.5.zip(16.66 MB)

v.0.0.4 - added item DOWNGRADE BOOTLOADER
v.0.0.5 - added Extract ROM
- added backup / restore efs option

Post has been editedA.S._id - 09.02.13, 13:00

[A.S._id]

BOOT & RECOVERY REPACKER

I present a tool for repacking boot.img and recovery.img in LINUX

Instructions and menu items:

* Before use.

Make sure all tool files have executable permissions.
Place the necessary files in the "source_img" folder
Run the boot_repacker script

* Menu items.

REPACK MENU
1 - Unpack boot.img - unpack boot.img
2 - Repack boot.img - repack boot.img
3 - Unpack recovery.img - unzip recovery.img
4 - Repack recovery.img - repack recovery.img
5 - Exit - exit

boot_repacker_v.001.zip(17.52 KB)


Post has been editedDimar - 27.01.16, 09:52

Reason for editing: Corrected typo

[A.S._id]

Tool

[DEV_TOOL] HTC ROM-EXTRACTOR

Tool for working with HTC firmware in LINUX

Before use, you must install libunshield version v.07 or higher.

$ sudo apt-get install automake
$ git clone https://github.com/kmdm/unshield.git
$ cd unshield /
$ git checkout -t origin / v18 ​​\ _wip
$ ./bootstrap
$ ./configure --prefix = / usr
$ make
$ sudo make install

HOW TO

1. Extract zip and put the firmware in the folder with the tool;
2. Run the rom-extractor file in the terminal and select the option:
MAIN MENU

u - UNRUU EXE TO ZIP - extract rom.zip from RUU.exe
d - DECRYPT MENU - go to DECRYPT MENU ROM.ZIP>OUTPUT.ZIP
r - REPACK MENU - go to REPACK MENU
e - ENCRYPT MENU - go to ENCRYPT MENU
c - CLEAN TOOL - clear tool
x - exit

>DECRYPT MENU ROM.ZIP>OUTPUT.ZIP

1 ... 24 - decoding rom.zip to output.zip (select the required device menu item)

>REPACK MENU

e - EXTRACT ZIP ROM - extract the contents of output.zip to the ROM folder
m - MOUNT SYSTEM (EXT4 ONLY) - mount system.img to the system folder (you can edit the mounted image, modify, delete, add files)
d - DESPARSE SYSTEM.IMG (EXT4 ONLY) - expanding the system.img image sparse into a regular ext4 image (compression is not available in all firmware and is recognized experimentally) and mounting the uncompressed system image into the system folder
s - MAKE SPARSE SYSTEM.IMG (EXT4 ONLY) - creating a sparse sistem.img image (before creating, you must enter the size of the XXXXM image (device-dependent) - for example, for HTC ONE X = 1280M)
n - UNMOUNT SYSTEM - unmount the system image
z - ADD SYSTEM.IMG>OUTPUT.ZIP - add system.img to the output.zip archive

>ENCRYPT MENU OUTPUT.ZIP>ROM.ZIP

1 ... 24 - encrypt rom.zip from output.zip, before encrypting, you must enter the parameters: keyindex chunks mainver, you will find the parameters in encrypt.log

screens

Source code on github by Kenny Millington kmdm

HTC_ROM-EXTRACTOR_v.0.0.5_x86.tar.gz(605.74 KB)


Post has been editedA.S._id - 14.04.13, 20:59

Reason for editing: v.0.0.5

[alexseyuh]

Unpacking and packaging firmware filessmd.
On UBUNTU!

Description

Create a daddy and throw into it what we need to unpack, for example:
SMD_PDA_I9001XXKQ6_CL980980_REV00_user_low_ship_EMMC.smd.md5
We remove the md5 resolution by simply renaming the file.
SMD_PDA_I9001XXKQ6_CL980980_REV00_user_low_ship_EMMC.smd
Download this archiver with 2 scriptsscr.zip(1.14 KB)

Unpack it and drop both files into the folder withSMD_PDA_I9001XXKQ6_CL980980_REV00_user_low_ship_EMMC.smd
Then in the terminal, go to this folder and make the scripts executable:

chmod + x extract.sh

chmod + x pack.sh

And we apply them:
Unpacking:

./extract.sh SMD_PDA_I9001XXKQ6_CL980980_REV00_user_low_ship_EMMC.smd

Packaging:

./pack.sh SMD_PDA_I9001XXKQ6_CL980980_REV00_user_low_ship_EMMC.smd

With MD5, I think you will figure it out for yourself))

Post has been editedDimar - 27.01.16, 10:08

Reason for editing: Spoiler

[fagci]

Porting tool by fagci

This script is used to port Android firmware.
OS: Windows XP +

Attention! It works only with devices with the same hardware filling!

The utility performs the following operations:

1. Compares versions of firmware archives;
   
2. Unpacks 2 archives (basic and portable);
   
3. Replaces libraries and other files, incl. and bootloader image with configuration files;
   
4. Replaces some configuration options for our device;
   
5. Packs the received firmware in the archive.
   

Recommendations for use:

• Detailed instructions for use are inside the archive with the utility;
  
• The base firmware is the firmware of the same version of Android as portable. The necessary files are taken from it;
  
• You need to flash the received archive without signature verification (in recovery: toggle signature check).
  

Ported personally and works

• AOKP (Android 4.1.2)
  [attachment = "2740615: htmlimage.png"] [attachment = "2740617: htmlimage (1) .png"]
  
• SlimBean (Android 4.1.2)
  
• Unofficial CM10 (Android 4.1.2)
  
• PAC Rom (Android 4.2.2)
  There is no screenshot yet, I did not make it in time =)
  

Bugs

Will be soon!

Info

A bug was found with unpacking the archive:
7zip does not support some types of zip archives, such as those created in Altap Salamander.
However, this archive was not at all from p500 =)

Version difference

0.9: 7zip with cygwin library
0.95: 7zip single file for win32
1.0b1: Replaces phone model and density with automatic
1.0RC1: checks for versions, fixed line breaks, logs to the log.txt and errorlog.txt files
2.0b1: added the ability to specify from which device to which port to produce, read the Readme.
2.0RC1: fixed bugs, fixed structure.

For geeks

The script replaces the necessary files in the portable rum and replaces the model number of the phone, as well as the screen resolution.
In the future, it is planned to make a complete machine using not one-liner porting scripts.
Source codes can be used for your own purposes as you please, while preserving information about me

Acknowledgments

MaximCSKA: for testing and active participation in the elimination of errors, as well as for support.

PortingTool_v0.9_21032013.zip(1013.3 KB)
PortingTools_v0.95_21032013.zip(303.19 KB)
PortingTools_v1.0RC1_25032013.zip(908.7 KB)
PortingTools_v2.0b1_14022014.zip(312.08 KB)
PortingTools_v2.0RC1_14022014.zip(306.29 KB)

If you find errors, as well as if you have any wishes, write to the post office, which is indicated in the ReadME, or here inQMS

Post has been editedfagci - 14.02.14, 12:56

Reason for editing: New version