[ROM][OFFICIAL][guacamole][11] LineageOS 18.1

Search This thread

Jashu9440

New member
Dec 11, 2017
3
0
Hello everyone, i am new to custom roms and successfully manage to install LOS 18.1 by their wiki. But i need to install Twrp and root?

i didn't any relevant searches regarding those.
 

ChewyLouis

New member
May 16, 2021
3
1
Hi guys,
i have a problem when trying to install the magisk_patched-xxx.img
The latest LOS (16.05.) and Magisk App (23) is installed.

When i'm in Lineage Recovery > Advanced FastbootD
and enter this command via cmd:

fastboot flash boot /path/to/magisk_patched.img

I always get this Error

sending 'boot' (98304 KB)...
OKAY [ 2.200s]
writing 'boot'...
FAILED (remote: No such file or directory)
finished. total time: 2.250s

Does anyone know how to fix this?
Thanks in advance, you guys are great! :)
 

Suarezian

Senior Member
  • Jun 18, 2012
    576
    379
    Mumbai
    I'm following the instructions on the official site and it says if I factory reset on recovery, it will wipe my internal storage too. Is that true? I've been flashing ROMs since 2011 and never has the Factory reset option wiped internal storage. Can someone clear this out for me?
     

    daniel84cs

    Senior Member
    Dec 27, 2011
    2,631
    5,444
    OnePlus 7 Pro
    I'm following the instructions on the official site and it says if I factory reset on recovery, it will wipe my internal storage too. Is that true? I've been flashing ROMs since 2011 and never has the Factory reset option wiped internal storage. Can someone clear this out for me?
    Factory Reset in stock recovery format your storage , only TWRP with factory reset leave untouched it. LOS recovery is like a stock recovery and it clean your storage for new encryption.
    Only old phones had no encryption by default. We have to go back to the days of the Nexus 5, I believe you only had older generation phones, otherwise you would have noticed. Also I have been flashing ROMs since 2007
     

    prad1po

    Member
    Jan 28, 2011
    39
    1
    It works perfect. Download the latest canary, rename the apk to zip and install by sideload. When you run Magisk the first time it will ask you to update.
    super it's worked for me thanks

    do you use the lineage camera app ? or we can flash the oos camera ?
     

    musicman5844

    Senior Member
    Jan 27, 2016
    1,521
    702
    there is no LOS recovery like TWRP. they're both 2 different recoveries. I'd reccomend to keep the LOS recovery, and just fastboot boot TWRP in case you need it.
    (if that even works, some people are unable to boot/flash twrp on android11)
    Question I keep getting waiting on device when trying to flash something using los recovery
     

    washichi

    Senior Member
    Jan 12, 2012
    145
    81
    OnePlus 3
    OnePlus 7 Pro
    Fastboot boot TWRP didn't work with A11. I tried and no luck
    That's the issue I'm talking about, I also have it.
    Some people don't have that problem.
    I made a separate thread fort this issue:
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 2
      anyone know how to install the OnePlus cam from apkpure?
      Use latest Gcam Arnova with SAP Overkill xml , work perfect on LOS, you can use it without google apps with gcam service provider.
      Screenshot_20210526-113529_Fotocamera.png
      1
      I know in the old days, I could wipe everything *but* internal storage and just flash the new ROM and gapps and all that lovely jazz and get up and running; however, it seems things aren't as straightforward, especially with all this A/B partition nonsense. I'm currently on OxygenOS 11, and I've got a good backup solution in place (TWRP us SSH backup to my home server), so can I:
      •Wipe all but internal storage
      •Flash Lineage, TWRP, Magisk, gapps, and kernel
      •And just reboot from TWRP aftert all that to enjoy the the awesomeness that is LineageOS?
      I've read most of this thread, but I'm still not quite sure I'm going about all this correctly. Also, if I flash this NikGapps everyone keeps talking about, I only gotta flash that once, right?
      Oh no! You have A/B partition device now. You must follow the instructions from Original Post.

      And yes, if you flash latest version of NikGapps, you won't have to flash it again after ota update.
    • 16
      FYI, next week you'll get the first official 18.1 build.
      Follow official installation instructions on https://wiki.lineageos.org for upgrade/install and https://gist.github.com/luk1337/6c18b1910fa38292f2d5fbd3df47fd91 for firmware update as OOS 11 FW is needed.
      13
      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. 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 :
      Downloads :
      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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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:
      7
      As someone who doesn't have that much experience in flashing, it' not a rhetorical question for me. Do I understand it correctly that the FW update is not necessary when updating from 17.1 to 18.1, since there is no information about it in the corresponding instructions in the wiki?
      It is a rhetorical question. I clearly said that OOS 11 firmware is needed; you wouldn't be running OOS 11 firmware on Lineage 17.1, would you? Also I'll update wiki warning when first build is out.
      4
      Has anyone tried this ROM with Micro G?
      I am running Lineage 17 Micro G on my OnePlus 6t and battery is amazing!
      4
      Hi, first of all, thank you for your work!

      I just updated to 18.1 from 17.1, and noticed that the back gesture doesnt produce a vibration effect anymore. Vibration isnt broken, everywhere else it seems to work fine. Just the back gesture doesnt do it anymore.

      Is this a known issue? Or intended? Or did I mess something up?

      Logcat and dmesg are attached. I do have Magisk installed, but the logs were captured with no modules enabled. I did notice something in the logs. When it vibrates, it produces something like this:

      Code:
      04-11 17:35:05.166   935   935 D vendor.qti.vibrator: QTI Vibrator reporting capabilities: 3
      04-11 17:35:05.168   935   935 D vendor.qti.vibrator: QTI Vibrator off
      04-11 17:35:05.181  1095  2628 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
      04-11 17:35:05.181   601   601 I servicemanager: Found android.hardware.vibrator.IVibrator/default in device VINTF manifest.
      04-11 17:35:05.182  1095  2628 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
      04-11 17:35:05.182   601   601 I servicemanager: Found android.hardware.vibrator.IVibrator/default in device VINTF manifest.
      04-11 17:35:05.185   935   935 D vendor.qti.vibrator: Vibrator on for timeoutMs: 10
      04-11 17:35:05.187     0     0 I [20210411_17:35:05.185729]@0 aw8697_duration_store: val:10
      04-11 17:35:05.187     0     0 I [20210411_17:35:05.186206]@0 aw8697_activate_store: value=1
      04-11 17:35:05.187     0     0 I [20210411_17:35:05.187083]@3 aw8697->pm_awake: 1
      04-11 17:35:05.203   935   935 D vendor.qti.vibrator: QTI Vibrator off
      04-11 17:35:05.207     0     0 I [20210411_17:35:05.203444]@3 aw8697->pm_awake: 0
      04-11 17:35:05.207     0     0 I [20210411_17:35:05.204415]@1 aw8697_activate_store: value=0
      04-11 17:35:05.207     0     0 I         : [20210411_17:35:05.206860]@3 aw8697_haptic_stop_delay wait for standby, reg glb_state=0x07

      But when I do a back gesture I only get this. No "Vibrator on for ..." and no aw8697 logs.

      Code:
      04-11 17:35:16.548   935   935 D vendor.qti.vibrator: QTI Vibrator off
      [...]
      04-11 17:35:16.556   971  1456 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor>
      04-11 17:35:16.556  3885  4083 I Finsky  : [204] rmc.a(1): Sending Heterodyne sync request for package com.android.vending
      04-11 17:35:16.558   971  1455 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor>
      [...]
      04-11 17:35:16.567   971  1455 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor>
      [...]
      04-11 17:35:16.570  1095  3695 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
      [...]
      04-11 17:35:16.573   601   601 I servicemanager: Found android.hardware.vibrator.IVibrator/default in device VINTF manifest.
      04-11 17:35:16.574  1095  1609 D InputDispatcher: Waiting to send key to Window{45a7a43 u0 com.topjohnwu.magisk/com.topjohnwu.magisk.ui.MainActivity} because there are unprocessed events that may cause focus to change
      04-11 17:35:16.574   971  1455 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor>
      [...]
      04-11 17:35:16.577  1095  1609 D InputDispatcher: Waiting to send key to Window{45a7a43 u0 com.topjohnwu.magisk/com.topjohnwu.magisk.ui.MainActivity} because there are unprocessed events that may cause focus to change
      04-11 17:35:16.578  1095  3695 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
      [...]
      04-11 17:35:16.583   601   601 I servicemanager: Found android.hardware.vibrator.IVibrator/default in device VINTF manifest.
      Also RE#2: I merged a set of interesting changes. You should notice some nice improvement in the next build.