Auto TWRP porter for Qualcomm v1.3 & Mediatek v1.5 launched
We’ve updated our Auto TWRP porters for Mediatek (MTK) and Qualcomm (QLM) devices. These are simple tools that port a […]
Learn more →
Tech. Tutorials, Tips & News
We’ve updated our Auto TWRP porters for Mediatek (MTK) and Qualcomm (QLM) devices. These are simple tools that port a […]
Learn more →We’ve launched v1.2 of our Qualcomm (QLM) Auto TWRP porter. In this version, we have made some improvements in the […]
Learn more →We want to thank all our Beta testers of v1.0 of this tool which supported only Android 7 (Nougat) Qualcomm […]
Learn more →Yesterday, we launched the Android IMG unsign tool v1.0 which enables you unsign signed images before unpacking them. Today, we’re […]
Learn more →Those of you whose firmware contain signed images (e.g boot-sign.img, recovery-sign.img, system-sign.img, vendor-sign.img etc) might have encountered errors while trying […]
Learn more →We’re kicking off 2019 with a special New Year’s sale for You. This January, You’ll get a discount when you […]
Learn more →Let us start by wishing you a Happy New Year. We’re quite certain you’re familiar with our Mediatek TWRP porter and […]
Learn more →Last month, we introduced our MTK auto TWRP porter v1.3 (GUI version) in response to two main issues often reported […]
Learn more →Our auto TWRP porter project has been successful thus far but two main issues which your feedback has brought to […]
Learn more →We’re happy to announce v1.4 of our Mediatek auto Philz recovery porter. This is coming after recent updates to the […]
Learn more →We have a global user base and with that comes a language barrier problem. In a bid to cater to […]
Learn more →Less than two months ago, we pushed an update to our Mediatek (MTK) Auto TWRP recovery porter (to v1.2). The […]
Learn more →We’re happy to announce the launch of our first online course titled Intro to Mediatek (MTK) smartphone software repairs. This […]
Learn more →Late last year, we removed the Forum from the Hovatek Mobile app due to persistent crash issues. We suggested a […]
Learn more →Let us start by thanking all those who dropped feedback during the v1.1 beta test. We’d taken note of some […]
Learn more →