[ROM][UNOFFICIAL][12][Moto G6][ali]LineageOS 19.1 by FWieP - Moto G6 ROMs, Kernels, Recoveries, & Other Develop

[ROM][UNOFFICIAL][12][Moto G6][ali]LineageOS 19.1 by FWieP - Moto G6 ROMs, Kernels, Recoveries, & Other Develop

Hello all,
Thanks to the LineageOS-developers and @brunogroa, this is my build containing the June-2023 security patches.
I plan to keep this build updated with the monthly security patches, for as long as LineageOS supports Android 12. Only the last build will be available for download; I'll keep this post as up-to-date as possible.
Update: OTA
Since the 2022-10-20 build, there is an OTA updater included in this ROM. It asks my download server for an updated build - just like in the official LineageOS. Don't forget to set it to check every month. It will download and install automatically; make sure you have a compatible recovery installed (preferably TWRP, see Links below).
Download
zip: lineage-19.1-20230611-UNOFFICIAL-ali.zip (mirror)
zip.sha256sum: lineage-19.1-20230611-UNOFFICIAL-ali.zip.sha256sum (mirror)
zip.sha256sum.asc: lineage-19.1-20230611-UNOFFICIAL-ali.zip.sha256sum.asc (mirror)
(the GPG signature can be verified by downloading my personal GPG-key)
Included/additional features
FM radio
Moto fingerprint gestures
Signed with my personal Android key
(see LineageOS' documentation on signing and verifying)
Known bugs
2nd SIM-card is not detected after reboot; open and close 2nd SIM-slot while booted to remedy
mobile-data and wifi-data measurements are always set to 0 bytes
Links
TWRP 64bit custom recovery
MindTheGapps, build-them-yourself Google apps, or download my current 12.1 build (mirror) (MD5, mirror)
Telegram group for support by the community, download links and more
Sources
Recent changes: LineageOS 19.1
Kernel tree: see roomservice.xml below
Device tree: see roomservice.xml below
Vendor tree: see roomservice.xml below
roomservice.xml for building it yourself:
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Kernel -->
<project name="brunorolak/kernel_motorola_msm8953" path="kernel/motorola/msm8953" remote="github" revision="lineage-19.1" />
<!-- Device tree -->
<project name="fwiep/device_motorola_ali" path="device/motorola/ali" remote="github" revision="lineage-19.1" />
<project name="fwiep/device_motorola_msm8953-common" path="device/motorola/msm8953-common" remote="github" revision="lineage-19.1" />
<!-- Vendor tree -->
<project name="brunorolak/vendor_motorola_ali" path="vendor/motorola/ali" remote="github" revision="lineage-19.1" />
<project name="brunorolak/vendor_motorola_msm8953-common" path="vendor/motorola/msm8953-common" remote="github" revision="lineage-19.1" />
<!-- Override LineageOS's QCom audio/display/media with custom AEX audio HALs -->
<remove-project name="LineageOS/android_hardware_qcom_audio" />
<remove-project name="LineageOS/android_hardware_qcom_display" />
<remove-project name="LineageOS/android_hardware_qcom_media" />
<project path="hardware/qcom-caf/msm8996/audio" name="AospExtended/platform_hardware_qcom_audio" groups="qcom,legacy-qcom" revision="12.x-caf-msm8996" />
<project path="hardware/qcom-caf/msm8996/display" name="AospExtended/platform_hardware_qcom_display" groups="qcom,legacy-qcom" revision="12.x-caf-msm8996" />
<project path="hardware/qcom-caf/msm8996/media" name="AospExtended/platform_hardware_qcom_media" groups="qcom,legacy-qcom" revision="12.x-caf-msm8996" />
<!-- Override LineageOS's Updater package -->
<remove-project name="LineageOS/android_packages_apps_Updater" />
<project name="fwiep/android_packages_apps_Updater" path="packages/apps/Updater" revision="lineage-19.1" />
</manifest>
Kind regards, see you next month,
FWieP

Sorry for a noob question: Is this 64bit ROM?

tnttrx said:
Is this 64bit ROM?
Click to expand...
Click to collapse
Yes, as are just about any custom ROM for the G6. Only stock OS is 32bit.
That's why there is a link to a 64bit TWRP - the ROM can't be installed in a 32bit TWRP.
Kind regards,
FWieP

Is this ROM rooted? Can i use magisk?

hugo.mattar said:
Is this ROM rooted?
Click to expand...
Click to collapse
No, not as such. But adb shell gives you root access (#-prompt).
hugo.mattar said:
Can i use magisk?
Click to expand...
Click to collapse
Probably yes. Please try and report back.
Kind regards,
FWieP

e-Título - Apps on Google Play
Official application of Elections of Voter Registration
play.google.com
Im trying to use this APP, and i get a warning about rooted phone..

I asked about magisk to give a try on the root hide module..

hugo.mattar said:
Im trying to use this APP, and i get a warning about rooted phone.
Click to expand...
Click to collapse
That depends on the app developer. Apps can detect whether they're running on a stock ROM or a custom ROM. Some apps warn about "You are running a custom ROM, we don't support that...", others mistakenly say: "You are running a rooted ROM...". That doesn't mean that root-capability is actually there.
I'm sorry - I've never used Magisk before and don't know about these things.
Kind regards,
FWieP

OK, thnks man
fwiep said:
That depends on the app developer. Apps can detect whether they're running on a stock ROM or a custom ROM. Some apps warn about "You are running a custom ROM, we don't support that...", others mistakenly say: "You are running a rooted ROM...". That doesn't mean that root-capability is actually there.
I'm sorry - I've never used Magisk before and don't know about these things.
Kind regards,
FWieP
Click to expand...
Click to collapse
OK thanks man ✌ very stable ROM by the way

Can't wait to flash this! I'm on stock Android Pie, so I should just be good to wipe data twice in TWRP, flash rom, flash magisk, and boot, right? No encryption garbage?

Easy peasy, flashed with no problem using your links. I'm using this phone as a 24/7 Pokemon Go bot device can't wait to see stability. I'll provide logs of whatever I find
Edit: Can anyone provide a built version of GApps? Need play services and such. I'm far too lazy to figure out how to build it myself
Edit 2: Using FlameGapps for Android 12.0 (FlameGApps-12.0-basic-arm64-20220811.zip), I try to flash it in TWRP after I flash my ROM (clean flash of course), and I get "Wrong android version detected This package is for android: 12.0 only Your ROM is Android: 12"
Can anyone advise on that? I've pulled my recovery log if needed. Thank you

UnitedShoes said:
Can anyone provide a built version of GApps
Click to expand...
Click to collapse
I've added my own MindTheGapps build to the downloads, above:
current 12.1 build (MD5)
Kind regards,
FWieP

UnitedShoes said:
Using FlameGapps for Android 12.0, I try to flash it in TWRP after I flash my ROM (clean flash of course), and I get "Wrong android version detected This package is for android: 12.0 only Your ROM is Android: 12"
Click to expand...
Click to collapse
This is because of the 12.0 and 12.1 (also called 12L) difference. This ROM is 12.1 (LineageOS 19.1). Please find packages for 12.1 specifically. Confusing, I know
Kind regards,
FWieP

fwiep said:
This is because of the 12.0 and 12.1 (also called 12L) difference. This ROM is 12.1 (LineageOS 19.1). Please find packages for 12.1 specifically. Confusing, I know
Kind regards,
FWieP
Click to expand...
Click to collapse
Thank you for your help, I just recently heard about 12L, confusing.
I'm trying out your GApps you provided but I'm having issues with first time setup. I boot to TWRP, wipe the phone, type yes, reboot to recovery, flash your Lineage ROM, flash the Gapps, wipe cache, then boot to system. For some reason, when I try to do my first time setup, I get stuck on "Just a sec..." after entering the date/time. I select "Set up offline" as well. I've been waiting on this screen for 15 minutes and tried this process over again with no luck.
I also would like to point out, when I first boot to the OS, I get the blue Google welcome screen instead of the Lineage one. Once I tap start or whatever, it then takes me to the black themed Lineage setup, where I proceed to get stuck.
I initially began on a Pie stock ROM, XT1925-6 Retail, if that's worth pointing out. I'd also like to link this Reddit comment I found, but I can't follow his instructions as there's no Lineage recovery for G6 that I can find.
Any ideas? Thank you

UnitedShoes said:
I boot to TWRP, wipe the phone, type yes, reboot to recovery, flash your Lineage ROM, flash the Gapps, wipe cache, then boot to system. For some reason, when I try to do my first time setup, I get stuck on "Just a sec..." after entering the date/time. I select "Set up offline" as well. I've been waiting on this screen for 15 minutes and tried this process over again with no luck.
I also would like to point out, when I first boot to the OS, I get the blue Google welcome screen instead of the Lineage one. Once I tap start or whatever, it then takes me to the black themed Lineage setup, where I proceed to get stuck.
Click to expand...
Click to collapse
This sounds like two of the many issues I had in the past few years - all caused by an unclean factory wipe. The golden tip that solved it for me, was to perform the wipe in the following way:
boot to TWRP
goto Wipe -> Advanced wipe
check Data, System, Vendor and both Cache partitions
perform the wipe
Then flash the ROM and the GApps in one go, then reboot to system.
The GApps provide the initial Google setup screen, but at the end of that setup, some of the dark-themed LineageOS screens should follow.
Note: MindTheGapps doesn't provide (smaller, slimmer) variants like OpenGapps does; you always get the complete package of Google stuff.
Good luck!
FWieP

fwiep said:
This sounds like two of the many issues I had in the past few years - all caused by an unclean factory wipe. The golden tip that solved it for me, was to perform the wipe in the following way:
boot to TWRP
goto Wipe -> Advanced wipe
check Data, System, Vendor and both Cache partitions
perform the wipe
Then flash the ROM and the GApps in one go, then reboot to system.
The GApps provide the initial Google setup screen, but at the end of that setup, some of the dark-themed LineageOS screens should follow.
Note: MindTheGapps doesn't provide (smaller, slimmer) variants like OpenGapps does; you always get the complete package of Google stuff.
Good luck!
FWieP
Click to expand...
Click to collapse
I don't see vendor on my wipe screen. Only cache, dalvik, data, internal, system, micro sd card. I can hit the checkbox for Vendor in mount, but it doesn't make it appear in wipe. Could this cause an issue?
I've proceeded to wipe using your instructions (except for Vendor), then flashed your ROM and Gapps, and I notice when I flash your ROM it says patching vendor image unconditionally. Could be a dirty flash because I can't wipe it?
I boot to system and I still can't get past the Just a sec screen. Been waiting for 5 minutes and counting. I can provide logs if you care to dig into this, but it's my bedtime for now. Thank you!

UnitedShoes said:
I don't see vendor on my wipe screen. Only cache, dalvik, data, internal, system, micro sd card. I can hit the checkbox for Vendor in mount, but it doesn't make it appear in wipe. Could this cause an issue?
I've proceeded to wipe using your instructions (except for Vendor), then flashed your ROM and Gapps, and I notice when I flash your ROM it says patching vendor image unconditionally. Could be a dirty flash because I can't wipe it?
I boot to system and I still can't get past the Just a sec screen. Been waiting for 5 minutes and counting. I can provide logs if you care to dig into this, but it's my bedtime for now. Thank you!
Click to expand...
Click to collapse
cos you need my twrp in this post >> https://forum.xda-developers.com/t/twrp-unofficial-twrp-64-bit-3-6-2.4328145/

hugo.mattar said:
e-Título - Apps on Google Play
Official application of Elections of Voter Registration
play.google.com
Im trying to use this APP, and i get a warning about rooted phone..
Click to expand...
Click to collapse
lineage dont has safetynet bypass... so you need to use magisk and modules to pass safetynet, good luck

The apps on the stock Moto G6 started acting up so I decided now was a good time to either reset the thing or find a current unofficial Lineage for it.
And here I am, about a week after unlocking and flashing. The phone feels fresh again. I'm not seeing any big issues so far. Bluetooth connection to a VW Golf hands free works as it should (contrary to another Lineage-phone I have).
I once lost all ringtones and notification sound settings - guess that was when I started the encryption process, so probably my fault. Even the "app provided sounds" were set to default Lineage sounds.
One single time the G6 refused to boot and was stuck with a black screen. A 30sec hard reset solved this.
All in all: thumbs up!

Bom dia, tudo bem com vocês? Eu estou com um problema, eu instalei a sua ROM, porém fiz um backup dos arquivos pelo comando adb backup -apk -shared -all -f C:\backup20111230.ab e estou tentando restaurar na sua ROM, consegue me ajudar?

Related

[GUIDE][TREBLE][PIE][9.0] Axon 7 path to HavocOS 2.0 Pie GSI via EDL and TWRP

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YOUR WARRANTY WILL BE VOID
I AM NOT responsible for anything that may happen to your phone while attempting to follow this guide.
You are doing so at your own risk, and you take full responsibility for your decisions and actions.
You are not to blame me or XDA, or any of it's respected developers.
Anyways, now that that is out of the way. Those of us who have been in the Axon 7 forums know that information is quite scattered about. So it can be difficult for any newcomers to find everything they need before making any leaps or dives with their device. This guide’s purpose is to centralize the quickest and easiest steps to follow in order to get Treblized and to get on a stable Pie GSI build that can be used as a home base before experimenting further with other ROMs and/or GSIs.
Even if you are not satisfied with the Havoc Pie GSI, your device will still be in an optimal state to try the latest Oreo 8.1 ROMs, such as LOS 15.1 or DotOS 2.5, or to try any of the other Pie GSIs in the Treble forums.
Things you will sacrifice:
No VOLTE
No Encryption
No Dolby
No Daydream
No AK4490 DAC (will default to AK4491)
Camera Flash out of sync (Use OpenCamera for flash shots)
Not able to set password for Hotspot (Open connection only)
Again, if you don't find using a Pie GSI worth these sacrifices after trying it out, you can easily move to an Oreo ROM like LOS 15.1 or DotOS 2.5, which have more functioning features.
----------------------------------------
DOWNLOAD
----------------------------------------
(NOTE: The below setup will be fluid as discussion in this thread finds more stability with newer vendor builds and newer HavocOS 2.0 GSI builds)
After completion of this guide, your device will be setup with the following (might as well download everything):
Oki's TWRP 3.2.3.0 Lab's Mod v1.3
B20 Bootstack by DrakenFX - Modified by Verequies (Splash or NoSplash)
Oreo Modem (U, G, or Chinese)
DotOS 2.5 boot.img (This also contains the DotOS vendor, if you wish to use it)
LOS 15.1 vendor (20181110) build
HavocOS 2.0 Pie GSI (20181027) build - NOTE: Most GSIs are provided compressed. You must extract the .img file from the downloaded file.
Your preferred GApps ( https://opengapps.org/ ) (ARM64, 9.0, Micro or below only)
Also download OrdenKrieger's TWRP 3.2.3.0, going to need it handy to flash the vendor img.
And the NFC_Hotspot Fix by Kountry83 (You will need this for almost every GSI you try)
----------------------------------------
FAQ
----------------------------------------
WHATS UP WITH THE BOOTSTACKS?
The bootstacks that are currently available for the Axon are somewhat of a mess, if not careful, you can easily brick your device.
For Pie GSI setups, I recommend the B20 bootstack by DrakenFX that has been modified by Verequies, Splash version.
Verequies has asked that I also link the NoSplash version in case some users have issues with the Splash version, but many testers have had no problems with the Splash version on this setup.
Unlike the DrakenFX B20 bootstack, these modified versions do not flash the modem, so there is no need to flash modem again when switching between them. Sometimes will need to Unlock Password in TWRP when switching though, it will say not recognized.
Splash
Ability to have Read/Write access in system.
Nice three logo splash screen, replacing bootloader warning screen.
No bootloader warning screen means not able hit volume button during boot to get menu for Recovery, Fastboot, etc.
Which also means you will have to use power button + volume up combo to enter Recovery, or reboot to recovery from the ROM.
No EDL three button combo.
Can't charge without booting system or TWRP.
NoSplash
Read Only access in system. (Which will break Magisk)
Ugly bootloader warning screen.
Able hit volume button during boot to get menu for Recovery, Fastboot, etc.
Able to use EDL three button combo.
Allows offline charging without booting into system.

WHY EDL?
Starting out with Oki’s LOS 15.1 EDL package just makes it easier for everyone. It’s easier for you because there will be less steps needed to get treblized, which will also mean less room for error. It’s easier for me because it makes for a much shorter guide, and it’s easier to find answers to issues if we all started on the same page. However, if there are enough requests, I’ll make a longer guide without the use of EDL.
If you are already treblized you won’t necessarily need to EDL (in most cases), but if you run into issues please don’t comment until you’ve tried starting with first step.
----------------------------------------
GUIDE
----------------------------------------
STEP 1:
Please follow Oki’s Easy Guide to EDL LOS15.1
IT IS IMPORTANT TO FOLLOW EVERY STEP
Try not to boot into system while going through the steps if possible, but it’s ok if you do.
You can use @djkuz Axon 7 EDL Tool, instead of MiFlash, if you are more familiar with that.
Also, in step 12, it states to format to F2FS, but I recommend to format to EXT4 for the best compatibility with GSIs. As a precaution, to make sure your partitions will read correctly, format the partitions to F2FS per the instructions, then format them back to EXT4.
You can always test if F2FS works for you later.
Thank you @Oki for this wonderful starting point for new Treble users.
CONGRATULATIONS - You are now TREBLIZED and should never have to do Step 1 again.
STEP 2:
Once done with Oki’s guide, stay in TWRP
Wipe Dalvik, Cache, Vendor, System and Data.
Flash the bootstack you chose.
Flash the appropriate modem for your variant.
CONGRATULATIONS - You should never have to flash those again, unless changing bootstack for whatever reason.
STEP 3:
In TWRP make sure System and Vendor partitions are mounted.
Flash the DotOS Vendor flashable.
(It doesn’t have DotOS in the file name, so it should be named something like “Vendor_Flashable_GSI…”)
In TWRP go to Install and in the bottom right select Install Image
Now we flash the Havoc GSI image you extracted, selecting the System partition.
DO NOT BOOT TO SYSTEM - We need to use OrdenKrieger’s TWRP 3.2.3.0 to flash the LOS 15.1 vendor.img
(If you wish to use the DotOS vendor, you can skip to Step 5. You will still need to reboot to Recovery, so don't skip that.)
STEP 4:
Flash TWRP 3.2.3.0 to Recovery partition and then reboot to Recovery
You should now be in TWRP 3.2.3.0
Flash the LOS 15.1 vendor.img to the Vendor partition
DO NOT BOOT TO SYSTEM - We need to restore Oki’s TWRP and flash GApps.
STEP 5:
Flash Oki’s TWRP 3.2.3.0 Lab’s Mod to Recovery partition and then reboot to Recovery
You should now be in Oki’s TWRP 3.2.3.0 Lab’s Mod
Flash GApps
Make sure System and Vendor are mounted
Flash the NFC_Hotspot Fix
NOW BOOT SYSTEM
I will wait here while you setup your device.
DONE? GOOD. Lets set up Magisk and pass SafetyNet
STEP 5:
At this time I recommend Magisk 17.2
Find it, download it, and flash it in TWRP
Once booted, in Magisk search for the module “MagiskHide Props Config” and install it.
Then search for BusyBox module by Osmosis and install it.
Reboot
Using a terminal app (not in TWRP) like Termux, type “su”
Grant root privileges
Then type “props”
You should be greeted with a menu
Select 1 to Edit fingerprint
Select F to Pick a Certified fingerprint
Then follow the menu to select ZTE and Axon 7
Then yes and yes to reboot.
Everything should be good to go now. ENJOY!!
To add just a few more options to your setup without overdoing it with a heavy launcher, I highly recommend:
Lean Launcher Optimized
I will surely be adding to this guide and modifying it as the situation evolves. So feel free to give me any input on how to improve it.
----------------------------------------
THANKS
----------------------------------------
Thanks to @raystef66 and all of the testers in the [SUMMARY][PIE] BEST PIE ROMS to TRY thread, as well everyone in the "Axon7 (s)GSI trebleSHOOT" Telegram group, for testing, "trebleSHOOTing" and reporting your findings.
Thanks to @Oki again for his easy guide and LOS 15.1 EDL package.
Thanks to @Unjustified Dev for uploading separate vendors for us GSI users, and for all of the work he's done on LOS and his help in the LOS threads.
Thanks to @Verequies for creating the two modified versions of @DrakenFX 's B20 bootstacks, and of course @DrakenFX for his B20 and B12 bootstacks.
Thanks to @SaintZ93 for his work on DotOS and for providing a flashable for boot and vendor only.
Thanks to @SaintZ93 and @Skrem339 for their great work on the Schwifty kernel.
And thanks to @hundeva for his work on Lean Launcher.

----------------------------------------
GUIDE EDIT LOG
----------------------------------------
11/22 - Updated that it is optional to stay with DotOS vendor and skip a step.
11/30 - Changed Step 1 to recommend EXT4 for best compatibility. Also to format from EXT4 to F2FS, then back to EXT4, to avoid internal storage error some are getting.
12/10 - Props Config module now requires BusyBox module, updated Step 5.

Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.

JKSurf said:
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
Click to expand...
Click to collapse
Please make sure you redownload Ordens TWRP. There are two of them with the same name out there. The one I linked should allow you to see Vendor partition. I should list this step as optional, as the DotOS vendor works, Ive just found the LOS vendor to show improvement personally. I also wanted to teach how to flash vendor.img, as there is only one way atm, using Ordens TWRP.
The vendor setup in this guide is all based off LOS sources, so any issues LOS is having that are vendor related will carry over to this setup. Sorry.

Really nice guide, sadly I just flashed but one thing that I like is that you try to explain why you choose what you choose and I would really like if you could elaborate more on that for example why DotOS boot image and kernel or why LOS 15.1 vendor.
And also is there a way for me (or anyone on havoc), already on havoc but got there differently, to painlessly migrate to your setup?

I am using this gsi for a week and I like it a lot. It has better battery life than LOS 16 right now and you can customise so much.
And btw for me daydream works normally and I installed the ported pixel camera with night sight, which seems to work normal, too.

Mousman said:
Really nice guide, sadly I just flashed but one thing that I like is that you try to explain why you choose what you choose and I would really like if you could elaborate more on that for example why DotOS boot image and kernel or why LOS 15.1 vendor.
And also is there a way for me (or anyone on havoc), already on havoc but got there differently, to painlessly migrate to your setup?
Click to expand...
Click to collapse
I found minor things to work better with the LOS vendor, such as GPS locking and Bluetooth not freezing display data in my car. Of course this can vary from user to user. And my preference changes as well when I find improvements with other vendors.
The DotOS vendor flashable is provided as it's the easiest way to get an up to date vendor. Otherwise you would have to download and flash an entire ROM, or extract the boot.img from that ROM, or modify the install script. Unjustified didn't provide the LOS vendor in combo with the boot.img, so the DotOS flashable is the best option as of now.
If you're already on the Havoc GSI, then you can just flash the bootstack, wipe vendor, flash DotOS vendor flashable, flash LOS vendor.img if you want (using Ordens TWRP), flash Magisk. Then boot.
It will feel like a dirty flash, but it's not, thanks to Treble.
Please do a full backup before doing so, as I think if your vendor partition was created differently, pulled from data, it might not work.

Kleva94 said:
I am using this gsi for a week and I like it a lot. It has better battery life than LOS 16 right now and you can customise so much.
And btw for me daydream works normally and I installed the ported pixel camera with night sight, which seems to work normal, too.
Click to expand...
Click to collapse
I don't use Daydream, I only know what was reported by others. If more people want to test and report that it's working, I'll gladly remove it from the sacrifices.

EBeatFLA said:
I don't use Daydream, I only know what was reported by others. If more people want to test and report that it's working, I'll gladly remove it from the sacrifices.
Click to expand...
Click to collapse
Re. sacrificing encryption, I thought LOS 15.1 vendor supports it. Is that not enough?
In other words, do you need vendor + system + rom for encryption to work? Or just system + rom? Or...?
Thx for all your work.

piet8stevens said:
Re. sacrificing encryption, I thought LOS 15.1 vendor supports it. Is that not enough?
In other words, do you need vendor + system + rom for encryption to work? Or just system + rom? Or...?
Thx for all your work.
Click to expand...
Click to collapse
This particular setup will sacrifice encryption. Getting encryption on a GSI would be another path. The TWRP and bootstack options we have for our device play a part in why I find encryption to be a mess right now, and chose to move forward without it.

I'm kinda having issues flashing LOS 15.1 vendor.img. I flashed Ordens TWRP, the one you provided but I do not get an option to flash to vendor partition when I choose to flash that LOS 15.1 vendor.img

g0dzstar said:
I'm kinda having issues flashing LOS 15.1 vendor.img. I flashed Ordens TWRP, the one you provided but I do not get an option to flash to vendor partition when I choose to flash that LOS 15.1 vendor.img
Click to expand...
Click to collapse
JKSurf said:
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
Click to expand...
Click to collapse
OMG guys, so sorry, was linking to the wrong TWRP. Link updated. It's not on AFH, so if you don't trust it's a legit link and want to check, it's the same link in the LOS16 op.
Thanks for testing.

Did everything from guide, but it seems like i don't have access to internal storage in havoc os and still accesible in twrp. Any suggestion what i did wrong?

Reakleases said:
Did everything from guide, but it seems like i don't have access to internal storage in havoc os and still accesible in twrp. Any suggestion what i did wrong?
Click to expand...
Click to collapse
Make sure to follow all of the steps in Oki's guide. Also, if you used the NoSplash bootstack, that might be it. But I'm pretty sure it's a missed step in his guide.

did everything again without success, but something of that helped, tried chmod 755 on root directory and fix contexts.

Really nice guide, thanks!

Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.

juniorD said:
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
Click to expand...
Click to collapse
Make sure system and vendor are mounted before flashing.

juniorD said:
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
Click to expand...
Click to collapse
Wrong bootstack,flash bootstack again!
Also i read in previous post,people are not wiping correctly the system with clean flash

Predatorhaze said:
Wrong bootstack,flash bootstack again!
Also i read in previous post,people are not wiping correctly the system with clean flash
Click to expand...
Click to collapse
Thanks for the reply.
I flashed the bootstack in the EDL package uploaded in the guide using MiFlash went through fine. Also did a clean wipe of everything and formatted my Internal Storage before I flashed the package.
---------- Post added at 07:51 AM ---------- Previous post was at 07:50 AM ----------
EBeatFLA said:
Make sure system and vendor are mounted before flashing.
Click to expand...
Click to collapse
Yup did that and checked a second time to make sure I did. They were mounted.
---------- Post added at 07:52 AM ---------- Previous post was at 07:51 AM ----------
EBeatFLA said:
Make sure system and vendor are mounted before flashing.
Click to expand...
Click to collapse
Yup did that and checked a second time to make sure I did. They were mounted.

[ROM] [Discontinued] [Android 10] [Payton] Arrow OS 10.0 | UNOFFICIAL STABLE

ArrowOS
ABOUTArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: paypal
changelog and future updates
join moto x4 telegram channel
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log
screenshot thanks to domenik (MotoX4Custom) for this website
INSTALLATION
click here
DOWNLOADS
ROM: Arrow-OS for payton
download
Gapps included
Source Code: https://github.com/ArrowOS
Device Source: https://github.com/mhdaslam790/device-motorola-payton
ROM OS Version: Android 10
ROM Kernel: Linux 3.x.x
Based On: AOSP 10.0

mhdaslam790 said:
ArrowOS
ABOUTArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: paypal
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : check how to
DOWNLOADS
ROM: Arrow-OS for payton
download
Gapps included
Source Code: https://github.com/ArrowOS
Device Source: https://github.com/mhdaslam790/device-motorola-payton
ROM OS Version: Android 10
ROM Kernel: Linux 3.x.x
Based On: AOSP 10.0
Click to expand...
Click to collapse
ScreenShots??

srishab55 said:
ScreenShots??
Click to expand...
Click to collapse
Screenshots are here
https://motox4custom.jimdofree.com/android-10/arrow-os/

Can anyone confirm whether Voice Match (OK Google) is working in this ROM? It appears that it might be causing mic issues in other Android 10 ROMs. Thanks!

jhedfors said:
Can anyone confirm whether Voice Match (OK Google) is working in this ROM? It appears that it might be causing mic issues in other Android 10 ROMs. Thanks!
Click to expand...
Click to collapse
Working fine

Thank you for not only this rom but also the custom website!
---------- Post added at 04:32 AM ---------- Previous post was at 03:58 AM ----------
What does ' Error applying update:15 ( ErrorCode:kNewRootfsVerificationError )' mean? I don't know how to solve it.

EthonBanks said:
Thank you for not only this rom but also the custom website!
---------- Post added at 04:32 AM ---------- Previous post was at 03:58 AM ----------
What does ' Error applying update:15 ( ErrorCode:kNewRootfsVerificationError )' mean? I don't know how to solve it.
Click to expand...
Click to collapse
Website is made by Dominick (motox4custom)
Huge shout out to him

Are MOTO actions included in this ROM and working?

Lakynko said:
Are MOTO actions included in this ROM and working?
Click to expand...
Click to collapse
Of course!

Already tried thank you
And must write, that very good ROM! Big thanks.
No bugs so far. Everything goes smoothly.
Stayed on a daily use!
PS: Came from Superior OS

I would appreciate some help. I took a FI X4 and installed Arrow with no issues. Then I tried to re-install with gapps and things went south. Maybe I'm being bitten by the A/B thing.
My current state:
SCENARIO 1
* Clean install Stock FI for X4 works
* Then "copy partitions" and reboot to System fails and reboots to Recovery. <-- Not sure why this happens
SCENARIO 2
* Clean install Stock FI again -- boots and works fine
* fastboot boot twrp, wipe, install Arrow -- install gives no errors
* Reboot to system results in endless Arrow boot animation. I've waited for a couple of hours, so it's not a matter of time.
Suggestions on what I can try? Is "copy partitions" really necessary? (I've put Lineage on two other X4's without using 'copy partitions' -- I didn't even know about it at the time.)

Randy Power said:
I would appreciate some help. I took a FI X4 and installed Arrow with no issues. Then I tried to re-install with gapps and things went south. Maybe I'm being bitten by the A/B thing.
My current state:
SCENARIO 1
* Clean install Stock FI for X4 works
* Then "copy partitions" and reboot to System fails and reboots to Recovery. <-- Not sure why this happens
SCENARIO 2
* Clean install Stock FI again -- boots and works fine
* fastboot boot twrp, wipe, install Arrow -- install gives no errors
* Reboot to system results in endless Arrow boot animation. I've waited for a couple of hours, so it's not a matter of time.
Suggestions on what I can try? Is "copy partitions" really necessary? (I've put Lineage on two other X4's without using 'copy partitions' -- I didn't even know about it at the time.)
Click to expand...
Click to collapse
Clean flash stock firmware
Then flash twrp format in f2fs and reboot
Boot to twrp and Flash copy partition and take persist efs backup
Then wipe data system dalvik
Flash rom+ twrp zip
Reboot recovery and flash magisk if you want...(you dont need to flash gapps BECAUSE it is included in rom)
Just reboot to system
Have look on this website for issue https://motox4custom.jimdofree.com/instructions/install-a-custom-rom/

Trouble installing
EDIT: Got it working!
I gave up waiting for the animation. Switched /data's file system to e2fs, formatted, re-installed Arrow+TWRP and badaboom! Arrow started up successfully. I think I was missing the "format /data" step after switching its fs.
Thank you
------------ END UPDATE -----------
mhdaslam790 said:
Clean flash stock firmware
Then flash twrp format in f2fs and reboot
Boot to twrp and Flash copy partition and take persist efs backup
Then wipe data system dalvik
Flash rom+ twrp zip
Reboot recovery and flash magisk if you want...(you dont need to flash gapps BECAUSE it is included in rom)
Just reboot to system
Have look on this website for issue https://motox4custom.jimdofree.com/instructions/install-a-custom-rom/
Click to expand...
Click to collapse
Thanks for the quick help and reference. I'm not sure if it worked yet or not... It's been running the Arrow boot animation for 20 minutes so far. I'll report back.
Questions:
Is TWRP's warning of "No OS Installed" something I can ignore? (see attached photo)
Why do you recommend a backup of efs and persist? I don't see it used later.
I did not switch /data to f2fs this time because it completely failed (Stock wouldn't boot up). Is f2fs required?
How long should I wait while the boot animation runs before giving up?
Can I capture a log that would be helpful troubleshooting what's going on with the boot?
Here's what I did:
Clean flash stock firmware (XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-6-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip)
Reboot to "Get Started" screen - SUCCESS
Boot to twrp
Flash copy partition
Reboot to "Get Started" screen (confirm all is still working) - SUCCESS
Make backup of persist and efs
Wipe data, system, dalvik
Flash Arrow (did not flash magisk or gapps) File: Arrow-v10.0-payton-UNOFFICIAL-20200119-VANILLA.zip
Flash twrp installer (zip)
Reboot to system --
- twrp warned of "no os installed"
- arrow boot animation

The latest update wiped out fingerprint gestures. It is turned on, but does not work.

What does ' Error applying update:15 ( ErrorCode:kNewRootfsVerificationError )' mean?
I tried both TWRP-payton-3.3.1-Syber-v2.2_11-02 and official twrp
step 1/2...
step 2/2...
Error applying update:15 ( ErrorCode:kNewRootfsVerificationError )

Fingerprint gestures don't work. And hope we can disable the battery charging LED.

johnjingle said:
The latest update wiped out fingerprint gestures. It is turned on, but does not work.
Click to expand...
Click to collapse
Wait for next update

Update -- I went back to stock and now can't get any mobile signal. No voice, no 2G; it's dead. The SIM works fine in my other (Lineage) X4. Looks like bad hardware.
----- end of update -----
Hi all. I'm taking my Arrow-powered new-to-me X4 out today for the first time and just realized it's not getting 4G. In fact, it's all the way back to Edge. My network is set to Global and I'm on T-Mobile USA.
Is LTE working for others here?
I can switch to stock later to check the hardware on this device but that will take some time.

Randy Power said:
Update -- I went back to stock and now can't get any mobile signal. No voice, no 2G; it's dead. The SIM works fine in my other (Lineage) X4. Looks like bad hardware.
----- end of update -----
Hi all. I'm taking my Arrow-powered new-to-me X4 out today for the first time and just realized it's not getting 4G. In fact, it's all the way back to Edge. My network is set to Global and I'm on T-Mobile USA.
Is LTE working for others here?
I can switch to stock later to check the hardware on this device but that will take some time.
Click to expand...
Click to collapse
Doesn't work for me, I do even get 3G, only phone calls.

johnjingle said:
Doesn't work for me, I do even get 3G, only phone calls.
Click to expand...
Click to collapse
Sorry to hear.
I acquired a different X4 and installed Arrow without incident and I'm getting 4G on T-Mobile USA fine now. Maybe you also have bad hardware? Does LTE work on your phone with different firmware?
---------- Post added at 01:47 AM ---------- Previous post was at 01:35 AM ----------
How does the Updater work?
In Settings, I can search for "update" and see "System updates" in the search results. Tapping on that brings up the System menu but there is no "System updates" listed.
I flashed 20200119 a couple of days ago and I thought it's been updated since then.

[Guide][GSI][10.0] How to get Havoc OS 3.12 GSI running on Redmi 8A

Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global Rom but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx, due to support wifi 2.4 ghz only. (Because bluetooth interfering with wifi 2.4 Ghz and our device doesn't support 5ghz wifi)
Compare to MIUI, Havoc OS has somethings i like:
+ Faster download/upload speed: no delay with wifi bluetooth interference
+ Doesn't have bloatware, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk and root.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI and extract to get system
From Official Havoc OS here: https://sourceforge.net/projects/havoc-os/files/a64-ab/ (Newer Version)
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature. If it doesn't work, then try an alternative way:
Open /vendor/bin/init.qcom.post_boot.sh and add the string:
Code:
sendevent /dev/input/event2 0 1 5
then reboot
13) Enjoy Havoc OS. Install apps, configure settings...
How to Update
- Flash system image over, no wipe require. Just reboot.
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from https://vancedapp.com/; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
- To fix Recording, from Misc features -> Force Timestamp Source, choose Clock boottime
And that's all. Now enjoy!
I gifted my sister this phone so i don't have device to test anymore. Still, sometime i'll test if i can. The guide still works so enjoy flashing!!!

Great. I've been using havocOs for almost two months now and it's great. Much quicker and smoother than stock miui. Only problem I've been trying to find a fix for is setting up a lock screen.
Thanks for sharing the dt2w module for magisk. Is there some sort of setting I need to mess with to get it to work? I've installed the module and activated it in magisk but dt2w still won't work. I also activated the dt2w setting that comes with havocOs 3.1 under " xiaomi features " but that never worked from the beginning.

ways2 said:
Great. I've been using havocOs for almost two months now and it's great. Much quicker and smoother than stock miui. Only problem I've been trying to find a fix for is setting up a lock screen.
Thanks for sharing the dt2w module for magisk. Is there some sort of setting I need to mess with to get it to work? I've installed the module and activated it in magisk but dt2w still won't work. I also activated the dt2w setting that comes with havocOs 3.1 under " xiaomi features " but that never worked from the beginning.
Click to expand...
Click to collapse
Did you flash no_encrypt zip? It'll make set up screen password impossible because encryption is disable. I have clean flashed Havoc OS and confirm d2tw module working, despite i don't active the xiaomi option in setting.

Ga_hap_la_chanh said:
Did you flash no_encrypt zip? It'll make set up screen password impossible because encryption is disable. I have clean flashed Havoc OS and confirm d2tw working, despite i don't active the xiaomi option in setting.
Click to expand...
Click to collapse
Yes I believe I did flash no_encrypt. Is there any possible way to re-enable Encryption to set up a screen lock at this point?

ways2 said:
Yes I believe I did flash no_encrypt. Is there any possible way to re-enable Encryption to set up a screen lock at this point?
Click to expand...
Click to collapse
There is a trick, you can enable encryption through Settings -> security -> Encryption and credentials then encrypt phone. If it doesn't work, then read this thread https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Or you can do the whole process again, clean flash and do as my thread. May be d2tw starts working.

Thank you sir
thanks a lot for this
can you tell me how to upgrade our 32bit os to 64bit

Ga_hap_la_chanh said:
There is a trick, you can enable encryption through Settings -> security -> Encryption and credentials then encrypt phone. If it doesn't work, then read this thread https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Or you can do the whole process again, clean flash and do as my thread. May be d2tw starts working.
Click to expand...
Click to collapse
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.

ways2 said:
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
Click to expand...
Click to collapse
Hi bro
i am new to this
i have 2gb indian varient
can you make a full youtube tutorial of twrp installation
or give correct steps how to do twrp
---------- Post added at 05:48 AM ---------- Previous post was at 05:42 AM ----------
Ga_hap_la_chanh said:
Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global 10.3 but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx.
Compare to MIUI, Havoc 3.1 has somethings i like:
+ Faster download/upload speed: almost the same as the speed of my network
+ Doesn't have some bloatwares, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important to me.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI from ExpressLuke and extract to get system imagehttps://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/A64/AB/
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature.
13) Enjoy Havoc OS. Install apps, configure settings...
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from vanced.app; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
And that's all. Now enjoy!
Click to expand...
Click to collapse
Hi
can you make a youtube video of twrp and gsi installation
please man for redmi 8a

eddy law paul king said:
Hi bro
i am new to this
i have 2gb indian varient
can you make a full youtube tutorial of twrp installation
or give correct steps how to do twrp
---------- Post added at 05:48 AM ---------- Previous post was at 05:42 AM ----------
Hi
can you make a youtube video of twrp and gsi installation
please man for redmi 8a
Click to expand...
Click to collapse
I've considered making a complete tutorial on installing recovery, root, & rom installation for this phone. Next time I go back to stock I probably will make a video. Until then you can definitely follow the tutorials on this forum to install a custom recovery and rom. Personally I would recommend installing OrangeFox recovery because TWRP has touchscreen issues sometimes.
You will have to unlock the bootloader first which takes 14 days if you have not already.
The tool to unlock the Bootloader is here: https://en.miui.com/unlock/download_en.html
Once your bootloader is unlocked you're ready to install OrangeFox custom recovery, the files and instructions can be found here:
https://forum.xda-developers.com/xi...t/orangefox-recovery-xiaomi-redmi-8a-t4032583
Once you have OrangeFox recovery installed you can follow this tutorial in this thread to install HavocOS rom or the other thread
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Try it out and then come back and let us know what problems you run into

ways2 said:
I've considered making a complete tutorial on installing recovery, root, & rom installation for this phone. Next time I go back to stock I probably will make a video. Until then you can definitely follow the tutorials on this forum to install a custom recovery and rom. Personally I would recommend installing OrangeFox recovery because TWRP has touchscreen issues sometimes.
You will have to unlock the bootloader first which takes 14 days if you have not already.
The tool to unlock the Bootloader is here: https://en.miui.com/unlock/download_en.html
Once your bootloader is unlocked you're ready to install OrangeFox custom recovery, the files and instructions can be found here:
https://forum.xda-developers.com/xi...t/orangefox-recovery-xiaomi-redmi-8a-t4032583
Once you have OrangeFox recovery installed you can follow this tutorial in this thread to install HavocOS rom or the other thread
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Try it out and then come back and let us know what problems you run into
Click to expand...
Click to collapse
i am very afraid that i brick my devise
so make a video
it is accurate and much helpful and easy to understand
i am waiting

Can I use the attached files for installing gsi in redmi 9 ?

vinith 32 said:
Can I use the attached files for installing gsi in redmi 9 ?
Click to expand...
Click to collapse
no
this is for 8 and 8a only

@Ga_hap_la_chanh
I'm wondering if that d2tw module not working for me has something similar to do with how the touch screen becomes unresponsive in TWRP for some people. What recovery did you use on your redmi?

ways2 said:
@Ga_hap_la_chanh
I'm wondering if that d2tw module not working for me has something similar to do with how the touch screen becomes unresponsive in TWRP for some people. What recovery did you use on your redmi?
Click to expand...
Click to collapse
I used TWRP then moved to Orange Fox. Everything working fine, may be your screen is different. In d2tw module, there's a file called readme.md: Manual usage : - enable $ set-dt2w 1 - disable $ set-dt2w 0
Just try it -))))))))

Great GSI. I have this one problem though. I cannot backup anything from TWRP. Is it really normal because it's encrypted?
createTarFork() process ended with ERROR: 255

Ga_hap_la_chanh said:
Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global 10.3 but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx.
Compare to MIUI, Havoc 3.1 has somethings i like:
+ Faster download/upload speed: almost the same as the speed of my network
+ Doesn't have some bloatwares, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important to me.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI from ExpressLuke and extract to get system imagehttps://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/A64/AB/
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature.
13) Enjoy Havoc OS. Install apps, configure settings...
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from vanced.app; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
And that's all. Now enjoy!
Click to expand...
Click to collapse
Bro having oragane fox recovery installed on my redmi 8a device, can you please tell me at which step of flashing gsi we have to flash vbmeta.img and boot. Img
---------- Post added at 03:13 AM ---------- Previous post was at 02:26 AM ----------
ways2 said:
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
Click to expand...
Click to collapse
bro can you tell me that have you flashed the boot.img while flashing the gsi and if yes then at which step..

ItsmeTushar said:
Bro having oragane fox recovery installed on my redmi 8a device, can you please tell me at which step of flashing gsi we have to flash vbmeta.img and boot. Img
---------- Post added at 03:13 AM ---------- Previous post was at 02:26 AM ----------
bro can you tell me that have you flashed the boot.img while flashing the gsi and if yes then at which step..
Click to expand...
Click to collapse
Boot.img and vbmeta are done before flashing the gsi. I'd recommend reading this thread first for better understanding
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Zzzleepy said:
Great GSI. I have this one problem though. I cannot backup anything from TWRP. Is it really normal because it's encrypted?
createTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
I'm getting the same error with attempting to make a back up in orangefox. After seeing you have the same problem now I'm assuming it is indeed a problem with encryption? I was able to make backups successfully before my phone was encrypted so I still have an old back up on my PC. However it would be nice to be able to make a new fresh back up.

I'm getting the same error with attempting to make a back up in orangefox. After seeing you have the same problem now I'm assuming it is indeed a problem with encryption? I was able to make backups successfully before my phone was encrypted so I still have an old back up on my PC. However it would be nice to be able to make a new fresh back up.
Click to expand...
Click to collapse
That was weird. In stock ROM, I can back up the /data/media just fine even when encrypted. But after having Havoc OS, I cannot do that anymore. Tried on both TWRP and OrangeFox. I can, with an unencrypted phone, but I do not feel comfortable without a lockscreen. Tried all things I have researched on that error. Not one worked. Might as well just stick to Titanium Backup for backups.
Overall, great GSI. Loading is faster than on stock (with the internet too)! Though, I have another issue with regards to the locking of apps, so that the app would not be cleared. Speaking of clearing apps, it is tiring to scroll left just to see the "Clear All" option in Recents. Autostart too.
I know you are not the developer, but just letting you know my concerns.

How to resize system partition for install gapps?

Soerex24 said:
How to resize system partition for install gapps?
Click to expand...
Click to collapse
Reboot to custom recovery > Menu > Manage Partitions > System > Resize or Repair

[ROM][OFFICIAL] LineageOS 17.1 for Nexus 6 (shamu)

LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Recovery
The LineageOS 17.1 reovery is recommended
If you still want to use TWRP never install the TWRP app as system app. Otherwise your device won't boot
Current lineage 17.1 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
Before you flash a bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one and don't need to flash it again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/shamu
Google apps: Opengapps Use an ARM (not ARM64) package for Android 10
HEADS UP: When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
Changelog
Builddate: 2020.06.17
Changes:
[new] June security updates
[new] LineageOS clock
Builddate: 2020.05.29
Changes:
[new] May security updates
[fix] ULL audio fixes
[new] Add back serif fonts
[fix] Screen turning itself on when no lockscreen is set
[new] Etar calendar
Builddate: 2020.04.12
Changes:
[new] April security updates ROM & kernel
Builddate: 2020.04.08
Changes:
[new] Initial LineagOS 17.1 release
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-16.0
[bug] IMS is not working - if you need it you have to stay on lineage-15.1
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, elektroschmock, npjohnson
Source Code: http://github.com/lineagos
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2020-04-08
Last Updated 2020-04-08

Reserved
First build isn't out yet, but I don't want the LineageOS 16.0 thread to be spammed with 17.1 questions
Will waiting for the build you might want to read the Changlog for the first LineageOS 17.1 release:
Changelog 24

Will there be a possibility to root?

Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?

Thanks @Elektroschmock and @npjohnson for keeping the Nexus 6 alive in 2020. :good:

Eazy said:
Will there be a possibility to root?
Click to expand...
Click to collapse
Yes you can use your root solution of choice.
Only thing coming with the ROM is adb root.
dlbarron said:
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Click to expand...
Click to collapse
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]

Elektroschmock said:
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Click to expand...
Click to collapse
Actually, I've been running Lineage and CM before that since I brought the phone home. So there's no way I had the latest stock image installed ever.
Thanks, I'm all set

Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.

BootloopedMillennials said:
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
Click to expand...
Click to collapse
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work

xrenoix said:
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
Click to expand...
Click to collapse
My system got corrupted by the previous process. So I had to do a fresh install.

BootloopedMillennials said:
My system got corrupted by the previous process. So I had to do a fresh install.
Click to expand...
Click to collapse
Hello you have test wipe system with twrp ? Or test repair ? And use pico gapps for trébuchet launcher not work with mirco gapps but pixel launcher work ? !

whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .

mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Best would be to use built in update. Unless you want to do a clean install, there's no reason to do it.

the update inside of lineage is blocking updating to lineage 17.1 , i tried tha earlier and i jsut tried it again. then it gives the link to the wiki page.so thats not going to work.i will have to do the old method of flashing through twrp or hoping that there is a command line approach to flashing lineage through lineage recovery.

mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Sorry, I didn't ignore your question, but I first had to check.
It's kind of hard to imagine how a blind person would do it if you can see.
If you have Lineage recovery installed and are able to boot into recovery do the following steps:
Press the Volume Down button 1 time
Press the power button two times
You are now in the adb apply update mode.
There you can install all the zip files you want. I guess you script does the rebooting to system itself.
If you need further help just ask.

@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!

s_dino said:
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
Click to expand...
Click to collapse
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.

Elektroschmock said:
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Click to expand...
Click to collapse
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.

I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).

s_dino said:
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
Click to expand...
Click to collapse
You still have those options:
Go to "Factory Reset"
There you can choose which partition you want to wipe.
- Wipe data/factory reset
- Wipe cache
- Wipe system
I guess you want the "wipe system" option
Sorry we don't support modifying our builds for obvius reasons. If you want to do that you are on your own. Sorry.
runekock said:
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
Click to expand...
Click to collapse
It's just a test. Non of us was able to trigger the loss of audio. Youl'll still have stereo but it won't switch channels if you turn your device.

[ROM][UNOFFICIAL][10.0][ALI] LineageOS 17.1 [64 Bit][DISCONTINUED]

Hi,
Thanks, I was waiting for this. I will test it on the weekend. Can you please move the thread to "Moto G6 ROMs, Kernels, Recoveries, & Other Development" section? It will be easier to find it.

roypen said:
Hi,
Thanks, I was waiting for this. I will test it on the weekend. Can you please move the thread to "Moto G6 ROMs, Kernels, Recoveries, & Other Development" section? It will be easier to find it.
Click to expand...
Click to collapse
Hi, I request to Moderators move the thread to that section. I don't have permissions to move it.

tomarc said:
Thanks you ! This is great news for me.
Can you fix the Moto Fingerprint Gestures ? Or maybe the rom has it own alternative ?
Click to expand...
Click to collapse
I'm trying to solve moto gestures but don't get a solution yet, the alternative are the android 10 gestures but they work with the screen, not with fingerprint

tomarc said:
Thanks you ! This is great news for me.
Can you fix the Moto Fingerprint Gestures ? Or maybe the rom has it own alternative ?
Click to expand...
Click to collapse
I'm trying to solve moto gestures but don't get a solution yet, the alternative are the android 10 gestures but they work with the screen, not with fingerprint

Thank you
Thank you very much for building and posting this ROM. I would very much like to try it on my G6 (XT1925-5).
Following this thread, I got as far as unlocking the bootloader and booting TWRP from fastboot. But could not flash anything because of a locked boot.img. I have requested an edited boot.img and hope to get a reply.
Is there perhaps another way to get my G6 (XT1925-5) with firmware version PPSS29.55-37-7-10 to be able to run LineageOS?
Thanks in advance,
FWieP

fwiep said:
Thank you very much for building and posting this ROM. I would very much like to try it on my G6 (XT1925-5).
Following this thread, I got as far as unlocking the bootloader and booting TWRP from fastboot. But could not flash anything because of a locked boot.img. I have requested an edited boot.img and hope to get a reply.
Is there perhaps another way to get my G6 (XT1925-5) with firmware version PPSS29.55-37-7-10 to be able to run LineageOS?
Thanks in advance,
FWieP
Click to expand...
Click to collapse
Hi, which twrp did you try? You might want to use the twrp64 as this LOS17.1-build is a 64 Bit

nightmw said:
Hi, which twrp did you try? You might want to use the twrp64 as this LOS17.1-build is a 64 Bit
Click to expand...
Click to collapse
Thanks for the reply. I used twrp-3.4.0-0-ali, downloaded from the official download page.
Is there a special download page for 64bit TWRP?
Kind regards,
FWieP

tomarc said:
You can find it here : https://forum.xda-developers.com/moto-g6/development/twrp-twrp-64-bit-ali-t4093879
Click to expand...
Click to collapse
Once again: thank you all. I downloaded the mali.img and booted TWRP from it.
Then, I flashed the new LineageOS 17.1 and OpenGapps - without any problems, warnings or errors.
If there is no way to flash TWRP into the recovery partition permanently, I can live with that.
Most important thing is, I can flash the system partition when needed.
Hope to see more of your work!
Kind regards,
FWieP

BetoxxDios said:
What's not working:
Moto Fingerprint Gestures
You tell me
Contributors
@BetoxxDios
@Electimon
@abhishek_d9
@jeangraff30
Click to expand...
Click to collapse
Having flashed this ROM a few days ago, I find it nearly perfect. Nearly
the October 2020 security patches are available from LineageOS; can they be included?
Would it be possible for you to share your kernel (link to source) and roomservice.xml?
I would like to try and build the ROM myself. Perhaps contribute, at least providing a mirror for the ROM files?
If not you (@BetoxxDios), perhaps the other contributors (@Electimon, @abhishek_d9, @jeangraff30) ?
Thanks!
Kind regards,
FWieP

failed to load kernel!
On my XT1925-5 I have flashed this rom serveral times, no errors, but it fails to boot.
When I restore the backup, I'm on stock again...
After installing twrp (mali.img) I did format data, reboot onto twrp, wipe, install etc.
Still it will boot only to fastboot: failed to load kernel!
Any suggestions?

Close, but no cigar - yet
fwiep said:
Would it be possible for you to share your kernel (link to source) and roomservice.xml?
I would like to try and build the ROM myself.
Click to expand...
Click to collapse
Thanks @BetoxxDios for providing the links to kernel, device and vendor trees in a private message.
After expanding the RAM of my machine to 16GB and some very educational experiments, the build finally succeeded.
TWRP flashed the ROM without any errors. Yeah!
Then the first reboot. I know that this usually takes a long time - say, 5 minutes. I've left it booting for more than 4 hours, but it doesn't get past the bootanimation.
Can anyone help me in solving this piece of the puzzle? Are there any logs I can get at while the phone is not yet adb-ready? What does LineageOS do while booting for the first time?
Thanks and kind regards,
FWieP
P.S. For the moment, I've flashed @BetoxxDios' original ROM. It's better (and safer) than Motorola's stock firmware.

fwiep said:
.
Then the first reboot. I know that this usually takes a long time - say, 5 minutes. I've left it booting for more than 4 hours, but it doesn't get past the bootanimation.
Can anyone help me in solving this piece of the puzzle? Are there any logs I can get at while the phone is not yet adb-ready? What does LineageOS do while booting for the first time?
Thanks and kind regards,
FWieP
A frozen boot screen like that has happened to me many times. Usually 1 of 2 issues. 1. Gapps problem 2. Magisk problem.
Cheers.
Click to expand...
Click to collapse

Baronstragen said:
A frozen boot screen like that has happened to me many times. Usually 1 of 2 issues. 1. Gapps problem 2. Magisk problem.
Click to expand...
Click to collapse
Thanks for the tip.
I'm afraid this is another issue - I haven't flashed any Gapps with my ROM (yet), and have never even used Magisk before.
 @BetoxxDios has shown me a way to get logfiles during boot: build an -eng variant instead of -user or -userdebug.
Now, we're investigating what's going wrong. To be continued!
Kind regards,
FWieP

tomarc said:
Yes, you can flash it permanently :
Fastboot flash recovery xxx.img ; xxx.img being the name of the recovery file.
Click to expand...
Click to collapse
Up until today, I thought this wouldn't work. When doing so, fastboot would say:
Code:
writing 'recovery'...
(bootloader) Image not signed or corrupt
And thus, I thought it had not flashed at all.
Today, I read elsewhere on this forum, to simply ignore this message and check whether it flashed. It actually has!
So, thank you, once again
Kind regards,
FWieP
---------- Post added at 17:22 ---------- Previous post was at 17:08 ----------
fwiep said:
Now, we're investigating what's going wrong. To be continued!
Click to expand...
Click to collapse
And continue it does.
Right from the start, while building this ROM, I got an error about an undefined shared library: libqsap_sdk in /device/motorola/ali/libshims/Android.mk.
I saw it was in a section marked "optional", so I commented it out. And the build succeeded. Yes! After flashing, I got the looping boot-animation. D'oh!
But then, while trying to build another ROM (Resurrection Remix OS 8.6.3 by @abhishek_d9), I got the same error.
I again commented the section out, built the ROM successfully, but got the same looping boot-animation after flashing.
So, XDA to the rescue: I found this post which explains to include '/system/qcom' from LineageOS to get that libqsap_sdk included. I've added it to my roomservice.xml and have started another build. It looks very promising.
Maybe case solved? I'll let you know.
Update
Close, but no cigar. The looping boot-animation still persists. I'll investigate further...
Kind regards,
FWieP

whats-in-a-name said:
On my XT1925-5 I have flashed this rom serveral times, no errors, but it fails to boot.
When I restore the backup, I'm on stock again...
After installing twrp (mali.img) I did format data, reboot onto twrp, wipe, install etc.
Still it will boot only to fastboot: failed to load kernel!
Any suggestions?
Click to expand...
Click to collapse
I bought a new phone, also XT1925-5 and unlocked. But also here, I get the same error:
failed to load kernel!
Stock Android was 8.0 and this rom is 10. could that be a problem?

Solved 'kernel not found'
whats-in-a-name said:
I bought a new phone, also XT1925-5 and unlocked. But also here, I get the same error:
failed to load kernel!
Stock Android was 8.0 and this rom is 10. could that be a problem?
Click to expand...
Click to collapse
I used Motorola Rescue and Smart Assistant Tool
First of all I restored the phone by using the rescue_and_smart_assistant and installed Android 9
Then I used: fastboot boot mali.img
In TWRP, I removed encryption by installing: Force_Encryption_Disabler_For_ALI_Oreo_v2.zip
Wipe, the standard wipe (factory reset) + Format data
Then reboot to bootloader, and again load TWRP: fastboot boot mali.img
Wipe again and install the system (lineage-17.1-20201001-UNOFFICIAL-ali.zip)
install Magisk
Wipe cache and Dalvik
reboot into system

whats-in-a-name said:
Solved 'kernel not found'
I used Motorola Rescue and Smart Assistant Tool
First of all I restored the phone by using the rescue_and_smart_assistant and installed Android 9
Then I used: fastboot boot mali.img
In TWRP, I removed encryption by installing: Force_Encryption_Disabler_For_ALI_Oreo_v2.zip
Wipe, the standard wipe (factory reset) + Format data
Then reboot to bootloader, and again load TWRP: fastboot boot mali.img
Wipe again and install the system (lineage-17.1-20201001-UNOFFICIAL-ali.zip)
install Magisk
Wipe cache and Dalvik
reboot into system
Click to expand...
Click to collapse
I tried all of that and keep getting "updater process ended with ERROR: 255 Error installing zip file...." Any way to fix this issue? I'm on XT1925-6 32gb.
Never mind, I had the wrong TWRP installed like a dope.

I installed the ROM following your instructions and other sources:
- unlocked the bootloader
- flashed the unofficial TWRP recovery for the moto g6 ali (https://forum.xda-developers.com/t/twrp-unofficial-twrp-64-bit-for-ali.4093879/)
- wiped system, data, cache and dalvik, my device has no vendor partition though
- flashed your Lineage Rom
- flashed the most recent GAPPS, for Android 10, arm 64, stock
Then rebooting the phone will just end up in an infinite boot animation.
Doing it all over without the gapps and the phone boots just fine. So it seems that the gapps installation is somehow causing the trouble. I tried many different gapps packages, but all without any success.
Could you provide a link to a gapp package that is known to work with your ROM?
Thanks in advance!

I installed the ROM following your instructions and other sources:
- unlocked the bootloader
- flashed the unofficial TWRP recovery for the moto g6 ali (https://forum.xda-developers.com/t/twrp-unofficial-twrp-64-bit-for-ali.4093879/)
- wiped system, data, cache and dalvik, my device has no vendor partition though
- flashed your Lineage Rom
- flashed the most recent GAPPS, for Android 10, arm 64, stock
Then rebooting the phone will just end up in an infinite boot animation.
Doing it all over without the gapps and the phone boots just fine. So it seems that the gapps installation is somehow causing the trouble. I tried many different gapps packages, but all without any success.
Could you provide a link to a gapp package that is known to work with your ROM?
Thanks in advance!

Better Mobile App

welcome