[ROM][OFFICIAL][kebab][11] LineageOS 18.1

Search This thread

Zlatozar

Member
Sep 22, 2018
19
0
Hello, I know you have to downgrade to OOS 11 from OOS 12 to flash this rom, but do I have to do it if I'm coming from Pixel Experience 12, which I flashed from OOS 11?
 

CarranTise

New member
Jul 11, 2022
2
0
So PayPal is auto-crashing on a fresh install with Magisk; I'm assuming some apps have root detection. How do I hide my root status? First time doing this.
 

thefanum

Senior Member
Dec 27, 2011
148
46
OnePlus 3T
OnePlus 7T
So PayPal is auto-crashing on a fresh install with Magisk; I'm assuming some apps have root detection. How do I hide my root status? First time doing this.
This worked for me, although I did have to follow these instructions, make sure everything Google was blacklisted, zygist deny list was enforcing, and then run su in terminal, then the command "props" in terminal, and select OnePlus and 8t fingerprint.

https://forum.xda-developers.com/t/magisk-google-wallet-pay-with-magisk.4471279
 

thefanum

Senior Member
Dec 27, 2011
148
46
OnePlus 3T
OnePlus 7T
If anyone is having issues with Google assistant not having the screen off detection, I had to re-flash gapps to fix it. Opengapp nano is required for that functionality, but it wouldn't flash on my LineageOS 18.1 OnePlus 8t, so I originally flashed pico. Which meant assistant was there, but not fully functional. So I flashed the Mindthegapps Android 11 arm64 package over that, and it works fine now.
 
  • Like
Reactions: Lz3807775t

JoeRGarner

Member
Dec 10, 2013
9
0
I just unlocked my tmobile 8t and am running stock 11. do I need to back anything up like persist.img before flashing? I jumped the gun on my 7t mclaren and ruined the finger printer reader. trying to avoid that! thanks.
 

OhioYJ

Senior Member
Feb 25, 2011
1,554
817
I just unlocked my tmobile 8t and am running stock 11. do I need to back anything up like persist.img before flashing? I jumped the gun on my 7t mclaren and ruined the finger printer reader. trying to avoid that! thanks.
Just follow the guidelines for installing and you should be good.

While I agree there is little risk following the instructions... There really is no reason to not back up your EFS and Persist. Especially as there is "no" way to recover the EFS if something goes wrong later, and they are unique to your device. You should never need them, but if you ever do, you'll be glad you have them.

From my write-up (if it helps)

sudo adb shell
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/modemst1.bin
dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/modemst2.bin
exit
sudo adb pull /sdcard/persist.img /home/mint/Desktop
sudo adb pull /sdcard/modemst1.bin /home/mint/Desktop
sudo adb pull /sdcard/modemst2.bin /home/mint/Desktop

I originally used the broken TWRP to do this.
 

Brasscat82

Senior Member
Jul 16, 2014
551
371
I have an issue with the latest LOS update.
I've installed TWRP and Lineage on slot A, and then proceeded to restart to recovery flash TWRP, gApps, and Magisk on slot B. Everything was running super smoothly until I downloaded the update, and flashed it to slot A. When I reboot, it boots to the LOS boot animation for about 40 cycles, then reboots.

I've reflashed Magisk (B) and TWRP (also B), but I still keep getting the bootlooop. Can anyone help me fix this without wiping my phone again? THANKS TO THE WONDERFUL COMMUNITY!!!
 

thefanum

Senior Member
Dec 27, 2011
148
46
OnePlus 3T
OnePlus 7T
I have an issue with the latest LOS update.
I've installed TWRP and Lineage on slot A, and then proceeded to restart to recovery flash TWRP, gApps, and Magisk on slot B. Everything was running super smoothly until I downloaded the update, and flashed it to slot A. When I reboot, it boots to the LOS boot animation for about 40 cycles, then reboots.

I've reflashed Magisk (B) and TWRP (also B), but I still keep getting the bootlooop. Can anyone help me fix this without wiping my phone again? THANKS TO THE WONDERFUL COMMUNITY!!!
I used the copy partitions zip when flashing LineageOS so they would all be the same, as instructed by the official documentation. I also used Lineage recovery and adb sideload. I don't think flashing with TWRP works.

Hope that helps
 
Can anyone help me fix this without wiping my phone again?
Try to switch the active partition.
Check in fastboot mode which one is active with
Code:
fastboot getvar current-slot
if you are on "a" then change the partition to the B-Slot with
Code:
fastboot --set-active=b
if you are on "b" then change to the A-Slot with
Code:
fastboot --set-active=a
and reboot the phone.
Good luck.
 

Dior DNA

Senior Member
Aug 17, 2015
1,569
664
Question (sorry if already answered) : will (y/n) lineageos 19 for 1+8t require oos 11 firmware or oos 12 firmware (or maybe two roms will tmp be available) ?
 

thefanum

Senior Member
Dec 27, 2011
148
46
OnePlus 3T
OnePlus 7T
nevertheless some custom ROMs offer (tmp) both OOS11 and OOS12 right now. And, will there ever be an OOS13?
Oh yeah, there is absolutely going to be a 13 for the 8t. But I have no info beyond what I already said.

 

OhioYJ

Senior Member
Feb 25, 2011
1,554
817
Question (sorry if already answered) : will (y/n) lineageos 19 for 1+8t require oos 11 firmware or oos 12 firmware (or maybe two roms will tmp be available) ?

I don't know for sure, but I would guess either 11 or 13. 12 breaks all current recoveries and won't allow you to flash anything.

Just speculating, and don't want to speak for the excellent devs, but if I were to place a bet, it would be 12 firmware will be required. The hang up has been waiting on OOS 12 sources from what I understand. Next if you look at similar devices, OP9, etc, OOS 12 firmware is required for LOS 19. Finally as long as LOS recovery works, doesn't really matter what happens with other recoveries, unfortunately.

My bet is on the OOS 12 firmware.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    The build.prop files have model=KB2005 ... so Oxygen updater today mentions image KB2005_11_C.35 for download. Would it be safe for me as root to change build.prop files to have model=KB2003 in order make Oxygen updater look for KB05BA EU images instead?
    ...you could always just look at oxygen updater settings.
  • 46
    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 /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:
    11
    tomorrow afternoon 3 p.m 😆
    More like few weeks after OOS12 kernel source is out.
    10
    Yaay. The thread is back. :D
    9
    Any update about LOS 19 ?
    Yep, everyone already has it except you. We were about to call you, but you ruined it by asking.
    8
    There are already oos 12 firmware based roms available so I asked if LOS 19 is coming soon or not.

    It appears OnePlus still has not released OOS 12 Kernel source. (<-- Github link)

    See these issue links in particular:

    Where are the DTS in the OOS12 kernel source?

    GPL Violation: OOS12 kernel_oneplus_sm8250 sources have not been released

    I linked to two of these issues, there are a ton of them actually, they are scattered across Github, across many devices. Then again across many Reddit threads. OnePlus apprently doesn't care about GPL and doesn't care about releasing the code as they are supposed to.