[ROM][UNOFFICIAL][kebab][11] LineageOS 18.1

M4TH1EU_

Member
Aug 25, 2020
19
1
8
github.com
If you want to install Magisk boot into the system after you flashed the ROM and then reboot to your recovery immediately and sideload Magisk. I don' know about Gapps, I don't use Google.
Hi, without Gapps have you found a solution for the push notifications ?
A lot of apps use google for notifications and don't have push notifications is kind of an issue for me.
 

cleck673

Member
Dec 1, 2008
5
1
33
Tuscaloosa
www.Aximsite.com
The method has been updated:
Instructions :
  • Download the latest build
  • $ adb reboot bootloader
  • $ fastboot boot recovery.img
  • Factory reset -> Format data/factory reset -> Format data ( skip if needed )
  • Advanced -> Enter fastboot
  • $ fastboot update {filename}.zip
I first unzipped the file to get to the recovery.img and it goes without saying that the bootloader must be unlocked. Make sure that ADB/fastboot program you installed is up to date.
Uhhhh... WOW. Thanks. I am up and running now.
 

Dior DNA

Senior Member
Aug 17, 2015
1,449
631
133
Unlike seamless oos full zip flashing with stock recovery, none of the flashing methods mentioned here as far as I understand, change slot current, right?
For example, does a full rom ZIP adb sideload from fastboot change slot?
 
Last edited:

card13

Senior Member
Nov 27, 2008
393
108
68
31
Tacoma
@OhioYJ Same Sideload process for Magisk as GApps. And no I don't need to disable Verity anymore with the new install process.
OOS install can be done through installing one of the fastboot ROMs flying around or Sideloading the OOS Full Package.
 
  • Like
Reactions: OhioYJ

chomsky55

Senior Member
Sep 21, 2020
77
17
18
Amsterdam
@OhioYJ Same Sideload process for Magisk as GApps. And no I don't need to disable Verity anymore with the new install process.
OOS install can be done through installing one of the fastboot ROMs flying around or Sideloading the OOS Full Package.
Just to be clear. In order to go back to OxygenOS I download the zip from their site, go into the LOS recovery and sideload the zip file?
 

OhioYJ

Senior Member
Feb 25, 2011
1,420
691
133
I started off clean, since I had to use the MSM tool. Let the phone update in OOS, then followed the instructions. I just get dumped off at the bootloader (I did format data).


[email protected]:~/Desktop/flash$ sudo fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.332s]
booting...
OKAY [ 0.080s]
finished. total time: 0.412s
[email protected]:~/Desktop/flash$ sudo fastboot update lineage-18.1-20210112_053040-UNOFFICIAL-kebab.zip
extracting android-info.txt (0 MB)...
extracting boot.img (96 MB)...
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (24 MB)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
extracting recovery.img (96 MB)...
archive does not contain 'recovery.sig'
extracting system.img (963 MB)...
archive does not contain 'system.sig'
archive does not contain 'system_other.img'
extracting vbmeta.img (0 MB)...
archive does not contain 'vbmeta.sig'
extracting vendor.img (969 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: unknown
Baseband Version.....:
Serial Number........: (removed)
--------------------------------------------
sending 'boot_b' (98304 KB)...
OKAY [ 3.445s]
writing 'boot_b'...
OKAY [ 0.389s]
sending 'dtbo_b' (24576 KB)...
OKAY [ 0.866s]
writing 'dtbo_b'...
OKAY [ 0.095s]
sending 'recovery_b' (98304 KB)...
OKAY [ 3.479s]
writing 'recovery_b'...
OKAY [ 0.280s]
sending sparse 'system_b' 1/4 (259064 KB)...
OKAY [ 9.501s]
writing 'system_b' 1/4...
OKAY [ 0.570s]
sending sparse 'system_b' 2/4 (258272 KB)...
OKAY [ 9.420s]
writing 'system_b' 2/4...
OKAY [ 0.420s]
sending sparse 'system_b' 3/4 (258272 KB)...
OKAY [ 9.452s]
writing 'system_b' 3/4...
OKAY [ 0.403s]
sending sparse 'system_b' 4/4 (210844 KB)...
OKAY [ 7.667s]
writing 'system_b' 4/4...
OKAY [ 0.369s]
sending 'vbmeta_b' (8 KB)...
OKAY [ 0.002s]
writing 'vbmeta_b'...
OKAY [ 0.004s]
sending sparse 'vendor_b' 1/4 (262140 KB)...
OKAY [ 9.427s]
writing 'vendor_b' 1/4...
OKAY [ 0.539s]
sending sparse 'vendor_b' 2/4 (262140 KB)...
OKAY [ 9.511s]
writing 'vendor_b' 2/4...
OKAY [ 0.545s]
sending sparse 'vendor_b' 3/4 (262140 KB)...
OKAY [ 9.576s]
writing 'vendor_b' 3/4...
OKAY [ 0.549s]
sending sparse 'vendor_b' 4/4 (206256 KB)...
OKAY [ 7.277s]
writing 'vendor_b' 4/4...
OKAY [ 0.347s]
Setting current slot to 'b'...
OKAY [ 0.033s]
rebooting...

finished. total time: 84.322s
[email protected]:~/Desktop/flash$
 

LuK1337

Recognized Developer
Jan 18, 2013
8,173
16,428
253
I started off clean, since I had to use the MSM tool. Let the phone update in OOS, then followed the instructions. I just get dumped off at the bootloader (I did format data).


[email protected]:~/Desktop/flash$ sudo fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.332s]
booting...
OKAY [ 0.080s]
finished. total time: 0.412s
[email protected]:~/Desktop/flash$ sudo fastboot update lineage-18.1-20210112_053040-UNOFFICIAL-kebab.zip
extracting android-info.txt (0 MB)...
extracting boot.img (96 MB)...
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (24 MB)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
extracting recovery.img (96 MB)...
archive does not contain 'recovery.sig'
extracting system.img (963 MB)...
archive does not contain 'system.sig'
archive does not contain 'system_other.img'
extracting vbmeta.img (0 MB)...
archive does not contain 'vbmeta.sig'
extracting vendor.img (969 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: unknown
Baseband Version.....:
Serial Number........: (removed)
--------------------------------------------
sending 'boot_b' (98304 KB)...
OKAY [ 3.445s]
writing 'boot_b'...
OKAY [ 0.389s]
sending 'dtbo_b' (24576 KB)...
OKAY [ 0.866s]
writing 'dtbo_b'...
OKAY [ 0.095s]
sending 'recovery_b' (98304 KB)...
OKAY [ 3.479s]
writing 'recovery_b'...
OKAY [ 0.280s]
sending sparse 'system_b' 1/4 (259064 KB)...
OKAY [ 9.501s]
writing 'system_b' 1/4...
OKAY [ 0.570s]
sending sparse 'system_b' 2/4 (258272 KB)...
OKAY [ 9.420s]
writing 'system_b' 2/4...
OKAY [ 0.420s]
sending sparse 'system_b' 3/4 (258272 KB)...
OKAY [ 9.452s]
writing 'system_b' 3/4...
OKAY [ 0.403s]
sending sparse 'system_b' 4/4 (210844 KB)...
OKAY [ 7.667s]
writing 'system_b' 4/4...
OKAY [ 0.369s]
sending 'vbmeta_b' (8 KB)...
OKAY [ 0.002s]
writing 'vbmeta_b'...
OKAY [ 0.004s]
sending sparse 'vendor_b' 1/4 (262140 KB)...
OKAY [ 9.427s]
writing 'vendor_b' 1/4...
OKAY [ 0.539s]
sending sparse 'vendor_b' 2/4 (262140 KB)...
OKAY [ 9.511s]
writing 'vendor_b' 2/4...
OKAY [ 0.545s]
sending sparse 'vendor_b' 3/4 (262140 KB)...
OKAY [ 9.576s]
writing 'vendor_b' 3/4...
OKAY [ 0.549s]
sending sparse 'vendor_b' 4/4 (206256 KB)...
OKAY [ 7.277s]
writing 'vendor_b' 4/4...
OKAY [ 0.347s]
Setting current slot to 'b'...
OKAY [ 0.033s]
rebooting...

finished. total time: 84.322s
[email protected]:~/Desktop/flash$
Your fastboot skipped multiple files lol. Are you using some 5yo fastboot version or something...?
 
  • Like
Reactions: OhioYJ

OhioYJ

Senior Member
Feb 25, 2011
1,420
691
133
Your fastboot skipped multiple files lol. Are you using some 5yo fastboot version or something...?
Haha, apprently.... I was just using what was included in my distro which was version 1.8..something. Downloaded the version straight from Google which was version 30..something, and it worked first try. Guess a few things changed in all those revisions.
 

card13

Senior Member
Nov 27, 2008
393
108
68
31
Tacoma
@LuK1337 Was using "lineage-18.1-20210112_054052-UNOFFICIAL-kebab-gms.zip" for awhile and noticed only 2 issues.
1: When in a call, if I put the phone on speaker and have the screen on, then the other person would get feedback (at one point it almost caused a feedback loop).
2. I had a strange USB Connection Issue when connected to my Kubuntu 20.10 Laptop Type-C Port. Seemed like sometimes it would charge and sometimes it wouldn't. I watched the notifier show the device reconnected roughly 6x in an hr during a charge session. Connected it to my Windows side and it had no issues (same laptop). I already reinstalled the Kubuntu to validate it happened on fresh installs.

Just moved to your Non-GMS build and used Opengapps Pico, will check a little later to see if I get the above glitches.

***Edit #1***
Forgot to mention that I install the LOS Build as a Clean Install as well.
 

LuK1337

Recognized Developer
Jan 18, 2013
8,173
16,428
253
@LuK1337 Was using "lineage-18.1-20210112_054052-UNOFFICIAL-kebab-gms.zip" for awhile and noticed only 2 issues.
1: When in a call, if I put the phone on speaker and have the screen on, then the other person would get feedback (at one point it almost caused a feedback loop).
2. I had a strange USB Connection Issue when connected to my Kubuntu 20.10 Laptop Type-C Port. Seemed like sometimes it would charge and sometimes it wouldn't. I watched the notifier show the device reconnected roughly 6x in an hr during a charge session. Connected it to my Windows side and it had no issues (same laptop). I already reinstalled the Kubuntu to validate it happened on fresh installs.

Just moved to your Non-GMS build and used Opengapps Pico, will check a little later to see if I get the above glitches.

***Edit #1***
Forgot to mention that I install the LOS Build as a Clean Install as well.
1: Try switching `vendor.audio.feature.spkr_prot.enable` from "false" to "true" or `ro.vendor.audio.sdk.fluencetype` from "fluence" to "none". Report back if doing either of these things changes anything.
2: ~ idk ~
 

M4TH1EU_

Member
Aug 25, 2020
19
1
8
github.com
I prefer non-gapps builds of ROMs myself. I just installed LOS for the first time using the OP's instructions and @theincognito's tips for sideloading NikGapps Core and Magisk. Installed on top of the TMO ROM, btw. No issues with install and setup. I love the ease of install and updates. The process was painless and took no time at all. The ROM is buttery smooth. Great job!
How did you did this ?
I can't find @theincognito's "tips message".

Thanks
 

nsiti

Senior Member
Mar 28, 2011
257
28
48
Hi,

Would it ne possible to use microg on this ROM ?
I think Nanodroid doesnt support signature-spoofing for android 11...

This is the only lineageOS we can find out there for the 8T and it would be awesome to have microg instead of Google ****ty services.

Thanks
I'd like to know the answer to this as well. Thank you.
 

kjslabber

Senior Member
Mar 8, 2015
151
23
43
66
Northeast Ohio
I'm runnin the latest build on global version 8t. My fitness tracker(fitbit) doen't connect with my phone unless I reboot both devices and re-pair fitbit to phone. The fitbit won't pair to the phone only if I reboot. Anybody else have similar problem? Using non-gapps version with sideloaded Nikgapps core and rooted.
 

raptor2017

Member
Jan 18, 2021
6
2
3
So I decided to flash this rom on my OnePlus 8T and found out later that verizon was not supported, so I wanted to flash back to the stock rom and bricked my phone bad. I ended up extracting .img files from OnePlus's OTA file with payload and started flashing all the files. I completed the flash and for some unknown reason I wanted to activate slot-b partition. When I did that, my phone now will not boot and it's stuck on a black screen. The only thing that works is if I holddown the up-vol key and power-key and then it boots up, I see the oneplus logo then it shuts down (or does something weird) and goes back to the black screen. ADB Tools sees my device but it says it's unauthorized. I've also tried MSMTools but that doesn't even see my phone. Don't know what to do anymore. Any help would be appreciated.

Is there anyway to get back to slot-a partition?
 
Last edited:

card13

Senior Member
Nov 27, 2008
393
108
68
31
Tacoma
@LuK1337
I ended up Dirty Flashing in this order (lineage-18.1-20210112_053040-UNOFFICIAL-kebab -> open_gapps-arm64-11.0-pico-20210110-TEST -> magisk-debug) then booting all the way up. After I got in uninstalled most Gapps, installed Google Dialer and haven't encountered either of the issues from last post. Wonder if maybe some Gapp was being a Gremlin.