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

Search This thread

LuK1337

Recognized Developer
Jan 18, 2013
8,325
16,639
Samsung Galaxy S III I9300
Moto G 2014
No recovery.img in zip. There's boot.img, not assuming it's the same file
hmm?
Code:
Archive:  lineage-18.1-20210217_093726-UNOFFICIAL-kebab.zip
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  02-17-2021 10:37   android-info.txt
 54059008  02-17-2021 10:36   boot-debug.img
100663296  02-17-2021 10:36   boot.img
  1894960  02-17-2021 10:24   dtb.img
 25165824  02-17-2021 10:24   dtbo.img
  1224816  02-17-2021 10:33   odm.img
342700360  02-17-2021 10:36   product.img
  1406865  02-17-2021 10:23   ramdisk-debug.img
  1261214  02-17-2021 10:23   ramdisk.img
  9752542  02-17-2021 10:26   ramdisk-recovery.img
100663296  02-17-2021 10:36   recovery.img
     5080  02-17-2021 10:23   super_empty.img
207687924  02-17-2021 10:36   system_ext.img
1011249588  02-17-2021 10:37   system.img
  1004220  02-17-2021 10:33   userdata.img
     8192  02-17-2021 10:37   vbmeta.img
     4096  02-17-2021 10:37   vbmeta_system.img
1016668464  02-17-2021 10:37   vendor.img
---------                     -------
2875419745                     18 files
 
  • Like
Reactions: OTAx1

OTAx1

Senior Member
Mar 13, 2019
52
26
After unbricking with MSM Download Tool & full restore couple times....

Went through OP steps exactly with latest Platform-tools as ROOT (Linux), and every time I get fastboot loop. Also, could not run $ fastboot boot recovery.img without first unlocking bootloader.

Any ideas? Thanks
 

tom65824

Senior Member
Aug 3, 2018
53
11
will try it again (with op) these days and report back
(for now I'm glad that I could restore the original state) ;-)

could not wait
and tried it again yesterday ;-)

worked wonderfully. looks first time pretty boring, but will be fine.
thanks for all your work, Luk1337
 

OTAx1

Senior Member
Mar 13, 2019
52
26
LOS Installed, still does fastboot loop..tried sideloading latest Magisk, still no luck...blah

Fyi. This was a factory sealed new KB2005, & I used the proper MSM Tool to unbrick, 4 times already!

Yes I'm using the latest Fastboot & ROOT when flashing. Out of the box, OOS took all updates prior to flash, unlocked bootloader, installed LOS. Never got past Fastboot even once. Cannot boot to LOS. Period.

IMG_20210222_142140.jpg
 
Last edited:

OTAx1

Senior Member
Mar 13, 2019
52
26
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...
 

koeksal

Member
Dec 6, 2018
10
1
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...

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

Senior Member
Feb 25, 2011
1,436
707
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...

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.
 

OTAx1

Senior Member
Mar 13, 2019
52
26
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.

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
 

OhioYJ

Senior Member
Feb 25, 2011
1,436
707
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

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 )
 

OTAx1

Senior Member
Mar 13, 2019
52
26
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 )

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

LuK1337

Recognized Developer
Jan 18, 2013
8,325
16,639
Samsung Galaxy S III I9300
Moto G 2014
Exactly per above instructions. Using only latest LuK1337 file. That's what is puzzling. It just goes straight to Fastboot every time
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

koeksal

Member
Dec 6, 2018
10
1
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
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Oh I know. Was just checking to see if it was installed in the ROM by default. Some LOS roms have them installed. I'm going to assume that they aren't and if I want to flash I can.

    Appreciate the help
    Official builds never ship with gapps.
    2
    So if I use the official instructions I keep getting an error. It won't install via that method.

    - I've tried updating the recovery.
    - I did a factory reset, format data.
    - I ran the copy partition script listed, and it ran successfully.

    When trying to sideload the zip it says:

    Step 1/2
    Error appying update 7 (ErrorCode : : kInstallDeviceOpenError)
    E:Error in /sideload/package.zip (status 1)

    It goes no further. When I reboot, I still have the previous unofficial build.
    2
    When trying to sideload the zip it says:

    Step 1/2
    Error appying update 7 (ErrorCode : : kInstallDeviceOpenError)
    E:Error in /sideload/package.zip (status 1)

    It goes no further. When I reboot, I still have the previous unofficial build.

    I have the same issue so I looked at the recovery log and it looks like there's something being miscalculated during the partition setup, causing the error 7:

    Code:
    [   52.774938] update_engine_sideload E 04-26 03:38:27   621   621 [ERROR:dynamic_partition_control_android.cc(803)] The maximum size of all groups with suffix _a (7511998464) has exceeded half of allocatable space for dynamic partitions 3757572096.
    [   52.774939] update_engine_sideload E 04-26 03:38:27   621   621 [ERROR:delta_performer.cc(995)] Unable to initialize partition metadata for slot A
    [   52.774941] update_engine_sideload E 04-26 03:38:27   621   621 [ERROR:download_action.cc(336)] Error ErrorCode::kInstallDeviceOpenError (7) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
    2
    Hello guys.. hm... I am new oneplus user and i want to install this rom. Can someone help me? 🙂
    Instructions :
    Downloads :
    1
    I know, but not this version (OnePlus 8T isn't listed on LineageOS website yet).

    it is. However, let me know if you get it to install, using their instructions.
  • 23
    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:
    5
    How do you do backups? What would be a good way to keep backups if I wanted to flash this ROM on a semi daily basis? I noticed after flashing the ROM it asks if I want to restore from a backup.

    Another observation as I flashed the GMS version last night is there was no gallery app. Maybe this is normal.

    I would suggest Swift Backup. Was a titanium user, but I find Swift Backup to be better performing on Android 11.
    5
    Yaay. The thread is back. :D
    4
    You could try to run fastboot --version and ./fastboot --version in your platform-tools directory and compare the output.

    Adding ./ did it. Thanks! :cool:

    IMG_20210228_102128.jpg
    3
    One more question. Is it normal for the device I'd to change from kb2007 to kb2003?
    Yes, adding model detection is a waste of time so it'll always show KB2003.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone