Simple and powerful MediaTek phone philz Touch Recovery Installer, detailed tutorial-this article is from Gaozhou Bar

Original address: http://bbs.gaozhouba.com/thread-19355-1-1.html

* * * * * * * * * * * * * * * * * * * * * * * * *

Philz Touch 6 Recovery

CWM Advanced Edition 6.x

* * * * * * * * * * * * * * * * * * * * * * * * *

Friends who like to brush the machine must be very familiar with Philz Touch CWM advanced Edition, and it is exciting that it now fully supports the MediaTek chip (MediaTek) device.

Supported MediaTek devices-ARM11, CORTEX-A9, Cortex-a7

Warning:

Under normal circumstances, even if the wrong third party recovery will only destroy the recovery, but it is still safe, this needs to take the risk.

Philz touch includes many features, so it usually works on MTK devices with recovery partitions larger than 6Mb, and of course you can take a chance.

The test is already available on MT6573 & MT6577 old machines.

First of all, do a full backup of the original ROM, you can use the MTK Droid Tools to operate.

Then search the Google Market flashify and install to back up your current recovery (for security), Boot.img also need to back up.

Unzip the downloaded file to your desktop, Win7 or win8[.1] If you disable UAC, restart your computer, double-click Start PhilZ.exe, and then follow the instructions.

Known issues with MTK MediaTek device

Most of the old midrange MediaTek phones recovery partitions are only 6Mb in size, such as MT6589, MT6572. In most cases, it is not working properly. But why some old equipment low-end machine mt6573,mt6577 can use it? Because their cores are small. Already a lot of netizens feedback now the newer MediaTek mobile phone's recovery partition has 7Mb & 8Mb size, the newest MT6592 recovery partition even more than 8Mb.

Philz Touch does not currently support ubifs file system

Philz Touch does not currently support MTK Alcatel models with/custpack partitions

There is no confirmation that the built-in SD card uses the latest voldmanaged mount point of the/storage/usbdisk Voldmanaged=usbdisk:auto, so it will not mount the built-in SD card with this design.

In the past, it has been reported that some MTK phones, recovery under the touch operation, you can try to use a different version of the kernel for your model. The Recovery is independent, so the GB (2.3.x), ICS (4.0.x) or JB (4.1.x) kernels work properly!

Flip screen works properly on Philz Touch by adding the flip-screen tag (flag). However, it has a minor problem, that is, the screen will blink & bounce when using a virtual key. So, if the touch works perfectly, we can disable it without using a virtual key or permanently. Philz Settings, GUI Preferences, Toggle Virtual Keys.

Do not try to lock the bootloader MTK model, has been confirmed to become brick.

This tool will automatically install Aroma filemanager (Aroma File Manager), some MTK devices Aroma File Manager does not start, the error message that appears is E:can ' t make/tmp/update_binary Installation aborted ...

Workaround

First Use automatic mode (auto), it will automatically back up your current recovery.

Unplug the data cable, use the phone status normally, copy the recovery.img from the Backup-mtk-recovery folder to the stock folder, it will call you to plug in the USB link computer.

Now use the notepad++ editor to open the Stock/recovery/rmdisk/init.rc and add the following highlighted line of content after saving.

Connect the computer, press OK, select your device resolution, it will automatically perform the installation.

Mkdir/emmc

Mkdir/system

Mkdir/data

Mkdir/cache

Mkdir/tmp <-Add this line to Init.rc

Mount Tmpfs tmpfs/tmp

Chown Root Shell/tmp

chmod 0775/tmp

Now, Aroma FileManager should be able to use it normally.

Case study, the old ICS 4.04 MT6577 model with 480x850 resolution, the transplanted Philz Touch does not start, and then discovers that the kernel cannot support 320x480 resolution philz!

Workaround

Steps: Windows Explorer, Show hidden files and folders, Mtk_philz, Bin, res.7z, extract the 240x320_bg.png and rename it to Stitch.png.

Insert the data cable in normal mode, select your device resolution, and it will ask if you have flipped screen.

Copy and paste the extracted 240x320 stitch.png to the Stock/recovery/rmdisk/res/images folder under overlay, and then confirm just the flipped screen issue.

Then perform the steps: Philz Settings, GUI Preferences, change Background, Reset Koush Background.

About fault detection of mounted USB storage

For MTK equipment, Fstab v2 is the standard fstab (Unified fstab) is no longer mysterious, now in Philz touch can be perfectly mounted inside and outside SDcard.

I do not have MediaTek's machine, because of different voldmanaged path, so it is very possible in recovery to not mount internal and external memory. The following will identify and resolve this issue.

Open the editor to create new text (recommended notepad++), copy the content below and save it to the Mtk_philz folder as a Philz Touch recovery.img file for unpacking/packaging the migration.

Mkt_unpack.bat

@echo off

CD%~dp0

CHCP 1251

if (% 1) = = () (

echo Select Image

Goto END

)

Setlocal enabledelayedexpansion

COLOR 0A

Mode con:cols=65 lines=31

Bin\sfk166.exe hexfind%1-pat-bin/88168858/-case >bin\offset.txt

Bin\sfk166.exe hexfind%1-pat-bin/ffffffff1f8b08/-case >>bin\offset.txt

Bin\sfk166.exe Find Bin\offset.txt-pat Offset>bin\off2.txt

Bin\sfk166.exe Replace bin\off2.txt-binary/20/0a/-yes

If exist%~n1st/s/q%~n1 >nul

set/a n=0

: Loop

for/f%%g in (bin\off2.txt) do (

if! N!==1 (

set/a ofs1=%%g

set/a n+=1

)

if! N!==3 (

set/a ofs2=%%g

set/a n+=1

)

if! N!==5 (

set/a ofs3=%%g+4

set/a n+=1

)

If '%%g ' EQU ' offset ' (

set/a n+=1

)

)

For%%i in (% 1) do (set/a Boot_size=%%~zi)

Echo.

Echo-size of%1%boot_size% byte

Echo-kernel Offset-%ofs1%

Echo-ram_header Offset-%ofs2%

Echo-ram_disk Offset-%ofs3%

Echo.

Del Bin\offset.txt

Del Bin\off2.txt

MD%~n1

Echo-extracting Kernel_header ...

Bin\sfk166.exe partcopy%1-fromto 0x0%ofs1%%~n1\kernel_header-yes

Echo-extracting kernel ...

Bin\sfk166.exe partcopy%1-fromto%ofs1%%ofs2%%~n1\kernel-yes

Echo-extracting Ram_header ...

Bin\sfk166.exe partcopy%1-fromto%ofs2%%ofs3%%~n1\ram_header-yes

Echo-extracting Ram_disk ...

Bin\sfk166.exe partcopy%1-fromto%ofs3%%boot_size%%~n1\ram_disk.gz-yes

Echo-unpack ram_disk.gz ...

Bin\7za.exe-tgzip x-y%~n1\ram_disk.gz-o%~n1 >nul

Echo-unpack Ram_disk.cpio ...

MD%~n1\rmdisk

CD%~N1

CD Rmdisk

%~dp0bin\cpio.exe-i < /ram_disk

Cd..

Cd..

Copy%1%~n1

Echo.

Echo-done ^^!

Echo.

Pause

: End

Mtk_pack.bat

@echo off

CD%~dp0

CHCP 1251

if (% 1) = = () (

echo Select folder

Goto END

)

Setlocal enabledelayedexpansion

COLOR 0A

Mode con:cols=60 lines=39

Set pt=%~n1%~x1

Echo%pt%

Copy%pt%\ram_header%~n1\new_ram_with_header >nul

CD%pt%

%~dp0bin\chmod OG=XR Rmdisk

CD Rmdisk

Echo-pack Rmdisk to Cpio ...

%~dp0bin\find. | %~dp0bin\cpio.exe-o-H newc-f. /new_ram_disk.cpio >nul

Move: \ram_disk. \ram_disk_old >nul

Copy.. \new_ram_disk.cpio. \ram_disk

Echo-pack Rmdisk to gzip ...

%~dp0bin\gzip-n-F. /ram_disk

Echo-add header ...

%~dp0bin\dd if=. /ram_disk.gz >>. /new_ram_with_header

For%%i in (.. /ram_disk.gz) do (set/a Size=%%~zi)

Echo-new RAMDisk%size% Byte

%~dp0bin\sfk166 Hex%size%-digits=8 ... /.. /size.txt

For%%i in (.. /.. /size.txt) do (set/a Size=%%~zi)

%~dp0bin\sfk166 split 1. /.. /size.txt. /.. /1 >nul

For/f%%i in (.. /.. /1.PART7) do (set a1=%%i)

For/f%%i in (.. /.. /1.PART8) do (set a2=%%i)

For/f%%i in (.. /.. /1.PART5) do (set a3=%%i)

For/f%%i in (.. /.. /1.PART6) do (set a4=%%i)

For/f%%i in (.. /.. /1.PART3) do (set a5=%%i)

For/f%%i in (.. /.. /1.PART4) do (set a6=%%i)

For/f%%i in (.. /.. /1.PART1) do (set a7=%%i)

For/f%%i in (.. /.. /1.PART2) do (set a8=%%i)

Echo%a7%%a8%>size.txt

Echo%a5%%a6%>>size.txt

Echo%a3%%a4%>>size.txt

Echo%a1%%a2%>>size.txt

Echo-add new size in header 0x%a1%%a2% 0x%a3%%a4% 0x%a5%%a6% 0x%a7%%a8%

%~dp0bin\sfk166.exe echo%a1%%a2%%a3%%a4%%a5%%a6%%a7%%a8% +hextobin. /.. /tmp1.dat

%~dp0bin\sfk166.exe partcopy. /.. /tmp1.dat 0 4.. /new_ram_with_header 4-yes>nul

Echo-make image ...

%~dp0bin\mkbootimg.exe--kernel. /kernel--ramdisk. /new_ram_with_header-o. /new_image.img

Del Size.txt >nul

Copy.. \new_image.img%~dp0\new_image.img

Move: \ram_disk_old. \ram_disk >nul

Cd..

Cd..

Del Size.txt >nul

Del Tmp1.dat>nul

Del 1.part*>nul

Echo.

Echo-done ^^!

Echo.

Pause

: End

Just drag and release the ported Philz Touch recovery.img This file to Mtk_unpack.bat to perform the decompression, then drag and release the extracted recovery folder to the Mtk_pack.bat. First, turn off UAC.

Or you can download the Windows Boot/recovery repack utils to unzip/pack the ported Philz Touch Recovery. Basically, its operation is exactly the same, except for this porting tool. It uses a separate 7za.exe to operate instead of relying on 7z.dll's 7z.exe.

Mt65xx's Recovery.fstab

# Android Fstab file.

# The FileSystem that contains the FileSystem checker binary (Typically/system) cannot

# specify Mf_check, and must come before any filesystems this do specify Mf_check

#

/DEV/BOOTIMG/BOOTIMG eMMC Defaults defaults

/dev/recovery/recovery eMMC Defaults defaults

/dev/uboot/uboot eMMC Defaults defaults

/[email protected]/system ext4 ro,noatime wait

/[email protected]/cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait

/[email protected]/data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer

# for MT6577

/DEVICES/PLATFORM/MTK-SD.0/MMC_HOST/MMC0 Auto Auto Defaults voldmanaged=sdcard0:6

/DEVICES/PLATFORM/MTK-SD.1/MMC_HOST/MMC1 Auto Auto Defaults voldmanaged=sdcard1:auto

# for MT65XX

/DEVICES/PLATFORM/MTK-MSDC.0/MMC_HOST/MMC0 Auto Auto Defaults voldmanaged=sdcard0:6

/DEVICES/PLATFORM/MTK-MSDC.1/MMC_HOST/MMC1 Auto Auto Defaults voldmanaged=sdcard1:auto

Confirm your MTK device sdcard voldmanaged path, adb shell Find/sys-name mmc0. You don't need to include this primary path/sys, then it will start searching at/devices.

Confirm your built-in SDcard area code (internal SDcard partition No.), adb shell Cat/proc/dumchar_info view FAT partition block information/dev/block/mmcblk 0P6, make the corresponding update ...

It also needs to be updated to Fstab.${ro.hardware}.

The method of correctly checking ${ro.hardware}, adb shell Getprop ro.hardware-mt6577, should be renamed to fstab.mt6577.

Some MTK models do not use fat as the built-in SDcard mount point, then this tool will not be able to confirm it, and always philz Touch will cause the phone to not start or infinite restart ...

/DEVICES/PLATFORM/MTK-MSDC.0/MMC_HOST/MMC0 Auto Auto defaults voldmanaged=sdcard0: <-empty

/DEVICES/PLATFORM/MTK-MSDC.1/MMC_HOST/MMC1 Auto Auto Defaults voldmanaged=sdcard1:auto

Workaround-Add # to the beginning of this line or just delete it, so you can

#/devices/platform/mtk-msdc.0/mmc_host/mmc0 Auto Auto defaults voldmanaged=sdcard0: <-empty

/DEVICES/PLATFORM/MTK-MSDC.1/MMC_HOST/MMC1 Auto Auto Defaults voldmanaged=sdcard1:auto

How do I confirm the USB voldmanaged mount point of the built-in SD? adb shell su-c "ls-r" > c:\users\ your computer's user name \desktop\usb.txt

Find any USB keywords inside, try updating to Fstab.${ro.hardware} and Recovery.fstab. Two are needed, otherwise they will not work.

If your device is this:/data/media. Then it's not working.

Simple and powerful MediaTek phone philz Touch Recovery Installer, detailed tutorial-this article is from Gaozhou Bar