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

[notmyrealhandle]

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:

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.

 

[mathew2214]

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?

 

[SyberHexen]

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]

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.

 

[RETIEF]

The kiev cannot be bootloader unlocked to my understanding.

 

[SyberHexen]

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]

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?

 

[bluesy_92]

Is there anything I need to update to go to Havoc 5.7? Vendors, radios, anything like that?

 

[fddm]

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?

You can just flash the new firmware.

Is there anything I need to update to go to Havoc 5.7? Vendors, radios, anything like that?

None that you really need to, afaik. Still good to keep your radio up-to-date.

 

[notmyrealhandle]

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.

 

[smartasiankid]

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?

 

[notmyrealhandle]

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?

 

[smartasiankid]

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.

 

[notmyrealhandle]

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]

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.

 

[smartasiankid]

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

 

[J_Woo]

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.

 

[notmyrealhandle]

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

 

[AviBharti35]

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?

It might be there just did not catch my eye. Glad it was resolved with the app update.

 

[J_Woo]

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?