Related
My current android version is jellybean I want to update kernel 4.4
I don't want to replace my stock rom
Just want to update my stock kernel to custom kernel
Is it possible? ?
So
I search for
EvolutionKernel
But in downloading it gives 3 files of same version zip md5 tar so in my
Cwm support only for zip so how to flash
I have taken backup from cwm in backup folder cwm put many file so I am confused which file use to restore if any thing wrong
Give nebula kernel a try since you're on 4.4.4
current android version is 4.2.2 jellybean
osas514 said:
Give nebula kernel a try since you're on 4.4.4
Click to expand...
Click to collapse
My android version is jellybean not kitkat
You have to use Evolution Kernel (Stock) from here. You choose the version though it's always better to use the latest. Give v.1.7.9 a try as its latest from k2wl stable.
Please tell me which to choose
osas514 said:
Give nebula kernel a try since you're on 4.4.4
Click to expand...
Click to collapse
Trilochanaaya said:
You have to use Evolution Kernel (Stock) from here. You choose the version though it's always better to use the latest. Give v.1.7.9 a try as its latest from k2wl stable.
Click to expand...
Click to collapse
EvolutionKernel-stock-v1.7.9-k2wl-20140504-1803.zip
5.4MB May 04, 2014 | 08:05AM
257 dls
EvolutionKernel-stock-v1.7.9-k2wl-20140504-1803.zip.md5
86B May 04, 2014 | 08:05AM
93 dls
EvolutionKernel-stock-v1.7.9-k2wl-20140504-1803.zip.sha1
Mine is jellybean want to update to kitkat kernel
Taken backup with rom manger
Is it sufficient
sushantraje2000 said:
EvolutionKernel-stock-v1.7.9-k2wl-20140504-1803.zip
5.4MB May 04, 2014 | 08:05AM
257 dls
EvolutionKernel-stock-v1.7.9-k2wl-20140504-1803.zip.md5
86B May 04, 2014 | 08:05AM
93 dls
EvolutionKernel-stock-v1.7.9-k2wl-20140504-1803.zip.sha1
Mine is jellybean want to update to kitkat kernel
Taken backup with rom manger
Is it sufficient
Click to expand...
Click to collapse
Flash this kernel through recovery and remember to wipe cache/dalvik cache after flashing and reboot.
thank you for support
just waiting for OTG full support
read about 1.8.1 otg part 1 enable
will this kernel work on stock rom
will this kernel work on stock rom or which rom support
sushantraje2000 said:
will this kernel work on stock rom or which rom support
Click to expand...
Click to collapse
It's only for Stock!
Google play store stop working
After installing this kernel
Google play stop working say unfortunately Google play store stop
Tried with clear cache
Remove Google account
And which tunner available for this kernel evolution
sushantraje2000 said:
After installing this kernel
Google play stop working say unfortunately Google play store stop
Tried with clear cache
Remove Google account
And which tunner available for this kernel evolution
Click to expand...
Click to collapse
Wipe Dalvik Cache also.
unknown volume for path [/sd -evt]
Trilochanaaya said:
Wipe Dalvik Cache also.
Click to expand...
Click to collapse
unknown volume for path [/sd -evt] coming while again I trying to clear dalvik
That msg was coming again n again cel was getting stuck
So I factory reset
Now when I am trying to add Google account after entering username and password it saying could not established reliable connection
where I can get advantage n disadvantages of this kernel
where I can get advantage n disadvantages of this kernel
Like here screen shot not working
sushantraje2000 said:
just waiting for OTG full support
read about 1.8.1 otg part 1 enable
Click to expand...
Click to collapse
I don't understand what are u talking about! There is no v1.8.1 for Evolution Kernel(Stock).
please visit this link
Trilochanaaya said:
I don't understand what are u talking about! There is no v1.8.1 for Evolution Kernel(Stock).
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2564504
Version 1.8.1
- USB host notify enabled [OTG part 1]
- Given more power to USB fsa9845 switch
- reverted back to 4.9.1 linaro toolchain.
- few battery saving and performance tweaks
unable to on wifi
problem was occurring still so i restore my previous working kernel
now i am not able to switch on WIFI
sushantraje2000 said:
http://forum.xda-developers.com/showthread.php?t=2564504
Version 1.8.1
- USB host notify enabled [OTG part 1]
- Given more power to USB fsa9845 switch
- reverted back to 4.9.1 linaro toolchain.
- few battery saving and performance tweaks
Click to expand...
Click to collapse
I know that u r messing up things. Read the warning of the thread which u have given as link. That kernel is only for CM/AOSP Roms based on Kitkat. U said u r on stock ROM that's why i have given link for Evolution Kernel Stock. If u are unable to follow what has been suggested, I cannot suggest u any further on this. Sorry.
Trilochanaaya said:
I know that u r messing up things. Read the warning of the thread which u have given as link. That kernel is only for CM/AOSP Roms based on Kitkat. U said u r on stock ROM that's why i have given link for Evolution Kernel Stock. If u are unable to follow what has been suggested, I cannot suggest u any further on this. Sorry.
Click to expand...
Click to collapse
ok sorry was totally my mistake
but can you please help me to restoring previous backup
please tell me solution on wifi
Hello,
I tried flashing v1.7.9 from recovery. I wiped cache and dalvik cache... I'm stuck in boot loop.... For now, I've restored from my back up. KIndly give me a solution to get back to stock kernel..
Right now, I'm on a custom kernel 3.0.31- 1262039 [email protected] #1 SMP PREEMPT Thu Jun 13 20:16:26 KST 2013. I want to get back to stock kernel, so that I can upgrade to stock rom 4.2.2
Has anyone managed to get Viper4Android working with CM14.1?
I installed it according to the directions here: h t t p s : // w w w . y o u t u b e .com/watch?v=5CxotYNQEn0[
1. Flash V4A 2.5.0.5.zip
2. Go to root/vendor/etc and rename audio_effects.conf to audio_effects.conf.bak
3. Reboot
Unfortunately I am getting Status: Abonormal for the driver.
Has anyone had success getting Viper working on CM 14.1?
ysaliens said:
Has anyone managed to get Viper4Android working with CM14.1?
I installed it according to the directions here: h t t p s : // w w w . y o u t u b e .com/watch?v=5CxotYNQEn0[
1. Flash V4A 2.5.0.5.zip
2. Go to root/vendor/etc and rename audio_effects.conf to audio_effects.conf.bak
3. Reboot
Unfortunately I am getting Status: Abonormal for the driver.
Has anyone had success getting Viper working on CM 14.1?
Click to expand...
Click to collapse
Dude, why are you not using Arise / Deuteronomy? It's like 5 times better than vanilla Viper. Think of it as viper on steroids. It's even a flashable zip, you don't have to worry about editing build.prop files and all that BS. On top of that it even has Dolby Atmos:
http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Installed Arise / Deuteronomy by simply flashing it and I'm having the same problem. Driver status is abnormal.
This is after Factory Reset-->Flash latest CM14.1 nightly-->Boot-->Flash Arise/Deuteronomy-->Boot-->open Arise app and check driver status.
What am I doing wrong?
FIGURED IT OUT: Kernel needs to be set to Permissive for it to work properly. You can use SELinuxModeChanger to change it.
ysaliens said:
FIGURED IT OUT: Kernel needs to be set to Permissive for it to work properly. You can use SELinuxModeChanger to change it.
Click to expand...
Click to collapse
Hey, I'm a little noobish at this. Where exactly is the zip in that gigantic thread for Deuteronomy?
Finally works great on the latest Cyanogenmod 14.1 nightly.
Get the .zip from here: https://www.androidfilehost.com/?w=files&flid=126523
Make sure you're in permissive mode for the Linux kernel.
Also make sure to run it in "Compatibility Mode" if using Spotify or it won't work.
Link to app. - https://dbp.noobdev.io/downloads/
https://dbp.noobdev.io/files/9.2.0....atcherAndroid-9.2.0.r25.g0638efb-snapshot.apk
Official website. dpb.noobdev.io
Offcial thread -
https://forum.xda-developers.com/showthread.php?t=2447534
All the steps on how to use are on the official thread
Please note it is not created nor tested by me
All the credits goes to official developer chenxiaolong
And @ndrancs who commited changes for Z00T
Z00L support will come i am committing changes for that
Thanks to rom developers also
Great news again for Z00T user!!
But, unfortunately i can't use it at all -_-
First, i attemp to backup the current rom, but error coz the app can't locate my boot.img (because magisk, maybe? It's patching the boot.img btw.)
Second, i attemp to flash the stock one, but still error (old marshmallow they said)
And lastly, i tried to flash the new Oct-OS N, but error bcoz the updater script contain the script to read asus trust zone, but they can't read it.
XTprion said:
Great news again for Z00T user!!
But, unfortunately i can't use it at all -_-
First, i attemp to backup the current rom, but error coz the app can't locate my boot.img (because magisk, maybe? It's patching the boot.img btw.)
Second, i attemp to flash the stock one, but still error (old marshmallow they said)
And lastly, i tried to flash the new Oct-OS N, but error bcoz the updater script contain the script to read asus trust zone, but they can't read it.
Click to expand...
Click to collapse
I cant test this coz i have Z00L
Once support for that phone comes i will test and tell how to get it work
Coz both are same Z00T and Z00L
Have same partitions
XTprion said:
Great news again for Z00T user!!
But, unfortunately i can't use it at all -_-
First, i attemp to backup the current rom, but error coz the app can't locate my boot.img (because magisk, maybe? It's patching the boot.img btw.)
Second, i attemp to flash the stock one, but still error (old marshmallow they said)
And lastly, i tried to flash the new Oct-OS N, but error bcoz the updater script contain the script to read asus trust zone, but they can't read it.
Click to expand...
Click to collapse
I suggest u to use this app for only custom roms
Coz stock roms have errors in many devices
addy692 said:
I suggest u to use this app for only custom roms
Coz stock roms have errors in many devices
Click to expand...
Click to collapse
Thanks for the suggestion, but I've already test it and error trustzone (can't read the trustzone)
New: I replace the updater script, deleting the line to bypass checking, but it's stuck in the "Patching system unconditionally" without any move -_-.
XTprion said:
Thanks for the suggestion, but I've already test it and error trustzone (can't read the trustzone)
New: I replace the updater script, deleting the line to bypass checking, but it's stuck in the "Patching system unconditionally" without any move -_-.
Click to expand...
Click to collapse
Yeah may be there's something wrong with partition details provided in tha app
Once support for Z00L comes i will solve it
Still, my problem isn't solved. I think you should to see this:
1. Asus Z00T variant, including Z00U, Z00UD, Z00UDH, Z00U_1 and Z00UD_1 is similar in every specs, so i think you should make Z00T variant is rrecognized the other codename too... (Z00U, etc)
2. When trying to install opengapps, it's aborted bcoz they detect my primary rom os (primary: stock 6.0), instead of secondary 7.1.1, but if it doesn't happend, the secondary rom can't boot bcoz the 1st problem..
XTprion said:
Still, my problem isn't solved. I think you should to see this:
1. Asus Z00T variant, including Z00U, Z00UD, Z00UDH, Z00U_1 and Z00UD_1 is similar in every specs, so i think you should make Z00T variant is rrecognized the other codename too... (Z00U, etc)
2. When trying to install opengapps, it's aborted bcoz they detect my primary rom os (primary: stock 6.0), instead of secondary 7.1.1, but if it doesn't happend, the secondary rom can't boot bcoz the 1st problem..
Click to expand...
Click to collapse
Ok i will add all these codenames in the next update
addy692 said:
Ok i will add all these codenames in the next update
Click to expand...
Click to collapse
Thaaankkss...
BTW, all codenames from Z00T family:
Z00T / Z00TD, Z00U / Z00UD / Z00UDH / Z00UDB, Z011 / Z011D / Z011DD
Source: LuK1337 LineageOS Thread...
XTprion said:
Thaaankkss...
BTW, all codenames from Z00T family:
Z00T / Z00TD, Z00U / Z00UD / Z00UDH / Z00UDB, Z011 / Z011D / Z011DD
Source: LuK1337 LineageOS Thread...
Click to expand...
Click to collapse
Added will be there in next update
XTprion said:
Thaaankkss...
BTW, all codenames from Z00T family:
Z00T / Z00TD, Z00U / Z00UD / Z00UDH / Z00UDB, Z011 / Z011D / Z011DD
Source: LuK1337 LineageOS Thread...
Click to expand...
Click to collapse
all codemanes added
Just download new update
addy692 said:
all codemanes added
Just download new update
Click to expand...
Click to collapse
Yess the update.... Thanks man...
Edit: it's still not work, unfortunately.
I think you forget to add Asus_ to device codename (my device is Asus_Z00U, and the apps can't recognize it bcoz you add Z00U device codename only -_-)
Sometimes i think vendor like asus make everything complicated with their awkward codename, even if the device can share the same software -_-.
XTprion said:
Yess the update.... Thanks man...
Edit: it's still not work, unfortunately.
I think you forget to add Asus_ to device codename (my device is Asus_Z00U, and the apps can't recognize it bcoz you add Z00U device codename only -_-)
Sometimes i think vendor like asus make everything complicated with their awkward codename, even if the device can share the same software -_-.
Click to expand...
Click to collapse
Oh .....
Yeah that asus missed
Now have to wait for another update
I will update all codenames with asus added
XTprion said:
Yess the update.... Thanks man...
Edit: it's still not work, unfortunately.
I think you forget to add Asus_ to device codename (my device is Asus_Z00U, and the apps can't recognize it bcoz you add Z00U device codename only -_-)
Sometimes i think vendor like asus make everything complicated with their awkward codename, even if the device can share the same software -_-.
Click to expand...
Click to collapse
U can change ur codename in build.prop also
addy692 said:
U can change ur codename in build.prop also
Click to expand...
Click to collapse
I do it before you say it man...
But the probem is, my build.prop list my device as Z00T
XTprion said:
I do it before you say it man...
But the probem is, my build.prop list my device as Z00T
Click to expand...
Click to collapse
can u attach a ss
addy692 said:
can u attach a ss
Click to expand...
Click to collapse
Ok...
XTprion said:
Ok...
Click to expand...
Click to collapse
try using any other rom or stock rom
Also
I will add al codenames with asus_ added
addy692 said:
try using any other rom or stock rom
Also
I will add al codenames with asus_ added
Click to expand...
Click to collapse
Its same guys, i dont know where i should change
(In my old Zenfone 5, there's a different build.prop that contain T00F model or T00J. Rename it will make my phone model changed, but in this phone (even on the stock), it's useless -_-)
Plus: i think you should use Asus_ instead of asus_ to avoid useless things again wkwk)
XTprion said:
Its same guys, i dont know where i should change
(In my old Zenfone 5, there's a different build.prop that contain T00F model or T00J. Rename it will make my phone model changed, but in this phone (even on the stock), it's useless -_-)
Plus: i think you should use Asus_ instead of asus_ to avoid useless things again wkwk)
Click to expand...
Click to collapse
yeah Asus_ i will add
And just for testing can u upload ur build.prop to gdrive and give link
Havoc 3.0 Q gsi fixed build for Huawei P10 Lite
About
Originally Havoc 3.0 Q gsi based on v204 compiled by ExpressLuke , but for Hi6250 some bugs persist , so I managed to fix them and repacked the IMG then highly compressed.
Fixed
* Camera * media ( sound , video , YouTube ..) * NFC * battery usage * auto brightness * phone Info's ( build number , model , manufacturer , device name .. ) * added Havoc bootanimation .
Bugs
* Offline charging ( requires permissive kernel , Labyrinth kernel 2.0 by Dil3mm4 tested * Blurry can be fixed in phh treble settings > Huawei features > 3rd option ( disabling hwcomposer ).
Installation
* Extract img from xz archive * go to TWRP and do a full wipe (system, data, cache, dalvik/art cache) * flash the image in system image partition * flash root (optional) NOTE1: If you are coming from Android 9 flashing root is a MUST DO ! NOTE2: Flash only the Magisk zip linked in this post ! * reboot to System * reboot to TWRP * flash gapps (optional) * Enjoy !!!
Download
https://mega.nz/#!2S4xxQ6C!f0KJlCA_9_yyJzWZAtlNYVJHktSuyyFY7p82kXK4caM
Twrp recommended ( by @Pretoriano80 ):
https://mega.nz/#!LLhBXSzY!3runNNoW9z1tOHSu-heIUhyy-4u8XHvc8rZMsn547so
Magisk.phh:
https://mega.nz/#!uX4k1KjS!2gnUV3IyLt8XXf4NO3RyZEJnt5YNJQ8tY9i11oGfKYM
Credits: @phhusson ExpressLuke @haky 86 @DarkJoker360 @Dil3mm4
Regards!
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8.x,bootloader unlocked and TWRP
Based On: AOSP
Version Information
Status: Stable
Created 2019-12-01
6 hrs SoT
Hami_Do said:
6 hrs SoT
Click to expand...
Click to collapse
Wow that's really impressive for a 3000 mAh device! Many people aren't getting that on the Note 10 Plus!
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
No, it's simply Havoc GSI with several fixes included especially for our device/platform and no, gapps are not included (you would have known if you read the first post more carefully )
TureX said:
Hi! Thats nice, so basically Is a Kirin gsi? Are gapps included?
Click to expand...
Click to collapse
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Hami_Do said:
For gapps , pico worked for me as it should , from here :
https://sourceforge.net/projects/opengapps/files/arm64/beta/20191114/
Click to expand...
Click to collapse
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english
TureX said:
Hi! I Guess for Who hasn't a working twrp Is not possible to flash gapps. Thanks for your work and sorry for my english
Click to expand...
Click to collapse
the suggested twrp in first post works perfectly on most hi6250 ( emui 8 ) , plus it has an option ( exclude OEM path from data wipe ) from there you don't need to format data & internal storage to boot any gsi/dssi AFAIK.
Only sometimes installing gapps requires resize system from advanced wipe menu.
thanks.. any build for havoc 2.9 ?
How can I remove the bottom pad that appears when I want to use the keyboard?
itsm03 said:
thanks.. any build for havoc 2.9 ?
Click to expand...
Click to collapse
the best 2.9 build here:
https://sourceforge.net/projects/ha...90912-phhgsi_arm64_a-Official.img.xz/download
1- wipe system data cache
2-flash havoc 2.9 and boot up to system
3- reboot to twrp and :
4- flash offline charger fix for pie
5- flash nfc patch for pie
6- flash hwcomposer ( follow instructions )
7- flash gapps and magisk ( optional )
Enjoy.
All flashable patches you find them here:
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745
ghassan haddad said:
How can I remove the bottom pad that appears when I want to use the keyboard?
Click to expand...
Click to collapse
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.
Hami_Do said:
Join https://t.me/hi6250group telegram group , there you can share your screenshots to understand the issue.
Click to expand...
Click to collapse
I Couldn't post pictures since new members need to wait, add to that I got only one answer telling me that it may not be possible.
I was referring to this pad in the picture
Now Gsi's based on v207 and later are stable , here you find latest Havoc Q gsi :
https://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/ARM64/A/
Probably only NFC patch is needed :
https://forum.xda-developers.com/p10-lite/how-to/gsis-manual-fixes-hi6250-devices-t3936745/page3
=========
No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti
Achieve is currupt :-/
i get Error while flashing image, here is the log
Erro 255
I get error while flashing image here is the log
I have the saame problem on WAS-LX1
anvetoti said:
No way to boot on my phone (WAS-LX1A)...stuck on boot, after some minutes its reboot, other minutes and then goes in erecovery.
I tried also a totally clean install starting with last firmware stock (WAS-LX1AC432B390) install (dload method) and then flashing Havoc 3.0 (based on v207) system file from fastboot.
Nothing to do and I came back beaten to Android 8.0
.....any help pls?
or maybe it is easier to buy a P30 lite
Tx
Toti
Click to expand...
Click to collapse
Any help?
Help this guy and me, please!
From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.
NeoPreacher said:
From my experience with flashing this device it is most likely that either your device is still encrypted or there are magisk leftovers or data partition wasn't wiped correctly, that's causing rom not to boot. And always use pretoriano's twrp_0.5_test, works best. Sometimes it boots to erecovery, but you can try to reboot and it might work then.
Click to expand...
Click to collapse
I think you're right, I also think it's due to encryption or data partition (not magisk because I made a clean installation), because I had the same problem, stuck on boot, with all the Roms (PIE and Q) that require TWRP.
The only rom without problems was OpenKirin-OmniROM Pie Alpha 6.2 which does not require a custom recovery for installation !!
Do you have any operational suggestions to give me or I just have to try with pretoriano's twrp_0.5_test ??
What do you think if :
- In a stock recovery I do a factory reset
- From fastboot I do fastboot erase system, userdata and cache (or better to use format command for userdata?)
- the I flash system.img
- then I flash TWRP
- and then install magisk and gapps from TWRP?
TX
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:
#
Code:
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.....
Thanks for your effort. I am giving the rom & other links here to make things easier for others. If you find any wrong link, please message me. And I can help you by testing things in my XT1944-6.
------------------------------------------------------------------------------------------------
Custom rom links for NORA according to the fixed kernel numbers by @Stranger Absolute -
ROM credits to the respective developers
1/AICP link
2/Aosp Extended link
3/Arrow OS link
4/CrDroid link
5/Derpfest link
6/ion OS link
7/Lineage OS link
8/Nusantara link
9/Pixel Experience link
10/Pixel Experience Plus link
11/Pixel Plus Ui link
12/Resurrection Remix link
13/MSM Xtended link
14/Havoc OS link
Twrp - link
7/Lineageos rom is also attached (Because of dead link in the thread).
Rescue & Smart Assistant Tool for emergency situation and rolling back to stock condition link
Stranger Absolute said:
Hi guys, I'm making this topic to solve a little problem that was happening with Moto E5 nora.
Before I start talking about this problem, I will make it very clear in this thread that I am talking about. And until the end of the last line in this post.
-----------------------------------------------------------------------------------------
##IMPORTANT DESCRIPTION##
MAKING IT CLEAR to the moderators of the site and to the developers of the ROMs I will quote 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 sensitive screen problem, and that when you downloaded the ROMs it wouldn't start. 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 with video recording or internet network problems.
This kernel Image that I compiled. I did not use the same boot kernel Image from such ROM to get in another. You have to subscribe to the boot kernels of the ROMs to be able to boot, this is for the people who patch the kernels. I recommend that you do this, otherwise you will boot infinitely.
Repeat this again for any ROMs that are mentioned here. I will not and will not and am not taking these ROMs as my own. I am just solving this problem that was happening to me.
I'm 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 not 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 under test by me. Because I edited its config when compiling. I am checking to see if there are any compilation errors or other problems that can happen in the future. Because of the edit that I added to it's config.
The kernel source doesn't have any problems. Not that I know of.
So I will always update boot.img when possible
I recommend to backup your sensors. because there are some active sensors in the kernel, and I don't know if it can hurt it or make it dead.
THIS KERNEL WAS TESTED ON THE MOTO E5 NORA XT1944-4
THIS KERNEL WILL ONLY WORK ON THE NORA
note: i only tested on the xt1944-4, it may work... or not. It depends on the variant
VARIANTS XT1944 -2,-3,-4, -6? I DON'T KNOW VERY WELL.
#######NOTICE#########
DON'T DO THIS IF YOU DON'T KNOW HOW TO GET OUT OF A BROKEN KERNEL
HAVE A BACKUP OF THE BOOT IMG OF THE KERNEL THAT IS WORKING PERFECTLY
SO YOU CAN GET OUT OF THE BROKEN KERNEL
AND THEN JUST PUT IT BACK IN AND EVERYTHING WILL BE FINE.
########+++++########
How to flash this kernel
Simple, you can flash it through custom recovery or TWRP or fastboot.
fastboot command:
#
fastboot flash boot boot.img
#
What is this kernel for?
It serves to fix the problem of the touch screen
Low memory kill improved (I increased its value) (If you have the 1gb of RAM that I had and you don't leave for nothing, I recommend switching vendors)
No but interactive (No need for this KERNEL.)(Also.. it is not stock. And yes customized.)
And the prolonged recording problem or as we know ldk(Got corrected)
And others..
No recovery: (TWRP)
Go to install in recovery
Look for the folder where you left the boot, either on the memory card or on the pendrive.
And of course, choose the install image option so that the image you downloaded appears.
And where is this install image? Right when you select install on the home screen when you sign in. Right below it will be on the side select storage. Just change to install image.
Boot img kernel;
aicp_nora =1
AospExtended-v7.3-nora =2
Arrow-v10.0-nora =3
crDroidAndroid-10.0-2 =4
DerpFest-10-Bare =5
ion-2.9.a-EOL-nora =6
lineageos_17.1 =7
Nusantara_LTS-10-nora =8
PixelExperience_nora =9
PixelExperience_Plus_nora =10
PixelPlusUI_2.0_nora =11
RROS-Q-8.7.3-20210920-nora =12
Xtended-Tribute-To-MartinCoulon-nora =13
in case no one understands the name corresponding to the ROM that will be downloaded from NORA's XDA. And that is not crashing with kernel boot.
Just look at the ROM name when you download it. When it already has it in .zip and that way you can find its corresponding boot.
Why so much boot img?
Unfortunately a single boot.img will not work on another ROM. After the system does not accept the boot of another system build. Only his. Removing GSI.
--------------------------------------------------------------------------------------
When downloading, rename it to boot.img
The numbers next to the ROM name correspond to the boot patch.
THESE ROMS ARE ALL FROM XDA THAT ARE HERE FROM NORA
Sources: https://github.com/E5Series/kernel_motorola_msm8953-3.18
Compile: aarch64-linux-android-4.9-lineage-19.1
Compile 32bits: arm-linux-androideabi-4.9-lineage-19.0
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
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.
Click to expand...
Click to collapse
Everything works fine except the inbuilt screen recorder.. Is it possible to fix that through kernel? Thanks again. Really appreciate your work. I can now install any rom without touch,sd card & video issues. I also had abnormal graphics and freezing problem in 3D games. Finally it is fixed
Tawsif999 said:
Everything works fine except the inbuilt screen recorder.. Is it possible to fix that through kernel? Thanks again. Really appreciate your work. I can now install any rom without touch,sd card & video issues. I also had abnormal graphics and freezing problem in 3D games. Finally it is fixed
Click to expand...
Click to collapse
Yes, it's possible. but, only if some line is missing in the config fo kernel. but this boot was to fix that, but I already knew that it couldn't solve it in some variants. oh.. and another thing. it might be because of the rom sometimes. if it's for the rom, there's not much to do. only the development of the ROM itself will be able to correct this error.
I noticed this error in a gsi (generic system). and of course, it's gsi. I already expected this to happen. but I expected it soon when I put the root in it but .. amazingly it only stays for a long period of time, and I thought it would work soon when I put the root. as it happened with the other kernel other than the one in the topic.
but it's like I told you, that in most cases it can be in the rom. already in 3d like games or edition.. they improved I would say. the intention was just to adjust the touch and that's it. only after I modified it. he got faster! with more performance. that wasn't the intention but that's what ended up happening. that's why it got better.
Tawsif999 said:
Everything works fine except the inbuilt screen recorder.. Is it possible to fix that through kernel? Thanks again. Really appreciate your work. I can now install any rom without touch,sd card & video issues. I also had abnormal graphics and freezing problem in 3D games. Finally it is fixed
Click to expand...
Click to collapse
but I'll check to see which one is missing in the kernel config to solve the problem
Tawsif999 said:
Thanks for your effort. I am giving the rom & other links here to make things easier for others. If you find any wrong link, please message me. And I can help you by testing things in my XT1944-6.
------------------------------------------------------------------------------------------------
Custom rom links for NORA according to the fixed kernel numbers by @Stranger Absolute -
ROM credits to the respective developers
1/AICP link
2/Aosp Extended link
3/Arrow OS link
4/CrDroid link
5/Derpfest link
6/ion OS link
7/Lineage OS link
8/Nusantara link
9/Pixel Experience link
10/Pixel Experience Plus link
11/Pixel Plus Ui link
12/Resurrection Remix link
13/MSM Xtended link
TWRP 64 bit is attached. If touch screen doesn't work in TWRP, use mouse via OTG. And if you have decryption problem in TWRP, use SD card & put files there.
7/Lineageos rom is also attached (Because of dead link in the thread).
Rescue & Smart Assistant Tool for emergency situation and rolling back to stock condition link
Click to expand...
Click to collapse
Hello how are you doing? I am a fan of custom roms, I have been trying to install lineage os on my moto e5 variant 3 for months, without success in getting the file, thank you and the creator of the post, what I have noticed is that the loading times in games are a bit slow, any way to fix it? It should be noted that I installed the root and dolby atmos, working correctly, greetings from Argentina
7 de argentina said:
Hello how are you doing? I am a fan of custom roms, I have been trying to install lineage os on my moto e5 variant 3 for months, without success in getting the file, thank you and the creator of the post, what I have noticed is that the loading times in games are a bit slow, any way to fix it? It should be noted that I installed the root and dolby atmos, working correctly, greetings from Argentina
Click to expand...
Click to collapse
I use hktweaks(updated version of kernel auditor) & I increase cpu,gpu speed to the maximum. Also select apply on boot.
Idk if this method really works or not. But I do it everytime. Anyways, if anyone wants an amazing gaming boot logo & boot animation, I can provide it.
Stranger Absolute said:
Hi guys, I'm making this topic to solve a little problem that was happening with Moto E5 nora.
Before I start talking about this problem, I will make it very clear in this thread that I am talking about. And until the end of the last line in this post.
-----------------------------------------------------------------------------------------
##IMPORTANT DESCRIPTION##
MAKING IT CLEAR to the moderators of the site and to the developers of the ROMs I will quote 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 sensitive screen problem, and that when you downloaded the ROMs it wouldn't start. 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 with video recording or internet network problems.
This kernel Image that I compiled. I did not use the same boot kernel Image from such ROM to get in another. You have to subscribe to the boot kernels of the ROMs to be able to boot, this is for the people who patch the kernels. I recommend that you do this, otherwise you will boot infinitely.
Repeat this again for any ROMs that are mentioned here. I will not and will not and am not taking these ROMs as my own. I am just solving this problem that was happening to me.
I'm 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 not 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 under test by me. Because I edited its config when compiling. I am checking to see if there are any compilation errors or other problems that can happen in the future. Because of the edit that I added to it's config.
The kernel source doesn't have any problems. Not that I know of.
So I will always update boot.img when possible
I recommend to backup your sensors. because there are some active sensors in the kernel, and I don't know if it can hurt it or make it dead.
THIS KERNEL WAS TESTED ON THE MOTO E5 NORA XT1944-4
THIS KERNEL WILL ONLY WORK ON THE NORA
note: i only tested on the xt1944-4, it may work... or not. It depends on the variant
VARIANTS XT1944 -2,-3,-4, -6? I DON'T KNOW VERY WELL.
#######NOTICE#########
DON'T DO THIS IF YOU DON'T KNOW HOW TO GET OUT OF A BROKEN KERNEL
HAVE A BACKUP OF THE BOOT IMG OF THE KERNEL THAT IS WORKING PERFECTLY
SO YOU CAN GET OUT OF THE BROKEN KERNEL
AND THEN JUST PUT IT BACK IN AND EVERYTHING WILL BE FINE.
########+++++########
How to flash this kernel
Simple, you can flash it through custom recovery or TWRP or fastboot.
fastboot command:
#
fastboot flash boot boot.img
#
What is this kernel for?
It serves to fix the problem of the touch screen
Low memory kill improved (I increased its value) (If you have the 1gb of RAM that I had and you don't leave for nothing, I recommend switching vendors)
The CPU governor is not interactive anymore (No need for this KERNEL.)(Also.. it is not stock. And yes customized.)
And the prolonged recording problem or as we know ldk(Got corrected)
And others..
No recovery: (TWRP)
Go to install in recovery
Procure a pasta onde deixou o boot, seja no cartão de memória ou no pendrive.
E claro, escolha a opção de imagem de instalação para que apareça a imagem que você baixou.
E onde está essa imagem de instalação? Logo quando você seleciona instalar na tela inicial ao fazer login. Logo abaixo, estará no lado, selecione armazenamento. Basta alterar para instalar a imagem .
Kernel img de inicialização;
aicp_nora =1
AospExtended-v7.3-nora =2
Arrow-v10.0-nora =3
crDroidAndroid-10.0-2 =4
DerpFest-10-Bare =5
ion-2.9.a-EOL-nora =6
lineageos_17.1 =7
Nusantara_LTS-10-nora =8
PixelExperience_nora =9
PixelExperience_Plus_nora =10
PixelPlusUI_2.0_nora =11
Ressurreição Remix-Q-8.7.3-nora =12
Xtended-Tribute-To-MartinCoulon-nora =13
Havoc-OS-v3.12-nora =14
caso ninguém entenda o nome correspondente à ROM que será baixada do XDA da NORA. E isso não está travando com a inicialização do kernel.
Basta olhar para o nome da ROM quando você baixá-lo. Quando já tiver em .zip e assim você achar o boot correspondente.
Por que tanto boot img?
Infelizmente, um único boot.img não funcionará em outra ROM. Depois que o sistema não aceitar a inicialização de outra compilação do sistema. Só dele. Removendo GSI.
-------------------------------------------------- ------------------------------------
Ao baixar, renomeie-o para boot.img
Os números ao lado do nome da ROM correspondem ao patch de inicialização.
ESSAS ROMS SÃO TODAS DO XDA QUE SÃO AQUI DA NORA
Fontes: https://github.com/E5Series/kernel_motorola_msm8953-3.18
Compilar: aarch64-linux-android-4.9-lineage-19.1
Compilar 32 bits: arm-linux-androideabi-4.9-lineage-19.0
Infelizmente o defconfig não está lá nos fontes, tive que removê-lo da ROM para poder compilar.
Só para alguém saber de onde tirei , caso queira compilar
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.
Click to expand...
Click to collapse
I added Havoc OS to the list. At the request of Tawsif999. I'm glad you reminded me because I had forgotten . I took a while because I was testing the ROM. But it's there.
7 de argentina said:
Hello how are you doing? I am a fan of custom roms, I have been trying to install lineage os on my moto e5 variant 3 for months, without success in getting the file, thank you and the creator of the post, what I have noticed is that the loading times in games are a bit slow, any way to fix it? It should be noted that I installed the root and dolby atmos, working correctly, greetings from Argentina
Click to expand...
Click to collapse
I'm fine n.n! Thanks for the appreciation . In fact this problem itself is not from the kernel many times and from the ROM which is not very well optimized. And it depends on which game you are going to run if it takes with internet or offline, or if it's too heavy too.But if it is in the rom or in the vendor. Just remembering that the vendor is part of all this and it also has something that makes the system faster. I was playing brawl stars and I noticed that it improved a little when it is played in the native quality of the mobile, of course, there are still a few glitches when playing. But I noticed that it got better. Now in low quality it runs even smooth . But it's playable!
In short, there's not much you can do about these details as games for the kernel. Since this kernel is a bit old. In fact, this kernel was not supposed to be used in Android 10 ROM, but the 4.9 that runs better. With my knowledge you can go to kernel 4.9. some people will say no... But it does. Unfortunately, there isn't much to do since the config doesn't have a command that exists for that.
Remembering that the updates I sitei on the post will happen.
There will be three updates for the Kernel
V2,V3,V4 These updates are from the config that I edited.. so there will be. Post well will only arrive these updates in 3 months. Why that?? I need time to check if there are any errors or problems with such a config.
I say stay tuned for the next few months.
Bugs found (Kernel or rom issue)
I'm using lineage os and found a bug. After installing some particular(Not all) apps from playstore, they just crash while opening. For example, This app. I can't remember the other apps that crashed earlier. But why does they get installed if they are not compatible.
Tawsif999 said:
Bugs found (Kernel or rom issue)
I'm using lineage os and found a bug. After installing some particular(Not all) apps from playstore, they just crash while opening. For example, This app. I can't remember the other apps that crashed earlier. But why does they get installed if they are not compatible.
Click to expand...
Click to collapse
actually this bug is not because of the kernel, it's from the rom. The kernel doesn't interfere with these things. It's rare that this happens with the kernel. unfortunately i can't resolve this bug. Only the ROM developer himself can verify the problem that is causing it. I don't recommend you use Lineage os. There are some bugs in this rom that are not very user friendly.
Stranger Absolute said:
Hi guys, I'm making this topic to solve a little problem that was happening with Moto E5 nora.
Before I start talking about this problem, I will make it very clear in this thread that I am talking about. And until the end of the last line in this post.
-----------------------------------------------------------------------------------------
##IMPORTANT DESCRIPTION##
MAKING IT CLEAR to the moderators of the site and to the developers of the ROMs I will quote 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 sensitive screen problem, and that when you downloaded the ROMs it wouldn't start. 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 with video recording or internet network problems.
This kernel Image that I compiled, this boot config (touch fix) from the rom (Lineage os 17.1) was not used for my boot. You have to subscribe to the boot kernels of the ROMs to be able to boot, this is for the people who patch the kernels. I recommend that you do this, otherwise you will boot infinitely.
Repeat this again for any ROMs that are mentioned here. I will not and will not and am not taking these ROMs as my own. I am just solving this problem that was happening to me.
I'm 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 not 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 under test by me. Because I edited its config when compiling. I am checking to see if there are any compilation errors or other problems that can happen in the future. Because of the edit that I added to it's config.
The kernel source doesn't have any problems. Not that I know of.
So I will always update boot.img when possible
I recommend to backup your sensors. because there are some active sensors in the kernel, and I don't know if it can hurt it or make it dead.
THIS KERNEL WAS TESTED ON THE MOTO E5 NORA XT1944-4
note: i only tested on the xt1944-4, it may work... or not. It depends on the variant
VARIANTS XT1944 -1,-2,-3,-5,-4 -6.
#######NOTICE#########
DON'T DO THIS IF YOU DON'T KNOW HOW TO GET OUT OF A BROKEN KERNEL
HAVE A BACKUP OF THE BOOT IMG OF THE KERNEL THAT IS WORKING PERFECTLY
SO YOU CAN GET OUT OF THE BROKEN KERNEL
AND THEN JUST PUT IT BACK IN AND EVERYTHING WILL BE FINE.
########+++++########
How to flash this kernel
Simple, you can flash it through custom recovery or TWRP or fastboot.
fastboot command:
#
fastboot flash boot boot.img
#
What is this kernel for?
It serves to fix the problem of the touch screen
Low memory kill improved (I increased its value) (If you have the 1gb of RAM that I had and you don't leave for nothing, I recommend switching vendors)
The CPU governor is not interactive anymore (No need for this KERNEL.)(Also.. it is not stock. And yes customized.)
And the prolonged recording problem or as we know ldk(Got corrected)
Touchscreen issue has been resolved.
And others..
No recovery: (TWRP)
Go to install in recovery
Look for the folder where you left the boot, either on the memory card or on the pendrive.
And of course, choose the install image option so that the image you downloaded appears.
And where is this install image? Right when you select install on the home screen when you sign in. Right below it will be on the side select storage. Just change to install image.
Boot img kernel download
aicp_nora =1
AospExtended-v7.3-nora =2
Arrow-v10.0-nora =3
crDroidAndroid-10.0-2 =4
DerpFest-10-Bare =5
ion-2.9.a-EOL-nora =6
lineageos_17.1 =7
Nusantara_LTS-10-nora =8
PixelExperience_nora =9
PixelExperience_Plus_nora =10
PixelPlusUI_2.0_nora =11
Resurrection Remix-Q-8.7.3-nora =12
Xtended-Tribute-To-MartinCoulon-nora =13
Havoc-OS-v3.12-nora =14
in case no one understands the name corresponding to the ROM that will be downloaded from NORA's XDA. And that is not crashing with kernel boot.
Just look at the ROM name when you download it. When it already has it in .zip and that way you can find its corresponding boot.
Why so much boot img?
Unfortunately a single boot.img will not work on another ROM. After the system does not accept the boot of another system build. Only his. Removing GSI.
--------------------------------------------------------------------------------------
When downloading, rename it to boot.img
The numbers next to the ROM name correspond to the boot patch.
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's nothing you 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.
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 soon....
Click to expand...
Click to collapse
I'm running DerpFest-10-Bare-Beta-nora-20211212, and this kernel just solved the issue when dowloading stuff to my sdcard, the phone would reboot every time i tried to download something, so thank you very much!
Is it possible to root img file via Magisk?
Is it possible to root the img file via Magisk?
Issue-
If you use any custom rom in moto e5, it will make the games think that you're using a device better than moto e5. That's why the texture will be better. For this, the game will run laggy. But there is a fix. Use gl tools and configure your game. Use a template of 1gb ram device.
Next, the graphics glitch persists. In free fire, the shrink zone looks odd. When I'm close to the circle, I can't even understand if I'm inside safezone or not. But the op's kernel (plus-linux) works better than twerk-x, which is given inside every rom for nora. In twerk-x, the game was crashing for graphics glitch. Anyways, plus-linux can handle it better.
Let's see if it gets fixed in next kernel updates. Most probably, it's problem of custom roms.
As the op mentioned, I tried havoc os & surprisingly it is more stable than pixel experience.
masoko said:
Is it possible to root the img file via Magisk?
Click to expand...
Click to collapse
Hi, sorry... just saw your answer now. It is possible yes, I recommend that you do after the ROM flash. I say this because there are some ROMs that give infinite boot. But, don't worry, they are only two. It only happens when you flash the ROM together with the magisk zip. It rarely happens, but ... It happens.
Thanks for your reply, what are the instructions for installing your kernel on swap?
masoko said:
Thanks for your reply, what are the instructions for installing your kernel on swap?
Click to expand...
Click to collapse
I hadn't stopped to think about it , you can use a module for magisk that will solve the swap problem.
You can use the one I will leave here.
This module was downloaded from pling. From the pling site. And I know there are several of them. But they don't replace the swap and also this swap that comes in the roms you can't delete it either by terminal or file. I don't recommend anyone to use this swap that comes in the ROMs. Technically I don't know what they are good for.
This module provides 2 GB of swap which is already enough for the moto e5.
masoko said:
I'm running DerpFest-10-Bare-Beta-nora-20211212, and this kernel just solved the issue when dowloading stuff to my sdcard, the phone would reboot every time i tried to download something, so thank you very much!
Click to expand...
Click to collapse
Was microsd using exfat or fat32?