[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] Stranger Absolute:
Hello guys, I am creating this topic to solve a little problem that was happening with the Moto E5 nora.

Before I start talking about this problem, I will make it very clear in this thread that I am talking. And until the end of the last line of this post.

-------------------------------------------------- ---------------------------------------

## IMPORTANT DESCRIPTION ##

MAKING IT CLEAR to the site moderators and the developers of the ROMs I will be quoting here in this post.

I do not and will not, and am not taking these ROMs as my own. I am just solving a problem that to this day there has been no update or patch to fix the touchscreen problem, and that when I downloaded the ROMs I didn't get the touch. Just one, but... this patch is not well configured and some commands are missing in the kernel defconfig /I'm talking about touchfix/ and that is why it is giving problems in video recording or problems in the internet network.

This kernel image that I compiled, and this boot configuration (touch fix) of the rom (Lineage os 17.1) was not used on my boot. i used configuration to subscribe to the boot kernel of the ROMs to be able to boot.

repeating this again for all the ROMs mentioned here. I will not and do not want and am not taking these ROMs as my own. I am just solving this problem that was happening to me.

I am just sharing it with people who are having the same problem as me.

-------------------------------------------------- ---------------------------------------

ROM THAT WILL NOT BE INCLUDED HERE

CARBON-CR-8.0-PAX-UNOFFICIAL

PROBLEM THAT I NOTICED

it won't boot with the kernel that comes with it. And neither with this boot that I compiled.

I know what the problem is, but I won't mention it.

I forgot to mention, this boot is being tested by me. Because I edited its configuration when compiling. I am checking if there are any compilation errors or other problems that might happen in the future. Because of the editing I mentioned

The kernel source doesn't have any problems. Not that I know of.

So I will always update the boot.img when possible

I recommend backing up your sensors. because there are some active sensors in the kernel and I don't know if that can harm it or make it dead.

THIS KERNEL WAS TESTED ON MOTO E5 NORA XT1944-4

note: i only tested it on the xt1944-4, it may work... or not. Depends on the variant

VARIANTS XT1944 -1,-2,-3,-5,-4 -6.

####### WARNING #########

DON'T DO THIS IF YOU DON'T KNOW HOW TO GET OUT OF A BROKEN KERNEL

HAVE A BACKUP BOOT IMG OF THE KERNEL THAT IS WORKING PERFECTLY

SO THAT YOU CAN GET OUT OF THE BROKEN KERNEL

AND THEN JUST PUT IT BACK IN AND EVERYTHING WILL BE FINE.

########+++++########

How to upgrade this kernel

Simple, you can upgrade it via TWRP recovery or fastboot.

fastboot command:

#

flastboot flash boot boot.img

#

What is this kernel for?

Serves to fix the touch screen problem

Improved low memory kill ( I increased the value) (If you have the 1gb of RAM I had, and it won't go out for anything, I recommend switching vendors) ---> no need but because the kernel already does this.

The CPU governor is no longer interactive (is not needed in this kernel.) (Also... not stock. and yes custom.)

And the problem of prolonged recording or as we know ldk (has been fixed)

And others.

with recovery: (TWRP)

Go to install in recovery

Look for the folder where you left the boot, either on the memory card or on the USB stick.

And of course, choose the install image option so that the image you downloaded appears.

And where is this installation image option? Right when you select install on the home screen when you login. Right below it, it will be on the side of select storage. Just change it to install image .

Download the boot kernel img​

aicp nora =1

AospExtended v7.3 =2 (stable)

Arrow-v10.0 =3 (unstable)

crDroid Android 10.0 =4 (unstable)

DerpFest-10-Bare =5

ion-2.9.a-EOL-nora =6

lineageos_17.1 =7 (unstable)

Nusantara_LTS-10 =8 (recommended)

PixelExperience_nora =9 (stable)

PixelExperience_Plus_nora =10 (unstable)

PixelPlusUI_2.0_nora =11 (recommended)

Resurrection Remix-Q-8.7.3-nora =12 (unstable)

Xtended-Tribute-To-MartinCoulon-nora =13

Havoc-OS-v3.12-nora =14 (recommended)

in case no one understands the corresponding ROM name. just follow the corresponding boot number

Just look at the ROM name when you download it. When it is already in .zip and so you find the corresponding boot.

Why so many boot img?

Unfortunately, a single boot.img will not work for all ROMs. After that the system will not accept booting another build of the system.

-------------------------------------------------- ------------------------------------

When downloading, rename it to boot.img

THESE ROMS ARE ALL FROM XDA THAT ARE HERE FROM NORA

Kernel: plus-LINUX

Sources code: https://github.com/E5Series/kernel_motorola_msm8953-3.18

Compile: GCC aarch64 linux android 4.9 lineage 19.1

Compile 32bits: GCC arm linux androideabi 4.9 lineage 19.1

Unfortunately defconfig is not there in the sources, I had to remove it from the ROM in order to compile.

Just so someone knows where I got it from 😁, in case you want to compile

----------------------------------------------------------------+----------------------------

problems, improvements and answers...​

This kernel is running very well on Android 11. well.. depending on which custom android 11 you run with it. it can run bad or good, it will just depend on which GSI build.

From my tests that I did, there are certain custom ROMs of the moto E5 that are not very well optimized or stable. I recommend you to use Havoc OS and Nusantara LTS ROMs. Why them?? From my tests they performed very well with the kernel. Remembering that you don't have to use them obligatorily. And just my guess for you don't have problems like some bugs in the ROM itself. I'm not guaranteeing you won't get bugs with those either.

Now you can use the ROMs you want now without touch problem.

And if there's a bug in the ROM I'm using, can I send it to you? Not really, remembering that I'm not the owner of these ROMs that I've sited here. If that happens, there is nothing I can do about it. I recommend that you get the developer of the ROM you are using to solve it himself.

Already on Android 12 it will not work very well because of the vendor. If you are going to use Android 12 you will have to look for a vendor for a specific compilation for it. I don't recommend you use the build of Android 10 that already comes in the ROM because it doesn't hold Android 12 as it will make it restart all the time.

recommend (default) (required) (alert)​

I recommend that you use a swap for this kernel. I mean, don't use the swap itself from the rom. well, use a swap that take and that is more efficient. Let it really work. Because so out of nowhere. Recently I found out that roms swap doesn't work. Or it works, but not as swap or zram. I honestly don't really know what it's for. Leaving a warning for you about what I discovered. This will make the default for upcoming updates.​

The names of the ROM that were quoted here are not mine. I'm not sending them as mine and I don't want to and shouldn't.

Just a reminder.

Update for V2...​

update coming soon.....​