Jiayu G4S - FAQ | Jiayu G4S Advanced, JY-G4S, Jiayu G4 Octa-Core



Rep: (3321)
Jiayu G4S - FAQ
Picture Jiayu G4S, JY-G4S, Jiayu G4 Octa-Core
Description | Discussion пїЅ | FAQ - To help the newcomer | Firmware 4.2.2 пїЅ | Firmware 4.4.x KitKat пїЅ | ORR firmware пїЅ | Lewa пїЅ | MIUI пїЅ | GPS talk on Jiayu G4S пїЅ | Purchase пїЅ | Accessories пїЅ | JIAYU G4S / L Club пїЅ | Discussion of problems with self-loading on Jiayu G4S пїЅ

Post has been editedmainbord - 23.01.17, 11:13



Rep: (3321)
NOTE!
For most of the cases described below, it is necessary to set the following parameters in the phone settings:
1. Settings- Developer Parameters - tick the checkbox "USB Debugging"
2. Settings- Protection - check the box “Unknown sources”.
First of all, as soon as the phone was received, it is strongly recommended to make Backup IMEI and Backup OS. This will allow you to restore the working system, if for some reason after your actions it has come into disrepair. Protect yourself!

Groundwork used

In firmware basedNOTon the stock methods may be different.
This is especially true for firmware LEWA, MIUI, ColorOS, BaiduOS.
In each of the topics / posts with firmware there is information that is also worth reading!
[/ center]
  1. Interpretation of the name and models of firmware
  2. Glossary
  3. Backup IMEI and everything related to the NVRAM partition (IMEI / MAC / Wi-Fi / BT)

  4. Backup (Backup) and System Restore (Restore)

  5. Phone firmware and everything connected with it
    ....
  6. Install ROOT rights
  7. EVERYTHING ABOUT SYSTEM APPLICATIONS JiaYu G4S (L) & G5S (L)
  8. Solving other shortcomings and errors
  9. All about sound
  10. All about GPS
  11. All about the battery


Post has been editedjemi - 05.04.15, 00:44



Rep: (3321)
Interpretation of the name and models of firmware

CATEGORICALLY IT IS NOT RECOMMENDED TO PUSH THE PHONE BY FIRMWARE NOT CONFORMING TO IT MODELS !!!
G4S - phone model
G4S - Advanced (2/16 GB)
G4SL - Standard (1/4 GB)

G4SW - Worlwide (2 / 16GB)

G5S - phone model
G5S - Advanced (2/16 GB)
G5SL - Standard (1/4 GB)

2014XXXX-firmware release date
Yyyyy - firmware release time

FT - FlashTool version
CWM - version for mod.rekavery
Recovery - version for updating streaming firmware from standard recovery (using update.zip)

Post has been editedjemi - 22.03.15, 21:17



Rep: (3321)
Glossary
It is interesting to read for a start: [FAQ] The basic concepts of the Android OS.
"Padonkaffsky", or "Albany" Yezig or Yazyk Padonkaff
- the style of using the Russian language with a phonetically almost true, but on purpose of the XXI century, which has spread in Runet at the beginning of the 21st century, the frequent use of non -normative vocabulary and certain stamps that are characteristic of slangs (although habits are so strong that “Padonki is so strong ", Without noticing it, they correctly include the words - a hare, a hare ... - And as a result, phonetic fidelity is lost in many cases). Most often used when writing comments on the texts in blogs, chats and web forums. Slang gave rise to many stereotypical expressions and Internet memes, in particular, it is associated with the “Pereved” meme. Wikipedia material. The official language of the forum -Russian.
Core
Core- is part of the operating system, and it is not only Android, but also other operating systems: Windows, iOS, MacOS and others. But we will be interested in the Android kernel, and what I will try to explain at the level of novice users.
The Android kernel is the most important part of the operating system, which is responsible for the interaction between the hardware and software part of the device. The kernel consists of a set of drivers for all the hardware present in the device, and a subsystem for managing memory, network, security, and other basic functions of the operating system.
The kernel manages absolutely all the equipment: Wi-Fi, Bluetooth, GPS, memory and other devices. There is no exception and processor. The kernel can control its frequency and power supply.
The stock core is optimized by the manufacturer for a particular device, but it usually blocks such important core functions as, for example, CPU frequency control. And if you need to overclock the processor of your device, you will need to change the kernel to a custom one, in which the frequency control function of the processor is unlocked.
Here is a sample list of features that custom kernels give us:
  • Changing the processor frequency over a wide range;
  • Overclocking graphics subsystem (GPU);
  • Reducing the frequency and voltage of the processor, which allows for a longer battery life;
  • More recent and high-quality drivers, such as accelerating the work of the GPS or adding new features;
  • Ample opportunities for setting and configuration of sound and color screen;
  • Support for alternative file systems (XFS, ReiserFS, and others).

Info taken from 4Tablet-PC.
Firmware (English Firmware, fw)
Firmwarecalled the contents of the non-volatile memory of a computer or any digital computing device - a calculator, cell phone, GPS-navigator, etc., which contains its firmware.
The word “firmware” is sometimes called the ROM image, intended to be written into the memory of the corresponding device in order to update its firmware, as well as the actual process of writing this image to the non-volatile memory of the device.
The memory is flashed when the device is manufactured in various ways - for example, by installing a memory chip with recorded contents (“stitched”).
Most devices allow the replacement of the contents of memory ("flashing"). Methods of "flashing" can be very different - from the physical replacement of the memory chip to transfer data over wireless channels.
Smartphones- This is essentially high -tech computers with their own operating system and allow you to expand their functionality by installing additional and third -party software. So, the more complicated the smartphones become, the more potential places for the occurrence of the functioning errors of the operating system serving the smartphone and its hardware filling are especially in the new model of a particular device. The new version of the firmware for the smartphone, as a rule, corrects the error discovered at the time of its release, and in addition, optimizes the work of existing software and hardware parts of the smartphone (for example, the camera begins to remove better, leaks of RAM disappear, sometimes additional functionality appears, etc. P.). Therefore, when the developer produces a new firmware, it is almost always worth updating it in his device.
What is off. ROM for flashlight?
preloader (~ 0.25 Mb.)- preloader. It connects the phone with FlashTool in "USB mode" for firmware, and also ensures the launch of the device. Presumably loads uboot into RAM and transfers control to it. It is not always recommended to (re) flash.
nvram (~ 5.0 MB.)- stores calibration of hardware, IMEI, BT and WIFI MAC addresses and more. Mount point / data / nvram.
seccnfg (~ 0,125Mb.)- unknown thing, usually contains only the emptiness of "FF FF ...".
uboot (~ 0 MB.)- lk.bin, operating system loader + drivers for initialization of the main equipment (display, processor, GPIO).
boot (~ 10.0 MB.)- kernel and operating system drivers (cameras, sensors, sensors). Mount Point.
recovery (~ 10.0 MB.)- mini-system (system in the kernel) whose function is only to backup / restore system applications, reset to factory settings. In advanced recovery, the functionality is of course much richer.
secstatic (~ 1.156 MB.)- sec_ro, what is needed is not clear, nothing happens when erasing on Android 2.2.1 and 2.3.5. On Android 2.2.2 (mostly at Fly-ying), this section takes up a good piece of ROM and it has Google services. Mount point / system / secro. File system yaffs2.
misc (~ 0 Mb.)- unknown thing, usually contains only the emptiness of "FF FF ...".
logo (~ 8.0 Mb.)- The first picture when turned on, picture charging. At 95% contains only the emptiness of "FF FF ...".
expdb (~ 0.65 MB.)- unknown thing, usually contains only the emptiness of "FF FF ...".
system (~ 889 MB.)- Android system section. Here everything that relates to the functioning of the device, from the "muzzle" to the supported functions of the operating system. Everything that changes here is not subject to restoration by factory reset. Mount point / system. File system yaffs2.
cache (~ 125.0 MB.)- section for the location of temporary files. Typically used by applications (Market, ROM Manager ...). If the section is lost, the system operation will not suffer. Incorrect content may cause a hang when loading the device. Fully erased at factory reset. Mount point / cache. File system yaffs2.
userdata (~ 4030 MB.)- data, this is the section for installing programs of calendars, telephones, profiles, settings of various programs and systems. With the loss of the contents of the section usually * the functioning of the system does not suffer. Incorrect content may cause a hang when loading the device. Fully erased at factory reset. Mount point / data. File system yaffs2.

If you have problems with your phone, do not rush to flash it.
First, do a full reset from recovery.
How to do this depends on the version of your recovery.
If you have been tinkering with RootExplorer or deleting system programs, then we flash only the system and do a reset via recovery. There is no need to sew anything else. From this "more factory phone will not." From inept actions he can become more brick.
99% of the problems are reduced to the fact that users install a third-party launcher, and then delete the system launcher (as unnecessary). As a result, after a reset:
  • "Aw, after the reset, black screen and everything! Nothing works."
  • "Guard, after reset, I click on the icon of the robot (Wisard or Installation Wizard), but nothing happens!"
Scatter
The file in which the phone memory map is stored
Scatter content from firmware 22.04
############################################################################################################
#
# General Setting
#
############################################################################################################
- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6592
project: vanzo92_wet_jb9
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000
############################################################################################################
#
# Layout Setting
#
############################################################################################################
- partition_index: SYS0
partition_name: PRELOADER
file_name: preloader_vanzo92_wet_jb9.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
region: EMMC_BOOT_1
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
reserve: 0x00

- partition_index: SYS1
partition_name: MBR
file_name: MBR
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

- partition_index: SYS2
partition_name: EBR1
file_name: EBR1
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x80000
physical_start_addr: 0x80000
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

- partition_index: SYS3
partition_name: PRO_INFO
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x100000
physical_start_addr: 0x100000
partition_size: 0x300000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00

- partition_index: SYS4
partition_name: NVRAM
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x400000
physical_start_addr: 0x400000
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BINREGION
reserve: 0x00

- partition_index: SYS5
partition_name: PROTECT_F
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x900000
physical_start_addr: 0x900000
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00

- partition_index: SYS6
partition_name: PROTECT_S
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x1300000
physical_start_addr: 0x1300000
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00

- partition_index: SYS7
partition_name: SECCFG
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x1d00000
physical_start_addr: 0x1d00000
partition_size: 0x40000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00

- partition_index: SYS8
partition_name: UBOOT
file_name: lk.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1d40000
physical_start_addr: 0x1d40000
partition_size: 0x60000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

- partition_index: SYS9
partition_name: BOOTIMG
file_name: boot.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1da0000
physical_start_addr: 0x1da0000
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

- partition_index: SYS10
partition_name: RECOVERY
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x27a0000
physical_start_addr: 0x27a0000
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

- partition_index: SYS11
partition_name: SEC_RO
file_name: secro.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x31a0000
physical_start_addr: 0x31a0000
partition_size: 0x600000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

- partition_index: SYS12
partition_name: MISC
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x37a0000
physical_start_addr: 0x37a0000
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00

- partition_index: SYS13
partition_name: LOGO
file_name: logo.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x3820000
physical_start_addr: 0x3820000
partition_size: 0x800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

- partition_index: SYS14
partition_name: EBR2
file_name: EBR2
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x4020000
physical_start_addr: 0x4020000
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

- partition_index: SYS15
partition_name: EXPDB
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x40a0000
physical_start_addr: 0x40a0000
partition_size: 0xf60000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00

- partition_index: SYS16
partition_name: ANDROID
file_name: system.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x5000000
physical_start_addr: 0x5000000
partition_size: 0x32000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

- partition_index: SYS17
partition_name: CACHE
file_name: cache.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x37000000
physical_start_addr: 0x37000000
partition_size: 0x8000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

- partition_index: SYS18
partition_name: USRDATA
file_name: userdata.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x3f000000
physical_start_addr: 0x3f000000
partition_size: 0x100000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00

- partition_index: SYS19
partition_name: FAT
file_name: fat_sparse_mt6592jb9
is_download: false
type: EXT4_IMG
linear_start_addr: 0x13f000000
physical_start_addr: 0x13f000000
partition_size: 0x0
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00

- partition_index: SYS20
partition_name: BMTPOOL
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xFFFF00a8
physical_start_addr: 0xFFFF00a8
partition_size: 0x1500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
reserve: 0x00
Patches, or patches (English patch)
- information intended for the automated introduction of certain changes in computer files. Applying a patch is sometimes called “patching.”
Patch or update eng. The update is called, in particular, an automated, separately supplied software that contains such information and is used to fix software problems or change its functionality.
The fix can be applied to an already installed program, or to its source codes. This includes fixing errors, changing the appearance, improving the ergonomics or performance of programs, as well as any other changes that the developer wished to make.
The size of the patches can vary from a few kilobytes to hundreds of megabytes. In particular, patches can be very large when changing or replacing non -gram data, such as files with graphics and sound (often found in computer games). Nevertheless, the large size can be caused by the multiplicity of the changes made. At the same time, the words “patch”, “patch” are usually used to indicate small corrections, but large patches that seriously change or update the program are often called “Service Pack” or “Software Updates”. Wikipedia material
Odex-deodex
SISTEMS .APK files along with them have a file with the same name and expansion .ODEX. With their help, it is supposed to save some space. Deodxing means that you convert this .ODEX in .DEX (the same file stored inside .APK) and put it back into .APK. This allows us to freely replace the system applications, without worrying about the raxes, but the main reason for deodecting was to do such an operation with the Services.jar file, so you can change the colors of all texts (for example, the color of the white hours to black, etc.) , And in order to deodects Services.jar, it is necessary to deodect all systemic .APK-shki. The craftsmen removed the .ODEX files from the firmware, prescribing the information contained in them inside the APK files, thereby reduced the firmware and most importantly-now the apk files themselves can be changed as you like, this does not affect the operation of the system with a fatal way. This is called deodexing. What is good-in a deodoxed firmware, you can easily open an archive for the APK file, change resources (pictures, etc.) in it and return the changed file to a place in the firmware. What is not very good - the process of the system with such files slows down a little, but this is not critical.
Boot.img
The boot image of the system, in fact, this is the core of the OS. The bootloader works like a Linux kernel: it can use an mboot-compatible bootloader (usually patched syslinux is used), which serves the boot-dfe .img file (for Linux users, it is known as a RAM disk or initrd), and boot-dfe uses it to get kext / mkext files. (OSx86)
build.prop
On our smartphone in the system folder there is a file build.prop. This file contains information about the settings and firmware of the device, which are applied immediately after it is turned on.
If desired, you can edit this system file. Romodels usually use this file to speed up or improve system performance.tweaks .
ro.build.display.id = XXXX. This line shows the name of the firmware build. It can be viewed in Settings-About phone-Build number. The value XXXX can be changed to suit your taste.
debug.sf.hw = X. This line is responsible for hardware acceleration. It is needed to speed up the graphical interface. A value of 1 activates it. A value of 0 deactivates.
dalvik.vm.heapsize = Xm. This line sets the heapsize value. VM Heap Tool - increase the size of memory for applications. Experienced users say that the value of X is better to change to 512.
dalvik.vm.execution-mode = int: XXX. This line is responsible for JIT. Value jit includes it, and the value fast turns off.
ro.product.model = XXXX Here, instead of XXX, the device model is written. It is useful for those who have some games refuse to start, due to the fact that the device does not fit. We prescribe another model instead of yours, for example, desire HD and the game starts ...
So, with the lines, it seems, sorted out. Now we need to learn how to edit them. If Root Explorer is installed, open it and go to the / system / folder. We see below the folder list file build.prop. Switch the top of the button R / W to R / O. Long tap on the file, opens the list of editing options. Select Open in a text editor (Open in Text Editor). Well and then we edit.
But with the build.prop Editor application, you can greatly simplify this process.
The program build.prop Editor is very easy to use. After its launch, we see the list of parameters contained in the build.prop file and we can select any of them to change its value. In addition, you can add new parameters to the file. In order for the changes to take effect, a system reboot is required.
Attention! Editing the build.prop file, you must clearly understand what a particular parameter means, otherwise you can seriously disrupt the performance of your phone! There are a lot of information on editing this file and adding tweaks.savagemessiahzine.comand on the pages of Google.
I usually add several parameters to my firmware, namely:

# TWEAKS

# Enable init.d (read more about init.d below)
sys.initd = 1
sys.initd.loop = 1

# Tweaks of the speaker signal
persist.cust.tel.eons = 1
ro.ril.enable.amr.wideband = 1
ro.config.hw_fast_dormancy = 1

# Disable JIT compilation
dalvik.vm.execution-mode = int: fast

# Disable the debug mode icon in the status bar when the cable is connected
persist.adb.notify = 0

# Disable call delay
ro.telephony.call_ring.delay = 0

Build.prop content from firmware fromJiaYu G4Sfrom 22.04
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id = JDQ39
ro.build.display.id = G4S 20140422-121442
ro.build.version.incremental = eng.scm.1398140016
ro.custom.build.version = 1398140016
ro.build.version.sdk = 17
ro.build.version.codename = REL
ro.build.version.release = 4.2.2
ro.build.date = Tue Apr 22 12:14:42 CST 2014
ro.build.date.utc = 1398140082
ro.build.type = user
ro.build.user = scm
ro.build.host = v75
ro.build.tags = test-keys
ro.product.model = JY-G4S
ro.product.brand = JIAYU
ro.product.name = S8
ro.product.device = S8
ro.product.board = S8
ro.product.cpu.abi = armeabi-v7a
ro.product.cpu.abi2 = armeabi
ro.product.manufacturer = JYT
ro.product.locale.language = en
ro.product.locale.region = RU
ro.wifi.channels =
ro.board.platform = MT92_S8
# ro.build.product is obsolete; use ro.product.device
ro.build.product = S8
# Do not try to parse ro.build.description or .fingerprint
ro.build.description = S8-user 4.2.2 JDQ39 eng.scm.1398140016 test-keys
ro.build.fingerprint = JIAYU / S8 / S8: 4.2.2 / JDQ39 / 1398140016: user / test-keys
ro.build.flavor = mt92_s8_g4s_jyt_jb9_wcdma_ldata_tphone
ro.build.characteristics = default
# end build properties

# begin mediatek build properties
ro.mediatek.version.release = ALPS.JB9.MP.V1.4
ro.mediatek.platform = MT6592
ro.mediatek.chip_ver = S01
ro.mediatek.version.branch = ALPS.JB9.MP
ro.mediatek.version.sdk = 1
# end mediatek build properties
#
# system.prop for generic sdk
#

rild.libpath = / system / lib / mtk-ril.so
rild.libargs = -d / dev / ttyC0


# MTK, Infinity, 20090720 {
wifi.interface = wlan0
# MTK, Infinity, 20090720}

# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc = 1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p = 1
# MTK, mtk03034 20110318}

# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia = 0
# MTK, mtk03034 20101213}


#
wifi.tethering.interface = ap0
#

ro.opengles.version = 131072

wifi.direct.interface = p2p0
dalvik.vm.heapgrowthlimit = 256m
dalvik.vm.heapsize = 512m
dalvik.vm.execution-mode = int: fast

# USB MTP WHQL
ro.sys.usb.mtp.whql.enable = 0

# Power off opt in IPO
sys.ipo.pwrdncap = 2

# Switching Menu of Mass Storage and MTP
ro.sys.usb.storage.type = mtp, mass_storage

# USB BICR function
ro.sys.usb.bicr = yes

# USB Charge only function
ro.sys.usb.charging.only = yes

# audio
ro.camera.sound.forced = 0
ro.audio.silent = 0

ro.zygote.preload.enable = 0

#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num = 2
ro.gemini.smart_sim_switch = false
ro.gemini.smart_3g_switch = 1
ril.specific.sm_cause = 0
bgw.current3gband = 0
ril.external.md = 0
ro.btstack = blueangel
ro.sf.hwrotation = 0
ril.current.share_modem = 2
launcherplus.allappsgrid = 2d
launcher2.allappsgrid = 3d_20
curlockscreen = 1
ro.mediatek.gemini_support = true
persist.radio.fd.counter = 15
persist.radio.fd.off.counter = 5
persist.radio.fd.r8.counter = 15
persist.radio.fd.off.r8.counter = 5
persist.mtk.wcn.combo.chipid = -1
drm.service.enabled = true
fmradio.driver.enable = 1
ril.first.md = 1
ril.flightmode.poweroffMD = 1
ril.telephony.mode = 1
dalvik.vm.mtk-stack-trace-file = / data / anr / mtk_traces.txt
persist.mtk.anr.mechanism = 1
mediatek.wlan.chip = MTK_CONNSYS_MT6592
mediatek.wlan.module.postfix = _mtk_connsys_mt6592
ril.radiooff.poweroffMD = 0
ro.config.notification_sound = F1_New_MMS.ogg
ro.config.alarm_alert = Alarm_Classic.ogg
ro.config.ringtone = Champagne_Edition.ogg
ter.service.enable = 0
persist.sys.display.clearMotion = 1
persist.clearMotion.fblevel.nrm = 255
persist.clearMotion.fblevel.bdr = 255
persist.sys.custom_transparency = 1
persist.sys.timezone = Europe / Moscow
persist.sys.themePackageName = com.tmobile.theme.Grass
persist.sys.themeId = Grass
ro.init.show_bat_percent = 1
ro.init.ringtone_vol = 15
ro.init.notification_vol = 15
ro.init.alarm_vol = 15
ro.init.music_vol = 15
ro.init.fm_vol = 15
ro.init.profile_vibration = true
ro.init.install_non_market_app = true
ro.init.call_vol = 6
ro.init.screen_brightness = 255
persist.sys.status_bar_alpha = 0
net.bt.name = Android
dalvik.vm.stack-trace-file = / data / anr / traces.txt
ROOT
- Linux users know that root access rights are usually known, and for Windows users, it is possible to log in to the system as an administrator. In short, root rights give us the opportunity to do with the system everything that pleases: delete, edit, add files, including system files.
The list of opportunities that open to the user of the Android system, which has root rights:
Unlimited control over the system.
The ability to replace system files with which you can:
  • Change themes
  • Replace standard applications such as calendar, clock, mail program, etc.
  • Replace the system loader and the Recovery image for the ability to save and restore the system and replace the firmware.
  • You can add and change system applications, for example, with the busybox program, which allows you to execute almost all linux commands, you can replace the existing toolbox, which has a very limited set of commands.
  • Change images and animations that are displayed at system startup.
  • Run applications that give you more control over the system, such as SuperUser, which allows you to grant root rights to various programs, the Root Explorer, the file manager, which allows you to see and work with all the files on your device, unlike the standard file manager, Programs that allow delete and change any applications, including system and many more programs that make life easier for the Android user.
  • Make a backup of your system, including the programs you added and data that you can restore at any time after resetting to factory settings or updating the firmware
  • Move installed applications from phone or tablet memory to a memory card.
  • Transfer temporary files of the Internet browser and cache of various applications to the memory card.
  • Manage your device using a computer via USB or WiFi connection.

Busybox
Busybox is essentially a set of console utilities for Linux systems. It is necessary, for example, to run app2sd or overclocking programs or something like that, which requires the connection of third-party kernel modules. In most custom firmware it is already built. Read more below [/ b]
USB OTG (On-The-Go)
-Further expansion of the USB 2.0 specification, designed for a light connection of peripheral USB devices with each other without the need to connect to a PC. For example, a digital camera can be connected to the photo printer directly if they both support the USB OTG standard. You can connect some USB devices to models of PDA and communicators supporting USB OTG. Usually these are flash drives, digital cameras, keyboard, mice and other devices that do not require additional drivers. This standard arose due to the already sharply increased need for a reliable connection of various devices without using a PC.
When connected via USB, the OTG device rank (master or slave) is determined by the presence of a jumper to the ID plug in the wire. Wikipedia
BB is a big brother
- This is a computer or laptop with any internet connection.
Why do you need it? For example, the situation: you have access to the network via DSL, wi-fi is not, GPRS is too expensive. What to do? That's right, to connect a smaller brother to an older brother, in order to calmly update applications and follow Twitter through an android device.
You and I need the BB to transfer files from a computer to a smartphone and vice versa, and also to assign rights to files copied to the system folders of a smartphone. This is done most conveniently through TotalCommander with the adbplugin plugin installed. Well, and most importantly, perhaps, this is the ability to flash the smartphone system completely or in parts using the FlashTool tool.
CWM
- is a system recovery utility (menu) that allows you to make full backup copies of the entire system of the device, install firmware, mods and much more on it.
Details below
TWRP
- advanced touch recovery, with a graphical interface and full touch control. More details below.
Block sections from TWRP recovery 2.7.1.0. from sevenmaxxs
The knowledge of this or that block is necessary for romodels in the first place, in order to understand where to write the files from the firmware.
For example, section
/ system matches block / dev / block /mmcblk0p5
Partition Logs:
/ boot | / dev / bootimg | Size: 10MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: / dev / bootimg
Display_Name: Boot
Storage_Name: boot
Backup_Path: / boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: / boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/ logo | / dev / logo | Size: 8MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: / dev / logo
Display_Name: Logo
Storage_Name: Logo
Backup_Path: / logo
Backup_Name: logo
Backup_Display_Name: Logo
Storage_Path: / logo
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/ misc | / dev / misc | Size: 0MB
Flags: IsPresent
Primary_Block_Device: / dev / misc
Display_Name: misc
Storage_Name: misc
Backup_Path: / misc
Backup_Name: misc
Backup_Display_Name: misc
Storage_Path: / misc
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/ nvram | / dev / nvram | Size: 5MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: / dev / nvram
Display_Name: Nvram
Storage_Name: Nvram
Backup_Path: / nvram
Backup_Name: nvram
Backup_Display_Name: Nvram
Storage_Path: / nvram
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/ recovery | / dev / recovery | Size: 10MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: / dev / recovery
Display_Name: Recovery
Storage_Name: Recovery
Backup_Path: / recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: / recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/ uboot | / dev / uboot | Size: 0MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: / dev / uboot
Display_Name: Uboot
Storage_Name: Uboot
Backup_Path: / uboot
Backup_Name: uboot
Backup_Display_Name: Uboot
Storage_Path: / uboot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/ system | / dev / block / mmcblk0p5 | Size: 889MB Used: 588MB Free: 300MB Backup Size: 588MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: / dev / block / mmcblk0p5
Display_Name: System
Storage_Name: System
Backup_Path: / system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: / system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

/ cache | / dev / block / mmcblk0p6 | Size: 125MB Used: 8MB Free: 117MB Backup Size: 8MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: / dev / block / mmcblk0p6
Display_Name: Cache
Storage_Name: Cache
Backup_Path: / cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: / cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

/ data | / dev / block / mmcblk0p7 | Size: 4030MB Used: 1097MB Free: 2932MB Backup Size: 1097MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Encrypt_Backup Use_Userdata_Encryption
Primary_Block_Device: / dev / block / mmcblk0p7
Display_Name: Data
Storage_Name: Data
Backup_Path: / data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: / data
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

/ emmc | / dev / block / mmcblk0p8 | Size: 9678MB Used: 3041MB Free: 6637MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent Has_Android_Secure Is_Storage Is_Settings_Storage
Symlink_Path: /emmc/.android_secure
Symlink_Mount_Point: / and-sec
Primary_Block_Device: / dev / block / mmcblk0p8
Display_Name: Int.SDcard
Storage_Name: Int.SDcard
Backup_Path: / and-sec
Backup_Name: and-sec
Backup_Display_Name: Android Secure
Storage_Path: / emmc
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files

/ sdcard | / dev / block / mmcblk1p1 | Size: 29718MB Used: 18193MB Free: 11524MB Backup Size: 18193MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable IsPresent Is_Storage
Primary_Block_Device: / dev / block / mmcblk1p1
Alternate_Block_Device: / dev / block / mmcblk1
Display_Name: Ext.SDcard
Storage_Name: Ext.SDcard
Backup_Path: / sdcard
Backup_Name: sdcard
Backup_Display_Name: Ext.SDcard
Storage_Path: / sdcard
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files

/ sd-ext | / dev / block / mmcblk1p2 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mitted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset
Primary_Block_Device: / dev / block / mmcblk1p2
Display_Name: SD-ExtFS
Storage_Name: SD-ExtFS
Backup_Path: / sd-ext
Backup_Name: sd-ext
Backup_Display_Name: SD-ExtFS
Storage_Path: / sd-ext
Current_File_System: swap
Fstab_File_System: auto
Backup_Method: files

/ usb-otg | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
Primary_Block_Device: / dev / block / sda1
Alternate_Block_Device: / dev / block / sda
Display_Name: Usb-Otg
Storage_Name: Usb-Otg
Backup_Path: / usb-otg
Backup_Name: usb-otg
Backup_Display_Name: Usb-Otg
Storage_Path: / usb-otg
Current_File_System: auto
Fstab_File_System: auto
Backup_Method: files
What is a Test Point?
Test points (English test points - key points) are points on electronic equipment that give access to software in the event of a software or hardware error. In particular, the test points located on the mobile phone board allow you to record any information in the boot area.
These points can be of different modifications, for example, a track on the board, a specific contact, or a set of contacts. Usually, in order to change the boot part of the phone, as well as to modify the capabilities of the phone, it is necessary to “cut” the test point (that is, to close or cut it).
Test points are used to disable the internal boot loader (bootcore) of mobile phones, which by default do not allow someone else's bootloader into their firmware. After completing the bootloader shutdown procedure through test points, it becomes possible to unlock a mobile phone (removing the SP lock), flashing the phone with damaged software, or flashing the phone with new software.
For accurate and quick access to the test points on the board, special connectors can be used, which are superimposed on the disassembled mobile phone and connect the phone to a computer or an independent unlocking device. In addition to connectors, special test point cables can also be used, which are wires with needles of a certain thickness at the ends. Wikipedia
MIUI, meow, mia, miyu, miyu, miyuai
MIUI (pronounced "Me You I") - User interface for smartphones based on the Android operating system with open source. The MIUI firmware code is closed. It is developed by Xiaomi Tech. The firmware is a strongly changed user interface in which there is no application menu. The firmware combines the most successful solutions Android and iOS. User firmware includes additional functions that are absent in the standard Android OS, such as switches in the retractable notification panel, a new camera, a gallery and player, also changed the nomeronabrifier, which displays the contacts as the user enters the number. Taken from Wikipedia
LEWA, left, left, left
LEWA- user interface for smartphones based on the Android operating system with open source. LeWa firmware is developed by a team of professional developers, from the country, the Middle Kingdom. This ensures the stability of the project, as well as they ensure continuous development. The firmware comes out with an interval of 1 week (7 days (168 hours (10080 minutes)))!
Why is LeWa better than others?
  • Advanced status bar, includes a traffic counter, phone memory management, notifications, and in addition has a large quick access bar;
  • Built-in program to block unwanted calls, and SMS filtering;
  • When calling from a hidden number, under the inscription "Private number", the number itself is written;)
  • Record a conversation directly from the line, while it has the function of auto-recording;
  • Unique search engine in the address book;
  • A universal power manager, called "Power +", will help to significantly save your battery;
  • Native file manager, which has no analogues in beauty and functionality;
  • The ability to quickly and freely change the design of the entire smartphone, through the Themes application, everything changes from boot to fonts. As well as a catalog of topics;
  • When you call, the photo is displayed on the whole screen;
Here is a small list of what is in this firmware, but the main thing is that what is not visible in it “hides” inside, i.e. very thoughtful program code! That guarantees stability and ease of use.


Post has been editedjemi - 22.03.15, 21:18



Rep: (3321)
Backup IMEI and everything related to the NVRAM partition (IMEI / MAC / Wi-Fi / BT)

What is the NVRAM section and what is it used with?
  1. For storing calibrations of wireless modules (GSM / Wi-Fi / BT / GPS) and equipment, identification information (IMEI, MAC), equipment settings (speaker, microphone, camera features), a separate fat-like memory is provided in the built-in flash (ROM) referred to as NVRAM. For the MT6577 / 89/72/82/92/95 processor series, its size is about 5MB.
  2. The / dev / nvram section is flashed at the factory and all further official updates and firmware even dare not touch it. No matter how the program part changes, it remains unchanged. In rare cases, the manufacturer makes changes to it, and releases firmware for service centers, including this section.
  3. During the first launch of the phone, information from this memory area is copied (cached) to / data / nvram. After that, the data in the cache can be changed by the firmware of the phone, as well as from the engineering menu. Resetting the phone to the factory settings or flashing the userdata section, either separately or as part of the firmware, erases this cache and is cached again when it is first started (all user changes are lost, reset to factory settings).
  4. The recommendation is to save the / data / nvram folder to restore IMEI in the future. This, of course, is true. But restoring / data / nvram will not return the contents in the / dev / nvram block.

What should be done to avoid any problems in the future?
  • The one and only thing is to create a complete memory dump of the device immediately after purchasing the device. Depending on the dump method, among other files there must be a nvram.img file (nvram.bin). It is the image whether it is .img or .bin size 5242880 - and there is an image of the necessary section. Any nvram.tar and other ext4 are copies of / data / nvram and are of no interest;

REQUIREMENTS:
  1. Windows 7/8 / 8.1 / 10
  2. By experience, I would say that it is desirable to have a clean as a tear system, where there are no extra drivers, any obscure programs, and so on.
  3. Official stock firmware on the smartphone under the SP Flash Tool, (where you must be in a separate folder of the APBD and MODEMDB database, although we already have bases in the ammunition)
  4. Memory card
  5. Make sure your NVRAM is really damaged. (Settings - About phone - Status (general information) - About IMEI. If IMEI is not there, then nvram is damaged. Wi-Fi networks show "Nvram warning err = 0x10". Changing (absent) MAC address of Bluetooth and Wi -Fi)
  6. Charged smartphone min. up to 50%.
  7. To be ready, that it’s possible to fail from 1 or even 5 times and mistakes will be sprinkled !!!
Backup (Backup) IMEI
Method 1. Universal and basic through MtkDroidTools
Need enabled RTH.
1. Unpack MtkDroidTools.
2. Turn on the phone: Settings - For Developers - USB Debugging
3. Run MtkDroidTools, connect the cable to the phone
4. In the program, press ROOT (root must be enabled on the phone). If there are requests on the phone screen - we allow. waiting for the inscription "root shel received temporarily before rebooting
Attached Image

5. Click IMEI / NVRAM =>Backup.
6. 2 files appear in the BackupNVRAM folder: JiaYu-G4S_your IMEI_nvram_date-time with bin and tar extensions
6. Copy these files to a safe place.

Method 2. Through the TWRP custom recovery, where this feature is provided
1. Find the Backup item.
Attached Image
2. Put a tick on the item nvram.
Attached Image
3. Go to the NAME tab and rename for convenience.
Attached Image
4. ->Swipe to BackUp.
Attached Image
5. Make sure that the operation succeeded "Successful".
6. Press the "Reboot System" key.
7. The nvram backup is located on the built-in or external memory in the / TWRP / BACKUPS / G4s / YYYY-MM-DD folder — HH-mm-ss /, where Y, M, m are common date / time mask characters. The folder will contain the files nvram.emmc.win, nvram.emmc.win.md5.
We copy the entire folder together with the root in a couple of safe places until the need for it.

Method 3. Via the Mobile Uncle application (Mobileuncle Tools)
1. Need a ROOT.
2. Go to the menu item IMEI Backup and Restore (MTK).
3. Back up either to the internal memory or to the SDCARD, and better both there and there.
4. We keep in a safe place just in case.

Method 4. Via ADB
1. Download the archive and follow the instructions.
2. For backup, run the batch file nv_restore.bat
Download:Attached file[Email Protected](468.86 KB)

Method 5. Through Terminal Emulator for Android
1. It is important to have root-rights on the device!
2. DownloadingAndroid Terminal Emulator
3. Run Terminal Emulator for Android.
4. We register:
su
dd if = / dev / nvram of = / sdcard / nvram.img bs = 5242880c count = 1

5. Connect the device to the computer and in the root of the drive, find the file nvram.img and copy it to a couple of reliable places on the PC until the need for it.

Restore IMEI
I made a decision, for the convenience of understanding further actions, to divide the methods of restoring NVRAM conditionally into"factory" and "software" , that is, on methods when the NVRAM partition is restored to the "factory" state and when IMEI is simply written at the firmware level.

To restore the NVRAM partition to the "factory" state, along with IMEI, MAC, Bluetooth, a database is usually required, which usually lies in a separate folder to the stock firmware for SP FLASHTOOL. Sample file names are as follows: database with files APDB_MT6592_S01_KK1.MP1_ and BPLGUInfoCustomAppSrcP_MT6592_S00 _..._ wg_n

For our device, I rebuilt the full ammunition to restore IMEI with the APBD and MODEMDB databases, drivers and software. You can use the full set of drivers anytime and anywhere (wherever the instructions talk about drivers, specify this folder), and the APBD and MODEMDB databases are compiled for both KitKat and JellyBeen.


Full IMEI Restoration Ammunition
Composition:
1. Drivers: common drivers for the device, Preloader mode driver (USB VCOM Driver - usb2ser_Win ***. Inf), Meta mode mode driver (CDC Serial - cdc-acm.inf), MediaTek USB Port mode driver (android usb - androidusb .sys) + couple just in case.
2. SN Write tool up to 2.1504.0
3. IMEI & SN Writer V1.5.3
4. Maui META exe 3G v7.1412.1.
Modem Database Jelly Been
Modem Database KitKat
_ALL_IN_ONE - all in one

Download : shared folder Yandex.Disk
FACTORY METHODS
Restore IMEI backup
Method 1. Through MtkDroidTools.
Need enabled RTH.
1. Unpack MtkDroidTools.
2. Turn on the phone: Settings - For Developers - USB Debugging
3. Run MtkDroidTools, connect the cable to the phone
4. In the program, press ROOT (root must be enabled on the phone). If there are requests on the phone screen - we allow. waiting for the inscription "root shel received temporarily before rebooting
Attached Image
5. Click IMEI / NVRAM =>Restore.
6. Select the file from the previously made backup JiaYu-G4S_your IMEI_nvram_date-time.bin
7. Select the file from the previously made backup JiaYu-G4S_your IMEI_nvram_date-time.tar
8. Restart the phone. IMEI recovery is over.

Method 2. Method through TWRP custom recovery, where such an opportunity is provided
1. Backup nvram should be on the way of backup backups / TWRP / BACKUPS / G4S / YYYY-MM-DD - HH-mm-ss /
2. Find the Restore item.
Attached Image

3. We see a tick on the item nvram.
4. ->Swipe to BackUp.
5. Make sure that the operation succeeded "Successful".
6. Press the "Reboot System" key.

Method 3. Via the Mobile Uncle application (Mobileuncle Tools)
1. Need a ROOT.
2. Go to the menu item IMEI Backup and Restore (MTK).
3. We restore (the RESTORE item) either from the internal memory or from the SDCARD.

Method 4. Via ADB
1. Download the archive and follow the instructions.
2. To restore run the batch file nv_restore.bat
Download:Attached file[Email Protected] (468.86 KB)

Method 5. Through Terminal Emulator for Android
1. It is important to have root-rights on the device!
2. DownloadingAndroid Terminal Emulator
3. Run Terminal Emulator for Android.
4. We register:
su
dd if = / sdcard / nvram.img of = / dev / nvram

5. We make wipe cache and dalwik in recovery
Recover Lost IMEI
ALL 3 WAYS DESCRIBED WAYS NEEDED FOLLOWING:
1. Official stock firmware with a completely clean as a tear smartphone inside and preferably without a sdcard (we may think that it is the cause of failure)
2. Clean from drivers of various flashing, in general, like a tear of Windows
3. Complete ammo kit for IMEI repair onYandex.Disk
3. Patience in installing drivers.
3.1. Required installed drivers: Preloader mode drivers (USB VCOM Driver - usb2ser_Win ***. Inf), Meta mode mode drivers (CDC Serial - cdc-acm.inf), MediaTek USB Port mode drivers (android usb - androidusb.sys).
4. THREE BELOW-WRITTEN METHODS OF LIKE YOURSELF
IMEI & SN Writer
Later I will probably describe it in words, but for now watch the video:https://www.youtube.com/watch?t=78&v=WHFNrbt-b2o
SN Write Station
Restore to SN Write Station Tool v2.1320.00
1. The most basic and problematic is the installation of drivers. I prefer to do it in the process of working in this program, rather than before the start. You try and so and so.
1. Install the program (setup.exe)
2. Start the label SN_STATION
3. Since both wi-fi and Bluetooth work on the device, only IMEI is invigorated. Put a tick (select items) as in the screenshot below
Attached Image
4. We are looking for the necessary database files in the freshly downloaded archive of "full ammunition for restoring IMEI with APBD and MODEMDB databases, drivers and software".
5. Turn off the phone (the cable from the computer is disconnected!). Click the START button.
6. The program will display a window in which you need to enter both IMEI. Next, click OK.
Attached Image
7. Connect the phone (with battery) to the computer. Windows will find a new device, will install the driver. We follow the process in the device manager. Right-click on one of the unknown devices ->Update driver ->We manually specify the folder with the ammunition kit (or the folder with the drivers for the device, it is desirable that the entire full set of the driver be in it).
8. We are waiting for the drivers to be successfully installed.
9. The program at this point may give an error. We take out-insert the battery and repeat steps 3-8. If the error is again, try one more time. This is all the driver installation costs - while the program is waiting for a response from the smartphone, drivers are installed at this point, and the program simply runs out of time. If you think well, then at least three times you can observe an error (it was said above about installing three additional drivers of different modes).
10. There should be no errors in the status window.
11. We are waiting for the end of the program. If the IMEI recording process is successful, then Write Result Indicator will turn green. And a new IMEI entry window will appear. Press ESC and close SN_Write_Tool.
Turn on the device and check IMEI (* # 06 #)
Maui META 3G and SP META
SOFTWARE METHODS
Method 1. Repair IMEI through the terminal
Ruth is not needed
To register in Android Terminal Emulator:
echo 'AT + EGMR = 1.7, "IMEI_1"'>/ dev / pttycmd1
echo 'AT + EGMR = 1.10, "IMEI_2"'>/ dev / pttycmd1
where IMEI_1 and IMEI_2 are your IMEI, which are registered under the battery on the case.

Method 2. Repair IMEI without software
In the dialer dial:
*#4634#
In the dialog that appears, enter your IMEI twice and press SAVE.

Method 3. Restore broken NVRAM from vova.vafin
Patch to restore broken NVRAM from vova.vafin for custom recovery

Method 4. Repair IMEI after flashing through the code of the engineering menu
  1. Enter the code of the engineering menu * # * # 3646633 # * # *
  2. In the engineering menu, select: "CDS Information" ->"Radio Information" ->"Phone1" "Phone2"
  3. In the uppermost field, where it is written AT + add EGMR = 1.7, "your_imei1"
  4. as a result, we get the string AT + EGMR = 1.7, "your_imei1" and press the "SEND AT COMMAND" button
  5. If you need to register IMEI for the second SIM card, then go to the section "Phone2", where we write AT + EGMR = 1.10, "your_imei2" and again press the "SEND AT COMMAND"
  6. Exit the engineering menu and restart the smartphone.
  7. Check your imei by dialing the code * # 06 #

Method 5. Mobileuncle MTK IMEI Write Tool
Attached Image
As they laid out the Chinese program for recovering imeev. She was in Chinese and worked strangely (at least for me).
I bring to your attention a modified and translated into English MobileUNCLE MTK IMEI Write Tool V1.2 English by[Email Protected]specifically for our apparatus collected.
What is it then?
Description : it serves itself to replace the software recovery method by means of the AT command of the above described method 4 and with the subsequent restoration in the mobile uncle.
A source : http://bbs.ydss.cn/thread-317023-1-1.html
Translation and optimization: jemi
  1. Download and unpack Attached fileMobileuncle MTK IMEI Write Tool V1.2 Engl by[Email Protected] (80.13 KB)

  2. Launch MobileUNCLE MTK IMEI Write Tool V1.2 Engl by[Email Protected]and seescribbleEnglish and not mighty. Follow the instructions.
  3. Enter IMEI 1 code ->"Y"
  4. Enter IMEI 2 code ->"Y"
  5. The created IMEI. BAK is transferred to the root of the SD card
  6. Next, download to your smartphoneВ® Mobileuncle MTK Tools
  7. Run, select IMEI backup and restore, restore IMEI.bak.
  8. Is done.
More methods (unverified, etc.)

MAC Address Lock -Jiayu G4S - LeWa OS Firmware (OS 4.2.x - 4.4.x) (Post $ iLence # 34492815)
Replacing the MAC address:Jiayu G4S - LeWa OS Firmware (OS 4.2.x - 4.4.x) (Post RM4Y # 35790600)
Links to the theory on various resources

Download the software mentioned in the post.


Old text
NVRAM information on MTK devices, backup, restore on Lenovo-Forum

What is NVRAM, its backup and recovery readZOPO ZP990 - Firmware (OS)]
An old little article on recovering lost when hardware reset IMEIhere
Perhaps the instruction will helphere
Also in our subject isNVRAM backup / restore instructions in MtkDroidTools
Repair IMEI via terminal (Route is not needed)
Instructions based on this FAQ and how to conclude it:Jiayu G4S - Official firmware (OS 4.2.2) (Post # 34206068)
Instructions for the restoration of IMEI on MTK processors through the mobileuncle mtk imei write tool
Repair IMEI without software
Patch to restore broken NVRAM from vova.vafin for custom recovery - relevant to the kitkat (after you need to enter your own name)
Repair IMEI after flashing through the engineering menu code
Another short instruction on how to restore IMEI through SN_Write_tool prog

MAC Address Lock -Jiayu G4S - LeWa OS Firmware (OS 4.2.x - 4.4.x) (Post $ iLence # 34492815)
In general, his replacement:Jiayu G4S - LeWa OS Firmware (OS 4.2.x - 4.4.x) (Post RM4Y # 35790600)

Forfull recovery The NVRAM section, along with IMEI, MAC, Bluetooth, requires a database, which usually lies in a separate folder for the stock firmware for SP FLASHTOOL. Sample file names are as follows: database with files APDB_MT6592_S01_KK1.MP1_ and BPLGUInfoCustomAppSrcP_MT6592_S00_MOLY_WR8_W1315_MD_WG_MP_V34_1_wg_n

My advice is to use the information below:
If you have studied all the above this information about the NVRAM section, then you would understand the restoration disadvantages of some of the above methods (by the way, I’ll not be afraid and say that the largest and most accurate collection of all kinds of instructions for the restoration of those has been collected). And the minus is one at least, but alas, the most nasty. All of the above recovery methods (except for those where there is a person -made backup) do not restore the NVRAM section, but only fit the values ​​(Tobish have) into your real firmware, and with reflaging they will fly again. Therefore, we read further ..

Full ammo kit for IMEI repair where I collected a complete set of firewood (everywhere where the instructions talk about drivers, indicate this folder), databases for KitKat and JellyBeen, a couple of instructions and the necessary programs I collected here.
I tried to recover on win8, win7. No problem, just desire and patience. Firewood from the first time will not be established most likely.
Full IMEI Repair Kit - [attachment = "4946039: IMEI Recovery.rar"] Full Recovery Kit onYandex.Disk
We try, try and try again. I consult in drugs only after well, nothing happens.



Post has been editedjemi - 21.09.15, 23:58
Reason for editing: MobileUNCLE MTK IMEI Write Tool V1.2 Engl by [Email Protected] - the program did not work, fixed, repacked and simplified



Rep: (3321)
Backup (Backup) and System Restore (Restore)
May need the latest BusyBox! (its installation file can be downloaded for free from the Google Play Market:BusyBox Installer by JRummy Apps Inc.orBusyBox from Stephen (Stericson))
Through modified CWM
Backup system:
  • Run CWM recovery
  • Choose "Backup & restore"
  • Choose "backup"
  • Choose "YES"
  • Select Reboot system now (reboot)
  • After that, a full backup will appear on the memory card in the clockworkmod / backup folder. The name of the backup copy includes the time and date of its creation, but the name can be given arbitrary, of course, in Latin letters without spaces.
Recovery:
  • Enter CWM Recovery
  • Choose "backup & restore"
  • Choose "restore"
  • Select the previously saved backup. It should be on the memory card in the folder clockworkmod / backup.
  • Confirm the recovery, select "YES". The confirmation item is usually not the first one on the list, this is normal.
  • At the end of the process, select "Reboot system now" (reboot).
Through modified TWRP
We read here:Attached fileInstall_firmware.pdf(2.99 KB)
Instructions for backup firmware in the program MtkDroidTools
For this method, you must first install the driver on your PC! How to do this, see the item "Installing drivers"
On the phone, "Connecting to a USB drive" should be turned off (the item appears in the curtain when connected via USB to a PC)
On the phone you need a ROOT and SD card
  1. Unpacking MtkDroidTools
  2. Turn on the phone: Settings - For Developers - USB Debugging
  3. Run MtkDroidTools, connect the cable to the phone
  4. In the program, press ROOT (root must be enabled on the phone). If there are requests on the phone screen - we allow. waiting for the inscription "root shel received temporarily before the reboot"
  5. Go to the tab "root, backup, recovery"
  6. Click Backup
  7. We wait. Then appears "Pack saved to the archive?". Click YES.
  8. After that, a backup file appears like JiaYu-G * S_dat-build_backup_dat-time.zip which is backup. It can be flashed using the SP Flash Tool.
Thank you say:baz88ka


Post has been editedjemi - 05.04.15, 00:45



Rep: (3321)
JiaYu G4S firmware and everything related to it

Algorithm "From purchase to installation of custom on the whale"
1. Check the build quality
2. Installing drivers
3. Work in MTK Droid Root & Tools
4. Work in the SP Flash Tool
5. Installing custom via TWRP / CWM

Content:
Work with drivers
MiniFAQ for firmware 4.4.2 KitKat

Work in the SP Flash Tool - the main flasher of official (and not only) firmware for the device
Work in the program MTK Droid Root & Tools v2.5.3 - the main program for obtaining Root, creating Backup, firmware Recovery. Provides complete information about the device, blocks and so on. For MT65xx. The main topic and all the answers to China-Forum .

FEATURES OF INSTALLING A KASTOMNOUS FIRMWARE 4.2. and 4.4.
Instructions for firmware 4.2.2(JellyBean)via SP Flash Tool 5 and the restoration of "bricks"
Instructions for firmware 4.4.2(Kitkat)via SP Flash Tool 5 and the restoration of "bricks"
Instructions for upgrading from version 4.2.2 (JellyBean) to version 4.4.2 (Kitkat) (stock & custom) + how to restore a brick

Installing TWPR / CWM ClockworkMod recovery in multiple ways
Installing patches, boot.img, bootanimation, and so on.

Post has been editedjemi - 12.08.15, 18:16



Rep: (3321)
Work with drivers

Driver Description + Download
Main driver archive - FeaturePhoneDriver (main driver), MT65xx Preloader (preloader driver), DPInst64.exe (additional driver for win 7/8), spinstall.exe (additional driver) + plus the necessary software to install the drivers correctly!
Download: https://yadi.sk/d/RwOniwkIfmcV4

JiaYu Official Drivers and Utilities - The official package of necessary drivers and utilities for flashing a smartphone. Also included are instructions for installing drivers and firmware of a smartphone in Chinese with pictures in DOC format.
Download : https://yadi.sk/d/v36K2fM3fmcYM

PDANet Driver - Driver and software for PC access to the Internet via a mobile device.
Download : https://yadi.sk/d/p3t0EWbIfmcZC

Universal ADB drivers - driver for connecting the ANDROID device by Adb
Download : https://yadi.sk/d/IpuYZKC8fmceZ

Shared folder with drivers on Yandex.Disk
Go to : https://yadi.sk/d/mgwsO1cTfmc6a
Driver installation
There is nothing difficult in installation. Let's stop only on the main points.
Automatic
Installing the main driver package.
1. We unpack the archive MAIN_MTK_Drivers_install_package.rar to the root of the "C" disk
2. In the FeaturePhoneDriver / v1.1123 folder, run InstallDriver.exe as administrator.
3. We are waiting for the appearance of the window
https://yadi.sk/i/lbwZq3WdfmdMA
4. If something does not work, install the remaining drivers from this folder.

Manually
Installing the main driver package.
If something did not work out automatically, do the following.
1. We unpack the archive MAIN_MTK_Drivers_install_package.rar to the root of the "C" disk
2. Go to the device manager
3. Turn off the phone and remove the battery and then connect the phone via USB to the computer
4. We see the appearance of an unknown device type "MTK65xx"
5. Click the right mouse button ->Driver Update ->Manually ->Search this computer ->Specify the path to our driver folder ->OK
Features of installing drivers on Win8 / Win8.1


Post has been editedjemi - 05.04.15, 14:11



Rep: (3321)
MiniFAQ on official KitKat / JellyBean firmware
General issues
How to reset the settings in the engineering menu to the factory.
It is necessary to delete the data / nvram / apcfg / aprdcl folder
Jiayu G4S - Official firmware (OS 4.2.2) (Post # 32636470)

How to log off through recovery - how it was installed, firmware, patch, update, and so on. (recovery.log)
[TWRP] Need to goimmediately after installing the firmware, patch, update etc. in the Advanced menu and click on Copy Log to SD Card. And it will be copied either to internal memory or to a memory card. You will see in the course.


Why out of 16 GB ~ 9 GB available?
The specified 16 GB of memory = 16.000.000.000 bytes, the real is 16.000.000.000/1024 = 15.625.000 KB / 1024 = 15.259 MB / 1024 = 14.9 GB. Of these, ~ 800-1000 mb under the OS, under the applications 4 GB and the remaining 10 GB under the files.


Where can I see what my screen is?
There are three types of screens:
5-touch AUO (usually in black models)
AUO on 10 touches (??)
LG for 5 touches (usually in white models)
LG for 10 touches (??)
Full information about the device (screen model, rear and front camera sensor, processor model) can be found in the engineering menu in "Other extra" where only the "Device info" item is available.
Example Device info
Attached Image
Either way: Jiayu G4S Advanced - Discussion (Post # 32080907)

Adequate and comfortable automatic backlight control (brightness) of the screen

At the expense of the camera sensors used in the device:
They put two types of modules: ov13850 (roughly 13) and ov12830 (roughly 12) both like mipiraw ... you should add statistics, when and where they shoved ... The 12th, if it doesn’t change memory, was announced just for version 1+ 4, remember more?
Now they are shoved randomly, purchased, and used as it should ...
Uh ... it turns out that it can be the 13th support in the firmware for 2 + 16, and for the 12th one should be pulled from the 1 + 4 firmware!
Vanguey that there are problems with soap, precisely because of the combination of firmware for 2 + 16 and the module 12830!
ov - OmniVision - manufacturer of CMOS sensors
truly - Truly Opto-Electronics - camera module manufacturer
I note that in ov12830 there is no Truly reference.
I believe that first of all it is a CMOS sensor model (ov13850), in the title of which there is infa about the number of pixels (first 2 digits).

Instructions for obtaining the "Mi-POP" navigation buttons

Installation method Xposed and Gravity Box on the official firmware.

SWAP ON - Actually for owners of Standart version (1/4)

Official Russian manual for Jiayu G4

JellyBean
JellyBean

Kitkat
Attention!!! ALL WHO PLANS TO SELL ON Android 4.4. KitKat !!!
Firmware based on official Kitkat v2 and higher have a new touchscreen driver. When you roll back to the firmware based on 4.2.2 and Kitkat v1, the shift of the wheel occurs.

What is the difference between the official firmware v1 and the official firmware v2 / v3 / v4 / v5?
In the official firmware v1, the so-called "old touchscreen driver". Its difference from the driver in v2 / v3 / v4 / v5 firmware is that it can roll back to version 4.2.2.

If I go through the official firmware v2 / v3 / v4 / v5, then what consequences will this entail?
When you roll back to the official firmware v1 or custom based on v1, you will get a touchscreen offset, provided that you have an AUO screen. On LG screens (5 touches) you will get an unworkable phone

How to roll back to Jelly Bean (4.2.x) and restore the touchscreen?
After installing any firmware 4.2. flash right awayTFKernel V.3 Jiayu G4S - to return to 4.2.2 JB | GoogleDrive

Vibration of panel keys does not work, how to fix it?
Trythismethod

The camera is working incorrectly (back-3 MPx, front-13), what should I do?
The solution you need in thispost

I downloaded the camera / auto brightness patch, etc. How to install it?
All patches are installed via custom recovery.

Titanium Backup refuses to backup, writes "not enough memory". What should I do?
Here issolution to this problem

I can not get into the recovery, butanimation sometimes disappears (screen lg47)
Help from galgai_erzloi in thispost

What is the difference between G4S firmware and G4SW
1. G4SW is the firmware for the European region. Accordingly, G4S firmware for Asian.
2. In the "European" version of the firmware is missing Chinese
3. Also in the "European" firmware there is no RTH-Prav
4. Modems in the "European" versions, according to users, keep the connection better


Post has been editedjemi - 12.08.15, 18:17



Rep: (3321)
Work in the SP Flash Tool

Instructions for firmware 4.2.2 (JellyBean) via SP Flash Tool 5 and the restoration of "bricks"
Instructions for firmware SP Flash Tool 5 and the restoration of "bricks"

When flashing devices via SP_Flash_Tool, do not sew the preloader file unless absolutely necessary.
1. Unpack the SP Flash Tool (link)
2. Turn off the smartphone. The cable is not connected to the computer.
3. Take out the battery.
4. Connect the phone to the computer with a cable. The operating system will find a new device - specify the system folder with the driver MT6592 USB VCOM (for its version of the OS). (link to drivers)
Either we install any other drivers from the header (or from the FAQ), there is also an installation file!
5. Disconnect the cable from the computer.
6. Unpack the OFFICIAL FIRMWARE.
[attachment = "4587774: drliWAp_1_.png"]

7. Run the program SP Flash Tool.
On the way to the folder with the firmware, there MUST NOT be Russian and / or Chinese characters.
8. Click on the Scatter-loading button and select the file in the folder with the *** scatter.txt firmware (in my case the file is called MT6592_Android_scatter.txt). just below, select "Firmware Upgrade" (in case of errors, select "Download"; again, an error? then Firmware Upgrade + Download.BUT ATTENTION!Be sure to backup IMEI before this using any of the known methods (in the help of the FAQ, the topic header)
9. Click the Download button.
10. Connect the phone to the computer with a cable. The program should see it and start the firmware. If the phone is not found then disconnect from the computer, insert and remove the battery and reconnect to the computer.
11. At the end of the firmware should see a circle with the words OK.
Attention
I am not responsible for the dead phones.

Instructions for firmware 4.4. (KitKat) via SP Flash Tool 5 and the restoration of "bricks"

Post has been editedjemi - 17.08.15, 13:44



Rep: (3321)
Work in the program MTK Droid Root & Tools v2.5.3

FEATURES OF INSTALLING KASTOMNYE FIRMWARE 4.2. and 4.4.

Post has been editedjemi - 05.04.15, 15:07



Rep: (3321)
FEATURES OF INSTALLING A KASTOMNOUS FIRMWARE 4.2. and 4.4.

Content:
Instructions for firmware 4.2.2 (JellyBean) via SP Flash Tool 5 and the restoration of "bricks"
Instructions for firmware 4.4.2 (Kitkat) via SP Flash Tool 5 and the restoration of "bricks"
Instructions for upgrading from version 4.2.2 (JellyBean) to version 4.4.2 (Kitkat) (stock & custom) + how to restore a brick

Instructions for firmware 4.2.2 (JellyBean) via SP Flash Tool 5 and the restoration of "bricks"
Creating a scatter file
What is a scatter file?
This is a text format file that describes the partitioning of the device’s internal memory into sections (PRELOADER, MBR, BOOTIMG, RECOVERY, ANDROID, USRDATE, etc.). It is used so that the flash program (for example, FlashTool) records the prepared images of one or several sections at the addresses specified in the scatter file, thereby not violating the original markup of the internal memory of the phone.
  • On the phone, we enable "USB debugging" in the phone (Menu-Settings-Applications-Development)
  • On the PC, launch MTK Droid Root & Tool
  • We connect the phone to the PC (in the program on the first tab should appear information about the phone!)
  • Click "Block Map"
  • Click "Create scatter file"

Install TWPR / CWM ClockworkMod recovery
For TWPR / CWM firmware, you must first download it. For factory firmware, a modified CWM is required.
After CWM firmware, you cannot reset to factory settings via the phone menu! This will result in a cyclic reboot, which can be cured only by flashing the native factory Recovery.
To enter CWM you needWhen the phone is off with the charging stuck, hold down the "ON" and "Volume +" keys.

What is ClockworkMod recovery (CWM)?
This is a modified unofficial recovery, which is available for most devices running Android. It has much more features than native recovery. On some devices it is installed instead of native recovery, on other devices it is installed in parallel. Allows:
  • Install unofficial firmware
  • Install add-ons and fixes
  • Connect to PC via USB in removable storage mode
  • Connect to PC via USB in ADB mode
  • Create a backup of both the entire firmware and its individual parts (system, settings, installed programs)
  • Recover data from previously created backup
  • Reset the data to the factory settings (Wipe - data / factory reset), clear the cache partition (wipe cache), clear the dalwick cache (wipe Dalvik-cache), clear the battery statistics (wipe battery stats)
  • Format and create partitions on a memory card

If you cannot turn on the phone and download android, you can always restore a previously created backup with all applications and settings via CWM.
Read moreClockworkMod recovery FAQ
What is TeamWin recovery (TWRP)?
TeamWin recovery (TWRP) - modified unofficial recovery, which is available for most devices running Android. It has much more features than native recovery. On some devices it is installed instead of native recovery, on other devices it is installed in parallel. Allows:
  • Install unofficial firmware
  • Install add-ons and fixes
  • Connect to PC via USB in removable storage mode
  • Connect to PC via USB in ADB mode
  • Create a backup of both the entire firmware and its individual parts (system, settings, installed programs)
  • Recover data from previously created backup
  • Reset the data to factory settings (Wipe - data / factory reset), clear the cache partition (wipe cache), clear the dalwick cache (wipe Dalvik-cache), clear the battery statistics (wipe battery stats)
  • Format and create partitions on a memory card

If you cannot turn on the phone and download android, you can always restore a previously created backup with all applications and settings via TWRP.
Read moreTWRP recovery FAQ
Install TWPR / CWM via Mobileuncle MTK Tools
  • Download the archive from TWPR / CWM and extract recovery.img to the root of the SD card.
  • Launch the Mobileuncle Tool.
  • Select "Recovery Update".
  • PS: If it does not find it, then you can try searching in the section "Firmware Update" ("Firmware Update")
  • We choose the previously thrown .img and agree with all the warnings.
  • Enjoying the stitched device
  • Installation in pictures look here
Jiayu G4S - Official firmware (OS 4.2.2)
Installing TWPR / CWM via Flashtool (via PC)
Jiayu G4S - Official firmware (OS 4.2.2)

It is important(!!!)
When installing CWM, in no case can you reset the phone via the "Backup and reset" settings menu item!
In this case, you will have a cyclic reboot (that is, the phone will go to endlessly repeated overload). In this case, the phone needs to install the factory recovery using a computer (ie, install the driver on the PC, and use the scatter file and Flashtool to flash the phone)
[/ color]
Attention for owners of factory firmware!
You must delete the file "recovery-from-boot.p"! This file "removes" non-native recovery with each reboot!
This requires ROOT and Root Explorer:
  • Go to the system directory
  • Click on the button R / W
  • Find the file recovery-from-boot.p and delete it.
Update / Install custom firmware
To flashing the phone, you first need to download the file of this firmware and drop it into the root of the SD card of the phone (Exception - update via "Software Update")
After flashing your device will be in Chinese. Remember in advance where you need to go to change the language!

Through "Software Update" in the phone programs
  • Download the archive with the desired firmware marked "... for" System Update ";
  • From the archive we take update.zip and put it in the root of the SD card of the phone;
  • Remove from the root of the phone card all folders with long names left over from previous firmware, if any;
  • We go into the program, run the "Software Update" and agree with the irreversibility;
  • Enjoy the stitched device.
Via Mobileuncle MTK Tools
  • Download the archive with the desired firmware and throw it into the root of the SD card.
  • Launch the Mobileuncle Tool.
  • Select "Firmware Update" ("Firmware Update").
  • Select the previously cast archive and agree with all the warnings.
  • Enjoying the stitched device
Through modified TWPR / CWM
TWRP recovery FAQ
ClockworkMod recovery FAQ
Normal CWM: Navigation to this recovery is due to the volume keys (up and down, respectively) and the phone's power key (selecting an item)
Touch CWM: Navigation to this recovery is due to the sensor.
  • Download the archive with the desired firmware and throw it into the root of the SD card.
  • We enter CWM (when the phone is turned off, hold down the "ON" and "Volume +" keys)
  • Making the Wipe system: select the items "Wipe data / factory reset" and "Wipe cahce partition"
  • ATTENTION! All personal data and installed programs will be lost! First, it’s better to do Backup with Titanium!
  • Go to the file selection menu: select the item "Install zip from sdcard", and in it the item "Choose zip from sdcard"
  • We find the previously archived firmware archive and select it.
  • Go back to the main menu and select
  • Normal CWM: select "Reboot system now"
  • Enjoying the stitched device
Instructions for flashing Jiayu G4S (L) and JiaYu G5S (L) smartphones via TWRP here Jiayu G4S - Official firmware (OS 4.2.2)


Post has been editedjemi - 12.08.15, 18:18



Rep: (3321)
EVERYTHING FOR SYSTEM APPLICATIONS JiaYu G4S (L)
DESCRIPTION, DELETE, X-KA, MANUALS, INSTRUCTIONS
JELLYBEAN 4.2.

AND ALSO SCRIPT REMOVAL OF SYSTEM APPLICATIONS TO FACILITATE THE SYSTEM!

Perhaps I'll start this important and relevant topic for everyone! Your kind words and advantages to your turnips have encouraged me to this =)
Not so long ago, with an android (3-4 years old), this is why there is not enough knowledge in some moments.
Please do not rush slippers, and culturally point to shortcomings!

The article refers directly toFAQ - Help newcomer!

Structure and purpose of folders and files in Android
The structure has a tree view. Any tree has a root, it also exists in UNIX / Linux. The root is the starting point in the file structure; from the root, the system is cluttered with folders and files. The root in UNIX / Linux is marked as a token: "/ "
/acct / - ???
/cache / - this section contains temporary files; more precisely, system updates are downloaded here.
/config / - ???
/custom / - ????
/data / - user section where installed applications are located; personal settings

More about the data section
/ data / app - here are installed applications, games
/data / app-lib - additional libraries needed for certain applications (present in new versions of Android)
/data / dalvik-cache - cache memory, for the work of Java machine Dalvik which is the “engine” in Android responsible for the launch and operation of applications.
/data / data - this folder contains individual settings for each user application, libraries and other files necessary files for their work.
/data / system / - this section contains system application settings
/dev/ - this section contains information about system devices and files
/proc/ - connected to the kernel, boot (unpacked boot) and with mount points, it is better not to touch it.
/root/ - ???
/sbchk/ - connected to the kernel, boot (unpacked boot) and with mount points, it is better not to touch it.
/sbin/ - connected to the kernel, boot (unpacked boot) and with mount points, it is better not to touch it.
/sys/ - ???

/system / - this section contains system folders and files necessary for Android operation.
More about the system section
/system / app - here are the system applications and services (in the new Android OS, service applications have been taken to another priv-app folder)
/system / bin and / system / xbin - folder contains files and links to executable binary files.
/system / xbin / su - the file is responsible for Root rights
/system / camerdata - this folder contains files responsible for the camera operation
/system / etc - in this folder are the configuration files required when booting the OS and also necessary during the work of various programs
/system / init.d - in this folder are scripts
/system / etc / hosts - the file is responsible for blocking, redirecting web addresses.
/system / etc / apns.conf - file with information about Internet access points (APN)
/system / etc / gps.conf - GPS settings
/system / fonts - folder with system fonts
/system / framework - folder with "processes" Android
/system / lib / - libraries of system applications and services
/system / lib / modules - system drivers
/system / media - folder with system sounds and inclusion animation
/system / media / bootanimation.zip - executable archive with boot animation
/system / priv-app - folder with Android services
/system / tts - folder with voice engines of the system
/system / build.prop - configuration file with which you can change the system settings
/proc- virtual section containing information about the kernel and its configuration
/mnt- in this section, memory cards and internal memory and other virtual partitions are mounted (added) (also in new versions you can find the storage section)
/storage- only real (existing, that is, non-virtual) memory cards and internal memory are mounted in this section

Learn more about mnt and storage.
All the files that you have on Android (pictures, ringtones, videos, documents) are recorded either on the internal memory or memory card. If Android has its own memory (internal memory), then it is mounted under the name /mnt / sdcard or / storage / sdcard . If there is no internal memory, then this name is occupied by the memory card. If there is both internal memory and a memory card, then the internal one remains under the name sdcard, and the memory card takes one of the names
sdcard2
external_sd
sdcard1
extSdCard
Residues, tails of programs
After deleting the program, we simply deleted the apk, we still need to delete its data.
To do this, and write this explanation.
So, parts of the programs can remain indata / data, data / dalvik-cache, system / lib, system / framework, system / ttsand some others. The system / lib folder is advised not to touch, because There are dependencies between libs and apk files. Here the file names do not always coincide with the name of the application. Be careful. And to find out the "internal" name of the program, you need to goRootExplorerin the folder where it lies, then a short tap on the apk file - click view and see the manifest. After deletion, it is advisable to make a HARD RESET (full reset, XP).

Everything is generally true here, but I want to clarify, if you do not plan on doing a hard reset after deleting the system programs, then yes you need to remove the "tails" from the specified sections of the system, but I would not advise you to do this removal method, it is difficult and you need to understand in the name of the programs.In the above sections, the programs are usually called not so much as in the system / app, it is better to make it easier, remove everything unnecessary from the system / app, and then make xp.And that's all, after xp, if the program is not in the system / app, it clearly will not put its data in the data section. But unfortunately, such a simple cleanup will not affect the system / lib. In this section, the "tails" will remain.

However, many and with a complex removal method do not climb into the system / lib. Since this is a really dangerous folder, there is almost no lib with an explicit name that can be deleted there. There are only two explicit names and associations with remote programs from the system / app, these are keyboard libraries. But sometimes,to find out which lib is tied to this or that program, you just need to open * .apk with WinRar and look in the lib folder (if it exists, which is rare in the system).

I will explain the "danger" of the system / lib folder. After removing some lib.so, if you restart the phone or make xp, the system (android) will not boot. On the phone screen, you will see a cyclic reboot (constant reboot). You can get out of this reboot either if you re-flash your phone, or via recovery mode with update.zip. In this archive there should be a remote library and creaks, with commands where to put this library. That's the danger of the system / lib folder
Actually LIST
Based on the rich information from the Internet, I collected the best. I checked it if possible. This list is fully applied to our smartphone. Infa sea in the internet, here I tried to systematize and assemble the entire info in one place. Tobish, some applications are described here, which are not in the stock firmware of our devices. But he did not dare to delete information about them. Thus, I can say with confidence that this is a complete and detailed list of programs in the open spaces. Naturally, with regard to Chinese MTK smartphones. I did not describe specific applications. I added a lot on my own.
Navigation:

The spoiler name is the name of the application file (apk, or apk + odex pairs)
NAME- those applications that are not yet finished (no description, etc., etc.)

Explanations directly in the spoiler :
The internal name of the application, then a dash, in quotes - "display name"
Application Description
- dependent applications and those in which the current occurs
* my comment
ActivityNetwork
com.android.ActivityNetwork - "Network Diagnose Tool"
Record network logs using tcpdump (as well as some tests, such as ping, etc.) on an sd card, to the / mnt / sdcard / mtklog / netlog folder,
called from the engineering menu, the item "SystemLog->NetLog or SystemLog>Common UI->[Network Test] "

- EngineerMode
* If you do not plan to use the testing functionality, you can delete it.
ApplicationsProvider
com.android.providers.applications - Search Provider
Provides a list of applications installed on the phone, needed for search queries
- GoogleQuickSearchBox
- QuickSearchBox

* not to delete, it is necessary for normal work
Atciservice
com.mediatek.atci.service - "Atci_serice"
Service providing access to FMRadio functions to GN_MMITest application
* if you do not plan to use the FM radio test from GN_MMITest - you can delete
BackupRestoreConfirmation
com.android.backupconfirm - ""
Prompts the user if an application attempts to back up / restore data
- framework (services.odex)
* removal at will
BatteryWarning
com.mediatek.batterywarning - "BatteryWarning"
Warns of battery charger over-voltage, battery temperature, charging too long, or low charge.
- System
- Engeener

* can be deleted
Bluetooth
com.android.bluetooth - "Bluetooth transmission"
* do not delete
Browser
com.android.browser - Browser
- Contacts
- DownloadProvider
- Email
- framework (framework.odex)
- Gallery2
- GMail
- GoogleQuickSearchBox
- LatinIME
- Launcher2
- Mms
- MTKAndroidSuiteDaemon
- Phonesky
- QuickSearchBox
- Stk1
- Stk2
- Talk
- VoiceSearch

* standard browser, if you use alternative - you can delete
Calculator
com.android.calculator2 - "Calculator"
* does not affect the operation of the system - deletion at will
Calendar
com.android.calendar - Calendar
- CalendarImporter
- CalendarProvider
- Email
- Exchange
- framework (framework.odex)
- GoogleCalendarSyncAdapter
- GoogleLoginService
- Launcher2
- MTKAndroidSuiteDaemon
CalendarImporter
com.mediatek.calendarimporter - "VCalendar"
- Calendar
- MtkBt

* I deleted it myself, the calendar works at the same time (but I do not use synchronization with either the computer or google account)
CalendarProvider
com.android.providers.calendar - "Calendar Memory"
- Calendar
- GoogleCalendarSyncAdapter

* do not delete if you use a calendar, it is necessary for its work
CDS_INFO
com.mediatek.connectivity - "Common Data Service"
Information about networks (GSM, WiFi), view configurations, interfaces,
the amount of data transferred, as well as the tests associated with it,
called from the engineering menu, the item "CDS Information"

- EngineerMode
- LocationEM

* test utility, if you do not plan to use - you can delete
Cellconnservice
com.mediatek.CellConnService - "CellConnectionService"
- Contacts
- Mms
- Phone
- Settings
- StkSelection

* it is better not to delete, it is necessary for normal operation (including something related to the choice of SIM)
Certinstaller
com.android.certinstaller - "Certificate Installer"
- framework (framework.odex)
- KeyChain
- Settings

* needed to install certificates from the SD card - deletion at will
ChromeBookmarksSyncAdapter
com.google.android.syncadapters.calendar - Google Calendar Sync
Synchronization of the bookmarks of the built-in browser with the Google service
- With other Google applications
* can be deleted
com.google.android.street
- see Maps_ * dpi
com.android.flip
com.android.flip - "how tokabaydanakitaykam"
Chinese operation manual
* can be deleted
For fun screenshots of this guide here
com.baidu.input
com.baidu.input - kakayataabaydanakitayskam
Combine consisting of a keyboard, search engine and cloud storage
* can be deleted
Contacts
com.android.contacts - "Phonebook"
- Calendar
- ContactsProvider
- Email
- Exchange
- framework (framework.odex)
- GoogleContactsSyncAdapter
- GoogleLoginService
- GoogleQuickSearchBox
- Launcher2
- Maps_hdpi
- Mms
- MTKAndroidSuiteDaemon
- MtkBt
- Phone
- QuickSearchBox
- Talk
- VoiceSearch

* not to delete, it is necessary for the phone to work
ContactsProvider
com.android.providers.contacts - "Contact Store"
* not to delete, it is necessary for the phone to work
DataTransfer
com.mediatek.datatransfer- "Backup"
Backup and restore (apk, contacts, calls, favorites backup)
* Does not affect the operation of other backup programs, you can delete
DataUsageLockScreenClient
something related to loxgrin! Unfortunately we could not figure it out!
*do not delete
DefaultContainerService
com.android.defcontainer - Package Access Wizard
- DownloadProvider
- framework (services.odex)
- Settings

* do not delete
Deskclock
com.android.deskclock - "Clock"
- framework (services.odex)
- MediaProvider
- VoiceSearch

* can be deleted
DownloadProvider
com.android.providers.downloads - "Download Manager"
- DownloadProviderUi
- framework (services.odex)

* it works through the download of applications from the market, when you click the "download" button, it is also used in a standard browser when downloading files, perhaps somewhere else - it is better not to delete
DownloadProviderUi
com.android.providers.downloads.ui - "Downloads"
- DownloadProvider
* graphic interface to the boot manager - it is better not to delete
DrmProvider
com.android.providers.drm - DRM Protected Content Storage
Email
com.android.email - "E-mail"
- CalendarImporter
- Contacts
- Exchange
- framework (services.odex)
- GN_ZoomClipView
- LatinIME
- Launcher2
- MediaUploader
- Mms
- MtkBt

* can be deleted
EngineerMode
com.mediatek.engineermode - "EngineerMode"
- ActivityNetwork
- framework (services.odex)
- InternalEngineerMode
- MobileLog
- ModemLog
- Phone
- Settings

* engineering menu, if you do not plan to use it is better not to delete
EngineerModeSim
com.android.simmelock - "EM SIM ME Lock"
Management of SIM-card locks, called from the engineering menu, the item "SIMMeLock"
- EngineerMode
* when deleting, the corresponding item "SIMMeLock" does not work, the rest of the functionality works
Exchange
com.android.exchange - Exchange Services
- CalendarImporter
- CalendarProvider
- Contacts
- Email

* needed to work with mail through the Exchange protocol, if you do not plan to use it, you can delete it
Facelock
com.android.facelock - "Face Control"
- framework (framework.odex)
- Settings

* One of the screen lock methods, if you do not plan to use it, you can delete it.
FactoryMode
com.mediatek.factorymode - "FactoryMode"
Engineering test program (test menu), which is called via * # 59 # in the native dialer.
* can be removed without serious consequences
Filemanager
com.mediatek.filemanager - "File Manager"
Regular file manager
* you can delete
Fusedlocation
com.android.location.fused - "FusedLocation"
GPS system from Google. There is information that the phone will not boot without this application.
*do not delete
FMRadio
com.mediatek.FMRadio - "FM Radio"
- AtciService
- EngineerMode
- framework (framework.odex, services.odex)
- GN_MMITest
- Music

* FM radio - better to leave
Galaxy4
com.android.galaxy4 - Black Hole
live wallpaper option
Gallery2
com.android.gallery3d - Gallery
standard gallery
- Launcher2
- MediaProvider

* if you do not plan to use it, you can delete it (BUT it is not recommended! You can use a third-party viewer, for example, QuickPic)
Gmail
com.google.android.gm - "Gmail"
- EngineerMode
- EngineerModeSim
- LatimIME
- Launcher2
- MediaUploader
- Talk
- VoiceSearch

* if you do not plan to use - you can delete
Gmscore
com.google.android.gms - Google Play Services
Google Play services.
* deletion will lead to the inoperability of most Google applications.
GoogleBackupTransport
com.google.android.backup - "Google Backup Transport"
- Calendar
- framework (services.odex)
- GoogleLoginService

* I deleted myself, the market and YouTube are working
GoogleCalendarSyncAdapter
com.google.android.syncadapters.calendar - "Google Calendar Sync"
Synchronization of the calendar with Google account
* if you do not plan to use - you can delete
GoogleContactsSyncAdapter
com.google.android.syncadapters.contacts - "Google Contacts Sync"
Synchronization of contacts with Google account
* if you do not plan to use - you can delete
GoogleEars
Audio Search on Google Play.
* you can delete
GoogleFeedback
com.google.android.feedback - "Market Feedback"
Sending bug reports to Google (maybe some other functionality)
- GoogleServicesFramework
- Phonesky

* I deleted myself, the market and YouTube are working
GoogleLoginService
com.google.android.gsf.login - Google Accounts
Google account support
- GoogleServicesFramework
- GoogleTTS
- MediaUploader
- SetupWizard
- YouTube

* it is necessary for the Market and SetupWizard to work, if you reset the phone, the SetupWizard that started when it is first turned on will drop at the next step and the phone will remain in this state neither close nor do anything with it, you can say it is necessary for work, not delete
GooglePartnerSetup
com.google.android.partnersetup - "Setting up a Google Partner"
- Browser
- GoogleQuickSearchBox

* A terrible tool, presumably for rolling applications with the knowledge of Google unnoticed by the user, I deleted it myself in the first place, the functionality I needed was not affected
GoogleQuickSearchBox
com.google.android.googlequicksearchbox - Google Search
Google search, as well as a "non-removable" desktop search widget
- Browser
- Maps_hdpi
- VoiceSearch

* I deleted from myself, I use the search from the browser, and the search string from the desktop disappears, deletion at will
GoogleServicesFramework
com.google.android.gsf - "Google Services Framework"
- gmail
- GoogleBackupTransport
- GoogleCalendarSyncAdapter
- GoogleContactsSyncAdapter
- GoogleFeedback
- GoogleLoginService
- GooglePartnerSetup
- GoogleQuickSearchBox
- GoogleTTS
- Maps_hdpi
- MediaUploader
- NetworkLocation
- Phonesky
- Settings
- SetupWizard
- Talk
- VoiceSearch
- YouTube

* As far as I understand the transport aplica, from google services without it only YouTube works, if you need a market - we leave
GoogleTTS
com.google.android.tts - Google Speech Synthesizer
- Maps_hdpi
* if you do not plan to use - you can delete
HoloSpiralWallpaper
com.android.wallpaper.holospiral - "Holographic Spirals"
* option "live wallpaper", if you do not plan to use this option - you can delete
HTMLViewer
com.android.htmlviewer - "HTMLViewer"
HTML viewer
* if you do not plan to use it, you can delete it, but it can be convenient to save the html file (as well as directly from apk) to view it with the help of this tool, and not through the browser
InputDevices
com.android.inputdevices - "Input Devices"
Something related to keyboard layout.
*do not delete
Keychain
com.android.keychain - "Main chain"
- framework (framework.odex)
LatinIME
com.android.inputmethod.latin - "Android Keyboard"
- framework (framework.odex)
- Maps_hdpi
- SettingsProvider

* delete only if there is an alternative and it is also systemic! but even with the installed alternative, it is better not to delete this, to avoid problems when resetting the phone to factory settings
Launcher2
com.android.launcher - "Launcher"
- Browser
- EngineerMode
- framework (services.odex)
- GoogleQuickSearchBox
- Maps_hdpi
- MtkWorldClockWidget
- Phonesky
- QuickSearchBox
- Settings
- VoiceSearch

* standard launcher (desktop and list of applications / widgets); similar to clave. It is necessary for normal operation, it is better to leave it even if you use an alternative one (to avoid problems after collecting data on factory data)
LiveWallpapers
com.android.wallpaper - "Android Live Wallpaper"
- framework (framework.odex, services.odex)
* A standard set of "live wallpaper": water, galaxy, neurons, polar clock, grass. if you do not plan to use - you can delete
LiveWallpapersPicker
com.android.wallpaper.livepicker - "Live Wallpaper Catalog"
* the choice of live wallpaper, it is better to leave - if you plan to use though some kind of "live wallpaper", if not - you can delete
LocationEM
com.mediatek.lbs.em - "Location Engineer Mode"
GPS status (AGPS, EPO), tests and settings related to this, is called from the engineering menu, item "LocationBasedService"
- EngineerMode
* if you do not plan to use - you can delete
MagicSmokeWallpapers
com.android.magicsmoke - "Magic Smoke"
* option "live wallpaper", if you do not plan to use this option - you can delete
Maps _ ** dpi (Google Maps, possibly another name)
com.google.android.apps.maps - Maps
- Gallery2
- GooglePartnerSetup
- GoogleQuickSearchBox
- VoiceSearch

* if you do not plan to use or use alternative (Yandex, Navitel, iGo) - you can delete it (provided that you don’t use Google+, etc. gugloservisy)
MediaProvider
com.android.providers.media - "Multimedia Storage"
At a minimum, access to data on a flash drive (maybe something else)
- DownloadProvider
- framework (services.odex)

* If you remove any application does not access the data on the flash card through a standard API, it is necessary for normal operation, do not delete
MediaTekLocationProvider
com.android.networklocationservice - "MediaTekLocationProvider"
Used most likely to determine the location of the mobile network
- LocationEM
- Engeneer

*do not delete
MediaUploader
com.google.android.apps.uploader - My Downloads
- YouTube
* used by YouTube to upload your video to the server, if you do not plan to use this functionality, you can delete it
Mms
com.android.mms - SMS / MMS
- Contacts
- framework (framework.odex, services.odex)
- Gallery2
- GoogleQuickSearchBox
- LatinIME
- Launcher2
- MTKAndroidSuiteDaemon
- Omacp
- Phone
- Settings
- SystemUI
- VoiceSearch
MobileLog
com.mediatek.mobilelog - "MobileLog"
Writes the radio logs of the radio module (GSM, bluetooth, etc.) to the sd card, to the / mnt / sdcard / mtklog / mobilelog folder, called from the engineering menu, the item "SystemLog->MobileLog "or" SystemLog->Common UI->[Mobile
Log] "

- EngineerMode
- framework (framework.odex, services.odex)

* test utility, if you do not plan to use - you can delete
ModemLog
com.mediatek.mdlogger - "ModemLog"
Writes logs to the sd card, to the folder / mnt / sdcard / mtklog / mdlog, called from the engineering menu, the item "SystemLog->ModemLog "or
"SystemLog->Common UI->[Modem Log] "

- EngineerMode
- framework (framework.odex)

* test utility, if you do not plan to use - you can delete
MTKAndroidSuiteDaemon
(MTKAndroidSuiteDaemon)
com.mediatek.apst.target - "MTK Android Suite Daemon"
- framework (services.odex)
* Something related to synchronization with the computer, apparently a utility from MTK, if you do not plan to use it, you can delete it
Mtkbt
com.mediatek.bluetooth - "Bluetooth"
- framework (framework.odex, services.odex)
- Music
- Settings

* required for bluetooth operation, do not delete
MTKThermalManager
com.mediatek.thermalmanager - "MTK Thermal Manager"
telephone temperature monitoring service
- InternalEngineerMode
* I think it is better not to delete
MtkWorldClockWidget
com.mediatek.appwidget.worldclock - World Clock
* widget, if you do not plan to use - you can delete
Music
com.android.music - "Music"
Standard audio player
- AtciService
- FMRadio
- framework (framework.odex, services.odex)
- Gallery2
- GN_Camera
- GN_SoundRecorder
- GoogleQuickSearchBox
- Launcher2
- MediaProvider
- Mms
- Settings
- VisualizationWallpapers
Musicfx
com.android.musicfx - "MusicFX"
Sound effects support, equalizer
- Settings
- Music

* You can remove, but better to replace, for example Viper4Android
Networklocation
com.google.android.location - "Network Location"
- framework (services.odex)
- LocationEM
- Maps_hdpi
- Settings

* I have deleted something related to determining the approximate location of the cell towers (LBS) in my home - Yandex determines this on its own, deletion at will
Noisefield
com.android.noisefield - "Bubbles"
* option "live wallpaper", if you do not plan to use this option - you can delete
Omacp
com.mediatek.omacp - ""
- Browser
- Email
- Exchange
- MediaProvider
- Mms
- Settings

* do not delete, something related to the application of the settings sent in the SMS, and not only (as when deleting, it seems, the settings of the APN seem to fall off -
mobile internet)
PackageInstaller
com.android.packageinstaller - "Package Installer"
*do not delete
PermissionControl
com.mediatek.security - ""
Access control ??
* can be deleted
Phasebeam
com.android.phasebeam - "Phase beam"
* option "live wallpaper", if you do not plan to use this option - you can delete
Phone
com.android.phone - "Phone"
- CDS_INFO
- CellConnService
- Contacts
- EngineerMode
- framework (android.policy.odex, framework.odex, services.odex)
- GN_MMITest
- GoogleLoginService
- Mms
- Settings
- SetupWizard
- Stk1
- Stk2
- StkSelection
- TelephonyProvider

* caller itself, do not delete
Phonesky
com.android.vending - Google Play Store
- GoogleLoginService
- GooglePartnerSetup
- GoogleServicesFramework
- Launcher2
- Maps_hdpi
- YouTube

* Optionally, you can delete if you do not use the market
Picots
com.svox.pico - "Pico TTS"
Text to Speech, Pronunciation
- framework (framework.odex)
- Maps_hdpi

* if you do not plan to use - you can delete
Pink
One of the themes
- ThemeChooser
- ThemeManager

* can be deleted
Protips
com.android.protips - "Home Screen Management Tips"
- Launcher2
* if you do not plan to use - you can delete
Provision
com.android.provision - ""
Saves the setting that the device was prepared (worked SetupWizard)
* Without it, for some reviews, everything works fine, for others it does not. In any case, as far as JiaYu is concerned, it is better not to delete it, without it, when you download the firmware, the home button, the usb connection, and the top menu do not work.
Quicksearchbox
com.android.quicksearchbox - "Search"
- Browser
- VoiceSearch

* if you do not plan to use - you can delete
Ringdroid
com.zzz.ringdroid - "Ringdroid Program"
Whether a set of custom tunes, or once there was an application for trimming tunes
* In case of deletion after installation of custom melodies, there may be errors - it is not recommended to delete
SchedulePowerOnOff
com.mediatek.schpwronoff - "Schedule On / Off"
Manager on / off the phone on a schedule.
*do not delete
Settings
com.android.settings - Parameters
- CertInstaller
- DeskClock
- EngineerMode
- framework (android.policy.odex, framework.odex, secondary_framework.odex, services.odex)
- GoogleLoginService
- GoogleTTS
- Launcher2
- LocationEM
- MediaProvider
- Mms
- PackageInstaller
- Phone
- SetupWizard

* not to delete, it is necessary for normal operation of the phone
SettingsProvider
com.android.providers.settings - "Settings Store"
- framework (framework.odex, services.odex)
- GoogleBackupTransport

* not to delete, it is necessary for normal operation of the phone
SetupWizard
com.google.android.setupwizard - “Setup Wizard”
Initial device setup
- framework (android.policy.odex, framework.odex)
- LatinIME
- Provision

* better not to delete, without it everything works until the first reset of the phone to
factory settings, after resetting the settings can be done manually
SharedStorageBackup
com.android.sharedstoragebackup - ""
Something related to backup
- framework (services.odex)
* I deleted myself, I use backup via recovery
Sky
One of the themes
- ThemeChooser
- ThemeManager

* can be deleted
Soundrecorder
com.android.soundrecorder - "Voice Recorder"
Standard voice recorder. There are alternatives.
*can be deleted
Stk1
com.android.stk - SIM Menu
- Launcher2
- Phone
- StkSelection

* not to delete, it is necessary for the phone to work
Stk2
com.android.stk2 - "Tools on SIM"
- Launcher2
- Phone
- StkSelection

* not to delete, it is necessary for the phone to work
Stkselection
com.mediatek.StkSelection - "SIM Menu"
* not to delete, it is necessary for the phone to work
SystemUI
com.android.systemui - "Graphical System Interface"
Top bar with status bar, network icons, battery and clock, curtain
- framework (android.policy.odex, framework.odex, services.odex)
- Settings

* not to delete, it is necessary for the phone to work
Talk
com.google.android.talk - "Google Talk"
- framework (services.odex)
- GoogleServicesFramework
- LatinIME

* if you do not plan to use - you can delete
TelephonyProvider
com.android.providers.telephony - "Number Memory / SMS / MMS"
- Mms
- Phone
- Contacts

* not to delete, it is necessary for the phone to work

ThemeChooser

Theme manager

Todos
com.mediatek.todos - "Tasks"
Assignment schedule
* can be deleted
Torch
net.cactii.flash2 - "Flashlight"
Standard flashlight
* can be deleted
UpdateSystem
com.mediatek.updatesystem - "System Update"
Update via update.zip, which you need to throw on the memory card and flash through the standard stock recovery
* need to remove a meaningless application, because all custom firmware is installed only through custom recovery
UserDictionaryProvider
com.android.providers.userdictionary - "User Dictionary"
* better to leave
VideoEditor
com.android.videoeditor - "Video Editor"
Standard video editor
* can be deleted
VideoF-00-00
Featured Videos
* delete, similar to the previous one
VideoPlayer
Video player
* delete, along with the previous two
VisualizationWallpapers
com.android.musicvis - "Backgrounds: Audio Visualization"
* option "live wallpaper", if you do not plan to use this option - you can delete
Voicecommand
com.mediatek.voicecommand - "VoiceCommand"
Voice commands.
*at one's own risk
Voiceunlock
com.mediatek.voiceunlock - Voice Enabled
Unlock screen voice.
* better not to delete
Voicesearch
com.google.android.voicesearch - "Voice Search"
In addition to voice search, provides voice input.
- gmail
- GooglePartnerSetup
- GoogleQuickSearchBox
- LatinIME

* if you do not plan to use - you can delete
VpnDialogs
com.android.vpndialogs - "VpnDialogs"
- framework (framework.odex)
* do not delete
WallpaperChooser
com.android.wallpaper.multipicker - "Wallpaper"
Select wallpaper for your desktop and lock screen.
* it is possible to delete, but it is desirable to replace it with an analogue, because there may be problems in the work of background images
Ygsp
com.mediatek.ygps - "YGPS"
Test utility, shows the state of GPS, is called from the engineering menu, the item "YGPS"
- EngineerMode
- LocationEM

*do not delete
As for the lib folder and some other
FOR MORE EXPERIENCES, OTHER BECAP!
As I indicated above, to completely remove certain files, you must also delete tails.
And so, in folders ...
system \ bin
bugmailer.sh
bugreport
send_bug
mobile_log_d
system \ framework
(all of the following is related to GOOGLE)
com.google.android.maps.jar
com.google.android.media.effects.jar
com.google.widevine.software.drm.jar
send_bug.jar
system \ lib
Shared applications and related files
MobileLog.apk
libmobilelog_jni.so
/ system / bin / mobile_log_d
From standard video editor (VideoEditor)
libvideoeditor_core.so
libvideoeditor_jni.so
libvideoeditor_osal
libvideoeditorplayer.so
libvideoeditor_videofilters.so
FM radio (FMRadio.apk)
libfmjni.so
Standard Gallery + Camera (Gallery2.apk)
libjni_eglfence.so
libjni_mosaic.so
The application "Favorite videos" (VideoF favorites.apk)
libjtranscode.so
We also delete the folder of unnecessary video examples / system / media / video /
And from / system / usr / srec / en-US / you can delete offline voice input files (English only)
/ system / usr / srec / en-US / acoustic_model
/ system / usr / srec / en-US / clg
/ system / usr / srec / en-US / g2p_fst
/ system / usr / srec / en-US / offensive_word_normalizer
/ system / usr / srec / en-us / rescoring_lm
All that is connected with Google applications (gapps, gaps, Google Apps), and from it depends.
General:
libvcdecoder_jni.so
libgoogle_recognizer_jni_l.so
libgames_rtmp_jni.so
libAppDataSearch.so
libvorbisencoder.so
libvoicerecognition.so
libvoicerecognition_jni.so
libplus_jni_v8.so - Google Plus
librs.antblur.so
librs.antblur_constant.so
librs.antblur_drama.so
librs.drama.so
librs.film_base.so
librs.fixedframe.so
librs.grey.so
librs.image_wrapper.so
librs.retrolux.so
librsjni.so
libRSSupport.so
libstg-engine.so
Google talk
libgtalk_jni.so
libgtalk_stabilize.so
libvideochat_jni.so
libvideochat_stabilize.so
Google Drive
libandroid_ndk1.so
libdocsimageutils.so
Google+
libgcomm_jni.so
Chrome browser
libchromeview.so
Keyboard LatinIME.apk
libjni_latinime.so
Face lock (FaceLock.apk)
libfacelock_jni.so
libfilterpack_facedetect.so
And you can also delete face recognition libraries / system / vendor / pittpatt /
PicoTts voice engine
libttscompat.so
libttspico.so
Languages ​​for PicoTts: delete the folder / system / tts
Google Voice Search (Velvet.apk)
libgoggles_clientvision.so
libgoogle_recognizer_jni_l.so
BaiduInput
libBdMoplusMD5_V1.so
libBDVoiceRecognitionClient_V1.so
libchiperencoder_v1_2_1.so
libmtprocessor-jni.so
libkpencore.so
librabjni-1.so
libshare_v2.so
libtmfe30.so
system \ res
res
system \ tts
tts
system \ vendor
operator
pittpatt

Files of stock deodexed firmware (* .apk, build.prop, framework, lib, etc.)
stok_g4s_09.06.2014_deodex -https://yadi.sk/d/fNBmcLo3beLFZ
stok_g4s_10.04.2014_deodex -https://yadi.sk/d/IM0XZJsKbeLGH
stok_g4s_18.04.2014_deodex -https://yadi.sk/d/YlCR3ldkbeLHW
stok_g4s_22.04.2014_deodex -https://yadi.sk/d/j-HjR1gMbeLJK
stok_g4sL_18.06.2014_deodex -https://yadi.sk/d/IPv2Jw51beLKJ
stok_g4sw_06.09.2014_deodex -https://yadi.sk/d/q7-S-PXNbhiwq
SHARED FOLDER
Removing unnecessary ("harmful") Chinese programs from the system
Removing unnecessary ("harmful") Chinese programs from the system:
  1. using ES Explorer
    • We give root ES - Functions button - Tools - Root-conductor - ON
    • Remove recovery-from-boot.p if there is
    • Go further button Functions - Tools - Application Manager - System - Remove unnecessary
    • We delete some "problem" programs on the system / app path:
    • com.UCMobile.apk (Chinese browser);
    • PinyinIME.apk and PinyinIME.odex (Chinese keyboard);
    • SmsReg.apk and SmsReg.odex (there is confirmation that this service sends SMS to Chinese numbers by itself);
    • MobileLog.apk, ModemLog.apk, ModemLog.odex.
    • Also read this post necessarily [/ b] -Jiayu G4S - Official firmware (OS 4.2.2) (Post # 34284417)
    • Enjoying a clean device

  2. Using MTK Droid Root & Tools

    • Launch MTK Droid Root & Tool and connect your phone to PC via USB
    • We are waiting for the information on the phone to appear in the program on the first tab.
    • Select the tab "root, bacup, recovery"
    • Press the "ROOT" button
    • On the phone in the lower right corner, select the item "Restore data" and wait until the phone restarts (After rebooting, the phone can slow down! This is normal and lasts until the first reboot of the phone)
    • Reconnect the USB cable to the phone
    • If everything went smoothly in the lower left corner there should be a green rectangle with the inscription
    • In MTK Droid Root & Tool, click the button "Delete china" and agree with the removal of programs
      PS: Deleting files from the phone will be in accordance with the list of files_for_delete.txt in the program folder!
    • Click the "Reboot" button and in the dialog box that appears, click the "Reload" button
    • Enjoying a clean device
Script to remove unnecessary programs
I decided to bungle a script that removes most of the unnecessary programs.
And so is version 1.FULL!
Plans to makebasic & standart version!

FULL: Attached fileRemoVing_Script_by_jemi_v_1.zip (124.41 KB)
ui_print ("--->DELETING SOFT 1 STEP ");
delete ("/ system / app / AtciService.apk");
delete ("/ system / app / AtciService.odex");
delete ("/ system / app / BackupRestoreConfirmation.apk");
delete ("/ system / app / BackupRestoreConfirmation.odex");
delete ("/ system / app / BaiduInput.apk");
delete ("/ system / app / BasicDreams.apk");
delete ("/ system / app / BatteryWarning.apk");
delete ("/ system / app / Browser.apk");
delete ("/ system / app / Browser.odex");
delete ("/ system / app / CDS_INFO.apk");
delete ("/ system / app / CDS_INFO.odex");
delete ("/ system / app / CellBroadcastReceiver.apk");
delete ("/ system / app / ChromeBookmarksSyncAdapter.apk");
delete ("/ system / app / com.android.flip.apk");
delete ("/ system / app / com.baidu.input.apk");
delete ("/ system / app / com.google.android.street.apk");
delete ("/ system / app / DataTransfer.apk");
delete ("/ system / app / DataTransfer.odex");
delete ("/ system / app / Deskclock.apk");
delete ("/ system / app / Deskclock.odex");

ui_print ("--->DELETING SOFT 2 STEP ");
delete ("/ system / app / DrmProvider.apk");
delete ("/ system / app / Email.apk");
delete ("/ system / app / Email.odex");
delete ("/ system / app / Exchange2.apk");
delete ("/ system / app / Exchange2.odex");
delete ("/ system / app / FaceLock.apk");
delete ("/ system / app / FileManager.apk");
delete ("/ system / app / FileManager.apk");
delete ("/ system / app / FileManager.odex");
delete ("/ system / app / FileManager.odex");
delete ("/ system / app / Galaxy4.apk");
delete ("/ system / app / Galaxy4.odex");
delete ("/ system / app / Gallery4.apk");
delete ("/ system / app / Gallery4.odex");
delete ("/ system / app / GoogleBackupTransport.apk");
delete ("/ system / app / GoogleBackupTransport.odex");
delete ("/ system / app / GoogleFeedback.apk");
delete ("/ system / app / GoogleTTS.apk");
delete ("/ system / app / HoloSpiralWallpaper.apk");
delete ("/ system / app / HoloSpiralWallpaper.odex");

ui_print ("--->DELETING SOFT 3 STEP ");
delete ("/ system / app / KeyChain.apk");
delete ("/ system / app / LiveWallpapers.apk");
delete ("/ system / app / LiveWallpapers.odex");
delete ("/ system / app / LiveWallpapersPicker.apk");
delete ("/ system / app / LiveWallpapersPicker.odex");
delete ("/ system / app / MagicSmokeWallpapers.apk");
delete ("/ system / app / MagicSmokeWallpapers.odex");
delete ("/ system / app / MediaTekLocationProvider.apk");
delete ("/ system / app / MediaUploader.apk");
delete ("/ system / app / MobileLog.apk");
delete ("/ system / app / ModemLog.apk");
delete ("/ system / app / MTKAndroidSuiteDaemon.apk");
delete ("/ system / app / MTKAndroidSuiteDaemon.odex");
delete ("/ system / app / MTKLogger.apk");
delete ("/ system / app / MTKThermalManager.apk");
delete ("/ system / app / MtkWeatherProvider.apk");
delete ("/ system / app / MtkWeatherProvider.odex");
delete ("/ system / app / MtkWorldClockWidget.apk");
delete ("/ system / app / MtkWorldClockWidget.odex");
delete ("/ system / app / NoiseField.apk");
delete ("/ system / app / NoiseField.odex");

ui_print ("--->DELETING SOFT 4 STEP ");
delete ("/ system / app / PhaseBeam.apk");
delete ("/ system / app / PhaseBeam.odex");
delete ("/ system / app / PhotoTable.apk");
delete ("/ system / app / PicoTts.apk");
delete ("/ system / app / PicoTts.odex");
delete ("/ system / app / PinyinIME.apk");
delete ("/ system / app / Protips.apk");
delete ("/ system / app / Protips.apk");
delete ("/ system / app / Protips.odex");
delete ("/ system / app / Protips.odex");
delete ("/ system / app / SearchBox.apk");
delete ("/ system / app / SetupWizard.apk");
delete ("/ system / app / SetupWizard.odex");
delete ("/ system / app / SmsReg.apk");
delete ("/ system / app / SmsReg.odex");
delete ("/ system / app / sogouinput.apk");
delete ("/ system / app / Stk1.apk");
delete ("/ system / app / Stk1.odex");
delete ("/ system / app / StkSelection.apk");
delete ("/ system / app / StkSelection.odex");

ui_print ("--->DELETING SOFT 5 STEP ");
delete ("/ system / app / SystemUpdate.apk");
delete ("/ system / app / SystemUpdateAssistant.apk");
delete ("/ system / app / TaskManager2.apk");
delete ("/ system / app / Todos.apk");
delete ("/ system / app / Todos.odex");
delete ("/ system / app / UpdateSystem.apk");
delete ("/ system / app / UpdateSystem.apk");
delete ("/ system / app / UpdateSystem.odex");
delete ("/ system / app / UpdateSystem.odex");
delete ("/ system / app / VideoF favorites.apk");
delete ("/ system / app / VideoF favorites.odex");
delete ("/ system / app / VideoPlayer.apk");
delete ("/ system / app / VideoPlayer.odex");
delete ("/ system / app / VisualizationWallpapers.apk");
delete ("/ system / app / VisualizationWallpapers.odex");
delete ("/ system / app / VoiceCommand.apk");
delete ("/ system / app / VoiceUnlock.apk");
delete ("/ system / app / VoiceUnlock.apk");
delete ("/ system / app / VoiceUnlock.odex");
delete ("/ system / app / VoiceUnlock.odex");
delete ("/ system / app / YunYingyong.apk");

ui_print ("--->DELETING SOFT 6 STEP ");
delete ("/ system / framework / com.google.android.maps.jar");
delete ("/ system / framework / com.google.android.media.effects.jar");
delete ("/ system / framework / com.google.widevine.software.drm.jar");
delete ("/ system / framework / send_bug.jar");

ui_print ("--->DELETING LIBS & OTHER TAILS ");
ui_print ("--->DELETING LIB BaiduInput.apk ");
delete ("/ system / bin / bugmailer.sh");
delete ("/ system / bin / bugreport");
delete ("/ system / bin / send_bug");
delete ("/ system / bin / mobile_log_d");

ui_print ("--->DELETING LIB: MobileLog ");
delete ("/ system / lib / libmobilelog_jni.so");

ui_print ("--->DELETING LIB: VideoEditor ");
delete ("/ system / lib / libmobilelog_jni.so");
delete ("/ system / lib / libvideoeditor_core.so");
delete ("/ system / lib / libvideoeditor_jni.so");
delete ("/ system / lib / libvideoeditor_osal");
delete ("/ system / lib / libvideoeditorplayer.so");
delete ("/ system / lib / libvideoeditor_videofilters.so");

ui_print ("--->DELETING LIB: FMRadio ");
delete ("/ system / lib / libfmjni.so");

ui_print ("--->DELETING LIB: Gallery2 ");
delete ("/ system / lib / libjni_eglfence.so");
delete ("/ system / lib / libjni_mosaic.so");

ui_print ("--->DELETING LIB: VideoF.41 ");
delete ("/ system / lib / libjtranscode.so");

ui_print ("--->DELETING LIB: BaiduInput.apk ");
delete ("/ system / lib / libchiperencoder_v1_2_1.so");
delete ("/ system / lib / libBdMoplusMD5_V1.so");
delete ("/ system / lib / libBDVoiceRecognitionClient_V1.so");
delete ("/ system / lib / libmtprocessor-jni.so");
delete ("/ system / lib / libkpencore.so");
delete ("/ system / lib / librabjni-1.so");
delete ("/ system / lib / libshare_v2.so");
delete ("/ system / lib / libtmfe30.so");

ui_print ("--->DELETING LIBS: Google Apps ");
ui_print ("--->Others ");
delete ("/ system / lib / libvcdecoder_jni.so");
delete ("/ system / lib / libgoogle_recognizer_jni_l.so");
delete ("/ system / lib / libgames_rtmp_jni.so");
delete ("/ system / lib / libAppDataSearch.so");
delete ("/ system / lib / libvorbisencoder.so");
delete ("/ system / lib / libvoicerecognition.so");
delete ("/ system / lib / libvoicerecognition_jni.so");
delete ("/ system / lib / libplus_jni_v8.so");
delete ("/ system / lib / librs.antblur.so");
delete ("/ system / lib / librs.antblur_constant.so");
delete ("/ system / lib / librs.antblur_drama.so");
delete ("/ system / lib / librs.drama.so");
delete ("/ system / lib / librs.film_base.so");
delete ("/ system / lib / librs.fixedframe.so");
delete ("/ system / lib / librs.grey.so");
delete ("/ system / lib / librs.image_wrapper.so");
delete ("/ system / lib / librs.retrolux.so");
delete ("/ system / lib / librsjni.so");
delete ("/ system / lib / libRSSupport.so");
delete ("/ system / lib / libstg-engine.so");

ui_print ("--->Google Talk ");
delete ("/ system / lib / libgtalk_jni.so");
delete ("/ system / lib / libgtalk_stabilize.so");
delete ("/ system / lib / libvideochat_jni.so");
delete ("/ system / lib / libvideochat_stabilize.so");

ui_print ("--->Google.Drive ");
delete ("/ system / lib / libandroid_ndk1.so");
delete ("/ system / lib / libdocsimageutils.so");

ui_print ("--->Google+ ");
delete ("/ system / lib / libgcomm_jni.so");

ui_print ("--->Chrome ");
delete ("/ system / lib / libchromeview.so");

ui_print ("--->LatinIME ");
delete ("/ system / lib / libjni_latinime.so");

ui_print ("--->FaceLock ");
delete ("/ system / lib / libfacelock_jni.so");
delete ("/ system / lib / libfilterpack_facedetect.so");

ui_print ("--->PicoTts ");
delete ("/ system / lib / libttscompat.so");
delete ("/ system / lib / libttspico.so");

ui_print ("--->Velvet ");
delete ("/ system / lib / libgoggles_clientvision.so");
delete ("/ system / lib / libgoogle_recognizer_jni_l.so");

ui_print ("--->DELETING SOFT 8 STEP ");
delete_recursive ("/ system / tts /");
delete_recursive ("/ system / media / images");
delete_recursive ("/ system / media / video");
delete_recursive ("/ system / mobile_toolkit /");
delete_recursive ("/ system / res /");
delete_recursive ("/ system / secro /");
delete_recursive ("/ system / vendor / operator /");
delete_recursive ("/ system / vendor / pittpatt /");
delete_recursive ("/ system / media / video /");
delete_recursive ("/ system / usr / srec / en-US /");

BASIC:
STANDART:

Resources used

Thanks in PM
Thank, say thank you, give a beer, ice cream, chocolate or bread with student mayonnaise, as well as about the use of the information that is laid out here, contactHERE!


Post has been editedjemi - 05.04.15, 01:16



Rep: (3321)
All about sound
Here I will gradually collect manuals, tips, patches with instructions, as well as ideas on sound and its improvement.
And so, there was a lot of discussion about the sound ... If anyone is interested in reading about all these demagogues, then I ask in related topics, especially intopic of discussionand through the search in the topic for the keywords "sound", "Yamaha" and so on. etc. looking for what you need. Here I will try to collect / give / give specific advice
Should be read
You are here 2-3 people who are not enough bass and dissatisfied with the sound of our phone! Either you are too sophisticated in the ear for music, or your phones with sound marriage.
I already wrote here earlier that everyone has different perceptions of sound. And that the sound in any headphones, that for $ 1, that for $ 300, must be tuned differently.
Today I specifically checked (tuned and compared) the sound of Sony Xperia Z1c, Nexus5, Fly 440, Acer A511 and our g4s (jet + Viper4A) - the sound is almost the same. And this is more than enough for me to listen to music on the road.
Well, for fans of pure sound with perfect frequency response, I advise you not to buy Chinese (as you like to say), but a decent phone or player is 3-5 times more expensive!
$ iLence @ 08/10/2014, 00:32*
I will not write many clever and cunning words. To whom it is boring - let him put the RMAA on the studio and measure. I did not set such a goal. He promised subjectivity - here she is. And in the pursuit of super-sound, you obviously didn’t go there. To rant about the right tracks for testing and bitrate - to the special forums. I can tell and show the way
Actually.
While the bullet was being drawn, I quickly flaced two phones. Its "old" Zopo C2 and, since I got my hand on the Lenovo A820.
Bottom line: with the 820th, we are in complete parity. With ZOPO C2 (whose Yamaha is a refinement for those who are not able to read one page back) - we are also in full parity. BUT!!
Up to about 70-80% volume. But then - zopo "opens." Sharply and even somewhere stunning. Literally - an explosion. And our cheater simply increases the volume. Though it is uncomfortable for me to listen at such a volume - but to deny what I heard is stupid
Wow ... even wrote - but I repeat. 24-line brains of pro-alpha. I did not think to listen, compare on 16 omnikami. Although it was an opportunity.
Bzby @ 08/09/2014, 06:14*
If there are doubts in the liners - compare on full-size computer headphones. And you need to connect the viper.
Also do not expect that if the melody has 256-320 kb, then it is of high quality. A lot of fakes and upskeilov.
Better for tests download:
http://rutracker.org/f...viewtopic.php?t=382362
For me, the standard of quality from cheap Chinese was thl w1 + - you could unscrew the bottoms in it as you like and they carried out (laid) their ears. And it was still possible to switch tracks with camera buttons.
At the current thl w200s, the smart has impeccable medium and high. In g4s (ml version) there should be the same thing at least (but it looks like the album got fake and I don’t have time to evaluate it - I’ll find better tracks) - I can’t say the same thing yet and I don’t have time to evaluate low ones with a viper.
IMHO, if the medium and high were like the w200s, and the lower classes like the w1 + and still had the linearity of the characteristics - then hardly anyone would find fault with the sound.
If the computer has a good sound card, then in this topic, it seems like audio analyzers were used to quickly check the audio path.
On the sinks, I did not find the difference between Jiayu g4s and thl w200s. On full-size headphones (philips sbc hp820 (possibly inflated the lower classes)) - the sound is excellent. On simple Dialog EP-271V inserts, the sound is worse - large differences in low frequencies (but they are present) and more medium. With the built-in computer audio card, I also did not notice much difference. Here only instrumental method of comparison will help.
Experiments earlier with the wiper on thl w200s didn’t lead to anything good (maybe there was a bad sound source), but the wow effect on thl w1 + is unlikely to wait here (the only minus of the old wiper is the lack of audio “normalization” in frequencies like on the dsp enhancer plugin dsp_enh.dll - it is impossible to listen to assemblies - from one on the bottom it lays down the ears, should be done quieter, in others there are no drums and the bottoms - it should be done louder).
It makes no sense to look for a good sound in old smarts like w1 + or audio players. But compare with thl 5000 where NXP-box audio box solution is declared (audio chip UDA1380HN?) 24 bits or with another smart of the same performance and close price category - whoever has such an opportunity would not hurt.
djbob2000 @ 05/27/2014, 01:09*
I will touch upon the sore subject again, at the request of one comrade: I compared the sound of the NEO N003 with the Yamaha and the cheeks. I ask you to refrain from commenting, this is my IMHO.
Listen to flack: Dao Dezi - La Jument de Mishao, Yello - How How, Yello - Squeeze Please.
Neo plays almost perfectly, very close to the third galaxy, and even better than the third galaxy in high frequencies. The neo bass is hard, Samsung is softer, lamps :) In general, the neo really liked the sound. There is a power supply, you feel, plays louder Zhuyki. Of course, the beetle is inferior in sound, it feels like a low -power amplifier. One middle, basses are littered, tall too. It seems that they specially left the middle in the middle to play the outer speaker well. As a result, the bass blockage gives a feeling of “low -power” sound, and the blockage of high makes sound cheap, as if you are listening to the cassette :) I am exaggerating, but I think the essence is clear - there is no such crystal sound with high tingling needles, clear, everything is smeared. We must try to add volume in the engineering menu, if there really is a pit, a volume supply should be. And even then, the frequencies are vain viper. In principle, if you configure the sound should be normal. For example, they so evacked the sound - it is incomprehensible. But the outer speaker yells perfectly!
Tell me where in engineering to add volume to headphones?
Prompted: Headphone Mode = Headphone Mode =>Media
Added a maximum of 255, and 160 max volume. Yes, it was added, but before Neo falls short by 10%.

Manual how to gash a good sound
How to make a smooth volume

Patches that improve the sound (based on the info above)
All of the below listed patches are in the header, but here I will duplicate all the same.
ATTENTION! All of the following patches are suitable only for stock AOSP firmware, and custom, which are based on them.
Do not try to put on all sorts of LEWA, MIUI and various ports.


SOUND PATCH FOR JIAYU G4S WITH VIPER & WALKMAN
Download : Jiayu G4S - Official firmware (OS 4.2.2) (Post # 33822686)
Description :
Customized VIPER with driver installed
Walkman Player
Engineer settings for normal sound, without echo in the dynamics, buzzing, noise, cracks and other things.
The engineer is set up according to the principlehereandhere.


Patch in the Engineering menu on the speaker settings
Download : Jiayu G4S - Official firmware (OS 4.2.2) (Post # 33826380)
Description :
Here, only the settings of the engineering menu, without VIPER and Walkman
Engineer settings for normal sound, without echo in the dynamics, buzzing, noise, cracks and other things.
The engineer is set up according to the principlehereandhere.


Post has been editedjemi - 12.08.15, 18:25



Rep: (3321)
All about GPS

ALL LAZY TO READ FIRST OF ALL!

May we rejoice, for the theme has come to light.
You are welcome to the profile topic about the work of GPS on our device.
GPS talk on Jiayu G4S
Here is a bunch of instructions, manuals, discussions and tips.

If you have problems with GPS.

Post has been editedjemi - 12.08.15, 18:27



Rep: (3321)
[spoiler =All about the battery]
Will be replenished as far as possible.
While the main post here:Jiayu G4S - Purchase

Battery calibration instructions
Disable Google services to save battery. We read here:Jiayu G4S - Official firmware (OS 4.2.2) (Post # 34911263)
What writes about the batteryBloomberg mikki:
Jiayu G4S - Purchase
Below picture is Abroad version, Battery paste Lion and CE lable, Box is white
Battery color Li-Polymer Battery
Cause Jiayu Phone Import to Europe Country. If they paste it, it’s not necessary to do so.
And G4S lable to G4 reason is as below:
Previous Jiayu G4 MTK6589T phone have passed CE certification in last year,
but it doesn’t pay another $ 20,000 to G4S, it’s G4S, it’s a G4S MTK6592 phone.
We send China version or Abroad random based on stock.
If you are insist Chinese version, with Green color battery ok, remark the order.
Chinese verson have Chinese plug charger + EU adapter. Box is brown color.


The exact same info, but the words uv. MrGeptil
MrGeptil @ 09/12/2014, 9:51 PM*
Okay ... I will answer do not swear (everything is in the subject ...)
1) Black and green battery - ABSOLUTELY identical. They simply write fake data on black, so as not to rebuild expensive certification, this batch goes to the European market for retail sale in off-line stores, and there is firmware without g4sw in Chinese ... you should look at the correct data for both batteries at green.
2) For the same reason, they write on g4s, g4! The early model is included in the register of permitted products for passage through customs! And it is easier for the Chinese to wipe the letter in the firmware line than to go through the millstones of the international bureaucracy again ... All characteristics refer to the 8th nuclear model ...
This is all not relevant when buying directly from China ... iron is almost the same (almost, if you take the camera and the display, then the roulette)

Ps in pursuit. White boxes went to 2 + 16. Brown 1 + 4. Then 1 + 4 "died" ... Then everything mixed up, the euro version was added, it always goes in white, but to the shops. From China they send, how they will get ... The screens of the ski and ayu are almost the same, you should not bother absolutely, it's almost off of the top ...


Post has been editedjemi - 12.08.15, 18:27



Rep: (3321)
Issues related to software (firmware) MIUI
First of all, there is a theme on the firmware for the device for this device.
It is highly recommended to visit her and study the material set out there.

Jiayu G4S - MIUI Firmware (OS OS 4.2.X)
MIUI Installation / Firmware Questions
FAQ for MIUIv5
Official site: http://en.miui.com/
Software (firmware) issues LEWA
First of all, there is a theme on the left firmware for this device.
It is highly recommended to visit her and study the material set out there.

Jiayu G4S - LeWa OS Firmware (OS 4.2.x)
Mini FAQ
Extra buns LEWA
Description of system applications LEWA OS
Official site: http://www.lewaos.com/main.html

ALL NECESSARY SOFTWARE IN ONE PLACE
As the writing of the FAQ will add
SP Flash Tool is a flash driver for MTK smartphones.
MTK Droid Tools - Program for root, backup and create recovery on MT65 **

Drivers
Suitable for both JiaYu G4S (L) and JiaYu G5S (L)
Drivers for JiaYu G4S
Jiayu G4S Driver Kit
Universal ADB drivers
All-in-one drivers: just run the file and install all the firewood at once; There is a choice of individual drivers.

[attachment = "4946039: IMEI Recovery.rar"]- all to restore it (read the details above in the spoiler to restore IMEI

В® Mobileuncle MTK Tools - Google play | savagemessiahzine.com
BusyBox Installer (JRummy Apps Inc.) - Google play
BusyBox (Stephen (Stericson)) - Google play | savagemessiahzine.com
В® Titanium Backup (Backup of applications and user data (sms / mms / contacts)) - Google play | savagemessiahzine.com
Helium (Backup and Sync. Alternative to Titanium Backup) - Google play | savagemessiahzine.com


Post has been editedjemi - 12.08.15, 18:28



Rep: (3321)
20


Full version    

Help     rules

Now: 11/24/22, 18:38