[OFFICIAL][ZS620KL] LineageOS 20 (Android 13) for the Asus Zenfone 5z - Asus Zenfone 5Z ROMs, Kernels, Recoveries, & Othe

[OFFICIAL][ZS620KL] LineageOS 20 (Android 13) for the Asus Zenfone 5z - Asus Zenfone 5Z ROMs, Kernels, Recoveries, & Othe

Features over Stock
FM Radio, File-Based Encryption (which allows power-off Alarm to actually work and no annoying PIN prompt half-ways through boot), QTI Bluetooth stack
KNOWN BUGS
ViLTE does not work
Touch sometimes doesn't work in Lineage Recovery. The workaround is to use the volume buttons to move around the menu and power to select or to reboot to recovery.
SafetyNet does not pass (Unfortunately, this is not possible as our SoC has hardware attestation... the workaround is to use unsupported mods like Magisk which tbh I haven't tried myself as I don't root my devices, but other users said that plus the SafetyNet Magisk mod works)
No Widevine L1 after bootloader unlock. Unfortunately Asus wipes DRM keys when bootloader unlock is performed. This happens on both official and unofficial bootloader unlock...
Frequently Asked Questions
Is there a different way to unlock the bootloader than the Asus official method? You can try the unofficial bootloader unlock here

will try later

Screenshots here
seems working fine
Thanks for the new build

Heyyo, LineageOS 20 official for Z01R is up!

Is this ROM stable enough for daily driving or are there any notable issues? (I would be using TWRP, no root and don't need VoLTE)

@DarkAlpha.Sete I wouldn't be official if it wasn't stable
Known bugs are in the second post

MindTheGapps-13.0.0-arm64 is no function now . wait for the fix

zenfone 5z adb driver for windows 11 . link = https://adb.clockworkmod.com/

Heyyo @loopstudio007 , the current version is MindTheGapps-13.0.0-arm64-20221025_100653 and it does work. Please make sure you follow the installation instructions and you can also try to redownload it just incase your download is corrupt.
That clockworkmod ADB driver is ancient. I'd recommend downloading the Google driver from here https://developer.android.com/studio/run/win-usb

ok. thank you.i'll try later

I have installed the rom and it worked so far perfect, also mobile data in my country. Now I am in a foreign country in EU and mobile data roaming is not working. I have tried different apn settings but no success.
Can somebody help?

Appreciate all your hard work @ThE_MarD , it seems I'm having some difficulty installing.
Bootloader unlocked, I've had issues with fastboot, so I used EDL to replace the boot.img with TWRP from the link you've provided. Now I can get into TWRP and flash the rom. I just wind up in a boot loop.
- Unlock the bootloader and install TWRP. [Done via EDL]
- Download LineageOS [Got your latest unofficial, rather than the nightlies]
- Boot into TWRP [done]
- Copy the downloaded zip files to the internal SD card. [Done, incl MindTheGApps, TWRP Zip and of course your rom.]
- Perform a backup of your current ROM. (Optional) [Ignored]
- NOTE! If you're coming from stock ROM? You MUST format data. Wipe > "Format Data" button > type "yes" > keyboard checkbox [I have done this each time as coming from stock rom WW_ZS620KL_100.10.107.123]
- RECOMMENDED: Do a factory reset (clean wipe)! No support if you didn't! (Wipe System, Cache and Data) [Done]
- Flash LineageOS zip. [Done, current slot A, flashed slot B]
- Flash TWRP installer zip. [Done via the "add more Zips" feature]
- Reboot to TWRP. [Rebooting, changes to current slot B]
- Optional: Install the Google Apps add-on package. [Installed MindTheGApps]
- Reboot to system. [I hit reboot button, and then tap system at the top, it says current slot B]
Boot loop... Comes up with integrity warning, "Powered by Android", loop.
Any advice? I've not done an A/B phone before, and previously I'd been having issues where fastboot wouldn't detect on my PC (hence the EDL route). Worst case, I can take it back to stock-stock via EDL, but I've come this far, I'd really really really really like to get the upgrade to LineageOS if I could.

Heyyo @Sometimes.I.Brick.Phones , hmm, well just in case the issue is TWRP please try with Lineage Recovery
I would recommend using the latest official nightly as my last test build is a bit old.
That's quite odd though that you need to use EDL to flash recovery, did something happen to your device?
You can try QPST and then flash updated ZenUI stock ROM and then switch to Lineage Recovery and flash?
A/B devices are a bit of a pain, but I did make things easier by including the correct device firmware which is why we don't need the copy-partitions step like some other A/B devices need

ThE_MarD said:
Heyyo @Sometimes.I.Brick.Phones , hmm, well just in case the issue is TWRP please try with Lineage Recovery
I would recommend using the latest official nightly as my last test build is a bit old.
That's quite odd though that you need to use EDL to flash recovery, did something happen to your device?
You can try QPST and then flash updated ZenUI stock ROM and then switch to Lineage Recovery and flash?
A/B devices are a bit of a pain, but I did make things easier by including the correct device firmware which is why we don't need the copy-partitions step like some other A/B devices need
Click to expand...
Click to collapse
Thanks for the quick response!
I'm grabbing the latest nightly, AND IT WORKED! As for steps, went TWRP, flash LineageOS Nightly, flash TWRP, rebooted to system. Checked it's all working, managed to get GApps on, next step is working out Magisk!
RE: Fastboot, I'm largely using QMSCT (link to thread) to replace to stock rom with modified TWRP boot.img. When I run fastboot mode I get a "device descriptor request failed" across multiple PCs (yet MTP and ADB detect fine, thread). It's been a bit of a nightmare for me I'm afraid, but thankful for the community for getting me unbricked.
I do very much appreciate how you've built it out, just thought I'd be verbose in calling out slots!

@Sometimes.I.Brick.Phones glad it all worked out! Enjoy!

Related

[ROM][testing] AICP 15.0 - q10.0 - apollo (Sony XZ2 Compact)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q with a base of AOSP repositories and some additions from LineageOS for device specific repositories.
If there are any bugs, either we will sort them out, if it concerns our code base. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
AOSiP team
Community
...
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 15.0
Download link: https://dwnld.aicp-rom.com/
Note: No official builds for now.
Test builds: https://androidfilehost.com/?w=files&flid=309318
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
- You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
No.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behaviour on flashing a new official build by (or using) the build-in updater service. However, please make sure to backup your device regularly in case something goes wrong.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Q. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
0. Install the latest stock ROM, ideally to both slots or use the LineageOS copy-partitions.zip
1. Boot a current TWRP
2. Factory reset
3. Flash the ROM zip
4. Optional: Reboot to recovery, then flash add-ons like GApps, Magisk etc.
How to upgrade from an older AICP build to a newer test build:
1. Make sure you have advanced reboot enabled: Settings/AICP Extras/Auxiliary buttons/Power menu/Advanced Reboot
2. Press the power button, select "Advanced" and "Recovery" to enter the inbuilt TWRP recovery
3. Flash the ROM zip
4. Optional: Reboot to recovery, then flash add-ons like GApps, Magisk etc.
Old instructions:
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot and set up your device, enable developer settings and in them OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
1. Flash latest stock ROM (52.1.A.0.672)
-> either with sony flashtool ("emma") or xperifirm + newflasher
2. Unpack the ROM tar
Code:
> tar -xzvf the_file_you_downloaded.tar.gz
2. Flash the ROM
Code:
> fastboot flash boot boot.img
> fastboot flash dtbo dtbo.img
> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
> fastboot flash system system.img
> fastboot flash vendor vendor.img
> fastboot flash userdata userdata.img
Skip flashing userdata if you are comming from an older AICP 15.0 build and want to upgrade without losing your data!
3. Reboot to the ROM
Code:
> fastboot reboot
First boot might take a few minutes.
4. Optional: flash GApps and/or Magisk
- Enable Advanced Reboot in Settings / AICP Extras / Hardware buttons / Power menu
- Press power button, select Advanced > Recovery
- Use the inbuilt TWRP recovery to flash zips
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.3 don't usually need to be flashed on every dirty flash.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices you will have to enter your PIN/password in TWRP before the process starts.
Note: no official builds for now.
If you want to contribute to AICP, or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/AICP/kernel_sony_sdm845/tree/q10.0
Device tree source:
https://github.com/AICP/device_sony_apollo/tree/q10.0
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
- Olivier
- Sjll
- MartinX3 - thanks to him for allowing me to include his TWRP
- The sony open devices team and contributors
- LineageOS team
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
Android Ice Cold Project (AICP) 15.0 (q10.0) apollo (Sony XZ2 Compact), ROM for the Sony Xperia XZ2 Compact
Contributors
SpiritCroc
Source Code: https://github.com/AICP
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Version Information
Status: Testing
Created 2020-04-26
Last Updated 2020-10-18

Nice job!
SpiritCroc said:
Offline charging is broken, your device will boot when you connect a charger to a switched off
Click to expand...
Click to collapse
You may want to cherry-pick this kernel patch - it will fix offmode charging.

Olivier said:
Nice job!
You may want to cherry-pick this kernel patch - it will fix offmode charging.
Click to expand...
Click to collapse
Great, thank you!

Nice work!
(Damn! Not the first who comment!)
[emoji2957][emoji12]

don't need to flash sony oem? ( https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-tama/ )

nikkdib said:
don't need to flash sony oem? ( https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-tama/ )
Click to expand...
Click to collapse
No
It's a stock based ROM

MartinX3 said:
No
It's a stock based ROM
Click to expand...
Click to collapse
so in this rom will never be a gcam?

nikkdib said:
so in this rom will never be a gcam?
Click to expand...
Click to collapse
Yes, on the other side SODP and stock doesn't share the same bugs

nikkdib said:
so in this rom will never be a gcam?
Click to expand...
Click to collapse
In case the sony open devices program at any point in the future catches up with stock-based solutions concerning performance and functionality, I might switch to it as well.
For now, I experience the best results with a stock-based approach.

Would flashing this ROM fix the quiet microphone issue?

pakman5391 said:
Would flashing this ROM fix the quiet microphone issue?
Click to expand...
Click to collapse
The microphone is loud enough for me, but I don't know your issue personally, so your best bet is to try it out I guess

I uploaded a new build.
I have not tested a dirty flash this time, so I recommend to do a full backup to external storage in case something goes wrong if you try to upgrade from the previous AICP build (otherwise, you need a clean flash either way).
This time, it's a flashable zip (instead of images for fastboot), I have updated the install instructions accordingly.
This update features enforcing sepolicy (thanks to @Olivier and @Sjll for their work on the offcial lineage trees).
It might be ready for official AICP builds, but I don't know if it's worth it since I have not received any user feedback yet and don't know if there is actually demand... so if you use AICP, would be great if you could provide some feedback

I will definitely flash this when i'm in vacation. Needed a working phone to manage things because of a car accident.
Things are done now and it's time to say goodbye to pie.

Bug report: Proximity sensor not working
Edit: it seems that are other sensors too...

shamllakh said:
Bug report: Proximity sensor not working
Edit: it seems that are other sensors too...
Click to expand...
Click to collapse
These are working for me. Have you flashed the latest stock ROM (52.1.A.3.49) to both slots before flashing latest AICP?

SpiritCroc said:
These are working for me. Have you flashed the latest stock ROM (52.1.A.3.49) to both slots before flashing latest AICP?
Click to expand...
Click to collapse
I flashed the 52.1.A.3.49 using xperiafirmware flasher.
Then, i used the old method (fastboot method) to flash the AICP rom...
Did i miss anything?

shamllakh said:
I flashed the 52.1.A.3.49 using xperiafirmware flasher.
Then, i used the old method (fastboot method) to flash the AICP rom...
Did i miss anything?
Click to expand...
Click to collapse
So you flashed the old build (20200425_1435)? That one might need older firmware (around 52.1.A.0.672).
For the newest AICP build (20200731_1348), you need the new firmware (52.1.A.3.49) and the new instructions.

SpiritCroc said:
So you flashed the old build (20200425_1435)? That one might need older firmware (around 52.1.A.0.672).
For the newest AICP build (20200731_1348), you need the new firmware (52.1.A.3.49) and the new instructions.
Click to expand...
Click to collapse
Thanks a lot for the hint
I re-flashed the 25.1.A.3.49 via newflasher33, then flashed the AICP ROM via fastboot.
Now it works fine.
:fingers-crossed:

I finally found the time to flash my xz2c with this great rom and first i want to thank @Olivier for the official LOS base and second @SpiritCroc making this possible on this device!
As i use Aicp since years as my main Rom on my HTC One M8 i know what i'm getting with this.
However i had problems with installation: no matter what i did, i could not get the "zip" flashing to boot.
I first used Newflasher to update to the latest stock Rom, then i booted it twice to finish the carrier installation.
then i booted up twrp and flashed the zip file. Once, for the unused slot, then on the other slot. Spent a whole evening without succes...don't know what was wrong. Unfortunately i'm not used to this A/B flashing.
I then used this guide/files to extract the img files and flashed them with fastboot. That worked like a charm!
All in all this Rom has almost no problems and is faster than stock to me. Some things i noticed so far:
- biggest (and only real) problem (and as far as i heard it is the same on the LOS base) the ringtone/notification sound is is quieter than stock. I hope this can be solved, because stock was not really loud already
- flashlight brightness is not really bright, same like stock rom i think. I used some modded lib files from an Android 9 mod to make it brighter.
- i miss the option to change the visual appearance of the navbar button which was available until Android 9 in Aicp
- screen colors seems to be much more brighter, it looks much more better than stock to me
I will continue testing and see what i'll find.
All in all this Rom with it's many features is definitely worth flashing it!!!

!!! KUDOS !!!
AICP-q10.0_apollo_20200731_1348 is the first the most customizable and fully working ROM for Xperia XZ2C, if not the only one at all. I have not tested all the goods yet, but the most important features are here:
* fully working TWRP v3.4.0.0 - no issues with touch every time! until now the only TWRP working for me was the one booted with fastboot, all the flashed TWRPs had either touch issues or SD card issues
* SafetyNet basicIntegrity passed! - ctsProfile can be easily fixed with MagiskHide Props Config and therefor we have a full SafetyNet passed along with Magisk, allowing the banking and all the other sensitive apps to work
* WIFI
* Bluetooth (audio and calling)
* GPS
* fingerprint
* camera (but not the Sony one )
* encryption with TWRP decryption working
* SD card with exFAT
* notification LED
A few installations points from me
The ROM Installation was very easy and quick, but I was doing a total clean install. Here is what I did
1. Install Sony's stock ROM 52.1.A.3.49 with newflasher
2. Boot TWRP v3.4.0.0 stock version with fastboot
3. Flash AICP-q10.0_apollo_20200731_1348.zip (please note the messages, it should flash to "inactive slot B")
4. In TWRP select Reboot => Slot B => Recovery... to reboot the phone into recovery in Slot B
5. Flash Gapps
6. Format data (just in case, many times without format with other ROMs I got bootloop)
If you need fully working Magisk with full SafetyNet pass (steps are not logical and obvious but it works, tried it w few times):
1. Flash Magisk v20.1 or v20.3.... later versions breaks the basicIntegrity! If you have flashed later Magisk version simply use Magisk Unistaller zip in TWRP and flash v20.1 or v20.3
2. Boot the phone and update Magisk Manager to the latest version 8.0.2 (307) with an option inside the Magisk Manager
3. Go back to the TWRP and now you can flash Magisk v20.4 or v21.0 - this time flashing does not break the basicIntegrity and those versions are required to fix the ctsProfile
4. Install MagiskHide Props Config module in Magisk Manager
5. Install Terminal Emulator
6. Run terminal and enter the commands su followed by props
7. Change fingerprint to XZ2C with the following options: 1 => f => 27 => 20 => reboot
Ok, so what are the drawbacks? Well not much and more personal preferences I think:
1. Missing Sony's stock camera app. I tried to flash those zips below but I get "unknown error" when I try to launch the app. Do you think it would be possible to make the Sony camera work with your ROM?
https://androidfilehost.com/?w=search&s=semccamera
2. Missing custom navigation bar buttons. On the RR ROMs I used to work the most it was possible to add extra navigation buttons and assign customized actions for tap, long press, etc.
3. Slow auto brightness reaction (I can live with that)
4. Veeery low flashlight level (there was a solution for XZ1C to fix that, I have to dig a little bit to see if it can be done here as well)
5. Ambient Display - to show notifications on blocked screen
Please don't give up the project. There is not much going with the XZ2C custom development, the last and only "normal size" Android phone.
Do you think you can take a look at some of my "drawbacks" and try to fix them?
Do you think you will make some other ROMs for XZ2C in the future, like ResurrectionRemix, EvolutionX, HavocOS?

[OFFICIAL][ZS620KL] LineageOS 17.1 (Android 10) for the Asus Zenfone 5z

Features over Stock
FM Radio, File-Based Encryption (which allows power-off Alarm to actually work and no annoying PIN prompt half-ways through boot)
Known Bugs
4K UHD Video recording does not work in LineageOS Snap Camera app. (A workaround is to use other camera apps like OpenCamera or Gcam Mods)
Touch sometimes doesn't work in Lineage Recovery. The workaround is to use the volume buttons to move around the menu and power to select or to reboot to recovery.
Bluetooth A2DP can cause crashes during voice calls with certain Bluetooth devices (a workaround is to disable Bluetooth A2DP offload via developer options)
The current official build of TWRP doesn't support File-Based Encryption. The workaround is to use my modified build of TWRP found here

Just a heads up, I'm unsure when official builds will be starting, so please be patient. I'm guessing between Monday to Friday of this coming week
w00t! We got mentioned in an XDA article!
LineageOS 17.1 adds support for the OnePlus Nord, ASUS ZenFone 5Z, and more
Official LineageOS 17.1 builds are now available for the OnePlus Nord, the ASUS ZenFone 5Z, the Fairphone 3, and the Samsung Galaxy SIII Neo.
www.xda-developers.com

can't waiiit, thank you

Awesome work!

can someone help me, i tried the noob-friendly guide to install the recovery and ROM but whenever I install the recovery and try to install the recovery permanently, it gives me errors and phone sort of bricks. I really want to install an android 11 ROM please help.

amitrahi04 said:
can someone help me, i tried the noob-friendly guide to install the recovery and ROM but whenever I install the recovery and try to install the recovery permanently, it gives me errors and phone sort of bricks. I really want to install an android 11 ROM please help.
Click to expand...
Click to collapse
what steps you following?

Heyyo @amitrahi04 , sorry I accidentally had Android 11 in the thread title when LineageOS 17.1 is Android 10.
In order to use Android 11 ROMs please check their threads and their instructions.
I do plan to work on LineageOS 18.1 for Z01R later, but first I want to work on my Zippo (Lenovo Z6 Pro) and Payton (Motorola X4) and my x2 (LeEco Le Max 2) as they're already in progress for 18.1 and tbh I didn't expect 17.1 for Z01R to take this long, but OSS Vendor took a lot of time and effort

decentguy49 said:
what steps you following?
Click to expand...
Click to collapse
I'm following this guide: https://forum.xda-developers.com/t/guide-noob-friendly-custom-rom-flashing-guide.3944849/
I want to try this ROM: https://forum.xda-developers.com/t/rom-11-r-official-evolution-x-z01r-19-12.3981601/

amitrahi04 said:
I'm following this guide: https://forum.xda-developers.com/t/guide-noob-friendly-custom-rom-flashing-guide.3944849/
I want to try this ROM: https://forum.xda-developers.com/t/rom-11-r-official-evolution-x-z01r-19-12.3981601/
Click to expand...
Click to collapse
If you have anything important on your device then back it up
Download the LOS ROM, LOS recovery and GAPPS if you want to flash
Use official tool to unlock bootloader
Once bootloader is unlocked, reboot to bootloader
adb reboot bootloader
Click to expand...
Click to collapse
Flash LOS recovery
fastboot flash boot RecoveryName.img
Click to expand...
Click to collapse
Now reboot to recovery
Select Factory Reset.
Flash the LOS ROM
if you want to use GAPPS, then reboot to recovery and flash Open GApps
Reboot to system

@amitrahi04 , if you want help for that ROM I'd recommend posting in the thread for that ROM as this thread is for LineageOS 17.1 for Z01R, so please keep posts in this thread for this ROM

Heyyo! It is time! Official LineageOS 17.1 for Z01R is released!!!

I tried to install GAPPS nano for it, but when it starts, G Apps as (Play Store) does not appear on the system. First time I had this error. I ended up going back to Stock, i tried 5x...

ThE_MarD said:
Heyyo! It is time! Official LineageOS 17.1 for Z01R is released!!!
Click to expand...
Click to collapse
I installed it right away when it is available. Everything's working fine. Using it as my daily driver.

iShaKinGameR said:
I tried to install GAPPS nano for it, but when it starts, G Apps as (Play Store) does not appear on the system. First time I had this error. I ended up going back to Stock, i tried 5x...
Click to expand...
Click to collapse
Assuming that you used the Lineage Recovery, the same thing happened to me on my first attempt. Right after flashing the ROM, i continued to flash GAPPS and reboot. Like your problem, Google apps did not show up when i boot the system.
However, i missed one step as stated in the installation process. As per the instruction, right after flashing the ROM itself, you have to click Advanced, then Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB, then adb sideload <filename>.zip, which in this case is the gapps.zip. Then, reboot to system. The google apps will now appear in the system. Hope it works for you also

HtMawia said:
Assuming that you used the Lineage Recovery, the same thing happened to me on my first attempt. Right after flashing the ROM, i continued to flash GAPPS and reboot. Like your problem, Google apps did not show up when i boot the system.
However, i missed one step as stated in the installation process. As per the instruction, right after flashing the ROM itself, you have to click Advanced, then Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB, then adb sideload <filename>.zip, which in this case is the gapps.zip. Then, reboot to system. The google apps will now appear in the system. Hope it works for you also
Click to expand...
Click to collapse
Thank you very much! I took advantage of this function and put the Magisk, so I can use the rom to test.

Heyyo @iShaKinGameR and @HtMawia , the step after ROM flash and reboot to recovery is very important for us as Z01R is an A/B partitioned device. The ROM always flashes to the inactive slot and then it tells the bootloader to switch slots which requires a reboot. So the reboot to recovery is to get recovery to reload onto the slot that the ROM was flashed so that you can then install gapps and such.
Devices that are A-Only, such as the Lenovo Z6 Pro (Zippo) do not need this step as there is only one slot it can flash to. I think the Asus Zenfone Max Pro M1 (X00TD) Is only A-Only as well.

So far everything is OK and more fluid than ZenUI. I just realized that the ROM doesn't seem to have a Camera Wide-Angle, I tried to activate it through build.prop and went into bootloop. I am trying to use it daily.
Edit: The HDR DCI mode does not activate on YouTube.

Hi, the rom is great, but I have no mobile network. It should just reigster on the network automatically... Any ideas? I think maybe it has something to do with the vendor file. How do I update this? Which file is correct, and at what point do I flash it? Thanks!

@iShaKinGameR , the LOS snap camera app only supports the main rear camera. For the aux rear camera I recommend switching to a different camera app like OpenCamera or better yet, the Wichaya GCam mods which I link to in my first post.
There's no need for that aux camera app prop as I used the newer prop that just exposes the aux camera to all camera apps
Z01R: Expose aux camera globally · LineageOS/[email protected]
Switch out vendor.camera.aux.packagelist for persist.vendor.camera.expose.aux Change-Id: I7295184a001d4c851b2d147bd35399b06a185bc4
github.com
Tbh I'm unsure of any HDR DCI videos on YouTube, but I do know that HDR itself does work for me on the LOS official build...
If it doesn't work for you, can you please provide logcat?
@greves1 , can you please provide logcat? There is no need to modify anything in the vendor partition as we use a source-built vendor partition which includes everything needed to make our device work on LineageOS 17.1.

[DISCONTINUED][ZS620KL] LineageOS 18.1 (Android 11) for the Asus Zenfone 5z

Features over Stock
FM Radio, File-Based Encryption (which allows power-off Alarm to actually work and no annoying PIN prompt half-ways through boot), QTI Bluetooth stack
KNOWN BUGS
ViLTE does not work
4K UHD Video recording does not work in LineageOS Snap Camera app. (A workaround is to use other camera apps like OpenCamera or Gcam Mods)
Touch sometimes doesn't work in Lineage Recovery. The workaround is to use the volume buttons to move around the menu and power to select or to reboot to recovery.
SafetyNet does not pass (Unfortunately, this is not possible as your SoC has hardware attestation... the workaround is to use unsupported mods like Magisk which tbh I haven't tried myself as I don't root my devices, but other users said that plus the SafetyNet Magisk mod works)
Frequently Asked Questions
Is there a different way to unlock the bootloader than the Asus official method? You can try the unofficial bootloader unlock here

Heyyo, LineageOS 18.1 for Z01R public beta test build is up! lineage-18.1-20210411-UNOFFICIAL-Z01R has QTI Bluetooth! NFC! WiFi Display! WiFi Hostspot! Source-built Vendor! Selinux Enforcing! File-Based Encryption! It's all working good.

Hi There,
nice to read we'll get 18.1 on our device !
Is this beta okay to use on my only daily driver phone ? or should i better wait ?
& Which vendor-patch-level is it ?

Heyyo @Spassbremse from my tests so far she's very stable and I plan to daily drive it for a few days just to be safe. I went through the logcat and already fixed a lot of things just to ensure she's stable. There are a few more minor upgrades I'd want to do later on, but I'm super happy with the result that we currently have.
Tbh vendor patch level is just a suggestion lol... there's no way to check if someone lied or not about it. Technically the vendor security patch level should be based on the device's firmware and the vendor blobs. Ours is based upon stock ROM UL-Z01R-WW-100.10.107.123-user so I set our vendor security patch level to 2021-01-05.
I've seen other people set theirs to whatever date is on for just a few blobs kanged from a different device, but that's technically lying as the device firmware and other parts of the blobs would still be an earlier date... so what I'm saying is? Don't trust vendor security patch level. The most important part anyways is the system security patch level and selinux enforcing and avoid keeping root (like Magisk) on your device as root is a security bypass. I've seen vulnerabilities in the past to gatekeeper and keymaster that could allow an attacker to bypass lockscreen security that could only be achieved if the attacker had access to root... so yeah, I never install Magisk on my Z01R.

Heyyo, another new test build is going up! lineage-18.1-20210412-UNOFFICIAL-Z01R contains updates from Nokia 8.1 Android 11 release for GPS, IMS, QMI and RIL. Maybe it's just me, but LTE+ seems to be working better.
I haven't had time yet to check into if it's possible to force ViLTE support though

Well I haven't heard any serious bugs from LOS 18.1 so I'm going to be requesting official builds for Z01R and hopefully it doesn't take too long

Excuse me, is call recording enabled on LineageOS 18.1 now? It's one of the attractive but rare function from the stock firmware.

Heyyo @Dragonkind , yes call recording was enabled on Z01R for LineageOS since the prebuilt vendor 17.1 days and is still enabled

Well done, the phone deserves this. Asus is still insisting on 2 versions android support policy, but thanks to you, hope find more contribution for the project for the bugs.

Heyyo @aLLyC , thank you for the kind words! I definitely love my Asus Zenfone 5z and our LineageOS 18.1 builds for her are already in better shape than 17.1! Only a matter of time before those official builds will be a thing
One the Hudson promote Z01R to 18.1 gets merged? Our next build will be 18.1 w00t!
https://review.lineageos.org/c/LineageOS/hudson/+/308513

Do you think that this version supports ethernet tethering ? I am using USB-C Ethernet Adapter, however Zen failed to work with directly routers wan port while sammy gets it is done with Android11.

Heyyo, w00t! We were approved! Our next official build for LineageOS will be for 18.1! Meow I only have my Lenovo Z6 Pro left to get official builds hehe
@aLLyC , I'll ask Kailash as he's the Z01R kernel guy as tbh I'm unsure what changes we would need in the kernel to support USB devices (afaik it's the kernel only that needs the adjustments???)

Great!! normally it supports ethernet connects an node but not tethering... thanks!
Sammy UI has a seperate option for the feature under tethering menu in note series in Android 11

Details below;

So I forgot to post an update lol oops, but LineageOS 18.1 for Z01R build from 04/20 is posted and contains stuff like the LiveDisplay color profiles for those who want to try it before the official build goes up in two days https://osdn.net/projects/lineageos-for-z01r/releases/75006

Thank you for your development effort towards Zenfone 5Z. I'm interested in installing your ROM as it has encryption enabled.
Does this support copying text from recents(Pixel feature drop)?
Also does it support VoWiFi on Jio(Indian carrier) that was given to stock Zen UI in its penultimate update? I'm on Evo11 (OSS vendor) and it has VoWiFi support for the aforementioned carrier.
Thanks again.
--- Edit ---
VoWiFi works on Jio without problems.

Heyyo @nnmanobala thanks man! Yeah encryption is important to me, so I made sure we support File-Based Encryption as AOSP has depreciated Full-Disk Encryption that our stock ROM used.
Tbh I'm unsure for that feature as I think it requires the launcher support it... So maybe those who use Pixel Launcher could answer this question?
For VoWiFi? I can't test that as I'm in Canada where they block VoLTE, ViLTE and VoWiFi on BYOD as they consider those "premium features... So no idea tbh if it works. Do you know if by chance it worked or not on LineageOS 17.1?

Heyyo, I just realized that the first official build of LineageOS 18.1 is up for Z01R! w00t! Thread updated

Hi !
I just got the new 18.1 lineage running on my phone ! Thanxs a lot for your work !!
Feels faster than the 17.1 .
I just can't figure out how to reactivate the "Screenshot" in the Power-(Button)-Menu.
Can Someone pls help or point me to a good source of Lineage Dokumentation ??

[DISCONTINUED][heart] LineageOS 18.1 (Android 11) for the Lenovo Z5 Pro GT

KNOWN BUGS
SafetyNet does not pass (Unfortunately, this is not possible as your SoC has hardware attestation... the workaround is to use unsupported mods like Magisk which tbh I haven't tried myself as I don't root my devices, but other users said that plus the SafetyNet Magisk mod works). I posted Rob's solution to SafetyNet / gPay here
SBC HD does not work

Heyyo, allow me to introduce myself. I am Marc "ThE_MarD" Bourgoin and I maintain LineageOS and TWRP for the LeEco Le Max 2 (X2) and was crowdfunded a zippo which I will maintain LineageOS for (with selinux enforcing of course) and TWRP as well. I also own an Asus Zenfone 5z (Z01R) which I maintain LineageOS and TWRP for and I was also donated a Motorola Moto X4 (Payton) which I maintain LineageOS and TWRP for.
I saw there wasn't much custom ROM development for heart and since we already have a pretty good sm8150-common tree set up? I decided to get heart working good on our LOS 18.1 trees, and it does! Everything works good, no major bugs.
I'd like to take this moment to also thank anyone who donated to the crowdfunding campaign for my zippo! Without you? I wouldn't have this epic device in my hands to work on.
Also MAJOR thanks to Zhenxiang Chen (aka pasta_con_tonno, Lucchetto) for all the amazing work he has done on zippo.
Special thanks goes out to Einar Gednochsson (aka kanstmablason, pete80pro) for organizing the crowdfunding campaign for my zippo and also a new one for KuranKaname so he can revamp our kernel.
Thanks also to hypnz, chema f, gawin and Lucky for also working in zippo and to HighwayStar who started the initial trees for heart (Lenovo z5 Pro GT) which zippo trees are based upon and Art_Chen for working on heart and zippo and also bringing us FOD Dimming and DC Dimming.
Thanks again to Zhenxiang and Chema f for figuring out and implementing the QFIL recovery and vbmeta while keeping the bootloader locked
Special thanks as well to @odei0funk @optional_toast @frostyfeety @VinciosFernandes who tested a lot of stuff for heart! Without their reports? It would have been a lot harder to accomplish what we did

On test21 build I uploaded today, I added power_profile needed for battery stats. Please test it to ensure battery usage stats work. If I don't hear any bug reports in about a week's time? I will merge all the heart commits into LineageOS and request official heart builds!

Great release
One question @ThE_MarD , my bootloader is unlocked, because the last TWRP I've installed, to flash with your ROM. To lock the bootloader and install your latest lineage release, do I just need to install this following TWRP?
TWRP for bootloader locked:
https://osdn.net/projects/twrp-for-heart/releases/p18120
Click to expand...
Click to collapse
Or I need something else?

Heyyo @rafman79 unfortunately it's not to simple as that, here's a guide:
Backup everything important off of the device as we will be formatting data
You need to QFIL back to stock https://forum.xda-developers.com/t/...t-l78032-stock-firmware-bootloop-fix.3915945/
Next, reboot to bootloader
Then type in...
Code:
fastboot flashing lock
Reboot to system
After it boots in? Reboot to bootloader so we can check it
In bootloader, type this...
Code:
fastboot OEM device-info
If it shows that your bootloader is locked? Then reboot into EDL mode and then flash either the TWRP bootloader locked or the Lineage Recovery version
Then flash required device firmware for LineageOS and then ROM and your GApps if you wish to use it
Reboot to system

Hello. Good stuff!
Is it all works: all slider functions and logic (e.g., taking a call by opening a slider), all rear and front cameras (including IR-camera), stable Wi-Fi, not false-triggered fingerprint?

Heyyo @Atom_Z , yes it all works, otherwise I wouldn't be applying for LineageOS official builds

great job @ThE_MarD ! I Flash your rom for two weeks,everything worked,but a little case of WIFI.
wifi can work but can not connect to a hide ssid.
big thanks for your work.you let my l78032 regain a new life!

Heyyo @niuxue3 , glad to hear you're really enjoying it!
Can you please provide info on your router? Is it WPA3 or WPA2 or WPA1? and is it using TKIP or AES?
I've also applied for official LineageOS 18.1 builds for heart! Just need to wait for LOS team to review

ThE_MarD said:
Heyyo @rafman79 unfortunately it's not to simple as that, here's a guide:
Backup everything important off of the device as we will be formatting data
You need to QFIL back to stock https://forum.xda-developers.com/t/...t-l78032-stock-firmware-bootloop-fix.3915945/
Next, reboot to bootloader
Then type in...
Code:
fastboot flashing lock
Reboot to system
After it boots in? Reboot to bootloader so we can check it
In bootloader, type this...
Code:
fastboot OEM device-info
If it shows that your bootloader is locked? Then reboot into EDL mode and then flash either the TWRP bootloader locked or the Lineage Recovery version
Then flash required device firmware for LineageOS and then ROM and your GApps if you wish to use it
Reboot to system
Click to expand...
Click to collapse
I'm trying install TWRP locked via EDL, but it doesn't install. It reboots but always on official LENOVO's recovery...

@rafman79 , sorry I should have mentioned, as soon as you QFIL flash recovery? Hold the power and volume down and once it reboots into bootloader? Reboot into recovery. If you reboot to system after QFIL install of recovery? The stock ROM will overwrite it with stock recovery.
[UPDATE]
w00t! We are approved for LineageOS 18.1 official builds! They should hopefully be coming within a week

ThE_MarD said:
Heyyo @niuxue3 , glad to hear you're really enjoying it!
Can you please provide info on your router? Is it WPA3 or WPA2 or WPA1? and is it using TKIP or AES?
I've also applied for official LineageOS 18.1 builds for heart! Just need to wait for LOS team to review
Click to expand...
Click to collapse
Thanks for your reply！
My route flash openwrt , using WPA2 PSK (CCMP)

@niuxue3 , hmm it should just work then... Can you please provide logcat?
How to capture logs | LineageOS Wiki
wiki.lineageos.org

Z5 Pro GT - Official LineageOS 18.1 Downloads Available
ThE_MarD said:
[UPDATE]
w00t! We are approved for LineageOS 18.1 official builds! They should hopefully be coming within a week
Click to expand...
Click to collapse
Done! https://download.lineageos.org/heart
Thanks for supporting this device & being active in this thread.
***

A new test build is going up. lineage-18.1-20210916-UNOFFICIAL-heart I'm testing the switch to Xiaomi sm8150 Android 11 NFC configs and NFC firmware as I'm guessing the problem is heart's NFC configs are only meant to work with ZUI vendor image if someone wants to test gPay
Release lineage-18.1 lineage-18.1-20210916-UNOFFICIAL-heart - LineageOS for heart - OSDN
Release lineage-18.1 lineage-18.1-20210916-UNOFFICIAL-heart - LineageOS for heart #osdn
osdn.net
UPDATE:
I got confirmation it works! gPay now works properly. I have merged it onto the official LOS branch so the next official build for heart will include it. I'm guessing every Wednesday will be the day for our weekly builds.
Optional_Toast made this guide in order to get gPay working:
[Forwarded from Rob M]
Google Pay - Lineage OS 18.1 - 16/09/2021 - Working
I have made a purchase in an actual shop for goods using Google Pay on Heart. My device has a locked Bootloader.
These are the steps I took.
1. Install Magisk
2. Hide the Magisk app
3. Turn on MagiskHide (I did nothing more than this, I didn't hide any other apps rather than those set by default, you may need to hide your bank apps if you have them installed, but I cannot confirm this)
4. Install MagiskHidePropsConf - reboot
5. Install a terminal app (I used Termix)
6. Open terminal and type props (if you're using Termix run su first to grant permissions)
7. Follow institutions https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#usage I chose the "Edit device fingerprint" option and selected the Pixel 5 as the device id.
8. I cleared data for Google Play Services and Google Play Store and rebooted
9. when you open Google Pay you should be able to add card
10. Go to shop, consume.

Heyyo, err, unfortunately, I have some bad news... Recently on LineageOS they merged a repo for AndroidTV devices that used the same KeyHandler name for their special remote buttons which is the same name that heart uses for the slider which broke our build... I'll be renaming it to DeviceSettings which should prevent that error from happening. Since the official build already failed though? We will have to wait until next week for another official build, oof... In the meantime? There is that unofficial test build with the NFC changes that works great with gPay (as long as you do SafetyNet haxxs which tbh I've never tried so someone else would need to guide you guys). I'll probably also be merging a bunch of test stuff I have for display blob updates and reworking the ramdisk to try and make the boot a little faster and also a minor HIDL manifest cleanup.
Update: ok, issue was fixed. A new build was queued so we should still be getting an official build today!

Official build is there and it is glorious.

Heyyo @blairpoodle , I'm glad you're enjoying the official builds bro! A lot of effort was put into our Lenovo sm8150-common trees with a major special thanks going to Zhenxiang Chen for getting it all started and also Rob M for testing almost every build since I started working on heart and helping to get it working on our trees too.

Hi. Problems with bluetooth headphones using the Aptx protocol. Connected but no sound. SBC headphones work without problems.

[DISCONTINUED][ZS620KL] LineageOS 19.1 (Android 12.1) for the Asus Zenfone 5z

Features over Stock
FM Radio, File-Based Encryption (which allows power-off Alarm to actually work and no annoying PIN prompt half-ways through boot), QTI Bluetooth stack
KNOWN BUGS
ViLTE does not work
4K UHD Video recording does not work in LineageOS Snap Camera app. (A workaround is to use other camera apps like OpenCamera or Gcam Mods)
Touch sometimes doesn't work in Lineage Recovery. The workaround is to use the volume buttons to move around the menu and power to select or to reboot to recovery.
SafetyNet does not pass (Unfortunately, this is not possible as your SoC has hardware attestation... the workaround is to use unsupported mods like Magisk which tbh I haven't tried myself as I don't root my devices, but other users said that plus the SafetyNet Magisk mod works)
Frequently Asked Questions
Is there a different way to unlock the bootloader than the Asus official method? You can try the unofficial bootloader unlock here

Heyyo, a new test build is going up! It will be ready within 10 minutes of this post. lineage-19.1-20220406-UNOFFICIAL-Z01R is stable and pre-official! This is what the official builds will be like whenever 19.1 goes live (whenver that is? No idea lol). Offline charging bug is fixed and QTI bluetooth too thanks to Edward's kernel.
Release lineage-19.1 lineage-19.1-20220406-UNOFFICIAL-Z01R - lineageos-for-z01r - OSDN
Release lineage-19.1 lineage-19.1-20220406-UNOFFICIAL-Z01R - lineageos-for-z01r #osdn
osdn.net

ThE_MarD said:
Heyyo, a new test build is going up! It will be ready within 10 minutes of this post. lineage-19.1-20220406-UNOFFICIAL-Z01R is stable and pre-official! This is what the official builds will be like whenever 19.1 goes live (whenver that is? No idea lol). Offline charging bug is fixed and QTI bluetooth too thanks to Edward's kernel.
Release lineage-19.1 lineage-19.1-20220406-UNOFFICIAL-Z01R - lineageos-for-z01r - OSDN
Release lineage-19.1 lineage-19.1-20220406-UNOFFICIAL-Z01R - lineageos-for-z01r #osdn
osdn.net
Click to expand...
Click to collapse
This rom now official right ? I saw it on lineage official download with nightly status.
Anw, can i just download the nightly and update using updater or should i use sideload to update ?

Heyyo @semuabaik, yes we are official now! One of 19 devices that got official builds of 19 heh
You will need to manually update to official as OTA via Lineage Updater only works if you're already on an official build that is the same version. Upgrading versions must be done manually as any additions like GApps would need to be updated too.

ThE_MarD said:
Heyyo @semuabaik, yes we are official now! One of 19 devices that got official builds of 19 heh
You will need to manually update to official as OTA via Lineage Updater only works if you're already on an official build that is the same version. Upgrading versions must be done manually as any additions like GApps would need to be updated too.
Click to expand...
Click to collapse
Ah so the step is the same when i updated from 18 to 19.1
But i can't get my laptop to detect my phone anymore since i update to 19.1
I tried to change the cable, different slots, etc but nothing worked then i used the same cable to my brother's phone and every cables i tried worked.

@semuabaik you can use USB OTG if you have a USB flash drive or micro SDcard

I am to install lineageos 19, however when I install GApps, the phone gets stuck at the boot animations. I have wiped the phone and started from scratch 3 times. Any thoughts?
Edit: I am going to try the GApps version that doesn't specify 64 bit and report back.

Update, it boot loops no matter which version of GApps is used. I might go back to one of the builds that isn't a nightly and try that.

ThE_MarD said:
Heyyo @semuabaik, yes we are official now! One of 19 devices that got official builds of 19 heh
Click to expand...
Click to collapse
This is a fantastic surprise. Thanks so much @ThE_MarD & team! It is working brilliantly. Not at all what I'd expect from a nightly.
semuabaik said:
can't get my laptop to detect my phone anymore since i update to 19.1
Click to expand...
Click to collapse
If you are running Windows, download the (Windows 8) USB drivers directly from ASUS support. Unpack and direct device manager to the unpacked drivers. Works up to W10 for ADB in powershell (prefix with .\), not sure about W11.
Cyb3rk1ll said:
Update, it boot loops no matter which version of GApps is used.
Click to expand...
Click to collapse
First time go for me & device can be restarted without issue. Wrote the recovery image, OS and gapps to SD rather than using ADB, but otherwise followed the official instructions using:
20220516 nightly
gapps version MindTheGapps-12.1.0-arm64-20220416_174313
GL if you give it another go!

Heyyo @Cyb3rk1ll , can you please specify which GApps and package name it is you are trying to install?
@Incoherent Ian , tbh it's crazy how good Z01R works on custom ROMs! It actually works best out of all my devices too haha... Only real downside is Widevine L1 because Asus wiped DRM keys on bootloader unlock...
From what I've heard? Newer Asus devices don't wipe DRM keys, so they can do L1 the lucky buggers

Hi, its possible relock the bootloader s SafetyNet pass im test?

So I believe I managed to brick my phone while retaining access to TWRP... I'm kinda panicking right now and would appreciate some help.
(I never flashed GAPPs throughout this as I want to degoogle my life, but I had them before)
I was running EvolutionX and decided to clean flash the latest LineageOS build. No errors, but booting resulted in it rebooting straight back to recovery. TWRP logs mentioned Android Rescue Party with reason enablefilecrypto.
The only thing I did that wasn't usual was flashing a new version of TWRP directly to boot_a instead of just boot.
Wiped Data and Cache, tried again, same thing. Restored my EvolutionX backup. Now it just got stuck on the Powered by Android screen, didn't do anything. Clean flashed EvolutionX and after a few reboots it entered a cycle of lockscreen for 2 seconds - boot animation - lockscreen.
This is when I decided to use the Linea recovery, use ADB sideloas and follow the installation steps as closely as possible, which resulted in the same recovery bootloop. Somewhere throughout all this I tried the LineageOS build just before the last (maybe the latest was broken) to no avail.
Sorry for the wall of text but I wanted to explain all that I've tried. I'm not sure what to do anymore. What can I do?

Heyyo @DarkAlpha.Sete sorry but for some reason, I didn't get a notification for your post.
Just to check, when you said clean flash, did you format data? Wiping data in TWRP doesn't count as it doesn't format the part of the partition that handles encryption and I'm unsure if EvoX or other ROMs even have any encryption on Z01R.
On LineageOS, we use File-Based Encryption to ensure future compatibility with encryption on Android as Google has depreciated Full-Disk Encrytption back on A10. ZenUI stock ROM used FDE, so definitely coming from stock a Format Data is required (and tbh recommended on any device anyways).
Your device isn't bricked, it's just a matter of finding the solution and I suspect it is encryption is the issue.

ThE_MarD said:
Heyyo @DarkAlpha.Sete sorry but for some reason, I didn't get a notification for your post.
Just to check, when you said clean flash, did you format data? Wiping data in TWRP doesn't count as it doesn't format the part of the partition that handles encryption and I'm unsure if EvoX or other ROMs even have any encryption on Z01R.
On LineageOS, we use File-Based Encryption to ensure future compatibility with encryption on Android as Google has depreciated Full-Disk Encrytption back on A10. ZenUI stock ROM used FDE, so definitely coming from stock a Format Data is required (and tbh recommended on any device anyways).
Your device isn't bricked, it's just a matter of finding the solution and I suspect it is encryption is the issue.
Click to expand...
Click to collapse
Intially, do I did not. Something I later found to be a mistake when chatting with the guys over at IRC. I also tried clean flashing with a regular format again to no avail. Even tried the LOS recovery and followed the install instructions as closely as possible (sideloading). TWRP logs would show a message about failing to enable file based encryption (Android Rescue Party). LOS just gave me a screen asking to factory reset, which solved nothing.
I also tried just flashing EvoX again (had no encryption), but it just rebooted back to recovery. Do note that every time I flashed LineageOS/EvolutionX I either formatted or wiped data and tried on both slots most of the times. Nothing changed. Another thing of note is that I was never flashing gapps (trying to degoogle).
Later I even tried LOS 18.1, but no boot as well. By the way, 19 rebooted to recovery right after the Powered by Android screen, but 18.1 got to the boot animation... and stayed there for 15 minutes after which I gave up and flashed stock via the bootloader. Tried flashing LOS again after stock - same thing -, so I'm on stock now.
Sorry for this insane wall of text, but I didn't want to miss anything. Hopefully anything can be taken out of this.

Hmm super odd... Ok, next time you try it, can you check via TWRP if there is anything in here? And if so download a copy and send it to me?
/sys/fs/pstore
Or you can do via terminal
Code:
adb pull /sys/fs/pstore

Dear @ The_Mard
First and foremost, fantastic and fabulous development. You have practically extended the life of the Asus Zenfone 5Z by a straight 12 months! As such in India, 5G - with all band support will take 6 to 12 months (especially handsets with mmwave support), till then I can manage with 5Z.
I have 3 sets of queries / doubts which I have posted as 3 different posts - for better understanding and clarity! When you do have spare time, please do share your thoughts - in the following posts!
I have 3 - 5Z mobiles and I use 2 as my daily driver and 1 as back-up. Yet to update Lineage OS - planning to start with Lineage OS from September 1st. Got to clarify before going all out.
@ThE_MarD

My 1st / First Set of Queries! (My Handset is ZS621KL (Asus Zenfone 5z - 8 GB - 256 GB)
Would like to understand, whether the Lineage OS 19.x will support the standards features of Qualcomm 845 Chipset?
1. Cellular LTE Carrier Aggregation Support - 2x20 MHz carrier aggregation (Up-Load), 5x20 MHz carrier aggregation (Download).
I'm on Jio Network and I have CA supported SIM. Standard Asus ROM used to indicate 4G+ as the network indicator. Will Lineage OS support 2CA for Upload and 5CA for download?
2. Wi fi Support - Does it support Peak 256 QAM Wi-Fi, MU-MIMO & Multi-gigabit Wi-Fi. For MU-MIMO, is it 2x2 or 3x3?
3. Will Lineage OS support Qualcomm® Qualcomm® Quick Charge™ 4 technology?
4. Does Lineage OS support all the APIs - Vulkan® 1.1, OpenCL™ 2.0 Full, DirectX® 12 & OpenGL® ES 3.2?
5. Will Lineage OS support Qualcomm® aptX™ audio playback support & Qualcomm® aptX™ HD?
@ThE_MarD

My 2nd / Second Set of Queries!
These set of queries are from your initial logs #
1. Is the ViLTE working now?
2. any plans to enable 4K UHD Video recording in LineageOS Snap Camera app itself?
3. Is there anyway to activate Widevine L1 using some method - from any other Asus Phone or any other 845 Chipset model or something of that sort? Will writing to Asus through email or Asus Forums help? I can attempt, in case if it's feasible!
@ThE_MarD

My 3rd & Final Set of Queries!
1. Lineage OS Updates - When I check for updates in Lineage OS, I see the update files listed as full 900 MB or so - which means it's a full file download.
Not only it takes bandwidth, but, it seems to rewrite the whole code once again and not merely update the changes alone.
The official upgrades used to be incremental and small in size - where-in I know that it only updates the relevant part of the code which requires change.
Is my understanding right or am I off the standard lineage logic?
I'm also worried that one such FULL LINEAGE update one day will knock off my data and will start as if it's going to be a FRESH upgrade! it will disturb my day to day life an hence such questions!
2. Since I will be moving to Lineage OS, is there any app - which If I install in mobile will keep sending the errors / bugs as log file to the developer? This will help pass the bugs issues / automatically!
If my understanding is right, then the lines in the log file will be (possibly) coloured differentially - which means all error lines will be RED in colour which will help you to address the issues!
Point 2 above is just my wish list and hence was checking if an option of that sort is possible - either automatically or manually!
@ThE_MarD

Develop Bugs

welcome