[ROM][Q][3.12][UNOFFICIAL][nora] HavocOS for Moto E5

[FPSensor]

HavocOS for moto e5 is here and this is what you need to know

notes
- If you have problems with the video recording with the camera use this camera https://footej.com/

Download

GKart_builds - Browse /nora/HavocOS at SourceForge.net

builds by GKart

sourceforge.net

credits
- thanks to HavocOS team for the sources of the ROM
- thanks to @whodat711 for the vendor and common sources

Sources
- ROM https://github.com/Havoc-OS
- Kernel https://github.com/motoe5/android_kernel_motorola_msm8937 (twerk-X)
- vendor https://gitlab.com/the-flash/proprietary_vendor_motorola

greetings and enjoy

 

[kenshinta]

Hi there.

Havocos is one of my most preferred roms because I like to use microg which need signature spoofing.

However I noticed that this build has baked gapps(or at least gservices) unlike previous versions I used.

Can you bake a real gapps free build?

This rom is doing great on my nora so far. Just too bad on the camera video issue.

 

[FPSensor]

Hi there.

Havocos is one of my most preferred roms because I like to use microg which need signature spoofing.

However I noticed that this build has baked gapps(or at least gservices) unlike previous versions I used.

Can you bake a real gapps free build?

This rom is doing great on my nora so far. Just too bad on the camera video issue.

agree
for the camera problem download the footej camera
and you can uninstall gservices with root or twrp since I did the build without gapps
you can appreciate it by looking at the size of a gapps rom and a without

 

[kenshinta]

Re

agree
for the camera problem download the footej camera
and you can uninstall gservices with root or twrp since I did the build without gapps
you can appreciate it by looking at the size of a gapps rom and a without

Re gapps
maybe it's more accurate to say "gsf + play store" was baked in.
Would a appreciate a version without any Google services - unless its included by default by havoc os now?

 

[paulinhonoia62]

HavocOS for moto e5 is here and this is what you need to know

notes
- If you have problems with the video recording with the camera use this camera https://footej.com/

Download

GKart_builds - Browse /nora/HavocOS at SourceForge.net

builds by GKart

sourceforge.net

credits
- thanks to HavocOS team for the sources of the ROM
- thanks to @whodat711 for the vendor and common sources

Sources
- ROM https://github.com/Havoc-OS
- Kernel https://github.com/motoe5/android_kernel_motorola_msm8937 (twerk-X)
- vendor https://gitlab.com/the-flash/proprietary_vendor_motorola

greetings and enjoy

nO

HavocOS for moto e5 is here and this is what you need to know

notes
- If you have problems with the video recording with the camera use this camera https://footej.com/

Download

GKart_builds - Browse /nora/HavocOS at SourceForge.net

builds by GKart

sourceforge.net

credits
- thanks to HavocOS team for the sources of the ROM
- thanks to @whodat711 for the vendor and common sources

Sources
- ROM https://github.com/Havoc-OS
- Kernel https://github.com/motoe5/android_kernel_motorola_msm8937 (twerk-X)
- vendor https://gitlab.com/the-flash/proprietary_vendor_motorola

greetings and enjoy

when I install any custom rom on my moto g5 nora the touch screen doesn't work do you know how to solve it?

 

[kenshinta]

There is a sdcard bug with this rom and 2 others built by @op.

looks like exfat support is buggy as in all the different times I used said ROMs there is a common symptom.

The same microsd formatted as exfat (both ondevice or via a PC) will corrupt after 2-3gb data is written on it. Doesn't matter if its multiple files or 1 big file.

Same issue was noticed with RR https://forum.xda-developers.com/t/rom-q-8-7-3-nora-resurrection-remix-for-moto-e5.4337565/ and msm xtended https://forum.xda-developers.com/t/rom-q-x-q-unofficial-nora-msmxtended-for-moto-e5.4365671/. (The corruption of the card is the reason I switched roms from havoc).

Fix for me was to use fat32 instead (even ext4) - corruption never happened way beyond the 3gb mark.

I assume because if the same kernel sources used on all your ROMs.