[ROM][10.0][OFFICIAL]LineageOS 17.1[guacamoleb] - OnePlus 7 ROMs, Kernels, Recoveries, & Other Devel

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
https://download.lineageos.org/guacamoleb
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Common Device tree: Here
Device tree: Here
Kernel tree: Here
XDA:DevDB Information
guacamoleb-lineage, ROM for the OnePlus 7
Contributors
ash4win
Source Code: https://github.com/lineageos
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 10
Based On: AOSP
Version Information
Status: Nightly
Created 2020-06-03
Last Updated 2020-06-21

Reserved

Reserved

Excellent work @ash4win :highfive:
I tried it the following way coming from OxygenOS with encrypted storage:
Backup everything off your device!
1. Remove lockscreen pin from OxygenOS which removes encryption too to prevent mounting issues of internal storage (I'm doing this every time)
2. Reboot to TWRP
3. Wipe System and Data partition
4. Flash Lineage OS
5. Flash TWRP installer(the same as your TWRP, otherwise you will end up in LineageOS TWRP)
6. Flash Magisk
7. Reboot TWRP
8. Flash Gapps (BIT/Opengapps)
9. Format data within TWRP
10. Reboot

Thank you for your hard work !

Can someone plz mention the exact full steps to install it, I haven't tried any custom rom on oneplus 7 yet, currently am running latest oos
I have read the op, but confused after formating data can i flash directly the lineage rom or have to flash oos rom then lineage rom
Thanks in advance

ZenR2 said:
Can someone plz mention the exact full steps to install it, I haven't tried any custom rom on oneplus 7 yet, currently am running latest oos
I have read the op, but confused after formating data can i flash directly the lineage rom or have to flash oos rom then lineage rom
Thanks in advance
Click to expand...
Click to collapse
Please see above

Can someone tell me how to update the rom when current version is rooted and magisk installed.
Can we update the rom directly via Lineage os updater along with magisk.
I have installed 31-5 build and somehow i messed with the update process and stuck in bootloop.

Cehmu77 said:
Can someone tell me how to update the rom when current version is rooted and magisk installed.
Can we update the rom directly via Lineage os updater along with magisk.
I have installed 31-5 build and somehow i messed with the update process and stuck in bootloop.
Click to expand...
Click to collapse
Updating via ota rewrites the bootimage, hence removing magisk.
If u want to update and still have magisk, i suggest u use a recovery.

ash4win said:
Updating via ota rewrites the bootimage, hence removing magisk.
If u want to update and still have magisk, i suggest u use a recovery.
Click to expand...
Click to collapse
Tq for the reply.
So now tell me how do i update lineage os when rooted with magisk.
I would like to use this rom as my daily driver. Can you pls provide the update installation procedure.

ash4win said:
Updating via ota rewrites the bootimage, hence removing magisk.
If u want to update and still have magisk, i suggest u use a recovery.
Click to expand...
Click to collapse
I found that installing magisk to inactive slot after installing ota update but before reboot as you would do with oos updates still preserves magisk. No need to reflash it in twrp.

ash4win said:
Updating via ota rewrites the bootimage, hence removing magisk.
If u want to update and still have magisk, i suggest u use a recovery.
Click to expand...
Click to collapse
Can you provide the installation steps.
I have magisk installed and i would like to update along with magisk.

Cehmu77 said:
Can you provide the installation steps.
I have magisk installed and i would like to update along with magisk.
Click to expand...
Click to collapse
After updating the rom you should be good to go with installing the twrp installer and then flash magisk.
This should work :good:

Cehmu77 said:
Can you provide the installation steps.
I have magisk installed and i would like to update along with magisk.
Click to expand...
Click to collapse
Boot to twrp
Flash rom
Flash twrp installer
Reboot to recovery
Flash gapps
Flash Magisk
Reboot to System

New build: Here
-Improved Fingerprint on Display

Hi! Thanks for all your hard work on this ROM. I have a question about installing this.
I'm currently on Oxygen OS 10.3.1 with TWRP and Magisk. I would like to install LineageOS without gapps (or any google services) and add microg. I want to see what it's like to use an Android phone without Google.
Do you have any suggestions for how to do this? Will Nanodroid work with this, or is there a better method of adding microg to this install?
Thanks for any help.

strongst said:
Excellent work @ash4win :highfive:
I tried it the following way coming from OxygenOS with encrypted storage:
Backup everything off your device!
1. Remove lockscreen pin from OxygenOS(I'm doing this every time)
2. Reboot to TWRP
3. Wipe System and Data partition
4. Flash Lineage OS
5. Flash TWRP installer(the same as your TWRP, otherwise you will end up in LineageOS TWRP)
6. Flash Magisk
7. Reboot TWRP
8. Flash Gapps (BIT/Opengapps)
9. Format data within TWRP
10. Reboot
Click to expand...
Click to collapse
Hi... Can you give link which twrp version you use with this build.

deani77 said:
Hi... Can you give link which twrp version you use with this build.
Click to expand...
Click to collapse
Sure, it's from here https://forum.xda-developers.com/on...nofficial-twrp-recovery-t3932943/post79585368 the installer file twrp-3.3.1-79-guacamole-unified-installer-mauronofrio.zip

strongst said:
Sure, it's from here https://forum.xda-developers.com/on...nofficial-twrp-recovery-t3932943/post79585368 the installer file twrp-3.3.1-79-guacamole-unified-installer-mauronofrio.zip
Click to expand...
Click to collapse
Thanks.... Haven't flash any custom rom since using OP7... Feeling itchy hand now

micro_cat said:
Hi! Thanks for all your hard work on this ROM. I have a question about installing this.
I'm currently on Oxygen OS 10.3.1 with TWRP and Magisk. I would like to install LineageOS without gapps (or any google services) and add microg. I want to see what it's like to use an Android phone without Google.
Do you have any suggestions for how to do this? Will Nanodroid work with this, or is there a better method of adding microg to this install?
Thanks for any help.
Click to expand...
Click to collapse
Need to have signature spoofing. I am also looking for help, if any senior member can guide.

Related

[ROM] [ ANGLER ] AICP 14.0 | Pie 9.0.rX | OFFICIAL WEEKLIES

{
"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"
}
AICP
Android Ice Cold Project​
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then evolved into a mature ROM with the BEST community you can find!!!
Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM when it comes to hardware, drivers and some features.
With the rebrand of CM to LineageOS (LAOS) we are now actually LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so no need to report errors or bugs to them!!
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. Hard & a lot.
*
*/
W. I. P.
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
@razorloves and @sam3000 for their awesome work with all Nexus devices & LineageOS
DU team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 13.1
Download link: AICP Downloads
By the download link
It's a Nexus - You tell...
FAQ:​
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see, if your device is build on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
A. No. You can still use them (as long as they are LOS based), but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Xposed is not yet available for nougat (officialy), however there are unofficial versions. You will need to use the version arm64/arm for SDK 25.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I dirty flash builds?
A. Wipe System, Cache and ART/Dalvik cache. Flash the ROM, your preferred root solution and reboot. Or you might just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. Boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot", then swipe to flash, then go back to the install screen and install your root method again if you don't want to loose root, and then reboot.
A2. LOS based kernels sometimes come as a flashable ZIP file too. You can flash them together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue, if you don't want to loose root. Now swipe to flash, clear Cache & ART/Dalvik cache and then reboot.
Using the ROM:
Q. How do I enable software buttons?
A. Settings -> Navigation -> Enable navigation bar. The bar can be configured separately in its settings.
Q I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A In TWRP, flash the substratum rescue zip in the substratum folder on the internal storage.
Q I keep losing root with Magisk, how do I fix it?
A Check this out, if that doesn't work for you ask for help in this thread, read or ask in the Magisk thread on XDA or just flash Magisk again!
Q I'm having issues with WhatsApp, how do I fix it?
A Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the root section in the AICP Extras menu.​
​The ROM should contain everything you need to enjoy Android Oreo. You don't need to install any Add-Ons, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How To Flash:​
(Again: Don't do it if you don't know it!)​
1. Download needed Factory Images from Google (bootloader, radio and vendor) OR from my 2nd post (Current: 8.1.0 (OPM7.181205.001, Dec 2018)) and flash them via FASTBOOT in Bootloader Mode.
2. Download the ROM, GApps and Magisk 18.0 (or higher) (Optional) then transfer them to your device
2a. Google Apps: I'm using micro package from OpenGAPPS. Also you can find the link for latest GAPPS in my 3rd post.
3. Boot to recovery (TWRP recommended)
4. Wipe system, Cache, data and ART/Dalvik cache
5. Flash ROM Zipfile
6. Flash/Install GApps (optional, needed for e.g. Google Playstore to work)
7. Flash/Install the root solution of choice (optional) - Magisk 18.0 or higher versions works pretty nice!
8. Reboot to system
PREREQUISITE FOR OTA:
To be able to flash using the buildin OTA app that needs TWRP recovery installed to work.
You can still use LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery.
Zip gets saved in the "AICP_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery.​
The ROM has GApps persistance in between dirty flashes, so you only have to flash them once!
No need to flash root solution on every OTA update (= ROM Update) If you are on Magisk 18.0 or higher!
Supported Root Solutions:​
Magisk v18.0 or higher​
KERNEL:
The kernel in this ROM follows LineageOS source with custom additions from AICP, AOSP and Android Community.
https://github.com/AICP/kernel_huawei_angler
If you want to contribute to the AICP or wanna see what is being worked on/merged, feel free to visit our Gerrit review system. (Link is at the bottom!!!)
ROM & Additional links:
Gerrit Code Review
Github
IceColdJelly AICP G+ community
Contributors
(mention all the devs who have contributed to your device tree, kernel, vendor, etc,
only mention the main ones though, probably the top four or so, otherwise this list will be a mile long unless if you're a huge kanger xD)
ROM OS Version: 9.0.x Oreo
ROM Kernel: Linux 3.10.xxx
Version Information
Status: NIGHTLY
Stable Release Date: Not released yet
Creation date: 04-10-2017
Last Updated: Nightly
You want to see a normal night at the "DEV office", click here!!​
XDA:DevDB Information
[ROM] [ ANGLER ] AICP 14.0 | Pie 9.0.rX | OFFICIAL WEEKLIES, ROM for the Huawei Nexus 6P
Contributors
semdoc, GreekDragon, LorD ClockaN, wartomato
Source Code: https://github.com/AICP
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 8.1.0 (OPM7.181205.001, Dec 2018)
Based On: GZOSP
Version Information
Status: Nightly
Stable Release Date: 2019-03-03
Created 2017-10-04
Last Updated 2019-03-13
Reserved
Notice: We are shipping vendor.img into ROM.zip. No need to flash any stock image on new ASB's with Pie Builds !!!​
Just make sure you are on Dec 2018 Stock images while you are starting....
******************************************************************************************************************************************************
For Oreo Builds (AICP 13.1):
Stock Images to be flashed via FASTBOOT
ASB Dec 2018 Stock Images: 8.1.0 (OPM7.181205.001, Dec 2018)
******************************************************************************************************************************************************
How to get my Fi Project SIM Discovered ? all credits goes to @flashblue. Please go and thank him
flashblue said:
I'd suggest these steps to get your Project Fi SIM discovered:
1. Go to post #1 and install the ROM completely following the instructions.
2. Setup your phone, but skip the window about inserting the SIM card.
3. When your phone is setup (it will be without Fi service) go to settings and choose security.
4. Make sure you select "none" as the security option. You don't want a pin for sure.
5. Reboot into "Recovery" and follow the steps in post #1 to install the ROM and Vendor image.
6. Your phone should boot normally and discover the Fi SIM card.
As you can see from my post count I am new at helping anyone. Hopefully I did this right
Click to expand...
Click to collapse
Reserved
1. GAPPS:
Go for latest Open GAPPS micro package.
**********************************************************************************************************************************************************************************
Recomendation for Google Camera Mods: You can find the latest here (I'll try to keep this folder updated)
Feel free to use any of them.
d.
jenkins is building angler currently... So new nightly will be available in 40 minutes...
Site still doesnt show aicp 13.0 to downloand.
Update : showing now, changelog link isnt working though
Second. Thanks
Does substratum work on this?
is this an unofficial lineage os 15? dont understand the 13
tejkumarvusirikala said:
Site still doesnt show aicp 13.0 to downloand.
Update : showing now, changelog link isnt working though
Click to expand...
Click to collapse
http://dwnld.aicp-rom.com/?device=angler
Jiggs82 said:
Does substratum work on this?
Click to expand...
Click to collapse
Nope. Not implemented yet.
hanschke said:
is this an unofficial lineage os 15? dont understand the 13
Click to expand...
Click to collapse
This is internal AICP Number. So. This is AICP Oreo edition....
First I would like to say Thank you for sharing the rom. Quick question though. Will there be a flashable zip eventually? Don't have access to a laptop.
atrix2man said:
First I would like to say Thank you for sharing the rom. Quick question though. Will there be a flashable zip eventually? Don't have access to a laptop.
Click to expand...
Click to collapse
This ROM is a flashable zip. http://dwnld.aicp-rom.com/?device=angler&type=all
Are the AICP EXTRA available in this build ?
ultyrunner said:
This ROM is a flashable zip. http://dwnld.aicp-rom.com/?device=angler&type=all
Click to expand...
Click to collapse
Well in the OP it states that it's a fastboot file. I can flash in recovery?
Edit: nevermind, he updated the OP from earlier
atrix2man said:
Well in the OP it states that it's a fastboot file. I can flash in recovery?
Click to expand...
Click to collapse
It would depend on what you're coming from what you need to flash and how. If you're on Nougat, then you'd have to fastboot flash the October radio and bootloader and maybe the vendor to be safe. In fact, it's better to flash the full factory image for a completely new Android release, then flash a custom ROM.
The OP has always said the ROM is a zip, as all custom ROMs are. You have to flash the radio and bootloader with fastboot, but you can flash any of the other IMG file partitions with TWRP and flashable zips.
There's a 7 point guide in the OP that's very clear about installation.
atrix2man said:
Well in the OP it states that it's a fastboot file. I can flash in recovery?
Edit: nevermind, he updated the OP from earlier
Click to expand...
Click to collapse
Templates were really outdated... Sorry for confusion... Now all should be fine ?
ROM itself is flashable via recovery zip. Although, factory images for bootloader, radio and vendor should be flashed via fastboot in bootloader mode.
To All:
You may want to test open commits on Gerrit with some new additions:
Link:
https://drive.google.com/file/d/0B1z9h6r3XzxTREU4NUM1VFkyOEE/view?usp=drivesdk
If you are on oreo build already, flash dirty, clean caches and reboot.
This is my current build already - it has same build date whit the build from Jenkins while it includes open changes...
Cheerz
Welcome. :fingers-crossed::fingers-crossed::fingers-crossed:
semdoc said:
Templates were really outdated... Sorry for confusion... Now all should be fine
ROM itself is flashable via recovery zip. Although, factory images for bootloader, radio and vendor should be flashed via fastboot in bootloader mode.
To All:
You may want to test open commits on Gerrit with some new additions:
Link:
https://drive.google.com/file/d/0B1z9h6r3XzxTREU4NUM1VFkyOEE/view?usp=drivesdk
If you are on oreo build already, flash dirty, clean caches and reboot.
This is my current build already - it has same build date whit the build from Jenkins while it includes open changes...
Cheerz
Click to expand...
Click to collapse
Thanks man! Downloading now
Jiggs82 said:
Does substratum work on this?
Click to expand...
Click to collapse
Why wouldn't it? Legacy mode works on 8.0
Thanks for your efforts. I flashed this last night and it is almost flawless so far. Except there is no night light. How can I enable night light in this ROM?
WoW thanks for AICP oreo.. One doubt..
semdoc said:
The ROM has GApps persistance in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)!
Click to expand...
Click to collapse
I am not getting this.. does that mean after this build whenever we have to dirty flash the new build, we have to flash only the Rom ( root/kernel optional) and no need to flash gapps evrytime I dirty update to a new build?
Sorry for a dumb question.:silly:
Thanks!

[ROM] [marlin] [8.1] [LOS-based] **crDroid**OMS**v4.7 (10/12/18)

ROM thread text:
This is crDroid for 5.5" Pixel XL [marlin]
crDroid Website: https://crdroid.net/
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. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
Vendor image for current build - OPM4 July vendor image - DOWNLOAD VENDOR
GAPPS: For now, open gapps unofficial, also courtsey @razorloves - DOWNLOAD GAPPS
OpenGapps: Not Supported anymore, use @razorloves gapps.
First time installing crDroid to your PixelXL, or coming from another ROM:
**NOTE** As you probably know by now, marlin (and sailfish) is weird. You must be on TWRP 3.2.0.0 to install this! 3.2.1.0 does not allow ROM installation. 3.2.0.0 does not encrypt properly, so you must remove your PIN/password before booting to and / or installing it. These installation instructions will assume you already know and have done that.
**NOTE** You are also able to use 3.2.1.-2 (3.2.0.0 or 3.2.1.-2)(Nothing in between)
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Copy crDroid zip, gapps zip & vendor img to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
5) Flash TWRP ***If you do not do this, you will lose TWRP!***
6) Reboot back into TWRP
7) Flash vendor image
7a) Mount vendor partition, navigate to vendor/overlay and delete that folder
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk 16.2
If you like music like I do and want to make it better, see post #3 for instructions on installing ViPER4Android.
Instructional Video
I Apologize about video quality, but this will help get you an idea of the steps involved.
Steps are the same for Marlin and Sailfish. Use corresponding files for device.
https://youtu.be/mmxIrp7BiRk
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.
KNOWN ISSUES
None yet, If you find something that is consistently reproducible, do so and pull a log. Without logs, we cannot fix the bugs. Please report any that you run into, assuming you have tested on a clean install. :good:
NOTE ON SUBSTRATUM
We currently do not have substratum commits in the ROM because they have not updated their repos on git for Oreo. As such, if you want to use Substratum, you will be doing so by allowing root and using legacy mode. you -must- make sure whatever theme you try supports 8.1. Even some that say they support Oreo may only work with 8.0, not 8.1. I'd recommend the following:
Suggestion: whenever installing themes, remove your pin/password so you can get TWRP to mount data.
If you get in a FC/bootloop situation, boot to TWRP, mount data and remove the file /data/system/overlays.xml.
That should allow you to boot and uninstall the overlays without reinstalling anything.
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- @razorloves - Without his device tree and kernel bringup to work from, crDroid for marlin would not be possible at all. Apart from the ROM development itself (for which @neobuddy89 bears the largest burden, in addition to the great developers of LineageOS itself), credit for this ROM being able to even build goes to razorloves.
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE
crDroid G+ community​
Source Code:
Device tree: https://github.com/razorloves/android_device_google_marlin
Kernel tree: https://github.com/razorloves/android_kernel_google_marlin
Vendor tree: https://github.com/razorloves/proprietary_vendor_google
Credit for all of those trees goes to @razorloves , without whose work crDroid for marlin would be a shell of itself!
XDA:DevDB Information
[ROM] [marlin] [8.1] [LOS-based] **crDroid**v4.7, ROM for the Google Pixel XL
Contributors
hokiealumnus, neobuddy89, BHermes21, razorloves
Source Code: https://github.com/crdroidandroid
ROM OS Version: 8.x Oreo
Version Information
Status: Nightly
Current Stable Version: v4.0
Stable Release Date: 2018-03-23
Beta Release Date: 2018-01-19
Created 2018-01-09
Last Updated 2018-10-12
I already said it in my post above, but feel it needs repeating. HUGE thanks to @razorloves , without whose marlin bring-up this ROM would still not be built.
*** NOTE - We cannot actively support audio (or any other) mods. I'm posting this because it works for me and I use it personally. This is not supported by our ROM team. Only the ROM / vendor / gapps and nothing else is supported by the crDroid development team. ***
If you like music as much as I do and prefer to use Viper4Android, install it as follows:
0) This requires Magisk; install Magisk 15.2 (as of 1/9/2018)
1) Using a root explorer (I prefer FX File Explorer), navigate to /system/system/priv-app/AudioFX and rename AudioFX.apk to AudioFX.BAK. Reboot.
2) Install three Magisk modules:
a) Magisk SELinux Permissive Script (Get it here: https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549)
b) Busybox for Android NDK v1.27.2 by osm0sis (Get it from Magisk downloads in the Magisk app)
c) ViPER4Android FX v2.8 by ahrion, zackptg5 (Also from Magisk downloads)
3) Reboot.
4) Enjoy your better music!
Sweet thanks
Awesome! I know I asked this on the nougat version, does the unlimited photo storage work? I noticed on the unofficial LOS rom by @razorloves it's been enabled, but I wanted to confirm. I'm still running nougat because I've been waiting for an oreo rom that has DUI.
hokiealumnus said:
This is crDroid for 5.5" Pixel XL [marlin]
If you're looking for the 5" Pixel [sailfish], it is not built yet; sorry.
Click to expand...
Click to collapse
Yet...... Hahaha there's still hope! Thanks for your work as always man. crDroid on N was solid as it gets!
Awesome thank you. Flashing now
Akomack said:
Awesome! I know I asked this on the nougat version, does the unlimited photo storage work? I noticed on the unofficial LOS rom by @razorloves it's been enabled, but I wanted to confirm. I'm still running nougat because I've been waiting for an oreo rom that has DUI.
Click to expand...
Click to collapse
It -says- it does in Photos. However, it said it did in Nougat, but never did actually work in any LOS / LOS-based ROM. It took up storage space even though the Photos app said back up all you want with Pixel. Therefore I can't promise full functionality. The app does say it works though.
thebigdonny said:
Yet...... Hahaha there's still hope! Thanks for your work as always man. crDroid on N was solid as it gets!
Click to expand...
Click to collapse
No promises on a time frame though I'm sorry to say!
hokiealumnus said:
No promises on a time frame though I'm sorry to say!
Click to expand...
Click to collapse
Soon TM
Added instructions for using Viper4Android in the 3rd post while they're still working on a functioning ARISE.
Works very good only one force close which I just uninstalled and reinstalled anyway been running du 12.0 nice change thanks
hokiealumnus said:
If you like music as much as I do and prefer to use Viper4Android, install it as follows:
0) This requires Magisk; install Magisk 15.2 (as of 1/9/2018)
1) Using a root explorer (I prefer FX File Explorer), navigate to /system/system/priv-app/AudioFX and rename AudioFX.apk to AudioFX.BAK. Reboot.
2) Install three Magisk modules:
a) Magisk SELinux Permissive Script (Get it here: https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549)
b) Busybox for Android NDK v1.27.2 by osm0sis (Get it from Magisk downloads in the Magisk app)
c) ViPER4Android FX v2.8 by ahrion, zackptg5 (Also from Magisk downloads)
3) Reboot.
4) Enjoy your better music!
Click to expand...
Click to collapse
Bruh, gimme the credit, if u want atmos and any other mod for 8.1 here's the link https://forum.xda-developers.com/pixel-xl/how-to/guide-ultimate-audio-battery-guide-t3727124/page1
kingbri said:
Bruh, gimme the credit, if u want atmos and any other mod for 8.1 here's the link https://forum.xda-developers.com/pixel-xl/how-to/guide-ultimate-audio-battery-guide-t3727124/page1
Click to expand...
Click to collapse
Why would I give you credit? I've never even seen that post.
Are there any custom kernels that will work with this ROM right now?
Sent from my Pixel XL using Tapatalk
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
*Update*
For those of you that get stuck at this point and run into bootloops, instead of Wiping Cache, System & Data manually, just simply hit "Factory Reset" instead. and continue with OP's flashing instructions and you should be good.
Thanks so much, Hokie! Packed with features, really appreciate all of the detailed instructions! Thank you!
Herk718 said:
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
Click to expand...
Click to collapse
Yes that is normal
Herk718 said:
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
Click to expand...
Click to collapse
Yep normal.
Reboot recovery. Flash gapps/vendor reboot.
Giving this a whirl. Thanks OP!!!
Herk718 said:
@hokiealumnus After flashing Rom and Twrp, then I hit reboot to recovery, its says "No OS Installed" on the reboot screen. Is that normal?
*Update*
For those of you that get stuck at this point and run into bootloops, instead of Wiping Cache, System & Data manually, just simply hit "Factory Reset" instead. and continue with OP's flashing instructions and you should be good.
Click to expand...
Click to collapse
Aye, that is normal. It just means you don't have vendor installed, which you can't do until rebooting back to TWRP (so it switches slots).
Factory reset does not wipe system partition. If you are coming from a different ROM, when you switch slots, you are leaving a different ROM on your inactive slot. Not a huge deal, but I don't recommend it.
Edit - The best way to avoid stressing about that is to allow the reboot, but interrupt boot (pwr + vol down), and go right to recovery from the bootloader.
BHermes211 said:
Are there any custom kernels that will work with this ROM right now?
Click to expand...
Click to collapse
Maybe? I haven't tried installing one yet. ElementalX has always worked well in the past, indeed I always built nougat crDroid with it. Just haven't tried it on Oreo.
If you want to try installing it, worst it will do is bootloop. Just dirty flash (wipe only cache/system, leave data, repeat normal install) back to the included kernel.

[ROM][9.0.0_r30] crDroid v5.0 [UNOFFICIAL]

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. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
DOWNLOAD GAPPS
First time installing crDroid to your Moto G5, or coming from another ROM: <--THESE MAY NEED UPDATING FOR YOUR PARTICULAR DEVICE; BE THOROUGH IN INSTRUCTIONS-->
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Copy crDroid zip, gapps zip to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
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.
KNOWN ISSUES
You tell me
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- ENTER-SPECIFIC-THANKS-HERE-IF-YOU-HAVE-THEM
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
crDroid G+ community
Source Code: https://github.com/crdroidandroid
Device tree: https://github.com/Fedray/android_device_motorola_cedric/tree/lineage-16.0
Kernel: https://github.com/Sohamlad7/android_kernel_motorola_msm8937/tree/lineage-16.0
Vendor: https://github.com/Sohamlad7/android_vendor_motorola_cedric/tree/lineage-16.0
ROM OS Version: 9.0.0 Pie
Based On: LineageOS 16
Version Information
Status: Stable
Current Stable Version: 5.0
Stable Release Date: 2019-01-21
Last Edit Date: 2019-01-21
Changelog:
20/1/2019
-Initial build
biometric sensor working?
Screenshots?
Welcome back @Fedray ROM works flawlessly so far!
Joseph3546 said:
biometric sensor working?
Click to expand...
Click to collapse
Yes, of course, it works on every rom.
lucki1000 said:
Screenshots?
Click to expand...
Click to collapse
I will upload when I have time.
mrfrantastic said:
Welcome back @Fedray ROM works flawlessly so far!
Click to expand...
Click to collapse
Thanks Glad to hear that!
Fedray said:
Yes, of course, it works on every rom.
I will upload when I have time.
Thanks Glad to hear that!
Click to expand...
Click to collapse
Whats the chance to go offical with this ROM?
fedray back at it again with another stable rom, good to see you post something once in a while
Thanks for this ROM, I already relied on you worh on the Moto G, Fedray!
Any advice what to do if Quickstep launcher fc at startup? Wiping cache/dalvik is problematic because trwp can not decrypt the data partition. Btw: Does anybody usw a twrp version abel to decrypt it?
Did someone successfully managed to install Magisk? After I flash it, it always does not appear in Magisk Manager. Manager claims it is not installed and offer to do it, but this also does not work.
sambahb said:
Did someone successfully managed to install Magisk? After I flash it, it always does not appear in Magisk Manager. Manager claims it is not installed and offer to do it, but this also does not work.
Click to expand...
Click to collapse
Uninstall magisk install magisk start if app not in the list extract the zip and install the app manually, and if the app say additional setup needed install it again without uninstall.
lucki1000 said:
Uninstall magisk install magisk start if app not in the list extract the zip and install the app manually, and if the app say additional setup needed install it again without uninstall.
Click to expand...
Click to collapse
Is there a place, where this manually is described better? I am not sure, what you exactly mean.
sambahb said:
Is there a place, where this manually is described better? I am not sure, what you exactly mean.
Click to expand...
Click to collapse
Okay, you should uninstall magisk over TWRP then you install magisk via TWRP, then make a restart and boot into crdroid, if magisk app not avaible, then go to the magisk.zip and install manually the magisk.apk (who is in the zip) and if you get a report in the magisk app like this additional setup needed or similar you reboot into TWRP and install magisk again and reboot into crdroid that should work.
lucki1000 said:
Okay, you should uninstall magisk over TWRP then you install magisk via TWRP, then make a restart and boot into crdroid, if magisk app not avaible, then go to the magisk.zip and install manually the magisk.apk (who is in the zip) and if you get a report in the magisk app like this additional setup needed or similar you reboot into TWRP and install magisk again and reboot into crdroid that should work.
Click to expand...
Click to collapse
This is exactly what I did about 5 times. First I always had to install Magisk Manager manually because it was not available. After install Manager told me that Magisk is not installed and there is the possibility from within the app. Download worked, but installwise nothing happend. It looks like it does not event try
sambahb said:
This is exactly what I did about 5 times. First I always had to install Magisk Manager manually because it was not available. After install Manager told me that Magisk is not installed and there is the possibility from within the app. Download worked, but installwise nothing happend. It looks like it does not event try
Click to expand...
Click to collapse
You install it start system and if you get magisk is not installed then go again to TWRP and install magisk, (without uninstall or any wipe or something else only install magisk again) if this also not work ask in the magisk thread.
when I will get official built. This ROM is loving. please built official version as soon as possible. Thanks to developer.
Anyone else constantly experiencing system UI crashes?
Will there be an update to 5.1?
Thanks to the developer, great ROM!
Hi.
I have upgraded from crdroid 8 to this rom and losted biometric sensor.
It does not appear at Configurations, the Moto Actions configurations don't work for finger gestures.
It was working at previous crdroid version.
I did a clean install.
Any suggestion on how to make it work again?
Lrd-Nero said:
Anyone else constantly experiencing system UI crashes?
Will there be an update to 5.1?
Thanks to the developer, great ROM!
Click to expand...
Click to collapse
Same problem.
diogopetermann said:
Hi.
I have upgraded from crdroid 8 to this rom and losted biometric sensor.
It does not appear at Configurations, the Moto Actions configurations don't work for finger gestures.
It was working at previous crdroid version.
I did a clean install.
Any suggestion on how to make it work again?
Click to expand...
Click to collapse
Flash this using the TWRP to make your fingerprint work again: https://drive.google.com/file/d/1e_8alb2MFX7uXqjYZ7OruCCImbYIge1r/view

[ROM] Dirty Unicorns 14.7 {Marlin} (09/13/20)

{
"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"
}
About Us:
Dirty Unicorns is an AOSP based project built to enhance the stock Android experience.
Our focus has been and is always to contribute back to the community. That is ultimately why we do what we do.
We DO NOT accept, nor ask, for donations. We do not believe in that. Everything that is necessary to keep this project going comes out of our own pocket. This includes, but is not limited to; Devices, Gerrit, our websites and services, etc.. The only thing that we ask in return is that you have patience, search the thread for answers prior to posting, read diligently, and try to enjoy the process with us!
Kernel Source:
https://github.com/DirtyUnicorns/android_kernel_google_marlin
Flashing Instructions:
If you have a device that uses TWRP
Verify that you're using the latest version of TWRP
Perform a FULL WIPE: (A full wipe is when you wipe system/data/cache/dalvik)
Flash the latest version of this ROM
Flash vendor image (once only to both slots if coming from another ROM) via bootloader:
Code:
fastboot flash --slot all vendor vendor.img
Reboot and ENJOY!
If you have a device that does not use TWRP
Download boot.img and ROM zip from DU server
Reboot into bootloader and flash the boot.img
Code:
fastboot flash --slot all boot boot.img
Reboot to recovery
Go to recovery select factory reset
Select Apply update from ADB to flash the zip
Code:
adb sideload nameofbuild.zip
Flash vendor image (once only) via bootloader:
Code:
fastboot flash --slot all vendor vendor.img
Reboot and ENJOY!
If you're just updating DU on a device without TWRP
Download ROM zip from DU server
Reboot into recovery and select Apply update from ADB to flash the zip
Reboot system now and ENJOY!
**All bugs and feature requests must be reported to JIRA**
**If you use Xposed, please don't bother reporting any bugs**
**If you use another kernel, please don't bother reporting any bugs**
**If you fail to follow these instructions, please don't bother reporting any bugs**
Download Links:
Build(s) - Marlin
Other Links:
ROM Source - https://github.com/DirtyUnicorns
Gerrit - http://gerrit.dirtyunicorns.com
Crowdin (translations) - https://crowdin.net/project/dirtyunicorns
JIRA (Bug Reporting / Feature Requests) - http://jira.dirtyunicorns.com/
Telegram - https://t.me/dirtyunicorns / https://t.me/DirtyUnicornsSupport
XDA:DevDB Information
Dirty Unicorns, ROM for the Google Pixel XL
Contributors
NYCHitman1
Source Code: https://github.com/DirtyUnicorns
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.7
Stable Release Date: 2020-09-13
Created 2020-08-08
Last Updated 2020-09-13
one of the BEST ROMS for Marlin, loving it
imna357 said:
one of the BEST ROMS for Marlin, loving it
Click to expand...
Click to collapse
Is it available for Sailfish or can this build can be flash on Sailfish
rom
thanks
kiran8631 said:
Is it available for Sailfish or can this build can be flash on Sailfish
Click to expand...
Click to collapse
Sorry, Marlin only.
Cool beans.....
Tried a few rom from other developers but the battery drains fast. This one have no problem. Thanks for good rom.
Was anyone able to install Magisk?
Whenever I try to install Magisk I get stuck in a Bootloop at the Google Logo.
Doesn't matter if I do KEEPFORCEENCRYPT=true & KEEPVERITY=true in the .magisk for or false.
Wanted to test disable DM-Verity but TWRP is unable to mount /system_root (Neither TWRP 3.4.0.0 or 3.3.1 work)
My Phone has an encrypted Storage if that helps narrowing down the issue
Darthsternie said:
Was anyone able to install Magisk?
Whenever I try to install Magisk I get stuck in a Bootloop at the Google Logo.
Doesn't matter if I do KEEPFORCEENCRYPT=true & KEEPVERITY=true in the .magisk for or false.
Wanted to test disable DM-Verity but TWRP is unable to mount /system_root (Neither TWRP 3.4.0.0 or 3.3.1 work)
My Phone has an encrypted Storage if that helps narrowing down the issue
Click to expand...
Click to collapse
Try using the orangefox recovery when flashing the magisk, never had this issue
Ok this looks sick. Gunna flash tonight.
Darthsternie said:
Was anyone able to install Magisk?
Whenever I try to install Magisk I get stuck in a Bootloop at the Google Logo.
Doesn't matter if I do KEEPFORCEENCRYPT=true & KEEPVERITY=true in the .magisk for or false.
Wanted to test disable DM-Verity but TWRP is unable to mount /system_root (Neither TWRP 3.4.0.0 or 3.3.1 work)
My Phone has an encrypted Storage if that helps narrowing down the issue
Click to expand...
Click to collapse
Magisk 19.3 installed without any issue using twrp 3.4.0.0
bhaskarjyotisarmah51 said:
Magisk 19.3 installed without any issue using twrp 3.4.0.0
Click to expand...
Click to collapse
So you have TWRP permanently installed on Android 10? I can't get it to work
GalaxyWhy said:
So you have TWRP permanently installed on Android 10? I can't get it to work
Click to expand...
Click to collapse
download both files, twrp.img and the twrp.zip, fastboot boot twrp.img then once in TWRP flash the twrp.zip...note, make sure to remove any PIN, password or any security on the ROM first, or else it will not decrypt:good:
GalaxyWhy said:
So you have TWRP permanently installed on Android 10? I can't get it to work
Click to expand...
Click to collapse
No TWRP permanently installed. Temporary boot into TWRP using fastboot flashed magisk.
Magisk 19.3 or 20.4 both work
Just don't set any pin/password lock on the rom
imna357 said:
download both files, twrp.img and the twrp.zip, fastboot boot twrp.img then once in TWRP flash the twrp.zip...note, make sure to remove any PIN, password or any security on the ROM first, or else it will not decrypt:good:
Click to expand...
Click to collapse
Does that mean that you actually managed it to install TWRP permanently on a Pixel XL running the latest version on any Android 10 ROMs?
And what about when there's an OTA available. Do you have to reflash it then?
I'm seriously impressed, because TWRP themselves said flashing TWRP on Android 10 wouldn't be possible yet (at least on Marlin)
And last, but not least, can I put the pin/password/safety features back to activation after I installed TWRP?
Help The Peace said:
Does that mean that you actually managed it to install TWRP permanently on a Pixel XL running the latest version on any Android 10 ROMs?
And what about when there's an OTA available. Do you have to reflash it then?
I'm seriously impressed, because TWRP themselves said flashing TWRP on Android 10 wouldn't be possible yet (at least on Marlin)
And last, but not least, can I put the pin/password/safety features back to activation after I installed TWRP?
Click to expand...
Click to collapse
How you mangaed to install TWRP on Android 10?
When I flashed TWRP after installing custom rom my phone won't boot. I have to flash a stock image to make it boot.
Help The Peace said:
Does that mean that you actually managed it to install TWRP permanently on a Pixel XL running the latest version on any Android 10 ROMs?
And what about when there's an OTA available. Do you have to reflash it then?
I'm seriously impressed, because TWRP themselves said flashing TWRP on Android 10 wouldn't be possible yet (at least on Marlin)
And last, but not least, can I put the pin/password/safety features back to activation after I installed TWRP?
Click to expand...
Click to collapse
Yup, I'm on Bliss rom right now, tried all except GSI treble. When I'm doing update, I reboot to TWRP and wipe system and cache then flash the new update afterwards flash TWRP.ZIP again.
Can't install TWRP permanently, you need to flash it everytime you are doing an upgrade, that's just me
GalaxyWhy said:
So you have TWRP permanently installed on Android 10? I can't get it to work
Click to expand...
Click to collapse
Head back over to the TWRP screen on your phone and swipe the slider that says "Swipe to Allow Modifications" if needed. Now you should be sitting on the TWRP main menu where you can then go into the "Advanced" section. From there, tap the "Install Recovery Ramdisk" option, and finally, navigate to the "Download" folder where you copied the TWRP image file.
Tap the image file once to bring up the "Install Recovery" main screen and check the "Back up existing image first" option to backup your current recovery for safekeeping. Now slide the "Swipe to Install" button at the bottom to begin installing the permanent version of TWRP onto your system partition. After it finishes installing, press the home button, go to "Reboot," then "Recovery".
Help The Peace said:
Does that mean that you actually managed it to install TWRP permanently on a Pixel XL running the latest version on any Android 10 ROMs?
And what about when there's an OTA available. Do you have to reflash it then?
I'm seriously impressed, because TWRP themselves said flashing TWRP on Android 10 wouldn't be possible yet (at least on Marlin)
And last, but not least, can I put the pin/password/safety features back to activation after I installed TWRP?
Click to expand...
Click to collapse
Yep i got it working, had to flash "twrp-pixel-installer-marlin-3.3.0-0.zip" and not the latest... dunno why but hey, it works!
rodken said:
Head back over to the TWRP screen on your phone and swipe the slider that says "Swipe to Allow Modifications" if needed. Now you should be sitting on the TWRP main menu where you can then go into the "Advanced" section. From there, tap the "Install Recovery Ramdisk" option, and finally, navigate to the "Download" folder where you copied the TWRP image file.
Tap the image file once to bring up the "Install Recovery" main screen and check the "Back up existing image first" option to backup your current recovery for safekeeping. Now slide the "Swipe to Install" button at the bottom to begin installing the permanent version of TWRP onto your system partition. After it finishes installing, press the home button, go to "Reboot," then "Recovery".
Click to expand...
Click to collapse
Does this work with latest TWRP as of june?
*EDIT*
Doesn't but "twrp-3.3.0-0-marlin.img" works following rodken's guide. Cheers!
https://mobile.twitter.com/_DirtyUnicorns_/status/1300601420903854080

[ROM][UNOFFICIAL][G770F/FD][11] LineageOS 18.1 S10 Lite

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the changelog for a full list of changes & features.
DISCLAIMER: LineageOS Legal
Requirement: Oneui 3.0 (DTL1).
Instructions:
Flash Lineage Recovery or grab the files from the download below and use the instruction from there to flash it
Format Data/Factory Reset
Flash the build (Use adb sideload, or push the file to sdcard with mtp)
Reboot
Notes:
VoLTE, IMS, and other samsung specific stock rom features wont be ported or fixed.
Download:
r5q 18.1
r5q recovery
Support Group: Telegram
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
I do this kind of stuff on my free time. If you like my work, please consider buying me a drink (donation) by clicking the link below.
Paypal
Archive link: Github Releases
Kernel source: Github
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
I think i had to mention this, booting recovery now requires you to have usb plugged in while you're punching the recovery combo to enter recovery.
Also, i've fixed the lineage recovery yesterday, sorry for the hassle.
New release are up! New release have a new repo right here https://github.com/mainey/r5q-archive/releases , hopefully this would be less confusing for the end users to find files needed. The old repo would now only releases new vendor updates from samsung.
New build: https://github.com/mainey/r5q-archive/releases/tag/ROM-20210121
note: i might or might not announce new builds in the future all the time, if you want to be notified when releases are published, make sure to click the watch button on the top right on the github repo page
What's handy?
How did you patch boot.img and root the ROM?
Is there a how-to for noobs? I guess all my knowledge on how to flash custom ROMs from 2 years ago are completely useless after all.
Thanks!
immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
Ok, I found the instructions for patching boot.img:
[HOW-TO-ROOT] [G770F/DS] Galaxy S10 Lite International Model
Models: SM-G770F or SM-G770F/DS Frequently used key combinations keys: FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button. DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via...
forum.xda-developers.com
darth.cabs said:
What's handy?
How did you patch boot.img and root the ROM?
Is there a how-to for noobs? I guess all my knowledge on how to flash custom ROMs from 2 years ago are completely useless after all.
Thanks!
Click to expand...
Click to collapse
Got new account nice to be here too..
Vaughnn said:
我想我不得不提一下,启动恢复现在需要您在插入恢复组合以进入恢复时插入USB。
另外,我昨天修复了血统恢复,很抱歉给您带来麻烦。
Click to expand...
Click to collapse
Vaughnn said:
LineageOS是免费的,社区构建的Android 11售后固件发行版,旨在提高设备的现有Android的性能和可靠性。
LineageOS基于Android开源项目,并得到了Android社区中许多人的额外贡献。无需安装任何Google应用程序即可使用它。下面链接的是一个来自另一个Android项目的程序包,这些程序可以还原Google部件。LineageOS仍然包含各种特定于硬件的代码,无论如何它们也正在缓慢地开源。
LineageOS的所有源代码都在LineageOS GitHub中提供。如果您想为LineageOS做出贡献,请访问Gerrit Code Review。您还可以查看更改日志以获取更改和功能的完整列表。
要求: Oneui 3.0(DTL1)。
指示:
Flash Lineage Recovery或从下面的下载文件中获取文件,然后使用此处的说明对其进行刷新
格式化数据/恢复出厂设置
刷新构建(使用adb侧载,或使用mtp将文件推送到sdcard)
重启
笔记:
请勿使GAPP闪烁,这包括最小的GAPP。我将发布带有gapps的版本,直到gapps程序包足够适合我的需求为止。
VoLTE,IMS和其他三星特定的rom功能将不会移植或修复。
在使用指纹之后或之前,屏幕有时会闪烁,这只是免责声明,如果有人使用此版本的癫痫病患者,我将不承担任何责任
错误:
接近度(可能无法在某些应用程序上运行)
5Ghz热点
下载:
r5q 18.1
r5q恢复
支持小组: 电报
报告错误
如果您正在运行自定义内核或已安装Xposed,请不要报告错误
问题发生后立即拿起logcat。(除非您知道自己在做什么,否则请至少包括日志的几页,而不仅仅是最后几行。)
如果是随机重新引导,请抓住/ proc / last_kmsg。(除非您在重新启动之前就可以获取它,否则不要费心获取一个logcat。重新启动之后的logcat是没有用的)
如果从根shell运行“ setenforce 0”后问题消失了,请抓住/data/misc/audit/audit.log
Code:
您的-
LineageOS版本:
LineageOS下载网址:
Gapps版本:
你是否 -
擦拭:
使用钛备份还原:
出现问题后重新启动:
你正在用吗 -
任务杀手:
非库存内核:
其他修改:
根据需要提供任何其他信息(观察/问题发生的频率/它工作的最新版本/等):[/ CODE]
[B]我会在业余时间做这种事情。如果您喜欢我的工作,请考虑通过单击下面的链接为我买一杯饮料(捐赠)。[/B]
[URL='https://www.paypal.com/donate/?cmd=_donations&[email protected]']贝宝[/URL]
存档链接:[URL='https://github.com/mainey/release-r5q/releases']Github版本[/URL]
内核来源:[URL='https://github.com/mainey/android_kernel_samsung_r5q']Github[/URL]
[/QUOTE]
Hello, I would like to ask how my phone is currently Android 10 and One ui is 2.1. I want to change to LineageOS.
[/QUOTE]
Click to expand...
Click to collapse
immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
Hello, I would like to ask how my phone is currently Android 10 and One ui is 2.1. I want to change to LineageOS.
Rom is fine. There's simply not much to tell about. It runs runs runs. No problems at all. Twrp or lineageos recovery....whatever. all good
Would it be possible to have a version without Gapps?
Vaughnn said:
New release are up! New release have a new repo right here https://github.com/mainey/r5q-archive/releases , hopefully this would be less confusing for the end users to find files needed. The old repo would now only releases new vendor updates from samsung.
New build: https://github.com/mainey/r5q-archive/releases/tag/ROM-20210121
note: i might or might not announce new builds in the future all the time, if you want to be notified when releases are published, make sure to click the watch button on the top right on the github repo page
Click to expand...
Click to collapse
Is your lineageos 19 beta google-free?
Hi. Can anyone confirm if [BETA] Lineage 19 20220307 Beta 4 is stable enough as daily ROM?
Banking apps work? OIS+EIS during video recording?
Thank you.
Vaughnn said:
Requirement: Oneui 3.0 (DTL1).
Instructions:
Flash Lineage Recovery or grab the files from the download below and use the instruction from there to flash it
Format Data/Factory Reset
Flash the build (Use adb sideload, or push the file to sdcard with mtp)
Reboot
Click to expand...
Click to collapse
First of all thank you for your time and energy.
I'm having problem flashing latest beta 4.
I'm coming android 11 Oneui 3.1. My device is was rooted with unlocked bootloader.
1. I've flashed the lineage recovery via odin (Including vbmeta_disable) and upon reboot (it needed 2 boots to get into recovery) I chose factory reset of the device.
2. I've enabled developer options and saw my bootloader was unlocked.
3. I've booted into recovery
4. I've flashed the lienage os 19 beta 4 with google apps
I keep getting status error 2 and installation is aborted :O(

Categories

Resources