How To Port PhilZ/CTR/CWM/TWRP Recovery to your Phone(MTK)

01:21 Alex 52 Comments

How To Port PhilZ/CTR/CWM/TWRP Recovery to your Phone


There are many low budget devices available in market and most of them have MediaTek soc in there heart. And sadly these devices are often left alone because of lack of development.
Well cooking roms for every device is not possible for developers. And new users dont want to try because of the fear that they will end up with there house on fire. :p

Well jokes apart if you fear that you will brick your device while trying to port/flash a custom rom, This is where a custom recovery comes handy. You can always backup your device in case of if something gets wrong and later restore that backup on your device. Except If you actually ended up burning your house to ashes.Dude no one can help you now.

There are many recovers available to save your day.

1. TeamWin Recovery Project aka TWRP
2. ClockWork Mod aka CWM
3. Carliv Touch Recovery aka CTR
3. PhilZ Recovery aka PhilZ Recovery

So without much ado lets start


Among all these my favorite recovery till now is PhilZ recovery. Carliv Touch Recovery is also one of the best recoveries which MTK phones have. TWRP and CWM exists too, but for me philZ is the best because it never throws errors without any solid reason. 
There’re 3 ways to port. One is to compile on your own which is the best, but tough for some newbies. Another one is to port manually which I will be explaining here and the last one is using automatic CTR porting tool, PhilZ porting tool and Cwm porting tool.
I will be explaining about CTR/twrp/philz/cot porting guide, manually and automatically both.
I prefer you to use the tool because it is less time consuming and works almost with every phone. Use manual porting only if you want learn about Android and other things, or I might say for educational purpose.

Preparations:

  • First, you need to have your device rooted. If you have not rooted your phone yet, try to root it using this guide it should work on all devices.
  • Next, you have to install ADB (Android Debug Bridge) drivers to your PC (Pdanet drivers will do). Note that computers with Windows 8 and/or 8.1 aren't recommended for installing unsigned drivers. I would recommend you to use Windows 7

Automated tools Porting Guide

(I recommend to use this method because it is very easy, less painful, takes few minute and best for those who have less or no experience on android development)

These are the tools you going to need!
TWRP Recovery Porting ToolClick here.
PHilz Recovery Porting Tool: Click here.
CWM Recovery Porting ToolClick here. I will suggest you to use MTK Droid Root and Tools [Latest one].
CTR Recovery Porting Tool: Click here.

Direct Links: 



Requirements

* USB debugging enabled on the phone (Settings > Developer . If no Developer under Settings, go to Settings > About > Keep tapping Build Number till Developer appears under Settings)
* USB cord
* A PC
* ADB and MTK drivers installed on PC

Procedure

1. Download CTRv2.2.zip or any from the link
2. Extract the content of  CTRv2.2.zip to a folder
4. Enable USB debugging on the phone then connect it to the PC
5. Temporarily disable your Antivirus
6. Launch CTRv2.2.exe as Administrator on your PC
7. CTRv2.2.exe will be automatically copied to your desktop. Click Ok to proceed
8. Click Yes to disable UAC 
9. Click Yes for Auto-Port
10. Ensure the phone is connected to the PC with USB debugging enabled then click Ok 
11. The Tool will Auto-detect your Chipset. you could click Ok or just leave it as it will automatically proceed
12. The Tool will Auto-detect your Partition type. you could click Ok or just leave it as it will automatically proceed
13. The Tool will Auto-detect your Screen resolution. you could click Ok or just leave it as it will automatically proceed
14. The Tool will prompt you to reboot in recovery mode. you could click Ok or just leave it as it will automatically proceed
15. If porting of Clockworkmod 6 (Carliv Touch Recovery) to the MTK phone was successful, you will get a prompt confirming the success
16. Congratulations! You now have Clockworkmod Version 6 on your MTK phone


Manual Porting Guide [Will work with CTR/CWM/TWRP/Philz etc]
(Only use this method if the automated tools fail or you just decide to go on an adventure, as this is only for experienced users and noobs who have piles of money to buy new device in case of brick)

Things you need :
CarlivImage Kitchen : This is needed to unpack and repack the recovery (it will unpack any type of recovery)
- Stock boot.img(In the rare case if your device dont have stock recovery) OR recovery.img
- A little time and patience
Carliv Touch Recovery (Download the recovery for your resolution)
Note : You can use port any recovery but make sure the resolution and chipset matches

How To :

- Rename stock recovery.img to stock_recovery.img and port recovery.img as port-recovery.img
- Just drag the recoveries in the .bat file in CarlivImage Kitchen and it will unpack them. 
- Replace from stock to port :
* meta_init.project.rc
* meta_init.rc
meta_init.modem.rc
* ueventd.rc
* ueventd.goldfish.rc
* fstab
* /etc/recovery.fstab
* replace kernel
* kernel_header (depends on the tool you used)

Note : Repack and test the recovery, whether it boots or not. After done unpack the new recovery and make the following changes 

- Compare default.prop of stock and port and only change the following lines (colored in red)
ro.mount.fs=EXT4
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KTU84Q
ro.build.display.id=cm_new-eng 4.4.4 KTU84Q 347d7427a4 test-keys
ro.build.version.incremental=347d7427a4
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.date=Tue Dec  9 16:23:16 EET 2014
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=carliv
ro.build.host=max
ro.build.tags=test-keys
ro.product.brand=mtk
ro.product.name=cm_new
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=mtk
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=mt6582
# ro.build.product is obsolete; use ro.product.device
ro.build.product=new
ro.product.model=new
ro.product.device=new
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=cm_new-eng 4.4.4 KTU84Q 347d7427a4 test-keys
ro.build.fingerprint=mtk/cm_new/new:4.4.4/KTU84Q/347d7427a4:eng/test-keys
ro.build.characteristics=default
ro.cm.device=new
# end build properties
#
# from device/mtk/new/system.prop
#
#
# system.prop for new
#

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmod
ro.com.google.clientidbase=android-google
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.build.selinux=1
persist.sys.dalvik.multithread=false
persist.sys.dun.override=0
persist.sys.root_access=1
ro.cm.version=11-20141209-UNOFFICIAL-new
ro.cm.releasetype=UNOFFICIAL
ro.modversion=11-20141209-UNOFFICIAL-new
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
persist.sys.recovery_update=false
ro.cm.display.version=11-20141209-UNOFFICIAL-new
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
ro.config.ringtone=Orion.ogg
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
Thats it.

52 comments:

  1. why did you mention stock boot.img if you didn't use it ?

    ReplyDelete
    Replies
    1. In some rare cases manufacturers decide to remove recovery file completely so in those cases you need stock boot image.
      Thank you for the mention though; i will fix the typo to avoid confusion.

      And i will suggest you to use Automated recovery compilers, Because they are easy to use and manual method dont always work and its only for experienced users.

      Delete
  2. You welcome Alex.. I haven't found a custom recovery for my new device which push me to learn how to build custom recovery nowdays..Now I satup my linux and the source is being downloaded. I'm Waiting it to finish then I will see what's going to do

    ReplyDelete
    Replies
    1. Why are you trying to make it from source. it is very advance method and not for new users and mistakes might lead to a hard brick.
      Can you give mode details about the device you are using? what kernel ver. it have.
      Have you tried automated tools? try to make it via them because its very easy and take only 10-15min to make a recovery with it.
      Best tool to make recovery are MTK Droid Tools and Easy Magic TWRP.
      If you want i will make detailed guides for each tool.

      Delete
  3. This is my build.prop for Galaxy A8 2016 (SM-A810F) DUOS
    -----

    # begin build properties
    # autogenerated by buildinfo.sh
    ro.build.id=MMB29K
    ro.build.display.id=MMB29K.A810FXXU1API7
    ro.build.version.incremental=A810FXXU1API7
    ro.build.version.sdk=23
    ro.build.version.preview_sdk=0
    ro.build.version.codename=REL
    ro.build.version.all_codenames=REL
    ro.build.version.release=6.0.1
    ro.build.version.security_patch=2016-09-01
    ro.build.version.base_os=
    ro.build.date=Mon Sep 19 19:39:16 KST 2016
    ro.build.date.utc=1474281556
    ro.build.type=user
    ro.build.user=dpi
    ro.build.host=SWDD6301
    ro.build.tags=release-keys
    ro.build.flavor=a8xeltejt-user
    ro.product.model=SM-A810F
    ro.product.brand=samsung
    ro.product.name=a8xeltejt
    ro.product.device=a8xelte
    ro.product.board=universal7420
    # ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
    # use ro.product.cpu.abilist instead.
    ro.product.cpu.abi=arm64-v8a
    ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi

    ReplyDelete
  4. ro.product.cpu.abilist32=armeabi-v7a,armeabi
    ro.product.cpu.abilist64=arm64-v8a
    ro.product.manufacturer=samsung
    ro.product.locale=en-GB
    ro.wifi.channels=
    ro.board.platform=exynos5
    # ro.build.product is obsolete; use ro.product.device
    ro.build.product=a8xelte
    # Do not try to parse description, fingerprint, or thumbprint
    ro.build.description=a8xeltejt-user 6.0.1 MMB29K A810FXXU1API7 release-keys
    ro.build.fingerprint=samsung/a8xeltejt/a8xelte:6.0.1/MMB29K/A810FXXU1API7:user/release-keys
    ro.build.characteristics=nosdcard,skt
    # Samsung Specific Properties
    ro.build.PDA=A810FXXU1API7
    ro.build.hidden_ver=A810FXXU1API7
    ro.config.rm_preload_enabled=0
    ro.build.changelist=9227245
    ro.product_ship=true
    ro.build.official.release=true
    ro.chipname=exynos7420
    # end build properties

    #
    # HWUI_BUILD_PROPERTIES
    #
    ro.hwui.texture_cache_size=50
    ro.hwui.layer_cache_size=34
    ro.hwui.path_cache_size=10
    ro.hwui.texture_cache_flushrate=0.4
    ro.hwui.shape_cache_size=4
    ro.hwui.gradient_cache_size=2
    ro.hwui.drop_shadow_cache_size=6
    ro.hwui.r_buffer_cache_size=4
    ro.hwui.text_small_cache_width=1024
    ro.hwui.text_small_cache_height=1024
    ro.hwui.text_large_cache_width=2048
    ro.hwui.text_large_cache_height=1024
    ro.hwui.fbo_cache_size=16
    #
    # from device/samsung/a8xelte/system.prop
    #
    #
    # system.prop for universal7420
    #
    ro.arch=exynos7420
    persist.demo.hdmirotationlock=false
    ro.zygote.disable_gl_preload=1

    ro.sf.lcd_density=480

    # Multimedia property for Smart View
    media.enable-commonsource=true

    # Multimedia property for Camcorder Recording
    media.sfrec.adj_frames=2

    # SAMPOo
    sys.config.samp_spcm_enable=true
    sys.config.spcm_db_enable=true
    sys.config.spcm_db_launcher=true
    sys.config.spcm_preload_enable=true

    #
    # ADDITIONAL_BUILD_PROPERTIES
    #
    ro.astcenc.astcsupport=1
    ro.mct.compressiontype=ETC1
    ro.config.tima=1
    ro.config.timaversion=3.0

    ReplyDelete
  5. ro.config.dmverity=true
    ro.config.rkp=true
    ro.config.kap_default_on=true
    ro.config.kap=true
    ro.multisim.simslotcount=2
    persist.radio.sib16_support=0
    ro.telephony.default_network=9
    dalvik.vm.image-dex2oat-filter=speed
    dalvik.vm.dex2oat-filter=speed
    ro.config.ringtone=Over_the_Horizon.ogg
    ro.config.notification_sound=Grace_Note.ogg
    ro.config.alarm_alert=Morning_Flower.ogg
    ro.config.media_sound=Media_preview_Touch_the_light.ogg
    ro.config.ringtone_2=Basic_Bell.ogg
    ro.config.notification_sound_2=S_Charming_Bell.ogg
    dalvik.vm.heapstartsize=8m
    dalvik.vm.heapgrowthlimit=256m
    dalvik.vm.heapsize=512m
    dalvik.vm.heaptargetutilization=0.75
    dalvik.vm.heapminfree=2m
    dalvik.vm.heapmaxfree=8m
    ro.opengles.version=196609
    ro.sf.lcd_density=480
    debug.hwc.force_gpu=0
    debug.hwc.nodirtyregion=0
    debug.hwc.winupdate=1
    drm.service.enabled=true
    ro.hdcp2.rx=tz
    ro.secwvk=220
    ro.securestorage.support=true
    ro.build.scafe.size=short
    ro.build.scafe.shot=double
    ro.build.scafe.cream=white
    ro.build.scafe.version=2016B
    ro.sec.fle.encryption=true
    ro.im.param.offset=7341648
    ro.me.param.offset=7341728
    ro.sn.param.offset=7341808
    ro.pr.param.offset=7341888
    ro.sku.param.offset=7341968
    security.mdpp=None
    ro.security.mdpp.ver=2.0
    ro.security.mdpp.release=6
    security.mdpp.result=None
    ro.hardware.keystore=mdfpp
    ro.security.vpnpp.ver=1.4
    ro.security.vpnpp.release=7.0
    ro.error.receiver.default=com.samsung.receiver.error
    ro.frp.pst=/dev/block/persistent
    ro.config.dha_cached_min=6
    ro.config.dha_cached_max=16
    ro.config.dha_empty_init=32
    ro.config.dha_empty_max=32
    ro.config.dha_lmk_scale=0.414
    ro.config.dha_pwhitelist_enable=1
    ro.config.fall_prevent_enable=true
    config.disable_atlas=true
    sys.config.samp_oak_enable=true
    sys.config.samp_oakoom_enable=true
    sys.config.bigdata_enable=true
    sys.config.bigdata_mem_enable=true
    keyguard.no_require_sim=true
    ro.carrier=unknown
    ro.com.google.clientidbase=android-samsung
    ro.security.icd.flagmode=multi
    security.ASKS.policy_version=000000
    ro.ril.hsxpa=1
    ro.ril.gprsclass=10
    ro.adb.qemud=1
    ro.setupwizard.mode=OPTIONAL
    ro.com.google.gmsversion=6.0_r6
    ro.build.selinux=1
    persist.sys.dalvik.vm.lib.2=libart.so
    dalvik.vm.isa.arm64.variant=generic
    dalvik.vm.isa.arm64.features=default
    dalvik.vm.isa.arm.variant=cortex-a15
    dalvik.vm.isa.arm.features=default
    ro.config.knox=v30
    ro.kernel.qemu=0
    net.bt.name=Android
    dalvik.vm.stack-trace-file=/data/anr/traces.txt
    ro.build.version.sdl=2302
    ro.expect.recovery_id=0x3d09027d9db141f197e9cb1cf71009e513a34959000000000000000000000000

    By the way my device isn't MTK so MTKdroid will not work for my device...

    ReplyDelete
  6. As i can see there in your buid.prop you are using Samsung Galaxy A8 A810F model.
    Your device have Samsung's Eynox chipset.
    And this guide is for Mediatek devices only; so sadly none of the above method will work for you.
    You will have to port recovery from source. Head over to the official guide to compile TWRP..

    ReplyDelete
  7. Hiiii....
    My phone is Intex aqua Power Hd
    And im not able to find stock recovery
    There is no boot.img or recovery.img
    What should I do know?????






    Plz Rply Fast....

    ReplyDelete
    Replies
    1. What is your device model number. you can get recovery and boot
      image from the stock firmware of your device. or you can extract
      from your device. there are many applications that let you backup
      your boot and recovery image. but for that you'll need root
      access. so just root your phone and backup recovery and boot. as
      far as i can remember Flashify
      let you backup both. If you are not rooted and want to root your device you can read about it here.
      How To ROOT

      Delete
  8. Or can u say me
    Where can I find my stock Boot.img or recovery.img?????

    ReplyDelete
  9. Manufacturer- Intex
    Model- Aqua power Hd

    Mediatek mt6592


    My device is rooted..

    I have tried many apps but when I click Backup Recovery app automatically stops


    And I have also searched in mY system but there is no recovery.img or boot.img...
    N I have also tried Terminal emulator method....
    Nothing is working...


    Plz give some solutions yaar.... I am tired finding it

    ReplyDelete
    Replies
    1. [You can not find boot and recovery images in system. They are stored in a different partition.]

      I have searched and found some links for stock rom for your device but
      as there is no specific model number it is quite difficult to say that those firmware are for mentioned device and will work 100%.

      As i mentioned earlier you can find your stock recovery.img in the stock firmware.
      So if you can find a reliable source to get stock firmware then get it
      (and just to make sure compare both build.prop and make sure device make, model are same.) and use recovery.img of that firmware.

      One more thing you can try is backup your current rom with MTKDroidTools and readback it with SP Flash tool.
      with this method you will get your own original stock SPTool flashable firmware.
      And then you can use its recovery or boot images.

      Delete
  10. but bro I Have tried MtkDroidTools...
    It Always says "Device not revealed, Connect or reconnect."

    Installed all Adb drivers...



    This phone is A fuck bitch phone I'm ferd of this...
    there is no custom rom, no custom recovery, no updates coming for this phone....


    Can u help me to connet My device with Pc...
    I have tried a Lot but it Cannot....


    Plz Help bro....

    ReplyDelete
    Replies
    1. this is just a driver problem
      install mtk vcom drivers.
      and ADB_usb_driver.
      Download from here Adb and mtk vcom drivers
      if it dont work we'll try on remote connection.
      Because we can not say how much time it will take to do
      so will have to do this on a free day.
      i'll let you know if i got free time.

      Delete
  11. Sir i have problem when i port my recovery and iflash to my oppo f1 mt6750 going to recovery i stock on recovery and reboot normaly
    What im going to do
    Please help me

    ReplyDelete
    Replies
    1. Make sure your recovery size do not exceeds from the size of your recovery partition(or stock recovery). use mtk droid tools to find your partitions size.

      Delete
    2. My phliz recovery sIze is 1280*720
      My phone is size is 1280*720
      When i go to recovery mode
      I see
      Not mount cache
      Not mount system
      Not mount data
      After 1mins reboot auto
      Plz help me

      Delete
    3. Edit mount points in
      recovery\ramdisk\fstab.*** and
      recovery\ramdisk\etc\recovery.fstab

      Delete
    4. Why sir i already edit the recovery.fstab is that problem when not editing a fstab

      Delete
    5. Yes, You have to edit every file which contains system paths.
      without correct mount points recovery can not detect system partitions.

      So basically check every file in 'recovery\ramdisk' and if it contains system paths/mount points, edit them according to your stock recovery.

      Delete
  12. Another question what is kernel header im extract my recovery port and no found the kernel header im only found is recovery kernel and recovery offset is that correct or not?
    Plz reply sir

    ReplyDelete
    Replies
    1. Header is in zImage. It depends on the tool you are using, that how it handles the kernel and also the methods used to compile it. Generally you won't see kernel headers separately.

      Delete
  13. Hii i cant see files like ueventd.goldfish.rc and fstab.and how can i get boot.img i get recovery.img from flashify.

    ReplyDelete
    Replies
    1. If you don't have the files just skip them.
      boot.img = kernel.
      So go on backup/restore option in flashify and choose to backup current kernel.

      Delete
  14. This comment has been removed by the author.

    ReplyDelete
  15. I skip that files but still nothing happened. Can u please create a recovery for my phone?? My phone is swipe elite 2 android 5.1 mt6735 1gb ram and my recovery and boot image link https://drive.google.com/file/d/0B-lDz-dagHGIRzZuVmt3T05ydU0/view?usp=drivesdk

    ReplyDelete
    Replies
    1. Your zip file seems to be corrupted. please upload it again.

      Delete
  16. https://drive.google.com/file/d/0B-lDz-dagHGIcjNYOHJxWWs4VW8/view?usp=drivesdk

    ReplyDelete
    Replies
    1. Please provide more details about your device.

      Delete
  17. Swipe elite 2 540x960 4.5 inch display mediatek mt6735 1 gb ram 8 gb rom android 5.1 1.3 quad core processors

    ReplyDelete
    Replies
    1. Please note that i do not have physical access to the device. and it is highly possible that these recovery's won't work. You should try automated tools or try to make the recovery's by yourself before trying these or ask any experienced dev who have physical access to your device.

      It could lead to brick your device.
      I will not take any responsibility if anything happens to your device.Before making any changes to system you must know how to fix your device if anything goes wrong.

      And ethically i should not help you by porting the recovery for you when i dont have the device with me.

      but if you still want it badly{like you cant live without it}

      Again!!!!! No Guaranty's!!!! Dont blame me for anything!

      Here you can try these recovery's. Download

      try one by one..

      Delete
  18. Thanx a loooooooooot twrp works and installed successfully .all file works.really thanks a lot😁😁😁

    ReplyDelete
    Replies
    1. :) welcome. do check if everything is working. like storage, and you are able to perform all actions. and if you want you can change device info in default.prop (last part of the guide).
      and if you please tell your friends about this website.

      Delete
  19. sir i have problem with my phone after flash twrp 3.0.. my phone going bootlop. can u please create a recovey for my phone to? my phone is meitu v4 5 inch display mediatek mt6795 ram 2 gb 64 rom android 5.1.
    i understand the risk and im not blame anyone. thank for help and sorry for bad english

    ReplyDelete
    Replies
    1. I am sorry but i have already said before that it is not possible to port recovery's or rom's for individual devices.

      I have ported the recovery for the guy above just to show that the process in this article works 100% if you follow it correctly.

      Check your devices mount points and edit them in files mentioned in the guide correctly.
      Also check your recovery partition size, And make sure your ported recovery's size do not exceed from max partition size.

      Delete
  20. ok sir, thank you very much

    ReplyDelete
    Replies
    1. Just try to port it again carefully. I am sure you will get success.

      Delete
  21. If someone is interested in helping me out to port TWRP on my device, here is the link of my stock recovery and scatterfile as well doc´s with the build number in written
    If possible also edit the scatterfile so apps can be working from the external sdcard because it is not supported can´t push the apps2sdcard ihave tried with carlivimagekitchen, still no succes,
    Many thanks

    i can´t rewrite the scatterfile

    https://drive.google.com/file/d/0B3JLexZp6srIaDk3UGZkRm1WbXc/view?usp=sharing

    ReplyDelete
  22. pls I need guide on rooting and installing custom recovery
    my email is donzeegy@gmail.com

    Hotwav Pixel 2 Specs:

    Hotwav Pixel 2 Fingerprint
    4GB RAM
    64GB Storage
    5.5 inch Full HD LCD
    2 Real Camera,4G
    Android 6.0
    Octa Core 1.5GHz Processor

    this is all the info I can get.
    pls help

    ReplyDelete
  23. I need twrp for my device. i tried rooting my device with most apps and rooting software with no results.My device is verykool cyprus li S6005. mt6580. marshmallow 6.0. I cant find custom rom, stock rom, or custom recovery for it. Dont know how you can assist with this. thanks in advance

    ReplyDelete
    Replies
    1. you can try above method to port a custom recovery for your device. after that rooting and creating custom roms will be very easy.

      Delete
  24. I thank u so much for your quick reply. Yes Sir. tried mtk droid tools but could not recognize my device which i thought to be for the fact that device is not rooted or so. i also tried fastboot with adb but received report that file i tried to flash was to large which caused me to doubt the twrp i downloaded. i dont have any rom for my device at the or scatter file. And my device is Verykool cpyrus ll S6005. mt6580 marshmallow 6.0. Kenel 3.18.19+ I really appreciate Sir

    ReplyDelete
    Replies
    1. Check what is your recovery partition size, and compare it with the recovery you have made. its size should not exceed than the recovery partition.
      there are some useless files in recovery img, like languages and some images, you can delete those language files and try to reused the image files size.
      point is make the recovery img smaller in size so it can fit in your recovery partition.
      OR
      first try to root your device. there are guides on this blog which will help you in rooting. after rooting it will be easier to use mtk droid tools and other tools.

      Delete
    2. If u havnt the scatter file then how did u flash the ported twrp??

      Delete
  25. I dont have any rom, scatter file or twrp. and my device is not rooted

    ReplyDelete
  26. kernel: Linux version 3.18.19+gcc version 4.8 (GCC) #2 SMP PREEMTP
    Machine: armv7l

    ReplyDelete
  27. This comment has been removed by the author.

    ReplyDelete

Disable_Adblock

We know Ads suck, but at IrisBuddies we will not let them do that
As blocking is a good idea to get rid of stupid “Download Now” Buttons around the web
That’s not in our case. We think you won't find Ads on Our site terrible or annoying
Support us by Whitelisting “IrisBuddies” on your Adblocking Plugin or By disabling your AdBlocking software

If you think this is not good and we should allow AdBlocking Plugins
then Please Contact Us or write us on our Facebook Page
and we might allow it in near future.