[TWRP] [CORRECTION] [NORA] 64 bit TWRP for Moto E5

Search This thread

Tawsif999

Senior Member
1681083532283.png


Introduction

I'm not a developer. After 4 days of messing with files I made this using AIK (Android Image Kitchen). It include files from different TWRPs. The theme is not mine. I provided all credits below.

As you guys know, our 64 bit TWRP from this thread is usable, but has some major bugs. Specially the touchscreen doesn't work & it's too big to flash. Now, here is a fixed twrp, no need to hassle with OTG & adb anymore!

Installation

Command-

fastboot flash recovery <filename>.img

Booting into TWRP-

- Power off
- Volume down + Power
- Keep pressing volume down until Recovery mode option comes
- Press power

Or,

Command-

adb reboot recovery


Install magisk.zip to avoid twrp being replaced by the stock recovery

Decryption

- Format data
- Install Disable_Dm-Verity_ForceEncrypt.zip


My works


I didn't know these steps from the beginning. I had to discover these. After 30-40 attempts & making 7 versions, the final result came out. To make the thread "To the point" here is what I did for the final one-

Touchscreen Fix :

- Extracted the old TWRP and started modifying it.
- Extracted plus-linux kernel, took "kernel image" & "kernel offset" from there. Inside TWRP, replaced kernel image & kernel offset with these new files. Touchscreen got fixed.


Minimal size :

The TWRP file must be 16 MB or less to be flashable for moto e5. This is because the device has very low recovery partition size. Making a 64 bit TWRP v3.7 under 16 MB was almost an impossible task. Here is how I finally did it-

- Removed txt files.
- Replaced /ramdisk/sbin/ folder with the sbin folder of official TWRP for Asus Nexus 7 2012 3G. This greatly reduced the file size & also made the TWRP v3.7. This happened because that TWRP is 32 bit. Means I used sbin from a 32 bit recovery. But our TWRP didn't become 32 bit because "bit" depends on split_image folder (specially kernel image file inside it)- not sbin folder. After this step, the twrp became 15.1 MB !
- Because of the previous step, a bug came where the cursor was always showing on the middle of the screen even though I was not using mouse via OTG. So I replaced cursor.png with a completely transparent image. So now, the cursor is hidden. And also you won't see cursor while using mouse. But no one need that, as touchscreen is fixed.
- Replaced files inside /ramdisk/twres/ with the files I got by extracting flashable zip of SHADOW"S BLACK THEME. We had a useless font that took almost 4 MB in our old TWRP. After doing the step, got the same font in 100 kb. But the overall file size increased because of new images in /ramdisk/twres/images folder. These images makes the recovery look better. After all, the size became 15.4 mb.

The steps look pretty much easier. But I had to suffer 3 days to discover them. I can briefly say that I ported a 32 bit twrp, used sbin from 8 TWRPs, tried to port 64 bit, removed languages and fonts, removed files from sbin folder, repacked & booted image every time after making every single changes, compressed images using online tools and many more !


I shared all these in case anyone finds them useful.


Bugs

- Adb push / pull (Sideload works though)
- Terminal
NB. Use adb version (boot only) to use adb features like push/pull & inbuilt terminal.
- MTP (Read File Transfer part)


File Transfer

MTP works fine. If you aren't able to use mtp & adb (in adb version), the problem is related to drivers. Here is the fix for windows (Sorry for linux / mac)-

1. Download Drivers.zip.
2. While in twrp, connect it with computer.
3. Go to device manager & uninstall devices related to adb - mtp. Adb device can be under "universal serial bus devices".
4. Disconnect the mobile.
5. In Device Manager, click on view & select "show hidden devices".
6. Again, Uninstall all drivers/devices related to adb - mtp.
7. Re-connect the mobile.

If windows doesn't install the drivers / the installed driver doesn't work, uninstall those and install working drivers manually-

How to install the drivers?
Install automatically- Run the exe file
Install manually
(Recommended) - Device manager > Right click on the device > Update driver > Browse my computer >Let me pick > Have disk > Browse > Select the appropiate .inf file provided in each folder.

If you can't see mtp device under portable devices, try running the mtp driver exe file & reconnecting. However, adb fix is guaranteed. Good luck for MTP!

Download

adb version (boot only) - Drive / Mega

v2.1- Drive / Mega

v2.1 (stock)- Drive / Mega


v2- Drive / Mega

v1- Drive / Mega

Drivers.zip- Drive / Mega


Disable dm verity force encrypt

Credits & Links
 

Attachments

  • Screenshot_1970-01-04-22-32-17.png
    Screenshot_1970-01-04-22-32-17.png
    68.5 KB · Views: 82
  • Screenshot_1970-01-04-22-32-22.png
    Screenshot_1970-01-04-22-32-22.png
    72.6 KB · Views: 72
  • Screenshot_1970-01-04-22-32-33.png
    Screenshot_1970-01-04-22-32-33.png
    72 KB · Views: 69
  • Screenshot_1970-01-04-22-32-38.png
    Screenshot_1970-01-04-22-32-38.png
    94.2 KB · Views: 61
  • Screenshot_1970-01-04-22-32-47.png
    Screenshot_1970-01-04-22-32-47.png
    67.7 KB · Views: 53
  • Screenshot_1970-01-04-22-32-51.png
    Screenshot_1970-01-04-22-32-51.png
    96.5 KB · Views: 55
  • Screenshot_1970-01-04-22-33-09.png
    Screenshot_1970-01-04-22-33-09.png
    87.2 KB · Views: 57
Last edited:

Tawsif999

Senior Member
Changelog

Version 2.1
- Removed "Install twrp app" screen

Version 2
- Fixed empty area in Advanced options
- Fixed stock theme version error
- Fixed override font error
- Fixed all string resource errors

- Removed all other languages rather than English (Other languages have font problems. And I can't add more fonts because of limited partition size)
 
Last edited:
  • Like
Reactions: kenshinta

kenshinta

Senior Member
Dec 13, 2004
411
65
Redmi Note 10S
Any plans for further updates?

If yes may I suggest the following:

1. Be able retain settings (ex. The prompt to install the twrp app, even if turned off, at next use it still prompts)

2. Use graphics resources of plain twrp, at least with keyboard and navbar, better with everything though.
 

Tawsif999

Senior Member
Any plans for further updates?

If yes may I suggest the following:

1. Be able retain settings (ex. The prompt to install the twrp app, even if turned off, at next use it still prompts)

2. Use graphics resources of plain twrp, at least with keyboard and navbar, better with everything though.
Actually I had to reset my whole computer & lost all my works. I made a list of best working gsi builds for both stock & custom rom. The gsis over stock rom didn't have graphics issues. And I also created other recoveries such as orange fox, Pitch black which were large to flash though. But I lost all of these 😣

I will try to remove that prompt.

And will make a stock theme variant as well. Thanks 😃
 
  • Like
Reactions: whodat711

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    1681083532283.png


    Introduction

    I'm not a developer. After 4 days of messing with files I made this using AIK (Android Image Kitchen). It include files from different TWRPs. The theme is not mine. I provided all credits below.

    As you guys know, our 64 bit TWRP from this thread is usable, but has some major bugs. Specially the touchscreen doesn't work & it's too big to flash. Now, here is a fixed twrp, no need to hassle with OTG & adb anymore!

    Installation

    Command-

    fastboot flash recovery <filename>.img

    Booting into TWRP-

    - Power off
    - Volume down + Power
    - Keep pressing volume down until Recovery mode option comes
    - Press power

    Or,

    Command-

    adb reboot recovery


    Install magisk.zip to avoid twrp being replaced by the stock recovery

    Decryption

    - Format data
    - Install Disable_Dm-Verity_ForceEncrypt.zip


    My works


    I didn't know these steps from the beginning. I had to discover these. After 30-40 attempts & making 7 versions, the final result came out. To make the thread "To the point" here is what I did for the final one-

    Touchscreen Fix :

    - Extracted the old TWRP and started modifying it.
    - Extracted plus-linux kernel, took "kernel image" & "kernel offset" from there. Inside TWRP, replaced kernel image & kernel offset with these new files. Touchscreen got fixed.


    Minimal size :

    The TWRP file must be 16 MB or less to be flashable for moto e5. This is because the device has very low recovery partition size. Making a 64 bit TWRP v3.7 under 16 MB was almost an impossible task. Here is how I finally did it-

    - Removed txt files.
    - Replaced /ramdisk/sbin/ folder with the sbin folder of official TWRP for Asus Nexus 7 2012 3G. This greatly reduced the file size & also made the TWRP v3.7. This happened because that TWRP is 32 bit. Means I used sbin from a 32 bit recovery. But our TWRP didn't become 32 bit because "bit" depends on split_image folder (specially kernel image file inside it)- not sbin folder. After this step, the twrp became 15.1 MB !
    - Because of the previous step, a bug came where the cursor was always showing on the middle of the screen even though I was not using mouse via OTG. So I replaced cursor.png with a completely transparent image. So now, the cursor is hidden. And also you won't see cursor while using mouse. But no one need that, as touchscreen is fixed.
    - Replaced files inside /ramdisk/twres/ with the files I got by extracting flashable zip of SHADOW"S BLACK THEME. We had a useless font that took almost 4 MB in our old TWRP. After doing the step, got the same font in 100 kb. But the overall file size increased because of new images in /ramdisk/twres/images folder. These images makes the recovery look better. After all, the size became 15.4 mb.

    The steps look pretty much easier. But I had to suffer 3 days to discover them. I can briefly say that I ported a 32 bit twrp, used sbin from 8 TWRPs, tried to port 64 bit, removed languages and fonts, removed files from sbin folder, repacked & booted image every time after making every single changes, compressed images using online tools and many more !


    I shared all these in case anyone finds them useful.


    Bugs

    - Adb push / pull (Sideload works though)
    - Terminal
    NB. Use adb version (boot only) to use adb features like push/pull & inbuilt terminal.
    - MTP (Read File Transfer part)


    File Transfer

    MTP works fine. If you aren't able to use mtp & adb (in adb version), the problem is related to drivers. Here is the fix for windows (Sorry for linux / mac)-

    1. Download Drivers.zip.
    2. While in twrp, connect it with computer.
    3. Go to device manager & uninstall devices related to adb - mtp. Adb device can be under "universal serial bus devices".
    4. Disconnect the mobile.
    5. In Device Manager, click on view & select "show hidden devices".
    6. Again, Uninstall all drivers/devices related to adb - mtp.
    7. Re-connect the mobile.

    If windows doesn't install the drivers / the installed driver doesn't work, uninstall those and install working drivers manually-

    How to install the drivers?
    Install automatically- Run the exe file
    Install manually
    (Recommended) - Device manager > Right click on the device > Update driver > Browse my computer >Let me pick > Have disk > Browse > Select the appropiate .inf file provided in each folder.

    If you can't see mtp device under portable devices, try running the mtp driver exe file & reconnecting. However, adb fix is guaranteed. Good luck for MTP!

    Download

    adb version (boot only) - Drive / Mega

    v2.1- Drive / Mega

    v2.1 (stock)- Drive / Mega


    v2- Drive / Mega

    v1- Drive / Mega

    Drivers.zip- Drive / Mega


    Disable dm verity force encrypt

    Credits & Links
    1
    Changelog

    Version 2.1
    - Removed "Install twrp app" screen

    Version 2
    - Fixed empty area in Advanced options
    - Fixed stock theme version error
    - Fixed override font error
    - Fixed all string resource errors

    - Removed all other languages rather than English (Other languages have font problems. And I can't add more fonts because of limited partition size)
    1
    Any plans for further updates?

    If yes may I suggest the following:

    1. Be able retain settings (ex. The prompt to install the twrp app, even if turned off, at next use it still prompts)

    2. Use graphics resources of plain twrp, at least with keyboard and navbar, better with everything though.
    Actually I had to reset my whole computer & lost all my works. I made a list of best working gsi builds for both stock & custom rom. The gsis over stock rom didn't have graphics issues. And I also created other recoveries such as orange fox, Pitch black which were large to flash though. But I lost all of these 😣

    I will try to remove that prompt.

    And will make a stock theme variant as well. Thanks 😃