[ROM]-[11.0]-[KIEV]-LineageOS-18.1-[UNOFFICIAL]

Search This thread
Sep 18, 2019
32
5
There is also this proposed commit in gerrit: sm7250-common: Add gaurd to ipa based on bootloader build version..

Will users run into issues if the latest retus version (android 11) is flashed and then lineageos is installed (without the guard to ipa commit)?


nvmd - this looks specific to racer - my bad.

EDIT: FWIW I unlocked the bootloader (coming from lineageos), flashed:
Code:
XT2113-2_KIEV_RETUS_11_RZK31.Q3-45-16_subsidy-DEFAULT_regulatory-DEFAULT_R8_CFC.xml.zip
and then booted into the retus android 11. This obviously wipes data. Boots fine, I didn't spend much time on it tho.

One concerning observation, the allow OEM unlock in developer options was grayed out and toggled to the "deny" position even tho the the text below it said the bootloader was unlocked. Note this option was in the green "allow" position before flashing the android 11 stock image. I am still able to use `fastboot flashing lock` despite this (more below).

Building a new "user" version of lineageos with the June security patches plus DIY patches that allow the bootloader to be relocked and enabling FM radio audio went without issue. Note that I updated the rollback index to 13 from 12 based on the stock android 11 image above.

After flashing copy-partitions, flashing the new lineageos image with the bootloader unlocked and booting into lineageos all went without issue. Allow OEM unlock is still grayed out, in the deny position, and indicating the bootloader is unlocked. Reboot to bootloader, lock the bootloader (wiping data again), and then rebooting into lineage went without issue. At this point, the allow OEM unlock is still in the deny position but at least I can (and did) toggle it to allow.

Seedvault restored apps and all the settings it can - this is still not the greatest backup option but it does save me some effort.

So far no issues running this way.
 
Last edited:

mathew2214

Member
Mar 31, 2019
29
6
is this compatible with the XT2213-3 (Austin)? i diddnt see it in the supported models list. this is the thread for the Motorola Moto G 5G right?
 
Last edited:

SyberHexen

Senior Member
is this compatible with the XT2213-3 (Austin)? i diddnt see it in the supported models list. this is the thread for the Motorola Moto 5 5G right?
No this fourm is for the Kiev

Moto g 5g (2022) aka 'Austin' will have its own forum. But probably too new to have a home on xda yet..

On another note I would be surprised to see roms on that device as it has a mediatek processor.

Good luck!
 

zigxda

New member
Apr 15, 2021
2
0
I have a Motorola One 5G Ace (non-UW) XT2113-2 "kiev" and a Motorola One 5G Ace UW XT2113-1 "kievv" both on Verizon.

The kiev is fully unlocked and working well on LineageOS 18.1-20220702-NIGHTLY-kiev.

The kievv, however, is apparently subsidy locked to Verizon and entering the necessary codes causes the Motorola web site to report that unlocking the bootloader is blocked. I bought the kievv outright and I assume eventually it will be possible to unlock the bootloader, but at that point will the kiev image work on the kievv also?

As I understand it, the only difference is that the kievv adds support for mmWave (n260/ n261) bands.
 

SyberHexen

Senior Member
I have a Motorola One 5G Ace (non-UW) XT2113-2 "kiev" and a Motorola One 5G Ace UW XT2113-1 "kievv" both on Verizon.

The kiev is fully unlocked and working well on LineageOS 18.1-20220702-NIGHTLY-kiev.

The kievv, however, is apparently subsidy locked to Verizon and entering the necessary codes causes the Motorola web site to report that unlocking the bootloader is blocked. I bought the kievv outright and I assume eventually it will be possible to unlock the bootloader, but at that point will the kiev image work on the kievv also?

As I understand it, the only difference is that the kievv adds support for mmWave (n260/ n261) bands.
Unfortunately Kievv can't be bootloader unlocked. Also if it was its got a different partition structure so the rom would not work anyways =/
 

smartasiankid

Senior Member
May 26, 2019
130
7
Can't say for sure, I want to build a custom kernel before moving to this myself (and I never touch the system partition anyway), but it should be formatted for R/W.

You only need to do an EFS backup and run Copy Partitions once when moving from Stock to Custom.

Follow the OP, reboot before installing GApps and Magisk.

Android Verified Boot state can never be changed on custom firmware without an exploit early in the boot chain or getting private signing keys. It does not matter, Magisk hides this so it has no effect. You can still pass safetynet as long as hardware attestation is not enforced. Your Note 4 does not have AVB.


No, you can flash over it without effecting anything else. The OP never says to flash recovery and it's optional anyway. Just boot into bootloader mode and send it over with "fastboot boot twrp.img".
Do i need to flash stock rom every time i move to a different custom rom or can i just go straight to a different rom wo flashing stock first?
 

fddm

Senior Member
Feb 24, 2011
256
171
Sep 18, 2019
32
5
Unlocked and flashed the 2022-06-30 RETUS update. Booted into stock to provision the radios and check on visual voicemail (more about that below). I noticed the same behavior as before wrt the oem unlocking, otherwise didn't stay here long.

Then flashed a DIY unofficial build (updating the rollback index to 14 from 13). Booted fine so i went ahead and re-locked the bootloader. No issues - I was able to toggle the oem locking to allow (after locking the bootloader) as before.

Restored a backup via seedvault and went through a couple of hours of additional tweeks that seedvault misses (some of which I don't expect seedvault should backup like firefox, nextcloud, davx accounts, k9 email passwords, etc).

The FM radio is back! No need for me to apply hackish patches - thank you for that.

The (new to lineageos) moto camera seems to work well. Hedgecam2 filled a need, but I think I'll switch to the lineageos provided moto camera. Thank you for that.

I have visual voice mail without having to use my carriers bloatware app! For the longest time (years), I could not get visual voicemail working and so just lived without it. I'm not sure what brought it back. Some bug fixed in the updated stock rom radios? Bugs fixed in the updated blobs? As mentioned above, I did use visual voice mail on the stock rom with the thought that maybe something needs to be provisioned for it after updating the radio. Any event, it's nice to have the option to use it.

Very pleased atm. My thanks to those that made this possible.
 
Last edited:

smartasiankid

Senior Member
May 26, 2019
130
7
Unlocked and flashed the 2022-06-30 RETUS update. Booted into stock to provision the radios and check on visual voicemail (more about that below). I noticed the same behavior as before wrt the oem unlocking, otherwise didn't stay here long.

Then flashed a DIY unofficial build (updating the rollback index to 14 from 13). Booted fine so i went ahead and re-locked the bootloader. No issues - I was able to toggle the oem locking to allow (after locking the bootloader) as before.

Restored a backup via seedvault and went through a couple of hours of additional tweeks that seedvault misses (some of which I don't expect seedvault should backup like firefox, nextcloud, davx accounts, k9 email passwords, etc).

The FM radio is back! No need for me to apply hackish patches - thank you for that.

The (new to lineageos) moto camera seems to work well. Hedgecam2 filled a need, but I think I'll switch to the lineageos provided moto camera. Thank you for that.

I have visual voice mail without having to use my carriers bloatware app! For the longest time (years), I could not get visual voicemail working and so just lived without it. I'm not sure what brought it back. Some bug fixed in the updated stock rom radios? Bugs fixed in the updated blobs? As mentioned above, I did use visual voice mail on the stock rom with the thought that maybe something needs to be provisioned for it after updating the radio. Any event, it's nice to have the option to use it.

Very pleased atm. My thanks to those that made this possible.
Instagram opening animation on lineageos is choppy on both 18.1 and 19.1, though shakeuptech said it was not. Can you comment on that?
 
Sep 18, 2019
32
5
Instagram opening animation on lineageos is choppy on both 18.1 and 19.1, though shakeuptech said it was not. Can you comment on that?
Sorry, I don't use instagram. I do turn off blur (but just because I don't like it).

BTW wifi calling is working for me but I have not used it in the past. I'm not sure if you might need to "provision" that as well while on stock before installing lineageos tho. I did test it out on stock before my most recent lineageos update. I wonder if that is part of the reason I've got visual voicemail now.

@SyberHexen

Regarding using stock to provision kiev's radios, is it necessary to do this when roaming between carriers? (i.e. if i provision on TMobile, but then travel to an area serviced by ATT only (in this case I think TMobile customers use ATT's network as "roaming") will I lose service? What about changing sims to verizon (RETUS should work with verizon if I'm not mistaken) or traveling to Europe, Asia, etc? Will I need to reload stock to provision each time I change networks/sims?
 
Last edited:

smartasiankid

Senior Member
May 26, 2019
130
7
Oh but the thing is the retus version for me doesn't have WiFi calling (I'm on at&t) but if i flash the Canadian firmware WiFi calling works fine on stock.
 
Last edited:
  • Like
Reactions: RETIEF
Sep 18, 2019
32
5
the retus version for me doesn't have WiFi calling (I'm on at&t)
Out of curiosity, have your tried flashing the most recent (6/30/2022) RETUS stock to upgrade the radios? Also, I believe the lineageos binary blobs are were updated from this RETUS version.

I have little experience and even less knowledge wrt "provisioning", wifi calling, when to update radios, and binary blobs (hence why I keep editing my prior post).
 

smartasiankid

Senior Member
May 26, 2019
130
7
Out of curiosity, have your tried flashing the most recent (6/30/2022) RETUS stock to upgrade the radios? Also, I believe the lineageos binary blobs are were updated from this RETUS version.

I have little experience and even less knowledge wrt "provisioning", wifi calling, when to update radios, and binary blobs (hence why I keep editing my prior post).
No I have not. Will probably try it when a new build for lineageos is out.
 
  • Like
Reactions: notmyrealhandle

smartasiankid

Senior Member
May 26, 2019
130
7


See just how laggy that animation is? It is definitely broken. And settings also has that issue sometimes when opening the app.
 

J_Woo

Member
Apr 5, 2008
24
12
Unlocked and flashed the 2022-06-30 RETUS update. Booted into stock to provision the radios and check on visual voicemail (more about that below). I noticed the same behavior as before wrt the oem unlocking, otherwise didn't stay here long.

Then flashed a DIY unofficial build (updating the rollback index to 14 from 13). Booted fine so i went ahead and re-locked the bootloader. No issues - I was able to toggle the oem locking to allow (after locking the bootloader) as before.

Restored a backup via seedvault and went through a couple of hours of additional tweeks that seedvault misses (some of which I don't expect seedvault should backup like firefox, nextcloud, davx accounts, k9 email passwords, etc).

The FM radio is back! No need for me to apply hackish patches - thank you for that.

The (new to lineageos) moto camera seems to work well. Hedgecam2 filled a need, but I think I'll switch to the lineageos provided moto camera. Thank you for that.

I have visual voice mail without having to use my carriers bloatware app! For the longest time (years), I could not get visual voicemail working and so just lived without it. I'm not sure what brought it back. Some bug fixed in the updated stock rom radios? Bugs fixed in the updated blobs? As mentioned above, I did use visual voice mail on the stock rom with the thought that maybe something needs to be provisioned for it after updating the radio. Any event, it's nice to have the option to use it.

Very pleased atm. My thanks to those that made this possible.
@notmyrealhandle which LineageOS version are you using with the Moto camera in it? Online, Lineage OS latest official build for Kiev is still 18.1 from July 16. Lineage OS 19..1 build (unofficial) is from June 29 and does not have the Moto camera if I remember correctly from when I tried it.
 
Sep 18, 2019
32
5
which LineageOS version are you using with the Moto camera in it?
I do my own builds of lineageos 18.1. The build I'm currently using is from 07/14/2022 and has com.motorolla.camera3 v 8.0.77.76. I did not add this my self, I believe this is the new default camera from inspecting this commit (and others associated with it).

I expect this is included in official builds starting with lineage-18.1-20220709-nightly-kiev-signed.zip
 

J_Woo

Member
Apr 5, 2008
24
12
I do my own builds of lineageos 18.1. The build I'm currently using is from 07/14/2022 and has com.motorolla.camera3 v 8.0.77.76. I did not add this my self, I believe this is the new default camera from inspecting this commit (and others associated with it).

I expect this is included in official builds starting with lineage-18.1-20220709-nightly-kiev-signed.zip
Cool. Last question. Getting GAPPS to load nicely with Lineage OS seems to be finicky. Which GAPPS are you using?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Oh but the thing is the retus version for me doesn't have WiFi calling (I'm on at&t) but if i flash the Canadian firmware WiFi calling works fine on stock.
    1
    Out of curiosity, have your tried flashing the most recent (6/30/2022) RETUS stock to upgrade the radios? Also, I believe the lineageos binary blobs are were updated from this RETUS version.

    I have little experience and even less knowledge wrt "provisioning", wifi calling, when to update radios, and binary blobs (hence why I keep editing my prior post).
    No I have not. Will probably try it when a new build for lineageos is out.
    1
    Which GAPPS are you using?
    I have been gapps free for more than 5 years. I just recently started playing with microg, but this is simply personal interest - I currently have no use for it.
    1
    MicroG does not have the Google Play Store. So how does one accommodate the many apps we use, such as banking or shopping apps?
    Use Google Play, an alternative gplay client like Aurora Store, or an alternative app market. The Google Play Store works well with MicroG.
  • 13
    2okPze5.png

    Motorola G 5G / Motorola One G 5G Ace
    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */
    Introduction:
    This is the Unofficial Lineage OS 18.1 thread for the Motorola G 5G, codename kiev.​
    Join our Motorola G 5g / Motorola One 5G Ace Development Telegram Group!​

    LINKS:
    Recovery: Unofficial TWRP
    Magisk: Magisk
    Factory Firmware: Stock Firmware Mirror
    "Copy Partitions Zip" - courtesy of @filipepferraz
    (To setup "Slot B")

    How to Install:
    01. Download the ROM, Firmware and GApps from the links above.
    02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
    03. Create backup. i.e. EFS / Persist and put somewhere safe.
    ## YOU ONLY NEED THIS STEP ONCE.. When updating Firmwares ##
    04.At this point Flash "Copy Partitions Zip" In TWRP "SLOT A"
    05. Flash the ROM
    06. Choose Reboot -> Bootloader
    07. boot twrp again "fastboot boot twrp.img"
    08. Install GApps & Magisk.
    09. Reboot -> Bootloader
    10. fastboot -w
    11. Click Start and Enjoy.

    NOTES:
    *Note-1: Slots, ROMS install to opposite (inactive) slot
    If you FLASHED ROM from "Slot A", then ROM is installed to "Slot B", If you Flashed ROM from "Slot B", then ROM is installed to "Slot A"
    *Note-2: Updating "Dirty Flash"
    01. Boot TWRP
    02. Flash ROM
    03. Reboot -> Bootloader
    04. Boot TWRP
    05. Install Gapps + Magisk
    06. Reboot -> System
    *Note-3: Updating "Dirty Flash"
    Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine with SafetyNet patcher modules, though is not supported.)​

    XDA:DevDB Information
    kiev-lineageos, ROM for the Motorole G 5G

    Contributors

    erfanoabdi, SyberHexen, Jleeblanch
    Source Code: https://github.com/SyberHexen

    ROM OS Version: Android 11
    ROM Kernel: Linux 4.19
    Based On: LineageOS

    Version Information
    Status:
    Stable

    Created 2021-07-05
    Last Updated 2021-07-22
    6
    I made this tutorial to help in flashing.
    3
    Changelogs:

    09/19/2021
    Device changelog:

    - Fixed Regression with DRM Apps
    3
    Past Changelogs:


    09/16/2021
    Device changelog:

    - Fixed Incoming call audio bug
    - Updated Brightness overlays
    - Updated Kernel Device Trees
    - Misc Improvements
    09/09/2021
    Device changelog:

    - Enforcing Selinux
    - Fixed Off-mode Charging
    - Switched to Racer Off-mode animation
    - Fixed Setting device model between Ace/5g variants
    - Fixed Media studder
    08/12/2021
    Device changelog:

    - carrierconfig: update from kievv tag 'RRV31.Q2-36-14-8'
    - carrierconfig: update from CAF tag 'LA.UM.9.12.r1-10800-SMxx50.0'
    - update defconfig from kievv tag 'RRV31.Q2-36-14-8'
    - Show Turbo Charging instead of charging rapidly
    - enable support for freeform windows and picture-in-picture
    - upgrade bootctrl hal to 1.1
    - increase audio for speaker(s) and microphone
    - Exfat driver included to kernel for LOS recovery support
    07/22/2021
    Device changelog:

    - Minor Fixes
    - Updated Brightness overlays

    07/05/2021
    Device changelog:

    - Minor Fixes
    - Switch to Pixel Power Hal

    07/01/2021
    Device changelog:

    - Initial Build

    3
    My Review After 1 Day:

    Running Android 11 - Lineage OS 18.1 Unofficial Nightly

    Just wanted to give you all my opinion. This is a very stable rom so far.. I just bought this phone today and had the bootloader unlocked, TWRP installed, this ROM with Gapps, and Magisk (both zip and apk).. all in about 2 hours. I have been ROMing for 10 years now and this was not that bad for someone with experience. I really didnt run into a problem. I have the stock firmware unbrick tool if I needed it. I did have to reflash my twrp after the initial rom install.. lineage has its own recovery which overwrites the twrp I wanted.. I just had to fastboot flash recovery to put the correct one on. Whats with this Slot A/B thing .. thats a strange concept that I need to select a Slot.. thats a new one. also the bootloader unlock code.. i have never had to enter an unlock code before for a bootloader but was easy to submit the request and my email came in 2 minutes.. this is a great rom with many more features than the stock firmware. I was able to switch the back and recents buttons to the older way with the back button on the right. I am testing GCam for a faster camera.. lineage stock camera has a little lag (after you press the button it takes a half second for the click sound and image preview to show). GCam is a little faster so far but I need to stress-test for stability.

    enjoy this rom.. its got my approval.

    EDIT: I attached my GCam config file. Everything is working.. all functions have been tested and no freezes or issues with instability. I will report back with issues.

    = GCam likes Google Photos app to load the images from within GCam.

    = I just snapped 50 pics one right after the other, non-stop, very fast beat.... there was lag but it was totally expected.. it did not freeze up and eventually caught up fine and would continue for a couple pics then lag again.. I would expect all this to happen and its stability was very good.

    Battery Drain is 2% over 5 hours sitting on my desk with screen off on standby. Battery Drain is a little more than I like while using apps. This needs some battery management but its not that bad.