Database Users

[GUIDE] Install Lineage OS 14.1 on Redmi Note 3 (No in call audio issue fixed)

Hello guys, this is my first guide here. So as the title says, I will show you how to install Lineage OS on your Redmi Note 3 device (kenzo).
So before following the guide, your device should have a unlocked bootloader and TWRP recovery.
I will also tell you how to fix in calls audio issue if you are facing it after installing Lineage OS 14.1
So let's begin.
First download the rom (refer to the official thread).
Download Cm14.1 firmware for kenzo (you can find it in the same rom thread)
Download Gapps (any package like micro or nano)
Procedure:-
1- Boot to TWRP recovery.
2- Go to wipe menu. Wipe system, data, dalvik cache and cache.
3- Now go to mount, and mount cust and persist.
4- Go to install. Select the firmware zip file you had downloaded. Install it. (This fixes in call audio problem)
5- After installing it you can unmount cust and persist from the mount menu.
6- After it flash the official Lineage OS rom which you had downloaded. (Install menu, zip)
7- After rom is flashed, flash Gapps package. (Install menu, zip)
8- After flashing Gapps, go to wipe and wipe cache, dalvik cache.
9- Reboot your device
10-Enjoy!
First Reboot will take a while so don't panic... Download Google camera if you want a more stable camera (since stock is quite buggy).. Also you can use Umang's Flashlight fix for the buggy Flashlight button.
Just in case you want to root the device, just download root add-on (found in official thread)
Enjoy the experience.. ?

xzy99 said:
Hello guys, this is my first guide here. So as the title says, I will show you how to install Lineage OS on your Redmi Note 3 device (kenzo).
So before following the guide, your device should have a unlocked bootloader and TWRP recovery.
I will also tell you how to fix in calls audio issue if you are facing it after installing Lineage OS 14.1
So let's begin.
First download the rom (refer to the official thread).
Download Cm14.1 firmware for kenzo (you can find it in the same rom thread)
Download Gapps (any package like micro or nano)
Procedure:-
1- Boot to TWRP recovery.
2- Go to wipe menu. Wipe system, data, dalvik cache and cache.
3- Now go to mount, and mount cust and persist.
4- Go to install. Select the firmware zip file you had downloaded. Install it. (This fixes in call audio problem)
5- After installing it you can unmount cust and persist from the mount menu.
6- After it flash the official Lineage OS rom which you had downloaded. (Install menu, zip)
7- After rom is flashed, flash Gapps package. (Install menu, zip)
8- After flashing Gapps, go to wipe and wipe cache, dalvik cache.
9- Reboot your device
10-Enjoy!
First Reboot will take a while so don't panic... Download Google camera if you want a more stable camera (since stock is quite buggy).. Also you can use Umang's Flashlight fix for the buggy Flashlight button.
Just in case you want to root the device, just download root add-on (found in official thread)
Enjoy the experience..
Click to expand...
Click to collapse
it this a joke? this looks like a chinese copy of a guide posted 1 week ago and is only 2 posts under this:
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
what is your intention?

@massan1 I hope you have eyes through which you can read properly. No offence brother. Well, I didn't copy it. Plus that guide is made for those who have locked bootloader. Second, I am posting this for those who want to clean install Lineage OS with the call audio fix. So, if you believe I have copied it , just keep believing it.
Keep burning.. I'll get ice packs for you. Thanks.

I was on cm 13 before flashing lineage OS 14.1..Now the issue iam facing is that while making calls without headphones the both myself and other person won't hear a thing. On reverting back to cm 13 everything works fine. Currently on nightly 07.02.2107

r28 said:
I was on cm 13 before flashing lineage OS 14.1..Now the issue iam facing is that while making calls without headphones the both myself and other person won't hear a thing. On reverting back to cm 13 everything works fine. Currently on nightly 07.02.2107
Click to expand...
Click to collapse
just flash upgraded firmware or change build.prop:
https://forum.xda-developers.com/re...stall-lineage-os-locked-t3546154/post70826457
Raaj52 said:
This is not a build.prop issue!! In order to work with the old firmware (patched one) you have to make fluence to none, this is done when you use patched VoLTE. If you make fluence to none the latest MM firmwares won't give sound in call, many are getting no sound because they are using the old patched firmware. Since the native VoLTE is fixed no need of the old firmware and you don't need to change fluence to none. Just flash the latest firmware and you are good to go.
Still doubt? OK then I need to tell you one more thing, The first patch for VoLTE for MIUI MM was made by me (you can check that in MIUI Global forum) and sudeep made a firmware.zip with my NON-HLOS.bin and I can see that the same is copied in the firmware.zip, in order to get fluence working in the patched firmware it should have used with the correct adspso.bin.
Many are thinking that changing firmware is useless but in reality it comes with lot of stability fixes, so I recommend everyone to update your firmware to the latest one instead of all this build.prop editing craps.
What is the problem if I edit build.prop? --> You have to edit your build.prop whenever you flash a ROM, you can't avoid it unless you flash the latest firmware.
Why I am so confident? --> Because I know what is firmware and How does it work!
If you have "no sound in calls" issue even after you change the firmware I recommend a clean mi flash tool flashing with the latest MIUI ROM (because it will fix all your partition related stuffs, instability issues)
@abhishek987 @akhilnarang could you please add the "solution for no sound in calls is to flash the latest firmware" in your first post?
Click to expand...
Click to collapse

[EXPLAINED] z2_plus | /factory to /vendor | revert to /factory - TREBLE

A GUIDE TO FLASH LATEST TREBLE ROMS, OLDER TREBLE ROMS OR NON-TREBLE ROMS ROMS
UPDATE: A guide to rename our /factory partition as /vendor so that you can flash OLDER Android Oreo treble builds! We do not need this guide on Android Pie custom ROMs or for Stock ZUI WE ONLY NEED THIS FOR ANDROID OREO TREBLE BUILDS REQUIRING /factory renamed as /vendor
for Lenovo Zuk Z2 Plus
Latest Treble : /factory renamed i.e switched to /vendor
Older Treble:/factory mounted as /vendor
Non-Treble: Nothing to do with Vendor, Factory stuff lol
INTRO
As you all know that we now have TREBLE, and Zuk-devs are working hard to improve it further so that when the time comes we can move to GSI builds of future Android versions.
Recently, Zuk-devs have renamed the /factory partition into /vendor partition previously we were mounting /factory as /vendor but now it has been converted(renamed) to /vendor partition with this you'll be able to use a Proper Magisk zip, and you don't need a modded/edited Magisk, etc and lotta other kinds of stuff that we will discuss and come to know in the future.
rootdir: fstab: Use the right label for our vendor partition.
TUTORIAL:
What you want to do:
** Flash OLD TREBLE ROMS /factory is renamed to /vendor - NOTE NOT NEEDED FOR NEWER ROMS! **
Instructions:
* Flash "Factory2Vendor_plus.zip",
*Flash below linkedTWRP,
*Reboot To TWRP,
*Flash ROM,
+ GApps / + Magisk etc
* Reboot.
*Enjoy :fingers-crossed:
Downloads:
Factory2Vendor_plus: https://androidfilehost.com/?fid=962187416754475515
treble-TWRP 3.2.2 v2: https://www.androidfilehost.com/?fid=5862345805528044154
** REVERTING BACK to NORMAL aka renaming /vendor back to/factory **
Instructions:
*Flash "Vendor 2Factory_plus.zip",
*Flash LATEST OFFICIAL TWRP,
*Reboot TWRP,
*Flash ROM,
(+ GApps)
*Reboot.
*Enjoy :fingers-crossed:
Downloads:
Vendor2Factory_plus: https://androidfilehost.com/?fid=962187416754475514
https://twrp.me/zuk/zukz2.html
3. Flashing a Non-Treble RoM which has nothing to do with /factory /vendor partition etc.
Instructions:
*Coming from the above procedure, no need to do anything! the new OFFICIAL TWRP will work for Non Treble roms as well and No patches need to be flashed*
*Flash ROM,
+ GApps / + Magisk etc
*Reboot.
*Enjoy :fingers-crossed:
Notes:
This 'New TWRP' will work for both Latest Treble and Non-Treble ROMs
For ZUI also no need to flash any patch, New TWRP shall work (Needs to be tested)
You can flash Non-Treble ROMs and Nougat Builds or other builds with the new TWRP and no patches need to be flashed
Once you flash "factory2vendor" or "vendor2factory" you do not need to flash again unless mentioned in the build
or if you want to revert back to Old Treble ROMs where /factory was mounted as /vendor
CREDITS
Zuk-devs - Davidevinavil, DD3Boh and Cosmedd (https://github.com/zuk-devs)
@Fedor917 for giving the idea
And all others who have contributed in any manner! :highfive:​

Team win recovery project - 3.2.2 - treble [unofficial]
Treble supported TWRP 3.2.2 ONLY FOR ROMS with /factory renamed as /vendor
CHANGELOGS:
V1-
Device Specific:-
- Persist option
- Download Mode (edl)
- Fixed Partition Size
- Update the kernel image to get the latest commits for ext4, f2fs etc (cosmedd)
- Default brightness to 40%
General:
- adb backup fixes
- OTA style update zips will now install automatically without prompting for decrypt
- minor tweaks to handling date/time on Qualcomm devices
- updates to some language translations
V2-
- Vendor Wiping option
- Persist Backup/Restore
- Splash backup/restore and now can be flashed via img
DOWNLOAD:
https://androidfilehost.com/?fid=5862345805528044154
Source Code:
Device: https://github.com/kubersharma001/twrp_device_zuk_z2_plus
Kernel : https://github.com/cosmedd/android_kernel_zuk_msm8996/tree/twrp[/url]
SPECIAL THANKS TO
Alvaro
DD3Boh
Cosmedd
DavideVinavil
Pavan & Starman for testing!
FOR ANYTHING ELSE OR NORMAL TREBLE BUILDS (aka just using /factory) or NON TREBLE BUILDS USE ONLY FROM:
https://forum.xda-developers.com/le...-official-teamwin-recovery-project-3-t3899166

Reserved

So we'll have an updated TWRP for this full treble now? Is it still backward compatible with non treble rom like the partial one?

pipyakas said:
So we'll have an updated TWRP for this full treble now? Is it still backward compatible with non treble rom like the partial one?
Click to expand...
Click to collapse
New TWRP is for New Treble ROMs where /factory partition has been renamed to /vendor partition and It is for all the Non Treble Builds
Old TWRP is for Partial/Full Treble ROMs where /factory partition is mounted as /vendor partition

Thanks for the detailed instructions!
I was before on non treble builds and as instructed on AEX thread (Davide recommendation) I flashed Zuk stock ZUI rom (Oreo)
Than I flashed partial treble rom with new TWRP he instructed, and also future full treble roms.
Now I'm on latest 5.4
I once did revert to 5.2 but before that I wiped everything and installed old TWRP and made come back to 5.2
But as new build came out fast with fixes I flashed again TWRP with treble support and flashed 5.4 rom
My question is do I need to do any step here explained or not?
Everything working fine here, TWRP saw and flashed vendor partition.
Thanks for answer in advance

I couldn't understand completely
Im on latest AEX With developers twrp
Should i flash New Twrp first and then the factory package
Or its the opposite
And which factory zip should i flash
To be on the next AEX version

The steps mentioned above applies for the new builds that are going to come.

Now I'm on AEX 5.4 with the treble TWRP from #2...
So with the next build I should flash the Factory2Vendor.zip then a new (official?) TWRP img and then (after a recovery reboot) clean install the new build as usual? @kubersharma

frozenfirevr said:
Now I'm on AEX 5.4 with the treble TWRP from #2...
So with the next build I should flash the Factory2Vendor.zip then a new (official?) TWRP img and then (after a recovery reboot) clean install the new build as usual? @kubersharma
Click to expand...
Click to collapse
Yes

Does New Twrp (#1) can Be used for Non Treble ROMs.?

--------

Please clarify, which zip should be flashed first, vendor zip or twrp zip.

Moto-B said:
Please clarify, which zip should be flashed first, vendor zip or twrp zip.
Click to expand...
Click to collapse
+1

Moto-B said:
Please clarify, which zip should be flashed first, vendor zip or twrp zip.
Click to expand...
Click to collapse
First flash,factory2vender zip....
And then flash new twrp.img

I am on bootleggers ROM
Can anyone explain sequence of flashing the files??

Dhinesh1999 said:
Does New Twrp (#1) can Be used for Non Treble ROMs.?
Click to expand...
Click to collapse
Yes you may. Already mention by Kuber somewhere in the first page.
---------- Post added at 01:37 PM ---------- Previous post was at 01:29 PM ----------
vuckovic_stefan said:
Thanks for the detailed instructions!
I was before on non treble builds and as instructed on AEX thread (Davide recommendation) I flashed Zuk stock ZUI rom (Oreo)
Than I flashed partial treble rom with new TWRP he instructed, and also future full treble roms.
Now I'm on latest 5.4
I once did revert to 5.2 but before that I wiped everything and installed old TWRP and made come back to 5.2
But as new build came out fast with fixes I flashed again TWRP with treble support and flashed 5.4 rom
My question is do I need to do any step here explained or not?
Everything working fine here, TWRP saw and flashed vendor partition.
Thanks for answer in advance
Click to expand...
Click to collapse
I suggest you follow steps in part 1 again so that you can clean flash AEX 5.4 04/16 build.
Further can you advice best way to flash Oreo zui and revert back to latest AEX? I assume bootloader gets locked when you flash back to Oreo zui? Do advice.

Will flashing the mentioned zips on AEX 5.4 do any harm ? It's official one and treble TWRP only.

lokendra17 said:
First flash,factory2vender zip....
And then flash new twrp.img
Click to expand...
Click to collapse
Naveenjain said:
+1
Click to expand...
Click to collapse
need to do full wipe before flash rom?

ERHAN53 said:
need to do full wipe before flash rom?
Click to expand...
Click to collapse
No need to full wipe...you can dirty flash aex rom over 11/04 built
---------- Post added at 09:50 AM ---------- Previous post was at 09:44 AM ----------
ashwath230 said:
Will flashing the mentioned zips on AEX 5.4 do any harm ? It's official one and treble TWRP only.
Click to expand...
Click to collapse
No...it will not do any harm....it only rename /factory partition to /vendor partition..By factory2vendor.zip

How to update AOSP extended ROM

Hey everyone I recently installed aosp extended and saw in their website that a newer version was available when I checked a youtube video it said that I needed to flash gapps along with the update can someone help me on how to update the ROM is it same like pixelexperience where we just flash the file and clear cache alone?

#updateaex
1. Boot into TWRP
2. Flash AEX zip
3. Flash TWRP installer
4. Reboot to TWRP
5. Flash gapps
6. Flash magisk (optional)
7. Wipe dalvik cache
8. Reboot to system and enjoy
from telegram channel
But, what's your actual version of AEX ?

Sorry to but in...
I have a Mi9 with AOSP...
(please go easy..I'm a tad clueless)
If there is an update do I follow the instructions 21vm gave? And will I lose my apps and settings?

want to install lineageos 16 but dont know of a/b partitions

i'm a newbie in the A/B partitions system previously i have installed many roms on many Android phones but all of them are below android 6.0. now i moved to Mi A1 and i flashed TWRP and rooted my phone with Magisk18 now i have tried to flash lineageOS 16 on stock Pie but when i tried to flash it asks for slot_a or slot_b and i dont know anything about a/b partitions so i quit installation and write this thread pls help.

iamranjodh said:
i'm a newbie in the A/B partitions system previously i have installed many roms on many Android phones but all of them are below android 6.0. now i moved to Mi A1 and i flashed TWRP and rooted my phone with Magisk18 now i have tried to flash lineageOS 16 on stock Pie but when i tried to flash it asks for slot_a or slot_b and i dont know anything about a/b partitions so i quit installation and write this thread pls help.
Click to expand...
Click to collapse
there you go
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/

1. Flash or update to lastest stock rom
2. Boot twrp (don't flash TWRP, just boot) from:
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
3. Wipe to factory
4. Install LOS16
5. Reboot to bootloader and boot TWRP again
6. Flash gapps and magisk if you need it
That's what I did and works like a charm but I prefer RR.
Cheers!

ccalixtro said:
1. Flash or update to lastest stock rom
2. Boot twrp (don't flash TWRP, just boot) from:
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
3. Wipe to factory
4. Install LOS16
5. Reboot to bootloader and boot TWRP again
6. Flash gapps and magisk if you need it
That's what I did and works like a charm but I prefer RR.
Cheers!
Click to expand...
Click to collapse
This method is not working. We have to use a special bootable TWRP for LOS 16 Official builds.
Sent from my Mi A1 using XDA Labs
---------- Post added at 09:52 PM ---------- Previous post was at 09:33 PM ----------
iamranjodh said:
i'm a newbie in the A/B partitions system previously i have installed many roms on many Android phones but all of them are below android 6.0. now i moved to Mi A1 and i flashed TWRP and rooted my phone with Magisk18 now i have tried to flash lineageOS 16 on stock Pie but when i tried to flash it asks for slot_a or slot_b and i dont know anything about a/b partitions so i quit installation and write this thread pls help.
Click to expand...
Click to collapse
Try following these steps:
1. Download and boot this TWRP. Only boot it, don't flash it. https://drive.google.com/file/d/1LtLrNnL0h7alZaaOWADvc2Sf5aNkNukM/view
2. Wipe system, data, cache and dalvik. If you are encrypted, make a Format Data.
3. Go to Reboot and select other slot. (For example, if you are on Slot A, select Slot B)
4. Boot TWRP again.
5. Wipe system, data, cache and dalvik. Make a format data again.
6. Install latest LineageOS 16 Official nightly. You can select A or B.
7. Reboot to bootloader.
8. Boot TWRP again.
9. Flash GApps and Magisk (if you want root).
10. Reboot to system and enjoy Lineage!
Sent from my Mi A1 using XDA Labs

[ROM] [Q][10] Evolution-X 4.0 for Moto Z-Griffin[TREBLE]

Thanks to your feedback I have added some extra steps to ensure that everyone can enjoy the GSI ROM
First of all I am not the creator of this ROM-GSI I only share it in the XDA community and give all the credit to @turbolukex5
You can download and try all of his work from https://sourceforge.net/projects/expressluke-gsis/files You can see all the work of him in https://forum.xda-developers.com/project-treble/trebleenabled-device-discussion/gsi-expressluke-built-gsis-t4003457
Evolution X 4.0 has all the extra features of the AOSP ROMs plus extra features of Evolution X and all the sweetness of the Pixel. Tested by myself, like Lineage is stable for daily use without any problem of any kind (obviously we all know that moto-mods don't work, only the moto-mod battery in default mode) when used in Moto Z. Needless to say, as you read in the title this ROM is GSI so if you want to try it you need to have Official Lineage OS 16 installed in your Moto Z before attempting to install the GSI image.
So let's go to the installation steps:
Steps when you are already in another GSI
1. Download the GSI image from https://sourceforge.net/projects/expressluke-gsis/files/EvolutionX/Ten/ARM64/A/ EvolutionX_4.0_ARM64A-10.0-20200112-2146-GSI.img.xz
2. Unzip the file to extract the system image and copy it inside your Moto Z
3. Go to TWRP and wipe Data(not internal storage) /Cache/System
4. Go to Install and change to Install image
5. Select the image of Evolution X and flash as system partition
6. Flash Magisk Canary if you want root, gapps already included
6. Reboot to System
7. Wait fist boot and enjoy Evolution X 4.0
First Install/Clean install
1. Install Official Lineage OS 16
2. Boot to Lineage 16
3. Reboot TWRP
4. Wipe System, Data, Cache, Internal Storage
5. Reboot to recovery
6. Copy Evolution X 4 GSI image to Internal storage
7. Go Install IMAGE and select as System partition
8. Flash permissiver_v4
9. Reboot to System
10. Wait first boot and enjoy Evolution X 4.0
By far the best GSI I have tested for our Moto Z
Screenshots
https://imgur.com/a/vxLkVUj
Extra Tips:
Magisk Modules
LSpeed Magisk Module for extra battery life
Magisk Dolby ATMOS Q. Although the GSI already comes with very good audio
One more:
Arnova Gcam
Android OS version: 10.0
Security patch level: January 2020
GSI author: turbolukex5
Source code: https://github.com/Evolution-X
ROM Developer: joeyhuab
ROM Kernel: Linux 3.18
ROM Firmware Required: Official Lineage OS 16
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 4.0
Stable Release Date: 2020-01-12

mosfet321 said:
Evolution X 4.0
Status: Stable
Current Stable Version: 4.0
Stable Release Date: 2020-01-12
Click to expand...
Click to collapse
Hey, thanks for the great share! :good::fingers-crossed::highfive::laugh::silly:
1. 'By far the best GSI I have tested for our Moto Z' - have you already tested havoc 3 gsi?
2. please, change this in the description "no gapps already included" it's not clear if they are included or not. simply state 'gapps included'
3. how long should one wait for boot? - for me it's on boot animation min 15 already.
3.1 currently can't pass boot animation (-05 china version of Moto Z)
4. is latest official twrp OK for flashing this image?

dimdimdim said:
Hey, thanks for the great share! :good::fingers-crossed::highfive::laugh::silly:
1. 'By far the best GSI I have tested for our Moto Z' - have you already tested havoc 3 gsi?
2. please, change this in the description "no gapps already included" it's not clear if they are included or not. simply state 'gapps included'
3. how long should one wait for boot? - for me it's on boot animation min 15 already.
3.1 currently can't pass boot animation (-05 china version of Moto Z)
4. is latest official twrp OK for flashing this image?
Click to expand...
Click to collapse
Thank you for your advice, I tried Havoc but the battery life was not ideal for me but it is still a great option. You need to use twrp-3.3.1-0 but I'm not sure if the official version works in the CN version. Already installed does not take more than 3 minutes to boot. Try to erase Data and flash Magisk.

mosfet321 said:
Thank you for your advice, I tried Havoc but the battery life was not ideal for me but it is still a great option. You need to use twrp-3.3.1-0 but I'm not sure if the official version works in the CN version. Already installed does not take more than 3 minutes to boot. Try to erase Data and flash Magisk.
Click to expand...
Click to collapse
Yeah, official 331 works just fine.
The case is it's 2 sim phone and aosp on this phone even has no sim up.
What do you mean by erase data? - format or factory reset or wipe?
By the way, which partitions do you backup in twrp for successful full restore?

dimdimdim said:
Yeah, official 331 works just fine.
The case is it's 2 sim phone and aosp on this phone even has no sim up.
What do you mean by erase data? - format or factory reset or wipe?
By the way, which partitions do you backup in twrp for successful full restore?
Click to expand...
Click to collapse
I mean Wipe data partition where you have to write "yes" to wipe data. I had a similar problem when I started trying GSI everything was solved when I did a full wipe of System, Data, Cache then reboot to TWRP and install Lineage 16 afther that reboot to system and after full boot again TWRP and start to flash gsi, never had problems again when I want to try a GSI image I just do wipe cache and system and that's it
I do not make any backup I only make a backup copy of google that saves my contacts, photos, Wi-Fi networks, etc. and does not wipe data partition
Remember permissive and fixzygote are not needed for GSI builds made after 25th September

mosfet321 said:
I mean Wipe data partition where you have to write "yes" to wipe data. I had a similar problem when I started trying GSI everything was solved when I did a full wipe of System, Data, Cache then reboot to TWRP and install Lineage 16 afther that reboot to system and after full boot again TWRP and start to flash gsi, never had problems again when I want to try a GSI image I just do wipe cache and system and that's it
I do not make any backup I only make a backup copy of google that saves my contacts, photos, Wi-Fi networks, etc. and does not wipe data partition
Remember permissive and fixzygote are not needed for GSI builds made after 25th September
Click to expand...
Click to collapse
Will try... Later

I don't know what I'm doing wrong but I can't damn install it

piotriix said:
I don't know what I'm doing wrong but I can't damn install it
Click to expand...
Click to collapse
Give us more information to help you. What is the error that shows you or where are you stopped in the process?

There is no mistake.
The installation ends with the boot image evolution and nothing further happens.
I wait about 20 minutes
I even did a clean LineageOS installation and it did nothing.
---------- Post added at 10:23 AM ---------- Previous post was at 09:55 AM ----------
mosfet321 said:
2. Unzip the file to extract the system image and copy it inside your Moto Z
Click to expand...
Click to collapse
winrar ? 7z?

piotriix said:
There is no mistake.
The installation ends with the boot image evolution and nothing further happens.
I wait about 20 minutes
I even did a clean LineageOS installation and it did nothing.
---------- Post added at 10:23 AM ---------- Previous post was at 09:55 AM ----------
winrar ? 7z?
Click to expand...
Click to collapse
winrar work pretty ok
check the consequence above by author with format via "yes" - BE SURE TO BACKUP INTERNAL STORAGE BEFORE AS IT CLEANS IT OUT.
I have the same problem as you, only can get a life long boot animation. even though aosp 210 boots up (with no ril unfortunately).
but I have not tried to do it with yes-format yet. so, if you are up to it now, would be great to know if you succeeded.
which device do you own? mine is -05 chineese 2 sim

piotriix said:
There is no mistake.
The installation ends with the boot image evolution and nothing further happens.
I wait about 20 minutes
I even did a clean LineageOS installation and it did nothing.
---------- Post added at 10:23 AM ---------- Previous post was at 09:55 AM ----------
winrar ? 7z?
Click to expand...
Click to collapse
Into the TWRP, folow these steps:
1- Go Wipe - Format Data (DON'T BOOT the System Yet)
2- Go Reboot - Recovery
3- Now you flash the System img. Be patient and wait the process. It can take 3-5 minutes, maybe more. (DON'T BOOT the System Yet)
4- Go Reboot - Recovery
5- Now go Wipe - Format Data - Boot Rom

Moto 03 reatu
Blackigor said:
Into the TWRP, folow these steps:
1- Go Wipe - Format Data (DON'T BOOT the System Yet)
2- Go Reboot - Recovery
3- Now you flash the System img. Be patient and wait the process. It can take 3-5 minutes, maybe more. (DON'T BOOT the System Yet)
4- Go Reboot - Recovery
5- Now go Wipe - Format Data - Boot Rom
Click to expand...
Click to collapse
I did so too.
All in all, I did a few approaches with different configurations.

piotriix said:
Moto 03 reatu
I did so too.
All in all, I did a few approaches with different configurations.
Click to expand...
Click to collapse
0. Check the attached
1. Try to flash permissiver on it
2. Try to wipe data not from twrp, but from fastboot only
3. Flash can still be done via twrp
4. Please, post the result

i have flashed permissivier over the rom and it worked https://androidfilehost.com/?fid=6006931924117886495

No change.
It hangs on the start log

piotriix said:
No change.
It hangs on the start log
Click to expand...
Click to collapse
OKAY, THIS IS HOW I BOOT IT (EASY):
1. system, data, cache wipes
2. flash lineageos16
3. boot and pass first setup
4. boot to recovery
5. flash image
6. flash permissiver V5 - with v4 there is no ril
7. boot
boots fast, a couple of minutes.

dimdimdim said:
0. Check the attached
1. Try to flash permissiver on it
2. Try to wipe data not from twrp, but from fastboot only
3. Flash can still be done via twrp
4. Please, post the result
Click to expand...
Click to collapse
Excellent step, apparently if you have never installed a GSI ROM it is absolutely necessary to flash permitsiver_v4, I have added the step and works smoothly. :good: I realized that after trying JoyUI GSI from Vegazsd, (it works but with the bugs of the camera and gsm network :crying and when I returned to Evolution X it only worked after flashing permissiver_4
The guide is updated and ready for everyone to enjoy the GSI on their Griffin

I installed permissiver_4 before installing img. It is a pity that I did not know about v4 installation after and not before.
And all in all I still don't know if v4 is good or if you need to install v5.
I have a request if you donate something, try to follow the right order of installation because information chaos creeps in.
Thank you for the advice and best regards.
Today I will try again and if it goes wrong it fits
As I understand it is supposed to be pure lineageos16 without gaps and Google applications like that?
He asks now in detail not to err.
As I understand it is supposed to be pure lineageos16 without gaps and Google applications like that?
He asks now in detail not to err.
---------- Post added at 11:01 AM ---------- Previous post was at 10:31 AM ----------
I tried and it works
I installed permissiver_v5 and clean lineageos 16
Thank you once again

Blackigor said:
Into the TWRP, folow these steps:
1- Go Wipe - Format Data (DON'T BOOT the System Yet)
2- Go Reboot - Recovery
3- Now you flash the System img. Be patient and wait the process. It can take 3-5 minutes, maybe more. (DON'T BOOT the System Yet)
4- Go Reboot - Recovery
5- Now go Wipe - Format Data - Boot Rom
Click to expand...
Click to collapse
I recommend flash permissiver v5 as my ril was back only with it. V4 doesn't help
And I think you can skip data formats if you did it once.
I did only
normal wipes,
then lineagos flash
then boot it and first setup
then straightly flash img and permissiver v5
then it boots just ok and fast
Ah, yeah, and for me it's always best idea to reboot recovery after every operation. Because here and there I've seen it may fail to properly mount some partitions depending on the situation, which leads to errors while flashing

I have a request.
Which Magisk to install?
The link from the first post has disappeared.