See - https://lineage-archive.timschumi.net/Does anyone have a 19x build I can't live without my camera. They have all been removed from the site from what I can see.
See - https://lineage-archive.timschumi.net/Does anyone have a 19x build I can't live without my camera. They have all been removed from the site from what I can see.
No, you can flash them on the official but the stuff that makes the unofficial worth using doesn't fit so no point.Hi All, I'm totally new here and this is the first time I've seriously considered updating a phone to an unofficial release so please bare with me if I ask a stupid questions. Thanks too for the great work here, anything that keeps working tech working and useful has to be good for the world!
For 7 Play you say "This device's partitions are too small for me to fit Google Apps and Pixel goodies, so no unofficial for it sadly". Does this mean it is impossible to get gmail, maps & play store on this device? Or have I missunderstood?
Thanks - Christopher
Just follow the guide, GApps work fine. Flash the right after you flash the ROM.Hi everyone!
Recently, i have installed Lineage OS 20 in my old reliable moto g7 play XT1952-2 following the official guidelines with unlocked bootloader requested in Lenovo forums (unlock website didnt work). Fortunately this device is not my daily driver (currently I'm using moto g stylus 2020 xt2043-4)
Lineage OS Rom works flawlessly (even the moto actions) but there's a big problem:
None of gapps working for me!
I've tried everything via adb interface and installing from the recovery:
MindTheGapps
BitGapps
NikGapps
FlameGapps
Sadly OpenGapps doesn't exist for Android 13
But nothing
Also, i`m dealing with another issue: after unlocking bootloader, motorola booting animation dissappeared and now stands a black screen with N/A text on it. Of course, it doesnt affect the normal operation of the device but i miss the motorola logo.
Can you help me with all this? Thanks in advance.
As for the moto logo just flash a logo.binHi everyone!
Recently, i have installed Lineage OS 20 in my old reliable moto g7 play XT1952-2 following the official guidelines with unlocked bootloader requested in Lenovo forums (unlock website didnt work). Fortunately this device is not my daily driver (currently I'm using moto g stylus 2020 xt2043-4)
Lineage OS Rom works flawlessly (even the moto actions) but there's a big problem:
None of gapps working for me!
I've tried everything via adb interface and installing from the recovery:
MindTheGapps
BitGapps
NikGapps
FlameGapps
Sadly OpenGapps doesn't exist for Android 13
But nothing
Also, i`m dealing with another issue: after unlocking bootloader, motorola booting animation dissappeared and now stands a black screen with N/A text on it. Of course, it doesnt affect the normal operation of the device but i miss the motorola logo.
Can you help me with all this? Thanks in advance.
On the other hand, updates to Lineageos on my Moto G7 River always did this. Patching the boot.img with Magisk, and flashing it via fastboot always brought it back.After installing the latest update I am left without root user. never happened to me with updates
Thanks for the reply i appreciate it very much.
nothing new. Works for some doesn't for others - logs unclear.Can anyone give me an update to the camera status. I would love to come back to the latest builds.
I have a bug.
NFC does not work.
It is off by default, and I cannot turn it on - there is no option to turn it on or off.
I have NFC and used it successfully on LOS 20.0 until last week of this May...For the Moto G7 series NFC is "market dependent" = Some G7 variants don't include NFC; if you have one of those then that setting might be for hardware that does not exist on that particular device. FYI, in UK the G7 and G7 Plus came with NFC but the G7 Play and G7 Power did not include NFC. In the US it may be the case that none of the G7 series includes NFC; such is the case for my US purchased Moto G7 Power (Ocean) which has no NFC in stock or in LOS ROMs.
What iteration and region of Moto G7 do you have? Has your G7 ever included NFC and if so in what Android variant (stock or custom) and in which Android version did NFC work on that device? if NFC ever did work properly on your device then you may have discovered a bug in which case logs and more details would inform development but if you have one of the devices which simply never included NFC then the "fix" may be for the ROM to hide that setting on devices which do not support NFC.
I have NFC and used it successfully on LOS 20.0 until last week of this May...
I suppose let me restate - I will post here very loudly and update the OP when/if it is fixed.I get your point and understand it can be annoying for you, but it helps others.
I was going to update myself, but since it's rather bothersome to reinstall Magisk after each update, I came here to see if anyone had already tried and thanks to Jim I knew I could skip this one.
Thank you, that works for me. Also, feel free to DM me if you need someone to test if it works.I suppose let me restate - I will post here very loudly and update the OP when/if it is fixed.
adb shell, can you give me a full getprop of your device?Thank you, that works for me. Also, feel free to DM me if you need someone to test if it works.
You should be following the update guide, not the install guide, and with that said, no, update via the updator and that's all you need to do.Do I need to run this evey time I update Lineage? I know it says I only need to run it once per device but what if I have an old Lineage build on slot B?
Ensuring all firmware partitions are consistent
info_outline
NOTE: The steps below only need to be run once per device.
In some cases, the inactive slot can be unpopulated or contain much older firmware than the active slot, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of the active slot to the inactive slot.
To do this, sideload the copy-partitions-20220613-signed.zip package by doing the following:
- Download the copy-partitions-20220613-signed.zip file from here. It should have a MD5 sum of 79f2f860830f023b7030c29bfbea7737 or a SHA-256 sum of 92f03b54dc029e9ca2d68858c14b649974838d73fdb006f9a07a503f2eddd2cd.
- Sideload the copy-partitions-20220613-signed.zip package:
- On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
- On the host machine, sideload the package using: adb sideload copy-partitions-20220613-signed.zip
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Well, it is frustrating simply because not anywhere it is indicated that LOS is in beta testing (or any, for that matter), as you indicated. I am an user not an early adopter.
It is a ready product. And as such should be fully functional.
Again I'll forestall any LOS self appointed henchmen, and point out that if something is free it does not mean it should be faulty.
Take note, that I do not criticize the DEVS work, but if at all, their timing and alacrity.
It's fixed. The last version had it broken, and was pulled.someone is testing the latest version for river? since the previous version did not work the wifi