{"id":5089,"date":"2017-01-18T11:58:18","date_gmt":"2017-01-18T04:58:18","guid":{"rendered":"http:\/\/www.jfdesignnet.com\/?p=5089"},"modified":"2017-01-23T10:44:36","modified_gmt":"2017-01-23T03:44:36","slug":"custom-recovery-twrp-3-0-2-0-for-axioo-m5cv2","status":"publish","type":"post","link":"https:\/\/www.jfdesignnet.com\/?p=5089","title":{"rendered":"custom recovery TWRP 3.0.2.0 for axioo M5Cv2"},"content":{"rendered":"<p style=\"text-align: justify;\"><a href=\"http:\/\/www.jfdesignnet.com\/wp-content\/uploads\/2016\/09\/m5c-twrp-fb.png\" rel=\"lightbox[5089]\"><img decoding=\"async\" loading=\"lazy\" class=\"alignright size-medium wp-image-4990\" src=\"http:\/\/www.jfdesignnet.com\/wp-content\/uploads\/2016\/09\/m5c-twrp-fb-262x300.png\" alt=\"\" width=\"262\" height=\"300\" \/><\/a>There is a reason I write this on separate article, this is TWRP for axioo M5C version 2, you cannot use this for M5C and vice versa. Why? On early week on this new year, axioo release another device revision of M5C model named as M5Cv2 that has a different hardware inside it. I&#8217;m not really sure what&#8217;s the different between the two, but as long as I know, the nand flash emmc and front \/ back camera are different.<br \/>\nThis M5Cv2 will need a new twrp because it has a different marshmallow kernel and etc. Here is the twrp 3.0.2.0 release :<\/p>\n<p style=\"text-align: justify;\">Download : <a href=\"http:\/\/www.mediafire.com\/file\/keg7zddkkhm6m8e\/recovery-twrp-m5cv2-3.0.2.0.img\">recovery-twrp-m5cv2-3.0.2.0.img<\/a><\/p>\n<p style=\"text-align: justify;\">MD5 : 703f62ec8b73adf7352f8427e0109b3a<\/p>\n<h4><strong>HOW TO INSTALL :<\/strong><\/h4>\n<p style=\"text-align: justify;\">To install this custom recovery, you need\u00a0SPFlashTool program which only available on winblows os platform so \u2026 really sorry, I cannot support it because I never use and don\u2019t have winblows. You may refer to this tutorial : <a title=\"Flashing Tutorial\" href=\"http:\/\/bm-smartphone-reviews.blogspot.com\/2012\/05\/mt6575-flashing-tutorial.html\" target=\"_blank\">MT65xx Flashing Tutorial<\/a> it is very well explained by Bruno Martin.<\/p>\n<p style=\"text-align: justify;\">Please be really careful using SPFlashTool, especially when flashing ROM not for your device, since it may bricked your device forever.<\/p>\n<p style=\"text-align: justify;\">Scatter file you might need : <a href=\"http:\/\/www.mediafire.com\/file\/leilfe4abgey3j0\/M5Cv2_MT6580_Android_scatter.rar\">M5Cv2_MT6580_Android_scatter.rar<\/a><\/p>\n<p style=\"text-align: justify;\">Of course you also can flash this custom recovery using linux or specific apk such as mobileuncle tool or recovery tool, but that\u2019s another story.<\/p>\n<h4><strong>HOW TO ENTER CUSTOM RECOVERY :<\/strong><\/h4>\n<p style=\"text-align: justify;\">Using button combination to enter the custom recovery mode on this model is really pain in the ass. I don\u2019t know why, usually it\u2019s easy on any mediatek platform, just like these : First, completely power off the device until you feel the device vibrate, indicating it was totally shutdown. Then, hold down Volume Up button then press Power button, hold them both until you see 3 menu list appear, Recovery, Fastboot and Normal. Scroll or choose between item using Vol up button and select them using Vol down button. On this case, choose Recovery and press Vol down button, wait a sec or two \u2026\u00a0 then you\u2019ll be entering recovery mode.<br \/>\nThe problem on this model is the timing, somehow it\u2019s different than any other mtk model I\u2019ve known, sometimes the button combination keypress just works okay just like that, sometimes not, be patient and I can assure you, it\u2019s all about timing.<\/p>\n<p style=\"text-align: justify;\">There are also many apk on playstore such as Quickboot, RecoveryTool, \u2026 etc, that can do reboot into recovery directly from alive system, but if this is your first time injecting twrp recovery, it\u2019s a must since you\u2019re not yet rooted. Read also my special note on this bottom of this article the reason why.<\/p>\n<h5><\/h5>\n<h4><strong>HOW TO ROOT :<\/strong><\/h4>\n<p style=\"text-align: justify;\">After installing this custom recovery, you can install root and Superuser manually as usual, I recommend to use latest <a href=\"http:\/\/forum.xda-developers.com\/showthread.php?t=1538053\" target=\"_blank\">chainfire SuperSU<\/a>. If you want to use <a href=\"http:\/\/www.jfdesignnet.com\/?p=5091\">my custom rom for this m5cv2 model<\/a>, then you not need to flash this root manually, it\u2019s already included on my custom rom.<\/p>\n<h4><strong>Special NOTE for newbie :<\/strong><\/h4>\n<p style=\"text-align: justify;\">If you came from stockrom and this is your first attempt to flash custom recovery, the sequence is mandatory. Please pay attention that after flash this recovery using spflashtool, you have to immediately enter the twrp recovery, <strong>DO NOT<\/strong> let the device boot into android os !! Why? Because if you let the device to boot into the system, the system will replace the twrp with the stock recovery again as part of their hacking attempt protection. This is common\u00a0 on any mediatek platform\u00a0(if not all), so don\u2019t be afraid, this is a well known protection issue.<br \/>\nI can understand the difficulties entering the recovery using button combination like I already mentioned above, but I cannot make this process easier and this is a must to do.\u00a0 If you\u2019re by accident forgot that, is okay, just flash it again and directly enter the twrp recovery after it. Once you enter the twrp, you can install <a href=\"http:\/\/forum.xda-developers.com\/showthread.php?t=1538053\">supersu<\/a> or <a href=\"http:\/\/www.jfdesignnet.com\/?p=5091\">my customrom<\/a> and it will have automated script that will disable that protection once and for all and the twrp will stick forever.<\/p>\n<p>Happy flashing !<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There is a reason I write this on separate article, this is TWRP for axioo M5C version 2, you cannot use this for M5C and vice versa. Why? On early week on this new year, axioo release another device revision of M5C model named as M5Cv2 that has a different hardware inside it. I&#8217;m not [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":5108,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,3,12],"tags":[192,243],"_links":{"self":[{"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/posts\/5089"}],"collection":[{"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=5089"}],"version-history":[{"count":7,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/posts\/5089\/revisions"}],"predecessor-version":[{"id":5128,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/posts\/5089\/revisions\/5128"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=\/wp\/v2\/media\/5108"}],"wp:attachment":[{"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5089"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5089"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jfdesignnet.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5089"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}