yashsingh1/xdaforums huggingface dataset:
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] hellwhynot:
Tried 20220512, did another clean Spotify reinstall and still the same issue: empty library and no playback on the local device. Anybody who can confirm this, suggestions as how to fix? TIA!
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] :
Thank a lot for this ROM, works flawlessly for me.

Much obliged.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] abcxdaabc:
Don't have any personal experience with spotify, but it's seems like it's an ongoing issue.

Try removing the sd card/unmount your sd card and restarting, then reinstall spotify.

See:

[Android] Unable to play music, all playlists appear empty

We've received reports from Android users that they're unable to play songs from Search. In addition, all playlists in the app appear empty. This is currently being investigated.

community.spotify.com
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] hellwhynot:
Tried 20220512, did another clean Spotify reinstall and still the same issue: empty library and no playback on the local device. Anybody who can confirm this, suggestions as how to fix? TIA!

I already found a lot of threads about the issue but had not noticed this one. Thanks!

As for the proposed 'solution' in these threads, removing the sd card is not an option for me. I really need the extra space! I guess for now I'll just wait and see.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] abcxdaabc:
Try it and then put it back in after reinstalling?

Nevermind.

Is the card internal storage or portable?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] hellwhynot:
It's portable and I like to keep it that way. Let's say using an external sd card for 'internal storage' did not always work for me... Thanks again though for pointing this out! I have posted in the thread you mentioned before, and hopefully it helps Spotify sorting out this issue.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] birdsilver:
No puedo instalar magisk en el último boot.img
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] mksu9:
Can I flash this ROM with old TWRP 3.2.0-0 and lineage-15.0-20171125_073252-UNOFFICIAL-cedric .
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
Use latest official twrp to avoid issues and backup everything

You need to be on latest retail stock firmware or at least flash the latest modem part of the firmware (doesn't matter what custom rom you are using and you don't need to actually flash stock rom - just need to have the latest modem as your base)

Format system data and cache before flashing a new rom
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] mksu9:
so install one of these through twrp maybe, https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/cedric/official/RETAIL/ but i don't know which one to get, OPP is latest. rest are OPPS?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
Stock firmware is flashed via fastboot not twrp

You just need to flash the modem parts or you can just flash the whole thing

Look at the date - you can see which is latest
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] mksu9:
I updated trwp, NON-HLOS.bin amd new rom. Everything seems to be working so far... Thanks
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] mksu9:
Microphone doesn't work in conversations.im audiocalls. Regular Audio recorder works normally. Conversations is allowed to use microphone "while in use" and mic icon in app window is turned on. Any ideas where to look?

Edit:

-tried reinstall app, clear data, reboot and no change

I also installed [ROM][I9190/I9192/I9195][Unofficial][11.0.0] LineageOS 18.1 for S4 Mini and microphone works normal way in conversations app.

Edit2:

I downgraded to LineageOS 14.1 temporarily and now the mic is working again.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] matiusuario:
I recommend you to install the TWRP flashable version of stock ROM before switching between a7/a8 ROMs to a9/a10/a11 and viceversa (Stock Nougat for a7/a8 and Oreo for a9+). So you don't loose fingerprint nor face microphone issues. It's easier and quicker than fastboot flashing individual parts of stock.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] mksu9:
I can't even remember what I flashed before first time I installed custom rom to this phone, because it was years ago, so I might have a frankensystem now. At least I know it's not a hardware issue since it's working now. I will try a whole stock image next.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] DefenderII:
I had a problem with syncing my google contacts. if anyone else does, here is what i did to make it work. I hope this helps others:

1: download gapps; I used Open Gapps

2: open the archive and extract:

googlecontactssync-all.tar.lz from the Core folder

calsync-all.tar.lz from the GApps folder (maybe the folder names and paths will change with other gapps? The archives names shouldn't though, so maybe you could search for the names and extract them)

3: extract the respective APKs. If you can't open ".tar.lz" archives because reasons, convert them or find a tool that will open them. I converted them to .zip archives with https://convertio.co/it/tar.lz-tar/ and win10 file explorer to extract them to the folder of your choice

4: put the the google calendar apk on your phone folder "download" (or any other folder, i used this one) and run it. => calendar syncs (it takes some time but it syncs!!!)

5: for the google contacts use de adb program on your pc and then via cmd (here you find how if you don't have adb)

open cmd platform-tool and type:

adb root

adb remount

adb shell

adb shell mkdir -p /system/app/GoogleContactsSyncAdapter

or if you are in the app folder:

mkdir -p GoogleContactsSyncAdapter

close the cmd window and open a new cmd platform-tool and type:

adb push "location of your apk file/GoogleContactsSyncAdapter.apk" "/system/app/GoogleContactsSyncAdapter"

check if the file was pushed:

adb root

adb remount

cd system

cd app

cd GoogleContactsSyncAdapter

ls (now you shoud see the apk file)

chmod 644 "/system/app/GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk"

ls -l to check the new rights (this should be rw-r-r)

adb reboot or simply reboot

this should be done after each update

Manage file permissions on Unix-like systems (iu.edu)
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] macGam:
Did someone tried a migration to Lineage OS 19 from 18.1. Is everything ok?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] mathew2214:
i am considering purchasing one of these phone for use with this ROM. i need to be able to use VoLTE with T-Mobile in the US. which exact model number is most ideal for this?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] mri0:
I have a fully updated device on stock ROM (Android 8.1).

Followed all the instructions (root, flash recovery). When trying to flash the latest build I get the following error on my device:

"This update requires firmware from an Adroid 8.1 based stock ROM build. Please upgrade firmware and retry! E:Error in /sideloads/package.zip (status 1)"

Any help? Thx.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] hellwhynot:
Might be related to the issue mentioned in page 9 of this thread.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] dzyndzla:
There isn't an official build of LOS19 for moto G5; I haven't even seen an unofficial one. So, I doubt anyone went through an update process for that device at all
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] mri0:
Thank you so much! This solved the problem.

@JarlPenguin Thank you so much for keeping this Room alive and up to date!

Another newbie question: What is the newest gcam which works best with this room and where to get it? Can I just download the 8.2 APK (latest which works with Android 11) and install it or is any specific adaptation for this phone needed?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] hellwhynot:
And sadly there probably won't be a LOS 19 build for cedric ever, see https://lineageos.org/Changelog-26/ (section Let’s talk about legacy devices…) It says there: "[...] for devices using kernel versions 3.18 and below, this may be the end of the road." Well, cedric is on 3.18...
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] dzyndzla:
Yeah, I've seen that as well; it would be great if @JarlPenguin could somehow comment on that one.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] JarlPenguin:
If we ever get sensors and in-call audio fixed on 4.9, then LineageOS 19 will officially be supported. Until then there will be no (un)official support.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] hellwhynot:
Good to know how things stand! Thank you for sharing this and the effort you put into maintaining LOS for cedric.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] ScubadooX:
It's running fine on my Moto G5. I had to install Oreo 8.1 first because it's a prerequisite to 18.1.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Horrible Username:
Out of curiousity…

I ended up abandoning L18 on my phone cause it was just too slow and laggy. Granted my phone is only the 2GB model, so I was wondering how do the 3GB G5's handle this?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] abcxdaabc:
Excellent for what i need it for, sits around 2,2GB standby with the apps im using.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] ScubadooX:
I have the Lenovo Moto G5 Dual-Sim (32GB + 2GB RAM) XT1671 and agree that 18.1 is laggy but so was Oreo 8.1. Can't remember what Nougat was like but I suspect it wasn't fast either.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] hellwhynot:
I have the 3 GB model and wouldn't call it laggy in my case. No difference between LOS 18.1 and Oreo / Nougat.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] ScubadooX:
After experimenting with LOS 17.1 and then a couple of releases of LOS 18.1, I finally reverted back to Oreo. LOS was definitely more laggy than Oreo and one app, the Indonesian COVID-19 app, wouldn't even run in LOS. But the real deal breaker was two catastrophic failures related to encryption that rendered the phone unbootable. Luckily in both cases I was able to reinstall Oreo using fastboot. Now having used Oreo for much of the morning, I realize just how laggy LOS was. Of course, running an unsupported version of Android is a security risk but I wonder how many people actually get hacked because of a security hole in an unsupported version of Android.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] KeithSJS:
Hello, I just installed Lineage 18.1 and it seems to be fully working. One query though: if I set the time by using network time then engage flight mode then turn the phone off then turn it on, the correct time is lost (it shows 03.00 or similar) and I have to make a network connection again to produce the correct time. I have searched the thread but can't see any reference to this problem. Any suggestions or workaround?

What I did see was an instruction (reply #80) that Oreo stock to flash this ROM. I did have (unofficial I think) Lineage 14.1 when I flashed 18.1. All I did was use the TWRP I had installed already (an older version than the one referenced in the instructions in post #1) to wipe / format everything on the phone and then flash the zip. Is this wrong, should I re-do it?

Any help much appreciated.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] hellwhynot:
I don't think this issue has anything to do with your installation method. I did that 'by the book' and my time is way off too when applying your scenario with flight mode on. A similar thing happens when booting into TWRP. I guess you just need network time to get time right with this ROM installed. (Which is not a big deal to me, though.)
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] KeithSJS:
Hey, Thanks for the reply. Yeah, I think this is maybe the way to go with this i.e. live with it; I just like that I can have my phone switched on in the morning and not have it 'connected' but still show the right time.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Geny boy:
got that error

this packge requires frimware from an android 8.1 based stock rom build please upgrade frimware and retry E:Error in /Sideload-package.zip (status 1)

and now restarting the device but it stuck on the ERROR Window "Window of unlocked device of motorella"
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] matiusuario:
Hi again.

Some other things adding to what I replied in the other thread:

1. You have to flash stock only when switching from a7/a8 to a9-or-later or from a9-or-later to a7/a8. Some issues might appear if you don't do so are fingerprint functionality lost, loudspeaker calls and I don't know what else.

2. Back up efs and persist with twrp 3.5.2 or later only once, not needed every time you flash a ROM. But remember where you save the back up. More-than-one place is recommended. e.g sd and pc.

3. Read the other thread.

4. As you aren't sure what your current firmware base is, I suggest you to upgrade twrp, then install twrp-flashable stock and the rom you want. (stock version depends on what rom you are willing to install).
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Ciantic:
I got 8.1 Android error as well, but fixed it by flashing CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip which is found in here:

https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/cedric/official/RETAIL/

You open the zip to your computer and painfully do the fastboot commands as instructed in this thread:

fastboot oem fb_mode_set

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot flash dsp adspso.bin

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk....

fastboot flash oem oem.img

fastboot erase cache

fastboot erase userdata

fastboot oem fb_mode_clear

fastboot reboot

After that LineageOS 18.1 installed fine.

As a word of caution some reported that SIM card does not work after that, given that I use with WIFI only I don't care.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] matiusuario:
Well... That's why I said to install the twrp-flashable stock, it's just one-tap and done, moreover it's safer because you won't screw it up by a wrong command nor loose your imei tinkering with software channels
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Ciantic:
I tried TWRP flash stock before doing that, it didn't remove the Android 8.1 error.

Specifically I tried this:

cedric-twrp-OPP28.85-13.zip

It flashed just fine, but didn't remove error.

So fastboot was required?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] matiusuario:
That's because version [...]85-13 is not the latest. You should install "cedric-twrp-OPPS28.85-19-4-2.zip" to avoid the "Upgrade firmware and retry" error
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] pawelluk:
Hello,

I have a moto G5 XT1671. I have booted into stock rom, and verified android 8.1. Have followed the procedure multiple times with flashing recovery, and then the latest lineageos rom through sideload.

So here is the issue. Every time I try the stock rom it boots into it no issues, and all works. Then when I flash the latest lineageos rom, it always just boots into recovery no matter what I do.

I have cleared dalvik, data, system, cache, and flashed lineageos again with no success.

Should add no errors while flashing.

Any feedback would be much appreciated.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] pawelluk:
Found out that I could only boot into ROM whether stock or lineageos by using this sequence BOOTLOADER->FACTORY MODE.

I fixed the issue using this guide:

https://xdaforums.com/t/fix-phone-r...de-can-only-be-started-from-fastboot.3705325/
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] odoll:
Just happened again.

SB else having the same issue?

Any hints how to wake the phone without having to remove the battery?

Thx
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] wk5779:
Same here. Happend after installing latest nightly (Oct 20) after first boot and twice afterwards (each morning). System seems to be running though (double pressing power button leads to vibration, seems to start camera app), but screen stays black (backlight not turned on). Please fix. Thank you!

(To reboot without removing battery: keep power button pressed for several seconds, until hardware resets)
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andr123a:
Hi all,

I was trying to make my first Lineage installation.

I unlocked successfully the bootloader, but when I try to sideload the lineage-18.1-20221020 I get the 8.1 error, but I followed all steps in the instructions (keeping my G5 updated to the last official build).

I read that some of you solved extracting and flashing NON-HLOS.bin file, but I didn't find it :(

Please, can you help my finding the correct procedure?

Many thanks

edit

Solved, I found the other zip file where to extract non-hlos.bin in the page 9 ;)
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] NestorMartinez:
Hello, I have installed the latest version of Lineage OS for my Moto G5 (Cedric), however the phone speaker is not working. Only headphones. I have tried installing stock roms, nougat and oreo and the sound does not return. Has anyone experienced this?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] jocker17:
Replying to myself for reference:

I wiped the system partition and reinstalled LineageOS followed by the Open-GApps (not MindTheGapps), and everything seems to work fine.

Not sure if a fresh install of LineageOS with MindTheGapps would work too.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] djibe89:
Hi, installed this perfect ROM and everything is working.

I describe below the workaround for the modem.bin crashing LOS install.

You can hide the Unlocked bootloader red message too.

Netflix + Disney+ work

Read this here: https://xdaforums.com/t/guide-tutorial-howto-motorola-moto-g5-stock-to-android-11.4524049/
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] f0urier:
I am using a Moto G5 with LOS: 18.1-20221216-NIGHTLY-cedric and am unable to charge the device while it is powered on. This screenshot from Settings > Battery, shows that the device is plugged in (as shown by the lightning icon), but says "Not charging".

The battery level stays constant, wont' go down or go up. The device charges fine while powered off, so I don't think it's a cable issue. Has anyone seen this before on the Moto G5 or any other device? Thanks.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] odoll:
No, everything's fine here
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] colocolo1234:
I have a problem with the microphone on my moto g5 after installing lineage os 18.1

in calls, if I don't put the speakerphone, they don't hear me

it's like it's muted but it really isn't

That the microphone is damaged I rule it out because as I say the moment I put the speaker on it starts to hear me without a problem

Has anyone experienced this and been able to fix it?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Epcilon:
I tried installing lineage-18.1-20230215-nightly-cedric-signed.zip for the first time following the cedric install guide and bumped into two issues, the second more serious than the first. I managed to install Lineage successfully in the end, so this is just an account that might help our dear dev or anyone experiencing the same issues:

Installing a custom recovery using fastboot failed and gave me an error message:

(bootloader) is-logical:recovery: not foundSending 'recovery' (15890 KB) OKAY [ 0.669s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.494s]
Finished. Total time: 1.172s

Was solved by running the fastboot flash recovery <recovery_filename>.img command twice before booting into recovery.

Installing LineageOS from recovery failed in a similar manner to these previous reports though my error was not in @/cache/recover/block.map but somewhere else (The path to the .zip on my PC if I recall correctly.) My G5 had the latest version that was supplied OTA by Motorola so I shouldn't have gotten the 8.1 incompatibility issue error:

Android version: 8.1.0

Current version: OPPS28.85-13-6

Scurity patch level: February 1,2019

I solved this by following the steps outlined here with the NON-HLOS.bin file contained in the .zip linked to from here. During these steps I had to reinstall the custom recovery.

I'm excited to explore my new OS now! Fingers crossed that everything works!
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] k3lcior:
Does anyone know how to disable the "AoD" screen when picking up the phone, that shows time and battery level?

Edit: I disabled it under Settings/Display/Lockscreen :)
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] MrhealerxD:
Pls can anyone help me my pc is not working and i want to reinstall the stock rom i have a phone pls help me someone
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] sumbuba:
Hello.I have one small problem.After installing lineageos 18.1 and mindthegapps i have "device is not certified" under Google play store.Everything else working fine.Should i install different gapps?How to solve this?Thnx
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] shutdown-h_now:
Look here; it shouldn't be a problem if everything is working fine:

How to Fix the "Device is not Certified by Google" Error

Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.

www.xda-developers.com
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Sarah TA:
Hello, I have installed LineageOS 18.1 with the hack of NON-HLOS.bin (thank you a lot!)

Everything works, except... calls! I don't hear anything if I send or receive a call.

I'm on Motorola G5 cedric XT1675 with LOS 18.1 20230915

It's not material, since I heard a simple app of piano

Have you a clue?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] danielcuervog:
Use Magisk + LSPosed + Shamiko + Don't enable denial list on Magisk + Enable Gapps like Play Store, Services and Services Framework and optionaly, Universal Safetynet fix.

If the problem persists, clear data on the Play Store app and it would work fine.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Sarah TA:
I have found a solution, described here:

https://www.reddit.com/r/LineageOS/comments/172vtnq/_/k73x52w