[TWRP] Ported TWRP Recovery For Moto E4 Mediatek Variant SKU XT1760

[kartik verma]

Read Carefully Before Doing Anything !

Requirement :
- TWRP Recovery TWRP_XT1760_3.1.1_MTKr1.img
- Minimal adb & fastboot
- Installed adb & fastboot drivers
- Moto E4 mediatek variant :laugh:
- Mediatek variant version SKU XT1760 :highfive:
- USB cable :cyclops:
- Unlocked bootloader
- Backup of whole firmware through Miracle Tool :silly:

Bugs :
- Not found yet

How To Enter Fastboot Mode :
- Press power and volume down button along
- When you see START in device screen leave both buttons
- locate to META MODE window only using vol. down button
- It is next to START window
- When you apply commands in fastboot mode
you will see fastboot command execution in this window

How To Install :
- Unpack the zip file first
- Drop TWRP_XT1760_3.1.1_MTKr1.img in this folder
- C:\Program Files\Minimal ADB and Fastboot\TWRP_XT1760_3.1.1_MTKr1.img
- Close this windows now !
- Open Minimal ADB & Fastboot command window

- Type These Fastboot Commands :
- fastboot devices
- fastboot flash recovery TWRP_XT1760_3.1.1_MTKr1.img
- TWRP Recovery installed now !

How To Boot into TWRP :
- Press power button and volume down button along
- When you see START in device screen leave both buttons
- locate to recovery window using vol. keys
- Press power button once
- Now your device boot in TWRP mode
- Done for now !

How To Disable Verity in Order To Boot into System :

( Follow this step if you were going to install TWRP recovery only
else if you want TWRP installed and a rooted device than follow below step. )​

- Place no-dmverity zip file in external SD_CARD
Download link :
http://www.mediafire.com/file/m0w6zu83am6z38i/no-verity-opt-encrypt.zip
- Disable Read-Only Option in TWRP Recovery
- There select allow modifications, swipe, wipe data & cache
- Again boot into TWRP
- Install no-dmverity
- Reboot to system
- Done !

How To Root Moto E4 Mediatek Variant SKU XT1760 :

( Follow this step if you want installed TWRP recovery and a rooted device ! )
Thread link :
https://forum.xda-developers.com/moto-e4/how-to/moto-e4-guide-to-rooting-international-t3657328​

- Still unable to Root this device with SuperSU & Magisk
- SuperSU failed to mount "/" Rootfs
- Magisk failed to load image file​

Downloads TWRP Recovery :
http://www.mediafire.com/file/emz8j0smqdsbc8g/TWRP_XT1760_3.1.1_MTKr1.zip

Credits :

@squid2
for original twrp recovery
and ported by me, from qualcomm variant to mtk variant​

Original Thread Link :
https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160​

 

[drganbds]

Ok stream of development started...thanks karthi for this effort.
Kartik bro does it have dm-verify issues? Do we need to disable dm-verify on first boot to twrp?

 

[kartik verma]

Ok stream of development started...thanks karthi for this effort.
Kartik bro does it have dm-verify issues? Do we need to disable dm-verify on first boot to twrp?

Thread Updated !
Refresh for new content

 

[kartik verma]

@drganbds search for no-dmverity.zip you will find one.
at this time my internet connection is slow cannot upload the file right now.

 

[squid2]

Good to have a TWRP for both variants.

Where did the term "International" come from? Both the Qualcomm and Meditatek versions of the Moto E4 are sold in several countries, so using the term "International" to refer to the MediaTek version seems confusing to me. Users may think "International" works on phones sold in all countries. I think it would be better to name this as TWRP for the MediaTek version rather than "International".

 

[andMego]

Good to have a TWRP for both variants.

Where did the term "International" come from? Both the Qualcomm and Meditatek versions of the Moto E4 are sold in several countries, so using the term "International" to refer to the MediaTek version seems confusing to me. Users may think "International" works on phones sold in all countries. I think it would be better to name this as TWRP for the MediaTek version rather than "International".

But not all users know what mediatek is so It probably makes sense to put "(mediatek)" in the title

 

[amarc78]

But not all users know what mediatek is so It probably makes sense to put "(mediatek)" in the title

Yes, and the model numbers should be specified also. Users just need to know what their model is.

 

[kartik verma]

Good to have a TWRP for both variants.

Where did the term "International" come from? Both the Qualcomm and Meditatek versions of the Moto E4 are sold in several countries, so using the term "International" to refer to the MediaTek version seems confusing to me. Users may think "International" works on phones sold in all countries. I think it would be better to name this as TWRP for the MediaTek version rather than "International".

Thanks for the suggestion

 

[kartik verma]

Yes, and the model numbers should be specified also. Users just need to know what their model is.

updated :good:

 

[kartik verma]

@squid2 @amarc78 @mendelgordon @drganbds

i have some strange problem with my device boot image. it unable to start any external service which i added after unpacking the boot image.
i write this command in init.rc to change sysinit file permission "chmod 0755 /sbin/sysinit". but no 0755 permission to sysinit. also daemon process start by init such as "service sysinit /sbin/sysinit \n oneshot" unable to start on boot. so no init.d support
Any help from your side

 

[drganbds]

@[email protected]@[email protected]

i have some strange problem with my device boot image. it unable to start any external service which i added after unpacking the boot image.
i write this command in init.rc to change sysinit file permission "chmod 0755 /sbin/sysinit". but no 0755 permission to sysinit. also daemon process start by init such as "service sysinit /sbin/sysinit \n oneshot" unable to start on boot. so no init.d support
Any help from your side

Sorry dude im eager to help you but I have very very little knowledge on Linux commands...because I'm a doctor

 

[kartik verma]

Sorry dude im eager to help you but I have very very little knowledge on Linux commands...because I'm a doctor

isn't a big deal. i also a medical stream student

 

[drganbds]

isn't a big deal. i also a medical stream student

I was playing with Linux (Ubuntu) on unpacking and packing boot image for cpu governors, tweaks etc, and with Android kitchens for creating so many roms for grand Quattro device but since 4years I haven't done anything and i stopped it...that's y I couldn't help you...

 

[kartik verma]

I was playing with Linux (Ubuntu) on unpacking and packing boot image for cpu governors, tweaks etc, and with Android kitchens for creating so many roms for grand Quattro device but since 4years I haven't done anything and i stopped it...that's y I couldn't help you...

ok :crying:

 

[andMego]

@[email protected]@[email protected]

i have some strange problem with my device boot image. it unable to start any external service which i added after unpacking the boot image.
i write this command in init.rc to change sysinit file permission "chmod 0755 /sbin/sysinit". but no 0755 permission to sysinit. also daemon process start by init such as "service sysinit /sbin/sysinit \n oneshot" unable to start on boot. so no init.d support
Any help from your side

Isn't kernel adiutor able to add init.d support (not really, but it works)
Edit: Where are you putting those commands? If in TWRP, try in a file explorer like mixplorer. If in a file explorer, try twrp.

 

[kartik verma]

Isn't kernel adiutor able to add init.d support (not really, but it works)
Edit: Where are you putting those commands? If in TWRP, try in a file explorer like mixplorer. If in a file explorer, try twrp.

seriously very strange problem.
init.rc unable to set file permission.

 

[amarc78]

@[email protected]@[email protected]

i have some strange problem with my device boot image. it unable to start any external service which i added after unpacking the boot image.
i write this command in init.rc to change sysinit file permission "chmod 0755 /sbin/sysinit". but no 0755 permission to sysinit. also daemon process start by init such as "service sysinit /sbin/sysinit \n oneshot" unable to start on boot. so no init.d support
Any help from your side

Can you upload the unmodified boot.img for me?

Sent from my LGLS755 using XDA Labs

 

[kartik verma]

Can you upload the unmodified boot.img for me?

sure...

 

[kartik verma]

sure...

https://www.mediafire.com/download/u0ex0htrtmutc15
link

 

[amarc78]

https://www.mediafire.com/download/u0ex0htrtmutc15
link

Try this. Init.d should be enabled. I also removed dm-verity and force encrypt and made it insecure. I wanted to make a flashable zip but I have no device info to do so. You'll have to extract it and flash the img. You might need to add the etc/init.d folder and set it's permissions manually. Let me know if it works ok.