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

Search This thread

the noan

Senior Member
Jun 15, 2010
168
37
San Antonio
OnePlus 7 Pro
No problem man. If you need help with anything else I'm here. I may not know much, but I'll try my best to help.
dude youre awesome, i havent been to these boards in like 4 years and you helped me out immediately on something i been tryin to figure out for a week cuz i didnt want to bother anyone. so now do i flash the copy-partitions-20210323_1922.zip then continue to flash the rom and gapps and so on?
 

GamingDoggo

Member
Aug 9, 2019
32
18
OnePlus One
Essential Phone
dude youre awesome, i havent been to these boards in like 4 years and you helped me out immediately on something i been tryin to figure out for a week cuz i didnt want to bother anyone. so now do i flash the copy-partitions-20210323_1922.zip then continue to flash the rom and gapps and so on?
How are you planning on flashing it? Through twrp or the lineage recovery?
 
  • Like
Reactions: the noan

GamingDoggo

Member
Aug 9, 2019
32
18
OnePlus One
Essential Phone
Well I'm going to be honest, I didn't flash the copy partitions. But you can if you want to. I'd say do this. Flash copy partitions. Format, flash lineage, flash twrp installer, reboot recovery, flash gapps, reboot system. All I did was formatted, flashed lineage.zip, twrp installer, reboot recovery flash gapps, reboot system. Just becareful if you decide to do it this way. When I first flashed it, it couldn't boot, sent me to recovery and couldn't boot to recovery either. The recovery splash screen kept flickering on and off. What I did was I flashed lineage recovery tried to boot. It told me I had to factory reset it so I did and it booted. I flashed it again today the same way and it had no issues. It booted fine with twrp.
 
Last edited:
  • Like
Reactions: the noan

the noan

Senior Member
Jun 15, 2010
168
37
San Antonio
OnePlus 7 Pro
Well I'm going to be honest, I didn't flash the copy partitions. But you can if you want to. I'd say do this. Flash copy partitions. Format, flash lineage, flash twrp installer, reboot recovery, flash gapps, reboot system. All I did was formatted, flashed lineage.zip, twrp installer, reboot recovery flash gapps, reboot system. Just becareful if you decide to do it this way. When I first flashed it, it couldn't boot, sent me to recovery and couldn't boot to recovery either. The recovery splash screen kept flickering on and off. What I did was I flashed lineage recovery tried to boot. It told me I had to factory reset it so I did and it booted. I flashed it again today the same way and it had no issues. It booted fine with twrp.
im not gonna get it tonight, too much vodka, but thank you for getting me on my way. been at this for a week and in the last hour or so youve helped me more than anything else has. i bricked again and am using the msmtool to go back to 9 to upgrade to 10. thanks for the help sober matt will take it from here tomorrow
 
  • Like
Reactions: GamingDoggo

GamingDoggo

Member
Aug 9, 2019
32
18
OnePlus One
Essential Phone
im not gonna get it tonight, too much vodka, but thank you for getting me on my way. been at this for a week and in the last hour or so youve helped me more than anything else has. i bricked again and am using the msmtool to go back to 9 to upgrade to 10. thanks for the help sober matt will take it from here tomorrow
Yeah no problem man. If you want I can help you out tomorrow. But what happened?
 

the noan

Senior Member
Jun 15, 2010
168
37
San Antonio
OnePlus 7 Pro
Yeah no problem man. If you want I can help you out tomorrow. But what happened?
i didnt follow your instructions properly. formatted then skipped the copy-partition and flashed the rom, flashed twrp, didnt reboot to flash gapps. thats probably where i messed up. after that it said there was no os to boot into and it booted to flashboot. ill figure it out tomorrow. thank you. seriously dm me and give me a cashapp or venmo or paypal or whatever and ill send you $10, if thats legal on these boards. you gave me the one thing i needed to fix this phone and i thank you
 

GamingDoggo

Member
Aug 9, 2019
32
18
OnePlus One
Essential Phone
i didnt follow your instructions properly. formatted then skipped the copy-partition and flashed the rom, flashed twrp, didnt reboot to flash gapps. thats probably where i messed up. after that it said there was no os to boot into and it booted to flashboot. ill figure it out tomorrow. thank you. seriously dm me and give me a cashapp or venmo or paypal or whatever and ill send you $10, if thats legal on these boards. you gave me the one thing i needed to fix this phone and i thank you
Oh I see. Hopefully we get it up and running soon. And nah man it's cool. I want to help. Just let me know when you have some spare time and we'll figure out the problem.
 
  • Like
Reactions: the noan and Nikhil

GamingDoggo

Member
Aug 9, 2019
32
18
OnePlus One
Essential Phone
No, I'm on Lineage 18 recovery
I thought there was no twrp for android 11
Thanks
Yeah there isn't a working twrp. I'm not sure if you can do this but you can download the update file for your phone directly from oneplus and flash it. If not, you can get this tool on you're computer https://forum.xda-developers.com/t/tool-tool-all-in-one-drivers-unlock-twrp-factory-image-stock-recovery.3358711/

And download a fastboot ROM from here https://forum.xda-developers.com/t/...boot-roms-for-oneplus-7-pro-7-pro-5g.3931424/
For your specific device. Once done, open the tool on your computer and click on flash factory images. From there select the fastboot ROM zip and plug your phone into the computer. Make sure you have USB debugging enabled. Click on wipe data and then click flash.The tool will start to unzip the file and flash the images. Your phone will automatically reboot once done.
 
Last edited:

the noan

Senior Member
Jun 15, 2010
168
37
San Antonio
OnePlus 7 Pro
Oh I see. Hopefully we get it up and running soon. And nah man it's cool. I want to help. Just let me know when you have some spare time and we'll figure out the problem.
thanks for your help, ive been at it for the last few nights on my own and i got it tonight! downgraded to android 9 with msm, upgraded to android 10, i flashed copy partitions formatted then flashed lineageos, rebooted to recovery and it took me to lineageos recovery, then flashed gapps via the adb sideload update. currently booted into lineageos and transferring everything. i plan on upgrading phones soon and dont plan on flashing anything new so i skipped the flashing of a custom recovery and everything works. thank you so much for your tip on android ten twrp. cheers mate you really saved me. a week without this phone sucked, been using my sons pixel 3a with a cracked to **** screen. the thing i never wouldve thought i missed the most was the sound slider on the side of the phone. i normally run on vibrate, unless i use headphones, and the ease of switching between silent, vibrate, and sound was something i never thought i wouldve missed. again thank you very much
 
  • Like
Reactions: GamingDoggo

GamingDoggo

Member
Aug 9, 2019
32
18
OnePlus One
Essential Phone
thanks for your help, ive been at it for the last few nights on my own and i got it tonight! downgraded to android 9 with msm, upgraded to android 10, i flashed copy partitions formatted then flashed lineageos, rebooted to recovery and it took me to lineageos recovery, then flashed gapps via the adb sideload update. currently booted into lineageos and transferring everything. i plan on upgrading phones soon and dont plan on flashing anything new so i skipped the flashing of a custom recovery and everything works. thank you so much for your tip on android ten twrp. cheers mate you really saved me. a week without this phone sucked, been using my sons pixel 3a with a cracked to **** screen. the thing i never wouldve thought i missed the most was the sound slider on the side of the phone. i normally run on vibrate, unless i use headphones, and the ease of switching between silent, vibrate, and sound was something i never thought i wouldve missed. again thank you very much
No problem man! It was my pleasure helping you out. And yeah the volume slider is a must. It's really easy to switch modes. Well enjoy your phone! I'm glad you were able to get it up and running! Hopefully using the pixel 3a wasn't too bad.
 
  • Like
Reactions: the noan

Top Liked Posts

  • There are no posts matching your filters.
  • 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.