Creating custom firmware | Instructions for dsixda's Android Kitchen



Rep: (267)
Creating custom firmware for dsixda's Android Kitchen

Windows / Linux / Mac OS X

This program is not a full-fledged tool to work with firmware. Create custom bikes usually starts from scratch requires a lot of time and patience. Author of this program just let the user to quickly get things done using an existing database, and the guide will help you to quickly learn how to work with the program. Material provided in this post is unofficial. In the case of the apparatus of death: the creator, author of the post and the administration do not bear responsibility website. All the action at your own risk.
List of devices supported by the kitchen:
  • Acer liquid
  • Dell Streak 7
  • 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 Eri
  • HTC Evo 3D
  • HTC Evo 4G
  • HTC Evo View 4G (not tested)
  • HTC Evo Shift 4G
  • HTC Flyer (not tested)
  • HTC HD2 -Details in this thread
  • 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 (not tested)
  • Huawei Ideos X6 -Details in this thread
  • Huawei U8100 / U8110 / U8120 / U8150 / U8160 / U8180 / U8650
  • Huawei U8220 / T-Mobile Pulse
  • Huawei U8500
  • Huawei u8850
  • Lg ally
  • LG GT540 Optimus
  • LG Optimus 2X (P990)
  • LG Optimus Black (not confirmed)
  • LG Optimus G2X (P999)
  • LG P500 -Details in this thread
  • LG Shine Plu
  • LG Vortex
  • Micromax A60
  • Motorola Atrix (not confirmed)
  • Motorola CLIQ / CLIQ XT
  • Motorola droid
  • Motorola Droid Bionic -Details in this thread
  • Motorola Milestone (not confirmed) - You may need to remove boot.img after building
  • Samsung Galaxy Nexus (not tested, only versions of 'maguro' and 'toro')
  • Samsung Galaxy S (GT-I9000 and all its variants) -Details in this thread
  • Samsung Galaxy S Plus (GT-I9001) -Details in this thread
  • Samsung GT-S7500 Galaxy Ace Plus -Details in this thread
  • Samsung Galaxy S2 (GT-I9100 and Exynos CPU variants) -Details in this thread
  • Samsung Galaxy S2 LTE (AT & T Skyrocket, T-Mobile SGH-T989) -Details in this thread
  • Samsung Galaxy W (GT-I8150, not tested)
  • Samsung Nexus S / Nexus S 4G
  • Samsung Galaxy Gio -Details in this thread
  • Sony Xperia X10 / X10 Mini / X10 Mini Pro -Details in this thread
  • Sony's entire line of phones '11, there may be gaps in the updater-script
  • ZTE Blade / Orange San Francisco


Installation:
Windows:
You can install the kitchen in Windows in several ways:
  • Install Cygwin (Unix-environment for Windows):
    1. Download and installJava jdkfor Windows 32-bit (ATTENTION: Do not install Cygwin in front of the JDK).
    2. Downloadcygwin, unpack and follow the instructions in "Installing .txt" (thank you for Cygwin userJlocb).
    Note: the kitchen only works with the version of Cygwin attached here.
  • Installing Linux through a virtual machine:
    1. Download and installVirtual box(or any other virtual machine).
    2. Install Linux into a virtual machine.
    3. Read more about preparing Linux in the section “Installation ->Linux ".
    Note: When using this method, the kitchen may run slower.

Linux (I recommend Ubuntu):
1. Install the "Ubuntu Application Center" by typing in the terminal "sudo apt-get install software center"(in recent versions, already built into the distribution).
2. For 64-bit systems we type in the terminal "sudo apt-get install ia32-libs".
3. Start the application center (you can use the command "software-center") and in the search box enter" Java ", among the results found, look for" OpenJDK Java 6 Runtime "(or something like that) and install it.
4. Those who put through a virtual machine, you still need to share folders between Windows and Linux.

Mac OS X:
1. Create an image .dmg disk for the kitchen, otherwise the finished disk will not boot.
2. Install the Sun Java JDK.
3. Install GNU versions of sed, Mac OS X version (FreeBSD) in sed is not compatible with kitchen.
4. Install GCC (compiler) if you do not have it by default. Just enter "GCC" for verification, it is included in the XcodeTools package on the installation DVD.
5. Install wget.
Note: I do not know all the subtleties of working on Mac OS X, so this method is experimental.
More accurate instructionsCreating custom firmware (Post # 21050611)

Run:
1. Before launch, we need to unzip the folder from the archive with the kitchen along the path "c: / cygwin / home / John /" for Cygwin or along the path "file system / home / John /" for Linux, where John is the user name, and rename in the "kitchen".
2. You need to run through Cygwin or the terminal commands "cd kitchen", then"./menu"(if you are running Windows 7, then cygwin needs to be run as an administrator).
Note 1: if you change the way, then the first team will change to "cd ../kitchen"where instead of points there will be a path to the kitchen.
For example: I have a kitchen "file system / home / kelt525 / papka / kitchen", then the command will look like "cd / home / kelt525 / papka / kitchen".
Note 2:for the kitchen to work correctly, the user name must be in English, i.e. For Cygwin create a separate profile with the English name.

ROM import:
To import a ROM into the kitchen, you need to drop it into the folder "original_update folder".
The kitchen supports several options:
1. ".zip" file firmware.
2. "system.img", "boot.img" and the rest.
3. ".exe" file firmware.
Note: ROM is taken from stock and custom firmware, based on what system to take as a basis.

Work with the kitchen:
After we imported the ROM, we start working with Kunya, launch it, as I described it in the “Launch” section under number two.
If you have done everything correctly before this, a menu should appear:
===================================================================
Android Kitchen - by dsixda (xda-developers.com)
===================================================================

1. Set up working folder from ROM
2. Add root permissions
3. Add BusyBox
4. Disable boot screen sounds
5. Add wireless tethering
6. Zipalign all * .apk files to optimize RAM usage
7. Change wipe status of ROM
8. Change name of ROM
9. Check update-script for errors
10. Show working folder information

0. Advanced Options
99. Build ROM from working folder

00. About / Update kitchen
0. Exit

Where entering “0 - ​​ADVANCED OPTIONS” we see:
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add / data / app functionality
14 - Add Nano text editor + sysro / sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Tools for boot image (unpack / re-pack / etc.)
21 - Unpack data.img
22 - Sign APK or ZIP file (s)
23 - Convert update-script or updater-script
24 - Miscellaneous optins / Plugin scripts

0 - Back to main menu

Here is the translation of all functions:
1. Create a working folder from ROM
2. Add root rights
3. Add BusyBox
4. Turn off the screen loading sounds
5. Add the function of creating a Wi-Fi router from the phone
6. Zipalign all ".apk" files, in other words, compress
7. Change the wipe status of the ROM
8. Change the name of the ROM version
9. Check update-scrypt for errors
10. View working folder information

0. Additional Functions
99. Collect ROM from working folder

00. About the kitchen / upgrade
0. Exit

11 - Make a DeOdex System
12 - Add task killer to increase speed (only for stock firmware)
13 - Add functional folder "/ data / app"
14 - Add text editor Nano + sysro / sysrw
15 - Add Bash (command line)
16 - Add Apps2SD
17 - Add script support "/etc/init.d" (busybox is required)
18 - Add loading animation
19 - Tools for porting (experimentally)
20 - Kernel tools (unpacking / repacking / etc.)
21 - Unpacking data.img
22 - Sign the ".apk" or ".zip" files
23 - Convert update script to updater script
24 - Running Scripts / Plugins

0 - Return to the main menu

Example of work in the kitchen:
1. Import ROM
2. Start the kitchen
3. Create a working folder from ROM
4. Add root and BusyBox
5. Making DeOdex
6. Remove / add / modify what you need
7. We collect ROM from the working folder
Note: after the build, we get a ".zip" file ready for firmware through the recovery in the "OUTPUT_ZIP" folder

Kernel replacement:
Two things you need to know:
Kernel is a file inside boot.img, but boot.img is not a kernel, it mainly contains kernel and initialization files at boot time.
Instructions for replacing the kernel on newer versions of the "kitchen"fromgeolog56
There are three options:
  • If the kernel that you want to use is closed in the ".img" file (ie, "boot.img"), then do the following:
    1. Rename it to "boot.img".
    2. Replace with the current "boot.img" that is in your kitchen.
    3. We also replace the modules (if any).
  • If you want to “transplant” a kernel from one “boot.img” into your existing “boot.img”:
    1. In "Advanced options", select the "unpack boot.img" option from "any folder".
    2. Place the new boot.img inside this folder, that is, you can extract the kernel (zImage).
    3. Then select the option “unpack a boot.img from your working folder”. This will create the "BOOT-EXTRACTED" folder.
    4. Copy zImage (from the new boot.img) to the "BOOT-EXTRACTED" folder.
    5. Select the "Re-pack the boot.img" option.
    6. Your "boot.img" in the working folder received a new kernel.
    7. Use the previous description if you also need to copy the modular files, if they are included in the “package”.
  • If the new kernel itself is not in "boot.img" (i.e., zImage or boot.img kernel), further description of how to add to the working folder in the kitchen:
    1. In the "Advanced options" menu, select the "unpack the boot.img" option from the working folder.
    2. Copy the kernel file to the created folder "BOOT-EXTRACTED" and rename the file to "zImage".
    3. Select the "re-pack the boot.img" option.
    4. Your working folder "boot.img" has become a new kernel.
    5. If the kernel comes with other files, such as “* .ko files for / system folder”, then copy them to the appropriate locations.

Add your own programs:
Again, there are several options for how to do this:
  • We throw programs in the "working folder / system / app" with a replacement if necessary.
  • Install them in data:
    1. In "Advanced options", select "Add / data / app functionality", then the folder "working folder / data / app" is created.
    2. We throw programs into it.

Note: Not all programs are well sewn into the firmware, an example of this is Dr. Web that does not start.

Features / additional features when working with ROM:

Download the latest version of the kitchen
Kitchen author's theme
Russian version of the kitchenfromloginivan
Russian version of the kitchenfromRostislav89
dsixda's Android Kitchen Without Cygwin Installation
Download Cygwin

Video instructions for installing and configuring Android KitchenfromSawamen

There is no curator in the subject. If there is a user in the subject who wants to become a Curator and the correspondingRequirements for candidates, he can apply in the topicI want to be curator(after having studied the topic header and all materials for curators).
Prior to the appointment of the curator, on filling caps, please contactmoderatorssection through a buttonPictureunder the messages to which you want to add links.


Post has been editedvaalf - 04.09.18, 19:26
Reason for editing: Editing header



Rep: (869)
do66epman @ 4.11.2013, 10:18*
alting
thanks for the advice. I understand, easier to call a person incompetent than to explain something

And then the sad sack? To drive a car, is at least, it is necessary to understand the pedals? ls -a conclusion show. You undertake to collect firmware without having a clue about azah kitchen work.



Rep: (489)
alting
The fact that the circumstances forced to use this method, I mean the kitchen
PC does not see the device (hardware problem), but I need rutirovat firmware
You are absolutely right - have not had to deal with the firmware build, but what to do?

Posted 04/11/2013, 9:55:

I just wanted to learn what the kitchen team to run on windows



Rep: (282)
Dimar, Read cap and dizanformiruyte person

do66epman let's qms, I work with cygwin and linux mint, I know - explain!

Post has been editedTimofey777 - 04.11.13, 10:59



Rep: (57)
I have a kitchen parses the latest firmware off, open the window and then Ex2Tool tupik.V nevaozmozhno window edit content fayla.Pri attempt rutovat, deodeksirovat firmware displays a message that the file is not present build.drop.Pri attempt to collect it as it is, in the Output file folder size only 18 mB of the 500 mB.
What's wrong? ((



Rep: (233)
good evening!
there updater script supersu1.65 for Ruta across cwm. who can see what makes this script? in fact need a guide for the implementation of this script hands (ie, for example take X file from the archive and move into a new folder Y in the phone).
my knowledge of the teams is not enough to understand.
But in general, here what problem: you rutirovat firmware 4.3. supersu1.65 c it consults through SVM. how to do it with the help of the kitchen. earlier versions of the superpowers are not working = (
and may already have the same file for rutirovaniya in already adapted form?
Thanks in advance and I plus =)

Attached files

Attached fileUPDATE-SuperSU-v1.65.zip(1007.73 KB)



Rep: (2964)
dronblack
That's what he does
#! / sbin / sh

OUTFD = $ 2
ZIP = $ 3

ui_print () {
echo -n -e "ui_print $ 1 \ n">/ proc / self / fd / $ OUTFD
echo -n -e "ui_print \ n">/ proc / self / fd / $ OUTFD
}

set_perm () {
chown $ 1. $ 2 $ 4
chown $ 1: $ 2 $ 4
chmod $ 3 $ 4
}

ch_con () {
/ System / bin / toolbox chcon u: object_r: system_file: s0 $ 1
chcon u: object_r: system_file: s0 $ 1
}

ui_print "*********************"
ui_print "SuperSU installer ZIP"
ui_print "*********************"

ui_print "- Mounting / system, / data and rootfs"
mount / system
mount / data
mount -o rw, remount / system / system
mount -o rw, remount / /

ABI = $ (cat /default.prop | grep ro.product.cpu.abi = | dd bs = 19 skip = 1 count = 3)
ABI2 = $ (cat /default.prop | grep ro.product.cpu.abi2 = | dd bs = 20 skip = 1 count = 3)

ARCH = arm
if [ "$ ABI" = "x86"]; then ARCH = x86; fi;
if [ "$ ABI2" = "x86"]; then ARCH = x86; fi;

ui_print "- Extracting files"
cd / tmp
mkdir supersu
cd supersu
unzip -o "$ ZIP"

BIN = / tmp / supersu / $ ARCH
COM = / tmp / supersu / common

ui_print "- Disabling OTA survival"
chmod 0755 / tmp / supersu / $ ARCH / chattr
$ BIN / chattr -i / system / xbin / su
$ BIN / chattr -i /system/bin/.ext/.su
$ BIN / chattr -i / system / xbin / daemonsu
$ BIN / chattr -i /system/etc/install-recovery.sh

ui_print "- Removing old files"
rm -f / system / bin / su
rm -f / system / xbin / su
rm -f / system / xbin / daemonsu
rm -f /system/bin/.ext/.su
rm -f /system/etc/install-recovery.sh
rm -f /system/etc/init.d/99SuperSUDaemon
rm -f /system/etc/.has_su_daemon
rm -f /system/etc/.installed_su_daemon
rm -f /system/app/Superuser.apk
rm -f /system/app/Superuser.odex
rm -f /system/app/SuperUser.apk
rm -f /system/app/SuperUser.odex
rm -f /system/app/superuser.apk
rm -f /system/app/superuser.odex
rm -f /system/app/Supersu.apk
rm -f /system/app/Supersu.odex
rm -f /system/app/SuperSU.apk
rm -f /system/app/SuperSU.odex
rm -f /system/app/supersu.apk
rm -f /system/app/supersu.odex
rm -f /data/dalvik-cache/*com.noshufou.android.su*
rm -f /data/dalvik-cache/*com.koushikdutta.superuser*
rm -f /data/dalvik-cache/*Superuser.apk*
rm -f /data/dalvik-cache/*SuperUser.apk*
rm -f /data/dalvik-cache/*superuser.apk*
rm -f /data/dalvik-cache/*eu.chainfire.supersu*
rm -f /data/dalvik-cache/*Supersu.apk*
rm -f /data/dalvik-cache/*SuperSU.apk*
rm -f /data/dalvik-cache/*supersu.apk*
rm -f /data/app/com.noshufou.android.su-*
rm -f /data/app/com.koushikdutta.superuser-*
rm -f /data/app/eu.chainfire.supersu-*

ui_print "- Creating space"
cp /system/app/Maps.apk /Maps.apk
cp /system/app/GMS_Maps.apk /GMS_Maps.apk
cp /system/app/YouTube.apk /YouTube.apk
rm /system/app/Maps.apk
rm /system/app/GMS_Maps.apk
rm /system/app/YouTube.apk

ui_print "- Placing files"
mkdir /system/bin/.ext
cp $ BIN / su / system / xbin / daemonsu
cp $ BIN / su / system / xbin / su
cp $ BIN / su /system/bin/.ext/.su
cp $ COM / Superuser.apk /system/app/Superuser.apk
cp $ COM / install-recovery.sh /system/etc/install-recovery.sh
cp $ COM / 99SuperSUDaemon /system/etc/init.d/99SuperSUDaemon
echo 1>/system/etc/.has_su_daemon
echo 1>/system/etc/.installed_su_daemon

ui_print "- Restoring files"
cp /Maps.apk /system/app/Maps.apk
cp /GMS_Maps.apk /system/app/GMS_Maps.apk
cp /YouTube.apk /system/app/YouTube.apk
rm /Maps.apk
rm /GMS_Maps.apk
rm /YouTube.apk

ui_print "- Setting permissions"
set_perm 0 0 0777 /system/bin/.ext
set_perm 0 0 06755 /system/bin/.ext/.su
set_perm 0 0 06755 / system / xbin / su
set_perm 0 0 06755 / system / xbin / daemonsu
set_perm 0 0 0755 /system/etc/install-recovery.sh
set_perm 0 0 0755 /system/etc/init.d/99SuperSUDaemon
set_perm 0 0 0644 /system/etc/.has_su_daemon
set_perm 0 0 0644 /system/etc/.installed_su_daemon
set_perm 0 0 0644 /system/app/Superuser.apk
set_perm 0 0 0644 /system/app/Maps.apk
set_perm 0 0 0644 /system/app/GMS_Maps.apk
set_perm 0 0 0644 /system/app/YouTube.apk

ch_con /system/bin/.ext/.su
ch_con / system / xbin / su
ch_con / system / xbin / daemonsu
ch_con /system/etc/install-recovery.sh
ch_con /system/etc/init.d/99SuperSUDaemon
ch_con /system/etc/.has_su_daemon
ch_con /system/etc/.installed_su_daemon
ch_con /system/app/Superuser.apk
ch_con /system/app/Maps.apk
ch_con /system/app/GMS_Maps.apk
ch_con /system/app/YouTube.apk

ui_print "- Unmounting / system and / data"
umount / system
umount / data

ui_print "- Done!"
exit 0


And read it
Development for GT-I9500 Galaxy S4 (firmware, kernel, root access, etc.) (Post # 26327418)

Development for GT-I9500 Galaxy S4 (firmware, kernel, root access, etc.) (Post # 26327290)

Post has been editedalexseyuh - 05.11.13, 00:24



Rep: (2964)
dronblack
Here are the files, how to do in the post above see 2 links, but there is a way to work with bypassing the kitchen.
Attached fileroot_files.zip(1.57 MB)


Posted on 11/05/2013, 00:30:

Here's how to work with images
Disassembly and subsequent assembly sewn images for SAMSUNG smartphones (under the LINUX) (Post # 26248282)
It seems to have done rutovanaya s3, download, install and see))

Post has been editedalexseyuh - 05.11.13, 00:36



Rep: (233)
Adding Root rights on 4.3 samsung galaxy s3 (sgs3, III), when creating the firmware in the kitchen xdixda.

Maybe it will be useful to someone. The question was solved in the following way:
in the kitchen xdixda - put Ruth, put busybox, add support init.d
further on this description (many thanks to the SW.iron1971 ):
If you inserted into the firmware version of Android 4.2 to the arm of the su file folders in folders xbin firmware and from the common file folder Superuser.apk firmware folder in the app, and the script does not need to add anything.
Another story with Android version 4.3 and higher.
From arm su file folder in xbin and there it is necessary to add a script daemonsu
(Script daemonsu, I picked up from an external source (ATP SW. alexseyuh ) Since update_superSU_1.65 in this file is not present).
From the common file folder in the app Superuser.apk firmware folder, file install-recovery.sh in etc and 99SuperSUDaemon file folder in the folder in the init.d etc.
The installation script updater-script needed after
set_perm (0, 0, 06755, "/ system / xbin / su");
copy the following commands.
set_perm (0, 0, 06 755, "/ system / xbin / daemonsu");
set_perm (0, 0, 0755, "/system/etc/install-recovery.sh");
(In the kitchen first, I packed firmware in Mode 1 -. Apdater-script, zipalign, sign And when the firmware is ready, in the script copied these lines).

Post has been editeddronblack - 05.11.13, 17:21



Rep: (242)
Hello! Ported firmware 4.2.2 on the Fly IQ440. Already I spread their version, but recently ran into a problem. When removing the video lags behind the sound for a few seconds. Camera and gallery changed on a computer that is also behind the sound, and even when the plug in headphones to the phone the sound only works in one dynamic, and in the second kakoeto strange poskripovanie. Thought headphones broke took another same. What is the problem? Can Lieb what may be necessary to replace? Or file? Prompt + with me at all.



Rep: (2964)
Andrey567,
There are 2 options, either to sort and search for libs that are responsible for the sound.
Or most likely it is necessary to alter the kernel, a new driver insert, may be wrong.



Rep: (15)
Hello.
There is a firmware 4.1 and 4.2
The firmware 4.1 in the system \ app folder are apk files, including launcher and a flashlight
If you put the apk from 4.1 in the same folder 4.2 - does not work:
- if you remove the launcher from 4.2 and put your - smart load without launcher. If you add the launcher to the existing - sees the two and offers a choice.
- a flashlight just does not work (even no shortcut). If it APK throw on the memory card and try to establish - is not put. But from the firmware 4.1 works fine

Explain (or allow read), how to use your APK, sewn into the system \ app?
thank

Post has been editedstally - 07.11.13, 10:41



Rep: (233)
stally @ 07.11.2013, 11:06*
If you put the apk from 4.1 in the same folder 4.2 - does not work:

because apart from the AIC should be more files belonging to a flashlight for example in the Lib folder.
in 4.1.2 is why it worked that the files were more than one, but you transfer only APC. poprobuytenayti lib about the name flashlight. not the fact that will work, because for him to go, or a widget or shortcut. but rather find a program on the market, covering their full
stally @ 07.11.2013, 11:06*
if you remove the launcher from 4.2 and put your

stock launcher can not be deleted. better let it be two. in different phones in different ways: but chances are you can put one of them defaults



Rep: (282)
dronblack @ 7.11.2013, 11:50*
stock launcher can not be deleted.

Oo as then I year without the stock launcher lived in a smart old and live in the new



Rep: (233)
Timofey777 @ 07.11.2013, 11:58*
Oo as then I year without the stock launcher lived in a smart old and live in the new

you will not be equal to itself, and the newcomer, so I saaavsem not sure that he will bring updater-script to the CWM, to fly off in the field if such launcher, he could recover. And depending on the device. IMHO all of course, but nafig such risks, especially in the newly launched razberatelstve already =)



Rep: (748)
dronblack @ 07.11.2013, 11:50*
stock launcher can not be deleted. better let it be two. in different phones in different ways: but chances are you can put one of them defaults

not always, sometimes removal of the built-in launcher painless, and sometimes leads to bad consequences ...



Rep: (15)
dronblack @ 07.11.2013, 11:50*
stock launcher can not be deleted. better let it be two. in different phones in different ways: but chances are you can put one of them defaults

The self-made firmware builds people somehow manages to insert any Apexy :)
And I want to insert the Next, it just does not work alone, the infection .. :)
Why Apex works and Next - no? Again, probably not enough heap of files ..

dronblack @ 07.11.2013, 12:06*
to fly off into the field if such launcher, he could recover

Well, I have a couple of months, probably :) I pick which that begin to think quietly. Yesterday updater-script itself copied, because he did not want to thrust my apps on the folder.
Without launcher has already been run a few times, rules, flooded again in TWRP.
In principle, everything is easy, but it is not clear why all the works, and I have - not :)

Post has been editedstally - 07.11.13, 12:10



Rep: (37)
Who does what but help
There are flashing off in app format
As it perepatroshit in zip



Rep: (1726)
stally @ 7.11.2013, 12:03*
The self-made firmware builds people somehow manages to insert any Apexy :)
And I want to insert the Next, it just does not work alone, the infection .. :)
Why Apex works and Next - no?

Because he needed a library. Open apk Next-and Winrar-th and the folder / lib / armeabi / cast your all files in the firmware in the / system / lib /



Rep: (4)
Hello.
I am trying to make their firmware for Widfire S on the basis of the drain 2.13.401.2. I use mostly Android Kitchen. As a source of inspiration and use firmware HenseMod7 search. I faced with some difficulties.
How are added / replaced by applications in the firmware? Specifically, after replacing HTC_IME (keyboard, I wanted to take HTC_IME mod) at system start immediately after it falls. After replacing framework_res.apk generally goes into eternal boot.
Also sistemune added some applications that I threw in the / data / app. Specifically established CpuSpy, NoFrillCpu and TerminalEmulator. For some reason it does not appear RootExplorer.
Tell me where I'm wrong, and what I'm doing wrong. And, in fact, how do the right thing, or where naguglit answers.



Rep: (233)
uzer2008 @ 09.11.2013, 18:35*
Tell me where I'm wrong, and what I'm doing wrong.


I do not know the specifics of your system, but I can assume:
1) it is not necessary to change the whole freyvork-res, the right of individual files, because for each firmware this APK unique.
2) files are commonly thrown me not to date / HW and systems / ann can in this kasyak.
3) Claudia may fall due to lack of Libov in the lib folder.

Again I repeat, answered without regard for the specific devices.


Full version    

Help     rules

Time is now: 10/02/20, 17:46