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

LuK1337

Recognized Developer
Jan 18, 2013
8,167
16,424
253
In the thread
people did IMO not come to a consistent definitive 'step by step instructions' recipe yet ... But clearly, after getting latest OOS (11.0.6.9.KB05BA in my case), several people (but not all), one by one, reported L3 -> L1 change happening somewhat magically.
Various actions to influence the transition have been suggested like:
- boot (stock) recovery and wipe /cache
(which is, I think, what I did, but, maybe I did not even wipe /cache and only booted recovery and then system)
Now 'DRM Info' showed L1, but to get 'Netflix' also show L1 I needed to
- force stop / delete cache and storage for Netflix
(that worked)
It is not clear where this 'widevine' data is stored (some say in /vendor), and, what determines the system id.
One thing seems clear: the latest OOS upgrade (which I flashed local full ZIP and both slots) seems to trigger the change.
Just tried that again and as expected it didn't work.
OTA'd to 11.0.3.3.IN11BA, unlocked BL, booted up - L3, wiped cache, booted up - still L3.

Until there's a clear way to achieve L1 on unlocked BL I'm not going to bother doing anything.
 
  • Like
Reactions: Dior DNA

Dior DNA

Senior Member
Aug 17, 2015
1,448
631
133
Just tried that again and as expected it didn't work.
OTA'd to 11.0.3.3.IN11BA, unlocked BL, booted up - L3, wiped cache, booted up - still L3.

Until there's a clear way to achieve L1 on unlocked BL I'm not going to bother doing anything.
Thanks, and sorry for your very valuable time.
Not sure which date 11.0.3.3.IN11BA was released, is it for 8T, it rather seems to be 8 or 8 Pro? Numbering wise it looks older compared to 11.0.6.9.KB05BA which was released begin January. Note that previous 8T release (11.0.6.8.KB05BA) did not achieve L1 (and had a terrible media stuttering bug as well)
 

LuK1337

Recognized Developer
Jan 18, 2013
8,167
16,424
253
Thanks, and sorry for your very valuable time.
Not sure which date 11.0.3.3.IN11BA was released, is it for 8T, it rather seems to be 8 or 8 Pro? Numbering wise it looks older compared to 11.0.6.9.KB05BA which was released begin January. Note that previous 8T release (11.0.6.8.KB05BA) did not achieve L1 (and had a terrible media stuttering bug as well)
I said I was willing to do it on 8 Pro. I'm not going to wipe my daily driver.
I can update it to open beta if that makes any difference.
EDIT: open beta is even older, 11.0.3.3 appears to be from january fyi https://forums.oneplus.com/threads/oxygenos-11-0-3-3-for-the-oneplus-8-and-oneplus-8-pro.1374182/
 
  • Like
Reactions: Dior DNA

z00man

Member
Jun 14, 2020
13
2
3
@LuK1337
Im tired up with quality of oos developing and im considering jump to los..

May i ask again maybe same questions, lazy to use searching..

Is it stable enough to as daily driver?
Does it pass safetynet with props magisk module?

Does "unofficial" release means more bugs?



really awesome that theres proper alternatives available, THANKS 🤗
 
Last edited:

anarchotaoist

Senior Member
Jun 2, 2018
68
8
18
I am stuck at command 2.

fastboot boot recovery.img
error: cannot load 'recovery.img': No such file or directory

Should I flash over the recovery.img from the LOS zip and try again?
 

anarchotaoist

Senior Member
Jun 2, 2018
68
8
18
I am stuck at command 2.

fastboot boot recovery.img
error: cannot load 'recovery.img': No such file or directory

Should I flash over the recovery.img from the LOS zip and try again?
hmmm, Is this booting from the recovery.img fiile on the phone or from inside the unpacked Los file on the computer?
 

anarchotaoist

Senior Member
Jun 2, 2018
68
8
18
Ugh! I think I am in a bootloop!

I ran the boot to recovery.img from with the unpacked los zip file and proceeded according to instructions.
All seem to go well, but pressing start only brings me back to fastboot.
☹
 

anarchotaoist

Senior Member
Jun 2, 2018
68
8
18
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........: 72cfba44
--------------------------------------------
sending 'boot_b' (98304 KB)...
OKAY [ 3.121s]
writing 'boot_b'...
OKAY [ 0.377s]
sending 'dtbo_b' (24576 KB)...
OKAY [ 0.741s]
writing 'dtbo_b'...
OKAY [ 0.097s]
sending 'recovery_b' (98304 KB)...
OKAY [ 3.190s]
writing 'recovery_b'...
OKAY [ 0.272s]
sending sparse 'system_b' 1/4 (259064 KB)...
OKAY [ 8.531s]
writing 'system_b' 1/4...
OKAY [ 0.561s]
sending sparse 'system_b' 2/4 (258272 KB)...
OKAY [ 8.587s]
writing 'system_b' 2/4...
OKAY [ 0.451s]
sending sparse 'system_b' 3/4 (258272 KB)...
OKAY [ 8.550s]
writing 'system_b' 3/4...
OKAY [ 0.412s]
sending sparse 'system_b' 4/4 (210844 KB)...
OKAY [ 6.970s]
writing 'system_b' 4/4...
OKAY [ 0.371s]
sending 'vbmeta_b' (8 KB)...
OKAY [ 0.001s]
writing 'vbmeta_b'...
OKAY [ 0.005s]
sending sparse 'vendor_b' 1/4 (262140 KB)...
OKAY [ 8.484s]
writing 'vendor_b' 1/4...
OKAY [ 0.536s]
sending sparse 'vendor_b' 2/4 (262140 KB)...
OKAY [ 8.593s]
writing 'vendor_b' 2/4...
OKAY [ 0.424s]
sending sparse 'vendor_b' 3/4 (262140 KB)...
OKAY [ 8.432s]
writing 'vendor_b' 3/4...
OKAY [ 0.430s]
sending sparse 'vendor_b' 4/4 (206256 KB)...
OKAY [ 6.451s]
writing 'vendor_b' 4/4...
OKAY [ 0.359s]
Setting current slot to 'b'...
OKAY [ 0.032s]
rebooting...

finished. total time: 76.
 

anarchotaoist

Senior Member
Jun 2, 2018
68
8
18
I booted with fastboot boot recovery.img
and then tried the old method:

fastboot flash boot boot.img
$ fastboot flash dtbo dtbo.img
$ fastboot flash system system.img
$ fastboot flash system_ext system_ext.img
$ fastboot flash product product.img
$ fastboot flash vbmeta vbmeta.img
$ fastboot flash vbmeta_system vbmeta_system.img
$ fastboot reboot


I am still in a bootloop!

Help!
 

Dior DNA

Senior Member
Aug 17, 2015
1,448
631
133
I booted with fastboot boot recovery.img
and then tried the old method:

fastboot flash boot boot.img
$ fastboot flash dtbo dtbo.img
$ fastboot flash system system.img
$ fastboot flash system_ext system_ext.img
$ fastboot flash product product.img
$ fastboot flash vbmeta vbmeta.img
$ fastboot flash vbmeta_system vbmeta_system.img
$ fastboot reboot


I am still in a bootloop!

Help!
try to go back to previous slot perhaps
 

OhioYJ

Senior Member
Feb 25, 2011
1,420
690
133
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........: 72cfba44
--------------------------------------------
sending 'boot_b' (98304 KB)...
OKAY [ 3.121s]
writing 'boot_b'...
OKAY [ 0.377s]
sending 'dtbo_b' (24576 KB)...
OKAY [ 0.741s]
writing 'dtbo_b'...
OKAY [ 0.097s]
sending 'recovery_b' (98304 KB)...
OKAY [ 3.190s]
writing 'recovery_b'...
OKAY [ 0.272s]
sending sparse 'system_b' 1/4 (259064 KB)...
OKAY [ 8.531s]
writing 'system_b' 1/4...
OKAY [ 0.561s]
sending sparse 'system_b' 2/4 (258272 KB)...
OKAY [ 8.587s]
writing 'system_b' 2/4...
OKAY [ 0.451s]
sending sparse 'system_b' 3/4 (258272 KB)...
OKAY [ 8.550s]
writing 'system_b' 3/4...
OKAY [ 0.412s]
sending sparse 'system_b' 4/4 (210844 KB)...
OKAY [ 6.970s]
writing 'system_b' 4/4...
OKAY [ 0.371s]
sending 'vbmeta_b' (8 KB)...
OKAY [ 0.001s]
writing 'vbmeta_b'...
OKAY [ 0.005s]
sending sparse 'vendor_b' 1/4 (262140 KB)...
OKAY [ 8.484s]
writing 'vendor_b' 1/4...
OKAY [ 0.536s]
sending sparse 'vendor_b' 2/4 (262140 KB)...
OKAY [ 8.593s]
writing 'vendor_b' 2/4...
OKAY [ 0.424s]
sending sparse 'vendor_b' 3/4 (262140 KB)...
OKAY [ 8.432s]
writing 'vendor_b' 3/4...
OKAY [ 0.430s]
sending sparse 'vendor_b' 4/4 (206256 KB)...
OKAY [ 6.451s]
writing 'vendor_b' 4/4...
OKAY [ 0.359s]
Setting current slot to 'b'...
OKAY [ 0.032s]
rebooting...

finished. total time: 76.
What you are going through sounds a lot like what happened to me. My fastboot was outdated, and not flashing everything. See this post, and compare it to your flashed list.

I went back to stock just to be safe, updated fastboot / adb, reflashed and it worked first try. I've started a installing LOS Guide here.
 
  • Like
Reactions: Dior DNA

OhioYJ

Senior Member
Feb 25, 2011
1,420
690
133
Tired up with quality of oos developing and im considering jump to los..

May i ask again maybe same questions, lazy to use searching..

Is it stable enough to as daily driver?
Does it pass safetynet with props magisk module?
I'm using it as a daily driver, no issues here. Rooted using Magisk, passes safety net with the props module using the 8T fingerprint. So far I've been charging my phone generally every other day getting 10-12 hours of SOT (depending on what I do).
 
  • Like
Reactions: z00man

Dior DNA

Senior Member
Aug 17, 2015
1,448
631
133
Hi! Could you explain that please.
What is a slot and how do I go back to it?
Thanks.
slots are explained by AOSP Google seamless update doc
if you are on slot a, boot fastboot and do
fastboot --set-active=b
fastboot reboot
and vice versa if you are on slot b
but, I can say, I have been through very same cycles already and more
In fact I did:
- MSM recover
- update flash 11.0.6.9.KB05BA EU both slots
(using OxygenOS updater for 2nd slot)
(fwiw this gave widevine L1)
- use new method to flash LOS 18.1
flash success but boot fail (back to fastboot)
- use old method to flash LOS 18.1
(gives error for flash system)

I am ready for another MSM recover (since even other slot won't boot) :)

Anyway, not big deal, I have backups and can eventually restore OOS 11.0.6.9.KB05BA EU data

keep you informed

something might be wrong with my fastboot version ?
Code:
# fastboot --version
fastboot version 9.0.0_r3
Installed as /usr/bin/fastboot
 
Last edited:

Dior DNA

Senior Member
Aug 17, 2015
1,448
631
133
What you are going through sounds a lot like what happened to me. My fastboot was outdated, and not flashing everything. See this post, and compare it to your flashed list.

I went back to stock just to be safe, updated fastboot / adb, reflashed and it worked first try. I've started a installing LOS Guide here.
can you do a
Code:
fastboot --version
please?
Are you running Windows or Linux, if Linux (like me), which package manager (mine gentoo portage)?
 
Last edited:

anarchotaoist

Senior Member
Jun 2, 2018
68
8
18
can you do a
Code:
fastboot --version
please?
Are you running Windows or Linux, if Linux (like me), which package manager (mine gentoo portage)?
Hey, yeah I am running Kubuntu 20.10. Repo version is 1.8.1.0 +r23-8.
I have downloaded the latest adb tools -but cannot figure out how to install them system wide! ugh!
I added export PATH=${PATH}:/home/anarcho/bin/android/platform-tools/adb export PATH=${PATH}:/home/anarcho/bin/android/platform-tools/fastboot to /home/myname/.bashrc but the command remains unrecognised! What am I doing wrong? Thanks
 

jwarrior319

Senior Member
Aug 22, 2015
672
200
73
Black Creek, wi
Hey, yeah I am running Kubuntu 20.10. Repo version is 1.8.1.0 +r23-8.
I have downloaded the latest adb tools -but cannot figure out how to install them system wide! ugh!
I added export PATH=${PATH}:/home/anarcho/bin/android/platform-tools/adb export PATH=${PATH}:/home/anarcho/bin/android/platform-tools/fastboot to /home/myname/.bashrc but the command remains unrecognised! What am I doing wrong? Thanks
Do export PATH=${PATH}:/home/anarcho/bin/android/platform-tools/
Its looking for a directory not file. So when you use the adb or fastboot commands it'll search the directories specified in your path and find the in the platform-tools folder
 

OhioYJ

Senior Member
Feb 25, 2011
1,420
690
133
Hey, yeah I am running Kubuntu 20.10. Repo version is 1.8.1.0 +r23-8.
I have downloaded the latest adb tools -but cannot figure out how to install them system wide! ugh!
I added export PATH=${PATH}:/home/anarcho/bin/android/platform-tools/adb export PATH=${PATH}:/home/anarcho/bin/android/platform-tools/fastboot to /home/myname/.bashrc but the command remains unrecognised! What am I doing wrong? Thanks
I'm running Linux. That version of Fastboot is your problem. My Install guide I linked to has instructions on how to update it.

wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
sudo cp platform-tools/adb /usr/bin/adb
sudo cp platform-tools/fastboot /usr/bin/fastboot
 
  • Like
Reactions: Dior DNA