[ROM][OFFICIAL][kebab][11] LineageOS 18.1
- Thread starter LuK1337
- Start date
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!
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!
Hi! Could you explain that please.
What is a slot and how do I go back to it?
Thanks.
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.
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).
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:
can you do a
Code:
fastboot --versionAre you running Windows or Linux, if Linux (like me), which package manager (mine gentoo portage)?
Last edited:
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
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
Thank you!!! That was one piece of the puzzle! I then had a udev error and had to have an executable script for it - which did not work but after other commands eventually did!
I ran the installation which did not look good - but have now booted to lineageOS. What an epic journey!
Now I shall attempt to root!
OK, too bad recent linux distros do not catch up with latest google platform-tools ...
Also: the platform-tools versioning is a bit mysterious
ubuntu : 1:8.1.0+r23-8
gentoo: 9.0.0_r3
google: 30.0.5-6877874
Perhaps the google platform-tools URL could be mentioned in OP to help avoid bad flashing.
FWIW: for 8T EU :
I soft bricked mine twice (because I did not use latest platform tools),
so I went through following procedure twice:
- MSM restore EU to 11.0.5.6 active on _a (and I guess _b as well)
- incremental OTA to 11.0.6.9 active on _b
- local full ZIP update to 11.0.6.9 active on _a
- unlock bootloader
Then I end up security level L1 and system id 199909.
no magic no delay no interventions
However, an 8T IN user in widevine XDA thread claims this procedure did not help for his variant (though he did not flash 11.0.6.9 on both _a and _b)
Last edited:
>MSM restore EU to 11.0.5.6 active on _a (and I guess _b as well)
Not like MSM restore even cares about your slot setting, it always flashes to _a as far as I can tell.
>local full ZIP update to 11.0.6.9 active on _a
I don't think that makes any difference...
>Then I end up security level L1 and system id 199909.
I don't. Sounds like it's some kind of device roulette, idk.
D
Deleted member 5408779
Guest
Agreed, I just wondered, and guessed, MSM would perhaps flash on _b as well (or do you think MSM would leave _b empty or untouched?). I could have tested it.
Last edited:
Hey Card13, so all your issues are cleared?
I am on Kubuntu 20.10 also and connection with both USBc and USBa are flaky! I cannot seem to file transfer anything larger than 12mb in MTP!
nb I am not using Gapps.
I used to get L1 on LOS, but since you changed the rom with the new recovery and all, I have lost L1. And the ROMs that follow your device tree (evolution X, pixel experience, etc), they display the same phenomenon. Maybe it's the additional partitions in the rom zip that's causing these? (just wildly guessing)
PS: Going back to OOS 11.0.6.9 EU/11.0.6.8 IN or H2OS 11.0.6.8 -> all give L1 back on unlocked bootloader
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
46
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
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
More like few weeks after OOS12 kernel source is out.tomorrow afternoon 3 p.m
109
Yep, everyone already has it except you. We were about to call you, but you ruined it by asking.8
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.
New posts
-
-
set samsung galaxy s5 mini to 4g only- Latest: quadcore_yt
-
-
