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

Search This thread
By:
Advanced…
O

OTAx1

Senior Member
Mar 13, 2019
84
31
Anyone? No sense in trying it again until there's some feedback.

Device is NOT bricked. Can still reinstall the ROM, just will not boot to LOS...
 
K

koeksal

Member
Dec 6, 2018
11
2
OTAx1 said:
Anyone? No sense in trying it again until there's some feedback.

Device is NOT bricked. Can still reinstall the ROM, just will not boot to LOS...
Click to expand...
Click to collapse

Sadly I can't help you. I have exactly the same issue as you. Did exactly the same like you and also had to recover it with MSN Tool. Only difference is that my device is a KB2003. I let OOS get all updates and used latest Platform-Tools, but after flashing I get stuck in fastboot, too.
 
OhioYJ

OhioYJ

Senior Member
Feb 25, 2011
1,590
841
OTAx1 said:
Anyone? No sense in trying it again until there's some feedback.

Device is NOT bricked. Can still reinstall the ROM, just will not boot to LOS...
Click to expand...
Click to collapse

Did it even boot LOS without trying to install anything else? I notice Magisk says it can't mount system. A new build was just uploaded. I updated my phone and compared my phone to your image and every thing was the same except mine was able to mount the partitions and continued on with the installation.
 
O

OTAx1

Senior Member
Mar 13, 2019
84
31
OhioYJ said:
Did it even boot LOS without trying to install anything else? I notice Magisk says it can't mount system. A new build was just uploaded. I updated my phone and compared my phone to your image and every thing was the same except mine was able to mount the partitions and continued on with the installation.
Click to expand...
Click to collapse

No, never booted to LOS. I just tried Magisk later for kicks.

Hearing on other 8T threads, ADB booting with boot.img (not flashing) from the build will make it past bootloop. Worth a try
 
A

Ankorad

Member
Apr 5, 2011
12
0
Just flashed lineage OS and now I got lags in almost every App. Spotify, Radio App, COD Mobile... any ideas??
 
OhioYJ

OhioYJ

Senior Member
Feb 25, 2011
1,590
841
OTAx1 said:
No, never booted to LOS. I just tried Magisk later for kicks.

Hearing on other 8T threads, ADB booting with boot.img (not flashing) from the build will make it past bootloop. Worth a try
Click to expand...
Click to collapse

Wait what boot.img are you flashing? Are you trying to do the old install method (where you install /flash each thing indivually, that will make it bootloop)? The new instructions are (from the OP):
  • 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 ( use up to date platform tools for this step )
 
O

OTAx1

Senior Member
Mar 13, 2019
84
31
OhioYJ said:
Wait what boot.img are you flashing? Are you trying to do the old install method (where you install /flash each thing indivually, that will make it bootloop)? The new instructions are (from the OP):
  • 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 ( use up to date platform tools for this step )
Click to expand...
Click to collapse

Exactly per above instructions. Using only latest LuK1337 file. That's what is puzzling. It just goes straight to Fastboot every time
 
LuK1337

LuK1337

Recognized Developer
Jan 18, 2013
8,940
18,141
Samsung Galaxy S III I9300
Moto G 2014
OTAx1 said:
Exactly per above instructions. Using only latest LuK1337 file. That's what is puzzling. It just goes straight to Fastboot every time
Click to expand...
Click to collapse
Not sure what kind of help y'all expect when you give no info other than "did everything perfect☆" + "boots to fastboot".
Really would it hurt to just post output of all commands...?
 
Last edited:
  • Like
Reactions: Dior DNA
K

koeksal

Member
Dec 6, 2018
11
2
This one ends up in Fastboot, too...

Code: 
fastboot update lineage-18.1-20210224_183303-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 (964 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........: xxxxxxxx
--------------------------------------------
sending 'boot_b' (98304 KB)...
OKAY [  2.870s]
writing 'boot_b'...
OKAY [  0.545s]
sending 'dtbo_b' (24576 KB)...
OKAY [  0.721s]
writing 'dtbo_b'...
OKAY [  0.158s]
sending 'recovery_b' (98304 KB)...
OKAY [  2.990s]
writing 'recovery_b'...
OKAY [  0.291s]
sending sparse 'system_b' 1/4 (259064 KB)...
OKAY [  7.947s]
writing 'system_b' 1/4...
OKAY [  0.567s]
sending sparse 'system_b' 2/4 (258272 KB)...
OKAY [  7.716s]
writing 'system_b' 2/4...
OKAY [  0.460s]
sending sparse 'system_b' 3/4 (258272 KB)...
OKAY [  7.987s]
writing 'system_b' 3/4...
OKAY [  0.489s]
sending sparse 'system_b' 4/4 (211956 KB)...
OKAY [  6.572s]
writing 'system_b' 4/4...
OKAY [  0.424s]
sending 'vbmeta_b' (8 KB)...
OKAY [  0.001s]
writing 'vbmeta_b'...
OKAY [  0.003s]
sending sparse 'vendor_b' 1/4 (262140 KB)...
OKAY [  8.106s]
writing 'vendor_b' 1/4...
OKAY [  0.594s]
sending sparse 'vendor_b' 2/4 (262140 KB)...
OKAY [  8.210s]
writing 'vendor_b' 2/4...
OKAY [  0.489s]
sending sparse 'vendor_b' 3/4 (262140 KB)...
OKAY [  8.044s]
writing 'vendor_b' 3/4...
OKAY [  0.476s]
sending sparse 'vendor_b' 4/4 (206420 KB)...
OKAY [  6.424s]
writing 'vendor_b' 4/4...
OKAY [  0.396s]
Setting current slot to 'b'...
OKAY [  0.031s]
rebooting...

finished. total time: 72.565s
 
LuK1337

LuK1337

Recognized Developer
Jan 18, 2013
8,940
18,141
Samsung Galaxy S III I9300
Moto G 2014
koeksal said:
This one ends up in Fastboot, too...

Code: 
fastboot update lineage-18.1-20210224_183303-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 (964 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........: xxxxxxxx
--------------------------------------------
sending 'boot_b' (98304 KB)...
OKAY [  2.870s]
writing 'boot_b'...
OKAY [  0.545s]
sending 'dtbo_b' (24576 KB)...
OKAY [  0.721s]
writing 'dtbo_b'...
OKAY [  0.158s]
sending 'recovery_b' (98304 KB)...
OKAY [  2.990s]
writing 'recovery_b'...
OKAY [  0.291s]
sending sparse 'system_b' 1/4 (259064 KB)...
OKAY [  7.947s]
writing 'system_b' 1/4...
OKAY [  0.567s]
sending sparse 'system_b' 2/4 (258272 KB)...
OKAY [  7.716s]
writing 'system_b' 2/4...
OKAY [  0.460s]
sending sparse 'system_b' 3/4 (258272 KB)...
OKAY [  7.987s]
writing 'system_b' 3/4...
OKAY [  0.489s]
sending sparse 'system_b' 4/4 (211956 KB)...
OKAY [  6.572s]
writing 'system_b' 4/4...
OKAY [  0.424s]
sending 'vbmeta_b' (8 KB)...
OKAY [  0.001s]
writing 'vbmeta_b'...
OKAY [  0.003s]
sending sparse 'vendor_b' 1/4 (262140 KB)...
OKAY [  8.106s]
writing 'vendor_b' 1/4...
OKAY [  0.594s]
sending sparse 'vendor_b' 2/4 (262140 KB)...
OKAY [  8.210s]
writing 'vendor_b' 2/4...
OKAY [  0.489s]
sending sparse 'vendor_b' 3/4 (262140 KB)...
OKAY [  8.044s]
writing 'vendor_b' 3/4...
OKAY [  0.476s]
sending sparse 'vendor_b' 4/4 (206420 KB)...
OKAY [  6.424s]
writing 'vendor_b' 4/4...
OKAY [  0.396s]
Setting current slot to 'b'...
OKAY [  0.031s]
rebooting...

finished. total time: 72.565s
Click to expand...
Click to collapse
It skipped like half of files... What's the output of fastboot --version?
 
O

OTAx1

Senior Member
Mar 13, 2019
84
31
koeksal said:
You're right...I was sure I updated platform-tools last time...:ROFLMAO:😒
Now trying with fastboot version 31.0.0-7110759 it boots as expected.
Thanks for that hint.
Click to expand...
Click to collapse

That's encouraging. At the time I flashed, latest platform tools were r30.0.5 (Linux); there's no r31.0 out for that OS yet.

[update] No r31.0 at official SDK site, however XDA does have it for Linux!

Maybe the OP can update link to the version that works so this doesn't happen to others ;)

Will report back later after trying it again with new tools
 
Last edited:
  • Like
Reactions: Lz3807775t
LuK1337

LuK1337

Recognized Developer
Jan 18, 2013
8,940
18,141
Samsung Galaxy S III I9300
Moto G 2014
O

OTAx1

Senior Member
Mar 13, 2019
84
31
Nope. Still goes to fastboot loop :(
-----------------------------------------------


root@xxxx:/home/xxxx/platform-tools_r31.0.0# fastboot update lineage-18.1-20210224_183303-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 (964 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........: xxxx
--------------------------------------------
sending 'boot_b' (98304 KB)...
OKAY [ 2.433s]
writing 'boot_b'...
OKAY [ 0.368s]
sending 'dtbo_b' (24576 KB)...
OKAY [ 0.606s]
writing 'dtbo_b'...
OKAY [ 0.093s]
sending 'recovery_b' (98304 KB)...
OKAY [ 2.440s]
writing 'recovery_b'...
OKAY [ 0.280s]
sending sparse 'system_b' 1/4 (259064 KB)...
OKAY [ 6.442s]
writing 'system_b' 1/4...
OKAY [ 0.526s]
sending sparse 'system_b' 2/4 (258272 KB)...
OKAY [ 6.428s]
writing 'system_b' 2/4...
OKAY [ 0.432s]
sending sparse 'system_b' 3/4 (258272 KB)...
OKAY [ 6.477s]
writing 'system_b' 3/4...
OKAY [ 0.423s]
sending sparse 'system_b' 4/4 (211956 KB)...
OKAY [ 5.254s]
writing 'system_b' 4/4...
OKAY [ 0.362s]
sending 'vbmeta_b' (8 KB)...
OKAY [ 0.001s]
writing 'vbmeta_b'...
OKAY [ 0.004s]
sending sparse 'vendor_b' 1/4 (262140 KB)...
OKAY [ 6.466s]
writing 'vendor_b' 1/4...
OKAY [ 0.545s]
sending sparse 'vendor_b' 2/4 (262140 KB)...
OKAY [ 6.496s]
writing 'vendor_b' 2/4...
OKAY [ 0.432s]
sending sparse 'vendor_b' 3/4 (262140 KB)...
OKAY [ 6.502s]
writing 'vendor_b' 3/4...
OKAY [ 0.422s]
sending sparse 'vendor_b' 4/4 (206420 KB)...
OKAY [ 5.160s]
writing 'vendor_b' 4/4...
OKAY [ 0.352s]
Setting current slot to 'b'...
OKAY [ 0.030s]
rebooting...

finished. total time: 59.026s
root@xxxx:/home/xxxx/platform-tools_r31.0.0#
 
LuK1337

LuK1337

Recognized Developer
Jan 18, 2013
8,940
18,141
Samsung Galaxy S III I9300
Moto G 2014
OTAx1 said:
I agree it should. But my log was same as koeksal, lots of files missed.
Click to expand...
Click to collapse
OTAx1 said:
Nope. Still goes to fastboot loop :(
-----------------------------------------------


root@xxxx:/home/xxxx/platform-tools_r31.0.0# fastboot update lineage-18.1-20210224_183303-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 (964 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........: xxxx
--------------------------------------------
sending 'boot_b' (98304 KB)...
OKAY [ 2.433s]
writing 'boot_b'...
OKAY [ 0.368s]
sending 'dtbo_b' (24576 KB)...
OKAY [ 0.606s]
writing 'dtbo_b'...
OKAY [ 0.093s]
sending 'recovery_b' (98304 KB)...
OKAY [ 2.440s]
writing 'recovery_b'...
OKAY [ 0.280s]
sending sparse 'system_b' 1/4 (259064 KB)...
OKAY [ 6.442s]
writing 'system_b' 1/4...
OKAY [ 0.526s]
sending sparse 'system_b' 2/4 (258272 KB)...
OKAY [ 6.428s]
writing 'system_b' 2/4...
OKAY [ 0.432s]
sending sparse 'system_b' 3/4 (258272 KB)...
OKAY [ 6.477s]
writing 'system_b' 3/4...
OKAY [ 0.423s]
sending sparse 'system_b' 4/4 (211956 KB)...
OKAY [ 5.254s]
writing 'system_b' 4/4...
OKAY [ 0.362s]
sending 'vbmeta_b' (8 KB)...
OKAY [ 0.001s]
writing 'vbmeta_b'...
OKAY [ 0.004s]
sending sparse 'vendor_b' 1/4 (262140 KB)...
OKAY [ 6.466s]
writing 'vendor_b' 1/4...
OKAY [ 0.545s]
sending sparse 'vendor_b' 2/4 (262140 KB)...
OKAY [ 6.496s]
writing 'vendor_b' 2/4...
OKAY [ 0.432s]
sending sparse 'vendor_b' 3/4 (262140 KB)...
OKAY [ 6.502s]
writing 'vendor_b' 3/4...
OKAY [ 0.422s]
sending sparse 'vendor_b' 4/4 (206420 KB)...
OKAY [ 5.160s]
writing 'vendor_b' 4/4...
OKAY [ 0.352s]
Setting current slot to 'b'...
OKAY [ 0.030s]
rebooting...

finished. total time: 59.026s
root@xxxx:/home/xxxx/platform-tools_r31.0.0#
Click to expand...
Click to collapse
You know you need to do `./` when attempting to execute a file from $PWD? Otherwise it'll attempt to find the executable in $PATH which may as well happen to be from old distro pkg...
 
You must log in or register to reply here.

Similar threads

D
ROM[OFFICIAL][kebab][11.0]**crDroid**[V7.14]
Replies
583
Views
98K
3MrBojangles3
3MrBojangles3
theincognito
  • Locked
[CLOSED] [No longer maintained] [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project (8T / Kebab) (2022-03-09)
Replies
566
Views
118K
shadowstep
shadowstep
LuK1337
[ROM][OFFICIAL][kebab][13] LineageOS 20
Replies
515
Views
59K
V
Vipe838
R
[ROM][11][OnePlus8T] PixelExperience [AOSP]
Replies
468
Views
124K
GraveDigger176
GraveDigger176
chandu dyavanapelli
[ROM][OFFICIAL][OOS CAM][OnePlus 8T/9R][12.1.0_r11]Nameless AOSP[2022/07/23]
Replies
1K
Views
180K
V
Vish11

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 46
    LuK1337
    LuK1337
    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:
    View
    11
    LuK1337
    LuK1337
    exthomeboy said:
    tomorrow afternoon 3 p.m 😆
    Click to expand...
    Click to collapse
    More like few weeks after OOS12 kernel source is out.
    View
    10
    theincognito
    theincognito
    Yaay. The thread is back. :D
    View
    9
    T
    thefanum
    Phoenix47 said:
    Any update about LOS 19 ?
    Click to expand...
    Click to collapse
    Yep, everyone already has it except you. We were about to call you, but you ruined it by asking.
    View
    8
    OhioYJ
    OhioYJ
    Phoenix47 said:
    There are already oos 12 firmware based roms available so I asked if LOS 19 is coming soon or not.
    Click to expand...
    Click to collapse

    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.
    View

New posts