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

Search This thread

SyberHexen

Senior Member
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
 
Last edited:

SyberHexen

Senior Member
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

 
Last edited:

Murderburger

Member
Jun 21, 2021
16
2
I am attempting this right now, So do we want the ROM to install Slot A or Slot B? I see you posted it installs to the opposite Slot
EDIT:
Had it on Slot A so it installed to Slot B and worked fine
Gapps has to be installed from https://wiki.lineageos.org/gapps.html the one you provided above does not work
For some reason on my MetroPCS phones Network its trying to connect directly to T-Mobile and not Metro by T-Mobile. Tried to Choose Network and nothing came up any ideas?
 
Last edited:

Skel40

Senior Member
Dec 27, 2019
336
171
Moto G 5G
@SyberHexen I may have the same exact XT2113-2 128 GB version of this phone as I just tried your recovery that has a working touchscreen. I was wondering which partitions should I backup?
 

SyberHexen

Senior Member
I am attempting this right now, So do we want the ROM to install Slot A or Slot B? I see you posted it installs to the opposite Slot
EDIT:
Had it on Slot A so it installed to Slot B and worked fine
Gapps has to be installed from https://wiki.lineageos.org/gapps.html the one you provided above does not work
For some reason on my MetroPCS phones Network its trying to connect directly to T-Mobile and not Metro by T-Mobile. Tried to Choose Network and nothing came up any ideas?
Use apn from your stock install or the metro website, or are options to edit apn greyed out?
 

Skel40

Senior Member
Dec 27, 2019
336
171
Moto G 5G
@AviBharti35 thanks!!! I was also curious where the system, data, vendor, and boot partitions are when backing up? I see super and all these partitions. I'm used to seeing system image, vendor image, data, and boot from different devices so I want to make sure I backup and restore the correct partitions just in case I want to restore the stock os in TWRP along with the stock recovery after flashing TWRP?
 

bobbyp1086

Senior Member
Awesome, one more, is rw a reality since it's lineage or is that not working? I hate reinstalling everything but hey booting up to twrp will let me back it up so plus 1 to amazing


Edit: looking over it a few questions, when fresh install, do we flash that one file if it's not updating firmware, going from stock rooted to lineage?

Would it be easier, since I know this route, to boot twrp - back up - flash twrp - wipe and format (should remove encrypted state) - then install lineage, gapps and then magisk? Or is that not a good way anymore?

Lastly, before I go and flash it, can you explain the different boot colors, red, orange and green? If they are what I think I could prolly help in getting the phone to orange or green, if it's anything like my old note 4
 
Last edited:

atsalchenberg

Member
Aug 1, 2014
39
10
Moto G 5G
Moto E (2020)
If I already flashed TWRP, do I need to reflash the stock recovery and then go about the steps or can I do the clean flash from the TWRP recovery? I just don't want to break my device, my phone's my only source of Internet.
 

fddm

Senior Member
Feb 24, 2011
260
172
Awesome, one more, is rw a reality since it's lineage or is that not working? I hate reinstalling everything but hey booting up to twrp will let me back it up so plus 1 to amazing
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.
Edit: looking over it a few questions, when fresh install, do we flash that one file if it's not updating firmware, going from stock rooted to lineage?
You only need to do an EFS backup and run Copy Partitions once when moving from Stock to Custom.
Would it be easier, since I know this route, to boot twrp - back up - flash twrp - wipe and format (should remove encrypted state) - then install lineage, gapps and then magisk? Or is that not a good way anymore?
Follow the OP, reboot before installing GApps and Magisk.
Lastly, before I go and flash it, can you explain the different boot colors, red, orange and green? If they are what I think I could prolly help in getting the phone to orange or green, if it's anything like my old note 4
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.

If I already flashed TWRP, do I need to reflash the stock recovery and then go about the steps or can I do the clean flash from the TWRP recovery? I just don't want to break my device, my phone's my only source of Internet.
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".
 

omgbathtub

Member
Apr 26, 2011
40
24
Any way to get rid of the red border that flashes when changing apps at times? Would love to run this but that annoyed the hell out of me and I had to return to stock.

Also, seemed to have an issue wherein the SIM card had random disconnects? I live in a low service area but I've never seen what was happening on this happen on stock. It would kick me out of the SIM settings menu, drop connection, then come back a second later with a data connection. XT2113-2 factory unlocked.
 

jhjhjhjhjhjh

Senior Member
Mar 14, 2017
388
181
Any way to get rid of the red border that flashes when changing apps at times? Would love to run this but that annoyed the hell out of me and I had to return to stock.

Also, seemed to have an issue wherein the SIM card had random disconnects? I live in a low service area but I've never seen what was happening on this happen on stock. It would kick me out of the SIM settings menu, drop connection, then come back a second later with a data connection. XT2113-2 factory unlocked.
First off much thanks to the o.p for a custom rom. No complaints here.
I had to research Lineage os since i haven't used that particular rom since oreo 8.1.1.
Havoc ,AICP and RR have been my go to roms...
Anyways, To use gapps it was recommended to use MindThegapps..ill send a link.
Ill tell ya this rom is tricky but good after proper installation. I saw the red rings of death too but after i re-flashed and put the rom on slot_a and flashed the Recommended gapps , no more Red Ring or nothing...

My problem was flashing gapps..Lineage only accepts gapps when flashed before first boot up. Also lineage flashes its own recovery and i couldn't boot to twrp or flash it.. Luckily, the lineage recovery has signature verification off so i was able to flash the gapps in Lineage recovery..

Hope this helps...

My install process requires an ext sd card and a cpu running windows 10..
Have copy of partitions zip lineage rom plus mindthegapps11 zip and optional magisk 23 zip on external sd card..
1. Flash stock firmware... mirror lolinet....moto kiev.. via fastboot..
2.Once new stock rom installed boot to welcome screen.
3.Now power off phone hold volume down have usb cord plugged in the phone then plug into cpu ..now ur in boot loader mode...
4.adb command fastboot boot recovery.img
in twrp now navigate to reboot and select reboot to slot_b
5.now flash copy partitions zip and lineage rom

6.Now select reboot to bootloader
7.Use volume keys to navigate to recovery and use power button to select "Recovery".
Now ull be in lineage recovery
8.use volume keys to navigate to install update use power button to select.
9.i placed all my zips in my download folder. look for the mindthegapps zip in the folder u put it in and hit install anyways when it says signature not verified.
10.now use volume keys to navigate to reboot to "bootloader"...Not System yet...
11. now in bootloader ...adb command
fastboot -w
now reboot system and profit...
 

Attachments

  • MindTheGapps-11.0.0-arm-20210412_124103.zip
    176.3 MB · Views: 55
  • MindTheGapps-11.0.0-arm64-20210412_124247.zip
    185.5 MB · Views: 191
Last edited:
  • Like
Reactions: Thanatos355

jhjhjhjhjhjh

Senior Member
Mar 14, 2017
388
181
Anyone who still plays ps3 and uses tether to connect ...this app "PS3 Proxy" is a life savor.. i only play socom confrontation since the servers was hacked and back online..

Also when tethering this app lets me know if im on a vpn or local host...local host 192.0.0.2 for some reason has no connectivity. but when its on lets say an address other than the local host then all devices have great tethered internet. just a jewel i found if any might wanna know.


P.S i can only tether h+ and lte only..
5G stays on local host 192.....xx.
The guy who made the boot img to override and modify the apn was only for stock..
if your reading this can you port the modified boot.img to lineage os 11..much thanks...
 
Last edited:
  • Like
Reactions: Thanatos355

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I tried your recommendation and it yielded weird results. I couldn't change the USB connection type from anything but the default "USB controlled by 'This Device'" and "Use USB for 'File Transfer'". For "Use USB for..." if I select "USB tethering", "MIDI", "PTP", "or "No data transfer", the screen "crashes" and then comes back with "File Transfer" selected. For "USB controlled by..." if I select "Connected device" it doesn't crash the "USB" settings screen and instead fails with error "Couldn't switch" and reselects the "This device" for "USB controlled by..."

    I think you're onto something with weird USB permissions in the LOS builds for Moto One 5G Ace (kiev). I think I may need to actually submit a bug report and this isn't user error on my part.

    I tried grabbing a logcat on both a working OEM TMO ROM where AA worked on my car and a logcat when using LOS 18 (same Android 11 as the OEM TMO ROM) and am going through them to look for PII before I submit a bug report to LOS. I'm not a programmer so it's a lot of log files to go through for me.
    1
    I think you're onto something with weird USB permissions in the LOS builds for Moto One 5G Ace (kiev). I think I may need to actually submit a bug report and this isn't user error on my part.
    I had a thought about permissions and found this.

    If you can pull the android auto (AA) granted permissions from kiev running stock (after validating that AA is working on stock), i.e. via adb:
    Code:
    adb shell dumpsys package com.google.android.projection.gearhead
    then you could compare that to the AA granted permissions on your lineageos 18.1 build to see if they are different. While your at it, do the same for the google assistant app (I think the package name is com.google.android.googlequicksearchbox) as the failure might be lack of permissions with that app.

    You also might want to grab permissions for these apps (from stock) with and with out the external sdcard inserted.

    I'd be looking for a granted permission related to the external sdcard from a working AA stock permissions just because I've experienced strange behavior related to external sdcards in the past (Google apparently does not support external sdcards well). Also I think the reports of AA working on devices running lineageos 18.1 do not have external sdcard capability. Perhaps someone else can confirm or contradict that.

    At a minimum, comparing permissions might help eliminate a lack of permission(s) as a cause.
    1
    I've also been unable to get AA working on my phone. I have an aftermarket head unit running Android, with an AA adapter, but it keeps telling me to connect my phone, and the AA notification on my phone keeps popping in and out. So, doesn't really help you, but at least this doesn't appear to be an issue with your phone specifically.

    I'm still running 18.1, I haven't had the time to update to 19 yet. I've also debated installing Havok and seeing if it works on that, but also haven't had time.
    1
    Trying Havok is a good idea. I think Havok (based on android 11) comes with gapps/AA already installed. I'd actually be surprised if it did not work there.

    A kiev user also asked on the lineageos redit about AA. WRT lineageos 19, AA is not supported as google apparently migrated the AA function into the google assistant app. I don't have a need for AA, do not want google assistant, and can't easily test, so I'm not going to be much help. Good luck.
    Regarding AA in 12, they didn't remove the AA function overall, it should still work in cars as it did before. The change in 12 is that you can no longer run the AA interface on your phone, that interface is now built into Google Assistant.

    I saw one comment about going into Settings -> Privacy -> Trust, apparently there was a bug that didn't set a permission for connecting USB devices until that page was viewed, it has supposedly recently been patched. I've done that and will give mine a try tomorrow to see if it fixes it. There are a couple spots that also reference giving something the Phone permissions, but Im not finding concrete steps on what needs that permission or how to do it.
    1
    OK, tried the Privacy -> Trust this morning, still not working.
  • 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.