bat launchers for updating (does not erase all data) and for a clean installation (erases all data)Ģ.5 Another very important feature of the AB structure in our case is two types of fastboot mod. Inside, as the author saw fit, there are. Installation via PC, via ADB (on the phone, AOSP recovery adb sideload/twrp adb sideload mode) or installation via TWRP directly from the deviceĢ.4 Custom ROMs for fastboot, usually used for a clean installation, which implies cleaning and data from memory (pictures, etc.) inside sometimes have firmware sections and always rom sections. Installation always goes to the adjacent NOT active memory slot, and after completion, makes the adjacent slot active to load the firmware Inside the archive there is a payload.bin file in which the rom and sometimes firmware sections are packed Not all partitions, but the main ones (always stitched into section A), including firmware (stitched into both slots A and B)Ģ.3.3 Sideload type firmware (99% of all custom ROMs) are divided into two installation methods. bat files speaks for themselvesĢ.3.2 Next - the installation. ![]() There are also 3 files inside - for easy installation of all partitions, for installing all partitions and formatting the memory, as well as for installing all partitions and locking the bootloader (the memory is formatted automatically), the name of the. ROMs of a custom type, those based on a "pure" android are often flashed for only partitions of the ROM, but not in 100% caseĢ.3 For our device, there are 3 types of ROM installation files, 2 of which are divided into two types of installation methodsĢ.3.1 Let's start simple, Official miui image for fastboot - installation is recommended via miflash, has all partitions inside the archive. Although this is not necessary in essence. In the case of firmware, they are put in both slots at once. "aop.img", "/dev/block/bootdevice/by-name/aop_b"and there are partitions directly ROM /data, /system /system_ext, /vendor, /product, /odm, /vendor_boot, /bootĢ.2 miui based ROMs update all of these sections. "aop.img", "/dev/block/bootdevice/by-name/aop_a" "imagefv.img", "/dev/block/bootdevice/by-name/imagefv_b" "imagefv.img", "/dev/block/bootdevice/by-name/imagefv_a" "hyp.img", "/dev/block/bootdevice/by-name/hyp_b" "hyp.img", "/dev/block/bootdevice/by-name/hyp_a" "devcfg.img", "/dev/block/bootdevice/by-name/devcfg_b" "devcfg.img", "/dev/block/bootdevice/by-name/devcfg_a" "cmnlib64.img", "/dev/block/bootdevice/by-name/cmnlib64_b" "cmnlib64.img", "/dev/block/bootdevice/by-name/cmnlib64_a" "cmnlib.img", "/dev/block/bootdevice/by-name/cmnlib_b" "cmnlib.img", "/dev/block/bootdevice/by-name/cmnlib_a" "xbl.img", "/dev/block/bootdevice/by-name/xbl_b" "xbl.img", "/dev/block/bootdevice/by-name/xbl_a" "qupfw.img", "/dev/block/bootdevice/by-name/qupfw_b" "qupfw.img", "/dev/block/bootdevice/by-name/qupfw_a" "uefisecapp.img", "/dev/block/bootdevice/by-name/uefisecapp_b" "uefisecapp.img", "/dev/block/bootdevice/by-name/uefisecapp_a" "keymaster.img", "/dev/block/bootdevice/by-name/keymaster_b" "keymaster.img", "/dev/block/bootdevice/by-name/keymaster_a" "featenabler.img", "/dev/block/bootdevice/by-name/featenabler_b" "featenabler.img", "/dev/block/bootdevice/by-name/featenabler_a" "abl.img", "/dev/block/bootdevice/by-name/abl_b" "abl.img", "/dev/block/bootdevice/by-name/abl_a" "bluetooth.img", "/dev/block/bootdevice/by-name/bluetooth_b" "bluetooth.img", "/dev/block/bootdevice/by-name/bluetooth_a" "tz.img", "/dev/block/bootdevice/by-name/tz_b" "tz.img", "/dev/block/bootdevice/by-name/tz_a" "modem.img", "/dev/block/bootdevice/by-name/modem_b" ![]() "modem.img", "/dev/block/bootdevice/by-name/modem_a" "xbl_config.img", "/dev/block/bootdevice/by-name/xbl_config_b" "xbl_config.img", "/dev/block/bootdevice/by-name/xbl_config_a" "dsp.img", "/dev/block/bootdevice/by-name/dsp_b" "dsp.img", "/dev/block/bootdevice/by-name/dsp_a"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |