Porting TWRP recovery
The first thing you need to find the device identical to the one on which we will port rekaveri. I found this Xiaomi Redmi 1S. Often, if the body is identical processors should succeed. Screen resolution Number of RAM, etc. not very important, but the phones are more like the greater the chance that everything will go smoothly.
Next swing rekaveri from off site
http://techerrata.com/browse/twrp2/armani(We were lucky to Xiaomi Redmi 1S on off site there are always straight from the tin rekaveri to other devices to look for in the vast inieta.)
Now a little theory. Rekaveri - it's too Suteev core with the same ramdikom but ramdisk set of utilities and binaries rekaveri interface. Should abstain from this that we need to dismantle rekaveri from a similar device to fix ramdisk and fasten our core. Well, sort of task is clear.
All use the same tool as for the disassembly of the nucleus
software modifications and embellishments for ZTE V5 (Post # 36404731)And so we assort our core. We assume that sorted out. Directory with the kernel parsed call \ Android Image Kitchen_stok_boot. Everything described here
software modifications and embellishments for ZTE V5 (Post # 36404731)(We need it especially for \ split_img - this is our core without a ramdisk.)
Create a new folder with the utility to disassemble and dismantle the core openrecovery-twrp-2.8.4.0-armani.img. Will work as long as strictly to that folder.
Here we have a new folder with the utility
Android Image Kitchen_TWRP_recovery
android_win_tools \
cleanup.bat
repackimg.bat
unpackimg.bat
Next, put it openrecovery-twrp-2.8.4.0-armani.img and rename it boot.img
And understand. All the same as here
software modifications and embellishments for ZTE V5 (Post # 36404731)Now work with the \ ramdisk
Go along the path \ Android Image Kitchen_TWRP_recovery \ ramdisk \ etc \ recovery.fstab here spelled mount points, they can also learn from recovery.fstab only rekaveri for our unit.
We will change nothing because Forums Xiaomi Redmi 1S is identical sections ZTE v5.Not exactly the same. Internal Memory s1 - the directory / data / media so the / sdcard mounted / data / media is displayed and section / data size. Therefore recovery.fstab you have to edit.
Here is an example of the edited
recovery.fstab
/ Boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/ System ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/ Data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata
/ Cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/ Recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/ Emmc vfat /dev/block/platform/msm_sdcc.1/by-name/grow flags = display = "Internal SDcard"; storage; wipeingui
/ External_sd vfat / dev / block / mmcblk1p1 / dev / block / mmcblk1 flags = display = "External SDcard"; storage; wipeingui; removable
/ Usb-otg vfat / dev / block / sda1 / dev / block / sda flags = display = "USB-OTG"; storage; wipeingui; removable
/ Splash emmc /dev/block/platform/msm_sdcc.1/by-name/splash flags = flashimg = 1; backup = 1; display = Splash
/ Efs1 emmc / dev / block / mmcblk0p13 flags = backup = 1; display = OEM
/ Efs2 emmc / dev / block / mmcblk0p14 flags = backup = 1; subpartitionof = / efs1
/ Efs3 emmc / dev / block / mmcblk0p15 flags = backup = 1; subpartitionof = / efs1
/ Modem emmc / dev / block / mmcblk0p1 flags = backup = 1; display = Radio
/ Persist emmc / dev / block / mmcblk0p22 flags = backup = 1; display = Persist
/ Aboot emmc / dev / block / mmcblk0p6 flags = backup = 1; display = Loader
/ Fmwr1 emmc / dev / block / mmcblk0p2 flags = backup = 1; display = Firmware
/ Fmwr2 emmc / dev / block / mmcblk0p4 flags = backup = 1; subpartitionof = / fmwr1
/ Fmwr3 emmc / dev / block / mmcblk0p8 flags = backup = 1; subpartitionof = / fmwr1
/ Fmwr4 emmc / dev / block / mmcblk0p10 flags = backup = 1; subpartitionof = / fmwr1
Here you can see the description of "flags"
http: //forum.xda-devel...owthread.php? t = 1943625C so recovery.fstab be displayed
Internal storage - / data / media (until he could disable)
Intarnal SDcard - Internal memory
External SDcard - SD-Card
You can make backup and restore:
OEM - (sections fsg, modemst1, modemst2)
Radio - (section modem)
Persist - (section persist)
Loader - (section aboot)
Firmware - (sections rpm, sbl1, sdi, tz)
Splash - (section splash)
And it will be possible to flash the image splash.img
Then we go along the path \ Android Image Kitchen_TWRP_recovery \ ramdisk \ res \ here are resources to display TWRP menu. Downloading source TWRP
https://github.com/Tea...m-Win-Recovery-Projectextract the archive and go along the path \ Team-Win-Recovery-Project-twrp2.7 \ Team-Win-Recovery-Project-twrp2.7 \ gui \ devices \ and seek permission for our system (for example, we need a directory named \ 720x1280 ) and copy the contents of the replacement \ Team-Win-Recovery-Project-twrp2.7 \ Team-Win-Recovery-Project-twrp2.7 \ gui \ devices \ 720x1280 in \ Android Image Kitchen \ ramdisk \ res \. We will change nothing because screen resolution Xiaomi Redmi 1S is identical ZTE v5.
Now edit \ Android Image Kitchen_TWRP_recovery \ ramdisk \ default.prop like this (replace every where there is mention of another unit, in this case, "Xiaomi", "armani", "S1" on the "ZTE", "X9180". Examples take from build.prop)
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure = 0
ro.allow.mock.location = 1
ro.debuggable = 1
persist.sys.usb.config = adb
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id = KTU84P
ro.build.display.id = X9180 4.4.4 KTU84P eng.dees_troy.20150113.055236 test-keys
ro.build.version.incremental = eng.dees_troy.20150113.055236
ro.build.version.sdk = 19
ro.build.version.codename = REL
ro.build.version.release = 4.4.4
ro.build.date = Tue Jan 13 05:53:10 UTC 2015
ro.build.date.utc = 0
ro.build.type = eng
ro.build.user = dees_troy
ro.build.host = ded1.ktechnology.net
ro.build.tags = test-keys
ro.product.brand = ZTE
ro.product.board = MSM8226
ro.product.cpu.abi = armeabi-v7a
ro.product.cpu.abi2 = armeabi
ro.product.manufacturer = ZTE
ro.product.locale.language = en
ro.product.locale.region = US
ro.wifi.channels =
ro.board.platform = msm8226
# ro.build.product is obsolete; use ro.product.device
ro.build.product = X9180
ro.product.model = X9180
ro.product.name = X9180
ro.product.device = X9180
# Do not try to parse ro.build.description or .fingerprint
ro.build.description = X9180 4.4.4 KTU84P eng.dees_troy.20150113.055236 test-keys
ro.build.fingerprint = ZTE / X9180 / X9180: 4.4.4 / KTU84P / eng.dees_troy.20150113.055236: eng / test-keys
ro.build.characteristics = default
ro.omni.device = X9180
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim = true
ro.com.android.dataroaming = true
ro.com.android.dateformat = MM-dd-yyyy
ro.carrier = unknown
ro.ril.hsxpa = 1
ro.ril.gprsclass = 10
ro.adb.qemud = 1
persist.sys.dalvik.vm.lib = libdvm.so
ro.kernel.android.checkjni = 1
net.bt.name = Android
dalvik.vm.stack-trace-file = / data / anr / traces.txt
And finally, we go along the path \ Android Image Kitchen_TWRP_recovery \ ramdisk \ init.rc and correct ven-id and dev-id is to adb driver picked up and displayed correctly in the machine system devices. We have, I have not changed since we are registered with Google aydishniki devices.
write / sys / class / android_usb / android0 / idVendor 18D1
write / sys / class / android_usb / android0 / idProduct 4EE2
With \ ramdisk all.
Now remove from \ Android Image Kitchen_TWRP_recovery directory \ split_img and copy the same directory from \ Android Image Kitchen_stok_boot.
All collected. Again, we turn to post
software modifications and embellishments for ZTE V5 (Post # 36404731)Well, the image-new.img rename it twrp_for_v5.img
Sews in any convenient manner. dd, fastboot or doing the zip file with the patch.
P.S. Get a job working with TWRP 2.8.4.0 mtp as a normal drive mounting. Installed five times the firmware patches are no glitches compared to 2.8.0.0 and 2.8.1.1
To install over rekaveri events
TWRP_2.8.4.0_signed.zip(9.61 MB)
Now sets the firmware verification device !!!
I express my gratitude for the prompt
proDOOMmanand
fazergooPost has been editedroky_rs - 05.02.15, 17:06Reason for editing: Corrected spelling errors