How To Create Port TWRP CWM On New MTK (Mediatek SoC) Phone Devices ^NEW^
Click Here ---> https://fancli.com/2tuhGn
How to Create Port TWRP CWM On New MTK (Mediatek soC) Phone Devices
TWRP (Team Win Recovery Project) and CWM (ClockworkMod) are two popular custom recoveries that allow you to flash custom ROMs, kernels, mods, and backup your data on your Android device. If you have a new MTK (Mediatek) device that does not have an official TWRP or CWM support, you can still create a ported version of these recoveries using some tools and guides. In this article, we will show you how to create port TWRP CWM on new MTK phone devices.
Requirements
A Windows PC with ADB and Fastboot drivers installed.
A USB cable to connect your device to your PC.
An original stock recovery image of your device. You can extract it from your firmware or backup it using a tool like MTK Droid Tools.
A working TWRP or CWM recovery image for a similar MTK device with the same chipset, kernel, and screen resolution as your device. You can search for it on XDA Forums or other websites.
A tool to unpack and repack recovery images. You can use Carliv Image Kitchen or Easy Magic TWRP Installer.
Steps
Download and extract the tool to unpack and repack recovery images on your PC.
Copy the stock recovery image and the working TWRP or CWM recovery image to the same folder as the tool.
Run the tool as an administrator and select the option to unpack the stock recovery image. This will create a folder named \"stock\" with the extracted files.
Select the option to unpack the working TWRP or CWM recovery image. This will create a folder named \"port\" with the extracted files.
Copy the following files from the \"port\" folder to the \"stock\" folder, replacing the existing ones: kernel, recovery.img-kernel_offset, fstab.mtXXXX (where XXXX is your chipset number), and META-INF folder.
Select the option to repack the stock recovery image. This will create a new file named \"recovery.img\" in the same folder as the tool.
Copy the new \"recovery.img\" file to your PC and rename it to \"twrp.img\" or \"cwm.img\" depending on which recovery you ported.
Boot your device into fastboot mode by holding down the power and volume down buttons simultaneously.
Connect your device to your PC using a USB cable and open a command prompt window on your PC.
Type the following command to flash the ported recovery image: fastboot flash recovery twrp.img or fastboot flash recovery cwm.img
Type the following command to reboot your device: fastboot reboot
Congratulations! You have successfully created port TWRP CWM on new MTK phone devices. You can now boot into your custom recovery by holding down the power and volume up buttons simultaneously. You can also use it to flash custom ROMs, kernels, mods, and backup your data.
Troubleshooting
If you encounter any problems while creating port TWRP CWM on new MTK phone devices, you can try the following solutions:
Make sure you have the correct stock recovery image and working TWRP or CWM recovery image for your device. You can check the chipset, kernel, and screen resolution of your device using a tool like CPU-Z or MTK Engineering Mode.
Make sure you have the latest ADB and Fastboot drivers installed on your PC. You can download them from here: https://developer.android.com/studio/releases/platform-tools
Make sure you have enabled USB debugging and OEM unlocking on your device. You can do this by going to Settings > About phone > Tap on Build number seven times > Go back to Settings > Developer options > Enable USB debugging and OEM unlocking.
Make sure you have unlocked the bootloader of your device. You can do this by following the instructions from your device manufacturer or using a tool like MTK Unlock Tool.
If you get a \"remote: dtb not found\" error while flashing the ported recovery image, you can try to add the following line to the end of the \"fstab.mtXXXX\" file in the \"stock\" folder before repacking it: /dev/block/platform/mtk-msdc.0/by-name/recovery /recovery emmc defaults defaults
If you get a \"remote: partition table doesn't exist\" error while flashing the ported recovery image, you can try to use a different tool to unpack and repack recovery images, such as Android Image Kitchen or MTK Extractor.
If you get a \"remote: command not allowed\" error while flashing the ported recovery image, you can try to use a different command prompt window, such as Minimal ADB and Fastboot or Windows PowerShell.
If you get a black screen or a boot loop after flashing the ported recovery image, you can try to wipe data and cache partitions from your custom recovery or restore your stock recovery image using fastboot.
If none of these solutions work for you, you can ask for help on XDA Forums or other websites where you can find other users with similar devices and experiences. a474f39169