[OFFICIAL] [Ten] Lineage 17.1

Search This thread

R a BB i t

Member
Aug 4, 2015
27
1
I have hard bricked my phone (I guess),
1)Phones not booting up, no led, no charging indications
2)Few days before hard brick the phone wouldn't boot post boot screen option if turned off (IDK Y)
3)Was constantly updated via OTA (last update would be before 29th of Aug as from 1st Sept phone has died
4) PC connection shows QUSB_Bulk. Unable to find a perfect tutorial to bring it back to life as zukfans.eu web is down

Any assistance would be highly appreciated, as I'm locked out of my web life as all my password & 2fa are within the phone (lazy ass habit had got me troubled) hence unable to go for full flash nor able to find any tutorial to bring it back to life
Help is on your way!

Get it revived here: https://t.me/zuk_z2_plus
 
Last edited:

linuxnoobbbb

Senior Member
Feb 25, 2012
56
14
I have hard bricked my phone (I guess),
1)Phones not booting up, no led, no charging indications
2)Few days before hard brick the phone wouldn't boot post boot screen option if turned off (IDK Y)
3)Was constantly updated via OTA (last update would be before 29th of Aug as from 1st Sept phone has died
4) PC connection shows QUSB_Bulk. Unable to find a perfect tutorial to bring it back to life as zukfans.eu web is down

Any assistance would be highly appreciated, as I'm locked out of my web life as all my password & 2fa are within the phone (lazy ass habit had got me troubled) hence unable to go for full flash nor able to find any tutorial to bring it back to life
Previously I have described about the test points and "deep flash USB cable".
 

linuxnoobbbb

Senior Member
Feb 25, 2012
56
14
Not booting after manually upgrading to 18.1 20211111 with TWRP. Decryption prompt didn't show up. I'm now reverting to 17.1.

Flashed OpenGapps stock (excluded some apps to save some space). Patched boot.img with Magisk. Encryption (FDE) has been enabled for quite some time.

Got this logcat after enabling adb through editing /system/etc/prop.default:

Code:
11-13 08:54:32.841  1557  1557 F appproc : app_process: Unable to determine ABI list from property ro.product.cpu.abilist32.
11-13 08:54:32.841  1557  1557 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 1557 (app_process32), pid 1557 (app_process32)
11-13 08:54:32.870  1563  1563 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-13 08:54:32.870  1563  1563 F DEBUG   : LineageOS Version: 'unknown'
11-13 08:54:32.870  1563  1563 F DEBUG   : Build fingerprint: 'ZUK/z2_plus/z2_plus:unknown/unknown/unknown:unknown/unknown'
11-13 08:54:32.870  1563  1563 F DEBUG   : Revision: '0'
11-13 08:54:32.870  1563  1563 F DEBUG   : ABI: 'arm64'
11-13 08:54:32.870  1563  1563 F DEBUG   : Timestamp: 2021-11-13 08:54:32+0000
11-13 08:54:32.870  1563  1563 F DEBUG   : pid: 1556, tid: 1556, name: app_process64  >>> /system/bin/app_process64 <<<
11-13 08:54:32.870  1563  1563 F DEBUG   : uid: 0
11-13 08:54:32.870  1563  1563 F DEBUG   : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
11-13 08:54:32.871  1563  1563 F DEBUG   : Abort message: 'app_process: Unable to determine ABI list from property ro.product.cpu.abilist64.'
11-13 08:54:32.871  1563  1563 F DEBUG   :     x0  0000000000000000  x1  0000000000000614  x2  0000000000000006  x3  0000007fe41a5010
11-13 08:54:32.871  1563  1563 F DEBUG   :     x4  0000000000000000  x5  0000000000000000  x6  0000000000000000  x7  7f7f7f7f7f7f7f7f
11-13 08:54:32.871  1563  1563 F DEBUG   :     x8  00000000000000f0  x9  20afbbadface79f4  x10 ffffff80ffffffdf  x11 ffffffc0ffffffdf
11-13 08:54:32.871  1563  1563 F DEBUG   :     x12 0000000000000000  x13 0000000000000000  x14 0000000000000000  x15 000000000146d2f6
11-13 08:54:32.871  1563  1563 F DEBUG   :     x16 0000007857787c78  x17 0000007857769c20  x18 000000785d0f2000  x19 00000000000000ac
11-13 08:54:32.871  1563  1563 F DEBUG   :     x20 0000000000000614  x21 00000000000000b2  x22 0000000000000614  x23 00000000ffffffff
11-13 08:54:32.871  1563  1563 F DEBUG   :     x24 00000063610ad034  x25 0000000000000005  x26 00000063610b2088  x27 0000000000000001
11-13 08:54:32.871  1563  1563 F DEBUG   :     x28 000000785c208000  x29 0000007fe41a5090
11-13 08:54:32.872  1563  1563 F DEBUG   :     lr  000000785771b56c  sp  0000007fe41a4ff0  pc  000000785771b598  pst 0000000000000000
11-13 08:54:32.875  1563  1563 F DEBUG   : backtrace:
11-13 08:54:32.875  1563  1563 F DEBUG   :       #00 pc 000000000004e598  /apex/com.android.runtime/lib64/bionic/libc.so (abort+176) (BuildId: 6fef2b0ca43a1525af04ae1c6da427de)
11-13 08:54:32.875  1563  1563 F DEBUG   :       #01 pc 00000000000062a0  /system/lib64/liblog.so (__android_log_default_aborter+12) (BuildId: b5e84530b2278e3780a02ed82997eafa)
11-13 08:54:32.875  1563  1563 F DEBUG   :       #02 pc 0000000000006dfc  /system/lib64/liblog.so (__android_log_assert+336) (BuildId: b5e84530b2278e3780a02ed82997eafa)
11-13 08:54:32.875  1563  1563 F DEBUG   :       #03 pc 0000000000003750  /system/bin/app_process64 (main+1800) (BuildId: 576b5cec43a5536af58efd0f281bade1)
11-13 08:54:32.875  1563  1563 F DEBUG   :       #04 pc 0000000000049aec  /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: 6fef2b0ca43a1525af04ae1c6da427de)

After editing /vendor/build.prop:
Code:
11-13 09:11:24.118  1433  1433 E Zygote  : Error preloading android.content.pm.PackageParser.
11-13 09:11:24.118  1433  1433 E Zygote  : java.lang.ExceptionInInitializerError
11-13 09:11:24.118  1433  1433 E Zygote  :      at android.content.pm.PackageParser.<clinit>(PackageParser.java:300)
11-13 09:11:24.118  1433  1433 E Zygote  :      at java.lang.Class.classForName(Native Method)
11-13 09:11:24.118  1433  1433 E Zygote  :      at java.lang.Class.forName(Class.java:454)
11-13 09:11:24.118  1433  1433 E Zygote  :      at com.android.internal.os.ZygoteInit.preloadClasses(ZygoteInit.java:302)
11-13 09:11:24.118  1433  1433 E Zygote  :      at com.android.internal.os.ZygoteInit.preload(ZygoteInit.java:134)
11-13 09:11:24.118  1433  1433 E Zygote  :      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:900)
11-13 09:11:24.118  1433  1433 E Zygote  : Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
11-13 09:11:24.118  1433  1433 E Zygote  :      at android.os.Build$VERSION.<clinit>(Build.java:367)
11-13 09:11:24.118  1433  1433 E Zygote  :      ... 6 more
11-13 09:11:24.182  1433  1433 E Zygote  : System zygote died with exception
11-13 09:11:24.182  1433  1433 E Zygote  : java.lang.ExceptionInInitializerError
11-13 09:11:24.182  1433  1433 E Zygote  :      at android.content.pm.PackageParser.<clinit>(PackageParser.java:300)
11-13 09:11:24.182  1433  1433 E Zygote  :      at java.lang.Class.classForName(Native Method)
11-13 09:11:24.182  1433  1433 E Zygote  :      at java.lang.Class.forName(Class.java:454)
11-13 09:11:24.182  1433  1433 E Zygote  :      at com.android.internal.os.ZygoteInit.preloadClasses(ZygoteInit.java:302)
11-13 09:11:24.182  1433  1433 E Zygote  :      at com.android.internal.os.ZygoteInit.preload(ZygoteInit.java:134)
11-13 09:11:24.182  1433  1433 E Zygote  :      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:900)
11-13 09:11:24.182  1433  1433 E Zygote  : Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
11-13 09:11:24.182  1433  1433 E Zygote  :      at android.os.Build$VERSION.<clinit>(Build.java:367)
11-13 09:11:24.182  1433  1433 E Zygote  :      ... 6 more
11-13 09:11:24.189  1437  1437 E Netd    : Error adding route 0.0.0.0/0 -> (null) dummy0 to table 1003: File exists
11-13 09:11:24.190  1437  1437 E Netd    : Unable to create netlink socket for family 5: Protocol not supported
 
Last edited:

siluok

Member
Dec 20, 2019
31
6
Upgraded to 18.1, But Deep Sleep isn't working
I have the same problem. I have been trying to fix this since migrating to 18.1 the moment it turned official. I was hopping this will be solved as the ROM gets updated. Unfortunately things didn’t change. Still 0 hours of deep sleep on AccuBattery.
 

shil40

Senior Member
Jun 15, 2011
72
14
Nexus 7
Sony Xperia Z Ultra
@DD3Boh

Some valued feedback upon nightly build I suppose:


(20220217 version just issued, I will test it later)

I came from stock ZUI 4.0, so it is a totally clean installation.

*Deep sleep ----> not an issue for my at all. More over, I suppose the power consuming is much better than stock ZUI version.

-Power charging & OTG issues (weird part mostly)

general usb 2 type-c cable with 5v/1a 5v/2a not functional any more (led lights up, but OTG & charging are not working)

Fast charge type c 2 type c cable worked , I used a Samsung S20 charger & type c 2 type 2 cable,
and OTG also works (must have a type-c port on your laptop or pc)

Power supply combination on the charger:

5V x 3A
9V x 2.77A
SKU# EP-TA800 (but trust me, it might be expensive than a 2nd handed ZUK Z2 in some markets, actually my other expensive chargers also woks..)

-for network issue

GSM/LTE/WCDMA works fine (2 local telecom SIMs tested)
CDMA/Edvo LTE sim card not work on my ZUK Z2 (100% worked on stock ZUI).
 
Last edited:

shil40

Senior Member
Jun 15, 2011
72
14
Nexus 7
Sony Xperia Z Ultra
@DD3Boh

Some valued feedback upon nightly build I suppose:


(20220217 version just issued, I will test it later)

I came from stock ZUI 4.0, so it is a totally clean installation.

*Deep sleep ----> not an issue for my at all. More over, I suppose the power consuming is much better than stock ZUI version.

-Power charging & OTG issues (weird part mostly)

general usb 2 type-c cable with 5v/1a 5v/2a not functional any more (led lights up, but OTG & charging are not working)

Fast charge type c 2 type c cable worked , I used a Samsung S20 charger & type c 2 type 2 cable,
and OTG also works (must have a type-c port on your laptop or pc)

Power supply combination on the charger:

5V x 3A
9V x 2.77A
SKU# EP-TA800 (but trust me, it might be expensive than a 2nd handed ZUK Z2 in some markets, actually my other expensive chargers also woks..)

-for network issue

GSM/LTE/WCDMA works fine (2 local telecom SIMs tested)
CDMA/Edvo LTE sim card not work on my ZUK Z2 (100% worked on stock ZUI).
Issue still existed on 0217 (dirty install based on previous nightly build + network profile rest)

but I glance 1 sec CDMA/EDVO LTE was recognized correctly, and then off line again.

One more surprise is that Z2 plus is able to connect with my latest wifi 6 AP with sounded linking speed, which I didn't remember it was functional on other LOS versions.
 

AkumDX

Senior Member
Aug 18, 2012
365
126
...
Can't seem to get GApps working but booting fine without gapps...

Which gapps is working with LOS 18.1?
 

siluok

Member
Dec 20, 2019
31
6
I have the same problem. I have been trying to fix this since migrating to 18.1 the moment it turned official. I was hopping this will be solved as the ROM gets updated. Unfortunately things didn’t change. Still 0 hours of deep sleep on AccuBattery.
After weeks of trying to find the cause of the drain might have found it. The App BetterBatteryStats shows permanent (100%) Kernel Wakelocks by "sensor_SMD 2000000000"!

This seems to be an Android 11 issue and has been discussed in the following thread:


and is also addressed i this thread:


I didn't find a proper solution! Hints and solutions appreciated...
 

P650SE

Senior Member
Aug 14, 2013
670
187
Is it possible anyone could help me find the latest Lineage 18.1 based on Android 11?

I am looking for this file:

lineage-18.1-20220811-nightly-z2_plus-signed.zip
SHA1: f1e082dc0f89c2d065e76b01611b8219bc93f870
SHA256: 5be1203cd876a6d7a39bcc722b53a8e2fcdd32577520e89a4124847fb4b60769
 

Top Liked Posts

  • There are no posts matching your filters.
  • 33
    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.