[ROM][UNOFFICIAL][10.0][ALI] LineageOS 17.1 [64 Bit][DISCONTINUED] - Moto G6 ROMs, Kernels, Recoveries, & Other Develop

[ROM][UNOFFICIAL][10.0][ALI] LineageOS 17.1 [64 Bit][DISCONTINUED] - Moto G6 ROMs, Kernels, Recoveries, & Other Develop

Hi,
Thanks, I was waiting for this. I will test it on the weekend. Can you please move the thread to "Moto G6 ROMs, Kernels, Recoveries, & Other Development" section? It will be easier to find it.

roypen said:
Hi,
Thanks, I was waiting for this. I will test it on the weekend. Can you please move the thread to "Moto G6 ROMs, Kernels, Recoveries, & Other Development" section? It will be easier to find it.
Click to expand...
Click to collapse
Hi, I request to Moderators move the thread to that section. I don't have permissions to move it.

tomarc said:
Thanks you ! This is great news for me.
Can you fix the Moto Fingerprint Gestures ? Or maybe the rom has it own alternative ?
Click to expand...
Click to collapse
I'm trying to solve moto gestures but don't get a solution yet, the alternative are the android 10 gestures but they work with the screen, not with fingerprint

tomarc said:
Thanks you ! This is great news for me.
Can you fix the Moto Fingerprint Gestures ? Or maybe the rom has it own alternative ?
Click to expand...
Click to collapse
I'm trying to solve moto gestures but don't get a solution yet, the alternative are the android 10 gestures but they work with the screen, not with fingerprint

Thank you
Thank you very much for building and posting this ROM. I would very much like to try it on my G6 (XT1925-5).
Following this thread, I got as far as unlocking the bootloader and booting TWRP from fastboot. But could not flash anything because of a locked boot.img. I have requested an edited boot.img and hope to get a reply.
Is there perhaps another way to get my G6 (XT1925-5) with firmware version PPSS29.55-37-7-10 to be able to run LineageOS?
Thanks in advance,
FWieP

fwiep said:
Thank you very much for building and posting this ROM. I would very much like to try it on my G6 (XT1925-5).
Following this thread, I got as far as unlocking the bootloader and booting TWRP from fastboot. But could not flash anything because of a locked boot.img. I have requested an edited boot.img and hope to get a reply.
Is there perhaps another way to get my G6 (XT1925-5) with firmware version PPSS29.55-37-7-10 to be able to run LineageOS?
Thanks in advance,
FWieP
Click to expand...
Click to collapse
Hi, which twrp did you try? You might want to use the twrp64 as this LOS17.1-build is a 64 Bit

nightmw said:
Hi, which twrp did you try? You might want to use the twrp64 as this LOS17.1-build is a 64 Bit
Click to expand...
Click to collapse
Thanks for the reply. I used twrp-3.4.0-0-ali, downloaded from the official download page.
Is there a special download page for 64bit TWRP?
Kind regards,
FWieP

tomarc said:
You can find it here : https://forum.xda-developers.com/moto-g6/development/twrp-twrp-64-bit-ali-t4093879
Click to expand...
Click to collapse
Once again: thank you all. I downloaded the mali.img and booted TWRP from it.
Then, I flashed the new LineageOS 17.1 and OpenGapps - without any problems, warnings or errors.
If there is no way to flash TWRP into the recovery partition permanently, I can live with that.
Most important thing is, I can flash the system partition when needed.
Hope to see more of your work!
Kind regards,
FWieP

BetoxxDios said:
What's not working:
Moto Fingerprint Gestures
You tell me
Contributors
@BetoxxDios
@Electimon
@abhishek_d9
@jeangraff30
Click to expand...
Click to collapse
Having flashed this ROM a few days ago, I find it nearly perfect. Nearly
the October 2020 security patches are available from LineageOS; can they be included?
Would it be possible for you to share your kernel (link to source) and roomservice.xml?
I would like to try and build the ROM myself. Perhaps contribute, at least providing a mirror for the ROM files?
If not you (@BetoxxDios), perhaps the other contributors (@Electimon, @abhishek_d9, @jeangraff30) ?
Thanks!
Kind regards,
FWieP

failed to load kernel!
On my XT1925-5 I have flashed this rom serveral times, no errors, but it fails to boot.
When I restore the backup, I'm on stock again...
After installing twrp (mali.img) I did format data, reboot onto twrp, wipe, install etc.
Still it will boot only to fastboot: failed to load kernel!
Any suggestions?

Close, but no cigar - yet
fwiep said:
Would it be possible for you to share your kernel (link to source) and roomservice.xml?
I would like to try and build the ROM myself.
Click to expand...
Click to collapse
Thanks @BetoxxDios for providing the links to kernel, device and vendor trees in a private message.
After expanding the RAM of my machine to 16GB and some very educational experiments, the build finally succeeded.
TWRP flashed the ROM without any errors. Yeah!
Then the first reboot. I know that this usually takes a long time - say, 5 minutes. I've left it booting for more than 4 hours, but it doesn't get past the bootanimation.
Can anyone help me in solving this piece of the puzzle? Are there any logs I can get at while the phone is not yet adb-ready? What does LineageOS do while booting for the first time?
Thanks and kind regards,
FWieP
P.S. For the moment, I've flashed @BetoxxDios' original ROM. It's better (and safer) than Motorola's stock firmware.

fwiep said:
.
Then the first reboot. I know that this usually takes a long time - say, 5 minutes. I've left it booting for more than 4 hours, but it doesn't get past the bootanimation.
Can anyone help me in solving this piece of the puzzle? Are there any logs I can get at while the phone is not yet adb-ready? What does LineageOS do while booting for the first time?
Thanks and kind regards,
FWieP
A frozen boot screen like that has happened to me many times. Usually 1 of 2 issues. 1. Gapps problem 2. Magisk problem.
Cheers.
Click to expand...
Click to collapse

Baronstragen said:
A frozen boot screen like that has happened to me many times. Usually 1 of 2 issues. 1. Gapps problem 2. Magisk problem.
Click to expand...
Click to collapse
Thanks for the tip.
I'm afraid this is another issue - I haven't flashed any Gapps with my ROM (yet), and have never even used Magisk before.
 @BetoxxDios has shown me a way to get logfiles during boot: build an -eng variant instead of -user or -userdebug.
Now, we're investigating what's going wrong. To be continued!
Kind regards,
FWieP

tomarc said:
Yes, you can flash it permanently :
Fastboot flash recovery xxx.img ; xxx.img being the name of the recovery file.
Click to expand...
Click to collapse
Up until today, I thought this wouldn't work. When doing so, fastboot would say:
Code:
writing 'recovery'...
(bootloader) Image not signed or corrupt
And thus, I thought it had not flashed at all.
Today, I read elsewhere on this forum, to simply ignore this message and check whether it flashed. It actually has!
So, thank you, once again
Kind regards,
FWieP
---------- Post added at 17:22 ---------- Previous post was at 17:08 ----------
fwiep said:
Now, we're investigating what's going wrong. To be continued!
Click to expand...
Click to collapse
And continue it does.
Right from the start, while building this ROM, I got an error about an undefined shared library: libqsap_sdk in /device/motorola/ali/libshims/Android.mk.
I saw it was in a section marked "optional", so I commented it out. And the build succeeded. Yes! After flashing, I got the looping boot-animation. D'oh!
But then, while trying to build another ROM (Resurrection Remix OS 8.6.3 by @abhishek_d9), I got the same error.
I again commented the section out, built the ROM successfully, but got the same looping boot-animation after flashing.
So, XDA to the rescue: I found this post which explains to include '/system/qcom' from LineageOS to get that libqsap_sdk included. I've added it to my roomservice.xml and have started another build. It looks very promising.
Maybe case solved? I'll let you know.
Update
Close, but no cigar. The looping boot-animation still persists. I'll investigate further...
Kind regards,
FWieP

whats-in-a-name said:
On my XT1925-5 I have flashed this rom serveral times, no errors, but it fails to boot.
When I restore the backup, I'm on stock again...
After installing twrp (mali.img) I did format data, reboot onto twrp, wipe, install etc.
Still it will boot only to fastboot: failed to load kernel!
Any suggestions?
Click to expand...
Click to collapse
I bought a new phone, also XT1925-5 and unlocked. But also here, I get the same error:
failed to load kernel!
Stock Android was 8.0 and this rom is 10. could that be a problem?

Solved 'kernel not found'
whats-in-a-name said:
I bought a new phone, also XT1925-5 and unlocked. But also here, I get the same error:
failed to load kernel!
Stock Android was 8.0 and this rom is 10. could that be a problem?
Click to expand...
Click to collapse
I used Motorola Rescue and Smart Assistant Tool
First of all I restored the phone by using the rescue_and_smart_assistant and installed Android 9
Then I used: fastboot boot mali.img
In TWRP, I removed encryption by installing: Force_Encryption_Disabler_For_ALI_Oreo_v2.zip
Wipe, the standard wipe (factory reset) + Format data
Then reboot to bootloader, and again load TWRP: fastboot boot mali.img
Wipe again and install the system (lineage-17.1-20201001-UNOFFICIAL-ali.zip)
install Magisk
Wipe cache and Dalvik
reboot into system

whats-in-a-name said:
Solved 'kernel not found'
I used Motorola Rescue and Smart Assistant Tool
First of all I restored the phone by using the rescue_and_smart_assistant and installed Android 9
Then I used: fastboot boot mali.img
In TWRP, I removed encryption by installing: Force_Encryption_Disabler_For_ALI_Oreo_v2.zip
Wipe, the standard wipe (factory reset) + Format data
Then reboot to bootloader, and again load TWRP: fastboot boot mali.img
Wipe again and install the system (lineage-17.1-20201001-UNOFFICIAL-ali.zip)
install Magisk
Wipe cache and Dalvik
reboot into system
Click to expand...
Click to collapse
I tried all of that and keep getting "updater process ended with ERROR: 255 Error installing zip file...." Any way to fix this issue? I'm on XT1925-6 32gb.
Never mind, I had the wrong TWRP installed like a dope.

I installed the ROM following your instructions and other sources:
- unlocked the bootloader
- flashed the unofficial TWRP recovery for the moto g6 ali (https://forum.xda-developers.com/t/twrp-unofficial-twrp-64-bit-for-ali.4093879/)
- wiped system, data, cache and dalvik, my device has no vendor partition though
- flashed your Lineage Rom
- flashed the most recent GAPPS, for Android 10, arm 64, stock
Then rebooting the phone will just end up in an infinite boot animation.
Doing it all over without the gapps and the phone boots just fine. So it seems that the gapps installation is somehow causing the trouble. I tried many different gapps packages, but all without any success.
Could you provide a link to a gapp package that is known to work with your ROM?
Thanks in advance!

I installed the ROM following your instructions and other sources:
- unlocked the bootloader
- flashed the unofficial TWRP recovery for the moto g6 ali (https://forum.xda-developers.com/t/twrp-unofficial-twrp-64-bit-for-ali.4093879/)
- wiped system, data, cache and dalvik, my device has no vendor partition though
- flashed your Lineage Rom
- flashed the most recent GAPPS, for Android 10, arm 64, stock
Then rebooting the phone will just end up in an infinite boot animation.
Doing it all over without the gapps and the phone boots just fine. So it seems that the gapps installation is somehow causing the trouble. I tried many different gapps packages, but all without any success.
Could you provide a link to a gapp package that is known to work with your ROM?
Thanks in advance!

Related

[ROM][Official][8.1.0] LineageOS 15.1 Nightlies For International Oppo R5/R5s (R8106)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://wiki.lineageos.org/devices/r5
Official nightlies for International Oppo R5/R5s (R8106) has arrived!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Important information
This thread is for LineageOS 15.1 builds for International Oppo R5/R5s (R8106). The following will not be supported here:
Custom kernels
Mods
Xposed
Installation
First time flashing LineageOS 15.1 on your device, or coming from another ROM?
Flash Project Spectrum as outlined here.
Flash unlockable bootloader obtained from here via stock recovery.
Unlock bootloader (fastboot oem unlock).
Flash compatible custom recovery.
Download the nightly/snapshot zip.
Perform a backup of your current ROM (optional).
Wipe data/factory reset.
Flash LineageOS.
(Optionally) flash Google Apps.
Reboot.
For more details, please see here.
Updating your TWRP recovery is recommended. Official TWRP isn't compatible ATM.
For CyanogenMod 13/14.1 users, see here.
Official Builds
https://download.lineageos.org/r5
Google Apps
http://opengapps.org/
Known Issue/Bugs
Found a bug? Random Reboot etc.
Please post logs.
Changelog
https://www.lineageoslog.com/15.1/r5
Source
https://github.com/LineageOS
Kernel: https://github.com/LineageOS/android_kernel_oppo_msm8939
Device: https://github.com/LineageOS/android_device_oppo_r5
Credits
LineageOS Community. I'm not the maintainer of it.
Official maintainer: Big thanks to:good: @maniac103

First of all big big thank you @maniac103 for supporting this device
Next I already found a bug as I can't connect to wifi. It tries to connect then the status stays on "connection saved". I've tried everything with wifi password, without and even WPS won't work. I've tested 20180724 and 20180731
Felt butter smooth but didn't do very much as I switched back to good working 14.1 pretty quick

Error 7 in TWRP with install.
Hi, thanks for the hard work, I have an Oppo r5s int version. I have tried to install/ update 15.1 and I get error 7 in TWRP. I have to unzip the ROM and edit the update script to get it to install, and I have had to do this with each nightly that has been released. What can I do to avoid this, I never had a problem with 14.1? I have tried a clean and dirty flash but get the same result. Another problem is gapps, I have tried to install arm 8. 1 within TWRP but the installation freezes. The gapps on my phone still works perfectly but are from the previous version of lineage 14.1. Does the gapps 8.1 take a long time to install as it overwrites the previous version or do I just leave it?

You probably have an old version of TWRP. Update to this version and you should be good to go: https://androidfilehost.com/?fid=673791459329072194
Maybe this also solves your GApps problem. If you install 15.1 your old GApps get deleted. I always flash the nano version as it is lighter and faster

Error 7 in TWRP with install.
mwayne said:
You probably have an old version of TWRP. Update to this version and you should be good to go: https://androidfilehost.com/?fid=673791459329072194
Maybe this also solves your GApps problem. If you install 15.1 your old GApps get deleted. I always flash the nano version as it is lighter and faster
Click to expand...
Click to collapse
Thanks, you are a star for guessing correctly. I had a slight suspicion it might be TWRP as I was on version 3.0.3.0. I did try and download it from the TWRP website but they never put the a version that works with the R5s, I tried the R7s version as I heard that works but it didn't. Your link for twrp worked perfectly, after that was installed I reflashed the latest nightly, no more error 7 and finally GApps 8.1 nano (always nano) again perfect. I hope this helps anyone else that has the same problems and again many thanks to you and the devs.
:good:

davendiva said:
Thanks, you are a star for guessing correctly. I had a slight suspicion it might be TWRP as I was on version 3.0.3.0. I did try and download it from the TWRP website but they never put the a version that works with the R5s, I tried the R7s version as I heard that works but it didn't. Your link for twrp worked perfectly, after that was installed I reflashed the latest nightly, no more error 7 and finally GApps 8.1 nano (always nano) again perfect. I hope this helps anyone else that has the same problems and again many thanks to you and the devs.
:good:
Click to expand...
Click to collapse
You're welcome. I had the same issue at first. Is your wifi working?

mwayne said:
You're welcome. I had the same issue at first. Is your wifi working?
Click to expand...
Click to collapse
Hi, I only had and issue with the wifi on the very first 15.1 nightly (20180710) it was very temperamental and would work then stop. So I reverted back to a backup of lineage 14.1 I had made prior to this, I guessed that being the very first nightly it could be a bit buggy. The next 15.1 nightly (20180717) which I flashed straight over 14.1 without any wipe in TWRP worked perfectly and wifi is operating as expected and has done with the 2 following 15.1 nightlies which is up to present. I have used my R5S on several different WiFi connections and all is functioning properly. Is your wifi working OK?

davendiva said:
Hi, I only had and issue with the wifi on the very first 15.1 nightly (20180710) it was very temperamental and would work then stop. So I reverted back to a backup of lineage 14.1 I had made prior to this, I guessed that being the very first nightly it could be a bit buggy. The next 15.1 nightly (20180717) which I flashed straight over 14.1 without any wipe in TWRP worked perfectly and wifi is operating as expected and has done with the 2 following 15.1 nightlies which is up to present. I have used my R5S on several different WiFi connections and all is functioning properly. Is your wifi working OK?
Click to expand...
Click to collapse
Thanks for the info. I just dirty flashed 20180731 (no wipe dalvik/cache) and it works perfect

mwayne said:
Thanks for the info. I just dirty flashed 20180731 (no wipe dalvik/cache) and it works perfect
Click to expand...
Click to collapse
Excellent, I'm glad you solved your problem, we both got there in the end. It should be simple from now on by using the update in the settings menu instead of messing around in TWRP manually.

mwayne said:
https://wiki.lineageos.org/devices/r5
Official nightlies for International Oppo R5/R5s (R8106) has arrived!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Important information
This thread is for LineageOS 15.1 builds for International Oppo R5/R5s (R8106). The following will not be supported here:
Custom kernels
Mods
Xposed
Installation
First time flashing LineageOS 15.1 on your device, or coming from another ROM?
Flash Project Spectrum as outlined here.
Flash unlockable bootloader obtained from here via stock recovery.
Unlock bootloader (fastboot oem unlock).
Flash compatible custom recovery.
Download the nightly/snapshot zip.
Perform a backup of your current ROM (optional).
Wipe data/factory reset.
Flash LineageOS.
(Optionally) flash Google Apps.
Reboot.
For more details, please see here.
Updating your TWRP recovery is recommended. Official TWRP isn't compatible ATM.
For CyanogenMod 13/14.1 users, see here.
Official Builds
https://download.lineageos.org/r5
Google Apps
http://opengapps.org/
Known Issue/Bugs
Found a bug? Random Reboot etc.
Please post logs.
Changelog
https://www.lineageoslog.com/15.1/r5
Source
https://github.com/LineageOS
Kernel: https://github.com/LineageOS/android_kernel_oppo_msm8939
Device: https://github.com/LineageOS/android_device_oppo_r5
Credits
LineageOS Community. I'm not the maintainer of it.
Official maintainer: Big thanks to:good: @maniac103
Click to expand...
Click to collapse
I got a issue with my wifi, I can't tunr on and searching for wifi network.
Can you fix this bug.
Thank you

Read the previous messages. You can flash straight over lineageos 14.1 without any wipe with the latest twrp installed with the latest 15.1 nightly

I can not reboot to recovery by holding the power button and volume down button after I falsh twrp-3.2.1-0-r5-20180110.img in fastboot.
I can only get into the system setup ,but the device does not respound when I touch the screen.
My device is OPPO R8107,the same hardware of R8106 version;Already flashed the Full Wipe Package.

I see a couple of problems with WiFi here. I too am having problems with the WiFi. I tried wiping the entire disk, all sections including the dalvik cache, system, data and cache and then re-installed again but I find the Wifi turns itself off as soon as I try to turn it on. I noticed some other people had similar problems, with their MAC addresses showing as 'Unavailable' or 02:00:00:00:00:00 which was suggested to be encryption on the disk which is why I wiped everything and re-installed again.
I installed this over an original Oppo R5 installation, following the instructions on the Lineage wiki for the R5.
Does anyone have any suggestions?
I should add that I installed version lineage-15.1-20181016-nightly-r5-signed. I have also tried a 'dirty flash' over the top of an existing install of Lineage which also seems to have the same problem.

FuLiTheOne said:
I can not reboot to recovery by holding the power button and volume down button after I falsh twrp-3.2.1-0-r5-20180110.img in fastboot.
I can only get into the system setup ,but the device does not respound when I touch the screen.
My device is OPPO R8107,the same hardware of R8106 version;Already flashed the Full Wipe Package.
Click to expand...
Click to collapse
The stage I installed TWRP is after you have flashed project spectrum recovery & rom and then unlocked the bootloader. The recovery can reset itself to the original if you reboot your phone with the computer. As soon as you have flashed TWRP from fastboot, unplug from the computer and then press power and vol down and hold them untill it reboots. Only use the twrp that mwayne posted earlier as the official TWRP site downloads don't work. If this doesn't work the issue might be because yours is the Chinese version, the R8106 is the global version.
---------- Post added at 08:20 AM ---------- Previous post was at 07:57 AM ----------
mkstevo said:
I see a couple of problems with WiFi here. I too am having problems with the WiFi. I tried wiping the entire disk, all sections including the dalvik cache, system, data and cache and then re-installed again but I find the Wifi turns itself off as soon as I try to turn it on. I noticed some other people had similar problems, with their MAC addresses showing as 'Unavailable' or 02:00:00:00:00:00 which was suggested to be encryption on the disk which is why I wiped everything and re-installed again.
I installed this over an original Oppo R5 installation, following the instructions on the Lineage wiki for the R5.
Does anyone have any suggestions?
I should add that I installed version lineage-15.1-20181016-nightly-r5-signed. I have also tried a 'dirty flash' over the top of an existing install of Lineage which also seems to have the same problem.
Click to expand...
Click to collapse
Hi, this are the steps I made for installing 15.1 and I have no issues with wifi other than the very first nightly.
1. Follow the steps from https://wiki.lineageos.org/devices/r5/install
2. Use only TWRP from mwayne's link from an earlier post.
https://androidfilehost.com/?fid=673791459329072194
3. Flash any lineage 14.1 rom first, this is important.
4. Once installed reboot phone and download the latest lineage 15.1 nightly and GApps ARM 8.1 nano onto phone.
5. Boot recovery, select the 15.1 and install then do the same with gapps. Once finished just reboot device. Do not wipe or format anything before or after the install in TWRP this time, just install and reboot.
6. You can go to gplay and add any more GApps you require.
Hope this helps

davendiva said:
The stage I installed TWRP is after you have flashed project spectrum recovery & rom and then unlocked the bootloader. The recovery can reset itself to the original if you reboot your phone with the computer. As soon as you have flashed TWRP from fastboot, unplug from the computer and then press power and vol down and hold them untill it reboots. Only use the twrp that mwayne posted earlier as the official TWRP site downloads don't work. If this doesn't work the issue might be because yours is the Chinese version, the R8106 is the global version.
---------- Post added at 08:20 AM ---------- Previous post was at 07:57 AM ----------
Hi, this are the steps I made for installing 15.1 and I have no issues with wifi other than the very first nightly.
1. Follow the steps from https://wiki.lineageos.org/devices/r5/install
2. Use only TWRP from mwayne's link from an earlier post.
https://androidfilehost.com/?fid=673791459329072194
3. Flash any lineage 14.1 rom first, this is important.
4. Once installed reboot phone and download the latest lineage 15.1 nightly and GApps ARM 8.1 nano onto phone.
5. Boot recovery, select the 15.1 and install then do the same with gapps. Once finished just reboot device. Do not wipe or format anything before or after the install in TWRP this time, just install and reboot.
6. You can go to gplay and add any more GApps you require.
Hope this helps
Click to expand...
Click to collapse
Hello.
I really appreciate your assistance here. I have tried to find a copy of the 14.1 rom for the R5 but they appear to have been removed from LineageOS website. Thinking you meant 'any' 14.1 rom, I downloaded one for the Oppo N3/N5 and attempted to install it but the install fails with the message that it is the wrong file for the device.
Am I looking in the wrong place for the 14.1 rom? Or should I be doing something to force the install of the N3/N5 version?
Sorry if I'm showing my stupidity here...

mkstevo said:
Hello.
I really appreciate your assistance here. I have tried to find a copy of the 14.1 rom for the R5 but they appear to have been removed from LineageOS website. Thinking you meant 'any' 14.1 rom, I downloaded one for the Oppo N3/N5 and attempted to install it but the install fails with the message that it is the wrong file for the device.
Am I looking in the wrong place for the 14.1 rom? Or should I be doing something to force the install of the N3/N5 version?
Sorry if I'm showing my stupidity here...
Click to expand...
Click to collapse
Hi, don't install anything other than the rom for the specific model. You're in luck that I found a lineage 14.1 on my pc. Click the link below
https://drive.google.com/file/d/1ndr2tI49GAaeHPDUgcOgNykBIZQ_J4wy/view?usp=drivesdk
Good luck.

davendiva said:
Hi, don't install anything other than the rom for the specific model. You're in luck that I found a lineage 14.1 on my pc. Click the link below
https://drive.google.com/file/d/1ndr2tI49GAaeHPDUgcOgNykBIZQ_J4wy/view?usp=drivesdk
Good luck.
Click to expand...
Click to collapse
Super thanks. I'll give it a go.
Many, many thanks for your kindness in locating the version 14 for me. I have today managed to install this onto my Oppo R5 and am delighted to say that it is working superbly, WiFi included.
As this version includes the Trebuchet launcher, I'm quite happy to stick with V14 for the time being, especially given that it is working and took me ages to set up as I would like. I prefer the Trebuchet launcher to most others and have actually installed the generic version of it (Catapult) on previous devices.
I'd like to say thanks again, you've helped a 50+ year old out immensely.

i am having a problem installing Lineage OS Version 15.1 and latest version 16 nightly. the error code 7 appears in all version available to download on the official website and tried to edit the script just to make the installation work. it did flashed the ROM, it will boot on the system, however in some unknown reason the device will freeze then the screen will turn off( but it seems like it did not shutdown, the device seems ACTIVE but the screen is OFF ). so i needed to hold the power button to reboot the device and the problem will be encounter again. the device will freeze after a few seconds after the device is booted or rebooted. i tried to wipe the data cache, dalvik, factory reset, no gapps installed do it over and over tried to install again then wipe cache/dalvik all possible way i know fix it but no luck. i even tried to boot the device on safe mode yet the problem still occurs. i can't even use my device even just for a minute to make a log.

I need help. I realized that my phone is r8107 rather than r8106. When I was trying to unlock the bootloader I couldn't install spectrum recovery. Is there any way to deal with it?

Help!
Is there anybody still have the nightlies lineageOS 14.1 ROM of OPPO R5?

[ROM][CrDroid v6.x][OFFICIAL][ocean][Discontinued]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Downloads
Official Website
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
*****Disclaimer*****
Important note before proceeding!!!
The copy A/B partitions zip is crucial in order to prevent bricks. It only needs to be done if you're coming from the stock ROM or you recently restored stock firmware manually. Other wise without it you can brick due to Motorola's A/B partition scheme.
Only use TWRP version 3.3.1-0, it has an advanced option for recovery bootloop fix. Sorry for some hassles with TWRP. It is not ROM related but the version I use works 100% of the time.
My apologies for any confusion/problems flashing!
Preparation for A/B Roms:
01. Download TWRP version 3.3.1-0 (do not use any other version)
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader
04. Use the terminal to boot the latest twrp.img "fastboot boot twrp.img"
05. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmware.)
06. While in TWRP choose Reboot > bootloader
07. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Wipe data, dalvik, system and internal storage, then format userdata.
04. Flash ROM.zip + TWRP_installer
05. Reboot > Recovery
06.Install Gapps + Magisk (if you choose)
07. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. Boot into recovery
03. Install ROM.zip + TWRP_installer
04. Reboot > Recovery
05. flash GAPPS + Magisk (if you choose)
06. Reboot > System
Notes:
Any time your internal storage aka "Userdata" is from a stock install you must "format data" in recovery before using ROMS
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
SOURCES:
ROM: https://github.com/crdroidandroid
Changelog::
https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/10.0/changelog_ocean.txt
Known issues:

Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
© 2020 GitHub, Inc.
XDA:DevDB Information
CrDroid, ROM for the Moto G7 Power
Contributors
Rondeau79
Source Code: https://github.com/Rondeau79/android_kernel_motorola_sdm632
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest TWRP unlocked bootloader
Based On: AOSP, Lineage OS
Version Information
Status: Stable
Current Stable Version: QQ2A.200305.003
Stable Release Date: 2020-03-22
Created 2020-03-22
Last Updated 2020-06-23

Reserved

Ahh the ole triple posts. Don't you just love it when that happens. lol. Hell of a job on this! Will Android 10 for Ocean device ever be able to have an enforcing kernel or no? Probably waiting for source for 10/Q before messing with all that stuff? I'm just curious and figured I'd ask.. Awesome work!!!! :good:

flash713 said:
Ahh the ole triple posts. Don't you just love it when that happens. lol. Hell of a job on this! Will Android 10 for Ocean device ever be able to have an enforcing kernel or no? Probably waiting for source for 10/Q before messing with all that stuff? I'm just curious and figured I'd ask.. Awesome work!!!! :good:
Click to expand...
Click to collapse
Thanks, this one was a tough task to get done. I don't mind a permissive kernel. I really don't dive too far into the Android system. I am a fan first and a developer second! I still really don't have an understanding of code and stuff. I just go with my instincts.

I performed a 'dirty flash' coming from crDroid 5.12 (based on Android 9).
I did not delete my Google account from the phone prior to flashing. This is the first time I've had problems upgrading crDroid. I realize it's also the first time I've done a major increment to the underlying Android OS.
Upon first boot I saw the new boot animation (it looks great!) but the phone did not complete booting after about ten minutes. I interrupted the boot by holding the power key. I tried wiping data. Later, I also tried re-formatting data partition (including built-internal media). I also tried re-installing the most recent version of crDroid 5.12 with no success with that as well.
Suggestions regarding the best way to correct this would be helpful and appreciated.
In the meantime, I'll look around and trying some other things. I hope it might be corrected without having to resort to ADB / PC connection, but I'll try whatever I can.
I don't know if this result is considered "a brick" because I can boot into TWRP.

danny8 said:
I performed a 'dirty flash' coming from crDroid 5.12 (based on Android 9).
I did not delete my Google account from the phone prior to flashing. This is the first time I've had problems upgrading crDroid. I realize it's also the first time I've done a major increment to the underlying Android OS.
Upon first boot I saw the new boot animation (it looks great!) but the phone did not complete booting after about ten minutes. I interrupted the boot by holding the power key. I tried wiping data. Later, I also tried re-formatting data partition (including built-internal media). I also tried re-installing the most recent version of crDroid 5.12 with no success with that as well.
Suggestions regarding the best way to correct this would be helpful and appreciated.
In the meantime, I'll look around and trying some other things. I hope it might be corrected without having to resort to ADB / PC connection, but I'll try whatever I can.
I don't know if this result is considered "a brick" because I can boot into TWRP.
Click to expand...
Click to collapse
You are not bricked. When coming from one version of android to another a clean flash must be done. You can dirty flash after that. Wipe both boot slots and then go about flashing like normal. First boot takes a while. It won't boot without wiping the system partition.

Excuse my ignorance, where do I have to install the rom, gapps and magisk, in slot A or B? Thank you in advance (sorry bad English)

D13Gho said:
Excuse my ignorance, where do I have to install the rom, gapps and magisk, in slot A or B? Thank you in advance (sorry bad English)
Click to expand...
Click to collapse
With the A/B partitions scene. When you flash a ROM it will be installed to the opposite slot. If you are on A then the zip will be installed to B and vica versa. Gapps are flashed after you reboot to recovery when you are on the boot slot the ROM was installed on same as Magisk.

Thank you, Rondeau79. I got it installed.
It looks great!

I've got every thing installed and running, but after setting up my apps (Chrome, messages, photos) app opening/closing is quite laggy. It become unusable after a couole hours.

Johnfoo19 said:
I've got every thing installed and running, but after setting up my apps (Chrome, messages, photos) app opening/closing is quite laggy. It become unusable after a couole hours.
Click to expand...
Click to collapse
Give it a little time to set in. Usually a fresh install takes a bit.

danny8 said:
Thank you, Rondeau79. I got it installed.
It looks great!
Click to expand...
Click to collapse
You're welcome.

pie had the option of changing colors in the display settings I am not a fan of blue I like black and red. is this in a future update it was the main reason i uninstalled the other android 10 roms

cgrimm9 said:
pie had the option of changing colors in the display settings I am not a fan of blue I like black and red. is this in a future update it was the main reason i uninstalled the other android 10 roms
Click to expand...
Click to collapse
Go to display styles and wallpapers to change to colors.

Is there any way to set the position of the battery bar? like bottom of the screen or lower status bar because where default is top of screen you kinda miss half the bar because of the notch

Has anyone had any issues with mobile data not working after installing this ROM? I was able to make calls and send texts (I have Sprint, phone: Moto G7 Power X1995-5). I reflashed it and OEM locked back to stock firmware since mobile data was not working. Also, I did not have SD card since I don't have one

n00b Samurai said:
Is there any way to set the position of the battery bar? like bottom of the screen or lower status bar because where default is top of screen you kinda miss half the bar because of the notch
Click to expand...
Click to collapse
Sorry there isn't, I can't change the base features of the ROM. However you can change the color and thickness of the bar and it's position on the screen.
You can always adjust the screen in order to account for the notch. It's in the developer settings.

barados742 said:
Has anyone had any issues with mobile data not working after installing this ROM? I was able to make calls and send texts (I have Sprint, phone: Moto G7 Power X1995-5). I reflashed it and OEM locked back to stock firmware since mobile data was not working. Also, I did not have SD card since I don't have one
Click to expand...
Click to collapse
You need an external sdCard for flashing ROMs. Wiping the user partitions properly is essential for a properly working ROM. If you just have internal storage then the installation of an OS won't be done right.

Thanks for the reply! I just bought an SD card and will try it tomorrow and will respond if it worked.

Good morning, guys I tried to install on my MOTO G 7 POWER 3/32 and the rom does not install says it is not compatible with the system. Any tips?

[RECOVERY] [OFFICIAL] [PBRP] [v2.9.1] 5/21/2020

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're 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 us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.2.3
PitchBlack version: 2.9.0
For device: U12+/Exodus1
Maintainer/Authors build: @JEANRIVERA @mikalovtch
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/jeanrivera/android_device_htc_ime
PitchBlack Team: @rezaadi0105, @firewolfxda, @manjot.gni, @androiabledroid, Arbaz Khan
Features
Supports Treble and non-Treble ROMs
Up-to-date Oreo kernel, built from sources (Pie is on the way)
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Temp boot Instructions
Download the PitchBlack img to your computer
Reboot to bootloader
Code:
fastboot boot recovery_name.img
The device will automatically reboot into PitchBlack Recovery
Enjoy
Permanent Install instructions
Download the PitchBlack img to your device
temp boot in TWRP or PBRP
install / install image bottom right corner / select PBRP.img / install recovery ramdisk
if you are rooted with Magisk remember to flash Magisk after install Recovery ramdisk
if your Kernel is stock flash touchscreen_hexpatcher.zip
Reboot to Recovery & Enjoy
Changelog
Code:
v2.9.1
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Known Issues
All Official TWRP Issues (not many)
Aroma not supported on U12+ / Exodus 1
Stock ROM Pie Decryption currently not possible (workaround disable Force Encrypt NOT Recommended if you want your device to be secured, your device your option
You Tell me
Downloads
https://sourceforge.net/projects/pitchblack-twrp/files/ime/
Additional Downloads
Touchscreen hexpatcher | Mirror (AFH) - SEE IMPORTANT NOTES BELOW:
Only needed when on stock kernel without touchscreen fix
Flashing touchscreen_hexpatcher.zip will make touch work when using stock kernel but render all recovery related commands unusable.
This includes "adb reboot recovery", reboot to recovery from Magisk Manager and reboot to recovery from inside TWRP. To get into TWRP you first have to reboot to bootloader and from there on to TWRP/Recovery!
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the HTC U12+
Contributors
JEANRIVERA, mikalovtch
TWRP: @Freak07, @Captain_Throwback
PBRP: Reza Adi, Firewolfxda, Manjot Sidhu, Mohd Faraz, Arbaz Khan
Source Code: https://github.com/PitchBlackRecoveryProject/android_bootable_recovery
Version Information
Status: Official
Current Version: 2.9.1
Release Date: 2020-05-21
Created 2020-05-01
Last Updated 2020-05-21

Reserved

Reserved

Great to see a updated recovery! Thanks for this! I will try it.
Do you know why is still not possible to decrypt pie? And why you do not recommended to disable it? At the beginning everyone wanted disable this.

Max128 said:
Great to see a updated recovery! Thanks for this! I will try it.
Do you know why is still not possible to decrypt pie? And why you do not recommended to disable it? At the beginning everyone wanted disable this.
Click to expand...
Click to collapse
1. it is no possible to decrypt stock pie due to HTC proprietary encryption protocol, it is not Open Source, and the Dev that made it possible @nkk71 to decrypt previous HTC Encrypted devices passed away, and no one has been able to take over his amazing work.
2. It is not secure to have an un-encrypted device, at the end is your device and your choice,

JEANRIVERA said:
1. it is no possible to decrypt stock pie due to HTC proprietary encryption protocol, it is not Open Source, and the Dev that made it possible @nkk71 to decrypt previous HTC Encrypted devices passed away, and no one has been able to take over his amazing work.
2. It is not secure to have an un-encrypted device, at the end is your device and your choice,
Click to expand...
Click to collapse
Hello, installed following the guide and got this

I also have a problem with this recovery. I want to make a nandroid backup ( system , boot and data ) i am on viper rom gsi now. I always have this error when i launch a backup , : unable to find partition for path '/system. In mount the system is checked and the mount system partition read only is not possible to uncheck it.
After that i have try the twrp updated for viper rom and is working fine this one no problem for backup.

new version uploaded, it should be as stable as official TWRP + some extras , & now become almost official release, still a pre-official test for official release
https://github.com/PitchBlackRecoveryProject/android_device_htc_ime-pbrp/releases

Max128 said:
I also have a problem with this recovery. I want to make a nandroid backup ( system , boot and data ) i am on viper rom gsi now. I always have this error when i launch a backup , : unable to find partition for path '/system. In mount the system is checked and the mount system partition read only is not possible to uncheck it.
After that i have try the twrp updated for viper rom and is working fine this one no problem for backup.
Click to expand...
Click to collapse
it has been fixed on new version!!

JEANRIVERA said:
it has been fixed on new version!!
Click to expand...
Click to collapse
Got it! , I will try it! Can you tell me if you flash permanent the recovery you still can flash a ruu later without do anything else? Also on the viper rom you suggest to flash your Touchscreen hexpatcher ? with flashing the header patch from venom or only the kernel pie 0.2 from venom i am not sure with what i have read..
Thanks you!

Max128 said:
Got it! , I will try it! Can you tell me if you flash permanent the recovery you still can flash a ruu later without do anything else? Also on the viper rom you suggest to flash your Touchscreen hexpatcher ? with flashing the header patch from venom or only the kernel pie 0.2 from venom i am not sure with what i have read..
Thanks you!
Click to expand...
Click to collapse
RUU should always works if done properly regardless of whatever you flash in your phone, and the hexpatcher will be only needed if you are on stock kernel, if you are using a custom kernel, then use the patch from venom

JEANRIVERA said:
RUU should always works if done properly regardless of whatever you flash in your phone, and the hexpatcher will be only needed if you are on stock kernel, if you are using a custom kernel, then use the patch from venom
Click to expand...
Click to collapse
I have asking it for to be sure, because some of my old phones like the htc 10 when you flashing a bootloader without a red text you should restore the original bootloader for flashing a ruu or a firmware if i am remember correctly.. I am pretty sure you are already know that but is for why i have asking it.
For my other question , so i am assuming the viper is on a custom kernel so i know now what files flashing.

Max128 said:
I have asking it for to be sure, because some of my old phones like the htc 10 when you flashing a bootloader without a red text you should restore the original bootloader for flashing a ruu or a firmware if i am remember correctly.. I am pretty sure you are already know that but is for why i have asking it.
For my other question , so i am assuming the viper is on a custom kernel so i know now what files flashing.
Click to expand...
Click to collapse
Rom and kernel are 2 different things, you can flash viper Rom and have stock kernel, or you can flash a custom kernel, custom kernel do no need the hexpatcher only stock kernel does regardless of the Rom you are using

JEANRIVERA said:
Rom and kernel are 2 different things, you can flash viper Rom and have stock kernel, or you can flash a custom kernel, custom kernel do no need the hexpatcher only stock kernel does regardless of the Rom you are using
Click to expand...
Click to collapse
Of course i know rom and kernel is a different things. I was thinking since the viper is not a official rom is need a custom kernel.

Max128 said:
Of course i know rom and kernel is a different things. I was thinking since the viper is not a official rom is need a custom kernel.
Click to expand...
Click to collapse
it doesn't requires a custom kernel, it is completely optional, just remember, if you stay on stock kernel, then you will need hexpatcher, if you use custom, as far as i know there are 3 available, CleanSlate, Kirisakura, & Beyond Stock, any of those 3 you will no need to use the hexpatcher

JEANRIVERA said:
it doesn't requires a custom kernel, it is completely optional, just remember, if you stay on stock kernel, then you will need hexpatcher, if you use custom, as far as i know there are 3 available, CleanSlate, Kirisakura, & Beyond Stock, any of those 3 you will no need to use the hexpatcher
Click to expand...
Click to collapse
Got it.
I have forget to tell you since your recovery is a port from twrp, when I write you about the bugs the other days, after that I have take the last twrp I have make a full backup with no errors , more later I have restored my backup with... I had got a bootloop on htc logo every times, I have trying to fix it but nothing to do... I was forced to install again the viper rom after that I was able to restore the data partition and is worked. Probably a bug in twrp restored, I am guessing probably have this bug on your recovery also.

@JEANRIVERA, thanks for the great job and maintaining TWRP!
I assume, it is still not possible to do a data backup on Pie (without this one)?

KotTHECat said:
@JEANRIVERA, thanks for the great job and maintaining TWRP!
I assume, it is still not possible to do a data backup on Pie (without this one)?
Click to expand...
Click to collapse
Not possible, this recovery is based on TWRP, every limitations on TWRP will also be here, Devoting HTC stock Pie at the moment is not supported by TWRP, but you can Decrypt AOSP Pie Encryption for example GSI ROMS based on PHH work like ViperExperience,

@JEANRIVERA I have done what you said and i have a problem , I have flash your recovery after that i have flash your touch patch and magisk.. reboot.. Android work fine.. ( except I was forced to delete some files in the recovery about the lockscreen , he didn't want let me to put again my password.. ) after that i has put again my password.. )
The problem now is on the recovery i boot it from the bootloader, the recovery stays on the logo pitch for a long time after that is said to me to put my password i enter it but it never want to decrypt the data. So i do not know why the recovery do not want the decrypt the data and why is stay so long on pitch logo every times. I have not flashing viper patch because is for custom kernel.

Max128 said:
@JEANRIVERA I have done what you said and i have a problem , I have flash your recovery after that i have flash your touch patch and magisk.. reboot.. Android work fine.. ( except I was forced to delete some files in the recovery about the lockscreen , he didn't want let me to put again my password.. ) after that i has put again my password.. )
The problem now is on the recovery i boot it from the bootloader, the recovery stays on the logo pitch for a long time after that is said to me to put my password i enter it but it never want to decrypt the data. So i do not know why the recovery do not want the decrypt the data and why is stay so long on pitch logo every times. I have not flashing viper patch because is for custom kernel.
Click to expand...
Click to collapse
please send me a screenshot of settings>about phone>Android Version

[ROM][10][OFFICIAL] Lineage 17.1 NIGHTLY for MOTO G5. (Cedric)

OFFICIAL LINEAGE OS 17.1 NIGHTLIES
LineageOS Downloads
download.lineageos.org
The most recent build was dated 25th Feb 2021. [Edit UPDATED to most recent build date].
The previous offerings were 2021-01-28; 2021-02-04 ; 2021-02-11; 2021-02-18.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CEDRIC WIKI
Info about cedric | LineageOS Wiki
wiki.lineageos.org

Hi, I tried to install it on OPP28.85-19-4-2 but the installation failed (infinite loop at start-up). According to this https://wiki.lineageos.org/devices/cedric/install the latest Android 8.1 firmware is required. Which one is it ? Thanks !

QRXpMUvS said:
Hi, I tried to install it on OPP28.85-19-4-2 but the installation failed (infinite loop at start-up). According to this https://wiki.lineageos.org/devices/cedric/install the latest Android 8.1 firmware is required. Which one is it ? Thanks !
Click to expand...
Click to collapse
Any oero firmware will do as your base
Flash via fastboot - if you don't know which to choose use the latest retail version
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
How to flash rom
Go to twrp
Select wipe
Format data - option on the right (will format everything on phone including personal files so backup first!)
Restart to twrp
Wipe then advanced wipe
Wipe system data and cache
Select install from main menu
Install rom zip
Install gapps (you want arm64 android 10 nano)
Install magisk (optional for root access & to hide apps from detecting root/custom rom)
Wipe delvik cache
Restart
Encrypt phone again if required once booted from phone settings menu

Thanks, I did as you explained, but I am still stuck with a lineageos logo looping for a few dozens of minuts before the phone restarts and goes straight to TWRP.

QRXpMUvS said:
Thanks, I did as you explained, but I am still stuck with a lineageos logo looping for a few dozens of minuts before the phone restarts and goes straight to TWRP.
Click to expand...
Click to collapse
Wipe system data cache and flash rom without gapps or magisk
Does it boot?
If yes wipe everything again and flash rom zip but flash gapps as well this time. And if it boots flash magisk (no need to wipe to flash magisk)
If magisk causes it to boot loop flash an older version
If none of the above works and you have the same issue trying to flash another rom eg lineage mint then its user error somewhere or an issue unrelated to the rom zip

Hi,
i updated my G5 to the official LOS. Although VoWifi and VoLTE are enabled in settings, none of them are working (They didn't work on the unofficial version either).
According to my network operator, these functions are activated.
Unter Phone Info (*#*#4636#*#* in dialer's app) it says "IMS Registration: Not Registered"
Is there anything I can do about this?
Thanks!

TheFixItMan said:
Wipe system data cache and flash rom without gapps or magisk
Does it boot?
If yes wipe everything again and flash rom zip but flash gapps as well this time. And if it boots flash magisk (no need to wipe to flash magisk)
If magisk causes it to boot loop flash an older version
If none of the above works and you have the same issue trying to flash another rom eg lineage mint then its user error somewhere or an issue unrelated to the rom zip
Click to expand...
Click to collapse
I tried without gapps and magisk, it does not boot, same with Mint.
So if I understand well, the problem is probably on my side
What I did :
New firmware using fastboot following these commands.
At this stage, TWRP had disappear (!), I reinstalled it using fastboot. Is it normal ?
Then I installed lineageos.

QRXpMUvS said:
I tried without gapps and magisk, it does not boot, same with Mint.
So if I understand well, the problem is probably on my side
What I did :
New firmware using fastboot following these commands.
At this stage, TWRP had disappear (!), I reinstalled it using fastboot. Is it normal ?
Then I installed lineageos.
Click to expand...
Click to collapse
I have the same problem. I can't get Lineage or Mint to boot on my Cedric.
I've tried TWRP 3.4 , and 3.5 and neither made a difference. I have been through the instructions on the lineage site many times, and I'm sure I'm not missing a step
But every time the device sticks at lineage boot logo for a long time, before returning to fastboot mode.
If I re-flash 8.1 using fastboot, the phone works again, then go from the top with twrp and lineage, and we're back to logo and eventually fastboot again.
So, although I cannot help yet, you are not alone.
Edit:
My cedric is the 3GB RAM XT1676 model which I think might be somewhat rare version?

HarpingOn said:
So, although I cannot help yet, you are not alone.
Click to expand...
Click to collapse
Thanks ! By chance, do you know any unofficial rom (not necessarely 17.1) correctly booting on 8.1 ?

QRXpMUvS said:
Thanks ! By chance, do you know any unofficial rom (not necessarely 17.1) correctly booting on 8.1 ?
Click to expand...
Click to collapse
I have only tried mint and official 17.1. Get the same problem with both sadly.

I just realised, on the installation instructions it says to flash the recovery from the lineage download page, not twrp
So I tried:
motog5> fastboot flash recovery lineage-17.1-20210225-recovery-cedric.img
target reported max download size of 535822336 bytes
Sending 'recovery' (18390 KB)...
OKAY [ 0.586s]
Writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
The cedric recovery image on the download page is about 2MB larger than the TWRP recovery.
So should I be using the lineage provided recovery to flash this?
edit:
I managed to get the cedric to boot the lineage supplied recovery by doing:
motog5> fastboot boot lineage-17.1-20210225-recovery-cedric.img
I then used that recovery (looks good by the way, smart looking recovery), but after flashing the matching lineage-17.1 image ( adb sideload lineage-17.1-20210225-nightly-cedric-signed.zip) , I still get the long running boot animation, and dumped back into bootloader after a while.
I think I should stop now, I'm getting tired

For your info everyone: the OP is not the developer. I am neither. I just patch the official builds and that is Mint.

HarpingOn said:
I just realised, on the installation instructions it says to flash the recovery from the lineage download page, not twrp
So I tried:
motog5> fastboot flash recovery lineage-17.1-20210225-recovery-cedric.img
target reported max download size of 535822336 bytes
Sending 'recovery' (18390 KB)...
OKAY [ 0.586s]
Writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
The cedric recovery image on the download page is about 2MB larger than the TWRP recovery.
So should I be using the lineage provided recovery to flash this?
edit:
I managed to get the cedric to boot the lineage supplied recovery by doing:
motog5> fastboot boot lineage-17.1-20210225-recovery-cedric.img
I then used that recovery (looks good by the way, smart looking recovery), but after flashing the matching lineage-17.1 image ( adb sideload lineage-17.1-20210225-nightly-cedric-signed.zip) , I still get the long running boot animation, and dumped back into bootloader after a while.
I think I should stop now, I'm getting tired
Click to expand...
Click to collapse
If you could give me logs, I'll check.

nift4 said:
If you could give me logs, I'll check.
Click to expand...
Click to collapse
My problem was that I was starting from the GB release of Cedric stock 8.1 as I'm in the UK. If I flashed the GB version, then no Lineage ROM would boot. Not this, and not the Mint one.
If you check out the Mint thread, what I did was use Fastboot to flash an international version of stock 8.1, then I could add TWRP and flash this successfully.
I ended up testing Lineage With microG, but actually successfully flashed this, and Mint as well.
So I'd say to anyone struggling to get a working flash of this ROM, try a different CEDRIC set of fastboot files.

as im aware, you need to flash from stock 8.1 but sometimes if youre on pie you gotta flash nougat and then oreo to flash custom roms i tried flashing that rom before but got no succes with bootlop but i didnt knew this i have tried unnoficial los 17 but never though about trying again the one from los page, guess its Worth a try

update: i got to flash and boot but the system reboots randomly, mostly when i open apps
also twitter doesnt login into my account for a weird reason dunno why. guess ill loke other roms around

Lighto97 said:
update: i got to flash and boot but the system reboots randomly, mostly when i open apps
also twitter doesnt login into my account for a weird reason dunno why. guess ill loke other roms around
Click to expand...
Click to collapse
You need to been on oreo firmware to flash this rom - preferably the latest retail version
You also need gapps that are arm64 android 10 nano
See my instructions above for how to flash rom correctly (post #3)
Without any logs the devs will put it down to user error

TheFixItMan said:
You need to been on oreo firmware to flash this rom - preferably the latest retail version
You also need gapps that are arm64 android 10 nano
See my instructions above for how to flash rom correctly (post #3)
Without any logs the devs will put it down to user error
Click to expand...
Click to collapse
oh damm i always forgot i have to send the log for them to track the issue, i already uninstaled anyway.
i did followed the steps the right way (thank you), right now im flashing stock nougat to try out LOS 14.1 (which i love and seems to be reeealy stable)

thank you very much to all involved for this … this gives a new lease of life to the moto g5. i tried both the official version and a microg4lineageos build - both work flawlessly afaict.
a few observations:
camera works, both photos and videos. the new camera app is quite usable.
coming from a build derived from codezeros 16.0-tree, i had to revert to the stock firmware to be able to install this. not doing so resulted in boot loops, wiping everything did not help
the los recovery cannot be flashed, it seems to be too big for the recovery partition. twrp works fine.

tfbb said:
thank you very much to all involved for this … this gives a new lease of life to the moto g5. i tried both the official version and a microg4lineageos build - both work flawlessly afaict.
a few observations:
camera works, both photos and videos. the new camera app is quite usable.
coming from a build derived from codezeros 16.0-tree, i had to revert to the stock firmware to be able to install this. not doing so resulted in boot loops, wiping everything did not help
the los recovery cannot be flashed, it seems to be too big for the recovery partition. twrp works fine.
Click to expand...
Click to collapse
i know how to boot with that LOS recovery, instead of flash comand you use boot command so the device will bot into recovery suing the image.

[ROM][SM-T510][UNOFFICIAL] LineageOS 19.1 for Galaxy Tab A 10.1 (2019)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 19.1 I just created based on the latest OEM stock firmware and @AndyYan's latest LineageOS 19.1 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even more custom ROMs for this tablet.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and this one is based on the latest Android 11 release (T510XXU5CWA1).
Stock recovery will be replaced with my latest TWRP build for the SM-T510.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
lineage-19.1-20230403-UNOFFICIAL-T510XXU5CWA1.tar.md5 (Odin tarball)
lineage-19.1-20230403-UNOFFICIAL-T510XXU5CWA1.zip (TWRP update)
Build archives:
Android File Host
Change Log:
20230403:
Updated to LineageOS 19.1 GSI (20230323) with March 2023 security patch and GApps.
Based on the latest Android 11 OEM kernel and vendor partition (T510XXU5CWA1).
Includes TWRP v3.7.0 custom recovery built on AOSP 11.
20220918:
Initial release based on LineageOS 19.1 GSI (20220912) with Sept. 2022 security patch and GApps.
Based on the latest Android 11 OEM kernel and vendor partition (T510XXU5CVG2).
Includes TWRP v3.6.2 custom recovery built on AOSP 11.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
If TWRP launches, factory reset with Wipe->Format Data and reboot to system. (Not necessary for incremental upgrades.)
From existing TWRP install:
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, Install Image, select your update (.img file), and then swipe to install
Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
Source:
android_device_samsung_gta3xlwifi
treble_build_los
Phh-Treble
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!

Reserved

Thank you dear @Magendanz very much for keeping my Old Youtube Tab Alive!
Quick Question, is an update from "lineage-18.1-20220417-UNOFFICIAL-T510XXU5CVB1.zip" to the new 19.1 Possible or do i have to update the base version first?

Good evening Mr. Magendanz,
i installed this ROM on my Samsung SM-T510 and my tab/back/home buttons are not in the middle/bottom position they are in the right corner (i had this issue also with another unffocial lineage Os 19.1 Rom for SM-T510)
How can i solve this ?

NJey90 said:
Good evening Mr. Magendanz,
i installed this ROM on my Samsung SM-T510 and my tab/back/home buttons are not in the middle/bottom position they are in the right corner (i had this issue also with another unffocial lineage Os 19.1 Rom for SM-T510)
How can i solve this ?
Click to expand...
Click to collapse
Is the task bare active? I have the same layout when it is. You can turn it off in settings, but research the bar, you might want to use it.

@Magendanz , I dirty installed it over my lineageos gsi, and it works great so far. One problem I see, and had with the gsi is that I have a notification to finish installation, but there is no way to get past the network selection. There is no button to either skip or continue. Is there a way to fix this?
Thank you for this - I know how hard it is given your other responsibilities!

Thanks Magendanz for this news!
Coming from LineageOS 17.1 (lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN), what would be the sequence of steps for updating to this rom ?
Thanks.

galoneta said:
Coming from LineageOS 17.1 (lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN), what would be the sequence of steps for updating to this rom ?
Click to expand...
Click to collapse
I recommend you download and install the T510XXU5CVG2 firmware, do a clean install with Odin...but intercept the restart by holding Vol Up & Down so that you reenter Download mode. Then, install this custom ROM with Odin and intercept the restart by holding Power + Vol Up to enter TWRP. From there, do a factory reset and reboot to system.
If you inadvertently miss the restart intercept and have to run through OEM setup, make sure to connect to the Internet and then enter Developer options to disarm Vaultkeeper. Don't try to flash anything else until you've verified the OEM Unlock is still on (but disabled).

Magendanz said:
I recommend you download and install the T510XXU5CVG2 firmware, do a clean install with Odin...but intercept the restart by holding Vol Up & Down so that you reenter Download mode. Then, install this custom ROM with Odin and intercept the restart by holding Power + Vol Up to enter TWRP. From there, do a factory reset and reboot to system.
If you inadvertently miss the restart intercept and have to run through OEM setup, make sure to connect to the Internet and then enter Developer options to disarm Vaultkeeper. Don't try to flash anything else until you've verified the OEM Unlock is still on (but disabled).
Click to expand...
Click to collapse
Thanks Magendanz for this clarifying tutorial!
So you must first always update \ have the samsung base AND the custom recovery to a MINIMUM combination set? In this case the minimum "combo" set would be a samsung rom with android 11 as base (and recovery 3.6) right ?
Will try this sequence and give feedback as soon as possible.
Thanks again.

Hey there, just wondering -- does hardware video acceleration work on this build seeing as its based on a GSI? Thanks

I tried to flash this on T515 via twrp. Seems like it only detect and allow install on t510

Can you also make a variant for sm-t515?
Cheers and thanks

dissidius said:
Can you also make a variant for sm-t515?
Cheers and thanks
Click to expand...
Click to collapse
In the ten or so years I've been dealing with Samsung tablets and XDA, I must have seen this question asked at least a hundred times. "Can you make the wifi ROM work on the LTE version?" of whatever tablet or vice versa. And the answer is always "No." They are two different animals and normally the dev has one or the other. And it is very difficult to make a ROM for a device you don't have. And the same thing goes for tablets with the S Pen. They are NOT the same.

lewmur said:
In the ten or so years I've been dealing with Samsung tablets and XDA, I must have seen this question asked at least a hundred times. "Can you make the wifi ROM work on the LTE version?" of whatever tablet or vice versa. And the answer is always "No." They are two different animals and normally the dev has one or the other. And it is very difficult to make a ROM for a device you don't have. And the same thing goes for tablets with the S Pen. They are NOT the same.
Click to expand...
Click to collapse
of course mate i like your passion in explaining such things but i belive *i can be wrong of course* that i wasn't asking on a Xiaomi Poco thread..... this two devices are very much similar, smt510 twrp works correcly on smt515 for example. Just maybe the rom could also work with some little tweaks. Thanks

dissidius said:
of course mate i like your passion in explaining such things but i belive *i can be wrong of course* that i wasn't asking on a Xiaomi Poco thread..... this two devices are very much similar, smt510 twrp works correcly on smt515 for example. Just maybe the rom could also work with some little tweaks. Thanks
Click to expand...
Click to collapse
Yes, TWRP can work on both but recovery doesn't access the LTE modem. And, again, I'm stating MY experience from over ten years of having people ask the question about many, many SAMSUNG tablets only.

Has anyone successfully installed MindTheGApps on lineageos19? did you use an sdcard or adb or some other method? I don't have access to an sdcard but I am curious if this is the only way. I have not been successful in using adb..... yet!

This version of Lineage 19 already has Gapps installed. So MindtheGapps is not needed. Installing it using the tar ball and Odin means you don't need an SD card. Or have I missed something?

dissidius said:
Can you also make a variant for sm-t515?
Cheers and thanks
Click to expand...
Click to collapse
I installed this on my T515 via TWRP and it worked just fine. Haven't tried LTE though, but the os installed perfectly.

DingusestDingus said:
I installed this on my T515 via TWRP and it worked just fine. Haven't tried LTE though, but the os installed perfectly.
Click to expand...
Click to collapse
Scratch that, I restarted it and its now in a bootloop

This is the 2019 version. I can't get this to install. Bootloader is unlocked and tablet is rooted

Better Mobile App

welcome