Little tricks on the part of flashing GU on this platform.
1. If you put the logo.bmp file and / or bootanimation.zip on the flash drive, you can replace the start logo and boot animation with your own.
Requirements for logo.bmp - the size in pixels must match the screen resolution (usually 1024x600, but there are exceptions)
2. The updatecfg.txt file contains instructions for additional operations during the flashing. There may be several instructions; each instruction is written on a separate line.
Instructions may be so (comments in English so as not to distort the meaning):
mass - Normal upgrade boot file (do not delete third-party applications)
twipe_all - Special boot file (double clear)
twipe_sd - use special upgrade boot files with caution (delete SDCARD)
delapp - Normal upgrade boot file (delete third-party applications)
make_updates - Make an upgrade U disk boot file
3. The file config.txt has a format similar to the file /system/build.prop and contains entries that supplement or replace similar entries in build.prop.
For example, you can specify the Russian localization and the Moscow time zone by default in config.txt:
ro.product.locale = en-RU
persist.sys.timezone = Europe / Moscow
4. The Allapp.pkg file is an archive of a special format in which there are applications that are additionally installed in the system, as well as additional system libraries and configuration files. The Apkpack.exe utility is used to unpack and package this archive.
ApkPackE.zip(782.44 KB)
All application files (* .apk) in the folder where you will unpack the archive (and from which you will pack the new archive if necessary) will be installed as system (non-removable) applications after the main flashing. Files from the uninstallable subfolders (if you create it) will be installed as user (deleted) applications.
Other (not * .apk) files in this archive:
fyt.prop - performs the same functions as config.txt (see above) - that is, it supplements and overlaps the values ​​in the build.prop file
customer_config.properties - customized hardware settings (better not to touch this file!)
skipkillapp.prop - in English:
The mechanism of the will of the process will be 0 ~ 15, it will not be killed by the OOM.
The top APK's oom_adj is 0, which is the last killed process. This is not the case.
It is not recommended that you accept it.
If you’re looking for a package of<package name>=<oom_adj>will set the process of oom_adj.
It is necessary to set the process name =<oom_adj>.
P.S.
jp2008 @ 02.02.19, 14:17
I want to add the post of a respected booroondook, my observations.
Thanks for the addition.
Yes, the instruction "twipe_data" in the updatecfg.txt file means deleting all data from the "data" section, which essentially means resetting the settings to the factory value and deleting user applications (however, the contents of the "internal memory card" remain as it was ( unless there is a "twipe_sd" instruction).
And one more trick. If you put the text file "crruptoff" in the root of the flash drive along with the firmware files (yes, this is the file name, without the extension), and this file will contain only one line with the text "fixwifi", then after the firmware you will receive GU
without GSM / 4G support. The SIM card indicator from the status line will disappear, and WiFi will be the only means of communication with the Internet.
Post has been editedbooroondook - 02.02.19, 14:45