lineage 18.1 is EOL for this device. 19.1 is now available:
https://forum.xda-developers.com/t/...rosshatch-android12-1-lineageos-19-1.4380097/
{
"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, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki for more details.
Downloads:
pixel 3 - blueline: https://download.lineageos.org/blueline
pixel 3 xl - crosshatch: https://download.lineageos.org/crosshatch
gapps zip (arm64): (optional): https://wiki.lineageos.org/gapps.html
Google Fi addon: https://sourceforge.net/projects/ra...-gapps-addon-arm64-11.0-20210212.zip/download (if you're on Google Fi, install this zip right after installing gapps zip.)
Android Auto addon: https://sourceforge.net/projects/ra...-gapps-addon-arm64-11.0-20201121.zip/download (if you want android auto, install this after installing gapps zip. note: this is only needed with opengapps)
Initial Install Instructions:
https://wiki.lineageos.org/devices/blueline/install
https://wiki.lineageos.org/devices/crosshatch/install
Update Instructions:
https://wiki.lineageos.org/devices/blueline/update
https://wiki.lineageos.org/devices/crosshatch/update
Upgrade Instructions: (from 17.1 to 18.1)
https://wiki.lineageos.org/devices/blueline/upgrade
https://wiki.lineageos.org/devices/crosshatch/upgrade
Notes:
1. lineage-18.1 comes with adb root that you can enable in developer options, but if you want root for apps, you can grab the magisk apk and rename it to .zip and install it in lineage recovery.
An alternative install method is to follow these boot.img patching instructions. You can get the boot img directly from the lineage download site. It's labeled as the recovery img but it's actually the boot img.
2. The newest vendor, radio, & bootloader are included in the lineage rom zip, so no need to worry about updating those manually.
Known issues:
1. when you format data in lineage recovery, you might see "cant send spi message". you can ignore it.
2. there's an issue with sprint mobile data not working. we're looking into it. there's an easy workaround though. send me a pm and i'll walk you through it.
Changelog:
blueline
crosshatch
Bug reporting:
https://wiki.lineageos.org/bugreport-howto.html
Source Code:
crosshatch device tree: https://github.com/LineageOS/android_device_google_crosshatch/tree/lineage-18.1
blueline device tree: https://github.com/LineageOS/android_device_google_blueline/tree/lineage-18.1
kernel tree: https://github.com/LineageOS/android_kernel_google_msm-4.9/tree/lineage-18.1
vendor tree: https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-18.1
Credits:
Many thanks to my fellow LineageOS team members and all the contributors out there in the community.
Android version: 11
Kernel version: 4.9.248
Status: nightly
Lovely!
Beauty and the beast
Havent tried it but many thanks for the active development...
I loved this rom I hope it continues the development
Can I update to or dirty flash from lineage 17.1 to lineage 18 on pixel 3?
New build with November security patch level. :good:
blueline rom zip - https://androidfilehost.com/?fid=10763459528675579025
blueline boot img - https://androidfilehost.com/?fid=10763459528675579024
i still dont know if the crosshatch builds even work. no reports on it yet, so no new builds. waiting on you guys. lol
crosshatch rom zip - https://androidfilehost.com/?fid=10763459528675580134
crosshatch boot img - https://androidfilehost.com/?fid=10763459528675580133
On crosshatch alternate build it's working very smooth and incredible well for first build, so far the only problem it's that gaming heats faster than usual.
razorloves said:
New build with November security patch level. :good:
crosshatch - i still dont know if the crosshatch builds even work. no reports on it yet, so no new builds. waiting on you guys. lol
Click to expand...
Click to collapse
Thank you so much, it works fine on crosshatch, any updates are highly appreciated!
For me, it is an exclusion criteria if there is no root and no lineageos available for a device.
____
The only problem for me was to use the wrong version of Magisk ending up in a non booting device.
So if you update to lineage-18 and want to get root, you will want to take the canary version of magisk manager to patch the boot.img.
#Crosshatch
great to see the simplest rom available
it booted with the first link provided.
much obliged
I will use it and report my experience with it.
---------- Post added at 07:23 PM ---------- Previous post was at 07:21 PM ----------
beanaman said:
Can I update to or dirty flash from lineage 17.1 to lineage 18 on pixel 3?
Click to expand...
Click to collapse
its highly recommended to clean flash it since its in beta status
razorloves said:
New build with November security patch level. :good:
blueline rom zip - https://androidfilehost.com/?fid=10763459528675579025
blueline boot img - https://androidfilehost.com/?fid=10763459528675579024
crosshatch - i still dont know if the crosshatch builds even work. no reports on it yet, so no new builds. waiting on you guys. lol
Click to expand...
Click to collapse
What is the ADB command to flash gapps? I have only flashed ROMs with gapps included
Zehlek said:
What is the ADB command to flash gapps? I have only flashed ROMs with gapps included
Click to expand...
Click to collapse
Just side load the zip file for the gapps
razorloves said:
New build with November security patch level. :good:
blueline rom zip - https://androidfilehost.com/?fid=10763459528675579025
blueline boot img - https://androidfilehost.com/?fid=10763459528675579024
i still dont know if the crosshatch builds even work. no reports on it yet, so no new builds. waiting on you guys. lol
crosshatch rom zip - https://androidfilehost.com/?fid=10763459528675580134
crosshatch boot img - https://androidfilehost.com/?fid=10763459528675580133
Click to expand...
Click to collapse
Crosshatch boot img it won't boot, it will go straight to bootloader, know bugs so far lte status bar icons aren't present on Nov patch update
Thanks to Razor we have the opportunity to have LOS .
I'll try it after work ?
Can anyone confirm if Android Auto works with this? A lot of the Android 10 roms did not, and that was a huge deal breaker for me, as I use Android auto daily.
New builds with some changes and fixes.
blueline rom zip - https://androidfilehost.com/?fid=10763459528675581018
blueline boot img - https://androidfilehost.com/?fid=10763459528675581017
crosshatch rom zip - https://androidfilehost.com/?fid=10763459528675580705
crosshatch boot img - https://androidfilehost.com/?fid=10763459528675580704
significant changes:
added power menu options (advanced restart) - https://review.lineageos.org/q/topic:eleven-powermenu
added support for skipping tracks with remote control - https://review.lineageos.org/292052
fixed missing status bar icons on devices with a notch - https://review.lineageos.org/292038
lineage recovery won't boot.
Hi razorloves. Thanks for all your hard work. But I'm having serious issues booting into any lineage recovery (I've tried multiple nightly builds from 17.1 and multiple boot.img from this thread). All are failing. I do fastboot flash boot boot.img (I've also tried both boot_a and boot_b) but once i reboot it goes back into fastboot and give me an error with the boot img. Yet when I do htis with twrp-3.3.0-0-blueline.img i boot into twrp fine. (only issue there being that the zip files for lineage os fail to flash when installing from twrp. I've also tried with stock recovery and that give the same error as twrp).
I should also note that when i do fastboot boot boot.img the boot just hangs and never goes through.
Any suggestions?
tantonj said:
Hi razorloves. Thanks for all your hard work. But I'm having serious issues booting into any lineage recovery (I've tried multiple nightly builds from 17.1 and multiple boot.img from this thread). All are failing. I do fastboot flash boot boot.img (I've also tried both boot_a and boot_b) but once i reboot it goes back into fastboot and give me an error with the boot img. Yet when I do htis with twrp-3.3.0-0-blueline.img i boot into twrp fine. (only issue there being that the zip files for lineage os fail to flash when installing from twrp. I've also tried with stock recovery and that give the same error as twrp).
I should also note that when i do fastboot boot boot.img the boot just hangs and never goes through.
Any suggestions?
Click to expand...
Click to collapse
Razorloves contacted me directly and help me sort out the issue. My problem is I first needed to flash to the CORRECT stock rom. (I was using the oldest android 9 rom. for 17.1 I needed newest 10 rom, for this I needed newest 11 rom).
Thanks,
xFaultx said:
Can anyone confirm if Android Auto works with this? A lot of the Android 10 roms did not, and that was a huge deal breaker for me, as I use Android auto daily.
Click to expand...
Click to collapse
Android Auto is not working for me. Crashes immediately after opening. I attached a logcat that should contain three failures right in a row.
tantonj said:
Razorloves contacted me directly and help me sort out the issue. My problem is I first needed to flash to the CORRECT stock rom. (I was using the oldest android 9 rom. for 17.1 I needed newest 10 rom, for this I needed newest 11 rom).
Thanks,
Click to expand...
Click to collapse
Is this a step that everyone needs to follow when upgradeing from LineageOS 17.1 to 18, or only if your still on OEM?
beanaman said:
Can I update to or dirty flash from lineage 17.1 to lineage 18 on pixel 3?
Click to expand...
Click to collapse
the migration changes are still in-work, so something might go wrong if you don't wipe data. you can follow the progress here: https://review.lineageos.org/q/topic:"eleven-db-migration"
ktdt00 said:
Android Auto is not working for me. Crashes immediately after opening. I attached a logcat that should contain three failures right in a row.
Click to expand...
Click to collapse
thx for log. will look into it.
FeralG said:
Is this a step that everyone needs to follow when upgradeing from LineageOS 17.1 to 18, or only if your still on OEM?
Click to expand...
Click to collapse
only when you're on stock rom
Related
ROM thread text:
This is crDroid for 5" Pixel [sailfish]
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 Pixel, or coming from another ROM:
**NOTE** As you probably know by now, marlin and sailfish are 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 that stand out, 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 & sailfish 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] [sailfish] [8.1] [LOS-based] **crDroid**v4.7, ROM for the Google Pixel
Contributors
hokiealumnus, neobuddy89, BHermes21, The rest of the crDroid team
Source Code: https://github.com/crdroidandroid/
ROM OS Version: 8.x Oreo
Based On: LineageOS
Version Information
Status: Nightly
Current Stable Version: v4.0
Stable Release Date: 2018-03-23
Beta Release Date: 2018-01-19
Created 2018-01-20
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.
Also thanks to @almightysiman for confirming the ROM functions on sailfish.
Side note: You won't find BETA2 for sailfish. I skipped it so sailfish & marlin were on the same version number.
*** 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.x (whatever is most recent)
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!
Awesome! :fingers-crossed:
Does this rom have always on display? Didn't see it in the features list
Thanks to all involved who had a part in creating this ROM...
Sorry to be that guy but could someone briefly explain step 7a for me ? I've only flash one Rom so far on my pixel and it did not go smoothly to say the least...
bluedog220 said:
Sorry to be that guy but could someone briefly explain step 7a for me ? I've only flash one Rom so far on my pixel and it did not go smoothly to say the least...
Click to expand...
Click to collapse
You have to mount vendor (TWRP/Mount/Vendor, back), then go to Advanced / file manager/ navigate to /vendor/overlay. Choose delete, swipe right.
Gotta say, this is, so far, the perfect flashing experience in Oreo ROMs. I had no force-closes at setup, and no issues with the flashing process. So far, it has been great. Gonna use it for a few days, but as of now, this looks like my daily driver. Thanks again for this!
Does inlimited original quality photos work? Some ROMs I've noticed it doesn't work
shagbag913 said:
Does inlimited original quality photos work? Some ROMs I've noticed it doesn't work
Click to expand...
Click to collapse
We good! Working on mine.
stompysan said:
We good! Working on mine.
Click to expand...
Click to collapse
Thanks for checking! Sounds like this is going on my pixel
is this supposed to have the stock boot animation or did i screw something up?
shagbag913 said:
is this supposed to have the stock boot animation or did i screw something up?
Click to expand...
Click to collapse
Yep, stock boot animation, at least for now.
Are GAPPS required to avoid problems? FC's bootloops etc. Just wondering cause I don't run gapps anymore and know that some of our oreo roms need GAPPS to function properly
jacobas92 said:
Are GAPPS required to avoid problems? FC's bootloops etc. Just wondering cause I don't run gapps anymore and know that some of our oreo roms need GAPPS to function properly
Click to expand...
Click to collapse
No clue, never tried. That's like running half a ROM for me. You're welcome to try though. Please report back if you do.
Hello somehow started on the dark interface when I used the dark wallpaper nothing changed ?
pepa 77 said:
Hello somehow started on the dark interface when I used the dark wallpaper nothing changed ?
Click to expand...
Click to collapse
Did you delete the overlay folder from vendor?
The dark theme auto switcher was disabled by our Dev. It was causing issues. I'm not surprised it didn't switch for you, but definitely am surprised it was enabled at all.
hokiealumnus said:
Did you delete the overlay folder from vendor?
The dark theme auto switcher was disabled by our Dev. It was causing issues. I'm not surprised it didn't switch for you, but definitely am surprised it was enabled at all.
Click to expand...
Click to collapse
Thanks for clarifying the thing, this is a great Rom Congratulations.?
Really nice for a beta ?
Sent from my Pixel using XDA-Developers Legacy app
{
"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"
}
We’re really excited to announce the release of Paranoid Android Pie betas.
On the first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. For those who are unfamiliar, Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhances the overall user experience.
The beta builds include adjustments and improvements on top of the stock Android CAF base. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features.
Device-specific issues
- "Fingerprint Hardware Not Available" can occur
Note: Custom kernels are NOT supported!
Download
Get the latest Essential PH-1 build HERE.
Changelogs
Keep an eye on our Twitter account, @paranoidaospa , as we will be posting about new features getting included in the beta builds.
Paranoid Android Pie beta released
Instructions & requirements
- TWRP recovery image released by dees_troy doesn’t have touch support. To get around this, do
`adb shell twrp decrypt "YOUR PASSCODE"` if applicable
`adb push ROMNAME.zip /sdcard/Download`
`adb shell twrp install /sdcard/Download/ROMNAME.zip`
- After TWRP indicates its done flashing (using the TWRP installer):
`adb reboot`
Important / Useful links
OpenGapps
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Community (Telegram)
Help us improve PA by submitting good bug reports possibly with a log attached. Learn how to take logs here.
Our device maintainers for Essential PH-1 @Newtsrock, having @ggpew2 as a device contributor. Mention (@) them if you need some assistance and/or when reporting bugs.
Cheers and #StayParanoid!
XDA:DevDB Information
Paranoid Android, ROM for the Essential Phone
Contributors
herna, newtsrock, ggpew2
Source Code: https://github.com/StatiXOS/android_kernel_essential_msm8998
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2019-01-09
Last Updated 2019-02-22
Reserved
Reserved!
Reserved!
Reserved!
This is awesome! I first used PA back when it's biggest feature was navbar and status bar colors. Super excited to be downloading it now.
Is twrp not working due to the official release that hasn't been updated?
Anyone have screenshots?
Is there a reason for fastboot w? Is this rom currently decrypted?
Awesome. I do have one correction, though: most recent TWRP builds DO have touch support, mainly if it's installed via the flashable zip OR with the patched boot img for stock. Just figured I'd mention that.
dragynbane222 said:
Awesome. I do have one correction, though: most recent TWRP builds DO have touch support, mainly if it's installed via the flashable zip OR with the patched boot img for stock. Just figured I'd mention that.
Click to expand...
Click to collapse
Could you provide an link to the patched boot image? I never brought the twrp touchscreen to life when I tried using it from pie
the_Pan said:
Could you provide an link to the patched boot image? I never brought the twrp touchscreen to life when I tried using it from pie
Click to expand...
Click to collapse
Here is a link to the latest patched boot image: https://drive.google.com/file/d/1wMiQ1M_2ib9kMVpC1X7j7HdbR4MXhOJ9/view
Source: https://www.reddit.com/r/essential/...date_root_and_twrp/?utm_source=reddit-android
Looks like there's a bootloop issue installing magisk and flashing twrp from the installer zip to both partitions, anyone else have this issue?
Edit: Looks like after installing the ROM - it overwrites the recovery flash from the above-patched twrp (Jan-Patch from Reddit source), it then just forces the boot to hang.
Edit 2:Looks like I got it to work, after installing the ROM, reboot back into recovery mode, flash the jan-patch twrp img again using fastboot.
Edit 3: Nope looks like a persistent bootloop. Gonna leave this ROM alone until it gets magisk and a proper TWRP fixed
prozo said:
Looks like there's a bootloop issue installing magisk and flashing twrp from the installer zip to both partitions, anyone else have this issue?
Edit: Looks like after installing the ROM - it overwrites the recovery flash from the above-patched twrp (Jan-Patch from Reddit source), it then just forces the boot to hang.
Edit 2:Looks like I got it to work, after installing the ROM, reboot back into recovery mode, flash the jan-patch twrp img again using fastboot.
Edit 3: Nope looks like a persistent bootloop. Gonna leave this ROM alone until it gets magisk and a proper TWRP fixed
Click to expand...
Click to collapse
Looks like the boot loop issue is occurring on both this ROM and the AOSIP ROM, leads me to believe this might be an issue with the patched TWRP possibly?
Anybody able to get this working with gapps? If I flash the rom it boots fine. If I flash twrp with it, it boots fine. But once I try to flash gapps it just hangs on the aospa boot animation
I tried with opengapps pico and nano as well as simplegapps
prozo said:
Looks like the boot loop issue is occurring on both this ROM and the AOSIP ROM, leads me to believe this might be an issue with the patched TWRP possibly?
Click to expand...
Click to collapse
I'm running aosip rom at the moment. I use the twrp installer each and every time I flash something. In the same session
uodii said:
Anybody able to get this working with gapps? If I flash the rom it boots fine. If I flash twrp with it, it boots fine. But once I try to flash gapps it just hangs on the aospa boot animation
I tried with opengapps pico and nano as well as simplegapps
Click to expand...
Click to collapse
Same issue here, can't install it without getting the hang
---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------
Bobbaloo said:
I'm running aosip rom at the moment. I use the twrp installer each and every time I flash something. In the same session
Click to expand...
Click to collapse
Are we talking about the same thing? The patch image in this thread or the original TWRP img from the original TWRP website?
After installing I can no longer access adb or fastboot commands, tried multiple devices, they all still detect my V40 in ADB but not the PH-1, any idea why?
Thanks for the ROM all wok good
This is how I install it
Flash ROM from twrp
Flash twrp installer
Reboot to twrp
Flash magisk
Reboot to system
Reboot to twrp
Flash gapps (micro)
Done
English not my first language
the_Pan said:
Could you provide an link to the patched boot image? I never brought the twrp touchscreen to life when I tried using it from pie
Click to expand...
Click to collapse
Here you go: https://drive.google.com/file/d/1wMiQ1M_2ib9kMVpC1X7j7HdbR4MXhOJ9/view?usp=sharing
The folks on Reddit usually make a patched stock boot image front the stock not image for each month within a week of release
lineage 18.1 (android 11) builds are now available. See new thread here:
https://forum.xda-developers.com/t/...1-for-pixel-3-xl-blueline-crosshatch.4185847/
{
"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, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki for more details.
IMPORTANT NOTES:
1. Since TWRP doesn't work on Q for our device yet, you can use the lineage recovery. It's built into the rom's boot.img and is available separately on the download portal, named recovery image.
2. The newest vendor, radio, & bootloader img's are included in the rom zip, so no need to flash those manually.
3. Lineage comes with adb root that you can enable in developer options, but if you want root for apps, you can install the magisk apk, then follow these boot.img patching instructions. Use the file labeled 'recovery image' on the lineage rom download portal, which is actually just the boot.img. It is renamed to recovery to simplify the rom install steps.
Downloads:
blueline rom: https://download.lineageos.org/blueline
crosshatch rom: https://download.lineageos.org/crosshatch
gapps: (gapps are optional) - link / WARNING: Only use pico or nano gapps.
google fi gapps addon - if your carrier is Google Fi, flash this zip right after flashing gapps zip. https://androidfilehost.com/?fid=8889791610682871038
Instructions:
FOR INITIAL INSTALL
blueline: https://wiki.lineageos.org/devices/blueline/install
crosshatch: https://wiki.lineageos.org/devices/crosshatch/install
FOR UPDATING
For normal updating from official 17.1 to a newer official 17.1, follow these steps:
blueline: https://wiki.lineageos.org/devices/blueline/update
crosshatch: https://wiki.lineageos.org/devices/crosshatch/update
Protip: Enable "Prioritize update process" in the Updater preferences to make it go faster
Alternative manual updating instructions:
1. boot into lineage recovery.
2. install rom zip.
3. if you use gapps, select the "reboot into recovery" option, then install the gapps zips.
Changelog
blueline
crosshatch
Bug reporting
https://wiki.lineageos.org/bugreport-howto.html
Source Code:
crosshatch device tree: https://github.com/LineageOS/android_device_google_crosshatch/tree/lineage-17.1
blueline device tree: https://github.com/LineageOS/android_device_google_blueline/tree/lineage-17.1
kernel tree: https://github.com/LineageOS/android_kernel_google_msm-4.9/tree/lineage-17.1
vendor tree: https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-17.1
Credits:
Many thanks to my fellow LineageOS team members and all the contributors out there in the community. :good:
Android version: 10
Kernel version: 4.9.210
Status: Official Nightly
Nice! Running great so far.
Just about ready to get magisk installed.
Thanks @razorloves
razorloves said:
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki for more details.
IMPORTANT NOTES:
1. The install instructions below result in all of /data being wiped, so backup your stuff if it's important to you.
2. Since TWRP doesn't work on Q yet, you can use the aosp/lineage recovery. It's in the rom's boot.img and is available in the download sections below for initial rom install.
3. My builds include a minimal gapps (MindTheGapps).
4. The newest vendor, radio, & bootloader img's are included in my builds, so no need to flash those manually.
5. lineage-17.0 is new and still in-work, so some custom features from 16.0 have not been ported over yet.
6. If you want root you can install magisk using these instructions https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Downloads:
blueline rom = https://androidfilehost.com/?fid=4349826312261647887
blueline boot img = https://androidfilehost.com/?fid=4349826312261647886
crosshatch rom = https://androidfilehost.com/?fid=4349826312261647891
crosshatch boot img = https://androidfilehost.com/?fid=4349826312261647892
Initial Install Instructions:
1. Enter this command while In bootloader mode 'fastboot flash boot boot.img', then select 'Recovery mode' with vol & power buttons.
2. Select 'Wipe data/factory reset'. (Note: This wipes EVERYTHING on the /data partition, including internal storage.)
3. Select "Apply update from ADB', then follow on screen instruction to sideload the rom zip. It will say "completed with status 0" on the screen when the sideload has finished successfully.
Update Instructions:
1. If you're already on lineage rom, reboot into recovery mode.
2. Select "Apply update from ADB', then follow on screen instruction to sideload the rom zip.
Source Code:
crosshatch device tree: https://github.com/LineageOS/android_device_google_crosshatch/tree/lineage-17.0
blueline device tree: https://github.com/LineageOS/android_device_google_blueline/tree/lineage-17.0
kernel tree: https://github.com/LineageOS/android_kernel_google_msm-4.9/tree/lineage-17.0
vendor tree: https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-17.0
miscellaneous changes from https://review.lineageos.org
Credits:
Many thanks to my fellow LineageOS team members and all the contributors out there in the community. :good:
Android version: 10
Kernel version: 4.9.165
Status: Beta
Click to expand...
Click to collapse
Does LOS17 include styles and wallpaper with clock option and is squeeze working?
Zehlek said:
Does LOS17 include styles and wallpaper with clock option and is squeeze working?
Click to expand...
Click to collapse
I was wondering the same thing about the styles/wallpaper/clocks. I was thinking about messing with it given the long weekend when I glanced at my 3XL (running Havoc) lock screen and remembered that I have a clock that I love having on there. I'm sure you are think the same as I am about Squeeze that it is highly unlikely to be working. I was going to go back to Havoc anyways. Oh, I long for the old Nandroid days where I could hot swap ROMs to test.
sliding_billy said:
I was wondering the same thing about the styles/wallpaper/clocks. I was thinking about messing with it given the long weekend when I glanced at my 3XL (running Havoc) lock screen and remembered that I have a clock that I love having on there. I'm sure you are think the same as I am about Squeeze that it is highly unlikely to be working. I was going to go back to Havoc anyways. Oh, I long for the old Nandroid days where I could hot swap ROMs to test.
Click to expand...
Click to collapse
Can't wait until a fully working TWRP. Clocks and squeeze are the main features I like
Zehlek said:
Can't wait until a fully working TWRP. Clocks and squeeze are the main features I like
Click to expand...
Click to collapse
what is this clock/wallpaper thing? is it present on stock Q too?
FcukBloat said:
what is this clock/wallpaper thing? is it present on stock Q too?
Click to expand...
Click to collapse
Unfortunately it is not available with stock except on P4. It is on Havoc and PDX where you can change the lockscreen clock
Here are some Screenshots of the rom!
francois amon said:
Here are some Screenshots of the rom!
Click to expand...
Click to collapse
Any squeeze option?
Zehlek said:
Any squeeze option?
Click to expand...
Click to collapse
Not yet
razorloves said:
4. The newest vendor, radio, & bootloader img's are included in my builds, so no need to flash those manually.
Click to expand...
Click to collapse
This is icing on the cake feature. I'm not sure if this is LOS17 feature or if razorloves went to extra lengths to make the process simple but i am absolutely thankful for the builds & installation process.
Thanks to @razorloves for this amazing job! I was expecting for a LOS17 build for a while and it's flawless! No issues at all! Initial setup occurred without any issues.
Working LOS17, Magisk, Adaway, and smooth AF!
Thanks!
Thanks so much! Ive been so eagerly waiting for this!
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
francois amon said:
Here are some Screenshots of the rom!
Click to expand...
Click to collapse
Hey buddy! thanks for the screenshots!
mcastro90 said:
Thanks to @razorloves for this amazing job! I was expecting for a LOS17 build for a while and it's flawless! No issues at all! Initial setup occurred without any issues.
Working LOS17, Magisk, Adaway, and smooth AF!
Thanks!
Click to expand...
Click to collapse
How's the camera?
mgp53 said:
How's the camera?
Click to expand...
Click to collapse
I'm using Google's Camera Apk (from Play Store) and it's the same feeling as stock. I cannot see a difference in pictures quality
Blueline - "Error booting boot.img" when trying to boot into lineageos recovery. Im not sure how i can get the logs at this point. Im not sure if i need to be on the latest vendor images & stuff but i was on August patches alongside LOS16. Will try to udate to Android 10 & report back.
Things I've tried:
Redowload the blueline boot.img
Reflashing TWRP then flashing boot.img
Devce details:
Bootloader is unlocked
ADB is enabled
bootloader version:b1c1-0.1-5578427
OS: LOS16
Edit: Updating to latest Android 10 google image resolved this issue.
Edit2: Short review
Rom is very smooth & without any issues. Im not entirely sure if its performance improvements or animation improvements but this feel even snappier than LOS16. Almost everything works. AOD, Wake on raise, Style & Wallpaper options work really well. Files & Claculator seems to support system dark mode. App startup & memory management seems good too.
Awesome features
Style & wallpaper options.
AOD & lock screen clock.
Raise to wake [Not sure this was in LOS16 but i really really like how accurate this feature is in raise detection]
Smooth animations
New gesture & sensitivity options.
Small Issues[Logact created in same order as below issues]
AOD shows expanded statusbar & tiles instead of clock [Im not sure if this is a feature] [Expand statusbar then select edit & let the device auto lock]
Sometimes privacy dashboard is not shown in settings > privacy [Or i am not sure when & what triggers the dashboard]
Settings > System > Status bar > Battery percentage does not work [Settings > Battery > Battery percentage works as an alternative]
Settings app does not seem to support amoled dark yet.
My most missed features
Privacy gaurd [Depricated in LOS17]
Per app data restrictions [VPN , Wifi , Cellular, Romaing] [Usually found in app info]
I do not have attachemnt permission yet, I've uploaded the resources to external site.
Logcat : https://pastebin.com/d8V6mSqt
Screenshots : https://ibb.co/album/hgS7GF
Any BSOD ( black screen of death) issue? Wanting to try this ROM since I get like 2 -3 BSOD on havoc everyday.
zizoty said:
Any BSOD ( black screen of death) issue? Wanting to try this ROM since I get like 2 -3 BSOD on havoc everyday.
Click to expand...
Click to collapse
Have you updated Magisk via Direct Install at all?
zizoty said:
Any BSOD ( black screen of death) issue? Wanting to try this ROM since I get like 2 -3 BSOD on havoc everyday.
Click to expand...
Click to collapse
No dude. Go ahead and flash this Rom!
{
"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 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:
Follow the instructions on the wiki page of your device https://wiki.lineageos.org/devices/#samsung
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Builds: https://download.lineageos.org
GApps: https://wiki.lineageos.org/gapps.html
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:
Support
Telegram group
Contributors
Linux4, haggertk
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_gta4xl
reserved
reserved
the golden question:
its possible to came to official build from unofficial without formatting data?
if not. do you plan to continue making builds for the unofficial branch?
flitzjoy said:
the golden question:
its possible to came to official build from unofficial without formatting data?
if not. do you plan to continue making builds for the unofficial branch?
Click to expand...
Click to collapse
Sorry, you can't (as always)
But I will continue unofficial 18.1 builds
Linux4 said:
Sorry, you can't (as always)
But I will continue unofficial 18.1 builds
Click to expand...
Click to collapse
Whats the difference between official and unofficial then? Thanks for your effort btw
AgentZed said:
Whats the difference between official and unofficial then? Thanks for your effort btw
Click to expand...
Click to collapse
Unofficial might less stable because I'll release builds with new stuff that isn't yet merged Into official (I thought that would be a good idea for testing stuff)
Still won't release something completely untested for unofficial tho
wanted to upgrade how it's described on the lineageOS wiki, however I got an error message, followed by being stuck at a "entering fastboot..."-screen.
I will try install stock Rom and repeat install from there.
Edit:
Restarting the process with stock rom helped.
I'm trying the get the first offical nightly build installed and it gets stuck on the blue lineage os loading arch. Anyone else get it to boot to setup? I'm using lineage recovery now. I was going to go back to unofficial and twrp but twrp builds were removed from the twrp thread.
julesism said:
I'm trying the get the first offical nightly build installed and it gets stuck on the blue lineage os loading arch. Anyone else get it to boot to setup? I'm using lineage recovery now. I was going to go back to unofficial and twrp but twrp builds were removed from the twrp thread.
Click to expand...
Click to collapse
Installed yesterday without any problems. I was running the unofficial los prior. Make sure to use the matching los recovery.
Hello,
as the developpement of 17.1 has stopped I'll try in the next days with 18.1. But I have a question:
after wipe in Recovery can I update the LineageOS Recovery than reboot into Recovery and flash the LOS18.1 via LOS Recovery from my external SD-Card and after that Magisk? That's the procedure I did in the past with TRWP but as I never worked with LOS Recovery before (as well as a decrypted internal SD-Card) I wanted first be sure about the procedure.
Is it safe to dirty flash official 18.1 over the unofficial?
Thanks so much for all your hard work on this!
Bracher said:
Hello,
as the developpement of 17.1 has stopped I'll try in the next days with 18.1. But I have a question:
after wipe in Recovery can I update the LineageOS Recovery than reboot into Recovery and flash the LOS18.1 via LOS Recovery from my external SD-Card and after that Magisk? That's the procedure I did in the past with TRWP but as I never worked with LOS Recovery before (as well as a decrypted internal SD-Card) I wanted first be sure about the procedure.
Click to expand...
Click to collapse
Sure, you could also sideload lineage and magisk but external sdcard should work too.
RsConqueror said:
Is it safe to dirty flash official 18.1 over the unofficial?
Thanks so much for all your hard work on this!
Click to expand...
Click to collapse
I already answered this, see this post
Jeez that's embarrassing. I don't know how I missed that.
Sorry I have another urgent question how can I update LOS Recovery (from 17.1 to 18.1)? In TRWP you can change into "install an image" than the recoveries are recognised in LOS Recovery there is no such possibililty you can only flash .zip files no other files are recognised.
Should I transform the image file into a zip file or how do you do that? Sorry I'm only used to TRWP
Bracher said:
Sorry I have another urgent question how can I update LOS Recovery (from 17.1 to 18.1)? In TRWP you can change into "install an image" than the recoveries are recognised in LOS Recovery there is no such possibililty you can only flash .zip files no other files are recognised.
Should I transform the image file into a zip file or how do you do that? Sorry I'm only used to TRWP
Click to expand...
Click to collapse
If you are still on 17.1 recovery you'll have to flash 18.1 recovery with Heimdall/Odin like you did when installing lineage for the first time.
Starting with 18.1 you are also able to flash it via fastbootd in recovery.
Thank you very much for your advice! But after my successfull update to official 18.1 including LOS Recovery I have a new problem, in devellopper modus is no longer the possibilitiy for enlarged reboot, so I can't reboot in recovery. Is this intended and if so why and is there a possibility to circumvent that? All in all I'm not very happy with 18.1 so I'm thinking going back to 17.1 which is unfortunately no longer maintained.
By the way is there a possibility to support your work - at least with some spending? I found no possibility yet
Bracher said:
Thank you very much for your advice! But after my successfull update to official 18.1 including LOS Recovery I have a new problem, in devellopper modus is no longer the possibilitiy for enlarged reboot, so I can't reboot in recovery. Is this intended and if so why and is there a possibility to circumvent that? All in all I'm not very happy with 18.1 so I'm thinking going back to 17.1 which is unfortunately no longer maintained.
Click to expand...
Click to collapse
Advanced reboot setting was moved to System -> Gestures -> Power Menu -> Advanced Restart
Do you have any other problem with 18.1?
Bracher said:
By the way is there a possibility to support your work - at least with some spending? I found no possibility yet
Click to expand...
Click to collapse
There's a paypal link in my profile if that's what you mean, thanks for considering to support me!
Thank you very much - for both information, as I said I suppose I'm getting old (72 year old grandmother...). as for the other problem I'm stuck with Nanodroid it's not possible to flash via Magisk, but that's not a ROM problem it's linked to Nanodroid. Your ROM is fine thanks a lot!!!
{
"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 repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
Boots
RIL
Fingerprint
Wi-Fi
Bluetooth
Camera
Audio
Sensors
Flash
GPS
NFC
DT2W
Known issues :
-
In order to prevent problems please use the recovery image included in this release!
Instructions :
-Download the ROM and recovery image
-Boot into bootloader: adb reboot bootloader
-Flash the recovery image: fastboot flash recovery recovery.img
-Format data / do a factory reset in recovery
-Reboot into recovery: click advanced --> reboot to recovery
-Go to Apply update and choose Apply from ADB
-Sideload the rom: adb sideload rom.zip
Downloads :
-Recovery image: *Link*
-LineageOS 18.1 with GApps included: *Link*
Android OS version: 11
Build author/ROM Maintainer: @GriefNorth
Kernel Source: *Link*
Device Tree: *Link* and *Link*
Based on: LineageOS
Status: Stable
Current Stable Version: 18.1
Stable Release Date: Updated monthly
Created: 2022-02-13
Last Updated: 2022-02-13
Special Thanks:
- to the LineageOS team
- @KakatkarAkshay for maintaning PixelExperience avicii device tree on which this build is heavily based on.
Donate link
CHANGELOG:
- sync with last source
- fix wi-fi for EU and GLO
- etc
UPDATING THE ROM:
Unless I say the opposite in the update announcement, this ROM can be updated using by two steps:
1. OTA update method
- SystemSettings
- Update system
- Download new version
- let the system do everything by itself
2. the dirty flash method.
In order to do so, follow these steps:
-Download the new version of the ROM you are using (microG/vanilla)
-Reboot into recovery: adb reboot recovery
-DO NOT CLICK ON FACTORY RESET / WIPE DATA
-Flash the Zip-File of the new ROM: adb sideload rom.zip
Hi, Great, thanks a lot for releasing LineageOS for this phone!!
Would it be possible to add a build without gapp?
Greetings seven
EDIT:
Hey,
Have tested today, installed with their OrangeFox recovery build, Boots not, endless the Linage logo.
Thanks, that sucks
Edit:
Finally Solved with your Revovery.img + Instructions,
It was not possible to avoid the formatting.
This is what I have been waiting for, finally some development!!
Finally something pleasing for this phone. Here're offficial LineageOS device sources for Redmi Note 9 Pro 5G / Mi 10T Lite / Mi 10i, the phones use the same SoC as ours. Maybe it could help to improve your code.
GitHub - LineageOS/android_device_xiaomi_gauguin
Contribute to LineageOS/android_device_xiaomi_gauguin development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_kernel_xiaomi_gauguin
Contribute to LineageOS/android_kernel_xiaomi_gauguin development by creating an account on GitHub.
github.com
Can you provide a Google Drive link?
Thx
novato97 said:
Can you provide a Google Drive link?
Thx
Click to expand...
Click to collapse
I can't, not enough space in GDrive. Maybe someone else
Seven1993 said:
Hi, Great, thanks a lot for releasing LineageOS for this phone!!
Would it be possible to add a build without gapp?
Greetings seven
EDIT:
Hey,
Have tested today, installed with their OrangeFox recovery build, Boots not, endless the Linage logo.
Thanks, that sucks
Edit:
Finally Solved with your Revovery.img + Instructions,
It was not possible to avoid the formatting.
Click to expand...
Click to collapse
I built the rom without gapps.
Link: https://www.dropbox.com/s/t2iiu5dfrgiokuk/lineage-18.1-20220224-UNOFFICIAL-ebba.zip?dl=0
asasamo said:
I built the rom without gapps.
Link: https://www.dropbox.com/s/t2iiu5dfrgiokuk/lineage-18.1-20220224-UNOFFICIAL-ebba.zip?dl=0
Click to expand...
Click to collapse
Thx for the effort!
What 3rd party gapps package would you suggest to use (Like opengapps, nikgapps, flamegapps etc.)?
Sony make.believe said:
Thx for the effort!
What 3rd party gapps package would you suggest to use (Like opengapps, nikgapps, flamegapps etc.)?
Click to expand...
Click to collapse
I always used opengapps in the past. Recently i started using microg for better battery life and little to no tracking.
asasamo said:
I built the rom without gapps.
Link: https://www.dropbox.com/s/t2iiu5dfrgiokuk/lineage-18.1-20220224-UNOFFICIAL-ebba.zip?dl=0
Click to expand...
Click to collapse
How would you add microg to lineage os? Do i need magisk for that?
Fisuxcel said:
How would you add microg to lineage os? Do i need magisk for that?
Click to expand...
Click to collapse
Look at this well made guide. Follow all the steps and you'll have a fully working microg install.
I'm glad to see there's active development for this device. Thanks for that.
I was looking into sources and noticed there's TARGET_CPU_VARIANT_RUNTIME = kryo385 (cortex A75 and A55) in boardconfigcommon.mk file but Snapdragon 750G is kryo570 which is cortex A77 and A55.
Flashing_Expert said:
I'm glad to see there's active development for this device. Thanks for that.
I was looking into sources and noticed there's TARGET_CPU_VARIANT_RUNTIME = kryo385 (cortex A75 and A55) in boardconfigcommon.mk file but Snapdragon 750G is kryo570 which is cortex A77 and A55.
Click to expand...
Click to collapse
You can join the development and fix what you think is wrong.
GriefNorth said:
You can join the development and fix what you think is wrong.
Click to expand...
Click to collapse
It wasn't meant that bad and I've never said something's wrong. Just an information.
Flashing_Expert said:
It wasn't meant that bad and I've never said something's wrong. Just an information.
Click to expand...
Click to collapse
I know, too, had nothing wrong, just one to miss some things
@GriefNorth ... The download link for your rom is no longer working.
Can you please create a new one?
Thank you!
Discombobulated85 said:
@GriefNorth ... The download link for your rom is no longer working.
Can you please create a new one?
Thank you!
Click to expand...
Click to collapse
updated link
if you still have problems with access, try using vpn, I'm from Russia and your ISPs may block access to us.
GriefNorth said:
CHANGELOG:
- sync with last source
- fix wi-fi for EU and GLO
- etc
UPDATING THE ROM:
Unless I say the opposite in the update announcement, this ROM can be updated using by two steps:
1. OTA update method
- SystemSettings
- Update system
- Download new version
- let the system do everything by itself
2. the dirty flash method.
In order to do so, follow these steps:
-Download the new version of the ROM you are using (microG/vanilla)
-Reboot into recovery: adb reboot recovery
-DO NOT CLICK ON FACTORY RESET / WIPE DATA
-Flash the Zip-File of the new ROM: adb sideload rom.zip
Click to expand...
Click to collapse
Just to make sure, I have the lineageos without gapps. I can update it with dirty flash and it won't install the gapps right?
Fisuxcel said:
Just to make sure, I have the lineageos without gapps. I can update it with dirty flash and it won't install the gapps right?
Click to expand...
Click to collapse
only for the version without gapps