Database Develop

Is there a Lineage or custom 7.1 rom for the ZUK Z2 Pro?

Is there a Lineage or custom 7.1 rom for the ZUK Z2 Pro? I'm sorry but I really hate the factory Android 7.0 update rom

The Z2 Pro will be getting official Lineage support, probably first builds will be rolling out within this week. It will either be on the Lineage homepage (https://lineageos.org) or on the maintainer's build page (https://www.androidfilehost.com/?w=files&flid=144110&sort_by=date&sort_dir=DESC)

SenK9 said:
The Z2 Pro will be getting official Lineage support, probably first builds will be rolling out within this week. It will either be on the Lineage homepage (https://lineageos.org) or on the maintainer's build page (https://www.androidfilehost.com/?w=files&flid=144110&sort_by=date&sort_dir=DESC)
Click to expand...
Click to collapse
where is the source for this information that the zuk z2 pro will get OFFICAL lineage support?
actually i dont believe it.

m45k said:
where is the source for this information that the zuk z2 pro will get OFFICAL lineage support?
actually i dont believe it.
Click to expand...
Click to collapse
Link broken

jpfp90 said:
Link broken
Click to expand...
Click to collapse
Actually the rom was there and I tried to install it and it wouldn't work so Edgar pulled it off the download site

SenK9 said:
The Z2 Pro will be getting official Lineage support, probably first builds will be rolling out within this week. It will either be on the Lineage homepage (https://lineageos.org) or on the maintainer's build page (https://www.androidfilehost.com/?w=files&flid=144110&sort_by=date&sort_dir=DESC)
Click to expand...
Click to collapse
When and where did i ever say that?
robert3892 said:
Actually the rom was there and I tried to install it and it wouldn't work so Edgar pulled it off the download site
Click to expand...
Click to collapse
Your getting an error 7 right? that means you have the wrong trwp version. Here's the right twrp version if you want to install custom roms: twrp-3.0.2
we had a working build a few weeks ago, but it had a major camera issue, it would physically damage your camera and flashing back to stock roms wouldn't fix it. I have fixed the camera issue and updated my sources since then but i can't get a boot now.
The biggest thing that changed is that I reverted my phone back to official stock ZUI 2.3 in order to get the latest ZUI 2.5 OTA. So i'm trying to figure out what changed and what needs to be fixed.
It would be nice if I could get some help, it seems like i'm the only one working on this now.
https://github.com/edTheGuy00?tab=repositories

Sorry I got mixed up between the Z2 Pro and Vibe Z2 Pro while skimming the official device lists. There is only unofficial atm.

Edgrr000 said:
It would be nice if I could get some help, it seems like i'm the only one working on this now.
https://github.com/edTheGuy00?tab=repositories
Click to expand...
Click to collapse
@Edgrr000
Hi, are you still working on this device? I don't see activities on your github since months. I'm trying to understand if there are working nougat device trees for this device.
Edit: nevermind, found another source

There is official AEX now

Troubleshooting, touch screen not working in TWRP

Hi everyone, so some mistakes have been made today. While playing around with substratum theme engine on my mix running lineage-os 14.1, i had uninstalled one of the themes and then decided to uninstall the app entirely, however after uninstall it didnt reset the theme, so i rebooted. While attempting to reboot it got stuck in a boot loop. At this point I plugged my phone into my pc and booted into twrp so i could access my files and get them off, however when attempting to boot into twrp i could not use the touch screen which is preventing me from re-flashing my rom. and so after troubleshooting for an hour or soi had all my files off of my device, so i decided to format the system partition. so now i have no rom flashed and a twrp that i cannot use due to lack of touchscreen, its temporarily bricked i guess. So my questions are; A. can i use an otg cable and a mouse to control twrp? B. Is there some way to directly flash a rom from adb or from the connected pc. Then I should also state that I have tried older/newer versions of twrp to try to get the touchscreen working, to no avail (currently running 3.1.1-0 lithium). Ive read that it may be touchscreen drivers or something that are mis-matched from the rom. the onlyt issue is that there is no rom, also ive heard that the touchscreen is at a kernel level so i may need to flash a new kernel to get it working. TBH im not going to do anything else so that i dont completely brick my phone. Thank you all in advance for helping out!

Please try this (older) TWRP by MrRaines: https://www.androidfilehost.com/?fid=673368273298927160
It's TWRP 3.0.2-0 based but has different kernel/driver that is more compatible with a varous bunch of ROMs.

You're a god, this is exactly what I needed, thanks!!!

raupe said:
Please try this (older) TWRP by MrRaines: https://www.androidfilehost.com/?fid=673368273298927160
It's TWRP 3.0.2-0 based but has different kernel/driver that is more compatible with a varous bunch of ROMs.
Click to expand...
Click to collapse
I LOVE you, spent hours trying to get recovery working. This was the only fix!
Thank you so much brother.

kanej2006 said:
I LOVE you, spent hours trying to get recovery working. This was the only fix!
Thank you so much brother.
Click to expand...
Click to collapse
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono

raupe said:
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono
Click to expand...
Click to collapse
Just see the kernel img, ramdisk and boot files/blobs

raupe said:
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono
Click to expand...
Click to collapse
Hmmm. I did try two or even three other versions of TWRP. The first two would not even flash giving me an error. The third worked but touch screen would not work. Final attempt was the one from MrRaines which worked perfect!

Android One Or Costom Rom?

hey guys at present I'm using my a2 On Official Android One Rom With Bootloader unlock (camera2api) Enabled. Some Users Say that Android one rom is laggy And lot's of bugs. So I want You To suggest Me What Should I Do? Install A Costom rom On my device like (Pe or something else) Or Stay With Android One?

I recommend Pixel Experience CAF version. I'm currently using that since I got fed up with Android One updates. I have been on custom ROMs for quite some time actually. CAF version supports OTA so you don't have to flash it again with every update, camera2api is already enabled and there is a MIUI camera included, but you'll have to find a working GCam yourself though. I haven't actually experienced any bugs for now but people say there are few and those will be fixed in the next update.
Edit: Just to add a few reasons why I am against Android One since you wrote that some users reported issues with stock but not you yourself.
It all started with the September update(if I recall correctly, or maybe even earlier). The bug present in that update made the faster CPU cores lock up at maximum frequency if the fingerprint sensor is used which drained battery really quickly. It took them like 1-2 months to fix that one. Then came Pie update, a lot of stuff stopped working. The storage for some reason got really slow and clearing large app cache(especially Chrome cache) would freeze the device or even make it reboot. This is the issue they STILL haven't fixed.
With January 2019 update a lot of devices went into bootlops and got bricked. February update changed contrast of the display and made everything really bright, definitely brighter than it should have been. Now they fixed that issue in March update BUT the update bootloped/bricked some more devices again so they pulled it. Their updates have really become a joke, which is why I'm all for custom ROMs. Definitely more stable than stock.

Brothr can u share the link to the post or step by step process for installing custom pe rom ?

Sid.Boi said:
Brothr can u share the link to the post or step by step process for installing custom pe rom
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
If you are flashing Pixel Experience you don't need to flash GApps, the rest is the same from the guide.

Thnq brthr :good:

I thinking same idea for months, but i have problem that i follow countless guides from forum here but i fail every to get PE CAF or Havoc rom to mine A2. I have every time black screen problem on instaling TWRP i couple times flash 10.0.2 version via mi flash tool, lock and unlock bootloader etc.. currenty i am on stock 10.0.7 with open bootloader because of camera2api, but i wanna clear phone from all the mess wanna clear both slots and finally instal succesfuly PE CAF version. Can someone provide some guide how to do it?

LineagesOS microG failed update

Hello all,
I was searching trough the internet and the forum without luck on this issues.
Is there any explanation, what happened between 31.07 and 02.08? The dipper (Xiaomi Mi 8) release got ~ 300MB bigger.
Also I can't find a statement from the microG project, why they have removed the 20190805 release. I installed the latest firmware (9.6.27) and before the microG build was removed from their sources, I installed it. Since then my phone is only looping in the "MI" logo.
TWRP is working and I managed to install the regular LOS with GApps, until the microG team fixed the issue. Still would be interesting to know, if anyone would share the information.
Thanks,
Sputnik

Is there no Android 10-based ROM for beckham? Not even treble?

I see a lot of gadgets (like the G7 plus bike that has the same hardware) with several Android 10-based Roms and it looks like our device has been forgotten. There is not even one in beta to installation?

There are no 10 ROMs (non GSI) available. In the telegram group there's work being done, but nothing has released. Be patient. Beckham doesn't have much support.

I came across a patched version of 3.3.1 twrp by "Jleeblanch" (and installed successfully) and also noticed an unofficial lineageOS 17 rom on the Android file host page for the z3 play. I have yet to try it though. Here is an install guide from cyanogenmods for it. https://www.cyanogenmods.org/moto-z3-play-lineageos-17/

so far?
gardensofgrief said:
I came across a patched version of 3.3.1 twrp by "Jleeblanch" (and installed successfully) and also noticed an unofficial lineageOS 17 rom on the Android file host page for the z3 play. I have yet to try it though. Here is an install guide from cyanogenmods for it.
Click to expand...
Click to collapse
So how is it working so far. I want to give it a shot, I am sad and tired of waiting for it officially.

Redman3000 said:
So how is it working so far. I want to give it a shot, I am sad and tired of waiting for it officially.
Click to expand...
Click to collapse
I found bugs in motomods and LiveDisplay.
Crashes on screen, it turning off but device is on.

Xavier2Bv said:
I found bugs in motomods and LiveDisplay.
Crashes on screen, it turning off but device is on.
Click to expand...
Click to collapse
Did you try the newest Lineage 17.1 that jleeblanch posted a few months ago? It works better than the one posted above. https://forum.xda-developers.com/showpost.php?p=83119095&postcount=54

NoMoreBackdoors said:
Did you try the newest Lineage 17.1 that jleeblanch posted a few months ago? It works better than the one posted above. https://forum.xda-developers.com/showpost.php?p=83119095&postcount=54
Click to expand...
Click to collapse
Thanks!
This ROM works better than Lineage 17.
I haven't have bugs, I installed it since yesterday and everything works well.