• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[OFFICIAL] [Ten] Lineage 17.1

Search This thread

art2111

Senior Member
Oct 23, 2011
192
25
Hi, I installed Lineage 17.1 and now I don't have TWRP. How can I restore it and install another ROM instead of Lineage 17.1?

Thank you.
 

4ngl09669

Senior Member
Jan 21, 2017
82
13
Nokia Lumia 820
Sony Xperia Z
Hi everyone,
I have a problem. I tried to install lineage 17.1 + Gapps and it doesn't work, the device gets stuck on the initial loading screen. Installing only Lineage instead it works...

I already have the latest official TWRP available installed, and I come from another custom ROM of Android 11, but obviously I have cleaned everything from TWRP.

Anyone have ideas?
 

linuxnoobbbb

Member
Feb 25, 2012
40
12
Hi everyone,
I have a problem. I tried to install lineage 17.1 + Gapps and it doesn't work, the device gets stuck on the initial loading screen. Installing only Lineage instead it works...

I already have the latest official TWRP available installed, and I come from another custom ROM of Android 11, but obviously I have cleaned everything from TWRP.

Anyone have ideas?
I got bootloop as well, with the latest LOS 20201217 and the latest OpenGapps stock 20201222. I think it might be related to OpenGapps.

I got bootloop with the old build of last month as well, then I found that an old OpenGapps release worked - however the last worked OpenGapps stock 20201119 (Sorry! OpenGapps stock 20201119 DIDN'T WORK at that time either. I checked my notes, then I found I misremembered it. It was OpenGapps stock 20201029 which actually worked at that time, NOT 20201119) no longer seems to work with LOS 20201217. I'm then trying older OpenGapps, will edit this reply when I see the outcome. Tried OpenGapps 20200827, it works.
 
Last edited:

linuxnoobbbb

Member
Feb 25, 2012
40
12
Hi, I installed Lineage 17.1 and now I don't have TWRP. How can I restore it and install another ROM instead of Lineage 17.1?

Thank you.

1. Use fastboot to flash TWRP into the recovery partition.
2. Use QPST/QFIL's partition manager to flash TWRP into recovery partition - the firehose programmer file is required, which can be obtained from stock ROM package. To enter EDL (9008) mode, you may try "deep flash USB cable".
 
  • Like
Reactions: art2111

andrepd

Senior Member
Dec 4, 2011
85
3
Hello. I followed the instructions on the lineage os website and after I adbsideload the lineage os zip succesfully. I go to reboot to system from recovery and it tells me there is no OS installed. It then boots into a blue screen. I was previously on jaguar 8.1 Rom. Am I missing something? Thank you

Hi! I'm having the same issue here when upgrading from a LineageOS Nougat rom. I read through the next pages and if I understand correctly I should use qfil/qdl to flash ZUI4.0?

Only this will lock my bootloader again right? And wipe twrp? MOST IMPORTANTLY, will it wipe my data in internal storage??

Is there any way to flash only the firmware without wiping anything else, like twrp and relocking bootloader etc?

Thanks, any help would be appreciated!

EDIT: For example here https://forum.xda-developers.com/t/...gh-twrp-without-relocking-bootloader.3576196/ they suggest removing emmc_appsboot.bin from the zip to be flashed. Will this work in this case?

EDIT2: I'm even more confused, the ZUI4.0 zip I downloaded has a whole bunch of stuff inside. What should I flash? I chose 'flat build' then there are two .elf binaries (lite and ddr), which am I supposed to pick? Then if I load a .xml again I have two to pick (one says retain_userdata, say I pick that). Then finally there's a patch file.
 
Last edited:

andrepd

Senior Member
Dec 4, 2011
85
3
Update: hooray! I finally found my unlock_bootloader.img somewhere in my old computer :D So even if I lock it by flashing ZUI 4 with qfil I can unlock again.

The question still stands, before I can go ahead with this: will it delete my internal storage, and is there a way to only flash firmware?
 
Last edited:

andrepd

Senior Member
Dec 4, 2011
85
3

prakashitbhav

Senior Member
Sep 2, 2017
296
240
Bengaluru
Another update: this thread https://web.archive.org/web/2019042...-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/ says that "USB flashing will wipe your internal phone storage!", also that I should lock my bootloader first or it will brick my phone. So what should i do?! Is there any way to just flash the correct firmware and be done with it?

Again, thanks for any help and thanks for your work in this ROM :)
You cannot qfil stock rom without wiping internal storage.
There are some TWRP flashable versions of stock rom available, but if you flash using twrp, why not flash some better ones :)
 

andrepd

Senior Member
Dec 4, 2011
85
3
You cannot qfil stock rom without wiping internal storage.

There are some TWRP flashable versions of stock rom available, but if you flash using twrp, why not flash some better ones :)

Hi, thanks for the reply!

I want to flash this LineageOS rom, however when I did it just enters into a blue-screen bootloop. So apparently I should update firmware by flashing the stock rom with QPST... This is why I need to flash that. Do you know if there is a way to flash only firmware and not wipe anything else?


Hi! Can you tell me something please? If you flashed with QPST/QFIL, did it delete your internal storage?? Thanks for the help!
 

fsck-justin

Member
Mar 28, 2016
15
1
In my lineageos 17.1 install, miracast service would not start. It worked in my 16 install.


--------- beginning of crash
10-04 19:32:49.097 3125 3125 F linker : CANNOT LINK EXECUTABLE "/system/bin/wfdservice": library "[email protected]" not found
10-04 19:32:53.643 5005 5209 E JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 920)
10-04 19:32:53.659 5005 5209 E JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 312)
10-04 19:32:54.058 3104 3123 E WiFiDisplayClient: wfdservice not available!
10-04 19:32:54.059 3104 3123 E WFDSession_1: nativeCreateWfdSession failed!
10-04 19:32:54.075 3104 3123 E WFDSession_1: deinit: mState = INITIALIZED
10-04 19:32:54.075 3104 3123 E : uibc_Fields_t dtor()
10-04 19:32:54.075 3104 3123 E WiFiDisplayClient: ~WiFiDisplayClient
10-04 19:32:54.075 3104 3123 E WiFiDisplayClient: ~WifiDisplayListener Dtor
10-04 19:32:56.102 1847 1847 E wpa_supplicant: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p0/drop_unicast_in_l2_multicast: No such file or directory
10-04 19:32:56.102 1847 1847 E wpa_supplicant: nl80211: Failed to set IPv4 unicast in multicast filter
10-04 19:32:56.105 1847 1847 E wpa_supplicant: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p0/drop_unicast_in_l2_multicast: No such file or directory
10-04 19:32:56.105 1847 1847 E wpa_supplicant: nl80211: Failed to set IPv4 unicast in multicast filter
10-04 19:32:56.716 1392 1405 E Netd : getIfIndex: cannot find interface p2p0
10-04 19:32:56.716 1392 1405 E Netd : inconceivable! added interface p2p0 with no index
10-04 19:32:58.700 5005 5209 E JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 920)
10-04 19:32:58.721 5005 5209 E JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 312)

It seems to be the case of crashing.
 

sujayrai

Member
Apr 13, 2020
6
2
Hi All,

I've been using lineage 17.1 for almost 6 months now, however post some update in February my insta videos/reels has started to pixelate while watching I've reinstalled the app many times but no success & also I'm unable to report the problem to Instagram as well because whenever I try sharing the report it gives failed error.
 

Attachments

  • Screenshot_20210310-235509_Instagram.png
    Screenshot_20210310-235509_Instagram.png
    1.5 MB · Views: 27

muralee krishna

Senior Member
Jan 18, 2018
104
12
Hi All,

I've been using lineage 17.1 for almost 6 months now, however post some update in February my insta videos/reels has started to pixelate while watching I've reinstalled the app many times but no success & also I'm unable to report the problem to Instagram as well because whenever I try sharing the report it gives failed error.
i also have same problem but i am having that problem in evolution x and pixel experience rom
 

Eden blizzard

Senior Member
Nov 12, 2013
180
27
Hi All,

I've been using lineage 17.1 for almost 6 months now, however post some update in February my insta videos/reels has started to pixelate while watching I've reinstalled the app many times but no success & also I'm unable to report the problem to Instagram as well because whenever I try sharing the report it gives failed error.
Same issue here also tried everything but nothing worked
 
  • Like
Reactions: muralee krishna

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    2okPze5.png

    Code:
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */

    LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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.

    Bugs :
    • You tell me

    Instructions :
    • Download the latest build
    • Reboot to recovery
    • Flash the latest build
    • Reboot

    Downloads :

    Notes :
    • Only Clean Installation Please
    • Bug Report Without logs means nothing

    Reporting Bugs :
    • DO NOT Report bugs if you installed Xposed or weird magisk modules
    • 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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)

    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.

    Sources :

    XDA:DevDB Information
    LineageOS 17.1 for z2_plus, ROM for the Lenovo ZUK Z2 (Plus)

    Contributors
    DD3Boh, Kubersharma, dmd79
    Source Code: https://github.com/LineageOS

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    ROM Firmware Required: ZUI 3.5 bootloader
    Based On: AOSP

    Version Information
    Status: Stable

    Created 2020-01-14
    Last Updated 2020-04-02
    25
    Reserved

    Unofficial builds deleted on April 2nd 2020
    7
    Hey guys, despite me being inactive (as usual) with unofficial builds releases, lineage-17.1 official builds are finally here :D

    If you want to dirty flash from 17.1 unofficial builds, that can be done migrating keys with a guide located here

    Dirty flash from lineage-16.0 is supported but of course needs gapps to be reflashed.

    All useful links are in the first post as usual, enjoy and stay safe!
    3
    Huge thanks to the developer, very exciting to have Android 10 up and running on my device, with encryption in place! :)

    PS: I couldn't get the beta version of Open GApps to flash in TWRP - It complained about a missing file in the ROM - I didn't make a note of what it said but I tried BitGApps instead and that worked fine: https://bitgapps.cf/arm64/Q/

    The 20200115 gapps beta build was the problem. The next beta gapps should have it fixed.