[ROM][OFFICIAL][redfin] LineageOS 18.1

Search This thread

user602

Senior Member
May 8, 2007
662
449
Samsung Galaxy Note 10.1
Nexus 7
Will someone using Magisk and gapps please outline their steps to update the ROM?

When updating to the 17 Feb build from the earlier one, I tried sideloading the lineage zip but ran into an error. I don't remember what the error was, but I had to flash a factory image to get the device to boot again; I was then able to successfully flash the 17 Feb build.

Thanks!
 

aleasto

Senior Member
Jul 15, 2012
862
2,388
Milan
Will someone using Magisk and gapps please outline their steps to update the ROM?

When updating to the 17 Feb build from the earlier one, I tried sideloading the lineage zip but ran into an error. I don't remember what the error was, but I had to flash a factory image to get the device to boot again; I was then able to successfully flash the 17 Feb build.

Thanks!
Added instructions to OP
 

user602

Senior Member
May 8, 2007
662
449
Samsung Galaxy Note 10.1
Nexus 7
I have been using the 17 Feb build with gapps, Magisk and kdrag0n's Universal SaftyNet Fix Magisk module. For anyone needing more detailed instructions, this is how to update to the latest build:

After downloading latest ROM zip, gapps, and v22.0 or newer Magisk apk:
1. Reboot to LOS Recovery, apply update > apply from ADB
2. adb sideload <filename of ROM zip>, reboot recovery
3. apply update > apply from ADB, adb sideload <filename of gapps zip>
4. adb sideload <filename of magisk apk> reboot system

Edit: Thanks to @aleasto for laughing at my original post and sharing an easier way. 🤣
 
Last edited:
  • Like
Reactions: CrashTestDroid

aleasto

Senior Member
Jul 15, 2012
862
2,388
Milan
I have been using the 17 Feb build with gapps, Magisk and kdrag0n's Universal SaftyNet Fix Magisk module. For anyone needing more detailed instructions, this is how I updated to the latest build.

After downloading latest ROM.zip, boot.img, and gapps:
1. Reboot to LOS Recovery, apply update > apply from ADB
2. adb sideload <filename of ROM zip>, reboot recovery
3. apply update > apply from ADB, adb sideload <filename of gapps zip>, reboot to system
At this point I checked Magisk Manager, and Magisk was not installed.

To re-install Magisk:
4. Transfer boot.img to phone, and patch with Magisk Manager using Install > select and patch a file; transfer patched boot.img to computer
5. Reboot to bootloader, fastboot flash boot <filename of patched boot img>, reboot system
I checked Magisk Manager again; Magisk was installed, and SafetyNet passed. All Magisk modules were still enabled, and Manager retained root permissions and Hide settings.

I am not used to flashing without TWRP, so there may be a better way to do this; I am simply sharing what worked for me and hope it helps somebody else.
Just sideload magisk in recovery lol
 

Neuken6969

Senior Member
Sep 25, 2018
72
6
Hi all I am still on the Feb build, while playing with some audio files .. Only 1 speaker is working. So my question isn't there 2 speakers, and if so is this issue a ROM issue?
 

indishcurry

Senior Member
Nov 24, 2016
72
60
i successfully installed latest unofficial lineageos with pico gapps and magisk. almost everything is working, here my remarks:
  • data transfer tool keeps crashing when trying to finish pixel setup
  • playstore states phone as uncertified, but magisk hide works for other apps
  • stock email client is missing
thanks @aleasto for your work!
 

shooterlgk

Senior Member
Jul 11, 2012
1,277
273
FrEsNo CA
I'm not sure if anyone here uses substratum but has anyone tried theming the qs tiles? Im not sure if it's the rom missing the ability to do so, or the themes might not be compatible but to the developer, any idea what I'm talking about? Here's a pic of the issue
 

Attachments

  • Screenshot_20210309-142414_substratum_lite.png
    Screenshot_20210309-142414_substratum_lite.png
    189.2 KB · Views: 50

Top Liked Posts

  • 1
    Anyone else have any issues while re-applying Magisk after the latest update?

    The app survived the OTA but, as usual, the Magisk was not itself installed. So, I get a stock image, select and patch the file in Magisk, and then attempt to 'fastboot flash boot [magisk.img]'. It installs no issues but fails SafetyNet.

    "SafetyNet API Error"
    "basicIntegrity -"
    "ctsProfile -"
    "evalType N/A"
    Had no problem with magisk install, but something is going on with safetynet check.
    Either magisk or Google did something, but you should still be google play certified.
  • 8
    We got assigned a faultly build slave, it has now been removed from the roster and the build rescheduled.

    The build will notably include:
    Fix for screen off loop with no lockscreen
    Reverse wireless charging / Wireless PowerShare functionality (available as a QuickSettings toggle only for now)
    5
    Same here. Magisk 22.1 survived both OTAs. After today's update, About Phone > Build Number shows "lineage_redfin-userdebug 11 RQ2A.210405.005 5c62535bef," is this correct?
    It is.
    4
    after you have installed the official build: Upcoming updates will be downloaded and installed directly on the device? what about gapps, do i still need a pc to install via adb?
    You just use Updater app: Settings > System > Updater.
    Gapps will persist.
    3
    installed the new OTA update (20210407) and everything works well, thank you.

    Just one thing, the update process took about one hour (the download itself was fast) is this normal ?
    Yes A/B updates are engineered to run quietly in the background.
    You can force priority mode for faster updates in the updater app preferences
    3
    No, factory reset is very much not the same as OTA. You need to sideload Magisk again.
    Well that's interesting, have done both ota's & magisk survived no reinstalling apk or anything. Magisk 22.1 if that matters.
  • 30
    2okPze5.png


    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. LineageOS does still include various proprietary hardware-specific code.

    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.

    Informations :
    • This ROM uses source built kernel, kernel modules, boot kernel modules (vendor_boot) and vendor image.
    • This ROM bundles the latest firmware so you don't have to worry about updating firmware beforehand.
    • To use the eSIM you need to install GApps
    Instructions :
    • Download the latest recovery image and rom zip
    • Boot to bootloader
    • fastboot flash boot boot.img
    • Boot to recovery
    • Format data
    • Flash LineageOS zip
    • Optionally flash any addons:
      • Advanced > Reboot to recovery
      • Flash the addons
    • Reboot
    See https://wiki.lineageos.org/devices/redfin/install for more detailed instructions​

    Downloads :
    Reporting Bugs
    • 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 /sys/fs/pstore/* (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.

    Known Issues
    • On the first boot, you might be presented the message "SIM Manager has crashed". You can safely ignore it.
    Contributors
    aleasto
    The LineageOS Team

    Source Code: https://github.com/LineageOS

    ROM OS Version: Android 11
    10
    New build out
    • Feb 2021 security patch
    • Update modem firmware from the T-Mobile factory images to enable 5G Standalone.
      Google only did this for T-Mobile images (RQ1C.210205.006), but it doesn't seem to negatively affect non T-Mobile users, thus I'm including it in the generic build (RQ1A.210205.004 based).
    10
    New build out
    The final checkups before official rolls out.
    We've also managed to remove the need for flashing vendor_boot.img so now the install instructions are back in line with other pixels.
    10
    New build out
    Enable Adaptive Sound, Live Captions, Now Playing, Screen Attention pixel features.
    These all work without gapps, and all process data offline.
    9
    Source code will be uploaded to LineageOS repos soon.
    Meanwhile you can view
    my github
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone